ERP fits into AS9100 primarily as the transactional and financial backbone that underpins quality and traceability, not as the sole system that fulfills all AS9100 requirements. In most aerospace environments, AS9100-compliant quality and traceability are delivered by a combination of ERP, MES, PLM, QMS, and controlled documents, with integration and governance being the deciding factors.
What ERP usually owns in an AS9100 environment
Typical AS9100-relevant responsibilities for ERP include:
- Customer, contract, and order data
Links between customers, contracts, sales orders, and the production orders that must be traceable to specific requirements and revisions.
- Item masters and BOMs (when not fully in PLM)
Part numbers, basic specifications, planning BOMs, and configuration rules that drive work orders and purchase orders.
- Work orders and routing headers
Creation and release of production orders, operation sequences, planned resources, and due dates that other systems use for execution control.
- Purchasing and supplier records
Approved supplier lists (sometimes shared with QMS), purchase orders, supplier performance data, and receiving transactions, all of which are inputs to supplier traceability.
- Inventory and lot/batch tracking
On-hand balances, location, lot/heat/batch IDs, certificates of conformance (often referenced, sometimes attached), and movement history between locations.
- Costing and financial impact of quality events
Standard and actual costs, scrap postings, and rework transactions that link financial consequences to quality and nonconformance data held elsewhere.
These functions are critical to AS9100, but they do not, by themselves, deliver complete, audit-ready traceability or process evidence. They need to be combined with controlled work instructions, inspection records, nonconformance workflows, and calibration/maintenance data, which often live outside ERP.
Where ERP usually is not sufficient for AS9100
Most aerospace ERPs were not designed as full manufacturing execution or quality systems. Common AS9100 needs that are only partially covered by ERP include:
- Detailed process and operation traceability
Operator sign-offs, actual machine, tool, or fixture used, special process parameters, and inspection results at each operation are typically handled by MES, LIMS, SPC, or point solutions, not by ERP.
- Nonconformance, MRB, and CAPA workflows
ERP may capture scrap or rework codes, but structured NCR, MRB decisions, root cause, containment, and CAPA workflows usually sit in a QMS or specialized NCR system for AS9100 compliance.
- Document and revision control
AS9100 requires robust control of drawings, specifications, and work instructions. These are usually managed via PLM, DMS, or QMS. ERP typically references revision levels but does not control content, distribution, or training records.
- FAI / AS9102 evidence
ERP may store a flag or reference indicating that FAI is required or completed, but the ballooned drawing, characteristic-level results, and FAIR package are almost always managed outside ERP.
- Gage management and calibration
Tooling and gage calibration schedules and histories are generally handled in metrology or asset systems, linked only loosely to ERP item and operation data.
- Detailed as-built genealogy
Many ERPs can model serial and lot tracking, but part-to-part genealogy (which specific serials and lots came together in each assembly and rework event) often needs MES or a specialized genealogy solution to be audit-ready.
Trying to force all of these into ERP alone typically results in heavy customization, validation risk, brittle integrations, and long-term upgrade constraints, especially in regulated and ITAR-constrained environments.
How ERP supports AS9100 quality and traceability in practice
In real AS9100-certified plants, ERP usually plays three key supporting roles:
- Authoritative source of core transactional data
ERP is the system of record for items, customers, suppliers, contracts, and inventory balances. Other systems reference ERP IDs and data to maintain consistency and traceability.
- Linking commercial and operational traceability
AS9100 expects you to trace from customer requirement to delivered product. ERP provides the chain from customer order and contract, through internal work orders and purchase orders, to shipment. MES, PLM, and QMS record what actually happened during production and inspection; ERP ties that to who ordered and received it.
- Financial and planning context for quality data
ERP captures the cost impact of scrap, rework, and yield loss. When integrated with QMS and MES, this enables evidence-based decisions in MRB and continuous improvement, but only if mappings between systems are clean and consistently governed.
From an AS9100 perspective, auditors typically want to see that ERP data is:
- Accurate and consistent with what MES, PLM, and QMS show.
- Under change control, with appropriate access, approvals, and audit trails.
- Clearly linked to procedures, work instructions, and quality records.
Integration patterns between ERP and execution/quality systems
In brownfield aerospace environments, ERP almost always coexists with other systems. Common patterns are:
- ERP + MES
ERP creates work orders and high-level routings. MES manages operation-level execution, labor reporting, in-process inspections, special processes, and detailed as-built genealogy. Completion and scrap feed back to ERP for inventory and costing.
- ERP + PLM / PDM
PLM controls the engineering BOM, CAD, drawings, and change process. ERP receives a released manufacturing BOM and revision references. Traceability relies on consistent part numbers, revisions, and change notices across systems.
- ERP + QMS
QMS manages nonconformances, CAPA, audits, document control, and training records. ERP may provide transaction context (e.g., which lot and work order were involved), and may hold summary status flags or cost impact.
- ERP + supplier portals / collaboration tools
ERP is the system of record for POs, receipts, and invoices. Supplier collaboration tools handle flowdown of requirements, digital certificates, and NCR workflows, feeding status back to ERP.
The key AS9100 issue is not which system “owns” a function, but whether:
- Interfaces and data mappings are documented and validated.
- There is a clear definition of the system of record for each data type.
- Users know where to find the evidence an auditor will request.
- Changes to integration are controlled, tested, and traceable.
Why full replacement by ERP often fails for AS9100 needs
Many organizations attempt to consolidate MES, QMS, and PLM capabilities into ERP to simplify the landscape. In AS9100 and long-lifecycle aerospace environments, this often fails or stalls because:
- Qualification and validation burden
Deep customizations or new ERP modules that affect quality records or traceability require rigorous validation, documentation, and sometimes customer or regulatory review.
- Downtime and cutover risk
Replacing established MES/QMS capabilities with ERP during a short outage window is high-risk, especially when customer programs cannot tolerate extended downtime.
- Integration and change-control complexity
ERP is typically integrated with finance, MRP, and external partners. Rewiring quality and execution inside ERP tends to create ripple effects across many interfaces and procedures.
- Long equipment and program lifecycles
Plants may need to maintain traceability for decades. Frequent ERP upgrades or vendor changes become problematic if critical execution and quality records are deeply embedded and heavily customized inside ERP.
Because of these realities, many AS9100-compliant organizations pursue an approach where ERP stays focused on planning, inventory, and financials, while MES/PLM/QMS handle detailed execution, documentation, and quality. The integration is then incrementally strengthened and validated rather than rebuilt in one step.
What to document for AS9100 using ERP data
To use ERP effectively in your AS9100 evidence set, it helps to explicitly document:
- Which AS9100 clauses are supported by ERP data, and which are supported by other systems.
- The defined system of record for part numbers, BOMs, routings, suppliers, and quality records.
- How work orders and purchase orders created in ERP link to FAI, inspection, and NCR data elsewhere.
- How changes to ERP master data are controlled, approved, and audited.
- How you demonstrate consistency between ERP and downstream systems during audits.
This mapping is usually more important than the specific technology choices, as long as roles and interfaces are clear, validated, and maintained under change control.
