Draft-New York Interim Number Pooling

Thousands Block (NXX-X) Assignment Guidelines

TABLE OF CONTENTS

revised 2/9 & 105/98

Section

Title

Objective

 

Preface

 
     

1.0

Purpose and Scope

 
     

2.0

Considerations, Assumptions and Constraints

     

3.0

Block Assignment Principles

 
     

4.0

Pre-conditions and Requirement of the Applicant for the Assignment & Reservation of Thousand Blocks (NXX-X)

*Criteria for 1,000 number block assignment.

Grandfathered NXX assignments

Utilization and fill

Access to the Industry Pool

     

5.0

Responsibilities of Code Holder & LERG Assignee

 

     

6.0

Responsibilities of Block Applicants & Holders

Who updates NPAC with block assignment, PA or SP?

[if blocks are shown in LERG, maintenance of information]

[If NPAC needs to know e.g. snapback to block holder , update NPAC]

     

7.0

Requirement & Reponsibilities of Pooling Administrator

Who updates NPAC with block assignment, PA or SP?

Process of assigning block

[If NPAC needs to know e.g. snapback to block holder , update NPAC]

 

     

8.0

Establishment of Industry Pool

Process to submit block to pool

     

9.0

Pool Level Maintenance Procedures

 
     

10.0

Special Requests & Vanity Numbers

 

 

Maintenance of these Guidelines

 

11.0

Jeopardy Situations

NPA

Rate Center

form in appendix

12.0

Appeals Process

Dispute resolution

     

13.0

Compliance (auditing)

Role of regulatory bodies

Serviced Provider Certification of usage

     

14.0

Glossary

 

Appendices A to F

  • Months To Exhaust Certification Worksheet
  • Timelines
  • 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

 
 

Forecast/TBUSCOCUS Form (per section 6.7)7.3, 6.7, 9.2, 8.1.3

 
     
 

Reports

Industry/Regulatory Reports on utilization of the pool & forecast on projected future usage.

 

Open Items: Vacant and blank number treatment Snap back and contamination

 

 

PREFACE

 

 

 

It may be necessary to modify the guidelines periodically to meet changing and unforeseen circumstances. Questions regarding the maintenance of the guidelines or requests for changes may be directed to:

 

New York Interim Number Pooling Guidelines Committee

Attention: Beth Gunter

Bell Atlantic

1 East Pratt Street, 3E

Baltimore, Maryland 21202

(TEL) 410-736-6811

(E-MAIL) beth.a.gunter@bellatlantic.com

 

OR

 

Rochelle Jones

Time Warner

300 First Stamford Place

Stamford, CT 06902-6732

(TEL) 203-328-4002

(E-MAIL) rochelle38@aol.com

 

Illinois Number Pooling Guidelines Committee:

Shawn Murphy

Pat Fleck

 

 

 

1.0 Purpose and Scope of This Document

 

This document specifies interim guidelines for the assignment processes ofthousands 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, Block Holder, CO Code Administrator and NPAC.

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 appropriate NANP area 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 shall apply directly to the CO Code Administrator for numbering resources. Guidelines addressing the assignment of central office codes (NXX) are covered under the Central Office (NXX) Assignment Guidelines (INC 95-0407-008).

 

 

 

2.0 Considerations, Assumptions and Constraints

 

The development of the assignment guidelines include the following assumptions and constraints:

 

2.1 NANP resources, including those covered in these guidelines, are collectively managed by the North American Telecommunications industry with oversight of the North American regulatory authorities.

 

The NANP resources are considered a public resource and are not owned by the assignees or the administrator. Consequently, the resources cannot be sold, brokered, bartered, or leased by the assignee for a fee or other consideration.

 

If a resource is sold, brokered, bartered, or leased for a fee, the resource is subject to reclamation by the Pooling Administrator.

2.2 NANP numbering resources shall be assigned to implement the most effective and efficient use of a finite numbering resource in order to prevent premature exhaust of the NANP and delay the need to develop and implement costly new numbering plans. Efficient resource management and code conservation are necessary due to the industry impacts of expanding the numbering resource (e.g., expansion from 10 to 11 digits). Impacts to the industry include:

 

  1. Customer impacts (e.g., dialing, number changes to advertising and stationary, security systems, etc.)
  2.  

  3. CPE modifications
  4.  

  5. Domestic and international switching hardware and software modifications
  6.  

  7. Operational support systems modifications
  8.  

  9. Reprogramming of non-telecommunications data bases that contain telephone numbers.

 

 

2.3 These guidelines are interim and were developed to operate under a Port-On-Demand architecture environment in the NY NPAs affected by number pooling. These guidelines are intended to remain in place until national guidelines are developed.

 

2.4 These assignment guidelines apply only to the assignment of thousands blocks to block applicants serving rate centers: a) that are subject to pooling by industry agreement or regulatory directive or both, and b) where permanent service provider number portability (LNP-LRN) has been implemented by the block applicant.

2.5 These guidelines do not address the issue of who will fulfill the role of Number Pooling Administrator(s). These guidelines were developed by the industry without any assumption on who would be the Number Pooling Administrator.

 

2.6 Applicants, utilizing resources from the pool, shall:

 

  1. The block applicant have or has applied for the appropriate regulatory approval to operate in the area.,
  2.  

  3. be capable of contributing numbering resources to the pool,
  4.  

  5. collectively agree to provide authorization to the Pooling Administrator to obtain NXX numbering resources from the CO Code Administrator for the Industry Pool. (see section 7.4)
  6.  

  7. establish internal policies and practices that provide for the efficient use and assignment of numbers to end users. These policies and practices shall balance product specifications and market strategies and customer needs with conservation principles to ensure best practices in number utilization. These policies should minimize contamination levels by assigning numbers from one contaminated block before assigning numbers from any other block (sequential number assignment).
  8.  

  9. minimize the use of blocks (NXX-X) for purposes other than assignment (e.g., test codes)
  10.  

  11. own or control an LNP capable switch serving a rate center subject to pooling.
  12.  

     

  13. be subject to audits to assure compliance with these guidelines, processes and principles (see Section 14).

 

 

 

3.0 Block Assignment Principles

 

The following assignment principles apply to all aspects of the Number Pooling Guidelines:

 

3.1 Where number pooling has been implemented, the Number Pooling Administrator will assign non-working numbering resources in 1,000 block increments. Resources will be available from both contaminated and non-contaminated blocks.

 

3.2 A requirement for an entire NXX code (i.e., 10,000 numbers) to satisfy the numbering needs for a single customer may be satisfied by the CO Code Administrator with an informal copy to the Pooling Administrator

 

3.3 Numbering resources in the Industry Inventory Pool shall be available and allocated to service providers in a fair and non-discriminatory manner, including special requests for specific blocks.

 

3.4 The information submitted by applicants for block assignments shall be kept to a minimum and shall be uniform for all applicants. All information provided on the NXX-X request form will be considered confidential, 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.

 

3.5 Block assignments will be made from NXX codes assigned and utilized within a single rate center.

 

3.6 The Number Pooling Administrator shall attempt to satisfy all requests (i.e., technical/marketing requests) for a specific NXX-X.

3.7 Any entity that is denied the assignment of one or more blocks under these guidelines has the right to appeal that decision per Section 12.0.

 

3.8 There must be a technical need for an initial block assignment. Utilization criteria or forecasts will not be used to justify an initial block (NXX-X) assignment. The technical need for an initial block assignment will be based upon one of the following:

  1. on identification of a new switching entity,
  2. physical point of interconnection (POI), or
  3. unique rate center requirements consistent with regulatory restriction.

 

3.9 Assignments of additional blocks shall be made based upon both on technical and growth needs -last sentence needs additional wordsmithing. Also, some of this section, if not all, belongs in section 4.

 

3.10 Requests for block reservation will be accepted. Block applicants should demonstrate good faith efforts to eliminate or to minimize the number of reserved blocks.

 

3.11 Single Vanity Number - refer to section 10.

 

3.12 Block assignment while the NPA and/or rate center is in jeopardy will require special handling as referenced in section 11.0.

 

3.13 A block applicant will request their own contaminated block from the pool, wherever possible.

 

 

 

4.0 Pre-conditions and Requirement of the applicant for the Assignment & Reservation of Thousand Blocks (NXX-X)

 

The assignment pre-conditions and requirements in the following sections shall be used by the Pooling Administrator(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, if required, 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 to the extent required to provide PSTN traffic as authorized or permitted by the appropriate regulatory or governmental authorities, and provided all the criteria in Sections 4.1.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 switching entity/POI, per service provided by that switching entity or POI, will exhaust within 6 months. In addition, the block holder must have documented and be prepared to supply as described in this Section, Sections 2 and 3, and Section 14 (Compliance) supporting data in the form of:

 

  1. Telephone Numbers (TNs) available for assignment
  2. Incremental growth history for 6 months
  3. Projected incremental demand for the coming 6 months

 

 

4.3.1 The applicant certifies that an additional block(s) is necessary for distinct customer routing or rating, tariff or billing purposes (e.g., Information Services). PARKING LOT ISSUE: Not sure if this is still applicable in number pooling. Policy issue. If we keep, move to section 3.8.

 

4.4 To reserve a block, block applicant must demonstrate that:

 

  1. the block is essential to accommodate technical or planning constraints or pending regulatory approval of a tariff and/or certification/registration. If regulatory approval is pending, the applicant must certify and provide appropriate documentation that a request for regulatory certification/registration has been submitted to the appropriate regulatory body to provide service when the applicant has provided a proposed use date within 6 months.
  2.  

  3. the applicant meets the requirements of block assignment as outlined in Sections 2, 3 and 4.4???.

 

4.4.1 If a reserved block is not activated within six months (check timeframe), the block will be released from reservation. See Section 9.2.

 

4.4.2 Reservations may be extended under the following circumstances:

 

  1. When the proposed block effective use date will be missed due to circumstances beyond the control of the applicant (e.g., hardware, software provision delays, regulatory delays, etc, upon written request to the Number Pooling Administrator, one reservation extension of 3 months will be granted. See Section 7.
  2. When the reservation was due to technical constraints (e.g., equipment limitations) solely, the reservation can be extended until the constraint is no longer present.

 

 

 

  1. 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:

 

  1. identify eligible blocks for donation to the pool upon initial establishment of the pool,
  2. provide blank and vacant code announcements prior to NPAC update,
  3. verify and test that the NXX is open prior to the NXX code effective.
  4. work with block holders to ??????
  5. coordinate with the Pooling Administrator in applying for a new NXX code. What about RDBS/BRIDS input - who inputs this, who sends in forms, etc.??

 

 

 

6.0 Responsibilities of Block Applicants and Holders

 

Applicants, utilizing resources from the pool, shall:

 

  1. Have documentation demonstrating that the applicant is licensed and/or certified, or has applied for regulatory approval to operate in the service area for which the central office thousands block is required
  2. be capable of contributing numbering resources to the pool,
  3.  

  4. provide (written) authorization to the Number Pooling Administrator to obtain NXX numbering resources from the CO Code Administrator for the Industry Pool. (see section 7.4)
  5.  

  6. maintain sufficient and audible data to demonstrate compliance with these guidelines, (see Section 14).

 

6.1 Additional information and or dialog may be required by the number Pooling Administrator to facilitate application processing. The Number Pooling Administrator is still required to respond within 10 business days.

 

6.2 If a service provider is deploying a new switching entity that requires the assignment of an LRN, the block applicant will indicate on the request form the need for assignment of a new NXX to become the LERG assignee for the purposes of being assigned an LRN. NOTE from Illinois: if SP needs an LRN, then they go directly to the CO Code Administrator to get a new NXX and then return unused blocks. Send copy of request to Pool Administrator. Other option is to change LERG ownership.

 

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 and Confirmation Form (Block Request Form).

 

6.3.2 There is no upper limit on the number of blocks that can be requested on one application form. The application form is structured per rate center, per switch. However, a request for an entire NXX code to satisfy the numbering needs for a single customer may be submitted to the CO Code Administrator with an informal copy to the Pooling Administrator.

6.3.3 The block applicant must accurately complete all required entries with current information on the Block Request Form. Additionally, block applicant must certify that necessary governmental/regulatory authorization has been obtained to provide the service(s) for which the block is being requested. Electronic transfer will be considered as signature.

 

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.3.4 The Block applicant should indicate on the request if any thousands block (i.e., 0-9) can be assigned or whether, for technical/marketing reasons, only certain thousands blocks may be assigned. The block applicant can request specific blocks on their application.

 

A block applicant will request their own contaminated block from the pool, wherever possible.

 

The Service Provider can refuse the assignment of a block when the block does not meet their technical/marketing constraints.

 

6.3.5 Requests for block assignments should not be made more than 6 months prior to the requested effective date.

 

6.3.6 When requesting additional and/or initial block assignments, applicants shall meet the requirements as described in Section 2, 3 and 4 4 and conform to the conditions contained therein.

 

 

6.4 Information Required For Block Allocation

 

6.4.1 Block Applicants should request effective dates at least 21 calendar days , after the date of receipt of the block request by the Pooling Administrator. This 21 calendar day interval is necessary because internal company notification, etc. 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.

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 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. For data integrity reasons, the Pooling Administrator must be informed of these types of changes to ensure that an accurate record of the entity responsible for the block and the data associated with the block is accurate.

 

It is the responsibility of the block holder to 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.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. Additionally, the new block holder must participate in the audit process.

 

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. This information is necessary regardless of who has RDBS and BRIDS database input responsibilities.

 

 

 

 

6.6 Block Use

 

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 6 months) (review this date since this will give you 12 months overall - suggest 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 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.6.1 All block holders agree to abide by the block reclamation procedures outlined in Section 9.2.

6.7 Industry Pool/NPA Planning Information

 

6.7.1 All block holders shall provide forecasted block requirements to the Pooling Administrator for projecting rate center exhaust and for input to the NPA code relief planning process. All such forecasts shall be treated on a proprietary basis.

 

6.7.2 Block Holders will provide to CO Code Administrator demand for rate centers that are not pooled using existing COCUS procedures. Block Holder will provide to Pooling Administrator forecast data for rate centers included in number pooling. Forecasted block information furnished by block holders shall be submitted on the form provided in Appendix ??to the Pooling Administrator. This forecast data will then become input to the annual COCUS study conducted by the CO Code Administrator.

 

6.7.3 The service provider shall perform all functions necessary to remove the block(s) from their internal systems and perform any porting to the NPAC that is necessary within ??? calendar days.

 

 

 

7.0 Requirements of Pooling Administrator

 

The following describes the responsibilities of the pooling administrator in: 1) assigning blocks of numbering resources to eligible service providers, 2) reporting status regarding pooling resources to Industry and Regulatory Authorities, 3) Forecasting & Planning, 4) General Administration processes.

 

 

7.1 Assignment Process

 

7.1.1 The administrator shall accept and process applications for block requests in an efficient and timely manner. Requests for block assignments shall be responded to within ten (10) business days.

 

7.1.2 The administrator shall confirm that the applicant is eligible to make the request, and that the service provider has certified a need for the block assignment.

 

7.1.3 The administrator should attempt to satisfy industry demands based on the technical and usage requirement of each service provider 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.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 and a contaminated block, where applicable..

 

7.1.5 The Pooling Administrator reserves the right to negotiate specific assignment of thousands blocks (e.g., which thousands block to assign, assign partial request or hold entire request) with the service provider when only a portion of the application can be satisfied immediately with blocks from the pool.

 

7.1.6 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.1.7 The PA is responsible to apply for new NXX codes in three specific instances: 1) a SPs request can only partially be filled, and 2) periodic replenishment of the pool is required and 3) need new NXX code assignment for LRN purposes. The PA shall request NXX codes to the CO Code Administrator acting as the authorized agent for the LERG assignee/service provider ACTION: Need legal review by carriers. (see section 2.??)

 

If a service providers request can only partially be filled with available blocks from the pool, the PA will submit a CO Code Application form to the Code Administrator within 2 business days of review of the application. The PA must also identify the LERG assignee (see section 9.1 for LERG Assignee process) including forwarding a copy of the filed Central Office (NXX) application to the designated LERG assignee. The Code Administrator then has 10 business days to respond to to the PA regarding the CO Code Application. The PA will then respond back to service provider no later than the 14th business day to provide pertinent information relating to the NXX code assignment.

 

The PA is responsible for obtaining 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 form and forward it to the CO Code Administrator for normal processing in accordance with CO Code guidelines. Upon request of a Service Provider and for a fee, the Pooling AdministratorThe PA may perform input of Part 2 data acting on behalf of the service provider.is/is not responsible for Part 2 input. Service Providers may also elect to perform Part 2 inputs themselves or request a third party to input this data. (This does not imply that the PA will be doing RDBS/BRIDS input or NPAC inputs. What responsibilities will the PA have regarding RDBS input? ACTION: Need to clarify with LERG SME.)

 

 

 

7.1.8 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 (i.e., LERG assignee) 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 Pooling Administrator will submit the appropriate application tofrom the code administrator and shall assign, at minimum, one block within the NXX code when assigned (this last sentence conflicts with section 7.12.5). (note to move closer to 7.11). Need to review this along with 7.13 - people prefer wording in 7.13)

 

PA will identify company (OCN), switch and LRN, effective date and Tandem(?) as part of the assignment process of a thousand block. Who will input this data into LERG?? See

 

In instances where the Service Provider does not designate a particular rate center for LRN assignment purposes, the administrator should recommend which rate center should be assigned an NXX in order to ensure efficient utilization of numbering resources. (needs wordsmithing here)

 

7.1.9 The Pooling Administrator will ensure that the block applicant places the code in service within the time frame specified in Sections ??? and ??? of these guidelines. If the assigned block is not used within this time frame, the Pooling Administrator(s) shall request the return of the block for reassignment.

 

7.1.10 The Pooling Administrator will perform block reclamation processes

 

 

 

 

7.2 Reporting Issues

 

7.2.1 The pooling administrator shall prepare and publish reports quarterly or as required to industry, NANPA,and regulatory authorities on utilization of the industry pool and provide forecasts on projected future usage.

 

7.2.2 The pooling administrator will provide jeopardy notification status (see section 11).

 

 

7.3 Forecasting & Planning

 

7.3.1 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.3.2 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 at 9 month’s supply,

c) assure the availability, based upon industry established criteria, of numbering resources within the industry inventory for a given rate center,

d) add to the resources in the industry inventory pool when necessary, by requesting additional CO codes from the CO code administrator, consistent with yet to be established process.

 

7.3.3 The Pooling Administator will also aggregate Block Holder forecast data and submit data to the Code Administrator(s) and to the NANPA for use in the annual COCUS studies.

 

 

7.4 General Administrative

 

7.4.1 The Pooling Administrator shall maintain 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 (i.e., specific TNs not available) with the initial establishment of the pool. 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 Wordsmith this to include that PA will keep confidential certain sections of data and let PA figure out how to set up db.

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:

 

a) provide copies of the thousand block code assignment guidelines when requested by applicants, including timely notification of changes.

 

b) Assist CO Code Administrator in analyzing and helping to resolve problems related to misrouted calls and calls that cannot be completed.

 

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 that meet the criteria outlined in section ??? including, if necessary, new NXX code blocks which are obtained from the CO Code Administrator.

 

8.1 Pool Sizing

 

8.1.1 The pooling administrator will determine what level of resources is needed to meet the demand and will advise the Service Providers of blocks that are required for return. The pooling administrator will also determine what contamination level (e.g.,7%) is required to meet demand. In cases where the NPA or rate center is in jeopardy, the pooling administrator will need to re-evaluate the pool size.

 

8.1.2 The size of the number pool will be a 9 month’s supply for each rate center will be determined from pooling analysis of service provider’s forecast.

 

8.1.3 All service providers will submit a forecast, on a quarterly basis (change to 6 months), by rate area to the Pooling Administrator. The forecast will be for a rolling 1 year period submitted using a quarterly view format determined by the Pooling Administrator. NOTE: AT&T, Sprint feel 6 months is more appropriate.

 

8.1.4 The Pooling Administrator will aggregate rate center forecasts and develop a new forecast using aggregated and other analysis factors (e.g., considering historical growth). If block demand will exceed availability of returned blocks, the Pooling Administrator will request additional NXX codes, as required, from the Code Administrator.

 

8.2 Process for Identifying and Donating Embedded Resources

 

 

8.2.1 Participants shall identify, and submit to the Pooling Administrator, all blocks which have contamination of no more than 10% (including zero). Of those blocks, participants may retain identified blocks if the provider can certify that:

 

a) a block will exceed 10% contamination within 6 months,

b) if only one block exists, or

c) 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 (as certified in section c above) for validity and will refer disputed reasons to the appropriate regulating authorities or their designate.

 

 

8.2.2 Service Providers will identify the actual working telephone numbers of any contaminated blocks that are being returned.

 

8.2.3 The pooling administrator will build the pool by taking first all clean/vacant blocks, then contaminated blocks, where needed,. For contaminated blocks, the Pooling Administrator will take back blocks with the least amount of contamination first (taking blocks from all service providers equally) until pool supply is satisfied. Lastly, the PA will apply a new NXX codes if both vacant and contaminated blocks to not adequately satisfy pool level.

 

 

8.2.4 All vacant blocks that a service provider cannot justify retaining initially will be returned to the Pooling Administrator. Porting of numbers from contaminated blocks (i.e., intra service provider port) will occur when the block is donated to the industry pool. When a contaminated block is assigned, the Pooling Administrator will notifiy the block applicant that the assigned block(s) is contaminated and will provide a list of working Telephone NumbersNs within the contaminated block that are not available for the block applicant’s use.

8.2.5 The service provider shall perform all functions necessary to remove the block(s) from their internal systems and perform any porting that is necessary within ??? calendar business days.

 

 

8.3 New CO Code Requests Procedures

 

8.3.1 The following provides the process flow and activation procedures for CO Codes in order to provide additional blocks to the Industry Inventory Pool:

 

 

 

 

 

 

 

or

 

8.3.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. Pool Level Maintenance Procedures

 

 

The replenishment of the resource via the assignment of a new NXX code, for a particular rate center, shall be subject to the same criteria as that used for thousands blocks made available at the initial establishment of the 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 numbering resources for rate centers meets demand and prevents exhaustion.exhaust.

 

The pooling administrator will maintain the pool required level by first replenishingpopulating the industry pool by obtaining:

a) any eligible contaminated blocks as defined in section 8.??, and

b) new blocks via the assignment of a CO Code.

 

9.1 Block Recovery Procedures

 

Utilization reports from service providers can be requested on a specific rate center basis, as needed. Service providers are expected to provide utilization reports on an annual basis, at minimum. It is expected that return of contaminated blocks within this process will occur within 30 calendar days. blocks to be returned

 

9.1.1 Assignee/Block Holder Responsibility

 

RReturn Code/Block if the default LERG assignee, assigned to the 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???) This is subject to auditing procedures as defined in section ???.

 

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:

 

  1. It is no longer needed by the entity for the purpose for which it was originally assigned
  2. The service it was assigned for is disconnected,
  3. The block(s) was not activated within the timeframe specified in these guidelines, or
  4. If contamination is below 10% for which service provider cannot justify retention per section 8.1 (wordsmith to include a block that never reaches 10%. Also refer to the appropriate section regarding updating LNP DB upon donation of contaminated block to pool.

 

 

9.1.3 If the block(s) was not activated within the timeframe specified in these guidelines, the assignee may apply to the Pooling Administrator for an extension date. Such an extension request must include the reason for the delay and a new activation time commitment.

 

9.1.4 Pooling Administrator Responsibility

The Pooling Administrator will contact any block assignee(s) identified as not having returned to the administrator for reassignment any block(s):

  1. Assigned, but no longer in use by the assignee(s),
  2. Assigned to a service no longer offered,
  3. Assigned, but not activated within the timeframe specified in these guidelines,
  4. Assigned, but not used in conformance with these assignment guidelines,
  5. Assigned, but where contamination is below 10% for which service provide cannot justify retention per Section 8.1, or (check section # & wordsmith)
  6. A previously activated block is not now in use.

 

 

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. The letter will request that they contact the administrator within 30 days regarding the alleged resource non-use or misuse. The block will be made available after 30 days for assignment.

 

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 (check date - action). Also include comment about SP keeping block until technical reqmt. Resolved.

 

9.1.6 The Pooling Administrator will receive, process, and refer to the appropriate regulating authorities any application from block assignees when extensions on block activation dates meets one or more of the following criteria:

 

  1. Activation has not occurred within the 90 day extension,
  2. Administrator believes that the activation has not occurred due to reason within the assignee’s control, or
  3. Assignee requests an extension in excess of 90 days.

Referral to the appropriate regulating authorities or their designate will include the offered reason why the extension was requested, a new proposed activation date, and the administrator’s recommended action.

 

The Pooling Administrator will make all returned resources available for assignment after 30 calendar days.

 

9.1.7 The Pooling Administrator will advise the regulating authority of any disputed reclamation actions.

 

9.1.8 Regulating Authorities or their Designate Responsibilities

 

The regulating authorities or their designate will:

  1. Accept all referrals of disputed alleged non-use or misuse of blocks(s) from the Pooling Administrator or any other entity,
  2. Investigate the referral,
  3. Review referrals in the context of these assignment guidelines,
  4. Attempt to resolve the referral, and
  5. Direct the Pooling Administrator regarding the action, if any, to be taken.

 

 

9.2 Ongoing Block Holder Forecasting Process -

 

9.2.1 All service providers will submit a forecast as described in Section 8.1 (Pool Sizing and in Section 6.7 (Industry Pool/NPA Planning Information).

9.2.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 annual COCUS studies for projecting NPA exhaust. The Pooling Administrator will internally aggregate, analyze & synthesize forecast data for use in determining rate center exhaust.

 

9.2.3 All block holders agree to abide by the block reclamation procedures outlined in Section 9.12. - maybe move to block assignment principles if not already there.

 

9.2.4 The Pooling Administrator will aggregate service provider data as described in Section 8.1 (Pool Sizing).

 

9.2.54 Semi-annual TBUS studies will be conducted utilizing projected demand forecasts, provided by block holders (see Section ???), to identify rate centersNPAs 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.

 

9.2.5 The Pooling Administrator will aggregate service provider data as described in Section 8.1 (Pool Sizing).

 

 

 

10.0 Special Requests & Vanity Numbers

 

Request for a block to satisfy a single vanity number is not allowed.

 

 

11.0 NPA and NXX Jeopardy Situations

 

11.1 NPA Jeopardy Situations

 

When it is determined by the Code Administrator(s) based on the NPA Code Relief Planning Guidelines (INC 94-1216-004check this number) that an NPA is in jeopardy, the following actions will be taken to provide relief in the jeopardy NPA.

 

  1. The Code Administrator(s) will notify the appropriate regulatory authority(ies) and the Pooling Administrator that the NPA is in jeopardy and that special conservation procedures will be invoked. If appropriate, the Code Administrator(s) will obtain the approval of the regulatory authority(ies) for the implementation of the special conservation provisions.

 

  1. 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 ???).
  2.  

  3. NANPA will notify the industry of the NPA in jeopardy via an Information Letter (IL) which will include the code relief date.

 

11.1.1 The following are special conservation procedures that will be invoked in the situation of a jeopardy NPA.

 

    1. 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.
    2.  

    3. 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 ???).
    4.  

    5. For additional growth codes , 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. Block holders will have documented and be prepared to supply as described in Section ???, Section ???, and Appendix ???(Audits) supporting data in the form of:

 

    1. TNs available for assignment
    2. Growth history for 3 months
    3. Projected demand for the coming 3 months (See Appendix ???B).
    4.  

      D. For blocks reserved per Section ???4.4:

       

    5. Holders of reserved blocks will be asked to voluntarily return their blocks or confirm their planned reservation dates. See Section ???.
    6. Reservations with planned activation dates beyond the "NPA relief date" will be reviewed and filled, with resources made available as a result of NPA relief.
    7. 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.
    8. In this situation, reservations with the latest planned activation date will be the first blocks to be used for assignment, and the reservation will be canceled.

 

    1. 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 can be submitted to the appropriate regulating authorities or their designate. If the appropriate regulating authorities or their designate reaches consensus that a special purpose block is warranted, the Pooling Administrator will be instructed to make the assignment. The decision to postpone or withdraw a block request is the block applicant’s responsibility and must be submitted in writing to the Pooling Administrator.
    2.  

    3. During the jeopardy period, planning to comply with extraordinary NPA-specific conservation procedures shall commence (Reference Section ???8.5).

 

11.1.2 Unique circumstances within a given jeopardy NPA may require extraordinary NPA-specific pooling conservation procedures. In this event, the following activities shall apply.

 

    1. The Pooling Administrator shall develop NPA-specific pooling 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 pooling conservation procedures, as necessary, until NPA relief. The Pooling Administrator will notify the appropriate regulating authorities or their designate and, if appropriate, obtain approval for the procedures.
    2.  

    3. If good faith efforts to reach agreements have failed, the Pooling Administrator shall draft and submit a proposed recommendation to the appropriate regulating authorities or their designate for approval. This does not preclude any other interested party from submitting an alternate recommendation.
    4.  

    5. 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.
    6.  

    7. The Pooling Administrator will notify the affected parties and the appropriate regulating authorities or their designate of the implementation of the NPA-specific conservation procedure(s) as they occur.
    8.  

    9. The Pooling Administrator will notify the Code Administrator of the NPA-specific conservation procedures to be implemented. The Code Administrator must document any new conservation procedures developed along with results in an Information Letter (IL) for future reference.

 

11.1.3 The special and/or extraordinary block-specific conservation procedures shall remain in effect, if required, until NPA relief has been implemented.

 

 

11.2 Rate Center Jeopardy Situations

 

Need to address a carrier that has unforecasted demand.

 

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. (move this section under assignment process.

 

 

A rate center jeopardy situation existsis when the available resources and the forecasted demand falls below 66 calendar days.

 

When it is determined by the Pooling Administrator based on the criteria outlined in section ??? of these guidelines 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.

 

 

 

  1. Following application for the new CO Code(s), the Pooling Administrator will notify affected parties of the established block relief date for the rate center and the special conservation procedures documented in Section 12.2.??? will be invoked immediately. The 5 business day interval for service providers to submit block applications as outlined in the jeopardy process will commence on the first business day of the week following announcement of the jeopardy. No block requests will be accepted in advance of the first 5 business days of the week following announcement of the jeopardy. If a block is received in the interim, it will be denied and will need to be resubmitted.

 

11.2.1 The following are special conservation procedures that will be invoked in the situation of a rate center jeopardy.

 

2) During the special conservation period, the Pooling Administrator will treat all block requests in a fair and impartial manner, consistent with the special conservation provisions.

 

3) 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 7-14 calendar days days using the ‘Jeopardy TBUS’ form Appendix ???).

 

4)In order to be eligible to obtain thousands blocks while the rate center is in jeopardy, the SP must have returned the TBUS to the PA within the required timeframe.

 

5) For additional blocks for growth, the applicant must certify that existing numbering resources do not reasonably meet the requirements for an additional block(s). Each block holder will certify that existing blocks for the switching entity/POI, per service provided by that switching entity or POI, will exhaust within 3 months. In addition, the block holder must have documented and be prepared to supply as described in Section ???, , and Appendix ???(Audits) supporting data in the form of:

 

    1. Telephone Numbers available for assignment
    2. Incremantal growth history for 3 months
    3. Projected incremental demand for the coming 3 months (See Appendix ???)

 

6) For blocks reserved per Section - ???:

 

 

 

7) During the jeopardy period, extraordinary Rate Center-specific conservation procedures shall commence. In this event the following activities shall apply.

 

 

Suggested Process (same as used for 212 lottery, is shown below)

 

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.

 

    1. Except as provided in Step 3 below, a maximum of (To Be Determined) ??? NXX blocks will be assigned bi-weekly until NXX relief is provided.
    2. During the first 5 business days of each bi-weekly cycle, each service provider may submit its request for no more than (TBD) ??? blocks (1st, 2nd, and 3rd request). Requests should be submitted and received by the Pooling Administrator during the first 5 business days of each bi-weekly cycle. (See Step 9).
    3. If fewer than a total of (TBD)??? blocks (by all service providers combined) are requested during the bi-weekly cyclea month, the blocks not requested will be added to the (TBD)three blocks available for the following bi-weekly cyclemonth.
    4. If more than (TBD)three companies/service providers apply for blocks per Step 2, the Pooling Code Administrator will use a lottery to determine the order in which blockscodes will be assigned. The first (TBD)three companies/service providers will be assigned blocks in the current cyclemonth. Only the remaining companies/service providers will receive blocks in the subsequent cyclesmonth(s) until each company/service provider requesting blocks in the bi-weekly cyclemonth has been assigned 1 block.
    5. If (TBD)three or fewer companies/service providers apply for block(s), all companies/service providers will receive 1 block. If more than a total of (TBD)three block(s) is requested, separate lotteries will be used to determine which companies/service providers may be assigned a 2nd and then a 3rd blockcode.
    6. The second and third block requests that cannot be filled during the bi-weekly cyclemonth the code in which they are requested are requested will be denied.
    7. Requests for block(s) from a future bi-weekly cyclemonth’s allocation of three blocks will not be accepted in advance of the first 5 business days of the bi-weekly cyclemonth.
    8. Not withstanding Steps 1 through 7, any company/service provider which qualifies for assignment of an initial block (i.e., one block in the rate center) 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 bi-weekly request cycle.month of the request. The assignment of blocksNXX codes to such companies/service providers will reduce the number of blocksNXX codes available for assignment by lottery under Steps 1 through 7. Should block requests submitted by qualifying companies/service providers in exceed (TBD)three, the Poolingcode Aadministrator shall assign the additional blocksNXX codes from the remaining supply of blocks in future bi-weekly cycles.NXX codes.
    9. Applications may be submitted to Pooling Administrator: (provide name, address, phone, fax, etc.)

    10. This process will remain in effect until rate center relief is provided.

 

12.0 Appeals Process

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 descried in Section ??? of the guidelines.

 

13.0 Compliance (Auditing)

 

The following section addresses compliance monitoring with respect to Interim Number Pooling Thousands Block Assignment Guidelines.

 

13.1 Purpose of an Audit

 

The purposes of any audit are two-fold:; (1) to provide an educational opportunity to those undergoing the audit, (2) as well as to ensure that the processes and procedures of those being audited are in agreement with established guidelines.

 

Reasons for the audits include the following:

(1) Ensure uniformity in application of guidelines

(2) Ensure consistent application of guidelines by the Pooling Administrator

(3) Ensure compliance with guidelines by block applicants and Pooling Administrator, and,

 

(4) Ensure the efficient and effective use of numbering resources by block applicants/holders and management of numbering resources by the Pooling Administrator.

 

13.2 Who Should Be Audited

 

It is expected that the Pooling Administrator, block holdersapplicant(s), code holder(s) participating in pooling, and service provider(s) using or managing the use of NANP resources will be subject to audits.

 

13.3 Types of Audits

 

Regularly Scheduled Audits - Audits which are planned in advance by the auditor where the entity being audited is notified in advance.

 

Random Audits - Audits which are planned in advance by the auditor, where the entity being audited are not notified in advance. Need to re-evaluate removing this.

 

Audits for Cause - Audits which are not planned in advance by the auditor, but are at the specific request of the pooling administrator or a regulatory authority with appropriate jurisdiction. another entity.

 

13.4 Who Should Conduct the Audit

 

The audit should be conducted by a neutral third party, which does not exclude the pooling administrator.

 

While this section does not specifically address what entity(ies) will perform the audit, it is imperative that any auditor possess certain characteristics. First, the independence of the auditor must be maintained. Second, the auditor should be an independent third party. Third, the auditor must be competent in the use of and application of standard audit procedures. Finally, any auditor must have knowledge of the block assignment process which is to be audited. These qualifications should ensure that the benefits to be obtained from the audit process are indeed realized.

 

 

13.5 Who Should Receive the Results

 

Audit results should be available to the party being audited and upon request and to the regulatory authority with appropriate jurisdiction.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) - Pat to check on whether this should remain in document

• Process modifications to Pooling Administrator and/or block applicants/holder maintenance of records for block and/or number assignments

 

 

Each entity which undergoes an audit where discrepancies are identified should be required to submit a written report within ten working days to the auditor and upon request to the regulatory authority with appropriate jurisdiction 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 upon request to the regulatory authority with appropriate jurisdiction New York PSC certifying that the corrective steps have been taken or are underway.

 

 

13.6 How the Audit Would Be Funded (should this section be removed???)

 

Audits which occur will be funded as specified in the existing Pooling Administrator contract. 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.

 

13.7 What Should Be Audited

 

The audit should examine:

 

  1. overall compliance with these interim guidelines and applicable FCC rules and other regulatory requirements,
  2. .

2. 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

 

Benchmarks:

(a) Responding to requests within 10 business days.

(b) ensure neutrality pursuant to administration of these guidelines

(cb) Comparable response to like requests.

(dc) Maintenance of records and block requests

 

2. Principle: Uniformity in block management practices

 

Benchmarks:

(a) Provides current data for block utilization studyies data to CO Code Administrator.

(b) Monitors the number of blocks assigned in an NPA for which they are responsible, and notifies CO Code Administrator/NANPA of an significant changes in jeopardy situations.

(c) Implementing jeopardy NPA and Rate Center procedures.

 

3. Principle: Consistent treatment and safeguarding of confidential information

 

Benchmarks:

(a) Maintain active/archieve records in a secure environment.

(b) Uses documented specific processes Documents and uses any specific process to ensure confidentiality.

 

4. Principle: Consistent approach/response to block reservations

 

Benchmark:

R (a)Reetains records of reservations.

(b)Monitors and conforms to reclamation procedures

Block Applicants:

 

1. Principle: Substantiation of certification

 

Benchmarks:

(a) Verification of nature of service provided relative to block requests.

(b) Verification of regulatory certificationauthoriationty., as appropriate.

2. Principle: Uniformity in block management practices

 

Benchmarks:

(a) Substantiates months to exhaust determination.

(b) Forecasting block requirements.

(c) Implementing rate center jeopardy jeopardy block procedures.

 

It should be noted that various forms/reports identified in these Guidelines should facilitate the review of the benchmarks identified above.

 

 

13.8 Location of Audit

 

The actual audit may take place on the service provider's or Pooling Administrator’s premises or, where more practical, the service provider and/or Pooling Administrator may be asked to forward the appropriate documentation to the auditor.

 

13.9 Auditor’s Responsibilities

 

The auditor should perform audits in a fair and non-discriminatory manner to encourage efficient utilization of the NANP resources. The auditor should follow generally accepted auditing practicesinciples.

 

 

13.10 Audits of Code Holders/ Service Providers/Block HoldersApplicants

 

13.10.1 Pooling Administrator's Responsibilities in an Audit

 

The Pooling Pooling Aadministrator(s) will provide the designated auditing agency with current appropriate guidelines. The Pooling Aadministrator(s) may assist the auditor in identifying potential block holdersapplicants/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.

 

13.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 an agreed upon timeframe.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.

 

13.10.2 What Should Be Audited

 

Forecast data to support block requests

???? Others items

 

 

13.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.

 

13.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.

 

13.11.12 Pooling Administrator's Responsibilities in an Audit

 

Pooling Administrator is required to provide information requested by the auditor within the required agreed upon timeframe.timeframe. The Pooling Aadministrator shall be responsible to be available to provide clarification necessary for auditor to complete the audit. The Pooling Aadministrator is required to take corrective action on any discrepancies identified by the auditor.

 

13.12 Recommended Audit Timeframes

 

Regularly Scheduled Audits:

a) of block holder - 1 time per year

b) of Pooling Administrator - 1 time per year

 

(Random Audits:

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.) Pat to check revised NANP WG to see if random audits is referenced.

 

Audits for Cause:

as needed basis.

 

 

14.0 Glossary

 

Active Block

A block formally assigned by the Pooling Administrator and implemented by the block holder in the Public Switched Telephone Network (PSTN) for specific routing or rating requirements.

 

Assigned Block

 

 

Allocated Block

 
   

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

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.

 

Conservation

Consideration given to the efficient and effective use of a finite numbering resource in order to minimize the cost and need to expand its availability in the introduction of new services, capabilities and features.

 

Contaminated Block

 

 

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.

 

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.

 

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.

 

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.

 

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 - 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 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

The entity to whom a CO code (NXX) has been assigned and/or for performing LERG assignee functions at a Switching Entity or Point of Interconnection it owns or controls. Code Holder does not necessarily imply use of all blocks within the NXX. Same as 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.

 

NPA

Numbering Plan Area, also called area code. An NPA is the 3-digit code that occupies the A, B, and C positions in the 10-digit NANP format that applies throughout the NANP Area. NPAs are of the form N0/1X, where N represents the digits 2-9 and X represents any digit 0-9. After 1/1/95, NPAs will be of the form NXX. In the NANP, NPAs are classified as either geographic or non-geographic.

a) Geographic NPAs are NPAs which correspond to discrete geographic areas within the NANP Area.

  1. Non-geographic NPAs are NPAs that do not correspond to discrete geographic areas, but which are instead assigned for services with attributes, functionalities, or requirements that transcend specific geographic boundaries. The common examples are NPAs in the N00 format, e.g., 800.

 

 

NPAC

 

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

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.

 

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) 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) 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.