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.
LIS Forecasting 7.2.2.8.1 Both CLEC and Qwest shall work in good faith to define a mutually agreed upon forecast of LIS trunking.
TRUNK FORECASTING 58.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Embarq shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Embarq twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include:
Purchase Order Number NETAPP's purchase order number must appear on all invoices, packing lists and bills of lading and shall appear on each package, container or envelope on each shipment made pursuant to such purchase order.
Purchase Order Pricing/Product Deviation If a deviation of pricing/product on a Purchase Order or contract modification occurs between the Vendor and the TIPS Member, TIPS must be notified within five (5) business days of receipt of change order. Termination for Convenience of TIPS Agreement Only TIPS reserves the right to terminate this agreement for cause or no cause for convenience with a thirty (30) days prior written notice. Termination for convenience is conditionally required under Federal Regulations 2 CFR part 200 if the customer is using federal funds for the procurement. All purchase orders presented to the Vendor, but not fulfilled by the Vendor, by a TIPS Member prior to the actual termination of this agreement shall be honored at the option of the TIPS Member. The awarded Vendor may terminate the agreement with ninety (90) days prior written notice to TIPS 0000 XX Xxx Xxxxx, Xxxxxxxxx, Xxxxx 00000. The vendor will be paid for goods and services delivered prior to the termination provided that the goods and services were delivered in accordance with the terms and conditions of the terminated agreement. This termination clause does not affect the sales agreements executed by the Vendor and the TIPS Member customer pursuant to this agreement. TIPS Members may negotiate a termination for convenience clause that meets the needs of the transaction based on applicable factors, such as funding sources or other needs. TIPS Member Purchasing Procedures Usually, purchase orders or their equal are issued by participating TIPS Member to the awarded vendor and should indicate on the order that the purchase is per the applicable TIPS Agreement Number. Orders are typically emailed to TIPS at xxxxxx@xxxx-xxx.xxx. • Awarded Vendor delivers goods/services directly to the participating member. • Awarded Vendor invoices the participating TIPS Member directly. • Awarded Vendor receives payment directly from the participating member. • Fees are due to TIPS upon payment by the Member to the Vendor. Vendor agrees to pay the participation fee to TIPS for all Agreement sales upon receipt of payment including partial payment, from the Member Entity or as otherwise agreed by TIPS in writing and signed by an authorized signatory of TIPS.
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.
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.
