How do we ensure data quality for ISO 22400 KPIs in aerospace production?

You ensure data quality for ISO 22400 KPIs by treating the KPI layer as a controlled manufacturing data product, not just a dashboard calculation. The standard helps with terminology and KPI structure, but it does not fix poor source data, inconsistent event capture, or conflicting business rules across plants and systems.

In aerospace production, the practical baseline is this: every KPI must have a governed definition, a known source system, a traceable calculation path, controlled timestamps, and a documented handling rule for exceptions such as rework, scrap, concessions, split lots, partial completions, and manual overrides.

What usually matters most

• Define each KPI unambiguously. Document the formula, unit of measure, aggregation level, reporting frequency, exclusions, and intended operational use. If one area counts queued work as WIP and another does not, the KPI is already compromised.

• Control the production event model. KPI quality depends on accurate events such as start, stop, complete, hold, scrap, rework, setup, downtime, and good quantity confirmation. If these events are captured differently by machine interfaces, MES transactions, and manual logs, the KPI will drift.

• Harden time and state logic. Many KPI errors come from clock drift, duplicate messages, late postings, missing end events, and ambiguous equipment states. This is especially common when PLC, SCADA, historian, MES, and ERP each keep their own timestamps.

• Establish master data discipline. Work center hierarchies, routing versions, part revisions, shift calendars, reason codes, units, and asset identifiers have to be consistent enough for aggregation. If they are not, cross-line or cross-plant KPI comparisons are often misleading.

• Trace every KPI back to record-level evidence. If leadership cannot drill from a reported number back to the underlying machine event, transaction, lot, serial, order, or quality record, the KPI is hard to trust and harder to validate.

• Put change control around calculations and mappings. A formula change, new connector, revised routing, updated reason code set, or machine retrofit can break trend continuity. Treat KPI logic changes as controlled changes with impact assessment and version history.

Brownfield reality in aerospace

Most aerospace plants do not have a clean, single-source architecture. They have mixed-vendor machines, aging PLCs, historians, spreadsheets, ERP, MES, QMS, and sometimes custom interfaces built over many years. That means data quality is usually limited by coexistence issues more than by the KPI standard itself.

In practice, you should expect problems such as:

• ERP completion posted hours after physical completion

• MES capturing labor and routing events but not machine micro-stoppages

• machine data with poor context about part, order, or operator

• quality events recorded in QMS with no clean join to production events

• rework performed off the original routing or outside the main execution system

• manual entries added after the fact to reconcile throughput or downtime

That does not mean ISO 22400 KPIs are unusable. It means the KPI program has to be explicit about source priority, reconciliation rules, and known blind spots. A partially automated but well-governed KPI is usually more trustworthy than a fully automated KPI assembled from poorly aligned systems.

Full replacement of legacy systems is often not the practical answer in aerospace. It can fail because of qualification burden, validation cost, downtime risk, interface complexity, and long equipment lifecycles. In many plants, the better path is staged improvement: stabilize definitions, improve mappings, instrument critical gaps, and validate KPI calculations incrementally while existing systems continue to operate.

Controls that improve KPI trustworthiness

• Canonical mapping layer. Map source events and codes from MES, ERP, QMS, and equipment systems into a controlled semantic model before KPI calculation.

• Data quality rules. Check completeness, uniqueness, sequence integrity, timestamp plausibility, referential integrity, and allowed state transitions.

• Exception queues. Route missing order links, duplicate completions, unmatched scrap records, and orphan downtime events for review instead of silently accepting them.

• Versioned KPI specifications. Keep approved definitions with effective dates so historical trends can be interpreted correctly after process or system changes.

• Reconciliation routines. Compare reported production, scrap, and downtime across systems on a defined cadence and investigate persistent variances.

• Role ownership. Assign ownership across operations, quality, engineering, and IT. KPI quality usually fails when no one owns the meaning of the metric and everyone assumes someone else owns the data.

• Validation and test cases. Use known production scenarios, including rework and nonconformance cases, to confirm calculations behave as intended before broad rollout.

Common failure modes

The most common failure is assuming a KPI is accurate because the formula is mathematically correct. In reality, KPI quality often breaks earlier in the chain.

• Different plants use the same label for different operational events

• Downtime categories are operator-entered with inconsistent discipline

• Good count and scrap count are booked at different steps

• Rework loops inflate throughput or hide loss

• Part revision changes are not aligned with routing or resource definitions

• Manual backposting smooths over missing real-time events

• Shift calendars and asset calendars are not synchronized

• Serial, lot, or order identifiers are missing, reused, or not propagated across systems

In regulated environments, another failure mode is weak evidence retention. If KPI calculations cannot be reproduced from retained records after a process change or system update, trust erodes quickly even if the dashboard still looks stable.

What good looks like

A credible ISO 22400 KPI program in aerospace usually has these characteristics:

• approved KPI definitions and data lineage

• documented source-system precedence and reconciliation rules

• clear treatment of rework, scrap, concessions, and partial completions

• audit-ready change history for interfaces, mappings, and formulas

• routine data quality monitoring with thresholds and review workflow

• drill-down from KPI to transaction and traceability records

• limited use of manual adjustments, with reason capture and approval

If those controls are weak, the answer is not to stop using KPIs. It is to qualify their intended use. A metric may still be useful for local trend detection while being unsuitable for cross-site comparison, supplier escalation, or executive capacity decisions.

So the short answer is yes, you can achieve high-quality ISO 22400 KPIs in aerospace production, but only if you govern definitions, source mappings, event timing, and change control as rigorously as the reporting layer itself. The standard helps structure the KPI program. It does not remove the need for data governance, validation, and brownfield integration discipline.