Learn what ISO 22400 is, why it was created, and how its standardized KPI concepts help manufacturers compare performance across plants, systems, and suppliers—without telling you which metrics or targets to choose.

Answer first: ISO 22400 is an international standard that defines how manufacturing key performance indicators (KPIs) are described, structured, and named so that plants, suppliers, and systems can talk about performance in the same language. It does not tell you which KPIs to use, what targets to set, or how to run improvement programs. Its job is to define what the metrics mean, not how you manage with them.
This overview explains the basics of ISO 22400 in plain language for operations, IT, and quality leaders. By the end, you should understand why the standard exists, what it covers (and doesn’t), and how its KPI concepts differ from homegrown definitions you may use today. If you later decide to build a standardized ISO 22400 KPI framework, you will know what role the standard can realistically play.
Many manufacturers grow through acquisitions, greenfield sites, and long supplier networks. Over time, each plant develops its own metrics and naming conventions. Common situations include:
The result is confusion. Leaders spend time debating what the numbers mean instead of discussing how to improve them. ISO 22400 exists to reduce this definitional noise.
Modern operations rely on a mix of systems: ERP for planning, MES for execution, SCADA and PLCs for control, historians for time-series data, and various reporting tools. Each system may:
When you connect multiple sites and suppliers, these inconsistencies multiply. A KPI that looks identical on a dashboard may be based on very different underlying logic. ISO 22400 addresses this by defining a shared conceptual framework for KPIs used in manufacturing operations management.
ISO 22400 belongs to the family of automation and integration standards. Its purpose is to provide a common language for performance data so that:
This language is intentionally industry neutral, so discrete, batch, and continuous operations can all use the same conceptual building blocks.
ISO 22400 focuses on the conceptual side of performance measurement. It defines:
The standard separates indicators into a broader set of performance indicators and a more selective set of key performance indicators. The key indicators are those considered particularly relevant for monitoring manufacturing operations.
ISO 22400 is closely aligned with IEC 62264, the reference standard for enterprise-control system integration. IEC 62264 defines hierarchical levels such as:
ISO 22400 positions its KPIs mainly at Level 3, the manufacturing operations layer. This is where production, quality, inventory, and maintenance are executed and monitored. Metrics that combine detailed operational data with financial results at Level 4 typically fall outside the scope of ISO 22400.
Understanding what ISO 22400 does not do is as important as understanding what it covers. The standard deliberately avoids:
If you adopt ISO 22400, you still decide which KPIs to track, what levels to report them at, and how to use them in decision-making. The standard provides vocabulary and structure, not a performance playbook.
ISO 22400 separates the universe of possible measures into:
The standard provides a structured description for KPIs, including their intended users (operator, supervisor, manager), applicable time horizons, and typical use cases. This helps organizations distinguish between raw data, general metrics, and the smaller group of measures that truly drive decisions.
In the ISO 22400 context, Manufacturing Operations Management (MOM) refers to the activities that plan, dispatch, execute, track, and report manufacturing and maintenance operations. MOM sits between enterprise planning systems and the shop-floor control layer.
ISO 22400 focuses on KPIs relevant to this MOM layer, such as:
By concentrating on Level 3, the standard builds a bridge between high-level business goals and detailed control-system data.
Another core concept in ISO 22400 is the object of measurement. KPIs are always tied to something being measured, for example:
The same conceptual KPI—such as equipment utilization—can be applied at different levels. ISO 22400 clarifies how these KPIs relate to time, quantity, and state concepts so that aggregation across levels is meaningful.
For organizations operating multiple plants or collaborating with external manufacturers, comparability is a key challenge. Without standard definitions, numbers for “availability,” “throughput,” or “scrap rate” may not be genuinely comparable.
By adopting ISO 22400 definitions:
Instead of spending time reconciling definitions, teams can focus on understanding performance differences and root causes.
Most manufacturers do not have a single monolithic system. Instead, they integrate ERP, MES, SCADA, historians, and specialized reporting tools. ISO 22400 supports this heterogeneous reality by providing:
When multiple systems use ISO 22400-aligned definitions, data exchange and aggregation become easier. Interfaces can be designed around shared KPI concepts rather than custom mappings for each integration.
Another practical benefit appears in commercial relationships. When performance reporting is part of a contract or service-level agreement (SLA), unclear metric definitions can lead to disputes.
By referencing ISO 22400 concepts in contracts—for example, defining “equipment utilization” or “order execution reliability” according to the standard—both parties can verify they are using the same language. This reduces ambiguity and supports more transparent, data-driven collaboration.
ISO 22400 is intentionally industry neutral and can be applied in:
Organizations with complex multi-site operations, regulated environments, or extensive supplier networks often benefit most from a standard KPI language.
Consider ISO 22400 if you recognize several of the following symptoms:
In such environments, a standardized conceptual framework can simplify reporting and improve the quality of performance discussions.
Even if you adopt ISO 22400, you will likely need additional, domain-specific measures. Examples include:
The key is to distinguish clearly between KPIs that follow ISO 22400 definitions and those that are custom to your organization. Many platforms and data models allow you to label metrics accordingly, so users know which indicators are standardized and which are local extensions.
Before changing tools or rolling out new dashboards, start with a structured assessment of your existing KPIs:
This inventory will show where ISO 22400 can bring the most immediate clarity.
You do not need to implement every ISO 22400 concept at once. Many organizations begin by focusing on a subset of domains, such as:
Starting small and expanding over time reduces disruption and helps teams build confidence in the standardized definitions.
Modern digital operations platforms can use ISO 22400 concepts as a semantic layer between shop-floor events and business reporting. For example, a platform aligned with the ISO 22400 Manufacturing KPIs: Standardized Performance Measurement for Modern Plants hub can:
In this way, the standard becomes an enabler of consistent reporting rather than a constraint on how you design your operations.
ISO 22400 is a definitional standard for manufacturing KPIs. It offers:
Equally important, it does not dictate which KPIs you must use, how to calculate them in detail, what targets to set, or how to run improvement programs. Those remain business decisions.
If your organization struggles with inconsistent KPI definitions across plants, systems, or suppliers, ISO 22400 can provide a solid foundation for a more coherent performance measurement framework. From there, you can build dashboards, analytics, and contracts on top of a shared understanding of what the numbers mean—while retaining the flexibility to add domain-specific metrics where needed.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.