MES versus ERP: draw the responsibility boundary
Decide whether MES adds useful execution capability beyond ERP. Assign record ownership and test orders, corrections and interface responsibilities.
Decide whether you need MES by identifying execution work your current ERP cannot perform adequately. Start with the order, material and quality decisions on the floor, then assign each record and transaction a system of record. Buying a second system does not resolve an ambiguous process.
Describe the gap without naming a product
Write the problem in observable terms. Operators may receive revisions too late, production counts may be entered only at shift end, or material substitutions may lack approval evidence. Each problem can have several possible remedies: process change, configuration of an existing application, a focused production app, or a broader MES.
Avoid defining the requirement as “install MES.” That fixes a solution before testing the need. Instead, state who needs to make which decision, when, and with which information. Ask the ERP team to demonstrate the existing capability using the same conditions proposed for the new system. Include exceptions rather than just the standard order flow.
Assign record ownership explicitly
| Object or event | Ownership question | Acceptance evidence |
|---|---|---|
| Production order | Where is it released and changed? | Controlled revision reaches the workstation |
| Material issue | Which system posts inventory? | Consumption reconciles without duplication |
| Work instruction | Where is the approved version held? | Correct revision shown for the operation |
| Quality hold | Who can block and release work? | Hold remains effective through exceptions |
| Completion | What counts as final and accepted? | Partial and corrected quantities reconcile |
The table is a discussion tool, not a prescribed architecture. The same plant may split responsibilities differently for different products. What matters is that ownership and the interface contract are unambiguous. Do not let two systems independently treat themselves as authoritative for the same transaction without a designed reconciliation rule.
Walk a difficult order across the boundary
Prepare a fictional production order with a revision change after release, a split lot, a rejected unit and a partial completion. Have the existing ERP workflow and the proposed execution workflow each handle it. Record operator actions, manual re-entry, delay, permissions and corrections. Use sanitized data and a test environment.
A useful result may be that ERP handles the workflow with modest configuration. Alternatively, the test may reveal a need for closer workstation guidance or more detailed event capture. Do not infer suitability from the presence of a module name. The evidence is whether the configured workflow meets the plant’s acceptance criteria with an operating burden the team can support.
Avoid duplicate masters and competing schedules
Identify who creates item codes, units of measure, resources, operations and routing revisions. Decide how changes are approved and propagated. If MES requires additional detail, such as a workstation instruction or a machine-specific parameter reference, document the relationship to the upstream object rather than copying an uncontrolled master.
Scheduling deserves similar care. A planning schedule and a local dispatch sequence can coexist, but the rules for order priority and rescheduling must be visible. Ask what happens when the upstream order is canceled after local work begins. A system boundary should prevent silent contradictions, not merely transfer more data. Name an owner for resolving those contradictions during operation.
Compare improvement paths fairly
Estimate the cost and limitations of process cleanup, ERP configuration, a focused app and a full MES against the same requirements. Include support, integrations, user training and future change. A focused app can be appropriate for one bounded workflow, but several independent apps can create fragmented identities and records if no one owns the architecture.
Use a decision matrix with mandatory requirements before weighted preferences. A candidate that cannot preserve a required quality hold should not win because it has a better dashboard. If no option passes, revise the scope or investigate the hard requirement. A numerical score cannot make an unproven production capability real.
Make the handoff operational
Before launch, assign responsibility for rejected orders, failed consumption postings, canceled work and inconsistent quantities. Define an exception queue with ownership, age and escalation. The plant should know who may correct data and how the change is recorded. Do not rely on an integration engineer manually editing records without a controlled procedure.
After go-live, reconcile a selected set of orders from release to final posting. Retain both successful and failed examples. Review whether the new boundary reduced the original problem or simply moved manual work to another team. That review should influence the next rollout decision and the budget for maintaining the interface.
Take this to the working meeting
Take one exception from the current process and ask the ERP owner and proposed MES owner to draw the resulting record changes independently. Compare the diagrams. Any record that both systems believe they own, or that neither owns, needs a specific decision. Use that decision to update the interface test and operating escalation path before treating the architecture as settled.
FAQ
Can ERP replace MES?
For some workflows it may be sufficient. Demonstrate the actual execution requirements rather than relying on a software category.
Should both systems own inventory?
Define authoritative transactions and reconciliation rules. Dual independent posting without a designed control creates ambiguity.
Is a separate MES always more capable?
Additional software can add capability and operating burden. Evaluate the configured workflow, interfaces and support model together.
Continue your decision
- MES cost: build a budget around the work
- Cloud, plant-hosted or hybrid MES?
- Write an MES RFP suppliers can actually price
- MES licensing: questions before signing
Use the pilot readiness to document your own inputs. Compare operating models on the comparison page.
Sources and scope
- NIST Smart Manufacturing — Official research context for manufacturing systems. The decision worksheets in this guide are editorial recommendations, not NIST requirements.
Examples are hypothetical and are not measured customer results, supplier quotations, or evidence of professional review. Prepared on October 30, 2026; confirm current requirements with the relevant official body and your responsible specialists.
