I’ve sat in hundreds of Monday morning ops reviews. Every single one follows the same script.
Someone pulls up the OEE numbers. “Line 3 ran 72% last week.” Everyone nods. That part is fine. The number is the number.
The problem starts thirty seconds later, when someone asks: “Why?”
Production says it’s maintenance. Maintenance says it’s operators. The scheduler says it was a brutal product mix. The plant manager just wants someone to tell him which of these is actually true and what to fix first.
Nobody can. And that’s the real problem.
The distrust isn’t about the number
The distrust in manufacturing isn’t about OEE being wrong. It’s about OEE not telling you enough.
OEE tells you what happened. It was never designed to tell you whether you can trust what happened, whether it’s getting better or worse, or who owns the fix.
When a shift supervisor looks at “78% OEE” on Line 3, three questions go unanswered:
- Was last week 78% too? Or was it 84%, and 78% is the start of a decline nobody will notice for three more weeks?
- Is 78% reliable? Or is it a 90% Monday / 65% Wednesday operation that averages out to “fine”?
- Can you plan around 78%? Can the planner commit to customer orders based on this line’s capacity, or are they gambling on variance?
Same OEE, different plant
Take two lines, both reporting 62% OEE.
Line A hits 60–64% every shift. Low variance. Stable trend. The planner can commit production orders against this line and sleep at night. It’s below target, but it’s predictable below target.
Line B swings between 45% and 80%. The average lands at 62%, but no individual shift looks anything like it. The planner who treats this line’s capacity as reliable will be wrong more often than right.
Same OEE. Completely different operational realities. One is a scheduling anchor. The other is a planning liability generating overtime, expediting costs, and missed commitments.
Standard reporting treats them as equivalent. A planner treating them the same will be wrong more often than right.
What TRI adds
The Throughput Reliability Index layers three dimensions on top of existing OEE data:
Throughput — how close is the line running to its target? This is the dimension OEE already captures. The foundation.
Reliability — how consistent is that performance shift after shift? A line averaging 75% that swings between 60% and 90% is a planning nightmare, even though the average looks acceptable. More variance always reduces the score.
Direction — is performance trending up, stable, or quietly deteriorating? A stable 68% and a declining 78% require completely different responses. But a snapshot treats them as comparable.
When you combine these three factors, every line falls into one of four operating states: Strong & Dependable, Strong but Unstable, Weak but Improving, or Weak & Deteriorating. Each state carries a different implication for how you manage, invest in, and plan around that line.
What this looks like with real data
In a recent assessment of a food manufacturing facility — four lines, 83 days of MES data — we found:
- Two lines with nearly identical OEE (~31%) that were 27% apart in reliability. One was the most dependable line in the plant. The other included weeks swinging between 43.9% and 11.3%.
- A line that appeared “about the same as usual” in standard reporting but was actually in crisis — output essentially random noise, CV of 0.721, deteriorating week over week.
- $1.4M in annualized exposure across four lines that no existing report surfaced.
- A single highest-return intervention ($280K annual recovery at $15–25K cost) that OEE-based prioritization would have sent CI to a completely different line.
Same MES export. Same data your team already collects. Completely different operating decisions.
Where the variance lives matters more than the average
TRI doesn’t just measure instability. It decomposes it. Where is the variance coming from?
- Within-shift variance = equipment or material problem. Maintenance owns it.
- Between-crew variance = training or standard work problem. Production owns it.
- Schedule-induced variance = changeover or product mix problem. Planning owns it.
Same Pareto bar. Different root cause. Different fix. Different owner.
This is how TRI turns a 45-minute blame argument into a 15-minute review of what changed, where the variance lives, who owns the fix, and what it’s worth.
The Monday meeting should be 15 minutes
OEE is a good starting point. It captures availability, performance, and quality into a single number. But it was designed for measurement, not diagnosis.
TRI adds the layers that diagnosis requires: reliability measurement, variance decomposition that identifies the actual driver, direction detection that catches deterioration before it becomes a crisis, and economic translation that connects every finding to the P&L.
It does not replace Lean, TPM, digital twins, or OEE. It tells you where to apply them first.
A plant does not deploy formulas. It deploys routines. TRI is the signal that tells those routines where to point.
If you want to see what your OEE data is hiding, start with the 10-day assessment. Send 90 days of shift-level data. Get back TRI baselines, variance decomposition, financial exposure by line, and a prioritized intervention plan. If it doesn’t surface at least one decision your current reporting missed, you pay nothing.