Validation Batches and Initial Order Clause Samples

Validation Batches and Initial Order. Noven and Endo hereby acknowledge and agree that, in order to address the initial requirements for the commercial launch of the Product, the lead times associated with manufacturing Product and the general preparation for such commercial launch, Noven and Endo will consult with each other in good faith regarding the anticipated commercial launch date. In connection with such discussions Endo will provide a binding initial purchase order to Noven approximately *** ; the delivery date for such purchase orders shall be between one and thirty days prior to the anticipated commercial launch date of the Product. The initial purchase orders shall be for quantities of the Product sufficient for launch and for the first month of sales of the Product; such amount of product shall be no less than *** and no greater than *** of Endo's most recent forecasted requirements for the first month of sales of the Product; provided, however, that upon request by Endo, Noven shall attempt in good faith to supply a quantity of the Product in excess of *** of the amount.
View SourceView Similar (4)

Related to Validation Batches and Initial Order

  • Contract Closure Contracting Officer shall give appropriate written notice to Purchaser when Purchaser has complied with the terms of this contract. Purchaser shall be paid refunds due from Timber Sale Account un- der B4.24 and excess cooperative deposits under B4.218.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following: a) drawings, designs, or specifications, where Goods to be furnished under the Contract are to be specifically manufactured for the Procuring Entity; b) the method of shipment or packing; c) the place of delivery; and d) the Related Services to be provided by the Supplier. 33.2 If any such change causes an increase or decrease in the cost of, or the time required for, the Supplier's performance of any provisions under the Contract, an equitable adjustment shall be made in the Contract Price or in the Delivery/Completion Schedule, or both, and the Contract shall accordingly be amended. Any claims by the Supplier for adjustment under this Clause must be asserted within twenty-eight (28) days from the date of the Supplier's receipt of the Procuring Entity's change order. 33.3 Prices to be charged by the Supplier for any Related Services that might be needed but which were not included in the Contract shall be agreed upon in advance by the parties and shall not exceed the prevailing rates charged to other parties by the Supplier for similar services.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before July 1, 2021, Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before July 15, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.