Incoming Specifications Sample Clauses

Incoming Specifications. The parties will in good faith cooperate with one another to develop the Specifications, which shall be acceptable to both parties. The Specifications shall be agreed upon in writing and shall be attached hereto and incorporated into this Agreement as Exhibit B, and may be amended from time to time by mutual written agreement of the parties. The Specifications shall be considered confidential information pursuant to Section 13 of the Collaboration Agreement and for the purposes of Section 10 hereof.
AutoNDA by SimpleDocs
Incoming Specifications. The parties will in good faith cooperate (via the Joint Steering Committee) with one another to develop the Specifications, which shall be acceptable to both parties and in any event in compliance with cGMP and any and all requirements of the Regulatory Authority in the Territory. The Specifications shall be agreed upon in writing by the parties and attached hereto and incorporated into this Supply Agreement as Exhibit B. To avoid doubt, with respect to any detailed aspects of the manufacturing process for Supply Product that are not explicitly stated in the agreed-upon Specifications, initially such detailed aspects are subject to mutual agreement by the parties (after which such detailed aspects shall be deemed included within the Specifications) and shall only be changed or amended in accordance with the process to amend the Specifications set forth in this Section. The Specifications may be amended from time-to-time by mutual written agreement of the parties and as set forth in this Section with respect to changes required to meet regulatory requirements in the Territory. Each of the parties acknowledges and agrees that it is each of their intentions for the Specifications to be the same in the Territory and in the Retained Territory, and they each agree to work together in good faith toward that intention. Notwithstanding the foregoing, the parties each agree that any change to the Specifications required to meet regulatory requirements in the Territory shall be deemed mutually agreed upon and the Specifications shall be deemed amended to incorporate such required change. ZKC shall notify Theraclone of such required changes and the regulatory requirements requiring them. Any costs of such required change to the Specifications (after the initial Specifications have been mutually agreed by the parties) shall be borne by ZKC. In addition, if ZKC requires (i) that the Specifications for Supply Product (including, without limitation, a combination product) to be used in the Territory are different from the specifications for the corresponding product in the Retained Territory and/or (ii) different Specifications because ZKC requires a Supply Product that is different from the product(s) being developed and/or commercialized in the Retained Territory, then [***] of all costs and expenses associated with developing such different Specifications for the Territory shall be ZKC’s responsibility, including (without limitation) all process development, manufactur...

Related to Incoming Specifications

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • Class Specifications The Human Resources Division shall determine:

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • 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.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

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