Interim Response Activities Mitigation Decision Matrix Sample Clauses

Interim Response Activities Mitigation Decision Matrix. The Interim Response Activities Mitigation Decision Matrix shown in Table 1 provides a description of two prioritized Exposure Categories with a corresponding range of Mitigation Options. TABLE 1 Interim Response Activities Mitigation Decision Matrix The Dow Chemical Company Exposure Category Exposure Category Description Mitigation Options Priority 1 Property presumed or determined to be impacted over 1,000 ppt TEQ proximate to a residence. Those residential properties identified through the above process where waters of the March 2004 flood event inundated, surrounded or approached the residence and those residential properties where it is otherwise known that the ATSDR action level is exceeded in soils proximate to the residence. Residential use, dioxin and furan concentrations in surface soil (0 to 1 inch and/or 0 to 8 inches for garden areas) above 1,000 ppt TEQ. Residential use includes properties with exposure potential that is similar to residential (e.g., schools, child care facilities, nursing homes, adult day care facilities). Mitigation options to be offered to the property owner(s): • Education and outreach • Provide temporary exposure barriers for exposed or poorly covered areas used by the owner : o Cover (e.g., sod, soil, raised garden bed, raised area, paving, mulch) o Augment existing cover o Provide paving or cover at entryways to minimize track-in of contaminated soils. • House cleaning, including cleaning of carpeting , interior ductwork, and other surfaces where contaminants may potentially accumulate • Identification of affected areas (known through sampling and or identification of flooding) by means agreeable to resident [e.g., flagging, marked aerial photographs]) • Monitoring, maintenance, and restoration of mitigation measures as necessary. • Removal of water and deposited sediment and soil after flooding events • Other reasonable mitigation measures identified and agreed to by property owner(s) based on their uses of the property Exposure
AutoNDA by SimpleDocs

Related to Interim Response Activities Mitigation Decision Matrix

  • Lobbying Activities - Standard Form - LLL No response Do not upload this form unless Vendor has reportable lobbying activities. There are Attributes entitled, “2 CFR Part 200 or Federal Provision - Xxxx Anti-Lobbying Amendment – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Disclosure of Lobbying Activities – Standard Form - LLL must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location.

  • Patent Filing Responsibilities and Costs 1. The invention and patent rights herein apply to any patent application or patents covering an invention made under this Agreement. Each Party is responsible for its own costs of obtaining and maintaining patents covering sole inventions of its employees. The Parties may agree otherwise, upon the reporting of any invention (sole or joint) or in any license granted.

  • Technical Objections to Grievance No grievance will be defeated or denied by any minor technical objection.

  • Primary Frequency Response Developer shall ensure the primary frequency response capability of its Large Generating Facility by installing, maintaining, and operating a functioning governor or equivalent controls. The term “functioning governor or equivalent controls” as used herein shall mean the required hardware and/or software that provides frequency responsive real power control with the ability to sense changes in system frequency and autonomously adjust the Large Generating Facility’s real power output in accordance with the droop and deadband parameters and in the direction needed to correct frequency deviations. Developer is required to install a governor or equivalent controls with the capability of operating: (1) with a maximum 5 percent droop ± 0.036 Hz deadband; or (2) in accordance with the relevant droop, deadband, and timely and sustained response settings from an approved Applicable Reliability Standard providing for equivalent or more stringent parameters. The droop characteristic shall be: (1) based on the nameplate capacity of the Large Generating Facility, and shall be linear in the range of frequencies between 59 and 61 Hz that are outside of the deadband parameter; or (2) based on an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. The deadband parameter shall be: the range of frequencies above and below nominal (60 Hz) in which the governor or equivalent controls is not expected to adjust the Large Generating Facility’s real power output in response to frequency deviations. The deadband shall be implemented: (1) without a step to the droop curve, that is, once the frequency deviation exceeds the deadband parameter, the expected change in the Large Generating Facility’s real power output in response to frequency deviations shall start from zero and then increase (for under-frequency deviations) or decrease (for over-frequency deviations) linearly in proportion to the magnitude of the frequency deviation; or (2) in accordance with an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. Developer shall notify NYISO that the primary frequency response capability of the Large Generating Facility has been tested and confirmed during commissioning. Once Developer has synchronized the Large Generating Facility with the New York State Transmission System, Developer shall operate the Large Generating Facility consistent with the provisions specified in Articles 9.5.5.1 and 9.5.5.2 of this Agreement. The primary frequency response requirements contained herein shall apply to both synchronous and non-synchronous Large Generating Facilities.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Deviation from Grievance Procedure The Employer agrees that, after a grievance has been discussed at Step 2 of the grievance procedure the Employer or his representatives shall not initiate any discussion or negotiations with respect to the grievance, either directly or indirectly with the aggrieved employee without the consent of the xxxxxxx or the Union.

  • DIRECTORS’ RESPONSIBILITY STATEMENT The Directors collectively and individually accept full responsibility for the accuracy of the information given in this announcement and confirm after making all reasonable enquiries that, to the best of their knowledge and belief, this announcement constitutes full and true disclosure of all material facts about the Proposed Acquisition, the Company and its subsidiaries, and the Directors are not aware of any facts the omission of which would make any statement in this announcement misleading. Where information in this announcement has been extracted from published or otherwise publicly available sources or obtained from a named source, the sole responsibility of the Directors has been to ensure that such information has been accurately and correctly extracted from those sources and/or reproduced in this announcement in its proper form and context.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • ADDITIONAL CONTRACTOR RESPONSIBILITIES 13 In addition to providing the services described in Paragraph 5 of this 14 Exhibit A, CONTRACTOR agrees to:

Time is Money Join Law Insider Premium to draft better contracts faster.