No. ISO 22400 does not prescribe which KPIs your plant must use. It defines a consistent framework, terms, and calculation methods for manufacturing KPIs, but selection and governance of KPIs remain business and site decisions.
What ISO 22400 actually provides
ISO 22400 is primarily about standardization and interoperability, not corporate performance management policy. In practice it helps you with:
- Common terminology for KPIs like OEE and related measures so MES, SCADA, historians, and reports use consistent definitions.
- Reference KPI definitions and formulas (for example, how availability, performance, and quality rates are combined).
- Structural models for how KPIs relate to lower-level data (events, states, counters).
- Guidance for IT/OT integration so different systems can exchange KPI-relevant data in a predictable way.
Nothing in ISO 22400 forces you to adopt a specific KPI set, target, or dashboard. It does not replace your own strategy deployment, policy deployment, or management review process.
What you still have to decide locally
Even if you adopt ISO 22400, you must still decide:
- Which KPIs matter for your regulatory, safety, and commercial risk profile (for example, OEE vs. flow-based metrics vs. quality cost measures).
- At what levels to use each KPI (line, cell, work center, product family, site, enterprise).
- How often to calculate and review them (real-time vs. shift vs. batch vs. campaign).
- How KPIs tie into incentives, CAPA, deviation management, and management review.
- Which local constraints to respect, such as regulated batch record timing, manual data entry limits, or data residency rules.
In regulated environments, KPI choice also has to reflect data integrity expectations, validated system boundaries, and how much change control overhead you can accept for new metrics and reports.
Using ISO 22400 in brownfield plants
Most regulated plants are brownfield: mixed vendors, legacy MES/ERP/QMS, and long-qualified equipment. In that reality, ISO 22400 is best used as a reference model, not a wholesale replacement program.
Typical patterns include:
- Rationalization of existing KPIs: Map current metrics to ISO 22400 definitions, identify duplicates and conflicts (for example, different OEE formulas across lines), and standardize where feasible.
- Incremental harmonization: When upgrading or validating new MES/SCADA modules, align their KPI logic to ISO 22400 instead of inventing new local definitions.
- Interface normalization: Use ISO 22400 terminology and structures when defining data interfaces or data models in historians and analytics layers.
A full “ISO 22400-compliant KPI replacement” is rarely practical in aerospace-grade or similar environments. The necessary system revalidation, downtime, retraining, and change-control load often outweigh the benefit of immediately perfect standardization. Most plants move gradually: start with the KPIs that drive the most confusion or cross-site misalignment and converge those first.
Key tradeoffs to consider
When deciding how tightly to align your KPIs with ISO 22400, explicitly weigh:
- Comparability vs. continuity: Standard formulas improve cross-site comparison, but changing long-standing metrics can disrupt trends and management routines, and may require re-baselining targets.
- Standard purity vs. integration cost: Strict conformance could mean changes to MES logic, historian schemas, and reports. In validated systems, each change brings qualification and documentation overhead.
- Detail vs. maintainability: ISO 22400 can support detailed breakdowns (for example, downtime categories), but over-granular designs often fail when they depend on operators to classify every event reliably.
- Automation vs. data integrity: Pushing fully automated KPI calculation across multiple legacy systems can introduce reconciliation issues. You may need staged adoption, with clear traceability for how data flows and is transformed.
Practical way to use ISO 22400 for KPI selection
A pragmatic approach in regulated, long-lifecycle environments is:
- Clarify business goals: Define what problems you are trying to solve (throughput, schedule adherence, deviation reduction, complaint rates, changeover losses).
- Inventory existing metrics: Document current KPIs, formulas, data sources, and where they live (MES, ERP, spreadsheets, BI tools).
- Map to ISO 22400 concepts: Identify where your metrics align or conflict with ISO 22400 definitions and naming.
- Select a minimal, high-impact set: Choose a small core set of KPIs to harmonize first (for example, OEE and its components, NPT, or specific downtime metrics).
- Plan change control and validation: For systems in scope of validation or governed change control, plan and document how formulas, reports, and interfaces will be updated and requalified.
- Phase implementation: Pilot on one line or area, verify data quality and usability, then extend. Avoid attempting an enterprise-wide KPI redesign in one step.
ISO 22400 is a useful reference to improve consistency, but it will not and should not replace your own governance on which KPIs are appropriate for your plant, your regulatory obligations, and your asset base.
