Operational Acceptance Tests Sample Clauses

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.

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.

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.

Operational Acceptance Tests. 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.

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.