Chapter 04 · Integrations

SYSTEMS THAT EXCHANGE

Every chapter so far has depended on data arriving from somewhere else. This one maps those exchanges, the standards that describe them, and the failure modes that buyers should test before signing.

The lounge sits downstream

A lounge is rarely the source of the data it relies on. Flight times come from the airport operational database (AODB) and flight information display systems. Passenger and cabin data originate in airline departure control systems. Status tiers live in loyalty platforms; programme memberships in network databases; prices and charges in point-of-sale; rosters in workforce management; temperatures and door states in building systems.

The lounge platform's job is to receive, reconcile and act. Its quality is therefore bounded by the quality and timeliness of what it receives, and by how clearly each source is designated as the authority for its own data.

Flight information display in a dark terminal with amber text rows

Exchange map

Latency tolerances are indicative and depend on use. The point is to agree them explicitly.

SourceData the lounge needsRelevant standard or frameworkTolerable delayIf it goes silent
AODB / flight informationEstimated times, gates, boarding statusIATA AIDX; EUROCONTROL A-CDM milestonesSeconds to a minuteMissed calls, wrong time windows
Departure controlCabin, check-in statusIATA BCBP (Resolution 792) at the barcode levelMinutesManual eligibility checks
Loyalty / programme networksStatus, membership validity, guest rulesContract-specific APIsSeconds at entryOffline fallback list required
Point-of-salePaid entry, guest fees, upgradesPCI DSS v4.0SecondsCash-free fallback rules
Workforce managementWho is on shift, rolesVendor-specificHoursTasks reach absent staff

Push, poll and source of truth

Integrations either push changes as they happen or poll a source at intervals. Pushed flight updates suit boarding information; polling every fifteen minutes is fine for rosters and harmful for gate changes. Ask every supplier, for each feed, which method is used, what the interval is, and how the system behaves if a message is late or arrives out of order.

Source of truth matters as much as speed. If the lounge stores its own copy of a guest's status, which copy wins when they differ? A clear rule — "the loyalty platform is authoritative; local copies expire after the visit" — prevents both disputes and stale data.

Security and regulatory frame

Several frameworks shape integration choices in Europe. The GDPR governs passenger data flows and requires processing agreements between controllers and processors. PCI DSS v4.0, published in March 2022 with v3.2.1 retired on 31 March 2024, applies wherever card data is handled. ISO/IEC 27001:2022 is a common reference for supplier information security. The NIS2 Directive, (EU) 2022/2555, which member states were required to transpose by 17 October 2024, covers airport managing bodies among other transport entities; lounge suppliers connected to airport systems may be asked to meet its supply-chain expectations.

Industry context

SITA's annual Air Transport IT Insights reports track airline and airport technology investment priorities, and IATA's One ID initiative explores the use of biometric identity across the journey. Both are useful for context; neither replaces testing the specific interfaces a lounge will run on. Companies such as SITA, Amadeus and Collinson operate in this space; we describe categories rather than recommending products.

Questions for technology buyers

  • For each feed: push or poll, interval, and documented behaviour on delay.
  • Which system is authoritative for each data item, and how conflicts resolve.
  • What the lounge can do with every feed offline, rehearsed in a drill.
  • Where data is stored, for how long, and under which processing agreement.
  • Evidence of security certification or audit relevant to the scope.
  • How changes in airline or programme contracts reach entitlement rules.
  • How monitoring shows a silent feed before staff notice its effects.
Dim lounge workspace with laptops and cables on a long dark counter

Sources and dates

  1. IATA, Aviation Information Data Exchange (AIDX) standard documentation, consulted January 2026.
  2. IATA, Resolution 792 — Bar Coded Boarding Pass standard.
  3. IATA, One ID programme overview, consulted January 2026.
  4. EUROCONTROL, Airport CDM Implementation Manual.
  5. PCI Security Standards Council, PCI DSS v4.0 (March 2022); v3.2.1 retirement 31 March 2024.
  6. ISO/IEC 27001:2022, published October 2022.
  7. Directive (EU) 2022/2555 (NIS2), transposition deadline 17 October 2024.
  8. SITA, Air Transport IT Insights (annual series).

Continue to the answerbook