Monthly Forecasting Sample Clauses

Monthly Forecasting. Ab De (T In conjunction with the status reporting, the Partner should also provide an updated forecast for the up- coming milestones, as well as the final delivery milestone.
AutoNDA by SimpleDocs
Monthly Forecasting. 14.4.1. Prospective financial statements, financial forecasts, and financial projections present, to the best of the responsible party’s knowledge expected financial position, operating and cash flow results. They are based on assumptions about conditions actually expected to occur and the course of action expected to be taken, given one or more hypothetical (i.e., “what if”) assumptions.

Related to Monthly Forecasting

  • LIS Forecasting 7.2.2.8.1 Both CLEC and Qwest shall work in good faith to define a mutually agreed upon forecast of LIS trunking.

  • TRUNK FORECASTING 58.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. Embarq 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 Embarq 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:

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

  • Monitoring and Adjusting Forecasts Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at ECI’s suggestion or request pursuant to the procedures identified in Section 14.2 of this Attachment. At the end of such ninety-(90) day period, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, Verizon determines that any trunks in the trunk group in excess of two (2) DS1s are not warranted by actual traffic volumes (considering engineering criteria for busy Centium Call Second (Hundred Call Second) and blocking percentages), then Verizon may hold ECI financially responsible for the excess facilities and disconnect such excess facilities.

  • Initial Trunk Forecast Requirements At least ninety (90) days before initiating interconnection in a LATA, Emergency shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • ANNUAL MASTER CONTRACT SALES REPORT Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by MS Excel.

  • Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.

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

  • Detailed Monthly Report Vendor shall electronically provide DIR with a detailed monthly report in the format required by DIR showing the dollar volume of any and all sales under the Contract for the previous calendar month period. Reports are due on the fifteenth (15th) calendar day of the month following the month of the sale. If the 15th calendar day falls on a weekend or state or federal holiday, the report shall be due on the next business day. The monthly report shall include, per transaction: the detailed sales for the period, Customer name, invoice date, invoice number, description, quantity, MSRP or List Price, unit price, extended price, Customer Purchase Order number, contact name, Customer’s complete billing address, the estimated administrative fee for the reporting period, subcontractor name, EPEAT designation (if applicable), configuration (if applicable), contract discount percentage, actual discount percentage, negotiated contract price (if fixed price is offered instead of discount off of MSRP), and other information as required by DIR. Each report must contain all information listed above per transaction or the report will be rejected and returned to the Vendor for correction in accordance with this section. Vendor shall report in a manner required by DIR which is subject to change dependent upon DIR’s business needs. Failure to do so may result in contract termination.

Time is Money Join Law Insider Premium to draft better contracts faster.