{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "delivery-of-a", "type": "clause", "offset": [5, 18]}, {"key": "field-technician", "type": "definition", "offset": [54, 70]}, {"key": "toll-free-number", "type": "definition", "offset": [120, 136]}, {"key": "acceptance-tests", "type": "definition", "offset": [193, 209]}], "size": 7, "snippet": "Upon delivery of a loop to/for CLEC, SBC- AMERITECH\u2019s 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.", "samples": [{"hash": "l6gQJiD8hPC", "uri": "/contracts/l6gQJiD8hPC#acceptance-testing-procedure", "label": "Interconnection Agreement", "score": 26.1704312115, "published": true}, {"hash": "jcNM7mGGyDp", "uri": "/contracts/jcNM7mGGyDp#acceptance-testing-procedure", "label": "Interconnection Agreement", "score": 26.1704312115, "published": true}, {"hash": "80NtVDZVKU8", "uri": "/contracts/80NtVDZVKU8#acceptance-testing-procedure", "label": "Interconnection Agreement", "score": 26.1704312115, "published": true}], "hash": "17ebb54aaaae33c00bc3ea1c3992b24b", "id": 1}, {"snippet_links": [{"key": "delivery-of-a", "type": "clause", "offset": [11, 24]}, {"key": "field-technician", "type": "definition", "offset": [65, 81]}, {"key": "operations-center", "type": "clause", "offset": [113, 130]}, {"key": "or-equivalent", "type": "definition", "offset": [137, 150]}, {"key": "organization-and", "type": "clause", "offset": [151, 167]}, {"key": "toll-free-number", "type": "definition", "offset": [199, 215]}, {"key": "acceptance-tests", "type": "definition", "offset": [274, 290]}, {"key": "provide-a", "type": "definition", "offset": [436, 445]}, {"key": "proof-of-continuity", "type": "definition", "offset": [733, 752]}, {"key": "this-article", "type": "definition", "offset": [780, 792]}, {"key": "confirmation-number", "type": "definition", "offset": [847, 866]}, {"key": "complete-the", "type": "clause", "offset": [887, 899]}, {"key": "pay-for", "type": "clause", "offset": [939, 946]}, {"key": "the-acceptance", "type": "clause", "offset": [947, 961]}, {"key": "as-specified", "type": "clause", "offset": [967, 979]}, {"key": "acceptance-testing-billing", "type": "clause", "offset": [992, 1018]}, {"key": "test-parameters", "type": "clause", "offset": [1071, 1086]}, {"key": "reasonable-steps", "type": "definition", "offset": [1167, 1183]}, {"key": "the-problem", "type": "clause", "offset": [1207, 1218]}, {"key": "on-the-line", "type": "definition", "offset": [1231, 1242]}, {"key": "not-limited", "type": "clause", "offset": [1258, 1269]}, {"key": "central-office", "type": "clause", "offset": [1286, 1300]}, {"key": "the-work", "type": "definition", "offset": [1489, 1497]}, {"key": "the-situation", "type": "clause", "offset": [1519, 1532]}, {"key": "an-order", "type": "clause", "offset": [1905, 1913]}, {"key": "industry-standards", "type": "definition", "offset": [2002, 2020]}, {"key": "test-equipment", "type": "clause", "offset": [2043, 2057]}, {"key": "digital-loop-carrier", "type": "clause", "offset": [2202, 2222]}, {"key": "trouble-ticket", "type": "definition", "offset": [2319, 2333]}, {"key": "business-days", "type": "clause", "offset": [2376, 2389]}, {"key": "recurring-charge", "type": "definition", "offset": [2477, 2493]}, {"key": "obligation-to-perform", "type": "clause", "offset": [2623, 2644]}, {"key": "acceptance-of-the", "type": "clause", "offset": [2712, 2729]}, {"key": "service-center", "type": "clause", "offset": [2796, 2810]}, {"key": "on-hold", "type": "definition", "offset": [2831, 2838]}, {"key": "existing-procedures", "type": "clause", "offset": [2921, 2940]}, {"key": "except-as-otherwise-provided", "type": "clause", "offset": [2942, 2970]}, {"key": "cost-of", "type": "definition", "offset": [3339, 3346]}, {"key": "terms-and-conditions-of", "type": "clause", "offset": [3486, 3509]}, {"key": "the-repair", "type": "definition", "offset": [3705, 3715]}, {"key": "hours-of", "type": "clause", "offset": [3768, 3776]}, {"key": "order-completion", "type": "clause", "offset": [3795, 3811]}, {"key": "will-work", "type": "clause", "offset": [3980, 3989]}, {"key": "acceptance-testing-procedures", "type": "definition", "offset": [4012, 4041]}, {"key": "agree-to", "type": "clause", "offset": [4100, 4108]}, {"key": "additional-testing", "type": "clause", "offset": [4109, 4127]}, {"key": "not-covered-by-this-agreement", "type": "clause", "offset": [4157, 4186]}, {"key": "the-parties-will", "type": "clause", "offset": [4188, 4204]}, {"key": "conditions-to", "type": "clause", "offset": [4225, 4238]}, {"key": "additional-charges", "type": "definition", "offset": [4303, 4321]}, {"key": "time-and-expense", "type": "clause", "offset": [4397, 4413]}], "size": 1, "snippet": "7.2.1 Upon delivery of a loop or subloop to Socket, CenturyTel\u2019s 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.\n7.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.\n7.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.\n7.2.2 If the loop passes the \u201cProof of Continuity\u201d 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.\n7.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.\n7.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\u2019s bill and refund the recurring charge of such a loop until CenturyTel has resolved the problem and closed the trouble ticket.\n7.2.5 CenturyTel will be relieved of the obligation to perform Acceptance Testing on a particular loop or subloop and will assume acceptance of the loop or subloop by Socket when Socket places the CenturyTel Local Service Center or field technician on hold for over ten (10) minutes. In that case, CenturyTel may close the order utilizing existing procedures. Except as otherwise provided in this Article, if no trouble ticket is opened on that loop or subloop within 24 hours, CenturyTel may bill and Socket shall pay as if the Acceptance Test had been completed and the loop or subloop accepted. If, however, a trouble ticket is opened on the loop or subloop within 24 hours and the trouble resulted from CenturyTel error, Socket will be credited for the cost of the acceptance test. Additionally, Socket may subsequently request and CenturyTel will perform testing of such a loop or subloop under the terms and conditions of a repair request. If such loop or subloop is found by CenturyTel to not meet loop continuity test parameters as defined herein, CenturyTel will not charge for any acceptance testing performed on the repair call.\n7.2.6 If a trouble ticket is opened within 24 hours of a loop or subloop order completion, and the trouble is determined to be CenturyTel\u2019s error, CenturyTel will credit Socket for any charge(s) previously assessed to Socket for the test.\n7.2.7 Both Parties will work together to implement Acceptance Testing procedures that are efficient and effective. If the Parties mutually agree to additional testing, procedures and/or standards not covered by this Agreement, the Parties will negotiate terms and conditions to implement such additional testing, procedures and/or standards. Additional charges may apply if any agreed-to changes require CenturyTel to expend additional time and expense.", "samples": [{"hash": "14z3E8omugu", "uri": "/contracts/14z3E8omugu#acceptance-testing-procedure", "label": "XDSL Agreement", "score": 28.7113193411, "published": true}], "hash": "8363f76249f04c37761f666549fa3dbd", "id": 8}, {"snippet_links": [{"key": "delivery-of-a", "type": "clause", "offset": [11, 24]}, {"key": "att-illinois", "type": "clause", "offset": [43, 56]}, {"key": "field-technician", "type": "definition", "offset": [58, 74]}, {"key": "toll-free-number", "type": "definition", "offset": [124, 140]}, {"key": "acceptance-tests", "type": "definition", "offset": [206, 222]}, {"key": "the-att", "type": "clause", "offset": [334, 342]}, {"key": "provide-a", "type": "definition", "offset": [374, 383]}, {"key": "digital-loop-carrier", "type": "clause", "offset": [550, 570]}, {"key": "technical-limitations", "type": "clause", "offset": [655, 676]}, {"key": "proof-of-continuity", "type": "definition", "offset": [708, 727]}, {"key": "clec-will-provide", "type": "clause", "offset": [784, 801]}, {"key": "confirmation-number", "type": "definition", "offset": [823, 842]}, {"key": "complete-the", "type": "clause", "offset": [866, 878]}, {"key": "pay-for", "type": "clause", "offset": [916, 923]}, {"key": "the-acceptance", "type": "clause", "offset": [924, 938]}, {"key": "applicable-rates", "type": "clause", "offset": [951, 967]}, {"key": "section-942", "type": "clause", "offset": [985, 998]}, {"key": "obligation-to-perform", "type": "clause", "offset": [1052, 1073]}, {"key": "acceptance-testing", "type": "definition", "offset": [1074, 1092]}, {"key": "acceptance-of-the", "type": "clause", "offset": [1130, 1147]}, {"key": "on-hold", "type": "definition", "offset": [1242, 1249]}, {"key": "existing-procedures", "type": "clause", "offset": [1327, 1346]}, {"key": "minimum-charges", "type": "definition", "offset": [1419, 1434]}, {"key": "test-parameters", "type": "clause", "offset": [1589, 1604]}, {"key": "reasonable-steps", "type": "definition", "offset": [1689, 1705]}, {"key": "the-problem", "type": "clause", "offset": [1729, 1740]}, {"key": "on-the-line", "type": "definition", "offset": [1751, 1762]}, {"key": "not-limited", "type": "clause", "offset": [1778, 1789]}, {"key": "central-office", "type": "clause", "offset": [1806, 1820]}, {"key": "the-work", "type": "definition", "offset": [2000, 2008]}, {"key": "the-situation", "type": "clause", "offset": [2030, 2043]}, {"key": "clec-and-att", "type": "clause", "offset": [2432, 2445]}, {"key": "industry-standards", "type": "definition", "offset": [2465, 2483]}, {"key": "test-equipment", "type": "clause", "offset": [2506, 2520]}, {"key": "agrees-to", "type": "clause", "offset": [2615, 2624]}, {"key": "trouble-ticket", "type": "definition", "offset": [2796, 2810]}, {"key": "network-fault", "type": "definition", "offset": [2832, 2845]}, {"key": "testing-procedures", "type": "clause", "offset": [2867, 2885]}, {"key": "business-days", "type": "clause", "offset": [2917, 2930]}, {"key": "recurring-charge", "type": "definition", "offset": [3081, 3097]}], "size": 5, "snippet": "9.3.1 Upon delivery of a loop to/for CLEC, AT&T ILLINOIS\u2019 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.\n9.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.\n9.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.\n9.3.2 If the loop passes the \u201cProof of Continuity\u201d 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.\n9.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 \u201clive\u201d 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 \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587 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.\n9.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\n9.3.4 Until such time as CLEC and AT&T ILLINOIS agree, or industry standards establish, that their test equipment can accurately and consistently send signals through repeaters or Digital Loop Carriers, CLEC agrees to accept IDSL or 2- wire digital loops, designed with such reach extenders, without testing the complete circuit. Consequently, AT&T ILLINOIS agrees that should CLEC open a trouble ticket and an AT&T ILLINOIS network fault be found by standard testing procedures on such a loop within ten (10) business days (in which it is determined by standard testing to be an AT&T ILLINOIS fault), AT&T ILLINOIS, upon CLEC request, will adjust \u2587\u2587\u2587\u2587\u2019\u2587 \u2587\u2587\u2587\u2587 to refund the recurring charge of such a loop until the fault has been resolved and the trouble ticket is closed.", "samples": [{"hash": "bpyHlCZaoOG", "uri": "/contracts/bpyHlCZaoOG#acceptance-testing-procedure", "label": "Interconnection Agreement", "score": 21.4449553553, "published": true}], "hash": "ad1fc2f4158905490f702b9ab5b491fc", "id": 2}, {"snippet_links": [{"key": "by-kmc", "type": "clause", "offset": [25, 31]}, {"key": "prior-to", "type": "definition", "offset": [62, 70]}, {"key": "accepted-by", "type": "definition", "offset": [101, 112]}, {"key": "requirements-of-the", "type": "clause", "offset": [142, 161]}, {"key": "written-certification", "type": "clause", "offset": [189, 210]}, {"key": "the-instruments", "type": "clause", "offset": [245, 260]}, {"key": "risk-of-loss", "type": "definition", "offset": [266, 278]}, {"key": "possession-of-the", "type": "clause", "offset": [335, 352]}, {"key": "transfer-to", "type": "definition", "offset": [376, 387]}, {"key": "designated-customer", "type": "definition", "offset": [453, 472]}, {"key": "storage-facility", "type": "definition", "offset": [485, 501]}], "size": 3, "snippet": "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\u2019s 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\u2019s designated customer, or (iii) a storage facility designated by LipoScience.", "samples": [{"hash": "dOyPRZ38Baw", "uri": "/contracts/dOyPRZ38Baw#acceptance-testing-procedure", "label": "Production Agreement (Liposcience Inc)", "score": 23.3189596167, "published": true}, {"hash": "eMa5I9vKynX", "uri": "/contracts/eMa5I9vKynX#acceptance-testing-procedure", "label": "Production Agreement (Liposcience Inc)", "score": 22.7440109514, "published": true}, {"hash": "eq6eMmLz8Mh", "uri": "/contracts/eq6eMmLz8Mh#acceptance-testing-procedure", "label": "Production Agreement (Liposcience Inc)", "score": 22.5797399042, "published": true}], "hash": "d76ac054ab8c3d8d5da4829ec5604929", "id": 3}, {"snippet_links": [{"key": "available-to", "type": "definition", "offset": [39, 51]}, {"key": "working-days", "type": "clause", "offset": [75, 87]}, {"key": "committed-delivery-date", "type": "definition", "offset": [97, 120]}, {"key": "for-purchaser", "type": "clause", "offset": [166, 179]}, {"key": "to-ensure", "type": "clause", "offset": [214, 223]}, {"key": "date-of", "type": "clause", "offset": [389, 396]}, {"key": "the-acceptance", "type": "clause", "offset": [599, 613]}, {"key": "step-procedure", "type": "clause", "offset": [649, 663]}, {"key": "pop-to-pop", "type": "definition", "offset": [688, 698]}, {"key": "according-to", "type": "definition", "offset": [736, 748]}, {"key": "with-the-exception-of", "type": "clause", "offset": [787, 808]}, {"key": "by-grantor", "type": "clause", "offset": [868, 878]}, {"key": "the-testing", "type": "definition", "offset": [917, 928]}, {"key": "end-to-end-testing", "type": "definition", "offset": [998, 1016]}, {"key": "rfs-date", "type": "definition", "offset": [1250, 1258]}, {"key": "purchase-price-for", "type": "clause", "offset": [1264, 1282]}, {"key": "expiry-of", "type": "clause", "offset": [1595, 1604]}, {"key": "acceptance-tests", "type": "definition", "offset": [1700, 1716]}, {"key": "the-procedure", "type": "definition", "offset": [1721, 1734]}, {"key": "to-apply", "type": "clause", "offset": [1780, 1788]}, {"key": "negative-response", "type": "clause", "offset": [1915, 1932]}, {"key": "the-relevant", "type": "clause", "offset": [2007, 2019]}, {"key": "notice-to-purchaser", "type": "definition", "offset": [2070, 2089]}, {"key": "acceptance-testing-period", "type": "definition", "offset": [2099, 2124]}, {"key": "an-additional", "type": "clause", "offset": [2178, 2191]}, {"key": "customer-support-center", "type": "definition", "offset": [2432, 2455]}, {"key": "clause-8", "type": "definition", "offset": [2477, 2485]}], "size": 3, "snippet": "(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.\n(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.\n1.2.2 The acceptance testing will be performed in a two-step procedure:\n(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.\n(ii) Continuity testing: Grantor shall co-operate with Purchaser to End to End testing between Purchaser's customers' sites.\n1.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.\n1.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.\n1.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.", "samples": [{"hash": "cdcyhCiyAgJ", "uri": "/contracts/cdcyhCiyAgJ#acceptance-testing-procedure", "label": "Capacity Purchase Agreement (Equant Nv)", "score": 18.0, "published": true}], "hash": "1f74836db8828f3565458128e3aaeeb6", "id": 4}, {"snippet_links": [{"key": "acceptance-tests", "type": "definition", "offset": [35, 51]}, {"key": "determine-whether", "type": "clause", "offset": [55, 72]}, {"key": "acceptance-criteria", "type": "clause", "offset": [118, 137]}, {"key": "day-of", "type": "clause", "offset": [241, 247]}, {"key": "the-relevant", "type": "clause", "offset": [262, 274]}, {"key": "in-writing", "type": "clause", "offset": [306, 316]}, {"key": "to-attend", "type": "clause", "offset": [371, 380]}, {"key": "the-customer-shall-not", "type": "clause", "offset": [415, 437]}, {"key": "agreed-that", "type": "clause", "offset": [585, 596]}, {"key": "agreement-to", "type": "definition", "offset": [710, 722]}, {"key": "expiry-of", "type": "clause", "offset": [740, 749]}, {"key": "to-the-supplier", "type": "clause", "offset": [869, 884]}, {"key": "nature-of-the", "type": "clause", "offset": [1042, 1055]}, {"key": "each-case", "type": "definition", "offset": [1068, 1077]}, {"key": "days-after", "type": "definition", "offset": [1108, 1118]}, {"key": "use-of-the-software", "type": "clause", "offset": [1291, 1310]}, {"key": "relevant-part", "type": "definition", "offset": [1319, 1332]}, {"key": "by-the-customer", "type": "clause", "offset": [1340, 1355]}, {"key": "business-days-of", "type": "clause", "offset": [1416, 1432]}, {"key": "product-owner", "type": "clause", "offset": [1468, 1481]}, {"key": "development-team", "type": "clause", "offset": [1504, 1520]}, {"key": "development-of-the-software", "type": "clause", "offset": [1674, 1701]}, {"key": "product-vision", "type": "definition", "offset": [1727, 1741]}, {"key": "the-parties", "type": "definition", "offset": [1751, 1762]}, {"key": "product-backlog", "type": "definition", "offset": [1889, 1904]}, {"key": "changes-to-the", "type": "definition", "offset": [1915, 1929]}, {"key": "subject-to-the", "type": "definition", "offset": [1955, 1969]}, {"key": "change-control-process", "type": "definition", "offset": [1976, 1998]}], "size": 2, "snippet": "\u200c 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.", "samples": [{"hash": "8s2ZZoh5GN8", "uri": "/contracts/8s2ZZoh5GN8#acceptance-testing-procedure", "label": "Support Agreement", "score": 33.0338529983, "published": true}, {"hash": "eglHBJod11Z", "uri": "/contracts/eglHBJod11Z#acceptance-testing-procedure", "label": "Support Agreement", "score": 33.030060065, "published": true}], "hash": "03a5aeb7a6fc0c60461d5e904e9b3888", "id": 5}, {"snippet_links": [{"key": "subject-to", "type": "definition", "offset": [43, 53]}, {"key": "acceptance-tests", "type": "definition", "offset": [54, 70]}, {"key": "statement-of-work", "type": "clause", "offset": [78, 95]}, {"key": "the-acceptance", "type": "clause", "offset": [126, 140]}, {"key": "determine-whether", "type": "clause", "offset": [150, 167]}, {"key": "acceptance-criteria", "type": "clause", "offset": [196, 215]}, {"key": "day-of", "type": "clause", "offset": [319, 325]}, {"key": "completion-of-the-services", "type": "definition", "offset": [326, 352]}, {"key": "in-writing", "type": "clause", "offset": [377, 387]}, {"key": "to-attend", "type": "clause", "offset": [426, 435]}, {"key": "the-customer-shall-not", "type": "clause", "offset": [474, 496]}, {"key": "agreement-to", "type": "definition", "offset": [740, 752]}, {"key": "expiry-of", "type": "clause", "offset": [776, 785]}, {"key": "after-completion", "type": "clause", "offset": [801, 817]}, {"key": "notice-to", "type": "definition", "offset": [881, 890]}, {"key": "nature-of-the", "type": "clause", "offset": [964, 977]}, {"key": "days-after", "type": "definition", "offset": [1018, 1028]}, {"key": "live-use", "type": "definition", "offset": [1172, 1180]}, {"key": "the-deliverables", "type": "clause", "offset": [1184, 1200]}, {"key": "relevant-part", "type": "definition", "offset": [1209, 1222]}, {"key": "by-the-customer", "type": "clause", "offset": [1232, 1247]}, {"key": "in-accordance-with", "type": "definition", "offset": [1450, 1468]}], "size": 2, "snippet": "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.\n7.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.\n7.3 The Customer shall not unreasonably withhold or delay its agreement that the Services meet its Acceptance Criteria.\n7.4 The Customer shall be deemed to have accepted that the Services have met the Acceptance Criteria on the earliest of:\n7.4.1 the Customer\u2019s written agreement to that effect;\n7.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;\n7.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\n7.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.\n7.5 Any part of the Services which are undeliverable for reasons that are outside of 6B\u2019s control shall be excluded from the Acceptance Tests carried out in accordance with paragraph 7.2.", "samples": [{"hash": "5cchjKqJe8x", "uri": "/contracts/5cchjKqJe8x#acceptance-testing-procedure", "label": "Master Services Agreement", "score": 33.34380612, "published": true}, {"hash": "jcIAqvMgq5l", "uri": "/contracts/jcIAqvMgq5l#acceptance-testing-procedure", "label": "Master Services Agreement", "score": 33.250911268, "published": true}], "hash": "f0ec4ce2ac90d2137b76be0a81fbae4d", "id": 6}, {"snippet_links": [{"key": "days-after", "type": "definition", "offset": [75, 85]}, {"key": "receipt-of", "type": "clause", "offset": [92, 102]}, {"key": "developed-software", "type": "clause", "offset": [107, 125]}, {"key": "acceptance-criteria", "type": "clause", "offset": [174, 193]}, {"key": "acceptance-of-the", "type": "clause", "offset": [226, 243]}, {"key": "statement-of", "type": "clause", "offset": [276, 288]}, {"key": "sufficient-detail", "type": "clause", "offset": [325, 342]}, {"key": "for-purposes-of-this", "type": "clause", "offset": [408, 428]}, {"key": "with-respect-to", "type": "clause", "offset": [590, 605]}, {"key": "right-to-re", "type": "clause", "offset": [625, 636]}, {"key": "obligation-to-correct", "type": "clause", "offset": [676, 697]}, {"key": "in-accordance-with", "type": "definition", "offset": [755, 773]}, {"key": "the-foregoing", "type": "definition", "offset": [774, 787]}, {"key": "joint-development-plan", "type": "definition", "offset": [842, 864]}], "size": 1, "snippet": "As soon as reasonably practicable, but in any event within forty-five (45) days after IGT\u2019s 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 (\u201cStatement of Errors\u201d). For purposes of this SCIA, \u201cError\u201d means [\u2026***\u2026] [\u2026***\u2026] [\u2026***\u2026] [\u2026***\u2026] 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\u2019s right to re-test the Developed Software and PGIC\u2019s 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.", "samples": [{"hash": "erBky7aKdFH", "uri": "/contracts/erBky7aKdFH#acceptance-testing-procedure", "label": "Asset Purchase and License Agreement (Progressive Gaming International Corp)", "score": 21.0, "published": true}], "hash": "12b792815430cdacd3efd683c58ccc15", "id": 7}, {"snippet_links": [{"key": "functional-testing", "type": "clause", "offset": [5, 23]}, {"key": "integration-testing", "type": "definition", "offset": [28, 47]}, {"key": "city-staff", "type": "definition", "offset": [77, 87]}, {"key": "necessary-tools", "type": "clause", "offset": [159, 174]}, {"key": "prior-to", "type": "definition", "offset": [215, 223]}, {"key": "test-scripts", "type": "definition", "offset": [277, 289]}, {"key": "test-matrix", "type": "definition", "offset": [345, 356]}, {"key": "by-subcontractor", "type": "clause", "offset": [357, 373]}, {"key": "city-will", "type": "clause", "offset": [401, 410]}, {"key": "the-\u2587", "type": "clause", "offset": [436, 441]}, {"key": "customer-data", "type": "clause", "offset": [469, 482]}, {"key": "the-subcontractor", "type": "clause", "offset": [506, 523]}, {"key": "the-documents", "type": "clause", "offset": [537, 550]}, {"key": "and-training", "type": "clause", "offset": [551, 563]}, {"key": "the-system", "type": "definition", "offset": [567, 577]}, {"key": "to-city", "type": "definition", "offset": [578, 585]}, {"key": "phone-calls", "type": "clause", "offset": [653, 664]}, {"key": "and-documentation", "type": "clause", "offset": [665, 682]}, {"key": "as-needed", "type": "clause", "offset": [683, 692]}, {"key": "time-to-perform", "type": "clause", "offset": [729, 744]}, {"key": "the-software", "type": "clause", "offset": [776, 788]}, {"key": "live-production-environment", "type": "clause", "offset": [813, 840]}, {"key": "acceptance-testing-period", "type": "definition", "offset": [848, 873]}, {"key": "the-acceptance", "type": "clause", "offset": [891, 905]}, {"key": "detailed-project-plan", "type": "definition", "offset": [944, 965]}, {"key": "formal-written-notification", "type": "clause", "offset": [1023, 1050]}, {"key": "ready-for-testing", "type": "definition", "offset": [1130, 1147]}, {"key": "both-parties", "type": "clause", "offset": [1188, 1200]}, {"key": "the-evaluation", "type": "clause", "offset": [1274, 1288]}, {"key": "requirements-document", "type": "definition", "offset": [1391, 1412]}, {"key": "testing-criteria", "type": "definition", "offset": [1446, 1462]}, {"key": "the-solution", "type": "definition", "offset": [1476, 1488]}, {"key": "solution-acceptance-criteria", "type": "clause", "offset": [1527, 1555]}, {"key": "notice-thereof", "type": "clause", "offset": [1615, 1629]}, {"key": "date-of", "type": "clause", "offset": [1639, 1646]}, {"key": "notice-to", "type": "definition", "offset": [1652, 1661]}, {"key": "acceptance-date", "type": "definition", "offset": [1686, 1701]}, {"key": "in-the-event", "type": "clause", "offset": [1704, 1716]}, {"key": "following-the", "type": "definition", "offset": [1806, 1819]}, {"key": "testing-cycle", "type": "definition", "offset": [1848, 1861]}, {"key": "written-notice", "type": "definition", "offset": [1900, 1914]}, {"key": "notice-of", "type": "clause", "offset": [2061, 2070]}, {"key": "subcontractor-shall", "type": "clause", "offset": [2082, 2101]}, {"key": "in-accordance-with", "type": "definition", "offset": [2277, 2295]}, {"key": "the-correction-period", "type": "clause", "offset": [2487, 2508]}, {"key": "by-city", "type": "clause", "offset": [2590, 2597]}, {"key": "testing-process", "type": "definition", "offset": [2623, 2638]}, {"key": "the-city-shall", "type": "clause", "offset": [2662, 2676]}, {"key": "based-on", "type": "clause", "offset": [2719, 2727]}, {"key": "severity-3", "type": "clause", "offset": [2732, 2742]}], "size": 1, "snippet": "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 \u2587\u2587\u2587\u2587\u2587\u2587 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 \u201cAcceptance Testing Period\u201d). 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 \u2587\u2587\u2587\u2587\u2587\u2587 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 \u201cSolution Acceptance Criteria\u201d), City will provide Subcontractor with written acceptance notice thereof, and the date of such notice to be the \u201cActual Solution Acceptance Date\u201d. 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 \u201cCorrection Period\u201d to correct any deficiency, after which the Solution Acceptance Testing will be resumed. The Correction Period will be defined in the Detailed Project Plan. In the event retesting is required by City, the Solution Acceptance Testing process will then be repeated. The City shall not reject or fail to accept the Software based on any Severity 3 issues, as defined in the table below;", "samples": [{"hash": "2Q1Z1ttJgjH", "uri": "/contracts/2Q1Z1ttJgjH#acceptance-testing-procedure", "label": "Master Agreement", "score": 22.8986995209, "published": true}], "hash": "b30f047e337083a4d6dd5bbe0560396c", "id": 9}, {"snippet_links": [{"key": "following-acceptance", "type": "clause", "offset": [4, 24]}, {"key": "applies-to", "type": "clause", "offset": [43, 53]}], "size": 1, "snippet": "The following Acceptance Testing procedure applies to each Deliverable:", "samples": [{"hash": "bCFov1i7cxb", "uri": "/contracts/bCFov1i7cxb#acceptance-testing-procedure", "label": "Master Agreement", "score": 34.0574736054, "published": true}], "hash": "6287b6acd773ec3d4c36f50b5ba93157", "id": 10}], "next_curs": "CmUSX2oVc35sYXdpbnNpZGVyY29udHJhY3RzckELEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IiVhY2NlcHRhbmNlLXRlc3RpbmctcHJvY2VkdXJlIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"title": "Acceptance Testing Procedure", "parents": [["production-of-instruments", "Production of Instruments"], ["acceptance-testing", "Acceptance Testing"], ["acceptance-test", "Acceptance Test"], ["general-terms-and-conditions", "General Terms and Conditions"], ["further-cooperation", "Further Cooperation"]], "size": 33, "children": [["intentionally-omitted", "Intentionally Omitted"], ["sbc-12state-will", "SBC-12STATE will"], ["acceptance-of-deliverables", "Acceptance of Deliverables"], ["testing-equipment", "Testing Equipment"], ["acceptance-by-client", "Acceptance by Client"]], "id": "acceptance-testing-procedure", "related": [["acceptance-testing", "Acceptance Testing", "Acceptance Testing"], ["acceptance-tests", "Acceptance Tests", "Acceptance Tests"], ["testing-procedures", "Testing Procedures", "Testing Procedures"], ["hiring-procedure", "HIRING PROCEDURE", "HIRING PROCEDURE"], ["acceptance-procedure", "Acceptance Procedure", "Acceptance Procedure"]], "related_snippets": [], "updated": "2025-07-07T12:37:50+00:00", "also_ask": ["What negotiation leverage can be gained by defining or narrowing acceptance criteria?", "Which drafting elements are essential to prevent disputes over test results or timelines?", "What are the most common risks or loopholes that undermine enforceability of acceptance testing clauses?", "How do acceptance testing procedures in this contract compare to industry standards or statutory requirements?", "What evidence is most persuasive in court to prove compliance or non-compliance with acceptance testing procedures?"], "drafting_tip": "Specify testing criteria and timelines to ensure clarity; require written acceptance to confirm mutual agreement; outline remedies for failed tests to provide recourse.", "explanation": "The Acceptance Testing Procedure clause outlines the process by which a delivered product or service is evaluated to ensure it meets the agreed-upon specifications and requirements. Typically, this clause details the steps for conducting tests, the criteria for passing or failing, and the timeframe within which the client must review and accept or reject the deliverable. By establishing a clear and structured method for verifying compliance, this clause helps prevent disputes over quality and ensures both parties have a mutual understanding of when obligations have been satisfactorily fulfilled."}, "json": true, "cursor": ""}}