Semiconductor fab automation: the data path from lot to tool

Semiconductor fabs make the relationship between material, equipment, recipe, and history unusually visible. A wafer lot moves through many tools and process steps; the value of a measurement depends on which lot, recipe revision, chamber, and time produced it. Automation is therefore as much about identity and traceability as it is about motion.

Follow the lot

The lot or carrier is the business object that connects dispatch, material control, quality, and production history. Automated material handling systems (AMHS) move carriers between stockers, bays, and tools, while equipment automation manages load ports, recipes, and process execution. A location event without a lot identity is operationally incomplete.

Keep the identifiers consistent from MES dispatch through equipment interface and return. Record recipe version, operator or service action, tool state, chamber, carrier, and material condition. When a measurement is out of family, the system needs enough context to hold the affected population rather than only raising a generic equipment alarm.

Integrate without hiding the tool

Equipment interfaces can report state, alarms, variables, and process results, but the integration must preserve the tool’s local interlocks and safe modes. MES or a host system can authorize a recipe and dispatch a lot; it should not bypass equipment protection. Separate the command path from high-volume telemetry and make communication failures visible.

Use event time, sequence numbers, and quality. Buffer at the edge when the host link is interrupted, but keep the tool’s behavior deterministic and auditable. Historians and analytics should be able to answer which data was known at the time, not only reconstruct a neat story later.

The operational test is a genealogy query: given a lot, can the team identify every tool, chamber, recipe revision, material movement, alarm, hold, and release decision that affected it? If the answer depends on joining spreadsheets after the fact, the automation boundary is leaking. Start with one process module, prove the identity and timestamp contracts, then extend the pattern to the next tool family.

The AMR versus AGV guide explains the material-movement distinction in simpler terms. The MES integration checklist covers ownership and corrections across systems. For the wider operations map, Understanding the Shop Floor is a practical companion ebook.