ERP, MOM, and MES are related boundaries, not interchangeable labels
ISA-95 places business planning and logistics at Level 4 and manufacturing operations management at Level 3. MES commonly supports Level 3 execution activities such as dispatch, data collection, traceability, and performance. ERP commonly supports Level 4 orders, planning, procurement, inventory, and finance. One product can span multiple levels, so architecture should assign process ownership, object authority, event direction, and reconciliation rather than insist on one product per label.
| Domain | Primary job | Typical objects | Time horizon | Boundary question |
|---|---|---|---|---|
| ERP, Level 4 | Business planning and logistics | Orders, items, supply, inventory, cost, finance | Days to months | What should be made or supplied, and with what business effect? |
| MOM, Level 3 | Manage manufacturing operations | Schedules, work, resources, quality, maintenance, performance | Shift to days | How will the operation execute and coordinate work? |
| MES, commonly Level 3 | Execute and record production | Dispatch, labor, material, genealogy, events, instructions | Seconds to shifts | What is happening to this order now? |
| Control, Levels 0 to 2 | Sense and control the process | Signals, states, setpoints, alarms | Milliseconds to minutes | What must the equipment measure or control? |
Use ISA-95 as an activity model, not a shopping list
ISA-95 provides a common way to discuss enterprise and control-system integration. Level 4 covers business planning and logistics. Level 3 covers manufacturing operations management. Levels 0 through 2 cover the physical process, sensing, monitoring, and control. The model helps teams find interfaces and responsibilities without dictating a vendor stack.
MOM includes activities across production, quality, inventory, and maintenance operations. MES is commonly used for the production-execution application within that space, although industry usage varies. A product may support several MOM activities or extend into ERP. Keep the activity and ownership clear even when the software boundary is broad.
MOM is not automatically another software purchase
A manufacturer may use one suite, several specialist applications, or a combination. The architecture decision is whether each activity, object, event, and exception has a clear owner and controlled source.
Define the Level 4 and Level 3 exchange
The downward flow usually includes production requirements and context: order, item, revision, quantity, due date, priority, routing, material, and relevant quality or work instructions. The upward flow includes actuals and exceptions: status, completion, consumption, labor, resource time, scrap, downtime, genealogy, inspection, and holds.
Each exchange needs an authoritative source, unique identity, timing rule, validation, duplicate control, error state, correction path, and reconciliation owner. When one suite spans ERP and MES, some technical interfaces may be reduced. The logical ownership still matters because the same person or process should not silently redefine controlled business and floor records.
- Assign who creates and changes every shared master-data object.
- Separate requested work from accepted and executable work.
- Define event time, posting time, and late-arriving behavior.
- Preserve rejected and corrected transactions for reconciliation.
- Make interface status visible to business owners, not only IT.
Compare integrated and composable patterns with the same scenarios
An integrated ERP and MES suite can reduce duplication and provide one transaction model. A composable architecture can preserve specialist capabilities or existing investments. Either pattern can fail if ownership is vague, identifiers differ, exceptions disappear between teams, or every report creates another private source of truth.
Evaluate both patterns with one end-to-end order and the same failure cases. Change a revision after release, delay material, report a partial quantity, place a lot on hold, lose a machine connection, correct scrap, and close the order. Record the number of transformations, queues, approvals, monitoring points, correction steps, and reconciliations.
| Decision factor | Integrated suite | Multiple specialist systems |
|---|---|---|
| Data model | Potentially fewer translations | Requires governed shared identities |
| Specialist depth | Verify required functions | Can retain focused capability |
| Change control | Coordinated release still required | Interface versioning adds work |
| Failure ownership | Can be operationally centralized | Must span vendor and system boundaries |
Evaluate DELMIAWorks against the ownership map
Dassault Systèmes describes DELMIAWorks as combining manufacturing ERP and MES in one shared database. That is a relevant architecture candidate when the requirement is to connect planning, production, quality, inventory, and financial transactions. It should be tested with the same Level 4 and Level 3 object and event map used for any alternative.
Confirm current functions, extensions, machine and system interfaces, site needs, security, validation, availability, recovery, and reporting for the intended release. ISA-95 does not prove fit. It provides a disciplined way to state what must be owned, exchanged, and reconciled.
Assign ownership before drawing the software boxes
The ownership map records the activity, ISA-95 domain, process owner, system of record, execution system, exchange, exception owner, and decision status.
Frequently asked questions
What is the difference between MES and MOM?
MOM is the Level 3 domain of manufacturing operations activities. MES is a software category commonly used to execute and document production activities within that domain. Usage varies, so define functions and ownership.
What is the difference between MES and ERP?
MES focuses on current manufacturing execution and production evidence. ERP coordinates wider business planning and transactions. They exchange released work, master data, status, consumption, completions, quality events, and cost inputs.
Does ISA-95 require separate ERP and MES products?
No. ISA-95 describes activities, levels, and interfaces. A single product can span levels, or several products can divide them. The organization still needs explicit ownership and controlled exchanges.
What should a manufacturing architecture map include?
Include each activity and object, its process owner, authoritative source, execution system, exchange direction and timing, validation, failure behavior, correction authority, and reconciliation owner.
References and method
- ISA-95 standard, enterprise-control integration levels and manufacturing operations context
- IBM: Manufacturing execution systems, general MES and ERP relationship
- Dassault Systèmes DELMIAWorks, current integrated ERP and MES architecture
- The tables, diagrams, selection questions, and downloadable register are Morphos 3D guidance. Verify product configuration, interfaces, validation requirements, and commercial packaging for the exact release and operating environment.
Assign the manufacturing architecture by activity and evidence
Map one order across planning, release, execution, quality, inventory, and close. Then compare architectures against the same owners and failure cases.