MES vs ERP: What a Factory Needs and When

The short answer

ERP covers the company as a whole: sales, purchasing, inventory, finance, HR and the overall production plan. MES covers what happens inside the plant: which work orders are running, on which equipment, with what output and quality.

A useful way to think about it: ERP knows what needs to be produced and what it costs. MES knows how it is being produced right now and what actually came out.

They are not competing systems but two layers of one architecture. Between them and the machines there is often an automation layer (SCADA, PLCs) from which MES receives data.

Comparison on key parameters

What each system does

ERP

• takes customer orders and builds the sales plan;
• calculates material requirements from bills of materials;
• creates the production plan by period;
• manages purchasing, inventory and cash flow;
• calculates cost and financial results.

MES

• breaks the plan into shift-level work orders per work center;
• sequences the queue considering changeovers and load;
• collects actual output, consumption and downtime;
• controls quality at each operation;
• keeps the history of every batch for traceability.

How ERP and MES exchange data

The exchange is two-way. A typical flow:

From ERP to MES:

• production orders with quantities and due dates;
• bills of materials (BOM) and routings;
• master data for items, equipment and staff;
• information about available materials.

From MES to ERP:

• actual output and scrap;
• actual material consumption;
• labor and machine time;
• order completion statuses.

The international standard ISA-95 (IEC 62264) describes the levels of this architecture and the exchange models between them, and many systems are built around it.

Practical integration rules:

• assign one master system for each set of master data, usually the ERP;
• send data on events (order released, operation completed) rather than once a day;
• run reconciliation of quantities and balances to catch mismatches;
• log every exchange and error.

In which order to implement

For most growing manufacturers the logical sequence is:

1. ERP or an accounting system first. Without unified records of items, BOMs, inventory and orders, MES has nowhere to get its input and nowhere to send its results.
2. Then clean up production data: BOMs, routings, time standards. This is often the most labor-intensive step.
3. Simple shop floor tools: downtime tracking, electronic shift reports, batch scanning.
4. MES — once the shop floor becomes the bottleneck: many lines, complex coordination, traceability and quality requirements.

The exception is industries with strict traceability requirements, such as pharma or food production. There, MES functions related to quality and batch history may need to come earlier or in parallel.

How to tell what you need now

You need ERP (or to develop it further) if:

• inventory and purchasing do not match production;
• product cost is unknown or calculated by hand;
• the production plan lives in Excel and is not linked to orders.

You need MES if:

• ERP records are in order, but the plan regularly slips on the floor;
• downtime and scrap are not tracked or are discovered after the fact;
• customers or auditors require batch history;
• supervisors spend their shift coordinating instead of producing.

Common mistakes

• MES on top of messy master data — work orders are built from wrong BOMs.
• Trying to replace MES with an ERP module where real-time data collection is needed.
• Duplicated functions — scheduling is done in both systems and nobody knows which plan is right.