Blog / MES
MES · Guide

MES vs LIMS: Production Floor and Quality Lab

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

An MES runs and records production. A LIMS (laboratory information management system) runs the quality lab: sample login, test methods, instruments, results, specifications and certificates. They meet at the sample: the MES asks for a test at a defined step and the LIMS returns a result, which decides if a batch moves on or waits.

Picture a finished batch sitting in a tank. Production thinks the lab has it, and the lab thinks the sample has not arrived, while the next order waits for the tank.

That gap between the two buildings is what this comparison is really about. Each system is good on its own side of the door.

Two sets of work, two sets of rules

A LIMS organises work in a lab. A sample gets an ID, then a set of tests, then results from analysts or instruments, then a review against a specification.

It tracks instruments, calibration, reagents, analyst training and chain of custody. ASTM E1578 is the standard guide for laboratory informatics, and ISO/IEC 17025 sets competence requirements for testing and calibration labs.

An MES organises work on the floor. Its objects are the order, the operation, the machine, the material lot and the operator.

MESLIMS
Main objectOrder and batchSample and test
UsersOperators, supervisorsAnalysts, lab managers, QA
RecordsSteps, materials, counts, stopsMethods, results, instruments, specs
Time scaleMinutes and shiftsHours and days, by test
OutputAs-made record, performance dataResult, certificate of analysis
Both hold quality data, but they hold it for different reasons.

The handoff, step by step

Most of the interface comes down to one round trip. Here it is for a typical batch.

1
MES triggers the sample
A step in the recipe or a time rule creates a request with batch, product, stage and test plan.
2
Operator takes the sample
The MES or LIMS prints a barcode, and the operator confirms time and location.
3
LIMS logs it in
The lab scans the sample at receipt. The clock for lab work starts here.
4
Analyst and instruments test
Results come from instruments, often through a chromatography data system, or from manual entry, and are reviewed.
5
Result returns to production
Pass, fail or hold goes back to the MES and the ERP, which set the batch or lot status.
One sample round trip. Each message carries the sample ID and the batch or lot ID.

Two details decide if this works. The sample ID must be scanned and never typed, and only reviewed results should change a batch status.

In regulated plants the release decision usually sits with quality, often in the ERP, QMS or MES, with the LIMS supplying the evidence. See MES vs QMS for that boundary.

Where the time goes

Example: a batch finishes at 10:00, and its result is approved at 15:00. Here is how those 300 minutes split.

Waiting for sample to be taken20 min
Transit and login30 min
Queue in the lab70 min
Testing140 min
Result review40 min
Example timeline, 10:00 to 15:00. Only 140 of the 300 minutes are testing.

Production alone sees the first bar, and the LIMS alone sees the queue. Joined up, the 120 minutes before testing starts become an obvious target.

A common fix is a test schedule that knows when batches finish, which requires the MES to share its expected end time with the lab.

What that hold does to OEE

This is where people disagree, and the answer depends on whether the equipment is tied up. If product can move to a holding tank and the reactor can start again, the wait costs inventory and lead time, with no OEE loss.

If the vessel must hold the batch until release, the 300 minutes are lost equipment time. In that case, plants may count it as unplanned downtime or as a planned part of the batch cycle.

Choose one rule and write it down. OEE for batch processes covers the options, and the availability calculator shows the effect on your own numbers.

Quality in OEE should reflect the lab outcome too. A batch that fails and is reworked is not good first time, so the count that feeds OEE quality depends on the result from the lab.

Tests at the line: who owns them?

The fuzzy area is the shop floor test. Operators check pH, weight or viscosity at the line, and each plant must decide where that data lands.

  • In-process checks in the MES. Fast, tied to the step, and seen at the line. This suits simple checks that hold up the next step.
  • In-process checks in the LIMS. Better if they use controlled methods and instruments, or if the lab needs to trend them with other results.
  • Specifications. If both systems hold limits for one test, they will drift apart. Keep one master and publish it to the other.
  • Environmental monitoring and stability tests. These normally stay in the LIMS, since no production order is attached.

Which plants run which

A contract lab can run on a LIMS alone, because it has samples and no production orders of its own. Some plants with a busy lab do the same while production records stay on paper or in the ERP.

A discrete plant that measures at the line or sends few tests out can often run an MES alone. A small lab may manage with a spreadsheet or a simple tool.

Pharma, food, chemicals and cosmetics plants often need both, since many batches wait on lab results. The value comes from linking them, because two unlinked systems leave staff retyping results.

See MES for pharma and OEE and downtime in food and beverage.

A small site with a few release tests can start on controlled paper records. Keep sample IDs and results tidy, because that is what auditors or customers will ask to see.

What regulated plants should check

The US FDA's 21 CFR Part 11 sets the criteria for trustworthy electronic records and signatures. Its data integrity guidance uses the ALCOA idea: attributable, legible, contemporaneously recorded, original or a true copy, and accurate.

An interface between MES and LIMS is part of that chain, so it should be validated, and a failed message must not vanish silently.

  • Audit trail on both sides. Part 11 expects time-stamped audit trails, and a change must not hide the earlier entry.
  • Retests. Define how a retest or an out-of-specification result flows back, and never overwrite the first value.
  • Time sync. The batch record and the lab record must agree on the time order of events.

Where the link usually breaks

  • Retyping results. Every manual copy between the systems is a chance for an error and a delay.
  • Reporting from each side alone. Lab turnaround looks fine when counted from login, and production only sees the total wait.
  • Treating the wait as "no one's loss". Give hold time its own reason code so it appears in a Pareto chart.
See it live in Fabrico

If lines or vessels sit idle while results come back, that time should carry a cause. Fabrico is a light MES for OEE: it takes stops live from the machine, and operators tag the cause at the line, so holds appear next to every other loss in OEE per line and shift. See how Fabrico tracks stops and causes.

What people ask next

Can an MES replace a LIMS?

For simple checks at the line, sometimes. A busy lab with methods, instruments, calibration and stability studies needs tools an MES usually does not cover. The MES modules page shows what its quality functions normally hold.

What is the difference between LIMS and ELN?

A LIMS manages structured sample and test workflows. An electronic lab notebook (ELN) records less structured experimental work, mainly in research. A laboratory execution system (LES) guides analysts through a method step by step.

How do MES and LIMS exchange data?

Commonly through web services, a message broker or middleware, using sample ID, batch ID and test results. Flat file exchange still exists at older sites. MES system architecture shows where these links sit.

Does the LIMS release the batch?

It usually supplies the approved results, and an authorised quality person makes the release decision. The status may be recorded in the ERP, the QMS or the MES, depending on your process. Agree on one place.

Should waiting for lab results count in OEE?

Only if the equipment is held and could otherwise run, and practice varies on whether that is planned time. State your rule and apply it consistently, as covered in OEE for batch processes.

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

← More OEE Lab guides · MES for pharma →

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