ISO 22400 does not prescribe exact dashboard labels, but in regulated, multi-site environments you should make the ISO basis explicit and distinguish between the standard KPI and any local variant. The goal is to avoid silent divergence of definitions across MES, SCADA, BI, and plant-specific dashboards.
Core labeling pattern
A practical, auditable pattern is:
- Primary label (business-friendly): Short, readable name for operators and managers (e.g. “OEE”, “Availability”, “Quality Rate”).
- Secondary label (ISO reference): Show the ISO 22400 identifier and official term nearby (e.g. “ISO 22400-2: KPI 5 – Overall Equipment Effectiveness”). This can be in a subtitle, tooltip, or info icon.
- Formula hint: A short text or hover help showing the denominator, included losses, and time basis (e.g. “Based on ISO 22400-2, 8-hour planned time, includes minor stops, excludes planned maintenance”).
This keeps dashboards usable day to day while maintaining traceability to a documented, standard definition.
Distinguishing standard vs local variants
In brownfield environments, many KPIs are already implemented with plant-specific logic. When you align with ISO 22400, avoid relabeling existing metrics as “ISO” unless the implementation actually matches:
- Use explicit tags for variants: For example, “OEE (Local – excludes setup)” vs “OEE (ISO 22400-2)” if you maintain both.
- Avoid ambiguous short labels: A card simply labeled “Availability” without context is risky when different systems treat micro-stops, setups, and changeovers differently.
- Document the difference: In KPI documentation and data catalog, include a short statement such as “Differs from ISO 22400-2 by excluding changeover time from planned time.”
Minimum information to show near each KPI
Where possible, each ISO 22400-based KPI on a dashboard should expose:
- Name: Friendly label (e.g. “Availability”, “Performance”, “Quality Rate”, “OEE”).
- Standard reference: ISO 22400 part and KPI identifier where defined (e.g. “ISO 22400-2 KPI 6 – Availability”).
- Time basis: Shift, day, week, or custom, and whether this is “planned time” vs calendar time.
- Scope: Whether the KPI is per line, machine, cell, or plant.
- Inclusions/exclusions: At least a short list of key inclusions/exclusions (e.g. “Includes minor stops; planned maintenance excluded from planned time”).
The details can be in a hover tooltip, drill-down, or a linked KPI definition page to avoid cluttering the main view.
Coexistence with existing MES/BI labels
In long-lived, regulated operations, a full relabeling of all dashboards to align with ISO 22400 often creates confusion and retraining burden. A more realistic approach is:
- Keep legacy labels where necessary for continuity, but add an ISO reference line or icon (e.g. “Legacy OEE (not ISO 22400)”).
- Introduce ISO 22400 views incrementally, starting with new dashboards or specific pilot lines, clearly marked as “ISO 22400-aligned KPIs”.
- Use consistent mapping in all tools: The same KPI name and ISO reference should appear in the MES screen, BI report, and any exported PDF used in reviews.
This minimizes disruption while increasing transparency about what is and is not standard-aligned.
Governance and change control
In regulated environments, labeling is part of KPI governance, not just UI design. To keep ISO 22400 KPIs reliable over time:
- Maintain a KPI catalog that records: name, business owner, ISO 22400 reference, formula, data sources, and known deviations.
- Route KPI definition changes through change control, especially if the formula or data source changes but the dashboard label stays the same.
- Validate calculations on each major system (MES, historian, BI) so that the same labeled KPI actually produces the same result across tools.
Without this discipline, dashboards can show identically labeled ISO KPIs that are not comparable across plants or systems.
Common pitfalls to avoid
- Using “ISO 22400” as a label without conformance: If you cannot match the standard definition due to data gaps or integration limits, label the KPI as a local variant and document the gap.
- Hiding ISO references entirely: Helps adoption in the short term but makes audits, cross-plant comparisons, and troubleshooting harder.
- Letting each plant rename KPIs freely: Leads to incompatible definitions under similar names. Use controlled label sets where possible.
Overall, label ISO 22400 KPIs so that operators can read them at a glance, while engineers, quality, and auditors can trace them back to a clear, documented standard definition.
