An MES has five working layers: a connection layer that reads machines, a data layer that stores events, a logic layer that turns events into states, order progress and OEE, an app layer for people, and an integration layer that talks to the ERP. In the ISA-95 pyramid, all five sit at Level 3, between control systems and business planning.
Inside the Level 3 box
Most pyramid drawings show the MES as one flat box. The levels around it are covered in ISA-95 levels explained, so this page opens the box.
What each layer does, and what fails when it is weak
| Layer | Job | Usually contains | Symptom when weak |
|---|---|---|---|
| Connect | Read signals, add a time stamp, survive network gaps | Protocol drivers, an edge gateway | Missing counts after every network blip |
| Data | Store what happened, plus the master data | Database, products, ideal rates, reason lists | Reports that disagree with each other |
| Logic | Turn raw events into meaning | State rules, order tracking, OEE | "Running" while nothing comes out |
| Apps | Show people what to do, and take their input | Line screens, boards, reports | Stops left without a cause |
| Integration | Swap orders and results with other systems | APIs, files, message queues | Good counts retyped into the ERP |
One count, up through the layers
Example: a case packer's counter ticks up on Line 3 at 10:14:07. Here is the journey of that one piece.
The gateway reads the counter at 18,412, one up from the last read, and adds a time stamp.
The change of +1 is stored against Line 3 and 10:14:07.
It joins order 4471, moves the rate for the last minutes and confirms the state is Running.
The line board moves on by one, and the shift view updates.
At order close, one total goes to the ERP. The single piece does not.
The direction matters. Detail stays low, and only summaries travel up.
Store events, not every sample
A common design error is saving each read of each tag in the MES database. The arithmetic shows why that hurts.
So the logic layer keeps state changes and count totals. Raw time series, if you need them, belong in a historian, and MES vs historian shows where the line falls.
The quiet part: master data
Events mean nothing without reference data. The data layer also holds which line makes what, at which ideal rate, on which shift pattern, with which stop reasons.
- Products and ideal rates: the base of the performance figure, as OEE performance shows.
- Lines, machines and shifts: needed to know what was planned time at all.
- Reason lists: who may add a reason, and how they group in reports.
- Orders: usually owned by the ERP and copied down, never edited in two places.
Name one owner for each item, and decide which system is the master. Many reports that "disagree" turn out to use two versions of one ideal rate.
Point-to-point links or a shared hub
A plant with many systems must choose how they talk. Direct links grow quickly, because each pair may need its own.
The hub idea is often called a unified namespace, and the open source United Manufacturing Hub says it helps you build one. It adds one more system to run, so a plant with an MES and an ERP alone can stay with one direct link.
Where each part runs
| Pattern | Connect layer | Other layers | Fits when |
|---|---|---|---|
| On site | Plant network | Plant server | Rules or policy keep data on site |
| Cloud with edge | Gateway at the machines | Hosted | Few IT staff on site, several plants |
| Hybrid | Gateway at the machines | Line screens local, reports hosted | Line screens must work through an outage |
One rule holds in all three: the connect layer must stay close to the machines and buffer data. If the link drops for an hour, the counts should arrive late, not vanish.
Where the security lines go
Keep the control network apart from the office network, and pass data through a controlled link.
The ISA/IEC 62443 series defines requirements and processes for securing industrial automation and control systems. Part 3-2, on security risk assessment for system design, is the place to start for this drawing.
Give the connect layer a read-only path where it can. If the MES must send something to a machine, treat that as a separate design, as in MES PLC integration.
Light and full MES share the same shape
The layers stay, and their thickness changes. A light MES has a thick connect and logic layer for stops and OEE, with thin order handling.
A full MES adds much more logic for dispatch, quality and genealogy, listed in MES modules. The trade-offs are in light MES vs full MES.
Draw your own in an hour
- Draw one box per system you have today, including spreadsheets.
- Draw one arrow per data flow, and label what, how often and who owns it.
- Mark every arrow that a person retypes. Those are your first integration targets.
- Mark what must keep working when the internet is down.
- Turn the gaps into lines in your requirements checklist.
In this drawing, Fabrico is a light MES for OEE. It takes stops, speed and counts live from PLCs or IoT sensors (external sensors on older machines), with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line, with OEE per line and shift. See how Fabrico connects machines.
What people ask next
What are the levels of an MES system?
The pyramid has five ISA-95 levels, from Level 0 the process up to Level 4 business planning, and the MES sits at Level 3. Inside it, this page uses five working layers. ISA-95 levels explained covers the outer pyramid.
Does an MES need SCADA underneath it?
No. An MES can read PLCs, gateways or sensors directly, and many lines have no SCADA at all. Where SCADA exists it can be one more data source, so check which system should own each signal.
Can an MES run in the cloud?
Most of it can, while the connect layer stays near the machines to read signals and buffer through gaps. Line screens need a plan for outages. The requirements checklist helps you write that down.
Is the ISA-95 pyramid out of date?
Its levels still describe jobs and time scales well, even when data no longer moves strictly level by level. Treat it as a map of who does what, and not as a wiring plan.
How does an MES connect to the ERP?
Usually through an API, a message queue or files. Orders and master data come down, and good counts and times go back up at agreed points. Keep machine tags out of the ERP, and let the MES translate.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.