Request and Forecasts Sample Clauses

Request and Forecasts. Based on the R&D Plan developed in accordance with the R&D Procedures, OpNext will require assistance on a binding basis from Hitachi on specific R&D Projects for the upcoming twelve (12) month period. OpNext will also provide Hitachi with a non-binding forecast of R&D Projects that OpNext expects to request from Hitachi for the twelve (12) month period following such twelve (12) month period. Hitachi and OpNext will update such forecasts during the quarterly meetings described in Section 2(a) above.

Related to Request and Forecasts

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

  • Forecasts Any forecasts provided by DXC shall not constitute a commitment of any type by DXC.

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

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