Acceptance Testing Procedure Clause Samples

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. 7.2.1.1 Except for IDSL loops or subloops that are provisioned through repeaters or digital loop carriers, the CenturyTel field technician will provide a solid short across the tip and ring of the circuit and then open the loop circuit. 7.2.1.2 For IDSL loops or subloops that are provisioned through repeaters or digital loop carriers, the CenturyTel field technician will not perform a short or open circuit. 7.2.2 If the loop passes the “Proof of Continuity” parameters, as defined by this Article for xDSL loops, Socket will provide CenturyTel with a confirmation number and CenturyTel will complete the order. Socket will be billed and shall pay for the Acceptance Test as specified below under Acceptance Testing Billing. 7.2.3 If the Acceptance Test fails loop continuity test parameters, as defined by this Article for xDSL loops, the CenturyTel technician will take reasonable steps to immediately resolve the problem with Socket on the line including, but not limited to, calling the central office to perform work or troubleshooting for physical faults. If the problem cannot be resolved in an expedient manner, the CenturyTel technician will release the Socket technician, and perform the work necessary to correct the situation. Once the loop is correctly provisioned, CenturyTel will contact Socket to repeat the Acceptance Test. When the aforementioned test parameters are met, Socket will provide CenturyTel with a confirmation number and CenturyTel will complete the order. If CenturyTel determines loop continuity parameters are met, CenturyTel may close the order. CenturyTel will not complete an order that fails Acceptance Testing. 7.2.4 Until such time as Socket and CenturyTel agree, or industry standards establish, that their test equipment can accurately send signals through repeaters or digital loop carriers, Socket will accept IDSL loops or subloops provided through repeaters or digital loop carrier without testing the complete circuit. Consequently, CenturyTel agrees that should Socket open a trouble ticket on such a loop or subloop within ten (10) business days (that is the fault of CenturyTel), CenturyTel will adjust Socket’s bill and refund the recurring charge of suc...

Acceptance Testing Procedure. 9.3.1 Upon delivery of a loop to/for CLEC, AT&T ILLINOIS’ field technician will call the LOC and the LOC tester will call a toll free number provided by CLEC so CLEC can initiate performance of a series of Acceptance Tests. 9.3.1.1 For IDSL or 2-wire digital loops that are not provisioned through repeaters or digital loop carriers, the AT&T ILLINOIS field technician will provide a solid short across the tip and ring of the circuit and then open the loop circuit. 9.3.1.2 For IDSL or 2-wire digital loops that are provisioned through repeaters or Digital Loop Carrier, the AT&T ILLINOIS field technician will not perform a short or open circuit due to technical limitations. 9.3.2 If the loop passes the “Proof of Continuity” parameters, as defined by this Appendix for DSL loops, CLEC will provide AT&T ILLINOIS with a confirmation number and AT&T ILLINOIS will complete the order. CLEC will be billed and shall pay for the Acceptance Test at the applicable rates as referenced in section 9.4.2 below. 9.3.2.1 AT&T ILLINOIS will be relieved of the obligation to perform Acceptance Testing on a particular loop and will assume acceptance of the loop by CLEC when CLEC cannot provide a “live” representative (through no answer or placement on hold) for over ten (10) minutes. AT&T ILLINOIS may then close the order utilizing existing procedures, document the time and reason, and may ▇▇▇▇ ▇▇▇▇ and CLEC shall pay the minimum charges as if the Acceptance Test had been completed and the loop accepted, referenced in section 9.4.2 below. 9.3.3 If the Acceptance Test fails loop Continuity test parameters, as defined by this Appendix for DSL loops, the LOC technician will take any or all reasonable steps to immediately resolve the problem with CLEC on the line including, but not limited to, calling the central office to perform work or troubleshooting for physical faults. If the problem cannot be resolved in an expedient manner, the technician will release the CLEC representative, and perform the work necessary to correct the situation. Once the loop is correctly provisioned, AT&T ILLINOIS will re- contact the CLEC representative to repeat the Acceptance Test. When the aforementioned test parameters are met, CLEC will provide AT&T ILLINOIS with a confirmation number and AT&T ILLINOIS will complete the order. If CLEC xDSL service does not function as desired, yet test parameters are met, AT&T 9.3.4 Until such time as CLEC and AT&T ILLINOIS agree, or industry standards establish, that ...

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. (a) Grantor shall make each Wavelength available to Purchaser for five (5) Working Days from 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. (b) Grantor shall make each Wavelength Ring available to Purchaser for ten (10) Working Days from the Committed Delivery Date of the last Wavelength in such Wavelength Ring or the date set forth in section 1.2.3 below for Purchaser to perform its acceptance testing to ensure that the Wavelength Ring meets the RFS Standard. 1.2.2 The acceptance testing will be performed in a two-step procedure: (i) Acceptance testing POP to POP: each Wavelength Ring will be tested according to RFS Standard between Grantor's Sites, with the exception of the Wavelengths terminating in Paris, where, when provided by Grantor, the Paris access will be included in the testing. (ii) Continuity testing: Grantor shall co-operate with Purchaser to End to End testing between Purchaser's customers' sites. 1.2.3 When Purchaser successfully completes its acceptance testing POP to POP and the Wavelengths and Wavelength Ring meet the RFS Standard, it shall notify Grantor and this shall constitute the RFS Date. The Purchase Price for each Wavelength Ring shall be paid on the RFS Date of such Wavelength Ring. Billing of OA&M Charges shall start from the RFS Date. 1.2.4 If Purchaser notifies Grantor that the Wavelengths or Wavelength Ring do not meet the RFS Standard, Grantor shall be given ten (10) Working Days to correct the defect. On the expiry of the ten (10) Working Days period Purchaser shall be given ten (10) Working Days to perform its acceptance tests and the procedure set forth in this section 1.2 shall continue to apply until the Wavelengths and Wavelength Ring meet the RFS Standard. 1.2.5 If Purchaser has not communicated either a positive or negative response to Grantor within ten (10) Working Days of the Committed Delivery Date of the relevant Wavelength or Wavelength Ring, Grantor shall give Notice to Purchaser that the acceptance testing period has expired without communication from Purchaser. If an additional ten (10) Working Days pass without communication from Purchaser, Grantor shall be entitled to invoice Purchaser for such Wavelength or Wavelength Ring (including OA&M fees). Any outage or defect on the Capacity shall be handled through the Customer Support Center process set forth in Clause 8.

Acceptance Testing Procedure. ‌ The customer shall undertake the acceptance tests to determine whether the sprint results have met their respective acceptance criteria. The customer shall carry out the acceptance tests using the acceptance criteria within [one] business day of completion of the relevant sprint, at a time to be agreed in writing with the supplier. The customer shall permit supplier to attend and observe the acceptance tests. The customer shall not unreasonably withhold or delay its agreement that any particular sprint result meets its acceptance criteria. The customer shall be deemed to have agreed that the sprint requirements have met their respective acceptance criteria on the earliest of: The customer's written agreement to that effect; The expiry of [one] business day after the completion of the relevant acceptance tests, unless the customer has given written notice to the supplier that one or more sprint results do not meet their respective acceptance criteria, specifying the relevant sprint result or sprint results and details of the nature of the failure, in each case; The expiry of [two] business days after the supplier informs the customer that the sprint requirements are ready for the relevant acceptance tests, if those acceptance tests have not been completed; and The live use of the software (or the relevant part of it) by the customer or any of its employees, agents or contractors. Within five business days of the end of every second sprint the product owner, scrum master and the development team shall hold a release planning session. At each release planning session, the product owner, scrum master and the development team shall: Discuss whether development of the software remains aligned with the product vision and with the parties' expectations. Evaluate cost and timeline impacts due to additions of requirements to, or deletions of requirements from, the product backlog. Material changes to the product backlog shall be subject to the agile change control process.

Acceptance Testing Procedure. 7.1 Where the Services are specified to be subject to Acceptance Tests in the Statement of Work, the Customer shall undertake the Acceptance Tests to determine whether the Services have met their Acceptance Criteria. 7.2 The Customer shall carry out the Acceptance Tests using the Acceptance Criteria within 1 Business Day of completion of the Services, at a time to be agreed in writing with 6B. The Customer shall permit 6B to attend and observe the Acceptance Tests. 7.3 The Customer shall not unreasonably withhold or delay its agreement that the Services meet its Acceptance Criteria. 7.4 The Customer shall be deemed to have accepted that the Services have met the Acceptance Criteria on the earliest of: 7.4.1 the Customer’s written agreement to that effect; 7.4.2 the expiry of 1 Business Day after completion of the Acceptance Tests, unless the Customer has given written notice to 6B that the Services do not meet the Acceptance Criteria, specifying the nature of the failure; 7.4.3 the expiry of 2 Business Days after 6B informs the Customer that the Services are ready for the Acceptance Tests, if those Acceptance Tests have not been completed; and 7.4.4 the live use of the Deliverables (or the relevant part of them) by the Customer or any of its employees, agents or contractors. 7.5 Any part of the Services which are undeliverable for reasons that are outside of 6B’s control shall be excluded from the Acceptance Tests carried out in accordance with paragraph 7.2.

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

Acceptance Testing Procedure. The following Acceptance Testing procedure applies to each Deliverable: