Semi E120.2

SEMI E120.2 defines a Protocol Buffers (protobuf) encoding for the Common Equipment Model — the same status-variable, equipment-constant, alarm, and collection-event information E120 defines and E120.1 validates as XML, re-expressed as a compact binary protobuf message a host can parse with far less overhead than an XSD-validated XML document. E120.1 gives CEM a rigorous XML grammar, but XML parsing and schema validation carry real CPU and bandwidth cost at fab scale, where a host may be loading or re-loading equipment models for hundreds of tools — E120.2 is the alternative serialization standard that keeps the same equipment-model content but swaps the wire format for one built for machine-to-machine efficiency rather than human-readability or document tooling.

The reason CEM needed a second encoding standard rather than staying XML-only is that E120.1's XSD-validated XML format, while rigorous, isn't the cheapest format to parse repeatedly — a host application reloading dozens or hundreds of tools' equipment models benefits from a binary format that skips text parsing and schema-validation overhead, provided the underlying information is still exactly equivalent to what the XML version carries. E120.2 is what gives equipment vendors and host developers that choice: publish CEM as E120.1-validated XML when document tooling and human readability matter, or as E120.2's protobuf encoding when parsing speed and payload size matter more, with both representing the identical equipment-model content so a host's internal data model doesn't change based on which wire format it received.

E120.2 is what keeps CEM relevant as fabs scale equipment-model loading to hundreds of tools: rather than forcing every host integration to absorb XML parsing overhead regardless of use case, it gives the industry a binary alternative that carries the exact same information, so the choice between E120.1 and E120.2 comes down to performance needs rather than any difference in what the equipment model actually describes.