No. ISO 22400 is a useful reference for manufacturing KPIs, but forcing every KPI to be ISO 22400-based is usually neither realistic nor desirable, especially in regulated, long-lifecycle environments.
Where ISO 22400 adds real value
ISO 22400 is strongest when you want consistency and comparability for core operations metrics across lines, plants, or sites, for example:
- Overall equipment effectiveness (OEE) and related availability, performance, and quality rates
- Utilization, load, and throughput measures for equipment and lines
- Standardized definitions of time categories (planned/unplanned downtime, changeover time, etc.)
Using ISO 22400 for these types of KPIs can help:
- Ensure a common vocabulary between OT, IT, engineering, quality, and finance
- Reduce arguments over definitions during audits, investigations, and performance reviews
- Simplify integration across MES, historians, and reporting tools by converging on standard data elements
Where strict ISO 22400 alignment breaks down
In regulated and complex operations, there are many important KPIs that do not map neatly to ISO 22400 definitions or require tailoring. Common examples include:
- Regulatory and quality KPIs such as batch release lead time, CAPA cycle time, deviation recurrence, and defect escape rates
- Product- and process-specific KPIs like first-pass yield by special process, qualification cycle time, or rework on critical characteristics
- Customer- and contract-driven KPIs such as on-time delivery definitions set by SLAs, or performance metrics linked to penalties/bonuses
- Safety and EHS KPIs that follow corporate standards or regulatory conventions rather than ISO 22400
- Legacy KPIs with long history where changing the definition would break trend comparability that management and regulators rely on
Trying to force these KPIs into ISO 22400 terminology can create confusion, weaken traceability to existing procedures, or misrepresent what the metric actually measures.
Practical approach: a layered KPI catalog
A more sustainable approach is to structure your KPI catalog in layers:
- Tier 1: ISO 22400-aligned KPIs where it fits cleanly
Define a core set of site-wide operations KPIs based on ISO 22400 (e.g., OEE, availability, performance, quality rate, production volume). Use the ISO terminology and calculation logic as the reference, with documented local clarifications where needed.
- Tier 2: Enterprise-standard KPIs that reference ISO concepts but are adapted
For example, you may use ISO 22400 time categories but define your own composite KPI for business reasons (e.g., a specific variant of schedule adherence that ties to MRP). Treat ISO 22400 as a building block, not a straightjacket, and document the differences explicitly.
- Tier 3: Local or domain-specific KPIs not covered by ISO 22400
Allow plant-, product-, or regulator-specific metrics when justified by risk, compliance, or customer requirements. For these, you still need clear definitions, data sources, and change control, even if there is no ISO 22400 anchor.
Key constraints in brownfield, regulated environments
In existing plants with mixed MES, historians, and reporting stacks, full conversion to ISO 22400 for every KPI is constrained by:
- Data model and historian limitations: Time categories and events may not be captured in ways that match ISO 22400 without re-engineering tags, interfaces, and calculations.
- Validation and qualification burden: In GxP or aerospace-grade contexts, any change to a KPI used in release decisions, investigations, or risk assessments may require revalidation, updated procedures, and retraining.
- Long trend baselines: KPIs with 5–10+ years of history used for risk justification or capacity planning cannot be redefined lightly without clear bridging logic and documented impact analysis.
- Downtime and integration risk: Reworking KPI logic at the MES/OT layer to fully match ISO 22400 may require changes in multiple systems and interfaces, raising the risk of misalignment between shop-floor reality and reported numbers.
These constraints mean that a “full replacement” strategy, where every existing KPI is forced into ISO 22400 forms, often fails or stalls. A targeted, incremental approach tends to be more realistic and less risky.
How to decide when to base a KPI on ISO 22400
For each KPI in your catalog, ask:
- Is there a clear, relevant ISO 22400 equivalent? If yes, adopting or aligning to it may reduce ambiguity.
- Will changing this KPI’s definition impact regulated decisions? If the metric supports release, deviation/complaint handling, or safety-related decisions, treat changes as controlled and justified.
- Does cross-site comparability matter? Where you benchmark across plants or suppliers, ISO 22400 alignment can be useful, but only if data collection and context are comparable.
- Can existing systems and data support the ISO definition reliably? If your event modeling, timestamps, or equipment states cannot be mapped cleanly, forcing ISO 22400 may result in misleading numbers.
- Is there a strong legacy or contractual definition? If yes, you might keep the current KPI and introduce a parallel ISO-aligned metric, clearly differentiated.
Governance and documentation
Regardless of whether a KPI is ISO 22400-based, in a regulated environment you should:
- Maintain a controlled KPI catalog with version history and approval traceability
- Document for each KPI: the calculation, data sources, system of record, purpose, owner, and whether it aligns with ISO 22400 (and how)
- Route KPI definition changes through appropriate change control, including impact assessment on procedures, validated systems, and reports
- Keep mapping documents that show how local KPI definitions relate to any ISO 22400 elements used (time categories, states, base measures)
This allows you to gain the benefits of ISO 22400 where it fits, without creating unrealistic standardization requirements or undermining existing traceability.
