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.
Rolled Throughput Yield — RTY — is the probability that a single unit passes through every step of a multi-step process right the first time, without rework, without repair, without scrap, without any detour. It is calculated as the product of the First Pass Yield of each individual step:
RTY = FPY₁ × FPY₂ × FPY₃ × … × FPYₙ
The mathematical structure is trivial. The managerial consequence is not. RTY is the metric that separates plants that think they are running clean processes from plants that know they are. In twenty-five years of introducing MES and Six Sigma into automotive plants on four continents, the pattern has repeated more times than I can count: every individual department lead reports a healthy 95 % yield, the plant-level financials disagree, and nobody can explain the gap. RTY is the explanation.
The honest disclosure up front: RTY is not a metric that makes anyone's shift look good on day one. Its introduction typically drops the plant's reported "yield number" from something comfortable like 95 % to something uncomfortable like 72 %. The plant has not gotten worse — it has only started measuring honestly. The organisations that survive this moment and use the new number to drive improvement are the ones that get the multi-year benefit; the ones that quietly bury the RTY calculation because it makes people look bad are the ones that keep losing margin to the same problem for the next decade.
The single biggest source of confusion around RTY is that "yield" means at least four different things depending on who is asking, and the numbers diverge sharply. Clarifying the four before the calculation is the step that most Green Belt training rushes past and then pays for later.
| Metric | What it counts | What it hides |
|---|---|---|
| Final Yield | Units out of the process ÷ units in. | All rework, all in-line repairs, all internal scrap that gets replaced before end of line. |
| First Pass Yield (FPY) | Units passing one specific step right first time ÷ units entering that step. | Per-step view only. Says nothing about the chain. |
| Throughput Yield (TPY) | Same as FPY at a single step, expressed in defect terms (e-DPU). | Technically a sub-case of FPY; terminology used in DPMO/sigma-level work. |
| Rolled Throughput Yield (RTY) | Probability of one unit passing every step first time, end-to-end. | Nothing — this is the systemic truth. Which is why it is the one people avoid. |
A production line can show Final Yield of 95 %, FPY of 95 % at every station, and RTY of 59 % simultaneously — all three numbers correctly calculated from the same production week. The divergence is not an error. It is the signal that rework loops are absorbing a quarter of the plant's capacity without appearing on any individual department's scorecard.
The piece of RTY that every introduction gets right, usually without drawing the full managerial conclusion:
Ten process steps, each with a perfectly respectable 95 % First Pass Yield:
0.9510 = 0.5987 → RTY ≈ 60 %
Four out of every ten units touched the rework loop at least once. Every single department lead can truthfully report 95 %. The plant manager looks at the margin line and cannot reconcile it with the department reports. RTY is the reconciliation.
Tighten it further. Fifteen process steps at 98 % each — which feels almost aspirational:
0.9815 = 0.7386 → RTY ≈ 74 %
More than a quarter of the units still went through some form of correction. This is the piece of the Six Sigma argument that most people internalise once and then forget: long process chains make FPY expectations that sound reasonable become systemically inadequate. A twenty-step assembly process requires 99.5 %+ at every station to deliver 90 % RTY. The number of plants that actually run at that level is small, and most of them are in semiconductor fabrication.
The term Hidden Factory comes from Joseph Juran's Juran on Planning for Quality (1988). His definition — and it has not improved since — is the capacity a plant consumes on rework, repair, re-inspection, and correction of its own internal mistakes, which never appears as scrap in the financials because the units eventually ship. The Hidden Factory is the dark twin of the visible factory: same people, same machines, same square metres, different output. Visible factory output goes to customers. Hidden factory output is the plant rebuilding its own work.
Every plant has a Hidden Factory. The plants that know its size can manage it. The plants that don't know its size manage around it — budgeting headcount for rework without ever calling it that, scheduling extra shifts for "throughput" that is actually recovery, buying buffer inventory to absorb quality surprises. RTY is the number that measures the Hidden Factory's size, and the gap between Final Yield and RTY is its rough capacity cost. When Final Yield is 95 % and RTY is 72 %, roughly 23 % of the plant's touch labour is Hidden Factory — not visible anywhere in the P&L, but visible immediately in the cash conversion cycle and in the margin.
From three years as a Six Sigma Black Belt in automotive headliner manufacturing at Johnson Controls in Rastatt, roughly 2000–2003: headliners are the moulded interior roof panels in cars — substrate plus foam plus fabric, bonded under pressure, then trimmed, die-cut, accessorised with visors and handles, inspected, packed. On paper the process is ten to twelve discrete operations per unit depending on the variant. Every station had its own FPY measurement, and every station was at 96–98 %. The plant manager was proud. Then we ran the first honest RTY calculation as part of a DMAIC project, which meant counting every unit that entered a rework loop — re-trim, re-foam, re-inspect, re-pack — as a first-pass failure regardless of whether it eventually shipped. RTY came out at 73 %. Nearly one headliner in four had touched the correction loop at some point. Nobody wanted to believe the number at first. The instinctive response was "the calculation must be wrong, because our FPYs are all fine." The calculation was not wrong. The FPYs were all fine individually. The chain was not fine, because ten stations at 97 % compound to 74 %, and we were not a statistical aberration — we were the mathematics working correctly on a reasonable-sounding FPY assumption. Once the number was on the wall, the conversation changed. Instead of optimising each station in isolation we started looking at defect propagation — which first-station defects caused later-station rework — and the improvement work found leverage it had never found before. Within eighteen months RTY moved from 73 % to about 86 %, and almost all of the gain came from three upstream fixes that nobody had prioritised previously because the upstream stations looked "fine" on their own FPY. This is the managerial lesson RTY teaches that nothing else does: in a multi-step process, station-level optimisation is a local game that ignores compound effects. RTY forces the plant to play the global game. The reason it is unpopular at introduction is exactly the reason it is valuable — it refuses to let any single department declare victory while the plant as a whole is quietly bleeding.
The part of RTY that gets sloppy in almost every first attempt, and which determines whether the number is actually useful: the counting rules. "First pass" is an operational definition that has to be decided explicitly, not inherited from whoever set up the dashboard. The five edge cases that matter:
The discipline that makes RTY worth calculating: the counting rules are written down, agreed with operations and quality together, and applied consistently across periods. The discipline that makes RTY worthless: each station decides its own rules and the chain-level number becomes a number that every department can individually dispute.
RTY is the entry point into the classical Six Sigma metrics chain that leads to sigma level. The logic:
The practical value of the chain is less in the sigma-level number itself — that becomes a corporate ceremony more often than a management tool — and more in the comparability across very different processes. A chemistry batch process, a ten-station assembly line and an electronics surface-mount operation have almost nothing in common operationally, but their DPMO numbers are directly comparable. For a multi-plant Black Belt running global improvement programmes, this cross-process comparability is the reason sigma level survives as a concept despite its reputation for being abstract.
The point I argue for in my book "OEE: Eine Zahl, viele Lügen" (2025) and which applies directly here: the Quality component of OEE is usually calculated as Final Yield — good parts divided by total parts — which is exactly the metric that hides the Hidden Factory. A plant running Final-Yield-based OEE Quality can show a Quality rate of 95 % while its RTY is 72 %, and both numbers are correct under their own definitions. The result is an OEE that looks healthier than the plant actually runs. The fix is not to replace OEE Quality with RTY — the metrics serve different purposes and have different history — but to report them side by side, so that the gap between them becomes a visible management signal rather than an invisible capacity loss. In modern MES platforms this is a one-time configuration decision: both metrics are calculated from the same underlying event stream, and displaying them together costs nothing operationally but exposes the Hidden Factory permanently. See also OEE: definition, calculation & practice for the broader OEE framework this sits inside.
The tactical value of RTY that rarely makes it into training material: RTY falls before Final Yield falls. When a tool begins to wear, when a process drifts, when a new material lot behaves slightly differently from the qualification lot, the first visible effect is an increase in rework at one or two stations. Final Yield is unaffected because the reworked units still ship. RTY drops because the definition counts the rework events. A plant that watches RTY on a weekly or shift basis catches the tool-wear signal four to eight weeks before it becomes a scrap signal at the end of line, and the cost differential between "catch at tool-wear" and "catch at end-of-line scrap" is typically an order of magnitude. This is the single most valuable tactical use of RTY in day-to-day plant operations, and almost nobody takes advantage of it because Final Yield is the number on the dashboard and RTY is calculated monthly in the quality report, too late to intervene.
SYMESTIC captures RTY directly from the same production event stream that feeds OEE, with user-configurable counting rules for the five edge cases described above. First-pass events, rework events, re-test events, auto-retry events and station-level attribution rules are all explicit configuration, documented in the MES and consistent across reporting periods. RTY is displayed alongside Final Yield and OEE Quality on the shopfloor dashboards, so that the gap between the three is visible rather than hidden, and the production metrics module drives the weekly or shift-level RTY trend that surfaces tool-wear and process-drift signals before they reach end-of-line scrap. Integration with quality systems — the Böhme & Weihs CASQ-it connection at Meleghy is one concrete example where in-line inspection events feed directly into the RTY calculation — ensures that rework events detected by third-party quality systems are captured as first-pass failures rather than being invisible to the MES. The architectural principle is the same one that runs through the whole platform: the metric that makes the plant uncomfortable in week one is the metric that makes it measurably better in year two, and the job of the MES is to make that metric impossible to ignore.
What is the difference between RTY and First Pass Yield?
First Pass Yield (FPY) measures a single process step — units passing that step right first time ÷ units entering. Rolled Throughput Yield (RTY) is the product of every step's FPY and measures the probability of one unit passing the entire process right first time. FPY is a local view; RTY is the systemic view. The two diverge rapidly in long process chains: ten steps at 95 % FPY each produce an RTY of only 60 %, because the mathematics of multiplication is unforgiving.
Why is the 95 % example so misleading?
Because 95 % sounds acceptable at the station level. A plant manager hearing "every station runs at 95 %" feels reasonable comfort. The managerial instinct is "95 % overall" — but the correct calculation for ten stations is 0.9510 = 59.9 %. Four out of ten units touched the rework loop. The reason RTY is valuable is exactly that it translates station-level "reasonable" into chain-level reality, and the translation is usually unpleasant.
What is the Hidden Factory?
The term is from Joseph Juran's Juran on Planning for Quality (1988). The Hidden Factory is the capacity a plant consumes on rework, repair, re-inspection and correction of its own defects — output that never reaches a customer because it rebuilds what the plant has already built once. Every plant has one; the plants that know its size can manage it. The gap between Final Yield and RTY is approximately the Hidden Factory's size. If Final Yield is 95 % and RTY is 72 %, roughly 23 % of touch labour is Hidden Factory.
How is RTY related to sigma level?
Through the chain RTY → DPU → DPMO → sigma level. DPU ≈ −ln(RTY); DPMO = (DPU ÷ opportunities per unit) × 1,000,000; sigma level is read from the DPMO table. Six Sigma ≈ 3.4 DPMO, Four Sigma ≈ 6,210 DPMO. The practical use of the chain is cross-process comparability — very different manufacturing processes can be compared on the same DPMO scale — rather than the sigma number itself, which tends to become a corporate ceremony.
How often should RTY be calculated?
For strategic improvement work, monthly is enough. For tactical early-warning — catching tool wear, process drift, material-lot variation before they reach end-of-line scrap — RTY needs to be calculated weekly or per shift. This is its single most underused tactical value: RTY starts falling four to eight weeks before Final Yield falls, because rework precedes scrap. A plant that watches RTY on a shift basis catches problems an order of magnitude cheaper than a plant that watches only Final Yield.
Can RTY be measured without an MES?
Yes, but the counting rules become the limiting factor. Manual RTY calculation — spreadsheet from quality reports, plus the station-level FPY numbers — is always possible and is where most plants start. The problem is consistency: manual counting rules drift between shifts, departments and auditors, and the RTY number becomes a number that every department can dispute. An MES with defined event types (first-pass, rework, re-test, auto-retry, scrap, replacement) gives RTY the audit-trail consistency that makes the number stand up in management reviews. The MES does not change the mathematics, it changes the defensibility.
What is the most common mistake in RTY calculations?
Counting in-line re-tests, auto-retries and within-station rework as "first pass" rather than as failures of first pass. The effect is an RTY number that is five to ten percentage points higher than reality — comforting but useless. The fix is to write down the counting rules explicitly, agree them between operations and quality, and apply them consistently. The second most common mistake is attributing downstream-discovered defects to the discovering station rather than the originating station, which hides the true root cause location.
Related: OEE: definition, calculation & practice · MES: definition, functions & benefits · OEE software · MES software compared · Recipe management · Work plan · Change control · BOM explosion · Production metrics module · Process data module · Production control module · Automotive · Metal processing · Plastics processing · For operational excellence · For production managers · For COOs & plant managers. External reference: ASQ – Six Sigma resources (the American Society for Quality's public reference library on Six Sigma methodology and terminology).
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.