Line Efficiency (OEE) for Beverage Bottling — How to Measure and Improve

1. What OEE measures

OEE is the product of three ratios: availability (the share of scheduled time the line actually runs), performance (the share of rated speed it holds while running) and quality (the share of produced bottles that pass). The three losses — stoppages, speed loss and rejects — are different problems with different fixes, and the metric separates them instead of hiding them in a single utilisation number.

OEE is a methodology, not a benchmark: the line's own baseline is the reference, and the improvement is measured against it — not against a number from another plant.

2. Availability

Availability is the share of scheduled production time the line runs: stoppages — breakdowns, changeovers, cleaning, waiting — reduce it. The losses are recorded with their causes, and the record is where the improvement starts: the stoppage that recurs daily is the stoppage worth fixing first. Availability is the category most plants improve first, because the data — the downtime log — is already being kept.

Define what counts as a stoppage before measuring — changeovers and cleaning are planned, breakdowns are not, and the classification decides what the log tells you.

3. Performance

Performance is the share of rated speed the line actually holds: speed loss — running below the rating, micro-stops, slow feeds — reduces it. It is the category most often hidden, because the line 'runs' while running slow. The speed record, bottle counts and the shift log show it, and the causes are the quiet ones: a starved infeed, a slow section, a machine running below its setting.

Performance is measured against the rated speed on the actual bottle — the rating itself is a spec, and the performance loss is the gap between it and reality.

4. Quality

Quality is the share of produced bottles that pass: rejects — underfill, bad caps, label faults, damaged bottles — reduce it. The quality loss is both the rework and the giveaway, and the reject data — the counts and the causes — is the improvement's input. On a beverage line the quality category is where the fill accuracy, the cap torque and the packaging checks show up as numbers.

Quality is measured on the final good bottles — the bottles that ship — and the reject record is the audit's evidence as much as the improvement's input.

5. The data

OEE is data-driven: the downtime log, the speed record, the reject counts and the scheduled time are the inputs, and the line's control system provides them — the shift reports, the machine counters and the quality records. The data quality decides the metric's value: the log that records every stop, honestly, is worth more than the summary that smooths it. Ask what data the line provides when you buy it.

The data is the plant's operating capital — the line that logs its own performance is the line that can be improved, and the audit that reads the logs is the audit that trusts them.

6. The loss hierarchy

The losses are not equal: on most lines, one category dominates — the biggest loss is the bottleneck, and it is the one worth fixing first. The hierarchy is found in the data: the downtime log's biggest cause, the performance gap's biggest section, the reject record's biggest fault. Fix the biggest loss, remeasure, and the next biggest becomes visible — the improvement loop is a sequence, not a programme.

The loss hierarchy is also the justification — every fix is priced against the loss it removes, and the sequence follows the numbers.

7. The improvement loop

The improvement loop is simple and relentless: measure (the OEE and its three categories), identify (the biggest loss), fix (the cause, engineered or procedural), remeasure (the same data), repeat. The discipline is the plant's; the data is the line's; and the loop turns the honesty metric into the operating plan. The line's control system and the training are what make the loop possible — both are specified at order.

The filling machine and combiblock ranges provide the line and its data; the loop is the plant's own, run shift by shift.

Frequently asked questions