MES: the factory's missing middle

Where MES sits — and why the gap exists

Industry stacks a factory into levels (the ISA-95 / Purdue model). The bottom reacts in milliseconds; the top plans in months. MES is Level 3 — the translator that takes a business order from above and turns it into executed, measured production below. Tap a level to see who lives there and what it cares about.

MES is one room. MOM is the house.

Here's the acronym that trips up everyone who just learned "MES". MOM — Manufacturing Operations Management — is the proper name for the whole of Level 3, not a rival to MES. ISA-95 Part 3 defines it as the activities that coordinate personnel, equipment and material in manufacturing, and splits it into four domains. MES is the production one. That's the entire relationship: MOM is the scope; MES is the room you already toured.

⚠️ Now the genuinely nasty part — "MOM" means two different things, and nobody warns you:

Which one is meant? Look at what's next to it. Beside ERP and MES → the house. Beside production, quality and inventory → the maintenance room. To avoid the whole mess, many people write the four domains as POM · QOM · MOM · IOM and keep "MOM" for the house only.

And the question everyone actually asks — so is MES just MOM with a new sticker? Three honest answers, all in circulation:

So much for the shape of it. What does a MOM platform actually do all day? Four capabilities — and note how each one is only possible because the four domains share one data model instead of sitting in separate silos:

🔑 The thread running through all four: killing data silos. A bolt-on MES + a separate CMMS + a separate LIMS can each be excellent and still can't answer “does the fryer make more scrap in the week before a bearing fails?” — because no single system holds both halves. That question is the entire argument for MOM.

Every acronym, in plain words

MES drowns you in three-letter words on day one. Here's the whole vocabulary — tap any card to flip it from jargon to plain English. Come back here whenever a term trips you up later in the lesson.

The five questions MES answers

Strip away the jargon and an MES exists to answer five questions the PLC and ERP can't, all day, automatically:

The one number everyone quotes and few compute right

OEE — Overall Equipment Effectiveness — is the headline metric MES produces. It's three honest fractions multiplied together: Availability × Performance × Quality. Because they multiply, a "pretty good" 90% on each collapses to a mediocre 73% overall. Drag the sliders and watch where the losses go.

🎮 The Donut Line — a live MES, one shift

Here's the whole thing working. A work order drops in: make 600 glazed donuts. MES dispatches it to the line, watches the three machines, counts good and scrapped units, computes OEE live, and writes a traceable record. Press Start shift — then sabotage it: inject a breakdown, a slow-down, or a bad batch and watch each one bite a different part of OEE. This is what a clipboard can never do.

Every line in that black log is data MES captured automatically: a timestamp, a reason code, a lot number. At shift end it becomes the OEE scorecard and the traceability record — no clipboard, no "I think it was around 2pm."

A birth certificate for every unit

Traceability (a.k.a. genealogy) is MES's quiet superpower: for any finished unit, it can tell you every material lot, machine, operator, setting and timestamp that touched it — and run that backwards or forwards.

MES vs SCADA vs ERP — who does what

The three get confused constantly. The clean split is time horizon and question asked:

How MES talks up and down

MES is useless in isolation — its value is being wired to both neighbours. Two standards do the heavy lifting:

What the PLC programmer actually does

"MES reads the PLC" sounds magic until it's your job. It isn't magic — it's a tidy, deliberate handful of steps. You never let the MES poke random memory addresses; you build it a clean, named interface and publish exactly that. Here's the real recipe, in order.

// The MES interface block — the ONLY thing you publish
TYPE stMES_Interface :
STRUCT
    OrderID      : STRING;   // ← written by MES
    TargetQty    : DINT;     // ← written by MES
    OrderReady   : BOOL;     // ← MES: "new order is valid"
    OrderAck     : BOOL;     // → PLC: "got it, loaded"
    GoodCount    : DINT;     // → read-only to MES
    RejectCount  : DINT;     // → read-only
    MachineState : INT;      // → 0=idle 1=run 2=down
    FaultCode    : INT;      // → the downtime reason code
    CurrentLot   : STRING;   // → for genealogy
    Heartbeat    : BOOL;     // → toggles every scan = "I'm alive"
END_STRUCT
END_TYPE

The 11 things to remember

Tape this above the desk. If you remember nothing else about MES, remember these.

1. MES is Level 3 — the bridge between ERP's orders and the floor's signals.
2. MOM is all of Level 3 — production + quality + maintenance + inventory. MES is its production room. (And beware: "MOM" also abbreviates Maintenance Operations Management.)
3. OEE = Availability × Performance × Quality. They multiply, so losses compound fast.
4. World-class OEE ≈ 85%; unmeasured plants are often 40–60% (your hidden factory).
5. A downtime reason code turns "it stopped" into "why it stopped" — the key to improvement.
6. Genealogy / traceability shrinks a recall from a month to a batch. Often it's the law.
7. SCADA watches the machine; ERP runs the business; MES runs the order and proves it.
8. A work order + a routing = what to make and the steps to make it.
9. WIP is work-in-progress — MES tracks where every unit is between raw and finished.
10. ISA-95 / B2MML connects MES to ERP; OPC UA connects it down to the floor.
11. MES doesn't replace people — it replaces the clipboard, the whiteboard and the 5pm spreadsheet.