Are you GEM Compliant?
Every GEM compliant equipment must include a GEM compliance statement in the documentation. The table declares not only which features are implemented, but also indicates whether or not implemented features comply to the standards. This implies that an equipment can implement a limited GEM implementation and still be considered GEM compliant. Some of the GEM features simply are not appropriate for all manufacturing equipment. If a feature is implemented, but not quite compliant, then simply document the exception. Below is a sample GEM compliance statement.
The SECS/GEM standard requires relatively few features. If a machine implements a minimum GEM interface with only the required data variables, status variables, equipment constants, and collection events then the GEM interface is only marginally useful. The GEM interface's full value is realized only when the equipment supplier provides additional machine-specific alarms, data variables, status variables, equipment constants and collection events.
- Learn more about the SECS/GEM standards
- Download the white paper on SEMI SECS/GEM
- View the sample GEM Compliance Statement
- Additional GEM Resources
GEM Compliance Statement Sample
| GEM Compliance Statement | ||
|---|---|---|
| FUNDAMENTAL GEM REQUIREMENTS | IMPLEMENTED | GEM COMPLIANT (See Note 1) |
| State Models | rYes rNo | rYes rNo |
| Equipment Processing States | rYes rNo | |
| Host-Initiated S1 = F13/F14 Scenario | rYes rNo | |
| Event Notification | rYes rNo | |
| On-Line Identification | rYes rNo | |
| Error Messages | rYes rNo | |
| Documentation | rYes rNo | |
| Control (Operator Initiated) | rYes rNo | |
| ADDITIONAL CAPABILITIES | IMPLEMENTED | GEM COMPLIANT (See Note 2) |
| Establish Communications | rYes rNo | rYes rNo |
| Dynamic Event-Report Configuration | rYes rNo | rYes rNo |
| Variable Data Collection | rYes rNo | rYes rNo |
| Trace Data Collection | rYes rNo | rYes rNo |
| Status Data Collection | rYes rNo | rYes rNo |
| Alarm Management | rYes rNo | rYes rNo |
| Remote Control | rYes rNo | rYes rNo |
| Equipment Constants | rYes rNo | rYes rNo |
| Process Program Management | rYes rNo | rYes rNo |
| Material Movement | rYes rNo | rYes rNo |
| Equipment Terminal Services | rYes rNo | rYes rNo |
| Clock | rYes rNo | rYes rNo |
| Limits Monitoring | rYes rNo | rYes rNo |
| Spooling | rYes rNo | rYes rNo |
| Control (Host-Initiated) | rYes rNo | rYes rNo |
Note 1: Do not mark YES unless all fundamental GEM requirements are implemented and GEM Compliant.
Note 2: Additional capabilities can not be marked GEM-compliant unless the fundamental GEM requirements are GEM compliant.
Resources for SECS/GEM SEMI Standards
- Download the complete white paper on the SEMI SECS/GEM Standards
- Learn more about High-Speed SECS Messaging (HSMS) and SECS-II(SEMI E5)
- Check out Cimetrix's Connectivity Products for the SECS/GEM Standards
- Visit the SEMI website
