OEE for airport ground equipment is often implemented on a false assumption: that an aviation-industry standard analogous to SEMI E79 (semiconductors) or ISO 22400 (manufacturing) already defines how to calculate OEE for GSE. The truth is the opposite: a review of the entire IATA ecosystem — the Airport Handling Manual, Ground Operations Manual, ISAGO, the GSE program, the Enhanced GSE Recognition Program — finds no standard or framework defining an OEE-style uptime/availability/performance metric for Ground Support Equipment (GSE) or Baggage Handling Systems (BHS).
This finding has been confirmed across two independent research passes — it isn't a gap from insufficiently deep searching. IATA's focus for GSE governance is safety and collision prevention — "GSE causes up to 40% of total global aircraft ground damage" — not a quantitative performance framework. This means anyone claiming to have a "standard aviation-industry OEE formula" is either inventing something that doesn't exist, or applying a manufacturing formula wholesale to a completely different context.
Why the manufacturing OEE formula doesn't transfer to GSE
The standard OEE formula (Availability × Performance × Quality) was designed for a continuous production line running at a fixed cadence. Airport ground equipment operates entirely differently: demand depends directly on airline departure/arrival peak windows. During off-peak hours, most of the GSE fleet sits idle — not because the equipment is bad, but simply because there are no flights to serve.
Applying the formula as-is drags down the Performance component during off-peak windows, even when the technical team maintains the equipment perfectly and it's 100% ready. The result is a misleading composite OEE number: it can't distinguish "the equipment is broken" from "the equipment is fine but has no work by the nature of the flight schedule." On top of that, manufacturing's definition of "Quality" (defect rate on a line) is nearly meaningless applied to a single ground power unit or de-icing truck.
A practical measurement framework: separate Uptime and Utilization instead of a combined OEE
Instead of forcing a standard that doesn't exist, real industry practice (per Umbrex Consulting's ground-operations overview) measures two fully separate technical metrics, not collapsed into one score:
GSE Uptime (%) — the asset's technical availability rate, reflecting the quality of preventive maintenance and repair. Measured from when a tool generates an unplanned repair ticket to when it's certified and returned to ready status. This metric belongs to the technical/CMMS team.
GSE Utilization (%) — the actual usage rate of equipment against total technically-available time, reflecting dispatch and resource-allocation efficiency. This metric belongs to the operations/dispatch team.
OEE for airport ground equipment: why separation makes more sense
Reason 1 — Clear accountability, impossible with a single combined score
Separating the two metrics gives management a precise diagnostic tool: if Uptime is low but Utilization is high, the problem is maintenance quality (CMMS/technical team's responsibility). If Uptime is high but Utilization is low, the problem is operational dispatch or over-purchasing equipment (dispatch/ERP's responsibility). A combined OEE score erases exactly this distinction — and that's precisely why a unified OEE standard doesn't fit GSE, not because the industry lacks measurement tools.
Reason 2 — Flight-schedule-driven load variability is a structural trait, not an anomaly to "fix"
In manufacturing, idle equipment is an anomaly worth investigating. At an airport, GSE sitting idle between peak windows is completely normal — that's the nature of flight-schedule demand, not an operational failure. A framework that treats "not running" as a loss identical to manufacturing will keep flagging problems that don't exist.
Reason 3 — The "quality" of a ground-service cycle is a coordination outcome, not a single tool's attribute
A successful aircraft turnaround is the coordinated outcome of dozens of different pieces of equipment and people — it can't be reduced to a "defect rate" for one belt loader or tug. Forcing the quality of the entire turnaround chain into the OEE formula of a single mechanical tool creates data overlap and fails to pinpoint where the real problem lives.
Illustrative scenario: when a combined OEE score hides the real issue
This is an illustrative scenario for a common type of problem in the industry, not a specific case from any named airport: a GSE management team tries applying a manufacturing-style combined OEE score to its baggage-cart fleet, and notices the score is consistently low during midday windows. Management initially concludes, incorrectly, that the maintenance team is underperforming. After splitting the report into Uptime (still very high, showing the technical team maintains equipment well) and Utilization (low at midday simply because there are fewer flights), the real issue becomes clear: it's not poor maintenance — the fleet was over-purchased relative to actual flight-schedule demand, a dispatch/ERP decision, not a technical one.
Reference table: metric — what it measures — owned by — when to use
| Metric | What it measures | Owned by | When to use |
|---|---|---|---|
| GSE Uptime (%) | Technical reliability, maintenance quality | Technical team/CMMS | Assessing preventive maintenance and repair effectiveness |
| GSE Utilization (%) | Dispatch efficiency, resource allocation | Operations team/ERP | Assessing CAPEX purchasing decisions, equipment dispatch |
| Manufacturing-style combined OEE | Doesn't fit GSE's operational profile | — | Not recommended for GSE as-is |
Conclusion
"The problem isn't that an OEE standard for airport ground equipment hasn't been found yet — the problem is that it doesn't exist, and a separated Uptime/Utilization framework fits how GSE actually operates far better."
Four things worth doing this week if you're evaluating or running a GSE performance-measurement system:
- Stop searching for a "standard aviation OEE" that doesn't exist — switch to measuring Uptime and Utilization separately.
- When Uptime is low, investigate maintenance quality/CMMS first; when Utilization is low, investigate purchasing decisions/dispatch first.
- Don't treat GSE idle time during off-peak windows as a "loss" to fix — it's a structural trait of flight-schedule demand.
- Be skeptical of any source (especially a software vendor's blog or sales content) claiming to have a "standard aviation-industry OEE formula" — per official IATA sources reviewed, that standard doesn't exist.