BMT sets out command challenge for hybrid navies

BMT has outlined command challenges for future hybrid naval fleets. As crewed ships, uncrewed vessels, distributed sensors, and autonomous systems converge, command tools and simulation environments are becoming core naval requirements.


IN Brief:

  • BMT has set out how hybrid fleets could reshape naval command at sea.
  • Future fleets will need stronger tools for distributed sensors, uncrewed systems, autonomy, and decision support.
  • Simulation, assurance, software, and training are becoming central to the industrial architecture of naval autonomy.

BMT has set out how hybrid fleets will reshape command at sea as navies combine crewed warships, uncrewed vessels, distributed sensors, autonomous systems, and software-defined decision support.

The company’s work, presented during the Combined Naval Event in Farnborough, focuses on the command problem created when naval forces move beyond conventional platform groupings. Hybrid fleets will not simply add uncrewed vessels around existing ships. They will change how commanders assess information, allocate tasks, judge system reliability, and remain accountable when sensing, decision support, and effects are spread across multiple nodes.

That challenge is becoming a central industrial question. Naval autonomy is often discussed through platforms: unmanned surface vessels, underwater vehicles, airborne drones, motherships, and optionally crewed systems. Those assets are only valuable when they can be commanded, simulated, tested, assured, and updated as part of a fleet architecture. Command software and training systems therefore sit alongside hulls, propulsion, payloads, and sensors.

BMT has already expanded its digital and simulation infrastructure through its Digital Innovation and Simulation Centre at Fareham. The facility supports autonomy, digital ports, complex operations training, simulation-based assurance, and ship-design de-risking. It reflects a wider shift across naval industry, where digital environments are no longer peripheral to platform development. They are becoming part of how systems are designed, tested, certified, and operated.

In a hybrid navy, commanders will need to judge competing streams of information from crewed and uncrewed systems. Some data will be real-time, some delayed, some uncertain, and some generated by autonomous processing. The command environment must help operators understand confidence levels, sensor provenance, task status, communications health, and the limits of automated recommendations. Poorly integrated autonomy risks increasing workload rather than reducing it.

Production planning now has to account for that. Uncrewed vessels and autonomous sensors need open interfaces, secure communications, software update routes, and test environments that can reproduce operational conditions. Combat systems need to accept new data sources without becoming brittle. Training systems need to rehearse failure modes, degraded communications, and ambiguous target information. Those requirements shape the design and manufacture of hardware from the start.

The same naval transition is visible in adjacent programmes. SubSea Craft’s MARS unmanned surface vessel has moved into production, bringing compact maritime autonomy closer to repeatable delivery. HAVELSAN’s ADVENT-AI upgrade shows the combat management side of the same movement, where decision-support tools must process sensor and operational data quickly enough to aid commanders at sea.

Hybrid fleets also create a sovereignty problem. Software, processors, data standards, artificial intelligence tools, communications hardware, sensors, and simulation environments all influence operational independence. Navies will need to decide which elements must be controlled nationally, which can be provided by allies, and which commercial technologies can be trusted in military architectures. That is not a theoretical procurement distinction. It affects factory sourcing, security accreditation, maintenance access, and upgrade control.

The training burden will be significant. Crews cannot learn hybrid fleet command solely during live exercises, especially when uncrewed systems are expected to operate in contested, congested, or communications-limited environments. Synthetic training and mission rehearsal will become core parts of readiness. Digital twins, bridge simulators, autonomy testbeds, and operational modelling will be required long before a fleet deploys with a mature uncrewed mix.

Assurance is likely to be one of the hardest areas. Human commanders will remain responsible for decisions while increasingly relying on automated recommendations, remote sensors, and systems beyond direct line of sight. Procurement authorities will therefore need evidence that software works as intended, data is traceable, autonomy is bounded, and operators can understand why a system behaves as it does. Certification will have to cover behaviour, not only hardware performance.

Shipyards and systems companies will feel that shift in work packages. Cable routing, equipment racks, antennas, power distribution, cooling, and cyber-hardening all need to support software-heavy fleets. A vessel designed without spare capacity for future autonomous systems will become harder to upgrade. A combat system that cannot take in new data sources will limit the value of uncrewed assets before they reach the water.

BMT’s command focus cuts to the centre of the hybrid navy problem. Buying uncrewed systems is easier than commanding them well. The fleets that turn autonomy into operational advantage will be those with the simulation, software, assurance, and training infrastructure to make distributed systems usable under pressure.