Semi E38

SEMI E38 defines Cluster Tool Module Communications (CTMC), the standard that lets a cluster tool's individual process modules — each physically separate chamber bolted onto a shared central handler — communicate with a host as either one unified piece of equipment or as several independently addressable subordinate entities, depending on how the tool is configured. A cluster tool's mechanical architecture (SEMI E21/E22's transport and exclusion-volume standards) says nothing about how the host talks to it; CTMC is the piece that defines whether the host sees "one tool" or "one handler plus N chambers, each with its own session," and it's exactly this choice that determines whether a cluster tool uses HSMS-SS or HSMS-GS underneath it.

The subordinate model is where CTMC does its real work: SEMI E38.1 specifies the HSMS/SECS-II environment that lets each process module behind the handler act as its own logical entity with its own Session-ID, which is the exact multi-session scenario SEMI E37.2's HSMS-GS mode exists to carry — a cluster tool exposing per-chamber sessions is the canonical real-world case for HSMS-GS, not a hypothetical one. This matters for fab integrators because the subordinate model gives a host finer-grained visibility (a recipe fault in one chamber doesn't have to be inferred from the whole tool's status) at the cost of more complex connection-handling code that has to track multiple Session-IDs correctly — exactly the failure mode called out when HSMS-SS-shaped code is pointed at an HSMS-GS connection.

CTMC's two models are the direct bridge between the cluster tool's physical architecture (E21/E22) and the transport-layer session mode (E37.1/E37.2) a host actually connects with — choosing unified or subordinate at CTMC's level is what decides which of those two transport modes the integration ends up needing.