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.
TL;DR: Lean Production (Lean Manufacturing) is a management system for eliminating waste and creating continuous flow in manufacturing. Developed at Toyota in the 1950s, it is built on 5 principles (define value → identify value stream → create flow → establish pull → pursue perfection) and targets 8 types of waste (muda). Lean is not a project or a toolbox — it is a way of operating a factory. The single biggest reason Lean programs fail: they run on observation and opinion instead of data. When an MES automatically captures OEE, cycle times, and downtime reasons, the 8 wastes stop being theoretical categories and become quantified losses with a dollar value — every shift, on every line.
Table of contents
Lean Production (also called Lean Manufacturing) is a production management system that aims to maximize customer value while minimizing waste. It originated from the Toyota Production System (TPS), developed by Taiichi Ohno and Eiji Toyoda in the 1950s, and was popularized in the West by the 1990 MIT study The Machine That Changed the World by Womack, Jones, and Roos.
The core premise is simple: every activity in a factory is either value-adding (the customer would pay for it) or waste (the customer would not). Lean's job is to ruthlessly reduce the second category while protecting and enhancing the first. This applies to material flow, information flow, machine utilization, changeovers, quality processes, and every handoff in between.
Lean is not a toolkit you pick from. It is an integrated system where the 5 principles, the 8 wastes, and the Lean tools (JIT, Kanban, 5S, SMED, VSM, TPM) reinforce each other. Without all elements working together, Lean degrades into isolated workshops that fade within months.
| # | Principle | What it means | In manufacturing practice |
|---|---|---|---|
| 1 | Define value | Value is defined by the customer — not by the producer | Ask: would the customer pay for this step? If no, it's a candidate for elimination. |
| 2 | Map the value stream | Visualize every step from raw material to delivery and classify: value-adding, necessary non-value-adding, or pure waste | Value Stream Mapping (VSM) — the diagnostic tool of Lean |
| 3 | Create flow | Products move through the value stream without stops, buffers, or backflows | Reduce batch sizes, eliminate bottlenecks, synchronize cycle times across stations |
| 4 | Establish pull | Produce only when the downstream process (or customer) signals demand — not in advance | Kanban cards, supermarket systems, JIT delivery |
| 5 | Pursue perfection | No process is ever finished. Every day, there is something to improve. | Kaizen events, PDCA cycles, employee-driven improvement |
These five principles are sequential: you cannot create flow (step 3) if you haven't mapped the value stream (step 2). You cannot establish pull (step 4) if flow doesn't exist. And perfection (step 5) is not a destination — it is the commitment to repeat steps 1–4 continuously.
The 8 wastes are the core diagnostic framework of Lean. The original 7 wastes were defined by Taiichi Ohno; the 8th (unused talent) was added later in Western adaptations. The Japanese term is muda (無駄). Lean also recognizes mura (unevenness) and muri (overburden), but the 8 wastes are the primary elimination targets.
| Waste | What it looks like on the shop floor | How an MES makes it visible |
|---|---|---|
| 1. Overproduction | Making more than the customer ordered, earlier than needed | Plan-vs-actual comparison per order — overproduction quantified |
| 2. Waiting | Machine idle, operator waiting for material, process waiting for approval | Automatic downtime capture — waiting time classified by reason |
| 3. Transport | Unnecessary movement of material between stations, warehouses, plants | Order tracking shows material path — excess transport exposed |
| 4. Over-processing | Processing beyond customer requirements, tighter tolerances than needed | Cycle time analysis — processing time exceeding standard = over-processing |
| 5. Inventory | WIP buffers, safety stock, finished goods sitting unsold | Bidirectional ERP integration — order status + throughput time visible |
| 6. Motion | Unnecessary movement of people — searching for tools, walking to printers | Digital shift reports + SFM dashboards eliminate paper-based data entry |
| 7. Defects | Scrap, rework, warranty claims, sorting actions | Automatic quality rate per order — scrap quantified per machine, shift, product |
| 8. Unused talent | Operators reduced to data entry instead of problem-solving | MES automates data capture → operators spend time on improvement, not paperwork |
| Tool | Purpose | Which waste it targets |
|---|---|---|
| Value Stream Mapping (VSM) | Visualize end-to-end material and information flow; identify waste | All — the diagnostic tool |
| 5S | Organize the workplace: Sort, Set in Order, Shine, Standardize, Sustain | Motion, Waiting (searching for tools) |
| Kanban | Pull-based production control using visual signals (cards, bins, digital) | Overproduction, Inventory |
| SMED | Reduce changeover times (Single-Minute Exchange of Die) | Waiting (changeover downtime) |
| TPM | Total Productive Maintenance — operators own machine care | Waiting (breakdowns), Defects (process drift) |
| Jidoka / Andon | Built-in quality: machines stop on defect; visual signal for help | Defects, Over-processing |
| Heijunka | Level production volume and mix to create steady flow | Overproduction, Waiting (batch-and-queue) |
Each tool targets specific wastes. The mistake most companies make: deploying 5S or Kanban as standalone "Lean projects." Without the underlying principles (value stream thinking, pull, flow), individual tools produce isolated improvements that don't compound.
The original Toyota Production System was designed for a world of physical kanban cards, chalk boards, and visual signals. That worked in the 1960s at Toyota City. In modern manufacturing — with higher speeds, more product variants, multi-plant operations, and tighter margins — Lean without data is guesswork.
| Lean activity | Without MES | With MES |
|---|---|---|
| VSM: "Where is the bottleneck?" | Paper-based VSM done once, outdated in 2 weeks | Real-time cycle times per station — bottleneck visible on the dashboard, live |
| SMED: "Did changeover time improve?" | Stopwatch before, stopwatch after — one data point each | Automatic before/after comparison across 50+ changeovers — statistically valid |
| Kanban: "Is pull working?" | Physical cards — no visibility into flow disruptions between shifts | Order status + WIP tracking in real time — flow disruptions trigger alerts |
| SFM: "What was our biggest loss yesterday?" | Shift leader's memory | Pareto chart of downtime reasons on the SFM board — before the meeting starts |
SYMESTIC implementation example: At Neoperl, Lean improvement cycles were powered by SYMESTIC's automatic data capture. SPS-based alarm correlation revealed a pattern between specific PLC alarms and quality defects — a connection invisible without automatic data linkage. Result: 10 % fewer stoppages, 15 % less scrap, 15 % productivity gain — not from a one-time Lean workshop, but from daily data-driven countermeasures.
| Dimension | Lean | Six Sigma | Kaizen |
|---|---|---|---|
| Core idea | Eliminate waste, create flow | Reduce process variation statistically | Every day, everyone improves |
| Scope | System-level (entire value stream) | Process-level (specific problem) | Activity-level (daily improvement) |
| Speed | Weeks (Kaizen events) to months (VSM redesign) | Months per DMAIC project | Immediate — implement today |
| Data need | Medium — cycle times, lead times, OEE | High — statistical analysis, SPC | Low to medium — observation + KPIs |
| Relationship | The system-level framework | A specialist tool within the framework | The daily habit that sustains the framework |
These are layers, not alternatives. Lean provides the system view. Kaizen provides the daily habit. Six Sigma solves the hard statistical problems. CIP structures the improvement cycle. SFM provides the daily management rhythm. Together, they form Operational Excellence.
What is Lean Production?
Lean Production (Lean Manufacturing) is a management system for eliminating waste and creating continuous flow in manufacturing. Developed at Toyota in the 1950s, it is built on 5 principles and targets 8 types of waste (muda). The goal is to maximize customer value while minimizing everything that doesn't contribute to it.
What are the 8 wastes in Lean?
The 8 wastes (muda) are: Overproduction, Waiting, Transport, Over-processing, Inventory, Motion, Defects, and Unused talent. The first 7 were defined by Taiichi Ohno; the 8th was added in Western Lean adaptations.
What is the difference between Lean and Six Sigma?
Lean focuses on eliminating waste and creating flow across the entire value stream. Six Sigma focuses on reducing process variation using statistical methods (DMAIC). Lean is system-level; Six Sigma is process-level. Most mature manufacturers use both — often as "Lean Six Sigma."
How does an MES support Lean Production?
An MES provides the data that makes every Lean tool measurable: real-time OEE for bottleneck identification, automatic downtime classification for waste quantification, before/after comparison for improvement verification, and order tracking for flow monitoring.
How long does a Lean transformation take?
Lean is not a project with an end date — it is a permanent way of operating. First measurable improvements (from data visibility + targeted countermeasures) typically appear within 4–8 weeks. A mature Lean culture takes 2–3 years. The critical success factor is not speed — it is sustaining the daily rhythm.
The bottom line: Lean Production is not a workshop, a poster, or a toolbox. It is a way of seeing waste — everywhere, every day — and systematically eliminating it. The 5 principles provide the logic. The 8 wastes provide the diagnostic. The tools provide the method. And real-time data from an MES provides the evidence that turns philosophy into measurable results.
→ What is an MES? · → OEE Explained · → Kaizen · → CIP · → Six Sigma · → Shopfloor Management · → Operational Excellence
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.