LNPA Transition Outreach and Education Plan (TOEP)

Transcription

1 LNPA Transition Outreach and Education Plan (TOEP) Frequently Asked s The LNPA Transition Oversight Manager (TOM) has assembled a list of Frequently Asked s (FAQ) that are of common interest to the NPAC community and other users of services provided by the LNPA. These questions have been grouped into several categories: 1. About the Transition 2. Scope and Customer Impact 3. Timeline 4. User Onboarding 5. User Testing 6. Communications and Staying Informed At this time, we are unable to answer certain specific questions that deal with aspects of the project that are still being finalized. But, as the transition progresses and additional details become available, we will update this FAQ document to reflect the responses to these questions 1. About the Transition Why is the transition occurring? What do PTRS, SP, SB, ELEP, LEAP, WDNC and PAS mean? What do you mean by "Vendor"? In March 2010, the NAPM announced its intention to begin a competitive process to select a new LNPA. This resulted in the FCC providing conditional approval, on March 26, 2015, of the NANC recommendation that Telcordia d.b.a. iconectiv serve as the next LNPA. Further details can be found here FCC LNPA order. PTRS is an abbreviation for "Provider of Telecommunications Related Services". SP is an abbreviation for "Service Provider", an NPAC system end-user SB is an abbreviation for "Service Bureau", a company that supports many end-user Service Providers ELEP is an abbreviation for "Enhanced Law Enforcement Platform" LEAP is an abbreviation for "Local number portability Enhanced Analytics Platform" WDNC is an abbreviation for "Wireless Do Not Call" service PAS means the "Pooling Administration Service" Vendor means a company that develops local systems, i.e.: LSMS software or SOA software, as a product. Note that some Vendors are also Service Providers Page 1 of 8

2 2. Scope and Customer Impact How will the transition impact user experience? Will there be a change in the Service Bureau that currently serves me? What about XML? I haven t heard anything about the XML interface How will this impact my total cost of services? Will there be extra fees for connection, testing, or other NPAC/SMS services? What is the scope of the LNPA transition? During the transition, some work will be required of users as part of onboarding and testing. However, following transition, the LNPA services are expected to be essentially the same as those before the transition including: Users connecting directly via a mechanized interface (CMIP/XML) should expect the same service Users connecting indirectly via a Service Bureau should expect the same service as changes will be managed by the Service Bureau Users connecting via the Web interface (LTI) can expect the same functionality, but will see some differences in style and application steps Users connecting via the IVR will do so via a different contact number, but should expect the same functionality. There may be some differences of style and application steps Users accessing the Helpdesk will do so via a different contact number but, should expect a similar level of service Users of the current LEAP service can expect the same functionality, but will see some differences in style and application steps More information will be provided once available. If you currently connect to NPAC/SMS services through a Service Bureau your experience is expected to remain essentially the same. Additional information will be provided to you and your Service Bureau regarding onboarding and testing when available. XML will be supported. Specific timing and next steps will be covered by iconectiv during your onboarding process. Specific information on fees will be provided during onboarding in conjunction with the NDA (non-disclosure agreement) and user agreement. Generally, we expect that future industry fees will be substantially lower than current fees. All functionality of the current NPAC will be part of the iconectiv NPAC and is within the scope of this transition. The associated FRS (functional requirements specification) is available at on the "The NPAC" tab under "Software Releases". Some included components, beyond the core NPAC/SMS are: mass ports, mass updates, most regular and custom/ad hoc reports, ELEP service (also known as LEAP), WDNC service, PortPS, and Bulk Data Download (BDD) file support. Page 2 of 8

3 However, new initiatives still being evaluated by the FCC, like national number portability and IP transition, are not part of this transition. 3. Timeline When will the transition begin? When will the NPAC migrate from Neustar to iconectiv? How will regions be migrated? How long will the testing phase(s) be? Will we have enough time? Where can I find the current timelines and when will a more detailed transition schedule be shared? The FCC order was released in March The TOM was engaged in August of 2015 and planning for the transition is well underway. The exact timeline for the transition is being finalized in conjunction with the Federal Communications Commission (FCC) and the North American Portability Management, LLC (NAPM). According to the preliminary transition timeline the initial phases of user transition will begin with onboarding activities in Data Migration and Go-Live activities will begin in first half of 2017 and continue into the second half of Please note that timing is dependent on final agreement on the MSA transition schedule. Per the Transition Oversight Plan (TOP), a first region will be migrated and allowed to run, or soak, for approximately 30 days. Upon successful conclusion of this soak period, the remaining regions will be migrated according to a defined schedule. The preliminary transition timeline indicates that testing will begin in 2016 and will continue well into The testing phases allow the various types of users to test the functionality of the new NPAC. The TOM is monitoring test plans to ensure service providers have sufficient time for testing. More specific information on this topic will be available in the future. Please note that timing is dependent on final agreement on the MSA transition schedule. The exact timeline for the transition is being finalized in conjunction with the Federal Communications Commission (FCC) and the North American Portability Management, LLC (NAPM). Once finalized and approved, the updated transition schedule will be published. This will permit parties to develop more precise estimates of the timing of activities, associated costs of transition, and expected recurring cost. Initial timeline information was provided in the TOP (Transition Oversight Plan), which can be found at the following link: The TOM subsequently provided draft date-range information in TOEP webcasts, which may be found at the following link: (see documents titled "TOEP webcast content"). Page 3 of 8

4 4. User Onboarding How will iconectiv determine the appropriate contact at a carrier for onboarding? When will I be onboarded, and by whom? What is an "operating authority?" If a provider serves 40 states, must it provide 40 documents? Why do I need to provide SPIDs as part of the NDA? How do I find out what type of user I currently am? Ex: SOA/LSMS Vendor, Service Bureaus/Service Provider, NPAC/SMS user? What is a "mechanized" user vs. a "non-mechanized" user? We are a provider that accesses the NPAC data to produce lists, reports, or other products for our clients. Do we have to sign an NDA? Will our clients have to sign an NDA? Can we sign on their behalf? When do I need to order circuits? iconectiv will use the contact information in the current NPAC/SMS associated with each SPID (Service Provider ID) to begin the onboarding process. One of the objectives of the outreach will be to update or confirm the appropriate contact(s) for each user. Onboarding activities, including the completion of NDAs, are expected to begin in 2016 and will be conducted in stages. Every NPAC user will be contacted and onboarded by iconectiv during this period. Note that onboarding will be conducted in stages. An operating authority is a state or federal grant of authority to serve. As was done with the current LNPA, the Service Provider must have an Operating Authority for each NPAC/SMS region in which it operates (maximum of seven). The SPID (Service Provider ID) is a key identifier for number portability and is essential to the transition to the new NPAC system. It is a requirement of the overall onboarding process to provide a disposition of every SPID in the existing NPAC system. When applicants provide their SPIDs with the NDA, it helps ensure that all SPIDs are accounted for. If you are uncertain as to the type of user that you are, you may contact the current LNPA to determine your user type. If you have a direct LSMS or SOA connection to the NPAC then you are considered a mechanized user. If you access the NPAC through a Service Bureau or through the LTI (including LTI Service Bureaus, IVR, helpdesk or as a user of NPAC ancillary services) then you are considered a non-mechanized user. Just like with the current LNPA, the new LNPA will require all users of NPAC/SMS data to complete an NDA. Whether this applies to your users or not, and the extent to which it applies, will be determined between you and the new LNPA during onboarding. All users of the NPAC/SMS, including PTRS, ELEP, and WDNC Service customers, must complete the required onboarding documentation to validate their appropriate usage of NPAC data. Note that the document execution process planned for onboarding will enable a proxy to fill out the data; however the authorized company user must still sign the agreements. Circuits may be ordered during the onboarding process. The start of onboarding varies by NPAC user group and adequate time will be Page 4 of 8

5 I am a Law Enforcement Agency, when do I onboard? How do we register for services? Is that the same as onboarding? made available for the ordering of circuits. iconectiv is expecting to begin onboarding Law Enforcement in late 2016 or early Registration for services is accomplished during onboarding. This includes the core NPAC/SMS services and all ancillary services like LEAP/ELEP, WDNC, and PortPS. 5. User Testing How can I participate in testing? Is testing mandatory? Do I need to order dedicated circuits to test? May I execute my own test cases? During the testing, will the iconectiv database be "live" and mirror the existing database or be a "mock" database? What QA (quality assurance) is iconectiv doing to ensure the NPAC is ready for testing? What are the entrance criteria for industry testing? Will VPN (Virtual Private Network) connections over the internet be allowed as the connection for testing? When will a draft version of the test cases be available? All NPAC users and users of NPAC data will have the opportunity to test after they have completed onboarding. Instruction will be provided on how to submit a request to establish access to the iconectiv test environment and to opt in for testing. Testing is mandatory for Vendors (SOA and LSMS). It is also mandatory for Service Providers, Service Bureaus and PTRS users with direct mechanized connections to the NPAC/SMS. Otherwise, testing is optional. A dedicated circuit is not required for testing. For mechanized system testing a VPN tunnel may be used. For LTI (web interface) a secure browser connection may be used with iconectiv-provided credential. Users with mechanized interfaces and Vendors will need to execute Industry Test Cases (ITCs) applicable to the parameters supported by their system. However, following the completion of the ITCs, iconectiv will support Group or Round Robin and Ad-Hoc testing for any user that wants to participate. During this period, users can execute their own test cases. iconectiv NPAC testing will include use of a live system operating with the Midwest Testbed Data as is used by the current NPAC. The new LNPA is required to test the new NPAC/SMS platform to validate that the platform meets the required industry specifications. Subsequently, Vendors, Service Providers and Service Bureaus who are required to test will certify with the new NPAC platform as they do today using the suite of known Industry Test Cases. IPSEC (Internet Protocol Security) VPN tunnels over the internet are permitted for testing. Industry Test Cases (ITCs) as developed by the LNPA working group will be used for vendor testing and for testing of NPAC users with mechanized interfaces. These test cases are currently available through Page 5 of 8

6 What iconectiv support will be offered if I wish to execute my own test cases? Which test cases do law enforcement agencies execute? I am an LTI user. Which test cases do I execute? What are industry test cases? Are these same as LNPA WG test cases? Will the network interconnections with iconectiv be in the same location as Neustar or different? When will these locations be identified? If my vendor tests, do I have to test? the NPAC website. iconectiv will provide industry test engineers and a help desk to facilitate the testing process. In addition, iconectiv will provide access to their test bed and will be available to answer questions as needed. iconectiv will develop acceptance test plans that describe test cases for execution by Law Enforcement Agencies. After completion of LTI training, users will have the option to execute a subset of the industry test cases. Industry test cases are those test cases defined by the LNPA Working Group (LNPA WG) in the NPAC/SMS Individual Service Provider Certification and Regression Test Plan document. If you are a vendor or are using a mechanized connection (whether Service Provider, Service Bureau, or PTRS), then you must execute the industry test cases. The network interconnection locations for the new LNPA production and test platforms are not the same as Neustar s current locations. During the onboarding process, the new LNPA will provide the details required for interconnection. Clarification of terms may be helpful: Vendors develop and sell local systems (LSMS/SOA) but do not operate them. Service Bureaus operate local systems (acquired from a Vendor) on behalf of Service Providers and PTRS. Note that some Vendors may separately operate a Service Bureau business. The Vendors LSMS and SOA products must be certified for proper function. However this is not the same as testing the actual in-service system as configured. So, once Vendor certification is complete, all of the local systems (LSMS/SOA) that connect to the NPAC must be tested to verify that their specific configuration and connection settings are being supported correctly. Testing for other users is optional. 6. Communications and Staying Informed Where can I get more information about the transition? Where can I ask questions? A variety of information sources are available: Information about the transition will be posted on the LNPA Transition tab at napmllc.org TOEP events will provide information about the LNPA transition progress The FCC periodically releases public notices about the transition The incoming LNPA vendor, iconectiv, will also be executing a communication plan to conduct outreach and education You may ask specific questions through the napmllc.org website in the Comments form under the LNPA Transition tab. All submissions Page 6 of 8

7 are routed to the Transition Oversight Manager (TOM) as well as the NAPM LLC. Where can we reach the TOM directly? Will the TOM interact directly with carriers? How can I contact the new LNPA (iconectiv)? Where can I learn more about the new LNPA in general? When is the next TOEP event? How can I access past TOEP webcasts? Who should attend TOEP events? Who is the intended audience? If you would like your question and the TOM's response published on the napmllc.org website, please include the text Publication Authorized as the first line of your submission. Due to the large number of stakeholders involved in the LNPA transition, direct input will be gathered using the NAPMLLC.org website in the Comments form on the LNPA Transition tab. The Transition Oversight Manager (TOM) will interact with carriers directly through the napmllc.org website and via the Transition Outreach and Education Plan (TOEP). The TOEP can be accessed at iconectiv may be contacted directly at LNPA-Acct- Mgmt@iconectiv.com for onboarding related questions and at lnpatransition@iconectiv.com for any generic LNPA transition related questions or comments. General information is available at TOEP webcast announcements are posted on napmllc.org along with a list of proposed events at which the TOM will provide a forum for outreach. Prior TOEP participants and those identified in TOEP mailing lists will receive updates by . To be added to the TOEP mailing list, visit the comments page at under the heading LNPA Transition by selecting the Comments option to the left of the page and request to be added to the TOEP mailing list. Audio recording, materials presented and the meeting notes from the TOEP webcast can be accessed at under the heading LNPA Transition by selecting the References Documents link on the left of the page. Any interested party is welcome to attend the events. The webcasts and in-person fora are the primary channels that will be used to communicate with the public in accordance with the Transition Outreach and Education Plan (TOEP) as described in the Transition Oversight Plan (TOP) issued 31-August The TOP can be accessed at The objectives of the TOEP webcasts are three-fold: 1. To provide transparent communications regarding the LNPA transition 2. To serve as an open forum to gather and understand your needs and concerns 3. To incorporate the feedback you provide to improve future Page 7 of 8

8 communications What are my options to meet with the TOM in person? Will the TOM attend any industry conferences or other events to answer questions for NPAC users? All transition stakeholders and interested parties are invited to attend. The TOM has presented at, and arranged face-to-face meetings convenient to, a number of industry events like the LNPA WG. The currently proposed list of events, conferences, and related meetings in 2016 is posted in the reference documents section of under the "LNPA Transition" tab. Some included events are CTIA, NTCA, NENA, APCO, and IACP. Page 8 of 8