Can I mix ISO 22400 KPIs with custom aerospace metrics in one report?

Yes. You can put ISO 22400 KPIs and custom aerospace metrics in one report.

The important constraint is that they should not be treated as interchangeable just because they appear on the same dashboard. ISO 22400 gives you standardized manufacturing KPI definitions. Your aerospace-specific metrics often reflect contractual, quality, traceability, routing, inspection, or program-execution realities that the standard does not fully cover. Mixing them is usually practical. Mixing them without governance is where problems start.

What has to be true for this to work

• Each metric needs a clear definition, owner, calculation logic, unit of measure, time basis, and source system.

• The report should distinguish standardized KPIs from site-defined or program-defined metrics.

• Any rollups across plants, lines, suppliers, or programs need consistent mapping rules. If one site calculates downtime or quality loss differently, the combined report can mislead.

• Version control matters. If a custom metric changes due to process updates, ERP or MES reconfiguration, or revised quality rules, the report should preserve traceability to the metric revision in effect.

• If data comes from MES, ERP, PLM, QMS, historians, or spreadsheets, timestamp alignment and event granularity need to be checked. A common failure mode is comparing near-real-time machine metrics to delayed transactional quality data as if they were synchronized.

Why teams do this

In aerospace and other regulated environments, ISO 22400 KPIs can provide a useful baseline for performance visibility, while custom metrics cover what operations leadership actually needs to manage, such as rework burden by program, escaped defect exposure, traveler completion latency, concession volume, inspection queue age, or outside-processing delay risk.

That combination can be valuable, especially in brownfield plants where no single system contains the full operational picture.

What can go wrong

• A standard KPI can look comparable across sites while the custom metric beside it is not comparable at all.

• Custom aerospace metrics often depend on local routing practice, NCR workflows, disposition timing, or manual data entry quality.

• Users may assume the entire report is standards-based when only part of it is.

• If metric lineage is weak, validation and change control become difficult, especially when reports influence quality or production decisions.

• Vendor dashboards may allow mixed widgets but not enforce semantic consistency. The tool capability does not solve the governance problem.

Brownfield reality

In most plants, this report will sit across multiple systems rather than come cleanly from one platform. That is normal. MES may provide equipment and execution events, ERP may provide order and cost context, QMS may hold nonconformance data, and PLM may govern product structure or revision state.

Because of that, a full replacement approach is usually not the answer. In regulated, long-lifecycle environments, replacing core systems just to standardize reporting often fails due to qualification burden, validation cost, downtime risk, integration complexity, and the need to preserve traceability through change control. A governed integration layer or semantic model is usually more realistic than ripping out existing systems.

Practical reporting approach

A mixed report is usually safer if it follows three rules:

1. Label ISO 22400 KPIs as standards-based and label aerospace metrics as enterprise-defined or program-defined.

2. Publish metric definitions in a controlled glossary or KPI catalog tied to report logic.

3. Do not aggregate or benchmark unlike metrics without an approved mapping rule.

If those controls are in place, one report can be effective. If they are not, the report may still look polished but it will not be reliable enough for cross-site comparison or high-stakes operational decisions.