Semi E30.1

SEMI E30.1 and E30.5 define ISEM (Inspection and Review Specific Equipment Model) and MSEM (Metrology Specific Equipment Model), two specializations of the base GEM standard (SEMI E30) that add the specific data objects and behaviors inspection/review tools and metrology tools need but that generic GEM doesn't define on its own. GEM's base model gives every piece of equipment a shared vocabulary for alarms, remote commands, and status variables, but it has nothing to say about defect-review workflows or measurement-result reporting — those are domain-specific needs that only inspection and metrology tools have, which is exactly why SEMI split them into their own specific equipment models rather than bloating the base GEM standard with concepts most equipment never uses.

ISEM's defect-specific additions let a host query structured defect records — location, classification, size — directly through the same GEM-style interface the tool already uses for alarms and status, rather than needing an entirely separate, non-standard reporting channel just for inspection results; MSEM does the equivalent for metrology tools, standardizing how a measurement result gets reported and tied back to the specific recipe and reference point that produced it. The reason this split-by-equipment-class approach matters is that a fab's host software can be written once against each specific equipment model and then work correctly against any vendor's inspection tool or any vendor's metrology tool, instead of every tool vendor inventing its own proprietary extension on top of plain GEM to cover the gap E30 alone leaves open.

E30, E30.1, and E30.5 together are what let a host's GEM-compliant software work correctly across a mixed fleet of generic process tools, inspection tools, and metrology tools without any of them needing a proprietary extension to fill a gap the base standard left open.