Draft-New York Interim Number Pooling

Thousands Block (NXX-X) Assignment Guidelines

TABLE OF CONTENTS

revised 2/275/98

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

PREFACE

1.0 Purpose and Scope of This Document

This document specifies interim guidelines for the assignment processes of thousands blocks (NXX-Xs) to service providers for use at a switching entity 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. CPE modifications
3. Domestic and international switching hardware and software modifications
4. Operational support systems modifications
5. 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 and implemented.

2.4 These assignment guidelines apply only to the assignment of thousands blocks to block applicants serving rate centers: a) that are subject to pooling by industry agreement or regulatory directive or both, and b) where permanent service provider number portability (LNP-LRN) has been implemented by 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. be capable of contributing numbering resources to the pool,
3. 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)
4. 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).
5. minimize the use of blocks (NXX-X) for purposes other than assignment (e.g., test codes)
6. own or control an LNP capable switch serving a rate center subject to pooling.

 

7. be subject to audits to assure compliance with these guidelines, processes and principles (see Section 14).
8. provide a forecast consistent with requirements provided in Section 8.1.3

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.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 These guidelines are not intended to be used to satisfy carriers vanity number needs. Refer to Section 10. 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.1.4 The applicant must have previously submitted a block forecast consistent with requirements provided in Section 8.1.3 in order to be eligible for assignment of blocks.

4.2 Blocks (NXX-Xs) are assigned to service providers for use at a Switching Entity or Point of Interconnection they own or control. Assignment of the initial block(s) will be used to the extent required to provide PSTN traffic as authorized or permitted by the 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 the past 6 months
3. Projected incremental demand for the coming 6 months

4.3.1 The applicant certifies that an additional block(s) are necessary for distinct or unique service needs, separate from the growth blocks as described in Section 4.3. (See Section 1.7 of Part 1 form.) 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.

1. the block is essential to accommodate switch technical or planning constraints;
2. or pending regulatory approval of a tariff and/or certification/registration is pending or approved. 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.
3. the applicant meets the criteria forrequirements 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.1.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 solely to technical constraints (e.g., equipment limitations) solely, the reservation can be extended until the constraint is eliminatedno longer present.

0. Responsibilities of Code Holders and LERG Assignee

The following section describes the responsibilities of the Code Holder/LERG Assignee. This section also defines the relationship between the Code Holder/LERG Assignee and the Block Holder as well as the relationship between the Code Holder/LERG Assignee and the Pooling Administrator.

5.1 Code Holders shall:

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. perform intra-service provider ports prior within the timeframes specified in these guidelines for contaminated blocks.

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. 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)
4. maintain data that is sufficient and can be audited to demonstrate compliance with these guidelines, (see Section 13).

1. 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 Nnumber Pooling Administrator to facilitate block 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. ACTION: Check to make sure this is shown on the form itself.

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

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

6.3.65 Requests for block assignments should not be made more than 6 months (Bell Atl. Suggests 3 months) prior to the requested effective date..

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

6.4 Information Required For Block Allocation

6.4.1 Block Applicants should request effective dates at least 21 (Bell Atl. Suggests 42 calendar days) calendar days , after the date of receipt of the block request by the Pooling Administrator. This 21 (42) 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 from the initially published effective date) 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.12.

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 (Bell Atl. Suggests 66 calendar days for return of initial vacant and contaminated blocks).

6.7.4 Block Holders will provide telephone number utilization reports in accordance with Section 9.1

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.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 Service Provider’s 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.??)

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 to the code administrator and shall assign, at minimum, one block within the NXX code when assigned

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

The pool shall initially be established from donations of service provider embedded resources that meet the criteria outlined in section 8.2.1 and 8.2.4 including, if necessary, new NXX code blocks which are obtained from the CO Code Administrator.

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 existing service providers will submit a forecast, on a semi-annual basisquarterly basis (change to 6 months), by rate area to the Pooling Administrator. The Pooling Administrator may also request a forecast on a per rate center basis if needed. The forecast will be for a rolling 18 month year period submitted using a quarterly view format determined by the Pooling Administrator. The Pooling Administrator will establish and publish a schedule for the semi-annual forecast. If the Pooling Administrator makes a forecast request on a per rate center basis, service providers shall typically reply within a reasonable period of time (e.g., 14 calendar days). If circumstances warrant, the Pooling Administrator may specify a particular time period based on the size and urgency of the request. An initial service provider is expected to provide a forecast at the time they make application for their first block.

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

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 (to whom - NPAC?) 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 do 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 notify the block applicant that the assigned block(s) is contaminated and will provide a list of working Telephone Numbers within the contaminated block that are not available for the block applicant’s use. (Bell Atl. Suggests that the NPAC provide the list of working telephone numbers within the contaminated block).

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

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

• Step 1 - LECs send growth forecasts to Pooling Administrator on a per Rate Center basis

• Step 2 - Based on forecasts and actual growth the Pooling Administrator 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, the Pooling 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.

or

• 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. This service will be provided by the Pooling Administrator for a fee.

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:

• First, assigned to new participating service providers who require a unique LRN
• Second, should be assigned to service providers who volunteer to become the LERG Assignee
• 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

0. Pool Level Maintenance Procedures

The replenishment of the resource via the assignment of a new NXX code, for a particular rate center, shall be subject to the same criteria as that used for thousands blocks made available at the initial establishment of the pool at the outset of block assignments. It is expected that 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.

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

a) any eligible contaminated blocks as defined in section 8.2.3, and

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

9.1 Block Recovery Procedures

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

Service Providers are expected to return a Code and/or Block if the default LERG assignee, assigned to the CO Code, no longer provides service in the rate area associated with the NXX. This is subject to auditing procedures as defined in section 13.0.

9.1.2 The entity to which a block(s) has been assigned from the pool (as opposed to embedded base) shall return the block(s) to the Pooling Administrator if:

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, not to exceed 6 months???.

9.1.4 Pooling Administrator Responsibility

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

1. Assigned, but no longer in use by the assignee(s),
2. Assigned to a service no longer offered,
3. Assigned, but not activated within the 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 issuerequest a letter tofrom 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 and synch with 9.1.3). Also include comment about SP keeping block until technical requirement is 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 2130 calendar days.

A default LERG Assignee who is returning block(s) in conjunction with the return of an NXX code and Section 9.1.1 shall perform all functions necessary to remove the blocks(s) from their internal systems and perform any porting to the NPAC that is necessary in accordance with the existing process and timeframes (total 66 calendar days) used for the establishment of a new CO Code.

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.1. - 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.5 Semi-annual TBUS studies (5 year view at rate center level) will be conducted utilizing projected demand forecasts, provided by block holders (see Section ???), to identify rate centers 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.0 Special Requests & Vanity Numbers

11.0 NPA and NXX 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.

2. 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 ???).
3. NANPA will notify the industry of the NPA in jeopardy via an Information Letter (IL) which will include the code relief date.

D. Prior to any Industry meeting called by the CO Code Administrator, the Pooling Administrator shall call a meeting of all participating pooling members for the purpose of determining a consensus position.

E. The Pooling Administrator shall, unless otherwise explicitly requested not to by an individual member, represent all members of the pool at any Industry Jeopardy Planning Meetings. The Pooling Administrator shall ensure that the conservation measures adopted by the industry reflect the needs of the pooling membership as compared to any single entity not participating in pooling.

1. During the special conservation period, the Pooling Administrator will treat all blockcode requests in a fair and impartial manner, consistent with the special conservation provisions.
2. 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 ???).
3. For additional growth blockscodes , each block holder will certify that existing blockscodes 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).

1. Holders of reserved blocks will be asked to voluntarily return their blocks or confirm their planned reservation dates. See Section ???.
2. Reservations with planned activation dates beyond the "NPA relief date" will be reviewed and filled, with resources made available as a result of NPA relief.
3. 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.
4. 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.

1. Holders of reserved blocks will be asked to voluntarily return their blocks or confirm their planned reservation dates. See Section ???.
2. Reservations with planned activation dates beyond the "NPA relief date" will be reviewed and filled, with resources made available as a result of NPA relief.
3. 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.
4. 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. Following the receipt of final industry procedures, the Pooling Administrator shall develop rate center-specific pooling conservation procedures in conjunction with the affected parties in the jeopardy NPA. The Pooling Administrator will work with the affected parties to continually refine the rate center specific pooling conservation procedures, as necessary, until NPA relief. The Pooling Administrator will notify the appropriate regulating authorities or their designate as well as the Industry Relief Team and, if appropriate, obtain approval for the procedures.
2. 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.
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. The Pooling Administrator will comply with any forecast requests made by the CO Code Administrator. 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 appropriate regulating authorities or their designate of the implementation of the NPA-specific conservation procedure(s) as they occur.

5. 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.2 Rate Center Jeopardy Situations

A rate center jeopardy situation exists when the available resources and the actual and forecasted demand falls below 66 calendar days. This situation is not expected to occur, based on the pooling administrator’s administration responsibilities, but can occur, if demand outpaces the rate center block forecast.

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 this sSection 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.

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

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

• Holders of reserved blocks will be asked to voluntarily return their reserved blocks or confirm their planned reservation dates..
• Reservations with planned activation dates beyond the "Rate Center relief date" will be reviewed, with resources made available as a result of Rate Center relief.
• Reservations with 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. 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.

• Allocation of existing blocks will be on a first-come, first-served basis for all service providers who have previously submitted a block forecast during the most recent forecast cycle, consistent with section 2.6, item H of the guidelines. All available blocks will be allocated, as requested, until no blocks remain.

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 (1^st, 2^nd, and 3^rd 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 cycle, the blocks not requested will be added to the (TBD) blocks available for the following bi-weekly cycle.
4. If more than (TBD) companies/service providers apply for blocksper Step 2, the Pooling Administrator will use a lottery to determine the order in which blocks will be assigned. The first (TBD) companies/service providers will be assigned blocks in the current cycle. Only the remaining companies/service providers will receive blocks in the subsequent cycles(s) until each company/service provider requesting blocks in the bi-weekly cycle has been assigned 1 block.
5. If (TBD) or fewer companies/service providers apply for block(s), all companies/service providers will receive 1 block. If more than a total of (TBD) block(s) is requested, separate lotteries will be used to determine which companies/service providers may be assigned a 2^nd and then a 3^rd block.
6. The second and third block requests that cannot be filled during the bi-weekly cycle in which they are requested will be denied.
7. Requests for block(s) from a future bi-weekly cycle will not be accepted in advance of the first 5 business days of the bi-weekly cycle.
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) and which requests such assignment under Step 1 shall receive assignment priority over all other companies/service providers in the bi-weekly request cycle.. The assignment of blocks to such companies/service providers will reduce the number of blocks available for assignment by lottery under Steps 1 through 7. Should block requests submitted by qualifying companies/service providers exceed (TBD), the Pooling Administrator shall assign the additional blocks from theremaining supply of blocks in future bi-weekly cycles..

Applications may be submitted to Pooling Administrator: (provide name, address, phone, fax, etc.)

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

• 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 the Pooling Administrator. 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 appropriate regulatory authorities or their designate.

Requests for modification of these interim guidelines can be pursued as descried in Section ??? of the guidelines.

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

The audit should examine:

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

2. Files and records relating to NANP resources. . This includes examining a random sample for completeness and accuracy as well as compliance with time intervals specified in these guidelines.

To achieve the benefits of an audit process, various principles and benchmarks contained within these guidelines should be considered during an audit. These principles are reflective of the anticipated benefits of an audit while the benchmarks provide an objective measurement of the degree to which the principles are being met. Examples of these principles and the associated benchmarks are as follows:

14.0 Glossary