In aerospace, delivery numbers dominate headlines and executive reviews. Monthly and yearly totals are easy to understand and easy to compare. But if you are responsible for an aircraft, missile, or space hardware production line, you already know the problem: deliveries say almost nothing about how hard the system had to work to ship that hardware, or whether it can do it again next month.

The core issue is the same one explored in the misleading aerospace scoreboard: we are using surface-level output metrics to judge systems that are fundamentally constrained by complexity, regulation, and coordination. If you manage an AS9100 production environment, you need a different scoreboard—one that measures throughput, flow, and system health instead of just deliveries.

For teams putting this topic into daily operation, execution systems for aerospace manufacturing, shop floor execution control, a connected execution platform help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on Connect 981’s aerospace execution solutions, real aerospace execution examples, Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

Why Delivery Counts Dominate the Aerospace Narrative

The visual appeal of delivery charts

Delivery charts are compelling because they compress a complicated story into a single line. Executives can see trends at a glance. Investors can compare OEMs. Programs can be ranked and benchmarked. A rising line signals momentum; a falling line triggers concern.

Inside factories and across the supply chain, these same charts shape behavior. Teams feel pressure to “hit the number” by quarter-end. Ship dates become fixed reference points, even when upstream realities are changing daily. The simplicity of deliveries makes them attractive, but that simplicity comes with cost: almost all context is stripped away.

Investor communication reinforces delivery obsession

Public aerospace companies rely on delivery counts as one of the few operational metrics that can be disclosed consistently across programs and time. Analysts model revenue and cash flow around shipments. Backlog and deliveries become shorthand for competitiveness.

This external framing seeps back into internal management. Senior leaders report deliveries upward, so functional teams naturally optimize for them. But an AS9100-regulated factory is not a commodity volume line. The effort required to ship one serial number can vary by orders of magnitude, depending on design maturity, supplier stability, and quality status. When all of that nuance is collapsed into a single count, the delivery number becomes a distorted lens rather than a clear one.

Why deliveries are only a partial view of performance

A delivery record tells you that a configuration passed a specific gate at a specific time. It does not tell you:

• How many hours of rework, repair, and concessions review were required.
• How many units of work-in-process (WIP) were tied up or cannibalized to complete that shipset.
• How many engineering changes or deviations were pushed through under schedule pressure.
• Whether the underlying flow is stable and repeatable, or a one-off surge effort.

Two factories can both ship 10 aircraft in a month. One may do so with high first-pass yield, predictable cycle times, and low overtime. The other may rely on firefighting, expediting, and hidden backlog. The delivery count is identical; the production systems are not.

Defining Throughput in Regulated Aerospace Manufacturing

Throughput versus takt in low-volume, high-complexity work

In high-mix aerospace environments, true throughput is not simply “units per hour.” It is the rate at which conforming, configuration-correct hardware moves through the value stream over time. That rate is constrained by:

• Engineering release and configuration maturity.
• Special processes and certified operations.
• Non-destructive testing and acceptance testing capacity.
• Supplier capability and lead time.

Unlike high-volume industries, takt time is rarely a single fixed number. Different work centers operate on different cadences, with long dwell times around inspections and tests. Measuring throughput requires looking at the whole flow across cells, not just a nominal cycle time at a single station.

Accounting for inspection, testing, and certification steps

Regulated aerospace production inserts multiple non-optional steps into the flow: in-process inspection, functional test, environmental test, flight test, conformity checks, and regulatory or customer acceptance. Each of these can become a limiting constraint, particularly when demand fluctuates or when a quality escape triggers additional sampling.

Throughput therefore must be measured across these verification gates, not just across assembly operations. A line that can mechanically assemble hardware quickly but waits days or weeks for test capacity does not have high throughput. It has local speed and system-level delay.

How rework and concessions distort perceived throughput

Rework is where the disconnect between deliveries and real throughput becomes most obvious. A unit that passes final inspection after three major rework cycles shows up as a single delivery. In the system, though, it consumed the equivalent capacity of multiple units:

• Additional touch labor and quality engineering support.
• Extra MRB (Material Review Board) and concession processing.
• Retesting, re-inspection, and documentation updates.

Concession-heavy programs can appear to be delivering acceptably while quietly burning massive capacity on hidden work. Without metrics that distinguish first-pass throughput from total output, leadership cannot see the erosion of real capability until it is severe.

Hidden Work Behind a Single Delivery

Non-conformances, deviations, and repair loops

Every major aerospace program carries a tail of non-conformances and deviations. A single shipset might involve dozens of quality records across subassemblies, hardware substitutions, and process deviations. Each record requires investigation, root cause analysis, and documented disposition.

On the shop floor, this translates into repair loops: units leave the main line, move to rework areas, wait on engineering or supplier input, and eventually return for retest and reintegration. From a delivery perspective, all of this collapses into a single date. From a throughput perspective, it represents a major diversion of flow and capacity.

Supplier-driven delays and expediting behaviors

Suppliers introduce another layer of hidden work. When critical components arrive late, out of tolerance, or incomplete, internal teams respond by:

• Resequencing work to keep technicians utilized.
• Partial building and kitting around missing items.
• Expediting shipments and engineering dispositions.
• Cannibalizing parts from other WIP to close a near-term delivery.

These tactics protect the delivery schedule in the short term, but they damage throughput. Flow becomes unpredictable, WIP grows in odd places, and future deliveries inherit the disruption. Without a clear view of these patterns, leaders may misinterpret on-time delivery as evidence of a healthy system when it is actually the result of unsustainable expediting.

Paperwork and traceability reconstruction effort

In AS9100 environments, paperwork and digital traceability are as important as physical build status. When travelers, inspection records, or certificates of conformance are incomplete, teams often scramble near ship dates to reconstruct the digital thread.

This reconstruction work rarely appears explicitly in any metric. Engineers and planners dig through email, shared drives, and spreadsheets to close gaps. The unit ships; the delivery target is met. But the underlying system is signaling a problem: execution and traceability are not aligned. True throughput should account for this late-stage effort, because it represents real cost and risk.

Metrics That Reveal True Capability

First-pass yield and right-first-time rate

First-pass yield (FPY) measures the percentage of units that complete a process or flow without requiring rework. In aerospace, you can define FPY at multiple levels: operation-level, cell-level, or end-to-end configuration-level. High FPY indicates that work instructions, training, tooling, and design stability are aligned.

Right-first-time rates are powerful because they convert quality into a flow metric. A line that delivers 95% of units right-first-time has far more real capacity than one that delivers the same total output but with 60% FPY. Dashboards that highlight FPY by constraint area let teams attack the factors that erode throughput long before delivery numbers slip.

Queue times versus touch times across operations

Touch time is how long a technician, inspector, or operator is actively working on a unit. Queue time is how long that unit is waiting—for materials, paperwork, quality sign-off, engineering decisions, or test slots. In many aerospace factories, queue time dwarfs touch time.

Measuring both is essential. You may discover that a critical assembly spends 80% of its lead time waiting between operations or sitting in front of a single constrained special process. Improving documentation flow or decision turnaround at those points can increase throughput without adding headcount or equipment.

WIP aging, bottleneck analysis, and constraint tracking

Healthy systems limit WIP and keep it moving. When WIP ages—units sit in the same status for days or weeks—it signals a flow break. Tracking WIP aging by operation, shop, and supplier reveals where the system is actually constrained.

Bottleneck analysis in aerospace is more dynamic than in simple lines. Constraints move between internal cells, external suppliers, test facilities, and engineering. A robust metric set tracks where the constraint is this week, how much capacity it has, and how variability is affecting it. That is the level of visibility required to convert schedule promises into actual throughput.

Lead time stability under schedule variation

Throughput is not just about average speed. It is about predictability. In a constrained, regulated environment, a stable 14-week lead time may be healthier than a nominal 10-week lead time that routinely fluctuates between 8 and 20 weeks.

Measuring lead time stability—for example, via standard deviation or on-time-complete metrics across internal milestones—gives you a truer sense of capability than delivery counts alone. Customers and program managers can plan around a stable system; unstable throughput forces constant replanning and erodes trust.

Why Traditional Systems Struggle to Measure Flow

Limitations of ERP-based completion reporting

ERP systems are optimized for planning and financial posting, not for real-time execution. They know what should have happened, which operations are planned, and when a work order is financially complete. But they often lack granular timestamps, partial completions, or rich status reasons for delay.

The result is a binary view of the world: not started, in process, complete. That may be enough for material requirements planning, but it is insufficient for understanding true throughput. The system does not natively distinguish a unit smoothly moving through flow from one oscillating between rework, MRB, and waiting on engineering.

Gaps in MES coverage across mixed-model and manual work

Many aerospace manufacturers have implemented MES systems for specific lines or processes, often around automated equipment or final assembly. But coverage is rarely universal. Manual, mixed-model, and prototype work frequently lives outside MES in travelers, whiteboards, and local databases.

These gaps fragment the execution picture. You may have good visibility in a test cell, but no structured data on how long units waited for that test or how many were diverted to repair before arriving. Without end-to-end coverage, throughput and flow metrics become partial and misleading.

The role of spreadsheets and manual status boards

To compensate, teams build their own visibility layers: spreadsheets for WIP tracking, PowerPoint-based status boards, and informal messaging channels. These tools are flexible and fast to change, but they are also fragile and non-authoritative.

From a metrics standpoint, manual layers break the digital thread. You cannot reliably compute FPY, WIP aging, or constraint utilization from a set of unlinked spreadsheets and hallway conversations. At best, you get snapshots; at worst, you get conflicting versions of reality across engineering, production, and quality.

Using a Connected Execution Layer to See Throughput Clearly

Real-time operation status and WIP tracking

A connected execution layer fills the gap between planning systems and the shop floor. It does not replace ERP or existing MES where they work well. Instead, it connects work orders, operations, and quality events into a coherent, real-time view of WIP.

In practice, this means every unit or serial number carries a live status: where it is, what operation it is on, who is working it, and what it is waiting on. With that foundation, throughput metrics are no longer estimates. You can see exactly how many conforming units are crossing key gates per day, week, or month and how that rate changes as conditions shift.

Linking non-conformances and rework to flow metrics

When quality events are integrated into the same execution layer, non-conformances, concessions, and repairs become part of the flow picture instead of being tracked separately. Each quality record is attached to specific work, operations, and components.

This enables new metrics: rework hours per shipped unit, FPY by operation and configuration, and the impact of specific defect modes on overall throughput. Leaders can identify which recurring issues are eroding capacity and prioritize corrective actions based on system-wide impact, not just defect count.

Visualizing constraint movement across suppliers and cells

A connected execution layer can also extend beyond a single site. When suppliers participate—even with limited, well-scoped data sharing—you can visualize where work is actually piling up: internal assembly, external machining, special processes, or test labs.

Rather than treating supplier delivery performance as a black box, you see WIP stages, queues, and cycle times in aggregate. This supports more productive conversations: instead of demanding “faster deliveries,” OEMs and tier-ones can collaborate with suppliers on specific constraint relief that improves throughput for both sides.

Aligning engineering, quality, and production around shared data

In many aerospace organizations, each function has its own view of performance. Engineering tracks change implementation. Quality tracks findings and audits. Production tracks schedule adherence. Without a shared execution layer, these views diverge and debates about “what is really happening” consume time.

When all three functions work from the same operational data—live WIP, integrated quality events, and configuration-aware status—the conversation changes. Instead of arguing about numbers, teams can focus on constraints, trade-offs, and systemic improvements that raise real throughput.

Redesigning the Aerospace Scoreboard Around System Health

Balancing deliveries with stability and predictability metrics

Deliveries will always matter. Customers, warfighters, and mission operators depend on them. The goal is not to dismiss delivery metrics, but to put them in the right context. A modern aerospace scoreboard balances:

• Delivery performance (on-time, by configuration and customer).
• Throughput at key gates (first-pass and total).
• FPY and rework intensity at constraints.
• Lead time stability and WIP aging.

When these metrics move together, you know the system is getting healthier. When deliveries improve while FPY and stability worsen, you know you are borrowing from the future.

Setting leading indicators for execution maturity

Throughput metrics can also serve as leading indicators of execution maturity. Examples include:

• Percentage of WIP with real-time status versus manual tracking.
• Share of quality events initiated at the point of work versus discovered downstream.
• Time from defect detection to containment and disposition.
• Proportion of work covered by a connected execution layer.

These indicators do not show up on investor slides, but they predict whether the system can handle increased rate, new configurations, or regulatory scrutiny without breaking.

How OEMs can communicate capability without oversimplifying

Externally, aerospace organizations face a tension: markets want simple numbers; operations need nuanced ones. The path forward is not to publish every internal metric, but to frame deliveries and backlog as outcomes of an execution system—and to explain how that system is being strengthened.

That might mean discussing investments in connected execution, traceability, and supplier integration as part of program updates, or highlighting improvements in stability and right-first-time performance alongside shipment counts. Over time, the industry can move away from a one-dimensional scoreboard and toward a more accurate understanding of what real capability looks like in regulated aerospace manufacturing.

For manufacturers across the supply chain, the underlying message is consistent: if you rely on deliveries alone to judge performance, you will miss the early signals. Throughput, flow, and system health live in the execution layer—and that is where competitive advantage is now being built.

Why ERP Isn’t Enough for Aerospace Manufacturing Execution

Most aerospace manufacturers rely on an ERP system as the backbone of their business. It holds contracts, materials requirements, routings, costs, and schedules. On paper, it looks like the system that should tell you everything about the factory.

In reality, it doesn’t. ERP is fundamentally a planning and transactional engine, not an execution environment. It models what should happen. It does not reliably show what is happening now on a specific line, cell, or work center.

For teams putting this topic into daily operation, Connect 981’s aerospace execution solutions help connect the concept to traceability, work-order reality, and audit-ready evidence.

For teams putting this topic into daily operation, execution systems for aerospace manufacturing, shop floor execution control help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on ERP, MES, and PLM integration paths, a connected execution platform, Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

The result is the familiar pattern across aerospace: program managers, production leaders, and quality teams spend their days reconciling ERP data with spreadsheets, whiteboards, emails, and walk-arounds. The system of record and the system of reality are different things.

This is the same visibility gap discussed in the broader argument that high-level aerospace scoreboards can be deeply misleading. Deliveries, revenue, and backlog hide the operational truth. So does an ERP screen that appears complete but lacks real-time execution detail.

This article explains where ERP works well in aerospace, where it stops at the edge of the shop floor, and what a dedicated execution layer must provide to close the gap.

What ERP Does Well in Aerospace Manufacturing

ERP is not the problem. It is simply built for a specific role: coordinating long-horizon planning, finance, and high-level production structures. In a regulated, long-cycle environment like aerospace and defense, those strengths matter.

Long-horizon planning, MRP, and capacity modeling

ERP systems excel at describing multi-year programs, long lead-time materials, and aggregate capacity. They provide:

• Material Requirements Planning (MRP) across complex bills of material (BOMs) and multi-tier supply chains.
• Rough-cut capacity planning that matches demand to high-level resource availability over weeks, months, and years.
• Forecasting and scenario planning for new programs, rate increases, or design changes.

For aircraft structures, engines, avionics, and space hardware, this strategic view is essential. Long lead-time components, export-controlled materials, and single-source suppliers all have to be modeled and committed well before work starts on the floor.

Financial integration, costing, and contract structures

Aerospace programs live and die on their financial architecture. ERP is the system that ties operational plans to contracts and cash:

• Cost collection and allocation across work breakdown structures and cost accounts.
• Contract and project accounting for government and commercial programs, including earned value and milestone billing.
• Invoicing, revenue recognition, and margin analysis at the program, lot, or configuration level.

This is also how OEMs and prime contractors coordinate with suppliers at a commercial level. Purchase orders, receipts, and invoice matching all run through ERP, providing the financial backbone that external auditors expect.

Baseline routings and high-level work orders

ERP holds the nominal view of how work should flow through the factory:

• Standard routings that define major operations and work centers.
• Planned work orders that describe which assemblies will move through those routings and when.
• Reference to manufacturing and engineering data such as part numbers, revisions, and configuration families.

This level of structure is valuable for planning labor, synchronizing with MRP, and giving finance a way to understand progress. But it is not the level where aerospace execution actually lives.

Where ERP Stops: The Reality Gap on the Shop Floor

The further you get toward the point of work, the more visible ERP’s limitations become. The model in ERP is abstract and relatively static. The factory is not.

Dynamic work sequencing and real-time priorities

On any given shift, supervisors and planners are constantly re-sequencing work:

• Pulling forward operations to protect a delivery milestone.
• Re-routing work around a down machine, unavailable tooling, or a blocked inspection station.
• Adjusting priorities when a hot unit arrives from a customer or a critical test slot opens up.

ERP can represent planned sequences and due dates. It is not designed to act as a live dispatch system that adapts minute by minute as constraints change. The result is a disconnect: what the ERP schedule says should be running and what the shop is actually running are often different, with the true logic living in local knowledge, emails, and paper travelers.

Detailed operation status, holds, and disruptions

ERP typically records status at the work order or major operation level: released, in process, complete. Aerospace execution requires far more granularity:

• Which specific unit is at which station right now?
• Is it actively being worked, waiting on material, or queued behind another lot?
• Is it on hold for an engineering issue, a suspected non-conformance, or a missing certification?

Capturing this level of status and context in ERP would mean turning a transactional database into a high-frequency event system. Most organizations choose not to do that, so they push this detail into travelers, local spreadsheets, or an MES-like tool, if one exists. The consequence: central systems show progress, but not the reasons behind delay or instability.

Granular traceability at the component and lot level

Aerospace programs demand deep traceability—not just of finished assemblies, but of individual components, lots, and process steps:

• Which exact hardware, material lots, and special processes are embedded in a serial-numbered unit?
• Which technician performed a specific operation, with which calibrated tools and which revision of the work instruction?
• How do you traverse that chain quickly when a supplier issue or field event triggers a containment?

ERP may be able to store some of this information, but doing so at the resolution and volume required for modern aerospace quickly becomes impractical. The data model and user experience are not optimized for capturing and navigating execution detail at the point of work.

How the Gap Shows Up in Day-to-Day Operations

The gap between ERP’s model and factory reality is not theoretical. It appears in the specific workarounds aerospace teams rely on just to run the day.

Shadow systems: spreadsheets and whiteboards

One of the clearest indicators that ERP is not enough is how much critical information lives outside of it:

• Supervisors maintain Excel boards with their own view of WIP, priorities, and constraints.
• Production meetings rely on printed reports annotated by hand to reflect the real situation.
• Cells and lines track status on whiteboards that are updated between shifts.

These shadow systems are a rational response to a real need: people require a fast, flexible, live representation of work that ERP does not offer. But they create risk. They are not controlled, not audited, and not visible to the rest of the organization.

Disconnected quality, inspection, and non-conformance workflows

In an AS9100 environment, quality and inspection processes must be tightly linked to execution. Yet they often run as parallel flows:

• Inspection plans and checklists in point solutions or PDFs.
• Non-conformance reports (NCRs) in a separate QMS, with manual reference to work orders and serials.
• Rework instructions and concessions communicated via email or manual document routing.

ERP might record the existence of an NCR or a rework order, but not the detailed path that unit took through quality decisions, nor the exact data needed to prove compliance in an audit. This fragmentation makes root cause analysis, escape investigations, and customer reporting slow and error-prone.

Manual status chasing for internal and customer reporting

Program reviews and customer status updates expose the underlying data problem. To answer seemingly basic questions—“Which units are at risk?” “What is blocking this delivery?” “How many hours of rework did we incur this month?”—teams often resort to manual status chasing:

• Walking the floor to visually confirm where hardware is.
• Calling or messaging supervisors and planners to reconcile discrepancies.
• Assembling one-off slides that combine ERP data with locally maintained trackers.

This is precisely the pattern the industry sees when external scoreboards like deliveries and backlog are treated as truth while the execution system itself remains opaque. The same misalignment exists inside many factories: summary metrics in ERP look fine, but the mechanisms producing them are fragile.

Why ERP Extensions Rarely Solve Execution

Many aerospace organizations attempt to close this gap by adding customizations or satellite modules onto ERP. The intent is reasonable—extend the system you already have—but structural constraints get in the way.

Architectural constraints of transactional systems

ERP architectures are optimized for transaction integrity and financial correctness, not for capturing every event happening on the shop floor. Pushing detailed execution into ERP creates challenges:

• High-frequency status updates can strain performance and licensing models.
• Complex, stateful workflows are difficult to represent with generic transaction tables.
• User interfaces built for planners and accountants are not ideal for operators on the line.

The result is often a partial implementation: a few extra fields, a couple of custom screens, and still a heavy reliance on external trackers for the real work.

Config complexity and variant-rich aerospace products

Aerospace hardware is highly configurable. Block points, customer-specific options, retrofits, and engineering changes all intersect on the same physical units. Representing that complexity at the execution level requires:

• Fine-grained configuration control down to the unit and operation.
• Dynamic work instructions that reflect the exact configuration in front of the operator.
• Ability to split and merge work, track partial completions, and handle deviations without losing traceability.

ERP is typically built around products, BOMs, and routings—not around an ever-changing, unit-specific execution graph. As configuration complexity grows, the gap between ERP’s static model and reality widens.

Audit and certification needs beyond standard ERP data models

AS9100, customer flow-downs, and regulatory requirements (e.g., export control, special processes, safety-critical components) demand an auditable record that goes beyond standard ERP fields:

• Who performed each step, with which qualifications, at what time.
• Which specific procedures, drawings, and revisions were in force.
• How non-conformances, escapes, and corrective actions were identified and resolved.

Trying to retrofit this level of detail into ERP often results in overgrown, hard-to-maintain customizations that still don’t match how work is actually performed. Audits then become reconstruction exercises instead of straightforward queries on a clean execution history.

Defining the Aerospace Execution Layer

To resolve this, organizations increasingly recognize the need for a distinct—but tightly connected—execution layer. This is not a competing system of record for finance and planning. It is the operational environment that lives between plan and reality.

Characteristics of a system that lives between plan and reality

A true aerospace execution layer has several defining properties:

• Plan-aware but not plan-bound: It understands work orders, routings, and configurations from ERP, but allows dynamic re-sequencing, holds, and path changes based on actual conditions.
• Event-centric: It records what really happens at the point of work—starts, pauses, completions, inspections, NCRs, and signoffs—as a time-stamped stream of events.
• Unit-level context: It follows individual serials or lots through their unique paths, rather than just aggregating by part number or routing.

This is the layer where execution rules and operational reality are reconciled in real time.

Real-time WIP tracking, operation context, and user workflows

Practically, an execution platform must allow teams to see and control work in process (WIP) at a level ERP can’t provide:

• Where every unit is, which operation it is on, and what is blocking it, updated continuously.
• Operator-guided workflows that present the right instructions, data capture, and checks at the right step.
• Visualizations of queues, constraints, and aging WIP for supervisors and program managers.

Instead of reconstructing status from multiple sources, the execution layer becomes the single operational picture of the factory—fed by events at the point of work and aligned with the plan in ERP.

Embedded traceability and configuration control at the point of work

Traceability and configuration control are most robust when they are embedded in how work is done, not layered on afterward. In an execution layer, that means:

• Capturing serials, material lots, and process parameters as part of the operator’s normal workflow.
• Ensuring only the correct, released instructions and data are available for the specific configuration in front of the operator.
• Automatically building a complete genealogy and event history as a byproduct of execution, not a separate data-entry task.

This is the difference between being audit-ready by default and having to assemble evidence from ERP logs, shared drives, and paper packets whenever a customer or regulator asks.

Integrating ERP with a Connected Execution Platform

None of this works if ERP and the execution layer are isolated. The value comes from clear boundaries and deliberate integration, not from trying to make one system do every job.

Data boundaries: what stays in ERP versus the execution layer

A clean architecture assigns responsibilities explicitly:

• ERP remains the system of record for contracts, orders, BOMs, routings, inventory positions, and financial transactions.
• The execution layer becomes the system of reality for WIP state, operation history, quality events, operator interactions, and unit-level genealogy.

The two are synchronized, but they do not duplicate each other. ERP doesn’t need every operator keystroke. The execution platform doesn’t need to manage accounts receivable.

Event-driven updates from shop floor to planning systems

Instead of batch uploads or manual status pushes, the execution layer should feed ERP using event-driven integration:

• When operations complete, ERP receives the necessary confirmations for backflush, cost collection, and schedule updates.
• When holds or major deviations occur, ERP and planning tools get signals that a plan needs to be re-evaluated.
• When units move across key milestones, program-level metrics refresh automatically.

This approach preserves ERP’s role as the planning and financial backbone while ensuring its view of progress is anchored in actual execution data.

Synchronizing BOM, routing, and configuration data

For aerospace, configuration discipline is non-negotiable. Integration must ensure:

• Approved BOMs, routings, and effectivity rules flow from ERP and engineering systems into the execution layer in a controlled manner.
• Changes are versioned, with clear cut-in points so that units in process do not drift into ambiguous states.
• The execution layer can enrich that structure with unit-specific context (e.g., concessions, unique serials, local rework paths) without breaking the underlying configuration logic.

This is also where a practical digital thread begins to emerge: the ability to follow a configuration from engineering intent through planning, execution, test, and delivery without losing continuity.

Example integration patterns for aerospace manufacturers

In practice, aerospace manufacturers often adopt patterns such as:

• Work-order centric integration: ERP creates and owns orders; the execution layer owns detailed steps and status, sending back completions and key quality flags.
• Serial-centric integration: Each serial number becomes the common key across ERP, execution, test, and field systems, allowing clear traceability across the lifecycle.
• Milestone signaling: The execution layer drives program milestones (e.g., mate, power-on, test complete) that ERP and reporting tools consume as the basis for progress and billing.

These patterns align with aerospace realities: long cycles, complex assemblies, and the need to reconcile financial, operational, and regulatory views of the same hardware.

Choosing the Right System Roles for a Regulated Environment

In an AS9100-governed organization, architecture choices are also compliance choices. How you assign system roles influences your ability to demonstrate control, traceability, and data integrity.

Aligning with AS9100 and customer flow-down requirements

AS9100 emphasizes documented processes, controlled records, and clear responsibility for quality. A well-designed split between ERP and execution supports this by:

• Making ERP the authoritative source for approved part numbers, routings, and high-level planning.
• Using the execution layer to capture how those processes were actually executed, including deviations, approvals, and verifications.
• Ensuring that customer and regulatory requirements are traceable from specification through to the specific steps and checks performed on each unit.

This reduces the gap between procedure and practice, which is where many audit findings originate.

Ensuring data integrity and auditability across systems

Having multiple systems does not have to mean fragmented data. It can, if done well, increase auditability:

• ERP holds stable master data and financial transactions, with strong change control.
• The execution layer produces a high-resolution record of events, approvals, and measurements tied to specific units.
• Integration provides a clear chain of custody: it is always visible how plan data was used, how execution data was produced, and how the two informed each other.

This architecture also supports selective disclosure: you can give customers or regulators deep visibility into execution history without exposing internal financial structures.

How platforms like Connect 981 complement, not replace, ERP

The industry’s direction is not to abandon ERP, but to surround it with systems that make its information meaningful in real time. Platforms like Connect 981 operate in this execution space:

• Taking the plan, configuration, and contractual context from ERP.
• Providing the live, unit-level picture of work, quality, and traceability that ERP cannot practically own.
• Feeding clean, structured execution signals back into planning, reporting, and decision-making layers.

For aerospace manufacturers, the question is less “Can ERP be made to do everything?” and more “How do we design a connected execution system where ERP, the shop floor, and quality all see the same reality?” The answer lies in embracing a dedicated execution layer that complements ERP, closes the visibility gap, and makes the high-level scoreboard reflect the real state of the system underneath.

Implementing ISO 22400: Practical Steps to Standardize Manufacturing KPIs

ISO 22400 gives aerospace and defense manufacturers a common language for manufacturing KPIs, but the standard does not tell you how to roll it out across MES, ERP, historians, and supplier portals. Turning its concepts into repeatable practice requires a structured implementation approach that respects existing systems, AS9100 processes, and the realities of multi-site aerospace production. This guide focuses on practical, non-vendor-specific steps to adopt the ISO 22400 manufacturing KPI framework inside a regulated aerospace manufacturing environment.

The goal is not formal certification. Instead, the emphasis is on making KPI definitions consistent across plants, programs, and partners so that “availability,” “utilization,” and order-related indicators mean the same thing in every system and report. Done correctly, ISO 22400 becomes part of your digital thread, not a competing structure.

For teams putting this topic into daily operation, industrial security evidence, security and compliance requirements, a connected execution platform help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on Connect 981’s aerospace execution solutions, real aerospace execution examples, Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

Assessing Your Current KPI Landscape

Inventorying existing KPIs and definitions

The starting point for ISO 22400 implementation is a realistic picture of the KPIs you already use. In a typical aerospace or space hardware program, KPIs are scattered across:

• MES dashboards monitoring work centers, takt performance, and rework rates
• ERP and MRP reports on schedule adherence, order lead time, and WIP age
• QMS and nonconformance systems tracking defect rates, escapes, and MRB cycle times
• Maintenance systems tracking equipment downtime and mean time between failures
• Excel-based “shadow systems” created by program teams and industrial engineers

Create a structured KPI inventory that captures at least:

• KPI name as used today (for example, “machine uptime,” “line utilization,” “on-time to promise”)
• Formal or informal definition, including what is in or out of scope
• Calculation description or formula (even if only documented in a spreadsheet)
• Data sources and systems (MES, historian, ERP, QMS, manual entry)
• Organizational owner (operations, quality, program office, finance)
• Where it is visible (reports, dashboards, SLAs, customer scorecards)

For aerospace organizations running multiple sites or supporting multiple OEM programs, capture which sites or programs use each KPI. Many inconsistencies only appear when comparing KPI catalogs across factories or business units.

Identifying inconsistent terms across plants and systems

With the inventory assembled, the next step is to surface inconsistent terminology. In aerospace production, this often appears in three patterns:

• Same name, different meaning – for example, one plant labels a KPI “availability” but includes scheduled maintenance in the denominator, while another excludes it.
• Different name, same meaning – for example, “uptime” in one system and “run time” in another both correspond to the same operating state.
• Different aggregation logic – for example, OEE calculated at the equipment level in one plant and at the line level in another, but reported as a single corporate metric.

Document these conflicts explicitly. ISO 22400 implementation is largely the process of resolving them and aligning to the standard’s definitions for time categories, states, and indicator semantics. Pay particular attention to KPIs that appear in:

• Customer-facing reports or contract deliverables
• Regulatory or airworthiness-related metrics (for example, defect escape rates)
• Executive dashboards and board-level reporting

These are the KPIs where ambiguity is most costly and where alignment with ISO 22400 will have the greatest impact on clarity and comparability.

Mapping Existing KPIs to ISO 22400 Concepts

Renaming vs. re-defining KPIs

Once you understand your current KPI landscape, the next step is to map those KPIs onto ISO 22400 concepts. The standard provides structured definitions for performance indicators and KPIs based on equipment states, time categories, and quantity-based measures. For each existing KPI, ask:

• Does ISO 22400 define a directly comparable KPI (for example, an availability or utilization concept)?
• If so, is our current definition materially aligned, or are there meaningful differences in scope or time basis?
• If not, is our KPI a useful extension (for example, a specific aerospace traceability or certification metric)?

In practice, you will end up with three categories of KPIs:

1. Aligned KPIs – Current definition closely matches an ISO 22400 KPI. Here, you can retain the definition and, if needed, adopt ISO 22400’s naming and attribute conventions.
2. Adjustable KPIs – KPIs that can be brought into alignment with limited changes, such as slightly adjusting time categorizations or clarifying which equipment states are included.
3. Non-standard KPIs – Aerospace- or program-specific KPIs that serve important purposes but are outside ISO 22400’s scope (for example, certification batch release lead time, or first article inspection queue time).

For the first two categories, decide whether you will:

• Rename the KPI to match ISO 22400 terminology while keeping the underlying logic essentially the same, or
• Re-define the KPI to fully conform with the ISO 22400 concept, updating the calculation logic and documentation.

Renaming is less disruptive but can leave subtle inconsistencies if the underlying logic still diverges from the standard. Re-defining offers better interoperability but requires more careful change management and stakeholder communication.

Dealing with near-duplicates (availability vs. uptime)

Near-duplicate KPIs are common in aerospace factories that have grown through acquisitions or that support different OEM programs with separate reporting expectations. A classic example is “availability” versus “uptime,” both attempting to describe how much of the planned time equipment spends in productive states.

ISO 22400 helps by providing precise definitions for equipment states (e.g., RUN, STOP, IDLE, SLOW) and the time categories derived from them. To reconcile near-duplicates:

1. Express each existing KPI in terms of ISO 22400 states and times (for example, “uptime” = RUN time only; “availability” = RUN + IDLE over planned time).
2. Identify which KPI best aligns with the ISO 22400 availability or utilization concept.
3. Standardize on that definition and make the alternative an alias or a retired KPI.

In aerospace, be especially rigorous with KPIs used in customer contracts or offset agreements. If an OEM contract references “equipment availability” for a nacelle line or composite layup cell, you should ensure the governing definition is explicitly mapped to the ISO 22400 concept and unambiguous across all reporting tools.

Adapting Data Models and Interfaces

Aligning equipment states and time categories

Conceptual alignment is only effective if your data models support it. ISO 22400 relies heavily on equipment states and their associated times. In practice, this means standardizing how signals from machines, test stands, and assembly cells are translated into high-level states across all plants.

For an aerospace environment with diverse equipment (CNC machining centers, autoclaves, bonding ovens, engine test cells, structural assembly lines), the implementation steps typically include:

• Defining a canonical set of equipment states aligned with ISO 22400 (for example, RUN, STOP-planned, STOP-unplanned, IDLE, SETUP, SLOW).
• Mapping PLC or control system signals into those states in a consistent way, even if different OEMs use different tags.
• Ensuring that historians and MES capture time in each state at an appropriate granularity.
• Deriving standardized time categories (planned time, busy time, operating time, downtime) from those states.

Because aerospace production frequently includes long-cycle, high-mix operations, state definitions must also consider:

• Setup and changeover for configuration changes and engineering effectivity
• Waiting states due to missing certifications, FAI completion, or quality hold
• Planned pauses due to coordination with external test facilities or customer inspections

Your implementation should make these distinctions explicit so that KPIs derived from state times remain interpretable by both operations and compliance teams.

Updating MES, ERP, and historian data schemas

After aligning states, you need to ensure that the underlying data models can express ISO 22400 KPIs cleanly. This does not require replacing existing systems, but it does typically involve schema extensions and interface adjustments. Common changes include:

• Adding standardized KPI identifiers and attributes to MES and reporting databases.
• Introducing explicit fields for ISO 22400 time categories instead of inferring them in every report.
• Tagging KPIs as ISO 22400-aligned versus organization-specific extensions.
• Harmonizing units of measure and timestamp conventions across systems (especially important in multi-site, multi-time-zone aerospace networks).

For ERP systems that manage orders and work breakdown structures, you may need to:

• Align production order and operation identifiers with the objects of measurement defined in ISO 22400.
• Ensure that order-level and equipment-level KPIs can be linked, enabling analysis of how equipment performance affects program schedule adherence.

A digital manufacturing platform such as Connect 981 can sit above existing MES, QMS, and ERP systems, mapping their native data structures into an ISO 22400-aligned KPI model. This approach allows you to standardize KPI semantics without forcing a single vendor stack across the entire enterprise or supply chain.

Governance: Owning and Maintaining KPI Definitions

Creating a KPI data dictionary and ownership model

ISO 22400 implementation fails quickly if KPI definitions drift over time. To prevent this, establish a formal KPI data dictionary and governance model that treat KPI definitions as controlled data assets, similar to engineering configurations or process specs.

Your KPI data dictionary should include, at minimum:

• The KPI name and unique identifier
• A clear, ISO 22400-based conceptual definition
• Mathematical expression or calculation logic
• Object of measurement (equipment, line, work center, area, site, order)
• Applicable time behavior, units of measure, and expected range
• Data sources and system-of-record
• Primary user groups (operators, manufacturing engineering, program management, executives)

Treat the dictionary as a controlled document or database under configuration control. Assign explicit ownership, typically through a cross-functional KPI governance board that includes operations, quality, IT/OT, and program representation. In AS9100 environments, the KPI dictionary often integrates with existing document control and change management processes.

Change management for KPI definitions and dashboards

Because KPIs influence decisions, incentives, and sometimes customer penalties, changing a KPI definition is a significant event. Your governance model should define:

• How KPI changes are proposed, reviewed, and approved
• How version history is maintained, including effective dates for each definition
• How changes propagate into reports, dashboards, and interfaces
• How historical data is handled (recalculated, re-labeled, or left unchanged with clear cutover markers)

In practice, this often means adopting a release cadence for KPI changes (for example, quarterly) and treating KPI updates like software or process changes. For aerospace programs with strict contractual reporting, align KPI definition changes with contract cycles or explicit customer agreement to avoid disputes over performance metrics mid-program.

Training Stakeholders on ISO 22400 Concepts

Educating operators, engineers, and managers

Standardized KPIs only deliver value if stakeholders understand what they mean and trust them. ISO 22400 concepts must therefore be embedded into everyday language on the shop floor and in program reviews.

Training should be tailored by role:

• Operators and cell leads need to understand equipment states, why accurate state entry matters, and how their actions affect KPIs such as availability and utilization.
• Manufacturing and industrial engineers need deeper knowledge of time categories, data models, and how their process changes might impact KPI definitions.
• Program managers and executives need clarity on how site-level and equipment-level ISO 22400 KPIs roll up to program performance views and what is and is not comparable across plants.

Use real examples from your own aerospace lines—such as a composite layup cell, an engine test bay, or a structures assembly station—to illustrate how states, times, and KPIs interact. This grounding avoids the perception that ISO 22400 is an academic overlay disconnected from day-to-day operations.

Communicating changes to suppliers and customers

Aerospace and defense production depends on a complex, regulated supply chain. When you change KPI definitions, your suppliers and customers can be affected, especially if KPIs appear in contracts, supplier scorecards, or performance-based logistics agreements.

For key partners, consider providing:

• A summarized ISO 22400-aligned KPI catalog you intend to use
• Clear mapping from any previously used KPIs to the new definitions
• Transition timelines and how historical performance will be treated

Some organizations use a digital manufacturing platform as a shared lens where both internal teams and suppliers can see KPI definitions and values aligned to the same ISO 22400 semantics. This approach minimizes misunderstandings when comparing performance across different factories or supplier tiers.

Example Implementation Timeline and Pitfalls to Avoid

Phased rollout across sites and systems

ISO 22400 implementation is best approached as a phased program rather than a single “big bang,” especially in multi-site aerospace networks with legacy systems. A typical pattern might look like:

1. Pilot scope definition – Select one value stream or product family (for example, a specific engine model, satellite program, or structural assembly line) and a constrained set of KPIs (for example, availability, utilization, order execution reliability).
2. Discovery and mapping – Complete the KPI inventory, mapping, and data model alignment for the pilot scope, including necessary MES/historian tweaks.
3. Governance and training – Stand up the KPI data dictionary, governance structure, and targeted training for the pilot stakeholders.
4. Pilot operation – Run with ISO 22400-aligned KPIs in parallel with existing reporting for a defined period to build trust and validate behavior.
5. Scale-out – Extend to additional lines, plants, or supplier tiers, reusing the data models and governance patterns built in the pilot.

Timelines will vary by organization size, system complexity, and regulatory constraints. The key is to preserve consistency of definitions while allowing local implementations to adapt to specific equipment, processes, and certification requirements.

Common mistakes in ISO 22400 adoption

Several common pitfalls tend to derail ISO 22400 initiatives in aerospace and defense manufacturing:

• Treating ISO 22400 as a reporting project only – Focusing solely on dashboards and ignoring the underlying state models and data quality leads to attractive visuals with inconsistent semantics.
• Over-customizing the standard – Adding many local variants of KPIs with subtle definition differences defeats the purpose of standardization and complicates multi-site comparisons.
• Underestimating change impact – Changing KPI definitions without careful communication can undermine trust from program teams and external partners who rely on year-over-year comparability.
• Ignoring non-standard but critical KPIs – For aerospace-specific indicators (for example, part genealogy completeness metrics or airworthiness sign-off cycle time), the goal is coexistence with ISO 22400, not forced alignment where it does not fit.

A disciplined approach that distinguishes between ISO 22400-aligned KPIs and intentional, well-documented extensions gives you the benefits of standardization without constraining necessary aerospace-specific measures.

Bringing ISO 22400 into the Aerospace Digital Thread

ISO 22400 does not replace your AS9100 processes, digital thread initiatives, or engineering change control. Instead, it supplies a shared vocabulary for performance measurement that can be woven through existing systems and workflows. When equipment states, time categories, and KPI definitions are standardized, it becomes easier to connect events in design, planning, execution, and quality into a coherent performance narrative.

Platforms like Connect 981 can implement ISO 22400-aligned KPI structures as part of a broader aerospace digital operations layer, tying together MES, ERP, QMS, and supplier data without forcing a single monolithic solution. The standard defines what KPIs mean; your organization decides which ones matter, how aggressively to target them, and how they support safe, compliant, and efficient aerospace production.

Most FAI debates do not start with bad intent. They start with a drawing revision, a supplier move, a long production gap, or a customer note buried in a purchase order. This guide answers when is full fai required, when a partial fai is enough, and how aerospace teams can make that decision without turning every change into a program delay.

Fast Answer: When Is a Full First Article Inspection Mandatory?

A full first article inspection is required when the prior baseline no longer proves that the article meets all engineering, manufacturing, and customer requirements. AS9102C, released on 2023-06-28, is the current aerospace reference, and customer flowdowns can be stricter than the standard.

A full FAI is required during new product introduction, production gaps, significant changes, major process overhauls, or customer demand for a re-baseline of quality data. If minor modifications are made, a partial or Delta FAI, focusing only on affected characteristics, is used instead of repeating the full FAI process.

Core triggers include:

• New part number, new first article, or first build to a customer design.
• Design change affecting fit, form, function, safety, or performance.
• Production lapse of 24 months or more, unless customer requirements define another interval.
• New site, new primary equipment, or new production process route.
• Change of material, source, or key special process, such as heat treat, plating, bonding, or welding.
• Customer-directed full FAI on the contract, purchase order, corrective actions plan, or approval process.

A full FAI covers the entire drawing and full characteristic accountability. A partial FAI covers only affected characteristics and links back to the baseline first article inspection report.

Full vs Partial FAI: Clear Definitions and Boundaries

A First Article Inspection (FAI) is a comprehensive review of the engineering documentation and the manufacturing process from raw materials through conversion and functional testing for one part. The AS9102 standard, developed by the International Aerospace Quality Group (IAQG), outlines the requirements for First Article Inspection in the aerospace industry, ensuring that all aspects of design, manufacturing, and inspection are verified and documented.

A complete fai includes:

• Ballooned engineering drawings or 3D models with every design characteristic, material note, surface finish, and specification requirement identified.
• A complete article inspection report FAIR using the three forms: Form 1, part number accountability form; Form 2, product accountability; Form 3, characteristic accountability with measured values.
• Compatibility evaluation against the latest design records, specification requirements, documentation requirements, and purchase order.

A partial FAI includes:

• Only new or revised dimensions, notes, materials, inspection methods, or production process changes.
• A FAIR that references the original baseline article inspection report by number and date.
• Evidence that unchanged tooling, calibrated tools, coordinate measuring machines, and inspection plan remain controlled.

Boundary example: a design note clarification with no functional effect usually supports partial FAI. A new machining center and fixture for the same part may require full FAI because the manufacturing environment changed.

Trigger Matrix: When a Full FAI Is Required vs When Partial Is Enough

Use a trigger matrix during supplier review, quality control, and formal approval. It gives responsible parties a consistent way to decide the required article inspection level.

Event

Impact

Typical decision

Notes

New Airbus A320neo bracket

No baseline

Full FAI

New first article inspection requirement

Hole location or tolerance change

Fit or function

Full FAI

Assembly risk

Drawing typo correction

Documentation only

Partial FAI

No change to specified requirements

New forging supplier for landing gear

Material and safety

Full FAI

Supply chain risk

Deburr clarification or cosmetic surface finish

Cosmetic only

Partial FAI

Unless CTQ

Flight control link restarted after 30 months

Lapse

Full FAI

Revalidate process and fai report

Standard inspection only

No change

No FAI

Normal inspection results still recorded

Default to full FAI if risk is unclear. That rule reduces non conformances, audit debate, and late customer rejection.

First Article Inspection is crucial in industries such as aerospace, defense, and automotive, where precision and quality are paramount, helping to prevent defects and ensure products meet design and performance criteria from the outset of production. The same risk logic appears in other regulated industries, including a medical device production run where a component fails and the team must prove the production process remains valid.

Design Change Triggers: Do All Design Changes Require a Full FAI?

No. AS9102C and most OEM specifications distinguish between changes that affect fit, form, function, safety, or performance and changes that are editorial.

Full FAI is normally required when a design revision:

• Adds or relocates mating interfaces, mounting holes, or datum schemes.
• Changes CTQ tolerances, GD&T, or key components.
• Adds functional requirements for pressure, load, vibration, leakage, electrical paths, or functional testing.

Partial FAI is commonly used when the change is limited to:

• Clarified inspection methods without changing the requirement.
• Spelling, unit symbols, or reference document numbers.
• Removal of unused reference dimensions while retaining the functional scheme.

Before deciding, confirm all routings, digital work instructions, CNC programs, CMM programs, and engineering documentation match the new revision. Some OEMs, including Boeing through D6-51991 practices and primes using advanced product quality planning or AS9145, may require full FAI for any revision on high criticality parts.

Process, Tooling, and Location Changes: When Production Lapses and Restarts Matter

AS9102C treats significant process and context changes as renewed article inspection triggers even when the drawing did not change. The question is whether the prior first article inspection fai still represents the actual production process.

Full FAI is typical for:

• Moving production to a different facility.
• Switching manual machining to five axis CNC, a new molding press, or a new welding cell.
• Replacing key fixtures that locate CTQ features.
• Introducing automation that changes process capability.

A common aerospace rule is that if manufactured parts have not been produced for 24 months or more, full FAI is usually required unless the customer specifies a shorter or longer interval. An actuator housing last built in 2021 and reordered in 2024 should receive full FAI to revalidate the article inspection process and article inspection report fair.

Partial FAI may be reasonable for documented minor tool wear replacement or non-critical cleaning changes. Connect981 can track last-production dates, routing changes, tooling IDs, and production process changes so teams can quickly see whether a full or partial FAI is required.

Material, Special Process, and Supplier Changes: Article Inspection Requirement Impacts

Material and special process changes are frequent sources of escapes. Full FAI is usually required for:

• Alloy or material specification changes, such as 7075-T6 to 7050-T7451.
• Material form changes, such as bar to forging or casting.
• New material supplier for structural or safety-critical parts.

Special process changes also matter. Heat treat, NDT, anodizing, plating, bonding, welding, curing cycle, temperature, or atmosphere changes should trigger re-validation and updated article inspections. If the change may affect performance, fatigue, corrosion, sealing, or safety, default to full FAI. If only a localized coating changes with no CTQ impact, partial FAI may be acceptable with customer approval.

Form 2 must be updated with new certifications, source approvals, test results, and product accountability evidence.

Customer, Regulatory, and Corrective-Action Driven Triggers

First Article Inspection (FAI) is mandated by various industry standards, including AS9100 for aerospace, which requires compliance with specific quality management practices to ensure that products meet design specifications before full production. FAI enhances regulatory compliance, as it is a mandatory requirement for many manufacturing sectors, including aerospace and automotive, ensuring that manufacturers meet critical regulations and standards.

Customer-driven triggers include:

• PO or quality clause requiring “AS9102 full FAI with Forms 1–3.”
• OEM-specific checks, such as BFAI, Boeing First Article Inspection.
• APQP, PPAP, or production part approval process gates.

Corrective-action triggers include:

• Escape or major nonconformance showing the original FAI is no longer valid.
• Repeat defects on CTQ features requiring containment, root cause, and full revalidation.

Audits, DER or UMAR approvals, NADCAP findings, AS9100 gaps, and safety-of-flight issues may also force retroactive full FAIs. Transparent article inspection reports help preserve customer confidence.

Supplier Decision Logic: How to Choose Full vs Partial FAI in Practice

Suppliers need repeatable fai procedures, not ad hoc judgment. A practical path is:

1. Check AS9102C, contract, customer requirements, quality requirements, and purchase order.
2. Classify the trigger: new part, design revision, process change, material change, location change, lapse, or corrective action.
3. Assess fit, form, function, safety, regulatory impact, and whether the article meets all specified requirements.
4. Use an internal matrix to choose full FAI, partial FAI, or no FAI, then document the rationale.
5. Get customer concurrence when selecting partial FAI for borderline cases.

High criticality parts such as flight controls, landing gear, pressure vessels, and structural sub component assemblies should lean toward full FAI. Low-risk covers or brackets may justify partial FAI for minor changes. The decision record should ensure traceability and support future audits.

What a Full FAI Actually Includes: Article Inspection Process and FAIR Content

Once triggered, the first article inspection process must follow a structured inspection process. Utilizing a full FAI can help detect errors, tooling misalignments, or misunderstood specifications before mass production begins, mitigating expensive scrap, rework, and recalls.

The article inspection process includes:

• Validate latest drawings, models, specifications, design specifications, and purchase order requirements.
• Balloon every dimension, material requirement, note, and surface finish.
• Execute dimensional, visual, material, and functional tests using calibrated tools, gages, NDT, and coordinate measuring machines.
• Record measured values, inspection results, pass or fail status, and approval signatures.

The First Article Inspection Report (FAIR) serves as a formal record of the inspection and provides crucial information to both the manufacturing entity and the customer, including inspection details, results, and approval signatures. The First Article Inspection Report (FAIR) is a critical document that summarizes the findings of the FAI process, including inspection results, non-conformance issues, and approval signatures, and is essential for compliance with industry standards.

Good FAIRs improve the approval process, ensure accuracy, support compatibility evaluation, and help both the manufacturer and the customer avoid disputes.

Avoiding Over-Inspection and Under-Inspection: Practical Risk Balancing

Full FAIs consume time. Under-inspection creates escapes. First Article Inspection (FAI) is crucial in various industrial quality management systems and standards, such as ISO 9001 and AS9100, as it acts as a form of risk mitigation by helping to catch potential issues before production begins.

Do not repeat full FAI for pure editorial corrections when no requirement changed. Use partial FAI for tightly scoped changes backed by stable capability data.

Do not rely on partial FAI when the manufacturing method, site, key material, or long lapse has changed. Implementing a structured FAI process can prevent costly defects, which dramatically reduces costs associated with scrap, rework, and product recalls, thereby enhancing overall manufacturing efficiency.

A robust Quality Management System (QMS) provides a structured framework and systematic approach to quality control, which is instrumental in ensuring the accuracy, reliability, and compliance of First Article Inspection processes in the manufacturing industry. Quality Management Systems are essential for ensuring compliance with industry standards such as AS9100, which governs quality assurance in aerospace manufacturing. The implementation of a Quality Management System helps organizations monitor and control all aspects of part production, ensuring that inspection plans are based on the technical data package tied to customer contracts.

One note on terminology: outside manufacturing, a full Fair Admission Index is needed when broad demographic changes invalidate prior admissions results or when transitioning between admissions criteria. In educational contexts, a full Fair Admission Index (FAI) is required when transitioning to a lottery-based system to ensure equitable access for all students. That is not the aerospace first article inspection fai discussed here.

Digitizing FAI and Trigger Logic with Connect981

Connect981 is built for aerospace manufacturing and MRO teams that need reliable digital article inspection fai workflows, not more spreadsheet control points. It connects ERP, MES, QMS, supplier data, documentation, and shopfloor execution in one operations layer.

The Connect981 platform helps teams:

• Centralize engineering documentation, revision history, routings, inspection plan data, and quality management records.
• Embed a configurable FAI trigger matrix into workflows so article inspection requirement decisions are consistent.
• Generate and manage article inspection reports, including characteristic accountability tables from ballooned drawings or models.
• Track production lapses from ERP and MES data and flag when AS9102C logic suggests a new full FAI.
• Link non conformances and corrective actions directly to FAI records.
• Give cross-factory and supplier visibility into current full and partial FAI status.

This ensures consistency, supports continuous improvement, and helps teams exceed customer expectations without adding manual reporting burden.

Request a demo to see a working FAI trigger matrix, digital first article inspection process, and automated FAIR workflow inside Connect981.

In aerospace and defense manufacturing, equipment-related KPIs sit at the core of production visibility, certification readiness, and multi-site reporting. ISO 22400 gives a shared vocabulary for these KPIs, including overall equipment effectiveness (OEE), availability, and utilization, without forcing plants into a single calculation method. For aerospace organizations building a digital thread across MES, ERP, PLM, and quality systems, aligning with the ISO 22400 manufacturing KPI standard helps ensure that equipment performance numbers mean the same thing at every site and supplier.

This article explains how ISO 22400 treats equipment-focused KPIs conceptually, how its OEE-related models (OEEA, OEEB) differ from traditional TPM-style OEE, and how aerospace manufacturers can adopt the terminology without rewriting every KPI formula. The focus is on definitions and structure, not on prescribing a specific way to improve performance.

For teams putting this topic into daily operation, ISO 22400 KPI governance, shop floor execution control, a connected execution platform help connect the concept to traceability, work-order reality, and audit-ready evidence.

The same operating model also depends on Connect 981’s aerospace execution solutions, real aerospace execution examples, Connect 981’s aerospace operations guidance, practical aerospace operations FAQs, especially when decisions have to move across quality, production, suppliers, and program leadership without losing context.

Why Equipment KPIs Are Central in ISO 22400

The role of equipment behavior in manufacturing performance

ISO 22400 pays particular attention to equipment because, in most aerospace production environments, complex assets drive both throughput and certification risk. A five-axis machining center, composite layup cell, or engine test stand may be the bottleneck for an entire aircraft program or propulsion line. If those assets are not running when planned—or if they run but produce nonconforming hardware—schedule and cost performance quickly degrade.

The standard therefore structures many KPIs around how equipment spends time and what it produces in that time. Time spent in specific states (RUN, STOP, IDLE, SLOW) is aggregated into concepts such as operating time, busy time, and downtime. Quantities produced in those time windows are tracked as good parts, rejections, and rework quantities. From these foundational elements, ISO 22400 defines equipment-oriented KPIs that can be compared across different plants, systems, and products.

For aerospace, this provides a disciplined way to separate questions like “Was the machining center available?” from “When it was busy, did it produce conforming hardware?” That distinction is important when determining whether issues belong to maintenance, production planning, or quality engineering.

Linking equipment KPIs to MOM and enterprise decisions

ISO 22400 places equipment KPIs within the broader context of manufacturing operations management (MOM). KPIs such as availability, utilization, and conceptual OEE are positioned at the level where work orders, routings, and resource assignments are executed—typically managed by MES or similar systems. These indicators feed upstream decisions in enterprise systems without forcing those systems to adopt a particular database or UI technology.

In an aerospace plant, this linkage might look like:

• MES level: Tracks equipment state changes, order execution, and scrap events; calculates ISO 22400-aligned indicators.
• ERP level: Consumes summarized equipment KPIs to refine capacity planning, program cost forecasts, and promise dates.
• PLM / configuration management: Uses production execution and quality-related KPIs to assess manufacturability of new designs and the impact of engineering changes.

By using a common ISO 22400 vocabulary across these systems, aerospace organizations can reason about equipment constraints, schedule risk, and capacity investments without debating what “availability” or “utilization” actually mean.

Conceptual View of OEE in ISO 22400

OEE as a composition of time and quantity indicators

ISO 22400 treats overall equipment effectiveness as a conceptual construct rather than as a single mandated formula. In the standard, OEE is assembled from well-defined time-based and quantity-based indicators. Time indicators describe how much of the calendar period is actually used for productive operation, while quantity indicators describe how much of the resulting output meets quality criteria.

This leads to a layered structure:

• Time-based elements: planned time, operating time, busy time, downtime categories, and related state-derived durations.
• Quantity-based elements: produced quantity, accepted quantity, rejected quantity, and reworked quantity.
• Derived indicators: equipment availability, utilization, and conceptual effectiveness ratios built from combinations of the above.

For aerospace plants, this abstraction allows different product families (e.g., composite structures vs. precision machined parts) to maintain their own cycle-time assumptions and yield profiles, while still reporting high-level OEE-related KPIs in a comparable way across programs.

How OEEA and OEEB models are structured conceptually

Within this conceptual framework, ISO 22400 introduces multiple OEE-related models, often referenced in literature as OEEA and OEEB. Each model describes a different way to compose time and quantity elements into an effectiveness measure while staying within the same terminology set.

Conceptually, OEEA tends to emphasize the relationship between busy time and produced volume, while OEEB more explicitly separates availability-related time losses from speed and quality-related losses. Both models rely on the same building blocks:

• Time structure: definitions of when equipment is considered operating, busy, or down.
• State mapping: rules for assigning RUN, STOP, IDLE, and other states into those time buckets.
• Output structure: distinctions between good pieces, scrap, rework, and test output.

ISO 22400 does not require any aerospace manufacturer to select one model over the other. Instead, it provides a common language so that, for example, a machining center in a European airframe plant and a test stand in a North American propulsion facility can both declare which conceptual OEE model they use and how it maps to their local KPI definitions.

Availability, Performance, and Quality Concepts

Time categories used to express availability

Availability in ISO 22400 is based on carefully defined time categories, rather than on informal labels such as “uptime.” Typical categories include:

• Planned time: the portion of the calendar where equipment is scheduled to be available for production or test.
• Operating time: the subset of planned time when the equipment is in a state that can produce, even if it is not actually busy.
• Busy time: the subset of operating time during which equipment is actively executing work (for example, producing a part or running a test sequence).
• Downtime: periods within planned time where the equipment is not available for production due to failures, setups, or other reasons.

For aerospace, this distinction between operating and busy time is important. A radar test bench that is powered on and ready (operating) but waiting for engineering sign-off or configuration data is not busy, yet it still consumes facility resources and may block other work. ISO 22400’s definitions support KPIs that highlight this difference.

Quantity concepts behind performance and quality factors

ISO 22400 also standardizes how quantities are treated within KPIs. Rather than mixing concepts like throughput and yield, it separates them into well-defined indicators:

• Produced quantity: total units processed by the equipment in a period, regardless of quality.
• Accepted quantity: units that meet defined quality criteria and are released for downstream use (assembly, test, shipment).
• Rejected quantity: units that are scrapped or quarantined as nonconforming.
• Reworked quantity: units that initially failed criteria but are successfully recovered through rework.

From these quantities, performance and quality-related factors are derived. In aerospace and space hardware production, where part genealogy and serial-level traceability are mandatory, tying these quantity concepts back to specific work orders, serial numbers, and configurations is essential. ISO 22400 does not define the traceability system itself, but it ensures that KPIs built on top of that system have consistent meaning.

Equipment States and Time Categories

RUN, STOP, IDLE, SLOW and their meaning

Equipment state models in ISO 22400 act as the bridge from control-system signals to conceptual KPIs. Common states include:

• RUN: equipment is executing productive work, such as machining, drilling, or test execution.
• STOP: equipment is not running, often due to a fault, changeover, or scheduled maintenance.
• IDLE: equipment is ready and capable of running but is waiting for material, instructions, or authorization.
• SLOW: equipment is running below its nominal performance, for example due to conservative feed rates on a new material or risk mitigation on a first article.

In an aerospace environment, these states can be further enriched with domain-specific reasons—such as waiting for nonconformance disposition, engineering change approval, or special process certification. ISO 22400 does not prescribe reason codes, but it ensures that however they are defined, they roll up consistently into state-based KPIs.

Mapping states to operating, busy, and downtime categories

Once state definitions are clear, ISO 22400 describes how to group them into time categories that underlie availability and utilization indicators. A typical mapping might be:

• Operating time: RUN, IDLE, SLOW, and possibly certain test or warm-up states.
• Busy time: RUN and SLOW, where equipment is actively processing a work order or test program.
• Downtime: STOP states that occur within planned time, subdivided into planned and unplanned downtime.

For aerospace manufacturers with highly engineered products, this mapping clarifies discussions where engineering or quality events appear as “downtime” from a scheduling perspective. If a composite cure oven is STOP because of an engineering hold on a material batch, the corresponding downtime can be categorized consistently across sites. That, in turn, supports comparisons across programs and facilities when analyzing bottlenecks in a regulated production network.

Comparing ISO 22400 OEE with Traditional TPM OEE

Where definitions align and where they differ

Traditional TPM-style OEE is often implemented as a product of three factors—availability, performance, and quality—each computed according to locally agreed formulas. ISO 22400 aligns with this general structure but is more explicit about the time and quantity elements that underlie each factor. Instead of declaring a single canonical OEE equation, it formalizes the building blocks and offers alternative composition models.

Alignment occurs at the conceptual level: unplanned downtime reduces availability; reduced speed and micro-stops affect performance; nonconforming output reduces quality. Differences arise in the degree of standardization. TPM implementations sometimes blur distinctions between operating vs busy time or between scrap vs rework, whereas ISO 22400 requires these concepts to be clearly separated and named. For aerospace programs seeking audit-ready KPI definitions, this additional clarity is an advantage.

Avoiding confusion in multi-site OEE reporting

One of the main risks in global aerospace production is believing that OEE numbers are comparable when they are not. Two plants might both report “OEE = 78%,” yet one includes test re-runs in performance losses while another does not. ISO 22400 helps avoid this by encouraging organizations to document which conceptual model they use (e.g., OEEA or OEEB), how states are mapped to time categories, and which quantity indicators are included in each factor.

For a multi-site aerospace or space hardware manufacturer, this documentation should be part of the digital manufacturing infrastructure: MES configuration, KPI catalogs, and integration contracts between systems. When a central team aggregates OEE data from different facilities, they can verify that the underlying ISO 22400 concepts match before drawing conclusions about best-performing plants or suppliers.

Using ISO 22400 Equipment KPIs Without Over-Prescription

Selecting which equipment KPIs to track

ISO 22400 defines a structured catalog of KPIs, but it does not tell an aerospace organization which ones it must use. In practice, plants choose a subset aligned with their operational priorities and regulatory context. A few examples:

• Engine test facilities may emphasize utilization and test-cycle adherence KPIs, since test cell access is a scarce resource.
• Precision machining centers may focus on availability and first-pass yield to manage capacity against long-cycle aerospace parts.
• Composite curing operations may track oven utilization and batch conformance indicators, as cure cycles often drive schedule risk.

All of these KPIs can be named and structured according to ISO 22400, even if not every KPI from the standard is implemented. That approach gives aerospace manufacturers a consistent conceptual basis while retaining flexibility.

Communicating definitions across plants and suppliers

The greatest value of ISO 22400 in aerospace manufacturing often appears at the boundaries between organizations: between a prime contractor and its tiered suppliers, or between an OEM and its MRO network. When contracts or performance reviews reference KPIs like equipment availability or utilization, tying those terms to ISO 22400 definitions reduces ambiguity.

Practically, this may involve maintaining an ISO 22400-aligned KPI dictionary within a digital manufacturing platform. Each KPI entry describes which states, time categories, and quantity indicators are used; which OEE-related model (if any) is assumed; and how the KPI is reported. When onboarding a new supplier or bringing a new plant into the network, that dictionary becomes the reference for configuring local MES and reporting systems, and it complements broader discussions of standardized KPIs as described in the ISO 22400 manufacturing KPI standard hub content.

Practical Considerations for Aerospace and Space Hardware Production

Integrating ISO 22400 concepts into MES and digital thread

To make ISO 22400 actionable, aerospace organizations embed its concepts in their MES and digital thread architecture. At the MES layer, equipment states, order events, and quality decisions are captured with sufficient granularity to derive ISO 22400-aligned time and quantity indicators. At higher layers, these indicators are associated with specific configurations, serial numbers, and engineering baselines, tying equipment performance back to the product definition.

In practice, this could mean:

• Standardizing state models and time-category mappings across all test stands or machine types in a program.
• Ensuring that part genealogy records link nonconforming quantities to the exact equipment and time window where they were produced.
• Configuring dashboards so that availability and utilization KPIs are derived from the same ISO 22400 building blocks across different plants.

This creates a consistent KPI layer in the digital thread, improving both operational decision-making and audit readiness.

Working within AS9100 and regulated environments

AS9100 and related aerospace quality requirements emphasize documented processes, traceability, and evidence-based decision-making. ISO 22400 contributes by providing standardized, auditable definitions of what key equipment-related KPIs mean. While AS9100 does not mandate specific OEE values or formulas, it does expect organizations to monitor and control processes that affect product quality and delivery.

By adopting ISO 22400 terminology, an aerospace manufacturer can demonstrate that KPIs used in management review and continuous improvement activities are consistently defined across programs and facilities. This reduces the risk that different sites interpret the same KPI differently during customer or regulatory audits and supports clear linkage between process performance and quality outcomes.

Balancing standardization with local optimization

Finally, ISO 22400 is explicit about its own limits: it standardizes definitions, not business strategy or improvement methods. Aerospace plants remain free to set their own OEE targets, to prioritize certain KPIs over others, and to implement local optimization practices aligned with their mix of programs and technologies.

The practical balance is to keep KPI definitions standardized (names, time and quantity concepts, state mappings) while allowing each plant to decide how aggressively to improve them. A propulsion test center and a structures assembly plant may share the same availability definition but choose different thresholds for what counts as acceptable performance. ISO 22400 supports that diversity by providing a common measurement language rather than enforcing a uniform scorecard.