Light MES (MES Lite): What It Covers, What It Leaves Out, and When It Is Enough (2026)

TL;DR

A light MES, also called MES lite or a lightweight MES, is the part of a manufacturing execution system that watches the machines. It collects machine data, shows what each line is doing now, records every stop with its cause and turns all of it into OEE. Orders, BOMs, routings and genealogy stay in your ERP.

• The name has no fixed definition. Vendors use it for three different kinds of product, so ask which one you are being shown.
• A light MES is enough when your biggest losses are downtime, slow running and scrap, and your ERP already runs orders well enough.
• You need a full MES when regulators or customers require genealogy or electronic batch records, or when dispatching and routing are the daily pain.
• Start on one pilot line, put a price on its losses, then roll out line by line with the same rules.

Most plants do not lack an MES. They lack an answer to one question: where did the time go on line 2 last night? A full MES can answer it at the end of a plant-wide project. A light MES is built to answer it first, on one line, with the machines you already have.

This guide explains what a light MES covers, what it leaves out, how to tell whether it is enough for your plant and how to start. It stays vendor-neutral until the section on where Fabrico fits. For the full-suite picture and the ISA-95 levels, read our guide to what a manufacturing execution system is.

What is a light MES?

A manufacturing execution system sits between the ERP, which plans what should be made, and the machines, which make it. A full MES covers that whole span: it schedules and dispatches orders, enforces routings and work instructions, traces every unit and records what happened.

A light MES covers the half closest to the machine. It records what each machine actually did, shift by shift, and why it stopped. It does not decide what runs next. That decision stays where it already is in most plants: in the ERP, a planning tool or the supervisor's head.

The trade is deliberate. You give up order control you may not need yet, and in return you get the loss data that most plants are missing, without changing how orders flow.

Three things vendors call "light MES"

There is no standard behind the term, and the market uses it for three different products. All three are legitimate. They solve different problems, so it pays to know which one is on the screen.

One question sorts them in a demo: what does the system record without anyone typing it? If the answer is machine run time, stops and counts, you are looking at a performance-first MES. If the answer is "nothing, the operator fills it in", it is a station app or a trimmed order system.

The rest of this guide uses light MES in the first sense, performance-first, because that is what most plants mean when they search for it: they want to see and fix their losses before they take on a plant-wide project.

What a light MES covers

A performance-first light MES is built on one data stream, the machine signal, and everything else is calculated from it.

• Machine data collection: run, stop and count, read from the PLC where there is one, from add-on sensors on older machines and from cameras at manual stations.
• Live production monitoring: which lines are running, which are stopped, for how long, and how much each line has produced so far in the shift. See how machine monitoring connects for the connection options.
• Downtime tracking with causes: every stop with its start and duration, and the cause the operator tags from a short list. This is the part that turns a number into an action. More in our page on downtime tracking.
• Micro-stops and speed loss: stops too short for anyone to write down, and slow cycles, detected from the signal and counted as performance loss. Our guide to micro-stops explains why they matter.
• OEE by machine, line and shift: availability, performance and quality, multiplied into one figure, with the split that shows which factor is pulling it down.
• Shift reports and dashboards: output, stops and OEE per shift on a screen or a phone, so the morning meeting starts from the numbers instead of collecting them.
• An ERP link: order and product data come in, results go back, so the light MES does not become a second place to plan.

Some products also keep maintenance on the same machine record, so a stop that needs a repair becomes a work order without retyping it. That is a useful extra, not the core.

What a light MES leaves out, and where it lives instead

In the 1990s MESA International described an MES as 11 functions. The list is still the clearest way to see where a light MES stops. Read the right-hand column before you buy: everything marked "elsewhere" must have a home that already works.

If a row in the right-hand column has no good home in your plant today, and it is the row that hurts most, a light MES will not fix it. If the rows that hurt are the first two, a light MES is aimed at exactly that.

Light MES vs full MES

The two are not better and worse versions of one thing. They start from different questions.

For the cost side of a full project, see what an MES implementation takes in cost, time and team, and for the ways those projects go wrong, why MES implementations fail.

Is a light MES enough? A five-question test

Answer these for your own plant, with the people who run it, not from the org chart.

1. Can you show last week's OEE for each line, calculated from machine data and not typed in after the shift?
2. Can you rank last month's downtime by cause, in minutes?
3. Does your ERP handle orders, BOMs and routings well enough today?
4. Do regulators or customers require you to trace every unit or batch back to its materials and process data?
5. Is the daily pain at the machine (why it stopped) or at the station (which job next, which instruction)?

How to read it. "No" to questions 1 and 2, "yes" to 3, "no" to 4 and "at the machine" for 5 is the classic light MES case: the plan works, the line loses time, and nobody can say where. A "yes" to question 4 means you need genealogy, which a light MES does not provide, so plan for a full MES or keep traceability in the ERP. "At the station" for question 5 points to a station app or a full MES, not to a performance-first system.

Many plants that pass the test still add order functions later. Starting light does not close that door. It means the first project pays for itself before the second one is approved.

A worked example: one shift on one line

This is the kind of figure a light MES produces at the end of every shift, without anyone adding it up.

• The shift is 8 hours with a 30-minute break, so the planned production time is 450 minutes.
• The line stopped for 54 minutes in total, so the run time was 396 minutes. Availability = 396 / 450 = 88%.
• The ideal cycle is 6 seconds, 10 units a minute, so the line could have made 3,960 units in its run time. It made 3,406. Performance = 3,406 / 3,960 = 86%.
• 3,270 of those units were good. Quality = 3,270 / 3,406 = 96%.
• OEE = 0.88 × 0.86 × 0.96 = 72.7%.

The figure on its own says little. The split says where to look: quality is fine, and the line lost about the same output to stops as to slow running. A shift log on paper usually lists the long stops. It rarely lists the four-minute ones, and those land in "performance" with no cause attached. A light MES records each of them with its time and length, so the 54 minutes and the slow running can both be ranked by cause the next morning.

For the formula and more worked cases, see our guide to OEE calculation and the full guide to overall equipment effectiveness.

How to start: one pilot line

A light MES is meant to prove itself small before it grows. The pilot that convinces a plant manager has four moves.

1. Connect one representative line. Not the newest line and not the worst one: the one the rest of the plant will recognise.
2. Measure its losses in money. Minutes of downtime and slow running, priced at what the line's output is worth.
3. Act on the highest-value losses. Two or three causes, owned by named people, reviewed every week.
4. Prove the recovered value against the baseline from the first weeks, then roll out line by line with the same rules.

What your side needs ready: network access at the line, access to the PLC where there is one, a first list of stop reasons short enough for an operator to use, and one owner who reviews the numbers each week. For a week-by-week view, read the cloud MES rollout timeline.

Eight questions to ask a light MES vendor

A demo on sample data proves little. Ask each vendor to answer these for one of your own lines.

1. How will each machine on this line report run, stop and count, the old ones included?
2. On what date will this line show live data, and what must we have ready by then?
3. How does an operator tag a stop, and how long does it take? Show us with one of our operators.
4. How do you define planned production time, changeovers and the short-stop threshold in the OEE?
5. Which data comes from our ERP, which goes back, and who maintains the link?
6. Where is our data hosted, who can see it, and which certifications cover it?
7. How does the price change from the pilot line to the whole plant?
8. If we need scheduling or genealogy later, what happens: your product, an integration or a migration?

Our MES software buying guide goes deeper on each point, and the light MES alternatives review compares five products side by side.

Can a light MES grow into a full MES later?

Sometimes, and it depends on the product. Some vendors add order functions over time, some integrate with a planning tool or the ERP, and some expect you to move to a full MES once you need genealogy.

The data you collect is not wasted either way. Clean machine data, a stop-reason list the operators actually use and a habit of weekly loss reviews are what a full MES project needs on day one, and most plants do not have them. That is why a light MES is often the first step of a larger project, not a substitute for it. More on how the two relate in OEE software vs MES.

Where Fabrico fits

Fabrico is a light MES in the performance-first sense: machine data collection, production monitoring, OEE and downtime analytics, and integration with SAP and other ERP systems. Job dispatching, BOMs, routings and genealogy stay in your ERP, and production planning and scheduling are not part of Fabrico today.

• Every machine, old or new: Fabrico reads automated lines from the PLC, fits an IoT device with external sensors to older machines, and uses AI cameras to count output at manual stations. See how the cameras work.
• Live in days: a pilot line is live in days. Installing and connecting the devices on your machines takes about one month, and the full rollout is complete in 3 to 4 months.
• Proof: a European defence manufacturer took OEE from 20% to 62% in three months, connecting 80 machines in 6 weeks with no PLC changes and no production stops. Read the story.
• Security: certified to ISO/IEC 27001, ISO 9001 and ISO/IEC 20000-1, hosted on AWS in the EU, with role-based access.

Most customers reach ROI in 3 months. The full scope is on our MES and OEE software page. To see your own losses with a price tag, book a demo or start with a pilot on one representative line.

Frequently asked questions

What does MES lite mean?

MES lite, light MES and lightweight MES are names for an MES that covers only part of the full function set. Most often it means the performance-first part: machine data collection, production monitoring, downtime tracking and OEE, with orders and BOMs left in the ERP. Some vendors use the same name for station apps or for a trimmed order system, so ask what the product records without anyone typing.

Is a light MES the same as OEE software?

The two overlap. OEE software measures where each machine loses time and output. A light MES usually wraps that measurement in live production monitoring, data collection from every kind of machine and a link to the ERP. Neither one plans or dispatches production orders.

Does a light MES need a PLC on every machine?

No. Machines with a usable PLC can be read directly, older machines can get add-on sensors, and manual stations can be covered by cameras or by operator input. Ask the vendor how each machine on your pilot line will report before you sign.

How long does a light MES take to implement?

A pilot line can show live data within days to a few weeks, depending on the vendor and on how ready your network and machines are. A plant-wide rollout takes longer because every line needs its connection, its reason list and its trained shift leads. With Fabrico, a pilot line is live in days and the full rollout is complete in 3 to 4 months.

Does a light MES replace the ERP?

No. The ERP keeps orders, BOMs, routings and costs. The light MES adds what the ERP cannot see: what each machine did, when it stopped and why. The two exchange data, so planners and the shop floor work from the same figures.

Who is a light MES for?

Plants whose biggest losses are downtime, slow running and scrap, and whose ERP already runs orders well enough. That includes small and mid-sized manufacturers with no MES team, and manufacturing groups that want the same loss data from every site before they commit to a plant-wide project.

When is a light MES not enough?

When regulators or customers require full genealogy or electronic batch records, when high-mix production makes dispatching and routing the daily pain, or when work instructions with sign-offs must be enforced at every station. Those are full MES functions.

See a light MES on your own line: book a demo.