The render surface of the fusion engine.

The Problem

Operator screens multiply. Radar on one, RF on another, EO/IR on a third, Remote ID broadcasts on a fourth, narrative feeds on a fifth. Each tool claims situational awareness; the operator provides the actual fusion, under time pressure, from memory. That works in a quiet environment with two tracks. It collapses the moment a real incursion generates fifteen simultaneous detections from eight sensor classes, and the operator is mentally correlating blips while the threat closes. A COP is supposed to solve this. Most don't. They put the same five feeds on one screen and call the resulting dashboard unified. The correlation problem doesn't move - it just gets compressed into less screen real estate.

Who Has This Problem

Key Workflows

Capabilities

Platform Integration

The COP is the primary operator surface for the Empyrean platform. It ingests WMS, WMTS, TMS, XYZ tile servers, GeoTIFF (including Cloud-Optimized GeoTIFF), KML/KMZ, DTED/SRTM terrain, and CoT/TAK natively. It generates MIL-STD-2525C and 2525D symbology dynamically from fused identity - SIDCs update as disposition evolves from unknown to suspect to hostile. Fusion tracks from the Fusion & Decision Engine, EMSO spectrum awareness with terrain-aware RF propagation modeling, SSA pass windows and RPO alerts, narrative intelligence clusters, CUAS force protection tracks, and cyber alerts all render on the same canvas. Zones drawn on the COP drive policy in the Policy & Decision Layer. Camera feeds from RTSP/RTSPS sources and Skydio Cloud render geolocated with CV detections projected to estimated ground coordinates - not just bounding boxes in a video pane. Reference overlays including OpenCellID cell tower density and FCC ULS licensed transmitter data compose alongside live tracks for contextual correlation. It runs at the edge, handles air-gapped deployments with offline basemap support via MBTiles, GeoPackage, and tile archive ingest, and works identically whether connected or dark.