Semi E90.1

SEMI E90.1 defines the SECS-II message set that carries SEMI E90's substrate-tracking data between equipment and host — E90 defines the substrate ID, location, and processing-history data model a tool must maintain per wafer, while E90.1 defines the actual wire-level messages that move that per-substrate data over the SECS-II link automatically. Without E90.1, E90's substrate-tracking model would describe what a tool needs to know about each wafer in the abstract, but a host would have no standardized way to actually read which substrate currently occupies which process position, or receive a notification the moment a substrate's tracked location changes — E90.1 is the protocol binding that turns substrate tracking into real-time, automatic data exchange rather than a periodic manual query.

SEMI E90 — substrate ID, location, processing-history model
What a tool must track per individual wafer
SEMI E90.1 — SECS-II message bindingHow per-substrate tracking data actually travels over the wire
Tool reports substrate location-change events
Standardized SECS-II event reports, per wafer
Host requests current substrate map on demand
Standardized SECS-II request/response messages
Host maintains real-time wafer-level location data automatically
No per-vendor polling scheme or custom integration

The reason substrate tracking needed its own SECS-II protocol spec rather than a generic status message is that per-wafer location data has to update in near-real time and at fine granularity — a host tracking lot genealogy or diagnosing a mis-process needs to know exactly which chamber or slot held which specific wafer at which moment, and a generic equipment-status message carries no guarantee of that granularity or timing across different tool vendors. A fab correlating a yield excursion back to a specific chamber exposure needs every tool's substrate-location reporting to use the same message structure and update cadence, which is exactly the integration cost E90.1 eliminates — standardizing the SECS-II layer underneath E90's tracking model the same way E87.1 did for carrier data and E58.1 did for ARAMS.

SEMI E90.1 — Substrate Tracking Protocol Binding data model vs. the wire-level messages that carry it SEMI E90 — substrate ID, location, processing history The vocabulary: what a tool tracks per individual wafer SEMI E90.1 — SECS-II messages carrying that vocabulary Standardized per-wafer event reports and request/response structures Same update cadence and message structure, every vendor

E90.1 is what makes wafer-level traceability actually real-time across a mixed-vendor fab rather than a batch-reconciled approximation — the protocol layer is what turns E90's tracking model into data a host can trust the moment something changes, not just after the fact.

Take SEMI E90.1 further

Ask the copilot about this term, or have our engineers assess it against your process.