The Importance of ESInet Interconnectivity Cannot Be Overstated
Posted on March 13, 2025 by Sherri Griffith Powell
Next Generation 911 (NG911) system implementation is progressing across the United States, though at a much slower pace than was envisioned when this game-changing technology first was contemplated a couple of decades ago. There are several reasons for the slower-than-anticipated pace, with a lack of adequate funding chief among them.
Two essential elements of an NG911 system are the emergency services Internet Protocol network (ESInet) and next-generation core services (NGCS). The former enables the delivery of emergency calls to 911 centers in the NG911 environment, while the latter consists of the functional elements that route those calls to the appropriate 911 center. Two other essential elements are call-handling equipment and geographic information systems. All must comply with the National Emergency Number Association (NENA) i3 standards.
Think of an ESInet as a giant pipe through which a tremendous amount of data can flow bidirectionally. When 911 authorities contemplate deploying NG911 service, their first thought typically centers on implementing an ESInet — this is intuitive because without one there is no NG911 service. And ESInets are being implemented statewide, regionally, and locally. However, very few 911 authorities are contemplating ESInet interconnection — and they should be, because the full potential of NG911 systems will be realized only when ESInets are seamlessly connected to enable robust data sharing and multijurisdictional collaboration.
At its core, ESInet interconnectivity enhances emergency response by enabling seamless transfer of voice, data, and multimedia between 911 authorities. This connectivity is crucial for several reasons:
- Interconnected ESInets enable real-time sharing of geographic information system (GIS) data, caller information, and other critical data points, improving situational awareness and decision-making for emergency responders.
- Natural disasters, such as hurricanes, wildfires, and winter storms, frequently disrupt emergency communications. Interconnected ESInets provide an essential backup mechanism, allowing unaffected jurisdictions to assist those in crisis.
- Emergencies often cross city, county, and state lines. Properly interconnected ESInets ensure that calls and data reach the correct agencies without delay, reducing response times and increasing efficiency.
- ESInet interconnectivity could enable broader access to shared surveillance footage, license-plate-recognition systems, and other critical tools that aid criminal investigations and foster crime prevention.
Despite its clear benefits, ESInet interconnectivity remains an underdeveloped aspect of NG911 implementation due to several key challenges:
- NENA’s i3 standards govern NG911. While the standards provide guidelines for ESInet interoperability, they are open to interpretation, which means that vendors often implement their solutions differently. This leads to technical inconsistencies that can make interconnection more complex.
- Establishing interconnectivity requires funding for both infrastructure and ongoing maintenance. Additionally, determining financial responsibility among multiple 911 authorities can be complex.
- Many, if not most, 911 authorities operate with limited IT staff, making it difficult to manage and troubleshoot interconnectivity issues without external support.
- Intergovernmental agreements must be in place to identify how data is shared, which agencies maintain oversight, and how disputes are resolved.
- Many 911 authorities have invested significant resources in NG911 implementation and are not yet ready for another major project.
Despite NG911 implementations being a heavy lift for many 911 authorities, they need to plan for ESInet interconnectivity if they haven’t already. The first step is to initiate discussions with neighboring jurisdictions and state agencies to explore how ESInets can be linked for mutual benefit. Entities experienced in NG911 deployments like MCP can provide valuable guidance. (We have helped guide numerous NG911 system implementations, including statewide systems in Arizona, Minnesota and Tennessee.)
Whether it’s facilitating discussions between vendors, establishing governance frameworks, or troubleshooting integration challenges, we can help make ESInet interconnectivity a reality. So, please reach out.