What a Manufacturing Execution System (MES) Actually Does — and When You Need One

A manufacturing execution system (MES) is the software layer that manages and records production as it happens on the shop floor. It takes released work from planning and business systems, dispatches it to people and machines, captures what was actually made, used, scrapped and checked, and keeps a traceable record that links materials, operations and finished output.

The practical problem for most small and mid-sized manufacturers is not a lack of software. It is the gap between the plan in the ERP, MRP or accounts system and what is happening on the floor right now. That gap is usually filled by paper travellers, whiteboards and the memory of one or two people, which makes late jobs, missing bookings and slow batch queries hard to see until a customer asks.

An MES records what happens at each operation, while the work is being done. Illustrative photograph, not an OpsMavix project.

Image credit: Cemrecan Yurtman, Unsplash License. No edits.

Key Takeaways

• An MES manages and records production execution between business planning and machine control.
• ISA-95 places MES at Level 3, below the business systems at Level 4 and above control systems.
• ERP runs the business, MRP calculates material and production requirements, and MES executes and records the work.
• Core MES capabilities include dispatching, data collection, tracking, genealogy, quality records and performance reporting.
• Many small manufacturers need a few MES capabilities long before they need a full MES platform.
• Compare configuration, integration, packaged MES, a focused application and full ERP against one shared scenario.

In this guide:

• 1. Understand What an MES Is
• 2. Place MES in the ISA-95 Levels
• 3. Know the Core MES Functions
• 4. Compare MES vs ERP vs MRP
• 5. Follow One Works Order Through an MES
• 6. Recognise When a Small Manufacturer Needs MES Capability
• 7. Compare the Available System Approaches
• 8. Pilot One Product Line Before Wider Rollout
• Frequently Asked Questions
• How OpsMavix Can Help

1. Understand What an MES Is

A plain definition

An MES is the system of record for how production was executed. Business systems know that an order exists, what it should contain and when it is due. Machines and operators make the product. The MES sits between them: it presents the right work to the right station, records each step as it happens and sends the results back to the systems that need them.

The record it produces answers questions such as:

• Which operation is each works order at right now, and what is queued behind it?
• Which material lots, operators and machines were involved in this batch?
• How many good and scrapped units came out of each operation?
• Which quality checks were completed, by whom and with what result?
• How long did each step take compared with its standard?

What an MES is not

An MES is not the same as a scheduling tool, a machine monitoring dashboard or an accounting package, although it may include or connect to all three. It also does not decide on its own what the business should make next month. That belongs to planning. A useful test is time scale: business planning tends to work in days, weeks and months, while execution works in shifts, hours and minutes.

2. Place MES in the ISA-95 Levels

The model behind the term

The most widely used reference for where MES sits is ISA-95, published by the International Society of Automation. ISA describes it as ISA-95, Enterprise-Control System Integration, also known as ANSI/ISA-95 or IEC 62264, created to provide an abstract model for information exchange between manufacturing control functions and business functions.

ISA’s page summarises the five levels as follows:

ISA notes that the standard primarily deals with the interface between Levels 3 and 4: the exchange between the plant and the business.

Manufacturing operations management

You will also see the term MOM, manufacturing operations management. In an InTech article on the standard, ISA’s standards vice president explains that ISA-95 Parts 3 and 4 formally defined the Level 3 space and created that term. The published scope of Part 3 describes activity models of manufacturing operations management that operate between business planning and logistics functions and Level 2 process control.

For a small manufacturer, the practical lesson is simple. Level 3 is a set of activities, not a single product. You can cover some of them in an ERP module, some in a focused application and some on paper, as long as the handoffs to Level 4 are clear.

3. Know the Core MES Functions

The capabilities buyers usually mean

Different vendors package MES differently, so compare capabilities rather than product names.

How these relate to other OpsMavix guides

Several of these capabilities are covered in depth elsewhere. A production monitoring system concentrates on the live state of machines and jobs. Shop floor WIP tracking covers the quantity and value sitting at each operation. OEE monitoring covers the performance measure. This guide stays with the definition: what the whole execution layer is and when it is worth having.

Traceability is sometimes a legal requirement

For some sectors, traceability is not optional. For food and feed, Article 18 of Regulation (EC) No 178/2002 as published on legislation.gov.uk requires business operators to have systems and procedures to identify who supplied them and which businesses their products were supplied to, and to make that information available to the competent authorities on demand. Customer contracts in other sectors may impose their own requirements. Confirm what applies to your products before deciding how much genealogy you need to record.

4. Compare MES vs ERP vs MRP

Three systems, three questions

The terms overlap in sales material, so define them by the question each one answers.

MRP is often a module inside an ERP. For the planning side, see whether you need an MRP system. Many ERP and MRP products also include some execution features, such as works order bookings or shop floor terminals. Check exactly which ones before assuming you need a separate MES.

Where the handoffs happen

Most of the rework in small manufacturers happens at these handoffs, where the same fact is typed into two systems or held on paper until someone copies it.

5. Follow One Works Order Through an MES

An MES follows each order through the operations on the floor and records what happened at each one. Illustrative photograph, not an OpsMavix project.

Image credit: Yetkin Ağaç, Pexels License. No edits.

The execution sequence

1. Planning releases a works order for a quantity, with its routing and BOM revision.
2. The MES places the order in the queue for the first operation.
3. Stores issues material and the lot number is scanned against the order.
4. Each operator starts the operation, completes good units and records scrap with a reason.
5. Inspection records results and either releases or holds the quantity.
6. The final completion moves good units into stock and returns actual material, scrap and time to the business system.

Hypothetical worked example: status queries and recall scope

The following figures are hypothetical and illustrative, not from a client.

A 35-person fabrication shop runs about 60 open works orders. Without a shared execution record, the office and sales team ask the floor for job status about 20 times a day, and each query takes about 6 minutes to answer by walking the floor or phoning a supervisor.

Now consider a supplier warning about one steel lot. Without genealogy, the shop cannot tell which orders used it, so it quarantines every bracket made in the two weeks the lot was in stores: 2,400 units. With lot numbers scanned at material issue, it finds that the lot went into 3 orders of 120, 150 and 90 units.

The 360 units are 360 / 2,400 = 15% of the period’s output. The example assumes every booking was made; a missed lot scan would put the shop back to quarantining everything. Before pricing any system, run the same sums with your own query volume, order sizes and material lots.

6. Recognise When a Small Manufacturer Needs MES Capability

Signs the execution layer is missing

Symptoms are not the same as needing a full platform

A full MES platform makes sense when many of these symptoms are present at once, across several lines or sites, with machine integration and formal quality requirements. A smaller manufacturer may have only two or three of them. In that case, the right answer may be to configure the existing ERP, add station terminals or build a focused application for the specific gap.

Questions to answer before choosing

1. Which three decisions would improve most if the floor position were live?
2. Which records must be traceable, for whom and how quickly?
3. Who will make bookings, on which devices, and how long can each one take?
4. Which system owns the order, the stock and the cost, and which one owns the booking?
5. What must keep working if the network drops?
6. Which machines, if any, need a direct signal rather than an operator entry?

7. Compare the Available System Approaches

Match the approach to a demonstrated gap

Packaged MES products can provide well tested capabilities, machine connectors and reporting, and suit plants whose processes match their model. A focused application can fit an unusual routing or a narrow gap closely, but it still needs ongoing ownership and support. Neither is automatically cheaper or more flexible over its life. For a comparison of named packaged options, see manufacturing operations management software; for an open-source route, see the OpenMES alternative guide.

Compare on one shared scenario

Ask every option to demonstrate the same works order: release from planning, a material lot scanned at issue, a split batch at one operation, two rejects at inspection, a quality hold and release, final completion into stock and a backward trace from the finished batch to its material lot. Mark each step as demonstrated, configurable, needing development or unsupported. Include licences or hosting, terminals, implementation, training, support and future changes in the cost comparison.

8. Pilot One Product Line Before Wider Rollout

Choose a representative pilot

Pick one product family that includes at least one split batch, one inspection step and one material that must be traced. Count what is actually on the floor and load that as the opening position rather than importing an old spreadsheet unchecked.

Practical acceptance checklist

1. Released orders reach the first operation with the correct routing and BOM revision.
2. Operators can book start, complete, scrap and hold at the station in a few seconds.
3. Material lots are linked to orders at issue.
4. Quantities balance at each operation: good in equals good out plus scrap plus still on hand.
5. Inspection results and holds are visible against the order.
6. Completions reach stock and the business system without retyping.
7. A backward trace from finished batch to material lot takes minutes, not hours.
8. Failed interfaces are visible, owned and corrected.
9. Corrections keep the original booking and show who changed it.
10. The office can answer status questions without asking the floor.

Expand to other product lines once balance breaks are rare, traces are reliable and someone owns the process day to day.

Frequently Asked Questions

What is a manufacturing execution system in simple terms?

It is software that manages and records production as it happens. It sends work to the floor, captures what was made, used, scrapped and checked, and keeps a traceable record linked to each order.

Where does an MES sit in ISA-95?

ISA places manufacturing execution systems at Level 3, between Level 4 business activities such as ERP and the Level 2 monitoring and supervisory control of physical processes.

What is the difference between MES and ERP?

ERP runs the business across sales, purchasing, stock and finance over days and months. An MES executes and records production on the floor over minutes and shifts, then returns actual results to the ERP.

What is the difference between MES and MRP?

MRP calculates what materials and production are needed, and when, from demand and bills of materials. An MES records how that planned production was actually carried out.

Do small manufacturers need an MES?

Many need some MES capabilities, such as station bookings, WIP tracking or lot traceability. Fewer need a full MES platform. Start from the specific decisions and records that are missing.

Is MES the same as MOM?

They overlap. Manufacturing operations management is the broader ISA-95 term for Level 3 activities. MES is the more common name for the software that performs many of them.

Can an ERP do the job of an MES?

Sometimes. Many ERP and MRP products include works order bookings, terminals or quality records. Check how they work at the station, offline and for traceability before deciding.

Can OpsMavix build a manufacturing execution system?

Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.

How OpsMavix Can Help

OpsMavix can map how orders move from planning to the floor and back, where bookings are lost or retyped and which traceability questions take too long to answer. From there we can define the smallest change that gives the floor and the office one execution record they trust.

That may mean configuring or connecting the tools you already use, building focused manufacturing production tracking for bookings, WIP and genealogy, linking completions to an inventory automation system, adding a project operations dashboard for managers or developing a full custom ERP.

Contact OpsMavix with one recent works order traveller, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.