Implementing ISO 22400: Practical Steps to Standardize Manufacturing KPIs

ISO 22400 gives aerospace and defense manufacturers a common language for manufacturing KPIs, but the standard does not tell you how to roll it out across MES, ERP, historians, and supplier portals. Turning its concepts into repeatable practice requires a structured implementation approach that respects existing systems, AS9100 processes, and the realities of multi-site aerospace production. This guide focuses on practical, non-vendor-specific steps to adopt the ISO 22400 manufacturing KPI framework inside a regulated aerospace manufacturing environment.

The goal is not formal certification. Instead, the emphasis is on making KPI definitions consistent across plants, programs, and partners so that “availability,” “utilization,” and order-related indicators mean the same thing in every system and report. Done correctly, ISO 22400 becomes part of your digital thread, not a competing structure.

Assessing Your Current KPI Landscape

Inventorying existing KPIs and definitions

The starting point for ISO 22400 implementation is a realistic picture of the KPIs you already use. In a typical aerospace or space hardware program, KPIs are scattered across:

• MES dashboards monitoring work centers, takt performance, and rework rates
• ERP and MRP reports on schedule adherence, order lead time, and WIP age
• QMS and nonconformance systems tracking defect rates, escapes, and MRB cycle times
• Maintenance systems tracking equipment downtime and mean time between failures
• Excel-based “shadow systems” created by program teams and industrial engineers

Create a structured KPI inventory that captures at least:

• KPI name as used today (for example, “machine uptime,” “line utilization,” “on-time to promise”)
• Formal or informal definition, including what is in or out of scope
• Calculation description or formula (even if only documented in a spreadsheet)
• Data sources and systems (MES, historian, ERP, QMS, manual entry)
• Organizational owner (operations, quality, program office, finance)
• Where it is visible (reports, dashboards, SLAs, customer scorecards)

For aerospace organizations running multiple sites or supporting multiple OEM programs, capture which sites or programs use each KPI. Many inconsistencies only appear when comparing KPI catalogs across factories or business units.

Identifying inconsistent terms across plants and systems

With the inventory assembled, the next step is to surface inconsistent terminology. In aerospace production, this often appears in three patterns:

• Same name, different meaning – for example, one plant labels a KPI “availability” but includes scheduled maintenance in the denominator, while another excludes it.
• Different name, same meaning – for example, “uptime” in one system and “run time” in another both correspond to the same operating state.
• Different aggregation logic – for example, OEE calculated at the equipment level in one plant and at the line level in another, but reported as a single corporate metric.

Document these conflicts explicitly. ISO 22400 implementation is largely the process of resolving them and aligning to the standard’s definitions for time categories, states, and indicator semantics. Pay particular attention to KPIs that appear in:

• Customer-facing reports or contract deliverables
• Regulatory or airworthiness-related metrics (for example, defect escape rates)
• Executive dashboards and board-level reporting

These are the KPIs where ambiguity is most costly and where alignment with ISO 22400 will have the greatest impact on clarity and comparability.

Mapping Existing KPIs to ISO 22400 Concepts

Renaming vs. re-defining KPIs

Once you understand your current KPI landscape, the next step is to map those KPIs onto ISO 22400 concepts. The standard provides structured definitions for performance indicators and KPIs based on equipment states, time categories, and quantity-based measures. For each existing KPI, ask:

• Does ISO 22400 define a directly comparable KPI (for example, an availability or utilization concept)?
• If so, is our current definition materially aligned, or are there meaningful differences in scope or time basis?
• If not, is our KPI a useful extension (for example, a specific aerospace traceability or certification metric)?

In practice, you will end up with three categories of KPIs:

1. Aligned KPIs – Current definition closely matches an ISO 22400 KPI. Here, you can retain the definition and, if needed, adopt ISO 22400’s naming and attribute conventions.
2. Adjustable KPIs – KPIs that can be brought into alignment with limited changes, such as slightly adjusting time categorizations or clarifying which equipment states are included.
3. Non-standard KPIs – Aerospace- or program-specific KPIs that serve important purposes but are outside ISO 22400’s scope (for example, certification batch release lead time, or first article inspection queue time).

For the first two categories, decide whether you will:

• Rename the KPI to match ISO 22400 terminology while keeping the underlying logic essentially the same, or
• Re-define the KPI to fully conform with the ISO 22400 concept, updating the calculation logic and documentation.

Renaming is less disruptive but can leave subtle inconsistencies if the underlying logic still diverges from the standard. Re-defining offers better interoperability but requires more careful change management and stakeholder communication.

Dealing with near-duplicates (availability vs. uptime)

Near-duplicate KPIs are common in aerospace factories that have grown through acquisitions or that support different OEM programs with separate reporting expectations. A classic example is “availability” versus “uptime,” both attempting to describe how much of the planned time equipment spends in productive states.

ISO 22400 helps by providing precise definitions for equipment states (e.g., RUN, STOP, IDLE, SLOW) and the time categories derived from them. To reconcile near-duplicates:

1. Express each existing KPI in terms of ISO 22400 states and times (for example, “uptime” = RUN time only; “availability” = RUN + IDLE over planned time).
2. Identify which KPI best aligns with the ISO 22400 availability or utilization concept.
3. Standardize on that definition and make the alternative an alias or a retired KPI.

In aerospace, be especially rigorous with KPIs used in customer contracts or offset agreements. If an OEM contract references “equipment availability” for a nacelle line or composite layup cell, you should ensure the governing definition is explicitly mapped to the ISO 22400 concept and unambiguous across all reporting tools.

Adapting Data Models and Interfaces

Aligning equipment states and time categories

Conceptual alignment is only effective if your data models support it. ISO 22400 relies heavily on equipment states and their associated times. In practice, this means standardizing how signals from machines, test stands, and assembly cells are translated into high-level states across all plants.

For an aerospace environment with diverse equipment (CNC machining centers, autoclaves, bonding ovens, engine test cells, structural assembly lines), the implementation steps typically include:

• Defining a canonical set of equipment states aligned with ISO 22400 (for example, RUN, STOP-planned, STOP-unplanned, IDLE, SETUP, SLOW).
• Mapping PLC or control system signals into those states in a consistent way, even if different OEMs use different tags.
• Ensuring that historians and MES capture time in each state at an appropriate granularity.
• Deriving standardized time categories (planned time, busy time, operating time, downtime) from those states.

Because aerospace production frequently includes long-cycle, high-mix operations, state definitions must also consider:

• Setup and changeover for configuration changes and engineering effectivity
• Waiting states due to missing certifications, FAI completion, or quality hold
• Planned pauses due to coordination with external test facilities or customer inspections

Your implementation should make these distinctions explicit so that KPIs derived from state times remain interpretable by both operations and compliance teams.

Updating MES, ERP, and historian data schemas

After aligning states, you need to ensure that the underlying data models can express ISO 22400 KPIs cleanly. This does not require replacing existing systems, but it does typically involve schema extensions and interface adjustments. Common changes include:

• Adding standardized KPI identifiers and attributes to MES and reporting databases.
• Introducing explicit fields for ISO 22400 time categories instead of inferring them in every report.
• Tagging KPIs as ISO 22400-aligned versus organization-specific extensions.
• Harmonizing units of measure and timestamp conventions across systems (especially important in multi-site, multi-time-zone aerospace networks).

For ERP systems that manage orders and work breakdown structures, you may need to:

• Align production order and operation identifiers with the objects of measurement defined in ISO 22400.
• Ensure that order-level and equipment-level KPIs can be linked, enabling analysis of how equipment performance affects program schedule adherence.

A digital manufacturing platform such as Connect 981 can sit above existing MES, QMS, and ERP systems, mapping their native data structures into an ISO 22400-aligned KPI model. This approach allows you to standardize KPI semantics without forcing a single vendor stack across the entire enterprise or supply chain.

Governance: Owning and Maintaining KPI Definitions

Creating a KPI data dictionary and ownership model

ISO 22400 implementation fails quickly if KPI definitions drift over time. To prevent this, establish a formal KPI data dictionary and governance model that treat KPI definitions as controlled data assets, similar to engineering configurations or process specs.

Your KPI data dictionary should include, at minimum:

• The KPI name and unique identifier
• A clear, ISO 22400-based conceptual definition
• Mathematical expression or calculation logic
• Object of measurement (equipment, line, work center, area, site, order)
• Applicable time behavior, units of measure, and expected range
• Data sources and system-of-record
• Primary user groups (operators, manufacturing engineering, program management, executives)

Treat the dictionary as a controlled document or database under configuration control. Assign explicit ownership, typically through a cross-functional KPI governance board that includes operations, quality, IT/OT, and program representation. In AS9100 environments, the KPI dictionary often integrates with existing document control and change management processes.

Change management for KPI definitions and dashboards

Because KPIs influence decisions, incentives, and sometimes customer penalties, changing a KPI definition is a significant event. Your governance model should define:

• How KPI changes are proposed, reviewed, and approved
• How version history is maintained, including effective dates for each definition
• How changes propagate into reports, dashboards, and interfaces
• How historical data is handled (recalculated, re-labeled, or left unchanged with clear cutover markers)

In practice, this often means adopting a release cadence for KPI changes (for example, quarterly) and treating KPI updates like software or process changes. For aerospace programs with strict contractual reporting, align KPI definition changes with contract cycles or explicit customer agreement to avoid disputes over performance metrics mid-program.

Training Stakeholders on ISO 22400 Concepts

Educating operators, engineers, and managers

Standardized KPIs only deliver value if stakeholders understand what they mean and trust them. ISO 22400 concepts must therefore be embedded into everyday language on the shop floor and in program reviews.

Training should be tailored by role:

• Operators and cell leads need to understand equipment states, why accurate state entry matters, and how their actions affect KPIs such as availability and utilization.
• Manufacturing and industrial engineers need deeper knowledge of time categories, data models, and how their process changes might impact KPI definitions.
• Program managers and executives need clarity on how site-level and equipment-level ISO 22400 KPIs roll up to program performance views and what is and is not comparable across plants.

Use real examples from your own aerospace lines—such as a composite layup cell, an engine test bay, or a structures assembly station—to illustrate how states, times, and KPIs interact. This grounding avoids the perception that ISO 22400 is an academic overlay disconnected from day-to-day operations.

Communicating changes to suppliers and customers

Aerospace and defense production depends on a complex, regulated supply chain. When you change KPI definitions, your suppliers and customers can be affected, especially if KPIs appear in contracts, supplier scorecards, or performance-based logistics agreements.

For key partners, consider providing:

• A summarized ISO 22400-aligned KPI catalog you intend to use
• Clear mapping from any previously used KPIs to the new definitions
• Transition timelines and how historical performance will be treated

Some organizations use a digital manufacturing platform as a shared lens where both internal teams and suppliers can see KPI definitions and values aligned to the same ISO 22400 semantics. This approach minimizes misunderstandings when comparing performance across different factories or supplier tiers.

Example Implementation Timeline and Pitfalls to Avoid

Phased rollout across sites and systems

ISO 22400 implementation is best approached as a phased program rather than a single “big bang,” especially in multi-site aerospace networks with legacy systems. A typical pattern might look like:

1. Pilot scope definition – Select one value stream or product family (for example, a specific engine model, satellite program, or structural assembly line) and a constrained set of KPIs (for example, availability, utilization, order execution reliability).
2. Discovery and mapping – Complete the KPI inventory, mapping, and data model alignment for the pilot scope, including necessary MES/historian tweaks.
3. Governance and training – Stand up the KPI data dictionary, governance structure, and targeted training for the pilot stakeholders.
4. Pilot operation – Run with ISO 22400-aligned KPIs in parallel with existing reporting for a defined period to build trust and validate behavior.
5. Scale-out – Extend to additional lines, plants, or supplier tiers, reusing the data models and governance patterns built in the pilot.

Timelines will vary by organization size, system complexity, and regulatory constraints. The key is to preserve consistency of definitions while allowing local implementations to adapt to specific equipment, processes, and certification requirements.

Common mistakes in ISO 22400 adoption

Several common pitfalls tend to derail ISO 22400 initiatives in aerospace and defense manufacturing:

• Treating ISO 22400 as a reporting project only – Focusing solely on dashboards and ignoring the underlying state models and data quality leads to attractive visuals with inconsistent semantics.
• Over-customizing the standard – Adding many local variants of KPIs with subtle definition differences defeats the purpose of standardization and complicates multi-site comparisons.
• Underestimating change impact – Changing KPI definitions without careful communication can undermine trust from program teams and external partners who rely on year-over-year comparability.
• Ignoring non-standard but critical KPIs – For aerospace-specific indicators (for example, part genealogy completeness metrics or airworthiness sign-off cycle time), the goal is coexistence with ISO 22400, not forced alignment where it does not fit.

A disciplined approach that distinguishes between ISO 22400-aligned KPIs and intentional, well-documented extensions gives you the benefits of standardization without constraining necessary aerospace-specific measures.

Bringing ISO 22400 into the Aerospace Digital Thread

ISO 22400 does not replace your AS9100 processes, digital thread initiatives, or engineering change control. Instead, it supplies a shared vocabulary for performance measurement that can be woven through existing systems and workflows. When equipment states, time categories, and KPI definitions are standardized, it becomes easier to connect events in design, planning, execution, and quality into a coherent performance narrative.

Platforms like Connect 981 can implement ISO 22400-aligned KPI structures as part of a broader aerospace digital operations layer, tying together MES, ERP, QMS, and supplier data without forcing a single monolithic solution. The standard defines what KPIs mean; your organization decides which ones matter, how aggressively to target them, and how they support safe, compliant, and efficient aerospace production.