Usually no. An ERP system can sometimes cover basic shop-floor reporting for a small aerospace supplier, but it usually does not replace MES when the plant needs controlled execution, in-process inspection evidence, digital travelers, operator guidance, serialized or lot traceability, nonconformance capture, and auditable production records. The smaller the supplier, the more tempting it is to stretch ERP; the risk is that execution control becomes a mix of ERP screens, spreadsheets, paper travelers, and tribal knowledge.
What ERP can realistically cover
ERP is normally strongest at business and planning functions: customer orders, purchasing, inventory, MRP, costing, financials, shipping, and sometimes high-level production order tracking. Some ERP products include quality or shop-floor modules, and those may be enough for very simple operations if the supplier has low routing complexity, limited inspection requirements, stable processes, and disciplined manual controls.
That does not mean the ERP is acting as a complete MES. It may simply be recording status after the work is done. In regulated aerospace work, that distinction matters because late data entry is not the same as controlled execution at the point of work.
Where ERP usually falls short
MES is typically used to manage and prove what happened on the shop floor. For aerospace suppliers, the gaps often appear around:
- step-by-step routing execution and operation signoff;
- revision-controlled work instructions at the point of use;
- in-process inspection capture and acceptance evidence;
- tooling, equipment, operator qualification, and certification checks;
- serialized, lot, and batch traceability;
- nonconformance and rework workflows tied to the production record;
- electronic audit trails and controlled record changes;
- integration with PLM, QMS, inspection systems, machines, or customer portals.
If those controls are required by customer contracts, internal quality procedures, AS9100-based processes, AS9102 first article workflows, or program-specific requirements, replacing MES with ERP alone is usually a poor fit unless the ERP module has been specifically configured, validated, and governed for those execution use cases.
When ERP may be enough
ERP may be sufficient for a small supplier when the work is low complexity, paper records are well controlled, inspection is limited, traceability requirements are modest, and the organization can demonstrate that manual procedures are followed consistently. This depends on the supplier’s quality system, customer requirements, product risk, special process exposure, and record retention obligations.
Even then, the supplier should be clear about the control model. If the ERP only stores final quantities and completion dates, the real execution system may still be paper, spreadsheets, or informal supervisor control. That can work in some environments, but it needs ownership, training, document control, and audit discipline.
The common brownfield answer is coexistence
For many aerospace suppliers, the practical answer is not ERP versus MES. It is ERP plus a focused MES or digital traveler layer. ERP remains the system of record for orders, inventory, planning, and costing. MES manages execution records, operator guidance, inspection capture, and traceability. PLM and QMS may still own engineering definitions, document control, corrective actions, and formal quality workflows.
Full replacement is often unrealistic in brownfield aerospace environments. Qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long equipment lifecycles make large system swaps difficult to justify and difficult to execute safely.
The main failure mode
The most common failure mode is forcing ERP to behave like MES through customization. That can create brittle workflows, expensive upgrades, weak usability at the point of work, inconsistent audit trails, and integration debt. It can also push operators back to paper or spreadsheets because the ERP transaction model does not match how production actually runs.
A better decision starts with required evidence, not software categories. Define what records must be created, when they must be created, who must approve them, what revision must be shown to the operator, what data must be traceable, and which systems must exchange controlled information. Then decide whether ERP alone can support that model without excessive customization or manual compensating controls.