For Forms U1, U2, U3, and U4, you may copy and paste or enter the data starting at row 21, columns A through J; Forms F1A/B, F2A/B starting at row 22, columns A through H; and Forms F3A/F3B starting at row 22, columns B through H. For the available, utilization and total columns, you must click the “Check the Data Before Submitting” button in the upper-right corner for these columns to calculate. 

If that does not work, you may find detailed instructions in the NRUF Geographic Job Aid located here, https://www.nanpa.com/nruf/requirements-file. 
 

You can delete the data in the cells within the row you want to delete. Then you must click the “Check the Data Before Submitting” button in the upper-right corner to delete those rows. 

If that does not work, you may find detailed instructions in the NRUF Geographic Job Aid located here, https://www.nanpa.com/nruf/requirements-file.

For Forms U2 and U4, you may copy and paste or enter data starting at row 21, columns A, and C through H; and Form F3B starting at row 22, columns B and D through H. For the available, utilization and total columns, you must click the “Check the Data Before Submitting” button in the upper-right corner for these columns to calculate. 

If that does not work, you may find detailed instructions in the NRUF Non-Geographic Job Aid located here, https://www.nanpa.com/nruf/requirements-file.
 

You can delete the data in the cells within the row you want to delete. Then you must click the “Check the Data Before Submitting” button in the upper-right corner to delete those rows. 

If that does not work, you may find detailed instructions in the NRUF Geographic Job Aid located here, https://www.nanpa.com/nruf/requirements-file.
 

The FCC Form 502 has enabled macros. You must not try to populate any cell that is protected. Company information can only be populated on the “Company Info” tab. For the geographic FCC Form 502, Forms U1, U2, U3 and U4, you must start at row 21 and can only populate columns A through J. For Forms F1A/B, F2A/B, you must start populating at row 22 columns A through H. For Forms F3A/B you must start populating on row 22 columns B through H. For the available, utilization and total columns, you must click the “Check the Data Before Submitting” button in the upper right corner for these columns to calculate.

If your NRUF response/reply includes errors, the row(s) containing errors are not considered on file and must be corrected. When completing the forms, you must enter your data starting on the header rows. This is required for NAS to read/process the data. The header row on the utilization forms is row 21, and on the forecast forms it is row 22.

NANPA recommends service providers and consultants to pull the NRUF Utilization Missing Report the next business day, after receiving a confirmation that the NRUF report has been accepted. The NRUF Utilization Missing Report can be found in NAS by going to the NRUF toolbar and selecting Reports. If there are any Central Office codes (NPA-NXXs) and/or Thousands-Blocks (NPA-NXX-Xs) appearing on the NRUF Utilization Missing Report, action is required. If you receive “No results found for those search parameters,” you have reported on all of your assigned numbering resources for the current reporting period.

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.
 

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

In NAS, from the Thousands-Block/CO Code toolbar, select Forecast, then select Request Update to Excluded 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.
      
      
       

Provide the date the safety valve waiver request was submitted in the Comments section of the Part 1 request.

You must provide the reason for the change e.g., merger/acquisition, OCN change within company, or other using the “Comments” field provided. For any reason other than merger/acquisition, you must also state in the “Comments” field that there are assigned numbers.

CO Code reservations are reserved for a period of 3 months from the Part 3 date approving the reservation. The CO Code reservation will be automatically cancelled and the CO Code will be returned to the available inventory one day after the original reservation expiration date unless an extension is requested prior to the reservation expiration date.

A CO Code will remain in reserved status until:

• A SP requests assignment of the reserved CO Code.
• A SP requests to cancel the reserved CO Code.

Per Section 5.3.8 of the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), the standard CO Code effective date is 59 calendar days from date of application.

Per Section 5.3.8 of the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), an expedited effective date is a date earlier than the standard CO Code effective date (59 calendar days):

1. Activities for the expedited 14 calendar day Interval:
   1. In addition to submitting the Part 1 application to the NANPA, the SP obtains agreement from its AOCN to input the Part 2 data within a specific negotiated time period.  This can reduce the AOCN period down from seven (7) calendar days.  The SP shall provide written confirmation to the NANPA of the reduction of the seven (7) calendar days.  In the case where an Applicant acts as its own AOCN, the CO Code Applicant should indicate so on the Part 1. Doing so will reduce the AOCN period down from seven (7) calendar days. 
   2. Then, the SP submits the Part 1 application through the NANPA with the attached confirmation from the AOCN if applicable.  When the SP requests to receive the “52 calendar day Effective Date” on the Part 1, NANPA shall reduce the Effective Date to the earliest date without compromising the 45 calendar day CO Code activation interval from the date NANPA processes the application. 
       
2. Activities for the expedited 45 calendar day Interval:
   1. The SP shall follow the Next Generation Interconnection and Interoperability Forum (NGIIF) procedures to expedite the 45 calendar day CO Code activation process.  
   2. On an exception basis, an activation interval of less than 45 calendar days may be requested on the Part 1. The Part 1 shall be accompanied by documentation from the homing tandem operating company that the shorter interval can be met.
   3. Under no circumstances shall an activation interval of less than 30 calendar days be approved by the homing tandem operating company or the NANPA.  

The requesting SP shall indicate on the Part 1 that this is an expedited application with its desired Effective Date.

If you made an error on a New CO Code request or CO Code Modification request, you could modify it if NANPA has not started processing the request or issued a Part 3.  You would access the request by using the Modify Pending Thousand-Block request tool in NAS.

[1] For more information, refer to the latest issue of ATIS-0300046, Next Generation Interconnection Interoperability Forum (NGIIF) “Recommended Notification Procedures to Industry for Changes in Access Network Architecture.”
[2] This is required to ensure facilities are available at the homing tandem and that appropriate Service Provider (SP) notification exists; expedited activation intervals or the rescheduling of existing effective dates to less than 45 calendar days have the potential to cause increased blocking and trouble reports for all SPs.
 

Yes, any user that has the same state, NPA and OCN in their profile will have the ability to modify a New CO Code request or CO Code Modification request, they can modify it if NANPA has not started processing the request or issued a Part 3. They would access the request by using the Modify Pending Thousand-Block request tool in NAS.