SEMI E30 — GEM
SEMI E30 defines the externally visible behavior expected from GEM equipment, including communication, control, state, data collection, alarms, variables, recipes, terminal services, and remote commands.
Area
Communications
Profile coverage
200 mm Tool Standards · 300 mm Tool Standards · 300 mm Overhead Automation
Purpose
GEM standardizes how a factory host observes and controls manufacturing equipment through SECS-II. It defines required behavior and capabilities so integration does not depend entirely on equipment-specific messages and undocumented state transitions.
Where it applies
GEM is widely used across semiconductor manufacturing and is not inherently limited to 200 mm or 300 mm tools. The required and optional capabilities for a project come from the current standard, customer specification, equipment function, and agreed interface documentation.
Who implements it
The equipment exposes a coherent GEM model backed by actual Tool Control Software state. The host configures reports, receives events and alarms, reads variables, manages online/control transitions, and invokes authorized equipment capabilities.
Relationships and dependencies
- Uses SEMI E5 message content over E37 HSMS or, for legacy systems, E4 SECS-I.
- Provides the behavioral foundation extended by the GEM300 standards.
- Is assumed by AMHS specific equipment models such as E82 and E88.
Practical implementation guidance
- Design the equipment model and data dictionary before wiring individual message handlers.
- Drive collection events, alarms, variables, and state transitions from one authoritative equipment state model.
- Validate scenarios with a host emulator and customer-specific acceptance tests, not only isolated messages.
Common mistakes
- Advertising GEM because the tool can answer a few common S1 messages.
- Reporting events before related data values and state are internally consistent.
- Treating online, equipment control, and process state as interchangeable concepts.