European first: Intelic connects multi-vendor sensors, C2 and interceptor drone in a single operational workflow

The counter-drone market has spent a decade getting very good at the first half of the kill chain and comparatively little time on the second. Radars, RF detectors, acoustic arrays and EO-IR turrets now routinely detect small unmanned aircraft at useful ranges, and a crowded field of jammers, guns, nets and interceptor drones exists to do something about it. What has lagged is the connective tissue: the software and message formats that turn a detection from one vendor's sensor into a tasking order for another vendor's effector, fast enough and reliably enough to matter. Intelic's Latvian field test is notable because it claims to have demonstrated precisely that join — detection, command and control, and interceptor tasking stitched into a single operational workflow across multiple vendors' equipment.

The mechanics deserve scrutiny, because this is where counter-UAS programs usually fail. A functioning workflow requires sensor data to be normalized into a common track picture, tracks to be classified and prioritized against rules of engagement, and a tasking message to reach an interceptor or its operator inside a decision window measured in seconds. Each of those steps crosses a vendor boundary, and each boundary is a place where latency, proprietary protocols and liability questions accumulate. The hard part is not the demonstration; it is sustaining track continuity when sensors disagree, when RF conditions degrade, and when the interceptor's own seeker or datalink has to hand off from the ground picture. Multi-vendor integration also raises a governance question that procurement officers should press on: who owns the arbitration logic when two sensors produce conflicting tracks, and who is accountable when the system tasks an interceptor on a false positive.