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 36<br />

12.2.1.4 Isolation of one or more PSAP(s), for 30 or more minutes, if the isolated PSAPs<br />

collectively serve 30,000 or more access lines, based on the carrier's database of<br />

lines served by each PSAP; or<br />

12.2.1.5 Isolation of an end office switch or host/remote cluster, for 30 minutes or more, if<br />

the switches collectively serve, 30,000 or more access lines; or<br />

12.2.1.6 Conditions described in Bell<strong>South</strong>’s Operational Understanding Guide.<br />

12.2.2 In accordance with Bell<strong>South</strong>’s Operational Understanding Guide, <strong>TC</strong> SYTEMS<br />

will subscribe to the email list server in order to receive email notifications on a<br />

24X7 basis of Bell<strong>South</strong> service disruptions that meet the criteria for FCC reportable<br />

events. Bell<strong>South</strong> will use the same thresholds, processes and schedule for notifying<br />

<strong>TC</strong> SYTEMS as it does for internal purposes. The email notification shall consist of<br />

the same information that Bell<strong>South</strong> provides to the FCC in reporting on an<br />

unplanned network outage. Bell<strong>South</strong> will include all information available to<br />

Bell<strong>South</strong> at the time such report is submitted, including but not limited to: (a)<br />

central office or offices affected; (b) OSS application or CLLI affected; (c)<br />

geographic area(s) affected; (d) description of trouble; and (e) date and time of<br />

trouble.<br />

12.2.3 <strong>TC</strong> SYTEMS may submit a request to the Bell<strong>South</strong> CISC for a subsequent email<br />

report, which Bell<strong>South</strong> will provide to <strong>TC</strong> SYTEMS as soon as Bell<strong>South</strong> has such<br />

information following such outage and no later than 30 days following the unplanned<br />

network outage.<br />

12.2.4 As needed, <strong>TC</strong> SYTEMS may request that the Parties meet to share contact<br />

information and review Bell<strong>South</strong>’s outage restoral processes and notification<br />

processes.<br />

12.3 Notice of Changes Section 251(c)(5)<br />

12.3.1 If Bell<strong>South</strong> makes a change in the information necessary for the transmission and<br />

routing of services using Bell<strong>South</strong>’s network, or any other change in its network<br />

which it believes will materially affect the interoperability of its network with <strong>TC</strong><br />

SYTEMS’s network, Bell<strong>South</strong> shall provide at least ninety (90) days advance<br />

written notice of such change to <strong>TC</strong> SYTEMS, and shall use all reasonable efforts to<br />

provide at least one hundred eighty (180) days notice where practicable, provided,<br />

however that if a longer period of notice is required by the FCC’s or Commission’s<br />

rule, including, e.g., the Network Disclosure rules set forth in the FCC Regulations.<br />

13 Joint Network Implementation and Grooming Process. <strong>TC</strong> SYTEMS and<br />

Bell<strong>South</strong> shall jointly develop an implementation and grooming process which shall<br />

define and detail, inter alia,<br />

13.1 standards to ensure that Interconnection trunk groups experience a grade of service,<br />

availability and quality which is comparable to that achieved on interoffice trunks<br />

CCCS 212 of 433

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

Saved successfully!

Ooh no, something went wrong!