Blog / OEE
OEE · Guide

Plant Manager OEE KPIs: What to See Each Week

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

A plant manager needs five OEE numbers a week: OEE per line against its four-week trend, the top three losses in minutes on the worst line, plan attainment at the constraint, the share of stop time with no known cause, and the actions still open. Those five fit on one page and lead straight to a decision.

Why so few

A plant manager's job with OEE differs from a shift lead's. The lead needs today's stops, while the manager needs to see where a decision or some support would change the result.

A wall of charts hides that. So each of the five numbers below is here because it leads to a specific action, and if a number leads to nothing, it stays off the page.

Number 1: OEE per line, with a trend

Show each line's OEE for the week next to its four-week trend. The direction tells you more than a single week, since one week can be moved by the product mix alone.

Then add a plant figure only if you need one, and weight it by time. A simple average gives a short line the same voice as a long one, and how to average OEE across machines explains why.

LinePlanned minGood minOEE4-week trend
Line 17,2005,11271.0%Flat
Line 27,2004,17658.0%Falling
Line 31,8001,47682.0%Rising
Plant16,20010,76466.4%
Example with hypothetical numbers. The simple average of the three percentages would say 70.3%, which flatters the plant by about 4 points.

Do not rank the lines against each other as a league table. They run different products, so their mixes and their targets differ too.

Number 2: top three losses, in minutes

For the line that matters most this week, show the losses as minutes, ranked from largest. Minutes add up and can be compared, while percentages of percentages confuse a meeting.

Example: line 2 had 7,200 planned minutes and 4,176 good minutes, so it lost 3,024. The picture below is what a manager should see.

Slow running, short stops940 min
Changeovers820 min
Waiting for material610 min
Breakdowns420 min
Scrap (as time)234 min
Bars show each loss as a share of the 3,024 lost minutes. The top three make up 78% of the loss.

This view also hands each loss to its owner. Changeovers may need engineering time, material waits belong with planning, and the speed loss needs someone at the line to see it.

The OEE loss tree shows how those minutes connect, and a downtime Pareto chart is the usual way to draw them.

Number 3: plan attainment at the constraint

OEE says how well the line ran, and plan attainment says whether the customer got the product. Read the two together, especially at your bottleneck.

A point of OEE at the constraint adds output to the whole plant. A point elsewhere may just add stock, so give the constraint the top row of the page.

Number 4: unknown stop time

This is the check on all the other numbers. If a big share of stop time has no cause, the Pareto above is only a partial picture, and any plan built on it could be wrong.

This gap can be large. In a study of 884 machines in 23 Swedish companies (Hedman et al., 2016), unclassified losses were about 19% of scheduled production time, more than half of all recorded loss time, and that was with automatic measurement.

So track the share of stop minutes coded as unknown or other, per line. If it starts to rise, fix the logging first, and unknown downtime shows you how.

Number 5: actions open and overdue

The last number is not an OEE figure, and it is what makes the others matter. How many actions were agreed from past reviews, how many are done, and how many are late?

A review with stable OEE and a long overdue list needs a different talk from one with a falling OEE and no list at all. Use the format in the OEE improvement action plan.

Run the review in 20 minutes

1
Check trust, 2 minutes
Unknown stop share per line. If it jumped, treat the rest with care.
2
Read the trends, 5 minutes
Which line moved, and has anything changed in mix or plan?
3
Pick one line, 8 minutes
Usually the constraint or the falling line. Go through its top three losses.
4
Decide, 5 minutes
One action per loss, one owner, one date. Close the old actions that are done.
Same order each week. The agenda stays short because the page has only five numbers.

A short weekly review works best when the daily routine carries the detail. The daily production meeting handles yesterday, and this review handles the pattern.

What to leave off the page

  • Shift rankings. Crews start to defend themselves and stop reporting. If shifts differ, ask why OEE differs between shifts at the line.
  • Small weekly moves. A change of one point is usually noise, so react to the trend.
  • A plant-wide OEE goal copied from elsewhere. The 85% figure usually traced to Nakajima is a reference from TPM, and is 85% OEE realistic explains why your own trend comes first.
  • Every machine on every line. Show the line result, and drill down only when the review needs it, as in line OEE vs machine OEE.
  • Availability, performance and quality on every line. Keep them one click away, and open them for the line under review.

Signals and what they ask of you

Each pattern suggests a different role for the manager. Most of them ask for a decision about priority, not for a lecture to the line.

  • OEE falls and unknown stops rise: ask for logging discipline before any new project.
  • OEE is steady and attainment falls: look at the plan, the mix and material supply.
  • Same top loss for three weeks: the owner may need budget, engineering time or authority.
  • Actions overdue on many lines: too many are open, so cut the list to what people can really finish.

Where to go next

See OEE dashboard examples for layouts, and production KPIs if you also need the wider measures. A spreadsheet can handle all five numbers at first, and the OEE tracking template has a starting layout.

See it live in Fabrico

This one-page view depends on stops and causes that are captured as they happen. With Fabrico, a light MES for OEE, stops, speed and counts come live from the line, operators tag the cause at the line, and OEE shows per line and shift. See how Fabrico shows OEE per line and shift.

What people ask next

What OEE KPIs should a plant manager track?

OEE per line with its trend, the top three losses in minutes, plan attainment at the constraint, the share of stop time with no cause, and open actions. Everything else can stay one click away.

How often should a plant manager review OEE?

Weekly works well for patterns and priorities, with the daily meeting handling yesterday's stops. Monthly is too slow to act on, and hourly belongs to the line.

Should plant OEE be a single number?

It can be, if it is weighted by planned time, but it hides more than it shows. Decisions come from the line-level figures, as how to average OEE across machines explains.

What OEE target should a plant manager set?

Base it on each line's own baseline and top losses, since products and processes differ. How to set OEE targets gives the method.

Should OEE be tied to bonuses?

Be careful. Once a number carries a bonus, people have a reason to shift rules, such as moving stops out of planned time. Keep the definitions locked and audited if you do so.

What should a weekly OEE report look like?

One page with five numbers, in the same order each week. See OEE dashboard examples for layouts you can copy.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

Related guides: Operator Buy-In for OEE: Earning Trust on the Line · Shop Floor Reporting: What to Report and When

← More OEE Lab guides · OEE dashboard examples →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES