Changes to Manufacturing Services, Packaging and Shipping Specifications and Test Procedures Sample Clauses

Changes to Manufacturing Services, Packaging and Shipping Specifications and Test Procedures. Company may, in writing, request a change to the Manufacturing Services, Packaging and Shipping Specifications and Test Procedures at any time. Jabil will analyze the requested change and provide Company with an assessment of the effect that the requested change will have on cost, manufacturing, scheduling, delivery and implementation. Company will be responsible for all costs associated with any accepted changes. Any such change shall be documented in a written change order and shall become effective only upon mutual written agreement of both Parties to the terms and conditions of such change order, including changes in time required for performance, cost and applicable delivery schedules.
AutoNDA by SimpleDocs
Changes to Manufacturing Services, Packaging and Shipping Specifications and Test Procedures. Company or Jabil may, in writing, request a change to the Manufacturing Services, Packaging and Shipping Specifications and Test Procedures at any time. Jabil will analyze the requested change and provide Company with an assessment of the effect in writing that the requested change will have on cost, manufacturing, scheduling, delivery and implementation. Company will be responsible for all costs associated with any accepted changes. Any such change shall be documented in a written change order and shall become effective only upon mutual written agreement of both Parties to the terms and conditions of such change order, including changes in time required for performance, cost and applicable delivery schedules. JBL073 Manufacturing Services Agreement [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions.

Related to Changes to Manufacturing Services, Packaging and Shipping Specifications and Test Procedures

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

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

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

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

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

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

  • Quality Agreement If appropriate or if required by Applicable Law, the parties will also agree upon a Quality Agreement containing quality assurance provisions for the Manufacture of Product (“Quality Agreement”), which agreement will also be attached to the applicable Work Order and incorporated by reference in the Work Order.

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

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

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