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

Examples of Operational Acceptance Tests in a sentence

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

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

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

  • At the Procuring Entity’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.


More Definitions of Operational Acceptance Tests

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
Operational Acceptance Tests means the tests specified in the Volume I of the RFP 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, Final Project Work Plan and System Requirement Specifications in accordance with the provisions of GCC Clause 5.10.2 (Operational Acceptance Test).
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).
Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed Project Plan to be carried out to ascertain whether the SaaS Solution is able to attain the functional and performance requirements specified in the Technical Requirements and Agreed Project Plan, in accordance with the provisions of FCGP Clause7.8 (Commissioning and Acceptance). 1.1.2: Place and Timea. “Purchaser’s Country” is the country named in the FCSP.b. “Service Provider’s Country” is the country in which the Service Provider is legally organized, as named in the Framework Agreement.c. “Eligible Country” means the countries and territories eligible for participation in procurements financed by the World Bank as defined in the Procurement Regulations.d. “Day” means calendar day of the Gregorian Calendar.e. “Week” means seven (7) consecutive Days, beginning the day of the week as is customary in the Purchaser’s Country.f. “Month” means calendar month of the Gregorian Calendar.g. “Year” means twelve (12) consecutive months.h. “Effective Date” means the date of fulfilment of all conditions specified in the Framework Contract, for the purpose of determining the Delivery, Installation, and Operational Acceptance dates for the SaaS Solution.
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 Procuring Entity 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) “Procuring Entity’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 Government. (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 Procuring Entity’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 Procuring Entity 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 given by the Supplier commencing at date of the Operational Acceptance Certificate of the System or Subsystem(s), during which the Supplier is responsible for defects with respect to the System (or the relevant Subsystem[s]) as provided in GCC Clause 29 (Defect Liability). (xii) “The Post-Warranty Services Period” means the number of years defined in the SCC (if any), following the expiration of the Warranty Period during which the Supplier may be obligated to provide Software licens...
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 entitled “Eligible 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 ...