Lot

A semiconductor lot is an identified group of wafers managed together for manufacturing control. The lot gives scheduling, route execution, quality decisions, and material history a common reference. Individual wafer IDs retain finer detail within that group. Being in the same lot does not guarantee that every wafer enters the same chamber at the same moment.

Three concepts should stay separate: the lot is a logical grouping, the carrier is a physical container, and a processing batch is the material processed together in a particular equipment run. A carrier exchange need not create a new lot. A batch tool may process material from more than one compatible lot, while a single-wafer tool processes members of one lot sequentially. The permitted combinations depend on factory and equipment rules.

Lot size is a control choice, not a definition. Carrier capacity places a physical limit on one loading configuration, but a lot need not fill every available slot. Engineering work, partial lots, sampling, and split operations can produce smaller groups. Report both lot count and wafer quantity when the distinction matters: two lots of three wafers do not represent more wafer inventory than one lot of six.

A split changes membership while preserving history. Splitting can separate wafers for an experiment, a different route, or a quality disposition. The system must record which wafer IDs moved into each resulting group, when the operation happened, and how the groups relate to the original material. The exact naming convention for parent and child lots is implementation-specific; the traceability requirement is not.

That quantity check is necessary but insufficient: recording W1 twice and losing W2 would preserve the count while corrupting identity. Verify the membership as well as the total. If a split involves physical sorting, logical records must remain coordinated with carrier and slot changes, including any interrupted transfers.

A merge is also a controlled transaction, not merely putting wafers in one container. Product, route position, process history, holds, and other compatibility rules can restrict what may be merged. A permitted merge must retain the ancestry and relevant wafer histories; combining groups does not erase a deviation that occurred before the merge.

Lot history and wafer history answer different questions. Lot-level records show shared route context and events. Wafer-level records can distinguish chamber assignment, measured results, or an exceptional path taken by one member. If only some wafers passed through a suspect chamber, a lot label alone may be too coarse to establish exposure. Traceability should be detailed enough to reconstruct which material actually experienced the condition under investigation.

A hold is a control state, not a scrap decision. A hold restricts specified manufacturing actions while material awaits review or another required condition. A release removes the applicable restriction under approved authority; it does not mean the issue never occurred. A lot may also have multiple restrictions, so clearing one reason need not make it eligible for every operation.

Quality review may lead to release, additional measurements, approved rework, or scrap. These are different outcomes. Scrap changes the accounted usable quantity and must be recorded explicitly; material should not disappear from inventory merely because it no longer appears on a dispatch list. Similarly, an aborted equipment run requires a disposition for affected wafers rather than an assumption that none received treatment.

Priority is not permission to skip controls. A hot lot receives elevated scheduling priority according to local rules. It still needs the correct route, qualified equipment, and applicable releases. There is no universal speed multiplier for a hot lot: its actual cycle time depends on availability, process duration, queues, and competing work. Frequent priority overrides can delay other material without increasing total factory capacity.

Production, engineering, monitor, and qualification material may have different purposes and permissions. Those labels should be explicit because they affect scheduling, sampling, and allowed operations. The manufacturing execution system (MES) ties identities, route revisions, material states, and equipment events together; a carrier label or spreadsheet alone does not provide that complete execution history.

The key idea: a lot makes a group manageable, while wafer identity keeps the details trustworthy. Good lot control preserves membership, quantity, genealogy, and processing eligibility even when material moves, splits, merges, or pauses.

Sources: Critical Manufacturing semiconductor MES, genealogy, split, and sorter documentation; Siemens lot-traceability and semiconductor execution documentation. Diagrams are conceptual examples, not factory operating procedures.