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 000-000-000 and BR 000-000-000;
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.
TRUNK FORECASTING. 4.4.1 The Parties will develop joint forecasting of trunk groups in accordance with Article III, Section 12. Intercompany forecast information must be provided by the Parties to each other twice a year. The semi-annual forecasts will include:
4.4.1.1 yearly forecasted trunk quantities for no less than a two-year period (current year, plus one year); and
4.4.1.2 the use of (i) CLCI -MSG codes, which are described in Telcordia Technologies document BR 000-000-000; (ii) circuit identifier codes as described in BR 000-000-000; and (iii) Trunk Group Serial Number (TGSN) as described in BR 000-000-000.
4.4.2 Description of major network projects that affect the other Party will be provided with the semi-annual forecasts provided pursuant to Section 4.4.1. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by either Party that are reflected by a significant increase or decrease in trunking demand for the following forecasting period.
4.4.3 Parties will meet to review and reconcile their forecasts if their respective forecasts differ significantly from one another.
TRUNK FORECASTING. The Parties shall work towards the development of joint forecasting responsibilities 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. The Parties shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Intercompany forecast information must be provided by the Parties to each other 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. 54.1.1. The Parties shall work towards the development of joint forecasting responsibilities 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. The Parties shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Intercompany forecast information must be provided by the Parties to each other 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:
54.1.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);
54.1.1.2. The use of Common Language Location Identifier (CLLI- MSG), which are described in Telcordia documents BR 000- 000-000 and BR 000-000-000;
54.1.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 either party that are reflected by a significant increase or decrease in trunking demand for the following forecasting period.
54.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly.
54.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes.
54.1.4. Trunking can be established to Tandems or end offices or a combination of both via either one-way or two-way trunks. Trunking will be at the XX- 0, XX-0, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint.
54.1.5. The parties agree to abide by the following if a forecast cannot be agreed to: local interconnection trunk groups will be provisioned to the higher forecast. A blocking standard of one percent (1%) during the average busy hour shall be maintained. Should the Parties not agree upon the forecast, and the Parties engineer facilities at the higher forecast, the P...
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:
58.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);
58.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000;
58.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.
58.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.
58.2. CLEC shall provide an updated trunk forecast when ordering or requesting additional trunks from Embarq anytime after the initial trunk implementation.
58.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes.
58.4. Trunking can be established to Tandems or end offices or a combination of both via either one-way or two-way trunks. Trunking will be at the DS0, DS1, DS3/OC3 level, or higher, as agreed upon by CLEC and Embarq.
58.5. The parties agree to abide by the following if a forecast cannot be agreed to: local interconnection trunk groups will be provisioned to the higher forecast. A blocking standard of one percent (1%) during the average busy hour shall be maintained. Should the Parties not agree upon the forecast, and the Parties ...
TRUNK FORECASTING. 2.11.1 The Parties will work towards the development of joint forecasting responsibilities for traffic utilization over interconnection trunk groups covered in this Agreement. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment becomes available. Each Party will make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Intercompany forecast information must be provided by the Parties to each other upon reasonable request. Frontier preference is a semi-annual forecast covering the following twenty- four (24) month period.
TRUNK FORECASTING. 4.1 WSP agrees to provide Trunk forecasts to assist in the planning and provisioning of Interconnection Trunk Groups and Facilities.
4.2 WSP will provide a Trunk forecast prior to initial implementation, and subsequent forecasts will be provided to AT&T-13STATE upon request, as often as twice a year. The forecast shall include yearly forecasted Trunk quantities (which include measurements that reflect actual Tandem local Interconnection and InterLATA Trunks, end office local Interconnection Trunks, and Tandem subtending local Interconnection end office equivalent Trunk requirements) for a minimum of three (current plus 2 future) years.
4.3 Revised Trunk forecasts will be provided by WSP whenever there are significant increases or decreases in trunking demand than reflected in previously submitted forecasts.
4.4 Trunk forecasts shall include yearly forecasted Trunk quantities by Tandem and subtending end offices. Identification of each Trunk will be by the “from” and “to” Common Language Location Identifiers (CLLI), as described in Telcordia Technologies documents BR 000-000-000 and BR 000-000-000.
4.5 The Parties agree to meet to review each submitted forecast.
TRUNK FORECASTING. 6.1 To permit orderly growth and network management, Carrier shall forecast the volume of traffic of each Trunk associated with each POI. Xxxxxxx forecast information must be provided to Telco upon request, as often as twice a year. When extraordinary changes are anticipated, Carrier shall provide additional timely forecasts to account for such changes. The forecasts shall include:
6.1.1 Yearly forecasted Trunk quantities (which include measurements that reflect actual Tandem and End Office Switch Paging Authorized Services Interconnection and Trunks and Tandem-subtending Paging Authorized Services Interconnection End Office Switch equivalent Trunk requirements) for two (2) years (current year and one (1) additional year) by quarter;
6.1.2 Identification of each Trunk by the from and to Common Language Location Identifiers (“CLLI”), which are described in Telcordia Technologies, Inc. documents BR 000-000-000 and BR 795-400- 100;
6.1.3 A description of major system projects. Major system projects include Trunking or system rearrangements, shifts in anticipated traffic patterns, or other activities by Carrier that are reflected by a significant increase or decrease in Trunk demand for the following forecasting period.
TRUNK FORECASTING. 6.1 To permit orderly growth and network management, Carrier shall forecast the volume of traffic of each Trunk associated with each POI. Xxxxxxx forecast information must be provided to Telco upon request, as often as twice a year. When extraordinary changes are anticipated, Carrier shall provide additional timely forecasts to account for such changes. The forecasts shall include:
6.1.1 Yearly forecasted Trunk quantities (which include measurements that reflect actual Tandem Switch Authorized Services Interconnection Trunks and Tandem-subtending Authorized Services Interconnection End Office Switch equivalent Trunk requirements) for two (2) years (current year and one (1) additional year) by quarter;
6.1.2 Identification of each Trunk by the from and to Common Language Location Identifiers (“CLLI”), which are described in Bellcore documents BR 000-000-000 and BR 000-000-000;
6.1.3 A description of major system projects. Major system projects include Trunking or system rearrangements, shifts in anticipated traffic patterns, or other activities by Carrier that are reflected by a significant increase or decrease in Trunk demand for the following forecasting period.
TRUNK FORECASTING. 4.4.1 The Parties will develop joint forecasting of trunk groups in accordance with Article III, Section 12. Intercompany forecast information must be provided by the Parties to each other once a year. The annual forecasts will include:
4.4.1.1 Yearly forecasted trunk quantities for no less than a two-year period (current year, plus one year). Description of major network projects that affect the other Party will be provided with the annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by either Party that are reflected by a significant increase or decrease in trunking demand for the following forecasting period.
4.4.1.2 Parties will meet to review and reconcile their forecasts if their respective forecasts differ significantly from one another.
