Skip to content
← Back to Resources

R2R / APC

Run-to-Run APC: Feedback + Feedforward

Run-to-Run (R2R) control adjusts the next run's recipe using the result of the previous run and the current system state. It is widely used in manufacturing processes with variation and drift to keep results from moving away from target.

Feedback Control — adjust from the result

Feedback control changes the next run's conditions after measuring the previous result. It calculates the error between the target and the actual outcome and updates the recipe so that error converges toward zero.

This is not an ad-hoc adjustment. It is an error convergence mechanism executed within designed control rules and constraints.

Feedforward Control — adjust in advance from current state

Feedforward control changes conditions before the process starts, using current state and historical context. Instead of correcting only after the outcome is known, it reflects factors that are already observable in the starting condition.

Feedforward is therefore more than a correction; it is a state-aware predictive adjustment.

Summary

  • Feedback: corrective action after observing result error
  • Feedforward: proactive adjustment using state and history
  • The two can be combined to keep process outcomes from drifting away from target.
FeedbackFeedforward
R2R does not repeat the same recipe. It keeps changing the next recipe based on each run's result and the current state.

Concept diagram

A compact view of how the feedback loop and feedforward input work together.

R2R-based APC (Feedback + Feedforward) Updated recipe Run Process execution Measurement Measurement & outcome Controller Controller / Recipe update Next run Feedback Outcome-error correction System state / History Feedforward State-aware proactive adjustment

A cooking analogy — not just following a recipe, but converging on the result

A noodle package specifies the amount of water and cooking time. Yet the result still changes with heat intensity, cookware and surrounding conditions.

So we naturally do two things.

  • Feedback: if the last result was off, adjust the next one.
  • Feedforward: if we already know this environment requires a different setting, adjust before starting.

Rather than repeating a recipe unchanged, we keep adjusting until the outcome converges on what we want. Semiconductor R2R control works on the same principle, continuously changing conditions to keep process results near target.

The analogy is only for intuition. Real control changes conditions safely within process-specific rules and constraints.

Analogy structure diagram

The goal is not an essay-like illustration, but a simple structural view of Feedback and Feedforward.

Feedback (Outcome-based) Correct the cooking conditions next time after tasting “Adjust after the outcome” Feedforward (State-based) Adjust proactively before cooking based on conditions “Adjust before you start” Recipe Cook Taste / Result State / Context Conditions Cook SUMMARY Feedback = outcome-based correction, Feedforward = state-based proactive adjustment → together they drive convergence to the target FEEDBACK ADJUSTS AFTER TASTING; FEEDFORWARD ADJUSTS BEFORE YOU START BASED ON SITUATION

This resource explains Run-to-Run APC from the control-structure perspective. Actual deployment depends on process and equipment characteristics, safety constraints, calibration strategy and operating policy.

Explore Amously's products
related to this topic.
Product overview
Estimate your ROIView pricing and adoption

Want to learn more about our products? Get in touch.

Contact us