What types of users should see which ISO 22400 KPIs in an aerospace plant?

Different user groups should see different subsets of ISO 22400 KPIs, with different time horizons and levels of detail. The practical rule is simple: show each role the KPIs it can act on, not every KPI the plant can calculate.

In an aerospace plant, that usually means operators and supervisors need near-real-time execution metrics, manufacturing and quality engineers need loss analysis and trend metrics, and leadership needs rolled-up indicators with drill-down to evidence. A single plant-wide dashboard for everyone usually creates noise, gaming, or decisions made without enough context.

Recommended role-based KPI visibility

• Operators and cell leads: show only the measures that help run the current job and shift. Typical examples include availability-related loss signals, schedule adherence at the work-center level, actual versus planned cycle or processing time, queue or wait conditions, first-pass outcomes where they are attributable, and bottleneck status. Avoid loading operator screens with finance-style aggregates or enterprise rollups they cannot influence directly.

• Production supervisors and area managers: show shift and daily views of throughput, utilization, delay, nonproductive time, backlog against plan, constraint status, and reason-coded losses by line, cell, or area. These users need comparison across crews, shifts, and work centers, but still with fast access to underlying events.

• Manufacturing engineers and industrial engineers: show trendable KPIs tied to process capability, flow, performance losses, changeover impact, asset utilization patterns, routing performance, and recurring bottlenecks. They usually need richer segmentation by part family, routing, machine, program, and revision. This is where ISO 22400 can be useful, but only if event definitions are stable and comparable across areas.

• Quality leaders and quality engineers: show KPIs that connect production performance to yield, rework, scrap, inspection burden, and defect escape risk. They also need traceable links back to lot, serial, operation, nonconformance, and reinspection events. Quality should not rely on operational KPIs alone, because a good throughput number can hide rework loops or deferred quality cost.

• Maintenance and reliability teams: show downtime composition, failure frequency, mean time patterns, planned versus unplanned stoppage, asset loading, and maintenance-related performance losses. In many plants, these values depend on how machine states and work-order events are mapped, so visibility should include reason-code confidence, not just the headline number.

• Plant leadership: show rolled-up KPIs for throughput, schedule attainment, utilization, delay, quality loss, and major constraint areas, with drill-down into site, program, area, and shift. Executives need cross-functional visibility, but not at the cost of false precision. If one area is manually reported and another is machine-derived, the dashboard should make that difference visible.

• Enterprise operations, program, and IT leadership: show normalized KPI families across plants only after semantic alignment is established. Cross-site comparison is useful for trend and capacity planning, but it often fails when plants use different routing models, reason codes, calendar rules, rework handling, or data collection discipline.

How to decide who sees what

A good assignment model uses four filters:

1. Decision authority: can this user change the outcome within the relevant time window?

2. Time horizon: is the user managing minutes, shifts, weeks, or quarters?

3. Controllability: does the KPI reflect factors the user can reasonably influence?

4. Data trust: is the underlying data complete and defined consistently enough for that audience?

If a user cannot act on a KPI, or the KPI blends multiple systems with weak data lineage, it should usually be hidden from routine operational use or clearly labeled as directional.

What usually goes wrong

• Too many users see OEE-style rollups without context. In aerospace, high-mix, low-volume work, long inspections, engineering holds, outside processing, and qualification constraints can distort aggregated utilization or efficiency metrics.

• Quality and execution are separated. A production dashboard may look healthy while the actual process is accumulating rework, deferred inspections, or concession risk.

• Cross-plant standardization is assumed too early. ISO 22400 provides a framework, but not automatic semantic consistency across MES, ERP, historians, machine interfaces, and manual logs.

• KPIs are assigned by hierarchy instead of workflow. A senior title does not always mean a broader dashboard is useful. Some leaders need exception-based views, not more indicators.

• Manual and automated signals are mixed without disclosure. That creates false confidence and weakens root-cause analysis.

Brownfield reality in aerospace plants

Most aerospace plants should not try to rebuild KPI visibility by replacing all core systems at once. Full replacement often fails because of qualification burden, validation cost, downtime risk, integration complexity, and the need to preserve traceability across long-lived assets and legacy processes.

A more realistic approach is to map KPI ownership by role, define canonical event meanings, and then expose role-specific views across the systems you already have. In practice, that often means MES provides execution context, ERP provides order and schedule context, QMS provides quality event context, and machine or historian data fills in state changes where reliable. The quality of the KPI depends less on the dashboard tool than on data governance, master data discipline, and change control.

Practical rule of thumb

Yes, different users should see different ISO 22400 KPIs, and often the same KPI should appear in different forms for different roles.

• Operators: current job, current constraint, immediate loss.

• Supervisors: shift execution, adherence, delays, bottlenecks.

• Engineers: trends, causes, segmentation, repeatability.

• Quality: yield, rework, defect-linked performance loss, traceable evidence.

• Maintenance: downtime composition and failure patterns.

• Leadership: rolled-up performance with drill-down and data-confidence context.

If your plant cannot explain who owns each KPI, what action it drives, and which source systems feed it, the visibility model is probably not ready yet.