UCI - Khan BMS Battlefield Management System
What UCI (Universal Command and Control Interface) actually does on a contested cca protocols link, and why Khan BMS treats it as a formation-level primitive instead of a vendor integration.
Universal Command and Control Interface is the kind of capability you only notice when it is missing. UCI sits inside the OODA loop, not next to it — which is exactly why it gets shortchanged in budget cycles.
Definitions first. UCI = Universal Command and Control Interface. Government-owned C2 messaging standard for off-board control of air and space assets. UCI is the off-board complement to OMS: a standardized set of XML/Protobuf messages and service contracts that lets a controller, ground station, or another aircraft task and receive telemetry from a remote platform without proprietary glue. UCI is widely cited as a core interface for Collaborative Combat Aircraft because it permits a single C2 node to drive a mixed fleet of CCAs from different vendors. Recent revisions emphasize machine-to-machine tasking, mission threads, and resilience to intermittent links.
Where most BMS platforms bolt UCI on as an integration item, Khan BMS folds it into the message bus itself. Tasking, telemetry and reconciliation share one intent envelope, so UCI state is auditable end-to-end without a separate logging path.
UCI is anchored at the Arban — ten nodes under one tactical leader. Small enough to reason about by hand, large enough to absorb the loss of a node without re-planning. Authority for UCI is bounded at this tier; nothing the Arban does can poison its parent.
Done right, UCI disappears into the background and the operator is free to think about the fight. That is the bar Khan BMS holds itself to.