Attachment iii. NANPA Transition Plan.pdf

Version 1.0 July 8, 2020

NANPA Transition Plan

NANPA Transition Plan Version 1.0

Somos Confidential and Proprietary 1 Contract Number: 273FCC19C0001

Table of Contents

1. Overview

1.1 Scope

1.2 System Overview

1.3 Document Overview

2. Description of the Transition

2.1 Transition Meeting

2.2 NANPA Processes and System Familiarization and Training

3. Notification to the Stakeholders

4. Records Transfer

5. Current System Functions and Transition Processes

5.1 Central Office (CO) Code Administration and NANPA Website Transition Plan

5.2.1 Functional Overview

5.1.2 System Overview

5.1.3 Relationship to NANPA and FCC Databases

5.1.4 Reference Documents

5.2 Numbering Resource Utilization/Forecast (NRUF) Reporting Transition Plan

5.2.1 Functional Overview

5.2.2 System Overview

5.2.3 Relationship to NANPA and FCC Databases

5.2.4 Reference Documents

5.3 NANP Resource Transition Plan

5.3.1 Functional Overview

5.3.2 System Overview

5.3.3 Relationship to NANPA and FCC Databases

Somos Confidential and Proprietary 2 Contract Number: 273FCC19C0001

5.3.4 Reference Documents

5.4 NPA Relief Planning Transition Plan

5.4.1 Functional Overview

5.4.2 System Overview

5.4.3 Relationship to NANPA and FCC Databases

5.4.4 Reference Documents

5.5 NANPA Director

5.6 Technical Operations Group

5.7 NANP Administration System (NAS) Transition

5.8 Central Office Code Administration Group

5.8.1 Functional Overview

5.8.2 Central Office Code Administration Functions Transition

5.8.3 Support Services

5.9 NANPA Website and Reports

5.9.1 Functional Overview

5.9.2 Reference Documents

5.9.3 Website and Reports Familiarization and Training

5.9.4 Transition

5.10 Numbering Resource Utilization/Forecast (NRUF) Functions

5.10.1 Functional Overview

5.10.2 Reference Documents

5.10.3 NRUF Transition

5.10.4 Support Services

5.11 NANP Resources Functions

5.11.1 Functional Overview

Somos Confidential and Proprietary 3 Contract Number: 273FCC19C0001

5.11.2 Reference Documents

5.11.3 NANP Resources Transition

5.11.4 Support Services

5.12 NPA Relief Planning Functions

5.12.1 Functional Overview

5.12.2 Additional Staffing

5.12.3 Reference Documents

5.12.4 NPA Relief Planning Transition

5.12.5 Support Services

6. NANPA Forum Participation

7. Transition Costs

8. Change History

Appendix A. NAS Licenses and Tools/System Transfer List

Appendix B. NANPA Records

Appendix C. Timeline

Appendix D. Glossary

Somos Confidential and Proprietary 4 Contract Number: 273FCC19C0001

1. Overview

1.1 Scope

In accordance with the current North American Numbering Plan Administration contract, Federal Communications Commission (FCC) Contract Number 273FCC19C0001, Somos, Inc.

(herein after Incumbent), as the North American Numbering Plan Administrator (NANPA), hereby submits this plan for the transfer of NANPA functions from Incumbent to a new Contractor. This document complies with the contractual requirements set forth in NANPA Technical Requirements (Technical Requirements), Section 2.15.4, Transition Plan, which states that:

The NANPA shall, 180 calendar days prior to contract termination, provide a detailed plan for an efficient and orderly transition. This transition plan shall follow the format, as applicable, of Reference 26, Software Transition Plan (STrP).

Reference to “the services continuity clause in Section I (52.237-03)” is found in NANPA Solicitation. Section 52.237 of the Federal Acquisition Regulations (FAR) reads as follows:

52.237-3 -- Continuity of Services.

(a) The Contractor recognizes that the services under this contract are vital to the Government and must be continued without interruption and that, upon contract expiration, a successor, either the Government or another contractor, may continue them. The Contractor agrees to-

(1) Furnish phase-in training; and

(2) Exercise its best efforts and cooperation to effect an orderly and efficient transition to a successor.

(b) The Contractor shall, upon the Contracting Officer's written notice, (1) furnish phase-in, phase-out services for up to 90 days after this contract expires and (2) negotiate in good faith a plan with a successor to determine the nature and extent of phase-in, phase-out services required. The plan shall specify a training program and a date for transferring responsibilities for each division of work described in the plan, and shall be subject to the Contracting Officer's approval. The Contractor shall provide sufficient experienced personnel during the phase-in, phase-out period to ensure that the services called for by this contract are maintained at the required level of proficiency.

(c) The Contractor shall allow as many personnel as practicable to remain on the job to help the successor maintain the continuity and consistency of the services required by this contract. The Contractor also shall disclose necessary personnel records and allow the successor to conduct on-site interviews with these employees. If selected employees are agreeable to the

Somos Confidential and Proprietary 5 Contract Number: 273FCC19C0001 change, the Contractor shall release them at a mutually agreeable date and negotiate transfer of their earned fringe benefits to the successor.

(d) The Contractor shall be reimbursed for all reasonable phase-in, phase-out costs (i.e., costs incurred within the agreed period after contract expiration that result from phase-in, phase-out operations) and a fee (profit) not to exceed a pro rata portion of the fee (profit) under this contract.

The objective of this Transition Plan is to ensure the continuity of NANPA functions in accordance with the appropriate requirements during the contract change. The plan will become operative only if a vendor other than the Incumbent is awarded the NANP Administration contract. This plan establishes a 90-day transition period from Incumbent to the newly selected vendor (hereinafter referred to as the “selected vendor”) that will commence on the date the FCC notifies Incumbent of the contract award to the selected vendor, and will enable the Incumbent to conduct pre-transition and actual transition activities. Transition time intervals for individual functions and services performed by the NANPA are established in this Transition Plan to allow for an effective migration of responsibilities to the selected vendor.

The following assumptions were used in the development of this Transition Plan:

• The selected vendor will assume all NANPA responsibilities over the course of the 90-day transition period;

• Incumbent NANPA will provide continuity of service support for a period of up to 45 days over a six-month period after the transition period;

• The selected vendor will provide the resources needed to carry out its obligations during the transition; and

• The selected vendor will be thoroughly conversant with all industry administration and assignment guidelines, the NANPA Requirements Document, and applicable federal and/or state directives pertaining to NANP administration.

If any of these assumptions are not met, the NANPA reserves the right to cease transition activities until the selected vendor resolves the deficiencies, after consultation and approval of the Contracting Officer.

Incumbent will transfer:

• Associated data and contracts;

• All system documentation specified in the System Documentation Plan;

• Application code from Incumbent’s current source code container, currently CodeCommit;

• All specifications with instructions to deploy NAS in an AWS environment;

Somos Confidential and Proprietary 6 Contract Number: 273FCC19C0001

• NAS data, records, and reports;

• NANPA operations files, records, and reports; and

• Copies of most recently delivered Contract Data Level Requirements (CDRLs).

Appendix A provides the specific software used in conjunction with the NANP Administration System (NAS) and indicates which licenses are transferable to the newly selected vendor.

Appendix B details the data records Incumbent will provide during transition.

1.2 System Overview

NAS is hosted on the Amazon Web Services (AWS) cloud platform under a master account transferable to the FCC when the Incumbent is no longer responsible for operating/maintaining the system. The current NAS architecture is configured with the primary region in US-EAST-1 and a disaster recovery location in US-WEST-2.

The North American Numbering Plan Administrator is responsible for the administration of NANP numbering resources and uses NAS as the primary system to carry out the following responsibilities.

NANP Resource Administration is the assignment and administration of various numbering resources (e.g., area codes, central office codes, Carrier Identification Codes) available via the NANP. These resources are added to, withdrawn from, and administered by NANPA Resource Administration staff using a number of industry-defined forms contained in assignment guidelines created by the Industry Numbering Committee (INC). In addition to defining the format of the forms, the Industry has also prescribed a sequence of events for each request, and strict time limits during which these events must occur.

Numbering Resource Utilization/Forecast (NRUF) reporting is the process by which those entities holding central office codes and one thousand (1K) blocks from geographic area codes report utilization and forecast information. Entities holding blocks of 10,000 in the area codes used for non-geographic services (i.e., 5XX NPA) and entities holding blocks of 10,000 in the ERC used for multiple carrier 900 access report utilization and forecast information. Using NAS, NANPA processes service provider NRUF submissions and collects, stores, and reports on number utilization and forecast data.

Area code relief planning is the process of identifying area code exhaust, developing various NPA relief alternatives, and submitting Industry consensus plans to state regulatory commissions. NAS provides the mechanism to effectively communicate to the Industry information concerning the development of NPA relief plans and their implementation.

NAS is a web-based system that enables:

• Service providers and NANP administration personnel to submit and process forms on-line;

Somos Confidential and Proprietary 7 Contract Number: 273FCC19C0001

• Automatic tracking of forms submitted, enabling service providers and NANPA to query and report on the status of applications and other submissions;

• Creation of a variety of reports available to NANPA and the Industry;

• Notifications on changes to assignment guidelines, NRUF requirements, report availability, client education, and system maintenance and availability.

NAS tracks and stores the following additional information:

• Session data (login times, number of users logged in, etc.);

• Volume Data (quantities of certain types of the Industry-approved forms submitted and issued, etc.);

• User Login and Passwords; and

• Additional user information contained in the user’s profile (i.e., company’s headquarters address, telephone number, email, etc.).

NAS supports a web-based GUI used by service providers to request resources and used by NANPA personnel for administering resources.

Users that interact with NAS include service providers, service provider consultants, federal and state regulators, NANPA personnel (resource administrators, NRUF administrators, and NPA relief planners), reports administrators, database administrators, and systems administrators.

Since NAS is a web-based system, the NANPA website and the domain names www.nanpa.com and www.nationalnanpa.com will also be transferred at the same time as the NAS function. The NANPA website contains an archive of data as well as all up-to-date information.

1.3 Document Overview

This document identifies the role of each functional group within the NANPA organization and addresses how and when those activities will be transferred to the selected vendor.

2. Description of the Transition

The transition will take place subsequent to the award of the new contract and will take no longer than 90 days. During the transition period, notification, records transfer, training, web site transfer, system transition, and assumption of NANPA responsibilities will occur. Plan Sections 3, 4, and 5 address those activities in more detail.

During the transition, the selected vendor will assume responsibilities for all numbering resources currently administered by Incumbent as the NANPA. These include:

• Numbering Plan Area (NPA) Codes;

Somos Confidential and Proprietary 8 Contract Number: 273FCC19C0001

• Central Office (CO) Code Administration within the U.S. NPAs;

• Non-Geographic 5XX-NXX Codes;

• 900 NXX Codes;

• N11 Service Codes;

• 800 855-XXXX line numbers;

• Carrier Identification Codes (CICs);

• Vertical Service Codes (VSCs); and

• ANI II Digits (Automatic Number Identification Information Integers).

The selected vendor will also assume responsibility for NPA Relief Planning in the United States and its territories and NRUF reporting. From contract award to service cutover, Incumbent will perform its current responsibilities as the NANPA.

Incumbent will designate a primary point of contact for transition activities. It is assumed that the selected vendor will also designate a primary point of contact for the transition. During the initial transition meeting, the respective points of contact will be identified.

This plan envisions a transition commencement meeting chaired by the FCC, during which parties will add any necessary further detail to this plan, specific to the situation, and will identify the specific dates for actions by both Incumbent and the selected vendor. This plan assumes that the selected vendor will be using the existing system and does not envision any modifications or enhancements to the existing NAS by the selected vendor.

2.1 Transition Meeting

It is anticipated that within one week of the contracting officer’s written notification to Incumbent, the FCC will facilitate a transition meeting between the selected vendor and Incumbent to:

• Develop a mutually agreeable schedule for the “NANPA Processes and System Familiarization and Training” and start date for the actual transition period;

• Define the roles and responsibilities of both the selected and incumbent vendors in the effective and efficient transfer of the NANPA functions; and

• Identify the information and training needs of the selected vendor.

Details of this plan may change during the transition meeting, either by mutual agreement of the parties, or at the direction of the FCC. All changes, modifications, or amendments to the plan must be in writing and must be approved by the FCC Contracting Officer.

Somos Confidential and Proprietary 9 Contract Number: 273FCC19C0001

2.2 NANPA Processes and System Familiarization and Training

As set forth in the timeline attached as Appendix C, Incumbent will provide the new vendor with an overview of and training for the NANPA processes and system and supply the new vendor with information needed to operate NAS and to assume the duties of the NANPA. The new vendor’s information needs shall be determined and agreed to at the transition meeting.

Incumbent will, if requested, provide up to 45 working days of technical support over a six– month period after the transition period.

3. Notification to the Stakeholders

Notification to Industry members and regulators of the transition of NANPA functions from Incumbent to the selected vendor will be the responsibility of and performed by the selected vendor in a coordinated effort between Incumbent and the selected vendor through a variety of mechanisms, including e-mail distribution via the NAS NANP Notification System, a notice posted to the NANPA web page, and FCC-approved press releases. Coordination between Incumbent and the selected vendor will be necessary to ensure proper notification is provided because the NANPA’s location, phone numbers, fax numbers, and e-mail addresses will change during the transition.

4. Records Transfer

All paper and electronic NANPA records will be transferred to the selected vendor at the direction of the FCC. These records include those items specifically identified in this Transition Plan as well as records listed in Appendix B. The selected vendor will be responsible for all reasonable and necessary costs associated with packaging and delivery of paper and electronic records and portable data files.

5. Current System Functions and Transition Processes

5.1 Central Office (CO) Code Administration and NANPA Website Transition Plan

5.2.1 Functional Overview

Central Office (CO) Code Administration administers central office codes in the United States and its territories using federal and state regulatory directives, the NANPA Technical Requirements Document, and Industry-developed guidelines (Central Office Code [NXX] Assignment Guidelines - COCAG). Code administration responsibilities include maintaining records of all central office code assignments, receiving and processing applications for central office code assignments, and preparing and providing reports on central office codes.

The NANPA web site (wwwnationalnanpa.com) serves as the repository for assignment information, as well as the place to look for updates on relief planning and the introduction of new area codes. In addition, the site serves as a gateway for entry into NAS. Updates to the NANPA web site are made on a real-time as well as daily basis.

http://www.nanpa.com/

Somos Confidential and Proprietary 10 Contract Number: 273FCC19C0001

The NANPA also maintains the North American Numbering Council (NANC) Chair web site (www.NANC-Chair.org) which serves as a repository for documentation used by the NANC. The present size of this web site is 688 megabytes (MB).

5.1.2 System Overview

The main NAS functionality for CO Code Administration includes:

• To create, store, execute, and administer Industry-defined forms by electronic means accessible to users via a connection to the World Wide Web.

• To generate reminder notices to Code Administrators and service providers (SPs) when time limits for events near expiration.

• To manage the inventory of central office code resources, as central office codes are changed, added to, or withdrawn from them.

• To minimize the amount of information service providers and code administrators are required to manually populate in the system. Each user will create a profile that will be automatically invoked by NAS whenever the user logs in and will be used to auto-populate the appropriate fields in the forms that the user accesses. As a user migrates from one form to another, any fields on the new form that are identical to or can be derived from fields on an earlier form, will also be auto-populated.

The two principal users of NAS CO Code Administration functionality are the service providers and the NANPA Code Administrators. The service providers are external users who utilize the CO codes. The Code Administrators are internal users who assign and administer the codes.

The following Industry-defined forms govern the majority of the interactions between these two types of users and NAS:

• Part 1;

• Part 3;

• Part 4;

• Part 4-PA;

• Part 5; and

• MTE (Months To Exhaust – TN Level and Block Level.

NAS external users can submit forms via:

• Web-enabled GUI;

http://www.nanc-chair.org/

Somos Confidential and Proprietary 11 Contract Number: 273FCC19C0001

• Secure FTP site (applies only to those Part 1s submitted through the Pooling Administration System - PAS); and

• Fax or e-mail.

The NANPA’s role is to ensure service providers’ requests for resources are met in a timely and impartial manner, and in accordance with regulatory mandates and the COCAG. NAS continuously and automatically performs a number of administrative functions, including sending out Part 4 (in-service confirmation) reminders and delinquent notices as well as automatically keeping track of the availability and status of codes in a geographic area code.

External users that interact with NAS for CO Code Administration purposes include:

• Service providers and service provider consultants;

• Federal Communications Commission users; and

• State commission users.

Internal personnel that maintain NAS profiles for CO Code Administration purposes include:

• Director, NANPA;

• Code Administrators;

• NPA Relief Planners;

• Customer Service Representative; and

• Manager, Data Analysis.

5.1.3 Relationship to NANPA and FCC Databases

A CO code and/or thousands-block applicant must have a current NRUF Form 502 on file with NANPA before it can receive a CO code. Code Administrators have access to the latest service provider NRUF submission data via NAS.

Code and Block applicants on the FCC Delinquent in Debt Owed the FCC (Red Light) list must be denied CO code and Thousands-block assignments. In order to comply with the Red Light rule, NANPA has a user name and password to access the FCC FTP site and download the FTP file of delinquent FRNs. The file is updated every calendar day, and NAS retrieves the Red Light file every day. NAS then compares the FRNs appearing on the FCC Red Light list with the FRNs appearing in NAS NRUF data for the current reporting cycle (either Aug 01/XXXX or Feb 01/XXXX). NAS creates a file of OCNs with their associated FRN which have been identified as delinquent. This file is imported into NAS in order to flag work items which have a corresponding OCN. NAS also delivers the same file on a daily basis to an intermediate server where PAS picks up the file and imports into PAS.

Somos Confidential and Proprietary 12 Contract Number: 273FCC19C0001

5.1.4 Reference Documents

All documents required to be provided to the selected vendor during the transition process are listed in Appendix B.

5.2 Numbering Resource Utilization/Forecast (NRUF) Reporting Transition Plan

5.2.1 Functional Overview

NRUF reporting is a semi-annual process whereby service providers submit utilization and forecast information to NANPA for use in the development of NPA and NANP exhaust projections. NANPA collects and stores this information on an on-going basis and provides this information to the FCC and state commissions. Service providers are required to report by February 1 and August 1 of each year. Service providers may submit updates and corrections to previous submissions throughout the year.

5.2.2 System Overview

NAS collects, sorts, and stores NRUF data submitted by service providers. Data may be sent via e-mail (i.e., Excel spreadsheet), Electronic File Transfer (EFT) file format, or it may be entered directly into NAS using a web-based GUI. NAS provides error-checking capabilities to ensure specific, required information has been provided. Any errors identified are documented and an e-mail is generated to those service providers that submitted filings (via EFT or excel spreadsheet) with errors. The e-mail indicates the specific error(s) detected and the need to correct these errors for numbering resources to be assigned to the service provider. These e-mails also contain the name and contact information of the NANPA employee the service provider can contact to discuss these errors and seek additional information.

NAS also generates NPA and statewide reports in Excel and Microsoft Access 2000 for use by state public service commissions that have appropriate confidentiality protections in place.

Reports provided to state commissions contain disaggregated service provider-specific NRUF data for carriers operating in the respective states. In addition, NAS provides status information to allow the NANPA to determine whether the required NRUF Form is on file for the OCN listed on any central office code application.

5.2.3 Relationship to NANPA and FCC Databases

NAS produces a daily listing of all service providers that have submitted an NRUF. CO Code and 5XX/900 Administration use this information to determine if a code applicant has a forecast on file for the location (e.g., NPA and/or rate center) in which it is requesting a CO code or 5XX/900-NXX code(s). Such information is required in order for a CO code or 5XX/900 code(s) to be assigned.

NRUF information is also used to identify service providers on the FCC Delinquent in Debt Owed the FCC (Red Light) list. On a daily basis, NAS accesses the FCC FTP file containing delinquent FCC Registration Numbers (FRNs). NAS then compares the FRNs in the FTP file

Somos Confidential and Proprietary 13 Contract Number: 273FCC19C0001 with the FRNs reported via the NRUF reporting process. This comparison permits the identification of the Operating Company Number(s) (OCNs) associated with the FRN. NAS generates a report of OCN(s) that are ineligible to receive numbering resources due to the appearance of their FRN on the FCC delinquent list. NAS alerts the Code Administrator to any requests in the assignment queue that are on the Red Light list, in order for the Code Administrator to deny any such request.

5.2.4 Reference Documents

All documents required to be provided to the selected vendor during the transition process are listed in Appendix B.

5.3 NANP Resource Transition Plan

5.3.1 Functional Overview

NANPA administers a variety of NANP numbering resources. These include area codes, carrier identification codes (CICs), 5XX-NXX codes, 900-NXX codes, 800-855 line numbers, ANI II digits, vertical service codes (VSCs), and N11 codes.

5.3.2 System Overview

Current assignment records for active resources are maintained in commonly used personal computer database systems as shown in the table below. As such, these databases are self-documenting. This information is uploaded into NAS whenever there is a change in the status of the resource.

Resource Database Software

Carrier identification codes FileMaker PRO 5.5

900-NXX FileMaker PRO 5.5

Assignments of N11 codes, VSCs, and 800-855 line numbers and ANI II digits are listed and maintained on the NANPA web site.

The main NAS functionality as they relate to NANP Resource Administration are similar to those of CO Code Administration:

• To create, store, execute, and administer Industry-defined forms by electronic means accessible to users via a connection to the World Wide Web.

• To generate reminder notices to Resource Administrators and service providers when time limits for events near expiration.

Somos Confidential and Proprietary 14 Contract Number: 273FCC19C0001

• To minimize the amount of information service providers and resource administrators are required to manually populate in the system. Each user will create a profile that will be automatically invoked by NAS whenever the user logs in and will be used to auto-populate the appropriate fields in the forms that the user accesses. As a user migrates from one form to another, any fields on the new form that are identical to or can be derived from fields on an earlier form, will also be auto-populated.

The two principal users of NAS resource administration functionality are service providers and NANPA staff. The following Industry-defined forms govern the majority of interactions between these users and NAS:

• Application Form (Part 1, Part A);

• Assignment Form (Part 3, Part B; and

• In-Service Confirmation Form (Part C).

NAS external users can submit forms via:

• Web-enabled GUI; and

• Fax or e-mail.

The NANPA’s role is to ensure service providers’ requests for resources are met in a timely and impartial manner, and in accordance with regulatory mandates and Industry guidelines.

External users that interact with NAS for NANP resource administration purposes include:

• Service providers;

• Service provider consultants;

• Canadian Numbering Administrator; and

• Federal Communications Commission users.

Personnel that maintain NAS profiles for NANP resource administration purposes include:

• Manager, NANP Resources;

• Manager, NPA Relief Planning;

• Manager, NRUF/Sr. NRUF Administrator;

• Code Administrators/Customer Service Representative;

• Senior Data Analyst; and

Somos Confidential and Proprietary 15 Contract Number: 273FCC19C0001

• NANPA Director.

5.3.3 Relationship to NANPA and FCC Databases

5XX/900 NXX code administration has available all service providers that have submitted NRUF forecasts to assist in the processing of applications for new codes. Code applicants must have an “NRUF on file” in order for a 5XX/900 code to be assigned.

5.3.4 Reference Documents

All documents required to be provided to the selected vendor during the transition process are listed in Appendix B.

5.4 NPA Relief Planning Transition Plan

5.4.1 Functional Overview

NPA Relief Planning is conducted in accordance with applicable state and federal regulatory orders and Industry guidelines. The primary functions of NPA Relief Planning involve determining the need for relief, notifying appropriate local Industry and state regulators of this need, and convening a preliminary meeting to discuss local dialing, communities of interest, and other pertinent issues. Relief planners then develop various relief alternatives and distribute an Initial Planning Document, conduct Industry meetings, attempt to attain consensus on the selection of one or more relief alternatives, produce meeting minutes, submit a petition to the responsible state regulator on behalf of the industry for approval of a relief plan, and facilitate an initial implementation meeting after a relief plan has received regulatory approval.

5.4.2 System Overview

NPA relief planning uses the NAS NANP Notification System (NNS) to provide notifications and documents relating to NPA relief planning activities. The system permits users to sign up and receive notifications on a state-by-state basis. Documentation such as meeting notifications, planning letters, meeting minutes, and regulatory filings are available for download in Adobe Portable Document Format (PDF).

5.4.3 Relationship to NANPA and FCC Databases

NPA relief planners obtain information concerning code processing activity as input on NPA relief alternatives and jeopardy assignment procedures.

5.4.4 Reference Documents

All documents required to be provided to the selected vendor during the transition process are listed in Appendix B.

Somos Confidential and Proprietary 16 Contract Number: 273FCC19C0001

5.5 NANPA Director

The Director, NANPA, has ultimate responsibility for the entire NANPA program, including the accuracy and timeliness of its deliverables, budget, payroll, compliance with the FCC and Industry requirements, performance evaluations, and the supervision, hiring, and training of a staff which includes the Central Office Code Administration Group, the NRUF Administration Group, the NANP Resources Administration Group, the NPA Relief Planning Group, and the Technical/Operations Group.

As needed, the Director interfaces with all internal and external customers, both regulators and Industry, to resolve all customer service issues. Additionally, the Director attends and participates in Industry groups meetings.

5.6 Technical Operations Group

The Technical Operations Group is composed of the Director, Software Development and the Software Development and Application Support Team.

The Technical Operations Group supports NAS with information and troubleshooting required for issues with customers and/or the system and creates and maintains custom applications.

Further, it maintains the NAS servers; keeps the operating system and software current; and assists end users with testing, troubleshooting, networking, and security concerns. This Group also performs software upgrades and updates, advises the team when updates are needed, maintains the testing environment, and deploys applications by upgrading the source code in

NAS.

This Group ensures the completion of the annual security training required by the contract and assists in the periodic reviews of the Security Plan and the Business Continuity/Disaster Recovery Plan.

5.7 NANP Administration System (NAS) Transition

The transition of all system components and functionality without any down time is critical. It is assumed that the new vendor will be capable of obtaining any user licenses for software without interruptions in service. In accordance with the agreed upon timeline, Incumbent will operate the system until the new vendor successfully cuts over NAS.

Incumbent proposes the following high-level transition approach for the transfer of the systems over the 90-day transition period, as reflected in more detail in Appendix C:

• Incumbent to review new Contractor’s transition plan and provide feedback and/or acceptance;

• Initial training session on NAS applications, website, and database structures;

• Execution of new Contractor’s Transition Plan;

Somos Confidential and Proprietary 17 Contract Number: 273FCC19C0001

• System cut over; and

• Post cutover activities/support.

Incumbent’s technical support team will conduct a two-week technical educational session for the selected vendor’s technical support team. The first part of the training will focus on system architecture, application code and database modules for NAS. Thereafter, a portion will be devoted to a review of web content management and reports generated by third party tools from NAS. Finally, a portion will focus on system administration support and review of service level agreements.

Incumbent will be available for technical support (i.e., answer questions, attend transition meetings, provide any system documentation and data, execute on agreed upon transition tasks) during execution of Contractor’s transition Plan. As stated previously, the processing of all NAS applications during this period will still be Incumbent’s responsibility.

Near the end of the transition period, when notifications have been made and the selected vendor is ready to handle live NAS transactions, a cutover period will begin. After systems review, testing, and transition are complete, based on a set of Go/No-Go criteria, the FCC will authorize the cutover of NANP administration responsibilities from Incumbent to the selected vendor. This will occur on a weekend approximately 85 days into the transition.

During this weekend, Incumbent and the selected vendor will perform a cutover. This cutover will consist of the final handoff from Incumbent to the new vendor of all AWS access keys, or if necessary, a direct data transfer of all live data from the NAS AWS cloud platform to the selected vendor’s primary server.

5.8 Central Office Code Administration Group

5.8.1 Functional Overview

The Central Office (CO) Code Administration Group consists of the Director, NANPA, three Code Administrators and one AOCN Administrator. The Director, NANPA serves as the Industry Interface Representative. All three Code Administrators assume the Customer Service Representative role. The staff is located in Herndon, VA.

The Director, NANPA is responsible for the day-to-day operation of CO Code Administration and the NANPA AOCN Enterprise service. The Other Resources, NPA Relief Planning, and NRUF Managers currently report directly to the Director. The main responsibilities of the Director include, but are not limited to, overseeing the staffing, handling escalated issues, evaluating current workflows, and identifying process improvements where needed. The Director develops and maintains methods and procedures as well as user guides for the CO Code Administration operations to ensure all CO Code Administration personnel perform their functions in compliance with Industry guidelines and the NANPA technical requirements. The Director performs code administration and AOCN service and works with service providers to resolve customer outage issues and data discrepancies. The Director works with NPA Relief

Somos Confidential and Proprietary 18 Contract Number: 273FCC19C0001

Planning to ensure the adequate supply of CO Codes (NXXs) and participates in the NPA relief planning process.

The Director also acts as the Industry Interface Representative (IIR) attends industry meetings such as the INC on behalf of NANPA (see Section 6). The IIR identifies how issues at these meetings affect the NANPA, provides real-time input on the impact of proposed INC issue resolutions on NANPA systems and operations, submits issues and associated contributions to address number resource administration matters, and generally represents the NANPA as the subject matter expert.

The Code Administrators (CAs) process Part 1, Part 4 and Part 4A applications for all geographic area codes in the U.S. and its territories (over 300 area codes). The types of requests the CAs process are applications for initial codes, growth codes, code modifications (e.g., OCN, rate center and switch changes, rescheduling an effective date, etc.), code transfers, and code disconnects. The CAs also manage the code return, reclamation, and abandoned process, per the CO Code Guidelines Appendix C process. The CAs also respond to inquiries by e-mail or telephone.

The Customer Service Representative (CSR) provides technical and non-technical support to internal and external customers in problem resolution. The CSR monitors trouble tickets to ensure timely resolution of problems and escalates issues in a timely manner. Additionally, the CSR handles creation, deletion, and maintenance of NAS user accounts and passwords.

The AOCN Administrator is responsible for entering rating and routing information into the iconectiv Business Integrated Routing & Rating Database System (BIRRDS) on behalf of service providers that contract with NANPA for this service. NANPA provides this service per the NANPA Requirements Document as an “Enterprise Service.”

5.8.2 Central Office Code Administration Functions Transition

The transition of CO Code Administrator functions will commence on the first day of the transition period, as determined at the commencement meeting. As identified in the timeline by Incumbent after the start of transition, and continuing for a period of approximately 10 business days from days 28 through 32, and from days 35 through 39 (see the Incumbent transition timeline), CO Code Administration personnel will provide an overview of the NAS from the perspective of the Code Administrators, its current operation, and a demonstration of how the current NAS internal GUI and the NAS external GUI work. The training will cover the manual functions and NAS functions used by CAs to process Part 1s and perform reclamation functions, as well as NANPA interactions with the Pooling Administrator (PA), the NPAC, and iconectiv.

Additionally, this training will contain sessions concerning the Customer Service Representative, Industry Interface Representative, and AOCN training.

During the training session on the Code Administrators’ processes and their use of NAS, CO ode administration personnel will process applications side-by-side with the representatives of the selected vendor to familiarize them with the existing processes. This will include explaining the processing differences between applications for initial and growth codes, the necessary review of paperwork, how to handle requests from the PA, requests for modifications, code reclamation processes, and manual applications, and how to respond to inquiries by e-mail or telephone.

Somos Confidential and Proprietary 19 Contract Number: 273FCC19C0001

This training activity will take place at Incumbent’s VA offices using the Code Administrator’s facilities and equipment.

During this time, the selected vendor will have the opportunity to become familiar with NAS functionality and begin to understand CO code processing functions. Incumbent will provide the selected vendor with a copy of all relevant documentation in electronic form. Since critical work functions performed by the CAs must continue on a daily basis, these training sessions may require careful scheduling and/or the use of backup CO Code Administration personnel during this training process. The inability of the selected vendor to properly schedule such sessions may result in overtime charges being required.

This process will occur under the direct supervision of the Director, NANPA. During the overlap period, the selected vendor’s administrators must recognize and take control of the documentation related to all applications associated with CO Code Administration (assignments, suspensions, changes, reclamation, etc.).

After this training session, on a date identified by Incumbent and the selected vendor, and noticed to the users, the selected vendor will assume responsibility for the CO Code Administration process at its own facilities. All applications and submissions will be directed to the new vendor. The selected vendor will be required to follow-up on any outstanding notifications to service providers concerning errors in their Part 1 submissions. Incumbent will either forward any CO Code Administration-related information, applications or submissions that Incumbent may receive on or after that date to the selected vendor or will refer the submitting party directly to the selected vendor.

The selected vendor will be responsible for ensuring documentation is moved to its facility, upon a date agreed to by both parties and the FCC, but this date shall not be later than three business days after the last day Incumbent accepts and processes applications.

Documents that will be provided to the successor are listed in Appendix B and organized, to the extent possible, by function.

The following supporting documentation will also be provided to the selected vendor:

• CO code applications and related documentation as posted on the ATIS website;

• General correspondence (letters for regulators, users, etc.); and

• Correspondence and orders from regulators.

5.8.3 Support Services

Hardware

The CO Code Administration group currently uses MacBook Pro laptops and office printer/copiers. This equipment is Corporate Incumbent equipment and does not transfer to the selected vendor.

Somos Confidential and Proprietary 20 Contract Number: 273FCC19C0001

Software

The CO Code Administration group uses a variety of software products, all of which are either standard purchased software products or are programs using those same off-the-shelf software products. This software is Corporate Incumbent equipment and does not transfer to the selected vendor.

Other Resources

The CO Code Administration group currently uses other resources that include BIRRDS and the LERG, which are products of iconectiv. The CA uses the BIRRDS database when assigning, modifying, or disconnecting codes. The CA updates the ACD screen with information associated with a code. A copy of the LERG, which is an output of BIRRDS, is sent to NANPA monthly.

The selected vendor will have to make provisions to obtain these elements as they are not transferable.

5.9 NANPA Website and Reports

5.9.1 Functional Overview

The NANPA website contains a variety of information concerning the various NANP numbering resources administered by the NANPA. The website contains dropdown menus for navigation of the site and real-time reports containing up to the minute assignment and availability information. The website also serves as the gateway to NAS.

The NANPA website contains a number of reports available to the public. All of these reports are either automatically generated by NAS or created off-line and posted to the website.

NANPA is also responsible for the management of the website used by the Chair of the NANC for posting presentations, documentation and other material used by this Federal Advisory Committee. The website is accessible via www.NANC-Chair.org.

5.9.2 Reference Documents

The information contained on the NANPA website is in accordance with the NANPA Technical Requirements Document, dated August 2018.

5.9.3 Website and Reports Familiarization and Training

The NANPA website is publicly available and thus readily available to any vendor interested in serving as the NANPA. As such, any potential vendor can presently search the website to understand its layout and become knowledgeable on where specific information is found.

http://www.nanc-chair.org/

Somos Confidential and Proprietary 21 Contract Number: 273FCC19C0001

5.9.4 Transition

During the transition period, NANPA personnel will conduct a 1/2 day training session on the website, with a specific focus on report generation. The training will take place on day 38 of the Incumbent transition timeline (see Appendix C).

During the transition period, Incumbent will continue to prepare and distribute required reports to the FCC and state regulators until the selected vendor takes over responsibility for each report. Any reports scheduled for production after the transition period will be the responsibility of the selected vendor. Upon completion of the transfer of the NAS, the selected vendor must assume the responsibility of generating all new and existing reports.

5.10 Numbering Resource Utilization/Forecast (NRUF) Functions

5.10.1 Functional Overview

The NRUF group includes the NRUF Manager and Senior NRUF Administrator. This group is responsible for overseeing NRUF reporting, which is a semi-annual process whereby service providers submit utilization and forecast information to NANPA for use in the development of NPA and NANP exhaust projections. NANPA collects and stores this information on an on-going basis and provides this information to the FCC and state commissions. Service providers are required to report by February 1 and August 1 of each year, although service providers regularly submit updates and corrections to previous submissions throughout the year.

The NRUF group handles the following essential functions:

• Processes NRUF Form 502 submissions, identifies any errors or anomalies in service provider submissions, and sends appropriate notification to the carrier. This includes working with the service provider to help understand the errors and any corrective action necessary.

• Educates service providers on the use of the Form 502 and the various submission methods available.

• Generates NPA and statewide reports for use by the FCC and those state public service commissions that have appropriate confidentiality protections in place. Reports provided to state commissions contain disaggregated service provider specific NRUF data for those carriers operating in the respective states.

• Provides refresher training for state commission representatives on how to access NAS and use the NRUF data and reports available to them via the system.

5.10.2 Reference Documents

The following documents relate to ongoing NRUF activities and will be provided to the successor. These documents are in addition to the documents found in Appendix B:

• NRUF Job Aids (latest version available at time of transfer);

Somos Confidential and Proprietary 22 Contract Number: 273FCC19C0001

• Form 502 (geographic and non-geographic);

• Semi-annual NRUF databases;

• Service provider NRUF Form 502 submissions;

• State letters providing assurance of appropriate confidentiality protections in place (paper only);

• State Database Job Aid (latest version available at time of transfer);

• Latest NPA exhaust model; and

• Latest NANP exhaust model.

5.10.3 NRUF Transition

The NRUF group will meet with representatives of the selected vendor for three business days, specifically on days 49 through 51 of the transition (see the Incumbent transition timeline, Appendix C) at a location chosen during the initial transition meeting. Specifically, the training will consist of an overview of the NAS NRUF capabilities, the current operation, and a demonstration of how the system works. During the training session on NRUF processes and the use of NAS, NRUF personnel will process Form 502 submissions side-by-side with the representative(s) of the selected vendor to familiarize them with existing processes.

A training session will be conducted on the NPA and NANP exhaust models. This training will take place on the same days as the NRUF training session. The Data Analysis Manager involved in the development of NPA and NANP exhaust projections will conduct this training.

After this training session, on a date identified by Incumbent and the selected vendor, and noticed to the users, the selected vendor will assume total responsibility for the NRUF process at its own facilities. All NRUF Form 502 submissions will be directed to the new vendor. The selected vendor will be required to follow-up on any outstanding notifications to service providers concerning errors in their NRUF submissions. Incumbent will either forward any NRUF-related information or submissions that Incumbent may receive on or after that date to the selected vendor or will refer the submitting party directly to the selected vendor.

5.10.4 Support Services

Hardware

The NRUF group currently uses Microsoft Windows-based laptops and office printer/copiers.

This equipment is Corporate Incumbent equipment and does not transfer to the selected vendor.

Somos Confidential and Proprietary 23 Contract Number: 273FCC19C0001

Software

The NRUF group uses a variety of software products, all of which are either standard purchased software products (Windows 10 Professional) or are programs using those same off-the-shelf software products. This software is Corporate Incumbent equipment and does not transfer to the selected vendor.

5.11 NANP Resources Functions

5.11.1 Functional Overview

The NANP Resource Administration Manager, NANP Resources is responsible for administration of the following resources: area codes, carrier identification codes (CICs); 5XX- NXX codes; 900-NXX codes; 800-855 line numbers; ANI II digits; vertical service codes (VSCs); and N11 codes. The Manager is located in a virtual office.

The Manager, NANP Resources handles the following essential functions:

• Processing applications for resources mentioned above and maintaining a database and other supporting documentation associated with assignment of the resource;

• Analyzing semi-annual service provider utilization and forecast reports for 5XX/9YY, semi-annual Entity and Access Provider reports for CICs, and identifying resources that may be subject to reclamation;

• Initiating reclamation of resources as defined by Industry guidelines and FCC directives; and

• Responding to inquiries by phone or e-mail from service providers and other entities regarding these resources.

5.1…