-----------------------------------------------------------------------
  NANPA TECHNICAL REQUIREMENTS DOCUMENT

  (Description/Specifications)

  March 2008

  -----------------------------------------------------------------------

# Table of Contents {#table-of-contents .Front-Matter-Header}

Section Page

1\.

Introduction 1-[1](#introduction)

1.1 Purpose
2-[1](#number-range-level2number-range-level3number-range-level4-purpose)

1.2 Scope
3-[1](#number-range-level2number-range-level3number-range-level4-scope)

1.3 Background
4-[1](#number-range-level2number-range-level3number-range-level4-background)

1.4 Attributes
5-[2](#number-range-level2number-range-level3number-range-level4-attributes)

1.5 Environment
6-[4](#number-range-level2number-range-level3number-range-level4-environment)

1.5.1 Regulatory
7-[4](#number-range-level3number-range-level4-regulatory)

1.5.2 Federal Advisory Committee
8-[4](#number-range-level3number-range-level4-federal-advisory-committee)

1.5.3 Industry Activities
9-[5](#number-range-level3number-range-level4-industry-activities)

General Requirements 10-[1](#general-requirements)

2.1 High-Level Requirements
11-[1](#number-range-level2number-range-level3number-range-level4-high-level-requirements)

2.1.1 Assigning and Administering NANP Resources
12-[1](#number-range-level3number-range-level4-assigning-and-administering-nanp-resources)

2.1.2 Accommodating Current and Future Numbering Needs
13-[1](#number-range-level3number-range-level4-accommodating-current-and-future-numbering-needs)

2.1.3 Administrative Resources for Legal, Financial, and Technical
Responsibilities
14-[2](#number-range-level3number-range-level4-administrative-resources-for-legal-financial-and-technical-responsibilities)

2.1.4 Supervision for All Services and Responsibility for Achieving
Performance Objectives
15-[2](#number-range-level3number-range-level4-supervision-for-all-services-and-responsibility-for-achieving-performance-objectives)

2.2 Relationships
16-[2](#number-range-level2number-range-level3number-range-level4-relationships)

2.2.1 United States
17-[2](#number-range-level3number-range-level4-united-states)

2.2.2 International
18-[2](#number-range-level3number-range-level4-international)

2.3 Administration and Management
19-[2](#number-range-level2number-range-level3number-range-level4-administration-and-management)

2.3.1 Requests for Numbering Resources
20-[3](#number-range-level3number-range-level4-requests-for-numbering-resources)

2.3.2 Service Provider and Regulator Support
21-[3](#number-range-level3number-range-level4-service-provider-and-regulator-support)

2.3.3 Numbering Resource Optimization
22-[3](#number-range-level3number-range-level4-numbering-resource-optimization)

2.4 Cost Allocation
23-[4](#number-range-level2number-range-level3number-range-level4-cost-allocation)

2.5 Staffing
24-[4](#number-range-level2number-range-level3number-range-level4-staffing)

2.6 Telecommunications Requirements
25-[4](#number-range-level2number-range-level3number-range-level4-telecommunications-requirements)

2.7 Daily Operations
26-[5](#number-range-level2number-range-level3number-range-level4-daily-operations)

2.7.1 Inquiry Response
27-[5](#number-range-level3number-range-level4-inquiry-response)

2.7.2 Emergency Notifications
28-[5](#number-range-level3number-range-level4-emergency-notifications)

2.7.3 Holidays 29-[5](#number-range-level3number-range-level4-holidays)

2.8 Physical Location
30-[6](#number-range-level2number-range-level3number-range-level4-physical-location)

2.9 Travel
31-[6](#number-range-level2number-range-level3number-range-level4-travel)

2.10 Modification of Guidelines
32-[6](#number-range-level2number-range-level3number-range-level4-modification-of-guidelines)

2.11 Audits
33-[8](#number-range-level2number-range-level3number-range-level4-audits)

2.11.1 For Cause Audits of Service Providers
34-[8](#number-range-level3number-range-level4-for-cause-audits-of-service-providers)

2.11.2 Other Audits of Service Providers
35-[8](#number-range-level3number-range-level4-other-audits-of-service-providers)

2.12 Dispute Resolution
36-[8](#number-range-level2number-range-level3number-range-level4-dispute-resolution)

2.13 Data Security
37-[9](#number-range-level2number-range-level3number-range-level4-data-security)

2.13.1 Limited Access
38-[9](#number-range-level3number-range-level4-limited-access)

2.13.2 Physical Security
39-[10](#number-range-level3number-range-level4-physical-security)

2.13.3 Site Visits
40-[10](#number-range-level3number-range-level4-site-visits)

2.13.4 Data Accessibility
41-[10](#number-range-level3number-range-level4-data-accessibility)

2.13.5 Unauthorized Access
42-[10](#number-range-level3number-range-level4-unauthorized-access)

2.14 Implementation Plan
43-[11](#number-range-level2number-range-level3number-range-level4-implementation-plan)

2.15 NANPA Transition to Successor
44-[11](#number-range-level2number-range-level3number-range-level4-nanpa-transition-to-successor)

2.15.1 Transfer Efficiency
45-[11](#number-range-level3number-range-level4-transfer-efficiency)

2.15.2 Technical Support
46-[11](#number-range-level3number-range-level4-technical-support)

2.15.3 Documentation
47-[12](#number-range-level3number-range-level4-documentation)

2.15.4 Transition Plan
48-[12](#number-range-level3number-range-level4-transition-plan)

2.16 Term of Administration
49-[12](#number-range-level2number-range-level3number-range-level4-term-of-administration)

2.17 Interfaces
50-[12](#number-range-level2number-range-level3number-range-level4-interfaces)

2.17.1 Interface With the Pooling Administrator
51-[12](#number-range-level3number-range-level4-interface-with-the-pooling-administrator)

2.17.2 Interface With BIRRDS
52-[12](#number-range-level3number-range-level4-interface-with-birrds)

2.17.3 Interface With the Number Portability Administration
53-[13](#number-range-level3number-range-level4-interface-with-the-number-portability-administration)

2.17.4 Interface With the Service Providers
54-[13](#number-range-level3number-range-level4-interface-with-the-service-providers)

2.17.5 Interface With the FCC
55-[13](#number-range-level3number-range-level4-interface-with-the-fcc)

2.17.6 Interface With the State Regulatory Agencies
56-[14](#number-range-level3number-range-level4-interface-with-the-state-regulatory-agencies)

2.17.7 Interface With the Media
57-[14](#number-range-level3number-range-level4-interface-with-the-media)

2.17.8 Interface With the ITU Technical Standards Bureau
58-[14](#number-range-level3number-range-level4-interface-with-the-itu-technical-standards-bureau)

2.17.9 Interface With the ITU Study Group 2
59-[14](#number-range-level3number-range-level4-interface-with-the-itu-study-group-2)

2.18 Mobile Identification Number Block Identifier Administrator
60-[14](#number-range-level2number-range-level3number-range-level4-mobile-identification-number-block-identifier-administrator)

2.18.1 MBI Resources
61-[15](#number-range-level3number-range-level4-mbi-resources)

2.18.2 NPA Splits
62-[15](#number-range-level3number-range-level4-npa-splits)

NANP Administration 63-[1](#nanp-administration)

3.1 Numbering Plan Areas (NPAs)
64-[1](#number-range-level2number-range-level3number-range-level4-numbering-plan-areas-npas)

3.2 Central Office (CO) Codes
65-[2](#number-range-level2number-range-level3number-range-level4-central-office-co-codes)

3.3 International Inbound NPA-456 NXX Codes
66-[2](#number-range-level2number-range-level3number-range-level4-international-inbound-npa-456-nxx-codes)

3.4 Personal Communications Service (PCS) NPA Codes
67-[2](#number-range-level2number-range-level3number-range-level4-personal-communications-service-pcs-npa-codes)

3.5 Easily Recognizable Code (ERC) Code 900 NXX Codes
68-[3](#number-range-level2number-range-level3number-range-level4-easily-recognizable-code-erc-code-900-nxx-codes)

3.6 N11 Service Codes
69-[3](#number-range-level2number-range-level3number-range-level4-n11-service-codes)

3.7 Hearing Impairment Codes-800 855 XXXX Line Numbers
70-[4](#number-range-level2number-range-level3number-range-level4-hearing-impairment-codes-800-855-xxxx-line-numbers)

3.8 Information Services Codes-555 XXXX Line Numbers
71-[4](#number-range-level2number-range-level3number-range-level4-information-services-codes-555-xxxx-line-numbers)

3.9 Carrier Identification Codes (CICs)
72-[4](#number-range-level2number-range-level3number-range-level4-carrier-identification-codes-cics)

3.10 Vertical Service Codes (VSC)
73-[5](#number-range-level2number-range-level3number-range-level4-vertical-service-codes-vsc)

3.11 Automatic Number Identification (ANI) II Digits
74-[5](#number-range-level2number-range-level3number-range-level4-automatic-number-identification-ani-ii-digits)

Central Office Code Administration
75-[1](#central-office-code-administration)

4.1 Requirements
76-[1](#number-range-level2number-range-level3number-range-level4-requirements)

4.2 Functional Specifications
77-[1](#number-range-level2number-range-level3number-range-level4-functional-specifications)

4.2.1 User Services
78-[2](#number-range-level3number-range-level4-user-services)

4.2.2 Processing
79-[2](#number-range-level3number-range-level4-processing)

4.2.3 Communication/Notification Functions
80-[3](#number-range-level3number-range-level4-communicationnotification-functions)

4.2.4 Status Reporting
81-[3](#number-range-level3number-range-level4-status-reporting)

4.2.5 Tracking CO Code Utilization for NPA Relief
82-[4](#number-range-level3number-range-level4-tracking-co-code-utilization-for-npa-relief)

4.2.6 Management of Jeopardy Conditions
83-[4](#management-of-jeopardy-conditions)

4.3 Management of the Code Inventory
84-[4](#number-range-level2number-range-level3number-range-level4-management-of-the-code-inventory)

4.4 Resource Reclamation
85-[4](#number-range-level2number-range-level3number-range-level4-resource-reclamation)

NPA Relief Planning 86-[1](#npa-relief-planning)

5.1 Key Responsibilities
87-[1](#number-range-level2number-range-level3number-range-level4-key-responsibilities)

5.1.1 Relief Timing
88-[1](#number-range-level3number-range-level4-relief-timing)

5.1.2 Relief Planning Communication
89-[1](#number-range-level3number-range-level4-relief-planning-communication)

5.1.3 Initial Planning Document (IPD) Preparation and Distribution
90-[2](#number-range-level3number-range-level4-initial-planning-document-ipd-preparation-and-distribution)

5.1.4 Relief Planning Meetings
91-[2](#number-range-level3number-range-level4-relief-planning-meetings)

5.1.5 Relief Planning Report
92-[2](#number-range-level3number-range-level4-relief-planning-report)

5.1.6 Relief Planning Consensus Building
93-[2](#number-range-level3number-range-level4-relief-planning-consensus-building)

5.1.7 Neutral Facilitator Role
94-[2](#number-range-level3number-range-level4-neutral-facilitator-role)

5.1.8 Proactive Role in Relief Planning
95-[2](#number-range-level3number-range-level4-proactive-role-in-relief-planning)

5.1.9 Status Reporting on Relief Plans
96-[2](#number-range-level3number-range-level4-status-reporting-on-relief-plans)

5.1.10 Possible Testimony
97-[3](#number-range-level3number-range-level4-possible-testimony)

5.1.11 New NPA Code Assignment
98-[3](#number-range-level3number-range-level4-new-npa-code-assignment)

5.1.12 Implementation Scheduling
99-[3](#number-range-level3number-range-level4-implementation-scheduling)

5.1.13 Industry Scheduling
100-[3](#number-range-level3number-range-level4-industry-scheduling)

5.1.14 Press Release
101-[3](#number-range-level3number-range-level4-press-release)

5.1.15 Implementation Assistance
102-[3](#number-range-level3number-range-level4-implementation-assistance)

5.1.16 Compliance 103-[4](#compliance)

5.2 User Notification
104-[4](#number-range-level2number-range-level3number-range-level4-user-notification)

Utilization and Forecasting 105-[1](#utilization-and-forecasting)

6.1 Responsibilities
106-[1](#number-range-level2number-range-level3number-range-level4-responsibilities)

6.1.1 Point of Contact
107-[1](#number-range-level3number-range-level4-point-of-contact)

6.1.2 Contact List Maintenance
108-[1](#number-range-level3number-range-level4-contact-list-maintenance)

6.1.3 Data Requests
109-[1](#number-range-level3number-range-level4-data-requests)

6.1.4 Data Requests in Pooled Areas
110-[2](#number-range-level3number-range-level4-data-requests-in-pooled-areas)

6.1.5 Data Analysis
111-[2](#number-range-level3number-range-level4-data-analysis)

6.1.6 Data Reporting
112-[2](#number-range-level3number-range-level4-data-reporting)

6.1.7 User Support
113-[2](#number-range-level3number-range-level4-user-support)

6.1.8 Data Aggregation
114-[2](#number-range-level3number-range-level4-data-aggregation)

6.1.9 Request to Review Data
115-[3](#number-range-level3number-range-level4-request-to-review-data)

6.1.10 Penalties for Non-Submission
116-[3](#number-range-level3number-range-level4-penalties-for-non-submission)

6.1.11 Report Anomalies
117-[3](#number-range-level3number-range-level4-report-anomalies)

6.2 Development of Tests for Anomalies and Inconsistencies
118-[4](#number-range-level2number-range-level3number-range-level4-development-of-tests-for-anomalies-and-inconsistencies)

6.3 NANPA Analysis of Data
119-[4](#number-range-level2number-range-level3number-range-level4-nanpa-analysis-of-data)

6.3.1 Methodology for Projecting NPA Exhaust
120-[4](#number-range-level3number-range-level4-methodology-for-projecting-npa-exhaust)

6.3.2 Minimum Analysis Requirements
121-[5](#number-range-level3number-range-level4-minimum-analysis-requirements)

6.3.3 Anomalies and Trends
122-[6](#number-range-level3number-range-level4-anomalies-and-trends)

6.4 Number Resource Utilization Form (NRUF) Submissions
123-[6](#number-range-level2number-range-level3number-range-level4-number-resource-utilization-form-nruf-submissions)

Automated System Support 124-[1](#automated-system-support)

7.1 System Characteristics
125-[1](#number-range-level2number-range-level3number-range-level4-system-characteristics)

7.1.1 System Availability
126-[1](#number-range-level3number-range-level4-system-availability)

7.1.2 System Query Capability
127-[1](#number-range-level3number-range-level4-system-query-capability)

7.1.3 System Scalability
128-[2](#number-range-level3number-range-level4-system-scalability)

7.2 System Capabilities
129-[2](#number-range-level2number-range-level3number-range-level4-system-capabilities)

7.3 System Location
130-[3](#number-range-level2number-range-level3number-range-level4-system-location)

7.3.1 Facility Characteristics
131-[3](#number-range-level3number-range-level4-facility-characteristics)

7.4 System Data
132-[3](#number-range-level2number-range-level3number-range-level4-system-data)

7.4.1 Data Integrity
133-[3](#number-range-level3number-range-level4-data-integrity)

7.4.2 Confidential Treatment
134-[3](#number-range-level3number-range-level4-confidential-treatment)

7.4.3 Automated Submittal
135-[4](#number-range-level3number-range-level4-automated-submittal)

7.4.4 Automated Data Output Capabilities
136-[4](#number-range-level3number-range-level4-automated-data-output-capabilities)

7.4.5 Mechanized Interface with the Pooling Administrator
137-[4](#mechanized-interface-with-the-pooling-administrator)

7.4.6 Alternative Data Capabilities
138-[4](#number-range-level3number-range-level4-alternative-data-capabilities)

7.5 System Maintenance
139-[4](#number-range-level2number-range-level3number-range-level4-system-maintenance)

7.6 System Security
140-[4](#number-range-level2number-range-level3number-range-level4-system-security)

7.7 System User Profile Application
141-[5](#number-range-level2number-range-level3number-range-level4-system-user-profile-application)

7.7.1 User Logon System
142-[5](#number-range-level3number-range-level4-user-logon-system)

7.7.2 Logon System Access
143-[5](#number-range-level3number-range-level4-logon-system-access)

7.7.3 Logon System Approval
144-[5](#number-range-level3number-range-level4-logon-system-approval)

7.7.4 Logon System Security Level
145-[5](#number-range-level3number-range-level4-logon-system-security-level)

7.7.5 Logon System Password
146-[5](#number-range-level3number-range-level4-logon-system-password)

7.7.6 Logon System Problems
147-[5](#number-range-level3number-range-level4-logon-system-problems)

7.7.7 User Access Permission Classes
148-[6](#number-range-level3number-range-level4-user-access-permission-classes)

7.7.8 Password Changes
149-[6](#number-range-level3number-range-level4-password-changes)

7.7.9 Unauthorized Client User System Access
150-[6](#number-range-level3number-range-level4-unauthorized-client-user-system-access)

7.8 System Inspection
151-[6](#number-range-level2number-range-level3number-range-level4-system-inspection)

7.9.1 Report Distribution
152-[7](#number-range-level3number-range-level4-report-distribution)

7.10 Help Desk
153-[7](#number-range-level2number-range-level3number-range-level4-help-desk)

7.10.1 Contact 154-[8](#number-range-level3number-range-level4-contact)

7.10.2 Help Desk Referrals
155-[8](#number-range-level3number-range-level4-help-desk-referrals)

7.10.3 Help Desk Actions
156-[8](#number-range-level3number-range-level4-help-desk-actions)

7.11 System Generated Notifications
157-[8](#number-range-level2number-range-level3number-range-level4-system-generated-notifications)

7.11.1 Customized Notifications
158-[9](#number-range-level3number-range-level4-customized-notifications)

7.12 System Testing
159-[9](#number-range-level2number-range-level3number-range-level4-system-testing)

7.12.1 System Test Results
160-[9](#number-range-level3number-range-level4-system-test-results)

7.13 System Disaster Recovery
161-[9](#number-range-level2number-range-level3number-range-level4-system-disaster-recovery)

7.14 System Backup
162-[10](#number-range-level2number-range-level3number-range-level4-system-backup)

7.15 System and Equipment Inventory
163-[10](#number-range-level2number-range-level3number-range-level4-system-and-equipment-inventory)

7.16 System Documentation Plan
164-[10](#number-range-level2number-range-level3number-range-level4-system-documentation-plan)

7.17 NANP Administration System Transfer to Successor
165-[10](#number-range-level2number-range-level3number-range-level4-nanp-administration-system-transfer-to-successor)

7.17.1 Transfer Efficacy
166-[11](#number-range-level3number-range-level4-transfer-efficacy)

7.17.2 System Software Source Code Escrow
167-[11](#number-range-level3number-range-level4-system-software-source-code-escrow)

7.17.3 System and Equipment Transfer
168-[11](#number-range-level3number-range-level4-system-and-equipment-transfer)

7.18 Tools
169-[11](#number-range-level2number-range-level3number-range-level4-tools)

7.18.1 Exhaust Forecasting
170-[11](#number-range-level3number-range-level4-exhaust-forecasting)

7.18.2 CO Codes
171-[12](#number-range-level3number-range-level4-co-codes)

7.18.3 NPA Exhaust Relief Planning
172-[13](#number-range-level3number-range-level4-npa-exhaust-relief-planning)

7.18.4 Federal and State Directives/Orders
173-[13](#number-range-level3number-range-level4-federal-and-state-directivesorders)

7.18.5 Federal and State Code Conservation Data
174-[14](#number-range-level3number-range-level4-federal-and-state-code-conservation-data)

7.18.6 CIC Access and Usage Report Processing
175-[14](#number-range-level3number-range-level4-cic-access-and-usage-report-processing)

7.18.7 Contact Information
176-[14](#number-range-level3number-range-level4-contact-information)

7.19 Web Site
177-[15](#number-range-level2number-range-level3number-range-level4-web-site)

7.19.1 Web Site Content
178-[15](#number-range-level3number-range-level4-web-site-content)

7.19.2 Content Posting
179-[17](#number-range-level3number-range-level4-content-posting)

7.19.3 Web Site Design
180-[17](#number-range-level3number-range-level4-web-site-design)

7.19.4 Availability and Access
181-[17](#number-range-level3number-range-level4-availability-and-access)

7.19.5 System Responsiveness
182-[17](#number-range-level3number-range-level4-system-responsiveness)

7.19.6 Out-of-Service
183-[18](#number-range-level3number-range-level4-out-of-service)

7.19.7 Out-of-Service Notification
184-[18](#number-range-level3number-range-level4-out-of-service-notification)

7.19.8 Web Site Privacy
185-[18](#number-range-level3number-range-level4-web-site-privacy)

7.19.9 Maintenance of NANC Chair Web Site
186-[19](#number-range-level3number-range-level4-maintenance-of-nanc-chair-web-site)

Reporting 187-[1](#reporting)

8.1 Annual Report
188-[1](#number-range-level2number-range-level3number-range-level4-annual-report)

8.2 NRUF Report
189-[2](#number-range-level2number-range-level3number-range-level4-nruf-report)

8.2.1 Data Anomalies
190-[3](#number-range-level3number-range-level4-data-anomalies)

8.2.2 Reports to Regulatory Authorities
191-[3](#number-range-level3number-range-level4-reports-to-regulatory-authorities)

8.3 NPA Relief Activity Status Report
192-[4](#number-range-level2number-range-level3number-range-level4-npa-relief-activity-status-report)

8.4 CO Code Activity Status Report
193-[5](#number-range-level2number-range-level3number-range-level4-co-code-activity-status-report)

8.5 Other NANP Activity and Status Reports
194-[6](#number-range-level2number-range-level3number-range-level4-other-nanp-activity-and-status-reports)

8.6 Requests for Additional Reports
195-[6](#number-range-level2number-range-level3number-range-level4-requests-for-additional-reports)

8.7 Reference Documentation
196-[6](#number-range-level2number-range-level3number-range-level4-reference-documentation)

8.8 Standardized Reports for State Commissions
197-[6](#number-range-level2number-range-level3number-range-level4-standardized-reports-for-state-commissions)

8.9 Summary of NANPA Technical Reports
198-[8](#number-range-level2number-range-level3number-range-level4-summary-of-nanpa-technical-reports)

8.10 Summary of NANPA Performance Reports
199-[10](#number-range-level2number-range-level3number-range-level4-summary-of-nanpa-performance-reports)

Audits and Performance Monitoring
200-[1](#audits-and-performance-monitoring)

9.1 Audit by FCC
201-[1](#number-range-level2number-range-level3number-range-level4-audit-by-fcc)

9.11 Staff Support 202-[1](#staff-support)

9.12 Office Facilities 203-[1](#office-facilities)

9.13 Audit Results 204-[1](#audit-results)

9.14 Compliance 205-[2](#compliance-1)

9.2 Monitoring
206-[2](#number-range-level2number-range-level3number-range-level4-monitoring)

9.2.1 NANPA Client Feedback Survey
207-[2](#nanpa-client-feedback-survey)

9.2.2 NANPA Annual Operational Review
208-[2](#nanpa-annual-operational-review-number-range-level2number-range-level3number-range-level4)

9.2.3 Performance Problems and Corrective Action
209-[3](#number-range-level2number-range-level3number-range-level4-performance-problems-and-corrective-action)

9.3 Performance Monitoring
210-[3](#number-range-level2number-range-level3number-range-level4-performance-monitoring)

9.4 NRUF-Related Measurements 211-[3](#nruf-related-measurements)

9.5 Self Assessment and Reporting
212-[4](#self-assessment-and-reporting)

Contract Data Requirements List (CDRL)
213-[1](#contract-data-requirements-list-cdrl)

10.1 Implementation Plan
214-[1](#number-range-level2number-range-level3number-range-level4-implementation-plan-1)

10.2 Security Plan
215-[1](#number-range-level2number-range-level3number-range-level4-security-plan)

10.3 Disaster/Continuity of Operations Plan
216-[1](#number-range-level2number-range-level3number-range-level4-disastercontinuity-of-operations-plan)

10.4 NANP Administration System Transfer List
217-[1](#number-range-level2number-range-level3number-range-level4-nanp-administration-system-transfer-list)

10.5 System Test Plan
218-[1](#number-range-level2number-range-level3number-range-level4-system-test-plan)

10.6 Change Management Plan
219-[1](#number-range-level2number-range-level3number-range-level4-change-management-plan)

10.7 Contract Change Management Plan
220-[1](#number-range-level2number-range-level3number-range-level4-contract-change-management-plan)

10.8 Training Plan
221-[2](#number-range-level2number-range-level3number-range-level4-training-plan)

10.9 System Maintenance Plan
222-[2](#number-range-level2number-range-level3number-range-level4-system-maintenance-plan)

10.10 System Documentation Plan
223-[2](#number-range-level2number-range-level3number-range-level4-system-documentation-plan-1)

10.11 Performance Improvement Plan
224-[2](#number-range-level2number-range-level3number-range-level4-performance-improvement-plan)

10.12 Transition Plan
225-[2](#number-range-level2number-range-level3number-range-level4-transition-plan)

10.13 System Source Code
226-[2](#number-range-level2number-range-level3number-range-level4-system-source-code)

Enterprise Services 227-[1](#enterprise-services)

11.1 Operating Principles 228-[1](#operating-principles)

11.2 Required Enterprise Service 229-[1](#required-enterprise-service)

11.3 Audit of Enterprise Services 230-[2](#audit-of-enterprise-services)

List of References

Appendix A. Terms

Appendix B. Interface Contact Information

Appendix C. Index to the Binder of Decisional Principles

# Section 231Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-231number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Introduction {#introduction .Section-Header}

## 231.1Number range Level2Number range Level3Number range Level4 Purpose

This document defines the North American Numbering Plan (NANP)
Administrator's technical, operational, and system requirements and
describes the full functionality required of the designated North
American Numbering Plan Administrator (NANPA). It also serves as a
reference document to other resources, such as industry guidelines,
United States Federal Communications Commission (FCC or Commission)
orders, technical standards, and technical requirements that support the
NANP.

The contractor shall, at the FCC's discretion, perform the duties of the
NANPA for up to a five-year term from the date of award.

## 231.2Number range Level2Number range Level3Number range Level4 Scope

This document describes the technical responsibilities of the vendor
selected by the FCC to serve as the NANPA. The primary scope of this
document is to define the NANPA's performance within the United States.

The NANPA's role in the United States includes the following functional
areas: overall NANP Administration, Central Office (CO) Code
Administration, Numbering Plan Area (NPA) relief planning, collection
and analysis of utilization and forecast data, report generation, and
all other related NANP Administration functions. Each of the functions
is described further in the document.

## 231.3Number range Level2Number range Level3Number range Level4 Background

The NANP is the basic numbering scheme for the Public Switched Telephone
Networks (PSTNs) in the following 19 countries (formerly known as World
Zone 1): Anguilla, Antigua & Barbuda, Bahamas, Barbados, Bermuda,
British Virgin Islands, Canada, Cayman Islands, Dominica, Dominican
Republic, Grenada, Jamaica, Montserrat, St. Kitts & Nevis, St. Lucia,
St. Vincent & the Grenadines, Trinidad & Tobago, Turks & Caicos Islands,
and the United States (including Puerto Rico, the U.S. Virgin Islands,
Guam, the Commonwealth of the Northern Mariana Islands and American
Samoa).

The format of the NANP is consistent with International
Telecommunication Union (ITU) Recommendation E.164 "The International
Public Telecommunication Numbering Plan."

The administration of the NANP was originally the responsibility of AT&T
until divestiture. At that time, Bellcore was instructed to take over
this administrative task. In 1997, this function was awarded to the
company that is now NeuStar through a competitive bid process conducted
at the direction of the FCC.

The term NPA Code refers to an area code that is the first three digits
of a telephone number. Each digit in a telephone number is identified by
an alphabetical character in the order ABC-DEF-GHIJ, consisting of a
3‑digit NPA (ABC), a 3‑digit CO Code (DEF), and a 4‑digit Line Number
(GHIJ). This is in the format NXX-NXX-XXXX, where: N = digits 2 to 9 and
X = digits 0 to 9 (*e.g*., 613 is the NPA code in the NANP number
613‑781‑0610). There were 335 geographic NPA codes in service as of
January 1, 2008. The number of new area codes assigned in the United
States since 1995 is shown in the table below:

  ----------------------------------- -----------------------------------
  **Year**                            **Number Assigned**

  1995                                14

  1996                                11

  1997                                32

  1998                                22

  1999                                43

  2000                                23

  2001                                21

  2002                                3

  2003                                1

  2004                                3

  2005                                2

  2006                                2

  2007                                3
  ----------------------------------- -----------------------------------

There shall be a transition from the current administrator to the new
administrator should the NANPA responsibility be awarded to a new party.

## 231.4Number range Level2Number range Level3Number range Level4 Attributes

The NANPA's role is to serve as the neutral numbering administrator. The
NANPA must comply with the statutory requirements for neutrality and
meet the Commission\'s neutrality requirements, set forth in Commission
rule 52.12, 47 C.F.R. § 52.12.

Rule 52.12 states:

(a)(1) Neutrality. The NANPA \[ \] shall be \[a\] non‑governmental
entities that \[is\] impartial and not aligned with any particular
telecommunication industry segment. Accordingly, while conducting \[ \]
operations under this section, the NANPA shall ensure that \[it\]
compl\[ies\] with the following neutrality criteria:

\(i\) The NANPA \[ \] may not be an affiliate of any telecommunications
service provider(s) as defined in the Telecommunications Act of 1996.
"Affiliate" is a person who controls, is controlled by, or is under the
direct or indirect common control with another person. A person shall be
deemed to control another if such person possesses, directly or
indirectly‑‑

\(A\) An equity interest by stock, partnership (general or limited)
interest, joint venture participation, or member interest in the other
person ten (10%) percent or more of the total outstanding equity
interests in the other person, or

\(B\) The power to vote ten (10%) percent or more of the securities (by
stock, partnership (general or limited) interest, joint venture
participation, or member interest) having ordinary voting power for the
election of directors, general partner, or management of such other
person, or

\(C\) The power to direct or cause the direction of the management and
policies of such other person, whether through the ownership of or right
to vote voting rights attributable to the stock, partnership (general or
limited) interest, joint venture participation, or member interest) of
such other person, by contract (including but not limited to stockholder
agreement, partnership (general or limited) agreement, joint venture
agreement, or operating agreement), or otherwise;

\(ii\) The NANPA \[ \] and any affiliate thereof, may not issue a
majority of its debt to, nor may it derive a majority of its revenues
from, any telecommunications service provider. "Majority" shall mean
greater than 50 percent, and "debt" shall mean stocks, bonds,
securities, notes, loans or any other instrument of indebtedness; and

\(iii\) Notwithstanding the neutrality criteria set forth in paragraphs
(a)(1) (i) and (ii) of this section, the NANPA \[ \] may be determined
to be or not to be subject to undue influence by parties with a vested
interest in the outcome of numbering administration and activities. \[
\]

\(2\) Any subcontractor that performs‑‑

\(i\) NANP Administration and central office code administration \[ \]
must also meet the neutrality criteria described in paragraph (a)(1).

Potential bidders must demonstrate that they meet the Commission's
neutrality requirements through submission of a certificate signed by a
Chief Executive Officer or President that explicitly certifies the
bidder meets each requirement. The successful bidder will be required to
re‑certify to its compliance at the time of award. Potential bidders, as
well as the successful bidder, should be prepared to provide any other
documentation verifying compliance as may be requested by the
Commission.

The entity selected to be the NANPA must adhere to all Commission
neutrality requirements, orders, and policies throughout the term of the
contract. In this regard, to avoid potential disruption of national
numbering administration, the successful bidder will be required to
apprise the Commission of any proposed changes that may affect its
neutrality sufficiently in advance to permit review of the proposed
changes and Commission determination as to whether any cure would be
necessary to ensure NANPA neutrality. Such changes might be, but are not
limited to, changes to organizational or ownership structure, investors,
Board of Directors, etc.

The NANPA is the designated independent, neutral entity responsible for
assigning and administering NANP resources in an efficient, effective,
fair, unbiased, and non-discriminatory manner consistent with regulatory
directives and industry guidelines, and is required to comply with state
regulatory decisions, rules and orders, as applicable, as long as they
are not in conflict with FCC decisions, orders, and rules.

The NANPA shall also ensure that numbering administration in the United
States is effective, while using the expertise and innovation of
industry to promote number optimization. It also shall support efforts
to accommodate current and future numbering needs, and to advise the
industry and regulators relative to numbering issues (*e.g.*, potential
resource exhaust).

## 231.5Number range Level2Number range Level3Number range Level4 Environment

### 231.5.1Number range Level3Number range Level4 Regulatory

The FCC has authority over numbering within the United States. The other
NANP member nations exercise similar regulatory jurisdiction.

The FCC has delegated specific authority to state regulatory agencies in
the United States. All states have been delegated authority over NPA
Relief. In addition, some states have been given authority to trial
certain number conservation measures. They have also been granted
authority to obtain data, reclaim resources, and establish and enforce
number allocation standards.

In the future, regulatory authorities may issue rules, requirements or
policy directives, which may increase, decrease or otherwise affect the
functions to be performed by the NANPA.

### 231.5.2Number range Level3Number range Level4 Federal Advisory Committee

The North American Numbering Council (NANC) is a Federal Advisory
Committee established pursuant to the United States Federal Advisory
Committee Act, 5 U.S.C., App. 2 (1988) (FACA). The NANC was established
to advise the FCC on issues related to NANP Administration, and to
advise the Commission on local number portability (LNP) administration
issues. The NANC develops policy recommendations on numbering issues,
initially resolves disputes, and provides guidance to the numbering
administrators.

The NANC's charter under the FACA provides that, in carrying out its
responsibilities, the NANC shall ensure that NANP Administration
supports identified policy objectives. The NANC shall ensure that the
NANPA:

-   Facilitates entry into the communications marketplace by making
    numbering resources available on an efficient, timely basis to
    communications service providers.

-   Does not unduly favor or disfavor any particular industry segment or
    group of consumers.

-   Does not unduly favor one technology over another.

-   Gives consumers easy access to the public switched telephone
    network.

-   Ensures that the interests of all NANP member countries are
    addressed fairly and efficiently, fostering continued integration of
    the NANP across NANP member countries.

### 231.5.3Number range Level3Number range Level4 Industry Activities

The industry develops number administration guidelines for the United
States based on industry consensus and regulatory direction. The
Industry Numbering Committee (INC), operating under the auspices of the
Alliance for Telecommunications Industry Solutions (ATIS), is the
industry forum established to develop such guidelines.

The mission of the INC is to provide a forum to address and resolve
industry-wide technical issues associated with the planning,
administration, allocation, assignment and use of numbering resources
and related dialing considerations for public telecommunications within
the NANP area.

INC guidelines incorporate federal regulatory requirements with
technical and operational principals. The guidelines also recognize the
existence of specific regulations in states where FCC-delegated
authority has been granted.

Industry guidelines and regulatory directives are subject to change
throughout the NANPA's Term of Administration.

# Section 232Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-232number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# General Requirements {#general-requirements .Section-Header}

This section describes the functions to be performed by the NANPA.

The scope of this document reflects the NANPA's functions, along with
FCC rules, FCC orders, state regulatory directives made under
FCC-delegated authority, and industry guidelines.

This document describes the functional requirements, administrative
tasks, and components of the responsibilities and duties of the NANPA.
The bidders shall also refer to related regulatory orders issued by the
FCC and states with delegated authority, industry guidelines, technical
standards, and NANC-related documentation. A List of References follows
Section 11 in this document.

## 232.1Number range Level2Number range Level3Number range Level4 High-Level Requirements

The four high level requirements of the NANPA are indicated below.

### 232.1.1Number range Level3Number range Level4 Assigning and Administering NANP Resources

In accordance with 47 C.F.R. § 52.13(b), the NANPA shall assign and
administer NANP resources in an efficient, effective, fair, unbiased,
and non-discriminatory manner consistent with regulatory directives and
industry guidelines.

### 232.1.2Number range Level3Number range Level4 Accommodating Current and Future Numbering Needs

The NANPA shall participate in industry efforts to accommodate current
and future numbering needs at the NPA level and the NANP level. The
NANPA shall advise the regulators and industry relative to numbering
issues, potential resource exhaust, and all routing and rating issues
that may affect service to users.

In addition to its many day-to-day numbering resource assignment and
administrative activities, the NANPA shall provide sufficient focus on
long-term planning to ensure the continued viability of the NANP. The
NANPA shall update its processes, procedures, systems, and forms to
reflect regulatory orders, rules, and directives.

The NANPA shall implement a planned approach utilizing effective
forecasting and management tools in order to make everyone aware of the
availability of numbering resources to meet current and future needs.

Critical components of NANP Administration include NPA relief planning
and providing systems and tools for managing number administration.

### 232.1.3Number range Level3Number range Level4 Administrative Resources for Legal, Financial, and Technical Responsibilities

The NANPA shall maintain necessary administrative resources to handle
the legal, financial, and technical responsibilities required to manage
all numbering resources.

### 232.1.4Number range Level3Number range Level4 Supervision for All Services and Responsibility for Achieving Performance Objectives

The NANPA shall provide management supervision for all of the services
it provides, including responsibility for achieving performance
objectives. The establishment of these objectives is a collaborative
effort between the NANPA, the FCC, state commissions, the NANC, and the
INC.

## 232.2Number range Level2Number range Level3Number range Level4 Relationships

### 232.2.1Number range Level3Number range Level4 United States

The NANPA shall establish and maintain relationships within the United
States with entities such as the FCC, other federal agencies, and state
regulatory authorities, as appropriate.

The NANPA shall cooperate with and actively participate in policy and
technical numbering bodies and industry forums, such as the NANC and its
subtending groups, and the INC.

### 232.2.2Number range Level3Number range Level4 International

The NANPA shall develop and maintain communications with all other NANP
member countries to ensure that their numbering needs are met.

The NANPA shall attend U.S. Department of State Study Group A meetings.

In addition, the NANPA shall maintain a working knowledge of ITU Study
Group 2 activities for the benefit of the U.S. telecommunications
industry.

Attendance at international meetings is not covered by the scope of this
contract.

## 232.3Number range Level2Number range Level3Number range Level4 Administration and Management

The NANPA shall manage the NANP in accordance with the most current
regulatory directives and policies and published industry guidelines.

Occasions may arise where decisions and interpretations are required on
issues that have not yet been addressed. The NANPA shall have the
knowledge and capability to recognize these instances and refer them to
the appropriate body for resolution.

The NANPA shall perform as the steward of the numbering resources. In
this capacity, the NANPA shall monitor the status of resources in all
areas of the NANP and take appropriate action to ensure the timely
availability of numbering resources.

### 232.3.1Number range Level3Number range Level4 Requests for Numbering Resources

Applications for numbering resources shall be submitted to the NANPA by
service providers via the Internet, facsimile, or the U.S. Mail. The
NANPA shall use a standard electronic format for application
transmissions. All applications received by the NANPA shall, in turn,
generate a confirmation back to the submitting service provider.

The NANPA shall review requests for numbering resources (*e.g.*, NPAs,
central office codes) for accuracy and appropriateness per FCC
requirements and industry guidelines.

### 232.3.2Number range Level3Number range Level4 Service Provider and Regulator Support

The NANPA shall serve as the information resource for regulatory bodies
and the industry concerning numbering resource issues related to NANP
Administration (*e.g.*, ITU E.164 Recommendation, NANP, NANP
Administration, regulatory issues affecting numbering, number resource
assignment guidelines, CO Code administration, and relief planning and
relevant international numbering issues).

The NANPA shall respond to inquiries about the numbering plan. The NANPA
shall provide, upon request, information on how to obtain current
documents and forms related to NANP Administration (including
application for automated access to its systems and all other materials
needed to properly request the assignment or disconnect of numbering
resources, or change of numbering data) by referring requesters to
specific NANPA web pages where they can download electronic copies or
other sources as appropriate (*e.g.*, to the FCC, state commissions, the
INC). The NANPA shall provide copies of documents it generates by
facsimile or U.S. Mail if the document is not available via the
Internet. A list of documents related to NANP Administration is provided
in the List of References following Section 11 in this document.

### 232.3.3Number range Level3Number range Level4 Numbering Resource Optimization

The NANPA shall provide assistance to users of numbering resources and
suggest alternatives, when possible, that shall optimize numbering
resource utilization.

The NANPA shall coordinate its numbering resource activities with the
Canadian Number Administrator and other NANP member countries'
administrators to ensure efficient and effective management of NANP
numbering resources.

The NANPA shall be knowledgeable regarding numbering resource
optimization methods (*e.g.*, rate center consolidation, individual
telephone number pooling, thousands- block number pooling) and the
potential impact upon the NANP itself. The NANPA shall remain completely
neutral and shall not take a position that favors one numbering resource
optimization method over another.

The NANPA shall not take independent action with respect to adoption of
optimization methods that are not within existing guidelines or
regulatory directives. However, the NANPA shall recognize optimization
opportunities and bring this information to the attention of the
appropriate body for consideration. The NANPA shall remain cognizant of
its obligation to remain neutral.

## 232.4Number range Level2Number range Level3Number range Level4 Cost Allocation

The Billing and Collection Agent shall determine the final allocation
methodology for sharing costs between NANP countries in accordance with
the Billing and Collection Agent Requirements Document, or appropriate
regulatory documentation. Should cost allocation disputes arise, the
Billing and Collection Agent shall request FCC guidance. In no
circumstances shall the NANPA decide on its own the cost methodology or
allocation between and among NANP member countries.

## 232.5Number range Level2Number range Level3Number range Level4 Staffing

The NANPA shall maintain the necessary staffing levels to support
industry and regulatory work relevant to the management of all NANP
numbering resources.

The NANPA shall maintain necessary administrative resources to handle
the legal, financial, and technical responsibilities connected with the
management of all numbering resources.

The NANPA shall maintain the necessary equipment (*e.g.*, inventory
systems, facilities, and proper billing arrangements associated with
day-to-day management of numbering resources) to support this staff.

All employees and subcontractors of the NANPA who have access to a
service provider's confidential information shall execute a
non-disclosure agreement that remains in effect following the
termination of employment.

Subcontractors may be used to perform work under this, or subsequent,
Terms of Administration.

## 232.6Number range Level2Number range Level3Number range Level4 Telecommunications Requirements

The NANPA shall have voice and data capabilities in order to communicate
with all clients and the public concerning NANP Administration.

Each NANPA staff member who has responsibilities for interfacing with
clients shall be reachable directly by those clients.

The telephone system shall provide the capability to allow a caller to
easily leave a message. This may be accomplished by an electronic
messaging system that allows the caller to leave a message for the
person called.

The NANPA shall maintain read/write access to routing and rating
databases.[^1] This can be accomplished through a GUI interface. The
NANPA shall also have access to the information contained in the Local
Exchange Routing Guide (LERG) or an equivalent.

The NANPA shall maintain access to Number Portability Administration
Center (NPAC) data the NANPA needs to perform its responsibilities. The
data shall be obtained from the NPAC administrator per the details
defined by the North American Portability Management, Limited Liability
Corporation (LLC) that oversees the vendor of the local number
portability systems and administration or as otherwise provided by FCC
requirements.

## 232.7Number range Level2Number range Level3Number range Level4 Daily Operations

The NANPA shall be available a minimum of five business days per week
(Monday through Friday), eight hours per day during the business hours
of its clients. However, since the NANP service area covers several time
zones, the NANPA shall provide a mechanism (*e.g.*, voicemail, e-mail,
facsimile) to be accessible on a 24-hour basis in order to meet the
needs of all of its clients.

The NANPA shall maintain a log of all client contacts for review by the
Auditor and other parties as designated by the FCC.

### 232.7.1Number range Level3Number range Level4 Inquiry Response

The NANPA shall respond within the next business day (to be defined in
the time zone where the inquiry was originated) to general inquires or
questions.

The NANPA shall monitor and report on its customer response rates. This
report shall be furnished upon request and used to review the NANPA's
customer service activities per the annual performance review process.

### 232.7.2Number range Level3Number range Level4 Emergency Notifications

The NANPA shall be called upon to provide industry notification outside
of the accepted timeframes defined in industry guidelines. These
notifications shall be issued as appropriate and necessary depending on
the circumstances.

### 232.7.3Number range Level3Number range Level4 Holidays

The NANPA shall observe U.S. holidays. The following is a list of
holidays that the NANPA shall observe:

-   New Year's Day

-   Memorial Day

-   Independence Day

-   Labor Day

-   Thanksgiving Day

-   Day after Thanksgiving\*

-   Christmas Day

    \* Not open for business but the Help Desk shall be open and this
    shall be considered a business day for day counts on processing.

NANPA shall be open for business on all other business days.

On an annual basis, the NANPA shall post a list of the holidays observed
and the calendar dates of those holidays on the NANPA web site.

## 232.8Number range Level2Number range Level3Number range Level4 Physical Location

The physical location of the NANPA facility(s) is at the discretion of
the contractor.

The NANPA shall notify clients and the public, by appropriate means,
prior to any facility relocation or telephone number change.

## 232.9Number range Level2Number range Level3Number range Level4 Travel

NANPA staff shall travel, when necessary, to meet the needs of the NANPA
(*e.g.*, to NANC meetings, INC meetings, NPA jeopardy situations, NPA
relief planning meetings, or as otherwise necessary to comply with FCC
requirements).

## 232.10Number range Level2Number range Level3Number range Level4 Modification of Guidelines

The NANPA shall participate in the development and modification of
guidelines and procedures, which may affect the performance of the NANPA
functions. These changes may come from regulatory directives and/or
modifications to guidelines. In addition, new guidelines may be
developed as appropriate to comply with regulatory directives. The NANPA
shall adopt and implement any changes that are consistent with
regulatory directives after they are officially adopted, recognizing
that some may constitute a change in the scope of work.

The NANPA shall:

-   Provide, in real time, technical guidance to ensure processes and
    procedures are effective in meeting the goals of the change.

-   Assess and share in real time the cost implications and
    administrative impact upon the NANPA duties and responsibilities.

-   Provide contributions, describing how the change benefits the NANP
    and how the change shall affect the NANPA's duties, obligations or
    accountability.

Within seven days of a change, the NANPA shall provide its
interpretation of the change, its impact upon service, the date the new
change is proposed to become effective, what steps in current procedures
need to change and when any new forms or procedures will be required.
The NANPA shall provide this information to the FCC and the NANC. When
the INC places any changes to its guidelines in initial closure, the
NANPA shall submit an assessment regarding the impact of scope of work,
time and costs to the INC, the NANC and the FCC within 30 days.

The NANPA shall post changes in procedures on its web site prior to the
change taking effect.

The NANC shall be consulted at the FCC's discretion regarding the
suggested implementation date to determine the likely impact on service
provider processes and systems (i.e., whether it would be unduly
burdensome or would unfairly disadvantage any service provider or group
of service providers per the NANPA's obligations and NANP administrative
principles).

Specifically, the NANPA shall:

-   Notify all interested parties when guidelines have changed.

-   Interpret guideline changes and impact upon processes.

-   Identify implementation date or effective date.

-   Provide notification of new forms or tools that may be required.

-   Identify a Single Point of Contact (SPOC) within the NANPA to answer
    questions.

-   Accept, process, and verify the accuracy of applications for CO
    Codes in accordance with regulatory requirements and industry
    guidelines.

-   Contact code applicant as necessary to gain clarification or
    additional information in order to process the application when
    first submitted.

-   Review entire application, identifying all errors and omissions when
    first submitted.

-   Provide information or location of tools and contacts to assist
    applicants in properly completing applications for connects, changes
    and disconnects.

## 232.11Number range Level2Number range Level3Number range Level4 Audits

The NANPA and service providers shall be subject to audits to verify
their compliance with guidelines and regulations relating to all
applicable areas of number administration.

### 232.11.1Number range Level3Number range Level4 For Cause Audits of Service Providers

In the performance of its numbering administration duties and in meeting
its responsibilities, the NANPA may encounter situations that may alert
it to a service provider's possible noncompliance with the industry
guidelines. This noncompliance warrants the need for a "For Cause"
audit.

In these situations, the NANPA shall document its observations and
forward relevant information to the FCC, service provider, and
appropriate state commission.

The NANPA shall maintain the confidentiality of all requested
information throughout the auditing process.

### 232.11.2Number range Level3Number range Level4 Other Audits of Service Providers

The NANPA shall be required to provide specific data to an auditor in
order to facilitate the audit of a service provider.

## 232.12Number range Level2Number range Level3Number range Level4 Dispute Resolution

The NANPA may be involved with dispute resolution. These disputes could
arise from the performance of NANPA activities, from industry forum
activities, or from conflicting government or regulatory policy
directives. The extent of involvement of the NANPA in the resolution of
disputes shall depend on the nature and origin of the dispute. A Dispute
Resolution process, established by the NANC, shall be followed for
determination of the controversy.

The NANPA shall assign numbering resources based on regulatory
directives and industry guidelines. A disagreement may arise when the
NANPA is assigning or denying the assignment of a resource, and the
NANPA shall be required, based on the relevant regulatory directives,
assignment guidelines, and the NANC Dispute Resolution process, to
address and, if possible, resolve the disagreement. In addition,
disputes may arise between regulatory authorities of NANP member
countries and the NANPA may be required to participate in the resolution
of the issue between the countries involved.

The NANPA shall interpret and apply relevant guidelines, directives, and
Orders, including those listed in the *Index to the Binder of Decisional
Principals* (see Appendix C), to resolve a disagreement when assigning
or denying the assignment of a numbering resource.

Disputes may also arise within industry numbering activities. When this
occurs, the NANPA may be requested to participate in dispute resolution
by providing guidance and/or historical data.

The NANPA shall abide by the NANC dispute resolution process. The NANPA
shall provide any information it has relative to the dispute to the
appropriate group responsible for resolving the dispute.

For all disputes, concerns, complaints, and issues raised by clients,
oral or written, the NANPA shall prepare a document that contains:

-   Description of the dispute, concern, complaint, or issue (recorded
    within one business day)

-   Plan of action (recorded within one business day)

-   The resolution and reasoning (recorded within one business day of
    resolution)

-   Business days passing before referred to appropriate state or
    federal regulators

-   Business days passing before resolution accepted by complainant

## 232.13Number range Level2Number range Level3Number range Level4 Data Security

The NANPA shall be responsible for maintaining the security,
reliability, performance and flexibility of the NANP Administration
systems. The systems shall protect the sensitive nature of any
information provided by service providers, the Pooling Administrator
(PA) or any other source of proprietary or confidential information.

The NANPA shall protect any service provider-specific data designated as
confidential unless otherwise directed by that service provider or the
FCC.

### 232.13.1Number range Level3Number range Level4 Limited Access

All work areas shall have limited access and secured record retention
practices to ensure that service provider-specific data is afforded the
level of security required to maintain its designated security status.

NANP Administration Systems shall have, at a minimum, security measures
that are in conformance with the FCC Computer Security Program (FCC INST
1479.2). Systems shall include appropriate security measures for
confidential data and accessibility for all service providers to their
own information through an appropriately secured mechanism. The NANPA
shall provide state commissions limited password-protected access to the
CO Code administration database.

### 232.13.2Number range Level3Number range Level4 Physical Security

The NANPA shall provide suitable security for any and all computer
systems that contain assignment information and proprietary applicant
information. This includes any system that is connected to any
telecommunications network. The NANPA shall maintain and enforce
physical security procedures that conform to the requirement to maintain
confidential and proprietary information.

The NANPA shall also be responsible for the activities of any
subcontractors to ensure the security of all systems and data, including
requiring all subcontractors to execute a nondisclosure agreement.

The NANPA shall ensure that any data requested by a non-NANPA entity is
protected as confidential by that entity through applicable law or
another documented nondisclosure mechanism.

### 232.13.3Number range Level3Number range Level4 Site Visits

The FCC, with or without notice to the NANPA, shall have the right to
make visits to NANP Administration and data centers to review
safety/security requirements. If the safety and physical security
procedures do not comply with those specified, the NANPA shall correct
such noncompliance within ten business days.

In the event of non-compliance the NANPA shall implement corrective
measures and give notice of such implementation to the FCC, and the FCC
may make one or more follow-up visits to the affected site, as
necessary, to confirm that the deficiency has been rectified. The FCC's
rights under this paragraph shall not in any way limit the FCC's ability
to visit any site for reasons other than a safety/security visit.

Inspections shall include, but not be limited to, the facilities of
subcontractors, telecommuting employees of the NANPA or subcontractors,
NANPA or subcontractor maintenance organizations, or individuals on
traveling status with access to NANPA's systems.

### 232.13.4Number range Level3Number range Level4 Data Accessibility

Systems shall have logon ID and password access. Formal access shall be
initiated upon receipt of a completed logon ID request form having the
proper signature approvals from the requesting organization. The user's
security requirement sets the correct level of record access and system
capabilities. For forms and reports requiring an applicant signature, a
valid logon ID and password shall be considered tantamount to an
applicant signature.

### 232.13.5Number range Level3Number range Level4 Unauthorized Access

In the event that the NANPA becomes aware of an unauthorized access to
its systems or user or service provider data, the NANPA shall
immediately notify the FCC and the applicable user(s) by e-mail,
investigate the unauthorized access, and provide the FCC and its
designees with reasonable access to all resources and information in the
NANPA's possession as may be necessary to investigate the unauthorized
access. The FCC shall have the right to conduct and control any
investigation relating to unauthorized access that it determines is
appropriate.

## 232.14Number range Level2Number range Level3Number range Level4 Implementation Plan

The NANPA shall provide an Implementation Plan to the FCC within 30 days
of contract award and an update of the Plan 30 days prior to the
takeover of NANP Administration. The objective of this Implementation
Plan shall be to achieve a seamless continuance of NANPA services across
Terms of Administration.

## 232.15Number range Level2Number range Level3Number range Level4 NANPA Transition to Successor

The NANPA shall transfer, in the case of termination or at the
expiration of the Term of Administration, to the FCC or designee all
hardware, software, and rights to software contracts and other
intellectual property as outlined in the Transition Plan.

This NANPA transition is additionally subject to the termination and
continuity provisions in Section H of the Solicitation. All bidders
should identify transition-related costs separately, including costs for
transition from its predecessor and costs for transition to a successor.

Any other equipment or contracts associated with NANPA day-to-day
operation shall transfer. This shall include but is not limited to:

-   The systems and all supporting documentation

-   All software

-   All hardware

-   Computers and related equipment

-   Other peripheral devices

-   All NANPA records both current and stored

### 232.15.1Number range Level3Number range Level4 Transfer Efficiency

The transfer of all property shall be performed in a manner that shall
ensure an efficient and orderly transition of the NANP Administration
System and associated equipment to a successor's environment in a fully
operational state.

### 232.15.2Number range Level3Number range Level4 Technical Support

The NANPA shall provide at least 15 working days, but up to 45 working
days over a 6-month period, if required, of technical support to ensure
a smooth transition of the system.

### 232.15.3Number range Level3Number range Level4 Documentation

The contractor shall provide the FCC with copies of all documentation
specified in the System Documentation Plan.

### 232.15.4Number range Level3Number range Level4 Transition Plan

The NANPA shall, 180 calendar days prior to contract termination,
provide a detailed plan for an efficient and orderly transition. This
transition plan shall follow the format, as applicable, of Reference 28,
*Software Transition Plan (STrP)*.

## 232.16Number range Level2Number range Level3Number range Level4 Term of Administration

The NANPA shall serve for an initial period of up to five years.

At any time prior to the termination of the initial Term of
Administration, the Term of Administration may be renewed up to five
years in length with the approval of the NANPA and the FCC.

## 232.17Number range Level2Number range Level3Number range Level4 Interfaces

The NANPA shall interact with the PA, the NPAC, the LERG, state, Federal
and NANP member country regulatory authorities, as well as with service
providers.

The NANPA shall also interact with the news media concerned with
numbering matters. Information and data shared with the news media shall
be factual in nature, publicly available and previously made known to
the industry and regulators prior to media disclosure.

At this writing, NeuStar is both the PA vendor and the NPAC vendor.
Telcordia maintains the LERG. Service providers, federal and state
regulators, and NANP member countries are responsible for establishing
mutually-agreed upon communication interfaces with the NANPA that meet
their individual equipment requirements.

### 232.17.1Number range Level3Number range Level4 Interface With the Pooling Administrator

The interface between the PA and the NANPA shall be used to exchange
information on the status of pooling and to solicit data that is
relevant to the daily functions of each administrator. NANPA shall
maintain a mechanized interface between the NANP Administration System
(NAS) and the Pooling Administration System (PAS) to permit the flow of
information pertaining to applications for central office code
assignments.

### 232.17.2Number range Level3Number range Level4 Interface With BIRRDS

The NANPA shall maintain access to the BIRRDS (Business Integrated
Rating and Routing Database) and LERG to perform both its administrative
functions and the required Enterprise Service.

The BIRRDS interface consists of a gui interface. The interface shall be
used to enter data into the BIRRDS database for central office code
assignments. (Telcordia maintains the BIRRDS database, which is used to
produce the LERG.) The NANPA shall arrange directly with Telcordia for
LERG access.

### 232.17.3Number range Level3Number range Level4 Interface With the Number Portability Administration

The interface shall be used to request information from the NPAC about
NXXs that are about to be reclaimed by NANPA to ensure that there are no
ported Telephone Numbers (TNs) contained within the NXX targeted for
reclamation. If the NANPA finds that there are ported TNs within the
targeted NXX, the NANPA shall refer to the appropriate guideline for
alternative reclamation processing steps.

### 232.17.4Number range Level3Number range Level4 Interface With the Service Providers

The Service Provider (SP) interface shall be used to receive NANP
resource applications and to send assignments, in a relay between the
NANPA and a service provider.

Any or all of the following interfaces also may be necessary, depending
on the particular service provider with which interaction is taking
place: system-to-system (FTP), web site, e-mail, facsimile, and U.S.
Mail. For example, these interfaces shall be used to receive requests
and to send assignments. They are also used for Number Resource
Utilization and Forecasting (NRUF) form submissions and to return a
confirmation receipt to the service provider after an application and/or
form has been accepted by the NANP Administration System for processing.
NANPA is responsible for ensuring the availability of these interfaces.

### 232.17.5Number range Level3Number range Level4 Interface With the FCC

This interface shall be used to obtain the information necessary to
conform to the FCC rule found at 47 C.F.R. §1.1910 and commonly referred
to as the "red light rule." This rule provides that anyone filing an
application or seeking a benefit from the Commission or one of its
components (including the Universal Service Administrative Corporation,
the Telecommunications Relay Service, or the North American Numbering
Plan Administrator) who is delinquent in debts owed to the Commission
will be barred from receiving a license or other benefit until the
delinquency has been resolved. Under this rule, when an application or
request for benefit is filed, the FCC Registration Number (FRN) will be
checked to determine if the entity or person is delinquent in debt owed
to the Commission. If the NANPA finds the applicant appears on the FCC's
Red Light List, they will withhold numbering resources from that entity.

### 232.17.6Number range Level3Number range Level4 Interface With the State Regulatory Agencies 

This interface shall support state regulatory access as appropriate to
forms and applications filed by service providers. It may also be
necessary to fulfill a data request by voice, facsimile or U.S. Mail.
For example, the interface shall be used to provide a regulator forecast
and utilization data for an NPA within its jurisdiction.

The NANPA may be called upon to testify in regulatory hearings. In these
cases the NANPA shall ensure that its testimony is specific to the scope
and requirements of this contract. Testimony in regulatory hearings
shall be treated as an enterprise service (see Section 11).

The NANPA shall also be responsible for interfacing with regulatory
authorities in person, when requested by such authority. The nature of
these meetings may be educational or informational depending on the
circumstances and issues identified.

### 232.17.7Number range Level3Number range Level4 Interface With the Media

The NANPA shall also be required to communicate with the press.

The NANPA shall prepare press releases and speak to the public in
matters relating to all aspects of administration and management of NANP
resources.

### 232.17.8Number range Level3Number range Level4 Interface With the ITU Technical Standards Bureau

The NANPA shall interface with the ITU-Technical Standards Bureau (TSB)
when required to provide information regarding the NANP. This
information shall consist of the latest web links, contact individuals
and timely information on the NANP, and any changes to the NANP (*e.g.*,
the introduction of new NPAs) as required from national numbering
administrators per ITU Recommendations.

### 232.17.9Number range Level3Number range Level4 Interface With the ITU Study Group 2

The NANPA shall interface with the U.S. State Department and
participating service providers through their attendance at ITU Study
Group 2 meetings and activities. The NANPA's role shall be to advise the
participants as to whether international issues and conflicts shall have
an impact on the management and availability of NANP resources.

## 232.18Number range Level2Number range Level3Number range Level4 Mobile Identification Number Block Identifier Administrator

The NANPA shall be required in the United States to work with the
neutral third party Mobile Block Identifier (MBI) administrator, for the
Mobile Identification Number (MIN) administration for wireless LNP and
thousands-block number pooling.

MIN-based wireless providers register existing MBIs and obtain new ones
through the MBI Administrator. NANPA shall interface with the MBI
Administrator on, among other issues, MBI Resources and NPA splits.

### 232.18.1Number range Level3Number range Level4 MBI Resources

MBI Administration needs to continually add MBI resources to its
database. The MBI Administration Guidelines and Procedures, developed by
Cellular Telephone Industries Association (CTIA) and the MBI Oversight
Council, state that "MBI Administration shall monitor the assignment of
central office codes on an ongoing and timely basis." The NANPA shall
provide the MBI Administrator information on the resources that are
available as assignable MBIs.

### 232.18.2Number range Level3Number range Level4 NPA Splits

In an NPA split situation, the wireless providers retain the MINs of the
old NPA, even if their Mobile Directory Numbers (MDNs) change because of
the split. The MDNs associated with the MINs may have a different NPA
and may become available for assignment in the old NPA, but the MINs or
MBIs remain the same so that customers do not have to bring in their
handsets to be reprogrammed. If an NPA-NXX combination becomes available
for assignment of MDNs in the old NPA, that corresponding MIN bloc
should already show up in the MBI administrator's database as "assigned"
and the corresponding MINs shall not be assigned again to a different
carrier. In addition, the MBI Guidelines state that the MBI
administrator shall not assign the corresponding MBIs for unassigned CO
Codes in order to accommodate non-LNP capable carriers. This is true for
all NPAs. If, however, the MBI has already been assigned before the
split and now the corresponding NPA-NXX becomes available for MDN
assignment in the old NPA, it creates a need for communication with the
NANPA so that the NANPA does not assign newly available or "freed-up"
NPA-NXX combinations to non-LNP wireless carriers. This is because the
corresponding MBI would already be assigned and would not be available.

# Section 233Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-233number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# NANP Administration {#nanp-administration .Section-Header}

The NANPA is responsible for management, administration, and assignment
of all designated numbering resources within the NANP.

The following list identifies NANP numbering resources that fall under
the NANPA's direct responsibility and management:

-   NPA Codes;

-   CO (NXX) Codes ;

-   International Inbound NPA 456 NXX Codes ;

-   Personal Communications Service (PCS)/NPA-NXX Codes ;

-   Easily Recognizable Code (ERC) 900 NXX Codes;

-   N11 Service Codes (reporting only);

-   Hearing Impairment Codes 800 855-XXXX line numbers;

-   Information Services Codes 555-XXXX line numbers;

-   Carrier Identification Codes (CICs);

-   Vertical Service Codes (VSCs);

-   Automatic Number Identification Information Integers (ANI II)
    Digits; and

-   Additional numbering resources, as may be defined.

The sections that follow describe each resource, and summarize the
NANPA's responsibilities. The NANPA is also required to report the
status of each resource.

## 233.1Number range Level2Number range Level3Number range Level4 Numbering Plan Areas (NPAs)

NPA refers to an area code that is the first three digits of a telephone
number.

NPAs are classified as either geographic or non-geographic:

-   Geographic NPAs are NPAs that correspond to discrete geographic
    areas within the NANP area.

-   Non-geographic NPAs are NPAs that do not correspond to discrete
    geographic areas, but which are instead assigned for services with
    attributes, functions, or requirements that transcend specific
    geographic boundaries.

States within the United States have been delegated area code relief
authority and may have unique directives and legal requirements
associated with approval and implementation of any NPA relief activity.

The NANPA is responsible for assigning NPAs when the criteria for such
an assignment have been met.

The NANPA shall ensure that an NPA assignment conforms to regulatory
directives and NPA relief plans (from the FCC and state commissions) and
industry guidelines (*e.g.*, from the INC).

## 233.2Number range Level2Number range Level3Number range Level4 Central Office (CO) Codes

The three digits after the NPA are referred to as the CO Code. The NANPA
shall monitor the actual and forecasted assignment of CO Codes through
the Months-to-Exhaust (MTE) form filed with each CO Code application.

In addition, forecast and utilization data are submitted to the NANPA by
reporting service providers in the NRUF Report. This information is used
to plan for the assignment of new NPA codes when existing NPA codes near
exhaust (*i.e.*, additional telephone numbers are required to serve
projected demand). The NANP Administration function also includes
consultation with affected service providers and state commission when
the depletion of central office codes necessitates relief.

## 233.3Number range Level2Number range Level3Number range Level4 International Inbound NPA-456 NXX Codes

The 456 NPA and its associated NXXs enable the routing of inbound
international calls for carrier specific services, particular to that
service provider\'s network. The NANPA shall assign the NXXs within this
NPA.

The procedures and guidelines are described in International Inbound NPA
(INT/NPA/NXX) Assignment Guidelines (ATIS-0300049).

## 233.4Number range Level2Number range Level3Number range Level4 Personal Communications Service (PCS) NPA Codes

A PCS NPA-NXX is a non-geographic numbering resource that offers the
user a set of capabilities that allows some combination of personal
mobility, terminal mobility, and service profile management. A PCS
NPA-NXX-XXXX number enables each PCS service user to participate in a
user-defined set of subscribed services, and to initiate and/or receive
calls on the basis of some combination of a personal number, terminal
number, and a service profile across multiple networks at any terminal,
fixed or mobile, irrespective of geographic location. Service is limited
only by terminal and network capabilities and restrictions imposed by
the personal communications service provider.

The NANPA shall manage, assign and administer NXX codes in the PCS NPA
pursuant to regulatory directives and INC assignment guidelines.

The NANPA shall reclaim PCS NPA-NXX codes assigned to entities that fail
to meet the terms specified in the assignment guidelines and /or by
directives from the appropriate regulatory authorities.

## 233.5Number range Level2Number range Level3Number range Level4 Easily Recognizable Code (ERC) Code 900 NXX Codes

The 900 NPA is an ERC used for information services in which the caller
pays for call setup and the specific services associated with the 900
call. The 900 NXX codes shall be assigned and used only for pay-per-call
information services. The codes, referred to as "Pay-Per-Calls," may be
accessed by the public over the PSTN using the dialing format
900-NXX-XXXX.

The NANPA shall reclaim 900 NXX codes assigned to entities that fail to
meet the terms specified in the assignment guidelines and/or by
directives from the appropriate regulatory authorities.

## 233.6Number range Level2Number range Level3Number range Level4 N11 Service Codes

Codes in the N11 format (*e.g.*, 911) are referred to as Service Codes.
There are eight N11 service codes available in the NANP. The FCC
determines the uses of N11 codes, which have been assigned as follows:

  ----------- -----------------------------------------------------------
  211         Community Information and Referral Services

  311         Non-emergency Police and Other Governmental Services

  511         Traffic and Transportation Information

  711         Telecommunications Relay Service (TRS)

  811         Access to One Call Services to Protect Pipeline and
              Utilities from Excavation Damage (US); Non-Urgent Health
              Teletriage Services (Canada)

  911         Emergency
  ----------- -----------------------------------------------------------

The 411 and 611 codes have not been assigned by the FCC. Carriers,
however, use the 411 and 611 codes for access to their directory
assistance and repair services respectively. Unassigned codes may also
be assigned locally with the understanding that a local assignment shall
be discontinued, on short notice, if the unassigned codes are requested
for nationally assigned purposes. Some U.S. states have permitted local
use of certain N11 codes, pending FCC designated assignments.

In Canada, the assignment of the N11 codes is generally consistent with
the table above, except for code 511 which has been assigned for weather
and traveler information services and 811 for non-urgent healthcare
telephone triage service. Other NANP member countries may in the future
designate specific uses for N11 codes within their jurisdictions.

## 233.7Number range Level2Number range Level3Number range Level4 Hearing Impairment Codes-800 855 XXXX Line Numbers

Line numbers from the 800 855-XXXX are used for assisting persons with
hearing impairments. These numbers are assigned individually at the line
level. The NANPA shall administer line numbers within the 800-855-XXXX
resource with respect to services for persons with hearing impairments.
Other NANP member countries may designate specific uses for 800-855-XXXX
line numbers in the future.

## 233.8Number range Level2Number range Level3Number range Level4 Information Services Codes-555 XXXX Line Numbers

The 555 NXX code appears (referred to as "555 numbers" in the form
NPA‑555‑XXXX) in all geographic NPAs for access to information services.
The guidelines permit a subscriber to dial a 555-XXXX number in any NPA
in North America using either a 7-digit or a 10-digit format.

Line numbers from the 555 NXX are assigned either on a national or
non-national basis. National assignment means that the number is
assigned exclusively to a single entity to be used in at least 30% of
the available NPAs or states or provinces in the NANP serving area.
Non-national assignment means that the number is assigned to an entity
for use in a specific geographic area or areas (NPAs, states, or
provinces) to be used in fewer than 30% of the available NPAs or states
or provinces in the NANP serving area. "Non-national" numbers are
available for assignment to multiple entities, allowing those entities
to use the "non-national" number in different geographic areas.

The NANPA shall reclaim 555 NXX codes assigned to entities that fail to
meet the terms specified in the assignment guidelines and /or by
directives from the appropriate regulatory authorities.

## 233.9Number range Level2Number range Level3Number range Level4 Carrier Identification Codes (CICs)

A CIC is a 4-digit numeric code primarily used to uniquely identify an
access customer who has purchased access such as Feature Group B (FGB)
and/or Feature Group D (FGD) access services.  These types of CICs are
primarily used for routing from a local network to the access purchaser
and for billing between the local network and the access purchaser.  In
addition, as the result of a 2002 directive to NANPA from the FCC,
switchless resellers may also be assigned CICs without the requirement
to first purchase direct FG D truck access.  Also, pursuant to agreement
reached by the Industry Numbering Committee (INC) in 2006, Billing and
Collection Clearinghouses that provide third-party bill aggregation
services on behalf of access purchasers may also be assigned CICs as
identifiers only when the use of an ABEC (Alternate Billing Entity Code)
is not technically feasible.

The NANPA shall manage and assign CICs. The NANPA shall reclaim CIC
codes assigned to entities that fail to meet the terms specified in the
assignment guidelines and/or by directives from the appropriate
regulatory authorities. Reclamation occurs most often because the entity
to which the CIC has been assigned does not obtain access within the
six-month period specified in the assignment guidelines.

## 233.10Number range Level2Number range Level3Number range Level4 Vertical Service Codes (VSC)

VSC are standardized codes dialed by customers to access network
features and services (*e.g.*, call forwarding) provided by network
service providers. These codes appear in the \*XX or \*2XX format. The
NANPA shall assign, manage, and approve new VSC assignment requests.

## 233.11Number range Level2Number range Level3Number range Level4 Automatic Number Identification (ANI) II Digits

ANI II digits are two digits that are sent with the originating
telephone number identifying the type of originating station (*e.g.*,
Plain Old Telephone Service (POTS), hotel/motel). The NANPA shall assign
the digits and track the assignments.

ANI II digits are assigned by the NANPA at the request of the INC. The
assignment of an ANI II digit does not imply its ubiquitous
availability.

# Section 234Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-234number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Central Office Code Administration {#central-office-code-administration .Section-Header}

## 234.1Number range Level2Number range Level3Number range Level4 Requirements

The NANPA shall manage the CO Code resource in accordance with federal
regulatory requirements and the latest version of the published *Central
Office Code (NXX) Assignment Guidelines* (ATIS-0300051).

The NANPA shall perform the CO Code administration that encompasses the
following major functional categories:

-   User[^2] Services

-   Processing

-   Client and Internal Communication / Notification Functions

-   Status Reporting

-   Tracking CO Code Utilization for NPA relief

-   Managing jeopardy conditions

The NANPA, in order to perform CO Code Administration functions, shall
maintain considerable knowledge of local/regional environments including
geography, demographics, growth patterns, local dialing plans, and
eligibility requirements. This knowledge shall be applied to each CO
Code assignment. Local conditions for each NPA shall be posted to the
NANPA web site.

The NANPA shall create a Change Management Plan for adapting the CO Code
assignment practices in accordance with updates and modifications to the
CO Code (NXX) Assignment Guidelines and regulatory directives. When
there are changes, the NANPA shall institute a training program to
educate all CO Code Administration staff in order to ensure consistent
application. Training shall be completed within five business days
before the date the change to the guidelines becomes effective.

## 234.2Number range Level2Number range Level3Number range Level4 Functional Specifications

CO Code administration activities include the key functional
requirements detailed below.

### 234.2.1Number range Level3Number range Level4 User Services

The NANPA shall produce and make available information regarding CO Code
Administration processes, guidelines, procedures, interfaces, and
services.

Upon request, the NANPA shall provide information on how to obtain
current documents related to CO Code Administration. The NANPA may refer
users to web sites where information can be located and downloaded.
These documents currently include:

-   CO Code (NXX) Assignment Guidelines

-   NPA Code Relief Planning Guidelines

-   Industry Notification of NPA Relief Activity Guidelines

-   NPA Allocation Plan and Assignment Guidelines

-   Recommended Notification Procedures to Industry for Changes in
    Access Network Architectures

The NANPA shall provide assistance to all entities who use numbering
resources and suggest alternatives, when possible, that may assist users
with numbering resource optimization and utilization issues.

The NANPA shall maintain working knowledge of applicable state
regulations and local dialing plans.

The NANPA shall assist Code Applicants with understanding and completing
all forms and appendices associated with INC Guidelines.

The NANPA shall educate users. Such education may include, but is not
limited to, providing job aides and providing necessary forms and
instructions on the NANPA web site.

The NANPA shall notify its users and interested parties when industry
guidelines or applicable regulatory directives have changed. The NANPA
shall provide electronic notification of administrative process and
procedural changes within five business days of the change being
identified by the NANPA. Implementation of these changes shall include a
transition period before the new process or procedure becomes effective.

The NANPA shall respond to inquiries regarding available and assigned CO
Codes. Such response may consist of referring the user to a specific
page on the NANPA web site.

### 234.2.2Number range Level3Number range Level4 Processing

The NANPA shall receive and verify applications for CO Codes in
accordance with FCC directives and CO Code (NXX) Assignment Guidelines.

If a state commission has not yet chosen a relief method and established
a relief date, the NANPA, as CO Code administrator, and the industry
shall devise the jeopardy conservation or rationing measures, consistent
with the industry guidelines.

As CO Code Administrator, the NANPA shall be aware of and adhere to any
limits on code assignments as ordered by state commissions or agreed to
by industry, as well as any other provisions of rationing plans such as
prioritization of applications.

The NANPA shall apply CO Code optimization practices in accordance with
FCC directives and the CO Code (NXX) Assignment Guidelines, as
appropriate.

The NANPA shall also:

-   Maintain a CO code conflict database and publish on the NANPA's web
    page CO codes by NPA that are "unavailable for assignment" due to
    dialing, routing and/or rating conflicts.

-   Include in this list CO codes that are unavailable due to
    permissible services identified by the state tariff, CO codes that
    are used for testing, and CO codes that are used for unique call
    routing/rating arrangements.

-   Consult, providing details of local/regional environments including,
    for example, geography, demographics, growth patterns, local dialing
    plans, and eligibility requirements.

### 234.2.3Number range Level3Number range Level4 Communication/Notification Functions

The NANPA shall post daily on its web site the NXXs assigned and the
NXXs available in each NPA. This information shall be updated daily as
changes occur. Other means of distributing reports shall be available as
necessary. The NANPA shall follow the CO Code (NXX) Assignment
Guidelines for notification of CO Code assignments. The NANPA shall
enter data directly into the BIRRDS database.

The NANPA shall have the capability to input rating and routing data
into the BIRRDS database as an enterprise service to a code holder.

The NANPA shall issue notification of all CO Code jeopardy situations
and other pertinent CO Code administration activities to the appropriate
regulatory agencies and the affected industry members.

### 234.2.4Number range Level3Number range Level4 Status Reporting

For CO Code Administration, the NANPA shall monitor and report the
status of NXXs in each NPA. These reports shall be generated and posted
to the NANPA web site each business day.

### 234.2.5Number range Level3Number range Level4 Tracking CO Code Utilization for NPA Relief

The NANPA shall fulfill the process responsibilities in accordance with
the NPA relief guidelines and regulatory directives, including the
following:

-   Determine when to initiate NPA Relief by continually monitoring CO
    Code growth and projecting exhaust.

-   Upon the identification of a potential exhaust situation, notify
    appropriate regulatory authorities and affected parties within the
    NPA.

-   If necessary, immediately organize a relief-planning meeting to
    obtain local industry consensus and subsequent regulatory direction
    for a relief implementation plan.

### 4.2.6 Management of Jeopardy Conditions

The NANPA shall:

-   Declare a jeopardy NPA condition within any NPA that meets the
    conditions established in the appropriate industry guidelines and
    regulatory orders.

-   Monitor CO Code growth and projected exhaust.

-   Notify appropriate regulatory authorities and affected parties
    within the NPA.

-   Notify the industry that jeopardy code rationing is available if so
    desired, or may be specified in a pending state commission order if
    the industry does not come to consensus on a rationing plan.

-   Implement NPA-specific conservation measures as a part of CO Code
    application processing, if necessary, subject to local industry
    consensus or regulatory direction.

## 234.3Number range Level2Number range Level3Number range Level4 Management of the Code Inventory

The NANPA shall track and monitor MTE, forecast, and utilization reports
so that it shall be able to forecast demand and anticipate the need for
relief to avoid premature exhaust of each NPA and the NANP.

## 234.4Number range Level2Number range Level3Number range Level4 Resource Reclamation

In accordance with paragraph 237 of the FCC Report and Order and Further
Notice of Proposed Rule Making, March 31, 2000 (FCC NRO Order), the
NANPA shall reclaim numbering resources assigned to entities that fail
to meet the terms specified in the assignment guidelines. The NANPA
shall receive and process Part 4 confirmations from code holders during
the six-month period following the published LERG effective date of the
code. Receipt of a Part 4 from a code holder certifies that the code has
been placed in service. The NANPA shall acknowledge its Part 4 receipt
by issuing the code holder a Part 5 Administrator's Part 4
Receipt/Confirmation verifying the code holder's use. The NANPA shall
maintain a tracking system for receipt of Part 4s and return
notification of Part 5 Forms.

No further action is required of the code holder once a Part 4 has been
submitted. Not later than one month prior to the end of the six-month
period, the NANPA shall send a reminder notice to code holders that no
Part 4 Form has been posted for the code now assigned to them. If
requested, the NANPA shall submit lists of service providers who are
delinquent in the return of the Part 4 forms to state regulators. If a
code holder fails to submit a Part 4 within the time-frame specified by
the FCC, the NANPA shall initiate the reclamation procedures, keeping
accurate and complete records for each action taken. The NANPA shall
obtain either state or FCC regulatory approval prior to initiating the
reclamation process.

The NANPA shall maintain a current point of contact list for CO Code
reclamation. Regulators and service providers are to be included on the
list. In addition, a contact list for all other NANP members shall be
maintained, if necessary.

The NANPA shall provide a confirmation in response to every CO Code
application received.

# Section 235Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-235number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# NPA Relief Planning {#npa-relief-planning .Section-Header}

The NANPA shall perform the area code (NPA) relief functions specified
in the INC NPA Code Relief Planning Guidelines. The NANPA shall be
prepared to work with state regulatory authorities that may choose to
assume any of these responsibilities, pursuant to FCC orders.

The NANPA, in order to effectively perform its NPA relief functions,
shall maintain considerable knowledge of local/regional environments
including geography, demographics, communities of interest, growth
patterns, local dialing plans, and operating/certified service
providers. The NANPA shall determine NPAs in need of relief and
appropriately manage the relief efforts through the implementation of a
new area code.

The NANPA shall notify all affected CO Code holders with regard to NPAs
in need of relief, and any associated meeting information. In addition
to notification, the NANPA shall forward the Initial Planning Documents
(IPD) a minimum of four weeks before any scheduled NPA relief-planning
meeting and the NANPA shall facilitate the meeting. The NANPA shall post
to its web site all NPA relief meeting announcements and preliminary
planning information.

Accordingly, the NANPA shall continue to update the local/regional
information and contact information to meet the level of NPA relief
expected in any given year during its Term of Administration.

## 235.1Number range Level2Number range Level3Number range Level4 Key Responsibilities

Key NANPA NPA relief responsibilities consist of the items noted below.

### 235.1.1Number range Level3Number range Level4 Relief Timing

The NANPA shall determine the need for and identify the timing of NPA
Relief in accordance with CO Code (NXX) Assignment Guidelines and NPA
Code Relief Planning Guidelines. One of the tools for performing this
task utilizes NRUF Report data.

### 235.1.2Number range Level3Number range Level4 Relief Planning Communication

The NANPA shall promptly communicate with all affected industry members
and appropriate state regulatory authorities to advise them of the need
for relief planning to occur.

### 235.1.3Number range Level3Number range Level4 Initial Planning Document (IPD) Preparation and Distribution 

The NANPA shall prepare and distribute to industry members and state
regulatory authorities an IPD for each NPA projected to exhaust over the
forecast period, as identified in the NRUF Report. The IPD shall
describe and assess possible relief options and include detailed
historical information regarding prior years' forecasts, versus the
actual assignment of codes.

### 235.1.4Number range Level3Number range Level4 Relief Planning Meetings

The NANPA shall schedule initial NPA relief planning meeting(s) per the
NPA Code Relief Planning & Notification Guidelines. This meeting shall
be 36 months in advance of the projected NPA exhaust date to permit the
timely planning and implementation of NPA relief.

### 235.1.5Number range Level3Number range Level4 Relief Planning Report

The NANPA shall provide a report to the NANC, once per quarter, on its
success or failure in meeting this Performance Measurement.

### 235.1.6Number range Level3Number range Level4 Relief Planning Consensus Building

The NANPA shall notify interested industry and state regulatory
authorities of NPA Relief Planning meeting(s) and conduct the meeting(s)
with the objective of gaining consensus on a relief plan.

### 235.1.7Number range Level3Number range Level4 Neutral Facilitator Role

The NANPA shall act as neutral facilitator for all relief planning
meeting(s) (i.e., issuing meeting announcements, coordinating meeting
arrangements, setting an agenda, leading the meeting, issuing meeting
minutes, and other duties necessary to conduct the meeting).

### 235.1.8Number range Level3Number range Level4 Proactive Role in Relief Planning

The NANPA shall ensure state regulatory authorities have appropriate
information necessary to endorse industry-consensus relief plans or
develop their own plan if they desire. The NANPA shall proactively work
with the state regulatory authorities to achieve endorsement of a relief
plan by the date established to allow the industry appropriate time for
implementation.

### 235.1.9Number range Level3Number range Level4 Status Reporting on Relief Plans

The NANPA shall track and report on the status of pending relief plans
to the FCC and the NANC each month.

### 235.1.10Number range Level3Number range Level4 Possible Testimony

The NANPA may be requested to provide testimony to the state regulatory
authorities regarding the relief plan, as necessary. This service shall
be treated as an enterprise service (see Section 11).

### 235.1.11Number range Level3Number range Level4 New NPA Code Assignment

The NANPA shall, prior to the NPA relief date, assign a new NPA code(s)
in accordance with the approved relief plan.

### 235.1.12Number range Level3Number range Level4 Implementation Scheduling

The NANPA shall schedule the first implementation meeting once a form of
relief has been selected and ordered by a state regulator.

### 235.1.13Number range Level3Number range Level4 Industry Scheduling

The NANPA shall provide industry notification of NPA code relief
implementation activities (*e.g.*, adequate advance notice, public
announcements, test number and testing period, new boundary maps, new
dialing procedures, Line Information Database (LIDB), the BIRRDS
database, LERG, LIDB Access Routing Guide (LARG), relief date,
permissive dialing period, mandatory dialing date, ANI records). The
NANPA shall also provide notifications of any subsequent changes made by
state commissions to relief dates, permissive dialing periods, or
mandatory dialing dates.

### 235.1.14Number range Level3Number range Level4 Press Release

The NANPA shall, with the input and approval of the state regulatory
authorities and industry, prepare and issue a press release to inform
the public of the approved Relief Plan and respond to requests from the
media and public for information.

### 235.1.15Number range Level3Number range Level4 Implementation Assistance

The NANPA shall assist NPA Relief implementation teams and the Number
Administration Service Center (NASC), as necessary, with modifications
to the toll-free database.

If necessary, the NANPA shall declare a code in jeopardy based upon the
INC definition of a jeopardy situation and implement an NXX
code-rationing plan agreed to by the industry. If there is no industry
consensus on an NXX code-rationing plan, the NANPA shall implement a
state approved rationing plan after the state commission orders NPA
relief. After a state regulatory authority orders a specific form of
area code relief and has established an implementation date, the NANPA
shall adopt and implement that plan as ordered by the state regulatory
authority.

### 5.1.16 Compliance

The NANPA shall:

-   Comply with CO Code (NXX) Assignment Guidelines, NPA Allocation Plan
    and Assignment Guidelines, and NPA Code Relief Planning Guidelines.

-   Implement a planned approach using effective forecasting and
    management tools and skills in order to ensure the availability of
    numbering resources.

-   Facilitate the timely planning and implementation of NPA relief.

-   Proactively work with state regulatory authorities to achieve
    selection of a relief plan by the requested date to allow the
    industry appropriate time for implementation.

If a relief plan has not been approved by 90 days prior to industry
requested approval date, then the NANPA shall notify the state
commission in writing of the date the relief plan approval was requested
-- a copy of which shall be sent to the NANC Chair.

If the state regulatory authorities have not ordered an NPA relief plan
on or before the industry requested approval date, the NANPA shall
notify the FCC and the NANC in writing and provide the date by which an
order is required to avoid jeopardizing the timely implementation of NPA
relief.

## 235.2Number range Level2Number range Level3Number range Level4 User Notification

The NANPA shall maintain an electronic document distribution system,
which NPA relief planners shall use to notify affected users of the need
for an NPA relief meeting and to keep all users informed of final relief
plans and implementation processes.

The document notification system shall also be used to distribute
additional details and data deemed necessary to keep clients informed of
the status of any relief activity that has experienced a delay in
implementation.

# Section 236Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-236number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Utilization and Forecasting {#utilization-and-forecasting .Section-Header}

The NRUF Report is filed twice annually by service providers in
accordance with FCC orders and regulations. Each service provider shall
complete the NRUF Report and submit it to the NANPA on or before
February 1st and August 1st of each year.

The NANPA shall compile, examine, and analyze the data gathered from
these reports and submit its analysis to the NANC, the FCC and state
regulatory commissions that have requested it, semi-annually on the last
business day of April and October of each year, unless otherwise
directed by the FCC.

## 236.1Number range Level2Number range Level3Number range Level4 Responsibilities

The following is a list of the functional areas that fall within the
NANPA's data collection, processing and NRUF reporting responsibilities:

### 236.1.1Number range Level3Number range Level4 Point of Contact

The NANPA shall be the point of contact for collecting forecast and
utilization data. Forms shall be submitted electronically unless
utilizing the Enterprise Service provided by NANPA as described in
Section 11.2. The NANPA shall assist carriers in completing the NRUF
forms by clarifying the service provider requirements to report and
correctly understand the NRUF process.

### 236.1.2Number range Level3Number range Level4 Contact List Maintenance

The NANPA shall maintain a list of the individuals within each reporting
entity identified on the last NRUF report submitted by that entity as
the contact person. The NANPA shall periodically remind reporting
entities in writing of the need to keep the list of contacts current and
accurate.

### 236.1.3Number range Level3Number range Level4 Data Requests

The NANPA shall request the NRUF data from all Service Providers within
the U.S. Such data shall be requested for submission on February 1^st^
and August 1^st^ of each year. All NRUF data shall be aggregated from
within the same timeframe. Data from U.S. service providers shall be
processed separately, and then aggregated with all other reported data
to obtain a complete picture of the status of the NANP.

Canada and the Caribbean will provide exhaust projections to the NANPA.

### 236.1.4Number range Level3Number range Level4 Data Requests in Pooled Areas

In pooled rate centers within an NPA, the NANPA shall receive forecast
data in thousands- block increments. The PA shall provide aggregated
NRUF forecast data to the NANPA.

### 236.1.5Number range Level3Number range Level4 Data Analysis

The NANPA shall compile, examine and analyze all the data obtained from
the semi-annual NRUF Report. The results of this analysis shall be made
available by the NANPA on the last business day of April and October of
each year.

The NANPA shall compare actual NPA exhaust and current exhaust forecasts
with the past five exhaust projections. The NANPA shall summarize the
accuracy of its forecast outlining (1) contributing factors, (2) changes
required, (3) the outcome if no change is made, (4) the parties who
shall participate in the changes, and (5) a description of the activity
each party shall take to realize the desired outcome. The NANPA shall
provide an analysis of the accuracy of its forecasting tool as an NPA
reaches exhaust prior to the beginning of each forecast cycle.

### 236.1.6Number range Level3Number range Level4 Data Reporting

The NANPA shall produce a semi-annual report that summarizes the
projections of exhaust of each NPA and the NANP as a whole. The report
shall at a minimum, be similar in format and content to the *NANP and
NPA Exhaust Analysis* report, currently provided to the NANC.

The NANPA shall highlight significant anomalies, for example, those NPAs
whose projected exhaust date changes by more than six months from one
report to another, and provide a brief explanation for the change.

### 236.1.7Number range Level3Number range Level4 User Support

The NANPA shall be available to its users to answer questions pertaining
to any aspect of the NRUF Report process (*e.g.*, forms, instructions,
analysis, data assumptions, etc.).

### 236.1.8Number range Level3Number range Level4 Data Aggregation

The NANPA shall also compile, examine, and analyze the forecast and
utilization data submitted by reporting service providers between
reporting periods. If it appears that the life of an NPA or the NANP
shall be significantly affected by an updated NRUF Report submitted by a
service provider(s), the NANPA shall report those results within 30 days
of receiving the data submissions from the service provider(s).

In the event that NANP exhaust is affected by an updated NRUF
submission, the NANPA shall send the results to the appropriate
regulatory authority in NANP member countries and the NANC. In cases
that only involve NPA exhaust, the NANPA shall forward the results to
the appropriate regulatory commission.

### 236.1.9Number range Level3Number range Level4 Request to Review Data

At the request of a U.S. state regulatory authority and upon receipt by
the NANPA of a written statement that the state regulatory authority has
confidentiality procedures in place to protect the data, the NANPA
shall, within ten business days, provide a single report containing
disaggregated data to any requesting state that is reported by service
providers in that state, so long as the request is made 30 days after
the deadline for NRUF reporting and before the subsequent NRUF reporting
deadline. Regulators shall also have access to the NRUF data for the
NPAs in their respective states via NAS.

The NANPA shall provide reports to state regulatory authorities per
their initial request and delivery schedule. State regulatory
authorities shall provide the NANPA with requested delivery schedule
changes and report content changes at least 30 days prior to the
effective date of the change. Requests of this nature shall be provided
without an additional charge to the state commission

### 236.1.10Number range Level3Number range Level4 Penalties for Non-Submission

If an NRUF Report has not been submitted by a service provider, the
NANPA shall withhold future numbering requests from that service
provider within the NPA for which the NRUF data has not been supplied.
Once the NRUF data has been submitted, the NANPA shall process the
request.

### 236.1.11Number range Level3Number range Level4 Report Anomalies

If the NANPA identifies any significant inconsistencies or anomalies in
a service provider's data, the NANPA shall inform the submitting service
provider of its findings, provide the specific data relevant to document
the significant inconsistency or anomaly in the service provider report,
and request a review and confirmation (written or oral) from the service
provider.

The NANPA shall allow the service provider five business days to provide
that confirmation, or to resubmit the data. If, after the discussions
with the provider, the NANPA still believes that the provider's data
contains inconsistencies or anomalies, then the NANPA shall report its
findings to the appropriate regulatory bodies (*e.g.*, state
commissions, the FCC).[^3]

The NANPA shall assign no additional numbering resources to such service
providers until the appropriate state commission instructs it to do so.
Where the state commission has chosen not to exercise this delegated
authority, the NANPA shall seek instruction from the FCC.

## 236.2Number range Level2Number range Level3Number range Level4 Development of Tests for Anomalies and Inconsistencies

The NANPA shall examine the NRUF report submitted by each service
provider for inconsistencies or anomalies. The NANPA shall design the
tests and algorithms that it shall use to test the utilization and
forecast data submitted by service providers prior to actually
performing any tests. The NANPA shall provide a detailed description of
the actual methodology employed to identify inconsistencies and
anomalies. The description shall include a list of all assumptions and
rationales incorporated into the methodology tests, as well as any
mathematical formulas that are used.

The NANPA shall also work with the NANC to form criteria for determining
what types of submissions shall be deemed inconsistent or anomalous. It
is expected that the NANPA shall continually refine this process and
remain mindful of the changing telecommunications landscape to ensure
that its methods and assumptions are current and valid.

## 236.3Number range Level2Number range Level3Number range Level4 NANPA Analysis of Data

The NANPA shall accumulate and analyze forecast and utilization data
from each service provider and the PA according to the schedule detailed
in the First FCC NRO Order. The NANPA shall use this information along
with historical and other data possessed by the NANPA to create a
forecast that is as accurate as possible.

### 236.3.1Number range Level3Number range Level4 Methodology for Projecting NPA Exhaust

The NANPA shall project the potential exhaust of NPA codes. Although the
NRUF data shall be the primary source of information for any analysis,
the NANPA shall incorporate other relevant data elements into its
analysis in determining the projected exhaust time frame of each
geographic NPA.

Some of the additional data elements are noted below.

#### 236.3.1.1Number range Level4 NRUF Survey Responses

Once the tests for inconsistencies and anomalies have been performed and
the responses deemed acceptable by the NANPA, these responses shall be
the primary input to any analysis of NANP and NPA exhaust.

#### 236.3.1.2Number range Level4 Historical CO Code Assignment Data

The historical CO Code data includes NXX code assignments over at least
the two years immediately preceding the date of the NRUF for all
industry segments, *e.g.*, Incumbent Local Exchange Carrier (ILEC),
Competitive Local Exchange Carrier (CLEC), two-way Commercial Mobile
Radio Service (CMRS) Carrier, and Paging Carrier.

#### 236.3.1.3Number range Level4 CO Code Rationing

After jeopardy has been declared, the rationed amount shall have a
significant and direct effect on the life of the NPA, regardless of
forecasted demand. In such cases, all other elements may be rendered
irrelevant.

#### 236.3.1.4Number range Level4 CO Code Assignments as of the Data Collection Date

A single recent event can affect the life span of an NPA, and thus CO
code assignments as of the data collection date should be factored into
the exhaust projections.

#### 236.3.1.5Number range Level4 Total Number of Codes Available for Assignment

If relief has been applied since the last reporting period, the
environment will have changed and the analysis must reflect the change.

#### 236.3.1.6Number range Level4 Rate Centers Per NPA

The effects of any rate center consolidation or split within an NPA may
have a significant impact on CO Code demand.

#### 236.3.1.7Number range Level4 Expanded Local Calling Areas

The inclusion of additional carriers in expanded local calling areas may
also have an impact on CO Code demand.

#### 236.3.1.8Number range Level4 Pooling

The impact of thousands-block number pooling on CO Code demand, where it
has been implemented, must also be taken into account.

### 236.3.2Number range Level3Number range Level4 Minimum Analysis Requirements

Prior to performing the analysis, the NANPA shall provide to the NANC a
detailed description of the actual methodology employed. The description
shall include a list of all assumptions and rationales incorporated into
the methodology, as well as any mathematical formulas that are used.

The NANC shall have the opportunity to provide advice and consent to the
analysis methods and assumptions the NANPA uses to perform its analysis
of the NRUF results. Continuous methodology refinement is expected and
encouraged. At a minimum, the analysis shall begin with a determination
of the quantity of available NXXs within each NPA.

Using the aggregated service provider forecasts and the tests developed
by the NANPA to identify inconsistencies and anomalies, the NANPA shall
determine the quarterly NXX demand for each NPA. The actual adjustments
applied shall be consistent with, and fully explained in, the NANPA's
description of assumptions and rationales.

### 236.3.3Number range Level3Number range Level4 Anomalies and Trends

The NANPA shall identify anomalies and trends in numbering usage for all
NANP resources. The NANPA shall assist users in assessing the results
shown and the action required to achieve numbering optimization goals.
On an annual basis, the NANPA shall provide a report to the FCC
reporting any anomalies and trends affecting the NANP.

## 236.4Number range Level2Number range Level3Number range Level4 Number Resource Utilization Form (NRUF) Submissions

The FCC requires U.S. service providers to submit NRUF data
electronically unless utilizing the Enterprise Service provided by NANPA
as described in Section 11.2.

The NANPA shall support three alternative methods for NRUF submission
data collection: electronic file transfer (EFT), spreadsheet attachment
to e-mail, and online entry.

# Section 237Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-237number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Automated System Support {#automated-system-support .Section-Header}

This section describes key requirements of the existing NANP
Administration System (NAS) and its capabilities. The system shall
provide NANPA employees and clients' access to all necessary information
required for NANP numbering resource management.

The NANPA shall maintain the NAS to ensure that the system is capable of
supporting the requirements and functionality acknowledged within this
document. In addition, the NAS shall be upgraded to ensure sufficient
capacity to support current and future resources and users.

This system shall include security measures for maintaining confidential
data and provide accessibility for all users to their own information
through an appropriately secured mechanism. In addition, a user class
shall be maintained that allows specific users (*e.g.*, state regulatory
authorities) to access selected, appropriate geographic data submitted
by other users.

## 237.1Number range Level2Number range Level3Number range Level4 System Characteristics

The NAS shall utilize standard electronic commerce type functionality
that allows efficient user interaction and data file transfer.

Data file transfer shall be simple and easy to understand.

### 237.1.1Number range Level3Number range Level4 System Availability

The NAS shall be available within the timeframes outlined within the FCC
approved transition plan. The NAS shall be seamlessly available for
input, processing, and downloads during users' normal business hours.

Scheduled maintenance shall occur outside of normal business hours and
users shall be notified no less than 30 days in advance of any scheduled
event

### 237.1.2Number range Level3Number range Level4 System Query Capability

For the purpose of this document, a query is defined as the ability to
request and retrieve data stored in the system.

The system shall:

-   Support users' needs to retrieve their data through a query
    capability.

-   Support a user authorization level that identifies the range and
    scope of the data access of each user, including identification
    notice of approved access to their data by other users.

-   Be capable of querying and retrieving one or multiple records using
    any stored data fields.

### 237.1.3Number range Level3Number range Level4 System Scalability 

The NAS shall continue to be expandable and flexible so that it can
easily expand its capacity and number of users.

Examples include:

-   Addition of new NPAs

-   Additional users

-   The addition of new resource, and data elements

-   Expansion of the NANP

## 237.2Number range Level2Number range Level3Number range Level4 System Capabilities

The NAS is designed for high reliability, possess data integrity
features, and allow for economical and efficient system expansion.

The NAS design shall provide for the following capabilities:

-   Capture all relevant applicant and user information.

-   Facilitate the application and data filing process and the capture
    of required data in the database.

-   Provide for generation of user information notices.

-   Possess the ability to track status of all NANP resources.

-   Support ad hoc query capabilities as well as production of
    predefined reports.

-   Assist with NANP Administration document management.

-   Possess the ability to track the status of a user's NANP resource
    application or data filing and the generation of reports regarding
    the tracking status of each application or data filing.

-   Maintain data integrity.

If the system becomes unavailable for normal operations due to any
reason, users shall be notified of the system unavailability within five
minutes of any outage.

When possible, such notification shall be made via electronic
capabilities. When this is not possible the NANPA shall notify all users
via identified contact information by prearranged method (*e.g.* fax,
telephone).

When the system is restored to normal operations, users shall be
notified of the system's availability via electronic broadcast message
within five minutes of system restoration.

## 237.3Number range Level2Number range Level3Number range Level4 System Location

The physical location of NAS facility is at the discretion of the NANPA.
The only limitation is that the facility shall be within the continental
United States. Identification of the proposed system location must be
included in the Bidder's proposal.

### 237.3.1Number range Level3Number range Level4 Facility Characteristics

Space allocated for the NAS shall have the following characteristics:

-   Be a distinguishable area with secure access points.

-   Be contiguous space where personnel are physically located within
    the same area.

-   Provide sufficient backup power to maintain operation through
    electrical outages for at least eight hours.

## 237.4Number range Level2Number range Level3Number range Level4 System Data

NANP numbering resource data and information shall be stored in the NAS
in accordance with the categories and formats that correspond to those
currently used and/or as may be defined in the future by regulatory
directives and industry guidelines.

### 237.4.1Number range Level3Number range Level4 Data Integrity

The NANPA shall ensure that all data stored is accurate and take
commercially reasonable steps to confirm that data processed is
accurate.

### 237.4.2Number range Level3Number range Level4 Confidential Treatment

All individual user-specific data submitted to the NANPA, in any form,
shall be treated as confidential.

Any data that contains proprietary user information shall not be
accessible by the public on the NANPA web site, or published by the
NANPA. The NANPA shall only publish and distribute aggregated data.

### 237.4.3Number range Level3Number range Level4 Automated Submittal

The NANPA shall use the data interface protocols previously adopted and
in use between service providers and the current NANPA vendor.

Except as noted, the NAS shall offer a web interface and/or allow for
automated data input via EFT for applications and data forecast reports,
as well as support an e-mail attachment transfer capability.

The EFT capability shall permit users to forward data in a predetermined
format, which the NANPA shall then use to initiate processing within the
NAS.

### 237.4.4Number range Level3Number range Level4 Automated Data Output Capabilities

The NANPA shall also accommodate automated data output via EFT when
transmitting responses and other industry forms/data or reports to users
per the appropriate industry guidelines.

### 7.4.5 Mechanized Interface with the Pooling Administrator

The NANPA will maintain a functional, mechanized interface between NAS
and Pooling Administration System (PAS) that allows for the passing of
information between the two administration systems and where
appropriate, from SPs to the NANPA via the PAS and vice versa. This
information includes the Part 1, Months-to-Exhaust Forms, Part 3, Part 4
and Part 4A.

### 237.4.6Number range Level3Number range Level4 Alternative Data Capabilities

The NANPA shall also support fax and e-mail submissions of user
documentation (*e.g.*, applications, forms, forecast reports).

## 237.5Number range Level2Number range Level3Number range Level4 System Maintenance

The details of a proposed system maintenance schedule shall be provided
in the NANPA's System Maintenance Plan.

## 237.6Number range Level2Number range Level3Number range Level4 System Security

The NANPA shall maintain and enforce system safety and physical security
procedures in accordance with the *FCC Computer Security Program*
(Reference 25).

The NANPA shall maintain confidential and proprietary information and
institute any physical and safety procedures required.

Following contract award, the NANPA shall prepare a NANPA Security Plan
following, as appropriate, the National Institute of Standards and
Technology (NIST) *Guide for Developing Security Plans for Information
Technology Systems* (Reference 30).

## 237.7Number range Level2Number range Level3Number range Level4 System User Profile Application

The NANPA shall develop and maintain a User Profile application process
for the NAS to ensure that there is a mechanism to distinguish one
system user from another. The NANPA shall maintain the capability to
reach all service providers by maintaining automated and up-to-date
lists of addresses corresponding to all contacts. The NANPA shall update
the list of contacts quarterly. The contact list shall be automated,
facilitating mailing via U.S. Mail or electronically via e-mail.

The User Profile application shall contain at a minimum the contact
information for each client, and other relevant identifying factors such
as service provider operating company number (OCN) and FCC Registration
Number (FRN). The NANPA is not responsible for assigning the OCN.

### 237.7.1Number range Level3Number range Level4 User Logon System

The system shall be able to support access to the NAS data with a unique
logon ID and password upon receipt and approval by the NANPA of a
request form.

### 237.7.2Number range Level3Number range Level4 Logon System Access

Access is initiated upon receipt by the NANPA of a completed logon ID
request form having the proper signature approvals from the requesting
organization.

### 237.7.3Number range Level3Number range Level4 Logon System Approval

After access approval, the NANPA shall assign the unique logon ID and
appropriate security level corresponding to the type of user requesting
access.

### 237.7.4Number range Level3Number range Level4 Logon System Security Level

The user's security clearance sets the correct level of record access
and system capabilities.

### 237.7.5Number range Level3Number range Level4 Logon System Password

After the logon is initialized and entered into the system by the NANPA,
the users shall be informed of the logon activation, and a completed
logon ID request form shall be sent back to the requestor for its
records.

### 237.7.6Number range Level3Number range Level4 Logon System Problems

Users experiencing problems in obtaining a logon ID shall contact the
NANPA for resolution.

The NANPA shall resolve all logon problems within one business day.

### 237.7.7Number range Level3Number range Level4 User Access Permission Classes

The NAS is responsible for assigning new users the appropriate security
permission class. The NANPA shall control access to all records.

### 237.7.8Number range Level3Number range Level4 Password Changes

All user passwords shall be changed every 180 days. If an individual
ends employment with the user, the NANPA shall be immediately notified
and a new password assigned.

### 237.7.9Number range Level3Number range Level4 Unauthorized Client User System Access

In the event the NANPA becomes aware of an unauthorized access to the
NAS or user data, the NANPA shall immediately:

-   Notify the FCC, and the applicable user(s) electronically.

-   Report to the NANC that a breach has occurred and that the affected
    party has been notified.

-   Subject to reasonable access, security, and confidentiality
    requirements, provide the FCC, affected users, and their respective
    designees with reasonable access to all resources and information in
    the NANPA's possession as may be necessary to investigate the
    unauthorized access.

The FCC, or its designee, shall have the right to conduct and control
any investigation relating to the unauthorized access as it determines
is appropriate.

## 237.8Number range Level2Number range Level3Number range Level4 System Inspection

Subject to the NANPA's reasonable access, security, and confidentiality
requirements, a NANP member country or a designee, upon notice to the
NANPA, shall have the right to make visits to the NAS facilities to
review safety/security applications.

However, the NANPA is not required to support more than four visits in
any 12-month period (excluding any follow-up visits referred to in the
following sentence).

If any of the safety and physical security procedures as stated in the
selected vendor's proposal are not implemented and maintained throughout
its Term of Administration, the vendor shall be deemed noncompliant.
Failure to correct such noncompliance within ten days shall subject the
vendor to termination.

The NANPA shall:

-   Implement corrective measures.

-   Give notice of such implementation in preparation for one or more
    follow-up visits to the affected facility, as necessary, to confirm
    that the deficiency has been rectified.

    **237.9Number range Level2Number range Level3Number range Level4
    System Report Administration**

The NAS shall be capable of generating and distributing reports upon
request. All reports, except individual user-specific data, shall be
available and accessible electronically on the NANPA web site. All
individual user-specific data submitted to the NANPA, in any form, shall
be treated as confidential. Any data that contains proprietary user
information shall not be accessible by the public on the NANPA web site,
or published by the NANPA. The NANPA shall only publish and distribute
aggregated data.

### 237.9.1Number range Level3Number range Level4 Report Distribution

Reports generated by the NAS shall be capable of being distributed and
updated automatically. The report distribution system shall support an
exploder list for automatic signup for updated report notification.

The NANPA shall distribute via the NANPA web site all summaries and
comprehensive reports made known to the NANPA or produced by the NANPA
or its affiliate contractor(s) performing NANPA duties in part or whole.

Reports shall be distributed by paper (including via U.S. Mail) and
facsimile when requested. The Bidder shall describe its report
distribution mechanism in its response.

## 237.10Number range Level2Number range Level3Number range Level4 Help Desk

The NANPA shall maintain a help desk that is accessible during the
NANPA's regularly scheduled business hours.

The Help Desk shall be available to assist users with the input and the
interpretation of system-generated reports.

The NANPA shall:

-   Report problems with the web site, facsimile, voice mail or e-mail;
    for each problem the Help Desk will open a trouble ticket.

-   Receive and transmit trouble tickets concerning communications
    problems with other vendors.

-   Require that each trouble ticket be time stamped with minute
    accuracy and stored for recall for up to two years.

-   Require that once a trouble ticket is closed, the originator of the
    trouble ticket shall be notified of disposition of the problem.

-   Summarize the quantity and type of trouble tickets opened and closed
    during the year in the annual report.

-   Require the help desk to assist customers to fill out applications
    or reports or to gain access to other authorized FCC or industry
    information.

-   Require that if out-of-service conditions exists, the time stamped
    on the trouble ticket shall be used as the time for the start of the
    out-of-service period; when the out-of-service condition has been
    cleared and the originator of the trouble ticket notified, the time
    stamped on the last update of the trouble ticket shall be used as
    the end of the out-of-service period.

### 237.10.1Number range Level3Number range Level4 Contact

The telephone number for the Help Desk shall be posted on the NANPA web
site along with other relevant contact information to help users.

The NANPA shall provide mechanisms; *e.g.*, web, voicemail, e-mail, and
facsimile, to be accessible on a 24-hour basis.

With e-mail, the NANPA shall have the capability of transmitting and
receiving e-mail messages with and without attached files. The NANPA
shall provide "firewall" protective screening of all incoming e-mail
messages and attachments based on a security profile established by the
NANPA and approved by the FCC. The NANPA shall additionally provide
virus protection software on all devices that receive e-mail. The NANPA
shall maintain the most recently updated version of virus software as
defined by the software provider.

With facsimile, the NANPA shall provide the capability of transmitting
and receiving ITU G.3 and G.4 facsimiles.

### 237.10.2Number range Level3Number range Level4 Help Desk Referrals

Response to user inquiries for assistance shall include, where
appropriate, referral to a NANPA Subject Matter Expert.

### 237.10.3Number range Level3Number range Level4 Help Desk Actions

Any frequently asked questions (FAQs) and their answers shall be added
to the FAQ page on the web site on at least a monthly basis.

Responses shall be provided within one business day of the request being
sent to the NANPA.

## 237.11Number range Level2Number range Level3Number range Level4 System Generated Notifications

The NAS shall support an email distribution list that both registered
and non-registered NAS users can apply to and receive system generated
notifications. Such email distribution list may be used to send a
general notice to all users, both registered and non-registered.

### 237.11.1Number range Level3Number range Level4 Customized Notifications

The NAS shall allow users to customize notices by geographical location
(*e.g.*, NPA relief planning by NPA or state) and/or resource type that
allows users to select categories of notices they want to receive.

The following subjects shall warrant customized notification support:

-   Instructions for users to subscribe to lists on
    [www.NANPA.com](http://www.NANPA.com/).

-   Topic and geography specific notifications.

-   NPA relief planning, guideline changes, regulatory directives, NANPA
    process changes.

-   NPA exhaust notification and relief planning.

-   General broadcast of system availability.

-   User education opportunities.

-   New items on the web site.

-   New personnel announcements.

-   International activities impacting the NANP.

-   Data related to the status of resources associated with state
    conservation deliberation.

## 237.12Number range Level2Number range Level3Number range Level4 System Testing

Prior to any new system functionality and feature implementation and
turn up, the NANPA shall provide a System Test Plan to the FCC. This
plan shall contain the selection criteria for users to participate in
system testing and the timeline and specific NAS elements to be tested.
The System Test Plan shall follow the format, where applicable, of
Reference 26, *IEEE Standard for Software Test Documentation.*

### 237.12.1Number range Level3Number range Level4 System Test Results

Upon completion of the NAS test, the NANPA shall publish the results of
said test. These results shall be readily available to all interested
parties.

## 237.13Number range Level2Number range Level3Number range Level4 System Disaster Recovery

A disaster recovery process shall be developed to restore the NAS within
two business days.

The NANPA shall develop and implement a detailed Disaster/Continuity of
Operations Plan, following the format, where applicable, of Reference
27, *NFPA 1600 Standard on Disaster/Emergency Management and Business
Continuity Programs.*

In the event of a disaster, the NANPA shall cover all costs associated
with rebuilding or recovering the applications systems, records, and
related information that existed prior to the disaster.

## 237.14Number range Level2Number range Level3Number range Level4 System Backup

The NANPA shall initiate and maintain a backup process that ensures that
the data contained in the system can be restored as needed. System
backup information shall be generated, at least daily, and stored in a
secure off site location that can be accessed within one business day if
backup data is necessary for system restoration. Files shall be retained
online for two years and archived for five years.

## 237.15Number range Level2Number range Level3Number range Level4 System and Equipment Inventory

Inventory data (hardware model, serial numbers and descriptions) on
equipment shall be reported as part of the NANPA's annual reporting
requirements, as well as any upgrades or replacements, including the
license numbers of any Commercial Off-the-Shelf (COTS) software.

## 237.16Number range Level2Number range Level3Number range Level4 System Documentation Plan

The NANPA shall provide the FCC designated Contract Administrator with
copies of the:

-   System Design documentation describing the system's structure,
    modules, and interactions.

-   System Operations documentation describing how to load, operate, and
    maintain the system.

-   System User documentation describing the system and its features
    from the end user perspective.

This documentation should be consistent with Reference 32, *IEEE
Recommended Practice for Software Design Descriptions*, Reference 33,
MIL-STD-498, *Computer Operation Manual (COM)-Data Item Description
(DID)*, and Reference 29, *IEEE Standard for Software User
Documentation*, respectively.

## 237.17Number range Level2Number range Level3Number range Level4 NANP Administration System Transfer to Successor

The NANPA shall transfer to a successor in the case of termination or at
the expiration of the Term of Administration, designated hardware and
software property developed with funding from this contract, including:

-   NAS and its software

-   Designated hardware

-   Computers and related equipment

-   Other peripheral devices

-   Records, both current and historical

The NANPA shall provide the FCC with a list of items that are subject to
transfer at the end of its term. The list shall be filed at the time of
the new or modified systems acceptance. Thereafter, the NANPA shall
update the list annually, and provide such list to the FCC.

### 237.17.1Number range Level3Number range Level4 Transfer Efficacy

Transfer of such physical property shall be performed in such a manner
as to ensure an efficient and orderly transition of the NAS and
associated equipment to a successor\'s environment in a fully
operational state without service interruption to any client.

### 237.17.2Number range Level3Number range Level4 System Software Source Code Escrow

The FCC shall be the custodian of a copy of the source code.

### 237.17.3Number range Level3Number range Level4 System and Equipment Transfer

System equipment shall transfer with lien-free title to the FCC or the
FCC's designee, without charge.

## 237.18Number range Level2Number range Level3Number range Level4 Tools

The NAS shall maintain the applications and tools necessary for users to
access and use the system to perform the applicable tasks and functions.

### 237.18.1Number range Level3Number range Level4 Exhaust Forecasting

Exhaust forecasting currently uses the NRUF tool. Other tools and data
may be needed and used to successfully forecast NPA and NANP exhaust.

The NAS shall validate data submissions for users, process them, and
then the NANPA will prepare and present an accurate NPA and NANP exhaust
forecast report.

The NANPA exhaust report shall be published biannually and as warranted
when information materially affecting the life of an NPA and/or the NANP
becomes known to the NANPA.

The NANPA shall maintain NRUF interface specifications and post them to
the NANPA web site.

The NANPA and the system shall be able to:

-   Produce timely forecasts that are reasonably accurate, currently at
    least 36 months in advance of exhaust as indicated in INC
    guidelines.

-   Retain the models used, the forecast and actual exhaust date for
    each NPA, and a comparison showing the accuracy of each model and
    forecast over the past five years.

-   Produce the NPA Exhaust Report when new data materially affecting
    NPA exhaust becomes available (*e.g.*, within 30 days of NRUF
    deadline).

-   Post all forms and job aids related to NPA Exhaust Forecasting and
    NANP Exhaust Forecasting for users on the NANPA web site.

-   Prepare and present monthly NPA relief tracking report to NANC
    during the NANPA's NANC report.

-   Maintain historical NRUF data by individual service provider so that
    it shall be available to the service provider for the previous five
    years. Additionally, provide service provider access to its NRUF
    data for the current submission cycle within the system.

-   Post exhaust forecasts and actual exhaust dates (without rationing)
    on the NANPA web site.

-   Maintain the forecasting system so that it shall be capable of
    accessing the five prior years of NRUF data forecasts and the
    corresponding actual consumption by service provider and rate area.

#### 237.18.1.1Number range Level4 Application Processing

The NAS and tools shall provide real time access to resource usage and
status data.

The NAS shall support standard electronic filing capabilities, as well
as on-line application processing capabilities via the NANPA web site.

### 237.18.2Number range Level3Number range Level4 CO Codes

Resource application submission shall be available via e-mail, on-line
with the NANPA web site, and by FTP.

The NAS shall process applications by performing application data
validation, resource eligibility verification, and receipt of request
and acceptance/rejection notification to service providers.

The NANPA shall:

-   Complete administrative forms online to avoid the need to send faxes
    and/or e-mail attachments. Web based tools shall be provided for use
    in performing code activities, including Code Requests (Part 1), In
    Service Notification (Part 4), and submission of MTE information.

-   Provide service providers with a web-based application that confirms
    Part 1 data field input accuracy and consistency using drop down
    menus for all appropriate fields, *e.g.*, OCN, FRN, rate area,
    homing tandem, switch COMMON LANGUAGE® Location Identification
    (CLLI™).

-   Display on its web site the status of each NXX block as (1)
    assigned, (2) available for assignment, to include codes in the
    pooling set-aside status, and (3) pending disconnect.

-   Provide accurate assignments, avoid rating and/or routing conflicts,
    and conform to established dialing plans.

-   Send a fax confirming receipt of CO Code applications to applicants
    who do not have electronic capabilities.

### 237.18.3Number range Level3Number range Level4 NPA Exhaust Relief Planning

The NAS shall broadly distribute all meeting notices and Initial
Planning Documents (IPD) via an electronic distribution system,
providing sufficient advance notice of forecasted exhaust and
corresponding anticipated relief meetings.

The NANPA shall facilitate and assist regulators in understanding and
approving the final industry recommendation for relief, and advise the
industry, the NANC, and the FCC on its progress and the status of the
approval of the NPA Relief Plan.

### 237.18.4Number range Level3Number range Level4 Federal and State Directives/Orders

The NANPA and/or a system application shall be capable of responding to
a request by a regulator for assistance and/or advice on a numbering
resource issue that may affect existing processes and procedures used
today by users in managing NANP resources.

Upon completion, the analysis shall be posted on the NANPA web page when
information becomes releasable so that interested parties can understand
the impact of the selected issue resolution.

The NANPA and the system's applications shall be capable of:

-   Documenting the impact upon users in terms of: (1) the resource
    assignment/change/disconnect application process, (2) the
    application approval criteria, (3) all application forms, and (4)
    reports given to NANPA and reports generated by NANPA for users.

-   Documenting the impact upon: (1) forecast analysis, (2) the
    timeliness of NPA Relief, (3) the need for rationing, and (4) the
    availability of numbering resources.

### 237.18.5Number range Level3Number range Level4 Federal and State Code Conservation Data

The NAS applications shall provide prompt data updates no later than the
next business day after the information has been received. The NANPA web
site shall be updated in the same timeframe.

The system shall produce timely and accurate documents displaying data
and statistics for all numbering resources for viewing by designated
users per confidentiality requirements and data access arrangements
specified by appropriate NANP member regulatory authorities.

Users shall be able to check the status of resources in real-time and
"look-up" specific conditions and administrative practices required by
local jurisdictions, including dialing and geographic characteristics
impacting the assignment and use of numbering resources.

The NANPA shall prepare summaries that describe local conditions and
geographic characteristics that vary from national guidelines. The
system shall also maintain existing NANP administrative duties, and user
application processes. The system's application shall be capable of
assembling this information so that it is readily available for user
access.

### 237.18.6Number range Level3Number range Level4 CIC Access and Usage Report Processing

CIC holders shall provide a usage report to the NANPA per the industry
CIC guidelines.

With respect to CICs subject to reclamation as a result of the NANPA's
usages analysis, **t**he NANPA shall first contact the user to verify
that the CIC should be reclaimed. The NANPA shall, in accordance with
industry guidelines, notify the NANC and the INC of CICs subject to
reclamation and simultaneously post this information to the NANPA web
site.

The NAS shall be capable of accepting CIC usage reports per guideline
requirements on January 31 for the period ending December 31 and no
later than July 31 for the period ending June 30. These reports may also
be mailed and accepted by the NANPA in paper form**.**

The CIC holder interface specifications and programs and processing used
by the NANPA when determining reclamation and recording and storing the
status of CIC codes shall be posted on the NANPA web site. Any new
specifications and reporting requirements shall be reviewed by the NANC
prior to any change.

### 237.18.7Number range Level3Number range Level4 Contact Information

The NAS applications shall record any contact information provided by
resource or subject category. The record shall contain the name,
address, telephone number, company name, title and area of
responsibility (i.e., code administrator, regulatory liaison for a state
or the FCC), and the date the record was verified, entered or updated.

The NAS and its applications shall be capable of report generation using
any of the entered fields for users and the NANPA. Such requests shall
be accessible through the NANPA's web site.

Users shall use the data to facilitate contact and correspondence among
the NANPA, users, the NANC, and industry fora and standards bodies.

## 237.19Number range Level2Number range Level3Number range Level4 Web Site

The NANPA shall provide and maintain an Internet web site.

### 237.19.1Number range Level3Number range Level4 Web Site Content

The NANPA web site shall contain nonproprietary data on all NANP
resources administered by the NANPA. It shall also contain links to the
industry guidelines, industry committees and relevant regulatory
agencies, and other information to assist users in obtaining NANP
numbering resources and the public with understanding NANP resources.

####### Table 237-1. Content on the NANPA Web Site

+-------------------------+--------------------------------------------+
| Category                | Content                                    |
+=========================+============================================+
| 1\. NANPA Information   | NANPA general information                  |
|                         |                                            |
|                         | All relevant contact names, updated as     |
|                         | necessary                                  |
|                         |                                            |
|                         | Telephone numbers                          |
|                         |                                            |
|                         | Facsimile numbers                          |
|                         |                                            |
|                         | E-mail addresses                           |
+-------------------------+--------------------------------------------+
| 2\. NPA Information     | Assigned, reserved for possible geographic |
|                         | relief (Specific areas not indicated)      |
|                         |                                            |
|                         | Other non-available NPA codes              |
|                         |                                            |
|                         | NPAs assigned by state or region           |
|                         |                                            |
|                         | Locations served by NPA                    |
|                         |                                            |
|                         | Dialing plans per NPA                      |
|                         |                                            |
|                         | Relief plan, planning and implementation   |
|                         | meetings, and implementation status        |
+-------------------------+--------------------------------------------+
| 3\. NPA NXX Code        | NPA-NXX assigned, the carrier to which the |
| Information             | NXX is assigned, effective date            |
|                         |                                            |
|                         | NPA-NXX test numbers                       |
|                         |                                            |
|                         | Unavailable NXXs                           |
|                         |                                            |
|                         | Summary of assigned and available NXXs per |
|                         | NPA                                        |
|                         |                                            |
|                         | During NPA relief activities: current data |
|                         | reflecting relief activity (*e.g.*, NXX    |
|                         | code assignments in each NPA, key dates,   |
|                         | etc.)                                      |
+-------------------------+--------------------------------------------+
| 4\. 900 NXX Information | List of assigned 900 NXX codes and the     |
|                         | carrier to which the NXX is assigned       |
+-------------------------+--------------------------------------------+
| 5\. PCS NPA NXX         | List of assigned PCS NXX codes and the     |
| Information             | carrier to which the NXX is assigned       |
+-------------------------+--------------------------------------------+
| 6\. CIC Information     | List of assigned CICs and the carrier to   |
|                         | which the CIC is assigned and date         |
|                         | assigned                                   |
+-------------------------+--------------------------------------------+
| 7\. Vertical Service    | List of assigned VSCs and their respective |
| Code Information        | purpose                                    |
+-------------------------+--------------------------------------------+
| 8\. 456 NXX Code        | List of 456 NXX codes and the carrier to   |
| Information             | which the NXX is assigned                  |
+-------------------------+--------------------------------------------+
| 9\. ANI II Digits       | List of assigned ANI II digits and the     |
| Information             | stated purpose of the code                 |
+-------------------------+--------------------------------------------+
| 10\. 555-XXXX Line      | List of 555 line numbers and the           |
| Number Information      | carrier/service provider to which the      |
|                         | 555-XXXX line number is assigned           |
+-------------------------+--------------------------------------------+
| 11\. N11 Service Code   | List of assigned N11 Service Codes and a   |
| Information             | description of the service to which the    |
|                         | N11 code is assigned                       |
+-------------------------+--------------------------------------------+
| 12\. 800-855 Number     | List of assigned 800-855 numbers and the   |
| Information             | carrier/service provider to which the      |
|                         | 800-855 number is assigned                 |
+-------------------------+--------------------------------------------+
| 13\. Description of and | Information concerning any new numbering   |
| details on new          | resources made available by the North      |
| numbering resources as  | American Numbering Plan (NANP)             |
| may be identified and   |                                            |
| defined in the future   |                                            |
+-------------------------+--------------------------------------------+
| 14\. INC Number         | List of links to the INC Number Assignment |
| Assignment Guidelines   | Guidelines                                 |
+-------------------------+--------------------------------------------+
| 15\. NANPA Planning     | List of all NANPA Planning Letters by year |
| Letters relative to NPA |                                            |
| Code Relief (*i.e.*,    |                                            |
| notification of         |                                            |
| assigned NPA and key    |                                            |
| dates associated with   |                                            |
| implementation)         |                                            |
+-------------------------+--------------------------------------------+
| 16\. Other NANPA        | Document and other information concerning  |
| information as directed | number assignment and administration made  |
| by the NANC or          | by NANC and/or regulatory agencies         |
| appropriate regulatory  |                                            |
| authorities             |                                            |
+-------------------------+--------------------------------------------+
| 17\. NANPA Reports      | List of NANPA Reports concerning numbering |
|                         | resources (does not include enterprise     |
|                         | service reports)                           |
|                         |                                            |
|                         | Annual report (downloadable in a           |
|                         | machine-readable form using standard word  |
|                         | processing and spreadsheet programs, as    |
|                         | appropriate).                              |
+-------------------------+--------------------------------------------+
| 18\. NANP member        | List of all NANP member companies and      |
| countries and any       | appropriate contact information.           |
| applicable information. |                                            |
+-------------------------+--------------------------------------------+
| 19\. Index of reference | FCC related directives                     |
| documentation also      |                                            |
| called the Binder of    | State directives under delegated authority |
| Decisional Principals   |                                            |
|                         | Other NANP member nation directives        |
+-------------------------+--------------------------------------------+

### 237.19.2Number range Level3Number range Level4 Content Posting

New information and documentation shall be posted to the NANPA web site
within one business day of its release.

Information contained on the web site shall be updated within one
business day of any change or document release.

### 237.19.3Number range Level3Number range Level4 Web Site Design

The NANPA web site ([www.nanpa.com](../www.nanpa.com)) shall be reliable
and be able to quickly fulfill reasonable user expectations. The NANPA's
web site shall be designed and maintained to ensure its accessibility
according to the following principles:

-   Maintain a NANP web site easily accessible by all users.

-   Allow web site pages to be navigated by keyboard.

-   Provide alternative methods to access non-textual content, including
    images, scripts, multimedia, tables, forms and frames for users who
    do not wish to display them.

-   Use accepted web site features (*e.g.*, drop down menus) to provide
    information about the purpose and function of web site elements.

-   Provide a search engine to facilitate site navigation.

### 237.19.4Number range Level3Number range Level4 Availability and Access

The NANPA web site shall be available 24 hours a day, 7 days a week.

The web site shall be able to support up to 500 simultaneous users with
an average holding time of 0.5 hours.

### 237.19.5Number range Level3Number range Level4 System Responsiveness

The NANPA shall provide rapid response when accessing the web site. The
NANPA shall provide a system such that a 56 Kbps modem-equipped user
will be able to view the complete home page in less than 8 seconds, 95%
of the time over any 12-month period.

If a user is experiencing greater than 12 seconds to view the complete
home page, the NAS shall have the capability to sense this condition.
The NANPA shall open a trouble ticket to investigate whether the problem
is between the web site and the Internet Service Provider (ISP) or is in
the NAS. If the user reports to the help desk a problem with accessing
information on either the web site or the NAS, a trouble ticket shall be
initiated to determine if an "out of service" condition exists.

### 237.19.6Number range Level3Number range Level4 Out-of-Service

The NANPA web site shall be operational 99.9% of the time over any
12-month period, excluding scheduled maintenance. NANPA's inability to
deliver services at this level shall be deemed "out of service." This
figure excludes problems due to the customer's network or equipment.

All scheduled maintenance activities shall occur during non-core
business hours, shall require prior approval of the FCC, and shall not
exceed a four-hour period unless approved by the FCC.

The NAS shall be capable of "pinging" its ISP(s) every five seconds to
confirm that the round-trip latency is less than or equal to 10
milliseconds. If the latency is greater than 10 milliseconds, the
connectivity between the web site and ISP(s) shall be considered out of
service and a trouble ticket opened.

### 237.19.7Number range Level3Number range Level4 Out-of-Service Notification

The NANPA shall be the point of contact for system recovery. The NANPA
shall be capable of distributing system status and outage reports to all
registered users.

All scheduled maintenance activities shall be approved in advance by the
FCC prior to commencing the activity. Once the FCC has approved the
scheduled maintenance activity, the NANPA shall provide notification to
all registered users as to when the activity will begin and end, as well
as the impact on the users.

### 237.19.8Number range Level3Number range Level4 Web Site Privacy

Web site privacy shall be monitored every time content and transaction
functionality is added or changed to avoid any risk of exposing the web
site to privacy risks and inappropriate access to the content.

#### 237.19.8.1Number range Level4 Privacy Management

Privacy management shall include the rules that govern the collection,
use, retention, and distribution of data. It shall address the privacy
needs of users by assessing the risks to confidential data; managing the
implementation of privacy policies and associated procedures; ensuring
on-going compliance; monitoring developments, accommodating changes, and
raising awareness within the NANPA's organization; and training NANPA
staff.

#### 237.19.8.2Number range Level4 Privacy Compliance

The NANPA's privacy practice shall contain details listing the
compliance with the Gramm-Leach Bliley Act of 1999 regarding regulating
the privacy of personally identifiable, non-public financial information
in the United States, and the privacy requirements per the Personal
Information Protection and Electronic Documents Act in Canada.

The NANPA shall prominently display its privacy statement explaining
NANPA's information handling practices.

#### 237.19.8.3Number range Level4 Privacy Breaches

The NANPA shall monitor web site access to ensure that identified
privacy practices are not compromised in any fashion.

Any web site data privacy breach shall be documented and reported to the
affected user and the appropriate regulatory authority. The NANPA shall
report the web site privacy breach to the FCC.

### 237.19.9Number range Level3Number range Level4 Maintenance of NANC Chair Web Site

The NANPA shall support and maintain an independent web site, the NANC
Chair web site ([www.nanc-chair.org](../www.nanc-chair.org)). The NANPA
is the administrator of the NANC Chair web site and as such shall be
required to maintain the web site in the same manner (*e.g.*,
accessibility, security) as the NANPA web site.

#### 237.19.9.1Number range Level4 Responsibilities

The NANC Chair web site administrator shall post documents as requested
by NANC members, members of the industry and regulatory agencies to the
web site in a timely manner prior to NANC meetings. In addition, the
administrator shall post documents and meeting records from the NANC's
designated supporting groups, *e.g.*, Working Groups and Issue
Management Groups (IMGs), and make those records easily accessible.

#### 237.19.9.2Number range Level4 Content

The following is a partial list of the content contained on the NANC
Chair web site:

-   Links to relevant web sites (*e.g.*, those administered by the FCC,
    the NANPA, and the INC).

-   Specific documentation (*e.g.,* NANC meeting minutes).

-   Working Group and IMG documentation (e.g*.*, meeting records, work
    in progress).

-   NANC, Working Group, IMG, and appropriate industry forum meeting
    dates by calendar year.

# Section 238Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-238number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Reporting {#reporting .Section-Header}

The following section discusses the numbering resource reports and the
web site requirements for the NANPA.

NANPA reporting shall take three forms: the first form shall be as an
update to a table or document on the NANPA web site; the second form
shall be as an electronic attachment to an e-mail distribution list; the
third form shall be as paper documents physically distributed at
meetings.

The NANPA shall provide regular reports on all NANP numbering resources
to the NANP distribution list. The NANPA shall provide reports in March
and in September on all numbering resources administered by the NANPA.
Reports shall contain a written summary interpreting trends and the
impact of new data upon numbering resources and the NANP in general. The
report shall contain, at a minimum, the following information:

-   Assignments (assigned and available resource)

-   Assignment rates

-   Historical trends

-   Projections (*e.g.,* NPA exhaust)

-   Triggers for user action

The NANPA shall report annually its projection for NANP exhaust.
Further, the NANPA shall notify the FCC, the NANC and other necessary
parties of any significant changes, as they occur, that might
substantially alter the NANP exhaust projection.

The report format shall be subject to change and shall include any other
information the NANC or the FCC deem necessary. The reports shall be for
all resources not in a designated form of jeopardy. For those jeopardy
resources the NANPA shall publish reports on a monthly basis when there
are high assignment rates and the resources are in danger of being
depleted within two years.

In addition, the NANPA shall identify and develop other reports deemed
necessary for managing the NANP resources in the future.

## 238.1Number range Level2Number range Level3Number range Level4 Annual Report

The NANPA shall publish this document annually to report on the status
of the NANP, NPAs, and CO Codes.

The report shall be published during the first quarter of each year. It
shall contain the results of the previous year-end NRUF survey results.
The annual report shall also be reviewed during the NANC annual
performance review process.

The annual report shall contain at a minimum, but not be limited to:

-   Brief description of the NANP

-   Historical trends

-   Highlights/significant milestones reached during previous year

-   Current NPA Code assignment listings-Alphabetical by State/Province
    and in numerical order

-   Current list of reserved NPAs

-   NRUF forecast results-Current year forecast

-   Exhaust projections for individual NPAs and the NANP

-   Status of NPA Codes

-   NPA-specific dialing plans

-   Description of all numbering resources assigned by the NANPA and
    appropriate points of contact

-   Activities identified in the Annual Report shall also be placed on
    the NANPA web site

## 238.2Number range Level2Number range Level3Number range Level4 NRUF Report

This report shall be produced and delivered to the FCC, to the NANP
member nations, and the NANC. The NANPA shall provide aggregated
forecast and utilization data to any requesting U.S. state user twice
per year consistent with the dates of the NRUF reporting process.

Within ten calendar days of the request, the NANPA shall provide to any
requesting state commission a single report containing only
disaggregated data reported by service providers in that state, so long
as the request is made 30 days after the deadline for NRUF reporting and
before the subsequent NRUF reporting deadline.

Because state commissions might wish to perform their own data analyses,
the NANPA shall provide the data to requesting states via electronic
transfer, which may include e-mail, or by computer disk. In the
alternative, upon request from a state commission, the NANPA shall
provide the data in paper copy form without additional charge to the
state commission.

### 238.2.1Number range Level3Number range Level4 Data Anomalies

The NANPA shall provide a statement of any identified anomalies along
with documented explanations for each anomaly in all NRUF reports to
assist users in assessing the reports' impact and results.

These reports shall serve several different functions, including the
following:

-   Assist in interpreting the NRUF data.

-   Review the NANPA's data management and analytical performance.

-   Assess the effectiveness of numbering resource optimization efforts.

### 238.2.2Number range Level3Number range Level4 Reports to Regulatory Authorities

The NANPA shall produce a list of all standardized NRUF data reports
offered to users. The NANPA and interested regulatory authorities shall
meet annually to determine the reports' format and content. These
reports shall be produced by the NANPA upon demand from an appropriate
regulatory authority, and at no charge to the requestor. Agreed-upon
changes or modifications to these reports shall be at no charge to the
requestor.

These reports, once requested by a regulatory authority, shall be
delivered continually until the regulatory authority notifies the NANPA
otherwise. The NANPA shall also be prepared to produce a state-level
summary of any of the NRUF reports.

Comparison calculations shall properly compensate for the change in
geographic coverage of both existing and new NPAs within areas that
experienced area code splits during the designated reporting periods.

The list below is not meant to be exclusive of any information, nor of
the extent or format of the data requested and required by regulatory
authorities or other users. These reports shall support a variety of
formats, including, but not limited to, text, Microsoft Excel, and
Microsoft Access.

-   Number of carriers in a rate center and/or NPA, identified by type.
    The NANPA shall produce on an as-needed basis a report that
    identifies the number of carriers that provided a NRUF report in a
    rate center and/or an NPA categorized by type as defined in FCC Form
    502.

-   Comparison of actual NPA exhaust with past five exhaust projections.
    To test the assumptions and gauge the NANPA's accuracy, the NANPA
    shall produce annually in April and in September reports that
    compare the actual exhaust dates of each NPA with the NANPA's
    projections for that NPA over the previous five reporting periods.

-   Comparison of most recent NPA and NANP exhaust projections with past
    five exhaust projections*.* To test the assumptions and gauge the
    NANPA's accuracy, as well as to identify any problems that need to
    be addressed immediately, the NANPA shall produce reports that
    compare the most recent projected exhaust dates of NPAs and the NANP
    with the projected exhaust dates of the previous five reporting
    periods.

-   Comparison of aggregated or disaggregated Service Provider (SP)
    forecasts in an NPA with actual growth, with and without rationing.
    To gauge the accuracy of SP forecasts, the NANPA shall produce in
    April and in September reports that compare previous (aggregated) SP
    forecasts within an NPA with actual code demand for that same NPA.

-   Comparison of actual unidentified demand with non-forecasted demand
    growth additive. To test the validity of the non-forecasted demand
    growth additive formula being used, the NANPA shall produce a report
    in April and in September (after three reporting periods) that
    compares the output of the formula with the actual quantity of
    non-forecasted demand that materialized.

-   CO Code growth rate by NPA*.* The NANPA shall produce a semi-annual
    report that provides the CO Code growth rate by NPA for the current
    and previous five reporting periods. The NANPA shall also produce a
    report that compares aggregated growth rates in pooled NPAs with
    growth rates in those NPAs prior to pooling. To test any conclusions
    drawn from this report, the NANPA shall also compare growth rates
    over the same period of time in NPAs that have not been pooled.

## 238.3Number range Level2Number range Level3Number range Level4 NPA Relief Activity Status Report

The NANPA shall report the status of NPA relief planning efforts to the
FCC and the NANC, and post its report on the NANPA and NANC-chair web
sites on a monthly basis. The report shall contain the following
categories:

  -----------------------------------------------------------------------
  Category                Detail
  ----------------------- -----------------------------------------------
  NPA                     NPA needing relief.

  Jurisdiction            NANP member country, state, and locality of NPA
                          needing relief.

  Date Relief Need        Date the NANPA determined that relief was
  Identified              needed.

  Declaration Date        Date the NANPA notified the industry and
                          regulators.

  Exhaust Date upon       Projected exhaust date when the need was
  Declaration             declared.

  Current Exhaust Date    Current projection for exhaust.

  Forecasted Exhaust Date The exhaust date of the NPA based on the latest
                          NRUF data.

  Number of Remaining     Number of NXXs that are available for
  NXXs                    assignment.

  Number of Unavailable   Number of NXXs that are unavailable for
  NXXs                    assignment.

  Initial Relief Planning Date the first NPA relief planning meeting
  Meeting Notice Date     notice was distributed.

  Actual Filing Date      The date relief plan was actually filed with
                          the appropriate regulatory authority.

  Requested               The requested date included in the relief plan
  Implementation Date     when NPA relief shall take place, *e.g.,* end
                          of mandatory dialing for a split, or the
                          effective date for an overlay. When no date is
                          requested, "none" is indicated.

  Requested Relief Type   The recommended NPA relief solution indicated
                          in the relief plan filed with the state
                          commission if the industry was able to reach
                          consensus. In some circumstances, the industry
                          may have reached consensus on more than one
                          alternative.

  Requested Approval Date The date indicated in the relief plan that
                          regulatory authority approval is requested.

  Approval Date           The date the relief plan was approved by the
                          regulatory authority.

  Approved Relief Type    The type of relief plan approved by the
                          regulatory authority (*e.g.,* split, overlay).

  Approved Implementation The date the regulatory authority has directed
  Date                    that the new NPA is to be implemented, *e.g.*,
                          end of mandatory dialing for a split or the
                          effective date for an overlay. In certain
                          situations, a relief implementation date is not
                          provided. The date may be determined at a later
                          time or a trigger is identified (*e.g.*, 60
                          days after the last NXX code is assigned in the
                          existing NPA).

  First Scheduled         The date of the initial NPA implementation
  Implementation Meeting  meeting that the NANPA shall conduct.

  Rationing Date          Date rationing began. If no rationing, leave
                          blank.

  Jeopardy Declared       Date on which jeopardy was declared.
  -----------------------------------------------------------------------

## 238.4Number range Level2Number range Level3Number range Level4 CO Code Activity Status Report

The NANPA shall report the CO Code activity status to the FCC and the
NANC, and post on both the NANPA and NANC-chair web sites a monthly
status report. This report shall reflect the CO Code administration
activity by state, and applicable NANP member country.

The report shall contain the following categories:

  -----------------------------------------------------------------------
  Category                Detail
  ----------------------- -----------------------------------------------
  New Applications        All applications that the NANPA is handling for
                          the first time.

  Assignments             The number of applications that resulted in the
                          assignment of a new central office code.

  Denials                 The number of applications that were denied
                          because the applicable criteria were not met.

  Reclamations            The number of assigned central office codes
                          reclaimed by the NANPA or returned by the
                          assignee.

  Total                   The sum of the above categories, equal to the
                          total number of applications processed.
  -----------------------------------------------------------------------

## 238.5Number range Level2Number range Level3Number range Level4 Other NANP Activity and Status Reports

The NANPA shall provide a status report on any activity that occurs with
other NANP resources that it administers. These reports shall be
provided to the FCC, the NANC and posted on the appropriate web sites on
a monthly basis. The reports shall provide details as appropriate to the
resource and the activity, including the NANP member country in which
the activity occurred.

## 238.6Number range Level2Number range Level3Number range Level4 Requests for Additional Reports

The NANPA may also be requested to produce additional reports as needed.

The NANPA may create and provide data in different formats to
accommodate requests to cull data and provide customized reports as
enterprise services for a fee that is reasonable and based on its costs.
(*See* Section 11 for details on enterprise services).

Note that enterprise services shall be reviewed by the NANC and approved
by the FCC, but, once approved, the NANPA shall be free to negotiate a
reasonable price with requestors.

## 238.7Number range Level2Number range Level3Number range Level4 Reference Documentation

The NANPA shall maintain and make readily available an addendum of
reference documentation to assist interested parties. The list shall
include the most recent version of all guidelines and all NANP-related
regulatory directives and requirements. This addendum shall be posted on
the NANPA web site and updated as needed.

## 238.8Number range Level2Number range Level3Number range Level4 Standardized Reports for State Commissions

The NANPA shall produce a series of standardized reports on CO Code
assignment activity. A weekly report of codes assigned and available by
NPA shall be available on the NANPA public website and, at a minimum,
include the following information:

-   NPA-NXX

-   Use (Available, Assigned, Protected, Reserved, Unavailable)

-   OCN

-   Company

-   Rate Center

-   Initial/Growth

-   Assignment Date

-   Effective Date

This same report will be available in the password protected portion of
NAS and will include switch information in addition to the above data
elements.

In addition, the NANPA shall provide a report on the NANPA public
website that includes the quantity of CO Codes assigned by the NANPA on
a monthly basis. The report shall include the following information:

-   ST-State

-   NPA-Area code

-   NPA Status (*e.g.*, jeopardy, exhausted)

-   Monthly Rationed Amount

-   Total Number on Priority List-If an NPA is in rationing and a
    priority list is used, the total number of code requests on the
    priority list

-   Month-Each month of the year and the quantity of codes assigned in
    that month

-   Current Month's Return-The total number of codes returned to the
    NANPA and made available for assignment

-   Year-to-date Returns-The total number of codes returned up through
    the last reported month

-   Protected-The number of protected codes

-   Total Unavailable-The total number of codes unavailable for
    assignment; these include codes assigned, reserved or otherwise
    unavailable for assignment

-   Total Available-The total number of codes available for assignment
    (i.e., vacant codes)

    NANPA will also provide a state-specific report to those states with
    appropriate confidentiality protections in place that contains
    pertinent information from the Part 1 application submitted by
    service providers and information from the Part 3 response. States
    will be able to select daily, weekly or monthly distribution of this
    report.

## 238.9Number range Level2Number range Level3Number range Level4 Summary of NANPA Technical Reports 

####### Table 238-1. Summary of Technical Reports

+-----------------------------+-------------+-------------------------+
| Name                        | Reference   | Frequency               |
+=============================+=============+=========================+
| Numbering Plan Area         | 8.0         | Weekly and Monthly.     |
|                             |             | Biannually in March and |
|                             |             | in September.           |
+-----------------------------+-------------+-------------------------+
| Central Office Code Status  | 4.1, 4.2.2, | Assigned and available  |
|                             | 4.2.4, 8.0  | posted daily; status    |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| International Inbound NPA   | 8.0         | Within five days of a   |
| Code                        |             | new assignment; status  |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| Personal Communications     | 8.0         | NRUF form               |
| Service Code                |             | semi-annually; upon any |
|                             |             | new assignment. Status  |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| 900 Code                    | 8.0         | NRUF form               |
|                             |             | semi-annually; upon any |
|                             |             | new assignment. Status  |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| 800 Code                    | 8.0         | Semi-annually; status   |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| N11 Code                    | 8.0         | Semi-annually; status   |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| 555 Code                    | 8.0         | New assignments within  |
|                             |             | five days; status       |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| Carrier Identification Code | 6.18.6,     | Semi-annual             |
|                             | 7.5,        | incorporating Entity    |
|                             | 9.5.2.4     | Usage 1 Access Reports; |
|                             |             | upon any new            |
|                             | 3.9         | assignment. Status      |
|                             |             | monthly. Biannually in  |
|                             |             | March and September.    |
+-----------------------------+-------------+-------------------------+
| Vertical Service Code       | 7.18.6, 8.0 | Existing VSCs, new      |
|                             |             | VSCs, and updates;      |
|                             |             | status monthly.         |
|                             |             | Biannually in March and |
|                             |             | September.              |
+-----------------------------+-------------+-------------------------+
| Automatic Number            | 8.0         | Existing ANI, new ANI,  |
| Identification              |             | and new assignments     |
|                             |             | within five business    |
|                             |             | days; status monthly.   |
|                             |             | Biannually in March and |
|                             |             | September.              |
+-----------------------------+-------------+-------------------------+
| Numbering Resource          | 3.2, 6.0,   | Semi-annually on        |
| Utilization Form            | 6.1.5, 8.0, | February and August     |
|                             | 8.2.2       | 1st.                    |
+-----------------------------+-------------+-------------------------+
| Code Relief Planning Report | 5.1.5       | Quarterly.              |
| to NANC                     |             |                         |
+-----------------------------+-------------+-------------------------+
| Status of Pending Relief    | 5.1.9       | Monthly, to FCC/NANC.   |
| Plans                       |             |                         |
+-----------------------------+-------------+-------------------------+
| Contact List Maintenance    | 4.4, 6.1.2, | Quarterly.              |
|                             | 7.7         |                         |
+-----------------------------+-------------+-------------------------+
| NANP/NPA Exhaust Analysis   | 6.16,       | Contingent upon         |
|                             | 7.18.1      | material impact and     |
|                             |             | annually.               |
+-----------------------------+-------------+-------------------------+
| NPA/NANP Life Impact        | 6.1.8       | Contingent, within 30   |
|                             |             | days of receipt of the  |
|                             |             | updated NRUF Report.    |
+-----------------------------+-------------+-------------------------+
| Reports to Regulatory       | 6.1.9,      | Contingent, within ten  |
| Authorities                 | 8.2.2       | days of request         |
|                             |             | following 30 days after |
|                             |             | the NRUF reporting      |
|                             |             | deadline.               |
+-----------------------------+-------------+-------------------------+
| NRUF Anomalies              | 6.1.11,     | Contingent, in case of  |
|                             | 6.3.3,      | unresolveable           |
|                             | 8.2.1       | anomalies, to State     |
|                             |             | Regulatory Commissions  |
|                             |             | or FCC. Also annually.  |
+-----------------------------+-------------+-------------------------+
| NANC Annual Report          | 7.10, 7.15, | Annually during first   |
|                             | 8.1         | quarter.                |
+-----------------------------+-------------+-------------------------+
| CO Code Growth Rate by NPA  | 8.2.2       | Semi-annually.          |
+-----------------------------+-------------+-------------------------+
| Aggregated Growth Rates,    | 8.2.2       | Upon demand.            |
| Pooled vs. Non-Pooled       |             |                         |
+-----------------------------+-------------+-------------------------+
| Aggregated Utilization Data | 8.2.2       | Upon demand.            |
+-----------------------------+-------------+-------------------------+
| NPA Relief Activity Status  | 8.3         | Monthly.                |
| Report                      |             |                         |
+-----------------------------+-------------+-------------------------+
| Disaggregated Data by State | 8.2         | By request, 30 days     |
|                             |             | after the deadline for  |
|                             |             | NRUF reporting and      |
|                             |             | before the subsequent   |
|                             |             | NRUF reporting          |
|                             |             | deadline.               |
+-----------------------------+-------------+-------------------------+
| Number of Carriers in rate  | 8.2.2       | Upon demand.            |
| center and/or NPA, by Type  |             |                         |
+-----------------------------+-------------+-------------------------+
| Comparison of Actual NPA    | 8.2.2       | Upon demand.            |
| Exhaust, with Past Five     |             |                         |
| Exhaust Projections         |             |                         |
+-----------------------------+-------------+-------------------------+
| Comparison of Most Recent   | 8.2.2       | Upon demand.            |
| NPA/NANP Exhaust            |             |                         |
| Projections with Past Five  |             |                         |
| Exhaust Projections         |             |                         |
+-----------------------------+-------------+-------------------------+
| Comparison of Aggregated SP | 8.2.2       | Upon demand.            |
| Forecasts in a NPA with     |             |                         |
| Actual Growth, with and     |             |                         |
| without Rationing           |             |                         |
+-----------------------------+-------------+-------------------------+
| Comparison of Actual        | 8.2.2       | Upon demand.            |
| Unidentified Demand with    |             |                         |
| Non-Forecasted Demand       |             |                         |
| Growth Additive             |             |                         |
+-----------------------------+-------------+-------------------------+
| Standardized Report for     | 8.4, 8.8    | Weekly and monthly.     |
| State Commissions on CO     |             |                         |
| Codes Assigned by the NANPA |             |                         |
+-----------------------------+-------------+-------------------------+
| Part 4 Form Delinquency     | 4.4         | Contingent, for code    |
| Notifications               |             | holders not submitting  |
|                             |             | Part 4 forms.           |
+-----------------------------+-------------+-------------------------+
| Relief Planning Report      | 5.1.5       | Quarterly.              |
+-----------------------------+-------------+-------------------------+

## 238.10Number range Level2Number range Level3Number range Level4 Summary of NANPA Performance Reports

####### Table 238-2. Summary of Performance Reports

  ------------------------------------------------------------------------
  Name                    Reference   Frequency
  ----------------------- ----------- ------------------------------------
  Customer Response Rates 2.7.1       Contingent and annual.

  Dispute/Plan of Action  2.1.2       Contingent, to be prepared within
                                      one business day.

  Self-Assessment         7.10, 9.5   Annually and Quarterly to NANC.

  Post-Audit Corrective   9.1.4       Within 20 days after receipt of the
  Action Plan                         auditor's report and monthly until
                                      completion.

  Unauthorized User       2.13.5,     Contingent upon occurrence.
  Access                  7.7.9       

  System Outage           7.19.7      Contingent upon occurrence to all
                                      clients.

  Privacy Breach          7.19.8.3    Contingent upon occurrence, to
                                      affected client, regulatory
                                      authority, and FCC

  Complaints              2.1.2, 7.10 Contingent, to be prepared within
                                      one business day.
  ------------------------------------------------------------------------

# Section 239Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-239number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Audits and Performance Monitoring {#audits-and-performance-monitoring .Section-Header}

## 239.1Number range Level2Number range Level3Number range Level4 Audit by FCC 

The NANPA shall be subject to audits by the FCC or its designees that
include the following:

-   Compliance with industry guidelines

-   Compliance with regulatory directives

-   Conflict of Interest

-   Neutrality

-   NANPA operations and financial viability

-   Record verification

-   Facilities

-   Security

-   Enterprise Services

### 9.11 Staff Support

The NANPA shall provide the FCC or its designee access during normal
business hours to the NANPA's staff and books, records, and supporting
documentation relating to the NANPA function being audited.

### 9.12 Office Facilities

The NANPA shall provide office space, office furnishings, telephone and
facsimile service, utilities, office-related equipment, and duplicating
services that auditors may require to perform audits.

### 9.13 Audit Results

The NANPA shall make audit results available to the public in a limited
manner that protects any confidential information. The NANC shall
receive a detailed summary of the audit results such that the content
shall not identify any service provider.

If any audit results in the NANPA being notified that it is not in
compliance with any law, regulation, or requirement relating to its
administration, the NANPA shall be required to take actions to correct
any non-compliance.

###  9.14 Compliance

The NANPA shall present a corrective action plan to the NANC within 20
days after the receipt of the auditor's report. The NANPA shall report
monthly, or more frequently if appropriate, on the status of compliance
efforts and notify the NANC upon completion of the corrective action
plan.

In the event that the NANPA does not meet these obligations, all
remedies, including termination, may be utilized to correct the default.

The NANPA shall bear the complete expense of compliance activities that
arise out of the implementation of a corrective action plan.

## 239.2Number range Level2Number range Level3Number range Level4 Monitoring 

### 9.2.1 NANPA Client Feedback Survey

The FCC or its designee shall develop a formal feedback survey to permit
all interested parties to provide performance assessment data and
recommendations to the NANC.

### 9.2.2 NANPA Annual Operational Review Number range Level2Number range Level3Number range Level4 

The NANPA shall undergo an annual operational review to be conducted by
the NANC or its designee in conjunction with the FCC.

The operational review shall consist of a review of appropriate NANPA
operations and facilities to ensure that the NANPA is performing its
functions and responsibilities in accordance with the requirements of
the contract. The NANPA shall ensure that all data provided to the group
conducting the operational review adheres to service provider
confidentially requirements.

The operational review shall at a minimum, contain the following
information:

-   State of the NANPA job aids and employee tools

-   Status of the system

-   Status of security plans and disaster recovery activities

-   Status of NPA relief planning activities

-   Status of NXX assignments

-   Status of NRUF data collection and analysis activities

-   Status of CIC, PCS NPA-NXX, 900 and other resources administered

-   Status of continuing education programs for employees to ensure a
    knowledgeable workforce

###  9.2.3Number range Level2Number range Level3Number range Level4 Performance Problems and Corrective Action

The NANPA shall implement remedial action, at no charge, to correct any
identified performance problems.

The NANPA shall develop a Performance Improvement Plan (PIP) that
addresses each area identified that requires performance improvement
along with a time for completion. The PIP shall be presented to the NANC
for review and acceptance prior to implementation. This presentation
shall be at the NANC meeting following the NANC's acceptance of that
year's performance review report.

The annual assessment process shall not preclude telecommunications
industry participants from identifying performance problems to the NANPA
and the NANC as they occur, and from seeking resolution of such
performance problems in an expeditious manner.

## 9.3Number range Level2Number range Level3Number range Level4 Performance Monitoring

The performance monitoring process shall include, but not be limited to,
an internal, documented performance monitoring mechanism to be developed
and implemented by the NANPA and made available to the NANC and the FCC.

## 9.4 NRUF-Related Measurements

The review of the NANPA's responsibilities with respect to how well it
discharged its duties related to NRUF shall include the following:

-   Identification of all service providers utilizing NANP resources,
    including the maintenance of an up-to-date list of contacts for each
    service provider obtained from the semi-annual NRUF report and any
    subsequently updated contact information.

-   Distribution of notification of NRUF reporting requirements to all
    service providers allocated NANP resources.

-   Timely analysis of data.

-   Review of data to ensure service provider compliance with reporting
    requirements, including frequency and granularity.

-   Timely follow-up with carriers and regulators, as needed to ensure
    compliance.

-   Performance of tests for inconsistencies and anomalies.

-   Accuracy of tests for inconsistencies and anomalies.

-   Accuracy and timeliness of calculation of exhaust projections for
    the NANP and individual NPAs.

-   Timely notification to the NANC and industry of problems and unusual
    activity.

-   Responsiveness to federal and state regulators.

-   Responsiveness to industry.

## 9.5 Self Assessment and Reporting

The NANPA shall provide a self-assessment of its performance. An annual
and quarterly report shall be delivered to the NANC or its designee
within 30 days of the measurement period. The NANPA shall provide the
following information:

-   Summary of areas in which NANPA experienced difficulty and how the
    NANPA corrected the problem (NANPA internal and external
    difficulties included).

-   Incidences of user dissatisfaction and a description of the action
    taken by the NANPA to ensure the problem shall not reoccur.

-   A summary tally of written and oral complaints identified by
    performance metric.

-   A summary list of major issues addressed by the NANPA including an
    evaluation of how the NANPA's activities influenced the outcome and
    how this outcome affected users.

# Section 240Number range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#section-240number-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Section-Heading}

# Contract Data Requirements List (CDRL) {#contract-data-requirements-list-cdrl .Section-Header}

All CDRLs shall be approved by the FCC.

## 240.1Number range Level2Number range Level3Number range Level4 Implementation Plan

The contractor shall provide an Implementation Plan per Section 2.14
within 30 days of contract award and an update to that Plan 30 days
prior to the takeover of NANP Administration.

## 240.2Number range Level2Number range Level3Number range Level4 Security Plan

The contractor shall provide a Security Plan per Section 7.6 within 45
days of contract award and an update to that Plan 30 days prior to the
takeover of NANP Administration. The Security Plan shall be updated
annually 45 days prior to the beginning of each Option Year.

## 240.3Number range Level2Number range Level3Number range Level4 Disaster/Continuity of Operations Plan

The contractor shall provide a Disaster/Continuity of Operations Plan
per Section 7.13 within 60 days of contract award. The Plan shall be
updated annually 30 days prior to the beginning of each Option Year.

## 240.4Number range Level2Number range Level3Number range Level4 NANP Administration System Transfer List

The contractor shall provide the NANP Administration System Transfer
List per Section 7.17 at the time of the new or modified systems
acceptance and the list shall be updated annually.

## 240.5Number range Level2Number range Level3Number range Level4 System Test Plan

The contractor shall provide a System Test Plan within 75 days of
contract award and whenever significant changes or modifications are
made to the system per Section 7.12.

## 240.6Number range Level2Number range Level3Number range Level4 Change Management Plan

The contractor shall provide a Change Management Plan per Section 4.1
within 90 days of contract award.

## 240.7Number range Level2Number range Level3Number range Level4 Contract Change Management Plan

The contractor shall provide a Contract Change Management Plan for
implementing the requirements of Section 2.10 within 90 days after the
start of the first Option Year. The Plan shall be reviewed and updated
annually 60 days prior to the beginning of each Option Year.

## 240.8Number range Level2Number range Level3Number range Level4 Training Plan

The contractor shall provide a Training Plan per Section 4.1 within 105
days of contract award. The Plan shall be reviewed and updated annually
30 days prior to the beginning of each Option Year.

## 240.9Number range Level2Number range Level3Number range Level4 System Maintenance Plan

The contractor shall provide a System Maintenance Plan per Section 7.5
prior to new or modified system acceptance. The Plan shall be reviewed
and updated annually 120 days prior to the beginning of each Option
Year.

## 240.10Number range Level2Number range Level3Number range Level4 System Documentation Plan

The contractor shall provide a System Documentation Plan per Sections
2.15.3 and 7.16 at the time of the new or modified systems acceptance
and the plan shall be updated annually.

## 240.11Number range Level2Number range Level3Number range Level4 Performance Improvement Plan

The contractor shall provide a Performance Improvement Plan per Section
9.2.3 on an annual basis following the NANC's acceptance of each year's
performance review report.

## 240.12Number range Level2Number range Level3Number range Level4 Transition Plan

The contractor shall provide a Transition Plan per Section 2.15.4 180
days prior to contract termination.

## 240.13Number range Level2Number range Level3Number range Level4 System Source Code

The contractor shall provide the system source code, in machine-readable
form, 180 days prior to contract termination.

# Section 11 {#section-11 .Section-Heading}

# Enterprise Services {#enterprise-services .Section-Header}

# Enterprise services are additional services that may be provided, for a specific fee, by the NANPA. These are described as services that the NANPA can provide but are limited to meeting the needs of a limited number of customers.  {#enterprise-services-are-additional-services-that-may-be-provided-for-a-specific-fee-by-the-nanpa.-these-are-described-as-services-that-the-nanpa-can-provide-but-are-limited-to-meeting-the-needs-of-a-limited-number-of-customers. .Back-Matter-Header}

Enterprise services and their associated fees are subject to prior
review by the NANC and approval by the applicable regulatory authorities
before they can be implemented and made available to the requestor(s).

## 11.1 Operating Principles

The following operating principles apply to the provision of enterprise
services:

-   The fees associated with enterprise services shall be fair and
    reasonable.

-   Enterprise service fees for the same service must be the same for
    all customers.

-   Enterprise services must be performed without jeopardizing NANPA
    duties and responsibilities.

-   Proprietary/confidential information provided to the NANPA shall be
    protected in the provision of any enterprise service.

-   Fees associated with an enterprise service shall be collected by the
    NANPA or the designated billing and collection agent, depending on
    the NANC recommendation and FCC approval.

-   Fees for enterprise services are independent of the price of this
    contract.

## 11.2 Required Enterprise Service

The NANPA is required to support the following enterprise services:

-   Provide rating and routing input to BIRRDS upon request from code
    applicants (Administrative Operating Company Number \[AOCN\]
    function). The information is contained in Part 3 of the CO Code
    Administration Guidelines. This includes reviewing the information,
    assisting in the preparation of the information and the actual
    inputting of the information in the associated database.

-   Provide input of paper submissions (*e.g.*, NRUF data, CO Code
    applications), either fax or mailed copies, into the system.

-   Provide testimony in state regulatory hearings. Any costs associated
    with testifying in such regulatory hearings shall be treated as
    enterprise services.

## 11.3 Audit of Enterprise Services

Any and all approved Enterprise Service(s) will be subject to an audit
by an independent auditor.

The NANPA will contract with an auditor to have an audit of all
enterprise service offerings the first, third and fifth year of their
Term of Administration. The audit report will be conducted during the
second quarter of the reporting year and the auditor's report must be
provided to the NANC and all appropriate regulatory agencies in the
third quarter of the reporting year.

# List of References {#list-of-references .Section-Header}

1.  Federal Communications Commission: *In the Matter of Number Resource
    Optimization, Report and Order and Further Notice of Proposed Rule
    Making*, CC Docket 99-200, FCC 00-104 (March 31, 2000). Available
    at:
    http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00104.pdf.

2.  Federal Communications Commission: *In the Matter of Numbering
    Resource Optimization, Second Report and Order, Order on
    Reconsideration in CC Docket No. 96-98 and CC Docket No. 99-200, and
    Second Further Notice of Proposed Rule Making in Docket 99-200,* CC
    Dockets 99-200 and 96-98, FCC 00-429 (December 29, 2000). Available
    at:
    <http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-429A1.pdf>.

3.  Federal Communications Commission: *In the Matter of Administration
    of the North American Numbering Plan*, CC Docket 92-237 (October 9,
    1992). Available at:
    <http://gullfoss2.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&id_document=1075810001>.

4.  Federal Communications Commission: *In the Matter of Use of N11
    Codes and Other Abbreviated Dialing Arrangements,* CC Docket 92-105
    (May 4, 1992). Available at:
    <http://gullfoss2.fcc.gov/prod/ecfs/retrieve.cgi?native_or_pdf=pdf&id_document=1021280001>.

5.  Dorothy Attwood: *Letter from the FCC Chief of the Common Carrier
    Bureau to NANPA,* June 25, 2001.

6.  Industry Numbering Committee: *Industry Numbering Committee (INC)
    Thousands-Block Number (NXX-X) Pooling Administration Guidelines,*
    (ATIS-0300066, (February 11, 2008), by the Industry Numbering
    Committee, a forum of the Carrier Liaison Committee, sponsored by
    the Alliance for Telecommunications Industry Solutions (ATIS).
    Available at: <http://www.atis.org/atis/clc/inc/incdocs.htm>.

7.  NeuStar, Inc: *NeuStar NANPA Central Code Administration System
    (CAS) Requirements Specification*, *Revision 4.3s*, (February 23,
    2000), by NeuStar, Inc, 1120 Vermont Ave. Washington, DC, 20005.

8.  Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *North American Numbering Plan Numbering Resource
    Utilization/Forecast Reporting (NRUF) Guidelines*, ATIS-0300068
    (November 9, 2007), by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

9.  Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Central Office Code (NXX) Assignment Guidelines*, ATIS-0300051
    (January 18, 2008) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

10. North American Numbering Council: *Number Administration Auditor
    Technical Requirements* (July 18, 2000) by the North American
    Numbering Council. Available at:
    http://www.fcc.gov/ccb/Nanc/FinAudReg.rtf.

11. North American Numbering Council: *NANC Audit Framework* (November
    16, 1999) by the North American Numbering Council. Available at:
    http://www.fcc.gov/ccb/Nanc/1116audit.pdf.

12. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Automatic Number Identification (ANI) Information Digit Codes*,
    ATIS-0300064 (September 18, 1998) by the Industry Numbering
    Committee, a forum of the Carrier Liaison Committee, sponsored by
    the Alliance for Telecommunications Industry Solutions (ATIS).
    Available at: <http://www.atis.org/atis/clc/inc/incdocs.htm>.

13. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *900-NXX Code Assignment Guidelines*, ATIS-0300060 (November
    9, 2007) by the Industry Numbering Committee, a forum of the Carrier
    Liaison Committee, sponsored by the Alliance for Telecommunications
    Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

14. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *555 NXX Assignment Guidelines*, ATIS-0300048 (May 13, 2005) by the
    Industry Numbering Committee, a forum of the Carrier Liaison
    Committee, sponsored by the Alliance for Telecommunications Industry
    Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

15. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Personal Communications Services N00-NXX Code Assignment
    Guidelines*, ATIS-0300052 (October 12, 2007) by the Industry
    Numbering Committee, a forum of the Carrier Liaison Committee,
    sponsored by the Alliance for Telecommunications Industry Solutions
    (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

16. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Carrier Identification Code Assignment Guidelines*, ATIS-0300050
    (August 10, 2007) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

17. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *800-855 Number Assignment Guidelines*, ATIS-0300047 (March
    23, 2004) by the Industry Numbering Committee, a forum of the
    Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

18. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Vertical Service Code Assignment Guidelines*, ATIS-0300058
    (February 28, 2000) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

19. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *NPA Allocation Plan and Assignment Guidelines*, ATIS-0300055
    (November 9, 2007) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

20. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *NPA Code Relief Planning and Notification Guidelines*, ATIS-0300061
    (November 9, 2007) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

21. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Location Routing Number Assignment Practices*, ATIS-0300065
    (December 1, 2006) by the Industry Numbering Committee, a forum of
    the Carrier Liaison Committee, sponsored by the Alliance for
    Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

22. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *Uniform Dialing Plan*, ATIS-0300059 (July 1998) by the Industry
    Numbering Committee, a forum of the Carrier Liaison Committee,
    sponsored by the Alliance for Telecommunications Industry Solutions
    (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

23. Industry Numbering Committee: *Industry Numbering Committee (INC)*
    *International Inbound NPA (INT/NPA/NXX) Assignment Guidelines*,
    ATIS-0300049 (March 23, 2004) by the Industry Numbering Committee, a
    forum of the Carrier Liaison Committee, sponsored by the Alliance
    for Telecommunications Industry Solutions (ATIS). Available at:
    <http://www.atis.org/atis/clc/inc/incdocs.htm>.

24. Federal Communications Commission: *FCC Computer Security Program,
    FCCINST 1479.2*. Effective Date, 10/02/2001.

25. IEEE-SA Standards Board: *IEEE Standard for Software Test
    Documentation, IEEE Std 82901998*. Available at
    <http://standards.ieee.org/catalog/olis/index.html>

26. National Fire Protection Association: *NFPA 1600 Standard on
    Disaster/Emergency Management and Business Continuity Programs, 2000
    Ed.* Available at <http://www.nfpa.org/>

27. Space and Naval Warfare Systems Command (SPAWAR): *Software
    Transition Plan (STrP), DI-IPSC-81429.* 10 January 2000. Available
    at <http://www.ihsengineering.com/>

28. IEEE-SA Standards Board: *IEEE Standard for Software User
    Documentation.* December 5, 2001. Available at
    <http://standards.ieee.org/catalog/olis/index.html>.

29. National Institute of Standards and Technology: *Guide for
    Developing Security Plans for Information Technology Systems, NIST
    Special Publication 800-18*. December 1998. Available at
    <http://crsc.nist.gov/publications/nistpubs/800-18/planguide.pdf>.

30. NeuStar, Inc: *NANP and NPA Exhaust Analysis*, (most recent) by
    NeuStar, Inc, 1120 Vermont Ave. Washington, DC, 20005.

31. IEEE-SA Standards Board: *IEEE Recommended Practice for Software
    Design Descriptions*, September 23, 1998. Available at
    <http://standards.ieee.org/catalog/olis/index.html>.

32. Department of Defense, *Computer Operation Manual (COM)-Data Item
    Description (DID)*, MIL-STD-498, December 5, 1994.

# Appendix ANumber range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#appendix-anumber-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Appendix-Header}

# Terms {#terms .Appendix-Header}

**ANI II Digits.** Automatic Number Identification (ANI) II digits are
two-digit pairs sent with the originating telephone number. These digits
identify the type of originating station.

**Table of Assigned** ANI Information Digits Codes

+--------+-------------------------------------------------------------+
| **DI   | **DESCRIPTION**                                             |
| GITS** |                                                             |
+========+=============================================================+
| 00     | Plain Old Telephone Service (POTS) - non-coin service       |
|        | requiring no special treatment                              |
+--------+-------------------------------------------------------------+
| 01     | Multi-party line (more than 2) - ANI cannot be provided on  |
|        | 4 or 8 party lines. The presence of this "01" code shall    |
|        | cause an Operator Number Identification (ONI) function to   |
|        | be performed at the distant location. The ONI feature       |
|        | routes the call to a CAMA operator or to an Operator        |
|        | Services System (OSS) for determination of the calling      |
|        | number.                                                     |
+--------+-------------------------------------------------------------+
| 02     | ANI Failure - the originating switching system indicates    |
|        | (by the "02" code), to the receiving office that the        |
|        | calling station has not been identified. If the receiving   |
|        | switching system routes the call to a CAMA or Operator      |
|        | Services System, the calling number may be verbally         |
|        | obtained and manually recorded. If manual operator          |
|        | identification is not available, the receiving switching    |
|        | system (*e.g.*, an inter-Local Access Transport Area        |
|        | \[LATA\] carrier without operator capabilities) may reject  |
|        | the call.                                                   |
+--------+-------------------------------------------------------------+
| 06     | Station Level Rating - The "06" digit pair is used when the |
|        | customer has subscribed to a class of service in order to   |
|        | be provided with real time billing information. For         |
|        | example, hotel/motels, served by PBXs, receive detailed     |
|        | billing information, including the calling party's room     |
|        | number. When the originating switching system does not      |
|        | receive the detailed billing information, *e.g.*, room      |
|        | number, this "06" code allows the call to be routed to an   |
|        | operator or operator services system to obtain complete     |
|        | billing information. The rating and/or billing information  |
|        | is then provided to the service subscriber. This code is    |
|        | used only when the directory number (DN) is not accompanied |
|        | by an automatic room/account identification.                |
+--------+-------------------------------------------------------------+
| 07     | Special Operator Handling Required - calls generated from   |
|        | stations that require further operator or Operator Services |
|        | System screening are accompanied by the "07" code. The code |
|        | is used to route the call to an operator or Operator        |
|        | Services System for further screening and to determine if   |
|        | the station has a denied-originating class of service or    |
|        | special routing/billing procedures. If the call is          |
|        | unauthorized, the calling party shall be routed to a        |
|        | standard intercept message.                                 |
+--------+-------------------------------------------------------------+
| 10     | Not assignable - conflict with 10X test code                |
+--------+-------------------------------------------------------------+
| 12-19  | Not assignable - conflict with international out pulsing    |
|        | code                                                        |
+--------+-------------------------------------------------------------+
| 20     | Automatic Identified Outward Dialing (AIOD) - without AIOD, |
|        | the billing number for a PBX is the same as the PBX         |
|        | Directory Number (DN). With the AIOD feature, the           |
|        | originating line number within the PBX is provided for      |
|        | charging purposes. If the AIOD number is available when ANI |
|        | is transmitted, code "00" is sent. If not, the PBX DN is    |
|        | sent with ANI code "20". In either case, the AIOD number is |
|        | included in the AMA record.                                 |
+--------+-------------------------------------------------------------+
| 23     | Coin or Non-Coin - on calls using database access, *e.g.*,  |
|        | 800, ANI II 23 is used to indicate that the coin/non-coin   |
|        | status of the originating line cannot be positively         |
|        | distinguished for ANI purposes by the SSP. The ANI II pair  |
|        | 23 is substituted for the II pairs, which would otherwise   |
|        | indicate that the non-coin status is known, i.e., 00, or    |
|        | when there is ANI failure.                                  |
|        |                                                             |
|        | ANI II 23 may be substituted for a valid 2-digit ANI pair   |
|        | on 0-800 calls. In all other cases, ANI II 23 should not be |
|        | substituted for a valid 2-digit ANI II pair which is        |
|        | forward to an SSP from an EAEO.                             |
|        |                                                             |
|        | Some of the situations in which the ANI II 23 may be sent:  |
|        |                                                             |
|        | • Calls from non-conforming end offices (CAMA or LAMA       |
|        | types) with combined coin/non-coin trunk groups.            |
|        |                                                             |
|        | • 0-800 Calls                                               |
|        |                                                             |
|        | • Type 1 Cellular Calls                                     |
|        |                                                             |
|        | • Calls from PBX Trunks                                     |
|        |                                                             |
|        | • Calls from Centrex Tie Lines                              |
+--------+-------------------------------------------------------------+
| 24     | Code 24 identifies a toll free service that has been        |
|        | translated to a Plain Old Telephone Service (POTS) routable |
|        | number via the toll free database that originated for any   |
|        | non-pay station. If the received toll free number is not    |
|        | converted to a POTS number, the database returns the        |
|        | received ANI code along with the received toll free number. |
|        | Thus, this 24 code indicates that this is a toll free       |
|        | service call since that fact can no longer be recognized    |
|        | simply by examining the called address.                     |
+--------+-------------------------------------------------------------+
| 25     | Code 25 identifies a toll free service call that has been   |
|        | translated to a Plain Old Telephone Service (POTS) routable |
|        | number via the toll free database that originated from any  |
|        | pay station, including inmate telephone service.            |
|        | Specifically, ANI II digits 27, 29 and 70 shall be replaced |
|        | with Code 25.                                               |
+--------+-------------------------------------------------------------+
| 27     | Code 27 identifies a line connected to a pay station which  |
|        | uses network provided coin control signaling. II 27 is used |
|        | to identify this type of pay station line irrespective of   |
|        | whether the pay station is provided by a Local Exchange     |
|        | Carrier (LEC) or a non-LEC. II 27 is transmitted from the   |
|        | originating end office on all calls made from these lines.  |
+--------+-------------------------------------------------------------+
| 29     | Code 29 is used to identify lines serving a                 |
|        | confinement/detention facility that are intended for        |
|        | inmate/detainee use and require outward call screening      |
|        | (*e.g.*, 0+ collect only service). As per Sect. 276 (d) of  |
|        | the Telecom Act, inmate telephone service is considered     |
|        | included in the general category of payphone service.       |
|        | Accordingly, lines identified with ANI II 29 include both   |
|        | prison/inmate phones/payphones.                             |
+--------+-------------------------------------------------------------+
| 30-32  | Intercept - where the capability is provided to route       |
|        | intercept calls (either directly or after an announcement   |
|        | recycle) to an access tandem with an associated Talc        |
|        | Operator Services System, the following ANI codes shall be  |
|        | used:                                                       |
+--------+-------------------------------------------------------------+
|        | 30 Intercept (blank) - for calls to unassigned directory    |
|        | number (DN)                                                 |
+--------+-------------------------------------------------------------+
|        | 31 Intercept (trouble) - for calls to directory numbers     |
|        | (DN) that have been manually placed in trouble-busy state   |
|        | by Talc personnel                                           |
+--------+-------------------------------------------------------------+
|        | 32 Intercept (regular) - for calls to recently changed or   |
|        | disconnected numbers                                        |
+--------+-------------------------------------------------------------+
| 34     | Talc Operator Handled Call - after the Talc Operator        |
|        | Services System has handled a call for an IC, it may change |
|        | the standard ANI digits to "34," before out-pulsing the     |
|        | sequence to the IC, when the Telco performs all call        |
|        | handling functions, *e.g.*, billing. The code tells the IC  |
|        | that the BOC has performed billing on the call and the IC   |
|        | only has to complete the call.                              |
+--------+-------------------------------------------------------------+
| 40-49  | Unrestricted Use - locally determined by carrier            |
+--------+-------------------------------------------------------------+
| 52     | Outward Wide Area Telecommunications Service (OUTWATS) -    |
|        | this service allows customers to make calls to a certain    |
|        | zone(s) or band(s) on a direct dialed basis for a flat      |
|        | monthly charge or for a charge based on accumulated usage.  |
|        | OUTWATS lines can dial station-to-station calls directly to |
|        | points within the selected band(s) or zone(s). The LEC      |
|        | performs a screening function to determine the correct      |
|        | charging and routing for OUTWATS calls based on the         |
|        | customer's class of service and the service area of the     |
|        | call party. When these calls are routed to the              |
|        | interexchange carrier via a combined WATS-POTS trunk group, |
|        | it is necessary to identify the WATS calls with the ANI     |
|        | code "52".                                                  |
+--------+-------------------------------------------------------------+
| 60     | Telecommunications Relay Service (TRS) - ANI II digit pair  |
|        | 60 indicates that the associated call is a TRS call         |
|        | delivered to a transport carrier from a TRS Provider and    |
|        | that the call originated from an unrestricted line (*i.e.*, |
|        | a line for which there are no billing restrictions).        |
|        | Accordingly, if no request for alternate billing is made,   |
|        | the call shall be billed to the calling line.               |
+--------+-------------------------------------------------------------+
| 61     | Cellular/Wireless Personal Communications Service (PCS)     |
|        | (Type 1) - The "61" digit pair is to be forwarded to the    |
|        | interexchange carrier by the local exchange carrier for     |
|        | traffic originating from a cellular/wireless PCS carrier    |
|        | over type 1 trunks. (Note: ANI information accompanying     |
|        | digit pair "61" identifies only the originating             |
|        | cellular/wireless PCS system, not the mobile directory      |
|        | placing the call.)                                          |
+--------+-------------------------------------------------------------+
| 62     | Cellular/Wireless PCS (Type 2) - The "62" digit pair is to  |
|        | be forwarded to the interexchange carrier by the            |
|        | cellular/wireless PCS carrier when routing traffic over     |
|        | type 2 trunks through the local exchange carrier access     |
|        | tandem for delivery to the interexchange carrier. (Note:    |
|        | ANI information accompanying digit pair "62" identifies the |
|        | mobile directory number placing the call but does not       |
|        | necessarily identify the true call point of origin.)        |
+--------+-------------------------------------------------------------+
| 63     | Cellular/Wireless PCS (Roaming) - The "63" digit pair is to |
|        | be forwarded to the interexchange carrier by the            |
|        | cellular/wireless PCS subscriber "roaming" in another       |
|        | cellular/wireless PCS network, over type 2 trunks through   |
|        | the local exchange carrier access tandem for delivery to    |
|        | the interexchange carrier. (Note: Use of "63" signifies     |
|        | that the "called number" is used only for network routing   |
|        | and should not be disclosed to the cellular/wireless PCS    |
|        | subscriber. Also, ANI information accompanying digit pair   |
|        | "63" identifies the mobile directory number forwarding the  |
|        | call but does not necessarily identify the true             |
|        | forwarded-call point of origin.)                            |
+--------+-------------------------------------------------------------+
| 66     | TRS - ANI II digit pair 66 indicates that the associated    |
|        | call is a TRS call delivered to a transport carrier from a  |
|        | TRS Provider, and that the call originates from a           |
|        | hotel/motel. The transport carrier can use this indication, |
|        | along with other information (*e.g.*, whether the call was  |
|        | dialed 1+ or 0+) to determine the appropriate billing       |
|        | arrangement (*i.e.*, bill to room or alternate bill).       |
+--------+-------------------------------------------------------------+
| 67     | TRS - ANI II digit pair 67 indicates that the associated    |
|        | call is a TRS call delivered to a transport carrier from a  |
|        | TRS Provider and that the call originated from a restricted |
|        | line. Accordingly, sent paid calls should not be allowed    |
|        | and additional screening, if available, should be performed |
|        | to determine the specific restrictions and type of          |
|        | alternate billing permitted.                                |
+--------+-------------------------------------------------------------+
| 70     | Code 70 identifies a line connected to a pay station        |
|        | (including both coin and coinless stations) which does not  |
|        | use network provided coin control signaling. II 70 is used  |
|        | to identify this type pay station line irrespective of      |
|        | whether the pay station is provided by a LEC or a non-LEC.  |
|        | II 70 is transmitted from the originating end office on all |
|        | calls made from these lines.                                |
+--------+-------------------------------------------------------------+
| 80-89  | Reserved for Future Expansion "to" 3-digit Code             |
+--------+-------------------------------------------------------------+
| 93     | Access for private virtual network types of service: the    |
|        | ANI code "93" indicates, to the IC, that the originating    |
|        | call is a private virtual network type of service call.     |
+--------+-------------------------------------------------------------+
| 95     | Unassigned - conflict with Test Codes 958 and 959           |
+--------+-------------------------------------------------------------+

**AOCN**. Administrative Operating Company Number. Also refers to the
company that updates Traffic Routing Administration (TRA) databases
under contract to a code holder.

**Carrier Identification** **Codes.** A CIC is a 4-digit numeric code
primarily used to uniquely identify an access customer who has purchased
access such as Feature Group B (FGB) and/or Feature Group D (FGD) access
services.  These types of CICs are primarily used for routing from a
local network to the access purchaser and for billing between the local
network and the access purchaser.  In addition, as the result of a 2002
directive to NANPA from the FCC, switchless resellers may also be
assigned CICs without the requirement to first purchase direct FG D
truck access.  Also, pursuant to agreement reached by the Industry
Numbering Committee (INC) in 2006, Billing and Collection Clearinghouses
that provide third-party bill aggregation services on behalf of access
purchasers may also be assigned CICs as identifiers only when the use of
an ABEC (Alternate Billing Entity Code) is not technically feasible.

**Auditor**. Neutral Fourth Party vendor selected to audit the telephone
number administration and assignment functions for the telephony
industry in the United States and all North American Numbering Plan
(NANP) Administrators, including the Pooling administrator.

**Bidder.** The company submitting a bid response to this RFP.

**Billing and Collection Agent.** The designated vendor responsible for
managing NANPA financial arrangements and payments between the industry
and the NANP Administration vendor.

**Code Holder.** The code holder is the Local Exchange Routing Guide
(LERG) assignee of the Numbering Plan Area (NPA)-NXX.

**Contractor.** The winning bidder for NANPA.

**Easily** **Recognizable Codes.** When the second and third digits of
an area code are the same, that code is called an easily recognizable
code (ERC). ERCs designate special services; *e.g.*, 888 for toll-free
service.

**Enterprise Services.** Functions performed by the Administrator that
are outside of the requirements and responsibilities detailed within
this proposal and associated industry guidelines and regulatory orders.

Feature Group B. Provides trunk side access to telephone company end
office switches with an associated uniform 950-XXXX access code for an
InterExchange Carrier's use in originating and terminating
communications.

**Feature Group D.** Provides trunk side access to telephone company end
office switches with an associated 101XXXX access code for an
InterExchange Carrier's use in originating or terminating
communications; no access code is required for calls to an InterExchange
Carrier over Feature Group D switched access service if the end-user's
telephone number is subscribed to that InterExchange Carrier.

**FCC Registration Number (FRN).** The FRN is a unique 10-digit number
that is assigned to an entity that does business with the Federal
Communications Commission.

**Knowledge Base.** A database provided on a Support Web Site programmed
with application-specific, self-help information that is constantly
being improved, added-to, and updated based on information gathered from
use of the Application.

**INC.** The Industry Numbering Committee (INC) is an industry forum
operating under the auspices of the Alliance for Telecommunications
Industry Solutions (ATIS). Their mission is to provide 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 NANP area.

**International Telecommunication Union (ITU) Study Group.** There are
15 ITU study groups that focus on a variety of topics. See:
<http://www.itu.int/ITU-T/studygroups/>

**NCS Pearson.** NCS Pearson is a global provider of applications,
services, and technologies for education, testing, assessment,
government and complex data management. See:
<http://www.ncspearson.com/>

**N11 Codes.** Service codes, commonly called N11 codes because of their
format, are used to provide three-digit dialing access special services.
In the United States, the Federal Communications Commission (FCC)
administers N11 codes, and recognizes only 211, 311, 511, 711, 811 and
911 as nationally assigned.

  ---------- ------------------------------------------------------------
  211        Community Information and Referral Services

  311        Non-emergency Police and Other Governmental Services (U.S.)

  411        Local Directory Assistance

  511        Traffic and Transportation Information (U.S.)

  611        Repair Service

  711        Telecommunications Relay Service (TRS)

  811        Access to One Call Services to Protect Pipeline and
             Utilities from Excavation Damage (US); Non-Urgent Health
             Teletriage Services (Canada)

  911        Emergency
  ---------- ------------------------------------------------------------

**North American Numbering Council (NANC).** The NANC is a Federal
Advisory Committee established pursuant to the United States Federal
Advisory Committee Act, 5 U.S.C., App. 2 (1988) (FACA). The NANC was
established to advise the FCC and other NANP member countries on issues
related to NANP Administration, and to advise the Commission on local
number portability administration issues in the United States. The NANC
also develops policy recommendations on numbering issues, initially
resolves disputes and provides guidance to the Pooling Administrator
(PA) as well as the NANPA.

The NANC's Charter under the FACA provides that, in carrying out its
responsibilities, the NANC shall assure that all NANP administrators
support the following policy objectives:

-   That the NANP facilitates entry into the communications marketplace
    by making numbering resources available on an efficient, timely
    basis to communications service providers;

-   That the NANP does not unduly favor or disfavor any particular
    industry segment or group of consumers;

-   That the NANP does not unduly favor one technology over another;

-   That the NANP gives consumers easy access to the public switched
    telephone network; and

-   That the NANP ensures that the interests of all NANP member
    countries are addressed fairly and efficiently, fostering continued
    integration of the NANP across NANP member countries.

**NANP.** The NANP is the basic numbering scheme for the Public Switched
Telephone Networks (PSTNs) in the following 19 countries (formerly known
as World Zone 1): Anguilla, Antigua & Barbuda, Bahamas, Barbados,
Bermuda, British Virgin Islands, Canada, Cayman Islands, Dominica,
Dominican Republic, Grenada, Jamaica, Montserrat, St. Kitts & Nevis, St.
Lucia, St. Vincent & the Grenadines, Trinidad & Tobago, Turks & Caicos
Islands, and the United States (including Puerto Rico, the U.S. Virgin
Islands, Guam, the Commonwealth of the Northern Mariana Islands and
American Samoa). The format of the NANP is in compliance with ITU
standards as detailed in Recommendation E.164.

**NXX.** The format of an NPA code or a central office code (N=2-9,
X=0-9)

Ported Telephone Numbers. This refers to the ability to maintain a
subscriber's Telephone Number (TN) while changing vendors.

**Rate Area**. Identifies the geographic area used to distinguish rating
and billing boundaries.

**Term of** **Administration.** Shall be the period of time for which
these requirements shall apply. At any time prior to the termination of
the initial or subsequent Term of Administration, the Term of
Administration may be renewed up to five years in length with the
approval of the NANPA vendor and the appropriate regulatory authorities.

**Query.** The ability to request and retrieve data stored in the NANP
Administration System

**Respondent.** The company submitting a bid response to this RFP.

**Subcontractor.** One not in the employment of the contractor, who is
performing designated services and functions contained within this
document.

U.S. Department of State Study Group A. Study Group A advises the State
Department, through the United States Telecommunications Advisory
Committee, on issues related to U.S. policy, standardization,
regulatory, and competitive aspects of the operations and tariffs of
telecommunications services.

**User(s).** The code applicants, code holders, regulatory
organizations, and the general public that shall interface with NANPA on
all the functions and applications contained with this document.

**Vertical Service Codes.** Vertical service codes (Viscous) are
customer-dialed codes that provide customer access to features and
services provided by local exchange carriers, interexchange carriers,
Commercial Mobile Radio Service (CMRS), etc. Services include call
forwarding, automatic callback, customer originated trace, and many
others. The format of a Vertical Service Code (VSC) is \*XX or \*2XX
(touch-tone) and 11XX or 112XX (rotary). For example, call forwarding is
activated by dialing \*72 or 1172.

#  Appendix BNumber range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#appendix-bnumber-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Appendix-Header}

# Interface Contact Information {#interface-contact-information .Appendix-Header}

**Current North American Numbering Plan Administrator (NANPA) Vendor**

**NeuStar**

John C. Manning

NANPA Director

46000 Center Oak Plaza

Sterling, VA 20166

Telephone: 571-434-5770

**Pooling Administrator**

**NeuStar**

Amy Putnam

Director - Thousand Block Pooling Administration

1800 Sutter St., Suite 780

Concord, CA 94520

Phone: 866-neu-pool  (866-638-7665)

# Number Portability Administration Center {#number-portability-administration-center .Heading-Two}

**NeuStar**

46000 Center Oak Plaza

Sterling, VA 20166

Telephone: 1-888 NPAC HELP

**Local Exchange Routing Guide (LERG)**

**Telcordia Technologies**

Traffic Routing Administration

One Telcordia Drive, Room 4A738

Piscataway, NJ 08854-41567

Telephone: 732-699-6700

**Mobile Block Identifier (MBI) Administration**

**Vangent, Inc.**

3833 Greenway Drive

Lawrence, KS 66046

Telephone: 785-331-2323

Linda Link\
MBI Administration Account Management\
Telephone: 952-831-9663

Mitch Kaufman\
MBI Administration Account Management\
Telephone: 703-435-8255

Contact information is included to facilitate responses to this document
by potential bidders and is not intended to endorse the particular
organizations listed.

# Appendix CNumber range Level1Number range Level2Number range Level3Number range Level4Number range FigureNumber range Table {#appendix-cnumber-range-level1number-range-level2number-range-level3number-range-level4number-range-figurenumber-range-table .Appendix-Header}

# Index to the Binder of Decisional Principles {#index-to-the-binder-of-decisional-principles .Appendix-Header}

**A Compilation of Numbering Rules, Orders, and Industry Agreements**

Date of Last Update

November 30, 2007

Table of Contents

###  Page

#### FCC Documents 3

####  CICs 3

####  Local Competition 4

####  N11 Codes 5

####  NRO/State Orders 6

####  Number Resource Optimization 8

####  Local Number Portability 13

####  NANP Administration 13

#### Canadian Numbering Documents 14

#### ATIS Sponsored Committees 14

#### ATIS Sponsored Committee Documents 15

####  INC Documents 15

####  Other ATIS Sponsored Committee Documents 15

#### ITU Numbering Documents 16

#### LNPA Working Documents 16

#### Telecommunications Industry Association (TIA) Documents 16

####  

### FCC Numbering Documents

+-----+-----+----+-------------------------------+------------------+
| **T | **  | *  | **Caption**                   | **Action**       |
| opi | Rel | *A |                               |                  |
| c** | eas | do |                               |                  |
|     | e** | pt |                               |                  |
|     |     | ed |                               |                  |
|     |     | ** |                               |                  |
+=====+=====+====+===============================+==================+
| C   | FCC | 4- | In the Matter of              | Second Report    |
| ICs | 97- | 7- | Administration Of The North   | And Order        |
|     | 125 | 97 | American Numbering Plan       |                  |
|     |     |    | Carrier Identification Codes  |                  |
|     |     |    | (CICs); Petition for          |                  |
|     |     |    | Rulemaking of VarTec          |                  |
|     |     |    | Telecom., Inc.                |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | FCC | 10 | Administration of the North   | Further Notice   |
| ICs | 97- | -0 | American Numbering Plan       | of Proposed      |
|     | 364 | 9- |                               | Rulemaking and   |
|     |     | 97 | Carrier Identification Codes  | Order            |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 7  | In the Matter of              | Order On         |
| ICs | 9   | -1 | Administration of the North   | Reconsideration, |
|     | 7-1 | 8- | American Numbering Plan       | Order On         |
|     | 524 | 97 | Carrier Identification Codes  | Application For  |
|     |     |    | (CICs)                        | Review, And      |
|     |     |    |                               | Second Further   |
|     |     |    |                               | Notice Of        |
|     |     |    |                               | Proposed         |
|     |     |    |                               | Rulemaking       |
+-----+-----+----+-------------------------------+------------------+
| C   | FCC | 10 | In the Matter of              | Order On         |
| ICs | 97- | -2 | Administration of the North   | Reconsideration, |
|     | 386 | 2- | American Numbering Plan,      | Order On         |
|     |     | 97 | Carrier Identification Codes  | Application For  |
|     |     |    | (CICs)                        | Review, And      |
|     |     |    |                               | Second Further   |
|     |     |    |                               | Notice Of        |
|     |     |    |                               | Proposed         |
|     |     |    |                               | Rulemaking       |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 11 | In the Matter of              | Order            |
| ICs | 9   | -2 | Administration of the North   |                  |
|     | 7-2 | 0- | American Numbering Plan       |                  |
|     | 439 | 97 | Carrier Identification Codes  |                  |
|     |     |    | (CICs)                        |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 3- | North American Numbering      | Public Notice    |
| ICs | 98- | 3- | Council Presents Report And   |                  |
|     | 412 | 98 | Recommendations Concerning    |                  |
|     |     |    | Use And Assignment Of Carrier |                  |
|     |     |    | Identification Codes (CICs)   |                  |
|     |     |    | (CC Docket No. 92-237)        |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 5- | In the Matter of              | Declaratory      |
| ICs | 98- | 1- | Administration of the North   | Ruling           |
|     | 828 | 98 | American Numbering Plan       |                  |
|     |     |    | Carrier Identification Codes  |                  |
|     |     |    | (CICs)                        |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | FCC | 7  | In the Matter of              | Third Report and |
| ICs | 00- | -2 | Implementation of the         | Order and Second |
|     | 255 | 1- | Subscriber Carrier Selection  | Order on         |
|     |     | 00 | Changes Provisions of the     | Reconsideration  |
|     |     |    | Telecommunications Act of     |                  |
|     |     |    | 1996, Policies and Rules      |                  |
|     |     |    | Concerning Unauthorized       |                  |
|     |     |    | Changes of Consumers Long     |                  |
|     |     |    | Distance Carriers             |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 6  | Common Carrier Bureau Directs | Public Notice    |
| ICs | 0   | -2 | The NANPA To Make Available   |                  |
|     | 1-1 | 6- | For Assignment Additional     |                  |
|     | 519 | 01 | Feature Group D Carrier       |                  |
|     |     |    | Identification Codes          |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | DA  | 8  | American Telnet Request for   | Order            |
| ICs | 0   | -2 | Declaratory Ruling and Waiver |                  |
|     | 3-2 | 8- |                               |                  |
|     | 765 | 03 |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| C   | N   | 4  | Time Warner Cable Information | Letter           |
| ICs | one | -2 | Services Request for a        |                  |
|     |     | 0- | Carrier Identification Code   |                  |
|     |     | 05 |                               |                  |
+-----+-----+----+-------------------------------+------------------+

  ----------------------------------------------------------------------------------------------
  **Topic**     **Release**   **Adopted**   **Caption**                      **Action**
  ------------- ------------- ------------- -------------------------------- -------------------
  Local         FCC 99-227    4-19-96       In The Matter Of Implementation  Notice Of Proposed
  Competition                               Of The Local Competition         Rulemaking
                                            Provisions In The                
                                            Telecommunications Act Of 1996   

  Local         FCC 99-170    8-1-96        In The Matter Of Implementation  First Report And
  Competition                               Of The Local Competition         Order
                                            Provisions In The                
                                            Telecommunications Act Of 1996;  
                                            Interconnection Between Local    
                                            Exchange Carriers And Commercial 
                                            Mobile Radio Service Providers   

  Local         FCC 96-333    8-8-96        In The Matter Of Implementation  Second Report And
  Competition                               Of The Local Competition         Order And
                                            Provisions Of The                Memorandum Opinion
                                            Telecommunications Act Of 1996;  And Order
                                            Interconnection Between Local    
                                            Exchange Carriers And Commercial 
                                            Mobile Radio Service Providers;  
                                            Area Code Relief Plan For Dallas 
                                            And Houston. Ordered By The      
                                            Public Utility Commission Of     
                                            Texas; Administration Of The     
                                            North American Numbering Plan;   
                                            Proposed 708 Relief Plan And 630 
                                            Numbering Plan Area Code By      
                                            Ameritech-Illinois               

  Local         FCC 99-227    8-23-99       In The Matters Of Implementation Third Report And
  Competition                               Of The Telecommunications Act Of Order In CC Docket
                                            1996: Telecommunications         No. 96-115, Second
                                            Carriers\' Use Of Customer       Order On
                                            Proprietary Network Information  Reconsideration Of
                                            And Other Customer Information;  The Second Report
                                            Implementation Of The Local      And Order In CC
                                            Competition Provisions Of The    Docket No. 96-98,
                                            Telecommunications Act Of 1996;  And Notice Of
                                            Provision Of Directory Listing   Proposed Rulemaking
                                            Information Under The            In 99-273
                                            Telecommunications Act Of 1934,  
                                            As Amended                       

  Local         FCC 99-170    7-12-99       In The Matters Of Implementation First Order On
  Competition                               Of The Local Competition         Reconsideration
                                            Provisions Of The                
                                            Telecommunications Act Of 1996;  
                                            Interconnection Between Local    
                                            Exchange Carriers And Commercial 
                                            Mobile Radio Service Providers;  
                                            Area Code Relief Plan For Dallas 
                                            And Houston, Ordered By The      
                                            Public Utility Commission Of     
                                            Texas; Administration Of The     
                                            North American Numbering Plan;   
                                            Proposed 708 Relief Plan And 630 
                                            Numbering Plan Area Code By      
                                            Ameritech-Illinois               

  Local         FCC 99-243    9-13-99       In The Matters Of Implementation Third Order On
  Competition                               Of The Local Competition         Reconsideration Of
                                            Provisions Of The                Second Report And
                                            Telecommunications Act Of 1996;  Order And
                                            Interconnection Between Local    Memorandum Opinion
                                            Exchange Carriers And Commercial And Order
                                            Mobile Radio Service Providers;  
                                            Area Code Relief Plan For Dallas 
                                            And Houston, Ordered By The      
                                            Public Utility Commission Of     
                                            Texas; Administration Of The     
                                            North American Numbering Plan;   
                                            Proposed 708 Relief Plan And 630 
                                            Numbering Plan Area Code By      
                                            Ameritech-Illinois; Petition For 
                                            Declaratory Ruling Regarding     
                                            Area Code Relief Plan For Area   
                                            Codes 508 And 617, Filed By The  
                                            Massachusetts Department Of      
                                            Public Utilities; New York       
                                            Department Of Public Service     
                                            Petition For Expedited Waiver Of 
                                            47 C.F.R. Section                
                                            52.19(C)(3)(Ii)                  
  ----------------------------------------------------------------------------------------------

  --------------------------------------------------------------------------------------------
  **Topic**   **Release**   **Adopted**   **Caption**                      **Action**
  ----------- ------------- ------------- -------------------------------- -------------------
  N11 Codes   FCC 92-203    5-4-92        In The Matter Of The Use Of N11  Notice Of Proposed
                                          Codes And Other Abbreviated      Rulemaking
                                          Dialing Arrangements             

  N11 Codes   FCC 97-51     2-18-97       In The Matter Of The Use Of N11  First Report And
                                          Codes And Other Abbreviated      Order And Further
                                          Dialing Arrangements             Notice Of Proposed
                                                                           Rulemaking

  N11 Codes   FCC 00-257    7-21-00       In The Matter Of The Use Of N11  Second Report And
                                          Codes And Other Abbreviated      Order
                                          Dialing Arrangements             

  N11 Codes   FCC 00-256    7-21-00       In The Matter Of Petition By The Third Report And
                                          United States Department Of      Order And Order On
                                          Transportation For Assignment Of Reconsideration
                                          An Abbreviated Dialing Code      
                                          (N11) To Access Intelligent      
                                          Transportation System (Its)      
                                          Services Nationwide; Request By  
                                          The Alliance Of Information And  
                                          Referral Systems, United Way Of  
                                          America, United Way 211          
                                          (Atlanta, Georgia), United Way   
                                          Of Connecticut, Florida Alliance 
                                          Of Information And Referral      
                                          Services, Inc., And Texas I&R    
                                          Network For Assignment Of 211    
                                          Dialing Code; The Use Of N11     
                                          Codes And Other Abbreviated      
                                          Dialing Arrangements             

  N11 Codes   FCC 00-327    8-24-00       In The Matter Of Implementation  Fourth Report And
                                          Of 911 Act; The Use Of N11 Codes Order And Third
                                          And Other Abbreviated Dialing    Notice Of Proposed
                                          Arrangements                     Rulemaking CC
                                                                           Docket No. 92-105
                                                                           Notice Of Proposed
                                                                           Rulemaking Wt
                                                                           Docket No. 00-110

  N11 Codes   FCC 01-384    12-21-01      In the matter of Provision of    Notice of Proposed
                                          Directory Listing Information    Rulemaking
                                          Under the Communications Act of  
                                          1934, As Amended; The use of N11 
                                          Codes and Other Abbreviated      
                                          Dialing Arrangements;            
                                          Administration of the North      
                                          American Numbering Plan          

  N11 Codes   FCC 05-59     3-10-05       In the Matter of the Use of N11  Report and Order
                                          Codes and Other Abbreviated      
                                          Dialing Arrangements             
  --------------------------------------------------------------------------------------------

+-----+-----+----+--------------------------------+------------------+
| **T | **  | *  | **Caption**                    | **Action**       |
| opi | Rel | *A |                                |                  |
| c** | eas | do |                                |                  |
|     | e** | pt |                                |                  |
|     |     | ed |                                |                  |
|     |     | ** |                                |                  |
+=====+=====+====+================================+==================+
| NRO | FCC | 9  | In The Matter Of Petition For  | Memorandum       |
| /St | 98- | -1 | Declaratory Ruling And Request | Opinion And      |
| ate | 224 | 1- | For Expedited Action On The    | Order And Order  |
| Ord |     | 98 | July 15, 1997 Order Of The     | On               |
| ers |     |    | Pennsylvania Public Utility    | Reconsideration  |
|     |     |    | Commission Regarding Area      |                  |
|     |     |    | Codes 412, 610, 215, And 717;  | \["Pennsylvania  |
|     |     |    | Implementation Of The Local    | Order"\]         |
|     |     |    | Competition Provisions Of The  |                  |
|     |     |    | Telecommunications Act Of 1996 |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 9  | In The Matter Of California    | Order            |
| /St | 99- | -1 | Public Utilities Commission    |                  |
| ate | 248 | 5- | Petition For Delegation Of     |                  |
| Ord |     | 99 | Additional Authority           |                  |
| ers |     |    | Pertaining To Area Code Relief |                  |
|     |     |    | And NXX Code Conservation      |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 9  | In The Matter Of Florida       | Order            |
| /St | 99- | -1 | Public Service Commission      |                  |
| ate | 249 | 5- | Petition To Federal            |                  |
| Ord |     | 99 | Communications Commission For  |                  |
| ers |     |    | Expedited Decision For Grant   |                  |
|     |     |    | Of Authority To Implement      |                  |
|     |     |    | Number Conservation Measures   |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 9  | In The Matter Of Massachusetts | Order            |
| /St | 99- | -1 | Department Of                  |                  |
| ate | 246 | 5- | Telecommunications And         |                  |
| Ord |     | 99 | Energy\'s Petition For Waiver  |                  |
| ers |     |    | Of Section 52.19 To Implement  |                  |
|     |     |    | Various Area Code Conservation |                  |
|     |     |    | Methods In The 508, 617, 781,  |                  |
|     |     |    | And 978 Area Codes             |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 9  | In The Matter Of New York      | Order            |
| /St | 99- | -1 | State Department Of Public     |                  |
| ate | 247 | 5- | Service Petition For           |                  |
| Ord |     | 99 | Additional Delegated Authority |                  |
| ers |     |    | To Implement Number            |                  |
|     |     |    | Conservation Measures          |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 9  | In The Matter Of Maine Public  | Order            |
| /St | 99- | -2 | Utilities Commission Petition  |                  |
| ate | 260 | 8- | For Additional Delegated       |                  |
| Ord |     | 99 | Authority To Implement Number  |                  |
| ers |     |    | Conservation Measures          |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 11 | In The Matter Of Petition Of   | Order            |
| /St | 9   | -3 | The Ohio Public Utilities      |                  |
| ate | 9-2 | 0- | Commission For Delegation Of   |                  |
| Ord | 635 | 99 | Additional Authority To        |                  |
| ers |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 11 | In The Matter Of Petition Of   | Order            |
| /St | 9   | -3 | The Public Utility Commission  |                  |
| ate | 9-2 | 0- | Of Texas For Expedited         |                  |
| Ord | 636 | 99 | Decision For Authority To      |                  |
| ers |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 11 | In The Matter Of Connecticut   | Order            |
| /St | 9   | -3 | Department Of Public Utility   |                  |
| ate | 9-2 | 0- | Control\'s Petition For        |                  |
| Ord | 633 | 99 | Delegation Of Additional       |                  |
| ers |     |    | Authority To Implement Area    |                  |
|     |     |    | Code Conservation Measures     |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 11 | In The Matter Of Petition Of   | Order            |
| /St | 9   | -3 | The Public Service Commission  |                  |
| ate | 9-2 | 0- | Of Wisconsin For Delegation Of |                  |
| Ord | 637 | 99 | Additional Authority To        |                  |
| ers |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 11 | In The Matter Of New Hampshire | Order            |
| /St | 9   | -3 | Public Utilities Commission\'s |                  |
| ate | 9-2 | 0- | Petition For Additional        |                  |
| Ord | 634 | 99 | Delegated Authority To         |                  |
| ers |     |    | Implement Number Optimization  |                  |
|     |     |    | Measures In The 603 Area Code  |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 8  | In the Matter of Numbering     | Order            |
| /St | 01- | -2 | Resource Optimization,         |                  |
| ate | 201 | 3- | Implementation of the Local    |                  |
| Ord | 3A1 | 01 | Competition Provisions of the  |                  |
| ers |     |    | Telecommunications Act of      |                  |
|     |     |    | 1996, Connecticut Department   |                  |
|     |     |    | of Public Utility Control      |                  |
|     |     |    | Expedited Petition for         |                  |
|     |     |    | Additional Authority, Michigan |                  |
|     |     |    | Public Service Commission      |                  |
|     |     |    | Petition for Additional        |                  |
|     |     |    | Delegated Authority to         |                  |
|     |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures, Petition of the      |                  |
|     |     |    | North Carolina Utilities       |                  |
|     |     |    | Commission for Additional      |                  |
|     |     |    | Delegated Authority to         |                  |
|     |     |    | Implement Number Optimization  |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 5  | In the Matter of the           | Memorandum       |
| /St | 03- | -1 | Connecticut Department of      | Opinion & Order  |
| ate | 114 | 6- | Public Utility Commission for  |                  |
| Ord |     | 03 | Delegated Authority to         |                  |
| ers |     |    | Implement specialized          |                  |
|     |     |    | Transitional Overlay           |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 8- | In the Matter of Petition of   | Order            |
| /St | 03- | 5- | California Public Utilities    |                  |
| ate | 196 | 03 | Commission for Waiver of the   |                  |
| Ord |     |    | federal Communications         |                  |
| ers |     |    | Commission's Contamination     |                  |
|     |     |    | Threshold Rule                 |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | FCC | 2  | In the Matter of               | Order            |
| /St | 06  | -1 |                                |                  |
| ate | -14 | 7- | Numbering Resource             |                  |
| Ord |     | 06 | Optimization                   |                  |
| ers |     |    |                                |                  |
|     |     |    | Petition of the West Virginia  |                  |
|     |     |    | Public Service Commission for  |                  |
|     |     |    | Expedited Decision for         |                  |
|     |     |    | Authority to Implement         |                  |
|     |     |    | Additional Number Conservation |                  |
|     |     |    | Measures                       |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Nebraska       |                  |
|     |     |    | Public Service Commission for  |                  |
|     |     |    | Expedited Decision for         |                  |
|     |     |    | Authority to Implement         |                  |
|     |     |    | Additional Number Conservation |                  |
|     |     |    | Measures                       |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Oklahoma       |                  |
|     |     |    | Corporation Commission for     |                  |
|     |     |    | Expedited Decision for         |                  |
|     |     |    | Authority to Implement         |                  |
|     |     |    | Additional Number Conservation |                  |
|     |     |    | Measures                       |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Michigan       |                  |
|     |     |    | Public Service Commission for  |                  |
|     |     |    | Additional Delegated Authority |                  |
|     |     |    | over Numbering Resource        |                  |
|     |     |    | Conservation Measures          |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Missouri       |                  |
|     |     |    | Public Service Commission for  |                  |
|     |     |    | Additional Delegated Authority |                  |
|     |     |    | to Implement Number            |                  |
|     |     |    | Conservation Measures          |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 1  | In the Matter of               | Order            |
| /St | 0   | 1- |                                |                  |
| ate | 6-2 | 9- | Numbering Resource             |                  |
| Ord | 299 | 06 | Optimization                   |                  |
| ers |     |    |                                |                  |
|     |     |    | Petition for Delegated         |                  |
|     |     |    | Authority by the Public        |                  |
|     |     |    | Utilities Commission of Ohio   |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the New York State |                  |
|     |     |    | Department of Public Service   |                  |
|     |     |    | for Mandatory Pooling          |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Washington     |                  |
|     |     |    | Utilities and Transportation   |                  |
|     |     |    | Commission for Mandatory       |                  |
|     |     |    | Number Pooling                 |                  |
|     |     |    |                                |                  |
|     |     |    | The New Mexico Public          |                  |
|     |     |    | Regulation commissions'        |                  |
|     |     |    | Petition for Delegated         |                  |
|     |     |    | Authority to Implement         |                  |
|     |     |    | Additional Number Conservation |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 5  | In the Matter of Numbering     | Order            |
| /St | 0   | -3 | Resource Optimization          |                  |
| ate | 7-2 | 1- | Implementation of the Local    |                  |
| Ord | 280 | 07 | Competition Provisions of the  |                  |
| ers |     |    | Telecommunications Act of 1996 |                  |
|     |     |    |                                |                  |
|     |     |    | Petition of the Kentucky       |                  |
|     |     |    | Public Service Commission for  |                  |
|     |     |    | Additional Delegated Authority |                  |
|     |     |    | to Implement Number            |                  |
|     |     |    | Conservation Measures          |                  |
+-----+-----+----+--------------------------------+------------------+
| NRO | DA  | 8  | In the Matter of Numbering     | Order            |
| /St | 0   | -2 | Resource Optimization          |                  |
| ate | 7-3 | 4- | Implementation of the Local    |                  |
| Ord | 728 | 07 | Competition Provisions of the  |                  |
| ers |     |    | Telecommunications Act of 1996 |                  |
|     |     |    | Petition of the Idaho Public   |                  |
|     |     |    | Utilities Commission for       |                  |
|     |     |    | Delegated Authority to         |                  |
|     |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures Petition of the       |                  |
|     |     |    | Alabama Public Service         |                  |
|     |     |    | Commission for Delegated       |                  |
|     |     |    | Authority to Implement Number  |                  |
|     |     |    | Conservation Measures Petition |                  |
|     |     |    | of the Public Service          |                  |
|     |     |    | Commission of Wisconsin for    |                  |
|     |     |    | Further Delegated Authority to |                  |
|     |     |    | Implement Number Conservation  |                  |
|     |     |    | Measures                       |                  |
+-----+-----+----+--------------------------------+------------------+

  -----------------------------------------------------------------------------------------------
  **Topic**      **Release**   **Adopted**   **Caption**                      **Action**
  -------------- ------------- ------------- -------------------------------- -------------------
  Number         DA 98-2265    11-6-98       Common Carrier Bureau Seeks      Public Notice
  Resource                                   Comment On North American        
  Optimization                               Numbering Council Report         
                                             Concerning Telephone Number      
                                             Pooling And Other Optimization   
                                             Measures                         

  Number         FCC 99-122    5-27-99       In The Matter Of Numbering       Notice Of Proposed
  Resource                                   Resource Optimization;           Rulemaking
  Optimization                               Connecticut Department Of Public 
                                             Utility Control Petition For     
                                             Rulemaking To Amend The          
                                             Commission\'s Rule Prohibiting   
                                             Technology-Specific Or           
                                             Service-Specific Area Code       
                                             Overlays; Massachusetts          
                                             Department Of Telecommunications 
                                             And Energy Petition For Waiver   
                                             To Implement A                   
                                             Technology-Specific Overlay In   
                                             The 508, 617, 781, And 978 Area  
                                             Codes; California Public         
                                             Utilities Commission And The     
                                             People Of The State Of           
                                             California Petition For Waiver   
                                             To Implement A                   
                                             Technology-Specific Or           
                                             Service-Specific Area Code       

  Number         FCC 00-104    3-17-00       In The Matter Of Numbering       Report And Order
  Resource                                   Resource Optimization            And Further Notice
  Optimization                                                                Of Proposed Rule
                                                                              Making
  -----------------------------------------------------------------------------------------------

+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 7  | Common Carrier Bureau         | Public Notice    |
| ber | 0   | -1 | Responses To Questions In The |                  |
| Re  | 0-1 | 1- | Numbering Resource            |                  |
| sou | 549 | 00 | Optimization Proceeding       |                  |
| rce |     |    |                               |                  |
| Opt |     |    |                               |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 7  | In The Matter Of Numbering    | Order            |
| ber | 0   | -2 | Resource Optimization;        |                  |
| Re  | 0-1 | 0- | Implementation Of The Local   |                  |
| sou | 616 | 00 | Competition Provisions Of The |                  |
| rce |     |    | Telecommunications Act Of     |                  |
| Opt |     |    | 1996; Petition Of The Arizona |                  |
| imi |     |    | Corporation Commission For    |                  |
| zat |     |    | Delegated Authority To        |                  |
| ion |     |    | Implement Number Conservation |                  |
|     |     |    | Measures; Petition Of The     |                  |
|     |     |    | Colorado Public Utilities     |                  |
|     |     |    | Commission For Additional     |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Resource     |                  |
|     |     |    | Optimization Measures;        |                  |
|     |     |    | Petition Of The Georgia       |                  |
|     |     |    | Public Service Commission For |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Indiana Regulatory Commission |                  |
|     |     |    | Petition For Additional       |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures; Iowa Utilities      |                  |
|     |     |    | Board Petition For Delegation |                  |
|     |     |    | Of Additional Authority And   |                  |
|     |     |    | Request For Limited Waiver;   |                  |
|     |     |    | Public Service Commission Of  |                  |
|     |     |    | Kentucky\'s Petition For      |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Missouri Public Service       |                  |
|     |     |    | Commission Petition For       |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures In The  |                  |
|     |     |    | 314, 417, 573, 636, 660 And   |                  |
|     |     |    | 816 Area Codes; Nebraska      |                  |
|     |     |    | Public Service Commission     |                  |
|     |     |    | Petition For Delegation Of    |                  |
|     |     |    | Additional Authority To       |                  |
|     |     |    | Implement Area Code           |                  |
|     |     |    | Conservation Methods In The   |                  |
|     |     |    | 402 Area Code; North Carolina |                  |
|     |     |    | Utilities Commission Petition |                  |
|     |     |    | For Additional Delegated      |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Optimization Measures;        |                  |
|     |     |    | Petition Of The Oregon Public |                  |
|     |     |    | Utility Commission For        |                  |
|     |     |    | Expedited Decision For        |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Petition Of The Pennsylvania  |                  |
|     |     |    | Public Utility Commission For |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures; Petition Of The     |                  |
|     |     |    | Tennessee Regulatory          |                  |
|     |     |    | Authority For Additional      |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Numbering           |                  |
|     |     |    | Conservation Methods;         |                  |
|     |     |    | Petition Of The Utah Public   |                  |
|     |     |    | Service Commission For        |                  |
|     |     |    | Accelerated Grant Of          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Petition Of The Virginia      |                  |
|     |     |    | State Corporation Commission  |                  |
|     |     |    | For Expedited Decision On     |                  |
|     |     |    | Delegation Of Authority To    |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures; Washington          |                  |
|     |     |    | Utilities And Transportation  |                  |
|     |     |    | Commission\'s Amended         |                  |
|     |     |    | Petition For Additional       |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures                      |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 7  | In The Matter Of Numbering    | Order            |
| ber | 00- | -3 | Resource Optimization         |                  |
| Re  | 280 | 1- |                               |                  |
| sou |     | 00 |                               |                  |
| rce |     |    |                               |                  |
| Opt |     |    |                               |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 1  | In The Matter Of Numbering    | Second Report    |
| ber | 00- | 2- | Resource Optimization;        | And Order, Order |
| Re  | 429 | 7- | Petition For Declaratory      | On               |
| sou |     | 00 | Ruling And Request For        | Reconsideration  |
| rce |     |    | Expedited Action On The July  | In CC Docket No. |
| Opt |     |    | 15, 1997 Order Of The         | 96-98 And CC     |
| imi |     |    | Pennsylvania Public Utility   | Docket No.       |
| zat |     |    | Commission Regarding Area     | 99-200, And      |
| ion |     |    | Codes 412, 610, 215, And 717  | Second Further   |
|     |     |    |                               | Notice Of        |
|     |     |    |                               | Proposed         |
|     |     |    |                               | Rulemaking In CC |
|     |     |    |                               | Docket No.       |
|     |     |    |                               | 99-200           |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 2  | In The Matter Of Numbering    | Order            |
| ber | 01- | -1 | Resource Optimization;        |                  |
| Re  | 386 | 3- | Implementation Of The Local   |                  |
| sou |     | 01 | Competition Provisions Of The |                  |
| rce |     |    | Telecommunications Act Of     |                  |
| Opt |     |    | 1996; Petition Of The         |                  |
| imi |     |    | Louisiana Public Service      |                  |
| zat |     |    | Commission For Expedited      |                  |
| ion |     |    | Decision For Additional       |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Numbering           |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Petition Of The Maryland      |                  |
|     |     |    | Public Service Commission For |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Massachusetts Department Of   |                  |
|     |     |    | Telecommunications And Energy |                  |
|     |     |    | Petition For Delegation Of    |                  |
|     |     |    | Additional Authority To       |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures In Massachusetts;    |                  |
|     |     |    | New Jersey Board Of Public    |                  |
|     |     |    | Utilities Petition For        |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures                      |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | \[  | 3  | FCC Releases Numbering        | News             |
| ber | Non | -1 | Resource Utilization Report;  |                  |
| Re  | e\] | 3- | Report Shows That Number      |                  |
| sou |     | 01 | Optimization Measures Adopted |                  |
| rce |     |    | By The FCC Are Improving      |                  |
| Opt |     |    | Phone Number Usage Efficiency |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 3  | In The Matter Of Numbering    | Order            |
| ber | 01- | -1 | Resource Optimization;        |                  |
| Re  | 656 | 3- | Implementation Of The Local   |                  |
| sou |     | 01 | Competition Provisions Of The |                  |
| rce |     |    | Telecommunications Act Of     |                  |
| Opt |     |    | 1996; Indiana Utility         |                  |
| imi |     |    | Regulatory Commission\'s      |                  |
| zat |     |    | Petition For Additional       |                  |
| ion |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Optimization |                  |
|     |     |    | Measures; Indiana Utility     |                  |
|     |     |    | Regulatory Commission\'s      |                  |
|     |     |    | Request For Expedited Ruling  |                  |
|     |     |    | And Second Supplement To      |                  |
|     |     |    | Petition For Additional       |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures; Minnesota Public    |                  |
|     |     |    | Utilities Commission Petition |                  |
|     |     |    | For Additional Delegated      |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Missouri Public Service       |                  |
|     |     |    | Commission\'s Petition For    |                  |
|     |     |    | Delegation Of Authority To    |                  |
|     |     |    | Implement Number Pooling In   |                  |
|     |     |    | The 816 Area Code; Petition   |                  |
|     |     |    | Of The Oklahoma Corporation   |                  |
|     |     |    | Commission For Expedited      |                  |
|     |     |    | Decision For Delegation Of    |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Petition Of The Tennessee     |                  |
|     |     |    | Regulatory Authority For      |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Vermont Public Service        |                  |
|     |     |    | Board\'s Petition For         |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority To Implement Number |                  |
|     |     |    | Conservation Measures;        |                  |
|     |     |    | Petition Of The Public        |                  |
|     |     |    | Service Commission Of West    |                  |
|     |     |    | Virginia For Additional       |                  |
|     |     |    | Delegated Authority To        |                  |
|     |     |    | Implement Number Conservation |                  |
|     |     |    | Measures                      |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 8  | In The Matter Of Numbering    | Order            |
| ber | 00- | -3 | Resource Optimization         |                  |
| Re  | 333 | 1- |                               |                  |
| sou |     | 01 |                               |                  |
| rce |     |    |                               |                  |
| Opt |     |    |                               |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 12 | In the Matter of              | Third Report and |
| ber | 01- | -1 |                               | Order and Second |
| Re  | 362 | 2- | Numbering Resource            | Order on         |
| sou |     | 01 | Optimization                  | Reconsideration  |
| rce |     |    |                               |                  |
| Opt |     |    | Implementation of the Local   |                  |
| imi |     |    | Competition Provisions of the |                  |
| zat |     |    | Telecommunications Act of     |                  |
| ion |     |    | 1996                          |                  |
|     |     |    |                               |                  |
|     |     |    | Telephone Number Portability  |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 12 | In the Matter of Numbering    | Order            |
| ber | 0   | -3 | Resource Optimization         |                  |
| Re  | 1-3 | 1- |                               |                  |
| sou | 025 | 01 | Implementation of the Local   |                  |
| rce |     |    | Competition Provisions of the |                  |
| Opt |     |    | Telecommunications Act of     |                  |
| imi |     |    | 1996                          |                  |
| zat |     |    |                               |                  |
| ion |     |    | Petition of Representative    |                  |
|     |     |    | Keith R. McCall and Members   |                  |
|     |     |    | of the Northeast Delegation   |                  |
|     |     |    | of the Pennsylvania House of  |                  |
|     |     |    | Representatives Requesting    |                  |
|     |     |    | that Additional Authority be  |                  |
|     |     |    | Delegated to the Pennsylvania |                  |
|     |     |    | Public Utility Commission to  |                  |
|     |     |    | Implement Additional Number   |                  |
|     |     |    | Conservation Measures         |                  |
|     |     |    |                               |                  |
|     |     |    | Petition of the Louisiana     |                  |
|     |     |    | Public Service Commission for |                  |
|     |     |    | Expedited Decision for        |                  |
|     |     |    | Additional Delegated          |                  |
|     |     |    | Authority to Implement Number |                  |
|     |     |    | conservation Measures         |                  |
|     |     |    | regarding 318                 |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 3  | In the Matter of Numbering    | Third Order on   |
| ber | 02  | -1 | Resource Optimization         | Reconsideration  |
| Re  | -73 | 3- |                               | in CC Docket No. |
| sou |     | 02 | Implementation of the Local   | 99-200, Third    |
| rce |     |    | Competition Provisions of the | Further Notice   |
| Opt |     |    | Telecommunications Act of     | of Proposed      |
| imi |     |    | 1996                          | Rulemaking in CC |
| zat |     |    |                               | Docket 99-200,   |
| ion |     |    | Telephone Number Portability  | and Second       |
|     |     |    |                               | Further Notice   |
|     |     |    |                               | of Proposed      |
|     |     |    |                               | Rulemaking in CC |
|     |     |    |                               | Docket No.       |
|     |     |    |                               | 95-116           |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 4  | In the Matter of Numbering    | Order            |
| ber | 02- | -2 | Resource Optimization         |                  |
| Re  | 948 | 4- |                               |                  |
| sou |     | 02 |                               |                  |
| rce |     |    |                               |                  |
| Opt |     |    |                               |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+

+-----+-----+----+-------------------------------+------------------+
| Num | FCC |    | In the Matter of Petition of  | Memorandum       |
| ber | 03- |    | the Connecticut Department of | Opinion and      |
| Re  | 114 |    | Public Utility Control for    | Order            |
| sou |     |    | Delegated Authority to        |                  |
| rce |     |    | Implement Specialized         |                  |
| Opt |     |    | Transitional Overlays         |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 5  | In the Matter of              | Fourth Report    |
| ber | 03- | -2 |                               | and Order in CC  |
| Re  | 126 | 8- | Numbering Resource            | Docket No.       |
| sou |     | 03 | Optimization                  | 99-200 and CC    |
| rce |     |    |                               | Docket No.       |
| Opt |     |    | Implementation of the Local   | 95-116, and      |
| imi |     |    | Competition Provisions of the | Fourth Further   |
| zat |     |    | Telecommunications Act of     | Notice of        |
| ion |     |    | 1996                          | Proposed         |
|     |     |    |                               | Rulemaking in CC |
|     |     |    | Telephone Number Portability  | Docket No.       |
|     |     |    |                               | 99-200           |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 6  | In the Matter of Numbering    | Memorandum       |
| ber | 03- | -1 | Resource Optimization         | Opinion and      |
| Re  | 140 | 9- |                               | Order            |
| sou |     | 03 | Petition for Forbearance from |                  |
| rce |     |    | Further Increases in the      |                  |
| Opt |     |    | Numbering Utilization         |                  |
| imi |     |    | Threshold                     |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 8- | In the Matter of Numbering    | Order            |
| ber | 03- | 5- | Resource Optimization         |                  |
| Re  | 196 | 03 | Petition of the California    |                  |
| sou |     |    | Public Utilities commission   |                  |
| rce |     |    | for Waiver of the Federal     |                  |
| Opt |     |    | Communications Commission's   |                  |
| imi |     |    | Contamination Threshold Rule  |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 1  | In the Matter of              | Order            |
| ber | 05  | -2 | Administration of the North   |                  |
| Re  | -20 | 8- | American Numbering Plan       |                  |
| sou |     | 05 |                               |                  |
| rce |     |    |                               |                  |
| Opt |     |    |                               |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | DA  | 8  | In the Matter of Petition of  | Order            |
| ber | 0   | -2 | the California Public         |                  |
| Re  | 5-2 | 4- | Utilities Commission for      |                  |
| sou | 439 | 05 | Delegated Authority to        |                  |
| rce |     |    | Implement Specialized         |                  |
| Opt |     |    | Transitional Overlays         |                  |
| imi |     |    |                               |                  |
| zat |     |    |                               |                  |
| ion |     |    |                               |                  |
+-----+-----+----+-------------------------------+------------------+
| Num | FCC | 10 | In the Matters of             | Report and       |
| ber | 07- | -3 |                               | Order,           |
| Re  | 188 | 1- | Telephone Number Requirements | Declaratory      |
| sou |     | 07 | for IP-Enabled Services       | Ruling, Order on |
| rce |     |    | Providers                     | Remand           |
| Opt |     |    |                               |                  |
| imi |     |    | Local Number Portability      |                  |
| zat |     |    | Porting Interval and          |                  |
| ion |     |    | Validation Requirements       |                  |
|     |     |    |                               |                  |
|     |     |    | IP-Enabled Services           |                  |
|     |     |    |                               |                  |
|     |     |    | Telephone Number Portability  |                  |
|     |     |    |                               |                  |
|     |     |    | CTIA Petitions for            |                  |
|     |     |    | Declaratory Ruling on         |                  |
|     |     |    | Wireline-Wireless Porting     |                  |
|     |     |    | Issues                        |                  |
|     |     |    |                               |                  |
|     |     |    | Final Regulatory Flexibility  |                  |
|     |     |    | Analysis                      |                  |
|     |     |    |                               |                  |
|     |     |    | Numbering Resource            |                  |
|     |     |    | Optimization                  |                  |
+-----+-----+----+-------------------------------+------------------+

  -----------------------------------------------------------------------------------------------
  **Topic**     **Release**   **Adopted**   **Caption**                       **Action**
  ------------- ------------- ------------- --------------------------------- -------------------
  Local Number  FCC 96-286    7-2-96        In The Matter Of Telephone Number First Report and
  Portability                               Portability                       Order and Further
                                                                              Notice of Proposed
                                                                              Rulemaking

  Local Number  FCC 97-74     3-6-97        In The Matter Of Telephone Number First Memorandum
  Portability                               Portability                       Opinion and Order
                                                                              on Reconsideration

  Local Number  FCC 97-289    8-14-97       In The Matter Of Telephone Number Second Report and
  Portability                               Portability                       Order
  -----------------------------------------------------------------------------------------------

+-----+-----+----+--------------------------------+------------------+
| **T | **  | *  | **Caption**                    | **Action**       |
| opi | Rel | *A |                                |                  |
| c** | eas | do |                                |                  |
|     | e** | pt |                                |                  |
|     |     | ed |                                |                  |
|     |     | ** |                                |                  |
+=====+=====+====+================================+==================+
| N   | FCC | >  | In the Matter of Proposed 708  | Declaratory      |
| ANP | 95- |  1 | Relief Plan and 630 Numbering  | Ruling and Order |
| Ad  | 019 | -1 | Plan Area Code by Ameritech -- |                  |
| min |     | 2- | Illinois                       |                  |
| ist |     | 95 |                                |                  |
| rat |     |    |                                |                  |
| ion |     |    |                                |                  |
+-----+-----+----+--------------------------------+------------------+
| N   | FCC | >  | In The Matter Of The           | Report and Order |
| ANP | 95- |  7 | Administration of the North    |                  |
| Ad  | 283 | -1 | American Numbering Plan        |                  |
| min |     | 3- |                                |                  |
| ist |     | 95 |                                |                  |
| rat |     |    |                                |                  |
| ion |     |    |                                |                  |
+-----+-----+----+--------------------------------+------------------+
| N   | FCC | >  | In The Matter Of The           | Third Report and |
| ANP | 97- |  1 | Administration of the North    | Order            |
| Ad  | 372 | 0- | American Numbering Plan / Toll |                  |
| min |     | 9- | Free Service Access Codes      |                  |
| ist |     | 97 |                                |                  |
| rat |     |    |                                |                  |
| ion |     |    |                                |                  |
+-----+-----+----+--------------------------------+------------------+
| N   | DA  | >  | Re: Petition of the            | Letter           |
| ANP | 0   |  5 | Connecticut Department of      |                  |
| Ad  | 1-1 | -1 | Public Utility Control for     |                  |
| min | 210 | 4- | Authority to Conduct a         |                  |
| ist |     | 01 | Voluntary Unassigned Number    |                  |
| rat |     |    | Porting Trial                  |                  |
| ion |     |    |                                |                  |
+-----+-----+----+--------------------------------+------------------+
| N   | DA  | >  | In The Matter Of The           | Order            |
| ANP | 0   |  6 | Administration of the North    |                  |
| Ad  | 4-1 | -1 | American Numbering Plan        |                  |
| min | 721 | 6- |                                |                  |
| ist |     | 04 |                                |                  |
| rat |     |    |                                |                  |
| ion |     |    |                                |                  |
+-----+-----+----+--------------------------------+------------------+

[Canadian Numbering Documents:]{.underline}

In Canada, telecommunications is governed by the Telecommunications Act.
The Canadian Radio-television & Telecommunications Commission (CRTC)
regulates all telecommunications in Canada under this Act. The CRTC has
established the CRTC Industry Steering Committee (CISC) to address
telecommunications issues in Canada. The Canadian Steering Committee on
Numbering (CSCN) is a subtending committee of the CISC. The role of the
CSCN is to establish numbering administration guidelines that apply in
Canada.

The major numbering administration guidelines that apply in Canada
include but are not limited to:

Canadian Central Office Code (NXX) Assignment Guidelines

Canadian NPA Relief Planning Guidelines

Canadian Adjunct to INC NPA Allocation Plan and Assignment Guidelines

Canadian Numbering Resource Utilization Forecast (C-NRUF) Guidelines

Canadian Adjunct to INC Carrier Identification Code (CIC) Assignment
Guidelines

Canadian Adjunct to INC International Inbound NPA (INT/NPA/NXX)
Assignment Guidelines

Canadian Adjunct to INC Personal Communications Services N00 NXX
Assignment Guidelines

CSCN approved 800-855 Number Assignment Guidelines

CSCN approved 555 NXX Assignment Guidelines

CSCN approved 900 NXX Assignment Guidelines

CSCN Guideline for Vertical Service Codes

Canadian MIN Block Identifier (MBI) Assignment Guidelines

Emergency Service Routing Digit (ESRD) Block Assignment Guidelines

Canadian International Mobile Station Identity Assignment Guidelines

Canadian System Identifiers (SID) Assignment Guidelines

The current versions of the numbering administration guidelines
applicable in Canada may be obtained from the Canadian Numbering
Administrator website at: [www.cnac.ca](http://www.cnac.ca/).

The Canadian Numbering Administrator contact is;

Glenn Pilley\
Director - Canadian Numbering Administrator\
SAIC Canada\
1516-60 Queen Street Ottawa, Ontario\
Canada K1P 5Y7\
Phone 613-563-7242\
Fax 613-563- 9293\
Email: pilleyg@saiccanada.com

There are various Decisions and Orders that affect numbering
administration in Canada. These Decisions and Orders may be obtained
form the CRTC website at: www.crtc.gc.ca.

**[ATIS Sponsored Committees]{.underline}**

  -----------------------------------------------------------------------
  Administration Council for Terminal Attachments (ACTA)

  Bar Code/Standard Coding Committee (BCSC)

  Emergency Services Interconnection Forum (ESIF)

  Information and Data Security Committee (IDSC)

  International Forum for ANSI-41 Standards Technology (IFAST)

  IPTV Interoperability (IIF)

  Industry Numbering Committee (INC)

  Inter-network Interoperability Test Coordination (IITC) Committee

  IMSI Oversight Council (IOC)

  Interactive Voice Response (IVR) Forum

  Network Integration, Operations and Administration Forum (NIOAF)

  Network Interconnection Interoperability Forum (NIIF)

  Network Interface, Power and Protection Committee (NIPP)

  Network Reliability Steering Committee (NRSC)

  Committee O5 - Wood Poles

  Ordering and Billing Forum (OBF)

  Optical Transport and Synchronization Committee (OPTXS)

  Packet Technologies and Systems Committee (PTSC)

  Performance, Reliability and Quality of Service Committee (PRQC)

  Protection Engineers Group (PEG)

  Telecommunications Fraud Prevention Committee (TFPC)

  Telecom Management and Operations Committee (TMOC)

  Text Telephone (TTY) Forum

  Wireless Technologies and Systems Committee (WTSC)
  -----------------------------------------------------------------------

**[ATIS Sponsored Committee Documents - INC Documents]{.underline}**

The latest copies of these documents may be downloaded from the ATIS
website at http://www.atis.org/inc/docs.asp.

  ------------------ ----------------------------------------------------
  ***Doc Number***   ***Title***

  ATIS-0300047       800-855 Number Assignment Guidelines

  ATIS-0300048       555 NXX Assignment Guidelines, and Forms

  ATIS-0300049       International Inbound NPA (INT/NPA/NXX) Assignment
                     Guidelines

  ATIS-0300050       Carrier Identification Code Assignment Guidelines

  ATIS-0300051       Central Office Code (NXX) Assignment Guidelines,
                     with Appendices and Forms

  ATIS-0300052       Personal Communication Services N00NXX Code
                     Assignment Guidelines

  ATIS-0300053       INC Report on PCS N00 Portability

  ATIS-0300054       Procedures for Change in E.164 Country Code
                     Assignments

  ATIS-0300055       NPA Allocation Plan & Assignment Guidelines

  ATIS-0300056       INC Report on Number Portability

  ATIS-0300057       Toll Free Resource Exhaust Relief Planning
                     Guidelines

  ATIS-0300058       Vertical Service Code Assignment Guideline

  ATIS-0300059       Uniform Dialing Plan

  ATIS-0300060       900 NXX Assignment Guidelines

  ATIS-0300061       NPA Code Relief Planning and Notification Guidelines

  ATIS-0300062       500/900 Report on LEC Number Portability

  ATIS-0300063       Initial Report to the NANC on Number Pooling
                     (Version 2)

  ATIS-0300064       ANI Information Digit Codes

  ATIS-0300065       Location Routing Number Assignment Practices

  ATIS-0300066       Thousands-Block Number (NXX-X) Pooling
                     Administration Guidelines

  ATIS-0300067       Interim NANP Expansion Report

  ATIS-0300068       North American Numbering Plan Resource
                     Utilization/Forecast Reporting

  ATIS-0300069       INC Report on Unassigned Number Porting (UNP)

  ATIS-0300070       Guidelines for the Administration of Telephone
                     Numbers

  ATIS-0300071       Industry Numbering Committee (INC) Recommended Plan
                     for Expanding the Capacity of the North American
                     Numbering Plan

  ATIS-0300072       D Digit Report

  ATIS-0300076       Numbering and Dialing Plan for the United States

  ATIS-0300089       p-ANI Administration Guidelines
  ------------------ ----------------------------------------------------

**For all other ATIS Sponsored Committee Documents**, please contact
ATIS at http://www.atis.org/doccenter.shtml.

ITU Numbering Documents:

Copies of these documents can be obtained by purchasing them from the
ITU.

The details can be obtained by accessing the ITU web site at
www.itu.int.

  -----------------------------------------------------------------------
  E.164 - The International Public Telecommunication Numbering Plan

  E.164.1- Criteria and Procedures for the Reservation, Assignment, and
  Reclamation of E.164 Country Codes and Associated Identification Codes
  (ICs)

  E.169 Application of Recommendation E.164 Numbering Plan for Universal
  International Freephone Numbers for International Freephone Service

  E.168 Application of E.164 Numbering Plan for UPT

  E.190 Principles and Responsibilities for the Management and Assignment
  of E Series International Numbering Resources

  E.191 B-ISDN Numbering and Addressing
  -----------------------------------------------------------------------

LNPA Working Documents Applicable to NANC

All documents are available on the Web at the LNPA website: www.npac.com

Telecommunications Industry Association (TIA) Documents:

Standards documents can be found listed at
[http://global.ihs.com](http://global.ihs.com/) and
[http://www.tiaonline.org](http://www.tiaonline.org/).

### 

[^1]: The Business Integrated Routing and Rating Database System,
    BIRRDS, is a Telcordia system that the industry uses to provide
    input access to the LERG. The LERG is the Local Exchange Routing
    Guide that contains the rating and routing information for assigned
    CO Codes.

[^2]: User represents code applicants, code holders, regulatory
    agencies, and the general public.

[^3]: U.S. telecommunications providers only.