NG911 Operational Continuity: Enabled by Technology, Driven by Governance

Emergency Communication Centers have always treated resiliency and continuity of operations as core mission requirements. Historically, these needs were met through reciprocal agreements, backup centers, and regional coordination. These approaches delivered value, but they were limited by technology, uneven vendor participation, and governance structures that were not designed for today’s interconnected environment.

During a session I recently moderated at the IJIS Institute Community Forum, leaders from Fairfax County (VA), Metro Nashville (TN), and Charleston County (SC) shared how they are addressing these challenges in real operational settings. Their work represents some of the first cross‑state, cross‑vendor NG911 continuity arrangements in the country. The discussion offered a clear view of what practical, scalable resiliency can look like.

1. Why Traditional Models Fell Short

Earlier continuity models were constrained by technology. Agencies could redirect voice calls, but the associated data did not follow. Location information, telematics, medical data, and alarm feeds remained local, leaving remote call‑takers without the context needed to act quickly.

Panelists also noted that governance was a barrier. Leadership was often reluctant to send 911 calls across state lines. Outages in the National Capital Region in 2012 and the Nashville bombing in 2020 demonstrated the limits of local‑only redundancy and created the conditions for change.

2. What Has Changed

Current NG911 capabilities are aligning more closely with the operational needs of ECCs. IP‑based routing, NG911 platforms, cloud services, and over‑the‑top data solutions now allow ECCs to support each other across states and vendor environments. Agencies can route calls to distant partners, preserve data, and maintain operational continuity even when local systems are disrupted.

Operational pressures have also increased. High call volumes, multi‑vendor ecosystems, staffing constraints, and the dominant use of cellular networks during major events have made regional and cross‑state support more important. Agencies are recognizing that resiliency requires partners who are not affected by the same outage footprint and who can absorb similar call volumes.

A related part of this work involves geospatial information. Modern NG911 environments rely on GIS based location data and mapping layers, and remote partners must be able to view caller location and incident context in a consistent manner when calls are routed across jurisdictions. Several of the data sources referenced during the session, including telematics, medical information, and other over the top data feeds, depend on GIS to display information accurately. As these partnerships expand, common mapping environments and synchronized geospatial layers will become increasingly important for operational clarity.

3. Governance as an Enabler

Governance has shifted from a constraint to an enabler. Agencies are using straightforward intergovernmental agreements rather than complex statewide emergency management compacts. Legal teams are aligning quickly. Leaders are framing the work as life safety rather than bureaucracy.

Trust is being built through transparency, shared disaster experience, and joint operational planning. Agencies are respecting each other’s domains and creating decision processes that work during disruption.

4. Case Studies: What Is Working

Charleston County (SC) and Collier County (FL)

This partnership is fully operational. Both agencies have successfully routed live 911 calls to each other without call transfer. They share the associated caller and incident data needed for remote call taking, supported by common situational awareness tools and coordinated communication channels. The model protects both sides by distributing call load and maintaining clear operational boundaries.

Fairfax County (VA) and Metro Nashville (TN)

This partnership is newer but progressing quickly. The agencies have tested call routing and are now mapping shared data paths, training workflows, and return‑call procedures. The geographic separation and similar call volumes make the partnership operationally realistic. Both agencies are planning joint training and technical exchanges.

National Capital Region (DC, Maryland, Virginia)

The NCR continues to demonstrate multi‑jurisdictional resiliency through CAD‑to‑CAD integration, shared governance structures, and coordinated outage response. The region provides a mature model for cross‑platform and cross‑agency operations.

5. Lessons Learned

Several themes emerged across all three examples.

• Keep the model simple. Disaster operations require clarity and minimal complexity.

• Respect differences in size, protocols, and technology.

• Test regularly. Annual or semi‑annual testing builds confidence and reveals issues early.

• Focus on data. Voice alone is not sufficient for modern 911 operations.

• Build governance that protects both sides and allows for growth.

• Choose partners who can absorb similar call volumes and who are not affected by the same outage footprint.

6. What This Signals for the Future

These early partnerships may represent the first practical blueprint for scalable NG911 resiliency. They show that cross‑state, cross‑vendor continuity is achievable with today’s technology and governance models. They also show that agencies can build trust and operational playbooks that work during catastrophic outages.

The next steps will involve deeper data integration, streamlined workflows for telecommunicators, and broader regional participation. Vendors will play an important role in supporting neutral, interoperable platforms that allow agencies to share information without being limited by proprietary boundaries.

The work is still evolving, but the direction is clear. Resiliency is no longer a local concept. It is regional, multi‑state, and multi‑vendor. These early models show what is possible and what the future may require.