Typical MES modules are data collection, performance analysis (OEE), quality records, dispatching and scheduling, product tracking, documents, labor and maintenance links. Most plants should start with data collection and performance analysis, because schedules, quality rates and the business case all lean on them. Add the rest when a measured loss or a customer rule asks for it.
The list, in plain words
For what an MES is and where it sits, read what is an MES. This page is about the parts, and the order to buy or switch them on.
The industry body MESA International defines 11 MES functions in its White Paper 2, and a 2009 journal paper by V. Modrák lists them in full.
Suppliers package those functions under their own names. So judge a module by the question it answers, not by what it is called.
| Module | Question it answers | What it needs |
|---|---|---|
| Data collection | Is it running? How many? | Machine signals or sensors |
| Performance analysis | Where did the time go? | Data collection, ideal cycle times, reasons |
| Quality records | What was rejected, and why? | Counts, reject reasons, check plans |
| Dispatch and scheduling | What runs next, and where? | Orders, routings, true machine capacity |
| Tracking and genealogy | What went into this unit? | Lots, orders, scanning at each step |
| Documents | Which instruction applies now? | Controlled versions, screens at the line |
| Labor | Who worked on what? | Logins, orders, skills records |
| Maintenance link | What does the machine need? | Stop history, a request path |
Why data collection comes first
Look at the right-hand column. Performance analysis, dispatch, quality rates and the maintenance link all lean on machine state and counts, and they need those to be right.
Documents, labor and genealogy run mostly on their own data. That is why a plant with a hard traceability rule may start there.
A schedule built on guessed capacity is a guess with nicer screens. Quality rates with a wrong total count are wrong too.
So a good OEE figure is a scheduling input as well. See the capacity calculator for that sum.
The usual order
- Layer 1: machine data, stops and OEE. This shows the size of your losses, and it works before any integration. It is the core of a light MES.
- Layer 2: quality records. Reject reasons complete the Q in OEE and give you first pass yield by product.
- Layer 3: dispatch and the ERP link. Now the plan can use the rates you measure, and good counts can flow back to the order. MES vs ERP shows who should own what.
- Layer 4: genealogy, documents and labor. These matter when a customer, a regulator or your own paperwork demands them.
When the order changes
The order above is a default, and three cases break it.
- A regulated product. If you cannot ship without lot genealogy or controlled records, that layer is a must from day one. Run it alongside layer 1, not after.
- A job shop in paper chaos. If orders get lost and machines wait for the next job, dispatching may hold the biggest prize. See OEE for job shops.
- A plant with good machine data already. If your lines already feed trusted stop and count data, start with the layer that loses the most.
Match modules to your own losses
Do not choose modules from a brochure. Take one week of lost time and sort it by which module would help.
Example: a line loses 2,400 minutes in a week. The team sorts them with the help of a downtime Pareto.
For this line, layer 1 goes first, and layer 3 is the sensible next step. Paperless instructions may be welcome, but on these numbers they can wait, as paperless manufacturing explains in more detail.
Your own week may sort very differently, which is the point of doing it. Once it is sorted, turn the result into a list with the MES requirements checklist.
How to buy modules without regret
- Buy what you will use this year. Ask for a written answer on what adding a module later involves.
- Check that the data carries over. A later module should read the same machines and orders, not need them set up again.
- Ask what a module needs from you. Genealogy, for one, usually needs scanning at each step, so somebody on the floor pays for it in time.
- Treat names with care. "Production monitoring", "shop floor control" and "OEE module" can each mean different things, so test with your own question.
- Prove value first. Use your first layer to work out the return before you pay for the next.
Fabrico is a light MES for OEE, built around the first layer: stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, causes tagged by operators at the line, and OEE per line and shift. See how Fabrico covers layer 1.
What people ask next
What are the 11 functions of an MES?
MESA International's list is resource allocation and status, operations scheduling, dispatching, document control, data collection, labor management, quality management, process management, maintenance management, product tracking and genealogy, and performance analysis. You can check it in Modrák (2009). What is an MES gives the wider picture.
Which MES module should I implement first?
For most plants, data collection with performance analysis, because schedules and quality figures lean on them. Regulated plants may need genealogy at the same time. MES implementation steps shows the rollout order.
Is OEE part of an MES?
Yes, OEE usually sits in the performance analysis function, fed by data collection. You can also track it alone with a spreadsheet template or with a light MES.
Do I need all the MES modules?
Rarely. Each one has a data and labor cost, so add a module only when a measured loss or a firm rule asks for it. A light MES is often enough for a long time.
How is a MES module different from an ISA-95 level?
A module is a function you use, while a level describes where a system sits between the machines and the business. ISA-95 levels explained covers that side.
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.
Related guides: MES vs WMS: Line, Warehouse and the Handoff