Yes, you can mix ISO 22400 KPIs with custom metrics in a single report, but you should do it deliberately and with strong governance so you do not lose clarity or traceability.
Key conditions for mixing ISO 22400 and custom metrics
- Explicit labeling: Clearly distinguish which indicators are ISO 22400 KPIs and which are site- or system-specific. Use consistent, visible labels in the report (for example, “ISO 22400: OEE” vs. “Plant-specific: Setup Efficiency”).
- Stable, documented definitions: Maintain a metric catalog or data dictionary that records for each metric: name, category (ISO vs custom), exact formula, units, data sources, and owner. This is important for audits, investigations, and cross-plant comparisons.
- No silent redefinition: Do not change the ISO 22400 formula or intent and still call it an ISO 22400 KPI. If you need a variant, treat it as a separate, custom metric with its own name and definition.
- Clear data lineage: Be able to trace where each metric comes from (MES, SCADA, ERP, manual input) and how transformations are applied. Mixed reports that feed decisions about capacity, quality, or compliance should have reproducible calculations.
- Governance and change control: Changes to metric definitions, source mappings, or aggregation logic should follow your existing change control, especially if reports are used in management reviews, CAPA, or regulatory evidence.
Common failure modes when mixing metrics
- Confusing standardized KPIs with local variants: Plants sometimes call a locally modified OEE calculation “ISO OEE,” which breaks comparability and can cause management to misinterpret trends across sites.
- Inconsistent time bases and scopes: Combining KPIs based on different time windows, shift definitions, or inclusion/exclusion rules (for example, planned vs unplanned downtime) without documenting this makes benchmarking misleading.
- Hidden manual adjustments: Manual corrections or spreadsheet-layer logic applied to some metrics but not others can undermine trust, especially when the report is used as part of audit evidence or RCA.
- Multiple truth sources: Pulling ISO KPIs from MES and custom metrics from ad hoc spreadsheets or a different data mart, with no reconciliation, often results in conflicting numbers during reviews.
Implications for brownfield, multi-system environments
In typical brownfield environments with legacy MES/SCADA, ERP, and point solutions, a mixed ISO/custom report is usually assembled from multiple systems rather than one clean source. That is acceptable, but it increases the importance of:
- Integration mapping: Make sure your integration layer or reporting tool maps raw events and states to ISO 22400 semantics correctly, while separately modeling custom states and codes.
- Version control: If you adjust how machines, orders, or downtime reasons map into your ISO KPIs, log that change. Otherwise, a visible step change in a KPI can be mistaken for an operational improvement or degradation.
- Validation and reconciliation: Periodically reconcile key ISO KPIs and major custom metrics against source systems. For example, validate that “ISO 22400 availability” computed in the data warehouse matches the same KPI computed in MES within an acceptable tolerance.
- Coexistence, not replacement: Do not assume that adopting ISO 22400 requires ripping out existing plant metrics. In regulated, long-lifecycle operations, full metric-model replacement is rarely practical due to validation, retraining, and change-control burden. A gradual coexistence model is safer: keep legacy metrics where they are needed and introduce ISO 22400 KPIs alongside them, with clear mapping and explanation.
How to structure a combined report in practice
- Group by origin: Separate sections for “ISO 22400 KPIs” and “Plant / Program-specific metrics” in the same report. This preserves comparability while giving local teams the flexibility they need.
- Make dependencies explicit: If a custom metric is derived from an ISO KPI (for example, “OEE loss due to changeovers”), state that dependency in the definition and, where possible, visually in the report.
- Align with decision use cases: Design the report around the decisions it supports: shift review, weekly performance, management review, or CAPA effectiveness. This will drive how much detail and traceability you must show for each metric.
- Document usage in procedures: If these reports feed into formal quality or management processes, reflect the ISO vs custom distinction and usage rules in your procedures or work instructions.
In summary, mixing ISO 22400 KPIs with custom metrics in a single report is feasible and often desirable, provided you clearly distinguish them, maintain strong definition and change control, and validate the combined view against your underlying systems.
