What is a good OEE score for a manufacturing line?

World-class OEE is widely cited at 85 percent, which breaks down to roughly 90 percent availability, 95 percent performance, and 99 percent quality. Most discrete manufacturers actually run between 40 and 60 percent when they first measure honestly. A score of 60 percent means you have real room to improve without capital spend. Do not chase 85 percent blindly; a stable 70 percent with predictable output often beats a volatile 80 percent.

How do I calculate OEE from availability, performance, and quality?

Multiply the three rates: OEE equals availability times performance times quality. Availability is run time divided by planned production time. Performance is (ideal cycle time times total count) divided by run time, or actual rate divided by ideal rate. Quality is good count divided by total count. Example: 0.90 times 0.95 times 0.99 equals 0.846, or 84.6 percent OEE. The template computes each factor from your raw inputs so you never multiply the wrong cells.

Should planned downtime be included in the OEE availability calculation?

No. Planned downtime such as scheduled breaks, no-demand periods, and preventive maintenance is subtracted from calendar time to get planned production time, which is your denominator. Availability only counts unplanned stops like breakdowns and changeovers against that planned time. If you include lunch breaks as downtime, availability drops artificially and OEE loses meaning. Log planned stops separately in the notes column, not in the downtime reason-code log that drives the rate.

What is the difference between OEE and TEEP?

OEE measures effectiveness against planned production time, so it ignores hours you chose not to run. TEEP, Total Effective Equipment Performance, measures against all 8,760 calendar hours in a year and includes a utilization factor. A line at 85 percent OEE running two of three shifts has a TEEP near 57 percent. Use OEE to improve a running process; use TEEP when deciding whether to add a shift or buy another machine.

How do micro-stops and speed losses show up in OEE?

They hit the performance factor, not availability. Micro-stops under a few minutes usually go unlogged, so run time looks full but the part count is low. If your ideal rate is 60 parts per hour and you actually make 50, performance is 83 percent even with zero recorded downtime. Enter both ideal and actual run rate in the template so this speed loss surfaces instead of hiding inside an inflated availability number.

How often should I record OEE data on this spreadsheet?

Log by shift at minimum, so a three-shift plant produces three rows per machine per day. Shift-level granularity lets you compare night versus day performance, which often differs 10 to 15 points due to staffing and support. Roll the entries into the daily and weekly summary rows for trending. Recording once per day masks which shift is losing time, and recording per part is overkill unless you are running a formal short-interval control study.

Manufacturing Cost and Quoting

OEE Tracker Spreadsheet Template

Track Overall Equipment Effectiveness across availability, performance, and quality for any machine, line, or shift.

Overview

This OEE Tracker is for line supervisors, process engineers, and continuous improvement leads who need to measure Overall Equipment Effectiveness on a single machine, a line, or a specific shift. OEE multiplies availability, performance, and quality into one number, so a machine running at 90 percent availability, 95 percent performance, and 98 percent quality lands at about 84 percent. Eyeballing uptime hides which of those three factors is bleeding capacity, and a spreadsheet forces you to log the reasons.

You enter planned production time, then log each downtime event with a reason code, which drives the availability rate. Actual run rate against ideal run rate from your machine nameplate gives performance. Good parts divided by total parts produced gives quality. Those three rates feed the OEE cell automatically. Daily and weekly summary rows roll the shift entries up so you can see, for example, that changeover downtime and micro-stops together cost you 6 points of availability last week.

In a real workflow, run this every shift and review the weekly summary in your Monday production meeting. Sort downtime by reason code to target the biggest loss first, usually changeovers or unplanned stops. Use it to baseline a machine before a SMED or TPM project, then re-measure after. Pair it with the OEE Calculator on the site for a quick single-shift check, then log that result here to build the trend line over weeks.

What this template includes

Planned production time input
Downtime log with reason codes
Actual vs ideal run rate comparison
Good parts vs total parts produced
Auto-calculated OEE, availability, performance, and quality rates
Daily and weekly summary rows
Notes column for shift observations

Suggested use case

Use this on the shop floor to baseline equipment performance before an improvement project, or to document OEE trends for a monthly plant review.

How to use it

Enter planned production hours and any downtime events for each shift.
Log actual run rate and ideal run rate from your machine specs.
Enter total parts produced and rejected parts for the period.
OEE and its three components calculate automatically.
Review the weekly summary to spot patterns.

Frequently Asked Questions

What is a good OEE score for a manufacturing line?: World-class OEE is widely cited at 85 percent, which breaks down to roughly 90 percent availability, 95 percent performance, and 99 percent quality. Most discrete manufacturers actually run between 40 and 60 percent when they first measure honestly. A score of 60 percent means you have real room to improve without capital spend. Do not chase 85 percent blindly; a stable 70 percent with predictable output often beats a volatile 80 percent.
How do I calculate OEE from availability, performance, and quality?: Multiply the three rates: OEE equals availability times performance times quality. Availability is run time divided by planned production time. Performance is (ideal cycle time times total count) divided by run time, or actual rate divided by ideal rate. Quality is good count divided by total count. Example: 0.90 times 0.95 times 0.99 equals 0.846, or 84.6 percent OEE. The template computes each factor from your raw inputs so you never multiply the wrong cells.
Should planned downtime be included in the OEE availability calculation?: No. Planned downtime such as scheduled breaks, no-demand periods, and preventive maintenance is subtracted from calendar time to get planned production time, which is your denominator. Availability only counts unplanned stops like breakdowns and changeovers against that planned time. If you include lunch breaks as downtime, availability drops artificially and OEE loses meaning. Log planned stops separately in the notes column, not in the downtime reason-code log that drives the rate.
What is the difference between OEE and TEEP?: OEE measures effectiveness against planned production time, so it ignores hours you chose not to run. TEEP, Total Effective Equipment Performance, measures against all 8,760 calendar hours in a year and includes a utilization factor. A line at 85 percent OEE running two of three shifts has a TEEP near 57 percent. Use OEE to improve a running process; use TEEP when deciding whether to add a shift or buy another machine.
How do micro-stops and speed losses show up in OEE?: They hit the performance factor, not availability. Micro-stops under a few minutes usually go unlogged, so run time looks full but the part count is low. If your ideal rate is 60 parts per hour and you actually make 50, performance is 83 percent even with zero recorded downtime. Enter both ideal and actual run rate in the template so this speed loss surfaces instead of hiding inside an inflated availability number.
How often should I record OEE data on this spreadsheet?: Log by shift at minimum, so a three-shift plant produces three rows per machine per day. Shift-level granularity lets you compare night versus day performance, which often differs 10 to 15 points due to staffing and support. Roll the entries into the daily and weekly summary rows for trending. Recording once per day masks which shift is losing time, and recording per part is overkill unless you are running a formal short-interval control study.