Operational Acceptance Tests definition

Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed Project Plan to be carried out to ascertain whether the System, or a specified Sub system, is able to attain the functional and performance requirements specified in the Technical Requirements and Agreed Project Plan, in accordance with the provisions of GCC Clause 27.2 (Operational Acceptance Test).
Operational Acceptance Tests means the tests specified in the Contract to be carried out to ascertain whether the System, or a specified Subsystem, is able to attain the functional and performance requirements specified in the Contract, in accordance with the provisions of the SCC;
Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed and Finalized Project Plan to be carried out to ascertain whether the System, or a specified Subsystem, is able to attain the functional and performance requirements specified in

Examples of Operational Acceptance Tests in a sentence

  • Upon the successful conclusion of the Operational Acceptance Tests, the Supplier shall notify the Purchaser of its request for Operational Acceptance Certification, in accordance with GCC Clause 27.3.3. The Purchaser shall then issue to the Supplier the Operational Acceptance Certification in accordance with GCC Clause 27.3.3 (a), or shall notify the Supplier of further defects, deficiencies, or other reasons for the failure of the Operational Acceptance Test.

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

  • The Supplier shall notify the Purchaser upon completion of the necessary changes, modifications, and/or additions and shall request the Purchaser to repeat the Operational Acceptance Tests until the System achieves Operational Acceptance.

  • The Operational Acceptance Tests shall be the primary responsibility of NIA, but shall be conducted with the full cooperation of the Bidder.

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

  • The Operational Acceptance Tests will be conducted as specified in the SCC, the Technical Requirements and/or the Agreed and Finalized Project Plan.

  • Unless otherwise specified in the SCC, the Operational Acceptance Tests during Commissioning will be conducted as specified in the Technical Requirements and/or the Agreed Project Plan.

  • If the supplied systems fails to pass the Operational Acceptance Test(s) then NIA may consider terminating the Contract to the risk and cost of Bidder.

  • Unless otherwise specified in the SCC, the Operational Acceptance Tests during Commissioning will be conducted as specified in the Technical Requirements and/ or the Agreed Project Plan.

  • Upon the successful conclusion of the Operational Acceptance Tests, the Supplier shall notify the Procuring Entity of its request for Operational Acceptance Certification, in accordance with GCC Clause 27.3.3. The Procuring Entity shall then issue to the Supplier the Operational Acceptance Certification in accordance with GCC Clause 27.3.3 (a), or shall notify the Supplier of further defects, deficiencies, or other reasons for the failure of the Operational Acceptance Test.


More Definitions of Operational Acceptance Tests

Operational Acceptance Tests means the tests specified in the Technical Requirements and
Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed and Finalized Project Plan to be carried out to ascertain whether the System, or a specified Subsystem, is able to attain the functional and performance requirements specified in the Technical Requirements and Agreed and Finalized Project Plan, in accordance with the provisions of GCC Clause 27.2 (Operational Acceptance Test). (vi) “Operational Acceptance” means the acceptance by the Purchaser of the System (or any Subsystem(s) where the Contract provides for acceptance of the System in parts), in accordance with GCC Clause 27.3 (Operational Acceptance). (e) place and time (i) “Purchaser’s Country” is the country named in the SCC. (ii) “Supplier’s Country” is the country in which the Supplier is legally organized, as named in the Contract Agreement. (iii) “Project Site(s)” means the place(s) specified in the SCC for the supply and installation of the System. (iv) “Eligible Country” means the countries and territories eligible for participation in procurements financed by the World Bank as defined in the Procurement Guidelines. (Note: The World Bank maintains a list of countries from which Bidders, Goods, and Services are not eligible to participate in procurement financed by the Bank. The list is regularly updated and can be obtained from the Public Information Center of the Bank or its web site on procurement. A copy of the list is contained in the Section of the Bidding Documents entitledEligible Countries for the Provision of Goods, Works, and Services in Bank-Financed Procurement”). (v) “Day” means calendar day of the Gregorian Calendar. (vi) “Week” means seven (7) consecutive Days, beginning the day of the week as is customary in the Purchaser’s Country. (vii) “Month” means calendar month of the Gregorian Calendar. (viii) “Year” means twelve (12) consecutive Months. (ix) “Effective Date” means the date of fulfillment of all conditions specified in Article 3 (Effective Date for Determining Time for Achieving Operational Acceptance) of the Contract Agreement, for the purpose of determining the Delivery, Installation, and Operational Acceptance dates for the System or Subsystem(s). (x) “Contract Period” is the time period during which this Contract governs the relations and obligations of the Purchaser and Supplier in relation to the System, as specified in the SCC. (xi) “Defect Liability Period” (also referred to as the “Warranty Period”) means the period of validity of the warranties ...
Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed Project Plan to be carried out to ascertain whether the System, or a specified Sub system, is able to attain the functional and performance requirements specified in

Related to Operational Acceptance Tests

  • Operational Acceptance means the acceptance by the Employer of the Facilities (or any part of the Facilities where the Contract provides for acceptance of the Facilities in parts), which certifies the Contractor’s fulfillment of the Contract in respect of Functional Guarantees of the Facilities (or the relevant part thereof) in accordance with the provisions of GCC Sub-Clause 20.2.2 (Operational Acceptance) hereof after successful Commissioning followed by Trial - Operation.

  • Final Acceptance means final written acceptance of all the Work by the Commissioner, a copy of which shall be sent to the Contractor.

  • technical specification means, with respect to any Software, the document setting forth the technical specifications for such Software and included in the Statement of Work.

  • RDDS test Means one query sent to a particular “IP address” of one of the servers of one of the RDDS services. Queries shall be about existing objects in the Registry System and the responses must contain the corresponding information otherwise the query will be considered unanswered. Queries with an RTT 5 times higher than the corresponding SLR will be considered as unanswered. The possible results to an RDDS test are: a number in milliseconds corresponding to the RTT or undefined/unanswered.

  • DNS test Means one non-­‐recursive DNS query sent to a particular “IP address” (via UDP or TCP). If DNSSEC is offered in the queried DNS zone, for a query to be considered answered, the signatures must be positively verified against a corresponding DS record published in the parent zone or, if the parent is not signed, against a statically configured Trust Anchor. The answer to the query must contain the corresponding information from the Registry System, otherwise the query will be considered unanswered. A query with a “DNS resolution RTT” 5 times higher than the corresponding SLR, will be considered unanswered. The possible results to a DNS test are: a number in milliseconds corresponding to the “DNS resolution RTT” or, undefined/unanswered.

  • Interconnection Feasibility Study means either a Generation Interconnection Feasibility Study or Transmission Interconnection Feasibility Study.