Moving to NG911: What the Transition Really Means for Your 911 System
Resources
5 minute read
The 911 system has done something remarkably difficult for decades. They’ve connected a person experiencing an emergency to the right Public Safety Answering Point (PSAP) quickly and reliably, with first responders arriving on scene as soon as possible.
However, the 911 system created in the 1960s and the technology used to handle emergency response was designed for a landline infrastructure. And as we all know, the way people communicate today has changed dramatically. Landlines are almost obsolete. We carry smartphones and text. We share precise location information. Vehicles and connected devices can generate emergency data. It is glaringly clear that we communicate mainly over Internet Protocol (IP) networks rather than traditional infrastructure.
That’s why public safety agencies across the country are moving to NG911, or Next Generation 911.
Moving to NG911 is much more than replacing old technology with new technology. The suite of Next Generation Core Services actually changes how emergency calls and data travel, how location is determined, how calls are routed, and how different parts of the public safety system work together. First responders arrive sooner, preventing emergencies from worsening and providing life saving support much quicker.
Traditional 911 systems were largely designed around voice calls and telephone numbers. NG911 is designed around secure, standards-based IP networks capable of supporting voice, text, data, images, video, and other forms of emergency information.
At a high level, the NG911 environment brings together several critical components:
An ESInet alone does not make a system NG911. It is the combination of network, core services, GIS, security, operational procedures, and interconnected systems that creates the larger NG911 environment.
Think of moving to NG911 as a system transformation, not simply a network upgrade.
One of the most significant changes in NG911 involves location and location accuracy.
In legacy 911 environments, call routing has traditionally depended heavily on telephone-related databases and predetermined routing information. NG911 introduces a much more location-centric approach.
Key datasets can include:
For GIS professionals, that represents a meaningful shift.
The GIS database is no longer just a useful mapping resource sitting alongside the 911 system. Its accuracy, completeness, topology, synchronization, and ongoing maintenance can directly affect NG911 operations.
Consider something as ordinary as a street address. To a person, an address may look perfectly correct, but NG911 systems need location information to be consistently understood and validated across multiple datasets and systems.
Problems can arise from seemingly small discrepancies, including:
This is why moving to NG911 requires close collaboration between 911 and GIS professionals. The question is no longer, “Does this address appear correctly on the map?” It becomes, “Can this location be consistently validated and routed within the NG911 environment?”
Public safety rarely operates within neat geographic boundaries, and NG911 is designed to improve the ability of systems and agencies to exchange emergency communications and associated data. A wireless caller may be near a jurisdictional border. An emergency may require assistance from neighboring agencies. A PSAP may need to transfer a call and its associated information to another center.
But interoperability does not happen simply because everyone is using IP technology.
For NG911 to work across organizational and geographic boundaries:
In other words, some of the most important work involved in moving to NG911 happens outside the equipment room. It happens through coordination.
It can be tempting to imagine NG911 migration as a clean before-and-after event.
Legacy system today. NG911 tomorrow.
Real-world transitions are rarely that simple.
Agencies may need to operate Legacy and Next Generation 911 components simultaneously. Different counties, regions, states, carriers, and technology providers may also be at different stages of migration.
A strong transition plan should look across the entire environment:
Network readiness: How will the agency connect to the ESInet? What redundancy, resiliency, monitoring, and security requirements need to be addressed?
NG911 Core Services: Which NGCS functions will be provided, and how will they interact with other systems in the 911 environment?
GIS readiness: Are required datasets complete, accurate, and maintained appropriately? Do boundaries and data align with neighboring jurisdictions?
Cybersecurity: How will interconnected IP-based infrastructure change the agency’s security requirements and risk profile?
Operational readiness: What changes will telecommunicators, supervisors, GIS teams, technical staff, and administrators need to understand?
Governance: Who owns and maintains the data? Who approves changes? How are issues resolved when multiple agencies, jurisdictions, or vendors are involved?
These questions may be less visible than the technology itself, but they often determine whether the transition works smoothly.
One of the easiest mistakes in an NG911 project is waiting too long to address GIS.
Because location data is so deeply connected to NG911 functionality, GIS readiness should be evaluated early. That can mean examining:
That final point matters. A one-time GIS cleanup may help prepare for migration, but NG911 requires something more sustainable. Roads change. New subdivisions are built. Addresses are created. Boundaries are adjusted.
The goal is not simply getting GIS data ready for NG911. It is keeping it ready.
With all the standards, systems, acronyms, and technical requirements involved, organizations considering moving to NG911 may wonder where to begin.
A practical first step is surprisingly simple: understand your current environment.
Document what exists today, including your:
From there, identify the gaps between today’s environment and the NG911 environment you are working toward.
That gap analysis turns NG911 from an abstract initiative into a more manageable roadmap.
NG911 introduces a great deal of new technology, but technology is not the end goal. The goal is to help public safety professionals receive and use better information when someone needs help.
Better location information can help identify where an emergency is happening. More flexible routing can help communications reach the appropriate destination. Additional emergency data can provide telecommunicators and responders with greater context.
Those capabilities depend on a foundation that is carefully planned, standards-based, interoperable, secure, and supported by accurate geographic data.
That’s why moving to NG911 deserves to be approached as more than an infrastructure project. It is a transformation of the 911 ecosystem.
At Synergem Technologies, we help public safety organizations navigate the technical and operational complexities of NG911, from network and systems planning to GIS readiness and implementation. The objective is not simply to move to the next generation of 911 technology. It is to build an NG911 environment that is resilient, interoperable, maintainable, and ready to serve the communities that depend on it.