Many cost engineers don’t start their careers on a factory floor. They start with spreadsheets, drawings, cycle times on paper, and assumptions that everything runs the way it is theoretically supposed to. In many cases, that works… right up until it doesn’t. That’s where OEE comes in.

You’ll hear manufacturing professionals throw around “OEE” like everyone knows what it means. If you haven’t lived in a factory, it can sound abstract or academic. It’s not - it’s a very grounded and practical way of answering a simple question:

How much of the time is this equipment really doing what we think it’s doing?

What is OEE ?

OEE stands for Overall Equipment Effectiveness. OEE is a single-number metric, shown as a percentage, that tells you how close a machine or an assembly line is operating to its full potential. Not its spec sheet potential - it's real, usable, good-parts-out-the-door potential.

An OEE of 100% would mean something almost mythical. The machine is running every minute it’s scheduled. It runs at full speed, and every part is good. No scrap. No hiccups. No slowdowns. If that sounds unrealistic, that’s because it is. Real factories don’t work that way. OEE exists because reality exists.

The way the OEE calculation works is quite straightforward. It’s built from three components: availability, performance, and quality.

Availability

Availability is about uptime. If a machine is scheduled to run for eight hours, how much of that time is it actually running? All stops impact availability, be they planned or unplanned – breakdowns, changeovers, waiting on material, etc.

If a machine was supposed to run eight hours and only ran seven, availability is about 87%. No fancy calculations there.

Performance

Performance is about speed. When the machine is running, is it running as fast as it’s supposed to? Not wide open, lab-condition fast – but rather, realistic, designed speed. Machines slow down all the time. Operators dial things back. Small jams happen. Sensors trip. None of these may stop production completely, but they quietly eat away at output. The performance metric captures that.

Quality

Quality (or yield) is the most intuitive portion of the OEE metric. Of all the parts that came out, how many were actually good? Scrap counts. Rework counts. Startup scrap counts. If you made 1,000 parts and 50 were bad, the quality is 95%.

The OEE Calculation

Put those three together, and you get OEE . . .

OEE = Availability × Performance × Quality

And here’s the part that surprises people the first time they see it. None of the aforementioned numbers looks terrible on their own. You might have 90% uptime. 90% speed. 95% yield. Sounds pretty solid, right ?

When you multiply them together . . .

OEE = 90% x 90% x 95% = 77%

You’re at about 77% OEE!! But that missing 23% is where cost savings opportunities reside. Manufacturing teams use OEE because it gives them a clean way to see where they’re losing ground. Is the problem caused by downtime, speed, or scrap? The number doesn’t just say “you’re bad.” - it provides the path to understanding the root cause.

Let’s talk about why cost engineers should care, because this is where things get interesting.

Impact on Cost Models

Most cost models are built on ideal behavior, such as ideal cycle time, planned production hours, and nominal scrap. We don’t do this because we’re careless. We do it because those are the numbers we’re given, or the only ones available early in the product’s development.

The problem is that factories don’t live in the ideal world. They live in the OEE world.

OEE is the bridge between what a process could do and what it actually does.

For example, consider capacity. On paper, a machine might be able to make a million parts a year. That’s the theoretical capacity. Multiply that by OEE and you get real capacity. If OEE is 65%, that million-part machine is really a 650,000-part machine.

That one adjustment changes everything.

Suddenly, you understand why a plant wants another machine even though “there should be enough capacity”, or why overtime never seems to go away, or why fixed costs feel heavy no matter how much volume they push.
From a cost perspective, OEE directly affects cost per unit. This is especially brutal in capital heavy processes, such as stamping presses, SMT lines, injection molding, and semiconductor processes. If OEE is low, the cost per unit is driven high.

An Important Caveat

When we build cost estimates, we should absolutely account for reality. We should not assume theoretical perfection. But we also should not build models around a specific supplier’s numbers.

There’s a difference.

If a supplier is running at 52% OEE because their maintenance program is weak, their changeovers are chaotic, and/or their scrap is out of control, then that is an inefficient operation. That’s their problem to fix. It does not represent the benchmark for the process and should not be treated as such.

Should-cost models should reflect what a competent, well-run, world-class operation can achieve. Not fantasy or perfection, but best-in-class for that process.

Every manufacturing process has a reasonable performance band. Injection molding might run consistently in the 75 to 85% OEE range in strong plants. SMT lines might have different metrics, as well as stamping processes. Semiconductor fabs obsess over yield and uptime at a completely different level.

The point is this. . .

We should develop should-cost models based on what is realistically achievable with disciplined operations - preventive maintenance, controlled changeovers, stable processes, and well-trained operators.

We should not model chronic breakdown culture. If you bake a given supplier’s inefficiency into your cost model, you normalize it. You make it look structural. Once it’s in the spreadsheet, it starts to feel justified.

The role of cost engineering is to anchor the conversation in what should be happening in a well-managed operation. That doesn’t mean ignoring downtime or scrap. It means using realistic, competitive benchmarks.

Example

Say a machine is supposed to make one part per minute, according to its spec sheet. Over an eight-hour shift, that’s 480 parts. If the fixed cost for that shift is $4,800, you’d model $10 per part.

Now, let’s introduce reality. Maybe availability is 85%, performance is 90%, and quality is 95%. We’ve established through benchmarking and experience that those are decent numbers for this operation. Multiply it out, and OEE is about 73%. Now, instead of 480 good parts, you’re getting closer to 350. That same $4,800 in fixed cost is now almost $14 per part.

That’s honest should-cost modeling that is credible and reflective of real-world conditions. In contrast, if a particular supplier is running the same process at 55% OEE because they haven’t invested in maintenance or process control, that does not redefine what the process costs. It tells you they are inefficient.

Your cost model should reflect what a capable competitor with world-class processes could do with the same equipment and demand profile. That distinction is subtle, yet powerful.

Summary

OEE helps you stay grounded in the realities of the manufacturing environment. It helps to make your cost models credible. At the same time, benchmarking OEE keeps you from modeling supplier inefficiencies and provides a means to identify cost savings opportunities.

For cost engineers, the practical takeaways are these. . .

• Ask for OEE data when you can. If the supplier won’t share their OEE, ask the questions behind it. How much downtime? How much scrap? How often do you change over? How fast does the line really run? Then sanity check those numbers against what strong plants achieve in that process.
• Build your model around disciplined, competitive performance that represents best-in-class for the manufacturing process.

OEE doesn’t replace cost engineering judgment – rather, it sharpens it. It provides credibility that comes from the factory floor instead of a spreadsheet assumption.

Jeff Miller Jeff Miller is President and Co-Founder of SPCEA and has 40 years of engineering, manufacturing, and commercial experience within the electronics and semiconductor industries. He has served in leadership and direct-contributor roles at General Motors, John Deere, Standard Motor Products, Ford Motor Company, Whirlpool Corporation, and Panasonic Automotive Systems. Jeff has been active within the cost engineering profession since 2002.   Copyright © 2026 – Society of Product Cost Engineering & Analytics. All rights reserved.