Blog / MES
MES · Guide

MES Modules: Typical Functions, and Which First

OL By OEE Lab Editorial |Updated 2 November 2026 |5 min read
Short answer

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.

ModuleQuestion it answersWhat it needs
Data collectionIs it running? How many?Machine signals or sensors
Performance analysisWhere did the time go?Data collection, ideal cycle times, reasons
Quality recordsWhat was rejected, and why?Counts, reject reasons, check plans
Dispatch and schedulingWhat runs next, and where?Orders, routings, true machine capacity
Tracking and genealogyWhat went into this unit?Lots, orders, scanning at each step
DocumentsWhich instruction applies now?Controlled versions, screens at the line
LaborWho worked on what?Logins, orders, skills records
Maintenance linkWhat does the machine need?Stop history, a request path
Our plain grouping of the usual functions. The classic list also splits out resource allocation and process management.

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.

Planned: 500 units/h x 8 h = 4,000 units
Measured: 500 x 62% OEE = 310 units/h
310 x 8 h = 2,480 units
Gap in the plan: 1,520 units a shift
Hypothetical line. Dispatching on a rated speed promises 1,520 units this line has not been making.

So a good OEE figure is a scheduling input as well. See the capacity calculator for that sum.

The usual order

Layers 2 and 3 lean on layer 1, while layer 4 runs mostly on its own data. Layer 1 is what a light MES covers first.
  • 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.

Stops (layer 1)1,050 min
Slow running, short stops (layer 1)650 min
Waiting for the next order (layer 3)400 min
Rejects (layer 2)200 min
Paperwork, finding instructions (layer 4)100 min
Hypothetical week, widths as shares of 2,400 lost minutes. The first two rows, 70.8% of the loss, sit in layer 1.

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.
See it live in Fabrico

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.

See OEE per line and shift on your own machines

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.

Book a Fabrico demo

Related guides: MES vs WMS: Line, Warehouse and the Handoff

← More OEE Lab guides

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES