ISO 22400 is not a primary or widely mandated standard in aerospace regulations. It is an ISO standard family focused on manufacturing KPIs (including OEE) for automated systems, not an aviation-safety or airworthiness standard.
How ISO 22400 is typically viewed in aerospace
In practice:
- Major aerospace regulatory frameworks (e.g. EASA, FAA regulations) and the AS/EN/JISQ 9100 series do not require or explicitly endorse ISO 22400.
- Some aerospace and defense manufacturers use ISO 22400 internally to structure OEE and related metrics, but this is an operations choice, not a regulatory mandate.
- Prime contractors and Tier 1s may recognize it as a reference for metric definitions, but customer contracts more often specify their own KPI definitions or data formats.
Where ISO 22400 is used, it is usually positioned as:
- A reference model for KPI terminology and calculation rules.
- A way to support consistency across plants and vendors when discussing OEE, availability, and performance metrics.
- A supporting standard in IT/OT integration and MES projects, not in type certification, airworthiness, or safety cases.
Relationship to AS9100 and aerospace expectations
AS9100 and related standards require you to define, monitor, and improve processes using appropriate performance indicators, but they do not prescribe ISO 22400 or any specific OEE formula.
If you adopt ISO 22400 in an aerospace environment, you typically need to:
- Document the KPI definitions (e.g. how you calculate availability, performance, and quality rates) within your QMS or operations procedures.
- Show traceability from those metrics to risk, quality, and delivery requirements, including how they support AS9100 clause requirements for performance monitoring and improvement.
- Align with customer and program requirements when they specify different KPI definitions or reporting structures.
Use in brownfield, regulated plants
In existing aerospace plants with mixed MES/ERP/QMS stacks and long-qualified equipment, ISO 22400 usually appears as a guideline for harmonizing metrics, not as a driver for system replacement.
Typical patterns:
- Coexistence with legacy metrics: Plants often keep historical KPI definitions for trending and contractual reasons, and map them to ISO 22400-based metrics where practical.
- Incremental adoption: Instead of a full overhaul, sites may standardize a subset of metrics (for example, how OEE is calculated) while leaving other legacy measures intact.
- Interface constraints: Existing MES/SCADA systems may not natively support ISO 22400 data structures. Any alignment usually depends on integration quality, data readiness, and available engineering capacity.
Trying to fully replace established KPI schemes or MES components solely to “be ISO 22400 compliant” often fails in aerospace-grade contexts because of:
- Qualification and validation burden on validated software and equipment.
- Downtime risk when touching core production or test systems.
- Integration complexity across multiple OEMs and internal systems.
- Change-control and traceability obligations that make sweeping metric changes hard to justify.
Regulatory and audit implications
Using ISO 22400:
- Does not provide any certification or compliance guarantee with aerospace regulations or the 9100-series.
- Will typically be viewed by auditors as one acceptable framework for defining and using operational metrics, if it is well documented, consistently applied, and aligned with risk and quality objectives.
- Requires the same change control, validation (where applicable), and data-governance rigor that applies to any change in metric definitions or reporting workflows.
In summary, ISO 22400 is recognized as a useful technical reference for manufacturing KPIs, but it is not a core aerospace regulatory standard. It can improve internal consistency if carefully mapped to existing QMS, contractual, and system constraints, but it should not be treated as a shortcut to regulatory compliance or audit outcomes.
