Required Specification Changes Sample Clauses

Required Specification Changes. 2.4.2.1 If a Required Specification Change is necessary, the Parties will confer immediately and in good faith to determine the most cost-effective and efficient means to implement or to otherwise provide for the Required Specification Change.
AutoNDA by SimpleDocs
Required Specification Changes. For changes to the Specifications that are required by Laws (collectively “Required Specification Changes”), EUSA and Innocoll shall cooperate in making such changes and use Commercially Reasonable Efforts to implement such changes in compliance with such Laws and as promptly as practicable.
Required Specification Changes. Allos will maintain a system (consistent with standard industry practice) to control and implement changes to API Specifications and Bulk Product Specifications, manufacturing processes and qualification procedures, in accordance with GMPs and other applicable Laws in the United States, the European Countries or under ICH Guidelines. Each Party will provide written notice in a timely manner to the other Party of any other applicable Laws in their respective territories that require any such changes. Any costs associated with changes to the Specifications required by Regulatory Authorities in the Licensed Territory that are not also required in the U.S. or Canada will be [***]. Any costs associated with changes to the API Specifications and Bulk Product Specifications procured by Allos for its own use required by Regulatory Authorities in the U.S. or Canada will be [***] unless such changes are also required by Regulatory Authorities in the Licensed Territory, in which case [***].
Required Specification Changes. For changes to the Specifications that are required by a Governmental Authority, the Marketing Authorization or applicable Laws (collectively “Required Specification Changes”), Adolor and Supplier shall cooperate in making such changes and Supplier shall implement such changes in compliance with such applicable Laws and as promptly as practicable.
Required Specification Changes. Spectrum will maintain a system (consistent with standard industry practice) to control and implement changes to Specifications, manufacturing processes and qualification procedures, in accordance with GMPs and other applicable Laws in the United States, the European Countries or under ICH Guidelines. Each Party will provide written notice in a timely manner to the other Party of any other applicable Laws in their respective territories that require any such changes. Any costs associated with changes to the Specifications required by Regulatory Authorities in the Licensed Territory that are not also required in the Spectrum Territory will be paid by MMCO. Any costs associated with changes to the Specifications procured by Spectrum for its own use required by Regulatory Authorities in the Spectrum Territory will be paid by Spectrum unless such changes are also required by Regulatory Authorities in the Licensed Territory, in which case they will be equally shared by the Parties.
Required Specification Changes. If a Governmental Authority in the Territory requires a change to the Product Specifications (a “Required Specification Change”), Incyte will promptly notify MacroGenics of such change. MacroGenics will use reasonable efforts to implement such Required Specification Change as promptly as possible within the time frame requested by the Governmental Authority at Incyte’s sole cost and expense.

Related to Required Specification Changes

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-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.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Class Specifications The Human Resources Division shall determine:

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Approval of Plans and Specifications The Plans and Specifications will conform to the requirements and conditions set out by applicable law or any effective restrictive covenant, and to all governmental authorities which exercise jurisdiction over the Leased Premises or the construction thereon.

Time is Money Join Law Insider Premium to draft better contracts faster.