Blog / OEE
OEE · Guide

OEE with Mixed Products and Ideal Cycle Times

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

Turn every product into minutes: OEE = Σ(good units × that product's ideal cycle time) ÷ scheduled time. Do not use one average ideal rate for the whole line, because then OEE moves whenever the product mix moves, even if the line ran exactly the same.

Mixed product OEE calculator

Enter one shift on one line. The defaults are the two-product shift worked through below. Updates as you type.

Time
min
Shift minus planned breaks.
min
All stops, changeovers included.
Products (2 to 10)
Defaults: 2 s and 4 s products
OEE for the shift
-%
OEE = availability × performance × quality
0%100% = no losses
Run time
-
Ideal time
-
Availability
-
Performance
-
Quality
-
Good units
-
Single rate
-
Off by
-

Ideal minutes per product

Rate per product or one average rate

The working

Quality is weighted by ideal time, so a scrapped slow unit counts for more line time than a scrapped fast one.

The problem with counting units

A carton of 12 and a carton of 48 do not take the same time to make. Adding them as "two cartons" hides that.

Units from different products cannot be added in a useful way. Minutes of ideal running can, and that is the whole trick.

Good time (A) = good units A x ideal cycle time A
Good time (B) = good units B x ideal cycle time B
OEE = (good time A + good time B) / scheduled time
Every product is converted to the same unit, minutes, before anything is added.

This is the same rule as the single-product formula. It just runs once per product, and the performance calculation works the same way.

Worked example: two products in one shift

Example: a line is scheduled for 480 minutes and loses 60 minutes to stops, including one changeover. That leaves 420 minutes of run time, split between two products.

Product AProduct BTotal
Ideal cycle time2 s4 s
Run time240 min180 min420 min
Units made6,0002,4008,400
Good units5,8802,3408,220
Ideal minutes, all units200160360
Ideal minutes, good units196156352
Example: 6,000 x 2 s ÷ 60 = 200 minutes, and 2,400 x 4 s ÷ 60 = 160 minutes.

Now the three factors work as usual, with minutes in place of units.

FactorSumResult
Availability420 ÷ 48087.5%
Performance360 ÷ 42085.7%
Quality352 ÷ 36097.8%
OEE352 ÷ 48073.3%

Check it: 0.875 × 0.857 × 0.978 = 73.3%. The short route, 352 ÷ 480, gives the same answer.

Watch the quality line. Counting units gives 8,220 ÷ 8,400 = 97.9%, which is slightly off, because a scrapped slow unit costs more line time than a scrapped fast one.

What goes wrong with one average rate

Teams with many products often use one rate for the whole line. Each choice fails in its own way, using the same shift as above.

Single ideal for all 8,400 unitsIdeal minutesPerformance
A's rate, 2 s28066.7%: B looks like a slow line
Average, 3 s420100%: every speed loss vanishes
B's rate, 4 s560133%: above the maximum
Per product (correct)36085.7%

The real damage comes the next day. A single rate turns a change of plan into a change of score.

Example: on day 2 the same line runs A for 120 minutes and B for 300 minutes, at the same speed on each product as day 1. That makes 3,000 of A and 4,000 of B, or 7,000 units in all.

Single 2 s rate, day 166.7%
Single 2 s rate, day 255.6%
Rate per product, day 185.7%
Rate per product, day 287.3%
Same speeds on both days. The single rate reports a fall of 11 points, and the rate per product shows the small rise that the longer B run really gave.

Day 2 by product: A is 3,000 × 2 s = 100 ideal minutes and B is 4,000 × 4 s = 266.7, so performance is 366.7 ÷ 420 = 87.3%. Day 2 by single rate: 7,000 × 2 s = 233.3 ideal minutes, and 233.3 ÷ 420 = 55.6%.

Meetings about a fall like that one waste everyone's time. The line did nothing different; the planner did.

Which ideal cycle time does each product get?

A rule here matters more than the sums: one accredited rate per product family of the same size and format.

This is the method in Overall Equipment Effectiveness (R. C. Hansen, 2001):

  • A real difference in format earns its own rate. A 2-litre bottle and a 500 ml bottle are different families, with different proven speeds.
  • A product that is simply harder to run does not. If a sticky recipe in the same format runs slower, keep the family rate and let OEE drop.

That drop is useful information, because it shows what the product costs in line time. The rules for setting each rate are in ideal cycle time.

Where changeovers go

A changeover between products is a stop, so it lowers availability for the line, as how to count changeovers in OEE explains. It belongs in the line total whatever else you do with it.

If you also split the line by product, someone has to carry it, and practice varies. We charge the incoming product and keep that rule fixed; OEE by product covers the split and the other options.

How to run it in a spreadsheet

Keep one row per run, with four columns: scheduled minutes, product, good units and ideal seconds per unit. Pull the ideal seconds from one fixed product table so nobody types them by hand.

=SUMPRODUCT(C2:C20,D2:D20)/60/SUM(B2:B20)
Good units in column C, ideal seconds in column D and scheduled minutes in column B, on rows 2 to 20.

The OEE tracking template gives you a layout to start from.

Mistakes to check for

  • Mixed units. Packs per minute and cartons per minute look alike in a report. Write the unit next to each rate.
  • A moving bottleneck. A product can be limited by the filler while another is limited by the packer. Use the rate of the step that limits that product.
  • Product table drift. An edit to one rate changes every past comparison, so date each change and mark it on the chart.
  • Averaging product OEEs. Weight them by scheduled time, as in how to average OEE across machines.
  • A new product with no rate. Do not leave it out quietly. Give it a provisional rate, mark it as provisional and replace it once proven.

Once the sum is right, the six big losses are comparable from week to week. A change in the score then means a change on the floor.

See it live in Fabrico

A mixed line needs counts and speed tied to what was running at the time. Fabrico takes stops, speed and counts live from PLCs or IoT sensors, and shows OEE per line and shift. See how Fabrico shows OEE per line and shift.

What people ask next

Can I use a weighted average ideal cycle time?

Only if you weight it by the units made in that same period, which is the sum above in another form. A fixed average from last year stops being true as soon as the mix changes. Ideal cycle time explains what to use.

Why did OEE drop when we ran more of a slow product?

With a rate per product, a slow product does not lower OEE by itself. If OEE still fell, look for more changeovers or a real speed loss, or check that the rate is per product. OEE calculation mistakes lists more checks.

Should a hard product get a lower ideal rate?

Not if it has the same size and format as its family. Keep the family rate so the time the product costs stays visible. Use OEE by product to see which ones cost most.

How do I calculate quality with several products?

Weight it by ideal time: good ideal minutes ÷ all ideal minutes. That way the three factors multiply back to the same OEE. How to calculate OEE quality covers scrap and rework.

How should I handle hundreds of SKUs?

Group them into families by size and format, each with one rate. A line with 300 SKUs may need far fewer rates than that, and the sum stays the same.

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: Ideal Run Rate in OEE: How to Calculate It

← More OEE Lab guides · OEE by product →

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