Overview#
Mission Defence Operations Centre teams judge software in the first five minutes of a live picture. If the command surface is four simulated panels that drift from truth, operators stop trusting it. If engagement actions are unclear about policy, commanders will not press them. If intercept geometry omits how far a shot is predicted to miss, assessment after a pass becomes folklore. Buyers comparing Argus MDOC to specialised C2 suites ask for one calm viewport, live data, governed actions, and kinematics they can defend in an after-action review.
The MDOC Command Workbench rebuilds the command surface into a single viewport fed by real services. Panels that once used simulated feeds now read served backend data. Governed operational controls and policy-based batch engagement mutations sit behind the same workbench. Intercept views expose predicted miss distance alongside the wider kinematics picture. Sensor-fusion fields such as coasting and seconds since measurement participate in track quality judgement. Top navigation consolidates entry so MDOC is reachable as a first-class defence workspace rather than an orphaned analysis mode.
This module is the operator-facing companion to the MDOC Interoperability and Connector Support Matrix: the matrix states which standards are native, partner, or planned; the workbench is where native live picture and governed action meet the human on duty.
Last Reviewed: 2026-09-15 Last Updated: 2026-09-15
Key Features#
-
Single-viewport command: Command text, time windows, and analysis modes share one workbench instead of fragmented simulated boards.
-
Live data paths: Panels read served backend data. Component inventories regenerate as the workbench evolves so documentation and UI do not silently diverge.
-
Governed operational controls: Operational actions enforce policy before execution, matching fail-closed instincts defence customers expect.
-
Policy-based batch engagement: Effector batch engagement mutations run only for sets policy allows, with rejection of sets that would violate rules of engagement configuration.
-
Predicted miss distance: Intercept assessment computes and persists miss distance so operators and planners share a numeric after-pass picture.
-
Sensor-fusion quality cues: Coasting and seconds-since-measurement style fields help operators judge whether a track is freshly measured or coasting on prediction.
-
Navigation consolidation: fe2 top navigation unlocks MDOC as a coherent destination alongside other defence tools.
-
Companion to connector honesty: Live contribution still respects the native-versus-partner rules documented in the interoperability matrix; the workbench does not market partner-only waveforms as native.
Use Cases#
-
Live air picture watch: Operators monitor tracks and intercept geometry in one viewport during heightened readiness.
-
Policy-constrained engagement: Commanders select a batch of effectors; policy blocks the subset that would violate ROE and allows the remainder.
-
Post-pass assessment and training: Planners review predicted miss distance recorded during an intercept sequence for procedure updates.
-
Coalition demonstration: Visitors see a workbench bound to live native standards rather than a slide of simulated tracks.
-
Integration with partner bridges: When partner gateways push normalised native shapes, those tracks appear in the same workbench operators already trust.
Integration#
MDOC and effector backends provide live panel data, governed controls, and batch engagement APIs. Intercept kinematics services supply miss distance and related geometry. Sensor fusion contributes track quality fields. fe2 hosts the workbench UI and navigation entry. The MDOC connector support matrix and live ingest paths define which standards can contribute to the picture. auth_service and service JWTs protect defence routes under existing scope registries.
Open Standards#
- NATO APP-6 symbology: Tracks and effectors remain presentable with standard military symbology where configured.
- STANAG-oriented track exchange: Track identity and kinematics align with STANAG-oriented track modules already in Argus (including STANAG 4676 native paths).
- GMTI / sensor fusion conventions: Coasting and measurement-age fields follow the sensor-fusion vocabulary used in ISR workbenches.
- OAuth 2.0 service JWTs: Machine and operator calls to MDOC live routes follow the platform service authentication model.