IN Brief:
- Rheinmetall and Breaker have demonstrated autonomous system control from an Australian Boxer Combat Reconnaissance Vehicle.
- A crew member with less than 30 minutes of training commanded a drone swarm through the standard microphone and headset.
- The working Boxer demonstration took place within six months of the companies’ first discussions.
Rheinmetall Defence Australia and Breaker have integrated Breaker’s tactical orchestration software into the Australian Boxer Combat Reconnaissance Vehicle, allowing a crew member to command autonomous systems by voice through the vehicle’s existing microphone and headset.
The customer demonstration used a single Boxer operator to direct a swarm of drones while continuing to operate the vehicle and perform normal crew duties. Rheinmetall says the operator received less than 30 minutes of training before using the system, placing the focus on reducing the amount of additional control equipment and operator interaction needed to manage the uncrewed systems.
Breaker’s software was first integrated into Rheinmetall Defence Australia’s simulator before the companies moved the capability onto a Boxer. A working vehicle demonstration followed within six months of their first discussion, giving the integration programme a short path from simulator work to operation on the physical platform.
The Boxer’s open electronic architecture provides the connection point for the new software. Breaker’s orchestration layer sits between the crew and the autonomous systems, allowing the operator to issue spoken commands without adding a separate hand controller or requiring the crew member to leave the vehicle’s normal communications equipment.
Using the standard microphone and headset removes one source of physical clutter inside an already equipment dense fighting compartment. A separate console or control unit would occupy space, require power and add another interface for the operator to monitor. Voice control instead uses equipment the crew already wears and keeps the command method within an existing operating routine.
The demonstration also tested whether one crew member could control autonomous systems without abandoning other duties. Rheinmetall states that the operator continued vehicle operation while directing the drone swarm, which is a more demanding test than demonstrating the software with a dedicated operator whose only task is controlling the uncrewed systems.
Human machine teaming aboard an armoured vehicle depends on how much attention the autonomous systems demand once they have been tasked. A control method that requires constant manual intervention can simply move workload from one interface to another. Breaker’s software is intended to let the crew command teams of systems at a higher level instead of manually flying each vehicle.
The public demonstration establishes the command interface and integration route but does not establish every condition needed for operational fielding. Rheinmetall has not published data on communications range, performance under electronic attack, the number of autonomous systems that can be managed simultaneously or the behaviour of the software when links to individual drones are lost.
Those limits keep the result within the scope demonstrated: voice control of a drone swarm from Boxer through standard crew equipment, with one operator trained in under half an hour. The companies have not presented the trial as proof of unrestricted autonomous operation or as evidence that the crew has been removed from command decisions.
Vehicle integration still has to account for the communications systems connecting Boxer to the uncrewed platforms. The orchestration software can organise commands, but the vehicle and drones still depend on data links to exchange them. The performance of those links will vary with the radios, antennas, terrain and electronic environment used in any future configuration.
Rheinmetall and Breaker have signed a teaming agreement around the capability, moving the work beyond an isolated software trial. The agreement gives the companies a route to develop the integration as part of Boxer upgrades and to examine other armoured vehicle applications where an existing electronic architecture can host the same orchestration layer.
Boxer is already built around modular mission systems and digital vehicle electronics, which gives software upgrades a different integration path from mechanical changes to armour, mobility or weapon mounts. New code can still affect safety, communications and crew workload, so qualification has to cover the vehicle configuration in which the software will actually be used.
The six month integration period demonstrates that the companies could move from simulator work to a functioning Boxer without redesigning the crew interface around a new controller. Further trials will need to show whether the same arrangement remains manageable with larger autonomous teams, different mission systems and degraded communications.
The present result is therefore specific and measurable: Breaker’s software ran on Boxer, a trained crew member commanded multiple drones through existing voice equipment and the operator continued normal vehicle duties during the demonstration. Those are the functions established by the trial and the basis for any subsequent vehicle integration work.
