JLG Consulting
Contact us

Capability 02

Surveillance data and real-time air traffic management (ATM) software

Software that reads surveillance data as it arrives, decodes it, assembles it into flights and finds the events that matter for safety. We have re-engineered and developed EUROCONTROL's ASMT since 2009, and built controller working position software with INDRA since 2006.

Contact usSee ASMT

The problem

Every message decoded, at the pace of the traffic.

Surveillance data reaches air traffic management software as a stream of binary messages in ASTERIX, EUROCONTROL's exchange format: system tracks, safety-net alerts, status messages, each category with its own layout and its own editions. Software that uses the stream has to decode every message, keep pace with the traffic and turn tracks into flights before it can say anything useful about them.

It also has to live next to operational systems that must not be disturbed. It is often installed on a closed network, where nothing can be downloaded, and it has to be tested without touching the live feed. When it finds a safety event, an investigator needs to see exactly what happened, weeks later, from the recorded data.

What we have built

From the radar feed to the replay.

in servicefor EUROCONTROL · 2009 to today

ASMT

EUROCONTROL's Automatic Safety Monitoring Tool. It records ASTERIX data from the network or from recordings, decodes it, builds flights and flags safety events that investigators replay on a map. We moved it to a new architecture and released version 6 in July 2026.

Read the case study →
ongoingwith INDRA · since 2006

Controller working position, with INDRA

Where the same tracks reach the controller. We build controller working position software with INDRA, including the iTEC working position.

Read the case study →

Standards and data formats

What this software reads.

  • ASTERIX Category 062: system track data
  • ASTERIX Category 004: safety net messages
  • ASTERIX Category 065: service status messages
  • ASTERIX recordings: raw, final frame and pcap

How we would approach yours

Start from your own recordings.

  1. Collect the data you haveRecordings from your own systems, and the ASTERIX categories and editions they produce.
  2. Decode before designingA decoder tested against your recordings comes first, so everything after it rests on data you trust.
  3. Keep the stages apartRecording, decoding, flight building and detection as separate services, each tested and scaled on its own.
  4. Make everything replayableAny event can be replayed from the recorded data, for an investigator or for a test.
  5. Plan for closed networksInstallation and updates that work on a closed network, from the first release.

A typical engagement

Inside your team, or a team of ours.

Model
Team extension, or build and run
Team
Engineers who already read ASTERIX, in your team or in a product team of ours
How it starts
A call about your data, your systems and your codebase. Screening comes first, and CVs are shared under NDA.
After launch
Regular releases and support from the same team

Next step

Tell us what you need.

Who else will ask, and what they'll want

  • Your engineering leadHow our engineers join your team, in Team extension.
  • Your security officerScreening and staff security, on Trust.
  • ProcurementCompany details, certification and references, on Trust.
Send this to a colleague