Semi E82

SEMI E82 defines the Interbay/Intrabay AMHS Specific Equipment Model (IBSEM) — the GEM-based behavior model for the automated material-handling-system (AMHS) vehicles and track that move FOUPs between bays (interbay) and within a single bay (intrabay) in a 300 mm fab, as distinct from the stocker and tool-level equipment models that cover storage and processing. A 300 mm fab's AMHS is really two coordinated transport layers — the interbay system that moves lots across the whole fab on a backbone loop, and the intrabay system that handles shorter moves within one process bay — and IBSEM is what lets a host system address both of those transport layers through the same standardized GEM state/event model it already uses for process equipment, rather than treating AMHS vehicles as a special case outside the fab's normal equipment-communication framework.

300 mm fab AMHS — two coordinated transport layers
Interbay backbone loop + intrabay local moves
SEMI E82 — IBSEM behavior modelGEM-based state/event model applied to AMHS vehicles
Interbay vehicle states and events
Moving, idle, fault — reported in standard GEM terms
Intrabay vehicle states and events
Same model, shorter-range local transport
Host tracks AMHS vehicles the same way it tracks process tools
One communication framework, not a separate AMHS-only protocol

The reason AMHS transport needed its own GEM-based equipment model rather than being folded into the stocker or tool equipment models is that a transport vehicle's relevant states are genuinely different from either — a stocker's states describe storage-slot occupancy and retrieval, a tool's states describe processing steps, but a vehicle's states describe location, motion, and routing status, none of which map cleanly onto either existing model. Without IBSEM, a fab would either have to bolt AMHS tracking onto an ill-fitting existing equipment model or build a proprietary, non-GEM interface just for vehicle status — both of which break the host's ability to monitor the fab's transport layer with the same tools and dashboards it already uses for every other piece of GEM-compliant equipment, which is exactly the integration gap E82 closes by giving interbay and intrabay vehicles their own standard-compliant behavior model.

SEMI E82 — IBSEM Covers Two Transport Layers one GEM model, applied to both interbay and intrabay vehicles Interbay AMHS Fab-wide backbone loop moving lots between bays States: moving, idle, fault reported via GEM/SECS-II Intrabay AMHS Local moves within one process bay Same IBSEM state/event model as interbay vehicles One standard model for a layer that otherwise fits neither stocker model (storage slots) nor tool model (process steps)

E82 is what keeps a fab's transport layer legible to the same host infrastructure as everything else: without IBSEM, AMHS vehicle status would either be invisible to standard GEM tooling or require a bespoke integration per vehicle vendor — IBSEM is the standard that makes "where is this lot right now" answerable through the exact same equipment-communication path as "what state is this process tool in."

Take SEMI E82 further

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

Ask CFSGPT about this → Request a technical assessment → Open the CFS app