In an aerospace manufacturing environment, ERP and MES solve different parts of the problem and need to coexist. ERP is primarily a planning, commercial, and financial backbone. MES is an execution and traceability backbone on the shop floor. Trying to collapse both into one system usually runs into limits around compliance, validation, and day-to-day usability for operators.
What ERP typically owns in aerospace
ERP systems in aerospace are usually the system of record for:
- Customer and contract data: sales orders, contracts, pricing, offsets, long-term agreements.
- Planning and MRP: demand plans, MPS/MRP runs, purchase orders, planned work orders.
- Inventory and costing: financial inventory, standard costs, variances, WIP valuation, project accounting.
- Procurement and vendors: purchase orders, receipts, payables, approved vendor lists (often with QMS input).
- Financials and compliance reporting: GL, project-level P&L, revenue recognition, billing, audit trails for financial regulations.
ERP is optimized for cross-functional planning, financial accuracy, and commercial control, not for second-by-second shop-floor interaction.
What MES typically owns in aerospace
MES systems in aerospace are usually the system of record for how work is actually executed and proven compliant:
- Work execution control: dispatching operations, enforcing routings, controlling queues and priorities by work center or cell.
- Digital travelers and work instructions: operator-facing steps, linked specs and models, revision-controlled instructions, required sign-offs.
- Data collection and as-built records: in-process data, measurement results, torque values, serialization, component usage, lot/heat numbers.
- Traceability and genealogy: which components and lots went into which assembly, by serial number, with who/when/where data.
- Nonconformance and rework execution: routing holds, defect capture on the line, rework instructions, repair and concession execution (often linked to QMS).
- Real-time visibility: WIP status, resource loading, takt vs actual, bottlenecks, downtime and delay categories.
MES is optimized for operators, supervisors, and manufacturing engineering: enforcing process, capturing evidence, and generating an auditable as-built record.
Why the distinction matters more in aerospace
Aerospace programs add constraints that make the ERP/MES split more critical than in some other industries:
- High-mix/low-volume and engineering change churn: frequent engineering changes, model options, and customer-specific variants are difficult to manage at operator level in ERP screens.
- Deep traceability: AS9100, AS9102, export controls, and customer requirements often demand part-level and process-level evidence MES is better suited to capture.
- Qualification and validation burden: putting complex shop-floor workflows into ERP can massively expand the scope and risk of ERP changes and validation.
- Operator usability and training: ERP UIs are rarely optimized for line operators; forcing them into ERP screens drives workarounds and erodes data quality.
- Long lifecycle and retrofit constraints: many aerospace plants must integrate with legacy machines and systems; MES can bridge OT and IT without re-architecting core ERP or revalidating everything.
Typical division of responsibilities
In a brownfield aerospace environment, a pragmatic split often looks like:
- ERP
- Defines part master, BOM, and high-level routing (often aligned with PLM).
- Creates work orders and purchase orders.
- Performs MRP and capacity planning at an aggregate level.
- Maintains financial inventory and WIP valuation.
- MES
- Consumes work orders and routings from ERP.
- Expands routing into detailed operation steps and checks, tied to engineering data and instructions.
- Controls execution: start/complete operations, holds, rework routing, inspections.
- Captures operator actions, measurements, and material usage, including serial/lot traceability.
- Feeds back operation completions, scrap, and consumption to ERP.
The boundary is not identical at every plant and depends on how PLM, QMS, and other systems are deployed, but this division is a common pattern.
Integration and coexistence realities
In most aerospace operations, neither ERP nor MES is greenfield. You will typically have an established ERP, legacy applications, and partial digital processes. This means:
- Replacement strategies are risky: ripping out ERP to get better execution, or ignoring MES and forcing everything into ERP, usually fails due to downtime risk, requalification costs, and integration complexity.
- Data models must align: part numbers, revisions, routing steps, and work-center definitions need clear mapping and governance. Poor alignment causes duplicate records, booking errors, and reconciliation problems.
- Interfaces need validation: integrations that move work orders, completions, and inventory movements must be version-controlled, tested, and change-controlled like any core system in a regulated environment.
- Traceability often spans multiple systems: true genealogy commonly pulls from PLM (design intent), ERP (orders and inventory), MES (as-built), and QMS (NCRs and CAPA). No single system holds everything.
Common failure modes when the roles blur
Issues tend to arise when the distinction between ERP and MES is ignored:
- Trying to make ERP the MES
- Operators bypass complex ERP screens with paper or spreadsheets.
- Real as-built and inspection data stays offline, weakening audit readiness.
- Engineering changes are not reflected reliably at the point of use.
- MES acting as a planning system
- Conflicting routings and BOMs between MES and ERP.
- MRP and capacity planning in ERP see distorted demand and WIP status.
- Financial inventory and WIP balances become hard to reconcile.
- Unclear system-of-record decisions
- Multiple “truths” for part structures, work instructions, and revisions.
- Audit challenges when evidence is scattered and inconsistent.
- Change-control processes spanning systems without clear ownership.
How to decide what belongs where
A practical way to draw the line in an aerospace context:
- If the function is financial, commercial, or high-level planning, it generally belongs in ERP.
- If the function is operator-facing, real-time, or evidence-generating on the line, it generally belongs in MES.
- If the function is product definition or design authority (models, drawings, technical specs), it generally belongs in PLM, with both ERP and MES consuming controlled views.
- If the function is quality system governance (CAPA, audits, document control), it is usually QMS, with execution hooks in MES and some references in ERP.
The exact split depends on your existing stack, integration maturity, and how much revalidation you can absorb. What is consistent across most aerospace programs is that ERP and MES are complementary, not interchangeable, and both must be managed under robust change control.
