1. Old Service Provider activates 10 digit trigger translations in Central Office by (TIME TO BE SPECIFIED)on the order due date. SEE NOTE 7.

NOTE 7: 10 digit trigger may optionally be applied by the new Service Provider.

2. New Service Provider activates Central Office translations.

The New Service Provider activates their own Central Office translations.

NOTE: Boxes 3 and 4 may be worked concurrently.

3. Old and New Service Providers make physical changes (where necessary).

Any physical work or changes will be made by either Old or New Service Provider as necessary.

4. New Service Provider notifies NPAC to activate routing number. (See note 9)

The new SP sends an activate message via the SOA interface to the NPAC SMS.

NOTE 9: No NPAC subscription version may activate before the FOC due date.

NOTE: Boxes 5, 6, and 7 may be concurrent, but at a minimum should be completed A.S.A.P.

5. NPAC SMS Downloads (real time) to all Service Providers (includes GTT's as appropriate).

The NPAC SMS will broadcast new subscription data to all SPs in the serving area in accordance with NOTE 0.

(NOTE 0 - These flows are intended to represent inter-company LNP processes. For complete specifications of all processing conditions, refer to pertinent requirements specifications document.)

6. NPAC SMS records date and time in history file.

The NPAC SMS will record the current date and time as the Activation Date and Time stamp, after all Local SMSs have successfully acknowledged receipt of new subscription version.

7. NPAC SMS Logs failures and non-responses. Sent to NPAC SMS System Administrator for investigation and/or correction. Also notification to new SP via SOA of which system(s) failed.

The NPAC SMS will resend the activation to a Local SMS that has not acknowledged receipt of the request. The number of NPAC SMS attempts to resend is a tunable parameter for which the current default is 3 attempts. Once this cycle is completed the NPAC personnel will investigate possible problem areas. In addition, the NPAC will send a notice to both the old and new SPs with a list of Local SMS that failed

activation.

8. All Service Providers update routing data bases (real time download). (See NOTE 8)

This is an internal process and performed in accordance with NOTE 0. Old Service Provider may remove translations subject to service order Due Date and time.

NOTE 8: Old Service Provider may remove all translations no earlier than (time to be specified) of the service order due date.

NOTE 0: These flows are intended to represent inter-company LNP processes. For complete specifications of all processing conditions, refer to pertinent requirements specifications document.

9. New Service Provider makes test calls to verify completion.

The New Service Provider should make test calls, as necessary, to verify that a call to a ported number completes as expected.

10. Do test calls complete?

If yes, go to step 14. If no, go to step 12.

11. Verify all provisioning steps are complete.

If the test call did not complete verify if all provisioning steps are completed and correct. If they are go to step 9 and make another test call.

12. 2nd time through decision?

If yes, go to step 13. If no, go to step 11.

13. Call your technical support organization.

If all provisioning steps are completed and correct and the test call does not complete correctly, then you need to contact your technical support organization.

14. End

This was a box which is no longer in the flow.

1xAA. Old Service Provider may removes all translations.

The Old Service Provider will remove translations at either the designated FDT or if the order has been designated as coordinated the New Service Provider will call the Old Service Provider to remove translations.