ReadNotes From the Field24 Jul 20262:283 min readMES & shop-floor systems

The Wafer That Can't Get Lost

The chip in your phone survived ~1,400 steps and about 3 months in a factory — and the fab can still tell you every tool, recipe, and chamber it touched.

A wafer carrier pod with a small rfid tag on its side, the tag lit warm gold, on a stocker shelf
The picture for this piece. Made for it: no people, no brands.

In plain words

The chip in your phone survived 1,400 steps and three months in a factory. The factory can still name every one.

Every wafer carries a record of every tool, recipe and chamber it touched. That record is called lot genealogy.

A chip factory logs more than 50 terabytes of it a day.

When a chamber goes bad, one query finds every wafer that passed through it. That search is called commonality analysis.

It is how a factory contains a problem to a few lots instead of a whole month of production.

And it is now a condition of defence contracts: no genealogy, no order.

Picture it. A passport stamped at every border, so when something goes wrong you know which border it crossed.

Why it matters to you. Any process you run can keep a family tree. The question is whether yours could answer 'which step did all the failures share' in a minute or a month.

The number

1,400

PROCESS STEPS PER CHIP · ABOUT THREE MONTHS IN THE FAB

What to do Monday

Build a "commonality finder" in ChatGPT (or a Claude Project) — paste failing units + their process history and ask what one tool/step/chamber they ALL share. I fed it 20 fails; it flagged a single chamber in seconds. Save it, try it this week.

The honest caveat

Full genealogy is expensive to keep, and most plants outside chips do not have it. A family tree only helps if someone asks it the right question quickly. The record is the easy part; the habit of using it is not.

Sources

The run's own source list was not recorded. These are the sources the piece names in its own words, listed here so every claim has an owner.

  1. As citedIndustry figures as stated in the piece — about 1,400 process steps and three months per chip, about 50 terabytes of genealogy a day in an advanced fab; defence contracts now requiring genealogy
Read the full script (339 words)
The chip in your phone survived more than a thousand steps… and about three MONTHS inside a factory. Lose track of one wafer, for one step — and you can scrap a month of work. So here's the system that never loses it. And once you see it, you can't unsee it. Every wafer gets a kind of birth certificate. Every tool it touched, every recipe, every chamber, every operator, every second of sensor data — recorded. It's called lot genealogy. And the scale is insane. One fab logs more than fifty TERABYTES… a day. A single tool can capture a thousand sensor readings per wafer. That's a quarter of a terabyte for one lot of twenty-five. Now here's why it matters. Say one process chamber goes bad — a tiny gas leak, a worn part. Without genealogy, you don't know which chips it touched… so you hold EVERYTHING. With it? You ask one question — which wafers went through that chamber — and in seconds the system hands you the exact list. That's commonality analysis. You contain twelve lots… instead of scrapping twelve hundred. And it's not optional. Your car's chips are traced die by die, kept on record for up to fifteen years, because automotive demands defects in the parts-per-BILLION. Every safety-critical chip traces back to the exact wafer, the exact tool, the exact minute. That's the real magic of a modern fab. It doesn't just build the chip — it never forgets HOW. And the engineer who can rewind any chip's entire life is the one who saves the factory on its worst day. If you want the fab explained the way it actually works — follow. One layer deeper, every week. And a quick tip you can steal this week. Build a "commonality finder" in ChatGPT — or a Claude Project. Paste a list of failing units with their process history, and ask: what's the ONE tool, step, or chamber they ALL share? I fed it twenty fails — it pointed at a single chamber in seconds. Save that prompt. Run it this week.