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:
Despite its clear benefits, ESInet interconnectivity remains an underdeveloped aspect of NG911 implementation due to several key challenges:
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.