Why doesn’t ISO 22400 tell us which KPIs to use?

ISO 22400 is a reference standard for manufacturing KPIs, not a prescriptive list of what every plant must measure. It focuses on giving you a consistent vocabulary, basic calculation logic, and information models so that systems and teams can understand each other. Selecting which KPIs to actually use is left to each organization.

What ISO 22400 is designed to do

ISO 22400 primarily aims to:

• Standardize KPI terminology so MES, SCADA, ERP, and reporting tools can align on what a metric means.
• Define generic formulas and input variables for common manufacturing KPIs.
• Provide an information model so KPIs can be exchanged between systems in a consistent way.
• Support interoperability across mixed-vendor environments without forcing a specific operational strategy.

In other words, it is about how to represent and calculate KPIs when you choose to use them, not which KPIs belong in your plant.

Why it does not prescribe “the right” KPIs for your plant

Regulated, industrial environments differ too much for a single, fixed KPI set to make sense. Some key dimensions that vary:

• Industry and risk profile: Aseptic pharma, space hardware, and heavy machining have very different critical failure modes and cost drivers.
• Product and process mix: A high-mix, low-volume cell shop needs different performance signals than a high-volume packaging line.
• Automation and data maturity: Plants with manual batch records and legacy equipment cannot reliably populate some ISO 22400 KPIs without major integration work.
• Regulatory expectations: KPIs that drive behavior in GMP environments may conflict with quality or data integrity expectations if they are chosen poorly or incentivize the wrong tradeoffs.

Because of these differences, a universal “you must use these 10 KPIs” list would either be too generic to be useful or misleading in many contexts. The standard avoids that by remaining technology and strategy neutral.

Implications for regulated, brownfield environments

In most brownfield plants with mixed vendors and legacy systems, ISO 22400 will not drop in as a turnkey KPI set. Instead, you typically need to:

• Map your existing KPIs to ISO 22400 terms: Identify where you already measure similar concepts and reconcile naming and formula differences.
• Decide which ISO 22400 KPIs are feasible: Filter the candidates based on what data your current MES, historians, and manual logs can reliably provide.
• Assess validation and change-control impact: In regulated environments, changing KPI definitions or data sources can trigger revalidation, documentation updates, and retraining.
• Align with existing systems: Ensure any new or revised KPIs do not break existing dashboards, SOPs, or quality investigations that depend on legacy definitions.

Because replacing KPI frameworks across all systems at once often implies revalidating MES, reports, and QMS procedures, full replacement strategies can be slow, costly, and sometimes not worth the disruption. Incremental alignment to ISO 22400 is more realistic.

How to use ISO 22400 practically

A pragmatic approach is to treat ISO 22400 as a structured catalog and reference, not a mandate:

• Start from your business and quality objectives: Define what you need to improve or control (e.g., release lead time, deviation rate, equipment uptime).
• Look up relevant ISO 22400 KPIs: Use the standard to find metrics that match those needs and understand their suggested data inputs and formulas.
• Evaluate data and system readiness: Confirm whether your existing plant data, integrations, and validation status support those KPIs without undermining traceability or data integrity.
• Standardize naming and documentation: Use ISO 22400 terminology in specifications, integration requirements, and SOPs so vendors and internal teams have a common language.

This keeps the benefits of standardization and interoperability while respecting plant-specific constraints and long equipment lifecycles.

Key takeaway

ISO 22400 is intentionally non-prescriptive about which KPIs you must use. It gives you a shared language and structure so that, once you decide which metrics matter for your products, risks, and regulatory context, different systems and stakeholders can handle those metrics consistently. The hard work of selecting, prioritizing, and validating the right KPIs remains a plant-level responsibility.