Delivery Schedule The scheduled months of delivery of the Aircraft are listed in the attached Table 1. Exhibit B describes certain responsibilities for both Customer and Boeing in order to accomplish the delivery of the Aircraft.
DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.
Project Delivery Contractor shall construct the Project in accordance with the Contract Documents, and Contractor shall deliver the Project completed in accordance with the Contract Documents, substantially free from defects, and within the Contract Time.
Delivery Date and Cancellation You agree to the cancellation policies and the procedures for scheduling of Training and On-Site Courses available at xxx.xxxxxx.xxx/xxxxxxxx/xxxxxxxxxxxx.xxxx. You must use all Red Hat training offerings, including Training Units and Consulting Units, within one (1) year of the date of purchase; any unused training offerings will be forfeited.
PRODUCT DELIVERY Delivery must be made as ordered to the address specified on the Purchase Order and in accordance with the terms of the Contract or Contract Award Notice. Unless otherwise specified in the Bid Documents, delivery shall be made within thirty calendar days after receipt of a Purchase Order by the Contractor. The decision of the Commissioner as to compliance with delivery terms shall be final. The burden of proof for delay in receipt of Purchase Order shall rest with the Contractor. In all instances of a potential or actual delay in delivery, the Contractor shall immediately notify the Commissioner and the Authorized User, and confirm in writing the explanation of the delay, and take appropriate action to avoid any subsequent late deliveries. Any extension of time for delivery must be requested in writing by the Contractor and approved in writing by the Authorized User. Failure to meet such delivery time schedule may be grounds for cancellation of the order or, in the Commissioner’s discretion, the Contract.
Delivery Location All Goods shall be delivered to the address specified in this Order (the "Delivery Location") during Buyer's normal business hours or as otherwise instructed by Buyer.
Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:
Notification of Delivery Destination Prior to final acceptance of contract requirements by STATE, PURCHASER shall notify STATE, in a form and manner prescribed by STATE, of the delivery destination of all timber purchased under this contract. STATE may hold PURCHASER's performance bond until satisfactory delivery destination information has been received. Notice of Transfer of State Timber. Prior to selling, trading, exchanging, or otherwise conveying unprocessed timber sold under this contract to any other person, PURCHASER must first obtain a certification of the person's eligibility to purchase unprocessed State timber, and their intent to comply with the terms and conditions contained in OAR 629-031-0005 through 629-031-0045. The certification shall be made in a form and manner prescribed by STATE, and shall be forwarded to STATE upon completion of the transaction. Obtaining the certification shall not relieve PURCHASER of the responsibility to provide STATE with an accounting of the delivery destination of that timber.
Delivery Dates If the due date of any notice, certificate or report required to be delivered by the Manager hereunder falls on a day that is not a Business Day, the due date for such notice, certificate or report shall be automatically extended to the next succeeding day that is a Business Day.
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.
