ISO 22400 and IEC 62264 address different but complementary aspects of manufacturing systems. In aerospace factories, they are typically used together rather than in competition.
What each standard covers
IEC 62264 (often aligned with ANSI/ISA-95) defines:
- A functional hierarchy of levels (0–4) from equipment and control up to business planning and logistics.
- Standard models for how ERP, MES, and control systems exchange information.
- A common language for describing where functions reside (e.g., Level 3 for MES-like activities).
ISO 22400 defines:
- Standardized manufacturing KPIs such as OEE, availability, performance, and quality metrics.
- How to structure and interpret these KPIs (input data, calculation logic, temporal aspects).
- Terminology and models for performance measurement across operations.
Put simply: IEC 62264 tells you where and between which levels functions and data flow; ISO 22400 tells you what performance indicators you can calculate from that data.
How ISO 22400 KPIs map onto IEC 62264 levels
There is no strict one-to-one mapping in the standards themselves, but in practice aerospace factories typically align KPIs with IEC 62264 levels as follows:
- Level 0/1 (process & equipment): Source data for ISO 22400 KPIs (machine states, counts, cycle times, alarms, scrap events). KPIs are not usually calculated here, but this level determines granularity and latency.
- Level 2 (area / cell control): Aggregated short-horizon metrics (e.g., cell OEE, micro-stoppage analysis) feeding Level 3. Some ISO 22400 metrics may be pre-aggregated or filtered here for performance reasons.
- Level 3 (manufacturing operations management / MES): The primary calculation and ownership layer for many ISO 22400 metrics such as OEE, availability, performance loss breakdowns, and order- or line-level KPIs aligned to shift, batch, and routing.
- Level 4 (ERP / business planning): Consumes ISO 22400 metrics coming from Level 3 for capacity planning, financial reporting, and supplier/contract KPIs. Occasionally, high-level KPIs (e.g., site OEE) are re-aggregated here, but the source-of-truth remains at Level 3.
In an aerospace MES context, you typically:
- Use IEC 62264 to define which activities, events, and data objects occur at which level.
- Use ISO 22400 to define the standardized KPIs derived from those activities and events.
- Attach each KPI to a level of responsibility (who calculates, who validates, who consumes).
Why this matters in regulated aerospace environments
In aerospace, metrics are not just for internal dashboards; they influence capacity commitments, cost models, and sometimes customer-facing performance. Combining IEC 62264 with ISO 22400 helps by:
- Clarifying ownership: IEC 62264 levels clarify whether the MES, ERP, or control layer is the authoritative source for data feeding an ISO 22400 KPI.
- Supporting traceability: When a performance number is challenged (e.g., during an AS9100 audit or customer review), you can trace it back through the hierarchy to tagged events and equipment data.
- Managing change control: KPI definitions (ISO 22400) and data interfaces (IEC 62264) are both configuration-controlled so changes are documented, validated, and auditable.
- Avoiding double counting: A clear level-by-level model reduces the risk of ERP and MES computing overlapping or conflicting KPIs from the same events.
Dependencies and limitations in brownfield aerospace factories
The practical value of combining ISO 22400 with IEC 62264 depends heavily on your current environment:
- Legacy equipment: Older machines without native connectivity may limit the precision of ISO 22400 KPIs. You may rely on manual data entry or retrofit data collection, which increases uncertainty and validation burden.
- Mixed vendor MES/ERP/SCADA: Different vendors often implement IEC 62264 concepts only partially. Mappings for event types and equipment states may not line up cleanly with ISO 22400 data requirements.
- Data quality and timing: ISO 22400 metrics are sensitive to timing, state changes, and event completeness. In loosely integrated brownfield stacks, misaligned timestamps or missing state transitions can materially distort OEE and related KPIs.
- Validation and qualification: In aerospace, using ISO 22400 KPIs for decisions that affect commitments or compliance often requires documented validation of calculations, interfaces, and data transformations. This is non-trivial and must be managed through formal change control.
It is usually more successful to layer ISO 22400 on top of existing IEC 62264-aligned structures than to attempt a complete system replacement purely to get “clean” KPI hierarchies. Full replacement carries downtime, requalification, and integration risks that are often unacceptable mid-program.
Practical implementation approach
For aerospace factories, a pragmatic way to relate ISO 22400 to IEC 62264 is:
- Document your current IEC 62264 mapping: Identify which systems and functions sit at each level (ERP, PLM, QMS, MES, SCADA, machine controllers).
- Select a limited ISO 22400 KPI set: Start with a small, high-value subset (e.g., availability, performance, quality rate, OEE) and define them formally.
- Map each KPI to a level and a system of record: Decide where calculations occur (typically Level 3) and which lower-level events they depend on.
- Define data contracts and interfaces: Using IEC 62264 models, specify which events and states must be exchanged across levels to support each KPI, with clear semantics.
- Validate, then scale: Pilot on a line or value stream, validate results against ground truth, then scale to more cells and sites with controlled changes.
Done this way, ISO 22400 becomes your common language for “what performance means,” and IEC 62264 remains your common language for “where that performance data lives and flows” within the aerospace manufacturing stack.
