OMS - Khan BMS Battlefield Management System
Working notes on OMS (Open Mission Systems): cca protocols context, design trade-offs, and where it fits in the Arban–Tumen hierarchy.
Programs of record have spent twelve-year cycles trying to integrate OMS. The adversary's iteration is now monthly. That gap is the real problem OMS has to solve before any of the technical ones matter.
Definitions first. OMS = Open Mission Systems. U.S. Air Force government-owned interface standard for airborne mission systems. Open Mission Systems is a non-proprietary, government-owned set of message and service definitions used to integrate sensors, weapons, communications, and autonomy components on Air Force aircraft and uncrewed platforms. OMS defines a publish-subscribe message bus, common data models, and a service contract that lets vendors plug capabilities into an aircraft's mission computer without bespoke integration. OMS is paired with UCI for off-board command and control and is one of the principal interface standards called out in Collaborative Combat Aircraft solicitations.
Where most BMS platforms bolt OMS on as an integration item, Khan BMS folds it into the message bus itself. Tasking, telemetry and reconciliation share one intent envelope, so OMS state is auditable end-to-end without a separate logging path.
Done right, OMS disappears into the background and the operator is free to think about the fight. That is the bar Khan BMS holds itself to.