VAERNSYSTEMS
EN/DA Discuss a pilot
Sensor integration for drone detection

Different sensors.One shared data path.

We are developing a vendor-independent software layer intended to translate and correlate data from radar, RF detectors, cameras and acoustic sensors — and pass it to the C2 system the user already relies on. We are starting with one bounded pilot.

Discuss a pilotSee the data path
Architecture concept
Sensor input → VAERN → existing C2. A concept illustration of the intended data path. C2 is the system the user already relies on for command, control and the situation picture.
01Selected sensor interfaces
02A common representation
03An agreed receiving format
AI-generated background
From noise to one data path

Many formats in.
One clear data path out.

Sensors can describe the same airspace in different formats, units and time stamps. VAERN is developing the layer intended to translate and correlate their reports — keeping source and uncertainty — before they reach the C2 system the user already relies on.

Illustration · example data · design goal
  1. Example sensor messages in mixed formats
  2. VAERN: translate and correlate
  3. Aligned fields for an existing C2
Illustration, not live data. Incoming: made-up example messages from four sensor types, each in its own format. VAERN layer: the software VAERN is developing. Outgoing: the same reports as aligned fields — such as source, bearing, uncertainty and status — on their way to an existing C2 system. Status values such as “possible relation” are examples; how reports relate will be evaluated in a pilot.

From sensor to receiver

Follow an observation.

Radar, RF detectors, cameras and acoustic sensors describe what they detect in different ways. Follow two illustrative reports through the data path we aim to test in a pilot.

Concept illustration. Specific interfaces and field rules must be agreed and tested in the first pilot.

Illustrative example data OBS-0142 · OBS-0217
01 / 04

Observations from two sources

Source messages · two RF detectorsINPUT
FieldSensor ASensor B
source_idsensor-Asensor-B
observation_idOBS-0142OBS-0217
bearing_deg42.6318.4
uncertainty_deg±2.0±3.0
time_utc14:03:07.214:03:07.5

First, we need to understand the source fields, units and limitations.

02 / 04

A shared language for data

bearing_deg42.6Source field
azimuth_deg42.6Shared field
Example shared fieldsVAERN
source_ref
sensor-A / OBS-0142
azimuth_deg
42.6
uncertainty_deg
±2.0
Original message
Kept as reference

The field gets a shared name. Its source and reported uncertainty travel with it.

03 / 04

One drone or two?

Bearing lines from two known sensor positions
Two reports to compareVAERN
Sensor A · RF detectorSensor B · RF detector
ReportOBS-0142OBS-0217
Bearing42.6° ±2.0°318.4° ±3.0°
Time (UTC)14:03:07.214:03:07.5

What is compared

  • Time — are the reports close enough in time?
  • Bearing or position — do they cross where an object could be?
  • Uncertainty — do the error margins overlap?
  • Source context — what can each sensor measure, and what can it not?

Possible outcomes

  • Same object
  • Two objects
  • Unresolved

When the data cannot separate two objects, the design goal is to report “unresolved” rather than guess. Methods and thresholds will be evaluated in a pilot.

04 / 04

On to the receiving system

Intended receiver formatOUTPUT
Reference
sensor-A / OBS-0142
Bearing
42.6°
Uncertainty
±2.0°
Possible relation
OBS-0142 ↔ OBS-0217 · Status: to be evaluated
Format and version
To agree in the pilot

The pilot must show that the receiver can read and use the agreed fields correctly.

Design goal: source and uncertainty stay attached to the observation all the way to the receiver.
THE SOFTWARE LAYER

The connection is more than a cable.

Different formats, different meanings. Our focus is the work that makes data understandable across system boundaries.

01 / VAERN

Translate the format.

Map selected sensor messages to agreed fields. With a clear definition of what each value means.

02 / VAERN

Correlate the reports.

Two RF detectors each report a drone. One drone or two? We are developing methods to suggest when reports may describe the same object — with the uncertainty shown, not hidden. This will be evaluated separately from format translation.

03 / VAERN

Keep the source in view.

Carry source, assumptions and uncertainty forward, so every output can be traced back to the original message.

See possible inputs, outputs and standards
START SMALL. LEARN SOMETHING REAL.

One connection.
A clear first step.

The first goal is a defined integration pilot. One source, one receiving system and an agreed way to evaluate the result.

Define the data path

Choose a source, a receiving system and the people responsible for their interfaces.

Agree the conditions

Specify formats, data rights, scope and measurable acceptance criteria before development.

Evaluate the result

Document what worked, what remains unresolved and whether a next integration is justified.

Find your starting point
Why sensor interoperability mattersExplore the wider context and our dated source overview.

Drone awareness is our first area of interest. These sourced events describe the context; they are not evidence of VAERN performance.

· Denmark

Copenhagen Airport (Kastrup)

Closure confirmed · drones neither proven nor ruled out No perpetrator identified

Copenhagen Airport closed for about four hours after drone reports

On the evening of 22 September 2025, air navigation provider Naviair halted all take-offs and landings at Copenhagen Airport after reports of two to three drones nearby. Traffic resumed around 00:30. In June 2026, Copenhagen Police said it could neither demonstrate nor rule out drone activity.

Sources: Rigspolitiet, 25 Jun 2026 (official) · DR, 25 Jun 2026 · +4 more sources

· Estonia

Auvere power station, Ida-Viru County

Drones confirmed by authorities No perpetrator identified

Drone from Russian airspace hit a chimney at an Estonian power station

At 03:43 on 25 March 2026, a drone that entered Estonian airspace from Russia hit a chimney at the Auvere power station near the Russian border. Nobody was hurt. The government said several drones crossed the border that morning during a Ukrainian attack on the Russian port of Ust-Luga.

Sources: Kriis.ee (Estonian Government crisis portal), 25 Mar 2026 (official) · ERR News, 25 Mar 2026 · +1 more source

· Denmark

Esbjerg, Sønderborg and Air Base Skrydstrup

Drones observed by authorities No perpetrator identified

Drones reported near Esbjerg and Sønderborg airports and Air Base Skrydstrup

On the night of 24–25 September 2025, police received reports of drones near Esbjerg and Sønderborg airports and Air Base Skrydstrup. The Danish Armed Forces said drones had been observed at several military installations, including Skrydstrup and the army barracks in Holstebro.

Sources: Forsvaret (Danish Armed Forces), 25 Sep 2025 (official) · Forsvarskommandoen (Danish Defence Command), 3 Jun 2026 (official) · +4 more sources

Read the full source overview
AI-generated background
LET’S DEFINE THE CONNECTION

Which data needs
to go where?

Bring a source format and a receiving need. Together, we can explore the scope of a first pilot.

Discuss a pilot
AI-generated background