Is ISO 22400 applicable to aerospace and MRO operations?

Yes, ISO 22400 is applicable to aerospace and MRO operations, but only as a generic KPI and terminology framework. It is not aerospace-specific, does not address regulatory or airworthiness requirements directly, and does not replace AS9100, customer scorecards, or OEM/MRO contract KPIs.

What ISO 22400 actually covers

ISO 22400 defines a set of manufacturing KPIs, data elements, and terminology for production operations. In aerospace and MRO, it can help by:

• Providing consistent definitions for metrics such as OEE, availability, performance, and utilization.
• Clarifying what should be measured at equipment, line, or cell level in a plant or hangar.
• Creating a shared language between operations, IT, and vendors when designing MES/MRO dashboards or performance reporting.

However, ISO 22400 was written to be sector-agnostic. It does not incorporate aerospace-specific concepts like airworthiness release, maintenance program compliance, configuration control of serialized assets, or regulatory reporting obligations.

Using ISO 22400 in aerospace production

In new build aerospace manufacturing, ISO 22400 can be used to standardize line and cell KPIs, provided you account for high-mix, low-volume realities:

• OEE in HMLV: Classical OEE assumes repeatable, short-cycle production. For aerospace, you will usually need to adapt OEE and related metrics to longer cycle times, complex routings, and shared resources.
• Data capture: ISO 22400 presumes reasonably clean, structured event data (start/stop, downtime codes, speed loss). Legacy machines, manual work centers, and paper-based travelers will limit how much of ISO 22400 you can implement without additional digitization and integration.
• System boundaries: In brownfield plants, OEE and availability signals may be split across MES, SCADA, machine controllers, and manual logs. Aligning these to ISO 22400 definitions requires careful mapping, interface design, and change control.
• Compliance alignment: The standard does not define how metrics should be used within AS9100, internal audit programs, or customer surveillance. You still need your own procedures describing which metrics are “for information” and which drive formal corrective action.

Using ISO 22400 in MRO and depot environments

For MRO and depot-level maintenance, ISO 22400 is partially applicable but needs careful interpretation:

• Repair vs production: ISO 22400 assumes relatively predictable production sequences. MRO work scopes can change mid-visit, and findings can significantly alter routing, which makes classic OEE and cycle-time metrics less straightforward.
• Capacity and turnaround: Some ISO 22400 concepts (availability, service level, queue times) can support turnaround time, bay utilization, and asset induction planning, particularly at the work-center or resource-group level.
• Serialized assets: In MRO, traceability is centered on tail numbers, serials, and configuration states. ISO 22400 does not define how KPI data should link to those records, so you must design that linkage in your MRO system, MES, or ERP.
• Regulator expectations: Aviation authorities focus on maintenance control, records, and compliance, not direct adherence to ISO 22400 KPIs. You can use ISO 22400 internally, but it will not, by itself, satisfy regulatory performance-reporting obligations.

How ISO 22400 coexists with existing systems

In most aerospace and MRO operations, you will not deploy ISO 22400 as a stand-alone program. Instead, you use it as a reference model that sits on top of existing systems and processes:

• MES/ERP/MRO tools: Many systems already implement some notion of OEE, utilization, or downtime. Aligning these to ISO 22400 usually involves mapping fields and re-labelling or redefining some metrics, not replacing the systems themselves.
• Reporting and BI layers: Implementing ISO 22400 is often easiest in the analytics layer, where you can build KPI calculations that reconcile data from multiple systems without ripping out validated MES or MRO platforms.
• Validation and change control: In regulated environments, changing KPI definitions, screen labels, or reports that inform decisions can trigger validation, re-training, and documentation updates. Adopting ISO 22400 terminology should be managed through established change control.

Attempting a full replacement of existing KPI schemes and reporting with pure ISO 22400 definitions in one step usually fails in aerospace and MRO because:

• Operational teams are tightly coupled to current KPIs used in contracts, SLAs, and executive reviews.
• System reconfiguration and revalidation costs are high, especially for qualified MES or MRO solutions.
• Downtime windows to change data collection and HMI logic are constrained.
• Historical comparisons and long-term trend lines must be preserved for audits and investigations.

Practical way to use ISO 22400 in aerospace and MRO

A pragmatic approach is to treat ISO 22400 as a harmonization guide rather than a prescription:

1. Inventory your current KPIs and their calculations across MES, MRO, ERP, and BI tools.
2. Map each critical KPI to the closest ISO 22400 equivalent, noting where your definition must differ due to aerospace or MRO realities.
3. Standardize terminology where it does not conflict with contractual or regulatory language.
4. Gradually adjust new dashboards, pilots, and greenfield lines to align more closely with ISO 22400, keeping legacy definitions where they are embedded in customer agreements.
5. Document the rationale for any deviations and keep this traceable for audits, internal training, and vendor onboarding.

Used this way, ISO 22400 can improve clarity and comparability of operational metrics without forcing a disruptive overhaul of existing systems or risking regulatory or contractual misalignment.