Blog / MES
MES · Guide

MES vs PLM: From Design Intent to Build Record

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

PLM holds what the product should be: designs, bills of materials, revisions and engineering changes. An MES holds what was actually done: which revision was built, by which order, on which machine, with which result. PLM releases the definition, often through the ERP, and the MES turns it into work and sends back the as-built facts.

The clearest way to separate these two is one engineering change. A designer alters a bracket on Monday, and by Thursday a machine must be building the new one without mixing the two.

PLM owns the first half of that story and the MES owns the second. What goes wrong usually happens where they meet.

Two different kinds of truth

Product lifecycle management (PLM) is the record of intent. It stores CAD files, specifications, engineering bills of materials, revision history and the approval path for each change.

A manufacturing execution system is the record of fact. It stores what ran, in what quantity, with which material and settings, and what stopped it.

PLM users are engineers working over months and years. MES users are operators and supervisors working over minutes and shifts.

ViewAnswersUsually lives in
As designed (engineering BOM)What parts make up this product, by function?PLM
As planned (manufacturing BOM, routing)In what order, at which station, with what kits and packaging?PLM or ERP
As builtWhat actually went into serial 1,241?MES
Three views of one product. Many plants keep the manufacturing BOM in the ERP, so the path runs PLM, then ERP, then MES.

One change, followed through

Example: change ECO-2291 replaces bracket revision C with revision D, because revision D is stiffer. The change is approved in PLM when the line has just built unit 1,060.

Scrapping stock would be wasteful, and 180 revision C brackets remain. So engineering sets revision D to start at unit 1,241.

Approvedunit 1,060Cut-inunit 1,241Rev C: 180 units leftRev D1,060 + 180 = 1,240, last rev C
Example revision cut-in. PLM states the rule, the MES enforces it unit by unit.

This is called effectivity, and it can be set by date, lot or serial number. PLM records the rule, but the line only obeys it if the MES knows about it.

The MES then does four things:

  • It shows the right drawing and work instruction for each unit.
  • It blocks a revision C bracket being scanned on unit 1,241 or later.
  • It records which revision went into every serial.
  • It reports when the cut-in really happened, which may differ from the plan if scrap ate some of the old stock.

That last point matters. If 5 revision C brackets are scrapped, the old stock runs out after unit 1,235, and the plan and the facts no longer match.

What flows between them

From PLM down: released BOMs, routings or process plans, drawings, work instructions, inspection characteristics and the change notices with their effectivity. PLM products with process planning tools may also hand over a full bill of process.

From MES up: as-built records, deviations, nonconformances, real cycle times and which steps fail. These tell engineers whether the design can be built as drawn.

Only release-state data should cross. The MES must never see a draft revision, or the line may build something unapproved.

In many plants the path goes through the ERP, which holds item masters and the manufacturing BOM. Direct PLM to MES links tend to carry work instructions and drawings.

The MES requirements checklist is a good place to write down which path you want.

Instructions, routings and quality plans

Three grey zones come up on every project.

  • Work instructions. Authored in PLM or in a separate tool, displayed by the MES. Decide where the master copy lives.
  • Routings. PLM can plan them, the ERP can hold them, and the MES can hold a more detailed version. One must be the master.
  • Quality plans. Characteristics start in design and get measured on the floor. See MES vs QMS for the quality system side.

The change that quietly breaks OEE

An engineering change can also alter how fast a product should run, and that reaches your OEE numbers. Forgetting to update the ideal cycle time is an easy miss.

Example: revision D needs an extra fixing, so the real best cycle goes from 30 to 33 seconds. The line makes 400 parts in 240 minutes of run time.

Old ideal: 400 x 30 s = 200 min
Performance = 200 / 240 = 83.3%
New ideal: 400 x 33 s = 220 min
Performance = 220 / 240 = 91.7%
Same parts, same minutes. Only the ideal cycle changed, and it moved performance by 8.3 points.

The floor then chases a speed loss that does not exist. Keep the ideal rate per product and revision, with the date it was set, as described in the OEE by product guide.

Which gap is hurting you?

Wrong revisions reach the floor, or designs get lost between teams: that is a design control problem, so PLM comes first. Many variants, long engineering cycles and outsourced production all push this way.

The drawings are under control, but the lines lose time: plants that build to a customer's drawing or run stable products often sit here. CAD files on a controlled drive and an ERP BOM can carry you while the MES work pays first.

A customer or auditor asks which revision went into which serial: you need both systems and the link between them. Complex engineered and regulated products usually end up here.

A small plant with few, stable products may need neither yet. That holds as long as revisions are controlled on paper and shop floor data is captured consistently.

Where engineering changes leak

  • Treating engineering release as shop release. Approved in PLM does not mean the floor has the parts, the tools or the training. Add a manufacturing readiness step.
  • Paper copies at the station. The MES shows revision D while a laminated sheet on the wall still shows revision C.
  • No feedback path. Operators find the same fit problem every week, and engineering never hears it. Send nonconformance data upstream, then run root cause analysis on it.
  • Comparing as-designed to as-built by hand. If a part has been substituted, that deviation should be a record, not a note on a traveller.
See it live in Fabrico

Once a new revision reaches the line, what you want to know is how it runs. Fabrico is a light MES for OEE: it shows stops, speed and counts live from your machines, with OEE per line and shift, so a change that slows the line is visible. See how Fabrico's light MES for OEE works.

What people ask next

Is PLM the same as ERP?

No. PLM manages how a product is defined and changed. ERP manages orders, stock, purchasing and cost for that product, and it usually receives the released BOM from PLM. The what is MES guide shows where the MES sits under the ERP.

What is the difference between EBOM and MBOM?

The engineering BOM lists parts by product structure and function. The manufacturing BOM adds how it is really built: sub-assemblies, kits, packaging and consumables, in build order. An MES normally works from the manufacturing version.

How does the MES know which revision to build?

The order carries the revision, or the MES applies an effectivity rule by date, lot or serial. Scanning parts at the station then confirms the match, which feeds MES traceability.

What is a digital thread?

It is the linked record from design through planning and production to service, so one serial traces back to its revision and forward to its build data. PLM and MES each hold part of it. Models that run on this data are covered in MES vs digital twin.

Should work instructions live in PLM or MES?

Author them where the process engineers work, which is often PLM or a dedicated tool, and display them through the MES at the station. What matters is one master copy, a release step and no loose paper.

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 traceability →

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