Airports data integration

Example use case

Operations teams combine A-CDM milestones, AODB stand allocations, baggage system load and terminal HVAC status to anticipate the effect of a late arrival wave on stands and passenger flow.

Typical sources and transports

A-CDM platform interfaces, AIDX messages, ADS-B and ASTERIX surveillance feeds, BACnet/IP for terminals, OPC UA for baggage and jet bridge controls, and METAR weather reports.

What the data means

Milestones distinguish scheduled, estimated, target and actual times. Surveillance positions are context, not separation data. Passenger flows should be aggregate counts.

Prerequisites

Before connecting airports sources, prepare an inventory of systems and owners, interface documentation for each one, read-only credentials and approved network paths. Agree identifiers, units and time zones early, and name a person who can confirm values against the source during commissioning.

Limitations

The platform is not an ATM or safety system. Surveillance licensing, AMHS and ACARS paths depend on third parties and are validated per project.

ALLINLET reads and normalises data; it does not control equipment.

Catalogue entries for this domain

The connector catalogue lists 64 entries for this domain. A selection is shown below. Listing indicates a possible integration path, not that it is implemented, validated or installed for your environment.

• A-CDM integration
• A-CDM platform
• ACARS via airline (ARINC 618/620)
• ADS-B (aircraft)
• AIDX
• AMHS gateway integration
• ANPR
• ASTERIX (native)
• ASTERIX feed (UDP multicast)
• BACnet/IP
• CDC
• CEF
• CSV
• DATEX II
• DICOS
• DICOS for images
• DNP3
• DPI messages to Eurocontrol

Further reading

• Digital twin guide
• Edge cloud guide
• All resources
• Connector catalogue
• Industries
• Products

Catalogue listings describe possible integration paths. Implementation and validation status is confirmed for each source during project scoping; no certification, service level or price is implied by this page.