Delivery Testing and Acceptance Sample Clauses
Delivery Testing and Acceptance. System: You shall, within thirty (30) days after the Effective Date, make the System available to us and deliver to us a master copy of the Software licensed hereunder in object code form, suitable for reproduction in accordance with this Agreement, in electronic files unless otherwise requested by us. All Government license keys, usernames, and passwords shall be authenticated by the Supplier and perform according to the SOW.
Delivery Testing and Acceptance. All deliveries of equipment or physical goods required under this Agreement shall be F.C.A. Selectron’s facilities. Selectron shall provide Licensee with the Documentation and access to the Licensed Software according to the delivery, testing, and acceptance schedule and terms and conditions set forth in Exhibit A and Exhibit C. Unless a testing period of different duration is set forth in Exhibit A or Exhibit C, Licensee shall have a testing period of thirty
Delivery Testing and Acceptance. 8 8 DELAYS.............................................................. 9 9 PRICING............................................................. 10 10
Delivery Testing and Acceptance. 11.01 OMT shall deliver Corrective Releases, ISE Requested Releases, and New Releases in the manner set forth herein.
11.01.1 The Parties intend that ISE will order ISE Requested Releases from OMT on a fixed time and fixed price basis.
11.01.2 OMT acknowledges that software and documentation quality and time to production start are of critical importance to ISE.
11.01.3 ISE acknowledges that OMT requires a defined scope before committing to deliveries on a fixed time and price basis. Changes to the scope may cause delays in OMT’s ability to adhere to delivery schedules. ISE further acknowledges that OMT requires timely deliveries of specifications and clarifications on changed and new requirements on functional and non-functional features in the software, and that delays in providing such specifications and clarifications may cause delays in OMT’s ability to adhere to delivery schedules.
11.01.4 The Parties acknowledge that they have increased their efforts under this Agreement to monitor and maintain software and documentation quality, and both Parties shall work together on these efforts for the duration of the Agreement. In addition, the Parties have agreed to implement a Software and Documentation Quality Penalty and Bonus Program, as set out below, to create incentives to improve software and documentation quality.
11.01.5 OMT shall attend semiannual executive quality reviews, which are separate from the support meetings and capacity planning meetings. The Parties shall mutually agree on the frequency and location of such quality reviews, and the Parties shall confirm the agenda for the quality review at least [***] in advance of any such meeting. The Parties acknowledge that the Acceptance Testing procedures in this Agreement are more comprehensive than the procedures in the previous support agreement, and that such procedures may affect schedules for providing testing and Acceptance.
11.02 The Parties shall plan and administer Corrective Releases, ISE Requested Releases, and New Releases in the manner set forth herein.
11.02.1 OMT shall, twice per year, provide ISE a one-year “look-ahead” product schedule of OMT releases and related Third Party Standard Software. The Parties recognize that these product schedules are forecasts that are subject to change. The Third Party Standard Software schedule will include, but will not be limited to, VMS, MS Windows NT, RTR, BMC Patrol, to the degree that accurate release information is available from the suppli...
Delivery Testing and Acceptance. 1 (a) Delivery...................................................................... 1 (b) Testing....................................................................... 2 (c) Acceptance.................................................................... 2 3. MODIFICATIONS............................................................................ 2 4.
Delivery Testing and Acceptance. 5.1 If any delay or failure in the Client’s performance of the Client’s obligations under this Agreement causes BlackLight Software delay in the performance of its obligations under this Agreement and/or causes BlackLight Software incur additional costs, then BlackLight Software is entitled to an extension of time to meet its obligations under this Agreement to take account of the impact caused by such delay and the provisions of conditions
Delivery Testing and Acceptance. RESPONSIBILITIES OF THE PARTIES.........................................................................8 Section 4.1
Delivery Testing and Acceptance. (1) The Supplier is responsible for ensuring that upon delivery the Application complies with the quality level specified in Annex 4. The Supplier shall substantiate the quality levels to the Client before handover.
(2) In addition to the tests under Section 4 of JIT 2015 – 3 (Special Terms and Conditions for the Procurement of Client’s Application under Software Terms Other than Open Source), the Supplier shall ensure that it performs sufficient testing of its own throughout the delivery process.
(3) The Supplier shall hand over the Application to the Client for acceptance testing no later than within 8 months after the signing of the agreement. At the request of the Client, the Supplier shall assist the Client during acceptance testing and the planning thereof.
(4) The Client shall have 30 days to perform the Client’s acceptance testing, starting from the date on which the Supplier has reported in writing that the Application or its agreed part is ready for acceptance testing and has handed over the Application for testing in accordance with Subsection 4.3 (3).
(5) The Supplier shall immediately correct any errors discovered during acceptance testing. The time reserved for acceptance testing shall be extended by the time the Supplier needs to correct the error and the Client reasonably needs for the testing and acceptance of the corrected errors.
(6) The Application is deemed deployed and the delivery completed when the Client has accepted it and the Supplier has fulfilled all its contractual delivery-related obligations.
(7) Accepted partial deliveries do not prevent the rejection of the whole delivery due to deficiencies identified during final testing.
(8) In other regards, the testing and acceptance of the Application is subject to what is stipulated in Section 4 of JIT 2015 – Annex 3 (Special Terms and Conditions for the Procurement of Client’s Application under Software Terms Other than Open Source).
Delivery Testing and Acceptance. 4.1 Subject Clause 3 above, the Service Provider shall carry out their respective responsibilities pertaining to the Services and deliverables as set out in APPENDIX A (“Deliverables”) in accordance with the mutually agreed acceptance test plan.
4.2 Each Deliverable shall:
(a) correspond to the applicable phase/component of the Services;
(b) be complete, fully functional, and fit for its intended purpose; and
(c) be accompanied by all relevant documentation, source code, object code, configuration files, and other materials reasonably necessary for TTSB to operate, maintain, support, and further develop the Apps.
4.3 Upon delivery of a Deliverable, the Service Provider shall conduct user acceptance tests (“UAT”) together with the TTSB which results are to be verified and acknowledge by the TTSB whereby in the event the end result fails to satisfy the acceptance criteria, the testing shall be repeated at reasonable intervals as required by the TTSB until those criteria are met.
4.4 Should the Deliverable fails to conform to an acceptance test despite numerous repeated UAT, the Service Provider shall promptly, at its own cost, rectify defects and resubmit for testing. No extension of time or additional compensation shall apply unless agreed in writing by TTSB.
4.5 A Deliverable is deemed accepted only upon issuance of TTSB’s written acceptance confirmation.
4.6 The Service Provider shall be responsible for the ongoing update and customization of the Tazte Apps and/or solution provided under this Agreement for the entire term of the Agreement.
4.7 In the event that the Service Provider fails to meet the service level, the following procedure shall be followed:
(a) TTSB shall promptly notify the Service Provider in writing of the service level breach;
(b) The Service Provider shall acknowledge the notificaftion and initiate actions to address and resolve the issue.
Delivery Testing and Acceptance. All deliveries of equipment or physical goods required under this Agreement shall be F.C.A.