How does ISO 22400 change the way we name KPIs?

ISO 22400 does not dictate a new naming convention you must adopt word for word, but it does change how you think about, structure, and document KPI names.

What ISO 22400 actually standardizes

ISO 22400 defines:

• A set of standard manufacturing performance indicators (e.g. OEE, availability, performance, quality rate).
• How those indicators are calculated, including required inputs and time bases.
• Conceptual relationships between KPIs, base measures, and manufacturing operations management functions.

In practice, this means you can and should treat ISO 22400 terms as the canonical names and definitions behind your local KPI labels, even if your plant has used different shorthand for years.

Typical impact on KPI naming

In brownfield, regulated environments, ISO 22400 usually leads to a layered approach instead of a wholesale rename.

1. Canonical vs. display names
   You define a canonical name consistent with ISO 22400, and allow local display names where necessary.
   Examples:
   • Canonical (ISO-consistent): OEE (Overall equipment effectiveness)
     Local label on dashboards: “Line utilization”
   • Canonical: Availability rate
     Local label: “Run-time %”

   The key change is that you document that “Line utilization” maps to the ISO 22400 definition of OEE, not a homegrown formula.

2. Disambiguation of overloaded terms
   ISO 22400 forces you to clarify terms that have been used inconsistently:
   • “Utilization” may mean availability to one team and OEE to another.
   • “Yield” may mix first-pass yield, rolled throughput yield, and scrap rate.

   Under ISO 22400, you distinguish these with precise names tied to defined formulas (e.g. “quality rate” as the ratio of good units to total units in the reference period).

3. Structured naming based on calculation scope
   The standard emphasizes:
   • Time basis (shift, day, order, batch, calendar vs. run-time).
   • Aggregation level (equipment, line, area, plant).
   • Scope of losses (e.g. including or excluding planned stops).

   This often results in more explicit names, such as:

   • “OEE_line_A_shift” vs. a generic “OEE” KPI.
   • “Availability_incl_planned_stops” vs. “Availability_excl_planned_stops” instead of a single ambiguous “Availability” metric.
4. Clear separation of base measures from KPIs
   ISO 22400 distinguishes raw measures (e.g. “scheduled production time”, “unplanned downtime”) from calculated indicators.
   Naming often shifts from a flat list of “KPIs” to a hierarchy:
   • Base measures: “Planned production time”, “Unplanned downtime”, “Produced quantity”, “Good quantity”.
   • Derived KPIs: “Availability rate”, “Performance rate”, “Quality rate”, “OEE”.

   In MES/BI models, this usually means more systematic measure names and less duplication of slightly different formulas under the same label.

Why you usually don’t rename everything

In established, regulated plants, full renaming of KPIs is rare and risky:

• Historical continuity: Sudden label changes break trend analysis, confuse auditors, and can invalidate pre-existing reports unless mappings are very clear.
• Validation and change control: MES, historian, and analytics changes that affect KPI names or definitions may require formal impact assessment, revalidation, and updated procedures.
• Multiple systems: ERP, MES, SCADA, and QMS often have their own hard-coded or configured KPI labels. Aligning every UI label to ISO 22400 can be more disruptive than beneficial.

Because of this, most organizations adopt ISO 22400 as a reference model instead of a strict renaming prescription:

• They keep plant-facing names where those are entrenched.
• They maintain a centrally governed mapping to ISO 22400 names and formulas.
• They gradually converge new reports and systems to the ISO vocabulary.

Practical steps for using ISO 22400 in KPI naming

If you want to align with ISO 22400 without breaking existing operations:

1. Inventory and map existing KPIs
   List current KPIs, definitions, and formulas per plant/system. Map each to the closest ISO 22400 indicator or base measure, or flag it as “non-standard” if it doesn’t match.
2. Define canonical KPI names and definitions
   For each mapped KPI, define:
   • The canonical name (aligned with ISO 22400 terminology).
   • The formal formula (inputs, filters, time base).
   • Permitted aliases or local display names.
3. Create and govern a KPI dictionary
   Store this in a controlled repository (e.g. within QMS or data governance tooling). This supports traceability and aids audits: you can show that “Line utilization” in a dashboard is the ISO 22400 OEE calculation for a specified scope.
4. Align new projects to ISO 22400 first
   For new MES, historian, or analytics deployments, use ISO 22400-compliant names by default, with clear aliases if operators are used to other terminology. This avoids growing technical and semantic debt.
5. Handle changes under formal change control
   If you change definitions or labels in validated systems, treat that as a controlled change: impact analysis, documentation updates, retraining, and where applicable, revalidation.

Coexistence with legacy metrics and systems

ISO 22400 is designed to help with interoperability and comparability, but most aerospace and similarly regulated plants operate in brownfield environments. Realistically:

• You will have legacy KPIs that have no clean ISO 22400 equivalent. You can still document them and mark them as plant-specific.
• Different systems may compute the same named KPI differently. ISO 22400 gives you a target; closing those gaps requires data model harmonization, not just renaming.
• Attempting a complete KPI replacement in one step is likely to fail due to validation overhead, training needs, and the need to preserve audit trails and historical analyses.

Using ISO 22400 as a backbone for naming and definitions, while allowing pragmatic coexistence with existing labels, is usually the most workable path in long-lifecycle, regulated environments.