Emergency Action Plan (EAP) and First Responders Sample Clauses

Emergency Action Plan (EAP) and First Responders. (Ski Patrol)
Sample 1
AutoNDA by SimpleDocs

Related to Emergency Action Plan (EAP) and First Responders

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Emergency Response Partners must develop, maintain, and carry out a response plan for public water system emergencies, including disease outbreaks, spills, operational failures, and water system contamination. Partners must notify DWS in a timely manner of emergencies that may affect drinking water supplies.

  • Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-­‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.

  • 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.

  • Contingent Emergency Response 1. In order to ensure the proper implementation of contingent emergency response activities under Part 4 of the Project (“Contingent Emergency Response Part”), the Recipient shall ensure that: (a) a manual (“CERC Manual”) is prepared and adopted in form and substance acceptable to the Association, which shall set forth detailed implementation arrangements for the Contingent Emergency Response Part, including: (i) any structures or institutional arrangements for coordinating and implementing the Contingent Emergency Response Part;

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • SCOPE OF SERVICES/CASE HANDLING A. Upon execution by GPM, attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client provides authorization to seek appointment as Lead Plaintiff in the class action, while the Attorneys will seek to be appointed Class Counsel. If this occurs, the Litigation will be prosecuted as a class action. B. If you obtain access to non-public information during the pendency of the Litigation, you must not engage in transactions in securities. C. Attorneys are authorized to prosecute the Litigation. The appointed Lead Plaintiffs will monitor, review and participate with counsel in the prosecution of the Litigation. The Attorneys shall consult with the appointed Lead Plaintiffs concerning all major substantive matters related to the Litigation, including, but not limited to, the complaint, dispositive motions and settlement. Because of potential differences of opinion between Clients concerning, among other things, strategy, goals and objectives of the Litigation, the Attorneys shall consult with the appointed Lead Plaintiffs as to the courses of action to pursue. The Client agrees to abide by the decisions of the appointed Lead Plaintiffs, which shall be final and binding on all Clients. D. GPM is given the authority to opt the Client out of any class action proceeding relating to the claims authorized herein and/or pursue the Client claim individually in a group action, if the Client is not appointed Lead Plaintiff and GPM is not appointed Class Counsel. E. The Attorneys shall provide sufficient resources, including attorney time and capital for payment of costs and expenses, to vigorously prosecute the Litigation. F. Any recovery from defendants that the Attorneys are responsible for will be divided among class members based on the recognized loss by each class member as calculated by a damage allocation plan which will be prepared by a financial expert or consultant, provided to the appointed Lead Plaintiffs, be subject to the Court's approval and will account for such factors as size of securities ownership, date of purchase, date of sale and continued holdings, if any. Under the rules governing class action litigation, while the Lead Plaintiffs recover according to the same formula as other class members, the Court may approve, upon application therefore, reimbursement of the Lead Plaintiffs’ reasonable costs and expenses directly related to the representation of the class. Examples are lost wages and travel expenses associated with testifying in the action.

  • REQUIRED PRICE PROPOSAL RESPONSE All pricing must be fixed cost, inclusive of all expenses and fees if this Statement of Work proposal is for a fixed price agreement. (Remove if Time and Materials agreement) For Time and Materials the pricing proposal must include estimated effort hours, hourly rate for proposed personnel, projected timeline, including timing expectations for the State functional and technical resources and be submitted as a separate document from the rest of the proposal. (Remove if not Time and Materials)

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!