ISO 22400 does not prescribe a fixed organizational hierarchy. Instead, it defines manufacturing KPIs and related data structures that can be applied at multiple levels of an organization (equipment, line, area, plant, enterprise). How those levels are defined and connected is primarily left to your internal modeling and supporting standards such as ISA‑95.
Scope of ISO 22400
The ISO 22400 series focuses on:
- Standardized definitions of manufacturing KPIs and basic indicators.
- Formal descriptions of input data elements and calculation rules.
- Information models so that systems can exchange and interpret KPI-related data consistently.
It assumes that KPIs may be applied at different organizational or technical levels, but it does not mandate what those levels are for your site.
Relation to organizational levels (equipment, line, plant, enterprise)
In practice, ISO 22400 KPIs can be scoped to different levels such as:
- Equipment or cell level: e.g., OEE, availability, speed loss for a specific machine or cell.
- Line or workcenter level: aggregated KPIs across multiple machines or stations.
- Area or value stream level: groups of lines or process areas.
- Plant level: consolidated metrics for an entire site.
- Enterprise or multi-site level: comparison and roll-up across several plants.
ISO 22400 allows these applications by defining KPIs and their required data, but it does not define exactly how you roll up from equipment to plant or enterprise. Those aggregation rules are an implementation responsibility and must be documented, validated, and controlled, especially in regulated environments.
Use alongside ISA‑95 (recommended in brownfield environments)
Most regulated, brownfield environments already use some variant of ISA‑95 levels (e.g., Level 0–4) or vendor-specific equivalents. A common and practical pattern is:
- Use ISA‑95 (or existing MES/ERP models) to define organizational and functional levels (equipment, work centers, areas, sites, enterprise).
- Use ISO 22400 to standardize KPI definitions, input data semantics, and naming.
- Explicitly map each KPI instance to the level where it is applied (for example: “OEE@WorkCenter_123”, “Availability@Site_A”).
This coexistence approach avoids a full replacement of existing level definitions, which is rarely practical in validated, long-lifecycle plants due to the qualification burden, downtime risk, integration debt, and need to preserve historical comparability.
Aggregation and traceability considerations
ISO 22400 assumes that a KPI with a clear definition can be applied at multiple levels, but it does not dictate:
- How to handle partial data (e.g., missing machine signals in one line).
- How to weight different resources during aggregation (e.g., bottleneck vs non-bottleneck machines).
- How to align time bases across systems (shift, batch, calendar, campaign).
In regulated environments, you should:
- Define level-specific KPI instances: e.g., “Line OEE is the production-weighted aggregation of equipment OEE over the defined shift window.”
- Document calculation rules and data lineage: including source systems (MES, historian, ERP), filters (planned vs unplanned downtime), and time alignment rules.
- Validate aggregation logic: confirm that enterprise- or plant-level KPIs are reproducible and correctly derived from lower-level data, with appropriate change control.
- Preserve historical comparability: if KPI scope or level definitions change, maintain versioning, effective dates, and clear labeling to avoid misleading trend analysis.
Brownfield implementation realities
When applying ISO 22400 into existing MES/ERP/QMS stacks:
- Expect mixed level models: different plants may use different notions of “line,” “area,” or “value stream.” ISO 22400 does not resolve that; it only standardizes the KPI semantics.
- Avoid big-bang hierarchy redesign: rewriting organizational levels across MES, SCADA, historian, and ERP is high risk and often unjustified. Instead, map existing structures to a consistent KPI catalog and document exceptions.
- Use a metadata layer: define a central KPI catalog that references ISO 22400 definitions and links each KPI instance to its organizational level and source data in the brownfield stack.
Constraints and limits of ISO 22400 for organizational levels
In summary, ISO 22400:
- Does provide: standardized KPI names, definitions, and input data models that are reusable across equipment, line, plant, and enterprise levels.
- Does not provide: a mandatory organizational hierarchy, detailed rules for aggregation between levels, or governance mechanisms for KPI ownership and approval.
You will still need internal standards (often building on ISA‑95 and existing MES data structures) to define organizational levels, assign KPIs to those levels, and formalize cross-level aggregation in a way that is validated, traceable, and compatible with your legacy systems.
