- TABLE OF CONTENTS
(updated 2/99)
Preface
1.0 Purpose and Scope
2.0 Considerations, Assumptions, and Constraints
3.0 Block Assignment Principles
4.0 Pre-Conditions and Requirements of the Applicant
5.0 Responsibilities of Code Holders and LERG Assignees
6.0 Responsibilities of Block Applicants and Holders
7.0 Assignment Process
8.0 Initial Establishment of Industry Pool
9.0 Pool Level Maintenance Procedures
10.0 Vanity Numbers
11.0 NPA and Rate Center Jeopardy Situations
12.0 Appeals Process
13.0 Compliance (Auditing)
14.0 Glossary
PREFACE
It may be necessary to modify the guidelines periodically to meet changing and unforeseen circumstances. Questions regarding the maintenance of the guidelines or requests for changes may be directed to:
- Pat Fleck
- meritech
- 25 W. Randolph, 29
- Chicago, IL 60606
- Tel: 312-551-9186
- E-mail: patricia.fleck@ameritech.com
OR
- Shawn Murphy
- AT&T
- 20 Independence Blvd
- Warren, NJ 07059
- Tel: 908-580-8741
- E-mail: smurfs@att.com
1.0 Purpose and Scope of This Document
This document specifies interim guidelines for the assignment processes of thousands blocks (NXX-Xs) to service providers for use at a switching entity they own or control. In addition, these guidelines outline the processes between the Pooling Administrator, Code Holder, Block Holder, CO Code Administrator and NPAC. Number pooling allows for the sharing of central office codes (NXXs) to multiple service providers serving the same rate center. All ten thousand numbers within each NXX continue to be assigned to one rate center, but can be shared among multiple service providers at the thousands-block (NXX-X) level. Examples of uses for blocks for which these guidelines apply include plain old telephone service (POTS), Centrex, Direct Inward Dialing (DID), wireless service, data lines, facsimile, and coin phones.
These guidelines do not supersede appropriate NANP area governmental or regulatory principles, procedures, and requirements.
Where number pooling has not been implemented, service providers are considered Code Holders and shall apply directly to the CO Code Administrator for numbering resources. Guidelines addressing the assignment of central office codes (NXX) are covered under the Central Office (NXX) Assignment Guidelines (INC 95-0407-008).
2.0 Considerations, Assumptions and Constraints
The development of the assignment guidelines include the following assumptions and constraints:
2.1 NANP resources, including those covered in these guidelines, are collectively managed by the North American Telecommunications industry with oversight of the North American regulatory authorities.
The NANP resources are considered a public resource and are not owned by the assignees or the administrator. Consequently, the resources cannot be sold, brokered, bartered, or leased by the assignee for a fee or other consideration.
If a resource is sold, brokered, bartered, or leased for a fee, the resource is subject to reclamation by the Pooling Administrator.
2.2 NANP numbering resources shall be assigned to implement the most effective and efficient use of a finite numbering resource in order to prevent premature exhaust of the NANP and delay the need to develop and implement costly new numbering plans. Efficient resource management and code conservation are necessary due to the industry impacts of expanding the numbering resource (e.g., expansion from 10 to 11 digits). Impacts to the industry include:
a) Customer impacts (e.g., dialing, number changes to advertising and stationary, security systems, etc.)
b) CPE modifications
c) Domestic and international switching hardware and software modifications
d) Operational support systems modifications
e) Reprogramming of non-telecommunications data bases that contain telephone numbers.
2.3 These guidelines are interim and were developed to operate under a pre-port architecture environment in the 847 NPA. These guidelines are intended to remain in place until national guidelines are developed and implemented.
2.4 These assignment guidelines apply only to the assignment of thousands blocks to block applicants serving rate centers: a) that are subject to pooling by industry agreement or regulatory directive or both, and b) where permanent service provider number portability (LNP-LRN) has been implemented by both the code holder and block applicant.
2.5 These guidelines do not address the issue of who will fulfill the role of Number Pooling Administrator(s). These guidelines were developed by the industry without any assumption on who would be the Number Pooling Administrator.
2.6 Applicants, utilizing resources from the pool, shall:
a. have or have applied for the appropriate regulatory approval to operate in the area,
b. be capable of contributing numbering resources to the pool,
c. cooperate with the Pooling Administrator to allocate numbering resources to the Industry Pool, (see section 7.1)
d. establish internal policies and practices that provide for the efficient use and assignment of numbers to end users. These policies and practices shall balance product specifications, market strategies and customer needs with conservation principles to ensure best practices in number utilization. These policies should minimize contamination levels by assigning numbers from one contaminated block before assigning numbers from a non-contaminated block.
e. minimize the use of blocks (NXX-X) for purposes other than assignment (e.g., test codes),
f. own or control an LNP capable switch serving a rate center subject to pooling.
g. be subject to audits to assure compliance with these guidelines, processes and principles (see Section 14).
3.0 Block Assignment Principles
The following assignment principles apply to all aspects of the Number Pooling Guidelines:
3.1 Where number pooling has been implemented, the Pooling Administrator will assign non-working numbering resources in 1,000 block increments. Resources will be available from both contaminated and non-contaminated blocks.
3.2 A requirement for an entire NXX code (i.e., 10,000 numbers) to satisfy the numbering needs for a single customer may be satisfied by the CO Code Administrator.
3.3 Numbering resources in the Industry Inventory Pool shall be available and allocated to service providers in a fair and non-discriminatory manner, including requests for specific blocks.
3.4 The information submitted by applicants for block assignments shall be kept to a minimum and shall be uniform for all applicants. All information provided on the NXX-X request form will be considered confidential. However, the information, if placed in the RDBS or BRIDS becomes public upon assignment of the block in the appropriate routing data base product (e.g. LERG).
3.5 Block assignments will be made from NXX codes assigned and utilized within a single rate center/rate district.
3.6 The Number Pooling Administrator shall attempt to satisfy all requests (i.e., technical/marketing requests) for a specific NXX-X.
3.7 Any entity that is denied the assignment of one or more blocks under these guidelines has the right to appeal that decision per Section 12.0.
3.8 There must be a technical need for an initial block assignment. Utilization criteria or forecasts will not be used to justify an initial block (NXX-X) assignment. The technical need for an initial block assignment will be based upon one of the following:
a) identification of a new switching entity,
b) unique rate center requirements consistent with regulatory restriction.
3.9 Assignments of additional blocks shall be made based upon both growth needs and technical limitations such as Customer PBX restrictions.
3.10 Requests for block reservations will be accepted. Block applicants should demonstrate good faith efforts to eliminate or to minimize the number of reserved blocks.
3.11 These guidelines are not intended to be used to satisfy vanity numbering needs.
3.12 Block assignment while the NPA and/or rate center is in jeopardy will require special handling as referenced in section 11.0.
3.13 The Pooling Administrator shall make every attempt to assign a service provider’s own contaminated block to that service provider from the pool.
4.0 Pre-conditions and Requirements of the Applicant for the Assignment & Reservation of Thousand Blocks (NXX-X)
The assignment pre-conditions and requirements in the following sections shall be used by the Pooling Administrator in reviewing a block request from a service provider for an initial or additional block.
4.1 The applicant, if required, must be licensed to operate in the area, and must certify to the Pooling Administrator that all applicable regulatory authority required to provide the service for which the block is required has been obtained or an application has been submitted.
4.2 The applicant must certify a need for a 1,000 block for both initial and additional blocks.
4.3 The applicant must submit an NXX-X request form certifying that a need exists for an NXX-X assignment to a switching entity. The NXX-X request form must provide an Operating Company Number (OCN) which uniquely identifies the applicant.
4.4 Blocks (NXX-Xs) are assigned to service providers for use at a Switching Entity they own or control. Assignment of the initial block(s) will be used, to the extent required, to provide PSTN traffic as authorized or permitted by the appropriate regulatory or governmental authorities, and provided all the criteria in Sections 4.1 through 4.3 are met.
4.5 For additional blocks for growth, the applicant must certify that existing numbering resources do not reasonably meet the requirements for an additional block(s). Each block holder will certify that existing blocks for the switching entity, per service provided by that switching entity, will exhaust within 6 months. In addition, the block holder must have documented and be prepared to supply as described in this Section, Sections 2 and 3, and Section 13 (Compliance) supporting data in the form of:
a) Telephone Numbers (TNs) available for assignment
b) Incremental growth history for past 6 months
c) Projected incremental demand for the coming 6 months
4.5.1 The applicant must certify that an additional block(s) is necessary for distinct or unique service needs separate from the growth blocks described in Section 4.5. (See Section 1.7 of the Block Request Form-Part 1)
4.6 To reserve a block, a block applicant must demonstrate that:
a. the block is essential to accommodate technical or switch planning constraints;
b. regulatory approval of a tariff and/or certification/registration is pending. If regulatory approval is pending, the applicant must certify and provide appropriate documentation that a request for regulatory certification/registration has been submitted to the appropriate regulatory body to provide service within 6 months.
c. the applicant meets the requirements of block assignment as outlined here and in Sections 2.0 and 3.0.
4.6.1 If a reserved block is not activated within six months, the block will be released from reservation. (See Section 9.1.4.)
4.6.2 Reservations may be extended under the following circumstances:
a. When the proposed block effective use date will be missed due to circumstances beyond the control of the applicant (e.g., hardware, software provision delays, regulatory delays, etc.) upon written request to the Number Pooling Administrator, one reservation extension of 3 months will be granted. (See Section 9.1.3.)
b. When the reservation was due to solely technical constraints, the reservation can be extended until the constraint is eliminated.
5.0 Responsibilities of Code Holders and LERG Assignees
The following section describes the responsibilities of the Code Holder/LERG Assignee. In the context of these guidelines, NXX codes may need to be activated for block assignment purposes to 1) replenish the pool, and/or 2) when a service provider request can only partially be met by resources from the pool.
5.1 Code Holders shall:
a. identify eligible blocks for donation to the pool upon initial establishment of the pool,
b. cooperate with the Pooling Administrator in applying for a new NXX code in the situations outlined in Section 5.0,
c. cooperate with block recipients to remove numbering resources in number assignment systems, and
d. perform intra-service provider ports prior to the effective date for contaminated blocks.
5.2 If a code holder inputs records into the NECA 4 tariff, the affected records should be deleted upon donation to the pool.
6.0 Responsibilities of Block Applicants and Holders
6.0 Applicants, utilizing resources from the pool, shall:
a. have documentation demonstrating that the applicant is licensed and/or certified, or has applied for regulatory approval to operate in the service area for which the central office thousands block is required,
b. be capable of contributing numbering resources to the pool,
c. maintain data that is sufficient and can be audited to demonstrate compliance with these guidelines, (see Section 13).
6.1 Additional information and or dialog may be required by the Pooling Administrator to facilitate block application processing. The Pooling Administrator is still required to resolve issues necessary to process the application within 10 business days.
6.2 If a service provider is deploying a new switching entity that requires the assignment of an LRN, the block applicant will indicate on the request form whether or not an LRN has been assigned. It is incumbent upon the service provider to return blocks to the number pool for which there is no forecasted demand.
6.3 The Application Process
6.3.1 Block applicants for initial and/or additional NXX-X block assignments shall submit their requests to the Pooling Administrator using the Number Pooling (NXX-X) Assignment Request Form (Block Request Form).
6.3.2 There is no upper limit on the number of blocks that can be requested on one application form. The application form is structured per rate center, per switch.
6.3.3 The block applicant must accurately complete all required entries on the Block Request Form. If electronic transfer is utilized, it will be considered as signature. If assistance is required by the block applicant, the pooling administrator should be contacted.
6.3.4 The Block applicant should indicate on the request if any thousands block (i.e., 0-9) can be assigned or whether, for technical/marketing reasons, only certain thousands blocks may be assigned. The block applicant can request specific blocks on their application. (See Sections 1.4d and 1.4e on the Block Request Form-Part 1.)
6.3.5 The Block Applicant can refuse the assignment of a block when the block does not meet their technical/marketing constraints.
6.3.6 Requests for block assignments should not be made more than 6 months prior to the requested effective date.
6.4 Information Required For Block Allocation
6.4.1 Block Applicants should typically request effective dates a minimum of 13 business days following the request date. It should be noted that 2 additional business days are required for the NPAC download sequence if the telephone numbers in the block are the first telephone numbers in the NXX to port.
6.4.2 A block applicant or block holder will be responsible for entering NXX-X block information into the appropriate databases for calling card validation, etc., as they currently do today.
6.5 Ongoing Administrator
6.5.1 Notification of Block Assignment Changes
The information associated with a block assignment may change over time. The Pool Administrator must be notified of any changes to the information in Part 1 of the NXX-X Block Assignment Request Form. This includes changes such as, but not limited to, OCN, switching entity. For data integrity reasons, the Pooling Administrator must be informed of these types of changes to ensure that an accurate record of the entity responsible for the block and the data associated with the block is accurate.
It is the responsibility of the block holder to make any changes to RDBS and BRIDS data associated with a switching entity including, but not limited to, Office Functionality and Switching Entity-Network Services through the Administrator, or the company with (AOCN) authorization.
6.5.2 The holder of a NXX-X block assigned by the Administrator(s) or acquired by an entity (i.e., by merger or acquisition) must still abide by these guidelines.
6.6 Block Use
Block assignments are made subject to the conditions listed in Section 2.0, 3.0 and 4.0. A block assigned to an entity, either directly by the Pooling Administrator or through transfer from another entity, should be placed in service within 6 months. In addition, if the assignee no longer has a need for the block or the contamination level of the block becomes less than 10% and the service provider has no forecasted demand, the block should be returned to the Pooling Administrator for reassignment. If it is determined through the audit process or other means that a block is not in use after 6 months, as noted above, the Pooling Administrator will request the return of the block.
6.6.1 All block holders must abide by the block reclamation procedures outlined in Section 9.1.
6.7 Industry Pool/NPA Planning Information
6.7.1 All block holders shall provide forecasted block requirements to the Pooling Administrator for projecting rate center exhaust and for input to the NPA code relief planning process. All such forecasts shall be treated on a proprietary basis. This forecast data will be aggregated and input into the annual COCUS study conducted by the CO Code Administrator.
7.0 Requirements of Pooling Administrator
The following describes the responsibilities of the pooling administrator in: 1) assigning blocks of numbering resources to eligible service providers, 2) reporting status regarding pooling resources to industry and regulatory authorities, 3) forecasting and planning, 4) general Administrator processes.
7.1 Assignment Process
7.1.1 The Pooling Administrator shall accept and process applications for block requests in an efficient and timely manner. Requests for block assignments shall be responded to within fourteen (14) calendar days.
7.1.2 The administrator shall confirm that the applicant is eligible to make the request, and that the service provider has certified a need for the block assignment.
7.1.3 The Pooling Administrator should attempt to assign blocks based on an applicants request for a specific block, or if no specific request was made, as follows:
1. the service provider’s own contaminated blocks,
2. available non-contaminated blocks (first attempting to use the 0, 1, 8, and 9 thousands blocks), and
3) blocks with increasing levels of contamination.
7.1.4 The Pooling Administrator reserves the right to negotiate specific assignment of thousands blocks (e.g., which thousands block to assign, assign partial request or hold entire request) with the service provider when only a portion of the application can be satisfied immediately with blocks from the pool.
7.1.5 If a specific block request(s) is made on an application, the Pooling Administrator will attempt to satisfy the request with available blocks in the pool. If the block applicant requests a specific block for technical reasons and the Pooling Administrator cannot satisfy the request with available blocks in the pool, the Pooling Administrator will work with the service providers to obtain a new NXX code from the Code Administrator.
7.1.6 The Pooling Administrator is responsible to work with the Service Provider to apply for new NXX codes in two specific instances: 1) a Service Provider’s request can only partially be filled, and 2) periodic replenishment of the pool is required.
7.1.7 When the Pooling Administrator identifies the need for additional NXX(s) codes to replenish the pool (it is expected that the administrator would identify the need for replenishment 9 months prior to exhaust within the rate center, 6 months if in a jeopardy situation), the Pooling Administrator will determine a service provider to be the code holder (i.e., LERG assignee) based on service provider forecasts for future demand, and contact that service provider to request that that service provider become the NXX assignee for the new code. The service provider will submit the appropriate application to the code administrator. The Service Provider will notify the Pooling Administrator of the specific NXX assignment. The Pooling Administrator will assign a mutually agreed to block within the NXX code.
7.1.8 The Pooling Administrator is responsible for notifying all service providers participating in the pool whenever blocks are assigned. The following information should be included in the notification: NPA, NXX, Block Range(s), Effective Date, Rate Center, LATA, Service Provider Identifications (SPIDs) for both the donor and recipient, From Switch CLLI, To Switch CLLI, Donor’s OCN, Recipient’s LRN, and the Class, LIDB, CNAM, and ISVM Destination Point Codes (DPC) and SSNs.
7.1.9 The Pooling Administrator will ensure that the block applicant places the block in service within the time frame specified in Section 6.6 of these guidelines. If the assigned block is not used within this time frame, the Pooling Administrator shall request the return of the block for reassignment.
7.1.10 The Pooling Administrator will perform block reclamation procedures.
7.2 Reporting Issues
7.2.1 The Pooling Administrator shall prepare and publish reports quarterly or as required to industry, NANPA, and regulatory authorities with appropriate jurisdiction on utilization of the industry pool and provide forecasts on projected future usage.
7.2.2 The Pooling Administrator will provide jeopardy notification status (see section 11).
7.3 Forecasting and Planning
7.3.1 The Pooling Administrator shall monitor the supply of available blocks for each of the rate centers being administered. This includes, but is not limited to anticipating the demand upon the pool and replenishing the supply as needed.
7.3.2 The Pooling Administrator shall:
a) receive and compile forecasts of demand from service providers for numbering resources within all
pooled rate centers,
b) analyze service provider forecasts to determine the numbering resources required to maintain the
industry inventory pool at 9 month’s supply,
c) assure the availability, based upon industry established criteria, of numbering resources within the
industry inventory for a given rate center,
d) add to the resources in the industry inventory pool when necessary, by working with the service
providers to obtain new CO codes.
7.3.3 The Pooling Administrator will also aggregate and analyze Block Holder forecast data and submit appropriate data to the Code Administrator(s) and to the NANPA for use in the annual COCUS studies.
7.4 General Administrative
7.4.1 The Pooling Administrator shall maintain a secure industry database accessible to all service providers to include all pooled thousand blocks and the status of the blocks, i.e., assigned, non-assigned and identified contamination (i.e., specific TNs not available) with the initial establishment of the pool. Service provider specific data submitted to the Pooling Administrator will be treated as confidential. Any published data will be aggregated to protect service provider specific information.
7.4.2 The Pooling Administrator may participate in, facilitate, and/or perform audits of service provider utilization of assigned resources, as required.
7.4.3 The Pooling Administrator shall:
a. provide copies of the thousand block code assignment guidelines when requested by
applicants, including timely notification of changes;
b. assist CO Code Administrator in analyzing and helping to resolve problems related to
misrouted calls and calls that cannot be completed; and
c. track updated switch cutovers and block reassignments, and perform other operational
functions; e.g., block reclamation.
8.0 Initial Establishment of Industry Pool
The pool shall initially be established from donations of service provider embedded resources that meet the criteria outlined in Section 8.2 including, if necessary, new NXX code blocks which are obtained from the CO Code Administrator with assistance from the service providers.
8.1 Pool Sizing
8.1.1 The Pooling Administrator will determine what level of resources is needed to meet the demand and will advise the Service Providers of blocks that are required for the rate center pools. The Pooling Administrator will apply a contamination level of 10% and will collect blocks conforming to this criteria when establishing the pool. In cases where the NPA or rate center is in jeopardy, the pooling administrator will need to re-evaluate the pool size.
8.1.2 The size of the number pool will be a 9 month’s supply for each rate center and will be determined from the pooling administrator’s analysis of the service provider’s forecast.
8.1.3 Upon the Pooling Administrator’s request all existing service providers will submit a forecast, on a biannual basis, by rate center to the Pooling Administrator unless otherwise directed by the Pooling Administrator. The Pooling Administrator may also request a forecast on a per rate center basis if needed. The forecast will be for a rolling 18 month period using a quarterly view format determined by the Pooling Administrator. The Pooling Administrator will establish and publish a schedule for the semi-annual forecast. If the Pooling Administrator makes a forecast request on a per rate center basis, service providers shall typically reply within a reasonable period of time (e.g., 14 calendar days). If circumstances warrant, the Pooling Administrator may specify a particular time period based on the size and urgency of the request. A service provider is expected to provide a forecast at the time they make application for their first block.
8.1.4 The Pooling Administrator will aggregate rate center forecasts and develop a new forecast using aggregated and other analysis factors (e.g., considering historical growth). If block demand will exceed availability of returned blocks, the Pooling Administrator will work with the Service Providers to obtain additional NXX codes, as required, from the Code Administrator.
8.2 Process for Identifying and Donating Embedded Resources
8.2.1 Participants shall identify, and submit to the Pooling Administrator, all blocks which have contamination of no more than 10% (including zero). Of those blocks, participants may retain identified blocks if the service provider can certify that:
a) a block will exceed 10% contamination within 6 months,
b) if only one block exists, or
c) can justify per service provider forecast and explain retaining the block for other technical reasons (i.e. interconnection agreements under negotiation). Retention of blocks is subject to audit and appeal procedures. (See Sections 12.0 and 13.0.)
Donations of qualifying blocks are compulsory and should be made to the number pool, subject to the carriers needs within six months of the order. (98-0497 Illinois Commerce Commission Order)
The Pooling Administrator will assess all technical reasons (as certified in section c above) for validity and will refer disputed reasons to the appropriate regulatory authorities or their designate.
8.2.2 Service Providers will identify to the Pooling Administrator the actual working telephone numbers within any contaminated blocks that are being returned.
8.2.3 The Pooling Administrator will build the pool from contributed non-contaminated blocks and contaminated blocks up to 10% contamination. Lastly, the Pooling Administrator will work with the service providers to obtain new NXX code(s) if both non-contaminated and contaminated blocks do not adequately satisfy rate center pool levels.
8.2.4 Porting of numbers from contaminated blocks (i.e., intra service provider port) should occur when the block is donated to the industry pool, but no later than the effective date. When a contaminated block is assigned, the Pooling Administrator will notify the block applicant that the assigned block(s) is contaminated and will provide a list of working telephone numbers within the contaminated block that are not available for the block applicant’s use.
8.2.5 The service provider shall perform all functions necessary to remove the block(s) from their internal systems and perform any porting to the NPAC that is necessary within 30 calendar days.
8.3 New CO Code Requests Procedures
8.3.1 The following provides the process flow and activation procedures for CO Codes in order to provide additional blocks to the Industry Inventory Pool:
Step 1 - LECs send growth forecasts to Pooling Administrator on a per Rate Center basis
Step 2 - Based on forecasts and actual growth the Pooling Administrator determines that a new NXX is required for a specific Rate Center.
Step 3 - The Pooling Administrator will poll the service providers, in the pooled area, to indentify the service provider that will be the default LEC (code holder) for the new NXX. The Pooling Administrator will notify the Code Administrator that a request is forthcoming.
Step 4 - The default LEC submits an application for the new NXX to the Code Administrator.
Step 5 - The Code Administrator reviews the request and notifies the Default LEC of the NXX(s) assignment.
Step 6 - The default LEC notifies the Pooling Administrator of the specific NXX assignment. The Pooling Administrator shall assign a mutually agreed to block within the NXX to the default LEC.
Step 7 - The Code Administrator assigns the NXX to the LEC in RDBS.
Step 8 - The default LEC inputs or causes to have input Part 2 information into RDBS and BRIDS.
8.3.2 In the event the Pooling Administrator is unable to identify a volunteer to become the default LEC, the Pooling Administrator will utilize the following process for selecting a LERG Assignee for a growth NXX that is to be added to the Industry Inventory Pool:
· First, assigned to new participating service providers who require a unique LRN
· Second, should be assigned to participating service providers on a rotational basis, until all participating service providers are the LERG Assignee for at least one NXX residing within the industry inventory pool. The first service provider will be determined on a random basis.
9.0 Pool Level Maintenance Procedures
The replenishment of the resource via the assignment of a new NXX code, for a particular rate center, shall be subject to the same criteria as that used for thousands blocks made available at the initial establishment of the pool at the outset of block assignments. It is expected that Administrator of the resource will require periodic replenishment by the assignment of new NXX code(s) assignments such that the numbering resources for rate centers meets demand and prevents exhaustion.
The pooling administrator will maintain the required pool level by first replenishing the industry pool by obtaining:
a) any eligible contaminated blocks as defined in section 8.2.3, and
b) new blocks via the assignment of a CO Code.
9.1 Block Recovery Procedures
Utilization reports from service providers can be requested on a specific rate center basis, as needed. Service providers are expected to provide utilization reports on an annual basis, at minimum. It is expected that return of contaminated blocks within this process will occur within 21 calendar days.
9.1.1 Assignee/Block Holder Responsibility
Service Providers are expected to return a block(s) if they no longer provide service in that rate area. If a service provider no longer provides service in that rate area and the service provider was a code holder for an NXX used in the pool, the Pooling Administrator must determine/acquire a new code holder for that NXX. This is subject to auditing procedures as defined in section 13.0.
9.1.2 The entity to which a block(s) has been assigned from the pool (as opposed to embedded base) shall return the block(s) to the Pooling Administrator if:
a. it is no longer needed by the entity for the purpose for which it was originally assigned,
b. the service it was assigned for is disconnected,
c. the block(s) was not activated within the time frame specified in these guidelines, or
d. if contamination is below 10% for which the service provider cannot justify retention per section 8.1
9.1.3 If the block(s) was not activated within the timeframe specified in these guidelines, the assignee may apply to the Pooling Administrator for an extension date. Such an extension request must include the reason for the delay and a new activation time commitment, not to exceed 3 months.
9.1.4 Pooling Administrator Responsibility
The Pooling Administrator will contact any block assignee(s) identified as not having returned to the administrator for reassignment any block(s):
1. assigned, but no longer in use by the assignee(s),
2. assigned to a service no longer offered,
3. assigned, but not activated within the time frame specified in these guidelines,
4. assigned, but not used in conformance with these assignment guidelines,
5. assigned, but where contamination is below 10% for which service provider cannot justify retention per Section 8.2, or
6. a previously activated block which is not now in use.
The Pooling Administrator will seek clarification from the assignee(s) regarding the alleged non-use or misuse. If the assignee(s) provides an explanation in conformance with these assignment guidelines the block(s) will remain assigned. If no satisfactory explanation is provided, the administrator will issue a letter to the assignee(s) returning the assigned block(s). If a direct contact can not be made with the assignee(s) to effect the above process a registered letter will be sent to the assignee(s) address of record. The letter will request that they contact the administrator within 30 days regarding the alleged resource non-use or misuse. The block will be made available after 30 days for assignment if the Pooling Administrator can determine whether the block has not been utilized.
A service provider, who previously donated blocks in a rate center to the pool, may determine that they no longer require the blocks in the rate center and want to return the entire NXX to the CO Code Administrator. If the Pooling Administrator needs blocks in the rate center to meet the appropriate industry inventory levels, the Pooling Administrator should work with the CO Code Administrator and the affected service providers to resolve the issue equitably. The resolution should balance the numbering requirements of all service providers with the operational and administrative functions which need to be performed.
9.1.5 If a block is not activated within the timeframe specified in these guidelines and the administrator determines, by discussion with the block(s) assignee, that the reason for the non-activation is not within the control of the assignee(s), the administrator may extend the activation date by up to 90 days.
9.1.6 The Pooling Administrator will receive, process, and refer to the appropriate regulatory authorities any application from block assignees when extensions on block activation dates meets one or more of the following criteria:
a. activation has not occurred within the 90 day extension,
b. the Pooling Administrator believes that the activation has not occurred due to reason within the assignee’s control, or
c. assignee requests an extension in excess of 90 days.
Referral to the appropriate regulatory authorities or their designate will include the offered reason why the extension was requested, a new proposed activation date, and the administrator’s recommended action.
The Pooling Administrator will make all returned resources available for assignment after 21 calendar days.
If a default LERG Assignee is returning block(s) in conjunction with the return of an NXX code as described in Section 9.1.1, the Pooling Administrator shall perform all functions necessary to ensure that the blocks(s) are spare and associated with the new code holder before reassigning them.
9.1.7 The Pooling Administrator will advise the regulatory authority of any disputed reclamation actions.
9.1.8 Regulatory Authorities or their Designate Responsibilities
The regulatory authority or their designate will:
1. accept all referrals of disputed alleged non-use or misuse of blocks(s) from the Pooling Administrator or any other entity,
2. investigate the referral,
3. review referrals in the context of these assignment guidelines,
4. attempt to resolve the referral, and
5. direct the Pooling Administrator regarding the action, if any, to be taken.
9.2 Ongoing Block Holder Forecasting Process
9.2.1 All service providers will submit a forecast as described in Sections 6.7 and 8.1.
9.2.2 Information furnished by block holders shall be submitted on the form provided in Appendix B. This data will be aggregated and submitted by the Pooling Administrator to the CO Code Administrator for use in annual COCUS studies for projecting NPA exhaust. The Pooling Administrator will internally aggregate, analyze and modify forecast data for use in determining rate center exhaust.
9.2.3 All block holders agree to abide by the block reclamation procedures outlined in Section 9.1.
9.2.4 The Pooling Administrator will aggregate service provider data as described in Section 8.1.
9.2.5 The Pooling Administrator will conduct semi-annual forecasts (5 year view at rate center level) to identify rate centers nearing exhaust.
10.0 Vanity Numbers
These guidelines do not address vanity numbers.
11.0 NPA and Rate Center Jeopardy Situations
11.1 NPA Jeopardy Situations
When it is determined by the Code Administrator(s) based on the NPA Code Relief Planning and Notification Guidelines (INC 97-0404-016) that an NPA is in jeopardy, the following actions will be taken to provide relief in the jeopardy NPA.
A. Per the NPA Relief Planning Guidelines, the Code Administrator(s) will notify the appropriate regulatory authority(ies) that the NPA is in jeopardy and that special conservation procedures will be invoked. If appropriate, the Code Administrator(s) will obtain the approval of the regulatory authority(ies) for the implementation of the special conservation provisions. It is anticipated that the Code Administrator will also notify the Pooling Administrator that the NPA is in jeopardy, the established code relief date, and that special conservation measures will be invoked.
B. Prior to any Industry meeting called by the CO Code Administrator, the Pooling Administrator shall call a meeting of all participating pooling members for the purpose of determining a consensus position concerning special conservation measures.
C. The Pooling Administrator shall, unless otherwise explicitly requested not to by an individual member, represent all members of the pool at any Industry Jeopardy Planning Meetings. The Pooling Administrator shall make every effort to ensure that the conservation measures adopted by the industry reflect the needs of the pooling membership as compared to any single entity not participating in pooling.
11.1.1 The following are special conservation procedures that will be invoked in the situation of a
jeopardy NPA.
A. During the special conservation period, the Pooling Administrator will treat all block requests in a fair and impartial manner, consistent with the special conservation provisions.
B. Upon receipt of the notice of the jeopardy situation from the Code Administrator and/or Pooling Administrator, each block holder will review their forecast and demand data and provide the information to the Pooling Administrator within 30 days using the Service Provider Thousand Blocks Forecast form, Appendix B. The number pooling administrator will not consider an NXX-X thousand block request from a carrier that has not previously submitted an NXX-X thousand block forecast.
C. For additional growth blocks, each block holder will certify that existing blocks for the switching entity, per service provided by that switching entity, will exhaust within 3 months. Block holders will have documented and supply as described in Sections 4.5 and 13.0 supporting data in the form of:
1. Telephone numbers available for assignment
2. Growth history for 3 months
3. Projected demand for the coming 3 months (See Appendix A).
D. For a new block, the block holder will certify that the block will be in service within 3
months from date of block request A Service Provider must supply a Months To Exhaust in supporting data in the form of:
1. Projected demand for the coming 3 months (See Appendix A).
E. Requests for assignment of blocks for other than growth or to serve a new switching entity should be minimized.
F. For blocks reserved per Section 4.4:
1. Holders of reserved blocks will be asked to voluntarily return their blocks or confirm their planned reservation dates. See Section 4.6. Reservations with the longest planned activation date will be the first blocks to be used for assignment, and the reservation will be canceled.
2. Reservations with planned activation dates beyond the "NPA relief date" will be reviewed and filled, with resources made available as a result of NPA relief. This does not necessarily imply that the blocks assigned in this situation will come from the new NPA.
G. During the jeopardy period, planning to comply with extraordinary NPA-specific conservation procedures shall commence.
H. The Pooling Administrator should maintain a six month supply in the industry inventory.
11.1.2 Unique circumstances within a given jeopardy NPA may require extraordinary NPA-specific pooling conservation procedures. In this event, the following activities shall apply.
A. Following the receipt of final industry procedures, the Pooling Administrator shall develop rate center-specific pooling conservation procedures in conjunction with the affected parties in the jeopardy NPA. The Pooling Administrator will work with the affected parties to continually refine the rate center specific pooling conservation procedures, as necessary, until NPA relief. The Pooling Administrator will notify the appropriate regulatory authorities or their designate as well as the Industry Relief Team and, if appropriate, obtain approval for the procedures.
B. If good faith efforts to reach agreements have failed, the Pooling Administrator shall draft and submit a proposed recommendation to the appropriate regulatory authorities and the Code Administrator for approval. This does not preclude any other interested party from submitting an alternate recommendation.
C. The Pooling Administrator will comply with any forecast requests made by the CO Code Administrator.
11.1.3 The special and/or extraordinary block-specific conservation procedures shall remain in effect, if required, until NPA relief has been implemented.
11.2 Rate Center Jeopardy Situations
A rate center jeopardy situation exists when the available resources and the actual and forecasted demand falls below 66 calendar days. This situation is not expected to occur, based on the pooling administrator’s Administrator responsibilities, but can occur, if demand outpaces the rate center block forecast.
When it is determined by the Pooling Administrator that a rate center is in jeopardy (i.e., that thousands blocks are expected to exhaust prior to their replenishment), the following actions will be taken to provide relief in the jeopardy rate center.
1. The Pooling Administrator identifies the default LEC per the replenishment procedures, working in conjunction with the service providers and the Code Administrator. Following the application for the new CO Code(s), the Pooling Administrator will notify affected parties of the established block relief date for the rate center and the special conservation procedures documented in this section will be invoked immediately.
2. During the special conservation period, the Pooling Administrator will treat all block requests in a fair and impartial manner, consistent with the special conservation provisions.
3. In order to be eligible to obtain a thousands block while the rate center is in jeopardy, the Service Provider must have submitted a forecast to the Pooling Administrator within the required time frame (see section 8.1.3). If this is related to a block applicant’s initial request, the block applicant must submit a forecast to obtain subsequent blocks.
4. For additional blocks for growth, the applicant must certify that existing numbering resources do not reasonably meet the requirements for an additional block(s). Each block holder whether a new entrant or an existing Service Provider will certify that existing blocks (if any) for the switching entity, per service provided by that switching entity, will exhaust within the jeopardy period (i.e., if you are 30 days into the jeopardy period, that your need is within 36 days).. In addition, the block holder must have documented and supply as described in Sections 4.5 and 13.0 supporting data in the form of:
1. Telephone Numbers available for assignment
2. Incremental growth history for 3 months
3. Projected incremental demand during the jeopardy period.
1. For blocks reserved per Section 4.6, holders of reserved blocks will be asked to voluntarily return their reserved blocks or confirm their planned reservation dates. Reservations with planned activation dates beyond the "Rate Center relief date" will be reviewed, with resources made available as a result of Rate Center relief. Reservations with the latest planned activation date will be the first blocks to be for assignment, and the reservation will be canceled.
2. During the jeopardy period, extraordinary Rate Center-specific conservation procedures shall commence. In this event the following activities shall apply.
· Allocation of existing blocks will be on a first-come, first-served basis for all service providers who have previously submitted a block forecast during the most recent forecast cycle, consistent with section 2.6, item H of the guidelines. All available blocks will be allocated, as requested, until no blocks remain.
NOTE: This process does not preclude the establishment of a rationing and/or lottery mechanism to ensure equal access to 1,000 blocks during a jeopardy period.
12.0 Appeals Process
Disagreements may arise between the Pooling Administrator and block holders/applicants in the context of the Administrator of these guidelines. In all cases, the Pooling Administrator and block holders/applicants will make reasonable, good faith efforts to resolve such disagreements amongst themselves consistent with the guidelines prior to pursuing any appeal. Appeals may include but are not limited to one or more of the following options:
o The block holder/applicant will have the opportunity to resubmit the matter to the Pooling Administrator for reconsideration with or without additional input.
o Guidelines interpretation/clarification questions may be referred to the appropriate regulatory authority. Unless otherwise mutually agreed to by the parties, these questions will be submitted in a generic manner protecting the identity of the appellant.
o The Pooling Administrator(s) and block holders/applicant may pursue the disagreement with the appropriate regulatory authorities or their designate.
Requests for modification of these interim guidelines can be pursued as described in the Preface of the guidelines.
13.0 Compliance (Auditing)
The following section addresses compliance monitoring with respect to Number Pooling Assignment Guidelines.
13.1 Purpose of an Audit
The purposes of any audit are two-fold: (1) to provide an educational opportunity to those undergoing the audit, (2) to ensure that the processes and procedures of those being audited are in agreement with established guidelines.
Reasons for the audits include the following:
(1) Ensure uniformity in application of guidelines
(2) Ensure consistent application of guidelines by the Pooling Administrator
(3) Ensure compliance with guidelines by block applicants and Pooling Administrator. .
13.2 Who Should Be Audited
It is expected that the Pooling Administrator, block holders(s), code holder(s) participating in pooling, using or managing the use of NANP resources will be subject to audits.
13.3 Types of Audits
Regularly Scheduled Audits - Audits which are planned in advance by the auditor where the entity being audited is notified in advance and a mutually agreed upon time has been established.
Audits for Cause - Audits which are not planned in advance by the auditor, but are at the specific request of the pooling administrator or a regulatory authority with appropriate jurisdiction.
13.4 Who Should Conduct the Audit
The audit should be conducted by a neutral third party, which does not exclude the pooling administrator.
While this section does not specifically address what entity(ies) will perform the audit, it is imperative that any auditor possess certain characteristics. First, the independence of the auditor must be maintained. Second, the auditor should be an independent third party. Third, the auditor must be competent in the use of and application of standard audit procedures. Finally, any auditor must have knowledge of the block assignment process which is to be audited. These qualifications should ensure that the benefits to be obtained from the audit process are indeed realized.
13.5 Who Should Receive the Results
Audit results should be available to the party being audited and upon request the regulatory authority with appropriate jurisdiction. Consideration of proprietary or confidential information will be given to the distribution of the audit results.
Audit results should be used to identify and recommend to the appropriate organization(s) specific corrective actions that may be necessary.
Examples of specific corrective actions which may be proposed are as follows:
· Modifications to the guidelines
· Additional training for Pooling Administrator and/or block applicants/holders
· Assignment or return of blocks
· Process modifications to Pooling Administrator and/or block applicants/holder maintenance of records for block and/or number assignments
Each entity which undergoes an audit where discrepancies are identified should be required to submit a written report within ten working days to the auditor and upon request to the regulatory authority with appropriate jurisdiction . This report should provide in detail the corrective action which will be taken to resolve discrepancies found in the audit. Within one month, the entity will submit a written report to the Auditor and upon request to the regulatory authority with appropriate jurisdiction certifying that the corrective steps have been taken or are underway.
13.6 How the Audit Would Be Funded
Audits which occur will be funded as specified in the existing Pooling Administrator contract.
13.7 What Should Be Audited
The audit should examine:
1. Overall compliance with these interim guidelines and applicable FCC rules and other regulatory requirements, and
2. Files and records relating to NANP resources. This includes examining a random sample for completeness and accuracy as well as compliance with time intervals specified in these guidelines.
To achieve the benefits of an audit process, various principles and benchmarks contained within these guidelines should be considered during an audit. These principles are reflective of the anticipated benefits of an audit while the benchmarks provide an objective measurement of the degree to which the principles are being met. Examples of these principles and the associated benchmarks are as follows:
Pooling Administrator(s):
1. Principle: Impartial/consistent response to block requests
Benchmarks:
a. Responding to requests within 10 business days.
b. Ensure neutrality pursuant to Administrator of these guidelines
c. Comparable response to like requests.
d. Maintenance of records and block requests
2. Principle: Uniformity in block management practices
Benchmarks:
a. Provides current block utilization study data to CO Code Administrator.
b. Monitors the number of blocks assigned in an NPA for which they are responsible, and notifies CO Code Administrator/NANPA of a significant changes in jeopardy situations.
c. Implement jeopardy NPA and Rate Center procedures.
3. Principle: Consistent treatment and safeguarding of confidential information
Benchmarks:
a. Maintain active/archive records in a secure environment.
b. Uses documented specific processes to ensure confidentiality.
4. Principle: Consistent approach/response to block reservations
Benchmarks:
a. Retains records of reservations.
b. Monitors and conforms to reclamation procedures
Block Applicants:
1. Principle: Substantiation of certification
Benchmarks:
a. Verification of service provided relative to block requests.
b. Verification of regulatory certification.
2. Principle: Uniformity in block management practices
Benchmarks:
a. Substantiates months to exhaust determination.
b. Forecast block requirements.
c. Implement rate center jeopardy procedures.
It should be noted that various forms/reports identified in these Guidelines should facilitate the review of the benchmarks identified above.
13.8 Location of Audit
The actual audit may take place on the service provider's or Pooling Administrator’s premises or, where more practical, the service provider and/or Pooling Administrator may be asked to forward the appropriate documentation to the auditor.
13.9 Auditor’s Responsibilities
The auditor should perform audits in a fair and non-discriminatory manner to encourage efficient utilization of the NANP resources. The auditor should follow generally accepted auditing practices.
13.10 Audits of Code Holders/ Block Holders
13.10.1 Pooling Administrator's Responsibilities in an Audit
The Pooling Administrator(s) will provide the designated auditing agency with current guidelines. The Pooling Administrator(s) may assist the auditor in identifying potential block holders code holders that are utilizing the NANP resource, the relevant criteria to be utilized in the audit, and relevant administrative records related to that criteria.
13.10.2 Block Applicant/Code Holder Responsibilities in an Audit
Each entity being audited is required to provide information requested by the auditor within an agreed upon time frame. The entity shall be responsible to be available to provide clarification necessary for auditor to complete the audit. The entity is required to take corrective action on any discrepancies identified by the auditor.
13.11 Audits of the Pooling Administrator
13.11.1 Pooling Administrator's Responsibilities in an Audit
Pooling Administrator is required to provide information requested by the auditor within the agreed upon time frame. The Pooling Administrator shall be responsible to be available to provide clarification necessary for auditor to complete the audit. The Pooling Administrator is required to take corrective action on any discrepancies identified by the auditor.
13.12 Recommended Audit Time Frames
Regularly Scheduled Audits:
a) of block holder - 1 time per year
b) of Pooling Administrator - 1 time per year
Audits for Cause:
as needed basis.
14.0 Glossary
Active Block A block formally assigned by the Pooling Administrator and implemented by the block holder in the Public Switched Telephone Network (PSTN) for specific routing or rating requirements.
Additonal NNX-X Block A block assigned to a switching entity subsequent to the assignment of the first code (See: Initial Block), for the same purpose as a block that was previously assigned to the same switching entity. A "Growth Block" is requested when the line numbers available for assignment in a previously assigned block code will not meet expected demand.
Affected Parties Affected parties are a) those entities that have applied for and/or received central office block (NXX-X) assignments or reservations within the NXX b) administrative entities involved in number Administrator, number portability or number pooling, c) code holders.
Authorized Representative of The person from the applicant’s organization or its agent that has the
Block Applicant legal authority to take action on behalf of the applicant.
Block 1,000 telephone numbers with all numbers being from within the same 1,000 block range within the NXX
Block Applicant The entity for whom a 1,000 block (NXX-X) is being requested.
Block (NXX-X) Exhaust A point in time at which the quantity of TN’s within existing block (NXX-X) which are "Available for Assignment" equals zero within a switching entity or, conversely, when the quantities of "Working Telephone Numbers" plus "TN’s Unavailable for Assignment" equal 1,000 times the quantity of existing blocks (NXX-X) assigned to a switching entity.
Block Holder The entity to whom a 1,000 block (NXX-X) has been assigned for use.
BRIDS_The Bellcore Rating Input Data Base System (BRIDS) contains data in the rating of calls. Data supports all CO Codes assigned through these Guidelines, as well as all CO Codes in place prior to the existence of these Guidelines, and covers all Numbering Plan Areas (NPAs) administered under the North American Numbering Plan (NANP). BRIDS is a replacement database for BRADS.
Central Office Code The sub-NPA code in a telephone number, i.e., digits D-E-F of a 10-digit NANP Area address. Central office codes are in the form "NXX", where N is a number from 2 to 9 and X is a number from 0 to 9. Central office codes may also be referred to as "NXX codes".
CLLIâ Common Language Location Identifierâ is an eleven-character descriptor of a switch and is used for routing calls.
CO Code (NXX) Exhaust A point in time at which the quantity of TN’s within existing CO codes (NXX) which are "Available for Assignment" equals zero within a switching entity or, conversely, when the quantities of "Working Telephone Numbers" plus "TN’s Unavailable for Assignment" equal 10,000 times the quantity of existing CO codes (NXX) assigned to a switching entity. Where CO code sharing occurs or partial CO codes are assigned to a switching entity, the latter number should be adjusted accordingly.
Certify (When used by the applicant): As part of the Central Office Block (NXX-X) Assignment request, to attest, through a formal statement information contained within the assignment request is true, accurate, and complete to the best of his/her knowledge.
(When used by regulator): Where applicable, to authorize, in writing, an entity to provide a telecommunications service in the relevant geographic area. Such authorization is the responsibility of the appropriate regulatory agency.
COCUS Central Office code Utilization Survey (COCUS) is conducted annually by NANPA from direct input received from Central Office Code Administrator(s) in order to monitor central office code utilization, projected exhaust of NPAs and demand for new NPAs to provide code relief. The purpose of COCUS is to provide an annual overall view of both present and projected CO code (NXX) utilization for each NPA in the NANP.
Code Administrator Entity(ies) responsible for the Administrator of the NXXs within an NPA.
Code Holder The entity to whom a CO code (NXX) has been assigned for use at a Switching Entity it owns or controls.
Conservation Consideration given to the efficient and effective use of a finite numbering resource in order to minimize the cost and need to expand its availability in the introduction of new services, capabilities and features.
Contaminated Block A block that has some quantity of telephone numbers that have previously been assigned by the code holder and thus are unassignable by the block recipient for end user service.
Effective Date The date by which routing and rating changes within the PSTN must be complete for the assigned block. Also, the date by which the block becomes an active block.
Initial Block The first geographic NXX-X block assigned at a unique switching entity.
In Service An active block in which specific subscribers or services are utilizing assigned telephone numbers.
Jeopardy NPA A jeopardy condition exists when the forecasted and/or actual demand for NXX resources will exceed the known supply during the planning/implementation interval for relief. Accordingly, pending exhaust of NXX resources within an NPA does not represent a jeopardy condition if NPA relief has been or can be planned and the additional NXXs associated with the NPA will satisfy the need for new NXX codes.
Jeopardy Rate Center A jeopardy condition exists when the forecasted and/or actual demand for NXX-X resources will exceed the known supply during the planning/implementation interval for relief. Accordingly, pending exhaust of NXX-X resources within rate center does not represent a jeopardy condition if NXX relief has been or can be planned and the additional NXX (s) associated with the Rate Center will satisfy the need for new NXX-X blocks.
LERG Local Exchange Routing Guide: contains information about the local routing data obtained from the Routing Data Base System (RDBS). This information reflects the current network configuration and scheduled network changes for all entities originating or terminating PSTN calls within the NANP excluding Canada.
LERG Assignee The entity to whom a CO code (NXX) has been assigned and/or for performing LERG assignee functions at a Switching Entity it owns or controls. Code Holder does not necessarily imply use of all blocks within the NXX. Same as LERG Assignee.
LRN Location Routing Number
Major Vertical Coordinate A five-digit number used with the Vertical Coordinates and Horizontal Coordinates to pinpoint the location of a rate center. The Vertical and Horizontal Coordinates can be used to calculate mileage measurements between two rate centers that is used to determine the appropriate mileage rates in determining the charge for message telephone service calls.
Minor Vertical Coordinate A five-digit number used with the Vertical Coordinates and Horizontal Coordinates to pinpoint a more specific location. The Minor Vertical and Horizontal Coordinates can be used to divide rate centers into zones for more specific distance calculations. Most often used to rate interstate messages when straight distance between the calling and called point if less than forty miles.
Months to Exhaust = TNs Available for Assignment
Growth (Quantity of Lines added per Month)
NANP The North American Numbering Plan is a numbering architecture in which every station in the NANP Area is identified by a unique ten-digit address consisting of a three-digit NPA code, a three digit central office code of the form NXX, and a four-digit line number of the form XXXX.
NANPA North American Numbering Plan Administrator. With divestiture, key responsibilities for coordination and Administrator of the North American Numbering/Dialing Plans were assigned to NANPA. These central Administrator functions are exercised in an impartial manner toward all industry segments while balancing the utilization of a limited resource.
NANP Area Consists of the United States, Canada and the Caribbean countries currently in NPA code 809.
NPA Numbering Plan Area, also called area code. An NPA is the 3-digit code that occupies the A, B, and C positions in the 10-digit NANP format that applies throughout the NANP Area. NPAs are of the form N0/1X, where N represents the digits 2-9 and X represents any digit 0-9. After 1/1/95, NPAs will be of the form NXX. In the NANP, NPAs are classified as either geographic or non-geographic.
a) Geographic NPAs are NPAs which correspond to discrete geographic areas within the NANP Area.
b) Non-geographic NPAs are NPAs that do not correspond to discrete geographic areas, but which are instead assigned for services with attributes, functionalities, or requirements that transcend specific geographic boundaries. The common examples are NPAs in the N00 format, e.g., 800.
NPAC Number Portability Administrator Center
NPA Code Relief NPA code relief refers to an activity that must be performed when and NPA nears exhaust of its 640 NNX or the 792 NXX capacity. Relief is typically provided to an NPA about a year before its capacity is reached. NPA Code Relief for an NPA that is nearing the 640 NNX limit is usually provided in the form of implementing interchangeable central office code (ICOC) which provides an additional 152 assignable central office codes. An NPA that has been implemented as ICOC has a capacity of 792 assignable NXX central office codes. Providing code relief to such an NPA normally takes the form of assigning a new NPA for an NPA split or overlay. Another option is changing the boundary of the existing NPA.
NPA Relief Date The date by which the NPA is introduced and routing of normal commercial traffic begins.
OCN Operating Company Number (OCN) assignments which must uniquely
identify the applicant.
Relative to CO Code assignments, NECA assigned Company Codes may be used may be used as OCNs. Companies with no prior CO Code or Company Code assignments may contact NECA (201 884-8355) to be assigned a Company Code(s). Since multiple OCNs and/or Company Codes may be associated with a given company, companies with prior assignments should direct questions regarding appropriate OCN usage to Bellcore’s Traffic Routing Administrator (TRA) (908 699-6700). (See Part 1, Footnote 4)
Pooling Administrator Entity responsible for the Administrator of the NXX-X blocks within an NPA.
Premature Exhaust (When referring to NANP): Premature exhaust means the exhaust of NANP resources (i.e., requires expansion beyond the 10-digit format) much sooner than the best industry projections. The NANP is expected to meet the numbering needs of the telecommunications industry well into the 21st century (i.e., a minimum of 25 years).
(When referring to NPA): Premature exhaust is when a specific date for NPA relief has been established and the NPA is projected to exhaust prior to that date.
(When referring to Rate Center): Premature exhaust is when a specific date for NXX relief has been established and the rate center is projected to exhaust prior to that date.
PSTN Public Switched Telephone Network. The PSTN is composed of all transmission and switching facilities and signal processors supplied and operated by all telecommunications common carriers for use by the public. Every station on the PSTN is capable of being accessed from every other station on the PSTN via the use of NANP E.164 numbers.
Rate Center A geographically specified point used for determining mileage-dependent rates for PSTN calls.
RDBS The Routing Data Base System (RDBS) contains a complete description of all Local Exchange Companies’ networks in the NANP Area (except, currently Canada) and pertinent information relating to the networks of other code holders. This provides information for, (1) message routing, (2) common channel signaling call setup routing, and (3) operator service access routing.
Reassignment Refers to the transfer of a working or assigned NXX from one switching entity to another.
Reserved Blocks A block that has been identified and set aside by the Pooling Administrator for some specific use or purpose. This block is not available for assignment but neither has it been officially assigned by the Pooling Administrator(s) to an entity.
Service Providers Any entity that is authorized, as appropriate, by local governmental, state, federal or the NANP Area governmental authorities to provide communications services to the public.
Switching Entity An electromechanical or electronic system for connecting lines to lines, lines to trunks, or trunks to trunks for the purpose of originating/terminating PSTN calls. A single switching system may handle several central office codes.
Technical Requirement A limitation of the Switching Entity where an existing block and/or numbers cannot be used for designated network routing and/or rating of PSTN calls.
Terminating Point Master The TPM contains all the active NPA and CO code (NXX) combinations in the NANP and for each of these points the following is provided: Major Vertical and Horizontal coordinates, LATA/LATA-like code, LATA subzone code, RAO code, place and state, province or country name abbreviation, and time zone indicator.
TN’s Available for Assignment Telephone numbers within existing blocks (NXX-X) which are immediately available for assignment to subscriber access lines or their equivalents within a switching entity.
TN’s Unavailable for Assignment Telephone numbers within existing blocks (NXX-X) which are neither "Working Telephone Numbers" as defined below, nor available for new assignments as working telephone numbers within a switching entity. Examples include numbers required for maintenance testing, numbers reserved for specific customers or specific services, disconnected numbers on intercept, pending connects or disconnects, etc.
Working Telephone Numbers Telephone numbers within existing blocks (NXX-X) which are assigned to working subscriber access lines or their equivalents, e.g., direct inward dialing trunks, paging numbers, special services, temporary local directory numbers (TLDNs), etc., within a switching entity.