09.08.2013 Views

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6/23/04<br />

Attachment 3<br />

Page 32<br />

8.3 The use of Common Language Location Identifier, described in Bellcore documents<br />

BR 795-100-100 and BR 795-400-100 and;<br />

8.4 A description of major network projects anticipated for the following six months.<br />

Major network projects include trunking or network rearrangements, shifts in<br />

anticipated traffic patterns, or other activities that are reflected by a significant<br />

increase or decrease in trunking demand for the following forecasting period.<br />

8.5 In order for Bell<strong>South</strong> to provide as accurate reciprocal trunking forecasts as<br />

possible to <strong>TC</strong> SYTEMS, <strong>TC</strong> SYTEMS must timely inform Bell<strong>South</strong> of any known<br />

or anticipated events that may affect Bell<strong>South</strong> reciprocal trunking requirements. If<br />

<strong>TC</strong> SYTEMS refuses to provide such information, Bell<strong>South</strong> shall provide<br />

reciprocal trunking forecasts based only on existing trunk group growth and<br />

Bell<strong>South</strong>’s annual estimated percentage of Bell<strong>South</strong> subscriber line growth.<br />

8.6 The Parties agree that trunk forecasts are non-binding and are based on the<br />

information available to each respective Party at the time the forecasts are prepared.<br />

The submitting and development of interconnection trunk forecasts shall not replace<br />

the ordering process for local interconnection trunks. Unforecasted trunk demands,<br />

if any, by one Party will be accommodated by the other Party as soon as practicable<br />

based on facility availability. Each Party shall exercise its best efforts to provide the<br />

quantity of interconnection trunks mutually forecasted. However, the provision of<br />

the forecasted quantity of interconnection trunks is subject to trunk terminations and<br />

facility capacity existing at the time the trunk order is submitted. For a non binding<br />

forecast, agreement between the two Parties on the trunk quantities and the<br />

timeframe of those trunks does not imply any liability to perform if the trunks are not<br />

available for use at the required time.<br />

8.7 With respect to two way trunks, if differences in semi-annual forecasts provided by<br />

either Party vary by more than 96 DS0 two-way trunks for each Local<br />

Interconnection Trunk Group, then the Parties shall meet to reconcile the forecast to<br />

within 96 DS0 trunks.<br />

8.8 For Bell<strong>South</strong>-to-<strong>TC</strong> SYTEMS one-way trunk groups (“Bell<strong>South</strong> Trunk Groups)<br />

that are the trunk groups that do not carry overflow traffic (“Final Trunk Groups”),<br />

Bell<strong>South</strong> and <strong>TC</strong> SYTEMS shall monitor traffic on each interconnection Bell<strong>South</strong><br />

Final Trunk Group that is ordered and installed. The Parties agree that the Bell<strong>South</strong><br />

Final Trunk Groups will be utilized at 60 percent (60%) of the time consistent busy<br />

hour utilization level within 90 days of installation. The Parties agree that the<br />

Bell<strong>South</strong> Final Trunk Groups will be utilized at eighty percent (80%) of the time<br />

consistent busy hour utilization level within 180 days of installation. Any Bell<strong>South</strong><br />

Final Trunk Group not meeting the minimum thresholds set forth in this Section are<br />

defined as “Under-utilized” trunks. Bell<strong>South</strong> may disconnect any Under-utilized<br />

Bell<strong>South</strong> Final Trunk Groups pursuant to the provisions of Section 4.1 of this<br />

Attachment 3.<br />

CCCS 208 of 433

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!