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.
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.
PURCHASE ORDERS AND INVOICING All invoices shall at a minimum, include the items listed below and any additional information identified in the Authorized User RFQ and resulting Authorized User Agreement: Contract Number; Contractor/Reseller Name; NYS Vendor ID; Manufacturer Part Number (SKU); Product Name; Product Description; Quantity; NYS Net Price for each Product; Specific designation of special price(s) which may be better than the NYS Net Contract Price; and Invoice Total.
Purchase Orders Unless otherwise authorized in writing by the Commissioner, no Product is to be delivered or furnished by Contractor until transmittal of an official Purchase Order from the Authorized User. Unless terminated or cancelled pursuant to the authority vested in the Commissioner, Purchase Orders shall be effective and binding upon the Contractor when placed in the mail or electronically transmitted prior to the termination of the contract period, addressed to the Contractor at the address for receipt of orders set forth in the Contract or in the Contract Award Notification. All Purchase Orders issued pursuant to Contracts let by the Commissioner must bear the appropriate Contract number and, if necessary, required State approvals. As deemed necessary, the Authorized User may confirm pricing and other Product information with the Contractor prior to placement of the Purchase Order. The State reserves the right to require any other information from the Contractor which the State deems necessary in order to complete any Purchase Order placed under the Contract. Unless otherwise specified, all Purchase Orders against Centralized Contracts will be placed by Authorized Users directly with the Contractor and any discrepancy between the terms stated on the vendor’s order form, confirmation or acknowledgment, and the Contract terms shall be resolved in favor of the terms most favorable to the Authorized User. Should an Authorized User add written terms and conditions to the Purchase Order that conflict with the terms and conditions of the Contract, the Contractor has the option of rejecting the Purchase Order within five business days of its receipt but shall first attempt to negotiate the additional written terms and conditions in good faith with the Authorized User, or fulfill the Purchase Order. Notwithstanding the above, the Authorized User reserves the right to dispute any discrepancies arising from the presentation of additional terms and conditions with the Contractor. If, with respect to an Agency Specific Contract let by the OGS Commissioner, a Purchase Order is not received by the Contractor within two weeks after the issuance of a Contract Award Notification, it is the responsibility of the Contractor to request in writing that the appropriate Authorized User forward a Purchase Order. If, thereafter, a Purchase Order is not received within a reasonable period of time, the Contractor shall promptly notify in writing the appropriate purchasing officer in OGS. Failure to timely notify such officer may, in the discretion of the OGS Commissioner and without cost to the State, result in the cancellation of such requirement by the OGS Commissioner with a corresponding reduction in the Contract quantity and price.