Operational Acceptance Tests Sample Clauses

Operational Acceptance Tests. The Operational Acceptance Tests (and repeats of such tests) shall be the primary responsibility of the Purchaser, but shall be conducted with the full cooperation of the Supplier during Commissioning of the System (or Subsystem[s] if specified in the Contract), to ascertain whether the System (or major component or Subsystem[s]) conforms to the Technical Requirements and meets the standard of performance quoted in the Supplier’s bid, including, but not restricted to, the functional and technical performance requirements. The Operational Acceptance Tests will be conducted as specified in the SCC, the Technical Requirements and/or the Agreed and Finalized Project Plan.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Operational Acceptance Tests. Pursuant to GCC Clause 28 and related SCC clauses, the Purchaser (with the assistance of the Supplier) will perform the all tests on the System and its Subsystems following Installation to determine whether the System and the Subsystems meet all the requirements mandated for Operational Acceptance.
Sample 1Sample 2See All (5)
Operational Acceptance Tests. On completion of the hot commissioning, the Contractor requests the commencement of operational acceptance tests from the Project Manager. The Contractor produces a detailed operational acceptance test procedure in advance for acceptance by the Project Manager. This is shown on the Accepted Programme. The control system is pre-tuned in order to prevent deviation limits of process parameters from exceeding the maximum permissible values defined during the technical clarification stages, and ensure safe operation of Plant. After satisfactory completion of installation and commissioning of the control system in conjunction with the plant, the Contractor demonstrates that the control system successfully performs the following:  Plant operated manually (local and/or remote).  Plant operated on manual with all remote supervisory/monitoring functions in the Tippler Control Room.  Plant operated automatically (start-up, sequential control and shut-down) with all remote supervisory/monitoring functions.  Plant operating on modulating control, responding to a safe and stable state for dynamic changes in the plant.  All individual operating and control functions such as alarms, displays, report generation and historian views perform successfully. The Contractor notifies completion of operational acceptance tests and requests the commencement of optimisation of the Plant and control from the Project Manager.
Sample 1Sample 2
Operational Acceptance Tests. 27.2.1 The Operational Acceptance Tests (and repeats of such tests) shall be the primary responsibility of the Purchaser (in accordance with GCC Clause 10.9), but shall be conducted with the full cooperation of the Supplier during Commissioning of the System (or Subsystem[s] if specified in the Contract), to ascertain whether the System (or major component or Subsystem[s]) conforms to the Technical Requirements and meets the standard of performance quoted in the Supplier’s bid, including, but not restricted to, the functional and technical performance requirements. The Operational Acceptance Tests during Commissioning will be conducted as specified in the SCC, the Technical Requirements and/or the Agreed and Finalized Project Plan. At the Purchaser’s discretion, Operational Acceptance Tests may also be performed on replacement Goods, upgrades and new version releases, and Goods that are added or field-modified after Operational Acceptance of the System. 27.2.2 If for reasons attributable to the Purchaser, the Operational Acceptance Test of the System (or Subsystem[s] or major component if allowed by the SCC and/or the Technical Specifications) cannot be successfully completed within the period specified in the SCC, from the date of Installation or any other period agreed upon in writing by the Purchaser and the Supplier, the Supplier shall be deemed to have fulfilled its obligations with respect to the technical and functional aspects of the Technical Specifications, SCC and/or the Agreed and Finalized Project Plan, and GCC Clause 28.2 and 28.3 shall not apply.
Sample 1Sample 2
Operational Acceptance Tests. The Purchaser (with the assistance of the Supplier) will perform the following tests on the System and its Subsystems following Installation to determine whether the System and the Subsystems meet all the requirements mandated for Operational Acceptance. Unit testing, validate that each individual module of the EHRS is working properly. Functional testing, validate that mandatory functional requirements of the System supplied work properly. It is necessary to conform that the System supplied conforms to the specification. Integration testing, validate that combined parts or modules of the EHRS are working properly. Volume testing, validate that any values that may become large over time (such as accumulated counts, logs, and data files) of the System can be accommodated by the program and will not cause the System to stop working or degrade its operation in any manner. Performance testing, validate that the System is in compliance with the Performance Requirements which will be established by the committee of representatives.
Sample 1

Related to Operational Acceptance Tests

  • Acceptance Tests 11.1 If the Contract provides acceptance tests for Goods and/or the result of Services after their completion and/or delivery to the Purchaser, the acceptance shall only be considered as definitive when such tests have demonstrated the compliance of the Goods and/or the result of the Services to the requirements in the Contract. 11.2 Where the Contract provides for an acceptance procedure in the presence of both parties, at the successful completion of such procedure, the Purchaser shall issue the Supplier with an acceptance certificate which shall authorise the Supplier to invoice the Purchaser for any payment due on such acceptance. 11.3 The Purchaser shall at its discretion be entitled to issue and acceptancecertificate with reserves. The Supplier shall be obliged to remedy any non-conformities within the period set out in the acceptance certificate. Any payment which would otherwise have been due on acceptance may be withheld by the Purchaser in whole or part until the non- conformities underlying the reserves have been remedied.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Final Acceptance All Work has been completed and accepted by the County. The Contractor has provided all required close-out documentation and items as required by the Detailed Scope of Work for the specific Job Order, and these items and have accepted and approved by the County

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

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

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