Demonstration Tests Required for Commercial Operation Sample Clauses

Demonstration Tests Required for Commercial Operation. The Demonstration tests required for commercial operation is summarized as follows. - Gas Turbine Fuel Oil Firing - Gas Turbine Fuel Switching - Gas Turbine Startup - Startup Durations - CTG Response Characteristics - Generators Leading/Lagging Operation - Minimum Load Operation - Automatic Generation Control The following will be the acceptance criteria for the Owner Demonstration Tests required for Commercial Operation unless noted otherwise. -------------------------------------------------------------------------------- EPC - Exhibit D TENASKA GEORGIA GENERATION PROJECT ACCEPTANCE TEST GUIDELINES, PROCEDURES AND SPECIFCATIONS Date 9/13/99 --------------------------------------------------------------------------------
AutoNDA by SimpleDocs

Related to Demonstration Tests Required for Commercial Operation

  • Money Market Fund Compliance Testing and Reporting Services Subject to the authorization and direction of the Trust and, in each case where appropriate, the review and comment by the Trust’s independent accountants and legal counsel, and in accordance with procedures that may be established from time to time between the Trust and the Administrator, the Administrator will:

  • Quality Assurance/Quality Control Contractor shall establish and maintain a quality assurance/quality control program which shall include procedures for continuous control of all construction and comprehensive inspection and testing of all items of Work, including any Work performed by Subcontractors, so as to ensure complete conformance to the Contract with respect to materials, workmanship, construction, finish, functional performance, and identification. The program established by Contractor shall comply with any quality assurance/quality control requirements incorporated in the Contract.

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.

  • Additional Compliance If any Proposed Key Holder Transfer is not consummated within forty-five (45) days after receipt of the Proposed Transfer Notice by the Company, the Key Holders proposing the Proposed Key Holder Transfer may not sell any Transfer Stock unless they first comply in full with each provision of this Section 2. The exercise or election not to exercise any right by any Investor hereunder shall not adversely affect its right to participate in any other sales of Transfer Stock subject to this Section 2.2.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

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