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 (4)
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.
Sample 1Sample 2
Operational Acceptance Tests. 3.3.0 Pursuant to GCC Clause 27 and related SCC clauses, the Procuring Entity (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.
Sample 1
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.

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

  • Acceptance Test 7.1 Before delivering the Goods or Articles upon completion of the Services, the Seller shall carefully inspect and test them for compliance with the Specification. The Seller shall, if required by the Buyer, give the Buyer reasonable notice of such test and the Buyer shall be entitled to be represented thereat. The test shall hereinafter be referred to as the “Acceptance Test”.

  • Final Acceptance When the Project/Service or any portion thereof, as designated by the COUNTY, is ready for its intended use, the COUNTY and any other invited parties shall make an inspection of the Project/Service, to verify its completeness and develop a punch list of items needing completion or correction before final payment will be made. CONTRACTOR shall have ten (10) calendar days to correct all deficiencies. An eighty-dollar ($80.00) re-inspection fee shall be applied for the third inspection and any required re-inspection thereafter. The COUNTY shall have the right to exclude CONTRACTOR from those portions of the work designated as complete after the inspection; provided, however, that CONTRACTOR will have reasonable access for the time allotted by the COUNTY to complete or correct items on the punch list. When the work provided for under this Agreement has been completely performed by CONTRACTOR, and the final inspection has been made by the COUNTY, a final invoice will be prepared by the CONTRACTOR. The amount of this invoice, less any sums that may have been deducted or retained under the provisions of this Agreement, will be paid to CONTRACTOR in accordance with this Agreement, and after CONTRACTOR has agreed in writing to accept the balance due, as determined by the COUNTY, as full settlement of the account under the contract and of all claims in connection therewith. Occupancy by the COUNTY alone does not constitute final acceptance.

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

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

  • 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 thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

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