Semi E30

SEMI E30 is the formal standard number for GEM (Generic Equipment Model) — when an equipment spec sheet says "SEMI E30 compliant," it means the same thing as "GEM compliant," because E30 is simply GEM's official designation within the SEMI numbering system. Where SECS-II (E5) defines the message grammar and HSMS (E37) defines the transport, E30 is the behavioral layer on top: it specifies what capabilities a piece of equipment must implement — state models, event reporting, alarm management, remote control — to be considered a well-behaved, host-controllable tool.

The equipment state model is the part of E30 that most directly shapes how a tool can actually be automated, because the host needs a small, predictable set of states to make any dispatch or scheduling decision. E30 defines standard top-level states like Offline, Host-Offline, Local, and Remote, plus a processing-state hierarchy underneath Remote (Idle, Setting Up, Ready, Executing, Pausing, Paused) — every GEM-compliant tool reports its current position in this same state tree, which is what lets MES dispatch logic ask "is this chamber Idle and Remote" the same way for an etch tool from one vendor and a deposition tool from another.

Local versus Remote is the control-authority split that makes GEM's remote-control capability meaningful. In Local mode, an operator at the tool's own console controls recipe selection and start/stop; in Remote mode, that authority transfers to the host, which can select a recipe, start a run, and monitor progress entirely through SECS-II messages without anyone touching the equipment. A fab's dispatch automation only works at all because tools spend their production time in Remote — a tool an operator leaves in Local blocks MES dispatch just as effectively as a hardware fault, even though nothing is mechanically wrong.

E30 compliance is a checklist a vendor can genuinely pass or fail, which is what makes it enforceable rather than aspirational. A tool that reports Executing when it's actually idle, or that doesn't generate a collection event on every state transition, or that can't accept a remote recipe-select command, isn't E30 compliant regardless of what the spec sheet claims — and a fab's equipment-engineering team typically runs a formal GEM conformance test during tool acceptance specifically to catch these gaps before the tool goes into production, because debugging a dispatch failure caused by an incomplete state model weeks after install is far more expensive than catching it at acceptance.

E30/GEM is the standard that makes the rest of this site's fab-automation entries — MES dispatch, chamber qualification gates, load-port carrier events — all speak the same state language regardless of which vendor built which tool, which is the entire point of it existing as a numbered SEMI standard instead of being left to each equipment maker's own convention.