Outline Control structure design (plantwide control)

Slides:



Advertisements
Similar presentations
Model-based PID tuning methods Two degree of freedom controllers
Advertisements

Chapter 21. Multiloop Control: Performance Analysis
The control hierarchy based on “time scale separation” MPC (slower advanced and multivariable control) PID (fast “regulatory” control) PROCESS setpoints.
Exercise 3. Solutions From Fujio Kida, JGC Co. All cases
1 Outline Control structure design (plantwide control) A procedure for control structure design I Top Down Step 1: Degrees of freedom Step 2: Operational.
Control of Multiple-Input, Multiple-Output Processes
1 Outline Control structure design (plantwide control) A procedure for control structure design I Top Down Step 1: Degrees of freedom Step 2: Operational.
CHE 185 – PROCESS CONTROL AND DYNAMICS PID CONTROL APPLIED TO MIMO PROCESSES.
Control of Multiple-Input, Multiple- Output (MIMO) Processes 18.1 Process Interactions and Control Loop Interactions 18.2 Pairing of Controlled and Manipulated.
Multivariable systems Relative Gain Array (RGA)
Multivariable Control Systems Ali Karimpour Assistant Professor Ferdowsi University of Mashhad.
Plantwide process control with focus on selecting economic controlled variables («self- optimizing control») Sigurd Skogestad, NTNU 2014.
Practical plantwide process control Sigurd Skogestad, NTNU Thailand, April 2014.
PID Tuning and Controllability Sigurd Skogestad NTNU, Trondheim, Norway.
Cascade, Ratio, and Feedforward Control
GHGT-8 Self-Optimizing and Control Structure Design for a CO 2 Capturing Plant Mehdi Panahi, Mehdi Karimi, Sigurd Skogestad, Magne Hillestad, Hallvard.
Part 3: Regulatory («stabilizing») control
1 Outline Skogestad procedure for control structure design I Top Down Step S1: Define operational objective (cost) and constraints Step S2: Identify degrees.
1 Plantwide control: Towards a systematic procedure Sigurd Skogestad Department of Chemical Engineering Norwegian University of Science and Tecnology (NTNU)
Outline Skogestad procedure for control structure design I Top Down
Alternative form with detuning factor F
1 Outline Control structure design (plantwide control) A procedure for control structure design I Top Down Step 1: Degrees of freedom Step 2: Operational.
1 Outline Skogestad procedure for control structure design I Top Down Step S1: Define operational objective (cost) and constraints Step S2: Identify degrees.
1 A Plantwide Control Procedure Applied to the HDA Process Antonio Araújo and Sigurd Skogestad Department of Chemical Engineering Norwegian University.
1 Practical plantwide process control. Extra Sigurd Skogestad, NTNU Thailand, April 2014.
1 E. S. Hori, Maximum Gain Rule Maximum Gain Rule for Selecting Controlled Variables Eduardo Shigueo Hori, Sigurd Skogestad Norwegian University of Science.
Sigurd Skogestad Department of Chemical Engineering
1 Plantwide control: Towards a systematic procedure Sigurd Skogestad Department of Chemical Engineering Norwegian University of Science and Tecnology (NTNU)
1 Outline Control structure design (plantwide control) A procedure for control structure design I Top Down Step 1: Degrees of freedom Step 2: Operational.
1 Part 3: Regulatory («stabilizing») control Inventory (level) control structure –Location of throughput manipulator –Consistency and radiating rule Structure.
1 Decentralized control Sigurd Skogestad Department of Chemical Engineering Norwegian University of Science and Tecnology (NTNU) Trondheim, Norway.
1 Decentralized control Sigurd Skogestad Department of Chemical Engineering Norwegian University of Science and Tecnology (NTNU) Trondheim, Norway.
1 Self-optimizing control From key performance indicators to control of biological systems Sigurd Skogestad Department of Chemical Engineering Norwegian.
1 II. Bottom-up Determine secondary controlled variables and structure (configuration) of control system (pairing) A good control configuration is insensitive.
Control Structure Design: New Developments and Future Directions Vinay Kariwala and Sigurd Skogestad Department of Chemical Engineering NTNU, Trondheim,
1 Self-optimizing control From key performance indicators to control of biological systems Sigurd Skogestad Department of Chemical Engineering Norwegian.
1 PLANTWIDE CONTROL Sigurd Skogestad Department of Chemical Engineering Norwegian University of Science and Tecnology (NTNU) Trondheim, Norway August/September.
Cascade Control Systems (串级控制系统)
Multi-Variable Control
Process Control. Feedback control y sp = set point (target value) y = measured value The process information (y) is fed back to the controller The objective.
Coordinator MPC with focus on maximizing throughput
Outline Control structure design (plantwide control)
Transfer Functions Convenient representation of a linear, dynamic model. A transfer function (TF) relates one input and one output: The following terminology.
Transfer Functions Chapter 4
Advanced process control with focus on selecting economic controlled variables («self-optimizing control») Sigurd Skogestad, NTNU 2016.
Part 3: Regulatory («stabilizing») control
Part 3: Regulatory («stabilizing») control
Control of Multiple-Input, Multiple-Output Processes
Changing between Active Constraint Regions for Optimal Operation: Classical Advanced Control versus Model Predictive Control Adriana Reyes-Lúa, Cristina.
Decentralized control
Process Control Engineering
Enhanced Single-Loop Control Strategies
Example regulatory control: Distillation
PLANTWIDE CONTROL Sigurd Skogestad Department of Chemical Engineering
Plantwide control: Towards a systematic procedure
PLANTWIDE CONTROL Sigurd Skogestad Department of Chemical Engineering
Outline Skogestad procedure for control structure design I Top Down
Outline Control structure design (plantwide control)
Perspectives and future directions in control structure selection
Plantwide control: Towards a systematic procedure
Example : Optimal blending of gasoline
Decentralized control
Example regulatory control: Distillation
Part 3: Regulatory («stabilizing») control
Plantwide control: Towards a systematic procedure
Example regulatory control: Distillation
Example regulatory control: Distillation
Example “stabilizing” control: Distillation
Part 3: Regulatory («stabilizing») control
Outline Control structure design (plantwide control)
Presentation transcript:

Outline Control structure design (plantwide control) A procedure for control structure design I Top Down Step 1: Degrees of freedom Step 2: Operational objectives (optimal operation) Step 3: What to control ? (self-optimizing control) Step 4: Where set production rate? II Bottom Up Step 5: Regulatory control: What more to control ? Step 6: Supervisory control Step 7: Real-time optimization Case studies

II. Bottom-up Determine secondary controlled variables and structure (configuration) of control system (pairing) A good control configuration is insensitive to parameter changes Step 5. REGULATORY CONTROL LAYER 5.1 Stabilization (including level control) 5.2 Local disturbance rejection (inner cascades) What more to control? (secondary variables) Step 6. SUPERVISORY CONTROL LAYER Decentralized or multivariable control (MPC)? Pairing? Step 7. OPTIMIZATION LAYER (RTO)

Step 5. Regulatory control layer Purpose: “Stabilize” the plant using a simple control configuration (usually: local SISO PID controllers + simple cascades) Enable manual operation (by operators) Main structural issues: What more should we control? (secondary cv’s, y2, use of extra measurements) Pairing with manipulated variables (mv’s u2) y1 = c y2 = ?

Objectives regulatory control layer Allow for manual operation Simple decentralized (local) PID controllers that can be tuned on-line Take care of “fast” control Track setpoint changes from the layer above Local disturbance rejection Stabilization (mathematical sense) Avoid “drift” (due to disturbances) so system stays in “linear region” “stabilization” (practical sense) Allow for “slow” control in layer above (supervisory control) Make control problem easy as seen from layer above The key decisions here (to be made by the control engineer) are: Which extra secondary (dynamic) variables y2 should we control? Propose a (simple) control configuration

Control configuration elements Control configuration. The restrictions imposed on the overall controller by decomposing it into a set of local controllers (subcontrollers, units, elements, blocks) with predetermined links and with a possibly predetermined design sequence where subcontrollers are designed locally. Some control configuration elements: Cascade controllers Decentralized controllers Feedforward elements Decoupling elements Selectors Split-range control

Cascade control arises when the output from one controller is the input to another. This is broader than the conventional definition of cascade control which is that the output from one controller is the reference command (setpoint) to another. In addition, in cascade control, it is usually assumed that the inner loop K2 is much faster than the outer loop K1. Feedforward elements link measured disturbances to manipulated inputs. Decoupling elements link one set of manipulated inputs (“measurements”) with another set of manipulated inputs. They are used to improve the performance of decentralized control systems, and are often viewed as feedforward elements (although this is not correct when we view the control system as a whole) where the “measured disturbance” is the manipulated input computed by another decentralized controller.

Why simplified configurations? Fundamental: Save on modelling effort Other: easy to understand easy to tune and retune insensitive to model uncertainty possible to design for failure tolerance fewer links reduced computation load

Use of (extra) measurements (y2) as (extra) CVs: Cascade control Primary CV y1 y2s K u2 G y2 Secondary CV (control for dynamic reasons) Key decision: Choice of y2 (controlled variable) Also important (since we almost always use single loops in the regulatory control layer): Choice of u2 (“pairing”)

Degrees of freedom unchanged No degrees of freedom lost by control of secondary (local) variables as setpoints become y2s replace inputs u2 as new degrees of freedom Cascade control: G K y2s u2 y2 y1 Original DOF New DOF

Example: Distillation Primary controlled variable: y1 = c = xD, xB (compositions top, bottom) BUT: Delay in measurement of x + unreliable Regulatory control: For “stabilization” need control of (y2): Liquid level condenser (MD) Liquid level reboiler (MB) Pressure (p) Holdup of light component in column (temperature profile) Unstable (Integrating) + No steady-state effect Variations in p disturb other loops Almost unstable (integrating) Ts TC T-loop in bottom

Cascade control distillation ys y Ts T Ls L z With flow loop + T-loop in top y XC Ts T TC Ls L FC z XC

Hierarchical control: Time scale separation With a “reasonable” time scale separation between the layers (typically by a factor 5 or more in terms of closed-loop response time) we have the following advantages: The stability and performance of the lower (faster) layer (involving y2) is not much influenced by the presence of the upper (slow) layers (involving y1) Reason: The frequency of the “disturbance” from the upper layer is well inside the bandwidth of the lower layers With the lower (faster) layer in place, the stability and performance of the upper (slower) layers do not depend much on the specific controller settings used in the lower layers Reason: The lower layers only effect frequencies outside the bandwidth of the upper layers

QUIZ: What are the benefits of adding a flow controller (inner cascade)? qs Extra measurement y2 = q q z Counteracts nonlinearity in valve, f(z) With fast flow control we can assume q = qs Eliminates effect of disturbances in p1 and p2

Objectives regulatory control layer Allow for manual operation Simple decentralized (local) PID controllers that can be tuned on-line Take care of “fast” control Track setpoint changes from the layer above Local disturbance rejection Stabilization (mathematical sense) Avoid “drift” (due to disturbances) so system stays in “linear region” “stabilization” (practical sense) Allow for “slow” control in layer above (supervisory control) Make control problem easy as seen from layer above Implications for selection of y2: Control of y2 “stabilizes the plant” y2 is easy to control (favorable dynamics)

1. “Control of y2 stabilizes the plant” A. “Mathematical stabilization” (e.g. reactor): Unstable mode is “quickly” detected (state observability) in the measurement (y2) and is easily affected (state controllability) by the input (u2). Tool for selecting input/output: Pole vectors y2: Want large element in output pole vector: Instability easily detected relative to noise u2: Want large element in input pole vector: Small input usage required for stabilization B. “Practical extended stabilization” (avoid “drift” due to disturbance sensitivity): Intuitive: y2 located close to important disturbance Maximum gain rule: Controllable range for y2 is large compared to sum of optimal variation and control error More exact tool: Partial control analysis

Recall maximum gain rule for selecting primary controlled variables c: Controlled variables c for which their controllable range is large compared to their sum of optimal variation and control error Restated for secondary controlled variables y2: Control variables y2 for which their controllable range is large compared to their sum of optimal variation and control error controllable range = range y2 may reach by varying the inputs optimal variation: due to disturbances control error = implementation error n Want large Want small

What should we control (y2)? Rule: Maximize the scaled gain General case: Maximize minimum singular value of scaled G Scalar case: |Gs| = |G| / span |G|: gain from independent variable (u2) to candidate controlled variable (y2) IMPORTANT: The gain |G| should be evaluated at the (bandwidth) frequency of the layer above in the control hierarchy! If the layer above is slow: OK with steady-state gain as used for selecting primary controlled variables (y1=c) BUT: In general, gain can be very different span (of y2) = optimal variation in y2 + control error for y2 Note optimal variation: This is often the same as the optimal variation used for selecting primary controlled variables (c). Exception: If we at the “fast” regulatory time scale have some yet unused “slower” inputs (u1) which are constant then we may want find a more suitable optimal variation for the fast time scale.

2. “y2 is easy to control” (controllability) Statics: Want large gain (from u2 to y2) Main rule: y2 is easy to measure and located close to available manipulated variable u2 (“pairing”) Dynamics: Want small effective delay (from u2 to y2) “effective delay” includes inverse response (RHP-zeros) + high-order lags

Rules for selecting u2 (to be paired with y2) Avoid using variable u2 that may saturate (especially in loops at the bottom of the control hieararchy) Alternatively: Need to use “input resetting” in higher layer (“mid-ranging”) Example: Stabilize reactor with bypass flow (e.g. if bypass may saturate, then reset in higher layer using cooling flow) “Pair close”: The controllability, for example in terms a small effective delay from u2 to y2, should be good.

Cascade control (conventional; with extra measurement) The reference r2 (= setpoint ys2) is an output from another controller General case (“parallel cascade”) Special common case (“series cascade”)

Series cascade Disturbances arising within the secondary loop (before y2) are corrected by the secondary controller before they can influence the primary variable y1 Phase lag existing in the secondary part of the process (G2) is reduced by the secondary loop. This improves the speed of response of the primary loop. Gain variations in G2 are overcome within its own loop. Thus, use cascade control (with an extra secondary measurement y2) when: The disturbance d2 is significant and G1 has an effective delay The plant G2 is uncertain (varies) or nonlinear Design / tuning First design K2 (“fast loop”) to deal with d2 Then design K1 to deal with d1

Partial control Cascade control: y2 not important in itself, and setpoint (r2) is available for control of y1 Decentralized control (using sequential design): y2 important in itself

Partial control analysis Primary controlled variable y1 = c (supervisory control layer) Local control of y2 using u2 (regulatory control layer) Setpoint y2s : new DOF for supervisory control Assumption: Perfect control (K2 -> 1) in “inner” loop Derivation: Set y2=y2s-n2 (perfect control), eliminate u2, and solve for y1

Partial control: Distillation Supervisory control: Primary controlled variables y1 = c = (xD xB)T Regulatory control: Control of y2=T using u2 = L (original DOF) Setpoint y2s = Ts : new DOF for supervisory control u1 = V

Limitations of partial control? Cascade control: Closing of secondary loops does not by itself impose new problems Theorem 10.2 (SP, 2005). The partially controlled system [P1 Pr1] from [u1 r2] to y1 has no new RHP-zeros that are not present in the open-loop system [G11 G12] from [u1 u2] to y1 provided r2 is available for control of y1 K2 has no RHP-zeros Decentralized control (sequential design): Can introduce limitations. Avoid pairing on negative RGA for u2/y2 – otherwise Pu likely has a RHP-zero

Selecting measurements and inputs for stabilization: Pole vectors Maximum gain rule is good for integrating (drifting) modes For “fast” unstable modes (e.g. reactor): Pole vectors useful for determining which input (valve) and output (measurement) to use for stabilizing unstable modes Assumes input usage (avoiding saturation) may be a problem Compute pole vectors from eigenvectors of A-matrix

Example: Tennessee Eastman challenge problem

Decentralized control (single-loop controllers) Use for: Noninteracting process and no change in active constraints + Tuning may be done on-line + No or minimal model requirements + Easy to fix and change - Need to determine pairing - Performance loss compared to multivariable control - Complicated logic required for reconfiguration when active constraints move

Multivariable control (with explicit constraint handling = MPC) Use for: Interacting process and changes in active constraints + Easy handling of feedforward control + Easy handling of changing constraints no need for logic smooth transition - Requires multivariable dynamic model - Tuning may be difficult - Less transparent - “Everything goes down at the same time”