• PAS Forecast Updates in Real Time
  PAS forecast updates immediately upon submission. Total number of blocks being requested must be populated under the month you are requesting them in, not the month you want them activated.
• NAS NRUF Updates Within 24hrs – 48hrs 
  NRUF forecast does not update in PAS in real time. Allow 24-48hrs after NRUF submission before submitting PAS requests.

Excerpt from section 4.8.11 of the Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG).

Evidence that demonstrates the SP has a license or authority issued by the FCC or a Certificate of Public Convenience and Necessity (CPCN) issued by a State Regulatory Body to provide service in the city and state/Rate Center/MSA#/RSA#/MTA#/BTA#/national/LATA. Evidence shall be provided to the Numbering Resource Administrator with the Part 1 or Part 1A application. Evidence shall be provided to the NANPA (e.g., email or fax) or PA (e.g., Attach Documents in PAS or email). If the documents are not being attached in PAS, the PAS tracking number shall be provided.

a)         A SP categorized as an ILEC, RBOC, ULEC, or CLEC shall provide evidence that demonstrates the SP has a CPCN issued by a State Regulatory Body to provide service in the area the Numbering Resource is being requested.

b)         A SP categorized as WIRE or PCS shall provide evidence that demonstrates the SP has a license issued by the FCC to provide service in the area the Numbering Resource is being requested.

1)         If a wireless SP provides a non-exclusive 3650-3700 MHz Radio Service nationwide license, it shall also provide a 3650-3700 MHz Service Registration Acceptance Letter from the FCC to establish both that it has registered fixed sites and base stations, and the location of those sites.

c)         A SP categorized as IPES shall provide evidence that demonstrates the SP has a national authorization issued by the FCC. In addition, the SP shall provide the 30-day State Notification as well as a date stamped filing or email receipt showing the 30-day notice was sent to the state.  See Appendix B Template for 30-day State Notification for Interconnected VoIP Providers. The 30-day notice shall contain the following information:

1)         Applicant’s IPES OCN (NECA Company Code classification shall be IPES)

2)         NPA and Rate Center(s) where the request(s) will be made

3)         Whether the applications shall be for Initial or Growth Numbering Resources

4)         Quantity of Thousands-Blocks and/or CO Codes that are being requested

5)         Accurate regulatory and numbering contact information

In the case that the name on the license or authority issued by the FCC or CPCN does not match the SP’s name on the application, or 30-day State Notification in the case of an Interconnected VoIP application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the name on the license or authority issued by the FCC or CPCN.

Excerpt from section 4.8.2 of the Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG).

Appropriate evidence that facilities are in place or will be in place to provide service within 60 days of the Numbering Resources activation date (LERG Routing Guide Effective Date) is required.  Evidence shall be provided to the appropriate Numbering Administrator with the Part 1 or Part 1A application. Evidence shall be provided to the NANPA (e.g., email or fax) or PA (e.g., Attach Documents in PAS or email). If the documents are not being attached in PAS, the PAS tracking number shall be provided.

• An ILEC, RBOC, ULEC, CLEC, WIRE or PCS OCN may send a copy of any one of the following document(s) the SP selects:
  
  

a) A current executed interconnection agreement between a Local Exchange Carrier and the SP requesting Numbering Resources. The relevant pages are the cover page, area covered, the expiration date and the signature page from the interconnection agreement. The SP shall provide only the relevant pages or indicate in the email the page numbers for the relevant pages if providing the entire interconnection agreement. The Numbering Resource Administrator shall deny any application when the relevant pages are not provided, or the SP does not indicate the page numbers of the relevant pages when providing the entire interconnection agreement via email. In the case that the name on the interconnection agreement does not match the SP’s name on the application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the name on the interconnection agreement.

b) Documentation of the state commission approval of the current interconnection agreement. In the case that the name on the state commission documentation does not match the SP’s name on the application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the name on the state commission documentation.

c) The Service Provider Business Plan/Pre-Planning Checklist (see Appendix A) to show that facilities for origination or termination for calls being used specifically for the requested code(s) have been requested and are anticipated to be completed in order to provide service within 60 calendar days of the numbering resources activation date (LERG Routing Guide effective date). If the CLLI of the applicant’s switch or POI has not been built in BIRRDS, including originating and terminating tandems (switch homing arrangements), the applicant cannot utilize this type of proof of facility readiness and must provide one of the other four types of proof of facility readiness. The PA will deny an application if the applicant’s switching entity/POI has not been built in BIRRDS at the time the application is processed.  NANPA will deny an application if the applicant’s switching entity/POI with switch homing arrangements have not been built in BIRRDS at the time the application is processed.

d) A confirmation letter or letter of intent provided by the LEC with which the requesting SP shall interconnect.  Interconnecting LECs are encouraged, but not required, to provide such letters.  In the case that the name on the confirmation letter does not match the SP’s name on the application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the name on the confirmation letter.

e) A letter from the requesting SP identifying a Thousands-Block/CO Code In Service in another Rate Center that already uses the same facilities and CLLI Code that shall be used to serve the new Rate Center where the Initial Numbering Resource is being requested and reflected on the application.  In the case that the OCN name associated with the Switching Entity CLLI serving the existing Thousands-Block/CO Code does not match the SP’s name on the application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the OCN name associated with the Switching Entity CLLI.

• An IPES OCN may send a copy of either of the following:

a) A combination of an agreement between the Interconnected VoIP SP and its Carrier partner and an interconnection agreement between that Carrier and the relevant local exchange Carrier (LEC), or

b) Proof that the Interconnected VoIP SP obtains interconnection with the Public Switched Telephone Network (PSTN) pursuant to a tariffed offering or a commercial arrangement (such as a TDM-to-IP or a VoIP interconnection agreement) that provides access to the PSTN.

When providing such documentation, the Applicant shall provide only the relevant pages or indicate in the email to the Numbering Resource Administrator the page numbers for the relevant pages if providing entire agreements or documents. For agreements between the Interconnected VoIP SP and its Carrier partner, and for interconnection agreements, the relevant pages are the cover page, area covered, the expiration date, and the signature page from the interconnection agreements. For tariffed offering or commercial arrangement documents, the relevant pages are the cover page, page that identifies area covered, pages that describe how traffic shall be exchanged, term of the contract or expiration date, and the signature page. If the document does not identify the area covered, the Applicant shall provide a Carrier partner’s written statement indicating the area covered. The Numbering Resource Administrator shall deny any application when the relevant pages are not provided, or the Applicant does not indicate the page numbers of the relevant pages when providing entire documents via email.

In the case that the name on an agreement does not match the Applicant’s name on the application, the Applicant shall provide verifiable merger/acquisition or name change documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the application with the name on the documents.

In the case that the Carrier partner name on the Carrier partner agreement does not match the Carrier partner company name on the applicable interconnection agreement, the Applicant shall provide documentation (e.g., state regulatory body or FCC approval, a copy of the NECA response to the SP confirming merger/acquisition or name change, letter of certification from an officer of the company) linking the name on the Carrier partner agreement with the name on the interconnection agreement.

1. That the code is active in the PSTN. Meaning that facilities are in place and a call through test was successfully performed.

2. The code is loaded into the NPAC. A Service Provider can load the code in the NPAC via their Service Order Activation (SOA) system, the NPAC Low Tech Interface (LTI), or a Service Bureau if they use a Service Bureau.
For questions about loading a code in the NPAC, please contact the NPAC Help Desk at 844-820-8039.

 All other CO Code Holder Responsibilities as outlined in section 8.2 of the Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG)] for the CO code have been fulfilled. 
Building BIRRDS records for the code (NXD record) is the responsibility of the SP’s AOCN (The AOCN is the entity authorized by the CO code holder to input and maintain data into BIRRDS.).

8.2.1

Pooled CO Code assignments are made subject to the conditions listed in Section 5.3 and 5.4.  CO Code Holders shall verify and test that a new Pooled CO Code is activated in the Public Switched Telephone Network (PSTN) starting five calendar days prior to the Central Office (CO) Code’s (NPA-NXX) LERG Routing Guide Effective Date.  Further, CO Code Holders shall verify that the CO Code has been added to the Number Portability Administration Center (NPAC) within ten calendar days of assignment by the North American Numbering Plan Administrator (NANPA).

8.2.4  

  
The CO Code Holder of a Pooled CO Code is responsible for default routing functions associated with the Pooled CO Code regardless of how many Thousands-Blocks (NPA-NXX-X) are retained by, or Assigned to, the CO Code Holder. The CO Code Holder of a Pooled CO Code shall:

a)         submit the appropriate CO Code request forms to the Pooling Administrator (PA) filled out as if the CO Code Holder was requesting the CO Code from the NANPA, with the appropriate information populated (e.g., Tandem Homing CLLI, Switching Entity/Point of Interconnection (POI), etc.);

b)         ensure Administrative Operating Company Number (AOCN) input of Pooled CO Code Part 2 data entry into BIRRDS, specifying the routing and rating information for the Pooled CO Code assignment, within 7 calendar days of the issuance of the Part 3;

c)         load the Pooled CO Code into the NPAC database within 10 calendar days of the Pooled CO Code being Assigned by the NANPA;

d)         submit a Part 1A Thousands-Block (NPA-NXX-X) Application modification to the PA after Thousands-Blocks are Assigned if the Part 1B NPAC Thousands-Block Data needs updating because the CO Code Holder is retaining multiple Thousands-Blocks and the routing information for one or more of those Thousands-Blocks is different than the Pooled CO Code routing information. The PA forwards the Part 1B to the NPAC after processing the modification;

e)         validate that all translations work is complete five calendar days prior to the Pooled CO Code’s LERG Routing Guide Effective Date;

f)          verify and test that the Pooled CO Code is activated in the Public Switch Telephone Network (PSTN) by performing successful call-through tests  starting five calendar days prior to the Pooled CO Code’s LERG Routing Guide Effective Date; 

g)         provide Vacant Code Announcement (VCA) or Reorder Announcement (ROA)  for TNs in un-Allocated Thousands-Blocks;

h)         maintain sufficient and auditable data to demonstrate compliance with these guidelines;

i)          notify the PA if the CO Code Holder is no longer able to perform the default functions of a Pooled CO Code (e.g., the SP is no longer providing service in the area served by that Pooled CO Code);

j)          prior to returning a Pooled CO Code, return all Thousands-Blocks Assigned or Retained in the Pooled CO Code;

k)         ensure the following occur a minimum of five business days prior to the LERG Routing Guide Effective Date to enable all Thousands-Blocks in the Pooled CO Code to be viable for other SPs:

1)         Assigned Pooled CO Code(s) is currently available for call routing, is flagged as Local Number Portability (LNP) capable in the LERG Routing Guide and the NPAC, and the NPA-NXX query triggers are applied in all switches and reflected in the appropriate network databases (e.g., STP routing tables);

2)         the Pooled CO Code’s -Assigned Switching Entity/POI is currently LNP-capable and shall process terminating traffic appropriately; and

3)         interconnection facilities have been established between the Pooled CO Code Assigned Switching Entity/POI and other interconnecting networks

l)          Ensure the Pooled CO Code is opened under the old Numbering Plan Area (NPA) before or during permissive dialing  for a geographic split in the NPAC, if the Pooled CO Code shall move to the new NPA at the end of permissive dialing;

m)        confirm via the Pooling Administration System (PAS) within five business days of the PA’s inquiry, indicating the status of the newly Assigned Pooled CO Code  (i.e., whether the Pooled CO Code has been activated in the PSTN, loaded in the NPAC, and all other responsibilities of a CO Code Holder of a Pooled CO Code have been fulfilled);

n)         if unable to activate its newly Assigned Pooled CO Code in the PSTN, load the Pooled CO Code in the NPAC and fulfill all other CO Code Holder responsibilities of a Pooled CO Code by the Pooled CO Code’s Part 3 Effective Date, notify the PA via PAS of the date that the CO Code Holder shall fulfill those responsibilities so that the PA can update the availability of the associated Thousands-Blocks in PAS and notify any SPs with Assigned Thousands-Blocks from the Pooled CO Code. The CO Code Holder shall still provide confirmation to the PA via PAS when the CO Code Holder activates the Assigned Pooled CO Code in the PSTN, loads the Pooled CO Code in the NPAC and fulfills all other CO Code Holder responsibilities of a Pooled CO Code; and

o)         be responsible for providing to the PA the Part 4 that confirms a full CO Code that was obtained to meet a SP’s single customer request has been placed In Service.