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.

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.