Semi E174

SEMI E174 specifies Wafer Job Management (WJM), a standard for tracking and managing job state at the level of an individual wafer, filling a gap left by E40's process-job model and E94's control-job model, both of which treat a group of wafers as the unit of work. A process job under E40 describes a recipe applied to a group of wafers as a batch; WJM answers a question that batch-level model was never built to answer: once those wafers enter a multi-chamber tool and each one takes a different path — one chamber running ahead, another catching up, a third flagged for rework — how does the host or equipment track and report on any single wafer's own progress, independent of where the rest of its batch currently stands.

SEMI E40 process job treats a group of wafers as one batch unit
One recipe, one job status, reported for the whole group together
What batch-level job tracking alone doesn't provideWafers in the same batch diverge once they enter a multi-chamber tool
No per-wafer job status once wafers split across chambers
Wafer 3 finishes chamber A while wafer 7 is still queued at chamber B
No standardized way to flag or reroute a single wafer independently
A defect on one wafer shouldn't require managing the whole batch as an exception
SEMI E174 — Wafer Job Management (WJM)Job tracking and control at individual-wafer granularity
Each wafer carries its own trackable job state, independent of its batch
Host can query, reroute, or flag one wafer without touching the rest
A multi-chamber tool reports and manages progress wafer by wafer
Batch-level job tracking and per-wafer job tracking now both standardized

A few things are worth knowing about why wafer-level job tracking needed its own standard in addition to the batch-level model E40 and E94 already provide:

A process job's batch-level status answers "how is this group of wafers doing overall," which is a genuinely different question from "how is this one wafer doing," and the difference only becomes operationally important once a tool actually processes wafers in parallel across multiple chambers rather than moving them through as a single lockstep unit. In a simple single-chamber tool, batch status and per-wafer status are nearly the same thing because every wafer in the job moves together. In a modern multi-chamber cluster tool, wafers from the same process job routinely diverge — one proceeds to the next step while another waits on a busy chamber, and a third might be pulled for inspection after an in-process measurement flags it. E40's batch-level model has no native way to represent that divergence; it reports the job as a whole, not the wafer that's currently three steps behind its siblings.

One Process Job, Three Wafers, Three Different Places SEMI E174 (WJM) tracks each wafer's own job state once a batch splits apart E40 process job: "Lot 5, recipe ETCH-A, status = in progress" One status line for the whole batch — true, but not the full picture Wafer 3 Chamber A, step 4 of 6, on schedule WJM: job state tracked independently Wafer 7 Chamber B, step 2 of 6, queued behind another lot WJM: job state tracked independently Wafer 12 Pulled for inspection, job flagged, rest unaffected WJM: rerouted without touching the batch Same process job, same recipe — three independently trackable wafer job states E40/E94 describe the batch; WJM is what describes each wafer inside it

WJM's value shows up specifically in the exception case — a wafer flagged for rework, a wafer that needs a different recipe variant, or a wafer pulled aside for an unscheduled inspection — because without per-wafer job tracking, handling that one wafer differently has historically meant treating the entire batch as an exception. A host that can only query and command at the process-job or control-job level has no clean way to say "hold wafer 12, let the rest of the lot continue" without some vendor-specific workaround layered on top of the standard batch model. WJM gives that exception handling a standardized home: a wafer's own job state — its current step, its assigned recipe, its hold/release status — is tracked and reportable independent of whatever batch it originally belonged to.

WJM sits above E40's process-job model and alongside E94's control-job model as the finest-grained layer in a job-management hierarchy this glossary has already covered from the batch side — E94 bundles process jobs into a coordinated multi-lot unit, E40 defines what a process job is for one batch, and WJM is the layer underneath both that tracks the individual wafer once batch-level sequencing stops being the whole story. None of those earlier standards needed wafer-level granularity because, historically, most tools moved wafers through as a lockstep unit. WJM exists because that assumption stopped holding once multi-chamber parallel processing became the norm.

Read E174 as the standard that closes the gap E40's batch-level process-job model was never built to close: a process job can report accurately that a lot is "in progress" while three of its wafers are actually in three different chambers at three different steps, and WJM is what actually gives the host a standardized way to track, query, and act on any one of those wafers individually.

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