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. 4.1 Subject Clause 3 above, the Developer shall carry out their respective responsibilities pertaining to the Services and Deliverables rendered by the Developer in accordance with the mutually agreed acceptance test plan.
4.2 Before delivering and installing any Software Deliverable, the Developer shall:
(a) test the Software component of such Software Deliverable to confirm that it is fully operable, meets all applicable Specifications, and will function in accordance with the Specifications and Documentation when properly installed in the operational environment;
(b) scan such Software Deliverable using the most up-to-date scanning software and definitions to confirm it is free of harmful code;
(c) remedy any Non-Conformity or harmful code identified and retest and rescan the Software Deliverable; and
(d) prepare, test and as necessary, revised Documentation component of the Software Deliverable to confirm it is complete and accurate and conforms to all requirement of this Agreement.
4.3 The Developer shall conduct user acceptance tests (“UAT”) together with the Company which results are to be verified and acknowledge by the Company 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 Company until those criteria are met.
4.4 Should the Software and/or Deliverables fails to conform to an acceptance test despite numerous repeated UAT, the Company may terminate this Agreement in accordance to Clause 13 herein, in the event that the acceptance test has failed more than three (3) times. The Developer hereby irrevocably agrees to refund all such Service Fees or any part thereof which has been paid to the Developer by the Company within fourteen (14) calendar days from the date of termination of this Agreement.
4.5 The Developer shall deliver each Deliverable and install all Software on or prior to the Milestone Date therefor in accordance with the delivery criteria set forth in Appendix B or such other criteria as may be set forth for such Deliverable in the Scope of Services therefor. Developer shall deliver each Software Deliverable, including complete Documentations and except to the extent the Scope of Services specific otherwise, the source code therefor. No Software Deliverable shall be deemed to have been delivered or installed unless it complies with the preceding sentence.
Delivery Testing and Acceptance. 8 8 DELAYS.............................................................. 9 9 PRICING............................................................. 10 10
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. 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. Subject to Article 8.3 of this Agreement, as soon as practicable after receipt of an order for the Intermediate from PathoGenesis, BMS shall manufacture and ship the specified quantity of the Intermediate ordered by PathoGenesis to the destination specified in the order. Each shipment shall be accompanied by the appropriate certificates of analysis with respect to the Intermediate. BMS shall arrange for shipment of all orders for the Intermediate hereunder Free on Board (FOB) BMS manufacturing facility (Incoterms 1990). PathoGenesis shall have a maximum of 45 days from the date of receipt of any shipment of the Intermediate to test for quality and quantity of the shipment and to accept or reject such shipment. If PathoGenesis determines that any shipment or portion thereof of the Intermediate does not meet the specifications warranted by BMS hereunder, PathoGenesis shall notify BMS in writing within 45 days of receipt of the shipment, indicating the particular lot, date of delivery and the defective nature of Intermediate.
Delivery Testing and Acceptance. 1 (a) Delivery...................................................................... 1 (b) Testing....................................................................... 2 (c) Acceptance.................................................................... 2 3. MODIFICATIONS............................................................................ 2 4.
Delivery Testing and Acceptance. All deliveries of equipment or physical goods required under this Agreement shall be F.C.A.
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
2.4 shall apply.
5.2 Upon completion of the creation of a system, or any module of a system, BlackLight Software shall notify the Client in writing of such completion and proposals for carrying out Acceptance Tests.
5.3 BlackLight Software shall prepare, with the reasonable assistance of the Client, and deliver in accordance with the Proposal and on a medium suitable for testing a copy of the module capable of suitable for User Acceptance Tests.
5.4 The Client shall, if reasonably required by BlackLight Software, prepare and provide test cases and test databases sufficient to enable each of the Acceptance Tests to be performed.
5.5 The Acceptance Tests in relation to each module shall be suitable to demonstrate that the relevant module, and any of the other modules which have been accepted prior to the commencement of such Acceptance Tests, fulfil the requirements of such module/s or system.
5.6 BlackLight will provide the client with 20 Working Days from delivery of the Module in which to carry out User Acceptance Tests of the module and/or system.
5.7 Before the release of a working module or system to the Client, BlackLight Software shall carry out pre-defined, mutually agreed, UAT (User Acceptance Testing).
5.8 At the end of the period referred to in condition 5.6, and subject to the Client not identifying any failure of the module or system to meet the Specification, and which are not thereby rectified by BlackLight Software, BlackLight Software shall require the Client to certify in writing to BlackLight Software in a form provided by BlackLight Software (the Acceptance Certificate”), that the Client has conducted full program and systems testing of all relevant parts of that module/the System and believes that that module/the System will perform to meet the Specification.
5.9 Save where the Client has identified any failure to meet the Specification, the Supplier shall promptly, and not less than 3 Working Days following the period referred to in condition 5.6 provide BlackLight Software with a properly signed an...