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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6/23/04<br />

Attachment 3<br />

Page 33<br />

8.9 Bell<strong>South</strong>’s Carrier Interconnection Switching Center (CISC) will notify <strong>TC</strong><br />

SYTEMS of any under-utilized Bell<strong>South</strong> Final Trunk Groups and the number of<br />

such trunk groups that Bell<strong>South</strong> wishes to disconnect. Bell<strong>South</strong> will provide<br />

supporting information either by email or facsimile to the designated <strong>TC</strong> SYTEMS<br />

interface. <strong>TC</strong> SYTEMS will provide concurrence with the disconnection in fourteen<br />

(14) business days or will provide specific information supporting why the trunks<br />

should not be disconnected. If <strong>TC</strong> SYTEMS fails to provide such information, <strong>TC</strong><br />

SYTEMS shall be considered to have concurred with Bell<strong>South</strong>’s request. Such<br />

supporting information should include expected traffic volumes (including traffic<br />

volumes generated due to Local Number Portability) and the timeframes within<br />

which <strong>TC</strong> SYTEMS expects to need such trunks. Bell<strong>South</strong>’s LISC Project<br />

Manager and Circuit Capacity Manager will discuss the information with <strong>TC</strong><br />

SYTEMS to determine if agreement can be reached on the number of Bell<strong>South</strong><br />

Final Trunk Groups to be removed. If no agreement can be reached, Bell<strong>South</strong> will<br />

issue disconnect orders to <strong>TC</strong> SYTEMS. The due date of these orders will be four<br />

weeks after <strong>TC</strong> SYTEMS was first notified in writing of the underutilization of the<br />

trunk groups.<br />

8.10 To the extent that any interconnection trunk group is utilized at a time-consistent<br />

busy hour of eighty percent (80%) or greater, the Parties may review the trunk<br />

groups and, if necessary, shall negotiate in good faith for the installation of<br />

augmented facilities.<br />

8.11 Each Party shall provide a specified point of contact for planning, forecasting and<br />

trunk servicing purposes.<br />

8.12 Both Parties will manage the capacity of their interconnection trunk groups.<br />

Bell<strong>South</strong> will issue an ASR to <strong>TC</strong> SYTEMS to order changes Bell<strong>South</strong> desires to<br />

the Bell<strong>South</strong> interconnection trunk groups based on Bell<strong>South</strong>’s capacity<br />

assessment. <strong>TC</strong> SYTEMS will issue an ASR to Bell<strong>South</strong> to order changes <strong>TC</strong><br />

SYTEMS desires to the <strong>TC</strong> SYTEMS interconnection trunk groups based on <strong>TC</strong><br />

SYTEMS’s capacity assessment.<br />

8.13 Either Party may issue a Trunk Group Service Request (“TGSR”) to the other Party<br />

to order changes it desires to the interconnection trunk groups based on its capacity<br />

assessment. The Party receiving the TGSR will, within ten (10) business days,<br />

respond with an ASR or an explanation of why it believes an ASR is inappropriate.<br />

8.14 The Party submitting an ASR will provide complete and accurate tie down inventory<br />

assignments in typical industry bay, panel and jack format, or in such other format as<br />

the Parties agree, on each order by use of a Design Layout Record. Additional tie<br />

down information, such as span information, may be required when applicable.<br />

8.15 The Parties will prepare ASRs pursuant to the industry standard guidelines of the<br />

OBF. When submitting an ASR, Bell<strong>South</strong> will identify <strong>TC</strong> SYTEMS’s end office<br />

in the SEC LOC field of the ASR form.<br />

CCCS 209 of 433

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

Saved successfully!

Ooh no, something went wrong!