We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Quantity Forecasts and Minimum Forecast Commitment Sample Clauses

Quantity Forecasts and Minimum Forecast Commitment 

Related to Quantity Forecasts and Minimum Forecast Commitment

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

  • Rolling Forecast (i) On or before the fifteenth (15th) calendar day of each month during the Term (as defined in Section 6.1 herein), Buyer shall provide Seller with an updated eighteen (18) month forecast of the Products to be manufactured and supplied (each a “Forecast”) for the eighteen (18) month period beginning on the first day of the following calendar month. The first two months of each Forecast will restate the balance of the Firm Order period of the prior Forecast, and the first three (3) months of the Forecast shall constitute the new Firm Order period for which Buyer is obligated to purchase and take delivery of the forecasted Product, and the supply required for the last month of such new Firm Order period shall not be more than one (1) full Standard Manufacturing Batch from the quantity specified for such month in the previous Forecast (or Initial Forecast, as the case may be). Except as provided in Section 2.2(a), Purchase Orders setting forth Buyer’s monthly Product requirements will be issued for the last month of each Firm Order period no later than the fifteenth calendar day of the first month of each Firm Order period, and such Purchase Order will be in agreement with the Firm Order period of the Forecast. If a Purchase Order for any month is not submitted by such deadline, Buyer shall be deemed to have submitted a Purchase Order for such month for the amount of Product set forth in Buyer’s Forecast for such month. (ii) The remainder of the Forecast shall set forth Buyer’s best estimate of its Product production and supply requirements for the remainder of the Forecast period. Each portion of such Forecast that is not deemed to be a Firm Order shall not be deemed to create a binding obligation on Buyer to purchase and take delivery of Products nor a binding obligation of Seller to deliver Products, except as otherwise provided in Section 2.2(f). (iii) Forecast and Purchase Orders shall be in full Standard Manufacturing Batches. If a Product has multiple SKUs, then the composite of the forecasted SKU must equate to the Standard Manufacturing Batch. One Purchase Order shall be issued for each full Standard Manufacturing Batch of Product and contain the required information set forth in Section 2.2(e) hereof.

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

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

  • Annual Forecasts As soon as available and in any event no later than 90 days after the end of each Fiscal Year, forecasts prepared by management of the Borrower, in form satisfactory to the Administrative Agent, of balance sheets, income statements and cash flow statements on an annual basis for the Fiscal Year following such Fiscal Year.

  • Contract Year A twelve (12) month period during the term of the Agreement commencing on the Effective Date and each anniversary thereof.

  • Minimum Commitment If for a certain Service a minimum commitment has been determined in the Agreement, the Customer guarantees to respect the minimum commitment described in the Agreement during the entire period of the Agreement. If the Customer does not respect this minimum commitment, the Customer shall pay the compensation mentioned in the Agreement. If no compensation has been mentioned in the Agreement, the Customer has to pay the applicable Charges for the respective Service, or the average of the applicable Charges if different Charges are applied for the respective Service, per missing number of its minimum commitment. Services that are timely cancelled by the Customer or Services for which the Customer has paid a cancellation fee , do not, even not partly, release the Customer from its obligation to respect the minimum commitment . Services cancelled as due to Force Majeure and Services cancelled by Lineas for other reasons than Force Majeure, will be considered as a Services ordered and paid for by the Customer. Services cancelled by the Customer or by Lineas because of holidays do not, even not partly, release the Customer from its obligation to respect its minimum commitment.

  • Time Commitment The Advisor shall, and shall cause its Affiliates and their respective employees, officers and agents to, devote to the Company such time as shall be reasonably necessary to conduct the business and affairs of the Company in an appropriate manner consistent with the terms of this Agreement. The Company acknowledges that the Advisor and its Affiliates and their respective employees, officers and agents may also engage in activities unrelated to the Company and may provide services to Persons other than the Company or any of its Affiliates.

  • Service Level Commitment IBM provides the following service level commitment (“SLA”) for the Cloud Service, after IBM makes the Cloud Service available to you.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.