Inferensys

Glossary

Run-to-Run Control

A discrete feedback methodology that adjusts recipe parameters between processing batches based on post-process metrology to compensate for drifting tool conditions and maintain target quality.
Developer demonstrating multi-agent tool use, agent tool selection interface on laptop, casual tech demo moment.
DISCRETE FEEDBACK METHODOLOGY

What is Run-to-Run Control?

Run-to-Run (R2R) control is a discrete feedback methodology that adjusts recipe parameters between processing batches based on post-process metrology to compensate for drifting tool conditions.

Run-to-Run Control is a supervisory process control technique where a recipe parameter for a manufacturing tool is modified between runs, not during them. After a wafer or batch is processed, a metrology tool measures the output quality. A control algorithm then compares this measurement to the target and computes an updated recipe setting for the next run, effectively compensating for process drift, tool aging, or consumable depletion.

The core mechanism relies on a process model that relates recipe adjustments to output changes. Common algorithms include the Exponentially Weighted Moving Average (EWMA) filter, which smooths measurement noise and adapts to gradual shifts. This methodology is critical in semiconductor manufacturing for processes like chemical-mechanical planarization (CMP) and etch, where maintaining angstrom-level precision across thousands of wafers is impossible with real-time feedback alone.

DISCRETE FEEDBACK METHODOLOGY

Key Characteristics of R2R Control

Run-to-Run (R2R) control is a supervisory feedback methodology that adjusts recipe parameters between processing batches based on post-process metrology to compensate for drifting tool conditions. It bridges the gap between real-time closed-loop control and long-term statistical process control.

01

Lot-to-Lot Feedback Architecture

R2R control operates on a discrete batch basis rather than continuous real-time adjustment. After a wafer or batch completes processing, post-process metrology measures critical quality characteristics. The R2R controller then calculates an updated recipe parameter for the next batch to minimize the deviation from target.

  • Sampling interval: Between runs, not within a run
  • Typical applications: Chemical Mechanical Planarization (CMP), etch depth control, deposition thickness
  • Key advantage: Compensates for slow tool drift that real-time PID loops cannot address
30-50%
Typical Cpk Improvement
02

EWMA Filtering Core

The Exponentially Weighted Moving Average (EWMA) filter is the foundational algorithm in most R2R controllers. It applies a weighting factor (λ) between 0 and 1 to blend the current measurement with the historical estimate, creating a smoothed disturbance model.

  • Formula: δ̂ₖ₊₁ = λ · δₖ + (1 - λ) · δ̂ₖ
  • λ close to 0: Heavy filtering, slow response to real shifts
  • λ close to 1: Light filtering, rapid response but noise-sensitive
  • Tuning trade-off: Balance between noise rejection and responsiveness to genuine tool drift
0.2-0.4
Typical λ Range
03

Threaded Control Contexts

Modern R2R systems maintain separate control threads for distinct process contexts. A single tool may run multiple products, each requiring independent disturbance tracking because different patterns and materials cause unique wear signatures.

  • Context identifiers: Product ID, tool chamber, recipe name, reticle
  • Thread management: Each context maintains its own EWMA state
  • Cold start problem: New contexts lack historical data and require pilot wafers or global model initialization
  • Context switching: Controller must seamlessly switch disturbance estimates when product mix changes
04

Gradual Mode Optimization

R2R controllers often employ gradual mode adjustments where recipe changes are intentionally dampened to prevent overcorrection. A deadband around the target prevents unnecessary adjustments when the process is within acceptable limits.

  • Gain parameter (K): Scales the correction magnitude (typically 0.3-0.7)
  • Deadband threshold: No adjustment if |error| < threshold
  • Clamping limits: Maximum allowable recipe change per run to prevent process excursions
  • Purpose: Prevents controller-induced variability from chasing measurement noise
0.3-0.7
Typical Gain Range
05

Virtual Metrology Integration

When physical metrology is slow or expensive, R2R controllers integrate virtual metrology (VM) models that predict wafer quality from upstream sensor data. This enables wafer-to-wafer control without waiting for actual measurements.

  • VM model inputs: Chamber pressure, RF power, gas flows, temperature traces
  • Prediction target: Film thickness, etch depth, uniformity
  • Confidence metrics: VM predictions include uncertainty estimates; low-confidence predictions may trigger a physical measurement
  • Benefit: Reduces metrology burden while maintaining tighter control
06

Fault Detection and Classification Coupling

R2R controllers are tightly integrated with Fault Detection and Classification (FDC) systems. If FDC flags a tool fault or an out-of-spec measurement, the R2R controller can suspend automatic updates to prevent corrupting the disturbance model with faulty data.

  • Measurement validation: Outlier rejection before EWMA update
  • Tool health gating: Recipe adjustments paused during maintenance recovery
  • Alarm escalation: Persistent large corrections trigger engineering review
  • Traceability: Every recipe change is logged with the metrology data and FDC status that triggered it
RUN-TO-RUN CONTROL EXPLAINED

Frequently Asked Questions

Precise answers to the most common technical questions about discrete batch-level feedback control in semiconductor and advanced manufacturing environments.

Run-to-Run (R2R) control is a discrete supervisory feedback methodology that adjusts recipe parameters between processing batches based on post-process metrology to compensate for drifting tool conditions. Unlike real-time PID loops that react within milliseconds, R2R operates on a wafer-to-wafer or lot-to-lot timescale. The core mechanism involves a process model that relates manipulatable recipe inputs (e.g., exposure time, temperature setpoint) to quality outputs (e.g., film thickness, critical dimension). After a batch completes, metrology data is fed into an estimator—often an Exponentially Weighted Moving Average (EWMA) filter—which updates the model's intercept term to track slow drift. The controller then solves an optimization problem to compute the recipe for the next run that minimizes the predicted deviation from target. This architecture effectively decouples fast inner-loop stabilization from slow outer-loop quality optimization.

CONTROL PARADIGM COMPARISON

R2R Control vs. Related Process Control Methodologies

Distinguishing Run-to-Run control from other feedback and optimization methodologies based on update frequency, objective, and data requirements.

FeatureRun-to-Run ControlModel Predictive ControlStatistical Process Control

Update Frequency

Between batches or wafers

Real-time (seconds or sub-second)

Periodic sampling intervals

Primary Objective

Compensate tool drift and maintain recipe targets

Optimize future trajectory over a receding horizon

Detect and distinguish special cause variation

Data Source

Post-process metrology

Real-time process sensors and dynamic model

Sampled quality measurements and control charts

Control Action Type

Recipe parameter adjustment for next run

Continuous manipulation of actuators

Alarm or operator notification for investigation

Model Dependency

Linear or non-linear input-output process model

Explicit dynamic state-space model

Statistical distribution model (no process dynamics)

Handles Multivariate Interactions

Typical Latency

Minutes to hours

Milliseconds to seconds

Hours to shifts

Compensates for Drift

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.