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.
Glossary
Run-to-Run Control

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.
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.
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.
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
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
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
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
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
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
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.
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.
| Feature | Run-to-Run Control | Model Predictive Control | Statistical 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 |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the foundational control methodologies and advanced algorithms that complement or extend Run-to-Run control in modern software-defined manufacturing.
Model Predictive Control (MPC)
An advanced control algorithm that uses a dynamic process model to predict future outputs and compute an optimal sequence of control moves over a finite receding horizon. Unlike Run-to-Run control's batch-to-batch adjustments, MPC operates continuously within a single process run.
- Key Distinction: Solves a constrained optimization problem at each time step
- Application: Ideal for multi-variable processes with complex interactions
- Synergy: Often used for inner-loop control while Run-to-Run handles outer-loop recipe adjustments
Virtual Metrology
A soft-sensing technique that predicts the quality characteristics of a manufactured wafer or product using upstream equipment sensor data without a physical post-process measurement. This provides the critical quality feedback signal that Run-to-Run controllers require, but with zero metrology delay.
- Benefit: Eliminates the time lag waiting for physical inspection results
- Enabler: Allows true wafer-to-wafer control rather than lot-to-lot
- Technology: Typically built on Gaussian Process Regression or deep neural networks
Exponentially Weighted Moving Average (EWMA) Controller
The most widely implemented Run-to-Run control algorithm in semiconductor manufacturing. The EWMA controller applies a discount factor (λ) to historical process disturbances, giving exponentially less weight to older data when calculating the recipe adjustment for the next batch.
- Tuning Parameter: λ balances responsiveness against noise sensitivity
- Stability: Guaranteed to converge for processes with a linear input-output relationship
- Limitation: Assumes a stationary disturbance model; struggles with abrupt shifts
Statistical Process Control (SPC)
A quality control methodology that uses statistical methods to monitor a process and distinguish between common cause variation (inherent noise) and special cause variation (assignable events). Run-to-Run control complements SPC by automatically correcting for common cause drift.
- Integration: SPC charts trigger alarms; Run-to-Run controllers execute corrections
- Tool: Control charts with Western Electric rules detect process shifts
- Philosophy: SPC identifies when intervention is needed; Run-to-Run automates the response
Gaussian Process Regression (GPR)
A non-parametric Bayesian inference method that models a distribution over possible functions to provide both predictions and calibrated uncertainty estimates for process variables. GPR is increasingly replacing linear models in advanced Run-to-Run controllers.
- Advantage: Naturally quantifies prediction confidence for risk-aware control
- Use Case: Modeling non-linear etch rates where traditional linear assumptions fail
- Output: Provides a mean prediction and a variance envelope for the next run's quality
Feedforward Compensation
A control technique that measures a measurable disturbance directly and preemptively adjusts the manipulated variable to cancel its effect before it impacts the process output. In Run-to-Run frameworks, feedforward handles incoming material variation while feedback corrects tool drift.
- Example: Adjusting etch time based on incoming film thickness measurements
- Combination: Feedforward + Run-to-Run feedback = complete disturbance rejection
- Requirement: Requires a reliable upstream metrology or virtual metrology signal

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us