Forecasts Orders Failure to Supply Sample Clauses
Forecasts Orders Failure to Supply
Rolling Forecasts Company shall provide Polyzen with a quarterly, rolling, written non-binding twelve (12) month forecast of its purchase requirements for the Products (each, a “Forecast”). Company’s initial Forecast shall be provided to Polyzen on the Effective Date. Company’s initial Purchase Order (the “Initial Purchase Order”) shall reflect the initial three months of the Forecast and shall be subject to the terms and conditions as provided in Section 2.2 of this Agreement. Thereafter, Company shall deliver to Polyzen its updated Forecast by no later than 5:00p.m. (EST) of the last business day of the second (2nd) month of the then current Order Period. For example, since the Effective Date of this Agreement is in July 2017, the initial Forecast delivered on the Effective Date would cover August 2017 through July 2018. Polyzen will use commercially reasonable efforts to maintain sufficient production capacity and redundancy to satisfy Company’s then forecasted requirements for the Products, which, in no event, will equal less than three (3) months of orders plus twenty percent (20%) upside flexibility.
Purchase Order A Customer may use purchase orders to buy commodities or contractual services pursuant to the Contract and, if applicable, the Contractor must provide commodities or contractual services pursuant to purchase orders. Purchase orders issued pursuant to the Contract must be received by the Contractor no later than the close of business on the last day of the Contract’s term. The Contractor is required to accept timely purchase orders specifying delivery schedules that extend beyond the Contract term even when such extended delivery will occur after expiration of the Contract. Purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the Contract shall survive the termination or expiration of the Contract and apply to the Contractor’s performance. The duration of purchase orders for recurring deliverables shall not exceed the expiration of the Contract by more than twelve months. Any purchase order terms and conditions conflicting with these Special Contract Conditions shall not become a part of the Contract.
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.
Forecasts and Orders 7.3.1 Not less than [*****] days prior to the first day of each calendar quarter (commencing with the first calendar quarter in which Intrexon, its sublicensees or their respective Affiliates order API from Halozyme hereunder), Intrexon shall prepare and provide Halozyme with a written forecast of its good faith estimated requirements for API under this Section 7.3 for each of the subsequent [*****] calendar quarters. Intrexon shall not (a) increase or decrease the quantity estimated for the [*****] quarterly period of each forecast from the quantity estimated for the [*****] quarterly period of the previous forecast, (b) increase or decrease the quantity estimated for the [*****] quarterly periods of each forecast by more than [*****] percent ([*****]%) of the quantity estimated for the [*****] quarterly periods of the previous forecast, respectively, without the prior express written consent of Halozyme. The quantities estimated for the [*****] quarterly periods of each forecast shall be non-binding, and for planning purposes only. 7.3.2 Intrexon shall be required to purchase [*****] of the quantity forecasted for each API under this Section 7.3 for the first and second quarterly periods of each forecast under Section 7.3.1. 7.3.3 Halozyme shall be required to supply the quantity of API ordered by Intrexon under this Section 7.3 in any calendar quarter up to [*****] percent ([*****]%) of the quantity forecasted for the [*****] quarterly period of the most recent forecast. If Intrexon’s Portions herein identified by [*****] have been omitted pursuant to a request for confidential treatment under Rule 24b-2 of the Securities Exchange Act of 1934, as amended. A complete copy of this document has been filed separately with the Securities and Exchange Commission. orders in any calendar quarter exceed [*****] percent ([*****]%) of the quantity forecasted for the [*****] quarterly period of the most recent forecast, Halozyme shall use commercially reasonable efforts to supply such excess. Halozyme shall use commercially reasonable efforts to meet Intrexon’s delivery requirements specified in accordance with Section 7.3.4. In the event of a shortfall to forecast, Halozyme shall use commercially reasonable efforts to apportion API among Intrexon and its other customers on a pro rata basis according to their respective forecasts. 7.3.4 Intrexon shall make all purchases under this Section 7.3 by submitting firm purchase orders to Halozyme. Each such purchase order shall be in writing in a form reasonably acceptable to Halozyme, and shall specify the quantity of API ordered, the place of delivery and the required delivery date therefor, which shall not be less than [*****] days after the date of such purchase order. No additional terms of any such purchase order shall be binding on Halozyme and are expressly rejected hereby. In the event of a conflict between the terms and conditions of any purchase order and this Agreement, the terms and conditions of this Agreement shall prevail.
Contract Quantity The Contract Quantity during each Contract Year is the amount set forth in the applicable Contract Year in Section D of the Cover Sheet (“Delivery Term Contract Quantity Schedule”), which amount is inclusive of outages.
Forecast Customer shall provide Flextronics, on a monthly basis, a rolling [***] forecast indicating Customer’s monthly Product requirements. The first [***] of the forecast will constitute Customer’s written purchase order for all Work to be completed within the first [***] period. Such purchase orders will be issued in accordance with Section 3.2 below.
Purchase Order Requirements Customers shall use a Request for Quote per section 287.056(2), Florida Statutes, when making purchases off of this State Term Contract. Customers shall issue Request for Quotes to at least 25 vendors approved to provide IT Staff Augmentation services in accordance with section 287.0591(5), Florida Statutes. Customers shall order services from the Request for Quote via a Purchase Order with the Customers’ selected Contractor. The terms of the Purchase Order shall not conflict with the terms and conditions established by this Contract. In accepting a Purchase Order, the Contractor recognizes its responsibility for all tasks and deliverables contained therein, warrants that it has fully informed itself of all relevant factors affecting accomplishment of the tasks and deliverables and agrees to be fully accountable for the performance thereof.
Failure to Meet Timelines Failure by the Union to comply with the timelines will result in the automatic withdrawal of the grievance. Failure by the Employer to comply with the timelines will entitle the Union to move the grievance to the next step of the procedure.
Purchase Order Duration Purchase orders issued pursuant to this State Term Contract must be received by the Contractor no later than close of business on the last day of the Contract’s term to be considered timely. The Contractor is obliged to fill those orders in accordance with the Contract’s terms and conditions. Purchase orders received by the Contractor after close of business on the last day of the State Term Contract’s term shall be considered void. Purchase orders for a one-time performance of contractual services shall be valid through the performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the single delivery/performance, and shall survive the termination of the Contract. Contractors are required to accept purchase orders specifying delivery schedules exceeding the contracted schedule even when such extended delivery will occur after expiration of the State Term Contract. For example, if a state term contract calls for delivery 30 days after receipt of order (ARO), and an order specifies delivery will occur both in excess of 30 days ARO and after expiration of the state term contract, the Contractor will accept the order. However, if the Contractor expressly and in writing notifies the ordering office within ten (10) calendar days of receipt of the purchase order that Contractor will not accept the extended delivery terms beyond the expiration of the state term contract, then the purchase order will either be amended in writing by the ordering entity within ten (10) calendar days of receipt of the contractor’s notice to reflect the state term contract delivery schedule, or it shall be considered withdrawn. The duration of purchase orders for recurring deliveries of commodities or performance of services shall not exceed the expiration of the State Term Contract by more than twelve months. However, if an extended pricing plan offered in the State Term Contract is selected by the Customer, the Contract terms on pricing plans shall govern the maximum duration of purchase orders reflecting such pricing plans. Timely purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the recurring delivery/performance as provided herein, and shall survive the termination of the Contract. Ordering offices shall not renew a purchase order issued pursuant to a State Term Contract if the underlying contract expires prior to the effective date of the renewal.
TRUNK FORECASTING 57.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. Sprint 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 Sprint 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: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.