OEE for Semiconductor Manufacturing: E10 and E79

OEE for semiconductor manufacturing is built on the SEMI E10 equipment-state model and the SEMI E79 productivity standard rather than a generic three-factor formula. E10 sorts every hour a tool exists into six mutually exclusive states, and E79 turns those states into availability, operational, rate, and quality efficiencies, a four-part OEE where yield, not downtime, usually dominates.

A wafer fab does not run like a packaging line. Tools cost tens of millions of dollars, a wafer carries hundreds of individual die, cycle times stretch across weeks and hundreds of steps, and a single contamination event can scrap accumulated value that no rework will recover. That environment produced its own standards, SEMI E10 and E79, precisely because generic OEE could not describe it cleanly. This post explains the six equipment states, how they map onto classic OEE, and why fabs measure effectiveness the way they do.

What are the six SEMI E10 equipment states?

SEMI E10 defines six mutually exclusive states that together account for all of a tool's time. Every hour lands in exactly one, which is what makes the model auditable and comparable tool to tool.

• Productive time the tool is performing its intended function: regular processing and rework.
• Standby time the tool is available and able to process, but no material or operator is present. It is idle, not broken.
• Engineering time the tool is running engineering work: process development, qualification, experiments. Uptime, but not saleable production.
• Scheduled downtime planned maintenance, PMs, scheduled setups and qualification cleans.
• Unscheduled downtime the tool is not in a condition to perform its function: failures and repairs. This is the "failed" state.
• Non-scheduled time the tool is not scheduled to be used at all: unworked shifts, plant shutdown, install or decommission.

The first three states, productive, standby, engineering, are equipment uptime. The next two are downtime. Non-scheduled time sits outside the operating window entirely, the fab-floor equivalent of schedule loss above the OEE line. Separating standby from downtime is the whole point: a tool sitting idle for lack of wafers is a loading and scheduling problem, not an equipment problem, and lumping the two together, as generic OEE tends to, hides which one you actually have.

How does SEMI E79 turn states into OEE?

SEMI E79 builds OEE from the E10 states as a product of four efficiencies rather than the familiar three. The extra term is what lets a fab separate an idle tool from a slow one.

Multiply the four and you have E79's OEE. Collapse Availability and Operational into one factor and you are back to the classic Availability × Performance × Quality of the standard OEE calculation. The reason fabs keep them split is diagnostic: a tool at low OEE because it keeps breaking (low Availability Efficiency) needs maintenance, while a tool at the same low OEE because it sits waiting for wafers (low Operational Efficiency) needs scheduling and material flow. Same score, opposite fix, and only the four-term model tells them apart, in the same spirit as separating equipment from loading in OEE versus TEEP.

The four-term structure also reflects how fab capital decisions are made. Because tools are so expensive, the question is rarely "run today's tool faster" and often "do we need another tool or are we underloading the ones we have?" A tool with high availability efficiency but low operational efficiency is not short of capacity, it is short of wafers, and buying another tool would make the loading problem worse, not better. The split between availability and operational efficiency is what keeps a fab from answering a scheduling question with a capital purchase, which on a multi-million-dollar tool is an expensive mistake to make on bad data.

Why is semiconductor OEE yield-dominated?

Semiconductor OEE is yield-dominated because a wafer is not one unit, it is hundreds of die, and the value lost when die fail dwarfs most downtime. Quality Efficiency in a fab is not a rounding error the way it can be on a robust discrete line; it is frequently the largest single loss. A wafer accumulates value across hundreds of process steps over weeks, so a defect introduced late destroys all the work that came before it, and a contamination excursion can scrap entire lots at once.

This is first-pass yield taken to its most demanding form. Because rework options are limited and the accumulated value is enormous, yield improvement usually returns more than availability improvement, the opposite of a downtime-dominated line. It also changes what "good" means in the quality factor: a fab counts good die not good wafers, so a wafer that runs perfectly through every tool still posts a quality loss if its die yield is low. Any OEE that counts wafers processed rather than good die out will badly overstate effectiveness.

The cleanroom itself consumes capacity in ways generic OEE never anticipates. Monitor and qualification wafers run through tools to verify the process and the environment are in control, occupying productive time without producing saleable die. Particle excursions and environmental limits force scheduled cleans and requalifications that land in scheduled downtime and engineering time. None of this is waste in the ordinary sense, it is the cost of holding a contamination-controlled process in spec, but it must be visible in the state model rather than smeared into productive time, or the fab will believe it has more saleable capacity than it does. The E10 states give each of these its own bucket, which is exactly why fabs adopted the model instead of a three-factor shortcut.

How do you build a fab OEE that maps to E10?

Build it directly on the E10 states so the number is standard, comparable, and diagnostic. Six steps take a tool from state logging to an actionable OEE.

1. Classify every hour into one E10 state. Productive, standby, engineering, scheduled down, unscheduled down, non-scheduled, mutually exclusive, no overlaps.
2. Separate uptime from downtime. Uptime is productive plus standby plus engineering; downtime is scheduled plus unscheduled. This split feeds Availability Efficiency.
3. Isolate standby and engineering. Productive time over uptime is Operational Efficiency, so idle-but-available time and engineering time show as loading and development losses, not equipment faults.
4. Compute Rate Efficiency against a theoretical process time for the actual units, capturing slow processing and micro-stops.
5. Compute Quality Efficiency on good die, not wafers, so die yield drives the factor as it should.
6. Multiply and diagnose. The four efficiencies point at four different owners: maintenance, scheduling, process engineering, and yield. Read them separately, not just as one product.

What are the authoritative sources for fab OEE?

The definitions are owned by SEMI, the semiconductor industry's standards body. SEMI E10 specifies the equipment-state model and the reliability, availability, and maintainability metrics, and SEMI E79 specifies the equipment-productivity metrics, including OEE, built on those states. Using the standard definitions is what makes tool-to-tool and fab-to-fab comparison meaningful; a home-grown OEE that redefines "downtime" or lumps standby into it cannot be benchmarked against anyone. For target-setting, still calibrate against what a good OEE score means for the specific tool type and process, since a lithography stepper and a wet bench live in different worlds. Price recovered capacity in wafer-start throughput and remember that on the most expensive tools even small OEE gains carry large capital value.

What makes semiconductor OEE trustworthy?

Trustworthy fab OEE comes from clean, automated E10 state classification and good-die-based quality, not from operators reconstructing tool states after the fact. The failure modes are specific: standby time misclassified as downtime (making an equipment problem out of a loading problem), engineering time buried in productive time (overstating saleable output), and quality measured on wafers instead of die (ignoring the fab's biggest loss). All three are solved by capturing tool state and yield from the equipment and MES rather than from memory, exactly the source-of-truth discipline that separates real OEE from the estimates in common OEE mistakes and the automated-capture principle behind good machine monitoring. Harmony derives effectiveness from machine signals and structured operator input rather than end-of-shift estimates (see the platform), which is what keeps a state model honest at fab scale. See the CLS field story for how source-captured effectiveness holds up on a real floor, and model a tool's four efficiencies with the OEE calculator.