An independent diagnostic framework · v1.0
Changi Airport put driverless baggage tractors into live airside service in January 2026, after nearly a year of trials and more than 5,000 test trips, with 24 vehicles planned by 2027. That is an operation, not a demonstration.
Most airports could not follow tomorrow. Not because the technology is unavailable — increasingly it is off the shelf — but because the airport itself is not yet a viable operating environment for it.
Free · about 10 minutes · scored report at the end · no commercial data required
The diagnosis
Having looked closely at why airport automation programmes stall, the pattern is remarkably consistent — and it is almost never the machine. It is the environment the machine was dropped into.
The apron was never mapped to survey grade. An autonomous vehicle navigates against a map. CAD drawings and stand plans are not one.
Positioning is accurate to five metres. Autonomy needs centimetres, in rain, at night, next to a moving aircraft.
The safety case has no author. Nobody in the building has written one for an autonomous system, so the vendor writes it — which makes it a liability rather than an asset.
The regulator has no precedent and no one opened the conversation early enough for one to be created.
The unions found out when the vendor arrived. Sequence, here, is the entire game.
Nobody owns the gap between "the pilot worked" and "this is now an operation." So nothing crosses it.
The failure state, named
A portfolio of trials, most of which technically worked, none of which became an operation. It happens because each pilot had to build its own connectivity, its own positioning fix, its own integration and its own safety argument — so the third project cost roughly what the first one cost. In a real platform, each deployment is cheaper than the last. When your marginal cost is flat, you don't have a platform. You have unrelated projects sharing a budget line.
The framework
Four operational domains describe where physical AI actually lands. Two enabling domains decide whether anything that lands there ever scales. The split is the framework's argument, and the weighting is deliberate.
Four operational domains
Apron mapping, GSE telematics, turnaround capture, AV operating envelopes, ramp safety data.
Robot-traversable buildings, flow sensing, service robots, PRM automation, checkpoint automation.
BHS data openness, robotic handling, bag-level tracking, cargo automation, inter-facility transport.
Asset registers, drone operations, automated FOD detection, predictive maintenance, digital twin.
Two enabling domains
Airside network coverage, precision positioning, integration architecture, data governance, cyber-physical security.
Regulatory pathway, safety-case capability, labour engagement, funding and procurement, stage-gate ownership.
Two domains carrying 40% of a six-domain index is intentional. An autonomous machine is a networked, positioned, integrated, governed thing — remove any one and it does not operate. The consequence is that an airport with impressive deployments and weak foundations cannot score highly. That is the correct behaviour: such an airport is not ready, it is exposed.
How it works
Step one
Passenger volume, operating model, your role. Scale changes what "ready" means, so results are read against a reference band for airports of your size.
Step two
Five per domain, each with five concrete level descriptors rather than agree-or-disagree scales. You pick the one that describes your operation. No numbers to look up.
Step three
A weighted score, a maturity band, your enablement deficit, and a prioritised sequence of moves — printable, and written to survive a leadership meeting.
The report
Everything is generated from your own answers. Nothing is generic.
What each score means for your operation specifically, and the move your answers point to in each domain.
The gap between what you deploy and what supports it — the metric that distinguishes two airports with identical scores and opposite problems.
Ranked by weighted gap, not by lowest score. A level-1 criterion in a heavily weighted domain outranks a level-0 in a light one.
Matched to your maturity band. Order matters more than speed, and most airports attempt these in the wrong order.
Read against a reference band for airports of your scale — clearly labelled as a modelled expectation, not a survey mean.
Save it as a PDF and circulate it internally. It is designed to be read by people who were not in the room when you filled it in.
Who built this
Answer as your airport is today, not as it is planned to be. The index is only useful if it is honest.
Start the assessment →