In most cases, yes. ISO 22400 focuses on how manufacturing KPIs are defined, structured, and calculated, not on forcing every plant to adopt identical KPI labels. You can typically keep your existing KPI names if you can demonstrate a clear and controlled mapping to the ISO 22400 model.
What ISO 22400 actually expects
ISO 22400 defines concepts, KPI structures, and calculation methods (for example, for OEE, availability, and performance). It does not require you to rename every KPI in your MES, ERP, or BI tools. Instead, it expects:
- Consistent KPI definitions and formulas for a given term.
- Clear understanding of which signals and time bases are used.
- Traceability from raw data to KPI output.
- Ability to compare like-for-like KPIs across lines, plants, or partners that also reference ISO 22400.
Keeping your current names: conditions and guardrails
You can usually keep existing KPI names and still align with ISO 22400 if you:
- Document a mapping from your KPIs to ISO 22400 KPIs (or justify why a KPI is out of scope).
- Clarify semantics where your historical names differ from ISO 22400 usage (for example, your “OEE” might exclude some losses that ISO 22400 includes).
- Align formulas and data sources to the ISO 22400 definitions, even if the on-screen label stays the same.
- Control changes through your existing change control, validation, and IT/OT governance processes.
If you cannot reconcile your formula, data filters, or time base with ISO 22400 without confusing users, keeping the old name may be more misleading than changing it.
When keeping names causes problems
Keeping legacy KPI names can create risk in some situations:
- Different formulas, same label: If your local “OEE” does not match ISO 22400 OEE, calling it OEE in external reports can be misleading. In that case, you may need distinct labels such as “OEE (Plant A definition)” and “OEE (ISO 22400)” or clear qualifiers in documentation.
- Multi-plant comparisons: If plants use the same name but different loss models, the data is not truly comparable. You either standardize the logic or explicitly treat them as separate KPIs.
- Brownfield system constraints: Older MES/SCADA may not support nuanced naming or the data segmentation needed to cleanly implement ISO 22400 semantics. Workarounds (for example, calculated KPIs in a data warehouse) must be clearly documented.
- Audit and customer expectations: If you claim ISO 22400 alignment, you need to show how your KPIs map to the standard. Inconsistent naming with no mapping or evidence will be hard to defend.
Practical way to approach this in brownfield environments
In mixed-vendor, multi-plant stacks, full renaming across MES, ERP, historians, and BI tools is often disruptive and high risk due to validation, re-training, and downtime constraints. A more realistic approach is:
- Inventory your KPIs by system, plant, and owner, including formula and data source.
- Map to ISO 22400 KPIs in a controlled reference (for example, a KPI catalog under document control).
- Tag ISO-aligned KPIs in your data warehouse or semantic layer, even if the front-end labels stay legacy.
- Gradually harmonize naming and formulas as you update systems, rather than attempting a one-time global rename.
- Train users so they understand which KPIs are ISO 22400 aligned and what caveats exist for legacy ones.
This lets you achieve functional ISO 22400 alignment without the risk and cost of a wholesale KPI renaming program across validated or safety-critical systems.
Evidence you should be prepared to show
If you reference ISO 22400 in internal standards, customer discussions, or audits, you should be able to produce:
- A KPI catalog that defines each KPI, its formula, time base, and data source.
- A mapping of each catalog entry to the relevant ISO 22400 KPI or a clear “not applicable” rationale.
- Change history and approvals for modifications to KPI logic, stored under your normal change control.
- Validation or verification records for any re-implemented KPI logic in MES, data warehouses, or BI tools.
With that in place, keeping legacy KPI names in user interfaces is usually compatible with ISO 22400 alignment, as long as the underlying definitions and mappings are controlled and transparent.
