What types of users should see which ISO 22400 KPIs?

ISO 22400 defines a common language for manufacturing KPIs, but it does not dictate who should see what. In regulated, mixed-system environments, you allocate KPIs by role, time horizon, and decision scope, and you limit views that can be misinterpreted or gamed.

1. Executive leadership (plant leadership, VP Ops, COO)

Goal: Direction, risk, and capital allocation, not minute-by-minute control.

Typical ISO 22400 KPI focus:

• High-level OEE / availability / performance per plant or line, trend-based, not real time.
• Order fulfillment and due-date adherence (delivery performance) by value stream or customer group.
• Scrap and rework rates as a contribution to cost of poor quality (aligned with finance, not shop-floor detail).
• Capacity utilization and bottleneck load for expansion / investment decisions.

What they should usually not see directly: Raw machine-level stoppage codes, operator-level performance, and unvalidated real-time dashboards. These tend to drive micro-management and can conflict with union or HR constraints.

2. Operations managers and area supervisors

Goal: Daily/shift control, schedule adherence, and coordination across lines and support functions.

Typical ISO 22400 KPI focus:

• OEE components by line or cell (availability, performance, quality) with drill-down.
• Planned vs actual production by work center and shift.
• Planned vs unplanned downtime, with reason codes and impact in minutes.
• Changeover times and setup efficiency for high-mix lines.
• Rework and first-pass yield per area (not yet at operator granularity).

Key constraints: These users need near real-time data, but only if integrations and timestamp alignment between MES, machines, and ERP are trustworthy. If data quality is weak, prioritize stable daily and weekly aggregates to avoid chasing noise.

3. Process engineering and industrial engineering

Goal: Identify and validate improvement opportunities, set realistic standards, and support new product introduction.

Typical ISO 22400 KPI focus:

• Cycle time and takt alignment at operation level.
• Micro-stoppage and minor loss KPIs (short stops, speed losses).
• Changeover / setup KPI detail including variance vs standard.
• Process capability / quality-related KPIs linked to yield and scrap.
• Resource utilization and routing adherence by product family.

Data caveats: Engineers often need more granular data than ISO 22400 names directly. Use ISO 22400 KPIs as the roll-up layer, but maintain traceability to machine tags, MES event logs, and routing data for root-cause work. Changes to KPI definitions must follow change control and be documented.

4. Quality and reliability engineering

Goal: Detect quality drift quickly, understand process-related drivers, and support audits and investigations.

Typical ISO 22400 KPI focus:

• Quality rate / defect rate aligned with OEE quality component.
• First-pass yield by product or key characteristic families.
• Rework and scrap ratios by line and shift.
• Inspection throughput and backlog KPIs where inspection is a constraint.
• Supplier-related defect KPIs connected to incoming inspection and NCR data (even if not strictly part of ISO 22400).

Integration considerations: Quality KPIs often require merging MES, QMS, and ERP data and preserving full genealogy. If traceability is incomplete, be explicit about scope (e.g., only certain part families, only certain lines) and avoid using partial KPIs as formal audit evidence without clear limits.

5. Production planners and schedulers

Goal: Build feasible schedules and respond to disruptions without breaking due-date commitments or regulatory routing constraints.

Typical ISO 22400 KPI focus:

• Effective capacity and load by line or work center (derived from OEE and planned availability).
• Adherence to plan (schedule attainment, sequence adherence).
• Queue time and WIP indicators at key work centers.
• Downtime impact on available capacity (rolling view).

Brownfield constraint: In many plants, these KPIs depend on fragile integrations between ERP and MES. If routing data or shift calendars are inconsistent, planners should see clear data quality flags rather than a false sense of precision.

6. Maintenance and reliability teams

Goal: Prioritize interventions that restore or improve availability without jeopardizing validation states or regulatory approvals.

Typical ISO 22400 KPI focus:

• Asset availability and downtime metrics by equipment.
• Mean time between failures (MTBF) / mean time to repair (MTTR).
• Preventive vs corrective maintenance ratios.
• Maintenance-related production loss translated into time or missed orders.

Regulated-environment nuance: Some equipment cannot be taken down freely due to validation or qualification constraints. Visibility should distinguish between theoretical and realistic availability so maintenance does not get penalized for constraints they cannot change.

7. Line leaders, team leads, and operators

Goal: Run the shift safely and effectively, surface issues early, and improve within their span of control.

Typical ISO 22400 KPI focus:

• Simple, shift-level OEE view for their line or cell only.
• Current shift performance vs target (pieces, takt adherence, first-pass yield) with minimal lag.
• Top downtime reasons this shift or day.
• Right-now constraints: WIP status, missing materials, machine state.

What to avoid: Cross-line comparisons, operator-level league tables, and financialized KPIs at the station level often create blame behavior, workarounds, and under-reporting of issues. In regulated environments, that can also undermine data integrity and auditability.

8. IT, data, and MES administrators

Goal: Ensure KPI calculations are reliable, explainable, and stable across system changes.

Typical ISO 22400 KPI focus:

• Meta-KPIs on data quality: event completeness, timestamp alignment, missing reason codes.
• System latency KPIs: time from event to dashboard availability.
• Consistency checks between ISO 22400 KPIs and legacy plant KPIs.

Why this matters: In brownfield environments with mixed vendors, the same-named KPI can be calculated 3 different ways. IT and data owners need visibility to maintain a validated, version-controlled KPI definition set and to document changes under formal change control.

9. Avoiding common missteps in KPI visibility

Regardless of role, several pitfalls recur when exposing ISO 22400 KPIs broadly:

• Unvalidated real-time KPIs: Streaming data that is not reconciled with MES/ERP often conflicts with official reports and erodes trust.
• Full replacement of legacy metrics: Trying to replace long-used local metrics overnight with ISO 22400 definitions can fail because of qualification burden, audit expectations, and user resistance. A coexistence and mapping period is usually necessary.
• Operator-level financial KPIs: Tying individuals directly to cost KPIs can incentivize hiding defects or bypassing paperwork in regulated settings.
• Lack of context: Showing OEE or downtime without explaining constraints (e.g., mandated inspections, change control, validation windows) leads to unrealistic targets and friction between functions.

10. Practical allocation guidelines

Given local differences in systems and maturity, there is no universal matrix, but the following rules of thumb are broadly applicable:

• Match time horizon to role: Executives see weekly/monthly views; supervisors see shift/daily; operators see current and last shift.
• Match scope to span of control: Operators see their cell; supervisors see their area; plant leadership sees the plant.
• Keep one “official” definition set: Even if multiple systems calculate variants, maintain a single, documented ISO 22400-aligned definition per KPI used for reporting and audits.
• Introduce ISO 22400 via mapping, not replacement: Start by mapping existing KPIs to ISO 22400, then progressively harmonize as integrations and validation catch up.

Ultimately, who sees which ISO 22400 KPI is a governance decision that depends on data reliability, system coexistence, and organizational trust. Treat KPI visibility as part of your overall MES/analytics governance, with clear ownership and change control.