Study guide

8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

NENA Emergency Number Professional ENP

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the NENA ENP Exam

2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture

1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1

3 Chapter 2: Modern Location Technologies & MLTS

2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act

4 Chapter 3: NG911 i3 Core Network & Security

3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow

5 Chapter 4: NG911 Location Services & Call Routing

4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements

6 Chapter 5: Public Safety Radio, Broadband & FirstNet

5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services

7 Chapter 6: Call Processing, Accessibility & Protocol Systems

6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment

8 Chapter 7: Computer Aided Dispatch & Information Systems

7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents

9 Chapter 8: GIS for Next Generation 9-1-1

8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

10 Chapter 9: Cybersecurity & CJIS Compliance

9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning

11 Chapter 10: Telecommunications Policy, Funding & Civil Rights

10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws

12 Chapter 11: PSAP Governance, Strategy & Facility Design

11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning

13 Chapter 12: Power Redundancy, COOP & Disaster Recovery

12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases

14 Chapter 13: Emergency Incident Management & NIMS/ICS

13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS

15 Chapter 14: Procurement, Contracts & Financial Management

14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management

16 Chapter 15: Staffing Models, Scheduling & Wellness

15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD

17 Chapter 16: Training, CTO Coaching & Quality Assurance

16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service

18 Chapter 17: Employee Relations, Labor Standards & Legal Protections

17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act

19 Chapter 18: Records Governance, Liability & Public Relations

18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach

20 Chapter 19: Recruiting, Hiring, Compensation & Retention

19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning

8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

Key Takeaways Explain This Topic AI

In legacy E9-1-1, service providers send Service Order Input (SOI) files to the 9-1-1 database management system provider (DBMSP), which validates addresses against the MSAG and updates ALI and selective routing records keyed by telephone number.

A service provider's Street Address Guide (SAG) supports order entry and can help build an initial MSAG, but actual customer records should not be used to create the MSAG, which must reflect the jurisdiction's authoritative addresses.

Number portability, tracked through the Number Portability Administration Center (NPAC), requires coordinated ALI record updates between the old and new providers; a missed update leaves wrong or missing ALI.

Other 9-1-1 data sources include NG9-1-1 databases (LVF/ECRF data, LIS, ADR, National Forest Guide, PCA), NIEM-based exchanges, and third-party supplemental databases whose advisory data must be verified.

The E9-1-1 database may be telco-hosted, self-maintained at the PSAP, stand-alone at the PSAP via telco extracts, or individually provided, and relational database interfaces move data between ALI, CAD, and other systems.

Last updated: September 2026

8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

Quick Answer: Legacy E9-1-1 depends on a chain of databases. Service providers send Service Order Input (SOI) files to the 9-1-1 database management system provider (DBMSP) , which validates each address against the MSAG , builds ALI records , and updates selective routing (SRDB) records that map each telephone number (TN) to an ESN. Providers use their own Street Address Guide (SAG) at order entry. Number portability , tracked in the Number Portability Administration Center (NPAC) , moves numbers between carriers and requires coordinated ALI updates. NG9-1-1 shifts much of this work to GIS-based validation and routing, LIS location, and Additional Data Repositories , while NIEM exchanges and third-party databases add context. The E9-1-1 database can be telco-hosted , self-maintained at the PSAP , stand-alone at the PSAP , or individually provided .

1. Types of 9-1-1 Databases

Database What It Holds Who Maintains It

Service Order Input (SOI) A file of completed service order updates (adds, changes, deletes) sent to the DBMSP Each telephone service provider

Street Address Guide (SAG) The service provider's internal list of valid street addresses used when taking service orders The service provider

MSAG, ESN, and ESZ Valid street names and address ranges by community, tied to Emergency Service Numbers that define Emergency Service Zones (1.2) The 9-1-1 authority's addressing and database staff, with the DBMSP

ALI records Each TN's customer name, service address, class of service, ESN, and agency information The DBMSP, from SOI data

Selective Routing System (SRS/SRDB) records The TN-to-ESN relationships the selective router uses to pick a PSAP The DBMSP and 9-1-1 system service provider

TN records Telephone number records, including shell records for pseudo-ANIs used by wireless and VoIP calls The DBMSP, from provider data

GIS Road centerlines, address points, and boundaries (8.1-8.3) The 9-1-1 authority and local GIS stewards

NG9-1-1 databases LVF and ECRF data, LIS location, ADR and IS-ADR Additional Data, logs, and policy (4.4) 9-1-1 authorities, NGCS providers, and originating networks

Third-party databases Supplemental device location, telematics, medical profiles, premise and hazard information, alarm data Commercial clearinghouses, alarm companies, and other providers

NIEM A common data model for exchanging information across justice, public safety, and emergency management systems (7.2) Standards community; used by agencies and vendors

NPAC The authoritative database of which service provider serves each ported telephone number The number portability administrator under FCC oversight

National Forest Guide The top-level directory of which ECRFs serve which areas, enabling routing between ESInets Coordinated nationally for NG9-1-1

PSAP Credentialing Agency (PCA) The root of the public safety PKI used to authenticate NG9-1-1 entities (9.1) NENA-coordinated PKI

The Street Address Guide and the MSAG

NENA's data standards for service providers and 9-1-1 jurisdictions (NENA-STA-059, the successor to NENA 02-011) describe how the DBMSP and each service provider supply their SAG at E9-1-1 conversion to help build an initial MSAG. The same standard warns that actual telephone customer records should not be used to create the MSAG , because the MSAG must reflect the jurisdiction's authoritative addresses. Customer records may help build a preliminary SAG, but TN records are not loaded until the jurisdiction approves the final MSAG.

  • 2. The Legacy Database Update Flow [Customer Order] -> [Service Provider Order System (checks SAG)]
  • |
  • v
  • [SOI File to DBMSP]
  • |

MSAG validation passes?

  • / \
  • YES NO
  • | |
  • [Build/Update ALI + SRDB Records] [Fallout/Error Report to Provider]
  • | |
  • [ALI Nodes & Selective Router] [Provider Corrects and Resubmits]
  • |
  • [PSAP ALI Display on 9-1-1 Calls] -> [PSAP ALI Discrepancy Report if wrong]

Fallout (error) records are service orders that fail MSAG validation. The provider must correct them, or the customer has no valid ALI record.

ALI discrepancy reports come from telecommunicators who see wrong information on a live call. The 9-1-1 database coordinator routes them to the responsible provider or addressing authority.

Timeliness matters: A new line or a move is not safe for 9-1-1 until its ALI and routing records are current.

3. Number Portability and 9-1-1

Local number portability lets customers keep their telephone number when changing carriers (wireline portability arrived in the late 1990s, and wireless portability in November 2003). The NPAC records the current provider for each ported number, and carriers query it to route calls.

For 9-1-1, porting requires two coordinated database actions: the old provider releases its ALI record for the number, and the new provider claims the record and updates it with its own information (NENA data standards define service order function codes for these steps). When either step fails, the PSAP may see the old carrier's data, stale address information, or "record not found."

  • 4. Relational Databases, Interfacing, and Data Streams
  • Relational Database Basics

Tables store records in rows and fields in columns (for example, a TN table, an MSAG table, and an agency table).

A primary key uniquely identifies each row (such as the TN), and a foreign key links tables (such as the ESN linking a TN record to agencies).

Queries (typically in SQL) join tables to answer questions, such as which agencies respond to a given telephone number.

Referential integrity rules prevent orphaned records, such as a TN assigned to an ESN that does not exist.

Interfacing and Data Streams

ALI to CAD: The call handling equipment passes ANI/ALI data to CAD over a serial or IP data stream (often called an ALI "spill"), so incidents start with location already filled in.

CAD to other systems: CAD exchanges data with records management, mobile data, NCIC and state systems, and other CADs through defined interfaces and web services (7.2).

Data quality and security: Interfaces need validation, error handling, audit trails, and access controls, including CJIS requirements when criminal justice information is involved (9.2).

5. Where the E9-1-1 Database Resides

Model Description Advantages Considerations

Telco-hosted The 9-1-1 system service provider or DBMSP hosts ALI and routing databases, and PSAPs query them remotely Carrier manages updates, redundancy, and provider data flows Less direct control; relies on data circuits and provider responsiveness

Self-maintained at the PSAP The 9-1-1 authority maintains its own MSAG and ALI database, often with vendor software Direct control and faster local corrections Requires skilled staff, security, backups, and provider data feeds

Stand-alone at the PSAP via telco A local ALI database at the PSAP is loaded from telco extracts and updates Local query speed and a fallback if remote links fail Keeping the local copy synchronized with the master

Individually provided or maintained A database provided and maintained for a specific system or customer, such as an enterprise PS-ALI arrangement Tailored to a campus or private system Must still meet NENA data formats and stay synchronized with 9-1-1 records

6. ESZ, ESN, and MSAG Development and Maintenance

Initial creation: Build ESZ boundaries with responding agencies, assign ESNs, and create MSAG ranges from authoritative addressing, using provider SAGs as a starting point.

Finalization: The jurisdiction reviews and approves the MSAG before TN records load.

Error correction: Work fallout and discrepancy reports promptly, fixing whichever source (MSAG or provider record) is wrong.

Maintenance: Update ranges and ESNs as addresses, annexations, and response areas change.

MSAG/GIS/ALI synchronization: Reconcile the three data sets; NENA 71-501 recommends at least a 98% match before relying on GIS (8.3).

NG9-1-1 database management: Shift to GIS data stewardship, Spatial Interface provisioning, and discrepancy reporting as NG9-1-1 replaces tabular routing.

7. Operational Traps & ENP Exam Watch

SOI vs. SAG vs. MSAG: SOI is the provider's service order update file, the SAG is the provider's internal address guide, and the MSAG is the jurisdiction's authoritative 9-1-1 address guide.

Do Not Build the MSAG From Customer Records: Customer records can contain errors that would become "valid" if used to create the MSAG.

Porting Needs Two Actions: The old provider must release the record and the new provider must claim it; a break in either step causes bad ALI.

Third-Party Data Is Advisory: Supplemental databases add context but do not replace authoritative ALI or NG9-1-1 location.

Location of the Database Drives Resilience: Telco-hosted, self-maintained, and stand-alone models fail in different ways, so COOP plans must match the model (Chapter 12).