CMMS for airport ground equipment must manage two asset classes with completely different compliance logic: Ground Support Equipment (GSE — tugs, belt loaders, ground power units, de-icing trucks) and Passenger Boarding Bridges (PBB). GSE is governed by IATA mainly through a safety/collision lens, while PBB has its own dedicated European technical standard specifying detailed maintenance requirements. A CMMS that doesn't distinguish these two logics correctly ends up applying the wrong process to each equipment type.
The real gap isn't a lack of monitoring technology — it's the space between a critical technical event (software upgrade, replacement of a critical component) and the mandatory safety confirmation that should follow, which gets easy to skip under continuous operational pressure.
AHM Chapter 9 and ISAGO: two different layers of GSE governance
IATA's Airport Handling Manual (AHM) Chapter 9 is IATA's sole official touchpoint for GSE technical specifications — covering autonomous GSE, nose-gear towbar tractors, and equipment-aircraft compatibility requirements. Critically: AHM Chapter 9 defines no reliability/availability metric whatsoever — it's purely a technical and operational-safety specification, not a performance framework.
ISAGO (IATA Safety Audit for Ground Operations) is IATA's global SMS-based safety audit program, checking compliance with IGOM, AHM Chapter 6, ICHM, and ICAO Annex 19 across 7 disciplines: Organization & Management, Training, Passenger, Baggage, Ramp, Load Control, Cargo & Mail. ISAGO is a process/safety audit — there's no eighth discipline measuring equipment reliability via MTBF or uptime.
IATA also states plainly: GSE causes up to 40% of total global aircraft ground damage — which is why IATA's focus is a collision-prevention program (the Enhanced GSE Recognition Program, folded into ISAGO station audits from 2025) rather than a quantitative performance framework.
CMMS for airport ground equipment: 3 real audit scenarios it must block
Scenario 1 — Skipping the safety check after a PBB software update
ACI Asia-Pacific (Guidelines on the Safe Operations of Passenger Boarding Bridge) is explicit: maintenance checks must be conducted right after any PBB operating-software upgrade or critical hardware component change. If the CMMS only logs "software updated" without automatically locking the tool into a pending-verification state until technical confirmation exists, the bridge can keep serving passengers while the risk of new-firmware conflicts (potentially affecting the auto-leveling system) hasn't been ruled out.
Scenario 2 — A technician working from outdated OEM maintenance documentation
BS EN 12312-4:2024 (a CEN European standard, also a British Standard) specifies requirements to minimize risk during PBB commissioning, operation, and maintenance. OEMs regularly issue technical revisions (for example, updated torque specifications for periodic bolt checks). If the CMMS still lets technicians work from an old printed checklist instead of requiring access to the latest OEM documentation through the system, the risk of tightening bolts outside spec — leading to metal fatigue at load-bearing joints — goes undetected until something fails.
Scenario 3 — Skipping the pre-use inspection on GSE
Before every shift, GSE needs a visual check of basic safety items (hydraulic fluid leaks, brake system, anti-collision sensors). If the CMMS doesn't hard-block engine start until the pre-use checklist is fully signed off, a tool with an abnormal sign (like a leak affecting brake pressure) can still be brought into operation near an approaching aircraft.
The technical lens: why an automatic "Red-tag" beats a manual process
What all three scenarios share: each has ONE mandatory confirmation step that people, under continuous operational pressure (an aircraft waiting, a packed flight schedule), have a real incentive to skip or defer. Effective ground-equipment CMMS at an airport doesn't rely on reminding technicians to comply voluntarily — it relies on a hard lock: the tool automatically flips to "Red-tag"/"Out of Service" the moment a critical condition occurs (software upgrade, a failed pre-use item), and can only be released again after a signed technical confirmation.
Illustrative scenario: closing the gap between a technical event and safety confirmation
This is an illustrative scenario for a common type of problem in the industry, not a specific case from any named airport: a passenger boarding bridge just received a new control-software update, but because the flight schedule is packed, the technical team hasn't yet filed the post-upgrade safety check — meanwhile, the bridge keeps connecting to serve several consecutive flights. After the CMMS is configured to automatically lock the tool into "pending verification" the moment it logs a software-update event — blocking any further connection command until an engineer signs off on having checked the safety sensors — this gap can no longer occur.
Reference table: ground-equipment CMMS item — requirement — evidence — system link
| Item | Compliance requirement | Evidence needed | System link |
|---|---|---|---|
| GSE technical specification | AHM Chapter 9 | Equipment-aircraft compatibility record, torque limits | Cross-checked when assigning equipment to a specific aircraft type |
| Process safety audit | ISAGO (7 disciplines) | Compliance checklist against IGOM/AHM Ch.6/ICHM | Synced with training records and operating procedures |
| PBB check after a change | ACI Guidelines + BS EN 12312-4:2024 | Post-upgrade/component-change verification ticket | Hard lock until technical confirmation exists |
| OEM maintenance documentation | BS EN 12312-4:2024 | Latest OEM document version, no outdated printed copies | Digital document library tied to asset ID |
| GSE pre-use inspection | Standard industry safety practice | Signed-off pre-shift checklist | Blocks startup when a safety item fails |
Conclusion
"A good CMMS for airport ground equipment isn't the one that reminds technicians to check — it's the one that never lets equipment run before a mandatory check is complete."
Four things worth doing this week if you're evaluating or running a CMMS for airport ground equipment:
- Check whether the CMMS automatically locks a PBB into "pending verification" right after any software update, or relies on a technician to file the ticket themselves.
- Confirm OEM maintenance documentation is accessed online from the latest version, with no outdated printed checklists still in circulation.
- Review the GSE pre-use inspection mechanism: does it hard-block startup when a safety item isn't signed off, or only log it after the tool is already running?
- Clearly separate in the system which items belong to safety/audit governance (ISAGO) and which belong to equipment technical specification (AHM/BS EN 12312-4) — avoid applying the wrong process to each.