Meeting the Specifications Sample Clauses

Meeting the Specifications. (a) Schedule 3 sets out the minimum Specifications required for the supply of Milk to us. You agree to meet or exceed the minimum Specifications in the provision of all Litres of Milk. (b) Schedule 3 also sets out the Control Limits for supply of Milk to us. You agree not to supply any milk that does not meet the Control Limits. (c) If you believe you will not be able to supply the Milk at or better than the minimum Specifications for a particular delivery, you will advise us (or our Representative) of the likely specification problem as soon as you form such belief. Where you supply Milk for collection by us at the Dairy for a particular delivery that does not meet the minimum Specifications but meets the Control Limits (“Failed Milk”) on:‌ (i) 5 consecutive milk collections; or (ii) 10 individual milk collections in a 6-month period, you will trigger a “Failed Milk Corrective Action” event. (d) For any “Failed Milk Corrective Action” event you are required, within 5 working days of being notified, to: (i) conduct further investigations into the causes of the Failed Milk and report back to us; and (ii) take whatever other action we deem reasonably necessary in order to mitigate the risk of a re- occurrence of those causes. Until you satisfy us that the causes of the Failed Milk have been rectified, we shall not be liable to accept Milk from you. (e) If you have 3 “Failed Milk Corrective Action” events in any 12 month period or you do not comply with the requirements of any single “Failed Milk Corrective Action” event as outlined in clause 3.4(d) then we will meet with you to discuss how to resolve this ongoing failure in good faith. (f) If you supply any Milk that does not meet the Control Limits or specifications, we have no obligation to purchase that Milk. We may: (i) deduct certain amounts from the payment for the Milk in accordance with Schedule 3; (ii) reject the Milk; or (iii) undertake whatever other reasonable action regarding that Milk, including disposal at your cost. (g) If milk supplied by you that does not meet the Control Limits results in the contamination of other milk within the FDA pick up / processing system, you will be held responsible for the total volume of milk and the total cost of rectification.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Meeting the Specifications. (a) Schedule 3 sets out the minimum Specifications required for the supply of Milk to us. You agree to meet or exceed the minimum Specifications in the provision of all Litres of Milk. (b) Schedule 3 also sets out the Control Limits for supply of Milk to us. You agree not to supply any milk that does not meet the Control Limits. (c) If you believe you will not be able to supply the Milk at or better than the minimum Specifications for a particular delivery, you will advise us (or our Representative) of the likely specification problem as soon as you form such belief. Where you supply Milk for collection by us at the Dairy for a particular delivery that does not meet the minimum Specifications but meets the Control Limits F³ailed Milk´o n: (i) 5 consecutive milk collections; or (ii) 10 individual milk collections in a 6-month period, outlined in clause 3.4(d) then we will meet with you to discuss how to resolve this ongoing failure in good faith.
Sample 1

Related to Meeting the Specifications

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

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

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

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

  • ODUF Packing Specifications 6.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.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

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

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!