North American Portability Management, LLC

LNPA Transition Contingency Rollback

Mechanized Provider Focused Industry Working Session

October 3rd, 2017

Agenda

• Industry-Led Rollback Process

o Rollback Work Flow

o Transaction Report

o Resubmission Aid

• Conclusion and Next Steps

• Q & A

2

About this meeting

Objectives

Our goal today is to review the rollback

planning with a focus on mechanized

provider procedures

This is the third in a series of meetings

to prepare for potential rollback

following transition

Facilitators

3

Welcome to today’s presentation!

Greg Chiasson

Principal

Chicago, IL

William Reilly

Director

Florham Park,

NJ

Jonathan

Turner

Manager

Washington, DC

Subject Matter Experts

4

Teresa Patton

NAPM Co-Chair &

Transition Team

AT&T Inc.

Deborah Tucker

NAPM Transition

Team

Verizon Inc.

John Malyar

LNPA Transition

Team

iconectiv LLC

Paul Mazouat

LNPA Transition

Team

iconectiv LLC

Dave Gorton

LNPA Transition

Team

iconectiv LLC

Suzanne Addington

NAPM Transition

Team

Sprint Inc.

A number of subject matter experts are present today and will support the discussion

Pat White

LNPA Transition

Team

iconectiv LLC

Rollback Workflow

5

Today we will focus on the “Act” components with more detail

Monitor Assess Decide Act

High Level Process

6

NAPM TOM maintains open conference bridges and WebEx for communications

Transition Pre-Rollback Point of Failure Rollback

Transition

completed

Begin logging NPAC requests

Begin monitoring performance

Maintain Neustar NPAC system in quiescent, state

Critical failure reported to TGT, with

details and status available at the time

iconectiv engineering works to resolve

Announce rollback on the

open conference bridge

Transaction Report provided to participants

Re-associate with Neustar NPAC

• Evaluate internal and iconectiv-provided

transaction reports

• Re-establish SOA and LSMS connections.

• Begin normal porting.

• Submit re-work transactions through the

usual interfaces (SOA, LTI, etc.).

Begin allowing connections to the NPAC,

with data as-of the close of transition

Industry

NAPM

iconectiv

Neustar

Transition Governance Team

Assess failure status

In the event of a rollback, preparation for re-submission is

likely to be the largest effort for Service Providers

• Identify internal operations personnel who will be handling the transition

and, if needed, rollback. Operations will include:

o NPAC connection and associations (including firewalls)

o Local system profiles

o Number porting record collection and analysis

o An escalation path for fallout management

• Become familiar with the Transaction Report specification

• Confirm availability of internal number porting records

• Evaluate and align (or develop) internal processes for transition and

rollback. Processes will need to cover:

o Switching connections between NPACs

o Ensuring that the tested/certified local system profiles is used

o Analyzing records and submitting re-work

• Plan for connectivity testing and regional pre-transition readiness checks

Workflow Level 2Rollback Readiness Planning

7

Advance planning will be needed for transaction preparation and re-submission

to be successful; Service Providers should:

Transaction Records and SOA State

(SP-compiled)

• Join the rollback conference bridge and WebEx

• Drop iconectiv NPAC connection

• Collect internal transaction recordso Regular NPAC porting

o MUMP, Pooling, and pending activity

• Retrieve Transaction Reports from the iconectiv SFTP site

• Review and organize work items from reportso Unrestricted work (e.g., modify active for own TNs)

o Customer service-impacting items

o Pooled blocks, LRN changes, etc.

o Port-outs

o Port-ins

o TNs with multiple ports during the period

o Other exceptions

• Prioritize and sequence work items

• Identify key porting partners and coordination

• Notify your customer care group to be prepared to handle customer calls

Workflow Level 2Prepare for Re-submission

Resubmission Aid

(iconectiv-provided

supplement )

Transaction Report

(iconectiv-provided)

• Restore credentials and profiles for the Neustar NPAC

• Re-associate SOA and LSMS systems with the Neustar

NPAC

o Join the Neustar maintenance conference bridges

o The Neustar NPAC has been ‘frozen’ in the maintenance

window since transition; follow normal ‘return from maintenance’

procedures

o Do not submit audit requests until your re-work is complete

o Do not apply BDD files to an LSMS until you are satisfied that

re-work is complete

• Begin re-work (including pooling) and regular porting

activity, coordinating with porting partners as necessary

• Engage your customer care groups to resolve fallout if

needed

• Re-schedule future mass transactions (SPID migrations,

etc.) with Neustar where needed

Workflow Level 2Re-submit Work

Operations Processes

(SP-internal, prepared in advance of transition)

Reviewing your transaction lists

before starting re-work will be

crucial to minimizing fallout

Most transactions will likely be

straightforward, but the complex

items should be identified early so

they can be handled properly

In addition to your own expertise,

iconectiv’s resubmission aid may

help to identify exceptions and

possible remediation steps

Managing complex transactions

may require coordination with

internal Care groups

Exceptions and Fallout Handling

1 0

Transaction Records

(SP-compiled)

Transaction Report

(iconectiv-provided)

Resubmission Aid

(iconectiv-provided)

Transaction Report

1 1

Service Providers will need to keep records of all work submitted to the

NPAC and Pooling Administrator between transition and the time the

region completes soak and is accepted as complete

iconectiv is also required to keep records; they will provide reports in the

previously shared format for each provider

Transaction Reports

1 2

Column

Number Column Name Example Value Format

NPA-NXX-X

Create

NPA-NXX-X

Modify

NPA-NXX-X

Delete

1 Transaction Timestamp 20140115153230.123 yyyymmddhhmmss.fff Required Required Required

2 Request Type NPA-NXX-X Create

enumerated, either LRN Create or

LRN Delete Required Required Required

3 Initiator SPID NPAC Will always be NPAC Required Required Required

4 Service Provider ID 0001 Always 4 alphanumeric Required Required Required

5 NPA-NXX-X 7326990 Always 7 digits Required Note 1 Note 1

6 NPA-NXX-X ID 1234567891 2 to 10 digits N/A Note 1 Note 1

7 Effective Timestamp 20140116000000 yyyymmddhhmmss Required Required N/A

8 NPA-NXX-X Pseudo LRN Indicator FALSE enumerated, either TRUE or FALSE Required N/A N/A

9 Scheduled Activity Date 20140115153200

yyyymmddhhmmss, seconds are

expected to be 00 N/A N/A Optional

Column

Number Column Name Example Value Format NPA-NXX Create

NPA-NXX

Delete

1 Transaction Timestamp 20140115153230.123 yyyymmddhhmmss.fff Required Required

2 Request Type LRN Create

enumerated, either LRN Create or

LRN Delete Required Required

3 Initiator SPID 0001

4 alphanumeric; if NPAC originates,

will be NPAC Required Required

4 Service Provider ID 0001 Always 4 alphanumeric Required Required

5 LRN 732699 Always 6 digits Required Note 1

6 LRN ID 123456 1 to 10 digits N/A Note 1

Column

Number Column Name Example Value Format

NPA-NXX

Create

NPA-NXX

Modify

NPA-NXX

Delete

1 Transaction Timestamp 20140115153230.123 yyyymmddhhmmss.fff Required Required Required

2 Request Type New SP Create

enumerated, either NPA-NXX

Create, NPA-NXX Delete, or NPA-

NXX Modify Required Required Required

3 Initiator SPID 0001

4 alphanumeric; if NPAC originates,

will be NPAC Required Required Required

4 Service Provider ID 0001 Always 4 alphanumeric Required Required Required

5 NPA-NXX 732699 Always 6 digits Required Note 1 Note 1

6 NPA-NXX ID 123456 1 to 10 digits N/A Note 1 Note 1

7 Effective Timestamp 20140116000000 yyyymmddhhmmss Required Required N/A

Column

Number Column Name Example Value Format

Block

Create Block Modify

1 Transaction Timestamp 20140115153230.123 yyyymmddhhmmss.fff Required Required

2 Request Type Block Create

enumerated, either Block Create or

Block Modify Required Required

3 Initiator SPID 0001

4 alphanumeric; if NPAC originates, will

be NPAC Required Required

4 Scheduled Activity Date 20140115153200

yyyymmddhhmmss, seconds are

expected to be 00 Required Required

5 NPA-NXX-X 7326991 7 digits Required Note 1

6 Block ID 1234567890 1 to 10 digits N/A Note 1

7 New Current SPID 0001 Always 4 alphanumeric Required Required

8 SV Type Wireline

enumerated: Wireline, Wireless, Class 2

VoIP, VoWIFI, Prepaid Wireless, Class

1 VoIP, SV TYPE 6 Optional Optional

9 LRN 7326999999 Always 10 digits Required Optional

10 CLASS DPC 028155067

always 9 digits, leading zero pad as

needed Optional Optional

11 CLASS SSN 000

always 3 digits, leading zero pad as

needed Optional Optional

12 LIDB DPC 028155067

always 9 digits, leading zero pad as

needed Optional Optional

13 LIDB SSN 000

always 3 digits, leading zero pad as

needed Optional Optional

14 ISVM DPC 028155067

always 9 digits, leading zero pad as

needed Optional Optional

15 ISVM SSN 000

always 3 digits, leading zero pad as

needed Optional Optional

16 CNAM DPC 028155067

always 9 digits, leading zero pad as

needed Optional Optional

17 CNAM SSN 000

always 3 digits, leading zero pad as

needed Optional Optional

18 WSMSC DPC 028155067

always 9 digits, leading zero pad as

needed Optional Optional

19 WSMSC SSN 000

always 3 digits, leading zero pad as

needed Optional Optional

20 Alternative SPID 0003 Always 4 alphanumeric Optional Optional

21 Alt-End User Location Value 123456789012 1 to 12 digits, leading zero allowed Optional Optional

22 Alt-End User Location Type 00 always 2 digits, leading zero allowed Optional Optional

23 Alt-Billing ID A40P 1 to 4 alphanumeric characters Optional Optional

24 Voice URI sip:user@example.com 1 to 255 characters Optional Optional

25 MMS URI mms:+17326990000 1 to 255 characters Optional Optional

26 SMS URI sms:+17326990000 1 to 255 characters Optional Optional

27 Last Alternative SPID X342 Always 4 alphanumeric Optional Optional

28 SOA Origination Flag 20140115180000 yyyymmddhhmmss Optional Optional

30 Suppress Initiator SPID FALSE enumerated, either TRUE or FALSE Optional Optional

31 Suppress Grantor SPID FALSE enumerated, either TRUE or FALSE Optional Optional

32 Suppress Delegate SPID FALSE enumerated, either TRUE or FALSE Optional Optional

33 Suppress Other SPID FALSE enumerated, either TRUE or FALSE N/A N/A

34 Suppress Other SPID Delegates FALSE enumerated, either TRUE or FALSE N/A N/A

Column

Number Column Name Example Value Format

New SP

Create

Old SP

Create

New SP

Modify

Old SP

Modify Cancel

Remove

From

Conflict

Activate Disconnect

1 Transaction Timestamp 20140115153230.123 yyyymmddhhmmss.fff Required Required Required Required Required Required Required Required

2 Request Type New SP Create

enumerated, either New SP Create, Old

SP Create, New SP Modify, Old SP

Modify, Cancel, Remove From Conflict,

Activate, or Disconnect. Required Required Required Required Required Required Required Required

3 Initiator SPID 0001

4 alphanumeric; if NPAC originates, will

be NPAC Required Required Required Required Required Required Required Required

4 Version TN 7326990000-0005

10 digits for single TN, 10 digits followed

by "-" followed by 4 digits for TN Range Required Required Note 1 Note 1 Note 1 Note 1 Note 1 Note 1

5 Version ID 1234567890 1 to 10 digits N/A N/A Note 1 Note 1 Note 1 Note 1 Note 1 Note 1

6 Status Pending

enumerated: Active, Pending,

Conflict,Disconnect Pending, Cancel-

Pending N/A N/A Note 2 Note 2 N/A N/A N/A N/A

7 LNP Type LSPP enumerated, either LSPP or LISP Required Required N/A N/A N/A N/A N/A N/A

8 Old SPID 0002 Always 4 alphanumeric Required Required N/A Required Note 3 Note 3 N/A N/A

9 Old SP Due Date 20140115153100 yyyymmddhhmmss N/A Required N/A Optional N/A N/A N/A N/A

10 Old SP Authorization FALSE enumerated, either TRUE or FALSE N/A Required N/A Optional N/A N/A N/A N/A

11 Cause Code 51 enumerated, either 50, 51, 52, 53, or 54 N/A Optional N/A Optional N/A N/A N/A N/A

12 Old SP Medium Timer Indicator TRUE enumerated, either TRUE or FALSE N/A Optional N/A Optional N/A N/A N/A N/A

13 New Current SPID 0001 Always 4 alphanumeric Required Required Required N/A Note 3 Note 3 Required Required

14 New SP Due Date 20140115153100 yyyymmddhhmmss Required N/A Optional Optional N/A N/A N/A N/A

15 New SP Medium Timer Indicator TRUE enumerated, either TRUE or FALSE Optional N/A Optional Optional N/A N/A N/A N/A

16 PTO Indicator TRUE enumerated, either TRUE or FALSE Required N/A N/A N/A N/A N/A N/A N/A

17 SV Type Wireline

enumerated: Wireline, Wireless, Class 2

VoIP, VoWIFI, Prepaid Wireless, Class

1 VoIP, SV TYPE 6 Optional N/A Optional N/A N/A N/A N/A N/A

17 New Version Status PENDING

must be "PENDING" (only specified for

Undo-Cancel Requests) N/A N/A Optional N/A N/A N/A N/A N/A

18 LRN 7326999999 Always 10 digits Optional N/A Optional N/A N/A N/A N/A N/A

19 CLASS DPC 028155067

always 9 digits, leading zero pad as

needed Optional N/A Optional N/A N/A N/A N/A N/A

20 CLASS SSN 000

always 3 digits, leading zero pad as

needed Optional N/A Optional N/A N/A N/A N/A N/A

21 LIDB DPC 028155067

always 9 digits, leading zero pad as

needed Optional N/A Optional N/A N/A N/A N/A N/A

22 LIDB SSN 000

always 3 digits, leading zero pad as

needed Optional N/A Optional N/A N/A N/A N/A N/A

23 ISVM DPC 028155067

always 9 digits, leading zero pad as

needed Optional N/A Optional N/A N/A N/A N/A N/A

The following worksheets describe the transactions that can occur for the major objects that NPAC users can

originate.

Each Worksheet defines the set of data that can occur in transactions for the object as well as what data is

required, optional, or N/A for each transaction.

The first row of each worksheet will contain the column names identifying the attributes that can appear in

transactions for the object. The set of attributes for a particular object will always be fixed. The remaining

rows will contain transactions that occur for that object. Each worksheet will be in a CSV format with pipe

character (|) used as the delimiter between fields. If an attribute for an object in N/A for a transaction or is

optional for a transaction and does not appear in a transaction request, then the pipes for the object will be

present with no value (if the last attribute listed for an object is N/A or does not appear, the ending pipe

character will not appear).

ICONECTIV CONFIDENTIAL - RESTRICTED ACCESS

This document and the confidential information it contains shall be distributed, routed or made available solely

to authorized persons having a need to know within iconectiv, except with written permission of iconectiv.

Telcordia Technologies, Inc. dba iconectiv.

Records should include all work: regular porting plus mass-transaction requests

Pending work

SV Data

Number Pool Blocks

NPA-NXX

LRN

NPA-NXX-X

SPs should also be

aware of any work that

will be in a pending state

across the transition

Transaction Report Specification documents were

distributed on August 25th to registered SPs. Our

current records suggest that all mechanized

providers have registered and should have

received the specification

At this point, everyone should have started

reviewing the iconectiv specification with their

operations teams

Expectations and Feedback

1 3

Between now and Jan 30th, SPs should identify the

processes and systems they will use to ensure that

primary records are kept (and make sure they are

accessible if needed)

Has any provider or service bureau in attendance today

NOT received the spec?

Resubmission Aid

1 4

iconectiv will provide a resubmission aid for use in the event of rollback as a supplement to Service Provider knowledge and experience

Resubmission Aid

1 5

The resubmission aid will provide guidance but is

not a replacement for provider expertise

Resubmission Aid

Contents

• Introduction

• Definitions

• Resubmission Guidelines

• Exceptions

The aid is intended to assist

service providers with:

• Organizing the work flow for

resubmitting transactions

• Identifying the various major

groups of transactions and

exceptions

• Prioritizing the work for

submission

• Resolving ‘exceptions’

The resubmission aid is in early draft today and will

go through a series of revisions prior to release

As described in the prior working sessions, we

expect iconectiv to publish the completed

document on or about 27 November

Expectations and Feedback

1 6

A review of recent NPAC data suggests that most re-

work will fall into a few key groups. However, there are

also a number of possible ‘exceptions’ that are being

considered

If, when you evaluate your procedures and transaction

reports, you identify particular scenarios of concern,

please provide that feedback so that iconectiv may

better address them in the resubmission aid

Please let us know what content and format would be most useful

Conclusions and Next Steps

17

Today we looked at a mechanized provider workflow for managing re-

work, and discussed how the Transaction Report and Resubmission

Aid will fit into the Industry-Led rollback

Next steps include

• Collecting and evaluating your feedback on the supporting material

• Assessing interest in a similar meeting focused on small provider

rollback and the LTI interface

• Completing the Resubmission Aid document, to be previewed at an

Industry Session in November/December

• Finalizing and sharing the connectivity testing plan

• Completing the schedule and preparations for user activation and

connectivity testing

Conclusions and next steps

1 8

Discussion

1 9

Thank you for your participation