Statewide NG911: Building Resilience From the Core to the Local Connection
ESInets and Next Generation Core Services are central to statewide 911 modernization. The connections supporting each participating location deserve the same attention.
Statewide Next Generation 911 projects bring together networks, software, location data and emergency communications centers to modernize how requests for help are delivered and handled.
That investment also raises a practical question: How will each participating location stay connected when its normal network paths are disrupted?
For state 911 authorities, local agencies and implementation partners, connectivity resilience needs to be part of the design from the beginning.
What Are the ESInet and Next Generation Core Services?
Two central components of NG911 are the Emergency Services IP Network (ESInet) and Next Generation Core Services (NGCS). They perform different, complementary roles.
Emergency Services IP Network
The ESInet provides managed IP transport connecting participating emergency communications centers and NG911 services. Its design must address availability, security, performance and connectivity between participating locations.
Next Generation Core Services
NGCS provides the software functions and databases that support emergency call routing and delivery, including functions that use location information to identify the appropriate destination.
Call-handling equipment and geographic information systems are additional parts of the overall NG911 environment. Each component must work with the others to support the complete service.
NG911 is designed to accommodate voice and additional forms of information while improving the ability to transfer calls and manage disruptions across centers. Available capabilities depend on the implementation and participating systems.
Background: National 911 Program: NG911 for Telecommunicators and Next Generation 911 overview .
A Statewide Design Still Depends on Local Connections
A statewide project must account for conditions at every participating location—from large urban communications centers to rural facilities with limited carrier options.
Redundant circuits deserve a closer look. Two connections may use different providers while sharing a building entrance, conduit, upstream facility or local power dependency. A single incident could affect both.
Planning should examine the complete path between each facility and the services it needs:
- Physical separation between access routes
- Shared infrastructure and power dependencies
- Options during an area-wide terrestrial outage
- Connectivity at alternate operating locations
- Capacity for essential applications
- Monitoring and support responsibilities
The objective is to understand which failures the design can tolerate and where additional diversity would provide practical value.
Add Connectivity Diversity Around the Statewide Architecture
IP Access International can support the connectivity portion of statewide NG911 initiatives through managed cellular and satellite services for fixed facilities, alternate operating locations and deployable communications systems.
This work complements the roles of the state 911 authority, ESInet operator, NGCS provider and system integrator. Any proposed connection carrying NG911 traffic must be designed, approved and tested within the project’s architecture.
Add Paths Beyond Terrestrial Circuits
Satellite connectivity can provide an additional access path that avoids local terrestrial cable routes. Cellular service can add further options where coverage and capacity support the application.
Each technology addresses different conditions. Satellite needs suitable antenna placement, power and sky visibility. Cellular availability depends on local coverage, capacity and network conditions. Site planning should identify both the diversity gained and the dependencies that remain.
Support Real-Time Blending
Through SuperGIG™, IP Access can combine multiple cellular carriers with satellite connectivity using real-time blending.
In a properly engineered deployment, this approach can help maintain connectivity as individual links change in quality or availability. Suitability for an ESInet access application depends on the operator’s requirements, including approved transport, security, routing, latency, jitter, packet loss and service levels.
An available broadband connection becomes useful to an NG911 project when the required systems can operate over it successfully and the responsible providers have approved its use.
Prepare Alternate and Temporary Operating Locations
Continuity planning also needs to address where personnel will work if their primary facility becomes unavailable.
IP Access can provide connectivity options for backup centers, temporary facilities and mobile command environments. Depending on the approved design, those connections may support agency applications, coordination tools and authorized access to operational systems.
Moving 911 call-taking to an alternate location requires additional planning for call-handling equipment, security, staffing and ESInet/NGCS integration. Connectivity supports that plan; the full operating environment must be validated together.
Keep Additional Connections Ready Between Incidents
IP Access supports its managed connectivity services through a 24/7/365 U.S.-based Network Operations Center. BlueVIEW™ provides visibility into supported device status and service usage, helping agencies manage their connectivity resources.
For statewide deployments, support responsibilities should be defined across providers so teams know who monitors each service, who responds to an issue and how escalation moves between organizations.
Test the Applications and the Outage Scenarios
A successful demonstration should establish more than whether a terminal can reach the internet.
The state authority and its implementation partners should define acceptance criteria for each proposed use. Testing should reflect the applications, operating conditions and disruptions the connection is intended to support.
- Application performance under expected load
- Latency, jitter and packet loss
- Security and authorized network access
- Transitions between available network paths
- Operation with reduced network capacity
- Power continuity and restoration procedures
For connections intended to carry NG911 traffic, validation must include the ESInet operator and relevant system providers. For supporting applications, testing should reflect the workloads staff will need during a disruption.
Statewide NG911 modernization creates an opportunity to examine resilience at every participating facility. IP Access can help agencies and project partners evaluate where managed cellular, satellite and blended connectivity fit within that broader design.
NG911 Connectivity FAQ
What is the difference between an ESInet and NGCS?
The ESInet provides managed IP network transport. Next Generation Core Services provides software functions and databases supporting emergency call routing and delivery. Both are components of the broader NG911 environment.
Can satellite provide an additional connection for a 911 center?
Satellite can provide another broadband access path for approved applications. Carrying NG911 traffic requires coordination with the ESInet operator, state authority and relevant system providers, followed by design review and testing.
Does adding satellite make a facility NG911-ready?
Satellite supplies connectivity. NG911 readiness also depends on core services, call-handling systems, location data, security, integration and operational procedures. Those elements must be evaluated together.
Where does IP Access fit in a statewide NG911 project?
IP Access can support managed cellular, satellite and blended connectivity for participating facilities, alternate locations and deployable systems. The scope and approved uses are established with the agency and its implementation partners.
How Will Your Locations Stay Connected?
Talk with IP Access about managed cellular, satellite and blended connectivity options that support your statewide NG911 project and continuity requirements.