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:
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.
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.
Use of Trunk Forecasts Trunk forecasts provided pursuant to this Agreement must be prepared in good faith but are not otherwise binding on CBB or Verizon.
DATA FOR CALCULATIONS The initial calculations for any payments owing under this Agreement shall be based upon the valuations placed upon the Qualified Property by the Appraisal District in its annual certified appraisal roll submitted to the District pursuant to § 26.01 of the TEXAS TAX CODE in or about July of each year of this Agreement. The certified appraisal roll data shall form the basis from which any and all amounts due under this Agreement are calculated, and the data utilized by the Consultant will be adjusted as necessary to reflect any subsequent adjustments by the Appraisal District to the District’s appraisal roll. Any estimates used by the Consultant to make calculations as required by this Agreement shall be based on the best and most current information available. The Consultant shall from time to time adjust the data utilized to reflect actual amounts, subsequent adjustments by the Appraisal District to the District’s certified appraisal roll, or any other relevant changes to material items such as student counts or tax collections.
Forecasts Any forecasts provided by DXC shall not constitute a commitment of any type by DXC.
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.
Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.
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.
