OEE for Australian Food and Beverage Lines: Meaning, Calculation and a Worked Example

OEE, or Overall Equipment Effectiveness, is the share of planned production time in which a line made good product at its ideal rate. It is calculated as availability multiplied by performance multiplied by quality, and it is the single line-performance figure most Australian food and beverage plants report. This guide explains what OEE means under the ISO 22400-2 standard, works through a full calculation on a two-SKU line, and shows the two booking decisions that move the figure most on food lines.

It is written for operations managers, production managers and engineering leads who report OEE, or are about to, and want a number that holds up in the weekly review.

What OEE means

OEE answers one question: of the time this line was supposed to be making product, how much of it actually turned into good product at full speed? A line at 100% OEE ran for the whole planned time, at its ideal rate, with no rejects. Every point below 100% is a loss, and OEE sorts those losses into three groups.

• Availability losses are time the line was planned to run but did not: breakdowns, changeovers, waiting on product or people, and stops long enough to be recorded as stops.
• Performance losses are time the line ran slower than its ideal rate: reduced speed, and short stops too brief to be logged as downtime.
• Quality losses are product made that could not be sold as first-pass good: rejects, rework and start-up scrap.

The measure is defined in ISO 22400-2, the international standard for manufacturing operations key performance indicators. It sits at Level 3 of the IEC 62264 (ISA-95) model, between the control system and business systems. ISO 22400-2 calls the OEE result the OEE index and names the performance factor effectiveness; most plants still say performance, and this guide does too.

The time model behind the three factors

Every OEE calculation starts by splitting the shift into time buckets. Getting these buckets right, and agreeing them across lines, matters more than the arithmetic that follows.

OEE is fully productive time divided by planned production time. The three factors are the ratios between consecutive rows.

How to calculate OEE

Availability = Run time ÷ Planned production time
Performance  = Σ (Ideal cycle time × Units made) ÷ Run time
Quality      = Good units ÷ Units made
OEE          = Availability × Performance × Quality

Two details trip up most first attempts.

1. The ideal cycle time belongs to the SKU, not the line. On a line that runs several products, performance has to add up ideal time SKU by SKU. That is why the formula uses a sum rather than one line rate.
2. The factors multiply. A line at 90% availability, 90% performance and 90% quality is at about 73% OEE, not 90%. Healthy individual numbers can still produce a modest headline figure.

Worked example: a two-SKU cup filling line

The figures below are illustrative, chosen to show the method. They are not measurements from a Metromotion Controls client.

A cup filling line on an eight-hour shift runs two SKUs with a changeover and allergen clean between them.

The shift also includes a 30-minute meal break (planned), a 45-minute changeover and allergen clean between the SKUs, and 25 minutes of breakdowns and recorded stops.

Availability. Planned production time is 480 minus 30, or 450 minutes. Run time is 450 minus 45 minus 25, or 380 minutes. Availability is 380 ÷ 450 = 84.4%.

Performance. At the ideal rate, SKU A's 10,800 units would take 180 minutes and SKU B's 6,480 units would take 162 minutes, a total of 342 minutes of net run time. The line actually ran for 380 minutes, so performance is 342 ÷ 380 = 90.0%.

Quality. The line made 17,280 units, of which 16,934 were good. Quality is 16,934 ÷ 17,280 = 98.0%.

OEE. 84.4% × 90.0% × 98.0% = 74.5%. As a check, the good units at their ideal rates represent 176.4 + 158.75 = 335.15 minutes of fully productive time, and 335.15 ÷ 450 is the same 74.5%.

The single-rate trap

Suppose the line's reporting uses one ideal rate, the 60 units per minute of the faster SKU, for everything. The 17,280 units made in 380 minutes are then compared with 22,800 possible units, and performance falls to 75.8%. OEE for the same shift falls from 74.5% to 62.7%, and the loss is blamed on the line running slowly when it ran each SKU close to its real ideal rate. On a line with a wide SKU range, a single rate also makes OEE rise and fall with the product mix rather than with how well the line ran. Each SKU needs its own validated ideal rate, held in the system that calculates OEE and selected automatically when the SKU changes.

Where the changeover is booked

Now suppose the 45-minute changeover and allergen clean is booked as planned downtime instead of an availability loss. Planned production time drops to 405 minutes, availability rises to 93.8% and OEE rises to 82.8%. Nothing about the line changed; only the booking rule did.

Neither rule is wrong, but they answer different questions. Booking changeover as unplanned keeps it visible as a loss to reduce, which is usually what a food plant wants, because changeover, CIP and allergen cleans are often among its largest losses. Whichever rule is chosen has to be written down and applied on every line and every shift, or cross-line comparisons stop meaning anything.

What is a good OEE for a food or beverage line

The often-quoted 85% "world-class" figure comes from discrete manufacturing benchmarks and assumes long runs with few changeovers. A hygienic, high-SKU food line that cleans between allergens will rarely look like that, and chasing the benchmark tends to push losses into the planned-downtime bucket where OEE no longer sees them.

A more useful target is the line's own baseline. Measure OEE consistently for several weeks, find the largest losses in the downtime Pareto, and track whether those specific losses shrink. A line that moves from 55% to 65% on a stable definition has improved more than a line that reports 85% on a definition nobody has checked.

OEE and production efficiency

Production efficiency is the broader question most managers are asking when they look at OEE: how much output does the plant get from the time, people, materials and energy it puts in? OEE answers one part of that question well, the share of scheduled line time that turned into good product at the ideal rate. It leaves the rest to other measures.

• Labour efficiency is output per labour hour. A line can hold its OEE while running with more people than it needs.
• Material yield and giveaway is good product out against ingredients and packaging in. Overfill on a checkweighed line costs money without touching OEE, because every overfilled pack still counts as good.
• Utility use per unit is energy and water against output. Long CIP cycles and idle running show up here more clearly than in OEE; see energy and utilities monitoring.
• Schedule adherence is whether the right product was made at the right time. A line can run efficiently on the wrong order.

The practical approach is to use OEE to find and track losses on each line, and to add the other measures from the same data layer once OEE is trusted. Checkweigher results, utility meters and the production schedule can all be stored against the same line, SKU and shift, so production efficiency can be read as one picture rather than four separate reports. Our production reports and dashboards page covers how those figures are delivered to each team.

Where OEE misleads

OEE is a strong measure of how efficiently a line ran. It says nothing about whether the line made the right product, it ignores hours the line was never scheduled, and it can be distorted by inconsistent booking of changeover and cleaning. We cover these limits in detail in where OEE misleads on Australian food and beverage lines. The short version: use OEE to find and track losses on a line, and be careful comparing lines that run different products or book time differently.

Getting OEE inputs from the line rather than a clipboard

Every number in the worked example has to come from somewhere. On many sites the answer is a shift sheet: stops written down with rounded durations, counts copied from a machine display, and reasons remembered at the end of the shift. That is where most OEE disputes start.

The controller already knows most of the answers. The PLC registers each stop and restart when it happens, counts output and rejects, and knows which fault stopped the machine. Reading those signals directly gives a timestamped record of each input.

• Machine state: running, stopped, starved, blocked, changeover, cleaning. PackML gives a common state model across OEMs; see our guide to PackML on packaging lines.
• Counts and rejects: read from the machine or the reject stations, not copied from a display.
• The SKU and its ideal rate: selected from the schedule or at changeover, so performance always uses the right rate.
• Stop reasons: automatic where the PLC knows the fault, and chosen by the operator from a short list where it does not.

Once those signals are reliable, OEE can be attributed to orders and SKUs, which is where an MES for a mid-size food plant starts to pay off, and the same stop events can raise maintenance jobs through maintenance from plant data.

How Metromotion Controls has delivered OEE data

At Chobani, we connected the existing PLC infrastructure to a centralised reporting environment with live OEE calculation and downtime event capture from PLC states. Consistent reason-code definitions across shifts gave the operations team a Pareto they could use in daily reviews, and shift-level and weekly management reports replaced manual spreadsheet collation.

At Cobs Fine Foods, we connected every line asset, including checkweighers and metal detectors, to Ignition and passed the data at PLC level to the site's third-party OEE platform, giving the operations team real-time line performance visibility.

What this means

OEE is simple arithmetic on top of three decisions: how the shift is split into time buckets, which ideal rate applies to each SKU, and where changeover and cleaning are booked. Make those decisions once, write them down, apply them on every line, and read the inputs from the PLCs rather than a shift sheet. The figure then becomes something a food plant can act on.

If you want OEE that your food and beverage lines calculate for themselves, speak with an engineer and we will review your lines, PLCs and current reporting.