The NANP Administration System (NAS) is a system used to submit various numbering resource applications, collecting numbering resource utilization, and forecast data and issuing notifications on numbering related matters.

Service providers that are authorized to direct access to numbering resources by the appropriate regulatory authority. Regulatory bodies and entities that have oversight on numbering and 911 related matters.

All consultants who register as a new NAS user must have a letter of authorization (LOA) on file for each service provider for whom they intend to submit requests.  The LOA shall:

• be on the SP client’s company letterhead,
• provide the date the letter is signed,
• list the authorized consultant’s name (or consultant company name)
• specify that the consultant is authorized to access NAS on the SP’s behalf
• identify all Operating Company Numbers (OCNs), Parent Operating Company Numbers (OCNs), National Emergency Number Association (NENA)IDs, and Interexchange Access Customers [IACs aka Access Customer Name Abbreviation (ACNA)] under the ownership of the SP client that the SPC user has authorization to add to their user profile and submit and view data for in NAS, and
• be signed by an authorized representative (e.g., officer of the company) of the SP client.

The LOA should be emailed to support@nanpa.com.

When an LOA is not on file for the SP client, the registration shall be rejected. When one or more Operating Company Numbers (OCNs), National Emergency Number Association (NENA)IDs, and Interexchange Access Customers [IACs aka Access Customer Name Abbreviation (ACNA)] under the ownership of the SP client is missing from the LOA, the item missing shall be removed from the SPC user’s registration.

Usernames and passwords cannot be shared. If NANPA determines that you are sharing your username and password, the account will be immediately disabled.

From the NAS log in screen, select Forgot Password to request a temporary password.

From the NAS log in screen, select Forgot Username to request your username.

Usernames cannot be changed.

Contact NANPA Customer Support at 1-866-623-2282.

NAS passwords expire every 180 days from the date of issuance. You will receive an email notification 30 calendar days prior to password expiration. You must log in to NAS and reset your password within 30 calendar days of receiving the initial “Password Expiration” notification.

The system will automatically log you out of the system after 20 minutes of inactivity, however, it will provide a warning, 5 minutes prior to logging you out, which you can extend by selecting “OK”. 

All reporting carriers must submit an NRUF Form 502 semi-annually, on or before February 1 for the preceding 6-month reporting period ending on December 31, and on or before August 1 for the preceding 6-month reporting period ending on June 30.

All carriers that receive numbering resources from NANPA, must report utilization and forecast data. In addition, carriers that receive intermediate numbers must report utilization data for such numbers in their inventories.

There are three submission methods supported by NAS: REST API interface (Application Programming Interface), SFTP interface (Secure File Transfer Protocol) and web-based User Interface.

To submit an NRUF Form 502, you must be a registered user of NAS and the account must be in an active status. 

You can locate this information on the website, by going to Thousands-Block Reports, select NPA/Rate Center Reports. Then select the state and NPA and click Submit. This will bring up a list of rate centers with their current pooling status. To view the Rate Center Pooling Status Designations, select the Rate Center Pooling Status Designations Defined on the Thousands-Block Reports page.
 

Submit an email to NANPA Customer Support at support@nanpa.com, and state that this is a request to update the status for an Excluded rate center to Optional pooling.
 

Once you’ve submitted a thousands-block forecast or a thousands-block disconnect, then you cannot withdraw from pooling in an optional rate center.

We recommend that you query the NPAC to determine the contamination status of a thousands-block. For assistance with performing the NPAC queries, contact the NPAC help desk at 844-820-8039.

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 11.3.12, the following steps should be taken based on the scenario:

1. Scenario 1: The Part 3 has been issued and the Non-pooled CO Code disconnected was approved and the Effective Date has not yet been reached.
   1. The SP shall to cancel the disconnect in NAS in order to cancel the disconnect view on the ACD in BIRRDS. 
   2. The SP shall take the appropriate steps to cancel the disconnect view on the NXD in BIRRDS.
   3. It is recommended that the SP contact the TRA to negotiate the issuance of an Emergency Notification.  
       
2. Scenario 2: The Part 3 has been issued and the Non-pooled CO Code disconnect was Approved and the Effective Date of the disconnect has passed.
   1. The SP shall re-request the CO Code through NAS by submitting a Part 1.
   2. The SP shall initiate contact with NANPA and the appropriate regulatory authority to get the disconnected CO Code re-Assigned.
   3. The SP shall take the appropriate steps to reestablish the Non-pooled CO Code in BIRRDS.
   4. The TRA shall issue an Emergency Notification if the Effective Date is fewer than 45 calendar days from when the CO Code is reestablished in BIRRDS.
       
3. Scenario 3: A Part 3 suspension has been issued and the Non-pooled CO Code disconnect was suspended to check for or due to ported TNs.
   1. The SP shall notify NANPA via email to cancel the disconnect in NAS.<
       
4. Scenario 4: The Part 3 Non-pooled CO Code disconnect denial has been issued to the disconnecting SP because a Part 3 transfer Approval has been issued to a new CO Code Holder.
   1. The disconnecting SP shall contact NANPA and the new CO Code Holder to obtain their approvals to cancel both the disconnect and the new assignment in NAS. NANPA shall cancel the scheduled transfer on the ACD in BIRRDS if the Effective Date has not passed or modify the ACD in BIRRDS assigning the Non-pooled CO Code back to the disconnecting SP if the Effective Date for the transfer has passed.
   2. The disconnecting SP shall contact TRA to change the AOCN on the CO Code record in BIRRDS and ensure that the Non-pooled CO Code is provisioned in BIRRDS with the appropriate information.
   3. The disconnecting SP and the new CO Code Holder shall ensure the transfer has been reversed with regard to NPAC changes.

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 11.2.13, the following steps should be taken based on the scenario:

1. Scenario 1: The Part 3 has been issued and the Pooled CO Code disconnect was Approved and the Effective Date has not yet been reached.
   1. The SP shall cancel the disconnect in the NAS in order for NANPA to cancel the disconnect view on the ACD in BIRRDS.
   2. The SP shall take the appropriate steps to cancel the disconnect view in BIRRDS.
   3. It is recommended that the SP contact the Telecom Routing Administration (TRA) to negotiate the issuance of an Emergency Notification. 
       
2. Scenario 2: The Part 3 has been issued and the Pooled CO Code disconnect was Approved and the Effective Date of the disconnect has passed. 
   1. The SP shall initiate contact with the NANPA and the appropriate regulatory authority to get the disconnected Pooled CO Code re-Assigned.
   2. The SP shall re-request the Pooled CO Code through NAS by submitting a Part 1.
   3. The SP shall take the appropriate steps to reestablish the Pooled CO Code in BIRRDS.
   4. The TRA shall issue an Emergency Notification if the Effective Date is fewer than 45 calendar days from when the Pooled CO Code is reestablished in BIRRDS.
       
3. Scenario 3: A Part 3 suspension has been issued and the Pooled CO Code disconnect was suspended to check for ported TNs or due to ported TNs.
   1. The SP shall notify the NANPA via email in order to cancel the disconnect.
       
4. Scenario 4: The Part 3 Pooled CO Code disconnect denial has been issued to the disconnecting SP because a Part 3 transfer Approval has been issued to a new CO Code Holder. 
   1. The disconnecting SP shall contact the NANPA and the new CO Code Holder to obtain their approvals to cancel both the disconnect and the new assignment.  NANPA shall cancel the scheduled transfer on the ACD in BIRRDS if the Effective Date has not passed or modify the ACD in BIRRDS assigning the Pooled CO Code back to the disconnecting SP if the Effective Date for the transfer has passed. 
   2. When applicable, the NANPA shall cancel the scheduled transfer on the impacted BCR records in BIRRDS if the Effective Date has not passed or modify the impacted BCR records in BIRRDS assigning the Pooled CO Code back to the disconnecting SP if the Effective Date for the transfer has passed.
   3. The disconnecting SP shall contact TRA to change the AOCN on the Pooled CO Code and applicable Thousands-Block record in BIRRDS and ensure that the Pooled CO Code is provisioned in BIRRDS with the appropriate information.
   4. The disconnecting SP and the new CO Code Holder shall ensure the transfer has been reversed with regard to NPAC changes.