Demand Forecasting Sample Clauses

POPULAR SAMPLE Copied 1 times
Demand Forecasting. If the Responsible PTO does not receive weekly Demand forecasts from Existing Rightholders, the Responsible PTO will not be required under the ISO Protocol of the ISO Tariff on Demand forecasting to submit weekly peak demand forecasts in relation to the Demand of Existing Rightholders. However, the Responsible PTO will submit such Demand forecasts as the Existing Contract allows the Responsible PTO to obtain.
Demand Forecasting. Probabilistic based - Uses historical and current booking patterns - Influenced by seasonal booking patterns - Influenced by special events and holidays as specified by the user - Forecasts remaining demand, no-shows and go-shows by class
Demand Forecasting. Tigard will be responsible for demand forecasting and planning based on population or other information provided by King City. King City will provide information as reasonably requested by Tigard to enable Tigard to complete this task.
Demand Forecasting. The City shall provide a Commitment of Volume, a Volume Forecast, and a Long Term Planning Forecast (collectively, the “Demand Forecast”) to the Company in order to facilitate demand management for the Thermal GAC Reactivation Facility in accordance with Section 5.5.
Demand Forecasting. Promptly following the Effective Date, NationsHealth will provide Aegis a written, rolling forecast of the Expected Number of Calls NationsHealth will send to Aegis in a subsequent three-Month period, with adjustments made every subsequent Month (a “Rolling Forecast”). The initial Rolling Forecast will be made as of the Agreement date. Aegis and NationsHealth agree to keep Rolling Forecasts confidential.

Related to Demand Forecasting

  • 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 ▇▇▇-▇▇▇-▇▇▇ and BR ▇▇▇-▇▇▇-▇▇▇; 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.

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

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

  • Forecasting Manager and Sprint PCS will work cooperatively to generate mutually acceptable forecasts of important business metrics including traffic volumes, handset sales, subscribers and Collected Revenues for the Sprint PCS Products and Services. The forecasts are for planning purposes only and do not constitute Manager's obligation to meet the quantities forecast.

  • Rolling Forecasts The Client shall provide Patheon with a written non-binding [ * ] forecast of the volume of each Product that the Client then anticipates will be required to be produced and delivered to the Client during each [ * ] of that [ * ] period. Such forecast will be updated by the Client [ * ] on or before the [ * ] day of each [ * ] on a rolling [ * ] basis. The most recent [ * ] forecast shall prevail.