North American Portability Management, LLC Transition Oversight Manager. TOEP Webcast March 9, 2016

Transcription

1 North American Portability Management, LLC Transition Oversight Manager TOEP Webcast March 9, 2016

2 Welcome to today s webcast Submit Questions for Q&A Click the Q&A widget at the bottom of your screen to submit questions Webcast Issues Check the volume on your speakers You may also use the Q&A widget if you need additional technical support 2

3 Presenters Greg Chiasson Principal, Chicago, IL William Reilly Director, Florham Park, NJ Ayesha Datta Senior Associate, Washington DC 3

4 Agenda Recap of Last TOEP Webcast Proposed TOEP Events NPAC User Onboarding Overview NPAC/SMS Testing Overview 4

5 Recap of the Previous TOEP Webcast Last TOEP webcast was held on 27 th January 2016 LNPA Transition Update and Progress Overview of Onboarding and Testing A recording of the webcast is available using the following link upon registration: Presentation materials, polling results, and other materials from the webcast can be found on napmllc.org under the LNPA Transition tab A Frequently Asked Questions (FAQ) document has also been posted on napmllc.org to address common questions about the transition 5

6 Q&A Approach All questions received during the webcast are captured and categorized Questions that are answerable and of general interest are addressed during the webcast and subsequently added to the FAQ Questions that are answerable but are specific to an individual or organization are addressed separately following the webcast Questions that pertain to transition details that have not been finalized or for which answers are not available during the webcast are logged to be answered during future TOEP events The goal of the Q&A approach is to foster open and free exchange while ensuring TOEP participants receive useful information in an efficient and effective manner 6

7 Revised Q&A Approach The TOM has received a request to publish questions received through the TOEP webcasts and napmllc.org website We seek transparency in the transition, but realize that not everyone wants every question published Therefore, we will adopt an OPT IN approach Questions marked with Publication Authorized will be logged and published with answers to the website 1 Applies to TOEP webcast and nampllc.org questions Publication Authorized: How can I access the TOEP webcast content? 1. Questions that are (i) of common interest to the NPAC Community, (ii) have not been previously asked and answered, and (iii) are not otherwise inappropriate will be published 7

8 Upcoming TOEP Events 8

9 Polling Question 1 How interested are you in learning more about the transition through in-person meetings with the TOM? A) Very interested B) Somewhat interested C) Not interested D) Not sure 9

10 Proposed 2016 TOEP Events Communications Conferences Month Event April 4/11-4/12 Incompas (formerly COMPTEL PLUS) Conference Washington, DC September 9/7-9/9 CTIA (Cellular Telephone Industries Association) Conference Las Vegas, NV 9/26-9/27 NTCA (National Telephone Cooperative Association / The Rural Broadband Association) Fall Conference Indianapolis, IN Note: Proposed events are tentative and may be revised 10

11 Proposed 2016 TOEP Events Public Safety Conferences Month Event June August October 6/13-6/14 NENA (National Emergency Number Association) Conference Indianapolis IN 8/15-8/16 APCO (Association of Public-Safety Communications Officials) Conference and Expo Orlando, FL 10/17-10/18 IACP (International Association of Chiefs of Police) Conference San Diego, CA Note: Proposed events are tentative and may be revised 11

12 Proposed 2016 TOEP Events Additional Venues Month Event March 3/24 NANC (North American Numbering Council) meeting, Washington, DC May 5/4 TOEP Session, (following LNPA WG), Miami, FL June 6/30 NANC (North American Numbering Council) meeting, Washington, DC July 7/13 TOEP Session, (following LNPA WG), Raleigh, NC September 9/15 NANC (North American Numbering Council) meeting, Washington, DC December 12/1 NANC (North American Numbering Council) meeting, Washington, DC Note: Proposed events are tentative and may be revised 12

13 Proposed 2016 TOEP Events Webcasts Month Event April 4/20 - TOEP Webcast May 5/25 - TOEP Webcast June 6/21 - TOEP Webcast July 7/20 - TOEP Webcast August 8/31 - TOEP Webcast September 9/21 - TOEP Webcast October 10/27 - TOEP Webcast November 11/16 - TOEP Webcast December 12/13 - TOEP Webcast Note: Proposed events are tentative and may be revised Additionally, TOEP surveys are planned on a quarterly basis 13

14 Polling Question 2 Which of the following Communications conferences are you most likely to attend? A) Incompas (formerly COMPTEL PLUS), April B) CTIA Cellular Telephone Industries Association, September C) NTCA The Rural Broadband Association, September D) None 14

15 Polling Question 3 Which of the following Public Safety conferences are you most likely to attend? A) NENA National Emergency Number Association, June B) APCO Assoc. of Public-Safety Communications Officials, August C) IACP International Association of Chiefs of Police, October D) None 15

16 NPAC User Onboarding Overview 16

17 NPAC User Onboarding Steps iconectiv Process Onboarding Testing User Outreach Non-Disclosure Agreement Transition User Application Regional User Execute Regional User Agreement(s) Execute Regional User Agreement(s) Establish Connectivity to Test Bed* Execute Tests* Onboarding is the process whereby current NPAC users apply for and are provided access to the NPAC/SMS and services iconectiv will provide online training for each of the onboarding process steps and forms iconectiv will use best efforts to leverage existing data to streamline the process * Only for those required to test or who choose to participate in testing 17

18 1 Non-Disclosure Agreement What is a Non-Disclosure Agreement? Non-Disclosure Agreement (NDA) is a standard legal document between the user of the NPAC and iconectiv in which the parties agree not to disclose information covered by the agreement Each NPAC applicant (mechanized or non-mechanized) is required to sign an NDA NDAs are standard documents and will not be tailored on a per user basis High-Level Process Steps to Complete the NDA As a first step, iconectiv will share the NDA form with the NPAC applicant The applicant will engage their legal support and complete the NDA; NDA will require the NPAC applicant to share a list of SPIDs that should be onboarded to the NPAC NPAC applicant will share the signed NDA with iconectiv Upon completion of this step, a confirmation will be returned to the NPAC applicant with instructions on how to proceed through the next steps of onboarding 18

19 2 User Application What is a User Application? A user application is akin to a user profile User application captures the following information: Key customer contacts NPAC/SMS applicant type Service Provider, PTRS etc. Use of NPAC data Routing, Rating, Billing, Network Maintenance Type of operating authority Wireline, Wireless, VoIP NPAC/SMS service areas or regions High-Level Process Steps to Complete the User Application iconectiv will share a user application form with the NPAC applicant The NPAC applicant will identify their primary NPAC/SMS contact as well as review and confirm existing information pre-populated on the user application form NPAC applicant will complete and submit the user application form, one per operating authority NPAC applicant will also be required to submit copies of documents When the user application is accepted, a confirmation will be sent to the NPAC applicant with instructions on how to proceed through the next steps of onboarding 19

20 3 Regional User Agreement(s) What is a Regional User Agreement? An NPAC applicant s access to any of the regional NPACs is conditioned upon execution of an NPAC/SMS Regional User Agreement (RUA) Upon such execution of an RUA, the NPAC applicant is considered a User of the regional NPAC for which the RUA is executed The completed RUA must be accepted by iconectiv before the applicant is considered an authorized NPAC User High-Level Process Steps to Complete the User Application iconectiv will share a RUA form with the NPAC applicant NPAC applicant will complete and submit one RUA per region in which they operate After each RUA has been accepted, a confirmation will be sent to the NPAC applicant with instructions to complete the next steps which include establishing connectivity. The NPAC applicant is now a User for that region. 20

21 4 Connectivity What is Connectivity? Involves establishing access to the NPAC test bed or production platform; could involve a VPN connection, dedicated circuits, RSA token or a PIN depending on the user s NPAC access method For VPN or dedicated circuits access, connectivity is established based on the parameters captured through the connectivity form Establishing connectivity requires close inter-working between the NPAC user and iconectiv High-Level Process Steps to Establish Connectivity Prior to the start of testing, NPAC user can choose the type of testing they would like to participate in (in addition to any required testing) and the type of access they would like to establish to the NPAC test bed and/or production platform At this stage, test cases that need to be executed will be determined and test schedule to execute the test cases will be agreed Test data and any files to be shared with the user during testing are also prepared 21

22 Next Steps for NPAC Users Determine primary contact for onboarding Determine legal contacts for signing the NDA Determine contacts for signing the User Agreement(s) Determine the SPIDs to onboard to the new NPAC as well as those (if any) that are no longer needed and are not required to migrate to the new NPAC 22

23 NPAC/SMS Testing Overview 23

24 NPAC/SMS Testing Objective Objective of the NPAC/SMS testing is to validate that the iconectiv NPAC/SMS is ready for transition 1 Certify all interfacing Vendors (SOA & LSMS) against the new NPAC/SMS using the industry s Continuing Certification Testing (CCT) 2 Validate the NPAC/SMS functionality by executing the industry test cases 3 Validate the NPAC/SMS functionality by executing Ad-Hoc and Round-Robin (Group) test cases (test cases outside industry test cases) 24

25 What are Industry Test Cases? These test cases are defined by the LNPA Working Group (LNPA WG) in the NPAC/SMS Individual Service Provider Certification and Regression Test Plan document These test cases are executed by Vendors and mechanized Service Providers (SPs), Service Bureaus (SBs) and PTRS users in order to successfully interoperate with the NPAC/SMS Currently, there are ~150 LSMS and ~450 SOA test cases iconectiv will work with the NPAC users to understand which test cases should be executed based on the type and functionality of the System Under Test (SUT) NPAC users can perform additional test cases as they see fit for their system outside of the industry test cases 25

26 NPAC/SMS Testing Progression SOA/LSMS Vendors Continuing Certification Testing (CCT) Service Bureaus / Service Providers Includes PTRS Users Round-Robin (Group) Testing/ Ad-Hoc Testing Testing will be conducted sequentially to ensure that the technology used by each Service Provider is certified in advance Testing will follow the below progression: Vendor testing performed by SOA or LSMS Vendors; A Vendor s System Under Test (SUT) must be certified before their customers can connect to the iconectiv NPAC Mechanized service provider testing conducted by directly connected Service Providers (SPs), Service Bureaus (SBs) and PTRS users Ad-Hoc and Round-Robin (Group) testing performed by NPAC users 26

27 NPAC/SMS Testing Sequence CCT for Service Providers, and PTRS with Mechanized Interfaces Ad-Hoc Testing for Service Providers with Mechanized Interfaces CCT for Vendors (SOA and LSMS) CCT for Service Bureaus with Mechanized Interfaces Round-Robin (Group) Ad-Hoc Testing for Service Provider Using Mechanized Service Bureaus Acronym Full Form CCT Continuing Certification Testing IVR Interactive Voice Response LTI Low-Tech Interface PTRS Providers of Telecom Related Services SP Service Provider SB Service Bureau LTI SBs Testing Service Providers using LTI Service Bureau Service Providers using Help Desk and IVR Key: Required to test Optional to test PTRS users not using a mechanized interface 27

28 NPAC/SMS Testing Participation Stakeholder Group Vendors (SOA and LSMS) CCT Required_ Testing Participation by NPAC Stakeholder Ad-Hoc Round-Robin (Group) Additional Tests SPs/SBs/PTRSs using mechanized interface Required* SPs using mechanized SBs SPs using LTI SBs SPs using Help Desk SPs using IVR PTRSs not using a mechanized interface Optional LTI testing Help Desk testing IVR testing Test BDD or reports * In some cases, some SPs may arrange with their SBs or vendors to test their configuration on their behalf 28

29 Polling Question 4 You anticipate taking part in which type of NPAC/SMS testing? A) Continuing Certification Testing B) Ad-Hoc Testing C) Round-Robin (Group) Testing D) Combination of Above E) Not Applicable 29

30 Prerequisites to NPAC/SMS Testing User onboarded (NDA, user application and regional user agreements completed and accepted) Connection to the iconectiv NPAC test bed established using a VPN connection, dedicated circuits, RSA token or a PIN User equipped with access to iconectiv secure FTP site, industry reference test data consistent with user configurations, individual test plan and test schedule Note: Some users may connect via VPN during testing in lieu of a later production connection (e.g. T1) 30

31 NPAC/SMS Testing Responsibilities Overview iconectiv User Facilitate onboarding Support test execution Provide access to test beds Provide status reports Correct defects found Complete NDA and related paperwork Conduct testing in accordance with test plan Report incidents as needed Coordinate with your Service Bureau or Vendor regarding testing if needed 31

32 NPAC/SMS Test Reporting Each test participant will receive individual test reports that record the test execution results for the System Under Test (SUT); no other parties will be granted access to the individual test reports Test reports will include test results i.e. test cases that passed or failed Aggregate (non-company specific) results will also be communicated through TOEP events and other means 32

33 What Has Been Covered So Far? Industry test cases are test cases defined by the LNPA Working Group in the NPAC/SMS Individual Service Provider Certification and Regression Test Plan document NPAC/SMS testing consists of three key types of testing Continuing Certification Testing (CCT), Ad-Hoc testing and Round-Robin (Group) testing Each Vendor and Service Providers (SPs), Service Bureaus (SBs) and PTRS users with a direct mechanized connection to the NPAC is required to complete Continuing Certification Testing (CCT) Prerequisites to testing include onboarding, establishing access to the iconectiv test bed in addition to determining which test cases to execute and when 33

34 Q & A 34

35 Thank you for attending today s webcast Next TOEP Event Tentatively Scheduled for 20th April 2016 Share your comments via napmllc.org Access the LNPA transition tab Use the quick launch bar on the left to access the comments tab Provide your details and comments and press submit 35