A planner releases a work order in the ERP on Monday. By Wednesday the line has changed over twice, a batch of material was rejected and a machine sat idle for forty minutes waiting for a tool. None of that is visible in the ERP until someone types it in. That gap between the plan and the floor is exactly where a manufacturing execution system (MES) earns its place. This guide explains what each system does, where they overlap and how to decide whether you need one, the other or both.

THE IDEA

ERP decides what the business should make. MES proves what the factory actually made.

To apply this workflow in your business, explore our MES development service and implementation approach.

What is the difference between MES and ERP?

Enterprise resource planning (ERP) software runs the business side of manufacturing. It holds customers, sales orders, purchase orders, bills of materials, inventory valuation and the general ledger. Its decisions are about what to make, what to buy and what it costs, and it typically works in days, weeks and months.

A manufacturing execution system runs the production side. It knows which job is on which machine, who is operating it, which material lot was consumed, how many good and rejected parts were made and why the line stopped. It works in shifts, hours and minutes, and much of its data comes from machines, scanners and operator terminals rather than office users.

The ISA-95 standard, known internationally as IEC 62264, describes this split as two layers: business planning and logistics at Level 4, and manufacturing operations management at Level 3. The standard's main concern is the information exchanged between those two layers, which is a useful way to think about any MES and ERP project.

References: OPC Foundation: ISA-95 overview (OPC 10030)

MES and ERP side by side

The comparison below is a practical summary rather than a vendor feature list. Many ERP suites include production modules, and many MES products include light planning tools, so the boundary in your business depends on the detail and speed you need on the floor.

How ERP and MES differ in day-to-day manufacturing
QuestionERPMES
Main question it answersWhat should we make, buy and sell, and what does it cost?What is happening on this line right now, and what did we actually make?
Time horizonMonths, weeks and daysShifts, hours and minutes
Typical usersFinance, purchasing, planning, salesSupervisors, operators, quality, maintenance
Core recordsSales and purchase orders, BOMs, stock value, invoicesWork in progress, machine states, downtime, consumption, inspections, genealogy
Where data comes fromPeople entering business transactionsMachines, PLCs, scanners and operator terminals
What success looks likeAccurate plans, costs and financial recordsOn-time, traceable, right-first-time production

Signs you have outgrown ERP alone

The clearest sign is a second, unofficial system made of paper travellers, whiteboards and spreadsheets. Supervisors rebuild the day in a shift report, production confirmations are keyed into the ERP in bulk at the end of a shift, and nobody can say with confidence why output was lower than planned yesterday.

Traceability is another signal. If a customer complaint means a day of searching to find which material lot, machine and operator produced a batch, the information exists but is not connected. An MES captures that history as the work happens, so the answer is a lookup rather than an investigation.

Finally, look at downtime. When stoppages are recorded as a single total rather than by reason, machine and time, improvement work relies on memory. Capturing reasons at the point of stoppage is one of the most valuable first steps an MES can take.

When an MES will not fix the problem

An MES amplifies the quality of the plan it receives. If bills of materials are wrong, routings are out of date or item codes are duplicated in the ERP, the shop floor will execute faithfully against bad instructions. Fix the master data that production depends on before, or alongside, the MES rollout.

Equally, a problem that sits in sales forecasting, purchasing lead times or financial approval will not be solved on the factory floor. Be clear about the question you are trying to answer, then choose the system that owns it.

How should MES and ERP share data?

A common, workable pattern is that the ERP releases production orders, bills of materials and routings to the MES, and the MES returns confirmed quantities, scrap, material consumption, labour time and quality status. The ERP keeps the financial view of inventory; the MES records movements at the point of use and reports them.

The detail that causes most integration failures is ownership. For every record, agree which system creates it, which may change it and which holds the accepted final state. A completed quantity should carry its job, operation, time and quality status so both teams read the same fact the same way.

Plan for interruptions too. If the ERP is unavailable, the MES should keep working, queue its confirmations and show what is pending. Test what happens when a message is sent twice, because a lost acknowledgement must not create a second production confirmation.

A sensible first project

Start with one line and one product family. Digitise the work order, capture downtime with reasons, record good and rejected quantities, and send confirmations to the ERP automatically. Run it alongside the current process for a few weeks and reconcile the totals with the ERP.

Expand when supervisors trust the numbers and the finance team can explain any difference between MES and ERP figures. Machine connectivity, quality workflows and advanced scheduling build naturally on that foundation.

FREQUENTLY ASKED QUESTIONS

Questions readers ask

Is MES part of ERP?

Some ERP vendors sell manufacturing execution modules, but real-time execution, machine data and production genealogy are distinct functions. Whether an ERP module is enough depends on how much detail and speed you need on the floor, and how many machines and operators need to interact with it directly.

Can a smaller manufacturer justify an MES?

Yes, if the scope is focused. Digital work orders, downtime capture with reasons and automatic production confirmations on one line can remove a large amount of manual reporting without an enterprise-wide programme.

Which system should own inventory?

Usually the ERP owns stock valuation and the financial view, while the MES records consumption and work-in-progress movements where they happen and reports them back. Agree ownership for each record type during design.

How long does an MES project take?

It depends on the number of machines to connect, the quality of ERP master data and how many sites are involved. A bounded pilot on one line is the fastest way to learn what a full rollout will need.

TAKE THIS INTO YOUR NEXT DISCUSSION

A practical starting checklist

  • One line and one product family for the pilot
  • Agreed record ownership between MES and ERP
  • Downtime reasons captured at the point of stoppage
  • A reconciliation check before expanding

Use ERP to plan and account for the business, and MES to run and prove production. Connect them around clearly owned records and expand from a pilot your team trusts.

Original guide by the IOT Software and Solutions editorial team. External facts are linked to their sources; examples are illustrative and do not describe measured client results.

Put the idea into practiceExplore MES Development