Who Should Use Feed Forward Control? What applications are best for Feed Forward?

ff-blockdia-big It’s not uncommon for process control discussions to focus on use of the PID to improve a loop’s ability to track Set Point.  Oftentimes tweaks to controller tuning parameters either seek incremental reduction in Settling Time or strive to limit Overshoot.  Indeed, many PID tuning courses position optimization of a control loop’s Set Point Tracking as the ultimate goal.  Such a bias overlooks the value of other strategies like Feed Forward Control.

While Feed Forward Control is not an appropriate control strategy for improving Set Point tracking, it’s been widely shown to help improve a process’ capacity for disturbance rejection.  If a disturbance to a process can be isolated then it can often be modeled and defused using the Feed Forward architecture.  Unlike traditional feedback control Feed Forward utilizes a model to proactively trigger an appropriate corrective action.  That action anticipates the end state of a disturbance rather than reacting to Error produced by the disturbance as it accumulates.  By getting a jump on the disturbance’s impact Feed Forward Control prepares the process to mute any ill effects.

Not every application is ideal for Feed Forward Control.  Even so most processes can benefit to some degree from its use.  Following are process attributes for which Feed Forward is well suited and for which the architecture can often improve disturbance rejection:

Load Changes

Manufacturing processes that are subject to frequent load changes are excellent candidates for Feed Forward.  Think of Food & Beverage manufacturers along with Utilities – especially power companies.  The load changes experienced by these and similar process manufacturers are largely predictable, readily modeled, and they can be neutralized through the application of appropriate counter-measures.

Slow Processes

Processes that can be characterized as slow due to a large Dead-Time are often good candidates for Feed Forward Control.  Manufacturers in the Oil & Gas and Basic Materials have many such processes.  The delayed responses of their processes offer a window of opportunity for the type of preemptive correction achieved through Feed Forward.  The counter-measure can be timed for implementation just as the disturbance impacts the process.

Big Equipment

For a variety of reasons large process infrastructure tends to be slow, important, and very expensive.  Multi-zone furnaces, steam turbines, and distillation columns are good examples and span a variety of industry segments from Chemicals and Oil & Gas to Basic Materials and Pulp & Paper.  The proactive control achieved through Feed Forward protects costly equipment that is also big and bulky.

These characteristics are shared by processes which are often good candidates for a disturbance rejection strategy such as Feed Forward.  While Feed Forward does not impact Set Point Tracking, it does serve an often equally important purpose – rejecting the negative effects of process disturbances.

These resources offer related content:

How Do I Calculate Dead-Time?

  Calculate Dead-Time By Visually Inspecting Your Step Test Data Adults can learn a thing or two from children. That's especially true when it comes to matters of time. Whereas adults view it as fashionable to show up to a social event 15 or more...
two men in front of a computer looking at data reports

Keeping Your PID Controllers Working as a Team

Evaluating the overall performance of many individual control loops, with interactions among them, under a variety of operating conditions is key to process optimization. Analytical tools are making this easier. Process engineers must look at all the loops regulating a process and determine which are...
osi pi data historian fi

4 Reasons the OSI PI Data Historian is King of the Market

Data historians are a “must have” technology and among the automation market’s options the PI Historian from OSIsoft is the gold standard. OSIsoft has more-or-less led the historian market from its inception in 1980. The reason: OSI has continuously innovated to assure that the PI...

Still looking for more?

Now that you’ve gotten the basics, connect with our team to learn how our people, processes and technologies can help you optimize.