ISA-95 Explained: Where MES Fits Between the PLC and the ERP
What is ISA-95?
ISA-95 is a series of standards for connecting a plant's control systems with its business systems, such as an ERP. It is published by the International Society of Automation (ISA) and, internationally, as IEC 62264. It does not tell you which software to buy. It gives everyone on a project the same model and the same words for which system does what, and what information passes between them.
That shared vocabulary is its main value. Many integration problems start because the people running the ERP and the people running the plant use the same word for different things.
What are the ISA-95 levels?
ISA-95 builds on a layered model of a manufacturing enterprise, often drawn as five levels. The ISA's overview of the standard describes them as follows.
| Level | What happens here | Typical systems |
|---|---|---|
| 0 | The physical production process | Machines, lines and process equipment |
| 1 | Sensing and acting on the process | Sensors, valves, smart devices |
| 2 | Monitoring and supervisory control | PLCs, DCS |
| 3 | Manufacturing operations management | MES, SCADA |
| 4 | Business planning and logistics | ERP |
The standard is mainly concerned with the boundary between level 3 and level 4: what the plant tells the business, and what the business tells the plant.
Where does MES fit?
A manufacturing execution system (MES) sits at level 3. It turns business plans into work on the floor and turns floor events back into business records. Typical jobs include dispatching orders to lines, tracking materials and batches, recording what was produced and consumed, and collecting quality results.
The ERP, at level 4, plans what to make, when and with what materials, over days and weeks. The controllers at level 2 run the process in seconds. MES bridges those two timescales. Without it, the gap is often filled by spreadsheets and people re-typing figures from the floor into the ERP at the end of the shift.
Not every plant needs a full MES. A smaller site may only need a few of its functions, such as production counts and downtime reasons sent to the ERP. The model still helps, because it makes clear which functions you are choosing to cover and which you are leaving out.
What information crosses the level 3 to level 4 boundary?
ISA-95 defines models for the information that business and manufacturing systems exchange. In everyday terms, the main flows are:
- From the business to the plant: what to produce, in what quantity and by when, along with the product definitions and recipes.
- From the plant to the business: what was actually produced, what materials were used, how much equipment and labour time it took, and the status of orders.
- Shared reference data: materials, equipment and personnel, defined once so that both sides mean the same thing.
Agreeing these flows in writing, including what happens when a message fails, is most of the work in an MES or ERP integration.
How do you use ISA-95 on a real project?
- Map what you have. Place each existing system on the levels. Gaps and overlaps become obvious, such as two systems both claiming to own production counts.
- Decide which system owns each piece of data. For example, the ERP owns the order and the MES owns the actual quantity produced. One owner per item avoids numbers that never agree.
- Write the interface down. For each flow, record the content, the trigger, the frequency and the behaviour when the other side is unavailable.
- Use the standard's terms in the specification. It saves time when your team, the ERP team and any vendors read the same document.
These decisions belong in the functional design specification. Our guide to what a functional design specification should contain covers that document, including interface ownership. For how data travels from the controllers to level 3 systems, see OPC UA explained for plant managers.
Using ISA-95 as a reference model is a way of agreeing structure and vocabulary. It is not a claim that a system is certified or compliant with the standard.
Connecting the plant floor to your ERP? Our PLC, SCADA and MES integration service includes an agreed message contract and defined failure behaviour for the interface. Our process starts with a fixed-fee assessment, and our FAQ explains what you receive and own.