ISO 22400 pairs well with several standards, but not as a single prescribed stack. In practice, it works best as the KPI and performance semantics layer, combined with other standards that handle equipment connectivity, application integration, product and process definitions, and quality data exchange.
For aerospace manufacturing systems, the most common complementary standards are:
ISA-95 / IEC 62264 for structuring information flows between enterprise systems and manufacturing operations systems. This is usually the closest fit when you need KPI definitions from ISO 22400 to align with MES, ERP, quality, and scheduling data.
OPC UA for secure, structured connectivity to equipment, cells, and edge systems. This is often the practical path for getting machine states, counts, events, and condition data that feed ISO 22400 metrics.
B2MML when you want an XML implementation approach for ISA-95 models between MES and business systems. It can help, but adoption quality varies, and many plants still need custom mapping.
MTConnect in environments with CNC and machine-tool-centric data collection. It can be useful for normalizing machine event and status data, though it usually does not cover all aerospace shop-floor processes by itself.
QIF for metrology and inspection data exchange where dimensional quality data needs to connect to production and performance reporting. This matters if KPI analysis is expected to correlate throughput or utilization with inspection outcomes.
STEP and related product data exchange standards where product definition, configuration, or manufacturing characteristics need to be tied back to execution and performance context.
MQTT as a transport pattern in modern architectures, especially for edge-to-platform event distribution. It is not a semantic standard for manufacturing KPIs, but it can coexist well with ISO 22400-oriented data pipelines.
The main point is that ISO 22400 does not replace ISA-95, OPC UA, QIF, or product data exchange standards. It complements them. ISO 22400 helps standardize how you define and calculate performance indicators. The other standards help move and contextualize the data required to calculate those indicators.
In aerospace, a practical combination is often:
ISA-95 / IEC 62264 for system and data model boundaries
OPC UA and sometimes MTConnect for equipment and machine connectivity
QIF for inspection and metrology interoperability
STEP or PLM-native controlled exchanges for product and configuration context
ISO 22400 for KPI naming, structure, and calculation consistency
That combination is usually more realistic than trying to force one standard to cover machine data, business integration, quality evidence, and KPI semantics at the same time.
No standard combination automatically produces comparable KPIs across plants. That depends on local event definitions, master data quality, routing discipline, downtime coding, shift calendars, genealogy completeness, and how rework, hold, inspection, and concession activities are represented. In regulated aerospace environments, those differences are often significant.
You also need to decide which system is authoritative for each data element. For example, machine state may come from OT connectivity, labor and operation completion may come from MES, order context may come from ERP, and quality disposition may come from QMS. If those ownership rules are unclear, ISO 22400 metrics will look standardized on paper but remain inconsistent in operation.
Validation and change control matter as well. If KPI definitions feed management decisions, customer reporting, or regulated records, interface changes and calculation logic changes may need formal review, testing, and traceability. That does not make standards unusable, but it does slow down changes compared with greenfield analytics projects.
Most aerospace plants do not implement these standards cleanly from end to end. They usually have mixed vendors, older equipment, custom ERP or MES integrations, historian conventions, spreadsheets, and plant-specific quality workflows. In that environment, ISO 22400 is often most useful as a target semantic model rather than a literal drop-in standard.
Full replacement strategies often fail here because the qualification burden is high, downtime windows are limited, and existing integrations carry more operational knowledge than the documentation suggests. A phased coexistence model is usually safer: normalize KPI definitions first, map key source systems second, and only then decide whether deeper standardization is worth the cost and validation effort.
The strongest pairings are usually ISA-95 / IEC 62264 for application and information structure, OPC UA for equipment connectivity, and QIF where inspection data matters. MTConnect, B2MML, and controlled product data exchange standards can add value depending on the process landscape. The best choice depends less on the standards catalog and more on your installed base, integration debt, data discipline, and how much cross-system semantic governance your organization can sustain.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
