Key Takeaways:
- NG911 deployment models take three forms: statewide ESInets, regional coalitions, and single PSAPs. A state can run one ESInet across every PSAP. A group of counties can pool procurement into a regional ESInet. Or an individual ECC can contract on its own. The model is often set by state 911 law and who holds the authority to levy, collect, and spend 911 fees.
- The NENA i3 standard is the shared architecture that lets statewide, regional, and local NG911 deployments work as one system. It defines every functional element of NG911, including how a call originates, how it routes, and how PSAPs transfer calls and share capacity across jurisdictions. How long a deployment lasts depends on how closely it holds to i3 at the boundary.
- Cross-ESInet interoperability depends on the i3 Forest Guide, the functional element that routes a 911 call when one ESInet can’t resolve the destination from its own data. The national Forest Guide is not yet operational, so inter-ESInet routing currently relies on bilateral coordination between adjacent providers. This makes “tested transfer success rate” the question that carries weight in procurement.

