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.

Version 3Q03: 11/12/2003<br />

BST 09/29/05 AL<br />

Attachment 2<br />

Page 40<br />

SYSTEMS will submit any Local Number Portability (“LNP”) orders associated with<br />

changes in service providers for its end users pursuant to Attachment 5 of this<br />

Agreement.<br />

2.8.3.3.9 Once <strong>TC</strong> SYSTEMS has accessed a UNTW pair to serve its end user, <strong>TC</strong> SYSTEMS<br />

will submit a Local Service Request (“LSR”) to Bell<strong>South</strong> within five (5) business<br />

days of UNTW pair activation to report activation of that UNTW pair using the<br />

information provided to <strong>TC</strong> SYSTEMS on the FOC. <strong>TC</strong> SYSTEMS may submit a<br />

single LSR to activate multiple UNTW pairs on the same IAT. If <strong>TC</strong> SYSTEMS<br />

deactivates a UNTW pair, <strong>TC</strong> SYSTEMS shall also submit an LSR within five (5)<br />

business days of UNTW pair deactivation to report such deactivation. LSRs shall be<br />

submitted to Bell<strong>South</strong> manually until such time as an electronic interface is deployed.<br />

2.8.3.3.10 <strong>TC</strong> SYSTEMS must test and isolate any repair problem on existing UNTW pairs. <strong>TC</strong><br />

SYSTEMS will be responsible for reporting repair problems on existing UNTW pairs<br />

to the appropriate Bell<strong>South</strong> department. Response to trouble and repair reports will<br />

be on a nondiscriminatory basis unless specific performance standards have been<br />

established for Bell<strong>South</strong>. In that case, those performance standards will apply to<br />

Bell<strong>South</strong> for the activities described in this Section. If Bell<strong>South</strong> dispatches a<br />

technician on a UNTW trouble reported by <strong>TC</strong> SYSTEMS and no trouble is found on<br />

the Bell<strong>South</strong> facility, Bell<strong>South</strong> will charge <strong>TC</strong> SYSTEMS for time spent on the<br />

dispatch and UNTW testing.<br />

2.8.3.3.11 <strong>TC</strong> SYSTEMS will pay a non-recurring charge per pair for UNTW pair activation, a<br />

monthly recurring charge per pair for use of a UNTW MDU pair and a non-recurring<br />

charge per pair for each UNTW garden terminal MDU pair disconnected when <strong>TC</strong><br />

SYSTEMS is no longer providing service to the end user. These charges are set forth<br />

in Exhibit A.<br />

2.8.3.3.12 If <strong>TC</strong> SYSTEMS or a third party service provider (other CLEC) has not activated at<br />

least one (1) pair on each IAT installed, as requested on the SI within six (6) months<br />

of completion of IAT installation, Bell<strong>South</strong> will issue an order for activation/billing of<br />

one (1) pair at an IAT, subject to the terrain, work permits, and equipment delivery.<br />

2.8.3.3.13 If Bell<strong>South</strong> determines that <strong>TC</strong> SYSTEMS is using a UNTW pair without reporting<br />

activation to Bell<strong>South</strong>, the following charges shall apply in addition to any fines<br />

which may be established by the Commission and any other remedies at law or in<br />

equity available to Bell<strong>South</strong>.<br />

2.8.3.3.14 If <strong>TC</strong> SYSTEMS activated a UNTW pair on which Bell<strong>South</strong> was not previously<br />

providing service, <strong>TC</strong> SYSTEMS will be billed for the use of that UNTW pair back to<br />

the date the end user began receiving service using that UNTW pair. Upon reasonable<br />

request, <strong>TC</strong> SYSTEMS will provide copies of billing records to substantiate such date.<br />

CCCS 121 of 433

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

Saved successfully!

Ooh no, something went wrong!