[Developers]

Operational Picture and Command Decision Workspace

Command teams need more than a map full of icons. They need a working view of what is happening, what systems are healthy enough to trust, what capabilities are available, and which decisions are waiting for a commander.

Category: ModulesLast Updated: Mar 18, 2026
modulesgeospatial

Overview#

Command teams need more than a map full of icons. They need a working view of what is happening, what systems are healthy enough to trust, what capabilities are available, and which decisions are waiting for a commander. When those pieces are separated across dashboards, messaging threads, and slide decks, the command picture is always out of date by the time it reaches the decision-maker.

The Operational Picture and Command Decision Workspace module provides a unified command-facing view that aggregates operational entities, exposes gateway and interoperability health, links capability packs and exercise scenarios, and keeps a persistent decision workflow alongside the live picture. It is designed for control rooms, command posts, exercises, and multi-agency environments where situational awareness and decision discipline have to live together.

Last Reviewed: 2026-03-18 Last Updated: 2026-03-18

Key Features#

  • Aggregated Operational Picture: Present a command-ready view of entities, incidents, and operational state in one workspace.
  • Operational Entity Drilldown: Let commanders open a specific entity and review its context without losing the wider picture.
  • Gateway Health View: Surface interoperability and gateway health so teams know whether a feed is trusted, degraded, or unavailable.
  • Capability Pack Visibility: Show which capability sets are in play for a workspace, scenario, or mission context.
  • Traceability Layer: Keep a record of how the command view maps to capability coverage and operational evidence.
  • Exercise Scenario Support: Run the same workspace in training or exercise mode without inventing a separate command tool.
  • Decision Recommendations: Present decision support items that can be approved, deferred, or escalated inside the same workflow.
  • Persistent Command Sessions: Maintain a command session for a workspace rather than treating every action as a disconnected event.

Use Cases#

  • Control Room Command View: A duty commander monitors live operations, sees which feeds are healthy, and tracks pending decisions from one workspace.
  • Exercise Control and Evaluation: An exercise team uses the same command view for a training scenario and later reviews the decision history.
  • Multi-Agency Coordination: Partner agencies work from a shared picture while preserving a formal command decision trail.
  • Gateway Degradation Awareness: A commander spots that a partner feed is degraded and adjusts the operational reliance placed on that data.
  • After-Action Review: The service reconstructs what the command team saw and which decisions were taken at each stage.

Integration#

  • PSAP and Dispatch Workflows: Incidents and call-driven operational context can feed directly into the command picture.
  • Operational Mapping and Geospatial Layers: The workspace can consume the same location, track, and overlay services used by map-facing modules.
  • Unified Command and Major-Incident Workflows: Command sessions can align with broader protocol, checklist, and escalation models.
  • Alerting and Notification Services: Decision items and feed-health changes can trigger updates outside the workspace when required.
  • Exercise and Readiness Workflows: Capability packs and scenarios can support training and readiness review as well as live operations.

Open Standards#

  • OGC API Features and GeoJSON: operational overlays and spatial entities can align with standard geospatial exchange models.
  • OGC SensorThings API: sensor-driven observations can feed the command picture using a standard observation pattern.
  • WGS 84 / EPSG:4326: positions and map references use the standard latitude-longitude model.
  • W3C PROV-DM: command decisions and traceability records can be represented as a provenance trail.
  • RFC 8259 JSON: workspace, capability, and decision payloads can be exchanged in a standard structured format.
  • ISO 8601: event and decision timestamps use a standard date-time format.

Ready to Build?

Get started with our APIs or contact our integration team for support.