- →What Is GEM300?
- →GEM vs GEM300: Key Differences
- →Core GEM300 Standards Explained
- →Why GEM300 Matters for AI Integration
- →Implementing GEM300: Practical Considerations
What Is GEM300?
GEM300 is a collection of SEMI standards that extend the Generic Equipment Model (GEM, SEMI E30) for 300mm semiconductor manufacturing. While GEM handles basic equipment-to-host communication, GEM300 adds the automation capabilities needed for 300mm fabs where wafers are transported in FOUPs (Front Opening Unified Pods) and handled entirely by automated systems — no human touches the wafers.
The “300” refers to 300mm (12-inch) wafer diameter, which is the current mainstream production format. 300mm fabs require higher automation levels than 200mm fabs because the wafers are too heavy and valuable for manual handling.
GEM vs GEM300: Key Differences
| Feature | GEM (E30) | GEM300 |
|---|---|---|
| Wafer size | Any (typically 150/200mm) | 300mm |
| Carrier management | Not defined | E116 (FOUP handling) |
| Process jobs | Basic recipe control | E40 + E94 (Control Jobs + Process Jobs) |
| Substrate tracking | Limited | E90 (individual wafer tracking) |
| Module process | Not defined | E157 (multi-chamber coordination) |
| Equipment terminal | Not defined | E172 (GUI standards) |
| Automation level | Semi-automated OK | Full automation required |
Core GEM300 Standards Explained
E116: Equipment Performance Tracking (Carrier Management)
E116 defines how equipment communicates carrier (FOUP) arrival, departure, and status to the host. In a 300mm fab, the AMHS (Automated Material Handling System) delivers FOUPs to load ports. The equipment must report carrier events so the MES knows exactly where every lot is.
E87: Carrier Management (CMS)
E87 specifies the Carrier Management state model, defining states like NOT ACCESSED, IN ACCESSED, and CARRIER COMPLETE. This ensures the host and equipment agree on carrier lifecycle events.
E90: Substrate Tracking
E90 tracks individual wafers (substrates) through multi-chamber cluster tools. When a wafer moves from the load lock to chamber 1, then chamber 2, E90 reports each transition. This enables per-wafer process history — critical for yield analysis and traceability.
E40 + E94: Process and Control Jobs
These standards define how the host specifies what to do with wafers:
- E94 (Control Job): A high-level instruction like “process these 25 wafers from FOUP A using recipe X”
- E40 (Process Job): The detailed execution: which chamber, which steps, in what order
E157: Module Process Tracking
E157 tracks processing at the module (chamber) level in cluster tools. A cluster tool might have 4 process chambers, 2 load locks, and a transfer robot. E157 reports what each module is doing, enabling the host to optimize scheduling and detect bottlenecks.
Why GEM300 Matters for AI Integration
GEM300 compliance is the foundation for AI-powered semiconductor manufacturing:
- Per-wafer data: E90 substrate tracking provides the granular data AI models need for virtual metrology and run-to-run control
- Real-time events: Equipment state transitions and carrier events enable real-time monitoring and FDC
- Recipe control: E40/E94 process jobs provide the interface for AI to adjust recipe parameters in real-time
- Multi-chamber optimization: E157 data enables AI to optimize wafer routing through cluster tools
Implementing GEM300: Practical Considerations
For equipment OEMs looking to implement GEM300:
- Start with GEM: Ensure solid E30/E37/E5 compliance before adding GEM300 extensions
- Use modern drivers: Open-source SECS/GEM drivers (like MST Python SECS/GEM driver) support GEM300 state models out of the box
- Test with simulators: GEM300 certification requires extensive testing — use host simulators before connecting to real MES
- Plan for data volume: GEM300 generates significantly more data than basic GEM. Ensure your equipment controller can handle the throughput
The Future: Beyond GEM300
As the industry discusses standards for next-generation fabs (High-NA EUV, Gate-All-Around, backside power delivery), the communication requirements will only increase. The integration of AI at the equipment level — through platforms like NeuroBox — requires robust GEM300 compliance as the data backbone.
We open-sourced our SECS/GEM Python driver. 3 lines of code to connect. 15,000+ downloads, 40+ contributors.
View Open-Source Driver →Discover how MST deploys AI across semiconductor design, manufacturing, and beyond.