Yes, if you have in your profile the same OCN, State, and NPA as the user who originally saved the request.

Yes, if you do not meet MTE and/or utilization, NAS provides a radio button ‘Need to Request a State Waiver’ that you may select. If this button is selected, NAS issue a Part 3 denial so you can proceed with requesting a safety valve waiver from the appropriate regulatory authority.

Yes, a new request will need to be submitted at the time you receive an approval for your safety valve waiver request from the regulatory authority.  You can use the Copy CO Code Request tool using the tracking number for the Part 3 denial.  On the MTE screen, select the Received a State Waiver radio button.  Attach a copy of the approved waiver to the request in NAS.

NAS will send a Part 4 reminder email one month prior to the Part 4 coming due. 

You must have at least one customer on the CO Code to submit a Part 4 to acknowledge that the resource is in service.  “In service” is defined in the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) as “A Central Office (CO) Code (NPA-NXX) or Thousands-Block (NPA-NXX-X) for which local routing information appears in the LERG™ Routing Guide, and one or more Telephone Numbers (TN) within the CO Code or Thousands-Block has been Assigned to an end user (FCC 00-104, ¶240).  Numbers that are categorized as Administrative, Aging, Intermediate, Reserved, or Available cannot also be Assigned and do not satisfy the In Service requirement.”

The Part 4 will be available to submit in NAS at the effective date of the CO Code and not before, this will account for effective date changes whether the date was rescheduled to an earlier date or a later date than the original effective date.

To extend a Part 4 due date, you must contact the appropriate regulatory authority  to request a Part 4 extension.

In NAS, from the Thousands-Block/CO Code toolbar, select CO Code Requests then select CO Code Modification Request. From the Type of Change screen, select OCN: Inter-Company (Transferring resource from another Company) or OCN: Intra-Company (Updating OCN within my Company) as the type of change and select this checkbox, “This modification is in response to a request from NANPA to become the new CO Code Holder.”  

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 11.1.10 “If an SP donates/disconnects a Thousands-Block to the NANPA in error and the Thousands-Block disconnect application has been processed but the Effective Date of the disconnect has not yet passed, the SP may cancel the Thousands-Block disconnect in the NANP Administration System (NAS). If an SP donates/disconnects a Thousands-Block in error and the Thousands-Block disconnect application has been processed, but the Effective Date of the Donation/disconnect has passed, and the Thousands-Block is still Available in the Industry Inventory Pool, the SP may retrieve the Thousands-Block by submitting a Part 1.”

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 11.1.5:

When a Thousands-Block Holder is donating/disconnecting a Thousands-Block to the NANPA, the Thousands-Block Holder is required to complete the following fields on the Part 1 in order for the NANPA to update the Contamination information for the Thousands-Block:

1. “Block contaminated?” (Yes or No) 
2. “If contaminated, how many TNs are not available for assignment?” (Enter quantity)
   1. When the SP enters a quantity greater than 100, the request shall be denied unless the SP notes that it is Exiting the Market in the “Comments” field.
3. “Have all IntraSP ports been completed?” (Yes or No)
   1. When the SP answers “No”, the request shall be denied.
4. “Has the Thousands-Block been protected from further assignment?” (Yes or No)
   1. When the SP answers “No”, the request shall be denied.

A Thousands-Block may only be donated/disconnected if the Thousands-Block does not contain more than 100 Unavailable TNs. This includes the donating/disconnecting Thousands-Block Holder’s Unavailable TNs and all other ported TNs identified in NPAC to other SPs.

SPs shall ensure that all donated/disconnected Thousands-Blocks are within CO Codes that have been flagged as LNP capable in the LERG™ Routing Guide and opened in the NPAC, and that the associated Switching Entity/POI(s) are LNP-capable and ready to process terminating traffic.

SPs shall complete their ISP Ports and protect the Thousands-Block from further TN assignment prior to the submission of the Part 1 to disconnect the Thousands-Block.  If ISP Ports in the NPAC are not completed or the Thousands-Block is not protected from further TN assignment, and a donated/disconnected contaminated Thousands-Block is Assigned, there may be service disruptions to customers Assigned Numbers from the Thousands-Block and potentially double assignments for those contaminated TNs. See Section 7.1.16 for resolution of double assignments. 

An SP donating/disconnecting a Thousands-Block containing a test line number shall disconnect the test line number prior to submitting the Part 1to disconnect the Thousands-Block. The test line shall be re-Assigned to a number in a Thousands-Block retained by, or Assigned to, the SP.

An SP donating/disconnecting a Thousands-Block that contains an LRN shall migrate any ported numbers or Pooled Thousands-Blocks utilizing the LRN to another LRN within a Thousands-Block being retained by or Assigned to the SP and delete the LRN in the NPAC and the iconectiv® LERG™ Routing Guide.

An SP donating/disconnecting a Thousands-Block(s) which has any special status or treatment, e.g., restricted use, chatline, etc. shall indicate that in the “Comments” field on the Part 1 disconnect.

When the CO Code is already a Pooled CO Code, SPs shall place a ‘D’ on the NXD-A screen in the Business Integrated Routing and Rating Database System (BIRRDS) prior to submitting the Thousands-Block disconnect. 

When the CO Code is a Non-pooled CO Code the SP shall build the records for any Thousands-Blocks being retained on the NXD-A screen after the NANPA has approved the disconnect. At the time the NANPA processes the disconnect the NANPA shall update the BCR record in BIRRDS with the Effective Date indicated on the Part 3.
 

Per 47 CFR 52.15 (g) (4) (iii), “All service providers shall maintain no more than a six-month inventory of telephone numbers in each rate center or service area in which it provides telecommunications service.” 

If you do not anticipate using the telephone numbers in the next six months, any thousands-block  that is ten percent or less contaminated in your inventory should be donated to the pool.

For additional information regarding donations/disconnects,  see Section 11.1.1 of the (ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG).
 

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 11.1.5, “When the CO Code is a Non-pooled CO Code the SP shall build the records for any Thousands-Blocks being retained on the NXD-A screen after the NANPA has approved the disconnect. At the time the NANPA processes the disconnect the NANPA shall update the BCR record in BIRRDS with the Effective Date indicated on the Part 3.” 

Any Thousands-Block within the CO Code that has been retained, your AOCN needs to go into BIRRDS and create the NXD-X records. For example, if you disconnect/donated NPA-NXX, Block 1, 2 and 3, your AOCN would need to create the NXD-X records for NPA-NXX Block 0, 4, 5, 6, 7, 8 and 9.

Per ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), Section 4.4., directs SPs to "submit their NRUF to the NANPA on a semi-annual basis on or before February 1 for the period ending December 31 and on or before August 1 for the period ending on June 30 of each year.  Additionally, under these same semi-annual reporting deadlines, SPs shall submit to the NANPA the Appendix 3." 

If you do not have a forecast on file at the time you are submitting a request for pooled resources, you must submit a thousands-block forecast prior to submitting your request.
 

Thousands-Block forecasts may be updated at any time.

You should enter the number of Thousands-Blocks in the month(s) in which you anticipate making requests for resources in each of the given rate centers. If a full pooled CO Code is needed, it must be reflected in Thousands-Blocks, e.g. a pooled full CO Code = 10 Thousands-Blocks.

Thousands-Block forecasts may not be deleted once submitted; however, you can modify your forecast with the updated information or change the forecasted amounts to all zeros.

A SP may request to reserve a Thousands-Block when a safety valve waiver request has been submitted to the appropriate regulatory authority.  Refer to Section 6 of the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) for additional information. 

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

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

A Thousands-Block will remain in reserved status until:

• A SP requests assignment of the reserved Thousands-Block.
• A SP requests to cancel the reserved Thousands-Block.

Per Section 5.1.7 of the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), the standard Thousands-Block effective date is 31 calendar days from date of application, however, SPs must allow at least two calendar days beyond the effective date prior to activating TNs within the assigned Thousands-Block.