ISO 22400 does not define how PLM or QMS software should work, and it is not a plug-in or module. It is a framework for standardizing manufacturing KPIs and related data. In aerospace environments, it typically “interacts” with PLM and QMS through data models, interfaces, and how metrics are implemented in MES and analytics platforms that are connected to them.
What ISO 22400 actually provides
ISO 22400 defines:
- Common terminology for manufacturing KPIs (such as OEE and time elements like operating time and planned downtime).
- Logical data structures and relationships needed to compute those KPIs.
- Guidance on how to decompose metrics from enterprise level down to work centers and equipment.
It does not prescribe PLM processes, QMS workflows, or specific system architectures. Instead, it offers a reference model you can align your PLM, MES, ERP, QMS, and analytics implementations to.
Typical interaction with PLM in aerospace
PLM primarily owns product definitions, configurations, and changes (BOMs, routings or process plans, NC programs, work instructions, and configuration baselines). ISO 22400 interacts with PLM indirectly by defining how manufacturing performance is measured against those definitions.
In practice, you often see:
- Metric structures tied to PLM objects: ISO 22400 KPI definitions (e.g., OEE, NPT-related time categories) are broken down by part number, configuration, revision, or program as defined in PLM.
- Process plan alignment: PLM-originated routings and work instructions are used by MES as the basis for what “planned” production is. ISO 22400 defines how to classify time and output so that planned vs. actual is measured consistently.
- Change impact analysis: When PLM introduces a design or process change, ISO 22400-aligned KPIs give a consistent way to evaluate performance impact across plants, lines, and aircraft programs.
- Configuration-sensitive metrics: Aerospace programs often run multiple configurations in parallel. ISO 22400 helps standardize KPI calculation so that performance can be compared between configurations, provided configuration data from PLM is accurately propagated into MES/ERP.
This interaction depends heavily on how well PLM is integrated with MES and ERP. If routings, work centers, or part identifiers are inconsistent, ISO 22400 definitions can be implemented, but comparisons across assets and sites will be weak or misleading.
Typical interaction with QMS in aerospace
QMS manages nonconformances, deviations, concessions, corrective and preventive actions, audits, and quality records. ISO 22400 comes into play when you want to measure and compare quality-related performance using consistent metrics across operations.
Typical interactions include:
- Defect and rework metrics: Counts of nonconformances, rework time, and scrap can be structured using ISO 22400 time and quantity concepts. The QMS remains the system of record for events, while MES/analytics use ISO 22400 to standardize the metrics that reference those events.
- Cost of Poor Quality (COPQ-related) views: While ISO 22400 does not define COPQ, its time and quantity models can underpin COPQ calculations if QMS provides the classification of defect types and dispositions and ERP provides cost rates.
- CAPA effectiveness metrics: QMS tracks CAPA actions and closure. ISO 22400 metrics (for example, change in scrap rate or nonconformance rate) can be used to quantify whether a CAPA is improving performance in a comparable way across programs or plants.
- Audit and regulatory evidence: For regulated aerospace operations, ISO 22400-aligned metrics give a traceable definition of how KPIs are calculated, which can support consistent evidence packages, provided traceability to QMS records is maintained.
Again, the interaction is mostly conceptual and data-driven. ISO 22400 does not replace QMS functions and does not guarantee compliance. It helps make the metrics that reference QMS data more consistent and auditable across the enterprise.
Where ISO 22400 usually sits in the architecture
In a typical aerospace stack:
- PLM provides product and process definitions.
- MES orchestrates execution and collects detailed production and event data.
- QMS manages quality events, dispositions, and CAPA.
- ERP handles orders, inventory, and financials.
- Analytics/BI layer consumes data from these systems to produce KPIs.
ISO 22400 typically sits as a reference in the MES and analytics layer:
- MES maps events (start, stop, changeover, breakdown, quality hold) and quantities to ISO 22400 categories.
- Analytics or KPI engines implement ISO 22400 formulae to compute standardized metrics across lines, plants, and programs.
- PLM and QMS are linked through identifiers (part, configuration, order, nonconformance number) so that KPIs can be broken down by product and quality context.
This means that the practical “interaction” with PLM and QMS is a function of:
- Data model alignment across PLM, MES, QMS, and ERP.
- Integration quality (interfaces, middleware, timing, and error handling).
- Governance of master data (work centers, equipment IDs, defect codes, time category codes).
Without reasonably mature integrations, ISO 22400 will mostly exist on paper or within isolated reports, rather than becoming a cross-system standard.
Benefits and tradeoffs in aerospace environments
Potential benefits when ISO 22400 is applied thoughtfully include:
- Common KPI definitions: Programs, suppliers, and plants can talk about OEE, availability, performance, and quality in a consistent way, reducing debate about how numbers are calculated.
- Better cross-site benchmarking: Sites using different MES vendors or homegrown systems can still align KPI semantics, provided mapping is done carefully.
- Stronger traceability for metrics: Clear definitions and category models make it easier to show how a KPI was derived from PLM, MES, QMS, and ERP data.
Key tradeoffs and constraints include:
- Integration effort: Mapping legacy MES/QMS code sets and time categories to ISO 22400 is nontrivial. Plants often have local conventions that conflict with standard definitions.
- Change management: Operators, planners, and quality engineers may need to log events and categorize downtime differently. This can affect behavior and must be managed with training and governance.
- Historical comparability: Once you move to ISO 22400-aligned metrics, historical KPIs may no longer be directly comparable unless you re-baseline or reprocess historical data.
- Supplier alignment: Getting external shops or tier suppliers to adopt compatible KPI definitions can be slow and may require contract or data-exchange updates.
Brownfield and long-lifecycle realities
In aerospace, most plants are brownfield environments with mixed MES, PLM, QMS, and ERP stacks that have evolved over decades. Attempting to “fully replace” existing KPIs and systems with a clean ISO 22400 architecture in one step is usually risky because of:
- Qualification and validation burden: Changing KPI logic in validated systems can require revalidation, documentation updates, and sometimes customer approvals.
- Downtime risk: Big-bang KPI and data model changes can disrupt reporting needed for daily operations and customer or regulatory reporting.
- Integration complexity: MES, PLM, QMS, and ERP interfaces may embed metric-specific logic that must be untangled carefully.
- Traceability expectations: Programs and regulatory bodies may expect continuity of metrics for years; sudden breaks in definitions can undermine trend analysis.
Most aerospace organizations that use ISO 22400 successfully do so incrementally:
- Start by documenting current KPI definitions and mapping them to ISO 22400 concepts.
- Implement ISO 22400-aligned metrics in a limited scope (for example, one line or one program) using the existing PLM and QMS systems.
- Gradually standardize code sets and event categories as systems are upgraded or integrated.
- Maintain clear documentation so that auditors, customers, and internal teams understand when and how KPI definitions changed.
What ISO 22400 does not do
It is important to be explicit about what ISO 22400 does not provide:
- It does not make a PLM or QMS “compliant” or guarantee any regulatory or customer audit outcomes.
- It does not remove the need for system validation, change control, or configuration management.
- It does not solve poor data quality, inconsistent master data, or missing integrations on its own.
- It does not dictate specific vendor choices or architectures for PLM, QMS, or MES.
It is most useful as a common language and template for how metrics are defined and calculated across your existing aerospace PLM, MES, QMS, and ERP landscape.
