Most manufacturers’ ERP systems work fine: orders come in, stock moves out, invoices get issued, the books close. But ask the production manager “how many minutes did machine 3 sit idle yesterday, and why?” and the answer rarely comes from an ERP screen — it comes from the shift supervisor’s notebook, or a WhatsApp chat. ERP holds the commercial backbone of a business; it wasn’t built to see what the production line is doing second by second.
The layer that fills this gap is called MES (Manufacturing Execution System). ERP and MES get confused constantly, because both get sold under the “production software” label. But they answer different questions, operate at different speeds, and are usually meant to work together rather than replace one another.
That confusion has a real cost. A business that installs a screen sold as an ERP “production module” and assumes the real-time gap is closed will still be asking the same question six months later: which machine, for how long, and why did it stop yesterday? The answer still lives in a notebook, or in a conversation nobody remembers.
What ERP does — and where it stops on the shop floor
ERP’s production-related modules typically manage material requirements planning (MRP), work-order creation, stock movements, costing, purchasing and shipping. Their time resolution is day or shift level — they answer questions like “how many work orders closed this week” or “what was raw-material consumption this month” reasonably well.
That’s ERP working as designed, not falling short. It exists to keep commercial and financial processes on a single source of truth — not to process a signal generated once a second at the machine.
What MES is, and at what level it operates
MES kicks in from the moment a work order “lands” on the factory floor: which operator, on which machine, produced which part, when, at what speed; what the reject/scrap rate was; what caused a stoppage. Its data source is usually PLC/SCADA signals, barcode/RFID scans, or operator terminal entries — raw data straight from the machine or the line, at minute or even second resolution.
Typical MES functions:
- Dispatching: which job runs on which station, in what order, updated in real time.
- Production and downtime logging: machine run/stop times and stoppage-reason codes, captured automatically or via operator input.
- Quality/reject tracking: reject, rework and scrap rates monitored on the line as they happen.
- OEE calculation: overall equipment effectiveness — availability × performance × quality — computed in real time.
- Traceability: which raw-material batch/serial number went into which finished product, logged for audit.
MES vs. ERP, side by side
| Dimension | ERP | MES |
|---|---|---|
| Focus | Orders, stock, finance, planning | Line/station-level production execution |
| Time resolution | Day / shift | Second / minute |
| Data source | User entry, integrations | PLC/SCADA, sensors, barcodes, operator terminals |
| Typical question | ”What was this month’s production cost?" | "Why is machine 3 down right now?” |
| Decision level | Business / planning | Shop floor / shift supervisor |
They’re not competitors — they’re layered. ERP sets the plan; MES measures how that plan actually plays out on the floor and feeds it back. Without the integration between them (the work order flows down from ERP to MES, actual output flows back up from MES to ERP), both systems stay stuck in their own silo.
When an SME actually needs MES
Not every manufacturer needs MES. A small, single-line, low-variation operation can run on Excel plus ERP for a long time. Signals worth watching for are usually:
- Multiple production lines/stations, and the bottleneck between them isn’t visible.
- Downtime and reject rates aren’t tracked consistently — there’s no clear answer to “what’s our OEE”.
- End-of-shift reports are compiled manually and arrive a day late.
- A certification body or customer audit asks for batch-level traceability.
- Energy and production data need to be read together — for example, to build a baseline for an ISO 50001 energy management system or a green-transition application.
That last point matters: real-time production data isn’t only about efficiency — it’s the input for every process that requires measurement, from energy monitoring to carbon-footprint calculation to sustainability reporting. Without data collected on the floor, nothing built on top of it rests on solid ground.
Where to start
An MES rollout doesn’t have to — and usually shouldn’t — try to cover everything at once. A realistic roadmap looks like this:
- One line, one pilot. Pick the most critical or most bottlenecked line; don’t try to cover the whole plant at once.
- Data collection before automation. Start simple — barcode scanning, digital forms, reading an existing PLC — before adding a fully automated sensor network.
- Design the ERP integration up front. How the work order flows down to MES, and how actual output flows back to ERP, needs to be settled during the pilot — not patched on afterward.
- Get the team used to reading the data. Software makes no difference until the shift supervisor and production manager actually look at the OEE dashboard every day.
- Expand after the pilot. Lessons learned on the first line — which downtime codes are meaningful, which reports actually get read — carry over faster to the next ones.
İkiz Eksen’s approach
İkiz Eksen treats ERP and shop-floor data as part of the same chain within digital transition: data collected from machines and sensors is structured through MES or a lighter production-monitoring layer, integrated with ERP, and pushed to decision dashboards. That track record comes from 550+ customers, 15+ sectors and 100+ ERP projects under the Qera umbrella, run by a team of ~35 specialists, on infrastructure hosted on Microsoft Azure.
We can help clarify which layer — ERP integration, full MES, or a lighter monitoring solution — fits your scale. Take a look at our solutions, or get in touch directly.
Frequently asked questions
Do I need ERP in place before I can install MES?
Not strictly, but it’s practical. MES can be installed without ERP; but since work-order, material and cost data live in ERP, without integration your MES data stays half-useful — you can’t carry what happened on the floor up to the business layer.
Is MES too expensive for a small business?
A full MES rollout can be a serious investment, but not every business needs the full scope. For most SMEs, starting with a lighter production-monitoring/data-collection layer (basic downtime and OEE tracking) and expanding as the need grows is the more realistic path.
Is MES the same as IoT/M2M?
No. IoT/M2M is the method of collecting data from machines (sensors, PLCs, gateways). MES is the software layer that combines that data with work-order, operator and quality information and makes sense of it. IoT supplies the data; MES turns it into something useful.
Can’t I just pull OEE out of ERP reports?
Roughly, yes — but it will be delayed and coarse, usually built on manual end-of-shift entry. Real-time, reliable OEE needs downtime and speed data straight from the machine, which is exactly what MES (or a similar data-collection layer) is for.
How do I show the return on this investment?
Measure your current state first — downtime, reject rate, planning delay — with data. Compare the same metrics after MES goes live. A concrete, measured before-and-after table is your strongest evidence, both internally and for any support or credit application.