Semi E109.1

SEMI E109.1 defines the SECS-II message set that carries SEMI E109's Reticle and Pod Management (RPMS) data between equipment and host — E109 defines what a fab needs to track about each reticle (identity, location, exposure count, requalification status), while E109.1 defines the actual wire-level messages a lithography tool uses to report that data automatically. Without E109.1, RPMS's reticle-lifecycle model would describe what the host needs to know in the abstract, but a scanner or stepper would have no standardized way to actually report "reticle X was just used, exposure count incremented" or "reticle Y has arrived at the reticle stage" — E109.1 is the protocol binding that turns RPMS into real-time tracking data, the same role every other dot-one protocol spec plays for its parent model.

The reason RPMS needed its own SECS-II protocol spec rather than folding reticle events into a generic equipment-status message is that exposure-count accuracy depends entirely on every single use being reported — a missed or delayed exposure-count update means a reticle could exceed its qualified usage limit without the host ever knowing, which is a real yield and quality risk, not just a bookkeeping inconvenience. E109.1 closes that gap by giving reticle-use events their own standardized, immediate SECS-II reporting path, so the exposure count RPMS relies on for requalification scheduling is always accurate in real time, across every lithography tool in the fab regardless of vendor — a level of reliability a generic, lower-priority status message was never built to guarantee.

E109.1 is what keeps RPMS's exposure-count data trustworthy enough to actually drive requalification scheduling — the protocol layer's reliability matters more here than for most other dot-one specs, because an undercounted reticle isn't just a data gap, it's a yield-risk waiting to be discovered after the fact.