Semi E98.1

SEMI E98.1 defines the SECS-II message set that carries SEMI E98's Object-Based Equipment Model (OBEM) data between equipment and host — E98 defines the object hierarchy that represents a tool's chambers and modules as independently addressable objects, while E98.1 defines the actual wire-level messages a host uses to query or receive events from any specific object in that hierarchy. Without E98.1, OBEM's object hierarchy would be a data model with no standardized way to actually reach into it — a host would have no defined message format for asking "what is Chamber A's current state" or receiving an event the moment Chamber C faults — E98.1 is the protocol binding that makes OBEM's per-object addressing actually usable over SECS-II, the same role every other `.1` protocol spec plays for its parent data model.

SEMI E98 — OBEM object hierarchy
Chambers/modules modeled as independently addressable objects
SEMI E98.1 — SECS-II message bindingHow a host actually reaches a specific object
Host queries a specific object's state by address
Standardized SECS-II request/response, not a flat tool query
Object reports its own state-change events
Standardized SECS-II event reports, scoped to that object
Host addresses any chamber/module directly, on any compliant tool
Per-object granularity works the same way across vendors

The reason OBEM needed its own protocol spec rather than reusing GEM's standard event/status messages is that those messages were built around one flat tool-level state, with no addressing scheme for reaching a specific object inside a hierarchy — asking "what's Chamber B doing" requires a message format that can specify which object the question is about, which a flat GEM status report has no field for. E98.1 is what makes OBEM's structural advantage actually reachable: without a standardized per-object addressing scheme in the protocol itself, two vendors implementing OBEM's object model could still encode object addressing differently, forcing custom per-vendor logic to do the one thing OBEM exists to enable — querying a specific chamber directly.

SEMI E98.1 — Addressing a Specific Object the message format that reaches into E98's object hierarchy SEMI E98 — object hierarchy (Chamber A, B, C...) The structure: independently addressable components SEMI E98.1 — SECS-II messages that address a specific object Standardized query/event messages scoped to one object Same addressing scheme, every vendor's OBEM implementation

E98.1 is the piece that makes OBEM's whole value proposition real across a mixed-vendor fleet — the object hierarchy only delivers per-chamber visibility if every vendor's implementation exposes it through the same standardized SECS-II addressing, which is exactly what this protocol spec locks in.

Take SEMI E98.1 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