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. 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 [***] as set out below, to create incentives to improve software and documentation quality.
11.01.5 OMT shall attend semiannual executive quality reviews, [***]. The Parties shall mutually agree on the frequency and location of such quality reviews, and the Parties shall confirm the agenda [***]. The Parties acknowledge that [***].
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 suppliers of Third Party Standard Software.
11.02.2 The Parties agree that Corrective Releases, New Releases and ISE Requested Releases can be delivered as separate deliveries or combined into one delivery. *** Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.
11.02.3 If ISE requests, OMT shall provide, telephone and on-site support for the installation and testing of releases.
11.02.3.1 OMT will provide telephone support during Operational...
Delivery Testing and Acceptance. 8 8 DELAYS.............................................................. 9 9 PRICING............................................................. 10 10
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. 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
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...
Delivery Testing and Acceptance. All deliveries of equipment or physical goods required under this Agreement shall be F.C.A.
Delivery Testing and Acceptance. RESPONSIBILITIES OF THE PARTIES.........................................................................8 Section 4.1
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.
