Acceptance Testing Procedure. 9.2.2.15.2.1 Upon delivery of a loop to/for CLEC, SBC- AMERITECH’s field technician will call the LOC and the LOC tester will call a toll free number provided by CLEC to initiate performance of a series of Acceptance Tests.
Acceptance Testing Procedure. Instruments manufactured by KMC shall be subjected to the ATP prior to shipment, and shall be deemed accepted by LipoScience upon meeting the requirements of the ATP, as confirmed by KMC’s written certification provided to LipoScience. Title to the Instruments, and risk of loss thereof, shall remain with KMC for so long as KMC is in possession of the Instruments, and shall transfer to LipoScience upon shipment to (i) LipoScience, (ii) LipoScience’s designated customer, or (iii) a storage facility designated by LipoScience.
Acceptance Testing Procedure. 7.2.1 Upon delivery of a loop to CLEC, AT&T’s field technician will call the Wholesale Customer Maintenance Center (WCMC) and the WCMC technician will call a toll free number provided by CLEC to initiate performance of a series of Acceptance Tests.
Acceptance Testing Procedure. 1.2.1 (a) Grantor shall make each Wavelength available to Purchaser for five (5) Working Days after the Committed Delivery Date or the date set forth in section 1.2.3 below for Purchaser to perform its acceptance testing to ensure that the Wavelength meets the RFS Standard.
Acceptance Testing Procedure. 9.1 If this Agreement contemplates that acceptance of the Goods or Services is subject to any acceptance testing, this clause applies subject to any modification agreed by the parties.
Acceptance Testing Procedure. As soon as reasonably practicable, but in any event within forty-five (45) days after IGT’s receipt of the Developed Software, IGT will test the Developed Software using the Acceptance Criteria and provide PGIC with a written acceptance of the Developed Software or a written statement of errors that describes all errors in sufficient detail to enable PGIC to reproduce such errors (“Statement of Errors”). For purposes of this SCIA, “Error” means […***…] […***…] […***…] […***…] to correct such Errors and re-deliver the Developed Software to IGT for re-testing of the Developed Software with respect to such Errors. IGT’s right to re-test the Developed Software and PGIC’s obligation to correct and re-deliver the Developed Software to IGT will repeat in accordance with the foregoing procedure, subject to the terms and conditions of the Joint Development Plan.
Acceptance Testing Procedure. 7.2.1 Upon delivery of a loop or subloop to Socket, CenturyTel’s field technician will call the CenturyTel Local Operations Center (LOC) or equivalent organization and the LOC technician will call a toll free number provided by Socket to initiate performance of a series of Acceptance Tests.
Acceptance Testing Procedure. (i) Upon Delivery of the Hosted Service, HCS shall conduct all Acceptance Tests agreed upon by the Parties to determine whether, and the extent to which:
Acceptance Testing Procedure. 95.2.1. Upon delivery of a loop or subloop to **CLEC, CenturyLink’s field technician will call the CenturyLink Local Operations Center (LOC) or equivalent organization, and the LOC technician will call a toll free number provided by **CLEC to initiate performance of a series of Acceptance Tests.
Acceptance Testing Procedure. Once Functional Testing and Integration Testing have been completed, and the City staff has received Functional Process Training, the City staff will have the necessary tools to perform Solution Acceptance Testing. Prior to commencing Solution Acceptance testing activity, the Test Scripts and Test Acceptance Criteria will be documented in the Test Matrix by Subcontractor collaboratively with City. City will have their own access to The Xxxxxx Software, loaded with customer data, to train and test on. The Subcontractor will provide the documents and training of the system to City staff. Training will be conducted onsite and using WebEx sessions, phone calls and documentation as needed. City will have a defined period of time to perform Solution Acceptance Testing on the Software (including testing in a live production environment) (the “Acceptance Testing Period”). The length of the Acceptance Testing Period will be defined in the Detailed Project Plan. This Solution Acceptance Testing Period will begin upon formal written notification from Subcontractor to City that the Xxxxxx Software has been configured and is ready for testing. During such Acceptance Testing Period, both Parties shall work diligently and dedicate the appropriate resources to conclude the evaluation in a timely and efficient fashion. If the Software substantially meets the Functional and Integration Requirements Document, and substantially satisfies the testing criteria set forth in the Solution Acceptance Test Matrix (together the “Solution Acceptance Criteria”), City will provide Subcontractor with written acceptance notice thereof, and the date of such notice to be the “Actual Solution Acceptance Date”. In the event City determines that the results of a test do not meet the Solution Acceptance Criteria, following the initial Solution Acceptance Testing cycle, City will provide Subcontractor with written notice thereof, specifying in reasonable detail how the Software failed to meet the Solution Acceptance Criteria. If City delivers to Subcontractor such notice of retesting, Subcontractor shall make all necessary corrections, repairs, fixes, modifications, or additions to or replacements of all or any part of the rejected Software so that it conforms to and performs in accordance with the Solution Acceptance Criteria. Subcontractor will have a defined period of time “Correction Period” to correct any deficiency, after which the Solution Acceptance Testing will be resumed. The Correctio...
