Airport Technology as a System of Systems
Systems · systems-architecture
Definition
A framework for understanding airport technology as six interlocking domains — Flight & Operations Data, Passenger Processing, Baggage, Security & Border Control, IT/OT Infrastructure, and Integration & Intelligence — and why a system being available is not the same as the operation it supports actually working.
Why Think in Systems, Not Silos
A modern airport doesn't run on one platform — it runs on dozens of purpose-built systems that were often bought from different vendors, in different decades, for different departments. Each one works. The hard part is what happens at the seams between them, because a passenger's journey (or a bag's, or an aircraft's) crosses six or seven of these systems in the space of an hour. This page maps that landscape into six domains and introduces a distinction that matters more than any single acronym: a system being available is not the same thing as the operation it supports actually working.
The Six Domains
System Availability Is Not Operational Resilience
A dashboard showing every system green — 100% uptime, no outages — can still coexist with a badly degraded operation. The reason is a dependency chain that sits underneath the six domains: System availability doesn't guarantee the interface between two systems is actually exchanging data correctly; a working interface doesn't guarantee the data crossing it is complete or correct; correct data doesn't guarantee the downstream process consuming it behaves as designed; and a working process doesn't guarantee the operational dependency relying on it is actually satisfied. Only at the end of that chain does a failure become visible as business impact — a delayed bag, a missed connection, a gate conflict.
Why the Distinction Matters in Practice
An AODB that is technically "up" but silently receiving stale flight-time updates from an airline's DCS will show green on every system-health dashboard while gate assignments, FIDS displays and stand allocation quietly drift out of sync with reality. The system didn't fail — the dependency chain running through it did. Monitoring individual systems in isolation catches outages; it does not catch this class of failure. That is the practical argument for treating airport technology as a system of systems rather than a list of platforms to keep patched and online: the failures that actually disrupt a passenger's day usually happen at the interfaces, not inside any single box.
About This Framework
The six-domain map and the System Availability vs. Operational Resilience distinction on this page are drawn from an infographic and framework published by Omer Alsayed (see Sources below). It is presented here as an individual practitioner's framework, not an official ICAO/IATA/ACI standard — the specific systems and abbreviations it references (AODB, A-CDM, CUPPS, CUSS, DCS, BHS, HBS, BRS, CIQ, APIS, eGate, INAD, SWIM, RFID, X-Ray Inspection) each have their own dedicated, independently sourced entries elsewhere in this Knowledge Base.
Related Terms
Sources
Last verified: 2026-09-30 · Status: draft