Use cases · 13 min read

Video wall for crisis management rooms and EOCs: activation-driven walls, multi-agency coordination, and where software fits

Last updated: 2026-05-29

Crisis management rooms — municipal, regional, and national Emergency Operations Centres (EOCs), corporate Incident Response (IR) rooms, public safety consolidated dispatch, healthcare mass-casualty coordination, cyber incident response — share the physical wall format with NOCs and transport ops, but the operating model is structurally different. Activation is event-driven, not continuous. Multiple agencies coordinate under a single command structure. Decisions are made with incomplete and sometimes contested information. Regulatory frames (NIMS / ICS in the US, CECIS in the EU, COBR in the UK, ECC equivalents elsewhere) shape the organisational structure that uses the wall. This article maps how that difference shows up in wall procurement and where software-defined walls appropriately fit.

What "crisis management room" actually covers

The phrase covers a wider operational range than the others in this E-use-cases series. The common architectural elements are activation-driven operation, multi-agency coordination, and an explicit command-and-control structure running the room during an event.

  • Municipal / regional EOC. City, county, or regional emergency operations centre, activated for natural disasters, large public events, mass-casualty incidents, critical infrastructure failures. Hosts representatives from police, fire, EMS, public works, transportation, public health, mass communications, and elected official staff during activation.
  • State / national EOC. FEMA Regional / National Response Coordination Centres in the US, Cabinet Office Briefing Rooms (COBR) in the UK, equivalent structures elsewhere. Activated for larger-scale events that exceed local capability or involve cross-border coordination.
  • Consolidated public safety dispatch / fusion centre. Combined PSAP (Public Safety Answering Point) plus dispatch plus intelligence fusion. Examples include the LA Joint Regional Intelligence Center pattern, state-level fusion centres, metropolitan PSAP consolidations.
  • Corporate Incident Response (IR) room. Activated during cyber incidents, ransomware events, supply-chain disruptions, product-safety incidents, executive crises. Often smaller (8-16 displays) but with comparable engineering rigour.
  • Healthcare mass-casualty coordination room. Hospital incident command, regional healthcare coordination during epidemics or surge events. Renders bed availability, transfer coordination, supply chain, staffing, morgue capacity.
  • Mobile / pop-up command vehicles. FEMA Mobile Emergency Response Support (MERS), state and local mobile command, large-event temporary EOCs in tents or transportable buildings. Collapsed wall format with mobile connectivity.

The procurement starting point is the same as in transport: name the environment before sizing the wall. An IR room for a 5,000-person company and a state EOC for a population of 12 million are different problems even when the display count happens to overlap.

Activation modes: blue-sky, grey-sky, red-sky

Unlike a NOC or a transport ops centre, a crisis room is not always in active use. The standard operational frame recognises three states, each placing different demands on the wall.

Blue-sky. No active incident. The room is used for training, exercises, planning, after-action review, maintenance, and tabletop scenarios. Wall content rotates through training scenarios, exercise injects, and baseline status dashboards. Most weeks of the year are blue-sky.

Grey-sky. A heightened but not yet active state — planned major events (large public gatherings, political events, sports finals), elevated threat windows (severe weather forecasts, intelligence advisories, cyber threat indicators), partial activations during smaller incidents. Wall content shifts to scenario-specific dashboards while retaining the training configuration for predictability.

Red-sky. Active incident, ICS positions staffed, primary operating picture in use. Wall is running real data with the full source mix activated. Decisions are being made and recorded for after-action review.

The engineering consequence: the wall must behave identically across all three modes. An operator trained on a configuration they only see during exercises will fumble it during the actual incident — exactly when fumbling matters most. That single requirement ripples into every other design decision: persistent layouts per ICS position, documented MTTR for each component, monthly maintenance windows with the wall in a known-good state before the next grey-sky window opens.

What goes on a crisis room wall during red-sky

Source mix for a typical municipal EOC wall (16-24 displays) during a red-sky activation:

  • Common operating picture (geospatial). Esri ArcGIS Mission, ArcGIS Dashboards, or equivalent mapping platform showing incident location, asset deployment, hazard zones, evacuation routes, damage assessment overlays. Usually the largest single tile on the wall.
  • Agency liaison dashboards (3-6 sources). Each represented agency brings its own primary platform's dashboard — police CAD overview, fire deployment, EMS unit status, utilities outage map, transportation status, public health resource state. Each rendered as a tile so the Incident Commander sees the cross-agency picture without walking to each liaison's console.
  • CCTV and field video. Municipal CCTV, traffic cameras, body-worn camera feeds during tactical operations, news helicopter video where shared. RTSP-heavy ingest, often 8-16 concurrent streams.
  • Public information layer. Mass-notification status (BlackBerry AtHoc, Everbridge), social media monitoring (Dataminr, NC4), news monitoring, public-facing briefing draft for the Public Information Officer.
  • Weather and environmental. NWS / national weather service feeds, river gauges during flood events, air quality during wildfire or chemical incidents, radiation monitoring where applicable.
  • Resource and logistics state. ICS resource tracking, shelter status, supply chain dashboards, mutual aid request board.
  • Communication state. P25 radio system health, 911 call volume, network status, public warning system arm state.

Pattern: geospatial common operating picture is the anchor. Agency-specific dashboards surround it. Field video provides ground truth where it exists. Public information layer is a constant secondary band that the Public Information Officer references for every public briefing.

The incumbent platforms — and where they sit

Crisis room procurement coexists with a small number of dominant platforms in the primary CAD / dispatch / public safety tier. The wall does not replace these; it renders alongside them.

  • CAD / dispatch / PSAP: Motorola Solutions CommandCentral, Hexagon Public Safety HxGN OnCall, Mark43, Tyler Technologies New World, Central Square, Caliber Public Safety, Carbyne (next-gen 911), Genesys (911 PSAP), Frequentis (public-safety voice and ops).
  • Geospatial / common operating picture: Esri ArcGIS Mission and Dashboards, Hexagon Luciad, Cesium, NICE Public Safety Mapping.
  • Physical security information management (PSIM): Genetec Security Center, Milestone XProtect, Verint Situational Awareness, NICE Suspect Search, Honeywell Pro-Watch.
  • Mass notification: BlackBerry AtHoc, Everbridge, Rave Mobile Safety, Singlewire InformaCast, Alertus, OnSolve.
  • Intelligence / fusion: Palantir Gotham, Dataminr, NC4 (Everbridge), Recorded Future (cyber-physical), IBM i2 iBase.
  • Mobile EOC platforms: FEMA MERS standard kits, Mutualink, JPS Interoperability Solutions ACU-T units, Cisco IRSC.

Most of these platforms expose browser-rendered dashboards or panels. That is what makes a software-defined wall practical in 2026 — the wall renders the same browser-rendered agency dashboards the liaison operators see on their consoles, and does so consistently across the diversity of vendors.

What's distinct vs other operations walls

Side-by-side with the other E-use-cases articles in this catalogue, three distinguishing characteristics drive the engineering:

  • Multi-agency rendering as a first-class requirement. A NOC wall renders one organisation's stack; a crisis room wall renders the operating pictures of 5-12 distinct agencies, each with its own visual style and update cadence. The wall has to host that diversity without forcing visual homogenisation.
  • Activation-driven, not continuous. Most of the year the wall is in blue-sky. The reliability bar during the rare red-sky activation is unforgiving — the wall has to come up reliably from a low-use state, not from a continuous- warm state. Different MTTR and cold-start engineering than a 24/7 NOC.
  • Public-facing situational layer is functional, not cosmetic. The Public Information Officer briefs from the wall. The wall is therefore both an operational tool and a backdrop for public- facing communication during the event. Layout choices, content quality, and the absence of extraneous noise matter for reasons that do not apply to a NOC or transport ops centre.

Where Craft Wall fits

Honest scope, mode by mode:

  • Municipal and regional EOCs. Strong fit at the secondary visualisation tier — common operating picture rendering, agency liaison dashboards, CCTV walls, weather and environmental overlays, resource and logistics state, public information layer. Air-gap capability supports facilities with intentional disconnection from public internet during activation.
  • State and national EOCs. Same fit at larger scale. Per-canvas perpetual licensing avoids subscription escalation across multi-decade infrastructure programmes. On-prem deployment without cloud telemetry is a requirement in many national EOC procurements.
  • Corporate IR rooms. Strong fit. Smaller wall format, cyber-incident-specific source mix (SIEM dashboards, attack- surface mapping, threat-intel feeds, comms-team briefing screens), browser-heavy sources.
  • Healthcare mass-casualty coordination. Strong fit at the visualisation tier. Renders bed-availability dashboards, transfer coordination, supply chain, staffing tools — most are browser-rendered today. Patient-level data flows belong inside the certified EHR / HIE chain, not the wall.
  • Mobile EOCs. Strong fit operationally — one commodity Linux mini-PC drives 4-8 displays in a vehicle, no cloud dependency, runs on LTE or satellite backhaul when available, air-gap when not. See hybrid cloud video wall architecture for the connectivity-tolerant split.

Not appropriate, consistently: 911 call-handling, CAD dispatch, PSAP primary operations, P25 radio chain, next-gen 911 i3 conformance. Those layers belong on certified Public Safety platforms; Craft Wall renders alongside, not inside.

Compliance frame

The wall itself rarely carries a compliance certification — but the environment around it does, and the wall has to be compatible with that environment.

  • NIMS / ICS (US National Incident Management System and Incident Command System) shapes the organisational structure of an activated EOC and the operational concepts that show up on the wall (ICS positions, ESF groupings, common operating picture, span of control).
  • NENA i3 defines next-generation 911. The wall is not in the i3 chain but coexists with i3-conformant PSAPs.
  • P25 defines digital public-safety radio. The wall renders P25 system health dashboards but is not part of the P25 chain itself.
  • CECIS (EU Common Emergency Communication and Information System) covers cross-border EU emergency coordination. COBR (UK Cabinet Office Briefing Rooms) defines the UK national coordination structure.
  • GDPR / HIPAA / state privacy laws apply to incident data flowing through the wall — body-camera video, victim information, patient data during healthcare activations. Renderable on-prem without external telemetry is usually a procurement requirement, not a preference.
  • Cybersecurity frames (CISA Cross-Sector Cybersecurity Performance Goals, NIST CSF, EU NIS2) increasingly require EOC infrastructure to meet baseline cybersecurity postures, which shapes wall procurement around air-gap capability, patch management, and supply-chain assurance. See compliance regulatory guide for the cross-sector map.

Tender language for crisis room walls

Phrases that consistently produce the right outcome in EOC and IR room procurement:

  • "Visualisation tier separate from CAD / PSAP / radio chain." Explicit decoupling from the certified Public Safety layer.
  • "Identical behaviour across blue-sky, grey-sky, and red-sky modes." Forces vendors to demonstrate cold-start reliability and persistent layouts that survive extended low-use periods.
  • "Browser-rendered agency dashboards as first-class source type." Required to host Motorola, Hexagon, Mark43, Esri, Genetec, AtHoc, NC4, and equivalent platforms as native tiles.
  • "Air-gap capable; on-prem only; no outbound telemetry." Standard requirement in sensitive EOC procurements.
  • "Persistent layouts per ICS position; layout restore under five seconds from cold." Encodes the activation-mode reliability requirement quantitatively.
  • "Compatible with mobile EOC deployment on a single ruggedised compute node." For agencies that operate both fixed and mobile EOCs, useful to require the same software stack across both formats — reduces operator retraining burden during activations.
  • "Documented MTTR per component class; quarterly maintenance window in writing." Removes the discovery-during- activation failure mode by forcing predictable maintenance.

Read next

For the companion E-use-cases articles, see the NOC reference architecture, broadcast monitoring guide, and transport control rooms map. For the cross-sector compliance frame — NIMS, CECIS, NIS2, GDPR, HIPAA, and how they shape what can sit at which layer — see the compliance regulatory guide. For the connectivity-tolerant architecture that mobile EOCs depend on, the hybrid cloud video wall architecture article splits primary plant from burstable cloud layers.

Frequently asked questions

What video wall is needed for a situation room or EOC?

A situation room video wall should be sized around the common operating picture, not around a fixed display count. Typical rooms run 8-24 displays or an equivalent LED canvas, with maps, CCTV, dashboards, weather, resource status, and public-warning views. Primary dispatch systems stay on certified operator consoles; the wall is the shared secondary layer for commanders and liaisons.

How is a video wall for an EMERCOM crisis centre different from a NOC wall?

A NOC wall runs continuously for one organisation's infrastructure. An EMERCOM / EOC wall is activation-driven and multi-agency: it has to switch between training, exercise, and active-incident modes, and render inputs from dispatch, weather, utilities, transport, healthcare, public warning, and neighbouring jurisdictions. That makes scenario control, read-only integrations, audit, and failover more important than a simple grid of monitoring screens.

Is a hardware video wall required for municipal dispatch, or is software enough?

For municipal dispatch, software is often enough for the secondary visualisation layer if it runs on premises, survives network interruptions, supports failover, and renders the required source mix. It must not replace the certified primary dispatch path: 112 / CAD / radio / PSIM operations remain on their own operator workstations and regulated systems.

Can a software video wall be used in a 911 PSAP or CAD primary dispatch chain?

No, not as part of the primary chain. The 911 / PSAP / CAD chain — call-taking, geo-location, unit dispatch, status tracking — runs on certified Public Safety platforms (Motorola CommandCentral, Hexagon HxGN OnCall, Mark43, Tyler Technologies, Carbyne for next-gen 911) with regulatory frames (NENA i3 for next-gen 911, P25 for radio, FCC requirements). A software wall renders the secondary common operating picture next to the certified PSAP positions — incident heat map, weather overlay, agency liaison dashboards, mass-notification status — but does not handle the call or the dispatch itself. The line is the same as in rail and ATC: certified chain primary, software wall secondary.

How is a crisis management room different from a NOC?

Three structural differences. First, activation pattern: a NOC runs continuously 24/7; a crisis room runs in three modes — blue-sky (training, maintenance, low-traffic), grey-sky (exercises, low-confidence threat windows, planned major events), and red-sky (active incident). The wall has to be usable in all three. Second, agency diversity: a NOC is one organisation's tools; a crisis room is multiple agencies coordinating — police, fire, EMS, utilities, transport, telecom, public health, mass-notification — each with their own primary platform that the wall has to render alongside. Third, decision pressure: a NOC operator works against tickets with relatively complete information; a crisis room incident commander makes decisions with incomplete and contested information, and the wall has to surface what is uncertain, not just what is known.

What does NIMS / ICS framing mean for the wall?

NIMS (US National Incident Management System) and ICS (Incident Command System) define the organisational structure that runs an activated EOC — positions like Incident Commander, Operations Section Chief, Planning Section Chief, Logistics, Finance/Admin, and Public Information Officer. ESF (Emergency Support Function) groupings map agency responsibilities to incident phases. For the wall: each ICS position has a primary working surface (their console), and the wall renders the cross-position common operating picture plus the public-facing situational layer the Public Information Officer needs to brief from. International equivalents are CECIS (EU), COBR (UK), and ECC frameworks in many jurisdictions — same functional pattern with different terminology.

How do mobile / pop-up EOCs differ from fixed ones, and can a software wall work in both?

Mobile EOCs — FEMA Mobile Emergency Response Support (MERS) vehicles, state-level mobile command vehicles, large-event temporary EOCs — collapse the wall down to 4-12 displays mounted in a vehicle or a rapidly-deployed tent, with intermittent connectivity (often LTE / satellite backhaul). The same software stack that runs a 16-32 display fixed EOC can run a 4-8 display mobile EOC if it tolerates intermittent network, runs on a single ruggedised mini-PC, and does not require a cloud control plane. Air-gap or limited-bandwidth capability is mandatory for mobile, not optional. Fixed EOCs have more headroom on display count and connectivity but inherit the same secondary-tier positioning.

Can Craft Wall integrate with Esri ArcGIS, Motorola CommandCentral, Hexagon HxGN OnCall, or Mark43?

Yes — at the visualisation tier, where these platforms expose browser-rendered dashboards (Esri ArcGIS Online, ArcGIS Dashboards, Motorola CommandCentral web consoles, HxGN OnCall web overlays, Mark43 BI dashboards). Craft Wall renders them as first-class browser tiles alongside CCTV, weather, and other sources. Bidirectional integration — the wall driving dispatch actions — is not supported and is not the right architectural pattern; those actions belong on the operator's primary console, not the shared wall surface. Read-only common-operating-picture overlays are the right wall tier.

Does the activation-only nature of crisis rooms change wall sizing or procurement?

It changes the spec, not the sizing. The wall has to look and behave identically in blue-sky training and red-sky activation — operators trained on a configuration they only see during exercises will fumble it during the actual incident. The activation pattern does drive other procurement choices: redundant servers and displays with documented MTTR because failures during an activation are unforgiving; persistent layout configurations per ICS position so a new commander walking in finds the wall as the previous commander left it; explicit testing in monthly maintenance windows so the wall is known-good before an event, not surprise-broken during one. Lifecycle expectations are also longer — a wall procured today should still be operational during a major event in 2034 without a forced migration cycle.

What is the difference between a regional EOC, a municipal dispatch (EDDS), and a corporate situation room?

Three different levels of the same coordination hierarchy. A regional EOC (in Russia — the ЦУКС at the regional Main Directorate of EMERCOM, one per subject of the federation) coordinates incident response across the entire region, interfaces with federal-level NCMC and with neighbouring regions. A municipal dispatch (ЕДДС — Единая дежурно-диспетчерская служба) operates at city or district level, handles primary call intake via the 112 single emergency number, dispatches first-line services (fire, EMS, police, utilities), and escalates to the regional ЦУКС when the incident scale exceeds municipal capability. A regional situation room (Региональный ситуационный центр) is a broader umbrella term for the governor / regional administration management space — it may host civil emergency coordination during a major event, but its day-to-day function is administrative monitoring, not call-taking or dispatch. The wall design differs accordingly: ЕДДС is dispatch-heavy (CAD console primary, wall secondary for context), regional ЦУКС is multi-agency activation-driven (wall is the shared common operating picture during red-sky mode), situation room is administrative monitoring (wall as ambient awareness tool with selective drill-down).

What is OKSION and how does the wall integrate with it?

OKSION — Общероссийская комплексная система информирования и оповещения населения в местах массового пребывания людей — is the Russian federal mass-notification system coordinated by EMERCOM, distributing emergency information through fixed terminals in public transport hubs, large retail, sports venues, and street displays. From the wall's perspective in a ЦУКС, OKSION is one of the sources of common operating picture: how many terminals fired in a triggered scenario, how many failed, what predicted population coverage was achieved. The integration is read-only: OKSION's primary control plane runs in its own dedicated centre (Главный центр управления ОКСИОН), and direct triggering of OKSION from a regional ЦУКС wall would bypass the federal regulatory chain. Treating OKSION status as a wall-rendered dashboard alongside weather, CCTV, and incident maps is the correct architectural tier.

Related reading