ISO 22400 and OEE: How the Standard Frames Equipment-Oriented KPIs

In aerospace and defense manufacturing, equipment-related KPIs sit at the core of production visibility, certification readiness, and multi-site reporting. ISO 22400 gives a shared vocabulary for these KPIs, including overall equipment effectiveness (OEE), availability, and utilization, without forcing plants into a single calculation method. For aerospace organizations building a digital thread across MES, ERP, PLM, and quality systems, aligning with the ISO 22400 manufacturing KPI standard helps ensure that equipment performance numbers mean the same thing at every site and supplier.

This article explains how ISO 22400 treats equipment-focused KPIs conceptually, how its OEE-related models (OEEA, OEEB) differ from traditional TPM-style OEE, and how aerospace manufacturers can adopt the terminology without rewriting every KPI formula. The focus is on definitions and structure, not on prescribing a specific way to improve performance.

Why Equipment KPIs Are Central in ISO 22400

The role of equipment behavior in manufacturing performance

ISO 22400 pays particular attention to equipment because, in most aerospace production environments, complex assets drive both throughput and certification risk. A five-axis machining center, composite layup cell, or engine test stand may be the bottleneck for an entire aircraft program or propulsion line. If those assets are not running when planned—or if they run but produce nonconforming hardware—schedule and cost performance quickly degrade.

The standard therefore structures many KPIs around how equipment spends time and what it produces in that time. Time spent in specific states (RUN, STOP, IDLE, SLOW) is aggregated into concepts such as operating time, busy time, and downtime. Quantities produced in those time windows are tracked as good parts, rejections, and rework quantities. From these foundational elements, ISO 22400 defines equipment-oriented KPIs that can be compared across different plants, systems, and products.

For aerospace, this provides a disciplined way to separate questions like “Was the machining center available?” from “When it was busy, did it produce conforming hardware?” That distinction is important when determining whether issues belong to maintenance, production planning, or quality engineering.

Linking equipment KPIs to MOM and enterprise decisions

ISO 22400 places equipment KPIs within the broader context of manufacturing operations management (MOM). KPIs such as availability, utilization, and conceptual OEE are positioned at the level where work orders, routings, and resource assignments are executed—typically managed by MES or similar systems. These indicators feed upstream decisions in enterprise systems without forcing those systems to adopt a particular database or UI technology.

In an aerospace plant, this linkage might look like:

• MES level: Tracks equipment state changes, order execution, and scrap events; calculates ISO 22400-aligned indicators.
• ERP level: Consumes summarized equipment KPIs to refine capacity planning, program cost forecasts, and promise dates.
• PLM / configuration management: Uses production execution and quality-related KPIs to assess manufacturability of new designs and the impact of engineering changes.

By using a common ISO 22400 vocabulary across these systems, aerospace organizations can reason about equipment constraints, schedule risk, and capacity investments without debating what “availability” or “utilization” actually mean.

Conceptual View of OEE in ISO 22400

OEE as a composition of time and quantity indicators

ISO 22400 treats overall equipment effectiveness as a conceptual construct rather than as a single mandated formula. In the standard, OEE is assembled from well-defined time-based and quantity-based indicators. Time indicators describe how much of the calendar period is actually used for productive operation, while quantity indicators describe how much of the resulting output meets quality criteria.

This leads to a layered structure:

• Time-based elements: planned time, operating time, busy time, downtime categories, and related state-derived durations.
• Quantity-based elements: produced quantity, accepted quantity, rejected quantity, and reworked quantity.
• Derived indicators: equipment availability, utilization, and conceptual effectiveness ratios built from combinations of the above.

For aerospace plants, this abstraction allows different product families (e.g., composite structures vs. precision machined parts) to maintain their own cycle-time assumptions and yield profiles, while still reporting high-level OEE-related KPIs in a comparable way across programs.

How OEEA and OEEB models are structured conceptually

Within this conceptual framework, ISO 22400 introduces multiple OEE-related models, often referenced in literature as OEEA and OEEB. Each model describes a different way to compose time and quantity elements into an effectiveness measure while staying within the same terminology set.

Conceptually, OEEA tends to emphasize the relationship between busy time and produced volume, while OEEB more explicitly separates availability-related time losses from speed and quality-related losses. Both models rely on the same building blocks:

• Time structure: definitions of when equipment is considered operating, busy, or down.
• State mapping: rules for assigning RUN, STOP, IDLE, and other states into those time buckets.
• Output structure: distinctions between good pieces, scrap, rework, and test output.

ISO 22400 does not require any aerospace manufacturer to select one model over the other. Instead, it provides a common language so that, for example, a machining center in a European airframe plant and a test stand in a North American propulsion facility can both declare which conceptual OEE model they use and how it maps to their local KPI definitions.

Availability, Performance, and Quality Concepts

Time categories used to express availability

Availability in ISO 22400 is based on carefully defined time categories, rather than on informal labels such as “uptime.” Typical categories include:

• Planned time: the portion of the calendar where equipment is scheduled to be available for production or test.
• Operating time: the subset of planned time when the equipment is in a state that can produce, even if it is not actually busy.
• Busy time: the subset of operating time during which equipment is actively executing work (for example, producing a part or running a test sequence).
• Downtime: periods within planned time where the equipment is not available for production due to failures, setups, or other reasons.

For aerospace, this distinction between operating and busy time is important. A radar test bench that is powered on and ready (operating) but waiting for engineering sign-off or configuration data is not busy, yet it still consumes facility resources and may block other work. ISO 22400’s definitions support KPIs that highlight this difference.

Quantity concepts behind performance and quality factors

ISO 22400 also standardizes how quantities are treated within KPIs. Rather than mixing concepts like throughput and yield, it separates them into well-defined indicators:

• Produced quantity: total units processed by the equipment in a period, regardless of quality.
• Accepted quantity: units that meet defined quality criteria and are released for downstream use (assembly, test, shipment).
• Rejected quantity: units that are scrapped or quarantined as nonconforming.
• Reworked quantity: units that initially failed criteria but are successfully recovered through rework.

From these quantities, performance and quality-related factors are derived. In aerospace and space hardware production, where part genealogy and serial-level traceability are mandatory, tying these quantity concepts back to specific work orders, serial numbers, and configurations is essential. ISO 22400 does not define the traceability system itself, but it ensures that KPIs built on top of that system have consistent meaning.

Equipment States and Time Categories

RUN, STOP, IDLE, SLOW and their meaning

Equipment state models in ISO 22400 act as the bridge from control-system signals to conceptual KPIs. Common states include:

• RUN: equipment is executing productive work, such as machining, drilling, or test execution.
• STOP: equipment is not running, often due to a fault, changeover, or scheduled maintenance.
• IDLE: equipment is ready and capable of running but is waiting for material, instructions, or authorization.
• SLOW: equipment is running below its nominal performance, for example due to conservative feed rates on a new material or risk mitigation on a first article.

In an aerospace environment, these states can be further enriched with domain-specific reasons—such as waiting for nonconformance disposition, engineering change approval, or special process certification. ISO 22400 does not prescribe reason codes, but it ensures that however they are defined, they roll up consistently into state-based KPIs.

Mapping states to operating, busy, and downtime categories

Once state definitions are clear, ISO 22400 describes how to group them into time categories that underlie availability and utilization indicators. A typical mapping might be:

• Operating time: RUN, IDLE, SLOW, and possibly certain test or warm-up states.
• Busy time: RUN and SLOW, where equipment is actively processing a work order or test program.
• Downtime: STOP states that occur within planned time, subdivided into planned and unplanned downtime.

For aerospace manufacturers with highly engineered products, this mapping clarifies discussions where engineering or quality events appear as “downtime” from a scheduling perspective. If a composite cure oven is STOP because of an engineering hold on a material batch, the corresponding downtime can be categorized consistently across sites. That, in turn, supports comparisons across programs and facilities when analyzing bottlenecks in a regulated production network.

Comparing ISO 22400 OEE with Traditional TPM OEE

Where definitions align and where they differ

Traditional TPM-style OEE is often implemented as a product of three factors—availability, performance, and quality—each computed according to locally agreed formulas. ISO 22400 aligns with this general structure but is more explicit about the time and quantity elements that underlie each factor. Instead of declaring a single canonical OEE equation, it formalizes the building blocks and offers alternative composition models.

Alignment occurs at the conceptual level: unplanned downtime reduces availability; reduced speed and micro-stops affect performance; nonconforming output reduces quality. Differences arise in the degree of standardization. TPM implementations sometimes blur distinctions between operating vs busy time or between scrap vs rework, whereas ISO 22400 requires these concepts to be clearly separated and named. For aerospace programs seeking audit-ready KPI definitions, this additional clarity is an advantage.

Avoiding confusion in multi-site OEE reporting

One of the main risks in global aerospace production is believing that OEE numbers are comparable when they are not. Two plants might both report “OEE = 78%,” yet one includes test re-runs in performance losses while another does not. ISO 22400 helps avoid this by encouraging organizations to document which conceptual model they use (e.g., OEEA or OEEB), how states are mapped to time categories, and which quantity indicators are included in each factor.

For a multi-site aerospace or space hardware manufacturer, this documentation should be part of the digital manufacturing infrastructure: MES configuration, KPI catalogs, and integration contracts between systems. When a central team aggregates OEE data from different facilities, they can verify that the underlying ISO 22400 concepts match before drawing conclusions about best-performing plants or suppliers.

Using ISO 22400 Equipment KPIs Without Over-Prescription

Selecting which equipment KPIs to track

ISO 22400 defines a structured catalog of KPIs, but it does not tell an aerospace organization which ones it must use. In practice, plants choose a subset aligned with their operational priorities and regulatory context. A few examples:

• Engine test facilities may emphasize utilization and test-cycle adherence KPIs, since test cell access is a scarce resource.
• Precision machining centers may focus on availability and first-pass yield to manage capacity against long-cycle aerospace parts.
• Composite curing operations may track oven utilization and batch conformance indicators, as cure cycles often drive schedule risk.

All of these KPIs can be named and structured according to ISO 22400, even if not every KPI from the standard is implemented. That approach gives aerospace manufacturers a consistent conceptual basis while retaining flexibility.

Communicating definitions across plants and suppliers

The greatest value of ISO 22400 in aerospace manufacturing often appears at the boundaries between organizations: between a prime contractor and its tiered suppliers, or between an OEM and its MRO network. When contracts or performance reviews reference KPIs like equipment availability or utilization, tying those terms to ISO 22400 definitions reduces ambiguity.

Practically, this may involve maintaining an ISO 22400-aligned KPI dictionary within a digital manufacturing platform. Each KPI entry describes which states, time categories, and quantity indicators are used; which OEE-related model (if any) is assumed; and how the KPI is reported. When onboarding a new supplier or bringing a new plant into the network, that dictionary becomes the reference for configuring local MES and reporting systems, and it complements broader discussions of standardized KPIs as described in the ISO 22400 manufacturing KPI standard hub content.

Practical Considerations for Aerospace and Space Hardware Production

Integrating ISO 22400 concepts into MES and digital thread

To make ISO 22400 actionable, aerospace organizations embed its concepts in their MES and digital thread architecture. At the MES layer, equipment states, order events, and quality decisions are captured with sufficient granularity to derive ISO 22400-aligned time and quantity indicators. At higher layers, these indicators are associated with specific configurations, serial numbers, and engineering baselines, tying equipment performance back to the product definition.

In practice, this could mean:

• Standardizing state models and time-category mappings across all test stands or machine types in a program.
• Ensuring that part genealogy records link nonconforming quantities to the exact equipment and time window where they were produced.
• Configuring dashboards so that availability and utilization KPIs are derived from the same ISO 22400 building blocks across different plants.

This creates a consistent KPI layer in the digital thread, improving both operational decision-making and audit readiness.

Working within AS9100 and regulated environments

AS9100 and related aerospace quality requirements emphasize documented processes, traceability, and evidence-based decision-making. ISO 22400 contributes by providing standardized, auditable definitions of what key equipment-related KPIs mean. While AS9100 does not mandate specific OEE values or formulas, it does expect organizations to monitor and control processes that affect product quality and delivery.

By adopting ISO 22400 terminology, an aerospace manufacturer can demonstrate that KPIs used in management review and continuous improvement activities are consistently defined across programs and facilities. This reduces the risk that different sites interpret the same KPI differently during customer or regulatory audits and supports clear linkage between process performance and quality outcomes.

Balancing standardization with local optimization

Finally, ISO 22400 is explicit about its own limits: it standardizes definitions, not business strategy or improvement methods. Aerospace plants remain free to set their own OEE targets, to prioritize certain KPIs over others, and to implement local optimization practices aligned with their mix of programs and technologies.

The practical balance is to keep KPI definitions standardized (names, time and quantity concepts, state mappings) while allowing each plant to decide how aggressively to improve them. A propulsion test center and a structures assembly plant may share the same availability definition but choose different thresholds for what counts as acceptable performance. ISO 22400 supports that diversity by providing a common measurement language rather than enforcing a uniform scorecard.