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

Meet fiber optic terminals are available. The rate charged by one Party to the other Party<br />

for such spare capacity shall be no more than the rates set forth in this Attachment for<br />

Dedicated Transport.<br />

2.3.4 Bell<strong>South</strong> shall, wholly at its own expense, procure, install and maintain the agreed upon<br />

SONET equipment in the Bell<strong>South</strong> Serving Wire Center ("BSWC").<br />

2.3.5 <strong>TC</strong> SYTEMS shall, wholly at its own expense, procure, install and maintain the agreed upon<br />

SONET equipment in the <strong>TC</strong> SYTEMS Serving Wire Center ("ASWC").<br />

2.3.6 The parties shall mutually agree upon a POI outside of the BSWC as a Fiber Meet point and<br />

shall make all necessary preparations to receive and to allow and enable delivery of fiber<br />

optic facilities into the POI with sufficient spare length to reach the POI. A Common<br />

Language Location Identification ("CLLI") code will be established for each POI. The code<br />

established must be a building type code. All orders shall originate from the POI (i.e., POI<br />

to <strong>TC</strong> SYTEMS, POI to Bell<strong>South</strong>).<br />

2.3.7 The Parties shall deliver and maintain their own strands wholly at their own expense. Upon<br />

verbal request by either Party, the other Party shall allow access to the Fiber Meet entry<br />

point for maintenance purposes as promptly as possible.<br />

2.3.8 The Parties shall jointly coordinate and undertake maintenance of the SONET transmission<br />

system. Each Party shall be responsible for maintaining the components of their own<br />

SONET transmission system.<br />

2.3.9 Each Party will be responsible for (i) providing its own transport facilities to the Fiber Meet,<br />

and (ii) the cost to build-out its facilities to such Fiber Meet. Each Party is responsible for<br />

transporting its originating traffic to the appropriate POI . The originating Party shall<br />

provide or cause to be provided any transport needed to deliver its originating traffic to any<br />

such POI that is not within the same serving wire center as the Mid-Span Fiber Meet<br />

terminal equipment. The Parties will utilize one of the interconnection methods set forth in<br />

this Attachment, as applicable, for any such additional transport.<br />

2.3.10 Neither Party shall charge the other for its portion of the Fiber Meet facility between the<br />

ASWC and the BSWC used exclusively for the other Party’s local traffic (i.e., the Local<br />

Channel). The Parties do not intend to utilize this arrangement for transit traffic.<br />

2.3.11 In establishing a Mid-Span Fiber Meet arrangement and associated interconnection trunking,<br />

or an augment to such an arrangement the Parties agree to work together on routing,<br />

determining the appropriate facility system size (e.g., OC-n) based on the most recent traffic<br />

forecasts, equipment selection, ordering, provisioning, maintenance, repair, testing,<br />

augment, and compensation procedures and arrangements, reasonable distance limitations,<br />

and on any other arrangements necessary to implement the Mid-Span Fiber Meet<br />

arrangement and associated interconnection trunking (“Implementation Provisions”). The<br />

Implementation Provisions shall be agreed to by the Parties in writing at the initial<br />

implementation meeting. If, despite the Parties good faith efforts, the Parties cannot agree<br />

on material terms relating to the Implementation Provisions, the dispute resolution<br />

CCCS 189 of 433

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

Saved successfully!

Ooh no, something went wrong!