ISO 22400 treats equipment availability and utilization as distinct but related manufacturing KPIs. It does not prescribe specific targets, but provides standardized definitions and formulas so different plants and systems can calculate these metrics consistently.
Equipment availability in ISO 22400
In ISO 22400, availability is a time-based indicator that compares the time equipment is actually capable of producing to the time it is planned to be available.
At a simplified level, for a given period:
- Planned time: Time the equipment is scheduled to be available for production (excluding planned long shutdowns such as major holidays or extended overhauls, depending on your site convention).
- Operating time: Time the equipment is in a state where it can produce (often called “available” or “up” in many MES/SCADA models). This typically includes running and short stops that do not put the equipment in a down state.
A commonly used ISO 22400-style form is:
Availability = Operating time / Planned time
ISO 22400 distinguishes between different equipment states (e.g., planned shutdown, unplanned downtime, setup, minor stops). How each state is included or excluded from “operating” and “planned” must be configured in your system and aligned with your site’s interpretation of the standard.
In many implementations, this aligns with the “availability” component of OEE, but ISO 22400 formalizes the underlying time categories and KPIs, rather than only the OEE composite.
Equipment utilization in ISO 22400
ISO 22400 defines utilization as a capacity-related indicator. It expresses how much of the equipment’s available capacity is actually used for productive operation during a period.
There are two common patterns depending on the specific ISO 22400 KPI variant you implement:
- Time-based utilization: Effective production time compared with some larger time base.
Typical form: Utilization = Effective production time / Calendar time or / Planned time, depending on configuration.
- Capacity-based utilization: Actual output compared to theoretical maximum capacity for the period.
Typical form: Utilization = Actual output / Theoretical maximum output.
ISO 22400 provides definitions for these KPIs and the underlying concepts (e.g., calendar time, operating time, net operating time, capacity), but it does not enforce one single utilization formula for all plants. Your organization must choose and document which ISO 22400 utilization KPI is being used, and how it maps to equipment states and order data.
Key differences: availability vs utilization
- What they measure:
- Availability measures time readiness: How much of the planned time was the equipment able to run.
- Utilization measures capacity usage: How much of the time or capacity base was actually used to produce.
- Primary inputs:
- Availability is driven by equipment states and downtime categorization.
- Utilization also depends on production schedules, order loading, and rated capacity or theoretical maximum rates.
- Typical interpretation:
- Low availability usually indicates maintenance, reliability, or changeover issues.
- Low utilization with good availability usually indicates scheduling, loading, mix, or demand issues.
Dependencies and implementation caveats
The standard definitions only become meaningful if they are implemented consistently across your systems and sites. In regulated and long-lifecycle environments, several realities affect how ISO 22400 availability and utilization behave in practice:
- State modeling and integration: SCADA/PLC, MES, and CMMS often use different equipment state models. How a state like “setup” or “warmup” is mapped into ISO 22400 categories (operating vs planned shutdown vs unplanned downtime) is site-specific and must be explicitly configured and validated.
- Brownfield coexistence: Many plants already have OEE logic embedded in legacy MES or custom reports. A strict ISO 22400 implementation often changes the numbers people are used to seeing. Running both side-by-side for a period, with clear mapping, is usually necessary to avoid confusion and claims that the data is “wrong”.
- Capacity definitions: Utilization requires credible definitions of rated speed and theoretical maximum output. In high-mix, low-volume operations, or with manual and semi-automated stations, these values are often approximate. You may need product-family or routing-step level capacities rather than a single number per machine.
- Regulatory constraints: Any change in KPI calculation logic that drives maintenance intervals, staffing, or qualification decisions may need documented change control, impact assessment, and potentially revalidation of associated reports and automated rules.
- Time-base alignment: Calendar time, shift time, and planned production time are not the same. ISO 22400 allows different KPI variants; if you mix them (for example, comparing one line on calendar-based utilization and another on shift-based utilization) you can easily misinterpret relative performance.
Relation to OEE and existing MES/ERP metrics
ISO 22400 does not require you to replace OEE or your current KPIs. It provides a standardized KPI framework that can sit under or alongside existing OEE implementations.
- OEE availability vs ISO 22400 availability: They are similar but not guaranteed to be identical. Many legacy OEE implementations treat some planned stops differently than ISO 22400. If you migrate to ISO 22400 definitions without careful mapping, historical comparisons will be distorted.
- Use as a reference model: A practical approach in brownfield environments is to:
- Map current MES/SCADA state codes and KPIs to ISO 22400 categories.
- Document any deliberate deviations from the standard (e.g., including certain planned micro-stops in availability).
- Gradually converge toward ISO 22400-compliant logic as systems are upgraded, rather than trying a big-bang replacement of all KPI logic.
What this means in a regulated, long-lifecycle plant
In aerospace, defense, and similar regulated environments, adopting ISO 22400 definitions for availability and utilization is less about installing a new KPI and more about establishing a traceable and auditable calculation method:
- You need clear documentation of definitions, formulas, and state mappings used at each asset and line.
- Changes to those definitions should go through change control, with impact analysis on any KPIs that feed maintenance planning, capacity commitments, or customer-facing performance reporting.
- Full replacement of existing KPI engines in MES, historians, and reporting tools is rarely feasible in one step due to validation burden, integration complexity, and downtime risk. A phased coexistence model, with ISO 22400 as the reference, is usually safer.
Used in this way, ISO 22400 provides a common language for availability and utilization across sites and vendors, while still allowing for local configuration where justified and documented.
