OEE Improvement
Every Fix Is a Tradeoff

Most advice on how to improve OEE is a list: cut changeovers, fix breakdowns, eliminate minor stops, run at rated speed. Every item on it is sensible, and every item trades against something else on the line. The plants that raise output, rather than just the metric, are the ones that price the tradeoff before they spend.

Why a list of fixes isn’t a plan

OEE is Availability × Performance × Quality, and the Six Big Losses map onto those factors: equipment failure and setup onto Availability, minor stops and reduced speed onto Performance, process defects and startup yield onto Quality. That invites treating each loss as an independent lever.

The levers are connected. Speed changes failure rates. Buffers change what a stoppage costs. A machine’s OEE and the line’s output are different quantities. And the metric itself can move because the schedule changed rather than the equipment. Five tradeoffs come up on nearly every line, and two experiments price most of them.

Tradeoff 1: speed vs stops

Performance loss is the gap between actual and rated speed, so the obvious fix is to run faster. On many machines, running faster also means more jams, misfeeds and minor stops, because failure rate rises with rate. Performance goes up, Availability comes down, and output follows whichever moved more.

Fischel and Lange’s published model of a food plant, in which each unit operation’s failure rate scales with its production rate, finds that throughput has an optimum rather than rising steadily with speed. An analysis that treats rate and reliability as separate numbers can’t see it.

Tradeoff 2: downtime vs buffer capacity

On a loss report, downtime is downtime. On the line, what it costs depends on where it happens. Ten minutes down in front of a well-stocked buffer can cost almost nothing, while the same ten minutes on a starved constraint costs ten minutes of finished product (why the two rankings differ).

So two levers compete. You can add storage so stoppages stay local, or make the machine stop less. Storage costs capital, floor space and work-in-process. Reliability work is often harder, but fixing a failure helps every machine downstream at once. The buffer tradeoff experiment puts both on one axis by sweeping a buffer’s capacity while dropping interrupts (Buffer Tradeoff results in the docs). The sweep, the knee where storage stops paying, and what storage really costs in a food plant are in How big should a buffer be?

Tradeoff 3: machine OEE vs line OEE

The 85% world-class figure is a single-machine benchmark. Where a line of such machines lands depends on its topology and buffering (Is 85% OEE achievable on your line?). For improvement work, that means raising a machine’s OEE raises line output only to the extent that machine’s losses were reaching the end of the line. A machine whose stops a buffer already absorbed, or which was starved or blocked by something else, can post a better number while the line makes the same product. The machine that limits the line also moves with downtime, product mix and schedule, which is the subject of theory of constraints simulation.

Tradeoff 4: changeovers vs responsiveness

Changing over less often cuts setup loss but trades it for inventory and responsiveness to the order book. Faster changeovers trade engineering effort instead, and what they return depends on where the changeover sits relative to the constraint. At a specialty olive packer, two-hour olive-size changeovers make the pitting machines a known bottleneck, and the model finds other choke points downstream in packaging (case study).

Product mix can also move the bottleneck, a second-order effect a loss report can’t show. On a Make-Store-Pack coffee operation, changing the packaging size relocated the constraint, and a planning system that assumed a fixed constraint couldn’t schedule it until a rate-based model reproduced the behavior (The Shifty Bottleneck).

Tradeoff 5: maintenance spend vs recovered throughput

Maintenance and reliability budgets are usually allocated from a downtime Pareto, largest bar first. That ranks losses by minutes (how often and how long something stopped), not by whether the line noticed. Frequent short stops on a tightly coupled line tend to cost more than their minutes suggest. Long stops on a buffered machine often cost less.

Loss/gain analysis asks the question a budget needs answered, which is what comes back if we fix it. In a validated model of the line, disable one failure mode, re-run the whole line, measure the production recovered, and repeat for every interrupt. In ReliaSim® this is the Efficiency Gain/Loss experiment, with a reference version for the bottling-line demo models on ReliaSim’s public MCP server. The method, the demo results and why it needs failure-mode detail are in Which loss to fix first.

Pricing the tradeoffs before you spend

Every tradeoff above has the same structure. There are two levers that both raise some number, costs you already know, and a throughput effect you don’t. OEE simulation supplies the throughput side, as long as the model deserves trust. The published bar for that is within 1% of measured OEE.

Frequently asked questions

Try it on a real bottling line: the Sandbox question What should we fix first?, or one move in Beat the Bottleneck.