How should aerospace suppliers incorporate ISO 22400 into contracts?

ISO 22400 can be a useful reference in aerospace supply contracts, but it should be incorporated as a structured, limited “metrics language,” not as a blanket compliance obligation. In regulated aerospace environments, you need to be explicit about which indicators apply, how they are calculated, and how they coexist with existing systems and customer requirements.

1. Use ISO 22400 as a reference, not a blanket requirement

Most aerospace primes and Tier 1s do not yet manage suppliers strictly against ISO 22400. Instead of writing “Supplier shall comply with ISO 22400,” use wording such as:

• “The parties will use ISO 22400-2 as the reference for definitions of the following KPIs: [list].”
• “Where not otherwise defined in customer specifications, KPI terminology and formulas shall align with ISO 22400-2.”

This avoids implying certification or guaranteeing audit outcomes, while still standardizing language.

2. Select a small, relevant KPI set

Do not attempt to contract around all ISO 22400 indicators. Pick a small, high-leverage subset that supports the commercial and quality intent of the agreement, for example:

• Availability-related metrics (planned vs unplanned downtime) to support on-time delivery.
• Performance-related metrics that tie to throughput or cycle-time commitments in the SOW.
• Quality-related metrics that support existing defect rate, escape, or COPQ expectations.

In contracts, explicitly list the agreed indicators and reference the relevant ISO 22400 part and clause where possible.

3. Contract the definition, not just the label

Using terms like OEE and availability is risky if different plants or vendors define them differently. To reduce ambiguity:

• State for each KPI: name, reference (ISO 22400 part/section), and any agreed deviations from the standard definition.
• Clarify inclusions/exclusions (e.g., does planned maintenance count as downtime, are setup and changeover considered losses?).
• Define the time basis (shift, day, week) and aggregation method (arithmetic mean, weighted, etc.).

This matters in aerospace, where disputes about root cause (supplier vs customer scheduling, material availability, design changes) are common.

4. Specify data sources and system-of-record

In brownfield environments, data comes from multiple systems: MES, ERP, machine data collectors, manual logs, and spreadsheets. Contracts should acknowledge this and specify:

• Primary source systems for each KPI (e.g., MES for downtime, QMS for defects, ERP for delivery adherence).
• Which side’s data is authoritative in case of discrepancies (e.g., supplier MES vs customer ASN / receiving system).
• How manual data capture is handled and how often it is digitized.

This prevents unrealistic expectations that all KPIs are automatically available or fully integrated, especially where legacy systems and partial digitization exist.

5. Align with existing quality and delivery clauses

Most aerospace contracts already include clauses for OTD, defect rates, escapes, FAIs, and NCR responsiveness. ISO 22400 should support those terms, not conflict with them. In practice:

• Map ISO 22400 KPIs to existing contractual commitments (e.g., a specific performance indicator supporting an OTD target).
• Avoid creating a second, conflicting definition of defect rate, scrap, or rework if your QMS already uses established metrics.
• Ensure KPIs used in supplier scorecards and business reviews match those in the contract to avoid disputes.

If there is a conflict between a customer-specific definition and ISO 22400, the contract should make the precedence explicit.

6. Be explicit about targets vs monitoring-only KPIs

Not every ISO 22400 indicator should carry contractual penalties or incentives. Distinguish clearly between:

• Commitment metrics: KPIs with contractual targets (e.g., on-time delivery, nonconformance rate) that may tie to pricing, allocation, or escalation.
• Diagnostic metrics: KPIs tracked for visibility and continuous improvement only (e.g., specific downtime categories, minor yield losses).

Specify which ISO 22400 indicators are used purely for joint performance reviews and which are linked to remedies or commercial consequences.

7. Include validation, traceability, and change control

In regulated aerospace manufacturing, changing how KPIs are measured can affect perceived performance and audit trails. Contract language should:

• Require documented calculation logic for each KPI (e.g., in a measurement & reporting specification under change control).
• State that changes to formulas, data sources, time-bucketing, or filtering require formal change control and mutual approval.
• Clarify expectations for data retention, audit trails, and the ability to reconstruct KPI history if calculations or systems change.

If KPIs are generated from validated MES or data collection systems, note that any material configuration change likely requires re-validation before metrics are treated as comparable.

8. Acknowledge integration and brownfield realities

Most aerospace suppliers operate mixed stacks of MES, ERP, PLM, QMS, machine controllers, and manual processes. When incorporating ISO 22400:

• Avoid implying that full, real-time KPI automation across all assets is in place if it is not.
• State whether calculations are based on real-time data, delayed batch exports, or periodic manual consolidation.
• Recognize that some cells or product families (especially legacy programs) may not have the same data granularity as newer lines.

Full system replacement to meet ISO 22400 perfectly is rarely justifiable in aerospace due to validation cost, downtime risk, and integration complexity. Contract language should focus on practical, incremental enhancements rather than assuming a greenfield environment.

9. Define review cadence and governance

To keep ISO 22400 usage practical and aligned with reality over the life of a long-term agreement:

• Define how often KPI definitions, targets, and data quality will be jointly reviewed (e.g., quarterly business reviews).
• Set expectations for data reconciliation and issue resolution if KPI values are contested.
• Clarify which roles (supplier operations, quality, IT) own metric generation, verification, and communication.

This governance is especially important when programs span many years and plants undergo system upgrades, line moves, or process changes.

10. Avoid implying certification or regulatory compliance

ISO 22400 is about manufacturing KPIs, not regulatory or quality system certification. Contracts should not suggest that using ISO 22400 produces compliance with AS9100, customer-specific quality clauses, or regulatory requirements. Instead, position it as:

• A common reference for how performance is measured and discussed.
• A tool to support continuous improvement and transparency.
• A way to reduce confusion in multi-plant, multi-supplier networks.

Keep quality system and regulatory obligations (AS9100, customer standards, export controls) in their own clauses and use ISO 22400 only for KPI structure.

Summary

Aerospace suppliers should incorporate ISO 22400 into contracts as a scoped, well-defined reference for specific KPIs, not as a blanket compliance mandate. The contract should specify the exact indicators, definitions, data sources, governance, and whether each KPI is a monitored metric or a contractual commitment. It must also recognize brownfield systems, validation constraints, and the long lifecycle of aerospace programs so that performance measurement is realistic, traceable, and sustainable over time.