Semi

SEMI is the global trade association and standards body for the semiconductor and electronics manufacturing supply chain — equipment makers, materials suppliers, and chipmakers all participate in its standards committees, and the resulting SEMI standards are what let a load port built by one vendor physically and electronically interoperate with a robot, AMHS, and host software built by three other vendors. Without SEMI standards, every fab would effectively need custom integration work for every new tool it buys; with them, "300 mm FOUP" or "GEM-compliant equipment" means the same physical and electrical thing regardless of which company built it.

Industry committee
Equipment, materials, and fab member companies
Standards families a fab actually touches daily
E-series
Equipment automation: E84 AMHS, E87 carrier mgmt, E90 substrate tracking
E30 / E37
GEM and HSMS — the SECS communication layer
M-series
Materials and wafer/FOUP mechanical specs
S-series
Safety guidelines for equipment design
Any compliant tool
Interoperates without custom integration

A single SEMI number can mean a mechanical spec, a communication protocol, or a safety guideline — the prefix tells you which. SEMI E84 defines the hardware handshake between an AMHS vehicle and a load port; SEMI E87 defines carrier management and verification; SEMI E30 is GEM itself, the equipment-to-host communication model; SEMI E37 is HSMS, the TCP/IP transport that SECS-II messages actually ride on top of. A FOUP's physical dimensions, door geometry, and kinematic coupling pins are specified separately, in SEMI's materials-handling standards, which is why a FOUP from one manufacturer sits correctly on any compliant load port from any other.

SEMI Standards — The Shared Vocabulary of the Fab one number, one fixed meaning, enforced across every vendor SEMI standard E84 — AMHS physical handoff load port ↔ vehicle handshake E87 — Carrier mgmt carrier ID, state, slot-map verification E30 — GEM equipment-to-host model M-series FOUP geometry, wafer mechanical spec every vendor builds to the same numbered spec — that's what lets a mixed-vendor fab floor actually work together

SEMI itself doesn't build or certify equipment — it publishes and maintains the specifications, and the industry self-polices compliance through interoperability. A tool vendor claims "SEMI E84 compliant" or "GEM300 compliant," and the real test happens when that tool gets installed next to AMHS and host software from other vendors — if the physical handshake, timing, and message sequences all work without custom patches, the compliance claim holds up. Fabs and vendors both participate in SEMI's working groups precisely because getting a new standard wrong, or ambiguous, creates exactly the kind of integration cost the standards exist to prevent.

For anyone reading equipment documentation, the practical habit is simple: when you see "SEMI E##" or "SEMI M##," that number is a lookup key, not a description. The equipment manual will reference the standard by number rather than re-explain it, assuming the reader (or the integrating engineer) already knows, or will look up, what E84 versus E87 versus E90 actually governs — which is also why the GEM, E84, and E87 concepts covered under this site's own gem-gep entry are worth reading together with this one.

SEMI standards are the reason a fab can mix load ports, robots, AMHS, and host software from entirely different vendors and still have them work as one coherent automation system — unglamorous committee work that turns into the physical and electronic compatibility every other piece of fab automation quietly depends on.

Take SEMI further

Ask the copilot about this term, or have our engineers assess it against your process.