Required Lead Time Sample Clauses

Required Lead Time. If Buyer submits a Purchase Order with a Delivery Schedule that does not allow for the Required Lead Time (each, a “Rush Order”) and Seller accepts and issues an Order Acknowledgement, Seller shall use commercially reasonable efforts to fill any such Rush Order. Notwithstanding anything to the contrary in this Agreement, Seller shall be under no obligation to accept a Rush Order and shall not be in breach of this Agreement should it accept such Rush Order and fail to deliver the Products at the Delivery Point by the Scheduled Ship Date(s).
Sample 1Sample 2
AutoNDA by SimpleDocs
Required Lead Time. QuickBooks will estimate the minimum time necessary between your instruction and the date the payment can be delivered (“Lead Time”), for each payment you wish to make. The stated Lead Time is an estimate only. We cannot guarantee prompt receipt and processing of payments by payees, so you must schedule a payment sufficiently in advance of the due date, (the “Due Date”) not including any grace period, to avoid late charges. We will not be responsible for any loss you may incur as a consequence of late payment if your payment is not scheduled within the time periods described in this Section.
Sample 1

Related to Required Lead Time

  • Lead Time The lead-time for delivery of Panther Drive Systems under a Purchase Order shall be * from the date of Purchase Order submission.

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

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

  • Lead Times In general, lead times shall be in accordance with the provisions of the latest edition of the “World Airlines and Suppliers Guide”.

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

  • Response Time PROVIDING PARTY shall respond to and resolve any problems in connection with the Corporate Services for RECEIVING PARTY within a commercially reasonable period of time, using response and proposed resolution times consistent with its response and resolution of such problems for itself.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

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

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

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

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