SECS/GEM refers to related SEMI standards used for communication between manufacturing equipment and a host. SECS-II describes message content, GEM describes equipment behavior over the link, and HSMS specifies a way to carry messages.
Updated
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
For a Chinese integration specification, retain stream and function identifiers, event names and example payload keys. Use the source revision and host interface guide to distinguish equipment behavior from transport settings. Confirm whether each message is an equipment event, a request or a reply.
Preserve the cited standards and their editions, along with the exact message identifiers, alarm IDs and payload fields. For Chinese deliverables, distinguish translated descriptions from machine-readable values. If the source gives only an event label, ask the interface owner whether the example represents a request, reply or equipment event.
Preparing a semiconductor file set for Chinese readers? Prepare interface strings and build checks →
Chinese document application
Illustrative wording only. Confirm the rendering against the actual source and approved project terminology.
This is an illustrative operator label. Keep the actual event ID exactly as supplied and translate the operator-facing label in the wording column.
Confirm that the Chinese label maps to the same event ID in the test interface and manual.
Include the message list, field definitions, actual interface or matching screenshots and build-review owner.
SEMI · Introduction to SECS/GEM
Technical terms need checking against the source, approved product terminology and related specifications. Keep units, parameter conditions and document versions aligned across the file set.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Japanese-to-Chinese documentation for a listed Japanese semiconductor manufacturer.
Read the published project →Corporate reporting and disclosure documentation, delivered across successive annual cycles.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Semiconductor solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.