Semi E102

SEMI E102 defines the CIM Framework Material-Transport and Storage Component, the concrete functional specification for the domain that SEMI E81's architecture labels "material handling" — the actual behavior a software component has to implement to track and command wafer-carrier movement between stockers, load ports, and AMHS vehicles across a fab. Where E81 only establishes that a material-transport domain exists with certain boundaries, and E96/E97 supply the general technical architecture and shared vocabulary any domain component is built from, E102 is the domain-specific specification — what operations a material-transport component must support (move requests, storage allocation, transport status queries) and what data it must track (carrier location, transport job state) to actually fulfill the material-handling domain's responsibilities.

SEMI E81 designates a material-transport domain
Conceptual boundary only — no behavior defined yet
SEMI E102 material-transport component specBuilt using E96/E97's general architecture and vocabulary
Move request + storage allocation operations
What the component must let other domains ask for
Carrier location + transport job state tracking
What the component must know and report
Material-transport domain is actually implementable
A vendor can build a conformant component from this spec

SEMI E102 is a concrete example of how the whole CIM Framework stack is meant to be used in practice — a vendor building a material-transport system doesn't start from scratch, and doesn't stop at reading E81's domain boundaries either; they read E102's domain-specific functional requirements, express them using E96's architectural patterns, and build the actual interfaces out of E97's shared global declarations, so the resulting component is both functionally complete for material transport and technically interoperable with every other domain's components in the fab. This layered relationship — E81 scopes, E96/E97 supply shared architecture and vocabulary, E102 (and its siblings like E105 for scheduling) supply domain-specific function — is the general pattern every concrete CIM Framework domain component follows, not something unique to material transport.

SEMI E102 — Where the CIM Framework Layers Meet domain scope + shared architecture + domain-specific function SEMI E81 — material-transport domain exists, has these boundaries SEMI E96 — architecture style SEMI E97 — shared vocabulary SEMI E102 — material-transport domain-specific spec move requests, storage allocation, carrier location, transport job state built from the layers above, concrete enough for a vendor to actually implement Same layered pattern applies to SEMI E105 (scheduling) and every other concrete domain component in the CIM Framework

SEMI E102 is the material-handling counterpart to SEMI E105 (the CIM Framework scheduling component), both concrete domain specifications built on the same E81/E96/E97 foundation, and E102's output feeds directly into the physical automated-material-handling standards elsewhere in this catalog — SEMI E82 (Interbay/Intrabay AMHS Specific Equipment Model) and SEMI E88 (AMHS storage equipment model) describe the equipment-level behavior that a conformant E102 software component ultimately commands.

Take SEMI E102 further

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

Ask CFSGPT about this → Request a technical assessment → Open the CFS app