JLG Consulting
Contact us

Capability 03

Operational HMIs and test data

Controller working position software, and test data from recorded surveillance traffic. We have built working position software with INDRA since 2006, including the iTEC working position.

Contact usRead the case study

The problem

One person, many systems, no spare attention.

The working position is where all the air traffic control software meets one person. A controller reads the traffic picture, the flight data and the safety-net alerts on it, and acts on them, for hours at a time. A screen that buries an alert, or an action that takes one step too many, costs attention when there is none to spare.

It runs at operational centres that never stop, so every change has to arrive tested, and the people who support it have to know the code and what the controller is looking at.

What we have built

At the controller's position, and at the investigator's.

ongoingwith INDRA · since 2006

Controller working position, with INDRA

We build controller working position software with INDRA, including the iTEC working position, and support the INDRA systems in operation at DFS, LVNL, NATS, ROMATSA, ENAIRE, Avinor and PANSA.

Read the case study →
in servicefor EUROCONTROL · 2009 to today

ASMT replay

The investigator's side of the screen: safety events replayed on a map from the recorded surveillance data, with filters, saved queries and export.

Read the case study →

Test data

Recorded traffic, played back as a live feed.

Software that reads surveillance data has to be tested against traffic that looks real, without touching the operational feed. In ASMT, converters read ASTERIX recordings, in raw, final frame or pcap form, and send them over the network as if they were live.

How we would approach yours

Work in your process, test on recorded traffic.

  1. Work inside your processYour codebase, your reviews and your release train.
  2. Test on recorded trafficReal recordings played back as a live feed, so the screen meets realistic traffic before it meets controllers.
  3. Support it in operationEngineers who know the code support it once controllers rely on it.

A typical engagement

Team extension, for the long term.

Model
Team extension
Team
Our engineers inside your team, on your codebase
How it starts
A call about the codebase and the roles. Screening comes first, and CVs are shared under NDA.
After launch
Support in operation, from engineers who know the code

Next step

Tell us what you need.

Who else will ask, and what they'll want

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