OEE Loss Tree vs Pareto: When to Use Each for Improvement Targeting

Key takeaways

• A loss tree is a hierarchical breakdown of every loss feeding the OEE gap.
• A Pareto ranks losses by impact and highlights the vital few.
• The tree gives completeness; the Pareto gives focus.
• Mature OEE programs use the tree to find candidates and the Pareto to prioritise.

Short answer: An OEE loss tree maps every contributor to your shortfall from world-class — Availability, Performance, and Quality losses broken down to specifics. A Pareto ranks those losses by impact so improvement targets the biggest. Use the tree so nothing is missed; use the Pareto so effort goes where it pays. See also oee for manufacturing.

What a loss tree shows

• Top: world-class OEE target.
• Branches: Availability, Performance, Quality loss.
• Leaves: breakdowns, changeover, micro-stops, speed loss, scrap, rework.

What a Pareto shows

• Losses sorted by impact, biggest first.
• The cumulative 80/20 line.
• The vital few to attack now.

When to use the tree

For diagnosis on a new line, executive communication of the gap, and making sure no loss category is invisible.

When to use the Pareto

For prioritising the next improvement, reporting to the operations team, and tracking how the loss mix shifts over time.

Common mistakes

Pareto without a tree: you optimise what you measure and miss unmeasured losses. Generic reason codes: the Pareto ranks "Other" first and tells you nothing.

See how Fabrico captures this automatically on your lines — explore OEE for manufacturing or book a demo.

Related reading

• oee for manufacturing
• plant availability vs equipment availability

Frequently asked questions

Should I use both?

Yes — tree for completeness, Pareto for focus.

How often update the Pareto?

Weekly is common; the tree quarterly.

Why is my top Pareto bar "Other"?

Reason codes are too generic — fix the codes.

Who builds the loss tree?

Operations and engineering together.