Product specific agreements Sample Clauses

Product specific agreements. Pursuant to one or more product specific agreements entered into and mutually agreed from time to time by duly authorized representatives of the Parties (“Product specific agreements” or “PSAs”), SBL will perform manufacturing services for Client as specified in such PSAs and applicable Project Plan and in accordance with the terms and conditions of this MSA (“Services”). Each PSA shall refer to this MSA and contain as applicable (i) a high level scope of work of the Services to be performed under such PSA which describes key activities, (ii) the Product for which Samsung will perform such Services for Client, (iii) a description of the Cell Line; (iv) fees to be paid to SBL by Client for the Services with a general timing plan for invoicing and a more detailed plan to be in the Project Plan, (v) if the Services pertain to the manufacture of the Product, the number of batches of Product to be manufactured by SBL and delivered to Client and the Specifications, (vi) any other deliverables, (vii) the Samsung facility where the Services are to be performed, and (viii) the Regulatory Approvals to be obtained by the Parties. Services shall be governed by the terms and conditions of this MSA, the applicable PSA, and any applicable Quality Agreement. In the event of a conflict between a Quality Agreement and either any provision of this MSA or any PSA, the MSA or PSA shall control except with respect to Product quality terms, in which case, the Quality Agreement will control. In the event of a conflict between any provision of this MSA and the PSA, this MSA shall control, except as explictly specified in the PSA.
Sample 1See All (5)
AutoNDA by SimpleDocs
Product specific agreements. SBL will perform Services for Client as specified in PSAs and in accordance with the terms and conditions of this MDSA. In the event of a conflict between any provision of this MDSA and the PSA, this MDSA shall control, except where the PSA specifically states otherwise and references this Section 2.1.
Sample 1
Product specific agreements. Pursuant to one or more Product specific agreements entered into and mutually agreed from time to time by duly authorized representatives of the Parties (“Product Specific Agreements” or “PSAs”), SBL will perform Manufacturing Services for Client as specified in such PSAs and in accordance with the terms and conditions of this MSA (“Services”). Each PSA shall refer to this MSA and contain as applicable (i) a high level scope of work of the Services to be performed under such PSA which describes key activities, (ii) the Product for which SBL will perform such Services for Client, (iii) a description of the Cell Line; (iv) fees to be paid to SBL by Client for such Services with a general timing plan for invoicing and a more detailed plan to be provided where appropriate, (v) if such Services pertain to the Manufacture of the Product, the number of Batches of Product to be manufactured by SBL and delivered to Client and the REF: 00038830.0 10. Confidential /// Fibrogen - Samsung Master Services Agreement (38830.0) 2020
Sample 1

Related to Product specific agreements

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

  • Product Specific Terms these terms apply to specific Products referenced in this section.

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

  • Supply Agreement Seller and Buyer, or their Affiliates, shall have executed the Supply Agreement.

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

  • Supply Agreements For a period of three years from the consummation of the IPO, Odetics shall not unilaterally terminate or assign its guarantee obligation with respect to any supply agreement pursuant to which it has guaranteed the performance by ATL of ATL's obligations, unless such suppliers have consented to the termination or assignment of such guarantee.

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

  • Specific Agreements 1. Investments made pursuant to a specific agreement concluded between one Contracting Party and investors of the other Party shall be covered by the provisions of this Agreement and by those of the specific agreement.

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