SECS/GEM: the protocol stack that runs semiconductor fabs

Every automated wafer fab speaks SECS/GEM. The SEMI Equipment Communications Standard (SECS) defines the messages, the Generic Equipment Model (GEM, E30) defines the behavior every tool must implement — state machines, collection events, alarms, spooling — and HSMS carries it all over TCP/IP. A lithography scanner, an etcher, and a metrology tool from three vendors all expose the same GEM interface upward, which is what lets a fab MES run hundreds of tools as one factory. For the fab-level data path around it, see semiconductor fab automation.

The layers, bottom up

HSMS (High-Speed SECS Message Services, E37) is the TCP/IP transport: connection management, message framing, and heartbeats over a single TCP connection per tool, usually initiated by the tool. It is deliberately simple — the complexity lives above it.

SECS-II (E5) defines the message dictionary: streams and functions (S1F1 "are you there", S6F11 event reports, S7Fxx process programs, and hundreds more) encoded in a binary list/item format. SECS-I (E4) is the legacy serial transport still found on older tools behind gateways.

GEM (E30) turns messages into a contract: defined equipment states (the GEM state machine every tool must implement), collection event reporting with linked data variables, alarm management, remote command handling, spooling during host outages, and clock synchronization. Compliance is verified against the GEM Compliance Statement — a standard checklist of required capabilities — which is the document to demand before accepting any tool.

What to get right at acceptance

Equipment acceptance is where GEM pays or costs for the next decade. Require the vendor's GEM compliance statement and test the claims that operations depends on: collection events fire with correct data for every production scenario (not just the demo recipe), alarms carry useful text and clear correctly, spooling survives a host outage and recovers without duplicate or lost events, and process program management (upload, download, verification) works through the host without operator console bypasses.

Plan the interface details jointly with MES, not after the tool arrives: the event-reporting model (which collection events, which variables attached), the trace data requirements for advanced process control, and the recipe-naming and versioning scheme. The historian tag naming guide and MES vs ERP checklist cover the naming and ownership disciplines that keep 300 tools' data joinable. Finally, treat interface froth as a lifecycle item: tool software upgrades routinely change GEM behavior, so every upgrade needs an interface regression test against the host — negotiated in the purchase contract, not discovered during production.