In aerospace manufacturing, ERP usually belongs at the enterprise planning and commercial control layer: demand, order management, procurement, MRP, inventory balances, costing, supplier transactions, production orders, and financial records. It should not be assumed to own every manufacturing detail. Detailed execution, operator guidance, inspection evidence, nonconformance workflows, and product definition often belong in MES, QMS, PLM, or specialized quality systems, depending on the site’s validated architecture.
The practical rule is simple: ERP should control what the business must plan, buy, value, schedule at a high level, ship, invoice, and reconcile. It should integrate with, not replace, the systems that control how work is executed and proven on the shop floor.
Common ERP responsibilities
In many aerospace environments, ERP is the system of record for:
- Customer demand, sales orders, contracts, and delivery commitments.
- Material requirements planning, purchasing, purchase orders, and supplier transactions.
- Inventory balances, lot or serial references, warehouse movements, and inventory valuation.
- Production orders, work orders, or jobs at a planning and control level.
- Standard cost, actual cost capture, labor or overhead costing models, and financial reconciliation.
- Shipping, receiving, invoicing, and commercial traceability.
- Approved suppliers, purchasing controls, and basic supplier performance data where configured.
Some ERP systems also hold routings, operations, inspection plans, quality holds, and nonconformance records. That can be valid, but only if the configuration, data governance, validation, and shop-floor usability support it. In many brownfield plants, those functions are split across ERP, MES, QMS, PLM, and legacy databases.
What usually should not live only in ERP
ERP is often a poor fit as the sole system for detailed shop-floor execution. Aerospace production needs controlled instructions, operation-level data capture, equipment context, operator signoffs, inspection results, rework history, and traceability that may be too granular or too time-sensitive for ERP alone.
These areas commonly belong outside ERP or require tightly governed integration:
- Engineering product definition: CAD, drawings, engineering BOMs, specifications, and design changes usually belong in PLM or document control systems.
- Digital work instructions: Operator-facing instructions, visual aids, revisions, and training links usually belong in MES, work instruction platforms, or controlled document systems.
- Execution records: Operation completions, electronic travelers, tool use, machine data, and as-built history are often better handled in MES.
- Quality execution: Inspection evidence, AS9102 FAI packages, NCRs, MRB disposition, CAPA, and audit records may sit in QMS, MES, or specialized systems rather than ERP alone.
- Detailed genealogy: Lot, serial, component, process, and material traceability may be referenced in ERP but often requires MES or traceability systems for full operation-level context.
The boundary is site-specific
There is no universal ERP boundary in aerospace. Some plants run more quality and routing control inside ERP. Others use ERP mainly for planning, purchasing, inventory, and finance while MES and QMS manage execution and evidence. The right boundary depends on product complexity, customer flowdowns, regulatory expectations, validation requirements, integration maturity, and the age of existing systems.
Master data ownership is usually the hardest part. Item masters, part revisions, approved manufacturers, units of measure, routings, work centers, alternates, effectivity, and serialization rules must be governed across ERP, PLM, MES, and QMS. If ownership is unclear, the result is duplicate records, mismatched revisions, manual reconciliation, and weak audit evidence.
Brownfield reality
Full ERP replacement is often unrealistic in aerospace-grade environments. The qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles can make replacement slower and riskier than expected. Many sites instead stabilize ERP as the planning and financial backbone, then add or modernize execution, quality, and integration layers around it.
That approach still requires discipline. Interfaces must be controlled. Data mappings must be documented. Changes to ERP, MES, PLM, or QMS must go through change control. Transaction timing matters: an inventory issue, operation completion, inspection hold, or nonconformance disposition in one system can create planning or shipment errors if the integration is late, incomplete, or manually bypassed.
Practical test
A function probably belongs in ERP if finance, procurement, inventory control, or enterprise planning needs it as the governed record. A function probably belongs in MES, QMS, PLM, or document control if it defines the product, guides the operator, proves how work was performed, records inspection evidence, or controls quality disposition at the point of execution.
The safest answer is not to force everything into ERP. Define system ownership by process, record type, revision control need, validation burden, and audit evidence requirements. Then integrate deliberately and test the failure modes before relying on the data for production, quality, or customer reporting.