SECTOR 02
Aviation & Airports
Aviation & Airports
An operational environment with no comfortable maintenance window — where every minute of downtime shows up in the flight schedule.
This environment
An airport is not a building with a network. It is a system of interlocking operational products, each of which depends on the others: the operations database, baggage handling, common-use passenger processing, and flight information displays. A fault in the network layer does not present as a network fault — it presents as a delayed flight. What distinguishes a vendor here is not a certificate, but knowing the names of these systems and how they relate before arriving.
Systems we work with
- AODB — the airport operational database
- BHS / BRS — baggage handling and reconciliation
- CUPPS / CUSS — common-use and self-service check-in
- FIDS — flight information display
- A-CDM — airport collaborative decision-making
- RMS — resource management
- Operational Technology Cybersecurity Controls (OTCC)
What matters in this environment
No maintenance window
Proactive monitoring is not an enhancement here but a necessity — detection must precede impact on the flight.
Inter-system dependency
Dependency maps link service to device to port — so outage impact is known before it spreads.
Sites distributed across the airport
Terminals, gates, aprons and technical buildings — with distributed polling engines rather than one central probe.
Business continuity
Tested continuity plans and documented evidence — precisely what airport tenders ask for.
We know your environment — and we start by reviewing it with you
One session with an engineer who knows this sector's systems by name: we review what you have as it is, and say where we add something and where we do not.