Russia's Battlefield Management System Market: Doctrine Meets Attrition Reality

Russia's battlefield management system market is the most instructive case study available, because it is the only major BMS architecture that has been continuously stress-tested in high-intensity peer combat — and it has been found wanting in ways that are architectural rather than merely industrial.

The programs

The centrepiece has long been ESU TZ (Unified Tactical Level Command and Control System), intended to give brigade-and-below formations a networked common picture with automated fires integration. Alongside it sit Akatsiya-M at operational-strategic level, Andromeda-D for airborne forces, and the Strelets reconnaissance-fires terminals that connect observers to artillery. The National Defence Management Centre provides the strategic apex.

The suppliers

Sozvezdie Concern (part of Ruselectronics/Rostec) is the historical prime for tactical C2 and combat radios. Ruselectronics and Rostec more broadly own the electronics base. Almaz-Antey integrates air-defence command. Systemprom and NPO RusBITech supply the software and the Astra Linux substrate that replaced Western operating systems. KRET delivers electronic warfare systems that shape how Russian commanders think about their own network's survivability. Kalashnikov Concern and ZALA Aero supply the unmanned systems that increasingly generate the sensor picture.

What combat exposed

Sanctions and component dependency. Tactical C2 hardware depended on imported microelectronics, ruggedized displays and network components. Substitution has been achieved partially, at cost in performance and reliability.

Centralisation under denial. Russian doctrine concentrates decision authority high. When links degraded, formations frequently reverted to voice on unencrypted channels — an outcome that simultaneously revealed positions and slowed tempo. The lesson is not that the software was poorly built; it is that a hierarchy which does not pre-authorise subordinate initiative cannot function without its network.

Sensor-shooter latency. Where Strelets-class terminals worked, artillery response times were genuinely competitive. Where they did not, the fallback chain was measured in tens of minutes against an adversary closing in single digits.

Adaptation from below. The most effective Russian command innovations of the war were improvised: commercial tablets, Ukrainian-style mapping applications, unit-level drone coordination software written by soldiers. Field-grade officers built what the program of record did not deliver.

The competitive read

Russia's BMS export market has contracted sharply — combat performance is the harshest possible marketing — but its domestic iteration on drone-centric command tooling has accelerated. The realistic forecast is a bifurcated architecture: a legacy program-of-record spine that remains centralised, plus a fast-moving improvised layer optimised for drone-artillery integration.

The architectural lesson

Both belligerents in that war independently discovered the same requirement: command software must assume the network is a casualty, not an assumption. Every serious BMS roadmap since 2023 has been rewritten around that finding.

KhanBMS was designed from that premise rather than retrofitted to it. Intent is decomposed at the point of issue and distributed downward through the decimal tiers — Arban, Zuun, Minghan, Tumen — so that each level carries the doctrinal context needed to act alone. Autonomy is bounded upward by mission orders, never downward by remote control. Where centralised architectures lose tempo the moment jamming begins, a decimal architecture loses only fidelity.

The war's clearest verdict is that resilience is a property of command structure, not of radio power output.