Blog / Performance
Performance · Guide

Performance Over 100 Percent in OEE: Fix Guide

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

Performance over 100% means the line seems to have made more units than its ideal rate allows, so an input is wrong. The usual causes are an ideal cycle time that is too long, a count that is too high, or a run time that is too short.

Read the formula backwards

Performance = (ideal cycle time × total units) ÷ run time. Only three inputs can push it over 100%, and each one needs a different fix.

Example: a stamping press runs for 400 minutes. The ideal cycle time on file is 2.0 seconds per part, and the counter shows 13,200 parts.

Ideal time = 13,200 × 2.0 s = 26,400 s = 440 min
Performance = 440 ÷ 400 = 110%
The press needed 440 minutes of ideal time inside 400 minutes of run time.

The press cannot have spent 440 minutes inside 400. The basic calculation is covered in how to calculate OEE performance, so here we chase the error.

The hourly count tells you which input to suspect

Before opening any setting, plot units per hour against the ideal rate. A 2.0 second cycle means 1,800 parts per hour.

Ideal rate on file1,800 / h
Pattern A, hour 11,980 / h
Pattern A, hour 22,040 / h
Pattern A, hour 32,010 / h
Pattern B, hour 11,620 / h
Pattern B, hour 23,240 / h
Pattern B, hour 31,590 / h
Hourly counts from two example presses. A steady run above the line points to the rate. A single spike points to the counter. Full bar = 3,600 parts per hour.

Pattern A is a calm line that beats the rate every hour, so the rate is wrong. Pattern B is a line below the rate with a jump that no machine can make, so the count is wrong.

Wrong ideal cycle time

Back to the press. It was rebuilt last year, and its true best cycle is now 1.6 seconds per part, but nobody changed the 2.0 on file.

With the right number, 13,200 × 1.6 s = 352 minutes, and performance is 352 ÷ 400 = 88%. So a line that looked 10 points over the limit actually has a 12-point speed loss.

Common ways this happens:

  • Machine upgrade. A new drive, feeder or tool made it faster and the old rate stayed.
  • Rate from an average. Someone set it from last month's output, so a good day beats it.
  • One rate for all products. The slowest product's rate is used for everything.
  • Cycles and parts mixed up. The rate is per cycle and the count is per part.

How to set a proper rate is in the guide to ideal cycle time.

The unit trap: 180% is a clue

Example: a tool moves from 2 cavities to 4, while the ideal rate on file stays at the 2-cavity figure. A press at 90% performance now reads 180%, exactly double.

A clean multiple like that usually points to units, so check the speed last. Work per part, then read it again.

The mix trap: one rate across two products

Example: in 400 minutes of run time a line makes 8,000 of product A at an ideal 40 per minute, and 1,500 of product B at an ideal 20 per minute. The ideal time is 200 + 75 = 275 minutes, so performance is 68.8%.

Put the whole 9,500 units on B's rate and it reads 9,500 ÷ 20 = 475 minutes, or 118.8%. Always add up ideal time by product and never average rates.

Count errors

Now say the 2.0 second rate is right, and a hand count of the press shows only 11,400 real parts. Performance is then 380 ÷ 400 = 95%.

The extra 1,800 counts came from somewhere, and these are the places to look:

  • Double pulses. A worn cam, a bouncing part or a sensor set too close fires twice.
  • Empty cycles. The counter reads machine strokes, including strokes with no part in the die.
  • Test pieces and returns. Setup pieces or reworked parts pass the sensor as if new.
  • Window errors. The count resets at 06:10 while the shift starts at 06:00, or units from a buffer come out in the next shift.

Hand count a fixed time, for example 15 minutes, in two different hours. Both should match the counter closely, and part counting sensors covers the options if they do not.

Run time that is too short

This one is easy to miss, and it starts in hand logs. If stops are written too long, run time shrinks and performance climbs.

Example: the press has 80 minutes of stops logged out of 480, but the real figure is 40. Run time should be 440 minutes, and 440 ÷ 440 = 100%, with no speed loss on paper and no overspeed either.

The clue is a shift where availability looks poor and performance looks too good. Check the log against machine records, as in OEE data collection methods.

Match the reading to the first suspect

What you seeFirst suspectTest
101-115%, steady, every shiftIdeal rate too lowBest sustained hour vs ideal rate
About 2, 4 or 8 times the usual readingCycles and parts mixedCount one cycle by hand
One hour spikes, the rest are normalCounter or resetHand count, check reset time
Only on one productRate for that formatCompare with similar formats
Only with one crewStop logging habitsLog vs machine run signal
Start with the pattern, then run one test. Our own rules of thumb, not a standard.

Cap it, and leave a flag

Overall Equipment Effectiveness (R. C. Hansen, 2001) caps the speed factor at 1.0 and notes any overspeed run to catch up. On a machine that is not the bottleneck, the ideal rate is the rate needed to feed the bottleneck, so running faster than that simply caps at 100%.

A capped figure has one side effect that helps you. Availability × capped performance × quality will no longer equal the good units check from the count-based method, and that gap is your flag.

Our advice is to store both numbers, and show the capped one. When the raw reading stays above 100% for more than a few shifts, open a data task and do not leave it.

After the fix, expect a drop

Correcting the press from 110% to 88% takes OEE down, and the line did not get any worse. Tell the crew first, because the old number was the wrong one.

The new gap is the real prize. In the example, 12% of 400 minutes is 48 minutes per shift of slow running and short stops, which you can now go after with speed losses and causes of reduced speed.

If OEE as a whole is over 100%, not just this factor, go to OEE over 100 percent, since planned time can be the cause there too.

See it live in Fabrico

A counter you can compare with the run signal is the fastest way to see which input is wrong. Fabrico takes stops, speed and counts live from PLCs or from IoT sensors on older machines, so hourly rate patterns sit next to the OEE per line and shift. See how Fabrico reads machine signals.

What people ask next

Is performance over 100% ever real?

A machine can truly run faster than the rate on file, but then the rate is wrong. Once the rate is the best accredited speed, a true overspeed is rare and short, and it is capped at 100%. See ideal cycle time.

Should I raise the ideal rate as soon as a line beats it?

Not on one good hour. Check that the count is right, then see whether the line holds the faster rate with normal quality, and accredit it after that. A short burst that makes scrap is not a new rate.

Does capping performance change my OEE?

Yes, the capped OEE is lower than the raw reading. It still hides any real speed loss if the rate is too low, so a cap does not replace fixing the rate. The OEE calculator lets you compare both.

Why does performance go over 100% only after a changeover?

The likely cause is that the rate in the system did not change with the product, or that the changeover was logged long, which cuts run time. Check how changeovers are counted and when the format was switched in the system.

Can micro-stops cause performance over 100%?

No, they push it down. Stops that are not logged stay inside run time and lower the rate. See micro-stops for how they work.

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: OEE for Printing Presses: Makeready, Waste, Speed · Cycle Time Variation: Causes and How to Measure · Ideal Run Rate in OEE: How to Calculate It

← More OEE Lab guides

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