Page ___ of ___

ATTACHMENT C – EXISTING NON-AMERITECH NUMBERS MOVING TO ENSEMBLE

(please document only CLEC native numbers moving to ENSEMBLE on this form)

In order to document the routing of cluster numbers to the associated hub TN, please list the end user’s existing CLEC numbers which will route to the hub number. If multiple hub TNs are to be used (requires Product Manager authorization) to segregate ISP traffic, complete the table below for each set of cluster number shich route to a specified hub TN. Indicate additional hub numbers in remarks section in lieu of having the actual hub numbers.

Has end user signed CPNI release? ( Yes ( No	Request for ENSEMBLE TN Assignments

What type of activity if this (check all that apply):	AIPC Initiator: __________________________________

( New ENSEMBLE installation	CBR: __________________________________________

( Addition of cluster numbers to existing	CUS Name: _____________________________________

ENSEMBLE service	Listed DN: ______________________________________

( Addition of hub TN to existing ENSEMBLE	DID Service Order No.: ____________________________

service	Due Date: _______________________________________

Removal of numbers from existing ENSEMBLE

Service

LATA: ________ (320, 340, 358, 356)

Please complete form and fax to Industry Markets LSC along with service request

Cluster office CLLI

(for TN assignment)	Switch

Type	Existing TN

***Important: Local TNs must be from a digital office i.e. DMS100, 5ESS, EWSD	Carrier of TN	SPS (CIG) Due Date
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Prime TNs (Same as Hub TN) (_____) _____-________ HUB TN (____) _____-________(hub number assigned by AIPC

REMARKS: __________________________________________________________________________________________

***Triggers are to be built/implemented in every office in the LATA with exception of 1AESS and DMS10 offices

NAC INFORMATION ONLY

DATE/TIME TO MKTG: _____________/_______________ NAC CONTACT/TN: _________________________________________________________

REMARKS: __________________________________________________________________________________________________________________

***IMPORTANT:

Local TNS must be from a digital office, i.e. DMS100, 5ESS, EWSD or associated remotes.

Based on end user or CLEC requirements, Industry Markets Service Manager may request (in IDM) that the order be divided into multiple orders for implementation of the triggers (on all the above numbers) in select offices in order to stage the moving of the end user’s existing numbers (and associated inbound traffic) onto ENSEMBLE.

EXISTING NON-AMERITECH PROVIDED NUMBERS MOVING TO ENSEMBLE – PAGE 4 – ATTACHMENT C

For new ENSEMBLE installations, fax this attachment C (and if appropriate, attachment B) along with the ENSEMBLE GENERAL INFORMATION SHEET to the LSC and your Service Manager. This information will provide traffic information for proper build out of the network for this end user.

This form is designed to capture the end users existing numbers moving to ENSEMBLE along with the associated Hub number. Additionally, this form will document the routing logic. Specifically, which cluster numbers will route to a Hub number. Hub numbers are used for routing purposes. It is strongly recommended that only one Hub number be used with ENSEMBLE. If multiple Hub numbers are to be used for routing purposes, please contact the product manager for authorization. Complete attachments A, B and C (as appropriate) for each Hub number being used. In addition to documenting the cluster offices to be use, this form will document the routing logic for each number at the Hub. For new installations, you will not have the Hub numbers assigned at this point. Use letters A, B, C, D and so on as place markers in lieu of the actual Hub number in the tables. The actual Hub numbers will be assigned during the installation by the NAC.

Has the end user signed CPNI release? –

A CPNI release should be received. Ameritech network personnel will be pulling traffic	information on the end user’s inbound traffic to help with proper engineering of the

ENSEMBLE network. Without CPNI release, Industry Markets will not have access to

this information. If CPNI has already been released, simply indicate “Y”. If not, have the

end user sign the CPNI release form. A copy of the form is in the Sales Kit.

What type of activity is this?

New ENSEMBLE service – in other words, new Hub TN and migrating Cluster TNs.

This should be the majority of orders.

Removal of numbers – document the specific number to be removed. If the

number to be removed is a Hub TN, please list the associated cluster numbers as

well.

Addition of cluster numbers – List the CLLI of the office from which you wish to

add a number from. In addition, document the Hub TN, which it will be

associated with.

Addition of Hub TN – You are required to document the corresponding new cluster

numbers for routing purposes. Attachment C should only be used when the cluster

numbers are existing CLEC numbers migrating to ENSEMBLE (please check

“addition of cluster numbers”). If cluster numbers are either existing ENSEMBLE

numbers or new cluster numbers , please REFER TO ATTACHMENTS A and B.

Request For ENSEMBLE TN Assignment –

Only end user name, LATA and Total number of numbers should be completed by the CLEC.

The DID due date will be completed by the service manager after the initial IDM. The remaining

will be completed by the AIPC. The AIPC will fax this form to NAC.

The Service Manager will receive a copy of the completed form after numbers are assigned.

ENSEMBLE NUMBERING TABLE

Document the cluster numbers and CLLI for the end user’s existing numbers to be added

to ENSEMBLE service. It is important to note that numbers are not available from the

following: 1A, DMS10, and the ENSEMBLE Hub (Cleveland Hub is an exception).

Refer to AFFTS or Pre-Order system for CLLI information on Ameritech native numbers. If

CLEC provided number are not existing in the Ameritech network, Industry Markets Technical

Planner to obtain which Ameritech CLLI should be used for the reverse ported CLEC number.

Please note ** not available with 1A, DMS10 and ENSEMBLE Hub offices.

Ameritech Host office CLLI – Available via AFFTS or Pre-Order system for native numbers or via

Technical planning for non-native numbers. This will determine the rate center for local

calls to the Hub.

Existing TN – Document the dial number to be migrated from the other Ameritech services to

ENSEMBLE.

Native TN – End users, which are migrating from a competitive carrier (CLEC), will have telephone

numbers which are either:

Numbers initially Ameritech that were ported to the CLEC (Native). The NXX

(exchange) of these numbers are already in our network. Converting these numbers

to ENSEMBLE will be relatively simple.

Numbers that have never been Ameritech numbers. These number are unique to the

CLEC (Non-Native). In order to migrate these numbers to ENSEMBLE service the

NXX must be opened in an Ameritech end office. It should be noted, that at this

point in time, non-native reverse portability is a lengthy process. When this is the

case, please involve the Technical Planner for assistance in the reverse LNP process.

Ameritech Host Switch Type – This is the Ameritech End Office, which the CLEC number will

reside. For native numbers this office is already available. For non-native numbers, this

office will need to be established by the Industry Markets Technical Planner. Please note

** offices cannot be 1A, DMS10 or ENSEMBLE Hub. Obtain this information from

AFFTS or the Pre-Order system.

Carrier – Document which carrier currently owns the end user’s number.

Hub TN – The Hub number will be assigned by NAC. Indicate only A, B, C and so on, as a place

marker for new installations when the number is not yet assigned. If adding new cluster

to an existing Hub TN, please indicate the hub number for which this order applies.

SPS (CTG) Order Due Date – The dates for the orders will be provided by Service Management.

Depending on the cutover/installation needs, the service manager may need to stagger

the CTG end office trigger orders based on the cluster numbers gradually moving the

end users traffic to ENSEMBLE over several days or weeks. The end users traffic will be

redirected to the ENSEMBLE trunk group number by number. This allows time to tear

down existing circuits and install ENSEMBLE circuits. Doing this should provide a less

intrusive migration for the end user. These dates should be negotiated between the IDM

members, service management and the CLEC.

Remarks – Please explain the order activity. ENSEMBLE is a complicated product. This

is an opportunity to provide additional information and prevent mistakes.

Page ___ of ___

CW9155

2001-07-11

Ameritech