In Attendance:

Phil Presworsky TCG

Jim Joerger MCI

Ed Elkin AT&T

Darin Liston Sprint

Lorin Pollock Sprint

Jane Dempsey Ericsson

Karen Kay Time Warner

Gene Johnston GTE

Bill Belshaw MCI

Robin Meier Ameritech

Dick Anderson World Com

Barry Bishop Ameritech

The purpose of the conference call was to review the changes and proposals to the provisioning flow verbiage that would support the NANC Flows. The attached documents support the NANC flows Fig. 1, and Fig. 2 and were agreed upon by those on the call.

There was one area for figure 1 where we did not have consensus. The proposed texts are outlined in a box. It was agreed that we would forward the verbiage to the NANC team as is.

In addition to the verbiage for Fig 1 and 2, the verbiage supporting the Repair flow and the NPA/NXX opening previously agreed upon would also be presented to the NANC team.

Also attached you will find a Draft verbiage for figure 3 which will be discussed at the next meeting. Robin Meier modified the verbiage in an attempt to save some time at the next meeting.

Very short minutes. If there are any necessary corrections, or items that I may have missed, please contact me ASAP.

Barry Bishop

312-220-8000

1. End User Contact

The process begins with an end user requesting service.

2. End User agrees to change to New Provider.

End User agrees to change to new service provider and wants to retain current telephone number.

3. Is End User porting all telephone numbers?

The New Service Provider will determine if there is service which will continue to be maintained by the Old Service Provider. If yes, go to step (4). If no, go to step (8).

4. New Service Provider notifies Old Service Provider of change using Local Service Request (LSR).

The New Service provider notifies the Old Service Provider of the porting using the LSR and sends the information via an electronic gateway, FAX, or other manual means.

5. Old Service Provider provides Firm Order Confirmation (FOC) to New Service Provider within 24 hours. (See note 5)

The Old Service Provider sends the FOC via electronic gateway, FAX, or other manual means to the New Service Provider within the 24 hour receipt of the completed LSR.

(Note 5 -Large complex porting LSR's may extend the FOC response beyond the 24 hours.)

Proposed Text for Note 5 by Jim Joerger (MCI)

"The minimum expectation is that the firm order confirmation (FOC) is to be returned within 24 hours except in cases where an LSR was submitted just prior to the end of a business week, or where superceded by inter-company agreements. It is the responsibility of the old service provider to contact the new service provider if the old service provider is unable to meet the 24 hour expectation for transmitting the FOC. If the FOC is not received by the new service provider within 24 hours, then the new service provider should contact the old service provider."

Proposed Test for Note 5 by Darin Liston (Sprint)

"The minimum expectation is that the firm order confirmation (FOC) is to be returned within 24 hours excluding weekends. Exception to this would be where superceded by inter-company agreements. It is the responsibility of the old service provider to contact the new service provider if the old service provider is unable to meet the 24 hour expectation for transmitting the FOC. If the FOC is not received by the new service provider within 24 hours, then the new service provider should contact the old service provider."

Differences are bolded and italicized

6. Old and New Service providers create and process Service Orders.

The Service providers create and process their service orders through their internal service order systems, from the information provided on FOC/LSR.

7. New Service Provider obtains End-User Authorization.

New Service provider obtains actual authority from end user to act as the official agent on behalf of the end user. The New Service Provider will be responsible for demonstrating such authority as necessary.

8. New Service provider notes only partial change of service in remarks on LSR.

The New Service provider will make a note in the remark section of the (LSR) to identify if the end user is only making a partial change of service.

9. Old (optionally) and New Service providers notify NPAC of change request. (See note 4)

Service Provider(s) enter subscription data into NPAC SMS via SOA interface for porting of end-user 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.

NOTE 4 - Due date on creation message is the due date on FOC. Any change of due date to NPAC must be the result of a change in FOC due date. The FOC Due date will be no earlier than 3 business days after the FOC receipt date, except for the first telephone number being ported in an NPA-NXX. It is assumed that the porting interval is not in addition to intervals for other requested services related to the porting (e.g. unbundled loops). The interval becomes the longest single interval required for the services requested. [Phil P. requesting wording change for NOTE 4, he will submit change request to NANC.]

10. NPAC performs Data Validation

NPAC SMS validates data to ensure value formats and consistency. (See 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.

11. Is data valid?

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

12. Did NPAC receive both, and accurate notifications within 9 hours ( _T1)? (See note 2)

If SPs have not notified the NPAC SMS and /or provided accurate data the NPAC SMS will send a notification to the SP who has not yet responded to the port. This is an NPAC SMS tunable parameter- (The designated time length is equal to 9 hours. See Note 2.) If yes, go to step 13. If no, go to step 16.

NOTE 2: NPAC SMS processing timers will include business hours only except where specified. Local business hours are to be defined as 12 daytime hours per day on Monday through Fridays, except holidays.

13. New Service Provider coordinates physical changes with old Service Provider.

The new Service Provider has the option of requesting a coordinated order.

(NOTE 1: If coordination is requested on the LSR, an indication of yes or no for the application of a 10 digit trigger is required. If no coordination indication is given, then, by default the 10 digit trigger is applied.)

14. 10 digit trigger?

If yes, go to Inter-Service Provider LNP Operations Flows - Provisioning with 10-Digit Trigger - Tie point AA- Draft- dated 1/31/97, issue 0.11. If no, go to Inter-Service Provider LNP Operations Flows - Provisioning without 10-digit trigger, tie point A, Draft, 1/31/97, issue 0.11.

Unconditional LNP trigger is an option assigned to a line on a donor switch during the transition period when the line is being physically moved from donor switch to recipient switch. (See NOTE 7) During this period it is possible for the line to be resident in both donor and recipient switches at the same time.

NOTE 7 - 10 digit trigger may optionally be applied by New Service Provider.

15. Return data to Service Provider.

If the data is not valid the NPAC will return notification to the Service Provider for correction.

16. NPAC notifies appropriate Service Provider(s) that information is missing or inaccurate.

NPAC SMS will provide an Initial Concurrence Window tunable parameter which is defined as the number of hours after the subscription version was initially created by which time both SPs can authorize transfer of subscription service. Current default is 9 hours. Once that time has expired the NPAC SMS will send a notification over the SOA interface to the SP and start timer (_T2).

17. Does NPAC receive information within 9 hours (_T2)? (See note 2)

The NPAC SMS will provide a Final Concurrence Window tunable parameter which is defined as the number of hours after the concurrence request is sent by the NPAC SMS. (The designated time is equal to 9 hours.) Depending on which SP is lacking concurrence the NPAC will take action. If yes, go to step 18. If no, go to step 22.

NOTE 2: NPAC SMS processing timers will include business hours only except where specified. Local business hours are to be defined as 12 daytime hours per day on Monday through Fridays, except holidays.

18. Did Old SP place order in Conflict? (see note 3)

(See note 0)

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

NOTE 3: Check Concurrence Flag Yes or No. If no, a cause code Conflict must be designated. Old will make a concerted effort to contact New Provider prior to placing subscription in conflict.

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

19. Data corrected & forwarded.

The SP upon notification from the NPAC SMS will correct the data and forward back to NPAC SMS.

20. NPAC notifies both service providers that transaction is canceled and change is rejected.

This subscription version is immediately canceled by NPAC SMS. Both service providers cancel all related internal work orders.

21. NPAC logs no response.

The NPAC records that it received no concurrence from the new SP.

22. Is missing or inaccurate information from New or Old service provider?

If new SP, go to step 21. If old SP, go to step 24.

23. NPAC logs request to place order into conflict including cause code.

The NPAC SMS will log the "conflict" request including the cause code. Go to Inter-Service Provider LNP Operations Flows - Conflict Flow for the Service Creation Provisioning Process-Tie Point B, Draft 1/31/97- issue 0.11, figure 4.

24. Porting proceeds under control of New Service Provider.

Return to step 13.

There are two things going on 1) A notification message is sent to the old service provider noting that the porting is proceeding in absence of any message from the old service provider. 2) This subscription version is now "non-concurred", as such the old SP will not be able to subsequently place this subscription version in conflict nor cancel the order.

This is also the re-entry point from the conflict flow Tie Point BB - Inter-Service Provider LNP Operations Flows - Conflict Flow for the Service Creation Provisioning Process-, Draft 1/31/97- issue 0.11. Tie Point BB.

25. End

NOTES:

NOTE 7 - 10 digit trigger may optionally be applied by New Service Provider.

NOTE 5 -Large complex porting LSR's may extend the FOC response beyond the 24 hours.

NOTE 4 - Due date on creation message is the due date on FOC. Any change of due date to NPAC must be the result of a change in FOC due date. The FOC Due date will be no earlier than 3 business days after the FOC receipt date, except for the first telephone number being ported in an NPA-NXX. It is assumed that the porting interval is not in addition to intervals for other requested services related to the porting (e.g. unbundled loops). The interval becomes the longest single interval required for the services requested.

NOTE 3: Check Concurrence Flag Yes or No. If no, a cause code for Conflict must be designated. Old will make a concerted effort to contact New Provider prior to placing subscription in conflict.

NOTE 2: NPAC/SMS processing timers will include business hours only except where specified. Local business hours are to be defined as 12 daytime hours per day on Monday through Fridays, except holidays.

NOTE 1: If coordination is requested on the LSR, an indication of yes or no for the application of a 10 digit trigger is required. If no coordination indication is given, then, by default the 10 digit trigger is applied.

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

NOTE: Boxes 1, 2, or 3 should be worked concurrently

1. New Service Provider activates (their) Central Office translations.

The New Service Provider will activate their own Central Office translations.

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

3. New Service Provider notifies NPAC to activate routing number.

The new SP sends an activate message via the SOA interface to the NPAC SMS.(See Note: 6 )

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

NOTE: Boxes 4, 5, 6, and 7 may be concurrent, but at a minimum should be completed ASAP.

4. 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 documents.

5. 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.

6. Old Service Provider removes translations in Central Office.

The Old Service Provider will remove translations within 30 minutes at either the designated Frame Due Date and Time, or if the order has been designated as coordinated the New Service Provider will call the Old Service Provider to remove translations.

NOTE: Revisit the 30 minute time frame within 90 days.

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).

This is an internal process and performed 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 documents.

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 11. If no, go to step13.

11. End

12. 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.

13. 2nd time through decision?

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

14. Call your technical support organization.

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

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.