Common use of TRUNK FORECASTING Clause in Contracts

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 Parties agree to abide by the following: 54.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.162.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.162.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.262.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.362.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.262.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.362.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.462.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.562.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 Parties agree to abide by the following: 54.1.5.162.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.262.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.362.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.140.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.140.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.240.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.340.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.240.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.340.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.440.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.540.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 Parties agree to abide by the following: 54.1.5.140.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.240.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.340.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.111.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 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.111.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.211.1.1.2. The use of Common Language Location Identifier (CLLI- CLLI-MSG), which are described in Telcordia documents BR 000- 000-000-000 and BR 000-000-000; 54.1.1.311.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.211.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.311.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.411.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.511.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 Parties agree to abide by the following: 54.1.5.111.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.211.1.5.2. The calculation of the twenty percent (20%) over-over- forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.311.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.145.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 on a nondiscriminatory basis as facilities and/or 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.145.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.245.1.1.2. The use of Common Language Location Identifier (CLLI- MSG), which are described in Telcordia documents BR 000- 000795-000 100- 100 and BR 000-000-000; 54.1.1.345.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.245.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.345.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 Parties agree to abide by the following: 54.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

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- DS- 0, XX-0DS-1, 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 Parties agree to abide by the following: 54.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.153.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 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.153.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.253.1.2. The use of Common Language Location Identifier (CLLI- CLLI-MSG), which are described in Telcordia documents BR 000- 000-000-000 and BR 000795-000-000400- 100; 54.1.1.353.1.2.1. 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.253.1.3. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.353.1.4. In addition, CLEC shall provide a trunk forecast when establishing a Point of Interconnection. 53.1.5. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.453.1.6. 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- 0XX-0, XX-0, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.553.1.7. 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 Parties agree to abide by the following: 54.1.5.153.1.7.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.253.1.7.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.353.1.7.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.161.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 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.161.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.261.1.1.2. The use of Common Language Location Identifier (CLLI- CLLI-MSG), which are described in Telcordia documents BR 000- 000-000-000 and BR 000-000-000; 54.1.1.361.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.261.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.361.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.461.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- 0XX-0, XX-0, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.561.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 Parties agree to abide by the following: 54.1.5.161.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.261.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.361.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

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 Parties agree to abide by the following: 54.1.5.1. In the event that one Party over-forecasts its trunking requirements by more than twenty percent (20%) or morethree DS1s (whichever is greater), and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.155.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.155.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.255.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.355.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.255.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.355.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.455.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.555.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 Parties agree to abide by the following: 54.1.5.155.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.255.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.355.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.153.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 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.153.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.253.1.2. The use of Common Language Location Identifier (CLLI- MSG), which are described in Telcordia documents BR 000- 000795-000 100- 100 and BR 000-000-000; 54.1.1.353.1.2.1. 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.253.1.3. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.353.1.4. In addition, CLEC shall provide a trunk forecast when establishing a Point of Interconnection. 53.1.5. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.453.1.6. 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- 0XX-0, XX-0, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.553.1.7. 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 Parties agree to abide by the following: 54.1.5.153.1.7.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.253.1.7.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.353.1.7.3. Expenses will only be recouped for non-non- recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.160.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 on a nondiscriminatory basis as facilities and/or 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.160.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);for 54.1.1.260.1.1.2. The use of Common Language Location Identifier (CLLI- MSG), which are described in Telcordia documents BR 000- 000795-000 100- 100 and BR 000-000-000; 54.1.1.360.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.260.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.360.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.460.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- 0XX-0, XX-0, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.560.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 forecastof the two forecasts notwithstanding the dispute , the Parties agree to abide by the following: 54.1.5.160.1.5.1. In Subject to Section 61.1.5.4, in the event that one Party over-over- forecasts its trunking requirements by twenty percent (20%) or moremore (measured twelve (12) months after the trunks have been provisioned), and the other Party acts upon this forecast to its detriment, the other Party may seek to recoup any actual and reasonable expense it incurscan prove it has incurred as a direct result of that over-forecast.Sprint will provide trunking to Level3 at the time intervals specified in the JOP. 54.1.5.260.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprintvolume, as measured twelve (12) months after the trunks have been provisioned. 54.1.5.360.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party. 60.1.5.4. A Party shall only be permitted to recover its costs pursuant to this Section 59.1.5 if it demonstrates that cost recovery is warranted. If the Parties disagree the cost recovery is warranted, the dispute will be resolved pursuant to section 23, dispute resolution. Furthermore, a party seeking cost recovery pursuant to this section must first demonstrate it has delivered trunks in a timely manner.

TRUNK FORECASTING. 54.1.140.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.140.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.240.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.340.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.240.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.340.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.440.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- DS- 0, XX-0DS-1, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.540.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 Parties agree to abide by the following: 54.1.5.140.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.240.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.340.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.153.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 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.153.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.253.1.2. The use of Common Language Location Identifier (CLLI- MSG), which are described in Telcordia documents BR 000- 000795-000 100- 100 and BR 000-000-000; 54.1.1.353.1.2.1. 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.253.1.3. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.353.1.4. In addition, CLEC shall provide a trunk forecast when establishing a Point of Interconnection. 53.1.5. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.453.1.6. 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- 0DS-0, XX-0DS-1, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. 54.1.553.1.7. 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 Parties agree to abide by the following: 54.1.5.153.1.7.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.253.1.7.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.353.1.7.3. Expenses will only be recouped for non-non- recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.

TRUNK FORECASTING. 54.1.142.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.142.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.242.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.342.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.242.1.2. Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. 54.1.342.1.3. Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. 54.1.442.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.542.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 Parties agree to abide by the following: 54.1.5.142.1.5.1. In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. 54.1.5.242.1.5.2. The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. 54.1.5.342.1.5.3. Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party.