Acceptance Testing Procedure. 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. (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.
(b) Grantor shall make each Wavelength Ring available to Purchaser for ten (10) Working Days after 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.
(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 Day 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 Centre process set forth in Clause 8.
1.3 LEAD TIME TO CONNECT GUARANTEE THE COMMITTED DELIVERY DATE is the date corresponding to the dates mentioned in. If the Committed Delivery Date is not m...
Acceptance Testing Procedure. 9.3.1 Upon delivery of a loop to/for CLEC, AT&T ILLINOIS’s 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 xxxx XXXX 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 ILLINOIS will still close the order. AT&T ILLINOIS will not complete an order that fails Acc...
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. 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.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.
7.2.1.1 Except for IDSL loops that are provisioned through repeaters or digital loop carriers, the AT&T 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 that are provisioned through repeaters or digital loop carriers, the AT&T 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 Attachment for xDSL loops, CLEC will provide AT&T with a confirmation number and AT&T will complete the order. CLEC 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 Attachment for xDSL loops, the WCMC or field technician will take 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 AT&T technician will release the CLEC technician, and perform the work necessary to correct the situation. Once the loop is correctly provisioned, AT&T will contact CLEC to repeat the Acceptance Test. When the aforementioned test parameters are met, CLEC will provide AT&T with a confirmation number and AT&T will complete the order. If CLEC does not send its confirmation number to AT&T, AT&T may close the order. AT&T will not complete an order that fails Acceptance Testing.
7.2.4 Until such time as CLEC and AT&T agree, or industry standards establish, that their test equipment can accurately send signals through repeaters or digital loop carriers, CLEC will accept IDSL loops without testing the complete circuit. Consequently, AT&T agrees that should CLEC open a trouble ticket on such a loop within ten (10) business days (that is the fault of AT&T), AT&T will adjust XXXX’x xxxx and refund the recurring charge of such a loop until AT&T has resolved the problem and closed the trouble ticket.
7.2.5 AT&T 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 places the ...
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:
a. the Hosted Service conforms to the Deliverables set forth in Schedule A, including the full operability, integration, interoperability and compatibility of the Hosted Service with the components and functions of the Operating Environment in accordance with the Documentation.
(ii) All Acceptance Tests shall:
(i) take place in the Operating Environment at a facility to be designated by HCS on prior notice to JUNYO;
(ii) begin within five (5) Business Days following Delivery of the Hosted Service; and
(iii) be conducted diligently for at most up to thirty (30) days ("Testing Period") by HCS.
(iii) HCS may suspend Acceptance Tests and the corresponding Testing Period by written notice to JUNYO if HCS discovers a Severity 1 or Severity 2 Nonconformity in the Hosted Service or part or feature thereof. In such event, JUNYO shall immediately, and in any case within five (5) Business Days, correct such Nonconformity, whereupon the Acceptance Tests and Testing Period shall resume for the balance of the Testing Period.
(iv) For any Acceptance Tests conducted by HCS, if requested by either party, JUNYO shall make suitable JUNYO Personnel available to observe and participate in such Acceptance Tests, and HCS shall make available HCS personnel, physical access, and all associated data and log files as reasonably requested by JUNYO to assist JUNYO in diagnosis and evaluation of results of Acceptance Tests
(v) All JUNYO performance of, participation in and observation of Acceptance Tests will be at JUNYO’s sole cost and expense.
Acceptance Testing Procedure. 12.2.1. Following delivery of Software, Licence, Enhancements, Upgrades, New Releases, Bug Fixes, Work Arounds or patches to SARS, SARS shall in its discretion, conduct Acceptance Testing thereof (collectively referred to as “Tested Deliverable(s)”).
12.2.2. During Acceptance Testing, the Service Provider shall (if required by SARS), assist SARS, to the extent necessary and reasonable, in conducting the Acceptance Testing and respond to any queries relating to the Services and/or Tested Deliverables, within a reasonable time. Without limiting the aforegoing, the Service Provider shall be available to liaise with SARS regarding any queries arising with regard to the Tested Deliverables and its related documentation and shall assist SARS with its evaluation of such Tested Deliverables and its related Documentation.
12.2.3. Should SARS not accept the Tested Deliverables and/or its related Documentation, SARS shall provide the Service Provider with written notice of its non-acceptance of such Tested Deliverables and/or its related Functional Specification. The Service Provider shall correct any Deficiencies in such Tested Deliverables and Functional Specification within timeframe agreed upon by the Parties in writing to ensure that such Tested Deliverable is free from Deficiencies and conform to SARS’s business and security requirements, where after such Tested Deliverable will be resubmitted to Acceptance Testing in accordance with this Clause.
12.2.4. The acceptance of the functionality of the Tested Deliverables shall be governed by a test and acceptance procedure and criteria, which shall demonstrate the correct and satisfactory operation and functioning of the relevant functionality of the Tested Deliverables in accordance with the Documentation.
12.2.5. SARS shall have the right to review and accept or reject all Tested Deliverables and any components of such Tested Deliverables to be provided by the Service Provider to SARS under this Agreement, pursuant to the methodology set forth in this Clause.
12.2.6. The Service Provider will be available to liaise with SARS regarding any queries arising with regard to a Deliverable and will assist SARS with its evaluation of Tested Deliverables.
12.2.7. Should SARS not accept the Tested Deliverable, SARS will provide the Service Provider with written notice of its non-acceptance, as well as detailed reasons for it not being acceptable. The Service Provider will correct any Deficiencies within 5 (five) business da...
Acceptance Testing Procedure. 7.1 Where the Services are specified to be subject to Acceptance Tests in the Statement of Work or project plan, the Customer shall undertake the Acceptance Tests to determine whether the Services have met their Acceptance Criteria as agreed to in the user stories and designs.
7.2 For each release to UAT, the Customer shall carry out the Acceptance Tests using the Acceptance Criteria within 3 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 3 Business Days 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 4 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.
7.6 6B will deliver a maximum of 2 rounds of Acceptance Testing for each Acceptance Testing Release, any additional rounds of Acceptance testing or any work related to feedback received outside of the Acceptance Testing feedback deadlines as outlined above, may be subject to additional charges and may impact project timescales. Any delay to timescales caused by the Customer failing to meet the Acceptance Testing process will be accepted by the Customer without penalty to 6B. Enhanced UAT, with additional rounds can be priced on request.
