09.08.2013 Views

Bright House Networks Information Services ... - AT&T Clec Online

Bright House Networks Information Services ... - AT&T Clec Online

Bright House Networks Information Services ... - 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.

Attachment 4-Central Office<br />

Page 4<br />

includes from two (2) to five (5) Premises within the same state. The response time<br />

for requests of more than five (5) Premises shall be negotiated between the Parties. If<br />

AT&T cannot meet the ten calendar day response time, AT&T shall notify BHN and<br />

inform BHN of the time frame under which it can respond.<br />

3. Collocation Options<br />

3.1 Cageless. AT&T shall allow BHN to collocate BHN‘s equipment and facilities<br />

without requiring the construction of a cage or similar structure. AT&T shall allow<br />

BHN to have direct access to BHN‘s equipment and facilities. AT&T shall make<br />

cageless collocation available in single bay increments. Except where BHN‘s<br />

equipment requires special technical considerations (e.g., special cable racking,<br />

isolated ground plane, etc.), AT&T shall assign cageless Collocation Space in<br />

conventional equipment rack lineups where feasible. For equipment requiring special<br />

technical considerations, BHN must provide the equipment layout, including spatial<br />

dimensions for such equipment pursuant to generic requirements contained in<br />

Telcordia GR-63-Core, and shall be responsible for compliance with all special<br />

technical requirements associated with such equipment.<br />

3.2 Caged. At BHN‘s expense, BHN may arrange with a Supplier certified by AT&T<br />

(“Certified Supplier”) to construct a collocation arrangement enclosure in accordance<br />

with AT&T’s guidelines and specifications prior to starting equipment installation.<br />

AT&T will provide guidelines and specifications upon request. Where local building<br />

codes require enclosure specifications more stringent than AT&T’s standard enclosure<br />

specification, BHN and BHN‘s Certified Supplier must comply with the more stringent<br />

local building code requirements. BHN‘s Certified Supplier shall be responsible for<br />

filing and receiving any and all necessary permits and/or licenses for such construction.<br />

AT&T shall cooperate with BHN and provide, at BHN‘s expense, the documentation,<br />

including existing building architectural drawings, enclosure drawings, and<br />

specifications required and necessary for BHN to obtain the zoning, permits and/or<br />

other licenses. BHN‘s Certified Supplier shall bill BHN directly for all work performed<br />

for BHN pursuant to this Attachment and AT&T shall have no liability for nor<br />

responsibility to pay such charges imposed by the BHN‘s Certified Supplier. BHN<br />

must provide the local AT&T building contact with two Access Keys used to enter the<br />

locked enclosure. Except in case of emergency, AT&T will not access BHN’s locked<br />

enclosure prior to notifying BHN. Upon request, AT&T shall construct the enclosure<br />

for BHN.<br />

3.2.1 AT&T may elect to review BHN’s plans and specifications prior to allowing<br />

construction to start to ensure compliance with AT&T’s guidelines and specifications.<br />

Notification to BHN indicating AT&T’s desire to execute this review will be provided<br />

in AT&T’s response to the Initial Application, if BHN has indicated their desire to<br />

construct their own enclosure. If BHN’s Initial Application does not indicate their<br />

desire to construct their own enclosure, but their subsequent firm order does indicate<br />

their desire to construct their own enclosure, then notification to review will be given<br />

within ten (10) calendar days after the Firm Order date. . AT&T shall complete its<br />

Version 4Q01: 12/01/01<br />

CCCS 134 of 369

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

Saved successfully!

Ooh no, something went wrong!