System Acceptance Test Clause Samples

System Acceptance Test. The Contractor shall conduct the System Acceptance Test. The SAT shall include thorough testing of final configurations. The purpose of the SAT is to demonstrate that the equipment was installed correctly and operates at the functional and performance levels required by this SOW and to verify that standards-compliant end-to-end workflows execute as anticipated. SAT shall include systematic end to end testing for local, state, and federal searches, including all response message types.

System Acceptance Test. 5.4.1 Supplier shall, at no cost to Host, test the System (with respect to the System, a “System Acceptance Test”) to confirm that the System (i) is capable of delivering Solar Services in accordance with the operational requirements that Supplier shall develop and provide to Host (the “System Requirements”) and (ii) meets all requirements established by the Local Distribution Company and any Applicable Law.‌‌ 5.4.2 Supplier shall notify Host not less than three (3) days prior to the conducting of System Acceptance Test and Host shall have the right, but not the obligation, to be present at and observe the System Acceptance Test, at no cost to Supplier. 5.4.3 If the results of the System Acceptance Test indicate that the System is capable of delivering electricity generated by the System to Host for eight (8) continuous hours using such instruments and meters as have been installed for such purposes and the System has been approved for interconnected operation by the Local Distribution Company, then Supplier shall send a written notice to that effect to Host (a “Completion Notice”), accompanied by a copy of the results of the System Acceptance Test. ARTICLE 6‌‌

System Acceptance Test. 14 B3708776.6 (a) Nexamp shall, at no cost to Host, test the System (with respect to the System, a “System Acceptance Test”) to confirmthat the System (i) is capable of delivering Solar Services in accordance with the operational requirements that Nexamp shall develop and provide to Host (the “System Requirements”) and (ii) meets all requirements established by the Local Distribution Company and any Applicable Law. Nexamp shall notify Host not less than three (3) days prior to the conducting of System Acceptance Test and Host shall have the right, but not the obligation, to be present at and observe the System Acceptance Test, at no cost to Nexamp.

System Acceptance Test. After successful completion of the functional testing the system shall be tested formally with full documentation using the previously approved recording form. The Contractor shall notify the Contracting Officer, in writing, forty eight (48) hours prior to system acceptance testing. The appointed Contracting Officer Representative will witness, date and stamp each test in the procedure. Acceptance of the system will be based upon the written approval of the Contracting Officer Technical Representative.

System Acceptance Test. After the fleet installations have been completed, the System Acceptance Test will be conducted to verify that the entire system is performing as intended. The System Acceptance Test will include the verification of: • Selling • Validation (check in / checkout) • Tests of system behavior under system failure conditions (network failure and SPS/SC failure) • Tests with connections to DriverMate and external interfaces System Acceptance shall not be granted until all previous validation testing of the Smart Card fare system has been completed and a System Acceptance Test is successfully completed. Successful completion of the System Acceptance test will occur if there are no major deficiencies that are recorded by FBC during the System Acceptance test. Minor deficiencies will be recorded onto a punch list and resolved during the warranty period. In the event of any major failure or reoccurring minor failure, system acceptance testing shall be halted until major failure or reoccurring minor failure rectification. FBC may determine after inspection and acceptance that an element is suitable for operation, although it may not be totally responsive to all contract requirements. FBC may conditionally accept that element of the system. Conditionally accepted elements will be available to FBC for use until Trapeze is able to initiate and execute corrective action. Trapeze understands that any conditional acceptance does not remove the liability to correct defects as required by the contract. Any defect will be recorded on a punch list and maintained until the warranty period is completed.

System Acceptance Test. The term "