What is SECS/GEM?

GEM (Generic Equipment Model) is a standard implementation of the SECS-II standard (SEMI E5). Most equipment in semiconductor, surface mount technology, electronics assembly, photovoltaic, LED, flat panel display, and other manufacturing industries provide a SECS/GEM interface so that factory host software can communicate with the equipment for monitoring and controlling purposes.

Because the GEM standard was written with very few semiconductor-specific features, it can be applied to virtually any manufacturing equipment in any industry. All GEM-compliant equipment share a consistent interface and certain consistent behavior.

Communication Architecture
FACTORY HOST
MES / Cell Controller / Line Manager
HSMS (TCP/IP) or SECS-I (RS-232)
EQUIPMENT
GEM Interface Software

How Equipment and Host Communicate

GEM equipment can communicate with a host using TCP/IP (HSMS standard, SEMI E37) or RS-232 serial protocol (SECS-I standard, SEMI E4).

🌐

HSMS (SEMI E37)

High-Speed Message Service — TCP/IP based network communication. Used almost exclusively in modern factories. Maximum message size of approximately 4.3 GB. More convenient and better aligned with modern manufacturing environments.

📟

SECS-I (SEMI E4)

RS-232 based serial communication. The legacy protocol that has been largely phased out due to inherent speed limitations. Maximum message size of approximately 8 MB. Replaced by HSMS in most modern installations.

SECS-II Messages

Once communication is established, the host and equipment exchange SECS-II messages. Each message is identified by a stream number (0–255) and function number (0–255). An odd-numbered function is a primary message; the consecutive even-numbered function is its secondary reply. Messages are sent as structured binary data to maximize content while minimizing bandwidth.

Key GEM Standard Features

The GEM standard defines a comprehensive set of features for equipment-to-host interaction. Here are the key capabilities.

Communication & Establishment +
The GEM standard defines how the equipment and the host initially establish communication and how communication is re-established when broken. An on-line identification method verifies the equipment's hardware and software identity. Terminal service features allow the host operator and equipment operator to exchange text manually.
Control State Model +
The GEM standard outlines a control state model defining the level of cooperation between the host and equipment operator. Equipment with a GEM interface provides three basic levels of host control. Remote control capabilities permit the host to send commands like START, STOP, PAUSE, RESUME, and ABORT to control equipment processing. Equipment constants allow the host to configure many aspects of equipment behavior.
Operation Notification (Events & Alarms) +
Collection events and alarms allow the host to monitor equipment operations in detail. Equipment alarms notify the host when potentially dangerous activity is detected and subsequently resolved. The host determines which events and alarms are enabled for notification, and the equipment sends messages only for the specified events to minimize network traffic.
Data Gathering (6 Methods) +
GEM defines six methods of gathering data: (1) Request status variable values at any time; (2) Request equipment constant values; (3) Request reports containing mixed variable types; (4) Define reports attached to collection events for automatic data transmission; (5) Define traces for periodic status variable transmission at set intervals; (6) Configure limits monitoring so the equipment notifies when a value crosses a threshold.
Process Program (Recipe) Management +
A process program is the set of instructions, settings, and parameters that determine the processing environment. The host can download, upload, delete, and list process programs. The equipment operator can send or request programs from the host. The host can select a process program for execution using remote commands.
Spooling +
Spooling provides the means for the equipment to queue information intended for the host during a communication failure. When communication is restored, the host can purge or request the queued data. The host can configure which information is queued, how a full queue is handled, the queue size, and how queued information is recovered.

SEMI Standards Overview

Key SEMI standards that form the SECS/GEM and GEM300 communication framework.

Standard Name Description
SEMI E4 SECS-I RS-232 serial communication protocol for host/equipment communication (legacy, replaced by HSMS).
SEMI E5 SECS-II Defines the message content, format, and structure for all GEM communication. The foundation of SECS/GEM.
SEMI E30 GEM Generic Equipment Model — the standard implementation of SECS-II that defines equipment behavior and features.
SEMI E37 HSMS High-Speed Message Service — TCP/IP network communication, the modern replacement for SECS-I.
SEMI E39 Object Services Provides standard object management services referenced by GEM300 standards.
SEMI E40 Process Job Management Manages processing jobs on equipment — part of the GEM300 standard suite.
SEMI E87 Carrier Management Carrier tracking and management for 300mm equipment. Core GEM300 standard.
SEMI E90 Substrate Tracking Tracks individual substrates (wafers) through processing. Core GEM300 standard.
SEMI E94 Control Job Management High-level control jobs that manage process job execution. Core GEM300 standard.
SEMI E116 Equipment Performance Tracking Tracks and reports equipment performance metrics. Core GEM300 standard.
SEMI E148 Time Sync Time synchronization between host and equipment, referenced by GEM300 and PV2.
SEMI E10 OEE Overall Equipment Effectiveness — standard for measuring and reporting equipment performance.

GEM Terminology

Key terms and concepts used in SECS/GEM implementations.

Alarm

An abnormal situation on the equipment that may endanger people, equipment, or material. GEM allows the host to be notified when alarm conditions are detected and cleared.

Collection Event

A detectable occurrence significant to the equipment and host. GEM allows the host to be notified when events occur, enabling detailed activity tracking.

Status Variable

Parameters that can be sampled in time (e.g., temperature, quantity of consumable). Status values always contain valid information and can be requested by the host.

Data Variable

Values that may only be valid upon the occurrence of a particular event. Provides information specifically related to the event context.

Equipment Constant

Settings that are adjustable by the host. Used to configure GEM state machines and control various aspects of equipment behavior.

Process Program (Recipe)

The set of instructions, settings, and parameters that determine the processing environment seen by the manufactured object.

Report

A set of variables predefined by the equipment or defined by the host. Used to gather status variable, data variable, and equipment constant values.

HSMS-SS

High-Speed Message Service Single Session — TCP/IP network communication standard. Only one host client can use a specific port at a time. Has effectively replaced SECS-I.

GEM Compliance

GEM compliance is self-proclaimed — there is no official certification. Equipment must include a GEM compliance statement documenting which features are implemented.

Frequently Asked Questions

How long does it take to implement a SECS/GEM interface? +
Building from scratch can take a few person-years to develop production-worthy software. Using a commercial SDK like NexSecs/Gem's SDK dramatically reduces this timeline — typically to weeks or a few months, depending on equipment complexity.
How fast is a SECS/GEM interface? +
Modern SECS/GEM implementations support trace data collection with rates specified in milliseconds. In practice, some factories request data at rates of about 10Hz (1 set of data every 100ms). Because the SECS-II and HSMS message format is very efficient, a lot of data can be transferred using minimal network bandwidth.
Can more than one host connect to a single piece of equipment? +
Yes, but not many GEM interface software products support this capability. NexSecs/Gem's SDK has a built-in multiple client (multi-host) feature that simplifies communicating with more than one host at a time using HSMS-SS. Each client uses a unique port.
How does equipment become GEM certified? +
There is no official GEM certification. GEM compliance is self-proclaimed. Equipment must include a GEM compliance statement in its documentation. The statement declares which features are implemented and whether they comply with the standards. Some features are optional — equipment can be compliant with a limited implementation.
How much network bandwidth does SECS/GEM require? +
Bandwidth utilization is largely determined by the host's configuration — which events and alarms are enabled, and the frequency of data gathering. If all events and alarms are disabled, a GEM connection will be nearly silent. The binary message format is very efficient, allowing large amounts of data to be transferred with minimal bandwidth.

Ready to Implement SECS/GEM?

Our team of SECS/GEM experts can help you build compliant equipment interfaces or connect your factory floor.