Common use of Interconnection in Additional LATAs Clause in Contracts

Interconnection in Additional LATAs. 4.4.1 If Covad determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad has designated in the new LATA; (ii) Covad's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad has identified as its initial Routing Point(s) in the LATA as the Covad-IP(s) in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a Tandem Office within the LATA nearest to the Covad-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of Covad's notice, BA and Covad shall confirm the BA-IP, the Covad-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad CLEC determines to offer Telephone Exchange Services Service within SBC-AMERITECH’s service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad CLEC shall provide written notice to BA SBC-AMERITECH of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad CLEC Switch Center POI(s) CLEC has designated in the new LATA; , (ii) CovadCLEC's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadCLEC's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad CLEC Switch Center that CLEC has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC-AMERITECH Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BASBC-IP(s) AMERITECH Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber- Meet is one hundred and thirty-five (135) calendar days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-hundred and thirty-five (45135) calendar days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which CLEC delivered notice to SBC-AMERITECH pursuant to Section 3.10.1. Within ten thirty (1030) business calendar days of BA's SBC-AMERITECH’s receipt of Covad's CLEC’s notice, BA SBC-AMERITECH and Covad CLEC shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC-AMERITECH will make its best effort to Schedule 3.0meet CLEC’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad CLEC determines to offer Telephone Exchange Services Service within SBC ILLINOIS' service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad CLEC shall provide written notice to BA SBC ILLINOIS of the its need to establish Interconnection in POI(s) within such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include for each LATA a Network Information Sheet-NIS (See CLEC to SBC NETWORK INFORMATION SHEET Attachment # 1) and a Forecast. For a joint planning meeting to be convened, the NIS will be filled out with the following minimum information: (i) the initial Routing Point Covad has designated in the new LATA; Roman Numeral I, Items 1, 2, and 5 completely filled out, and (ii) Covad's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadCLEC's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad CLEC Switch Center CLEC has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA the SBC ILLINOIS Tandem(s) Office Wire Center(s) that houses a Tandem Office Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) SBC ILLINOIS Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber-Meet is one hundred and fifty (150) calendar days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than forty-five of: (451) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, (2) the date that is a maximum of one- hundred and fifty (150) calendar days after the date on which CLEC delivered notice to SBC ILLINOIS pursuant to Section 3.10.1. The Parties acknowledge that circumstances may affect their ability to activate the interconnection within the 150 day period. Either Party may request that the 150 day period be expanded by giving notice to the other Party of a circumstance requiring expansion. Upon receipt by BA of all complete such notice, the Parties agree to meet and accurate trunk orders and routing informationagree upon a modified activation due date. Within ten (10) business days of BA's SBC ILLINOIS’ receipt of Covad's CLEC’s notice, BA SBC ILLINOIS and Covad CLEC shall confirm the BA-IPSBC ILLINOIS Interconnection Wire Center, the Covad-IP CLEC Interconnection Wire Center and the Interconnection Activation Date for the new LATA by attaching an addendum mutually agreeing to Schedule 3.0a Trunk Plan.

Interconnection in Additional LATAs. 4.4.1 If Covad Focal determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad Focal shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad Focal has designated in the new LATA; (ii) CovadFocal's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadFocal's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center Focal has identified as its initial Routing Point(s) Point in the LATA as the CovadFocal-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadFocal-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadFocal-IP, the Covad-Focal- IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadFocal; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadFocal's notice, BA and Covad Focal shall confirm the BA-IP, the CovadFocal-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad AT&T determines to offer Telephone Exchange Services Service within SBC-AMERITECH 's service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad AT&T shall provide written notice to BA SBC-AMERITECH of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad AT&T Switch Center POI(s) AT&T has designated in the new LATA; , (ii) CovadAT&T's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadAT&T's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad AT&T Switch Center AT&T has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC-AMERITECH Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BASBC-IP(s) AMERITECH Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber- Meet is one hundred and fifty (150) days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-five hundred and fifty (45150) calendar days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which AT&T delivered notice to SBC- AMERITECH pursuant to Section 3.10.1. Within ten (10) business days of BA's SBC- AMERITECH’s receipt of Covad's AT&T’s notice, BA SBC-AMERITECH and Covad AT&T shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC-AMERITECH will make its best effort to Schedule 3.0meet AT&T’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 If Covad MFS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad MFS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad MFS has designated in the new LATA; (ii) CovadMFS's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadMFS's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center MFS has identified as its initial Routing Point(s) Point in the LATA as the CovadM-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadM-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadM-IP, the CovadM-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadMFS; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadMFS's notice, BA and Covad MFS shall confirm the BA-IP, the CovadM-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad GNAPS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 4.0 in which BA also offers Telephone Exchange Services, Covad GNAPS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Rating Point Covad GNAPS has designated in the new LATA; (ii) Covad's GNAPS’ requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast conforming to subsection 10.3 of Covad's GNAPS’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad GNAPS has identified as its initial Routing Rating Point(s) in the LATA as the CovadGNAPS-IP(s) in that LATA and shall designate mutually agreed upon the BA Wire Center(s) that houses a Tandem Office Offices within the LATA nearest to the Covad-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadGNAPS-IP, the CovadGNAPS-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 4.0 to reflect the schedule applicable to each new LATA requested by CovadGNAPS; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's GNAPS’s notice, BA and Covad GNAPS shall confirm the BA-IPIP(s), the CovadGNAPS-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.04.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad CLEC determines to offer Telephone Exchange Services Service within SBC-AMERITECH’s service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad CLEC shall provide written notice to BA SBC-AMERITECH of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad CLEC Switch Center POI(s) CLEC has designated in the new LATA; , (ii) CovadCLEC's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadCLEC's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad CLEC Switch Center that CLEC has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC-AMERITECH Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BASBC-IP(s) AMERITECH Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber-Meet is one hundred and thirty-five (135) calendar days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-hundred and thirty-five (45135) calendar days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which CLEC delivered notice to SBC- AMERITECH pursuant to Section 3.10.1. Within ten thirty (1030) business calendar days of BA's SBC- AMERITECH’s receipt of Covad's CLEC’s notice, BA SBC-AMERITECH and Covad CLEC shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC-AMERITECH will make its best effort to Schedule 3.0meet CLEC’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 If Covad MFS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad MFS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad MFS has designated in the new New LATA; : (ii) CovadMFS's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); ): and (iii) a non-binding forecast of CovadMFS's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center MFS has identified as its initial Routing Point(s) Point in the LATA as the CovadM-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadM-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadM-IP, the CovadM-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; MFS: provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadMFS's notice, BA and Covad MFS shall confirm the BA-IP, the CovadM-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad CLEC determines to offer Telephone Exchange Services Service within SBC’s service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad CLEC shall provide written notice to BA SBC of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad CLEC Switch Center POI(s) CLEC has designated in the new LATA; , (ii) CovadCLEC's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadCLEC's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad CLEC Switch Center that CLEC has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) SBC Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber- Meet is one hundred and thirty-five (135) calendar days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-hundred and thirty-five (45135) calendar days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which CLEC delivered notice to SBC pursuant to Section 3.10.1. Within ten thirty (1030) business calendar days of BA's SBC’s receipt of Covad's CLEC’s notice, BA SBC and Covad CLEC shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC will make its best effort to Schedule 3.0meet CLEC’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 4.6.1 If Covad NCI determines to offer Telephone Exchange Services in any LATA in Massachusetts not listed in Schedule 3.0 4.0 in which BA also offers Telephone Exchange Services, Covad NCI shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.6.2 The notice provided in subsection 4.4.1 4.6.1 shall include (i) the initial Routing Rating Point Covad NCI has designated in the new LATA; (ii) CovadNCI's requested intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)Date; and (iii) a non-binding forecast of CovadNCI's trunking requirementsrequirements conforming to subsection 10.4. 4.4.3 4.6.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad NCI has identified as its initial Routing Rating Point(s) in the LATA as the CovadNCI-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadNCI-IP (as measured in airline miles utilizing the V&H V and H coordinates methodMethod) as the BA-BA- IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadNCI-IP, the CovadNCI-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.6.4 The Parties shall agree upon an addendum to Schedule 3.0 4.0 to reflect the schedule applicable to each new LATA requested by CovadNCI; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of Covadthe NCI's noticenotice provided for in 4.6.1, BA and Covad NCI shall confirm the BA-IP, the CovadNCI-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.04.0.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad Global determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Global shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 Section 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad Global has designated in the new LATA; (iid) Covad's requested Global’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's Global’s trunking requirementsrequirements conforming to Section 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Global has identified as its initial Routing Rating Point(s) in the LATA as the CovadGlobal-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadGlobal-IP (as measured in airline miles utilizing the V&H coordinates methodV and H Coordinates Method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadGlobal-IP, the CovadGlobal-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadGlobal; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Global’s notice provided for in Section 4.5.1, BA and Covad Global shall confirm the BA-IP, the CovadGlobal-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 3.4.1 If Covad Requesting Carrier determines to offer Telephone Exchange Services Service within Ameritech's service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad Requesting Carrier shall provide written notice to BA Ameritech of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.4.2 The notice provided in subsection 4.4.1 Section 3.4.1 shall include (i) the initial Routing Point Covad Central Offices Requesting Carrier has designated in the new LATA; (ii) CovadRequesting Carrier's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)Date; and (iii) a non-binding forecast of CovadRequesting Carrier's trunking and facilities requirements. 4.4.3 3.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Central Office Requesting Carrier has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) RICO in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the Ameritech Tandem Office Central Office within the LATA nearest to the Covad-IP RICO (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) AICO in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; provided, however, that unless 3.4.4 Unless otherwise agreed by the Parties, the Interconnection Activation Date in a each new LATA shall not be the earlier of (i) the date mutually agreed by the Parties and (ii) the date that is no more than forty-five one hundred fifty (45150) days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which Requesting Carrier delivered notice to Ameritech pursuant to Section 3.4.1. Within ten (10) business days Business Days of BAAmeritech's receipt of Covad's noticeRequesting Carrier’s notice specified in Section 3.4.1, BA Ameritech and Covad Requesting Carrier shall confirm the BA-IPAICOs, the Covad-IP RICOs and the Interconnection Activation Date for the new LATA by attaching an addendum a supplementary schedule to Schedule 3.02.1.

Interconnection in Additional LATAs. 4.4.1 If Covad determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad has designated in the new LATA; (ii) Covad's ’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's ’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad has identified as its initial Routing Point(s) in the LATA as the Covad-IP(s) in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a Tandem Office within the LATA nearest to the Covad-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's ’s notice, BA and Covad shall confirm the BA-IP, the Covad-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad USWest determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad USWest shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad USWest has designated in the new LATA; (iid) Covad's requested USWest’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's USWest’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad USWest has identified as its initial Routing Rating Point(s) in the LATA as the CovadUSWest-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadUSWest-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadUSWest-IP, the CovadUSWest-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadUSWest; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe USWest’s notice provided for in subsection 4.5.1, BA and Covad USWest shall confirm the BA-IP, the CovadUSWest-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad MFN determines to offer Telephone Exchange Services in any LATA in Pennsylvania not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad MFN shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad MFN has designated in the new LATA; (iid) Covad's requested MFN’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's MFN’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad MFN has identified as its initial Routing Rating Point(s) in the LATA as the CovadMFN-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadMFN-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadMFN-IP, the CovadMFN-IP shall be no further than an entrance facility a non- distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadMFN; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe MFN’s notice provided for in subsection 4.5.1, BA and Covad MFN shall confirm the BA-IP, the CovadMFN-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 If Covad MFS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad MFS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad MFS has designated in the new LATA; (ii) CovadMFS's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadMFS's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center MFS has identified as its initial Routing Point(s) Point in the LATA as the CovadM-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadM-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadM-IP, the CovadM-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadMFS; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadMFS's notice, BA and Covad MFS shall confirm the BA-IP, the CovadM-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad ICI determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad ICI shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad ICI has designated in the new LATA; (ii) Covad's ICI’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-non- binding forecast of Covad's ICI’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad ICI has identified as its initial Routing Point(s) in the LATA as the CovadI-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadI-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadI-IP, the CovadI-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadICI; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's ICI’s notice, BA and Covad ICI shall confirm the BA-IP, the CovadI-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad Compass determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Compass shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the Compass-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad Compass has designated in the new LATA; (iid) Covad's requested Compass’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's Compass’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Compass has identified as its initial Routing Rating Point(s) in the LATA as the CovadCompass-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadCompass-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadCompass-IP, the CovadCompass-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadCompass; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Compass’s notice provided for in subsection 4.5.1, BA and Covad Compass shall confirm the BA-IP, the CovadCompass-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 If Covad TCG determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad TCG shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad TCG has designated in the new LATA; (ii) Covad's TCG’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's TCG’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad TCG has identified as its initial Routing Point(s) in the LATA as the CovadTCG-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadTCG-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadTCG-IP, the CovadTCG-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadTCG; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of Covad's notice, BA and Covad shall confirm the BA-IP, the Covad-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.ten

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad DBC determines to offer Telephone Exchange Services in any LATA in Rhode Island not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad DBC shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the DBC-IP; (b) the requested BA- IP; (c)the initial Routing Rating Point Covad DBC has designated in the new LATA; (iid) Covad's requested DBC’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date ; and (iiie) a non-binding forecast of Covad's DBC’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad DBC has identified as its initial Routing Rating Point(s) in the LATA as the CovadDBC-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Office within the LATA nearest to the CovadDBC-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadDBC-IP, the CovadDBC-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadDBC; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days Business Days of BA's ’s receipt of Covad's noticethe DBC’s notice provided for in subsection 4.5.1, BA and Covad DBC shall confirm the BA-IP, the CovadDBC-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.0.4.1.‌‌‌‌‌‌

Interconnection in Additional LATAs. 4.4.1 If Covad ACI determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad ACI shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad ACI has designated in the new LATA; (ii) Covad's ACI’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's ACI’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad ACI has identified as its initial Routing Point(s) in the LATA as the CovadACI-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadACI-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadACI-IP, the CovadACI-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadACI; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's ACI’s notice, BA and Covad ACI shall confirm the BA-IP, the CovadACI-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad Commonwealth determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad Commonwealth shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad Commonwealth has designated in the new LATA; (ii) Covad's Commonwealth’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's Commonwealth’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Commonwealth has identified as its initial Routing Point(s) in the LATA as the CovadC-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a an Access Tandem Office within the LATA nearest to the CovadC-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadC-IP, the CovadC-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadCommonwealth; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's Commonwealth’s notice, BA and Covad Commonwealth shall confirm the BA-IP, the CovadC-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad Compass determines to offer Telephone Exchange Services in any LATA in Massachusetts not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Compass shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the Compass-IP; (b) the requested BA-IP; (c)the initial Routing Rating Point Covad Compass has designated in the new LATA; (iid) Covad's requested Compass’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date ; and (iiie) a non-binding forecast of Covad's Compass’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Compass has identified as its initial Routing Rating Point(s) in the LATA as the CovadCompass-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadCompass-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadCompass-IP, the CovadCompass-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadCompass; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Compass’s notice provided for in subsection 4.5.1, BA and Covad Compass shall confirm the BA-IP, the CovadCompass-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 If Covad determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad has designated in the new LATA; (ii) Covad's ’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-non- binding forecast of Covad's ’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad has identified as its initial Routing Point(s) in the LATA as the Covad-Covad- IP(s) in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a Tandem Office within the LATA nearest to the Covad-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad▇▇▇▇▇; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's ’s notice, BA and Covad shall confirm the BA-IP, the Covad-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 III.4.1 If Covad Requesting Carrier determines to offer Telephone Exchange Services Service within Ameritech's service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad Requesting Carrier shall provide written notice to BA Ameritech of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 III.4.2 The notice provided in subsection 4.4.1 Section 3.4.1 shall include (i) the initial Routing Point Covad Central Offices Requesting Carrier has designated in the new LATA; (ii) CovadRequesting Carrier's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)Date; and (iii) a non-binding forecast of CovadRequesting Carrier's trunking and facilities requirements. 4.4.3 III.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Central Office Requesting Carrier has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) RICO in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the Ameritech Tandem Office Central Office within the LATA nearest to the Covad-IP RICO (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) AICO in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; provided, however, that unless III.4.4 Unless otherwise agreed by the Parties, the Interconnection Activation Date in a each new LATA shall not be the earlier of (i) the date mutually agreed by the Parties and (ii) the date that is no more than forty-five one hundred fifty (45150) days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which Requesting Carrier delivered notice to Ameritech pursuant to Section 3.4.1. Within ten (10) business days Business Days of BAAmeritech's receipt of Covad's noticeRequesting Carriers notice specified in Section 3.4.1, BA Ameritech and Covad Requesting Carrier shall confirm the BA-IPAICOs, the Covad-IP RICOs and the Interconnection Activation Date for the new LATA by attaching an addendum a supplementary schedule to Schedule 3.02.1.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad Mpower determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Mpower shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 Section 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad Mpower has designated in the new LATA; (iid) Covad's requested Mpower’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's Mpower’s trunking requirementsrequirements conforming to Section 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Mpower has identified as its initial Routing Rating Point(s) in the LATA as the Covad-IP(sMpower -IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the Covad-IP -IP (as measured in airline miles utilizing the V&H coordinates methodV and H Coordinates Method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadMpower-IP, the Covad-IP Mpower -IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadMpower; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Mpower’s notice provided for in Section 4.5.1, BA and Covad Mpower shall confirm the BA-IP, the Covad-IP Mpower -IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad Mpower determines to offer Telephone Exchange Services in any LATA in Pennsylvania not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Mpower shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 Section 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad Mpower has designated in the new LATA; (iid) Covad's requested Mpower’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's Mpower’s trunking requirementsrequirements conforming to Section 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Mpower has identified as its initial Routing Rating Point(s) in the LATA as the Covad-Mpower- IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadMpower-IP (as measured in airline miles utilizing the V&H coordinates methodV and H Coordinates Method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadMpower-IP, the CovadMpower-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP.IP.‌‌‌ 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadMpower; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Mpower’s notice provided for in Section 4.5.1, BA and Covad Mpower shall confirm the BA-IP, the CovadMpower-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.

Interconnection in Additional LATAs. 4.4.1 If Covad Hyperion determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad Hyperion shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad Hyperion has designated in the new LATA; (ii) Covad's Hyperion’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's Hyperion’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Hyperion has identified as its initial Routing Point(s) in the LATA as the CovadH-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadH-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadH-IP, the CovadH-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadHyperion; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's Hyperion’s notice, BA and Covad Hyperion shall confirm the BA-IP, the Covad-H- IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad NEXTLINK determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad NEXTLINK shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad NEXTLINK has designated in the new LATA; (ii) Covad's NEXTLINK’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's NEXTLINK’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad NEXTLINK has identified as its initial Routing Point(s) in the LATA as the CovadNEXTLINK-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadNEXTLINK-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadNEXTLINK-IP, the CovadNEXTLINK-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadNEXTLINK; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five thirty (4530) business days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's NEXTLINK’s notice, BA and Covad NEXTLINK shall confirm the BA-IP, the CovadNEXTLINK-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad KMC determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad KMC shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad KMC has designated in the new LATA; (ii) Covad's KMC’s requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's KMC’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad KMC has identified as its initial Routing Point(s) in the LATA as the CovadKMC-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadKMC-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadKMC-IP, the CovadKMC-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadKMC; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's KMC’s notice, BA and Covad KMC shall confirm the BA-IP, the CovadKMC-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad CLEC determines to offer Telephone Exchange Services Service within SBC-AMERITECH’s service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad CLEC shall provide written notice to BA SBC-AMERITECH of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad CLEC Switch Center POI(s) CLEC has designated in the new LATA; , (ii) CovadCLEC's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadCLEC's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad CLEC Switch Center that CLEC has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC-AMERITECH Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BASBC-IP(s) AMERITECH Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber- Meet is one hundred and thirty-five (135) calendar days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-hundred and thirty- five (45135) calendar days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which CLEC delivered notice to SBC-AMERITECH pursuant to Section 3.10.1. Within ten thirty (1030) business calendar days of BA's SBC-AMERITECH’s receipt of Covad's CLEC’s notice, BA SBC-AMERITECH and Covad CLEC shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC-AMERITECH will make its best effort to Schedule 3.0meet CLEC’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 If Covad MFS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad MFS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad MFS has designated in the new LATA; (ii) CovadMFS's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadMFS's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center MFS has identified as its initial Routing Point(s) Point in the LATA as the CovadM-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadM-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadM-IP, the CovadM-IP shall be no further than an entrance facility away from the BA-BA- IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadMFS; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadMFS's notice, BA and Covad MFS shall confirm the BA-IP, the CovadM-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 3.10.1 If Covad AT&T determines to offer Telephone Exchange Services Service within SBC-AMERITECH 's service areas in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Servicesadditional LATA, Covad AT&T shall provide written notice to BA SBC-AMERITECH of the its need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 3.10.2 The notice provided in subsection 4.4.1 Section 3.10.1 shall include include: (i) address of the initial Routing Point Covad AT&T Switch Center POI(s) AT&T has designated in the new LATA; , (ii) CovadAT&T's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); Date, and (iii) a non-binding forecast of CovadAT&T's trunking requirements. 4.4.3 3.10.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad AT&T Switch Center AT&T has identified as its initial Routing Point(s) Point in the LATA as the Covad-IP(s) ATIWC in that LATA and shall designate mutually agreed upon BA Wire Center(s) that houses a the SBC-AMERITECH Tandem Office Wire Center within the LATA nearest to the Covad-IP ATIWC (as measured in airline miles utilizing the V&H coordinates method) as the BASBC-IP(s) AMERITECH Interconnection Wire Center AIWC in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP, the Covad-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 3.10.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to Interconnection Activation Date in each new LATA shall be mutually established based on then-existing force and load, the scope and complexity of the requested by Covad; providedInterconnection and other relevant factors. The Parties acknowledge that, howeveras of the Effective Date, that unless the average interval to establish Interconnection via Collocation or Fiber- Meet is one hundred and fifty (150) days. Unless otherwise agreed to by the Parties, the Interconnection interconnection Activation Date in a each new LATA or each new Interconnection Point within a LATA shall not be the earlier than fortyof: (1) the date mutually agreed by the Parties which time shall be reasonably related to the actual time needed for activation, or (2) the date that is one-five hundred and fifty (45150) days after receipt by BA of all complete and accurate trunk orders and routing informationthe date on which AT&T delivered notice to SBC-AMERITECH pursuant to Section 3.10.1. Within ten (10) business days of BA's SBC-AMERITECH’s receipt of Covad's AT&T’s notice, BA SBC-AMERITECH and Covad AT&T shall confirm the BA-IPAIWC, the Covad-IP ATIWC and the Interconnection Activation Date for by mutually agreeing to a Trunk Plan. Notwithstanding the new LATA current average interval to establish Interconnection by attaching an addendum Collocation, SBC-AMERITECH will make its best effort to Schedule 3.0meet AT&T’s requested Interconnection Activation Date.

Interconnection in Additional LATAs. 4.4.1 If Covad MFS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad MFS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad MFS has designated in the new LATA; : (ii) CovadMFS's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); ): and (iii) a non-binding forecast of CovadMFS's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Center MFS has identified as its initial Routing Point(s) Point in the LATA as the CovadM-IP(s) IP in that LATA and shall designate a mutually agreed upon BA Local Serving Wire Center(s) Center that houses a an Access Tandem Office within the LATA nearest to the CovadM-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) IP in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadM-IP, the CovadM-IP IP, shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad; MFS, provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadMFS's notice, . BA and Covad MFS shall confirm the BA-IP, the CovadM-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 4.6.1 If Covad Transwire determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad Transwire shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.6.2 The notice provided in subsection 4.4.1 4.6.1 shall include (i) CLEC-IP; (ii) the requested BA-IP; (iii)the initial Routing Rating Point Covad Transwire has designated in the new LATA; (iiiv) Covad's requested Transwire’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)Date; and (iiiv) a non-binding forecast of Covad's Transwire’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.6.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad Transwire has identified as its initial Routing Rating Point(s) in the LATA as the CovadTranswire-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadTranswire-IP (as measured in airline miles utilizing the V&H V and H coordinates methodMethod) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadTranswire-IP, the CovadTranswire-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.6.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadTranswire; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe Transwire’s notice provided for in 4.5.1, BA and Covad Transwire shall confirm the BA-IP, the CovadTranswire-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad ACI determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad ACI shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad ACI has designated in the new LATA; (ii) CovadACI's requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of CovadACI's trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad ACI has identified as its initial Routing Point(s) in the LATA as the CovadACI-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the CovadACI-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the CovadACI-IP, the CovadACI-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by CovadACI; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's receipt of CovadACI's notice, BA and Covad ACI shall confirm the BA-IP, the CovadACI-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 If Covad GNAPS determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 4.0 in which BA also offers Telephone Exchange Services, Covad GNAPS shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Rating Point Covad GNAPS has designated in the new LATA; (ii) Covad's GNAPS’ requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast conforming to subsection 10.3 of Covad's GNAPS’s trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad GNAPS has identified as its initial Routing Rating Point(s) in the LATA as the Covad-GNAPS- IP(s) in that LATA and shall designate mutually agreed upon the BA Wire Center(s) that houses a Tandem Office Offices within the LATA nearest to the Covad-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadGNAPS-IP, the CovadGNAPS-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 4.0 to reflect the schedule applicable to each new LATA requested by CovadGNAPS; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's GNAPS’s notice, BA and Covad GNAPS shall confirm the BA-IPIP(s), the CovadGNAPS-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.04.0.

Interconnection in Additional LATAs. 4.4.1 If Covad Cox determines to offer Telephone Exchange Services in any LATA not listed in Schedule 3.0 in which BA also offers Telephone Exchange Services, Covad ▇▇▇ shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 The notice provided in subsection 4.4.1 shall include (i) the initial Routing Point Covad ▇▇▇ has designated in the new LATA; (ii) Covad's ▇▇▇’▇ requested Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0); and (iii) a non-binding forecast of Covad's ▇▇▇’▇ trunking requirements. 4.4.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad ▇▇▇ has identified as its initial Routing Point(s) in the LATA as the Covad-IP(s▇▇▇-IP(s) in that LATA and shall designate mutually agreed upon BA Local Serving Wire Center(s) that houses a Tandem Office within the LATA nearest to the Covad-IP ▇▇▇-IP (as measured in airline miles utilizing the V&H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the BA-IP to the Covad-IP▇▇▇-IP, the Covad-IP ▇▇▇-IP shall be no further than an entrance facility away from the BA-IP. 4.4.4 The Parties shall agree upon an addendum to Schedule 3.0 to reflect the schedule applicable to each new LATA requested by Covad▇▇▇; provided, however, that unless agreed by the Parties, the Interconnection Activation Date in a new LATA shall not be earlier than forty-five (45) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's ▇▇▇’▇ notice, BA and Covad ▇▇▇ shall confirm the BA-IP, the Covad-IP ▇▇▇-IP and the Interconnection Activation Date for the new LATA by attaching an addendum to Schedule 3.0.

Interconnection in Additional LATAs. 4.4.1 4.5.1 If Covad MFN determines to offer Telephone Exchange Services in any LATA in Maryland not listed in Schedule 3.0 4.1 in which BA also offers Telephone Exchange Services, Covad MFN shall provide written notice to BA of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.4.2 4.5.2 The notice provided in subsection 4.4.1 4.5.1 shall include (ia) the CLEC-IP; (b) the requested BA-IP; (c) the initial Routing Rating Point Covad MFN has designated in the new LATA; (iid) Covad's requested MFN’s intended Interconnection Activation Date (and related milestone dates in accordance with the format in Schedule 3.0)activation date; and (iiie) a non-binding forecast of Covad's MFN’s trunking requirementsrequirements conforming to subsection 10.3. 4.4.3 4.5.3 Unless otherwise agreed to by the Parties, the Parties shall designate the Wire Center(s) Covad MFN has identified as its initial Routing Rating Point(s) in the LATA as the CovadMFN-IP(s) in that LATA and shall designate a mutually agreed upon BA Wire Center(s) that houses a Tandem Office or End Offices within the LATA nearest to the CovadMFN-IP (as measured in airline miles utilizing the V&H V and H coordinates method) as the BA-IP(s) in that LATA, provided that, for the purpose of charging for the transport of traffic from the a BA-IP to the CovadMFN-IP, the CovadMFN-IP shall be no further than an entrance facility a non-distance sensitive Entrance Facility away from the BA-IP. 4.4.4 4.5.4 The Parties shall agree upon an addendum to Schedule 3.0 4.1 to reflect the schedule applicable to each new LATA requested by CovadMFN; provided, however, that unless agreed by the Parties, the Interconnection Activation Date activation date in a new LATA shall not be earlier than forty-five sixty (4560) days after receipt by BA of all complete and accurate trunk orders and routing information. Within ten (10) business days of BA's ’s receipt of Covad's noticethe MFN’s notice provided for in subsection 4.5.1, BA and Covad MFN shall confirm the BA-IP, the CovadMFN-IP and the Interconnection Activation Date activation date for the new LATA by attaching an addendum to Schedule 3.04.1.