New York Interim Number Pooling Thousands Block (NXX-X) Assignment Guidelines PHASE 1
May 26, 1998
TABLE OF CONTENTS
New York Interim Number Pooling Thousands Block (NXX-X) Assignment Guidelines PHASE 1 *
2.0 Considerations, Assumptions and Constraints *
3.0 Block Assignment Principles *
4.0 Pre-conditions and Requirement of the applicant for the Assignment of Thousand Blocks (NXX-X) *
5.0 Responsibilities of Code Holders and LERG Assignee *
6.0 Responsibilities of Block Applicants and Holders *
7.0 Requirements of Pooling Administrator *
7.1 Assignment Process *
7.2 Planning & Reporting Issues *
7.3 Section Intentionally Omitted. *
7.4 General Administrative *
8.0 Initial Establishment of Industry Pool *
8.1 Pool Sizing *
9.0 Pool Level Maintenance Procedures *
9.1 Block Recovery Procedures *
10.0 Special Requests & Vanity Numbers *
11.0 Guidelines Modifications *
12.0 Appeals Process *
13.0 Compliance (Auditing) *
14.0 Glossary *
APPENDIX A: Months To Exhaust Certification Worksheet (Phase 1) *
APPENDIX B: Interim Number Pooling(Nxx-X) Assignment Request Form - Phase I: *
APPENDIX C: NXX-X Interim Number Pooling Administrator's Response/Confirmation *
APPENDIX D: Confirmation of NXX-X Block Activation (Required) *
1.0 Purpose and Scope of This Document
This document specifies interim Phase 1 guidelines for the assignment processes of thousands blocks (NXX-Xs) to service providers for use at a switching entity or point of interconnection (POI) they own or control. In addition, these guidelines outline the processes between the Pooling Administrator, Code Holder and Block Holder.
Number pooling allows for 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. The industry shall define the number of rate centers within the 212 NPA to provide for appropriate block allocation and tracking.
Phase 1 Interim Telephone Number Pooling is defined as an abbreviated version of the limited scope of interim telephone number pooling for New York and will be applicable only for the 212 NPA. This abbreviated version of the limited scope of interim number pooling will begin on July 1, 1998 when Service Providers have made their initial donation of thousands blocks to the interim Industry Pool Administrator for assignment by that interim administrator. Thousand blocks that are donated will consist of only non-contaminated blocks. The Industry Pool established under Phase 1 is expected to be administered by the interim pooling administrator for a period of 12 to 18 months after July 1, 1998.
These guidelines are not a comprehensive discussion of the use of North American Numbering Plan Area (NANP) resources, governmental or regulatory principles, procedures, and requirements.
Where number pooling has not been implemented, or is not in use by the service provider, applicants are considered Code Holders and are still eligible to receive and shall apply directly to the CO Code Administrator for CO Code (NXX) assignments. Guidelines addressing the assignment of central office codes (NXX) are covered under the Central Office (NXX) Assignment Guidelines (INC 95-0407-008). Additionally, Service Providers that have donated thousand blocks to the Industry Pool are still eligible to receive assignment of NXX codes as described in the Central Office (NXX) Assignment Guidelines.
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, including the NY PSC.
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 Section Intentionally omitted.
2.3.1 These Phase 1 guidelines are interim and were developed to operate under a Port-On-Demand architecture environment in the NY NPAs affected by number pooling.
2.3.2 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 directive from the New York Public Service Commission or both, and b) where permanent service provider number portability (LNP-LRN) has been implemented by the block applicant.
2.5 These guidelines do not address the issue of who will fulfill the role of interim Number Pooling Administrator(s). These guidelines were developed by the industry without any assumption on who would be the interim Number Pooling Administrator.
2.6 Participants in the pool are subject to these guidelines and shall:
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 Number Pooling Administrator will assign non-working numbering resources in 1,000 block increments. Resources will be available from only non-contaminated blocks.
3.2 Numbering resources in the Industry Inventory Pool shall be available and assigned to service providers in a fair and non-discriminatory manner.
3.3 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
3.4 Block assignments will be made from NXX codes assigned and utilized within a single rate center.
3.5 The Number Pooling Administrator shall attempt to satisfy all requests (i.e., technical/marketing requests) for a specific NXX-X.
3.6 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.7 There must be a technical need for an initial block assignment. Utilization criteria 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:
3.8 Assignments of additional blocks shall be made based upon both on technical and growth needs.
3.9 These guidelines are not intended to be used to satisfy carriers vanity number needs. Refer to Section 10.
3.10 A block applicant will request their own block from the pool, wherever possible.
4.0 Pre-conditions and Requirement of the applicant for the Assignment of Thousand Blocks (NXX-X)
The assignment pre-conditions and requirements in the following sections shall be used by the Pooling Administrator(s) in reviewing a block request from a service provider for an initial or additional block.
4.1.1 The applicant must be licensed or certified 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.
4.1.2 The applicant must certify a need for a 1,000 block for both initial and additional blocks.
4.1.3 The applicant must submit an NXX-X request form certifying that a need exists for an NXX-X assignment to a point of interconnection or a switching entity. The NXX-X request form must provide an Operating Company Number (OCN) which uniquely identifies the applicant.
4.2 Blocks (NXX-Xs) are assigned to service providers for use at a Switching Entity or Point of Interconnection 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 New York Public Service Commission, and provided all the criteria in Sections 4.1.1 through 4.1.3 are met.
4.3 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 rate center will exhaust within 3 months. However, if a service provider is unable to utilize blocks among multiple switches within the rate area, the certification of existing blocks will be per switching entity/POI per service provided by that switching entity or POI. 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:
4.3.1 The applicant certifies that an additional block(s) are necessary for distinct or unique service needs, separate from the growth blocks as described in Section 4.3. (See Section 1.7 of Part 1 form.)
4.4 Phase 1 of NY 212 Interim Number Pooling does not provide for the reservation of thousands blocks.
5.0 Responsibilities of Code Holders and LERG Assignee
The following section describes the responsibilities of the Code Holder/LERG Assignee. This section also defines the relationship between the Code Holder/LERG Assignee and the Block Holder as well as the relationship between the Code Holder/LERG Assignee and the Pooling Administrator.
5.1 Code Holders shall:
6.0 Responsibilities of Block Applicants and Holders
Applicants, utilizing resources from the pool, shall:
6.1 Additional information and or dialog may be required by the Number Pooling Administrator to facilitate block application processing. The Number Pooling Administrator is still required to respond within 7 calendar days (5 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 the need for assignment of a new NXX to become the LERG assignee for the purpose of being assigned an LRN.
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.
6.3.2 The application form is structured per rate center (and per switch). Per switch is an optional field entry if the service provider is certifying the block at the rate center level instead of the switching entity/POI.
6.3.3 The block applicant must accurately complete all required entries with current information on the Number Pooling (NXX-X) Assignment Request Form. Electronic transfer will be considered as signature.
An Operating Company Number (OCN), which uniquely identifies the applicant, must be provided.
6.3.4 The Block applicant should indicate on the assignment request form 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 assignment request form.
Block applicants will request their own block from the pool, wherever possible.
6.3.5 The Service Provider can refuse the assignment of a block when the block does not meet their technical/marketing constraints. However, a substitute 212 block that meets the Service Provider’s needs may not be available.
6.3.6 Section Intentionally Omitted.
6.3.7 When requesting additional and/or initial block assignments, applicants shall meet the requirements as described in Section 2, 3 and 4 and conform to the conditions contained therein.
6.4 Information Required For Block Allocation
6.4.2 A block applicant or holder will be responsible for entering NXX-X block information (LRN) into the appropriate databases for calling card validation, etc., as they currently do today.
6.5 Ongoing Administration
6.5.1 Notification of changes
The information associated with a block assignment may change over time. Such changes may occur, for example, because of the transfer of a block to a different switching entity within the same rate center. 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/POI. 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.
6.5.2 The holder of a NXX-X block assigned by the Administrator(s) or acquired by other means such as transfer (i.e., by merger or acquisition) must use the block consistent with these guidelines.
6.5.3 Any revisions to the data already submitted on an NXX-X Block Assignment Request Form, Part 1, must be submitted to the Administrator as soon as the block holder is aware of these changes.
6.6 Block Use - Growth Requests
Block assignments are made subject to the conditions listed in Section 2, 3 and 4. A block assigned to an entity, either directly by the Pooling Administrator or through transfer from another entity, should be placed in service within 3 months after the initially published effective date. Certification of in service will be required (see Number Pooling (NXX-X) Assignment Request and Confirmation Form - Part 4). If the assignee no longer has need for the block, 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 3 months, as noted above, the Pooling Administrator will request the return of the block.
6.7 Block Use - Initial Requests
Blocks retained by a service provider through assignment of a new NXX should follow existing requirements, as established in the Central Office Code Assignment Guidelines, for activation of these blocks. The quantity of these blocks to be contributed to the interim industry pool shall be a matter discussed between the service provider and the NY PSC.
6.8 All block holders agree to abide by the block reclamation procedures outlined in Section 9.1.
6.9 Industry Pool/NPA Planning Information
6.9.1 The service provider shall perform all functions necessary to remove the block(s) from their internal systems and donate blocks to the interim Pooling Administrator by July 1, 1998.
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) planning and reporting status regarding pooling resources to Industry and the NY-PSC, and 3) General Administration processes.
7.1.1 The administrator shall accept and process applications for block requests in an efficient and timely manner, and will treat all block requests in a fair and impartial manner, consistent with assignment processing procedures.
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 Section Intentionally Omitted.
7.1.4 The Pooling Administrator will work with Service Providers and will first attempt to fill requests with no specific block requirements first with the 0, 1, 8 and 9 thousand blocks.
7.1.5 The Pooling Administrator reserves the right to negotiate specific assignment of thousands blocks (e.g., which thousands block to assign) with the service provider.
7.1.6 Section Intentionally Omitted.
7.1.7 Section Intentionally Omitted.
7.1.8 Section Intentionally Omitted.
7.1.9 If the assigned block is not used within the time frame specified in Section 6.6 of these guidelines, the Pooling Administrator shall request the return of the block for reassignment.
7.1.11 The Pooling Administrator shall conduct a meeting of the industry to finalize the allocation procedure of blocks from the interim industry pool. After this process is approved by the industry, it shall remain in effect and transition to long term target architecture number pooling in the 212 NPA, or transition to Interim Number Pooling, Phase 2.
7.2 Planning & Reporting Issues
7.2.1 The pooling administrator shall prepare and publish reports as required to industry, NANPA, and the NY-PSC on utilization of the industry pool.
7.2.2 The administrator shall monitor the supply of available blocks for each of the rate centers being administered
The administrator should be aware of any restrictions or conditions (i.e., such as 2 way EAS) associated an NXX from which a block or blocks has been donated.
7.3 Section Intentionally Omitted.
7.4.1 With the initial establishment of the industry pool, the Pooling Administrator shall maintain a secure industry database, accessible to all service providers, that will include all pooled 1000 blocks, the status of the block, (i.e., assigned, non-assigned ).
7.4.2 The Pooling Administrator may arrange for and/or perform audits of service provider utilization of assigned resources, as required.
7.4.3 The Pooling Administrator will participate in and or facilitate audits, as required.
7.4.4 The Pooling Administrator shall:
b) Assist CO Code Administrator in analyzing and helping to resolve problems related to misrouted calls and calls that cannot be completed.
c) Track 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. The establishment of the industry pool is being developed through discussions between individual service providers and the NY PSC regarding the amount of uncontaminated thousands blocks that will be donated to the pool. The date by which all initial blocks are to be donated to the interim pooling administrator is July 1, 1998.
8.1.1 The size of the industry pool will be determined once final negotiations have concluded between individual service providers and the NY PSC. The NY PSC will advise the industry and the interim pooling administrator of the exact amount of thousands blocks that will be donated. It is anticipated that service providers will provide a one-time donation of those blocks to the industry pool by 7-1-98. It is also anticipated that the size of the pool may be increased from subsequent donations of thousands blocks from new service providers when they are assigned a new NXX code in the 212 NPA or subsequent embedded uncontaminated blocks from service providers as individually agreed to as discussed with the NY PSC
9.0 Pool Level Maintenance Procedures
The size of the industry pool will be initially established effective July 1, 1998. On a going forward basis, it is also anticipated that the size of the pool may be increased from subsequent donations of thousands blocks from new service providers when they are assigned a new NXX code in the 212 NPA. The addition of any new blocks, if any, resulting from assignment of full NXX codes to new service providers will be communicated to the Pooling Administrator from the NY PSC. Additionally, the process of block reclamation, as described in section 9.1, may result in the addition of blocks to the industry pool.
Service Providers are expected to return a block if the assignee no longer provides service in the rate area associated with the 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:
9.1.3 Section Intentionally Omitted.
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):
The administrator will seek clarification from the assignee(s) regarding the alleged non-use or misuse. If the assignee(s) provides an explanation satisfactory to the administrator, the block(s) will remain assigned. If no satisfactory explanation is provided, the administrator will issue a letter to the assignee(s) requesting return of 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 presumed to be reclaimed and be made available for reassignment in the pool after 30 calendar days.
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 NY-PSC any application from block assignees under two instances: 1) service provider refuses and disputes return of a block, and 2) when extensions on block activation dates meets one or more of the following criteria:
Referral to the NY-PSC 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 reassignment 21 calendar days following industry notification.
9.1.8 Responsibilities of the New York Public Service Commission
The NY-PSC or their designate will:
10.0 Special Requests & Vanity Numbers
Request for a block to satisfy a single vanity number is not allowed.
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 New York Public Service Commission or the NE LLC.
Disagreements will arise between the Pooling Administrator and block holders/applicants in the context of the administration 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:
Requests for modification of these interim guidelines can be pursued as described in Section 11 of the guidelines.
The following section addresses compliance monitoring with respect to Interim Number Pooling Thousands Block Assignment Guidelines.
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.
(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 that are planned in advance by the auditor where the entity being audited is notified in advance.
Unscheduled Audits - Audits that are planned in advance by the auditor, where the entity being audited are not notified in advance.
Audits for Cause - Audits that are not planned in advance by the auditor, but are at the specific request of the pooling administrator or the NY-PSC or other 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 performing audits. Finally, any auditor must have knowledge of the block assignment process that 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 NY-PSC. 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.
• Modifications to the guidelines
• Additional training for Pooling Administrator and/or block applicants/holders
• Assignment or return of blocks
• Requiring supporting documentation of future block requests in non-compliant situations
• Process modifications to Pooling Administrator and/or block applicants/holder maintenance of records for block and/or number assignments
Each entity that 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 NY-PSC. 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 NY-PSC certifying that the corrective steps have been taken or are underway.
13.6 Section intentionally removed.
The audit should examine:
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):
Benchmarks:
(a) Responding to requests within 7 calendar days.
(b) ensure neutrality pursuant to administration 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) Follows procedures for allocation of blocks.
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.
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.
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 and 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 timeframe. 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 timeframe. 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.
a) of block holders - X percent of block holders per year
b) of Pooling Administrator - interval to be determined
Unscheduled Audits:
of block holder - Y percent of block holders per year ( spot check Y_% of service providers on specific items most likely subject to non-conformance (to be determined by auditor) at least once on an annual basis.
Audits for Cause:
as needed basis.
| 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. | |
| Assigned Block | A 1000 block which has been requested by a service provider and subsequently confirmed by the interim number pooling administrator via the official assignment of a 1000 block from the interim industry inventory pool. | |
| Additional NXX-X Block Assignment for Growth | A block assigned to a switching entity or point of interconnection 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 or point of interconnection. 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 administration, number portability or number pooling. | |
| Authorized Representative of Block Applicant | The person from the applicant’s organization or its agent that has the 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/POI 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/POI. | |
| 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/POI 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/POI. Where CO code sharing occurs or partial CO codes are assigned to a switching entity/POI, 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 administration of the NXXs within an NPA. | |
| Code Holder | assignee of a full NXX code (10,000 telephone numbers) prior to the creation of the industry pool. Code Holders are considered potential candidates for donating thousand blocks upon initial establishment of the industry pool, but are not necessarily required to do so. In rate centers where number pooling has been implemented, the term "Code Holder" is only meaningful up to and including initial establishment of the industry pool. Subsequent to establishment of the industry pool, the term "Code Holder" is now referred to as "LERG Assignee". | |
| 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. | |
| 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 or point of interconnection. | |
| In Service | An active block in which specific subscribers or services are utilizing assigned telephone numbers. | |
| Interested Parties | Interested parties are service providers providing service within an area in which number pooling has been implemented. | |
| 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. | |
| LATA | Local Access and Transport Area, also referred to as service areas by some BOCs, and serve two basic purposes: to provide a method for delineating the area within which the BOCs may offer services and, to provide a basis for determining how the assets of the former Bell System were to be divided between the BOCs and AT&T at divestiture. | |
| 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 | In rate centers where number pooling has been implemented, the term "LERG Assignee" is used describe the service provider selected and responsible for default routing functions associated with an NXX code. The term LERG assignee will replace the term code holder where the code holder has donated blocks to the pool. LERG Assignees may be required, upon assignment of a new NXX code, to donate up to nine 1K blocks to the industry pool. The term "LERG Assignee" does not imply the service provider is authorized to administer or utilize all 10,000 TNs within an NXX code for which it is the LERG assignee. | |
| LRN | Local 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 Administration. With divestiture, key responsibilities for coordination and administration of the North American Numbering/Dialing Plans were assigned to NANPA. These central administration 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. | |
| Non-Contaminated Block | A 1000 block in which no telephone numbers are currently assigned, reserved or aging to or for an end user or utilized for test purposes. | |
| 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.
|
|
| NPAC | Number Portability Administration 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 Administration (TRA) (908 699-6700). (See Part 1, Footnote 4) | |
| Point of Interconnection (POI) | The physical location where a carrier’s connecting circuits interconnect for the purpose of interchanging traffic on the PSTN. | |
| Pooling Administrator/Interim Number Pooling Administrator | Entity responsible for the administration 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. |
|
| Private Networks | Private networks are composed of stations which are not directly accessible from all PSTN stations via the use of NANP E.164 numbers. | |
| 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/POI to another. | |
| Regulatory Authority or Appropriate Regulatory Authority | Term used as referenence to the New York State Public Service Commission. | |
| 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. | |
| TBUS | Thousand Block Utilization Survey (TBUS) is conducted ????annually by the Pooling Administrator from direct input received from Block Holders in order to monitor block utilization, projected exhaust of NXXs and demand for new NXXs to provide block relief. The purpose of TBUS is to provide an annual overall view of both present and projected block (NXX-X) utilization for each NXX in the NPA. | |
| Technical Requirement | A limitation of the Point of Interconnection or 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) or Central Office Codes (NXX) which are immediately available for assignment to subscriber access lines or their equivalents within a switching entity/POI. | |
| TN’s Unavailable for Assignment | Telephone numbers within existing blocks (NXX-X) or Central Office Codes (NXX) which are neither "Working Telephone Numbers" as defined below, nor available for new assignments as working telephone numbers within a switching entity/POI. 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 (TN’s) | 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/POI. | |
APPENDIX A: Months To Exhaust Certification Worksheet (Phase 1)
(Worksheet to be used for Requests for Additional Blocks for Growth)
Date: _____________
Company Name: __________________________________
Switching Entity/Point of Interconnection (CLLI): __________________________________ OR Rate Center:_______________________
NPA: ______ NXX-Xs included in growth calculation: ______________________________
Signature of Authorized Representative of Block Applicant: ___________________________
Title: _________________________ Telephone No.: _________________ FAX No.: _________________ E-Mail: ___________________
A. Telephone Numbers (TNs) Available for Assignment (See Glossary): _________
Month #1 Month #2 Month #3
B. Previous 3 - month incremental _______ _______ _______
growth history:
C. Projected incremental growth _______ _______ _______
Month 1-3:
D. Average Monthly Growth Rate (From Part C above): _________
Average Monthly Growth Rate (D)
Explanation:__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
APPENDIX B: Interim Number Pooling(NXX-X) Assignment Request Form - Phase I:
Please complete the following form. Use one form per switch per rate center block request. Preferred methods for forms completion are e-mail or web-site submission; however, US mail and fax are acceptable. Completed forms should be sent to the Interim Number Pooling Administrator.
The applicant is on notice that block assignments are granted subject to the condition that all block holders are subject to the Interim Phase 1 Number Pooling Thousands Block (NXX-X) Assignment Guidelines which are published and available from the Interim Number Pooling Administrator. A block assigned to an entity by the Interim Number Pooling Administrator should be placed in service within 3 months after the initially published effective date.
These guidelines may be modified from time-to-time. The assignment guidelines in effect shall apply equally to all block applicants and all existing block holders.
The applicant and the Interim Number Pooling Administrator acknowledge that the information contained on this request form is sensitive and will be treated as confidential. Prior to confirmation of block assignment by the Interim Number Pooling Administrator, the information in this form will only be shared with the appropriate administrator and/or regulators.
I hereby certify that the following information requesting an block NXX-X is true and accurate to the best of my knowledge and that this application has been prepared in accordance with most current Interim Phase I Number Pooling Thousands Block (NXX-X) Assignment Guidelines in effect.
It is understood that the applicant will return the block NXX-X to the Interim Number Pooling Administrator for reassignment in accordance with block recovery procedures outlined in the guidelines.
________________________________
Signature of Authorized Representative of Block Applicant
________________________________
Title
________________________________
Date
1.1 Contact information:
Block Applicant
Entity Name: ________________________________________
Contact Name:_______________________________________
Address:____________________________________________
City, State, ZIP:_______________________________________
Phone:______________FAX:____________ E-Mail ___________________
Interim Number Pooling Administrator
Name:____Shannon Collins - Lockheed Martin__________________________
Address:___200 South Wacker Drive, 34th floor__________________________
City, State, ZIP:____Chicago, Illinois 60606____________________________
Phone:_312-382-0564_____ FAX:__312-382-8080_____ E-Mail __shannon.collins@npac.com__
Switch Identification (Switching Entity / POI): ________________
City or Wire Center Name ___________________
Rate Center ________________ Sub Zone _________________
Homing Tandem Operating Company: ___________ Tandem Homing CLLI: ___________
Route same as: NPA___ NXX-X ____Use Same Rate Center as: NPA ____ NXX ____
Number of Blocks Being Requested:____________
1.3 Dates
Date of Application _____________________ _Requested Effective Date _____________
1.4 Type of Entity Requesting the Block:
a) Local Exchange Carrier ___
Interexchange Carrier ___ Other (specify) _________________________
b) Type of service for which block is being requested:
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
Yes ____ No _____
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
d) Blocks (NXX-X) Assignment Preference ____ (optional)
e) Blocks (NXX-X) that are undesirable for this assignment, if any ___________________
1.5 Type of Request (Select One):
_____ Block NXX-X request for New Application for existing switching entity or point of interconnection (Applicant must complete Section 1.7)
_____ Additional block NXX-X for growth (Applicant must complete Section 1.6)
_____ Update information (Block NXX-X) requiring update _____
1.6 Additional Block NXX-X Request for Growth)
Basis of eligibility for an additional NXX-X for growth assigned to the switching entity/POI assumes the following: the initial NXX-X or the NXX-X previously assigned to a new application meets the exhaust criteria, as specified in the Interim Phase I Thousands Block Number Pooling (NXX-X) Assignment Guidelines, and as restated below.
NPA/Rate Center Situation
1.7 NXX-X Request for New Application
Basis of eligibility for an additional block NXX-X means that there has not been an NXX-X assigned to this switching entity/point of interconnection for this purpose. (Check the applicable space and, if applicable, provide the requested information).
______NXX-X is necessary for distinct routing, rating or billing purposes
____________________________________________________________________
______Other (Explanation required) The applicant must provide an explanation of why existing resources assigned to that entity cannot satisfy this requirement.
____________________________________________________________________
APPENDIX C: NXX-X Interim Number Pooling Administrator's Response/Confirmation
Date of Application: __________ Block Effective Date: __________
Date of Receipt: __________ Date of Response: __________
Interim Number Pooling Administrator Contact Information:
___________________________ Phone: ____312-382-0564____________________
Signature of Interim Pooling Administrator
___Shannon Collins_______________ Fax:_____312-382-8080___________________
Name (print)
____shannon.collins@npac.com_____
E-mail Address
___ NPA-NXX: _____ Block(s) Assigned: _____ Date of NXX-X Block Assignment: _____
___ NPA-NXX: _____ Block(s) Assigned: _____ Date of NXX-X Block Assignment: _____
___ NPA-NXX: _____ Block(s) Assigned: _____ Date of NXX-X Block Assignment: _____
___ NPA-NXX: _____ Block(s) Assigned: _____ Date of NXX-X Block Assignment: _____
a. Switch Identification (Switching Entity / POI): ________________ Rate Center: __________
Additional information required in the following section(s):
_____________________________________________________________________
___ Form complete, Block request denied.
Explanation:___________________________________________________________
_____________________________________________________________________
___ Assignment activity suspended by the administrator.
Explanation:___________________________________________________________
Further Action: ___________________________________________________________
APPENDIX D: Confirmation of NXX-X Block Activation (Required)
By signing below, I certify that the thousand block(s) (NXX-X(s)) specified in Section 1 below is in service and is being used for the purpose specified in the original application.
_________________________________________ _________________________ Representative of Block Applicant (Print) Signature
_________________________________________ ____________
Title Date
_________________________________________
Company Name
1. NPA-NXX-X block(s): ________________________________________________
2. Applicant’s Switch Identification (Switching Entity / POI) : __________________
3. Applicant’s Rate Center ______________________________
4. Dates:
Date of Application: ___________
Effective Date: ___________