In most cases, yes: if your custom KPI is conceptually the same as an ISO 22400 metric, reusing the ISO term and structure is beneficial. However, it is not mandatory and should not be forced where the fit is poor or would confuse existing stakeholders.
When it makes sense to reuse ISO 22400 terminology
Reusing ISO 22400 names and definitions usually helps when:
- The KPI concept matches closely, for example availability, performance, quality rate, OEE-related measures, and many standard production or resource utilization indicators.
- Multiple plants or vendors are involved and you want a common language across different MES, historians, and analytics tools.
- Auditability and traceability matter, because referencing a recognized standard can make it easier to explain how a KPI is defined and maintained, without implying compliance or certification.
- Data integration is a problem today, and aligning to a standard reduces mapping work between systems or sites.
In these situations, adopting ISO 22400 terms (and documenting the link to the ISO definition) can reduce ambiguity, support evidence packages, and make future system upgrades or integrations less brittle.
When you should not force ISO 22400 reuse
There are also valid reasons not to reuse ISO 22400 terminology mechanically:
- Your KPI meaning diverges materially from the ISO definition, for example mixing schedule adherence with throughput in a single composite score.
- Legacy reports and SOPs already rely on a different term and renaming would create confusion or significant retraining burden without clear benefit.
- Regulatory filings, customer contracts, or internal specifications bind you to historical KPI definitions that are not ISO 22400 aligned.
- Your data model cannot support the ISO definition cleanly today due to how downtime, scrap, or rework are captured, and changing it would require high-risk system and validation changes.
In these cases it is often safer to keep the existing term but explicitly document how it differs from the nearest ISO 22400 metric, rather than forcing alignment in name only.
Practical approach in brownfield, regulated environments
In mixed, validated system landscapes, a pragmatic approach typically looks like this:
- Map first, rename later (if at all)
Start by mapping existing KPIs to ISO 22400 concepts where possible. Capture this mapping in a controlled document or data dictionary rather than changing system names immediately.
- Document definitions and formulas
For each KPI, maintain a controlled definition including purpose, formula, data sources, aggregation rules, and any deviations from the ISO 22400 definition. This supports traceability and audit questions regardless of naming.
- Use aliases in tools and specifications
Where systems allow, you can show both the legacy name and an ISO 22400-aligned alias. This is often less disruptive than fully renaming tags, reports, or MES objects.
- Apply change control to any renaming
Renaming KPIs in MES, data warehouses, or reports can affect trending, alerting, and validated calculations. Treat KPI definition and naming changes under the same change control and validation discipline as other configuration changes.
- Avoid full replacement just to match ISO terms
Swapping out existing KPI logic or systems solely to achieve ISO 22400 purity rarely justifies the downtime, revalidation, and integration risk in aerospace-grade or similar environments.
Benefits and tradeoffs of ISO 22400 alignment
Potential benefits:
- More consistent understanding of KPIs across plants, vendors, and functions.
- Simpler interface specifications for MES, historians, and analytics tools.
- Clearer responses in audits when asked how performance is measured and controlled.
- Smoother integration with commercial tools that already reference ISO 22400 structures.
Key tradeoffs and risks:
- Retraining and change impact on operations, quality, and management accustomed to legacy KPI names and dashboards.
- Historical comparability risks if the underlying formula changes while keeping the same name, or vice versa.
- Configuration and validation effort to update MES, data pipelines, and reports under change control.
- Vendor mismatches where off-the-shelf MES or OEE modules use proprietary definitions that only partially align with ISO 22400.
Recommended policy stance
A balanced policy in regulated, long-lifecycle operations is:
- Prefer reuse of ISO 22400 terminology where the KPI meaning and formula are substantially the same.
- Explicitly document any deviations when your custom KPI only partially aligns with an ISO 22400 metric.
- Allow justified exceptions when aligning would introduce confusion, high change cost, or conflict with validated or contractual definitions.
- Maintain a master KPI catalog (under document control) that records the relationship between your KPIs and relevant ISO 22400 metrics.
This approach gains most of the interoperability and clarity benefits of ISO 22400 while respecting brownfield constraints and existing regulatory and validation commitments.
