Source: http://ported.com/113glds.html
Timestamp: 2017-03-24 10:08:46
Document Index: 407107197

Matched Legal Cases: ['art 2', 'art 3', 'art 4', 'art 2', 'art 1', 'art 1', 'art 1', 'art 4', 'art 2', 'art 2', 'art 2', 'art 2', 'art 1', 'art 1']

Block Assignment Principles
Criteria for the Assignment & Reservation of 1k Blocks
*Criteria for 1,000 number block assignment.
Grandfathered NXX assignments
Utilization and fill
Access to the Industry Pool
Responsibilities of Code Holder & LERG Assignee
Responsibilities of Block Applicants
[if blocks are shown in LERG, maintenance of information]
[If NPAC needs to know e.g. snapback to block holder , update NPAC]
Responsibilities of Pooling Administrator Process of assigning block
Establishment of Industry Pool
Process to submit block to pool
Maintenance of these Guidelines
form in appendix
Compliance (auditing)
Serviced Provider Certification of usage
Months To Exhaust Certification Worksheet
Extraordinary NXX Rate Center Specific Alternatives
Central Office Block (NXX-X) Assignment Request and Confirmation Forms
NXX-X Code Assignment
Part 2 - Routing and Rating Information (Forms 1-6)
Part 3 - Administrator’s Response/Confirmation
Part 4 - Confirmation of Block Activation
Industry/Regulatory Reports on utilization of the pool & forecast on projected future usage.
Open Items: Vacant and blank number treatment Snap back and contamination
1.0 Purpose and Scope of This Document
This document specifies interim guidelines for the assignment of
thousands blocks (NXX-Xs) to service providers for use at a switching entity or point of interconnection (POI) they own or control. Entities assigned blocks are called block holders. 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. These guidelines do not supersede controlling appropriate NANP area governmental or regulatory principles, procedures, and requirements.
2.0 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. 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 These assignment guidelines apply only to the assignment of 1,000 blocks to service providers serving rate centers: a) that are subject to pooling, and b) where permanent service provider number portability (LNP-LRN) has been implemented by the block applicant. NOTE: reword this thought later.
2.3 NANP numbering resources shall be assigned to permit themost 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:
Customer impacts (e.g., dialing, changes to advertising and stationary, etc.)
CPE modifications
Domestic and international switching hardware and software modifications
Operational support systems modifications
Reprogramming of non-telecommunications data bases that contain telephone numbers.
2.4 These guidelines treat the assignment processes for NXX thousand blocks (NXX-X), including the processes between the Pooling Administrator, Code Holder, Block Holder, CO Code Administrator and NPAC. Guidelines addressing the assignment of central office codes (NXX) are covered under the Central Office (NXX) Assignment Guidelines (INC 95-0407-008).
2.5 The block applicant must be licensed or certified to operate in the area, if required, and must demonstrate that all applicable regulatory authority required to provide the service for which the central office code is required has been obtained.
2.6 These guidelines do not address the issue of who will fulfill the role of Number Pooling Administrator(s). The guidelines described herein were developed by the industry without any assumption on who should be the Number Pooling Administrator.
2.7 Administrative assignment of the CO code thousands block (NXX-X) public resource by an entity does not imply ownership of the resource by the entity performing the administrative function, nor does it imply ownership by the entity to which it is assigned.
2.8 Audits of all parties may be performed to assure compliance with these guidelines, processes and principles. 2.9 An applicant is not required to submit documentation other than a complete and accurate application and certification to the number Pooling Administrator.
2.10 Additional information and or dialog may be required by the number Pooling Administrator to facilitate application processing. The Number Pooling Administrator is still obliged to reply within 10 business days.
3.0 Block Assignment Principles
The following assignment principles apply to all aspects of the Pooling Guidelines:
3.1	All service providers are accountable for the efficient use and assignment of customers within blocks which have been assigned to them. Rochelle to draft text.
3.2	All assignments will be made in 1,000 block increments. 3.3 Requests for number resources should be submitted to the Pooling Administrator. However, requests for an entire NXX code to satisfy the numbering needs for a single customer should be sent directly to the code administrator with an informational copy to the Pooling Administrator. (MAYBE MOVE THIS SECTION TO CODE HOLDER RESPONSIBILITY. NEED TO REVISIT THIS ISSUE - DEPENDS ON WHETHER MARKET ENTRY IS INTO RATE CENTER WHERE THERE IS POOLING OR NO POOLING. IF POOLING, THEN GO TO PA, IF NO POOLING, THEN GO TO CODE ADMINISTRATOR.) 3.4 Numbering resources in the industry inventory pool shall be made equally available and allocated to service providers in a fair and non-discriminatory manner. Specific blocks assignments will be made on a first come, first served basis.
3.5 The information submitted by applicants for block assignments shall be kept to a minimum, shall be uniform for all applicants, and upon request, shall be treated as proprietary and adequately safeguarded.
3.6 It is expected that service providers participating in obtaining numbers from the pool are also capable of contributing numbering resources to the pool.
3.7 Block assignments will be made from NXX codes assigned and confined to a rate center. 3.8 It is acceptable to specify blocks that cannot be used for technical reasons when requesting a block. NEEDS WORDSMITHING.
3.9 Any entity that is denied the assignment of one or more blocks under these guidelines has the right to appeal that decision per Section 13.0. 3.10 There must be a technical need for an initial block assignment. Additional assignments will be made based on technical and growth needs. An initial block assignment will be based on identification of a new switching entity, physical point of interconnection (POI), or unique rate center consistent with regulatory restriction. Utilization criteria or projection will not be used to justify an initial block (NXX-X) assignment.
4.0 Criteria for the Assignment & Reservation of Thousand Blocks (NXX-X)
The assignment criteria in the following sections shall be used by Pooling Administrator(s) in reviewing a block request from a service provider for an initial and/or an additional block.
4.1 Blocks (NXX-Xs) are assigned to entities for use at a Switching Entity or Point of Interconnection they own or control (note: this sentence is a repeat of what is already in scope). Assignment of the initial block(s) will be to the extent required to terminate PSTN traffic as authorized or permitted by the appropriate regulatory or governmental authorities, and provided all the criteria in Sections 4.1.1 through 4.1.4 are met(may also want to add this sentence to scope). 4.1.1 The applicant must be licensed or certified to operate in the area, if required, and must demonstrate 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 All information provided on the NXX-X request form will be considered confidential, with selected information made available publicly only for those fields that must be input to the RDBS and BRIDS. The information placed in the RDBS or BRIDS becomes public upon assignment of the block in the appropriate routing data base product.
4.1.3 The applicant must certify a need for a 1,000 block for both initial and additional blocks. 4.1.4 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 due to routing, billing or tariff requirements. The NXX-X request form must provide an Operating Company Number (OCN) which uniquely identifies the applicant.
4.2 Assignment of additional block(s) will be made for an established point of interconnection or switching entity by satisfying one of the criteria in Sections 4.2.1 to 4.2.3. By completing the request form, the applicant certifies that their existing resources cannot reasonably meet this requirement.
4.2.1 For additional blocks for growth, each block holder will certify that existing blocks for the switching entity/POI, per service provided by that switching entity or POI, will exhaust within 6 months and will have documented and be prepared to supply as described in this Section, Section ???, and Appendix ??? supporting data in the form of:
1. Telephone Numbers (TNs) Available for Assignment
2. Growth history for 6 months
3. Projected demand for the coming 6 months
4.2.2 An additional block(s) is necessary for distinct routing or rating or billing purposes (e.g., Information Services). PARKING LOT ISSUE: Not sure if this is still applicable in number pooling. Policy issue.
4.2.3 Single Vanity Number - Parking LOT issue. Request for a block to satisfy a single vanity number is not allowed. 4.3 Blocks shall be assigned on a first-come, first-served basis. Good faith efforts shall be made to eliminate or to minimize the number of reserved blocks. Special requirements exist in a jeopardy situation. Allocation/Reservation is permitted if the applicant can demonstrate the reservation of the block is essential to accommodate technical or planning constraints or pending regulatory approval of a tariff and/or certification/registration if appropriate documentation to be provided should demonstrate that a request for regulatory certification/registration has been submitted to one appropriate regulatory body to provide service when the applicant has provided a proposed use date within 6 months. (Jo indicated that reservation was permitted so that svc. Providers getting certified and obtaining new switching equipment could make advanced reservation of blocks. Also, pending contract with a potential large business customer who has a need for a particular block, due to centrex dialing needs, may require reservations. Need for a reservation will probably be higher at a block level than at NXX level) Upon written request to the Pooling Administrator(s), one reservation extension of 3 months will be granted when the proposed code use date will be missed due to circumstances beyond the control of the applicant (e.g., hardware, software provision delays, regulatory delays, etc.). See Section 7.
No reservation will be made unless the applicant will meet the requirements of block assignment as outlined in Section 4??? For initial blocks or for additional blocks, dependent upon whether the reserved block is to be an initial or additional block.
If a reserved block is not activated within twelve months (check timeframe), the block will be released from reservation. See Section 7???.
When the reservation was due to technical constraints (e.g., equipment limitations) solely, the reservation will be extended until the constraint is no longer present.
Responsibilities of Code Holders and LERG Assignee
5.1 For initial establishment of the pool, code holders will identify eligible blocks for donation to the pool.
Need to identify responsibilities for participating in pooling
Need to identify responsibilities as network provider i.e., blank and vacant code announcements
Need to identify responsibilities to donate contaminated blocks
Identify communications between Code Holder and Pooling Administrator
Identify communications between CH and BH
Code holder needs to work with block holder 5.2 LERG Assignee Responsibilities
If a new NXX is needed in order to completely fulfill a service provider’s request, the Pooling Administrator will complete the CO Code Application form. The Pooling Administrator will need to obtain additional information to complete part 2 (if required) (i.e., switching info., routing and rating data, etc.) from the designated service provider (i.e., LERG Assignee) in order to complete CO Code Application.
The LERG Assignee is responsible for verifying and testing the NXX is open prior to the Pooling Administrator assigning any blocks of numbers from the designated NXX, and for providing any and all necessary vacant code treatment for the assigned NXX.
What about RDBS/BRIDS input??
6.0 Responsibilities of Block Applicants and Holders
Entities requesting new NXX-X block assignments as well as entities already assigned NXX-X blocks shall comply with the following:
6.1 The block applicant must be licensed or certified to operate in the area, if required, and must demonstrate that all applicable regulatory authority required to provide the service for which the block is required has been obtained.
6.2 These assignment guidelines apply only to the assignment of 1,000 blocks to service providers serving rate centers: a) that are subject to pooling, and b) where permanent service provider number portability (LNP-LRN) has been implemented by the block applicant. NOTE: reword this thought later.
6.3 Service providers requesting blocks of numbers must be eligible to submit a request to the Pooling Administrator. That is, the service provider must be LNP-capable and the service provider must own or control a LNP capable switch serving a rate center subject to pooling. In addition, the service provider making the request shall be, at minimum, a LERG NXX code holder, for LRN purposes.
6.4 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 purposes of being assigned an LRN. 6.5 The Application Process
6.5.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 and Confirmation Form (Block Request Form).
6.5.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.5.3 The block applicant will complete all required entries on the Block Request Form to the best of his/her knowledge as well as sign the Form. An Operating Company Number (OCN) which uniquely identifies the applicant must be provided. The applicant can get OCN information by calling TRA. (See the Forms Part 1, Section 2???check sections)
*** Is the information regarding OCN needed? Yes if LERG changes are made. If so, should it be the OCN or the Company Code? OCN, not company code. What does the NPAC need? N/A for the application process. NPAC is not involved.
6.5.4 The Block applicant should indicate on the request if any 1,000 block (i.e., 0-9) can be assigned or whether, for technical reasons, only certain 1,000 blocks may be assigned. The block applicant can request specific blocks on their application.
6.5.5 Requests for block assignments should not be made more than 6 months prior to the requested effective date.
6.5.6 When requesting additional block assignments, applicants shall meet the requirements as described in Section 4.2??? and conform to the conditions contained therein. (Need to wordsmith to include requests for initial blocks)
6.6 Information Required For Block Allocation
6.6.1 (changed from 6.1.4) The block applicant shall certify on the block Request Form that to the best of his/her knowledge necessary governmental/regulatory authorization has been obtained to provide the service(s) for which the code is being requested. Wordsmith to words used earlier in text.
6.6.2 Applicants should request effective dates at least 21 calendar days after the date of receipt of the block request. This 21 calendar day interval is necessary because internal company notification, etc. NEED TEXT. ACTION: Service providers to check if 21 days is okay. It should be noted that interconnection arrangements and facilities need to be in place prior to activation of a block. Such arrangements are outside the scope of these guidelines.
*** Add footnote indicating that the time frame includes the 10 days required for the administrator. Add language regarding contaminated blocks-is additional time required? Determine how long it takes to open a NXX to portability in a switch which isLNP capable. Service providers should verify that the 21 day interval allows for all internal work to be completed.
6.6.3 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.4 Ongoing Administration
6.4.1 Notification of LERG 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. Accordingly, the Pooling Administrator must be informed of these changes to ensure that an accurate record of the entity responsible for the block and the data associated with the block is maintained so as not to jeopardize data integrity.
It is the responsibility of the block holder to arrange for the entry of any changes to RDBS and BRIDS data associated with a switching entity/POI including, but not limited to, Office Functionality and Switching Entity-Network Services through the Administrator, or the company with (AOCN) authorization.
6.4.2 Responsibilities of the Block Holder (do we still need this section? Possible combination with section 6.3.1 above.)
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. Most importantly, the new block holder must participated in the audit process (See Appendix A in CO Code Guidelines and yet to be developed national guidelines) necessary to effectively assess block (numbering?) utilization. Any revisions to the 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. This information is necessary regardless of who has RDBS and BRIDS database input responsibilities.
6.4.3 Block Use
Block assignments are made subject to the conditions listed in Section ??4, Section ??6.1 and Section ??6.2. 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 (date okay) 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 or the contamination level of the block qualifies the block for return to the pool, 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.4.3.1 All block holders agree to abide by the block reclamation procedures outlined in Section 9.2.
6.5 Industry Pool/NPA Planning Information
6.5.1 All block holders shall provide forecasted block requirements to the Pooling Administrator to be used 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.
Changes would be required in existing COCUS process. BH will provide to CO Code Administrator demand for rate centers that are not pooling using existing COCUS procedures. BH will provide to PA for rate centers in pooling. 6.5.2 Forecasted block information furnished by block holders shall be submitted on the form provided in Appendix ??C. This data will be aggregated and submitted to the Code Administrator(s) and to the NANPA for use in the annual COCUS studies.
*** Form needs to be developed for Pooling Administrator to use.
7.0 Responsibilities of Pooling Administrator The following describes the responsibilities of the pooling administrator in assigning blocks of numbering resources to eligible service providers:
7.1 The Pooling Administrator reserves the right to negotiate with the service provider when only a portion of the application can be satisfied immediately with blocks from the pool.
7.2 The PA has 10 business days to respond to a SP 1,000 block application. If a service providers request can only partially be filled with available blocks from the pool, the PA will submit a NXX request to code administrator within 2 business days. The Code Administrator then has 10 business days to respond to a NXX code application. The PA will respond back to service provider on the 14th business day to provide pertinent information relating to the NXX code assignment.
7.3 If a new NXX is needed in order to completely fulfill a service provider’s request, the PA will complete the CO Code Application form. The PA will need to obtain additional information to complete part 2 (if required) (i.e., switching info., routing and rating data, etc.) from the designated service provider in order to complete CO Code Application.
7.4 The PA has permission to act as a service provider agent when requesting NXX codes (i.e., completing code request form and submitting to Code Administrator. ACTION: Need legal review by carriers.
7.5 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.6 The 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.7 The administrator shall accept and process applications for, block requests in an efficient and timely manner. It is expected that requests for block assignments shall be responded to within ten (10) business days.
7.8 The administrator should attempt to satisfy industry demand with blocks associated with the lowest level of contamination; first considering the use of uncontaminated blocks (i.e., 0%), and only then considering employing blocks with increasing levels of contamination (up to 10%).
7.9 The PA should attempt to fill requests with no specific block requirements first with the 0, 1, 8 and 9 thousand blocks. 7.10 The Pooling Administrator shall maintain an industry database accessible to all service providers through some mechanism yet to be defined to include all pooled thousand blocks and the status of the blocks, i.e., assigned, non-assigned and identified contamination with the initial establishment of the pool. The Pooling Administrator shall maintain their own internal database indicating to whom blocks are assigned. The Pooling Administrator shall maintain a secure database that will include all pooled 1000 blocks, the status of the block, (i.e., assigned, non-assigned), and if assigned, the identify of the service provider to which the block is allocated.
7.11 Forecasting & Planning
7.11.1 The Pooling Administrator shall: a) receive and compile forecasts of demand from service providers for numbering resources within given rate centers, b) analyze service provider forecasts to determine the numbering resources required to maintain the industry inventory pool, 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 requesting additional CO codes from the CO code administrator, consistent with yet to be established process.
7.11.2 The administrator shall prepare and publish reports to industry and regulatory authorities on utilization of the pool and provide forecasts on projected future usage. Frequency of reports TBD.
7.12 For LRN assignment purposes, the administrator should recommend which rate center should be assigned a block.
7.13 When the PA identifies the need for additional NXX code to replenish the pool, the Pooling Administrator is responsible to initiate CO code request and identify the LERG assignee. The Pooling Administrator will utilize the process in section 9.1 for selecting a LERG Assignee for a growth NXX that is to be added to the Industry Inventory Pool. The Pooling Administrator is responsible for the following activities:
7.13.1 Determining when a growth NXX is required for the industry inventory pool
7.13.2	Selecting and notifying the default LERG Assignee
7.13.3	Allocating numbers from the growth NXX to the LERG assignee in accordance with their forecasted requirements
7.13.4 selects and notifies participating service provider that they are the LERG Assignee for the growth NXX to be added to the industry inventory pool. 7.13.5 following the INC Central Office (NXX) Application Guidelines, and applies for a NXX on behalf of the selected, default, LERG Assignee; including forwarding a copy of the filed Central Office (NXX) application to the designated LERG Assignee.
7.13.6 When required, input Part 2 data into RDBS and BRIDS for activation V&H, LRN (?), Activation Date (At least 66 calendar days after date of input), etc.
7.14 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), the Pooling Administrator will determine a service provider to provide vacant code treatment 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 from the code administrator and shall receive one block within the NXX code when assigned (this last sentence conflicts with section 7.12.5).
7.15 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 may request a new NXX code from the Code Administrator. 7.16 The Pooling Administrator can refuse the assignment of a block per section ????? (Can a block assignment be refused? Yes)
7.17 The Pooling Administrator may arrange for and/or perform audits of service provider utilization of assigned resources, as required.
7.18 The Pooling Administrator will participate in an audits, as required.
8.0 Initial Establishment of Industry Pool
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 numbers made available to the pool at the outset of block assignments. It is expected that administration of the resource will require periodic replenishment by the assignment of new NXX code(s) assignments such that the pools for rate centers do not exhaust prematurely.
8.1 Criteria for block return from service providers:
Both newly assigned and embedded numbering resources will be considered for inclusion in the industry inventory pool. 8.1.1 Participants shall identify all blocks which have contamination of no more than 10% (including zero). Of those blocks, participants may retain identified blocks if provider can certify that block will exceed 10% contamination within 6 months, if only one block exists or can otherwise justify and explain maintaining block for other technical reasons. Retention of blocks is subject to audit and appeal procedures. Pooling Administrator will assess all technical reasons for validity and will refer disputed reasons to the NY-PSC. 8.1.2 All blocks that a service provider cannot justify retaining initially (both vacant and contaminated blocks) will be returned to the Pooling Administrator. Porting of numbers from contaminated blocks will occur when the block is donated to the pool. If a contaminated block is assigned, Pooling Administrator will notify both the Block Holder and Code Holder simultaneously of the assignment for porting purposes ??? do we need to do this or can CH wait for LERG notification???.
8.2 Pool Sizing 8.2.1 The size of the number pool for each rate center will be determined from pooling analysis of service provider’s forecast. 8.2.2 All service providers will submit a forecast by rate area to the Pooling Administrator. The forecast will be for a 1 year period submitted quarterly utilizing the format determined by the Pooling Administrator. 8.2.3 The Pooling Administrator will conduct an analysis of forecast data and returned blocks. If block demand will exceed availability of returned blocks, the Pooling Administrator will request additional NXX codes, as required, from the Code Administrator.
Include that in the case of 212 or in a jeopardy NPA, we need to develop wording.
Sizing the pool - what constitutes a 9 month’s supply? Analysis of forecast data to determine limit for each rate center
Identify block criteria and get from embedded base and assignment of new nxx’s
9.0 Pool Maintenance Procedures
9.1.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 sends a request to CO Code Administrator for a new NXX for a specific Rate Center. Included in the request will be default LEC, which has been selected by the Pooling Administrator
Step 3 - Concurrent with request to CO Code Administrator, notifies the LEC of his selection as default LEC for the new NXX for that Rate Center Pool.
Step 4 - CO Code Administrator reviews request and notifies the Pooling Administrator and Default LEC of the NXX(s) assignment.
Step 5 - CO Code Administrator assigns the NXX to the LEC in RDBS, Part A.
Step 6 - Default LEC inputs Part 2 into RDBS and BRIDS for activation with V&H, LRN (?), Activation Date (At least 66 calendar days after date of input), etc.
Step 6 - Pooling Administrator inputs Part 2 into RDBS and BRIDS for activation V&H, LRN (?), Activation Date (At least 66 calendar days after date of input), etc. 9.1.2 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:
1. First assigned to new participating service providers who require a unique LRN
2. Second should be assigned to service providers who volunteer to become the LERG Assignee
3. Third 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
9.2 Block Recovery Procedures
9.2.1	Assignee/Block Holder Responsibility
Return Code/Block if default LERG assignee assigned CO Code no longer provides service in the rate area associated with the NXX (need to address this in these guidelines or modified CO Code guidelines???)
The entity to which a block(s) has been assigned shall return the block(s) to the Pooling Administrator if:
It is no longer needed by the entity for the purpose for which it was originally assigned
The service it was assigned for is disconnected, or
The block(s) was not activated within the timeframe specified in these guidelines
if contamination falls below 10% for which service provider cannot justify retention per section 8.1 (wordsmith)
If the block(s) was not activated within the timeframe specified in these guidelines, the assignee may apply to the administrator for an extension date. Such an extension request must include the reason for the delay and a new activation time commitment.
9.2.2	Pooling Administrator Responsibility
9.2.2.1	The Pooling Administrator will contact any block assignee(s) identified as not having returned to the administrator for reassignment of any block(s):
Assigned, but no longer in use by the assignee(s),
Assigned to a service no longer offered,
Assigned, but not activated within the timeframe specified in these guidelines,
Assigned, but not used in conformance with these assignment guidelines.
Assigned, but where contamination falls below 10% for which service provide cannot justify retention per Section 8.1 (wordsmith)
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, and in conformance with these assignment guidelines the block(s) will remain assigned. If no satisfactory explanation is provided, the administrator will request a letter from 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 requesting that they contact the administrator within 30 days regarding the alleged resource non-use or misuse. If the letter is returned as non-delivered the administrator will advise the NY-PSC that the block(s) will be made available for reassignment following the established idle period, if any, unless the NY-PSC advises otherwise within 30 days.
9.2.2.2	The Pooling Administrator will refer to the NY-PSC for resolution any instance where a block has not been returned for reassignment by the assignee if:
The block has not been activated within the timeframe specified in these guidelines.
A previously activated block is not now in use.
An activated block is not being used in accordance with these assignment guidelines.
Activated block contamination level falls below 10% for which service provider cannot justify retention per Section 8.1 (wordsmith)
9.2.2.3	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 (check date).
9.2.2.4	The Pooling Administrator will receive, process and refer to the NY-PSC for resolution any application from block assignees for an extension on block activation date when the:
Activation has not occurred within the 90 day extension
Administrator believes that the activation has not occurred due to reason within the assignee’s control, or
Assignee requests an extension in excess of 90 days.
Referral to the NY-PSC will include the offered reason why the extension is requested, a new proposed activation date, and the administrator’s recommended action.
The Pooling Administrator will make all returned resources available for assignment following the established idle time, if any. (NOTE: What constitutes "established idle time"????
9.2.3	NY-PSC Responsibilities
The NY-PSC will:
Accept all referrals of alleged non-use or misuse of blocks(s) from the Pooling Administrator or any other entity. Investigate the referral,
Review referrals in the context of these assignment guidelines,
Attempt to resolve the referral, and
Direct the Pooling Administrator regarding the action, if any, to be taken.
9.3 Block Forecasting
Block holders are required to forecast projected demand on a semi-annual basis?
How often, process flow, etc.
9.3.1	All block holders shall provide forecasted code requirements to the Pooling Administrator to be used solely for projecting NPA & rate center exhaust and for planning NPA code relief. All such forecasts shall be treated on a proprietary basis.
9.3.2	Information furnished by block holders shall be submitted on the form provided in Appendix ???. This data will be aggregated and submitted by the Pooling Administrator to The CO Code Administrator for use in the annual COCUS studies used for projecting NPA exhaust. The Pooling Administrator will internally assess forecast data for use in determining rate center exhaust.
9.3.3	All block holders agree to abide by the block reclamation procedures outlined in Section 9.2.
10.0 Block Conservation
General Principles to address:
vanity assignments
administration of blocks
preferred/requested blocks
Assignment of NANP Area numbering resources is undertaken with the following objectives: to efficiently and effectively administer/manage a limited NANP resource through block conservation, to delay NPA exhaust and the need for NPA relief (e.g., splits/overlays) for as long as possible and to delay the eventual exhaust of the NANP (see Section ???). {The timelines included in Appendix ??? are provided for illustrative purposes only. However, the "NPA Relief" and the "RDBS Update" dates are the only dates currently recognized as industry standards. - take out?????} In meeting these objectives the following are conservation measures to be taken by Pooling Administrator(s).
10.1	Annual TBUS studies will be conducted utilizing projected demand forecasts, provided by block holders (see Section ???), to identify Naps nearing exhaust. The schedule for projected exhaust will be forwarded by NANPA to the appropriate Pooling Administrator(s) and published in summary format for industry use.
10.2	Ongoing code administration practices which fosterfostedr conservation shall include the following: (See Section 12.1 for jeopardy NPA situations and Section 9.2.1 for block reclamation procedures.)
Use of blocks (NXX-X) for purposes other than assignment (e.g., test codes) should be minimized.
Codes that may result in dialing confusion (e.g., HNPAs, adjacent NPAs used as CO codes) may be preferable for assignments other than to end users (i.e., test codes). Nonetheless, applicants requesting one of these codes are not precluded from receiving it, if unassigned and technically feasible.
Limitations to the reservation of blocks and the request for vanity blocks. (wordsmith) 11.0 Maintenance of these Guidelines
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 Interim Number Pooling Guidelines Committee
Attention: Beth Gunter
1 East Pratt Street, 3E
(TEL) 410-736-6811 (E-MAIL) beth.a.gunter@bellatlantic.com
OR Rochelle Jones
(TEL) 203-328-4002
(E-MAIL) rochelle38@aol.com
12.0 NPA and NXX Jeopardy Situations
12.1	NPA Jeopardy Situations
When it is determined by the Code Administrator(s) based on the NPA Code Relief Planning Guidelines (INC 94-1216-004) that an NPA is in jeopardy, the following actions will be taken to provide relief in the jeopardy NPA.
The Code Administrator(s) will notify the appropriate regulatory authority(ies) and the Pooling Administrator that the NPA is in jeopardy and that specialspecil 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.
The Code Administrator(s) will notify the NANPA and affected parties, including the Pooling Administrator, of the established code relief date and the special conservation procedures documented in Section ??? will be invoked immediately. Affected parties within the jeopardy NPA will be invited to attend a meeting convened by the Code Administrator for an explanation of the special conservation procedures that will be in effect until code relief if implemented and initiate discussion of extraordinary NPA-specific conservation procedures. If and when extraordinary procedures are required in addition to Section ???, the Code Administrator(s) will notify affected parties (See Section ???).
NANPA will notify the industry of the NPA in jeopardy via an Information Letter (IL) which will include the code relief date. 12.1.1	The following are special conservation procedures that will be invoked in the situation of a jeopardy NPA.
During the special conservation period, the Pooling Administrator will treat all code requests in a fair and impartial manner, consistent with the special conservation provisions.
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 ‘Jeopardy TBUS’ form Appendix ???).
For additional codes for growth, each block holder will certify that existing codes for the switching entity/POI, per service provided by that switching entity or POI, will exhaust within 3 months and will have documented and be prepared to supply as described in Section ???, Section ???, and Appendix ???(Audits) supporting data in the form of:
TNs A available for A assignment
Growth history for 3 months
Projected demand for the coming 3 months (See Appendix ???B).
D.	For codes reserved per Section ???4.4:
Holders of reserved blocks will be asked to voluntarily return their blocks or confirm their planned reservation dates. See Section ???.
Reservations with planned activation dates beyond the "NPA relief date" will be reviewed, with resources made available as a result of NPA relief.
Reservations with planned activation dates prior to the "NPA relief date" will not be honored if doing so would preclude the assignment of a block resource for which a certified request has been processed.
In this situation, reservations with the latest planned activation date will be the first blocks to be for assignment, and the reservation will be canceled.
Requests for assignment of blocks codes for other than growth or to serve a new switching entity/POI should be minimized. However, applications for such purposes purpoes can be submitted to the NY-PSC. If the NY-PSC reaches consensus that a special purpose block is warranted, the Pooling Administrator will be instructed to make the assignment, a special purpose block assignment may be appropriate. The decision to postpone or withdraw a block request is the block applicant’s and must be confirmed in writing to the Pooling Administrator.
During the jeopardy period, planning for extraordinary NPA-specific conservation procedures shall commence (Reference Section ???8.5).
12.1.2	Unique circumstances within a given jeopardy NPA may require extraordinary NPA-specific conservation procedures. In this event, the following activities shall apply.
The Pooling Administrator shall develop NPA-specific conservation procedures in conjunction with the affected parties in the jeopardy NPA (See Appendix??? F). The Pooling Administrator will work with the affected parties to continually refine the NPA-specific conservation procedures, as necessary, until NPA relief. The Pooling Administrator will notify the NY-PSC and, if appropriate, obtain approval for the procedures.
If good faith efforts to reach agreements have failed, the Pooling Administrator shall draft and submit a proposed recommendation to the NY-PSC for approval. This does not preclude any other interested party from submitting an alternate recommendation.
The Pooling Administrator will monitor changes in the jeopardy situation using the jeopardy TBUS form (J-COCUS, Appendix E???). Based upon the results of (a) and using the J-COCUS???? information, the Pooling Administrator will implement each NPA-specific conservation procedure as required.
The Pooling Administrator will notify the affected parties and the NY-PSC of the implementation of the NPA-specific conservation procedure(s) as they occur.
The Pooling Administrator will notify the Code Administrator of the NPA-specific conservation procedures to be implemented. The Code Administrator document any new conservation procedures developed along with results in an Information Letter (IL) for future reference.
12.1.3	The special and/or extraordinary block-specific conservation procedures shall remain in effect, if required, until NPA relief has been implemented.
12.2	NXX Jeopardy Situations
When it is determined by the Pooling Administrator based on these guidelines (section ???) that a rate center in the NPA 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.
The Pooling Administrator(s) will notify the NY-PSC that the rate center is in jeopardy and that specialspecil conservation procedures will be invoked. If appropriate, the Pooling Administrator(s) will obtain the approval from the NY-PSC for the implementation of the special conservation provisions.
The Pooling Administrator will notify affected parties of the established block relief date for the rate center and the special conservation procedures documented in Section 12.2.??? will be invoked immediately. 12.2.1	The following are special conservation procedures that will be invoked in the situation of a jeopardy rate center.
Upon receipt of the notice of the jeopardy situation from the Pooling Administrator, each block holder will review their forecast and demand data and provide the information to the Pooling Administrator within ???? days using the ‘Jeopardy TBUS’ form Appendix ???).
For additional blocks for growth, each block holder will certify that existing codes for the switching entity/POI, per service provided by that switching entity or POI, will exhaust within 3 months and will have documented and be prepared to supply as described in Section ???, Section ???, and Appendix ???(Audits) supporting data in the form of:
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 planned activation dates prior to the "Rate Center relief date" will not be honored if doing so would preclude the assignment of a block resource for which a certified request has been processed.
During the jeopardy period, planning for extraordinary Rate Center-specific conservation procedures shall commence (Reference Section ???8.5).
12.2.2	Unique circumstances within a given jeopardy rate center may require extraordinary rate center-specific conservation procedures. In this event, the following activities shall apply.
(Suggest a lottery process similar to what is used for 212 NPA jeopardy instead of trying to develop a process when the jeopardy occurs. If okay, then modify sections A thru E accordingly.)
Suggested Process (same as used for 212 lottery)
A copy of the block request along with Appendix ??? (Central Office Code (NNX/NXX) Assignment Guidelines, INC 95-0407-008) or its equivalent must be forwarded to the commission staff simultaneous with submission to the Pooling Administrator. Companies/service providers are free to submit additional justification information to the PSC staff in support of the application.
Except as provided in Step 3 below, a maximum of three NXX codes will be assigned each month until NPA relief is provided. During the first 5 business days of each month each service provider may submit its request for no more than 3 codes (1st, 2nd, and 3rd request). Requests should be submitted and received by the Code Administrator during the first 5 business days of the month. (See Step 9).
If fewer than a total of three codes (by all service providers combined) are requested during a month, the codes not requested will be added to the three codes available for the following month.
If more than three companies/service providers apply for codes per Step 2, the Code Administrator will use a lottery to determine the order in which codes will be assigned. The first three companies/service providers will be assigned codes in the current month. Only the remaining companies/service providers will receive codes in the subsequent month(s) until each company/service provider requesting codes in the current month has been assigned 1 code.
If three or fewer companies/service providers apply for codes, all companies/service providers will receive 1 code. If more than a total of three codes is requested, separate lotteries will be used to determine which companies/service providers may be assigned a 2nd and then a 3rd code.
The second and third code requests that cannot be filled during the month they are requested will be denied.
Requests for codes from a future month’s allocation of three codes will not be accepted in advance of the first 5 business days of the month. Not withstanding Steps 1 through 7, any company/service provider which qualifies for assignment of one NXX code under 47 C.F.R. Sec. 52.19 (c) (3) (iii) and which requests such assignment under Step 1 shall receive assignment priority over all other companies/service providers in the month of the request. The assignment of NXX codes to such companies/service providers will reduce the number of NXX codes available for assignment by lottery under Steps 1 through 7. Should NXX code requests submitted by qualifying companies/service providers in March 1998 exceed three, the code administrator shall assign the additional NXX codes from the remaining supply of NXX codes.
Applications may be submitted to Code Administrator: Steve McDermott, 140 West Street - Room 1150, New York, N.Y. 10007 Tel. No. 212-285-7323 Fax No. 917-965-0102
This process will remain in effect until all assignable 212 NXX codes are assigned or the process is superseded by number pooling guidelines.
12.1.3	The special and/or extraordinary block-specific conservation procedures shall remain in effect, if required, until rate center relief has been implemented.
13.0 Appeals Process
Disagreements may 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 among 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:
The block holder/applicant will have the opportunity to resubmit the matter to the Pooling Administrator for reconsideration with or without additional input.
Guidelines interpretation/clarification questions may be referred to the New York Number Pooling Industry Guidelines Committee. Unless otherwise mutually agreed to by the parties, these questions will be submitted in a generic manner protecting the identity of the appellant.
The Pooling Administrator(s) and block holders/applicant may pursue the disagreement with the New York State Public Service Commission. Requests for modification of these interim guidelines can be pursued as descried in Section 11 of the guidelines.
14.0 Compliance (Auditing)
The following section addresses compliance monitoring with respect to Interim Number Pooling Thousands Block Assignment Guidelines.
14.1	Purpose of an Audit
The purposes of any audit are two-fold; to provide an educational opportunity to those undergoing the audit as well as 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, and,
(4) Ensure the efficient and effective use of numbering resources by block applicants/holders and management of numbering resources by the Pooling Administrator.
14.2	Who Should Be Audited
It is expected that the Pooling Administrator, block applicant(s), code holder(s), and service provider(s) using or managing the use of NANP resources will be subject to audits.
14.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.
Random Audits - Audits which are planned in advance by the auditor, where the entity being audited are not notified in advance.
Audits for Cause - Audits which are not planned in advance by the auditor, but are at the specific request of another entity.
14.4	Who Should Conduct the Audit
The audit should be conducted by a neutral third party, which does not exclude the 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.
14.5	Who Should Receive the Results
Audit results should be available to the party being audited and to the New York 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.
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 •	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 which undergoes an audit where discrepancies are identified should be required to submit a written report within ten working days to the auditor and the New York 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 New York PSC certifying that the corrective steps have been taken or are underway.
14.6	How the Audit Would Be Funded (should this section be removed???)
It is anticipated that the costs of the audits would be borne by the industry. Audits which occur in the "normal course of business" should be paid for by the industry as a whole through the NANPA Cost Recovery mechanism. Audits for cause requested by industry will be paid for by the party at fault.
14.7	What Should Be Audited
The audit should examine overall compliance with these interim guidelines and applicable FCC rules and other regulatory requirements.
Files and records relating to NANP resources which is being audited. 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
(a)	Responding to requests within 10 business days.
(b)	Comparable response to like requests.
(c)	Maintenance of records and block requests
2.	Principle:	Uniformity in block management practices
Benchmarks:	(a)	Provide data for block utilization studies
(b)	Monitors the number of blocks assigned in an NPA for which they are responsible, and notifies NANPA of an significant changes in jeopardy situations.
(c)	Implementing jeopardy NPA procedures.
3.	Principle:	Consistent treatment and safeguarding of confidential information
(a)	Maintain records in a secure environment.
(b)	Documents and uses any specific process to ensure confidentiality.
4.	Principle:	Consistent approach/response to block reservations
Benchmark:	Retains records of reservations.
Block Applicants:
1.	Principle:	Substantiation of certification
(a)	Verification of nature of service provided relative to block requests.
(b)	Verification of regulatory authority, as appropriate.
(a)	Substantiates months to exhaust determination.
(b)	Forecasting block requirements.
(c)	Implementing jeopardy block procedures.
It should be noted that various forms/reports identified in these Guidelines should facilitate the review of the benchmarks identified above.
14.8	Location of Audit
The actual audit may take place on the service provider's or Pooling Administrator’s premise or, where more practical, the service provider and/or Pooling Administrator may be asked to forward the appropriate documentation to the auditor.
14.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 principles.
14.10	Audits of Code Holders/Service Providers/Block Applicants
14.10.1	Administrator's Responsibilities in an Audit
The Pooling administrator(s) will provide the designated auditing agency with current appropriate guidelines. The administrator(s) may assist the auditor in identifying potential block applicants/code holders/service providers that are utilizing the NANP resource, the relevant criteria to be utilized in the audit, and relevant administrative records related to that criteria.
14.10.2	Block Applicant/Code Holder/Service Provider Responsibilities in an Audit
Each entity being audited is required to provide information requested by the auditor within the required 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.
12.10.2	What Should Be Audited
Forecast data to support block requests
???? Others items
14.11	Audits of the Pooling Administrator
The Pooling Administrator should be audited to ensure they remain a neutral entity pursuant to the NANP Requirements documents. This audit should also examine the administrator's compliance with the interim guidelines and regulations. This audit should have emphasis on fair and consistent treatment of requests for NANP resources, accuracy of records, security, and adherence to the time intervals which are called for in industry guidelines.
14.11.1	What should be audited
Documentation of NANP resource requests for blocks which have been denied.
The Auditor should ensure that the administrator cited valid reasons for the denial and that no specific service provider or industry segment has been denied an inordinate amount of assignment requests.
Security methods which are used to guarantee the safeguarding of proprietary information.
14.11.2	Administrator's Responsibilities in an Audit
Administrator is required to provide information requested by the auditor within the required timeframe. The administrator shall be responsible to be available to provide clarification necessary for auditor to complete the audit. The administrator is required to take corrective action on any discrepancies identified by the auditor.
14.12	Recommended Audit Timeframes
Regularly Scheduled Audits:
of block holder - 1 time per year
of Pooling Administrator - 1 time per year
of block holder - spot check ___% 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:
A block formally assigned by the Pooling Administrator and implemented in the PSTN for specific routing or rating requirements.
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 are a) those entities that have applied for and/or received central office block (NXX-X) assignments or reservations within the NXX; b) all interested parties members of the industry within the affected NPA.
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.
1,000 telephone numbers with all numbers being from within the same 1,000 block range within the NXX
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.
The Bellcore Rating Input Data bBase 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 data base for BRADS. For purposes of the guidelines, the terms BRADS and BRIDS may be considered synonymous.
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.
(When used by the applicant): As part of the Central Office Block (NXX-X) Assignment request, to confirm, 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.
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.
Entity(ies) responsible for the administration of the NXXs within an NPA.
The entity to whom a CO code (NXX) has been assigned for use at a Switching Entity or Point of Interconnection it owns or controls.
Code Protection - TAKE OUT???
Code protection is an arrangement where a central office code assigned in one NPA is not assigned in an adjacent NPA, thereby becoming projected to allow 7-digit dialing across the common boundary.
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.
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.
INC - TAKE OUT????
Industry Numbering Committee, a standing committee of the Industry Carriers Compatibility Forum (ICCF) that provides an open forum to address and resolve industry-wide issues associated with the planning, administration, allocation, assignment and use of numbering resources and related dialing considerations for public telecommunications within the North American Numbering Plan (NANP) area.
The first geographic NXX-X block assigned at a unique switching entity or point of interconnection.
An active block in which specific subscribers or services are utilizing assigned telephone numbers.
Interchangeable NPAs - TAKE OUT????
Refers to an industry plan to expand substantially the supply of Numbering Plan Area codes (NPAs) in January 1995, by removing the restriction that the second digit of the NPA must be a 0 or 1.
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 - TAKE OUT???
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 determiningdeterming how the assets of the former Bell System were to be divided between the BOCs and AT&T at divestiture.
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.
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.
= TNs Available for Assignment______
Growth (Quantity of Lines added per Month)
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.
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 a Area
ConsistsConsista of the United States, Canada and the Caribbean countries currently in NPA code 809.
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.
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.
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.
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)Operating Company Number (OCN) is a term for a four character code used to associate a company with certain records in Bellcore’s RDBS and BRIDS databases, and in related output (e.g., LERG, V&H Coordinates Data). Specific to these guidelines, OCN is intended to identify the company assigned a CO code. Numeric OCNs are assigned by the National Exchange Carrier Association (NECA), and are refered to by NECA as Company Codes. Since some companies may be associated with multiple OCNs, to support consistency in RDBS, BRIDS, and related output, Bellcore’s TRA organization should be contacted first if there is a question about what OCN to use (see Part 1, Footnot 3).
The physical location where a carrier’s connecting circuits interconnect for the purpose of interchanging traffic on the PSTN.
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 are composed of stations which are not directly accessible from all PSTN stations via the use of NANP E.164 numbers.
A geographically specified point used for determining mileage-dependent rates for PSTN calls.
The Routing Data BaseDataBase 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.
Refers to the transfer of a working or assigned NXX from one switching entity/POI to another.
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.
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.
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.
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.
A limitation of the Point of Interconnection or Switching Entity where an existing block and/or numbers cannot be use for designated network routing and/or rating of PSTN calls.
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
The quantity of telephone numbers within existing blocks (NXX-X) which are immediately available for assignment to subscriber access lines or their equivalents within a switching entity/POI.
TN’s Unavailable for Assignment The quantity of 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/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)
The quantity of 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.