What does ‘integrating UAS and counter-UAS into the modern battlespace’ mean in practice?

“In practice, integration means your reconnaissance drone does not get shot down by your own C-UAS. It looks like a single screen in a command post where friendly drone tracks, incoming threat alerts, and active counter-UAS sectors are mapped in real time. But we're not there yet. Even in Ukraine, operators use multiple screens, radioing back and forth to avoid jamming their own systems.

“True integration is different – it means automated deconfliction. It is about linking sensor feeds directly to shooters and jamming arrays via unified networks so that action is taken in seconds, not minutes.”

Why is interoperability such a critical requirement for unmanned systems operating alongside manned assets?

“Alongside means we share the same airspace, while until today we’ve segregated horizontally and vertically. If a helicopter pilot and a drone operator cannot talk to the same network, they cannot share the sky safely. Interoperability means a manned jet or helicopter can receive target coordinates or video directly from a scouting drone without a human having to read coordinates over a radio.

“In high-threat environments, radio silence is survival. Systems must exchange data automatically, so they are more than the mere sum of their parts. Without this, manned crews will reject flying alongside drones because the risk of mid-air collision or friendly fire is too high.”

Can you explain what an open architecture approach involves, and why it matters for UAS and counter-UAS integration?

“Open architecture means building systems like Lego bricks. You have standard ports, standard data structures, and standard software interfaces. If a new jamming frequency is deployed by the enemy tomorrow, we cannot wait for a defence prime to redesign a proprietary system. We need to plug in a new radio or load a new software module instantly.

“It allows us to integrate a payload from company A onto a drone from company B, controlled by software from company C. This is of utmost importance when users operate dozens of different systems. Note that variety is not desired, it is a byproduct of how much mass we need – the magnitude of which can hardly be supplied by one manufacturer.”

What are the main technical or operational barriers to achieving true interoperability between different UAS platforms and systems?

“The technical barrier is proprietary data formats. Manufacturers still quite often intentionally lock their products to force users into their ecosystem. The operational barrier is the lack of standardised user interfaces. New drone, new operating system, therefore new training is needed. We need intuitive, user-friendly interfaces, not over-engineered complexity.”

How does counter-UAS technology need to evolve as unmanned systems become more sophisticated and widespread on the battlefield?

“Counter-UAS has largely focused on the easiest problem to solve: Shahed-like drones. Easily detectable, predictable, and quite a big target, they’re now defeated by a myriad of effectors.

“But the true issue C-UAS must tackle is different – the nimble, fast and erratic FPVs, ubiquitous in the battlefield. This needs smart interceptor drones that can launch, track, and destroy enemy threats at soldier level. Ideally, these would be man-portable systems – not the multi-million truck-mounted arrays that will be destroyed as soon as they hit the frontline.”

What does effective manned-unmanned teaming look like operationally, and what makes it work?

“It looks like the pilot of a manned aircraft commanding a swarm of scouting and strike drones with minimal cognitive load. The pilot does not fly the drones; they assign tasks, like searching a grid sector. The drones execute the task autonomously and report back only critical findings.

“It works when the onboard software handles the flight path, threat evasion, and sensor processing, allowing the human to focus strictly on tactical decisions and weapon release authority. It is about extending the pilot’s reach while keeping them out of harm’s way.

“To make it work, you need a resilient C2 system with graceful degradation, ensuring drones remain an asset, not a liability. And of course, the drone’s performance must match that of the associated manned aircraft, so the latter isn't slowed down.”

What role does open architecture play in enabling faster integration of new capabilities as threats evolve?

“It allows us to push software updates to the field in hours, not years. If we identify a new electronic warfare threat, we update our algorithms and deploy the patch to the fleet.

“This speed is impossible with closed, monolithic systems. Open architecture lets us treat hardware as a generic truck and software as the brain. We can continually upgrade the brain without needing to rebuild the truck.”

What can attendees expect to take away about the future direction of UAS and counter-UAS integration in defence operations?

“The takeaway is that software-defined capabilities win wars. The days of buying a drone and keeping it unchanged for ten years are over. To survive, defence forces must adopt a software-first mindset.”