MES manages execution between business planning and plant control
A manufacturing execution system manages and records production activity after work is released to the floor. It can dispatch work, identify material and resources, collect labor and machine events, enforce quality steps, track genealogy, and return completion, consumption, scrap, downtime, and status to business systems. The exact boundary varies, so define the transaction and event handoffs instead of assuming every MES has the same scope.
| Stage | MES responsibility | Required context | Return evidence |
|---|---|---|---|
| Release | Accept executable work | Order, revision, routing, quantity, priority | Accepted or rejected release |
| Dispatch | Present authorized work | Resource, labor, material, tooling, status | Start, hold, queue, assignment |
| Execute | Record production events | Instructions, limits, reason codes | Count, time, consumption, downtime |
| Verify | Capture quality and traceability | Plan, characteristic, lot or serial rules | Inspection, genealogy, disposition |
| Close | Reconcile completed work | Completion and accounting rules | Yield, scrap, status, cost inputs |
Define the MES boundary with orders and events
Start with a single production order. Identify where it is created, when it becomes executable, which revision and routing apply, what material is authorized, which resource can run it, and who can change priority. The release message needs enough context for the floor to act without rebuilding the plan in a spreadsheet.
Now trace the return path. A start, stop, partial completion, scrap event, material issue, inspection result, downtime code, and completed quantity each affect a different downstream decision. State which system records the event first, which system is authoritative, how duplicates are prevented, and who reconciles a failure.
- Name the authoritative source for orders, items, revisions, routings, people, resources, and quality plans.
- Define release, hold, cancel, change, and close behavior.
- Preserve event time, source, quantity, unit, reason, order, operation, and resource.
- Specify correction authority and retain the original and corrected evidence.
Separate MES functions from narrow machine monitoring
Machine monitoring can collect states, counts, alarms, or process values. Those signals become manufacturing evidence only after they are associated with the correct order, operation, resource, material, person, and reason. A counter that says a machine made 500 cycles does not establish which revision ran, whether parts were accepted, or how material genealogy should be recorded.
A broader MES coordinates the work around those signals. Depending on scope, that can include dispatch, instructions, labor, material movement, quality, genealogy, electronic records, maintenance coordination, and performance analysis. Do not buy a category name. Test the functions required by the operating process and the events needed by planning, quality, inventory, and cost.
Machine connectivity is a boundary, not a checkbox
Controllers, protocols, gateways, cycle logic, network conditions, buffering, and manual fallback vary by asset. Confirm the exact connection and failure behavior for representative machines before treating a signal as reliable production evidence.
Test normal work, corrections, and outages
A useful demonstration starts with released work and ends with reconciled records. Run a normal order, partial quantity, setup, material substitution, scrap with a reason, an inspection hold, rework, downtime, shift change, and completion. Confirm what each role sees and which transactions update inventory, planning, quality, and cost.
Then disconnect a device or interface. Enter an invalid reason, duplicate an event, delay an order change, and correct a quantity after downstream activity has begun. The system should fail visibly, preserve evidence, support an authorized correction, and let an owner prove that both sides agree.
| Selection question | Evidence |
|---|---|
| Can the floor identify the right work? | Order, revision, status, resource, authorization |
| Can an event be traced? | Source, timestamp, operation, quantity, reason |
| Can errors be corrected safely? | Role, audit history, downstream reconciliation |
| Can work continue during an outage? | Buffer, manual fallback, replay, duplicate control |
Use MES when the execution gap is broader than data collection
A full MES may be excessive when the problem is only a narrow counter or downtime capture requirement. It becomes more relevant when several departments need the same current production state, when traceability crosses material and process events, or when uncontrolled floor workarounds are weakening schedule, inventory, quality, and cost records.
Dassault Systèmes describes DELMIAWorks as blending manufacturing ERP and MES in one shared database. That can reduce some interface boundaries, but it does not remove transaction design. Roles, event definitions, machine connections, quality rules, corrections, and reconciliation still need to be proven in the intended environment.
Trace the handoff before evaluating MES features
Use the handoff map to record each order, master-data object, floor event, authoritative source, receiving role, failure evidence, and reconciliation owner.
Frequently asked questions
What does MES stand for in manufacturing?
MES stands for manufacturing execution system. It manages and records production activity between business planning and plant-floor control.
What is the difference between ERP and MES?
ERP coordinates business planning and transactions across functions. MES focuses on executing, observing, and documenting production. The systems exchange orders, master data, status, consumption, completions, quality events, and other actuals.
Is machine monitoring the same as MES?
No. Machine monitoring captures selected machine states or signals. MES connects production work, people, material, resources, quality, instructions, and events into a controlled execution record.
What should an MES evaluation test?
Test release, dispatch, normal production, partial completion, scrap, downtime, quality hold, rework, correction, interface failure, device outage, replay, and reconciliation with connected business records.
References and method
- ISA-95 standard, Level 3 manufacturing operations and Level 4 business-planning interface context
- IBM: Manufacturing execution systems, general MES definition and ERP relationship
- Dassault Systèmes DELMIAWorks, current vendor architecture
- DELMIAWorks MES data sheet, vendor-documented MES function set; current configuration requires verification
- 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.
Trace one production order before comparing MES options
Map the release, floor events, corrections, and return transactions. The missing owners and evidence will define the real MES requirement.