In aerospace environments, ERP typically owns inventory at the enterprise level, while MES owns inventory at the shop-floor execution level. ERP focuses on stocked items, planning, costing, and financial valuation, whereas MES focuses on what is actually at the work center, in WIP, and consumed in build. Both may maintain quantities and locations, but they operate at different abstraction layers and time scales. Confusion usually arises when plants expect either MES or ERP to fully replace the other for inventory, which rarely works without gaps in traceability or reconciliations.
ERP inventory management is typically the system of record for part numbers, stock levels, warehouse locations, and financial valuation. It supports MRP/APS planning, purchase orders, goods receipt, stock movements, and sometimes high-level shelf-life and batch/lot controls. In aerospace, ERP is often the reference for regulatory-relevant information such as approved sources, revision levels, and inspection status, but only at a coarse granularity. ERP generally does not track exact point-of-use, per-serial consumption, or detailed routing steps on the shop floor. Its primary orientation is towards planning, finance, and commercial commitments, not minute-by-minute production reality.
MES inventory management focuses on WIP and point-of-use material at stations, cells, and lines. It typically manages which serials, lots, or kits were used on which specific unit, at which operation, and under which conditions. For aerospace, MES is often where you enforce and record the use of the correct revision, configuration, and lot against a particular serialized assembly. MES may also manage local material staging, kitting, and backflushing based on work instruction execution. However, MES is usually not the authoritative source for enterprise stock levels, financial value, or global replenishment logic, even if it has detailed consumption records.
For aerospace, the critical difference is usually traceability depth: MES is optimized for proving what went into each serial number; ERP is optimized for proving what is on hand and what it cost. MES better supports one-to-one and one-to-many links between component serials and finished-assembly serials, including process parameters and operator actions. ERP can track batch/lot and sometimes serial, but typically not with full process context or per-operation detail. Regulators and customers usually expect alignment between ERP and MES records, not that one system alone provides the entire trace. Achieving that alignment requires disciplined master data, interface design, and change control, not just technology selection.
In a brownfield aerospace plant, MES and ERP inventory rarely match perfectly in real time, and attempting strict real-time mirroring can introduce fragility. Common patterns include ERP sending planned orders, BOMs, and stock availability to MES, and MES sending back confirmations of material consumed, scrap, and completions. Interfaces must be designed to handle communication failures, partial updates, and rework loops without losing traceability or double-counting inventory. Reconciliation procedures—daily or batch comparisons, exception reports, and manual investigations—are often necessary and must be formalized and validated. Without this, audit findings frequently center on mismatched quantities, unclear ownership of corrections, or undocumented workarounds at the shop floor.
Trying to run all inventory purely in ERP and treating MES as a “thin” work instruction viewer usually fails to meet aerospace traceability and configuration control needs. Operators end up creating local tracking tools to capture point-of-use and serial-level detail that ERP cannot handle gracefully, which increases validation and audit risk. Conversely, pushing all inventory logic into MES and relegating ERP to a minimal role can break planning, financial, and supply-chain processes that rely on ERP’s model. Full replacement also drives a high validation burden, complex data migrations, and long downtimes that are rarely acceptable for qualified aerospace lines. A more robust strategy is to define clear functional boundaries, explicit system-of-record ownership for each inventory attribute, and controlled interfaces between them.
In practice, aerospace organizations benefit from explicitly deciding where key responsibilities sit: stock valuation, replenishment logic, and procurement typically sit in ERP, while point-of-use control, WIP visibility, and per-serial consumption typically sit in MES. Shelf-life and environmental storage constraints may be modeled in both systems, but you must choose which system is authoritative and how updates propagate. Similarly, approved manufacturer and supplier controls might reside primarily in ERP, while MES enforces their use at the station level via allowed-lot lists. These boundaries should be documented in your system architecture, URS/FRS, and validation artifacts, not left to tribal knowledge. Over time, changes to these boundaries must go through formal change control to avoid gradual divergence between actual practice and validated design.
Most aerospace plants run legacy ERP and MES solutions alongside bespoke tools, and wholesale replacement of either system solely to “unify inventory” often backfires. The qualification effort, cutover risk, and integration debt tend to be underestimated, especially when dozens of external systems depend on existing ERP interfaces. Instead, many organizations gradually tighten the MES–ERP integration, clean up master data, and standardize inventory-related processes while leaving core platforms in place. Improvements such as clearer WIP definition, better serial–lot linking, and controlled backflush rules often yield more benefit than a large replatforming. The key is to treat MES and ERP as complementary inventory stakeholders, with explicit, validated contracts between them, rather than expecting one system to do everything.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
