Semi E123

SEMI E123 defines the Handler Specific Equipment Model (HSEM) — the set of status variables, equipment constants, alarms, and collection events specific to device handlers (the equipment that physically moves singulated die or packaged parts between a tester, a tray, or a tube/tape output) — built as a specialization of E120's generic Common Equipment Model, the same pattern E122's TSEM already applies to testers. A handler's operationally meaningful data — which output bin a part was sorted to, tray/tube fill level, pick-and-place cycle status, jam/misalignment alarms — has no natural home in generic CEM concepts or in TSEM's tester-focused vocabulary, so HSEM gives handler equipment its own defined, vendor-neutral model built around what a handler actually reports as it moves parts in and out of test.

Device handler needs to publish its equipment model to a host
Output-bin sort, tray/tube fill, jam alarms aren't CEM or TSEM concepts
SEMI E123 — HSEM, a handler-specific CEM specializationBuilt on E120's CEM structure, vocabulary for handler equipment
Defined status variables for bin sort, tray/tube fill, cycle state
Vendor-neutral terms for handler-specific concepts
Collection events for pick/place cycles and jam/alarm conditions
Same event model CEM already standardizes, handler-specific content
Host auto-configures against any compliant handler's model
No per-vendor translation of handler-specific terminology

The reason handlers needed their own CEM specialization distinct even from TSEM is that a handler and a tester report fundamentally different operational events at different physical stages of the same test cell — the tester reports what a test program found, while the handler reports whether the part it was holding got moved, sorted, and placed correctly — and collapsing both into one vocabulary would force either standard to carry concepts that don't belong to it. HSEM keeps that boundary clean: a fab's test-cell host software can load a TSEM-compliant tester's model and an HSEM-compliant handler's model side by side, each describing exactly the equipment category it belongs to, without one standard's vocabulary bleeding into the other's or requiring per-vendor glue code to reconcile them.

SEMI E123 — The Handler's Own Vocabulary, Not Shared with TSEM a tester reports what the test found; a handler reports whether the part moved correctly E122 — TSEM (tester) Test program ID, bin result, parallel-site status What the test program found E123 — HSEM (handler) Output-bin sort, tray/tube fill, pick/place cycle, jam alarms Whether the part moved correctly Collapsing both into one vocabulary would blur two distinct roles HSEM and TSEM each describe exactly the equipment category they belong to

E123's HSEM is what lets the handler side of a test cell participate in the same auto-configuration pattern CEM already established, with its own distinct vendor-neutral vocabulary — the mechanical complement to E122's TSEM, so a fab's host software can integrate the tester and the handler as two cleanly separated equipment models rather than one blended and ambiguous one.

Take SEMI E123 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