MES Software: Vendors, Features & Costs Compared 2026
MES software compared: vendors, functions per VDI 5600, costs (cloud vs. on-premise) and implementation. Honest market overview 2026.
Gemba (現場) is Japanese for "the real place" — in manufacturing, it means the shop floor: the exact location where products are made, machines run and value is created. The Gemba principle, formalised by Taiichi Ohno at Toyota, states that you cannot understand a production problem from a conference room. You have to go where the work happens, observe with your own eyes and talk to the people doing the work. In Lean production, Gemba is not a technique — it is a mindset. And in 2026, the question is no longer whether you should go to Gemba, but what data you bring with you when you get there.
A Gemba walk is not a factory tour. It is not an audit. It is not a management inspection. It is a structured observation discipline with a specific purpose: understand the current state of the process, identify waste and support the people doing the work. Here is the practitioner sequence:
| Step | Action | What to do | Common mistake |
|---|---|---|---|
| 1 | Define the theme | Choose one focus per walk: changeover time, scrap at station 4, material flow between press and assembly. Never try to observe "everything." | Walking without a theme → you see everything and learn nothing. |
| 2 | Prepare with data | Review the MES dashboard before leaving the office: current OEE, downtime Pareto, alarm history, scrap rate for the theme area. Arrive with a hypothesis, not a blank mind. | Going to Gemba "open-minded" without data → you default to confirming what you already believe. |
| 3 | Observe the process | Stand and watch for at least 10–15 minutes. Follow the product, not the person. Note what actually happens vs. what the standard work document says should happen. | Walking too fast — the Gemba walk becomes a Gemba run. You miss the waiting time, the workarounds, the micro-stops. |
| 4 | Ask, don't tell | Talk to operators: "What makes your job harder today?" "What happens when this alarm fires?" "Why is this material staged here?" Listen more than you speak. | Giving instructions on the spot — this turns the walk into an audit and operators stop telling the truth. |
| 5 | Compare observation vs. data | Does what you saw match the MES data? If the dashboard shows 95 % availability but you witnessed 3 micro-stops in 15 minutes, something is wrong — either the data or the threshold definition. | Trusting only the data or only the eyes. The power of Gemba is in the gap between the two. |
| 6 | Document findings | Record 3–5 specific observations with location, time and context. Not "changeover is slow" but "changeover on press 7, order 48291→48295, took 42 min. Internal setup not separated from external." | Vague notes that cannot be acted on. If you can't assign a root-cause investigation to it, don't write it down. |
| 7 | Follow up | Present findings in the next shopfloor management meeting. Assign actions. Close the loop in the following walk. | Observing without follow-up — operators notice immediately and stop engaging. "Management walks through, nothing changes." |
Frequency: the Lean standard is daily for the production manager, weekly for the plant manager. At Neoperl, the structured combination of Gemba observation with PLC alarm data correlation — operators explaining what they see, the system confirming what it measured — identified that 4 alarm codes accounted for 80 % of all downtime events. Neither the data alone nor the observation alone would have surfaced that insight.
This is the question that defines modern shop floor management. Traditional Gemba is physical: you walk, you observe, you talk. Digital Gemba is the real-time data layer that makes every walk more effective — and extends Gemba to locations you cannot physically visit.
| Dimension | Physical Gemba | Digital Gemba (MES dashboard) | Combined (best practice) |
|---|---|---|---|
| What you see | Operator behaviour, material flow, workarounds, body language, safety hazards | OEE trend, downtime Pareto, alarm history, cycle time distribution, scrap rate | Context: "The alarm data says bearing alarm #4017 fired 12 times today. Show me — what happens when it fires?" |
| Frequency | Daily or weekly, limited by physical presence | Continuous, 24/7, all shifts, all plants | Digital continuous monitoring → physical walk triggered by data anomalies |
| Blind spots | You see 15 min of a 480 min shift. You miss night shift entirely. | You see numbers but miss the why. A 5 % performance drop is a number — the reason is on the floor. | Minimal — data covers time; observation covers cause. |
| Multi-plant | Impossible for remote plants | Full visibility across all connected plants | Digital Gemba for remote plants, physical Gemba for home plant + periodic visits to remote sites |
At Meleghy Automotive — 6 plants across Germany, Czech Republic and Hungary — the COO cannot walk every shop floor every day. The SYMESTIC Cloud MES provides digital Gemba across all plants: one dashboard showing OEE, downtime and alarm patterns for every press line in every plant. When the data shows an anomaly at Brandýs, the local team conducts the physical Gemba walk. The COO sees the same data remotely and can ask the right questions in the morning call. That is the practical integration of physical and digital Gemba.
Ohno's three Gemba principles are simple, but they are violated in most plants every day:
Without an MES, the Gemba walk is observation + conversation. Powerful, but limited to what happens while you are standing there. With an MES, the walk gains a time dimension: you can see what happened before you arrived, compare today to last week and validate observations against historical data.
How often should a Gemba walk happen?
Daily for the production manager (15–20 minutes, one theme). Weekly for the plant manager (30–45 minutes, cross-area). Monthly for the operations director. The key is discipline, not duration. A 10-minute walk every day beats a 2-hour event once a quarter. At Brita, daily shopfloor visibility — supported by digital signal capture on automated assembly lines — made the daily Gemba rhythm practical because the data pre-filtered where to focus.
What is the difference between a Gemba walk and a management audit?
Intent. An audit checks compliance against a standard: "Is the control plan followed? Are the gauges calibrated?" A Gemba walk seeks understanding: "What is actually happening? What makes this process hard? Where is the waste?" Audits are periodic, checklist-driven and judgemental. Gemba walks are frequent, curiosity-driven and supportive. Mixing the two destroys trust — operators will never tell the truth to someone who is scoring them.
Can you do Gemba remotely?
Partially. A Cloud MES gives you digital Gemba — real-time visibility into machine status, OEE, alarms and order progress across multiple plants. At Carcoustics, 500+ machines across 7 countries are visible on a single dashboard. That is remote Gemba for the data layer. But it will never replace standing at the machine, watching the operator, and noticing that the material bin is in the wrong position. Remote digital Gemba identifies where to look. Physical Gemba reveals why.
Related: Kaizen · Lean Production · Shopfloor Management · OEE Explained · MES: Definition & Functions · Muda (7 Wastes)
MES software compared: vendors, functions per VDI 5600, costs (cloud vs. on-premise) and implementation. Honest market overview 2026.
OEE software captures availability, performance & quality automatically in real time. Vendor comparison, costs & case studies. 30-day free trial.
MES (Manufacturing Execution System): Functions per VDI 5600, architectures, costs and real-world results. With implementation data from 15,000+ machines.