Demand and Forecast Management Sample Clauses

Demand and Forecast Management. Support common practices for ordering assets, tracking orders and assets, and (for hardware/equipment) tagging (to include barcoding) the assets. Assist the Government in capacity planning, providing analysis of current systems equipment and/or software licenses are optimal to support additional influxes of capacity.
AutoNDA by SimpleDocs

Related to Demand and Forecast Management

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

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

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

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Midterm Review The Recipient shall:

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Program Narrative All restricted xxxxxx courses which are taught for the purpose of qualifying an individual for restricted xxxxxx license to practice barbering shall consist of a minimum of 1200 hours of training to prepare each restricted xxxxxx to service their communities.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!