Techbanq

Aviation · advisory

Airport systems are bought one at a time and fail at the joins

Every airport runs a portfolio of specialised systems — the operational database, the flight displays, the baggage system, passenger processing — each excellent alone and each bought from a different vendor. The expensive failures happen between them, which is why the advice on how they fit together should come from someone with nothing in the portfolio to sell.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The landscape

What the four-letter airport systems actually do

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

The vocabulary is the first barrier, so here it is plainly. The AODB — the airport operational database — is the single record of every flight movement: which aircraft, which stand, which gate, which times. FIDS — the flight information display system — is what passengers and staff read on the screens, and it is only ever as accurate as the AODB feeding it. The BHS — the baggage handling system — is the physical machinery of belts, sorters and screening that moves bags from check-in to aircraft and back. The PSS — the passenger service system — is the airline-side platform holding reservations, check-in and boarding. None of these is optional, none replaces another, and almost every operational question an airport asks touches at least two of them.

That is why the perennial cost in airport technology is not any one system but the joins between them. A stand change entered in the AODB must reach the displays, the baggage sorter, the ground handler and the airline within seconds, through interfaces that were often specified by different vendors in different decades. Advisory work that treats each procurement in isolation prices the licences correctly and misses the largest line on the eventual invoice.

The estate

How an airport systems estate groups when you map it honestly

Grouped by what each layer is for, not by vendor brochure category. The point of the map is to make the interfaces between the groups visible, because that is where budgets and timelines are actually decided.

The operational record

  • AODB
  • Resource management
  • Billing feed
  • Slot coordination data

The passenger-facing layer

  • FIDS
  • Wayfinding
  • Self-service kiosks
  • Mobile notifications

The physical machinery

  • BHS
  • Boarding-bridge control
  • Access control
  • CCTV estate

The airline-side platforms

  • PSS
  • Departure control
  • Load control
  • Crew systems

Selection

Running a systems selection no vendor is steering

A selection goes wrong at the requirements stage far more often than at the scoring stage. This is the sequence we advise, and the order is the point.

STAGE 01

Write requirements from your operation, not from brochures

Requirements copied from vendor material describe the product that will win. Requirements traced from your own irregular days — the diversion, the stand shortage, the belt failure — describe what the airport needs. A requirements set a vendor cannot have pre-written the answers to.

STAGE 02

Price the integration and the exit, not just the licence

Every candidate is scored on what it costs to connect to the AODB and the systems around it, and on what it would cost to leave in ten years — because both are real prices the licence figure hides. A comparison on lifetime cost rather than on day-one cost.

STAGE 03

Test against your irregular day, not the demo script

A scripted demo shows the product at its best. A trial against one of your own disrupted days — real flight data, a stand swap, a delayed inbound — shows the product where you will actually need it. Evidence from your operation, not the vendor’s.

STAGE 04

Phase the introduction around live operations

The terminal does not close for the project, so the plan runs old and new in parallel, cuts over in stages the operation can absorb, and keeps a way back at each stage. A rollout the duty manager signed off, not just the project board.

Our role

What an airport technology advisor should refuse to decide

  1. 01

    The map before the shortlist

    We document what you run today and how it connects before any product enters the discussion, because a shortlist built on an unmapped estate inherits every assumption in it.

  2. 02

    Neutral in the selection

    We take no commission, resell nothing and hold no reseller agreements with airport system vendors, so the recommendation costs us nothing to change when the evidence changes.

  3. 03

    Engineering judgement on the joins

    As a firm that builds and integrates software, we read interface specifications as engineers rather than as procurers — which is where the optimistic line in a vendor response gets caught.

The choice of vendor, the commercial negotiation and anything requiring the aviation authority’s approval stay with the operator and the authority; we bring the map, the evidence and the engineering reading that make those decisions informed ones.

Common questions

What buyers ask

What is an AODB, and why does every other airport system depend on it?+

The AODB is the airport’s single operational record: every flight, its aircraft, stand, gate, belt and timings, updated as the day actually unfolds. Everything else reads from it — the displays show its times, the resource system allocates against its schedule, the billing runs on its recorded movements. That is why AODB data quality is the quiet foundation of the whole estate: a wrong time in the AODB becomes a wrong gate on a screen, a mis-sorted bag and a disputed invoice, all from one entry. It is also why we advise treating any project that touches the AODB with more caution than its budget line suggests.

Can an airport introduce new systems without closing part of the terminal?+

Yes, and for an operating airport it is the only defensible plan. The method is parallel running and staged cutover: the new system is fed real operational data alongside the old one, proves itself against live days without being relied on, then takes over one function or one area at a time with the old system still able to take the load back. What makes it work is operational involvement from the start — the duty managers who will live with the system rehearse the cutover and hold the authority to call it off. What makes it fail is treating go-live as a project date rather than an operational decision.

Do you resell airport systems or take commissions from vendors?+

No. We hold no reseller agreements with airport system vendors and take no commission on any selection outcome, because the value of the advice depends on it costing us nothing when the evidence points away from a vendor we know well. Where we do have relevant self-interest — we build custom software and integrations, so a recommendation to build rather than buy could favour us — we say so explicitly in the recommendation, and we structure selections so a build option is scored by the same criteria as the products it competes with.

A working session that maps your current systems estate and its integration points before any product name enters the conversation.

Walk us through your estate