Techbanq

Aviation · reference guide

The airport systems landscape, mapped for people who run programmes

Five systems carry an airport’s operating day, and every digital initiative — an app, a dashboard, an AI assistant — must draw on at least two of them. This guide explains what each records, who owns it, and where their joins fail, so you can read a vendor proposal without needing the vendor to translate it.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CIO, COO
Decision
Understand what AODB, FIDS, BHS, PSS and RMS do, who owns each, and where integration risk lives, before scoping any airport programme
Languages
EN · AR

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The systems at work

One aircraft turnaround, read across the five systems that carry it

The quickest way to understand the landscape is to follow one flight through it. Read a column top to bottom to see every system touched at that moment; read a row across to see one system’s day.

  1. 01

    Inbound

    AODB — the operational record
    Updates the estimated arrival as the aircraft approaches.
    FIDS — the displays
    Shows the arrival and its belt to the people waiting.
    BHS — the baggage machinery
    Routes inbound bags to the belt the AODB assigned.
    PSS — the airline’s platform
    Tracks connecting passengers arriving on this aircraft.
    RMS — the allocator
    Assigns the stand, and reshuffles when the inbound slips.
  2. 02

    On the stand

    AODB — the operational record
    Records actual on-stand time; the billing clock starts here.
    FIDS — the displays
    Publishes check-in desks and any delay, straight from the AODB.
    BHS — the baggage machinery
    Accepts, screens and sorts outbound bags by flight.
    PSS — the airline’s platform
    Runs check-in and issues the boarding passes.
    RMS — the allocator
    Allocates the gate, desks and belt from the day’s plan.
  3. 03

    Boarding

    AODB — the operational record
    Holds the confirmed gate and boarding state every system reads.
    FIDS — the displays
    Calls passengers to the gate; a stale screen here strands people.
    BHS — the baggage machinery
    Chases the late bag whose owner is boarding.
    PSS — the airline’s platform
    Boards each passenger and knows who is still missing.
    RMS — the allocator
    Rebalances gates when a delay collides two flights.
  4. 04

    Departure

    AODB — the operational record
    Closes the movement with actual off-block and airborne times.
    FIDS — the displays
    Flips the flight to departed and clears it from the boards.
    BHS — the baggage machinery
    Reconciles loaded bags against the manifest before doors close.
    PSS — the airline’s platform
    Closes the flight and finalises the passenger manifest.
    RMS — the allocator
    Releases the resources back into the plan for the next visit.

Every hand-off in this table is an interface somebody specified, built and now maintains. That is the landscape in one sentence.

Ownership

Who owns which airport system, and why your project must know

The systems divide by owner, and the division explains most programme friction. The operator typically owns the AODB, the FIDS, the RMS and the terminal infrastructure around them — they describe the building and its resources, which are the operator’s to manage. The BHS is usually the operator’s asset too, though it is often run day to day by a specialist maintainer under contract, which means two parties sign off anything that touches it. The PSS belongs to each airline: it holds reservations, check-in and boarding for that carrier’s passengers, usually as a service from one of a small number of global providers, and the airport does not control it at all. Ground handlers bring their own task and roster tools, contracted to airlines rather than to the airport.

Read a project through this lens before scoping it. A new dashboard drawing only on AODB and RMS data lives entirely inside the operator’s authority and can move at the operator’s pace. Anything needing passenger-level data crosses into PSS territory, where each airline must agree individually and the answer arrives on airline timescales. Anything touching the BHS inherits its safety and certification regime and its maintainer’s change windows. The most common planning error in airport programmes is a schedule that assumes the operator can simply decide — for systems the operator does not own.

The seams

The four seams where airport programmes actually come apart

Projects rarely fail inside a system; they fail where two systems must agree. These are the seams to inspect before signing anything, on any airport programme.

  1. 01

    The airline-record seam: PSS to AODB

    The airline’s system and the airport’s record describe the same flight from different sides, and they disagree — on times, on delay causes, on when boarding really closed. Any product showing both sources must decide whose figure wins and label it, or its users will spend their days arbitrating.

  2. 02

    The display-latency seam: AODB to FIDS and beyond

    Every consumer of the operational record — screens, apps, assistants — is only as current as its feed. The question that exposes a weak integration is simple: when a gate changes, how many seconds until each surface says so, and what does each show in between.

  3. 03

    The physical seam: where the BHS meets everything digital

    The baggage system is machinery with software attached, governed by safety regimes and maintained in physical downtime windows. Digital projects that treat it as another API discover that its change calendar is measured in months and its test environment is a building.

  4. 04

    The assumption seam: the RMS plan against the real day

    The allocator plans a tidy day; the day is never tidy. The seam is how fast reality — a late inbound, a closed stand — flows back into the plan, and whether the humans trust the replan enough to follow it. A perfect allocation engine fed yesterday’s truth allocates yesterday’s airport.

Before you sign

What sets the real price of touching an airport system, and what to ask its vendor

Licence fees are the visible fraction. The drivers below set the rest of the bill, and the questions that follow are the ones a non-specialist can ask any vendor, in any of the five categories, and learn the most from.

VariableEffect on priceWhy
How many interfaces the work crossesEach system boundary multiplies parties, specifications and test cyclesA change inside one system is an estimate; a change across two is a negotiation; across three it is a programme. Count the seams in the diagram above before believing any schedule.
Whose consent the data needsData owned by airlines or handlers arrives at their pace, not yoursOperator-owned data can be used by decision; airline and handler data must be negotiated party by party, and that calendar — not the engineering — often sets the critical path.
How live the operation must stayParallel running, night windows and rollback rehearsals are paid workA terminal never closes for a project, so every cutover is engineered around a running operation. Quotes that skip this cost are not cheaper; they are incomplete.

Ask any supplier quoting this

  • For an AODB: which of your interfaces are standard product, and which were built once for another customer and never productised?
  • For a FIDS: when the operational record changes, what is the worst-case delay to the furthest screen, and how would we measure it ourselves?
  • For a BHS: what does the digital side report when the machinery falls back to manual sortation, and how do the two records reconcile afterwards?
  • For PSS access: exactly which passenger data fields will the airline’s host release to the airport, under what agreement, and how long has that approval taken elsewhere?
  • For an RMS: show us the day the plan broke — how the system behaved through a real disruption, and what the human controllers did with its replans.
  • For every category: if we leave you in ten years, what do we take with us — the data, the configurations, the interface definitions — and in what format?

Using this guide

Where the reference ends and the advisory work begins

This guide gives you the vocabulary and the map: what each system records, who owns it, where the seams are and what to ask. What it cannot give you is your airport — which of these systems you actually run, in which versions, joined by which interfaces, with which contracts expiring when. That mapping, and the vendor-neutral selection work that follows it, is a different exercise: it happens against your estate, with your operational staff in the room, and it is the subject of our airport technology consulting practice rather than of a reference page. Read this first; bring the questions it gives you to that work — or to any advisor you choose — and you will be a measurably harder client to oversell.

Common questions

What buyers ask

What does a resource management system actually decide in an airport?+

The RMS turns the flight schedule into an allocation of the airport’s scarce physical assets: which aircraft gets which stand, which flight boards from which gate, which check-in desks and baggage belts serve it, and — in fuller deployments — which staff and equipment attend the turnaround. Its plan is drafted in advance from the season’s schedule and then rewritten all day as reality intervenes: a late inbound cascades into stand conflicts, and the RMS proposes the reshuffle. Two things follow for any programme. Its output quality depends entirely on how fast the AODB feeds it the real situation, and its proposals only matter if the human controllers trust them — an RMS whose replans are quietly overridden on the radio is an expensive spreadsheet.

Why is the PSS owned by airlines when it runs inside the airport?+

Because the PSS manages the airline’s commercial relationship, not the airport’s building. It holds the reservation, the fare, the seat, the loyalty account and the boarding record — assets and liabilities of the carrier — and it follows the airline to every airport it flies to, usually as a hosted service from one of a few global providers. The airport supplies the counters, kiosks and networks the PSS is used on, which is why the boundary confuses people: the screen is in the terminal, but the system behind it answers to the airline. For programmes, the consequence is that passenger-level data — who is on board, who has checked in, who is still landside — can only reach an airport system through agreements struck with each airline, and multi-airline terminals must repeat that negotiation per carrier. Budgeting that negotiation as a line item, with time on the clock, is the mark of a plan written by someone who has done this before.

Do airport systems from different vendors exchange data out of the box?+

Assume no, and be pleasantly surprised occasionally. The industry has genuine standards for parts of the landscape — messaging conventions for flight and baggage information have existed for decades, and newer data-exchange specifications are gaining ground — but standards define the vocabulary, not the conversation. Two products can both support the same standard and still disagree on which optional fields they fill, how they encode a delay reason, or how often they publish. In practice every join in an airport estate gets an interface project: specification, mapping, testing against real operational days, and an owner for its maintenance afterwards. This is not vendor malice; it is what happens when specialised systems from different decades meet. The practical rule for budgeting is the one this guide keeps repeating: the systems are the visible cost, the joins are the recurring one.

A reader leaves able to name the five systems, say who owns each at their airport, and point at the seam their next programme will cross — or asks us to map it with them.

Map your estate with us