Common use of Bulk Migration Clause in Contracts

Bulk Migration. 2.1.10.1 BellSouth will make available to <<customer_short_name>> a Bulk Migration process pursuant to which <<customer_short_name>> may request to migrate port/loop combinations, provisioned pursuant to a separate agreement between the parties, to Loops (UNE-L). The Bulk Migration process may be used if such loop/port combinations are (1) associated with two (2) or more Existing Account Telephone Numbers (EATNs); and (2) located in the same Central Office. The terms and conditions for use of the Bulk Migration process are described in the BellSouth CLEC Information Package, incorporated herein by reference as it may be amended from time to time. The CLEC Information Package is located at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇/▇▇▇▇/▇▇▇▇.▇▇▇▇. The rates for the Bulk Migration process shall be the nonrecurring rates associated with the Loop type being requested on the Bulk Migration, as set forth in Exhibit A. Additionally, Operations Support Systems (OSS) charges will also apply. Loops connected to Integrated Digital Loop Carrier (IDLC) systems will be migrated pursuant to Section 2.6 below. 2.1.10.2 Should <<customer_short_name>> request migration for two (2) or more EATNs containing fifteen (15) or more circuits, <<customer_short_name>> must use the Bulk Migration process referenced in 2.1.11.1 above.

Bulk Migration. 2.1.10.1 BellSouth will make available to <<customer_short_name>> a Bulk Migration process pursuant to which <<customer_short_name>> may request to migrate port/loop combinations, provisioned pursuant to a separate agreement between the parties, to Loops (UNE-L). The Bulk Migration process may be used if such loop/port combinations are (1) associated with two (2) or more Existing Account Telephone Numbers (EATNs); and (2) located in the same Central Office. The terms and conditions for use of the Bulk Migration process are described in the BellSouth CLEC Information Package, incorporated herein by reference as it may be amended from time to time. The CLEC Information Package is located at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇/▇▇▇▇/▇▇▇▇.▇▇▇▇. The rates for the Bulk Migration process shall be the nonrecurring rates associated with the Loop type being requested on the Bulk Migration, as set forth in Exhibit A. Additionally, Operations Support Systems (OSS) charges will also apply. Loops connected to Integrated Digital Loop Carrier (IDLC) systems will be migrated pursuant to Section 2.6 below. 2.1.10.2 Should <<customer_short_name>> request migration for two (2) or more EATNs containing fifteen (15) or more circuits, <<customer_short_name>> must use the Bulk Migration process referenced in 2.1.11.1 above.

Bulk Migration. 2.1.10.1 BellSouth 2.1.13.1 AT&T will make available to <<customer_short_name>> a Bulk Migration process pursuant to which <<customer_short_name>> may request to migrate port/loop Loop combinations, provisioned pursuant to a separate agreement between the parties, to Loops (UNE-L). The Bulk Migration process may be used if such loopLoop/port combinations are (1) associated with two (2) or more Existing Account Telephone Numbers (EATNs); and (2) located in the same Central Office. The terms and conditions for use of the Bulk Migration process are described in the BellSouth AT&T CLEC Information Package, incorporated herein by reference as it may be amended from time to time. The CLEC Information Package is located at on AT&T’s Interconnection Web site at: ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇&▇.▇▇▇/▇▇▇▇▇▇/▇▇▇▇/▇▇▇▇.▇▇▇▇. The rates for the Bulk Migration process shall be the nonrecurring rates associated with the Loop type being requested on the Bulk Migration, as set forth in Exhibit A. Additionally, Operations Support Systems (OSS) OSS charges will also apply. Loops connected to Integrated Digital Loop Carrier (IDLC) systems will be migrated pursuant to Section 2.6 below. 2.1.10.2 2.1.13.2 Should <<customer_short_name>> request migration for two (2) or more EATNs containing fifteen (15) or more circuits, <<customer_short_name>> must use the Bulk Migration process referenced in 2.1.11.1 above.