OEE (Overall Equipment Effectiveness)
- Formula
- Availability × Performance × Quality
- Typical range
- 40 to 60% typical; 85% is world-class discrete manufacturing
- Direction
- Higher is better
Open the Calculator Generate the DAX
OEE measures how much good product a machine actually made versus what it could have made running full speed, all the time, with zero defects. It multiplies three losses together so nothing hides:
- Availability = run time ÷ planned production time. Captures downtime losses (breakdowns, changeovers, material shortages).
- Performance = (units produced × ideal cycle time) ÷ run time. Captures speed losses (slow cycles, minor stops).
- Quality = good units ÷ total units. Captures scrap and rework.
What Good Looks Like
The often-quoted “world class is 85%” number comes from mature discrete manufacturing. Most plants measuring honestly for the first time land at 40 to 60%, and that is normal. A plant that jumps from 45% to 60% has effectively found a third more capacity without buying a single machine.
Watch for inflated OEE: excluding changeovers from planned time, using padded ideal rates, or measuring only bottleneck-friendly shifts. An OEE above 90% usually means the calculation is flattering someone.
OEE in Power BI (DAX)
With an hourly production fact (units, target rate, downtime minutes, scrap):
Availability % =
DIVIDE (
SUM ( fact_production_hourly[run_minutes] ),
SUM ( fact_production_hourly[planned_minutes] )
)
-- Minutes the units would take at the line's ideal rate. Iterating the
-- distinct rates, not the fact rows, lets the storage engine sum units
-- per rate in one pass; DIVIDE then runs once per rate, not once per row.
Ideal Minutes Produced =
SUMX (
VALUES ( dim_line[ideal_rate_uph] ),
DIVIDE (
CALCULATE ( SUM ( fact_production_hourly[units_produced] ) ) * 60,
dim_line[ideal_rate_uph]
)
)
Ideal Minutes Good =
SUMX (
VALUES ( dim_line[ideal_rate_uph] ),
DIVIDE (
CALCULATE (
SUM ( fact_production_hourly[units_produced] ) - SUM ( fact_production_hourly[scrap_units] )
) * 60,
dim_line[ideal_rate_uph]
)
)
Performance % =
DIVIDE ( [Ideal Minutes Produced], SUM ( fact_production_hourly[run_minutes] ) )
Quality % =
DIVIDE ( [Ideal Minutes Good], [Ideal Minutes Produced] )
-- Equals Availability x Performance x Quality, and still adds up across lines
OEE % =
DIVIDE ( [Ideal Minutes Good], SUM ( fact_production_hourly[planned_minutes] ) )
Every component is in minutes at the line’s ideal rate, so the three still multiply to OEE when lines with different rates roll up to a plant. On one line, Quality % here is exactly good units ÷ total units. Across lines it weights each line by its time rather than its part count, which is what keeps the product honest.
The column names are examples. If your fact stores downtime rather than run and planned minutes, as the demo dataset does, planned minutes are the hours times 60 and run minutes are planned minus downtime.
Keep the three components on the same visual as OEE itself. A single OEE number tells a plant manager something is wrong; the three components tell them where.
Common Mistakes
- Rolling OEE up in units. A plain average of line OEEs weights a slow line the same as your biggest producer, and multiplying components summed in units is not much better: it weights each line by part count, not by time. Sum every component in minutes at ideal rate, as the DAX above does. On the demo data the unit-pooled company figure overstates by 2.3 points; see OEE across lines.
- Ideal rate drift. If engineering quietly lowers the ideal rate, OEE “improves” while output doesn’t. Version your rate table.
- Mixing planned and unplanned downtime. Both matter, but they belong to different owners: scheduling owns changeovers, maintenance owns breakdowns.
OEE Calculator
Runs in your browserResult
DAX Generator
Use My Own Table and Column NamesUpdates as You Type
Availability % =
DIVIDE (
SUM ( fact_production_hourly[run_minutes] ),
SUM ( fact_production_hourly[planned_minutes] )
)
-- Minutes the units would take at the line's ideal rate. Iterating the
-- distinct rates, not the fact rows, lets the storage engine sum units
-- per rate in one pass; DIVIDE then runs once per rate, not once per row.
Ideal Minutes Produced =
SUMX (
VALUES ( dim_line[ideal_rate_uph] ),
DIVIDE (
CALCULATE ( SUM ( fact_production_hourly[units_produced] ) ) * 60,
dim_line[ideal_rate_uph]
)
)
Ideal Minutes Good =
SUMX (
VALUES ( dim_line[ideal_rate_uph] ),
DIVIDE (
CALCULATE (
SUM ( fact_production_hourly[units_produced] ) - SUM ( fact_production_hourly[scrap_units] )
) * 60,
dim_line[ideal_rate_uph]
)
)
Performance % =
DIVIDE ( [Ideal Minutes Produced], SUM ( fact_production_hourly[run_minutes] ) )
Quality % =
DIVIDE ( [Ideal Minutes Good], [Ideal Minutes Produced] )
-- Equals Availability x Performance x Quality, and still adds up across lines
OEE % =
DIVIDE ( [Ideal Minutes Good], SUM ( fact_production_hourly[planned_minutes] ) )