The Limits of ISO 22400: When and How to Use Custom KPIs

ISO 22400 gives manufacturers a common language for performance measurement, not a fixed list of KPIs or improvement recipes. To use the standard effectively, you need to understand what it standardizes, what it intentionally leaves undecided, and how to design custom KPIs that work alongside it without creating confusion.

This article explains the practical limits of ISO 22400 and provides concrete guidance for introducing complementary, non-standard KPIs in a controlled way. The goal is to balance cross-site comparability with the flexibility you need for your industry, plants, and improvement programs. For a broader overview of the standard’s scope and core KPI framework, see our hub article on ISO 22400 manufacturing KPIs and their scope and boundaries.

Understanding What ISO 22400 Intentionally Leaves Open

ISO 22400 defines concepts, terminology, and KPI structures for manufacturing operations management. It is focused on semantic clarity and interoperability across systems and organizations. To preserve that neutrality, the standard deliberately avoids taking positions on business strategy or local optimization tactics.

No prescriptions on strategy, targets, or KPI selection

ISO 22400 clarifies what indicators such as availability, utilization, or order execution reliability mean. It does not decide which of these indicators matter most to your business or how you should prioritize them.

• No strategic priorities: The standard does not say whether you should focus first on OEE, throughput, energy efficiency, or delivery reliability.
• No target values: It does not define what constitutes a good, acceptable, or poor value for any KPI. A 75% OEE may be excellent in one highly variable environment and insufficient in a stable, high-volume line.
• No required KPI set: Although ISO 22400-2 lists 34 KPIs, this list is illustrative and conceptual, not a mandatory checklist. You can use some, all, or none, and you can add your own.

Because of this, it would be a misunderstanding to use ISO 22400 as a ready-made performance scorecard. You still need a separate strategy process to decide which KPIs are truly key in your context and how they support business objectives.

No enforcement of granularity, weighting, or thresholds

Another intentional limit is that the standard does not prescribe how detailed your KPIs must be or how they should be aggregated.

• Granularity choices: ISO 22400 can be applied to work units, lines, areas, sites, or orders. It does not say whether your “official” OEE should be calculated by machine, by line, or by plant.
• No weighting rules: If you combine KPIs into a composite score (for example, a plant performance index), the standard does not dictate how to weight availability vs. quality vs. cost.
• No thresholds or traffic lights: Red/yellow/green bands, control limits, and early-warning rules are left to your internal standards and governance.

These omissions are not gaps; they are boundaries. ISO 22400 aims to stay broadly applicable across industries and business models. Mandating granularity or thresholds would make it too rigid for many use cases.

No required calculation algorithms or visualization methods

While ISO 22400 describes KPI concepts, it often stops short of prescribing a single, implementation-ready formula or visualization.

• Calculation details: It defines logical relationships between time categories and quantities, but it does not mandate specific sampling rates, filtering rules, or how to handle ambiguous events.
• Data preparation: It does not tell you exactly how to reconcile signals from multiple systems (for example, reconciling MES and historian time stamps) as long as the result conforms to the conceptual definitions.
• Visualization: There is no requirement to use waterfalls, Pareto charts, Sankey diagrams, or any specific dashboard style. The standard is technology-neutral.

This gives organizations freedom but also creates the need for internal conventions. If two plants interpret the same KPI differently in terms of data preparation, they will both be aligned to ISO 22400 conceptually yet still be hard to compare. Internal alignment on implementation choices is therefore crucial.

Identifying Gaps Where Custom KPIs Are Needed

Because ISO 22400 is industry-neutral and deliberately limited in scope, many organizations will need custom KPIs that go beyond its 34 examples. The challenge is to recognize where these additions are justified and how to design them responsibly.

Regulatory or sector-specific requirements

Some industries operate under regulatory regimes or contractual frameworks that demand indicators outside the standard’s scope.

• Aerospace and MRO: Metrics around airworthiness release times, maintenance turnaround time (TAT) per aircraft, or compliance with mandatory inspections are unlikely to appear in a general manufacturing standard.
• Pharmaceuticals: Batch genealogy completeness, deviation closure time, and validated cleaning cycle performance are driven by GMP and similar regulations.
• Food and beverage: Shelf-life-related quality metrics, allergen changeover performance, or sanitation window adherence might be essential but non-standard.

In these cases, custom KPIs are not optional extras; they are required to demonstrate compliance or meet contractual obligations. ISO 22400 remains useful as a conceptual backbone, but it cannot replace sector-specific performance measures.

Company-specific process characteristics

Two companies in the same industry may have very different process architectures, automation levels, and risk profiles. This often calls for tailored KPIs.

• Unique technologies: An additive manufacturing shop may track build-job restart rate or laser utilization in ways that do not map cleanly to the standard KPI set.
• Highly customized products: Engineer-to-order environments may need indicators focused on engineering change propagation, first-article approval cycles, or configuration accuracy.
• Complex supply networks: Organizations with deep subcontracting structures may introduce KPIs that track external processing reliability or inbound quality in special ways.

These indicators can still be aligned with ISO 22400 by reusing concepts such as work units, states, or order-level views, even when the metric itself is non-standard.

Innovation and continuous improvement programs

Improvement initiatives often experiment with new ways of measuring performance before it makes sense to standardize those metrics widely.

• Pilot KPIs: A plant might trial an operator workload balance index, a changeover robustness score, or a digital-ization adoption indicator for a limited time.
• Lean and Six Sigma projects: DMAIC phases often introduce temporary diagnostic metrics that are too specific or short-lived to be candidates for formal inclusion in internal standards.
• Data science and analytics: Predictive maintenance models or anomaly detection may produce composite health scores that are not (yet) part of any standard.

These innovation-driven KPIs are legitimate, but they must be clearly distinguished from formally standardized indicators and carefully documented to avoid misinterpretation.

Design Principles for Custom KPIs Alongside ISO 22400

When you add KPIs beyond ISO 22400, your goal should be complementarity, not competition. Good design preserves the benefits of standardization while giving you the freedom to measure what matters locally.

Reusing ISO 22400 concepts and terminology where possible

The quickest way to keep your KPI landscape coherent is to base custom metrics on ISO 22400 building blocks.

• Use standard objects: Define measurement objects using the same hierarchy (work unit, work center, area, site, enterprise) that ISO 22400 and IEC 62264 reference.
• Reuse time categories and states: If your custom indicator depends on machine behavior, map its logic to the RUN, STOP, IDLE, and other states used to derive time-based KPIs in the standard.
• Align quantity definitions: Distinguish clearly between produced quantity, accepted quantity, and rejected quantity using ISO 22400 terminology wherever applicable.

By grounding your custom KPIs in the same conceptual foundation, you simplify both technical integration and human understanding.

Avoiding conflicting names and overlapping definitions

Confusion often arises when two metrics have similar names but different meanings, or when different departments define the same term differently. To prevent this:

• Do not overload ISO names: Avoid reusing terms such as “availability,” “utilization,” or “OEE” with non-standard meanings. If you need a variant, give it a distinct name (for example, “maintenance availability index”).
• Flag variants explicitly: If you intentionally deviate from an ISO 22400 definition, indicate this clearly in the KPI documentation and name, such as “OEE (local variant – setup included in busy time).”
• Check for overlap: Before creating a new KPI, check whether an existing one already covers most of the need. Redundant indicators dilute focus and create reporting overhead.

This naming discipline helps everyone understand which KPIs are truly comparable across sites and which are local or experimental.

Documenting derivations and assumptions clearly

Custom KPIs often chain together several data transformations and assumptions. Without documentation, they become opaque and hard to trust.

• Define purpose and users: State why the KPI exists (e.g., “to monitor maintenance-induced delays in MRO hangars”) and who is expected to act on it.
• Specify inputs and logic: List all input data elements, their sources, and the calculation steps. Show how it relates (if at all) to ISO 22400-defined indicators.
• Describe limitations: Note approximations, data quality constraints, or contexts where the KPI should not be used for comparison or incentives.

Good documentation transforms a custom KPI from a black box into a transparent tool that can be tested, audited, and improved.

Labeling and Cataloging Custom KPIs

Once you go beyond the ISO 22400 set, transparency depends on how well you label and organize your KPIs. Treating them as first-class, cataloged objects reduces misinterpretation and maintains comparability where it matters.

Distinguishing ISO 22400-based KPIs from non-standard ones

In your KPI catalog or reporting tools, make it obvious which indicators are based on ISO 22400 and which are not.

• Use explicit flags: Add metadata such as standard_reference = “ISO 22400” or standard_reference = “none (custom)”.
• Link to definitions: For each KPI that is directly aligned with ISO 22400, reference the relevant part and clause in the documentation.
• Clarify status: Distinguish between approved standard KPI, site-specific KPI, and experimental KPI so that users know how much governance stands behind each metric.

This clarity prevents users from assuming that every metric in a dashboard is part of an international standard when, in reality, many are local additions.

Tagging KPIs by domain, level, and purpose

Effective cataloging includes several dimensions of metadata beyond just “standard” vs. “custom.” At minimum, consider:

• Domain: Production, maintenance, quality, logistics, energy, safety, compliance, etc.
• Organizational level: Enterprise, site, area, line, work center, work unit, order/lot.
• Time horizon: Real-time, shift, day, week, month, order lifecycle.
• Purpose: Monitoring, early warning, diagnosis, optimization, compliance reporting, incentive calculation.

These tags make it easier to search, filter, and govern KPIs as your landscape grows across multiple sites and business units.

Using a catalog or dictionary that references the standard

Instead of maintaining KPI definitions in scattered documents or local spreadsheets, consolidate them into a centralized catalog.

• Single source of truth: A KPI dictionary ensures that the name, definition, formula, and ownership of each KPI are maintained in one place.
• Explicit linkage to ISO 22400: Where applicable, the catalog entry should note which ISO 22400 concept or KPI it builds upon, including any modifications.
• Lifecycle management: Track when KPIs are introduced, revised, or retired so that old reports can be interpreted correctly.

Many organizations implement this catalog inside their BI platform, MES, or a dedicated data governance tool, but the principle is the same: KPIs should be managed like master data, not ad hoc artifacts.

Examples of Complementary, Non-Standard KPIs

To illustrate how custom KPIs can coexist with ISO 22400, consider some examples from different domains. None of these are official parts of the standard, but they can be built on its concepts and integrated into a coherent KPI framework.

Domain-specific metrics in aerospace and MRO

Aerospace manufacturing and maintenance, repair, and overhaul (MRO) operations must handle complex traceability, safety, and regulatory requirements. Typical complementary KPIs include:

• Turnaround Time (TAT) per Aircraft or Work Package: Measures the elapsed time from induction to release to service. It may be broken down by work unit or area using the same hierarchical levels that ISO 22400 recognizes.
• On-Time Maintenance Release Rate: Percentage of maintenance events completed on or before the planned release time, linked to production-order-like objects in the ISO framework.
• Non-Routine Work Ratio: The share of maintenance hours triggered by unplanned findings, complementing standard utilization or availability KPIs.

These metrics address realities that ISO 22400, as a general manufacturing standard, does not cover, while still leveraging standard concepts such as orders, work units, and time categories.

Lean and continuous improvement indicators

Lean manufacturing, TPM, and other improvement methodologies often rely on indicators that do not appear as such in ISO 22400 but can use its terminology.

• Changeover Performance Index: Relates actual changeover duration to a target or benchmark, using ISO-aligned time definitions to capture setup and adjustment states.
• Flow Efficiency: Ratio of value-adding time to total lead time for a product family or order type, reusing the standard’s differentiation between active and idle states.
• Kaizen Implementation Rate: Measures the percentage of proposed improvements that are implemented, operating at a higher organizational level than most ISO 22400 KPIs.

These indicators support culture and process change while benefiting from consistent underlying definitions of states, orders, and time horizons.

Combined financial-operational performance indexes

ISO 22400 focuses on operational KPIs at manufacturing operations management level, while many business decisions demand indicators that combine cost, revenue, and operational performance.

• Cost per Good Unit Shipped: Combines operational data (good quantity, scrap, rework) with cost information from ERP systems.
• Contribution Margin per Constraint Hour: Ties product margins to utilization of bottleneck resources modeled as work units or lines.
• Service-Level-Adjusted Utilization Index: Adjusts standard utilization measures with penalties for missed delivery windows or expedited freight.

These composite indicators sit at the interface between Level 3 (MOM) and Level 4 (business planning) and must be clearly marked as outside the formal ISO 22400 scope, even when they reuse its concepts.

Maintaining Coherence in KPI Landscapes Over Time

Even well-designed KPI frameworks can drift over the years as processes change, systems are replaced, and new plants are acquired. Keeping your KPI landscape coherent requires ongoing governance, not a one-time project.

Periodic reviews to reduce duplication and drift

Regularly review your KPI portfolio to ensure it remains aligned with strategy and standards.

• Identify duplicates and near-duplicates: Consolidate metrics that measure essentially the same thing but use slightly different formulas or names.
• Retire obsolete indicators: Remove KPIs that no longer inform decisions or reflect current process realities.
• Confirm ISO alignment: Check that KPIs labeled as ISO 22400-based still match the standard’s definitions, especially after system upgrades or model changes.

These periodic reviews prevent KPI bloat and help keep dashboards meaningful and actionable.

Using platforms like the KPI hub to maintain clarity

Reporting and integration platforms can embed ISO 22400 concepts and your internal KPI catalog so that users see consistent definitions wherever they work.

• Centralized definitions: Dashboards, reports, and analytics should all reference the same KPI dictionary and explicitly indicate when a metric is standard-aligned vs. custom.
• Integrated metadata: Tooltips, drill-downs, and API responses can expose KPI metadata (definition, owner, standard reference, calculation version) so users understand what they are seeing.
• Controlled change management: Changes to KPI formulas or status (for example, from experimental to standard) should flow through a formal governance process and be reflected in all consuming systems.

By treating KPI definitions as shared infrastructure, you reduce local improvisation that might undermine comparability.

Aligning internal standards with evolving business needs

Finally, remember that your internal KPI standards must evolve with your business model, technology, and regulatory environment, while still staying grounded in widely understood concepts like those in ISO 22400.

• Revisit key KPIs: As new products or services emerge, some metrics may become more or less relevant; adjust your official KPI set accordingly.
• Incorporate proven custom KPIs: When experimental indicators consistently provide value, consider promoting them into your internal standard, with full documentation and governance.
• Monitor external standards: Keep an eye on updates to ISO 22400 and related standards so that your internal definitions do not drift away from the broader ecosystem.

This continuous alignment ensures that your KPI framework remains both locally effective and externally interpretable, preserving the benefits of standardization without sacrificing flexibility.

Conclusion: Using ISO 2240 0 as a Stable Backbone, Not a Complete Menu

ISO 22400 provides a powerful, shared vocabulary for manufacturing KPIs, but it intentionally stops short of telling you which KPIs to choose, what targets to set, or how to visualize performance. Those decisions are, and should remain, specific to your strategy, industry, and operations.

By recognizing the limits of the standard, you can design custom KPIs that complement it rather than conflict with it. Reuse ISO 22400 concepts, avoid ambiguous naming, document your assumptions, and maintain a governed KPI catalog. Over time, this approach lets you add the regulatory, sector-specific, financial, and innovation-driven indicators you need while keeping cross-site and cross-partner comparability intact.

For a broader discussion of the ISO framework itself and its role in interoperable performance measurement, refer back to our hub on core ISO 22400 manufacturing KPI scope and boundaries. Start with a solid backbone, then extend it carefully to reflect what truly matters in your operations.

For teams putting aviation and cross-sector software into daily operation, ISO 22400 KPI governance, aviation and cross sector software, a connected execution platform help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

For teams putting aviation and cross-sector software into daily operation, Connect 981’s aerospace execution solutions, real aerospace execution examples help connect the concept to traceability, work-order reality, and audit-ready evidence.