Why yield is not the same as utilization

Yield is the share of product that is good. Utilization is the share of a tool, bay, or fab that is busy. Both are percentages you will hear on the same tour. They are not the same meter, they do not move for the same reasons, and raising one can lower the other.

A FOUP on a loadport can hide the split. The box might be full of good wafers, full of scrap, or empty because the tool is waiting. From the aisle you see a yellow-amber pod and a green light. That is a logistics picture. It is not a yield picture.

Line yield asks how many wafers that started a sequence also finished it. Die yield asks how many sites on a finished wafer meet the spec — often after probe. Combined yield multiplies the two, and plants argue about what belongs in the denominator: all sites, all printable sites, or all sites that were even worth testing. None of those definitions is “how busy is the etcher.”

Utilization asks a different question: of the time this tool could have been processing, how much of that time was it processing? Some shops count only “productive” recipes. Some count any wafer on the chuck, including quals and monitors. Some quote fab utilization as wafer starts against nameplate starts. The number is about capacity, not about whether the silicon will bin out.

The mix-up is easy because both numbers are percentages, both live on the same operations slide, and both get worse when a tool is sick. A dirty chamber can scrap wafers and also sit idle while it is cleaned. A visitor hears “we are at 70 percent” and does not know which 70. An engineer who hears the wrong 70 ships the wrong action: more starts into a line that is already making scrap, or a yield task force on a bay that is simply starved of lots.

Defects belong to yield. A particle, a scratch, a misprocess, a weak via — those remove die or wafers from the good pile. You can have a quiet, underloaded factory with terrible yield if the recipe or the incoming material is wrong. You can have a packed factory with excellent yield if the process is stable and the constraint is demand or a bottleneck elsewhere.

Busy-ness belongs to utilization. A tool can run around the clock on monitor wafers and post a handsome utilization with no shippable die. A tool can sit idle because the previous step is down, and post a poor utilization while the wafers it already processed remain perfectly good. Filling every cassette does not make the product good. Emptying a bay does not make the product bad.

The aisle makes the confusion visual. Identical cabinets, repeating loadports, a few pods in motion: it looks like a capacity problem or a quality problem depending on the story you brought with you. Dispatchers watch queues and idle time. Yield engineers watch maps, fail signatures, and inline defect data. They share a building. They do not share a definition.

There is a real coupling, just not an identity. High utilization on a dirty tool can drive more defects. Low utilization can hide a yield crash because too few wafers were tested to see it. A constrained litho cell can force the rest of the line to idle, which looks like a utilization problem and is actually a bottleneck problem. Treat the coupling as a conversation between two meters, not as proof they are one meter.

A cassette of wafers is the right object to keep in your head. Count how many wafers are in the box, and you are close to a WIP or starts picture. Count how many of those wafers, or how many dies on them, will pass the next gate, and you are talking yield. Count how often the tool that empties that cassette was actually running, and you are talking utilization.

If someone quotes a percentage on the fab floor, ask “percent of what?” If the answer is good die, good wafers, or lots that finished, it is yield. If the answer is time, starts, or nameplate, it is utilization. Write the denominator down. The numerator is the easy part.