Key takeaways
Short answer: A Pareto chart is a sorted bar chart with a cumulative percentage line that shows which few causes account for most of the total loss. In manufacturing, it is the primary tool for converting OEE data into action — sorting downtime reasons by impact so the team attacks the biggest losses first instead of whatever happened most recently. See also Control Chart vs Run Chart.
A Pareto chart has two elements:
The chart makes the 80/20 principle visible: usually a small number of categories account for most of the total. The cumulative line crosses 80% at the boundary of the vital few.
An OEE platform captures hundreds of downtime events per shift. Listing them as a table is overwhelming. Pareto sorts them by total downtime contribution and surfaces the vital few. The team picks the top bar and works on it.
Without Pareto, the typical maintenance response is to attack the most recent or most dramatic failure. With Pareto, the team attacks the cause that loses the most hours, even if it is a less visible micro-stop that just adds up.
By reason code. Total minutes lost per reason. This is the classic Pareto and the easiest to act on.
By asset. Total minutes lost per machine, line, or cell. Surfaces the bad-actor assets that consume disproportionate maintenance and OEE budget.
By time pattern. Loss by shift, day of week, or part-of-shift. Surfaces patterns invisible in aggregate (e.g., 70% of losses in the first hour after lunch).
The three lenses are not substitutes. A single asset with one dominant reason looks different than a reason that distributes across many assets — and each pattern calls for a different fix.
The discipline is choosing one cause per cycle, not all of them. Solving the top bar usually moves enough mass that the next chart looks different.
1. Pareto as decoration. The chart on the wall that nobody acts on. The point is to pick the top bar and assign someone to fix it.
2. Aggregating too long a window. A six-month Pareto smears patterns. A weekly Pareto catches what changed.
3. Reason codes that are too granular. 50 reason codes produce 50 thin bars. Aim for 10-15 meaningful categories per axis.
4. Solving the easy bar instead of the top bar. Comfortable wins do not change the Pareto. Solving the top bar does.
A modern OEE platform auto-generates Pareto charts by reason code, asset, and time pattern, with configurable time windows. The good ones let you click a bar to drill into the underlying events with timestamps, operator notes, and linked work orders.
Fabrico's OEE module produces Pareto by reason code, asset, and shift in real time, with click-through to the underlying events and linked CMMS work orders. The focus is the top bar, every shift.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
From Vilfredo Pareto, an Italian economist who observed that 80% of Italy's land was owned by 20% of the population. The pattern repeats in manufacturing losses, quality defects, and customer complaints.
No. Sometimes it is 70/30 or 90/10. The principle is that a small number of causes account for most of the effect.
Aim for 10-15 categories that are mutually exclusive and meaningful to the team. Too few makes Pareto trivial; too many makes it noisy.
By total time for OEE. A reason code that happens 50 times but lasts 30 seconds each is less important than a reason code that happens 5 times but lasts 30 minutes each.
It shows where the 80% point is. Categories to the left of the 80% line are the vital few; categories to the right are the trivial many.
Connexion
Blog
