Recipe

A semiconductor process recipe is the executable set of instructions that tells equipment how to carry out a particular operation. It specifies settings, step order, timing or completion conditions, and permitted transitions. The intended result might be a film thickness, an etched profile, a thermal treatment, or a cleaned surface. The recipe describes the commanded operation; measurements establish what the equipment and wafer actually did.

A recipe is not the complete manufacturing route. The route determines which operations a wafer needs and in what order. A process recipe controls an operation within a module; a sequence recipe can coordinate which module recipes a tool executes. Exact terminology and file structure depend on the equipment supplier. There is no universal recipe file that can be copied unchanged between all tools.

Order and transitions are part of the instruction. A recipe can include stabilization, treatment, and clearing steps, each with its own settings. Some steps finish after a specified duration; others depend on an accepted sensor condition or endpoint, with appropriate timeout handling. Reaching a time limit without reaching a required condition is not equivalent to successful completion.

Parameters vary by process. A plasma operation may control gas delivery, pressure, source power, bias, and temperature-related settings. A wet process may specify chemical conditions and treatment time. A thermal operation may specify ramps and holds. These are interacting controls, not independent guarantees of a result. Changing one parameter can affect several wafer properties at once.

The setpoint is not the measured trajectory. A controller may command a new pressure or temperature while the physical system takes time to respond. Overshoot, settling, sensor location, calibration, and sampling all affect the recorded trace. A chuck temperature setpoint, for example, is not automatically a direct measurement of wafer-surface temperature. The relevant distinction is between what was requested, what was sensed, and what happened on the wafer.

Process traces help determine whether execution stayed within expected behavior, but a normal trace does not prove that every wafer result is acceptable. Film thickness, uniformity, feature dimensions, defects, or electrical properties may require separate metrology. A recipe can finish without a software error and still produce out-of-specification material.

Qualification establishes where a recipe works. Engineers evaluate settings against the required outputs for a defined substrate, hardware configuration, and process condition. A usable process window is the region where the relevant requirements are met together. Optimizing one output while ignoring another can select a recipe that is fast but unacceptable, or accurate at the center of a wafer but nonuniform elsewhere.

Real recipes have more than two dimensions. A two-dimensional plot is a slice with other conditions held fixed, not proof that any combination of individually allowed settings will work. Interactions, chamber condition, incoming wafer variation, and measurement uncertainty influence the usable margin. The purpose of experimentation is to characterize those effects rather than simply find one passing wafer.

The same file does not guarantee the same process. Chambers can differ in calibration, consumable condition, wall state, and thermal or gas-delivery behavior. Moving a recipe to another chamber, changing hardware, or returning from maintenance may require checks or requalification under the site's rules. A shared recipe name is not evidence of chamber matching.

Control the version that actually ran. A production record should identify the approved recipe content or revision, the equipment and chamber, the material processed, and the relevant execution data. A filename alone is weak evidence if its contents can be edited in place. Recipe management can support transfers between factory hosts and tools, change notification, and content verification, depending on the interface implementation.

Verification that a recipe file is structurally valid is not the same as qualification that it produces the intended wafer result. Both matter. Access control, review, version tracking, and clear separation of engineering and released content reduce the chance of running an unintended change. “Golden recipe” is a local label for an approved baseline, not a universal certification.

Adjustments must remain controlled. Run-to-run control may change selected settings using prior measurements, within defined limits and an approved control strategy. That does not authorize arbitrary edits or bypasses. Equipment safety interlocks remain separate protections; a recipe is not a substitute for them. An aborted run also needs a disposition for the affected material, because restarting the same instructions can repeat treatment already received.

The key idea: a recipe links intended process behavior to a specific, traceable execution. Good control requires the right version, qualified equipment and material, meaningful execution checks, and measured wafer results. A list of settings is only the beginning.

Sources: Cimetrix recipe design and GEM recipe-management documentation; Lam Research virtual-sensor process-control discussion; Applied Materials AIx process-recipe optimization overview. All diagrams are explanatory, with no usable process settings or operating instructions.