Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.
Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.
Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester. 7.2.2 No later than thirty (30) Days prior to the earlier of the Scheduled Substantial Completion Date or Substantial Completion, Design-Builder shall provide to Owner for review a detailed testing plan for the Performance Tests (other than for air emissions). Owner and Design-Builder shall agree upon a testing plan that shall be consistent with the Performance Test Protocol contained in Exhibit A hereto. After such agreement has been reached, Design-Builder shall notify the Owner five (5) business days prior to the date Design-Builder intends to commence the Performance Tests and shall notify the Owner upon commencement of the Performance Tests. Owner and Independent Engineer each have the right to witness all testing, including the Performance Tests and any equipment testing, whether at the Site or at the Subcontractor’s or equipment supplier’s premises during the course of this Agreement. Notwithstanding the foregoing sentence, Owner shall bear the costs of providing a witness to any such testing and all such witnesses shall comply at all times with Design-Builder’s, Subcontractor’s or equipment supplier’s safety and security procedures and other reasonable requirements, and otherwise conduct themselves in a manner that does not interfere with Design-Builder’s, Subcontractor’s or equipment supplier’s activities or operations. 7.2.3 Design-Builder shall provide to Owner a Performance Test report (excluding results from air emissions testing), including all applicable test data, calculations and certificates indicating the results of the Performance Tests and, within five (5) business days of Owner’s receipt of such results, Owner, Independent Engineer and Design-Builder will jointly inspect such Work and review the results of the Performance Tests to verify that the Performance Guarantee Criteria have been met. If Owner or Independent Engineer reasonably determines that the Performance Guarantee Criteria have not been met, Owner shall notify Design-Builder the reasons why Owner determined that the Performance Guarantee Criteria have not been met and Design-Builder shall promptly take such action or perform such additional work as will achieve the Performance Guarantee Criteria and shall issue to the Owner another notice in accordance with Section 7.2.2; provided however that if the notice relates to a retest, the notice may be provided no less than two (2) business days prior to the Performance Tests. Such procedure shall be repeated as necessary until Owner and Independent Engineer verifies that the Performance Guarantee Criteria have been met. 7.2.4 If Owner, for whatever reason, prevents Design-Builder from demonstrating the Performance Guarantee Criteria within thirty (30) Days of Design-Builder’s notice that the Plant is ready for Performance Testing, then Design-Builder shall be excused from demonstrating compliance with the Performance Guarantee Criteria during such period of time that Design-Builder is prevented from demonstrating compliance with the Performance Guarantee Criteria; provided however that Design-Builder will be deemed to have fulfilled all of its obligations to demonstrate that the Plant meets the Performance Guarantee Criteria should such period of time during which Design-Builder is prevented from demonstrating the Performance Criteria exceed thirty (30) Days or extend beyond the Final Completion Date.
Performance Adjustment One-twelfth of the annual Performance Adjustment Rate will be applied to the average of the net assets of the Portfolio (computed in the manner set forth in the Fund's Declaration of Trust or other organizational document) determined as of the close of business on each business day throughout the month and the performance period.
Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.
Performance Measure Grantee will adhere to the performance measures requirements documented in
Performance Measurement The Uniform Guidance requires completion of OMB-approved standard information collection forms (the PPR). The form focuses on outcomes, as related to the Federal Award Performance Goals that awarding Federal agencies are required to detail in the Awards.
Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.
Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6. (b) If the Operator does not comply with the Operator Performance Level then the Access Holder must pay to QR Network the amount determined in accordance with Schedule 5 as part of the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following QR Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to QR Network within fourteen (14) days after receipt of a Tax Invoice from QR Network. (c) If QR Network does not comply with the QR Network Performance Level then QR Network will credit to the Access Holder the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following the Access Holder becoming entitled to that amount. Where there is no next Billing Period, QR Network must pay such amount to the Access Holder within fourteen (14) days after receipt of a Tax Invoice from the Access Holder. (d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may agree on varied Performance Levels and any associated variations to the Agreement including the Base Access Charges and the Train Service Description. If the Parties are unable to agree to such variations, then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 5.6(e). (e) In the event that the Access Holder and/or the Operator (i) does not comply in any material respect with the Train Service Description; and (ii) the Access Holder fails to demonstrate to the reasonable satisfaction of QR Network when requested to do so, that the Access Holder will consistently comply with the Train Service Description for the remainder of the Term then, following consultation with the Access Holder, QR Network will be entitled to: (iii) vary the Train Service Description to a level it reasonably expects to be achievable by the Access Holder for the remainder of the Term having regard to the extent of previous compliance with the Train Service Description (ignoring, for the purpose of assessing previous compliance, any non-compliance to the extent that the non-compliance was attributable to a Railway Operator (other than the Access Holder) or to QR Network); and (iv) vary the Agreement (including, without limitation, the Operator Performance Level and the Base Access Charges) to reflect the impact of the change in the Train Service Description. (f) The Access Holder shall be entitled to dispute any variation proposed by QR Network pursuant to Clause 5.6(e) and such dispute will be referred to an expert for resolution in accordance with Clause 17.3.
Performance Delay Time is of the essence in the Vendor’s performance of this Agreement. If at any time it appears to Vendor that it may not meet any of the performance schedules or the scheduled completion date of the services to be performed for any reason, including labor disputes, Vendor shall immediately by verbal means (to be confirmed in writing) notify Customer of the reasons for and the estimated duration of such delay. If requested by Customer, Vendor shall make every effort to avoid or minimize the delay to the maximum extent possible including the expenditure of premium time. Any additional cost caused by these requirements of Customer shall be borne by Vendor, unless the delay in performance arises out of causes beyond the control and without the fault or negligence of Vendor or its subcontractors within the meaning of the Cancellation- Default clause herein. The foregoing requirements are in addition to any of Customer’s other rights and remedies as may be provided by law or this Agreement.