Yes, you can show ISO 22400 KPIs alongside financial metrics on one dashboard, but you should treat them as linked but distinct views, not as interchangeable measures. The value is in making the connection between technical performance and financial impact visible, while preserving ISO 22400 definitions, data lineage, and auditability.
What is safe to combine on one dashboard?
Generally acceptable:
- Displaying ISO 22400 KPIs (for example, Availability, Performance, Quality rate, OEE) in one area of the dashboard and financials (for example, labor cost, scrap cost, overtime, contribution margin) in another.
- Providing calculated context metrics that link them, such as “scrap cost driven by ISO 22400 Quality losses” or “capacity cost of unplanned downtime.”
- Using common filters and drill-down (for example, by line, product family, shift, date) so that users can see how a change in an ISO KPI aligns with cost or margin changes.
This approach keeps the ISO KPIs recognizable and traceable, while allowing finance and operations to discuss the same reality.
Key constraints and risks
Mixing operational and financial data on one dashboard in a regulated, brownfield environment introduces several risks that you need to manage explicitly:
- Definition drift: If you adjust ISO 22400 calculations to match finance conventions (for example, excluding certain downtime categories), the KPI is no longer an ISO 22400 KPI. You must label it differently and document the change.
- Loss of traceability: Blending tags, MES events, and ERP cost data into a single number without clear lineage makes it difficult to support audits, internal reviews, or root cause analysis.
- Conflicting data sources: In brownfield plants, MES, historian, and ERP rarely align perfectly. A single dashboard can surface discrepancies (for example, production counts not matching inventory movements) and trigger disputes if governance is weak.
- Regulatory perception: If the same KPI value is used informally in financial discussions and formally in a validated system, inconsistencies can create questions during audits, even if no regulation is directly violated.
Design principles for mixed KPI/financial dashboards
To keep the dashboard usable and defensible, consider these practices:
- Keep ISO KPIs canonical: Implement ISO 22400 KPIs exactly as defined (scope, time base, included/excluded losses). Label them clearly as ISO 22400 measures.
- Separate “ISO” from “business” variants: If you need adjusted metrics for finance (for example, excluding R&D runs, training, or certain maintenance), publish them as distinct KPIs (for example, “Business OEE”) with documented formulas and rationales.
- Use visual grouping: Place ISO 22400 KPIs in a clearly marked section (“Operational KPIs”) and financials in another (“Financial impact”), then link them via narratives or derived but labeled context metrics.
- Make data lineage visible: Provide drill-down to source systems (MES, historian, ERP) and show at least a high-level data path: what events, what time windows, what mappings.
- Control time alignment: Ensure that the time windows used for ISO KPIs match (or are clearly reconciled with) financial periods. Misaligned shifts, calendars, and posting delays are common failure modes.
- Document and version calculations: Treat calculation logic like configuration under change control: version it, review it, and log changes. This is especially important once decisions or regulatory submissions depend on the numbers.
Dependencies and implementation challenges
Whether mixed dashboards work well depends heavily on your data and systems maturity:
- Integration quality: You need stable interfaces between MES/SCADA/historian and ERP/finance. Ad hoc exports or manual spreadsheets undermine repeatability and increase error risk.
- Master data alignment: Equipment, product, and time hierarchies must be consistent across systems, or you will get conflicting counts, costs, and allocations.
- Validation and change control: In regulated environments, if the dashboard is referenced in procedures or used in validated processes, any change to KPI or financial calculations can trigger revalidation and documentation updates.
- Downtime constraints: Reworking MES or ERP logic to support new KPIs or cost allocations can require production system changes. In long-lifecycle assets, the approval, scheduling, and qualification effort is often more significant than the dashboard build itself.
These factors mean that a full replacement of existing plant reports with a single new “unified” dashboard often fails. It is usually safer to introduce the mixed dashboard as a complementary view on top of existing, validated reports, at least initially.
Recommended approach
In most regulated, mixed-vendor environments, a staged approach is more realistic than a big-bang rollout:
- Start with read-only integration: Pull data from existing MES/SCADA and ERP without changing their internal logic. Keep the dashboard clearly “for analysis and decision support” rather than as a formal system of record.
- Publish a KPI catalog: List ISO KPIs and financial metrics, with formulas, sources, and intended use. Mark which are canonical ISO 22400 and which are derived or adjusted.
- Pilot on a limited scope: Begin with one line or product family. Use the pilot to expose data quality and alignment issues before scaling.
- Align stakeholders: Have operations, quality, and finance agree on how the mixed metrics will be interpreted in daily management and escalation processes.
- Introduce governance: Set a lightweight process for requesting new metrics, changing formulas, and deprecating old ones, with appropriate review and documentation.
Handled this way, a mixed ISO 22400 and financial dashboard can provide shared visibility across functions while staying compatible with traceability, validation, and long equipment lifecycles.
