For KPIs that do not have a direct ISO 2240 equivalent, you should not force a mapping or abandon the metric. Instead, treat ISO 2240 as a reference layer and manage these KPIs explicitly as “non-standard” or “derived” metrics within a governed model.
1. Decide whether the KPI really must map to ISO 2240
Start by asking what the KPI is used for:
- External or cross-site reporting: Prefer ISO-aligned KPIs, or at least a clearly documented derived relationship.
- Local operational control: It is acceptable for a KPI to remain non-standard if it drives real decisions and cannot be expressed meaningfully via ISO 2240.
If the KPI is only used locally and is well understood by that team, it does not need a forced ISO 2240 equivalent, but it still needs documentation and governance.
2. Classify KPIs against ISO 2240
To avoid confusion across functions and sites, explicitly label each KPI in your portfolio as one of:
- Standard: Directly defined in ISO 2240, using the ISO name, definition, and formula.
- Mapped/alias: Your KPI is conceptually the same as an ISO 2240 KPI but uses a different name or minor formula variations (for example, different time buckets). Document the mapping and differences.
- Derived from ISO 2240: Your KPI is a calculated combination of one or more ISO 2240 KPIs (for example, a composite productivity index).
- Non-standard / unmapped: No direct, meaningful ISO 2240 equivalent exists. These require a clear rationale and ownership.
This classification should be maintained in a central KPI catalog, not hidden in local spreadsheets.
3. Document unmapped KPIs rigorously
For KPIs that have no direct ISO 2240 equivalent, treat documentation and traceability as your main control mechanism:
- Precise definition: Name, purpose, formula, units, data sources, and calculation frequency.
- Scope and boundaries: Which assets, product families, shifts, or plants it covers. Note any exclusions.
- Owner and consumers: Who is accountable for the KPI and which roles use it in decision-making.
- Relation to ISO 2240: State explicitly “no direct ISO 2240 equivalent” and, if helpful, note the closest concepts and why they are not suitable substitutes.
- Validation and change control: How the KPI logic is validated and how changes are reviewed, approved, and versioned.
This level of documentation is especially important in regulated environments, where auditors and internal quality teams will ask how metrics tie back to defined standards and procedures.
4. Provide a mapping or translation layer where possible
Where the KPI is important for cross-site comparison or corporate reporting, build an explicit translation layer:
- Upstream data: Whenever possible, base both ISO 2240 and non-standard KPIs on the same raw data elements and event definitions.
- Transformation logic: Document any formulas, assumptions, and filters that transform raw data into the non-standard KPI.
- Derived ISO view (if feasible): Even if the KPI itself has no equivalent, see whether a separate ISO 2240 KPI can be produced from the same data for comparability.
Technically, this often sits in your data warehouse, MES reporting layer, or analytics platform. The key point is to keep the logic transparent and version-controlled.
5. Govern non-standard KPIs like configuration, not like ad-hoc reports
In long-lifecycle, regulated operations, KPI definitions tend to live for years and drive important decisions. Treat them accordingly:
- Formal change control: Modifying the definition of an unmapped KPI should follow a documented process, with impact analysis, approvals, and version history.
- Traceability: Make it possible to answer “which KPI definition was in effect when we made this decision or filed this report?”
- Validation: If KPIs feed into validated systems (for example, quality dashboards used in release decisions), changes may require re-validation or at least documented verification.
- Periodic review: At an agreed interval, review unmapped KPIs to see whether they should be retired, merged, or aligned to newer versions of standards.
This avoids a landscape where each plant or engineer invents metrics that cannot survive audits or leadership scrutiny.
6. Be explicit about limits when comparing across sites
One common failure mode is treating a local, non-standard KPI as if it were comparable across all plants or product lines. For unmapped KPIs:
- Do not: Use the metric for direct benchmarking unless its definition, data source, and scope are identical in each site.
- Do: Label charts and dashboards clearly as “local KPI” or “non-standard,” especially in corporate or multi-plant views.
- Do: Provide an ISO 2240 metric alongside it when stakeholders expect comparability.
Where plants use different non-standard KPIs for similar purposes, consider adding a small set of ISO-based KPIs as a common layer for comparison, while still allowing local metrics for day-to-day control.
7. Coexistence with legacy MES/ERP and local spreadsheets
In brownfield environments, many non-standard KPIs live in plant-level spreadsheets or custom MES reports. Replacing them wholesale with only ISO 2240 metrics often fails because:
- Local KPIs encode hard-earned operational knowledge or constraints not reflected in the standard.
- Re-qualifying every metric in every system can be costly and disruptive.
- Downtime and validation burdens make large-scale metric overhauls hard to justify.
A more realistic approach is:
- Keep operationally critical local KPIs in place, but bring their logic and data into a governed catalog.
- Introduce ISO 2240 metrics as additional, not replacement, views where they add value.
- Gradually harmonize overlapping local KPIs when the benefit (better comparability, simpler reporting) outweighs the cost of change and re-validation.
This coexistence approach respects existing systems and processes while still moving you toward greater standardization and transparency.
8. When to retire or redesign an unmapped KPI
Not all non-standard KPIs deserve to live forever. Consider retiring or redesigning an unmapped KPI when:
- It duplicates the intent of an ISO 2240 KPI, but with a confusingly different formula.
- No clear owner can explain how it is used in decisions.
- Maintaining it creates significant overhead in reporting, integration, or validation.
- It encourages behavior that conflicts with quality, safety, or regulatory priorities.
In those cases, design a migration path to either an ISO 2240 metric or a better-defined local metric, with clear communication and transition rules.
In summary, KPIs without a direct ISO 2240 equivalent should be treated as first-class, governed metrics: clearly labeled as non-standard or derived, documented, validated where needed, and used with explicit limits on cross-site comparability. ISO 2240 becomes the common reference, not the only set of metrics allowed.
