Certain Performance Tests Sample Clauses

Certain Performance Tests. After Contractor has completed Performance Tests demonstrating compliance with all Performance Test requirements and Project performance necessary to achieve Substantial Completion, it shall give Notice to Owner and the Owner Engineer that it nominates such Performance Tests as a “Completed Performance Test.” Such Notice will be accompanied by a preliminary test report for such Completed Performance Test as soon as reasonably practicable but in no event more than 24 hours after the completion of such Completed Performance Test (or as soon thereafter as such reports are first available to Contractor) providing a summary of the Performance Tests on which it is based and including all raw data taken during such Performance Tests, and a final test report within 30 days thereafter. A Final Completed Performance Test report must be delivered to Owner in accordance with Appendix C. Contractor shall include sufficient results of testing in the preliminary test report to allow Owner to reasonably determine that there is a high probability that the final test results will confirm that the applicable conditions of Substantial Completion have been achieved. As soon as practicable, but in any event within 10 Business Days after receipt of Notice by Owner and the Owner Engineer, Owner shall give Notice to Contractor either concurring with, indication it cannot confirm concurrence, or rejecting the Completed Performance Test report and stating its reasons for such Notice, as the case may be. Such procedure shall be repeated until Contractor submits a Notice demonstrating Project performance necessary to achieve Substantial Completion or Final Completion, as applicable. Subject to Article 17, if Contractor’s Notice of a Completed Performance Test is rejected by Owner, such test shall not constitute a Completed Performance Test. Red River Environmental Products EPC Agreement
Sample 1
AutoNDA by SimpleDocs

Related to Certain Performance Tests

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

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

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • KEY PERFORMANCE INDICATORS 10.1 The Supplier shall at all times during the Framework Period comply with the Key Performance Indicators and achieve the KPI Targets set out in Part B of Framework Schedule 2 (Goods and/or Services and Key Performance Indicators).

  • Performance Measure The specific representation of a process or outcome that is relevant to the assessment of performance; it is quantifiable and can be documented

  • SCHEDULE FOR PERFORMANCE REVIEWS 8.1 The performance of each Employee in relation to his/her performance agreement shall be reviewed on the following dates with the understanding that reviews in the first and third quarter may be verbal if performance is satisfactory:

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Performance Delay The performance of a Party impacted by a Force Majeure Event, other than the satisfaction of payment obligations that have accrued under this Agreement, is delayed, without liability, for the duration of a Force Majeure Event.

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

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