What is MES? The Real-Time Data Capture Layer

What is MES?

Yesterday we talked about what ERP cannot do. It is perfect for finance and inventory management, but insufficient for shop-floor operations. So after a work order is issued, who measures how much time that part actually spent, where it stopped, and how many errors occurred?

The answer is MES.

MES (Manufacturing Execution System) is the layer that captures every second, every stoppage, and every loss from the moment a work order opens until it closes on the production floor in real time.

The Real Life of a Work Order

Let’s follow a work order:

09:15 — Work order “M-2024-001” goes to the shop floor. An operator picks it up. ERP says estimated time is 4 hours. Standard machine is #5.

09:20 — The operator begins setup. For example: die change, opening checks, material feed. MES records the start of this work.

09:40 — The machine runs a trial. The first sample comes out. The dimension is wrong when checked. Adjustment happens. MES records this as 20 minutes of time loss (setup or standby time).

10:15 — The product begins running in series. MES records one entry for each part. The speed is 30 parts per hour.

11:00 — Machine #5 breaks down. Tool failure; repair takes 45 minutes. During that time, the operator cannot produce 50 parts. MES records this as “downtime.”

11:45 — Repair is finished. The machine runs again. MES switches back to “production” mode.

12:45 — The work order target was 100 parts. 95 were produced; 5 came out defective. The operator says the work order is done. MES records the closure.

What Data Does MES Capture?

MES gathers information like this by the hour:

Actual production time: The time the machine actually spent making product (production time). Example: 3.5 hours.

Setup and preparation time: Time the machine spent getting ready for production, but serial production had not yet started. Example: 0.5 hours.

Downtime: Time when the machine was stopped due to breakdown, maintenance, waiting, or quality issue. Example: 0.75 hours.

Standby time: Time when the operator was doing something else or waiting for material. Example: 0.25 hours.

Batch and scrap data: How many units were targeted, how many were made, how many came out defective, how many had to be discarded. Example: 100 target, 95 good, 5 scrap.

Quality control notes: Which parameters had problems. Example: “Diameter 0.2 mm too large; adjustment made.”

Resource consumption: Electricity, air pressure, material usage. Example: “10 kg material A; 5 kg material B.”

MES vs ERP: What’s the Difference?

Imagine the same work order through the eyes of two systems:

ERP eye: Work order M-2024-001 opened at 09:00, closed at 13:00. Estimated time 4 hours. Standard labor rate 50 TL per hour. Total cost = 4 × 50 = 200 TL. Work order closed; open the next one.

MES eye: Work order M-2024-001 opened at 09:00. Actual production time 3.5 hours. Setup time 0.5 hours. Downtime 0.75 hours (machine breakdown). Standby 0.25 hours. Total elapsed 4 hours, but only 75% active production. Scrap rate 5%. Actual cost = 3.5 hours × 50 TL = 175 TL. However, with 5 parts scrapped, each good part absorbed 175 / 95 = 1.84 TL in labor cost.

One is a record; the other is finance. But MES belongs to the shop floor manager. He can understand the real reason the machine sat idle: was it a breakdown? Material shortage? Operator skill?

Who Needed MES?

In demand-driven manufacturing, every order brings surprises. An operator may be inexperienced. A machine may not have been serviced. A recipe changed, but the shop supervisor forgot to mention it. Result: the work order takes much longer than planned, error rates are high, cost estimates are wrong.

Without MES, why can’t these problems be understood? Because the shop manager keeps a notebook for each machine (or no notebook at all). Data lives on paper, in the supervisor’s head, in small notes. At day end, week end, month end, these are manually entered into the system. By then, the operator has forgotten, the supervisor misremembered the time.

If MES exists, the operator touches a tablet or phone at the machine before starting: “Work M-2024-001 starting.” It is recorded instantly. If the machine breaks down, the operator says “Machine breakdown, M3 issue,” and the system records it. When the job ends, “Job closing, 95 good, 5 scrap” goes to the server immediately.

The shop manager can see this data on screen at lunch break. At 11:00, he knows why machine M5 broke down, how long the repair took, how many parts were not produced during that hour, and whether another machine can catch up. He has all the real numbers.

Why Is MES Alone Not Enough?

MES shines in operational detail. But MES has a limit: it only collects data from the machine floor. If the work order design is wrong (recipe incomplete, route not written down), MES cannot fix it. If quality control makes a bad decision when a defect arises, MES cannot override it. If delivery is delayed after production, MES does not know this.

For these, you need a bigger coordination layer that wraps MES. A layer that orchestrates every decision, quality check, resource, and piece of information from design to disposal.

This layer is called MOM (Manufacturing Operations Management).

Tomorrow we’ll discuss MOM.