EquipmentModules PCS7V91 en V52
EquipmentModules PCS7V91 en V52
Industry
Online
Support
APPLICATION EXAMPLE
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several components in the
form of text, graphics and/or software modules. The application examples are a free service by Siemens AG and/or a
subsidiary of Siemens AG (“Siemens”). They are non-binding and make no claim to completeness or functionality
regarding configuration and equipment. The application examples merely offer help with typical tasks; they do not
constitute customer-specific solutions. You yourself are responsible for the proper and safe operation of the products in
accordance with applicable regulations and must also check the function of the respective application example and
customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the application examples
used by technically trained personnel. Any change to the application examples is your responsibility. Sharing the
application examples with third parties or copying the application examples or excerpts thereof is permitted only in
combination with your own products. The application examples are not required to undergo the customary tests and
quality inspections of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not result in property damage
or injury to persons.
Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for the
usability, availability, completeness and freedom from defects of the application examples as well as for related
information, configuration and performance data and any damage caused thereby. This shall not apply in cases of
mandatory liability, for example under the German Product Liability Act, or in cases of intent, gross negligence, or
culpable loss of life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent non-disclosure of a
defect, or culpable breach of material contractual obligations. Claims for damages arising from a breach of material
contractual obligations shall however be limited to the foreseeable damage typical of the type of agreement, unless
liability arises from intent or gross negligence or is based on loss of life, bodily injury or damage to health. The foregoing
provisions do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens against
existing or future claims of third parties in this connection except where Siemens is mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond the
liability provisions described.
Other information
Siemens reserves the right to make changes to the application examples at any time without notice. In case of
discrepancies between the suggestions in the application examples and other Siemens publications such as catalogs, the
content of the other documentation shall have precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.
Security information
Siemens provides products and solutions with industrial security functions that support the secure operation of plants,
systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement – and
continuously maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and solutions constitute
one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such
systems, machines and components should only be connected to an enterprise network or the internet if and to the
extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network
segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly
recommends that product updates are applied as soon as they are available and that the latest product versions are used.
Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer’s
exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under
https://www.siemens.com/cert.
Table of contents
1. Introduction ............................................................................................................... 5
4. Control Module......................................................................................................... 14
4.1. Introduction.......................................................................................................................... 14
4.2. Basic Control Module Type Library.......................................................................................... 16
4.3. "ModPreCon" 4x4 multivariable controller .............................................................................. 17
4.3.1. Standard multivariable controller ........................................................................................... 17
4.3.2. Predictive controller for only one controlled variable ............................................................... 19
4.4. "PIDCon” controller ................................................................................................................ 22
4.4.1. Standard controller ............................................................................................................... 22
4.4.2. Ratio controller ..................................................................................................................... 23
4.4.3. Split range controller ............................................................................................................. 26
5. Equipment Modules.................................................................................................. 29
1. Introduction
1.1. Overview
The standardization of automation engineering for processing plants, such as in the chemical industry, is a major
challenge. Different process steps and procedures, different equipment and flexibility in the production make the task
even more difficult.
One approach for standardization is structuring the plant according to the physical model of ISA 106. This specifies the
lower four levels, i.e. plant, unit, plant unit and control module. A plant always consists of units. The plant sections can, in
turn, contain standardized plant sections that are based on equipment modules. An equipment module comprises both
the physical equipment and the user program.
This application example contains standardized equipment modules in the form of software typicals that are provided in
SIMATIC PCS 7 as a multiproject.
Using them offers the following benefits:
The equipment modules offer a template that comprises the typical components of a partial automation solution, incl.
open- and closed-loop control, the necessary logic and visualization.
An equipment module is configured independently of the automation hardware and is a component of a pre-configured
PCS 7 project including the process visualization system. Due to hardware-independent configuration and the modular
structure, it is possible to integrate and use the equipment modules in PCS 7 projects in any way you like.
Equipment modules are composed of control modules (CMs). Function blocks of the PCS 7 Advanced Process Library (APL)
are used to create a control module.
Stirred tank
Temperature
control
Outflow of product
The equipment module concept provides pre-engineered and unified components for creating an automation solution,
e.g. metering or temperature control.
The equipment modules are implemented in the PCS 7 multiproject as follows:
• One project for the automation system (AS) and one project for the operator station (OS) are contained in the
component view.
• A hierarchy folder has been created in the plant hierarchy for each equipment module.
• The master data library contains all of the control module types in use.
In the AS project, all the open- and closed-loop control functions are implemented in the form of Continuous Function
Charts (CFCs). Apart from this, the AS project contains a simulation that approximately simulates a procedure, e.g. a filling
level change within an equipment module.
The OS project contains visualization by means of one process picture per equipment module and shows:
The visualization interface of the equipment modules consists of an overview picture and a process picture for each
equipment module.
Overview picture
The overview picture contains a schematic representation in the form of a material flow diagram of the process
engineering system that includes all the equipment modules in the example project.
Using the pushbutton of an equipment module, you switch to the respective process picture that contains the
functionality and the specific information of an equipment module. The system represents the process pictures in the
form of an appropriate section of the P&ID of a system.
Process picture
The process picture of an equipment module consists of the following parts:
Delimitation
The process behavior is not simulated in detail within the equipment module.
Required knowledge
Basic knowledge of the following specialist fields is a prerequisite:
SIMATIC PCS 7 ES/OS IPC647E For the PCS 7 V9.1 example project
W10
S7-PLCSIM Not part of SIMATIC PCS 7 V9.1; appropriate licenses are required.
NOTE In case of different hardware, please take heed of the minimum requirements for installing the
software components. The minimum requirements can be found in the Readme of the PCS 7 under
follow link:
https://support.industry.siemens.com/cs/ww/de/view/109780270.
2. Preparation and
commissioning
2.1. Preparation
The following instructions describe commissioning of the equipment modules by simulating the controller using the "S7-
PLCSIM" program. If you are using a real controller, you must configure existing hardware components in the hardware
settings.
1. Copy file "53843373_EquipmentModules_PROJ_PCS7V91.zip" to any folder on the configuration PC and then open
SIMATIC Manager.
2. Click on "File > Retrieve" on the menu bar and select file "53843373_EquipmentModules_PROJ_PCS7V91.zip". Then
click on "Open" to confirm.
3. Choose the folder where you want to save the project and click on "OK" to confirm.
The project is retrieved.
4. Confirm the "Retrieve" dialog by clicking on the "OK" button and then click on "Yes" in the dialog to open the project.
5. Right-click on "EquipmentModules_OS > OS01 > WinCC Appl. > OS" and then click on the "Open object" menu
command.
6. Confirm the "Configured server not available" dialog with "OK".
7. In the WinCC Explorer, open the properties of your computer and, in the opened Properties dialog, click on the "Use
local computer name" button.
NOTE If the OS cannot establish a connection with the AS (grayed out module icons), select the logical
device name "CP_H1_1" and restart the OS runtime.
2.2. Commissioning
You can commission the equipment modules after starting the simulation.
You can find a detailed description in Chapter 5.
NOTE If you have already worked with CMTs in your existing project, then check that they are identical
before skipping to the following steps, since this can lead to errors in your existing project or in the
Unit Template you want to integrate.
3. Copy the Enumerations from the master data library into the target project.
2. Copy the corresponding process screens from the OS project of the Equipment Module to the plant view of the target
project as well. If you wish, you can also copy the pictures "Help" and "Overview".
NOTE When copying the process screens, make sure that you copy the pictures to the hierarchy level of the
target project, which is configured as an OS area.
NOTE Please note that all colors are always used when exporting/importing color palettes. It is not possible
to export partial color tables.
If you have created your own color tables in your project, you can also export them and use an editor to merge the tables
in the XML file. Otherwise, you can create a new color table in your project and configure the colors individually. Make
sure, too, that the color index does not change, otherwise you will have to adjust the color settings of the objects in the
process screen. Of course, it is up to you to change the colors according to your requirements.
4. Control Module
4.1. Introduction
A control module is used to control individual pieces of equipment, like motors, valves, and controllers, for example. The
necessary blocks for carrying out this job, e.g. controlling a valve, are combined in a control module (CM). If a control
module is used several times in the project, e.g. with different characteristics, you create a control module type (CMT)
from it in PCS 7 and store it in the master data library. You can use this CMT in a flexible way anywhere in the project as
an instance with different characteristics (variants).
Using the technology allows to test automation projects using the program logic even if you do not have the real
hardware.
NOTE The application example "Control Module (CM) Technology - Efficient Engineering with SIMATIC PCS 7"
gives you a general overview of how to create, extend, and instantiate a CMT. The application example
is available at the following link: https://support.industry.siemens.com/cs/ww/en/view/109475748
NOTE Folder "pH" contains the source files of the pH simulation and the conversion block from pH value to
concentration difference. The functions and structure of the block are described in Section 6.5.
NOTE The BCM library uses the name of the central technology block of the APL.
NOTE A detailed description of each CMT with function description, supported variants and control elements
you can find in the application example "Control Module (CM) Technology - Efficient Engineering with
SIMATIC PCS 7" under the link:
https://support.industry.siemens.com/cs/ww/en/view/109475748
Structure
Chart partion A
Sheet 1 Sheet 4
Sheet 2 Sheet 5
Sheet 3 Sheet 6
Chart partition A
The following blocks are located on sheet 1:
NOTE In the case of operating point optimization, you do not specify an exact setpoint (e.g. SP1) for a
controlled variable; rather, a tolerance range is specified. The associated command value (CV1) may be
within this tolerance. Due to this tolerance definition, the controller works more flexibly and more
economically, since it does not have to control continuously to a fixed value.
• MV1_TrkOn ("Or04"): Forced manipulated variable (MV1) for the MPC controller in the case of a hardware fault
(CV_Bad) or if cascade switching is interrupted between the MV1 PID controller and the slave controller
• MV2_TrkOn ("Or04"): Forced manipulated variable (MV2) for the MPC controller in the case of a hardware fault
(CV_Bad) or if cascade switching is interrupted between the MV2 PID controller and the MV2 slave controller
• MV3_TrkOn ("Or04"): Forced manipulated variable (MV3) for the MPC controller in the case of a hardware fault
(CV_Bad) or if cascade switching is interrupted between the MV3 PID controller and the MV3 slave controller
• MV4_TrkOn ("Or04"): Forced manipulated variable (MV3) for the MPC controller in the case of a hardware fault
(CV_Bad) or if cascade switching is interrupted between the MV4 PID controller and the MV4 slave controller
The blocks below for monitoring and display of the control performance and the control deviation are located on sheet 4:
• Suppr_CPM_Calc_1 ("Or04"): Suppression of CPI calculation and message if message suppression was caused at an
"MPC_CPM_x" (CPI_SuRoot = 1) or a warning is active due to low control performance (CPI_WL_Act = 1).
• Suppr_CPM_Calc_2 ("Or04"): Suppression of CPI calculation and message if message suppression was caused at an
"MPC_CPM_x" (CPI_SuRoot = 1) or a warning is active due to low control performance (CPI_WL_Act = 1).
• Suppr_CPM_Calc_3 ("Or04"): Suppression of CPI calculation and message if message suppression was caused at an
"MPC_CPM_x" (CPI_SuRoot = 1) or a warning is active due to low control performance (CPI_WL_Act = 1).
• Suppr_CPM_Calc_4 ("Or04"): Suppression of CPI calculation and message if message suppression was caused at an
"MPC_CPM_x" (CPI_SuRoot = 1) or a warning is active due to low control performance (CPI_WL_Act = 1).
• MPC_CPM_1 ("ConPerMon"): Block for permanent monitoring of control performance (SP1Out, MV1 and CV1Out)
• MPC_CPM_2 ("ConPerMon"): Block for permanent monitoring of control performance (SP2Out, MV2 and CV2Out)
• MPC_CPM_3 ("ConPerMon"): Block for permanent monitoring of control performance (SP3Out, MV3 and CV3Out)
• MPC_CPM_4 ("ConPerMon"): Block for permanent monitoring of control performance (SP4Out, MV4 and CV4Out)
• QI_1 ("MonAnL"): Display and limit monitoring of the average value of control deviation for the TimeWindow specified
in "MPC_CPM_1"
• QI_2 ("MonAnL"): Display and limit monitoring of the average value of control deviation for the TimeWindow specified
in "MPC_CPM_2"
• QI_3 ("MonAnL"): Display and limit monitoring of the average value of control deviation for the TimeWindow specified
in "MPC_CPM_3"
• QI_4 ("MonAnL"): Display and limit monitoring of the average value of control deviation for the TimeWindow specified
in "MPC_CPM_4"
• from_Indicate_1 ("ComStruOut"): Reception of signals (measured value, unit, scaling and messages) of the first
process value to be controlled
• from_Indicate_2 ("ComStruOut"): Reception of signals (measured value, unit, scaling and messages) of the second
process value to be controlled
• from_Indicate_3 ("ComStruOut"): Reception of signals (measured value, unit, scaling and messages) of the third
process value to be controlled
The link blocks below, which are used for rapid engineering, are located on sheet 6:
• from_CTRL_1 ("ComStruOu"): Reception of control commands of the lower level PID controller for the MPC controller
parameters ("MV1ManHiLim", "MV1ManLoLim", and "MV1Trk") and the "MV1_TrkOn" block.
• to_CTRL_1 ("ComStruIn"): Output of the manipulated variable as a setpoint to the lower-level PID controller.
• from_CTRL_2 ("ComStruOu"): Reception of control commands of the lower level PID controller for the MPC controller
parameters ("MV2ManHiLim", "MV2ManLoLim", and "MV2Trk") and the "MV2_TrkOn" block.
• to_CTRL_2 ("ComStruIn"): Output of the manipulated variable as a setpoint to the lower-level PID controller.
• from_CTRL_3 ("ComStruOu"): Reception of control commands of the lower level PID controller for the MPC controller
parameters ("MV3ManHiLim", "MV3ManLoLim", and "MV3Trk") and the "MV3_TrkOn" block.
• to_CTRL_3 ("ComStruIn"): Output of the manipulated variable as a setpoint to the lower-level PID controller.
• from_CTRL_4 ("ComStruOu"): Reception of control commands of the lower level PID controller for the MPC controller
parameters ("MV4ManHiLim", "MV4ManLoLim", and "MV4Trk") and the "MV1_TrkOn" block.
• to_CTRL_4 ("ComStruIn"): Output of the manipulated variable as a setpoint to the lower-level PID controller.
NOTE The process value is made available to the MPC by linking the MonAn control module ("to_Indicate"
block) with the "from_Indicate_x" block.
NOTE The number of disturbance variables is determined by activating option '"Opt_DVx" and
interconnecting the respective process value. The disturbance variables are interconnected with the
following MPC inputs:
• 1st disturbance variable at the DV1 input of the MPC (activated as standard)
• 2nd disturbance variable at the MV2Trk input of the MPC (optional)
• 3rd disturbance variable at the MV3Trk input of the MPC (optional)
• 4th disturbance variable at the MV4Trk input of the MPC (optional)
Sheet 1 Sheet 4
Sheet 2 Sheet 5
Sheet 3 Sheet 6
Chart partition A
The following blocks are located on sheet 1:
NOTE In the case of operating point optimization, you do not specify an exact setpoint (e.g. SP1) for a
controlled variable; rather, a tolerance range is specified. The associated command value (CV1) may be
within this tolerance. Due to this tolerance definition, the controller works more flexibly and more
economically, since it does not control continuously to a fixed value.
The blocks below for monitoring and display of the control performance and the control deviation are located on sheet 4:
• MPC_CPM ("ConPerMon"): Block for permanent monitoring of control performance (SP1Out, MV1 and CV1Out)
• QI ("MonAnL"): Display and limit monitoring of the average value of control deviation for the TimeWindow specified in
"MPC_CPM"
• from_CV ("ComStruOut"): Receiving of signals (measured value, unit, scaling and messages) of the controlled variable
• CV_Lim ("StruScIn"): Upper and lower setpoint limit of the controlled variable
• from_DV1 ("ComStruOut"): Receiving of signals (measured value, CSF-signal and unit) of the first disturbance variable
• from_DV2 ("ComStruOut"): Receiving of signals (measured value, CSF-signal and unit) of the second disturbance
variable
• from_DV3 ("ComStruOut"): Reception of signals (measured value, CSF-signal and unit) of the third disturbance
variable
• from_DV4 ("ComStruOut"): Reception of signals (measured value, CSF-signal and unit) of the fourth disturbance
variable
NOTE The process values of the controlled variable and the disturbance variables are made available to the
MPC by linking the MonAn control modules ("to_Indicate" block) with the "from_CV", "from_DVx"
block.
The link blocks below, used for rapid engineering, are located on sheet 6.
• to_Actor ("ComStruIn"): Transfer of the manipulated variable (MV1), and the locking status (OosAct) to the actuator.
• from_Actor ("ComStruOu"): Reception of signals and standardization and unit of the actuator for the MPC (CSF,
OosAct, ScaleOut, Unit).
• MV1_Scale ("StruScIn"): Upper and lower manipulated variable limit for limiting the manipulated variable in the
controller in manual and automatic modes.
NOTE In "Plant View”, you activate master/slave operation by selecting "Opt_IF_Master”. After activation, the
"to_Master” and "from_Master” link blocks are available.
Using variants, the corresponding channel block is selected or deselected based on measured value transfer.
In addition, it is possible to use options to activate further functions without configuration at the CMT instance.
Variants and options are listed and described below.
Variant 1: Controller for analog measurement and manipulated variable (4-20 mA)
Variant 1 is activated by selecting functions PV_In and Opt_PV_Scale at the instance.
NOTE Scaling on the channel block has already been preset for the range 0 to 1.
You must carry out process value scaling at input "NormPV” of display block "C”.
PV_In
Intlock
CPM
PIDConRatio
(CMT Master Data Library)
NOTICE When using the Plant Automation Accelerator (PAA) V2.1, the variant "PV_Scale#" should not be used.
The scaling is set in PAA at the respective signal and adopted by the appropriate "Scale" input when
exporting to SIMATIC PCS 7.
NOTE In "plant view", you activate master/slave operation by selecting "IF_Master#". After activation, the
"to_Master" and "from_Master" link blocks are available.
Structure
• PV_Scale: Standardization of the process value for a channel block and measured value display
• PV_Unit: Standardization of the unit for a channel block and displaying measured values
• C ("PIDConL"): PID controller
• CPM ("ConPerMon"): Block for permanent monitoring of control quality
The outputs, operating mode, setpoint, actual value and manipulated variable of the PID controller are interconnected
with the CPM block
The following blocks are located on sheet 2:
• AIF_SFC ("ConnPID"): A free block for SFC linking (not a component of the APL or the standard library)
• Logic blocks for selecting the operating mode and for interlocking
- SP_LiOp ("Or04"): Setpoint source internal/external
- SP_IntLi ("Or04"): Internal setpoint via interconnection
- MV_Forced ("SelA02In"): Forced manipulated variable with selection ("In1" undefined, "In2" SFC link)
- MV_ForOn ("Or04"): Activates forced manipulated variable "In2" (MV_Forced) on the PID controller
- ManModOpLi ("Or04"): Formation of an OR output signal from field device in maintenance (channel blocks PV and
MV) and invalid process value (channel block PV in chart partition "B", Sheet 1.)
- ModLiOp ("Or04"): Operating mode selection between operator and interconnection or SFC
- ManModLi ("Or04"): Manual mode via interconnection or SFC (controlled via ModLiOp = 1)
Using the SFC link, data that is relevant to production is transferred to the PID controlling via the logic blocks. In addition,
channel blocks and the interlocking block (chart partition "A", Sheet 3) affect the output signals of the logic blocks.
Sheet 3 contains the "Intlock" interlocking module, which combines signals for standardized interlocking with the option
of displaying them on the OS.
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 24
Control Module
The link blocks below, used for rapid engineering, are located on sheet 6.
• to_Actor_Slave ("ComStruIn"): Transfer of the manipulated variable (MV), setpoint value (SP), process value (PV), and
the locking status to the actuator or slave (slave in the case of cascade control)
• from_Actor_Slave ("ComStruOu"): Reception of the actuating signal feedback (Rbk), the message with invalid process
values, and field device maintenance of channel blocks MV and Rbk, of the out unit and scaling of the actuating
display and travel range (ScaleOut) of the actuator or slave (slave in the case of cascade control)
• to_Master ("ComStruIn"): The communication block forms a structure consisting of outputs (setpoint, block is "out of
service" message, message for cascade switching, process value), of the PID controller, of the CSF block (message of
the channel blocks in the case of an invalid process value), and of channel blocks PV and MV (unit and scaling of the
process value).
• from_Master ("ComStruOu"): The communication block receives from the controller process tag of the main
component the signals of the CSF block and the setpoint of the PID controller that are relevant to interlocking.
• Ratio ("Ratio"): The block calculates the setpoint of the slave controller from the setpoint of the master PID controller
and the specified ratio.
• PV ("Pcs7AnIn"): Channel block for signal processing of an analog measured value, e.g. 0/4 to 20mA
• PV_TE ("Pcs7AnIn"): Channel block for signal processing of a resistance thermometer
• PV_FB ("FBAnIn"): Channel block for signal processing of a digitized process value (PA or FF processing unit)
• PV_DeltaCalc ("Sub02"): Formation of a difference value from two process values, e.g. differential pressure
• FromDeltaIn1: Input 1 for the difference value
• FromDeltaIn2: Input 2 for the difference value
• PV_IN ("Add08"): Merging the "PV_In" signals (analog process value)
• CSF ("Or04"): Grouping of the "Bad" signals (invalid process value) and reporting to the motor block and the Permit
group block
• OosAct ("Or04"): Grouping of the "OosAct" signals (device being maintained) and reporting to the motor block
NOTE If a thermocouple is used, you must carry out scaling at channel block "PV_TE" measured value display
in addition to scaling at block PV_Scale (process value scaling).
NOTICE The channel block for the thermocouple has already been preset for the range 0.0 to 1.0.
On sheet 2, the system additionally acquires the messages of the valve process tag channel block at blocks CSF and
OosAct and transfers them to the controller.
In the case of a positive "OosAct" signal, the controller switches to manual mode.
NOTE In "Plant View”, you activate master/slave operation by selecting "Opt_IF_Master”. After activation, the
"to_Master” and "from_Master” link blocks are available.
Using variants, the corresponding channel block is selected or deselected based on measured value transfer.
In addition, it is possible to use options to activate further functions without configuration at the CMT instance.
Variants and options are listed and described below.
Variant 1: Controller for analog measurement and manipulated variable (4-20 mA)
Variant 1 is activated by selecting functions PV_In and Opt_PV_Scale at the instance.
NOTE Scaling on the channel block has already been preset for the range 0 to 1.
You must carry out process value scaling at input "NormPV” of display block "C”.
PV_TE_In
PV_Fb_In
IF_Master#
PV_Scale#
PV_In
Intlock
CPM
PIDConSplitRange
(CMT Master Data library)
Moreover, there are split range applications with several actuators with the same direction of action (that individually
would not be strong enough), e.g.
• Oxygen control in bio fermenters via air feed and stirrer speed.
• Oxygen control in wastewater treatment plants via several compressors.
Structure
The control module type is preconfigured for the following setpoint range:
• PV_Scale: Standardization of the process value for a channel block and measured value display
• PV_Unit: Standardization of the unit for a channel block and displaying measured values
• C ("PIDConL"): PID controller
• CPM ("ConPerMon"): Block for permanent monitoring of control quality
The outputs, operating mode, setpoint, actual value and manipulated variable of the PID controller are interconnected
with the CPM block
The following blocks are located on sheet 2:
• AIF_SFC ("ConnPID"): A free block for SFC linking (not a component of the APL or the standard library)
• Logic blocks for selecting the operating mode and for interlocking
- SP_LiOp ("Or04"): Setpoint source internal/external
- SP_IntLi ("Or04"): Internal setpoint via interconnection
- MV_Forced ("SelA02In"): Forced manipulated variable with selection ("In1" undefined, "In2" SFC link)
- MV_ForOn ("Or04"): Activates forced manipulated variable "In2" (MV_Forced) on the PID controller
- ManModOpLi ("Or04"): Formation of an OR output signal from field device in maintenance (channel blocks PV and
MV) and invalid process value (channel block PV in chart partition "B", Sheet 1.)
- ModLiOp ("Or04"): Operating mode selection between operator and interconnection or SFC
- ManModLi ("Or04"): Manual mode via interconnection or SFC (controlled via ModLiOp = 1)
Using the SFC link, data that is relevant to production is transferred to the PID controlling via the logic blocks. In addition,
channel blocks and the interlocking block (chart partition "A", Sheet 3) affect the output signals of the logic blocks.
Sheet 3 contains the "Intlock" interlocking module, which combines signals for standardized interlocking with the option
of displaying them on the OS.
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 27
Control Module
The link blocks below, used for rapid engineering, are located on sheet 6.
• to_Actor_Slave ("ComStruIn"): Transfer of the manipulated variable (MV), setpoint value (SP), process value (PV), and
the locking status to the actuator or slave (slave in the case of cascade control)
• from_Actor_Slave ("ComStruOu"): Reception of the actuating signal feedback (Rbk), the message with invalid process
values, and field device maintenance of channel blocks MV and Rbk, of the out unit and scaling of the actuating
display and travel range (ScaleOut) of the actuator or slave (slave in the case of cascade control)
• to_Master ("ComStruIn"): The communication block forms a structure consisting of outputs (setpoint, block is "out of
service" message, message for cascade switching, process value), of the PID controller, of the CSF block (message of
the channel blocks in the case of an invalid process value), and of channel blocks PV and MV (unit and scaling of the
process value).
• from_Master ("ComStruOu"): The communication block receives from the controller process tag of the main
component the signals of the CSF block and the setpoint of the PID controller that are relevant to interlocking.
• SplitRange ("SplRange"): block to split the manipulated variable MV from the PID controller. The segmentation is based
on the set parameters.
• to_Actor_Slave2 ("ComStruIn"): Transfer of the manipulated variable (MV), setpoint value (SP), process value (PV), and
the locking status to the actuator or slave (slave in the case of cascade control)
• from_Actor_Slave2 ("ComStruOu"): Reception of the actuating signal feedback (Rbk), the message with invalid process
values, and field device maintenance of channel blocks MV and Rbk, of the out unit and scaling of the actuating
display and travel range (ScaleOut) of the actuator or slave (slave in the case of cascade control)
• SplitRangeCut ("Or04"): Grouping of the disconnect signals from the cascaded valves to the controller.
• PV ("Pcs7AnIn"): Channel block for signal processing of an analog measured value, e.g. 0/4 to 20mA
• PV_TE ("Pcs7AnIn"): Channel block for signal processing of a resistance thermometer
• PV_FB ("FBAnIn"): Channel block for signal processing of a digitized process value (PA or FF processing unit)
• PV_DeltaCalc ("Sub02"): Formation of a difference value from two process values, e.g. differential pressure
• FromDeltaIn1: Input 1 for the difference value
• FromDeltaIn2: Input 2 for the difference value
• PV_IN ("Add08"): Merging the "PV_In" signals (analog process value)
• CSF ("Or04"): Grouping of the "Bad" signals (invalid process value) and reporting to the motor block and the Permit
group block
• OosAct ("Or04"): Grouping of the "OosAct" signals (device being maintained) and reporting to the motor block
NOTE If a thermocouple is used, you must carry out scaling at channel block "PV_TE" measured value display
in addition to scaling at block PV_Scale (process value scaling).
NOTICE The channel block for the thermocouple has already been preset for the range 0.0 to 1.0.
On sheet 2, the system additionally acquires the messages of the valve process tag channel block at blocks CSF and
OosAct and transfers them to the controller.
In the case of a positive "OosAct" signal, the controller switches to manual mode.
5. Equipment Modules
In this chapter, you will find all the relevant information for each equipment module including specific properties. The
structure and basic functionality of the control module types that are used are described in Chapter 4 "Control Module".
The following equipment modules are described below:
• "Level-control"
• Buffer level control with feedforward disturbance compensation "Buffer-Control"
• "Split-Range-Pressure" control
• "Ratio-Control"
• "Split-Range-Temperature" control
• pH value control using the "pH-Control-Std" standard controller
• pH value control using the "pH-Control-MPC" model predictive controller
• Temperature cascade control via slave flow control loop "Temperature-Flow-Cascade"
• Coarse-/Finestream control using the "Stream-Control”
• Gradient limits in actuators "Gradient-Limit"
NOTE Below, we will use the designations CM for control module and CMT for control module type.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and containers relevant to operation.
FI
Inlet
Inflow
LIC
Level
YC FI
Outlet_Level Outlet
Outflow
CM and variants
The "Level Control" equipment module consists of four connected CMs and one simulation chart. The fill level of a
container is simulated in the "Sim_Level” simulation chart with the help of a non-linear model. In addition, the response of
the valve is simulated in this chart, which leads to a more realistic description of dynamic valve behavior. In the
"Sim_Level” simulation chart, the inflow is simulated with the help of a valve module and the valve position provided for
disturbance compensation is added.
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
PV_in_percent
to_Actor1 from_Ctrl
OUT
Out Out
mul_p_Hydro
from_Actor1 to_Ctrl
OUT
In Out
ValvelDeadtime
VlvAnL
Out FI_Outlet_Level
Rbk
PV
ScaleInlet SimPV_In
OUT FI_Inlet_Level
PV
SimPV_In
Control "LIC_Level" acquires the fill level of the container ("Sim_Level” simulation chart) and regulates it using
"YC_Outlet_Level” control valve. In addition, the two process tags "FI_Outlet_Level" and "FI_Inlet_Level” serve the purpose
of displaying inflow and discharge in the OS.
"Sim_Level" simulation
The structure and the parameterization of the "Sim_Level" simulation used is explained in Section 5.1.3.
LIC_Level
The instance has the following parameterization.
Block Connection Value Use
6. Wait for about 3 minutes and enter a new setpoint of 25 % for the "Sim_Level/Sim_Flow_Rate” valve.
7. Close the faceplate and observe the plotter for about two minutes until the new setpoint has been reached again.
8. Then click on the "Start/Stop" icon on the toolbar of the OnlineTrendControl.
Evaluation
After the inflow reduction, the level drops below the setpoint. The controller observes the level change and then reduces
the setpoint of the discharge valve until the level once again reaches the setpoint. Control towards the setpoint, however,
causes permanent fluctuations in the manipulated variable for the discharge valve.
Mode of operation
In the case of a closed-loop control with deadband, the manipulated variable is not changed as long as the controlled
variable moves within the parameterized limits of the deadband. Only if the values leave the deadband, the feedback
controller and consequently the final actuator become active.
If the controller is active, the deadband is dynamically switched off until the controlled variable is again in the center of
the deadband. This prevents a permanent fluctuation at the edge of the deadband.
NOTE The actuator activity can be further reduced by means of low-pass filtering of the disturbance variable.
This has no effect on the stability of the control loop because the low-pass filter is only in the
feedforward variable and not in the feedback path of the closed control loop. In addition, the
feedforward control is provided with its own deadband in order to further reduce actuator activity.
Controller design
In context of a buffer control task, the required behavior is different from exact level control. In buffer control, the tank
volume is used selectively to compensate for inflow fluctuations. Two options are available when doing this:
• The fill level is not measured continuously at all; rather, the minimum and maximum limits are monitored by binary
(e.g. capacitive) fill level switches. Continuous control is not used for this solution; rather, discrete-event control is
used, i.e. a binary signal is used to close the inflow or outflow.
• Controller tuning is purposefully set slower. Within the scope of the specification, the maximum permissible deviation
Δhmax of the fill level from the setpoint is defined, as well as the maximum hight d max of inflow step disturbances to be
expected. With regard to permanent control deviation, the gain of a P controller must be defined as greater than
Gain= dmax / Δhmax. You can also set up a PI controller such that the maximum deviation of fill level after step
disturbance is less than dmax. In the Dechema Seminar entitled "Process Controls – From the the Basics to Advanced
Control" (www.dechema.de), the formulas below are recommended:
- GainEff = 0.7358 dmax / Δhmax
- Ti = 5.4366/Ki * Δhmax / dmax
NOTE The physical controller gain is in units MV_Unit/PV_Unit. In case of normalization (NormPV ≠ NormMV),
gain must be converted according to the following formula:
Gain = GainEff * (NormPV.High - NormPV.Low) / (NormMV.High - NormMV.Low)
It is possible to determine the integration constant Ki of the controlled process in the unit PV_Unit/s using the PID tuner.
You can find the integration constants at "Gain" in the "Process parameter" sector.
• In order to avoid permanent control deviations, the proportional-only controller is enhanced with feedforward
disturbance compensation. This alternative is implemented in the template. In this case, the formulas with respect to
disturbance amplitude mentionend in the above paragraph are not relevant. The controller can be designed with any
standard approach considering stability and control performance, e.g. with PCS 7 PID-Tuner. During application of PID-
Tuner take care that the disturbance variable stays as even as possible during data logging for step testing. After
tuning, the level controller is temporarely run without deadband to verify loop dynamics, before activating deadband
in order to smooth outflow variations.
Overview
P&I Diagram
The P&I diagram below symbolically represents all of the components, such as field devices and tanks relevant to
operation.
Inflow FI
Inlet
DV (FFWD)
LIC
Buffer
YC FI
Outlet_Buffer Outlet
Outflow
CM and variants
The "BufferControl" equipment module consists of three connected control modules, a CFC chart for the dynamic
deadband of the feedforward disturbance compensation and a simulation plan. The level of a container is simulated in the
"Sim_Buffer” simulation chart with the help of a non-linear model. In addition, the dynamic response of the valve is
simulated in this chart, which leads to a more realistic model of valve behavior. In the "Sim_Buffer” simulation chart, the
inflow is simulated with the help of a valve module and valve position is provided as disturbance variable.
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 36
Equipment Modules
The following table provides an overview of the components of the equipment module including the associated control
modules.
CM CM Selected variants Description
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
PT1 Flow_to_MV
from_Ctrl
In Out
Out
ValvelDeadtime
to_Ctrl
Out
Out
Control "LIC_Buffer" acquires the fill level of the container and regulates it using "YC_Outlet_Buffer” control valve. In
addition the "Sim_Buffer” transmits the disturbance variable – the inflow into the container – to the "LIC_Buffer” process
tag which adds the "disturbance variable” to the manipulated variable of the controller. In addition, the simulation
generates from the valve state the inlet and outlet of the tank, which visualize over the both display monitors "FI_Inlet"
and "FI_Outlet".
Sim_Buffer
The structure and the parameterization of the "Sim_Buffer" simulation used is explained in Section 5.1.3.
LIC_Buffer
The instance has the following parameterization.
Block Connection Value Use
NOTE Determined by the nature of the process, the level does not have to correspond exactly to the setpoint
but must instead be in a mid-container zone instead. For this reason, it is a P-controller with a
relatively small controller gain (<1) and an activated deadband. In order to avoid an oscillation around
the deadband limit, the dynamic deadband disabling is effected via the feature bit 30 of the "PIDConL”
function block. If the fill level leaves the deadband, this is deactivated and the fill level is brought to
the center of the dead zone by the now active control. Only then is the control deactivated again and
the manipulated variable is held.
NOTE Feedforward control is realized via the "PIDConL.FFwd" connection. The value of "FFwd" is internally
added to the manipulated variable "MV" by the controller and thus directly affects the position of the
actuator. The flow measurement of the container inlet is used as the disturbance variable.
Dyn_Deadband
Due to inflow fluctuations, feedforward control leads to a permanent actuator activity despite the active controller
deadband. This undesirable behavior is suppressed in the "Dyn_Deadband" CFC. In order to calculate the appropriate value
for feedforward control, a characteristic curve for the effect of the disturbance variable on level control is stored.
1 4
7
6
3
1. Filtering of steep signal gradients (first order lag with 3 seconds time-constant)
2. Calculation of the upper limit for the adoption of a new disturbance value (Addition)
3. Calculation of the lower limit for the adoption of a new disturbance value (Subtraction)
4. Evaluation as to whether a limit has been exceeded or undercut
5. Deactivation of disturbance variable deadband upon disabling of controller deadband
6. Switchover between new and old disturbance variable
7. Conversion of disturbance variable to manipulated variable signal with the help of a polygon function block
NOTE In practice you will have to determine the interpolation values of the polygon function block either
experimentally or based on pre-existing measurements. When the deadband is disabled, the
associated outflow valve positions are recorded for the various values of the disturbance variable
which lead to the desired constant level. The value pairs "disturbance variable measurement / valve
position" yield the different interpolation points "InX / OutX" of the polygon module.
6. Wait for about 3 minutes and then enter a new setpoint of 25 % for the "Sim_Buffer/Sim_Flow_Rate” valve.
7. Close the faceplate and observe the plotter for about two minutes until the setpoint has been reached again.
8. Then click on the "Start/Stop" icon on the toolbar of the OnlineTrendControl.
1. After the inflow has been reduced, the feedforward compensation reduces the setpoint of the outflow valve such that
the tank level does not leave the deadband. In this case the controller does not need to intervene.
2. Thanks to the relatively wide deadband, the fill level does not reach the setpoint exactly again, but instead remains
slightly below the setpoint. However, for this no further intervention of the controller via the outlet valve is necessary,
so that the valve can be operated in a low-wear manner. Outflow keeps constant for longer time intervals.
3 4 5
7 8
1. Calculation of the flow for the inlet (valve opened by 100 % corresponds to inflow of 250 l/s)
2. Calculation of the flow for the outlet (valve opened by 100 % corresponds to inflow of 0.48 m²)
3. Determination of level change (addition of inflow and subtraction of discharge)
4. Formation of an integral value by integrating the change in flow (every second)
5. Delay in level (PT1 response with 3.5-second delay)
6. Calculation of flow rate for discharge according to Torricelli’s Law
7. Creation of measurement noise
8. Conversion of level into percentage
NOTE According to Torricelli’s Law, the higher the level, the higher the flow speed in the container outflow,
proportional to the square root of the fill level. As a consequence, for the same valve position the
discharge rate will vary depending on the fill level of the container:
q = A ∙v
v: Efflux rate g: Gravitational
constant
h: Fill height A: Efflux cross-section
q: Outflow quantity
On sheet 2 an equal percentage characteristic line for the outlet valve is simulated.
In addition, the valve reaction is delayed with respect to the valve position setpoint, and the valve position is discretized
to simulate the behavior of an electro-pneumatic valve positioner.
NOTE For further information about the equal-percentage valve characteristic line please refer to standard
VDI-2173.
1. Delay in valve actuation (first order lag with time constant 2 seconds)
2. Valve actuation in integer numbers (1 % steps)
3. Dead time of valve actuation (delay of 1 second)
4. Approximation of the equal percentage valve characteristic by means of a polygon function block
NOTE The tank outlet valve is further adapted to a realistic valve behavior through a small first order lag, a
dead time and a discretization of the valve position to integer percentages.
This means that the valve position follows the manipulated variable of the master level controller with
a certain sluggishness. The discretization only allows integer percentage values, i.e. the valve
simulation cannot reach the setpoint position with infinite accuracy. The equal-percentage
characteristic leads to a non-linearity in the actuator.
NOTE Both the tank simulation and the actuator have a non-linear behavior. Therefore, a non-linear
characteristic curve must be inserted with the aid of a polygon function block between the disturbance
variable measurement and the feedforward control.
The interpolation points of this characteristic curve can be determined experimentally. To do this, for
different inflow rates the actuator must be adjusted until the container level stays constant at the
desired value (container mid-height). The registered value pairs "Inflow measured/Valve position” can
then be used for the polygon block.
On Sheet 3 of the CFC the inflow with disturbance and measurement noise is simulated.
1 2 5 6
NOTE Now all the valves and controllers are pre-configured in such a manner that manipulated variable and
setpoint can be defined via the two analog input windows in the "Compare” window.
1 2 3
1. After the inflow increase, the level rises above the setpoint for both control concepts.
The PI controller for the exact level control detects the change in level and consequently increases the manipulated
variable of the outlet valve until the filling level has reached the desired setpoint again. Control towards the setpoint,
however, produces permanent fluctuations of the manipulated variable for the outlet valve.
In the case of the buffer level control with feedforward disturbance compensation, the changed inflow is detected as a
change in the disturbance variable and the manipulated variable is then moved accordingly. The immediate reaction
to the inflow change provides a faster intervention and the level rises less compared to PI control.
Thanks to the relatively wide deadband, the level does not leave the setpoint area and the controller has to re-adjust
less frequently, which eases the wear of the actuation mechanism.
2. With the inflow change from 75 % to 25 % of the maximum inflow, both fill levels sink and the fill level of the buffer
leaves the deadband. This activates the P controller and the deadband is temporarily deactivated. As soon as the level
approaches the setpoint again, the deadband is activated and the manipulated variable remains constant.
In a manner analogous to the inflow change described in point 1, the PI controller reacts to the exact filling level with
a change of the outflow valve until the fill level has reached the setpoint.
3. The third inflow change occurs before the PI controller has reached the fill level setpoint, the latter thus reacts by
overshooting the fill level more than with the inflow change under point 1.
In contrast to this, the buffer level controller is again within the setpoint range and therefore reacts only to a change
of the inflow with a change of the manipulated variable via the feedforward control.
Overview
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and tanks relevant to operation.
Venting
YC
Out
PIC YC
Split In
Inerting
CM and variants
The "Split-range pressure" equipment module consists of three connected CMs and one simulation chart. In the simulation
chart, a container pressure and the effects due to feeding and venting inert gas are simulated.
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 49
Equipment Modules
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
PV V
In
SimPV_In MV
In1
from_Actor1
In YC_Out
V
from_Actor2
MV
In
from_Ctrl
In
to_Ctrl
Out
"PIC_Split" acquires the container pressure ("Sim_PresLevel" simulation chart) and regulates it with the help of the two
control valves "YC_In" and "YC_Out".
"Sim_PresLevel" simulation
The pressure change in the container due to inerting or venting is simulated in the "Sim_PresLevel" CFC.
The figure below shows the sequence of the simulation.
1 2 3 4
1. Calculation of the pressure change starting from the proportionality factor (valve opened by 100 % corresponds to a
change in pressure of 0.1 bar)
2. Reduction in the pressure by 0.01 bar, e.g. due to container pressure loss
3. Time lag of the change in pressure
4. Time integral of pressure changes (every second)
InScale.High 100.0
Split range InScale.Low -100.0 Marginal range for the input signal
NOTE The program "PID Tuner" is available for commissioning the "PIC_Split" controller. At the beginning,
data recording for the "PID-Tuner" is done in an operating range where only positive values of the
manipulated variables are exptected. After this, a comparable experiment is made in an operating
range where only negative manipulated variables occur.
If both part transfer functions for venting and inerting show significantly different values for process
gain, this must be compensated by a different gradient of both branches of the split range
characteristic curve.
Further information and configuration guidelines can be found in the Online Help for the
"SplitrangeControl" process tag type.
The new setpoint will have been reached after about two minutes. To compensate the pressure loss of the container, the
valve is opened to about 10 % for venting.
6. Specify "3 bar” as new setpoint for the controller.
7. Close the faceplate and observe the plotter for about two minutes until the new setpoint has been reached.
Evaluation
1
2
1. After the setpoint step, the manipulated variable is set to -100 and by this, the pressure feed valve is opened.
2. The process value slightly exceeds the setpoint; the pressure feed valve is closed evenly.
3. After reaching the setpoint, the pressure feed valve has been opened by about 10 %; this means that the pressure loss
of the container has been compensated.
5.3. "Ratio-Control"
In case of ratio control, different gases or other input materials are fed in fixed mixing ratios into a tank via inlet lines.
The ratio control scheme consists of one controller for the main input material (master controller) and one controller for
each additional input material (slave controller).
The example below describes feed control with two input materials, and later on is expanded with another input material.
Overview
Below, the structure in the P&ID is shown and all of the CMs and the simulation of the equipment module are described.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and containers relevant to operation.
FIC MV YC Legende
MainComp SP MainComp MV = Manipulated variable
SP = Active setPoint
1st Inflow
FFIC YC
Comp_1 Comp_1
2nd Inflow FI
CompFlow
Outflow
CM and variants
The "ratio control" equipment module consists of four connected CMs and one simulation chart. On the simulation chart,
the system calculates the total of all the inflows (input materials) and displays them.
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
YC_MainComp "ValAn" • IF_Ctrl# Control valve for the main input material
• MV_Scale#
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 54
Equipment Modules
CM CMT Selected variants Description
• RbkReturn
• YC
YC_Comp_1 "ValAn" • IF_Ctrl# Control valve for the additional input material
• MV_Scale#
• RbkReturn
• YC
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
Sim_CompFlow FIC_MainComp
YC_MainComp
Scale_MainComp PV V
In1 SimPV_In MV
Scale_Comp_1 to_Actor_Slave
from_Ctrl
In1 Out
In
Lag_MainComp from_Actor_Slave
to_Ctrl
Out In
Out
Lag_Comp_1
Out
FFIC_Comp_1
SumOfFlow YC_Comp_1
PV
Out V
SimPV_In
MV
to_Actor_Slave
Out from_Ctrl
In
FI_CompFlow from_Master
In to_Ctrl
I
Out
PV from_Actor_Slave
In
Control "FIC_MainComp" acquires the flow of the main input material and regulates it using control valve "YC_MainComp".
In addition, "FIC_MainComp" transfers its own setpoint to process tag "FFIC_Comp_1". This means that "FIC_MainComp" is
the master controller for "FFIC_Comp_1".
Control "FFIC_Comp_1" acquires the flow of the additional input material and regulates it using control valve
"YC_Comp_1". "FFIC_Comp_1" receives the setpoint from control "FIC_MainComp"; this means that "FFIC_Comp_1" is the
slave controller.
"Sim_CompFlow" simulation
The flow of the main input material and the additional input material are simulated in the "Sim_CompFlow" CFC and the
overall flow rate is calculated too. Apart from this, the system displays the flow rate based on process tag type "MonAn".
The figure below shows the sequence of the simulation.
1 2 5
3 4
1. Calculation of the flow for the main input material (valve opened by 100 % corresponds to inflow of 2000 l/h)
2. Delay in change of flow (PT1 response with 5-second delay)
3. Calculation of the flow for the main input material (valve opened by 100 % corresponds to inflow of 500 l/h)
4. Delay in change of flow (PT1 response with 2-second delay)
5. Determination of the complete flow quantity (addition)
Inputs "In1" of highlighted blocks 1 and 3 get their manipulated variables from valve blocks "I" of process tags
"YC_MainComp" and "YC_Comp_1". The "Out" outputs of highlighted blocks 2 and 4 are interconnected with the channel
blocks of the controls.
FIC_MainComp
The instance has the following parameterization.
Block Connection Value Use
PV_Unit In 1353 Unit of the process value l/h (liters per hour)
NOTE In the current configuration, the master controller can carry out control regardless of the status of the
slave controller. If you do not want this behavior, you can, for example, interconnect the "CascaCut"
output of the slave controller to the "Interlock" input or block (can be selected optionally).
If you want to use other signals of the slave controller such as "LockAct" (locking active) or "OosAct"
(out of service) for locking, you can add another "ComStruOut" communication block to the slave
controller and interconnect block outputs BoStru1 thru BoStru3 to the locking block.
NOTE The setpoint is transferred to the controller process tag(s) of the additional input material(s). Using the
setpoint instead of the manipulated variable means that the controller structure does not correspond
to a typical cascade controller.
The "PID Tuner" program is available for commissioning the controller. If there is a considerably
difference in closed loop response time after the optimization, you can try adapting and compensating
the parameters of both control loops manually. The highest priority however is the stability of the
transient response of both individual control loops. In this context, there can be a temporary deviation
from the specified ratio in the case of setpoint steps. If such temporary deviations in one direction
must not occur at all due to safety reasons, additional logic has to be implemented. E.g. burner control
with flow controllers for fuel gas and air in a fixed ratio: in this case you have to make sure that there
is always a little bit more air than required, because a deficiency of air can be dangerous even in short
time intervalls.
FFIC_Comp_1
The instance has the following parameterization.
Block Connection Value Use
PV_Unit In 1353 Unit of the process value l/h (liters per hour)
FI_CompFlow
The instance has the following parameterization.
Block Connection Value Use
PV_Unit In 1353 Unit of the process value l/h (liters per hour)
NOTE While master controller "FIC_MainComp" is not working in automatic mode, it does not return a
setpoint (proportionally) to the slave controller either.
NOTE The system displays the current actual value of the ratio in the "Ratio" block, which results from the
setpoint directed to the slave controller.
Both controller setpoints will have been reached after about 1 minute.
8. Enter a new setpoint of "1500 l/h" in master controller "FIC_MainComp".
9. Wait for about 90 seconds and then click on the "Start/Stop" icon on the toolbar of the OnlineTrendControl.
10. On the toolbar of the OnlineTrendControl, click on the "Ruler" icon and move the ruler to the lowest value with the
greatest deviation, as show in the evaluation below.
Evaluation
The "OnlineTrendControl" that is embedded in the process picture is set to the maximum value ranges. If the ratio
changes, the value range of the additional input material adapts automatically.
Due to the different response times of the controllers, the ratio is temporarily 29 % (0.29). Compared to the ratio setpoint
of 25 % (0.25), a deviation of 4 % results temporarely before the correct ratio is reached in the steady state.
In this case, it is not possible to improve the controller design for slave controller "FFIC_Comp_1" by means of PID
controller optimization, since the aim of the controller design is optimum tracking of the additional input material.
NOTE For further information and configuration guidelines, refer to the Online Help for the "RatioControl"
process tag type. You can find the process tag type in "PCS 7 – Advanced Process Library”.
The response curves from the OnlineTrendControl lead to the considerations below for the controller design to match the
transient responses of the master and slave loops as closely as possible to one another:
• The relatively large deviation at the start of step response indicates that the gain of the slave controller is too high, i.e.
the slave controller process value rises faster than the actual value of the master controller.
• The relatively slow speed with which the final value of the setpoint step-change is reached, indicates an integration
time of the master controller that is too high, i.e. the master controller enters the steady state slower than the slave
controller.
Due to the different response times of the controllers, the ratio after optimization is temporarily 25.6 % (0.256).
Compared to the set ratio of 25 % (0.25), a deviation of 0.6 % results briefly.
NOTE If the number of locking signals of the slave controller has to be acquired in the master controller, the
options below are available for adapting the Ctrl type (CMT):
Group the signals of the communication blocks (from_Actor_Slave) using OR blocks. As a result, one
valve and seven additional input materials are interconnected by means of one interlock block.
Disadvantage:
Inaccurate error display, i.e. the system does not differentiate between errors in the cascade
controller, an "out of service” signal of the controller block, and a "Bad” status of the controller channel
blocks.
Duplicate the existing interlock block and group the two (Out) outputs of the interlock blocks using an
OR block. For interconnection (Out output) of the OR block, use the (Out output) interconnections of
the existing interlock block.
You can call up the faceplate of the first interlock block from the controller's faceplate. The faceplate of
the second interlock block is opened by means of its block display symbol in the process picture.
Replace the existing locking block with 8 input signals (Intlk08) with a locking block with 16 input
signals (Intlk16). Apply all the interconnections of the previous locking block.
Requirements
If different additional input materials are measured in different measurement units, the conversion factor in the ratio
block also includes conversion of the units.
NOTE In the case of different physical units, you must specify the other measurement unit for the additional
input material. The ratio factor in the ratio function block now has to include the conversion from the
flow unit of the master controller to the flow unit of the slave controller.
Additionally, when displaying the trend curves in a common diagram, it is advisable to label clearly.
If different travel ranges are needed in the case of the partial control loops of a ratio controller, you must delete the
corresponding interconnections and parameterize them for the respective partial control loop.
Description
To add another additional input material to the equipment module, proceed as follows:
1. Copy CMs "FFIC_Comp_1" and "YC_Comp_1" at the same time. Paste the copied CMs back into the same hierarchy
folder. Rename the process tags appropriately (below, the CMs will be referred to as "FFIC_Comp_2" and
"YC_Comp_2").
NOTE When you copy the process tags at the same time (highlight the process tags and then click on Edit >
Copy on the menu bar), the connections between the highlighted process tags are retained.
3. The simulation model is designed for two additional input materials. Make the interconnections below in CFC
"FFIC_Comp_2" to connect the second additional input material to the simulation.
Block Connection Use
4. Open process tag "YC_Comp_2" and make the following interconnections in chart partition "A" sheet 1:
Block Connection Use
NOTE When additional input materials are added to the "Ratio-Control” equipment module, you must
compile and load the blocks and charts and compile the OS.
NOTE The "Split-Range-Temperature" equipment module can be used for tanks or reactors in which
temperature control is provided via the reactor jacket or an external heat exchanger.
In the following example, reactor temperature control is carried out using an external heat exchanger.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and tanks relevant to operation.
TIC
Temp
TIC YC
Split Heat
Inflow
heating
medium
YC
Cool
Inflow
cooling
medium
Outflow
NS
PumpMixture
CM and variants
The "Split-range temperature" equipment module consists of four interconnected CMs, one CM for pump control, and one
simulation chart. The simulation chart simulates the internal temperature of a container (input material mixture), the
temperature of a heat exchanger, and the effect of changes in temperature (heating steam and cooling water).
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
TIC_Split PIDConSplit • IF_Master# Slave controller for split-range control with one
Range • PV manipulated variable and two actuators
• PV_Scale#
YC_Heat ValAn • IF_Ctrl# Control valve for the first manipulated variable
• MV_Scale#
• RbkReturn
• YC
YC_Cool ValAn • IF_Ctrl# Control valve for the second manipulated variable
• MV_Scale#
• RbkReturn
• YC
NS_PumpMixture Mot • 1Fbk# A pump (e.g. a flow pump) for continuous pumped
circulation of the contents of the container
NOTE The "NS_PumpMixture” CM is interconnected in the SFC (Sequential Function Chart) It is not necessary
to interconnect with other process tags in the "Split-Range Temperature” equipment module.
To ensure that the system does not generate an error message due to a missing feedback signal, the
"Start" output signal is interconnected with the "FbkRun" input signal of motor block "U".
Heat from_Master
from_Actor_Slave
In1 In
In
HeatExchanger Splitrange
PV
OPEN1_11 SimPV_In Out1
OPEN1_1 Out2
Out1Act
TempLevel Out2Act
Out YC_Heat
PV from_Ctrl
HeatExchanger SimPV_In In
V
to_Actor1 to_Ctrl
Out Out
to_Actor2
Out YC_Cool
from_Actor1 from_Ctrl
In In
from_Actor2 to_Ctrl
In Out
Controller "TIC_Temp" uses the simulated internal container temperature from simulation chart "Sim_TempLevel" and
generates the setpoint specification for the split range control. The desired temperature progression is thus configured in
process tag "TIC_Temp".
Controller "TIC_Split" receives the setpoint specification from the master controller and regulates the simulated
temperature of a heat exchanger that transfers heat to the inside of the container.
"Sim_TempLevel” simulation
In CFC "Sim_TempLevel", the system simulates a temperature change due to hot steam or cooling water onto the heat
exchanger and simulates the internal temperature of the container.
The figure below shows the sequence of the simulation.
1
2
1. Reduction of the manipulated variable for simulation. This makes it possible to represent the valve openings of the
heating and cooling valves with more emphasis in the trend display.
2. Calculation of the temperature of a heat exchanger. The change in temperature depends on the openings of both
valves (a bipolar signal is distributed to the heating steam and cooling water valve) and it is processed after passing
through a time-delay block.
3. Internal container temperature that changes depending on the inflow from the heat exchanger. The temperature in
the inside of the container is 40 % lower than in the heat exchanger (a factor of 0.6) and it is calculated after passing
through two delay elements. The output signal (internal container temperature) has small signal noise.
NOTE Simulation behavior does not correspond to a real process and it is only used to demonstrate the
functionality and mode of operation of the "Split range temperature" equipment module. Block
"SIMU_AI" has integrating behavior whereby heating and cooling act with the same intensity. With real
heat exchangers, both heat losses into the surroundings and different behavior when heating (e.g.
steam) and cooling (e.g. flowing water) are to be expected.
TIC_Temp
The instance has the following parameterization.
Block Connection Value Use
TIC_Split
The instance has the following parameterization.
Block Connection Value Use
C ManLoLim -100.0 Lower limit for the manipulated variable in manual mode
(hidden)
Split range InScale.High 100.0 Marginal range for the input signal
InScale.Low -100.0
NOTE The "PID Tuner" program is available for commissioning the "TIC_Split" controller.
At the beginning, experiments for data recording by "PID-Tuner" are conducted in an operating range
where only positive values of manipulated variables are expected. After this, a comparable experiment
is made in an operating range where only negative manipulated variables occur. If both part transfer
functions for heating and cooling show significantly different values for processgain, this must be
compensated by a different gradient in both branches of the split range characteristic curve. After the
slave controller including the split range has been completely commissioned and tested, the master
controller "TIC_Temp" is optimized using the "PID Tuner" program.
For further information and configuration guidelines, refer to the Online Help for the "CascadeControl"
process tag type of the PCS 7 Advanced Process Library.
YC_Heat
The instance has the following parameterization.
Block Connection Value Use
YC_Cool
The instance has the following parameterization.
Block Connection Value Use
NOTE The motor can be started with the "Start" command on the faceplate.
In process mode, the motor is controlled via an SFC, e.g. at start-up of the plant.
TIC_Temp TIC_Split
After setpoint change SP1, the master controller calculates a manipulated variable MV1 and forwards it in the cascade to
the slave controller. This manipulated variable is represented as setpoint SP2 for the slave controller in the curve chart.
The slave controller calculates manipulated variable MV2 from setpoint curve SP2. MV2 acts on the heating and cooling
valves and yields temperature curve PV2 of the heat exchanger.
Temperature PV1 in the container follows the temperature of heat exchanger PV2 with a delay.
Legend The noise of process variable PV1 leads to noise of manipulated variable MV1 and consequently of
setpoint SP2. The oscillation of manipulated variable MV2 in real world applications has to be avoided
1 (e.g. by definition of deadbands) especially around the neutral point of the split-range characteristic,
because this means alternating of heating and cooling. In the simulation, the oscillation is actually
centered around the neutral point because heat losses into the surroundings are neglected.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and containers to operation.
Neutralizing agent
YC
NeutSubst
QIC
pH_Control_Std
QI
pH_Tank
CM and variants
The "pH-Control-h" equipment module consists of three interconnected CMs and one simulation chart. In the simulation
chart, the system carries out pH setpoint specification (OpAnL block) and calculates the pH setpoint based on the
difference in concentration from the input substance and the neutralizing agent.
The controller gets the converted pH values (setpoint and actual values) as differences in concentration to control.
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
QIC_pH_Control_Std PIDCon • PV_Scale# Standard PID controller without channel blocks for
controlling the difference in concentration
YC_NeutrSubst VlvAn • IF_Ctrl# Control valve for the neutralizing agent
• MV_Scale#
• RbkReturn
• YC
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
pH_Std PV V
pHTitrConvert
Neutr_MV SimPV_In MV
CV
SP
pH_Std from_Ctrl
I
pH In
PV_Out to_Actor_Slave
Out
pH_SP to_Ctrl
SP_Out Out
from_Actor_Slave
In
"Sim_pH” simulation
In CFC "pH_Std" the system calculates the pH value. On sheet 2, there is an OpAnL block to specify the pH setpoint.
The following figure shows parameterization of the simulation block.
In the block inputs, fictional parameters are entered for buffer parameter "Alfa" and the "Ampl_pH" amplitude range that
is to be crossed. In addition, fixed values are specified for the pH value and flow amount of input material. No deadtime is
set for the pH simulation value (simulation process).
NOTE You can find additional information in Section 6.6 "Block description of "SimpHTitr"".
QI_pH_Tank
The pH value of the product in the tank is acquired and displayed in the instance. The instance has the following
parameterization.
Block Connection Value Use
QIC_pH_Control_Std
In the instance, the system converts the pH value provided by display "QI_pH_Tank" to a concentration difference using
block "pHTitrBlock". The concentration difference is used for control. The instance has the following parameterization.
Block Connection Value Use
NOTE You must carry out parameterization of the titration curve for a concrete chemical process before
setting the PID controller using the PID tuner. If large variations in the inflow amount of the input
materials are to be expected, it is recommend to compensate the disturbance by means of linear
manipulated variable conversion using the "pHTitrBlock" block. You can find additional information
about converting the pH value into a concentration difference in the block description in Section 6.5.
NOTE The "PID Tuner" program is available for commissioning controller "QIC_pH_Control_Std". The system
first records data for the "PID-Tuner" in an operating range in which only positive manipulated
variables occur. After this, a comparable experiment is made in an operating range in which only
negative manipulated variables occur. Optimization of the pH value-control was carried out based on
the concentration difference using different manipulated variables (MV) with a constant (input
material) inflow amount.
NOTE The following messages of the measurement "QI_pH_Tank" are not displayed in the controller:
YC_NeutrSubst
The instance has the following parameterization.
Block Connection Value Use
NOTE The controller uses the preset pH value of the OpAnL symbol display as the setpoint. In this symbol
display, 7 pH is set as the setpoint (neutral zone) based on which the amount of neutralizing agent is
fed (regulated).
4. Wait for about 2 minutes until the process value reaches its specified operating range.
5. Switch to operator control block "pH_SP" and specify a new setpoint of 6.5 pH.
6. Close the faceplate and observe the plotter for about one minute until the new setpoint has been reached.
Evaluation
The controller is optimized without overshooting to reach the setpoint. After changing the setpoint, the controller
regulates the addition of neutralizer with a slight delay.
NOTE The controller is set for an operating point of ± 0.5 pH around the neutral zone 7 pH. Under some
circumstances, different operating points may make it necessary to optimize the controller again.
P&I Diagram
The P&ID below symbolically represents all of the components, such as units and containers, etc. relevant to operation.
Neutralizing agent
CV
QIC MV YC
DV
pH_Control_MPC Neutralizer
QI FI
pH_Feed Feed
QI
pH_Product
Inflow
Outlet
CM and variants
The "pH-Control-MPC" equipment module consists of five interconnected CMs and one simulation chart. In the simulation
chart, the pH value of the product is determined from the pH value and the inflow amount of the input material and of
the neutralizer (manipulated variable of the valve).
Operators can adapt in the OS the pH value for the input material and the pH setpoint as well as the inflow amount. For
this, OpAnL blocks have been inserted in the simulation chart and the controller process tag.
For regulation, the controller uses the converted pH values (setpoint and actual values of the product and actual value of
the input material) as concentration differences. In addition, the inflow amount of the input material affects the inflow
amount of the neutralizer, since the maximum manipulated variable changes proportionally to the factor from the actual
inflow amount and the maximum inflow amount of the input material.
NOTE Additional information about calculating the manipulated variable or scaling in the block description
can be found in Section 6.5.
You specify the values below in the OpAnL blocks and can adjust them in the Operator Station:
• pH setpoint (product)
• pH value of the input material
• inflow amount of the input material
To simplify the project, an additional display process tag was not implemented for each value specification.
PV
PV_Out IF_SFC
ScaleOut SP1
pH_SP
SP_Out
Multivariable controller "QIC_pH_Control_MPC" acquires the pH value of the input material, the pH value of the draining
product, and the pH setpoint specification as concentration differences. Depending on the pH difference (setpoint and
actual value of the product), the system feeds the necessary amount of neutralizer to the tank via control valve
"YC_Neutralizer".
Simulation "Sim_pH_MPC"
In CFC "Sim_pH_MPC" the system calculates the pH value. On sheet 2, there is an OpAnL block to specify the pH setpoint,
the pH value, and the inflow amount of the input material.
The following figure shows parameterization of the simulation block.
In the block inputs, fictional parameters are entered for buffer parameter "Alfa" and the "Ampl_pH" amplitude range that
is to be crossed. In addition, the manipulated variable of control valve "YC_Neutralizer" and the inflow amount of the
input material (OpAnL block on sheet 2) are used for the calculation.
A deadtime of 10 seconds, a neutralizer inflow delay of 10 seconds, and a gain factor of 3 are set for the pH simulation
value (simulation process).
NOTE You can find additional information in the block description in Section 6.5.
QI_pH_Product
The pH value of the product is acquired and displayed in the instance. The instance has the following parameterization.
Block Connection Value Use
QI_pH_Feed
The pH value of the input material is acquired and displayed in the instance.
The instance has the following parameterization.
Block Connection Value Use
FI_Feed
The amount of the input material is acquired and displayed in the instance.
The instance has the following parameterization.
QIC_pH_Control_MPC
In the multivariable controller, the system converts the pH value provided by display "QI_pH_Product" to a concentration
difference using block "pHTitrBlock". The concentration difference is used for control. In the same way, the system
converts the setpoint specification as well as the pH value of the input material disturbance variable to a concentration
difference.
The instance has the following changes and parameterization.
Block Connection Value Use
MPC SP1HiLim 500 Upper setpoint limit for the concentration difference
MPC SP1LoLim -500 Lower setpoint limit for the concentration difference
NOTE The multivariable controller was optimized using the MPC configurator for an operating range from
7.5 to 6.5 pH and stored in DB 50. The relevant influencing variables were an inflow amount of the
input material of 3000 L/s with pH 4 and a neutralizing agent with a pH of 12.
For trend recording, the manipulated variable was excited using the "AutoExci" block and the
disturbance variable was changed (±10 %).
YC_Neutralizer
The instance has the following parameterization.
Block Connection Value Use
NOTE The controller uses the preset pH value of the OpAnL symbol display as the setpoint. In this symbol
display, 7 pH is set as the setpoint (neutral zone) based on which the amount of neutralizing agent is
fed (regulated).
4. Wait for about 1 minute until the process value reaches its specified operating range.
5. Switch to operator control block "pH_Feed" and specify a new setpoint of 4.5 pH.
6. Close the faceplate and observe the plotter for about one minute until the new setpoint has been reached.
1
2
1. The controller is optimized to reach the setpoint exactly and consequently, slowly. The controller detects the change
in the disturbance variable and it modifies the manipulated variable before the process responds to influencing of the
disturbance variable (set deadtime in the simulation block). The disturbance variable acts on the actual value without
delay (time delay elements).
2. In the example, the pH value of the input material was increased by 0.5 pH; however, it had an effect of about 1 pH
on the product.
Despite detecting the disturbance variable in good time, the controller needs about 90 seconds for compensation and
regulation. This time is also needed for control with bigger changes in the pH value of the input material.
5.7. "Temperature-Flow-Cascade"
Temperature control via flow controller for a service medium (e.g. heating steam, cooling water, or fuel) in cascade
structure is used for applications in which fluctuations within the auxiliary control loop (of the flow controller) have to be
compensated quickly, or the slave controller can compensate other unpleasant properties of the actuator (e.g. a non-
linear valve characteristic curve) which are therefore invisible for the master controller. Temperature flow cascades are
used for heat exchangers, reactors or burners, for example.
In the heat exchanger, the system continuously pumps the contents of the container through the heat exchanger via
piping. This heats up or cools the product material to a defined temperature by means of thermal transfer from the
service medium.
The same control concept is used with a burner, i.e. the amount of fuel flow regulates the temperature.
NOTE The "temperature flow cascade" equipment module can be used for any process applications where
temperature control is carried out via flow.
In the following example, we will consider temperature control on a heat exchanger that is heated by means of a heating
medium. It is also possible to use heat exchangers to cool a material flow. In this case, the flow of cooling medium is
manipulated instead of heating medium. The usual generic term for a heating or cooling medium is "service medium”.
The controller structure of heat exchangers does not depend on whether they are used for heating or cooling. The only
change is the sign of the master controller's controlled system.
P&I Diagram
The P&ID below symbolically represents all of the components, such as units and containers, etc. relevant to operation.
TIC
Temperature
FIC YC
ServMedium ServMedium
Inflow
Service medium
Outflow
Service medium
Inflow
Product
CM and variants
The "temperature flow cascade" equipment module consists of three interconnected CMs and one simulation chart. The
simulation chart simulates the effect of the heat exchanger on the input material temperature.
The following table provides an overview of the CMs of the equipment module including the associated CMTs.
CM CMT Selected variants Description
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
TIC_Temperature
PV
SimPV_In
to_Actor_Slave
Out
from_Actor_Slave
In
Sim_Temperature FIC_ServMedium
YC_ServMedium
to_Master
Lag_Heat_Slave
Out V
In
MV
from_Master
Noise_Master
In from_Ctrl
Out
In
PV
Gain_Slave
SimPV_In to_Ctrl
Out
Out
to_Actor_Slave
Out
from_Actor_Slave
In
"Sim_Temperature" simulation
In CFC "Sim_Temperature", the system simulates a temperature change of a material by a heat exchanger. The figure
below shows the sequence of the simulation.
2 4
5
3
1. If a valve is 100 % open, with a 3-second delay, a flow of 5 t/h (factor 0.05) is sent to the slave controller as the flow
rate actual value.
2. With a 10-second delay (as a simulation for heating up of the thermal capacity of the heat exchanger), ten times the
value of the heating steam flow rate is sent to the reference junction as the actual value of the hot air temperature.
3. Alternating input material temperature that changes every 90 seconds between 20 °C and 21 °C to simulate a
disturbance.
4. Input material temperature for the master controller that changes in dependence on the heat exchanger. The output
signal can be given slight signal noise.
5. Material temperature before being heated by the heat exchanger.
NOTE Simulation behavior does not correspond to a real process and it is only used to demonstrate the
functionality and mode of operation of the "temperature flow cascade" equipment module.
TIC_Temperature
The instance has the following parameterization.
Block Connection Value Use
FIC_ServMedium
The instance has the following parameterization.
Block Connection Value Use
PV_Unit In 1328 Unit of the process value in t/h (tons per hour)
NOTE The "PID Tuner" program is available for commissioning the controller. Please remind that you optimize
the slave controller (service medium flow) first, and then the master temperature controller.
YC_ServMedium
The instance has the following parameterization.
Block Connection Value Use
Evaluation
TIC_Temp TIC_Serv
1. The temperature of the product medium changes every 90 seconds. The master controller responds to this change
and regulates towards the temperature setpoint of 21 °C.
2. On detecting a temperature change, the master controller transfers a new setpoint to the slave controller. The slave
controller responds directly to this change with a new setpoint (brown trend display) and tracks the process value
(gray trend display) to the setpoint (orange trend display).
The slave controller (flow of the heating medium in t/h) is configured for exact control without overshooting.
• Quality control in chemical processes, such as pH control with flow control of the neutralizing agent.
• Temperature controls on distillation towers or reactors with flow control of the heating/cooling medium.
• Provision of auxiliary energy (heating steam, compressed air) for process plants, e.g. with a large and a small steam
generator or a large and a small compressor.
The fine flow controller uses the overall flow as controlled variable. The coarse flow controller uses as its controlled
variable the position of the control valve for the fine flow, with a setpoint of 50 % and a relatively broad deadband. The
aim of the coarse flow controller is to roughly adjust the main mass flow so that the fine flow controller remains in the
middle of its working range and can perform the fine regulation.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and pipes. relevant to operation.
YC
FineStream
Fine inflow
FIC
TotalStream
FIC
CoarseStream
YC
CoarseStream
Coarse inflow
CM and variants
The "Stream Control" equipment module consists of four connected CMs and one simulation chart. On the simulation
chart, the system forms the total from the two inflows (fine and coarse inflow).
The following table provides an overview of the CMs of the equipment module, including the associated CMTs.
CM CMT Selected variants Description
PV V
Scale_FineStream
SimPV_In MV
In1
FIC_CoarseStream YC_CoarseStream
C V
PV MV
to_Actor_Slave from_Ctrl
Out In
from_Actor_Slave to_Ctrl
In Out
Control "FIC_TotalStream" acquires the flow of the total stream and regulates the fine stream with control valve
"YC_FineStream".
The "FIC_CoarseStream" controller acquires the manipulated value of the "YC_FineStream" control valve and regulates the
coarse flow with the "YC_CoarseStream" control valve. The setpoint for the "FIC_CoarseStream" controller is 50%. With it
the "FIC_CoarseStream" controller works to keep the "YC_FineStream" control valve in the optimum working range of
50%.
"Sim_Stream" simulation
The flow of both the fine stream and the coarse stream are simulated in the "Sim_Stream" CFC and the overall flow rate is
calculated as well. Apart from this, the system displays the total flow rate based on process tag type "MonAn".
1 2 6
3 4
1. Calculation of the flow for the fine stream (valve 100 % open corresponds to inflow of 200 l/h)
2. Delay in change of flow (PT1 response with 8-second delay)
3. Calculation of the flow for the coarse stream (valve 100 % open corresponds to inflow of 2000 l/h)
4. Delay in change of flow (PT1 response with 24-second delay)
5. Determination of the complete flow quantity (addition)
6. Creation of measurement noise
PV_Unit In 1353 Unit of the process value l/h (liters per hour)
FIC_CoarseStream
The instance has the following parameterization.
Block Connection Value Use
YC_CoarseStream
The instance has the following parameterization.
Block Connection Value Use
NOTE The controller uses the preset setpoint "50" % as external setpoint to keep the valve "YC_FineStream" in
the middle of the working range.
7. Then wait about 1 minute until both controllers have reached their setpoints and change the main controller setpoint
to "1200 l/h”.
8. Wait for about 30 seconds and then click on the "Start/Stop" icon on the toolbar of the OnlineTrendControl.
The setpoint step from 800 l/h to 1200 l/h opens the valve for the fine stream completely. The coarse stream controller
registers the change of the fine stream control valve and regulates the coarse stream valve accordingly. This leads to a
significant change of the total flow so that the controller for the total flow closes the fine stream valve again until the
total flow has reached the new setpoint value.
NOTE Typical a large disturbance moves the overall flow away from its setpoint. The fine stream controller is
supposed to react quickly and compensate the disturbance, but will reach one of its manipulated
variable limits. The coarse flow controller slowly adapts to the situation and allows the fine stream
controller to return to the center of its manipulated variable range.
Overview
Below, the structure in the P&ID is shown and all CMs and the simulation of the equipment module are described. The
structure is described in general for all methods. The modifications of the respective method are explained in the
corresponding subchapter.
P&I Diagram
The P&ID below symbolically represents all of the components, such as field devices and containers relevant to operation.
FIC YC
GradLimit GradLimit
Feed
CM and variants
The technical function "GradientLimit" consists of two interconnected CMs and a simulation plan. The behavior of the
controlled system is simulated in the simulation plan.
The following table provides an overview of the CMs of the equipment module, including the associated CMTs.
CM CMT Variant Description
In the figure below, the structure with the cross-chart interconnections is shown in simplified form.
PV_In V
ValveGradSim
SimPV_In MV
In
from_Actor_Slave to_Ctrl
In Out
The "FIC_GradLimit" controller detects the flow and controls it using the "YC_GradLimit" control valve. In the CFC chart
"SimGradLimit", the flow rate is calculated from the control value for the valve and the gradient limitation.
Simulation "Sim_GradLimit"
The CFC "Sim_GradLimit" simulates the gradient limitation of the control valve and the flow rate.
2 3
1. Calculation of the valve feedback (valve position in the range 0...100 % and a maximum travel speed of 3 %/s in both
directions)
2. Calculation of the flow rate (100 % valve opening corresponds to an inlet of 2000 l/h)
3. Flow change delay (PT2 behavior with 15 seconds and 2 seconds delay)
4. Visualization of the position feedback in the WinCC Runtime
CFC "Method_GradLimit"
In the CFC "Method_GradLimit" the different methods for considering the gradient limitation of the actuator are selected
and activated.
The respective methods are activated in sub-sheets 1 to 4, the description of the individual methods can be found in the
following sub-sheets. The methods are selected in Subsheet 6.
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 96
Equipment Modules
1 2 3
FIC_GradLimit
The instance has the following parameterization.
Block Connection Value Use
PV_Unit In 1353 Unit of the process value l/h (liters per hour)
YC_GradLimit
The instance has the following parameterization.
Block Connection Value Use
During the positive setpoint step, a significant difference between the manipulated variable for the valve and the actual
valve position (position readback signal, green) is visible. The actual valve position cannot follow the commands of the
controller (red) fast enough due to the gradient limitation. Since the difference between the manipulated variable for the
valve and the actual valve position is not known to the controller, an overshoot of more than 30 % of the step height
occurs, which would not be acceptable in many applications.
Setup
Instead of the PIDConL controller, method 1 "External Reset" uses the PIDConR controller from the
NOTE
Advanced Process Library.
With the "External reset" method activated, a significantly better control response is achieved for the same setpoint step,
the overshoot is significantly smaller, and the settling time is also shorter.
Setup
Three additional blocks ("Sub02", "AbsR" and "CopmAn02") from the Advanced Process Library are required for the method
"Adjust control value if deviation is too large".
The following parameterization is required:
Block Connection Value Use
C MV_Trk Circuit for position feedback of Tracking value for manipulated variable MV
the valve
After the difference between the manipulated variable and the position feedback signal exceeds the parameterized limit
value, the controller output (red) is set to the position feedback signal (green). This limits the manipulated variable curve
and completely avoids overshoot. The method is not effective for smaller setpoint steps because the difference between
the controller output and the position feedback signal does not exceed the limit value.
Evaluation
With the "Blocking integrator" method activated, the integrator windup can be suppressed such that the overshoot is
reduced during the setpoint step. The lower part of the trend shows when the gradient limitation is active.
Direction-dependent blocking has the advantage that it works independently of the step height, such that tracking
behavior is less slowed down, and no parameterization is required. However, the binary signals required for this are only
available for a few installations in the distributed control system.
One example is an electro-pneumatic valve positioner, which often operates internally as a 5-point positioner. The so-
called slow gear zone, in which an approximately proportional control behavior is visible, covers only 1...10 % of the valve
position range. As soon as the control deviation leaves this range, the positioner opens the maximum air supply to the
valve actuator, i.e. it operates at its manipulated variable limit. This happens frequently during operation with large
setpoint steps. The corresponding binary signals are usually only available for internal use within the field device and are
not made available to the outside world via a communication interface.
Setup
For the "Blocking integrator with gradient calculation" method, three additional blocks ("Derivative" and twice
"CopmAn02") from the Advanced Process Library are required.
The following parameterization is required:
Evaluation
With the activated method "Blocking integrator with gradient calculation", the integrator windup can also be suppressed
such that the overshoot is reduced during the setpoint step. Due to the delay caused by the low-pass filter, the effect of
the method is not quite as good as if the original binary signals are available.
Tracking output value in Analog position feedback Switching threshold for Proportional step is
case of excessive deviation maximum deviation truncated, tracking
e.g. 25 %. behavior is slowed down,
slow settling times
Integrator blocking with Controller block PIDConL maximum travel gradient Avoids windup in case of
gradient calculation Analog position feedback active gradient limitation,
Low pass filtering with
from actuator reduces overshoots
meaningful time constant
The "External Reset" method has the advantage that it can be used for controllers with incremental algorithms without
further parameterization and without special requirements on the feedback signals from the final control element.
The method "Tracking the output value in case of excessive deviation" has the widest range of application. It does not
require a special control algorithm, binary feedback signals or high signal quality of the analog feedback signal. Only
application-specific limit values must be parameterized. The method slows down the tracking behavior for large setpoint
steps and remains completely ineffective for small setpoint steps.
The "Blocking integrator" method achieves the highest overall control performance for setpoint steps of different heights,
but requires binary feedback signals from the actuator when its internal manipulated variable signal limitation is active.
The "Blocking Integrator with gradient calculation" method allows the use of directional integrator blocking with reduced
precision even when there are no binary feedback signals from the actuator. For this the maximum actuator gradient and
a meaningful filter time constant must be determined.
NOTE No alarm, warning or tolerance limits are pre-parameterized in the equipment modules. If you
parameterize a limit value, you must also activate the corresponding notification.
For example, parameter "PV_AH_En" for upper alarm limit "PV_AH_Lim".
NOTE Interconnection of the process variables depends on the selected variant of a CM. In the configuration
below, the control, process, and manipulated variables are acquired via the "Pcs7AnIn" and "Pcs7AnOu"
analog channel blocks.
The tables below contain the relevant parameters that you must either set or interconnect.
Controller
Block Connection Use
PV_Scale HiScale Scaling of the measured value (e.g. maximum container fill level of 10000)
LoScale
PV_Unit IN Unit of the scaled measured value (e.g. 1038 fill level in liters)
Display
Block Connection Use
PV_Scale HiScale Scaling of the measured value (e.g. maximum container fill level of 10000)
LoScale
PV_Unit IN Unit of the scaled measured value (e.g. 1038 fill level in liters)
Valve
Block Connection Use
MV_Scale HiScale Scaling of the manipulated variable (manipulated value of the valve block)
LoScale
NOTE In the object properties of the message-type blocks, you can configure instance-specific messages. You
can find a guide to the procedure in the "SIMATIC PCS 7 Process Control System; Operator Station
(V9.1)" configuration manual under https://support.industry.siemens.com/cs/ww/de/view/109794374.
6. Additional information
6.1. General Information
Automation technology
Industrial processes in the chemicals or pharmaceuticals sectors, for example, are controlled and regulated using
automation technology.
The degree of automation of systems varies considerably and depends on the system type and the process.
In general, an automation solution includes the following aspects:
Process control
The operator’s main task is to carry out operative process control based on process and plant information with respect to
production process and its logistics and auxiliary processes.
The task of process control is to guarantee that operating conditions are are kept in, compliance with defined tolerance
ranges for process safety and product quality, in a selective and reproducible way. In case of disturbances, the process has
to be driven back to the desired operating state. In addition, the production sequence should be continuously optimized
regarding costs, quality, and safety.
Using SIMATIC PCS 7 Advanced Process Graphics (APG), it is possible to make process visualization more efficient for
operators. When doing this, the system shows the information in the plant overview that is relevant for orientation and
navigation. The information that is necessary for operator control and monitoring of a plant unit, e.g. a reactor, is made
available in a lower-level process picture. This procedure provides the great advantage of dispensing information in a task-
oriented way that is optimized for process operation.
NOTE You can find detailed information and the procedure for configuring APG in the Siemens Industry
Online Support in the entry entitled "Integration of Advanced Process Graphics in SIMATIC PCS 7"
under https://support.industry.siemens.com/cs/ww/en/view/89332241.
Unit
The term plant unit represents an apparatus (device) in process plants (e.g. stirred tank reactor, fermenter) which
includes sensor technology, actuators and automation (hardware and software).
There are structured units for both continuous and discontinuous processes.
Package units are variants of a plant units. Examples of package units include refrigeration systems, vacuum systems and
packaging machines. In this case, the manufacturer of the mechanical or technical device includes automation
technology, specially tailored for this device, which is mounted locally on the device on a separate hardware platform.
The package unit is integrated as a whole into a higher-level process control system.
Equipment module
An equipment module forms part of a unit and contains sensors, actuators and the automation system (hardware and
software). Equipment modules are designed and configured for use in concrete applications, such as process technology
(dosing device, level or temperature control).
The automation solution of an equipment module is structured as follows:
Control module
Actuators and sensors are used at the control module level as control modules.
In PCS 7, the control module is implemented with software typicals
(control module types) such as a valve, motor, or controller, for example.
The implementation in the CFC contains all the relevant building blocks, interconnections, and basic parameters. A
control module type is produced from the CFC, which is then stored in the PCS 7 master data library. You can create as
many instances as you like from this control module type using the Automation Interface, for example. There can be
major differences between the instances, e.g. you can select options for functions as well as for the process link.
Each designation of a control module follows a uniform naming convention. This means that the name provides
information about the function and the job of the control module.
The table below contains all the letters that are used in the Application Example and their meanings:
F Flow
J Power
L Level
M Moisture
N Motor
P Pressure
S Speed
T Temperature
W Weight
Y Control valve
A Alarming/Messages
C Control
F Fraction
I Indication
R Recording/Storage
H High
L Low
EquipmentModules OS Project
PDL
Overview picture
EquipmentModule 1
PDL
EquipmentModule 1
EquipmentModule 2
PDL
EquipmentModule 2
EquipmentModules AS Project
EquipmentModule 1
EquipmentModule 2
User program Simulation
Master controller
Slave controller
Control valve
No. Master controller Slave controller Control valve Control valve Comment
master controller slave controller
When using a split-range rule structure, it is not ensured that bumpless return to normal operation is
NOTE
possible.
Master controller
Slave controller
Control valve 1
Control valve 2
No. Master controller Slave controller Control valve1 Control valve2 Comment
Master controller
Slave controller
Control valve
Control or manipulated variable CSF puts the controller into No change in operating mode. The
specification is not possible since the disturbance status (external error). manipulated variable of the slave
CSF with the slave controller is forced Controller switches to manual mode. controller still matches the
The manipulated variable for the manipulated variable, MV.
control valve can be changed
NOTE As soon as the CSF on the slave controller is no longer active, it can be switched back to the original
operating status (automatic/external).
Slave controller
Control valve
CSF puts the controller into The slave controller continues to The control valve continues to receive
disturbance status (external error). receive the MV from the master the MV from the slave controller
The manipulated variable (MV) can controller
be changed.
NOTE As soon as the CSF on the master controller is no longer active, it can be switched back to the original
operating status (automatic/external).
Slave controller
Control valve
The controller receives the MV in the The controller receives the MV in the CSF puts the valve into disturbance
case of a manual change on the case of a manual change on the status (external error)
control valve control valve The manipulated variable (MV) can
be changed (manual)
NOTE As soon as the CSF on the control valve is no longer active, it can be switched back to the original
operating status (automatic/external).
Slave controller
Control valve
The controller maintains the old MV The controller cannot be operated The control valve retains the old
until normal operation is re- due to maintenance. value while there is no new MV from
established or the operator specifies a The user can switch to manual the slave controller
different MV on the slave controller mode and specify the MV for the
manually. control valve.
NOTE As soon as the maintenance status is no longer active, the slave controller can be switched back to the
original operating status (automatic/external).
Slave controller
Control valve
The controller cannot be operated The controller retains the old value The control valve retains the old
due to maintenance. while there is no new MV from the value while there is no new MV from
The user can switch to manual mode master controller. the slave controller.
and specify the MV for the slave
controller.
NOTE As soon as the maintenance status is no longer active, the master controller can be switched back to
the original operating status (automatic/external).
Slave controller
Control valve
Normal operation is possible Normal operation is possible Normal operation is still possible.
The maintenance status is
displayed.
NOTE In the chapter below, we will not consider the second slave controller with control valve, since the
behavior matches that of the first slave controller with control valve.
Slave controller 1
Control valve
Slave controller 1
Slave controller 2
Control valve
Slave controller 2
Master controller Control valve master Slave controller 1 Control valve slave
controller controller 1
The controller functions The control valve functions CSF puts the controller The control valve retains
without limitations. without limitations. into malfunction status. the old MV until the slave
The MV can be changed. controller specifies a new
value.
NOTE As soon as the CSF on the slave controller is no longer active, it can be switched back to the original
operating status (automatic/external).
Slave controller 1
Control valve
Slave controller 1
Slave controller 2
Control valve
Slave controller 2
Master controller Control valve master Slave controller 1 Control valve slave
controller controller 1
CSF puts the controller into The control valve functions The controller functions The control valve functions
malfunction status. without limitations. without limitations. without limitations.
The manipulated variable
can be changed.
NOTE As soon as the CSF on the master controller is no longer active, the master controller is back in
operating condition
Slave controller 1
Control valve
Slave controller 1
The controller functions CSF puts the control valve The controller functions The valve functions
without limitations. of the master controller without limitations. without limitations.
into malfunction status.
The valve functions
without limitations.
NOTE As soon as the CSF on the master controller's control valve is no longer active, it is back in
Automatic/External mode.
The controller functions The valve functions The controller functions CSF puts the control valve
without limitations. without limitations. without limitations. of the slavce controller
into malfunction status.
The valve functions
without limitations.
NOTE As soon as the CSF on the slave controller's control valve is no longer active, it is back in
Automatic/External mode.
Führungsregler
Master controller Control
Stellventil
valve
Master
Führungsregler
controller
SlaveFolgeregler
controller 11 Stellventil
Control valve
Slave controller 11
Folgeregler
SlaveFolgeregler
controller 22 Control
Stellventil
valve
SlaveFolgeregler
controller 2
Master controller Control valve master Slave controller Control valve slave
controller controller
The controller functions The valve functions The controller cannot be The control valve retains
without limitations. without limitations. operated due to the old value until the slave
maintenance. controller specifies a new
The user can switch to MV.
manual mode and change
the MV.
NOTE As soon as the maintenance status is no longer active, the slave controller can be switched back to the
original operating status (automatic/external).
Slave controller 2
Control valve
Slave controller 2
The controller cannot be The control valve retains The controller functions The valve functions
operated due to the old value until the slave without limitations. without limitations.
maintenance. controller specifies a new
The user can switch to MV.
manual mode and change
the MV.
NOTE As soon as the maintenance status is no longer active, the master controller can be switched back to
the original operating status (automatic).
Control valve
Master controller
Master controller
Master controller Control valve master Slave controller Control valve slave
controller controller
The controller functions The valve displays the The controller functions The valve functions
without limitations. maintenance status and without limitations. without limitations.
functions without
limitations.
Control valve
Master controller
Master controller
Master controller Control valve master Slave controller Control valve slave
controller controller
The controller functions The valve functions The controller functions The valve displays the
without limitations. without limitations. without limitations. maintenance status and
functions without
limitations.
Master controller
Slave controller
Control valve 1
Control valve 2
The controller functions CSF puts the controller The valve functions The valve functions
without limitations. into malfunction status. without limitations. without limitations.
The MV can be changed.
NOTE As soon as the CSF on the slave controller is no longer active, it can be switched back to the original
operating status (automatic/external).
Control valve 2
CSF puts the controller into The controller retains the The valve functions The valve functions
malfunction status. last manipulated variable without limitations. without limitations.
The MV can be changed. that was present until the
master controller specifies
a new value.
NOTE As soon as the CSF on the master controller is no longer active, it can be switched back to the original
operating status (automatic).
Master controller
Control valve 2
The controller functions The controller functions CSF puts the valve into The valve functions
without limitations. without limitations. malfunction status. without limitations.
Operation and the MV
can be changed.
Control valve
2
The controller functions The controller functions The valve functions CSF puts the valve into
without limitations. without limitations. without limitations. malfunction status.
The operating mode and
the MV can be changed.
Slave controller
Control valve 1
Control valve 2
The controller cannot affect The controller cannot be The valve functions The valve functions
the process while the slave operated due to without limitations. without limitations.
controller is being maintenance.
maintained. The user can switch to
manual mode and specify
the MV for the control
valve.
NOTE As soon as the maintenance status is no longer active, the slave controller can be switched back to the
original operating status (automatic/external).
Control valve 2
The controller cannot be The controller retains the The valve functions The valve functions
operated due to old value while there is no without limitations. without limitations.
maintenance. new MV from the master
The user can switch to controller.
manual mode and specify
the MV.
NOTE As soon as the maintenance status is no longer active, the master controller can be switched back to
the original operating status (automatic).
Control valve 2
The controller functions The controller functions The valve displays the The valve functions
without limitations. without limitations. maintenance status and without limitations.
functions without
limitations.
Slave controller
Control valve 1
Control valve 2
The controller functions The controller functions The valve functions The valve displays the
without limitations. without limitations. without limitations. maintenance status and
functions without
limitations.
For the equipment modules for pH value control, you use the trigonometric function below as an approximation of the
titration curve for conversion:
2𝑝𝐻𝑎𝑚𝑝𝑙 ∆𝑐
𝑝𝐻 = 7 + ∙ arctan (𝛼 ∙ 6 )
𝜋 10
This characteristic curve is inverted to convert pH values to concentration differences.
1 𝜋
∆𝑐 = ∙ tan ( ∙ (𝑝𝐻 − 7)) ∙ 106
𝛼 2𝑝𝐻𝑎𝑚𝑝𝑙
NOTE Conversion is carried out in the two blocks below that are a component of the "pHTitrBlock" and are
included in the master data library:
• FB1025 "Titr_pH" for converting the concentration difference to the →pH value
• FB1026 "TitrDeltaC" for converting the pH value to the →concentration difference
pH
12
11 alpha=3500
alpha=12000
10
2
-1 -0.8 -0.6 -0.4 -0.2 0 0.2 0.4 0.6 0.8 1
delta c 4
x 10
In the titration curve illustration, the neutral zone is at 7 pH with the maximum excursion (amplitude) of 5. Typical values
of between 3500 and 12000 are present for the steepness of the characteristic curve in the neutral point (parameter α).
Entry ID: 53843373 V5.2 09/2023 © Siemens 2023 131
Additional information
NOTICE Use in a productive environment is conditional upon knowing the titration curve that must be
entered in the block.
The parameters include:
Inputs
Input Data type Description
SP STRUCT pH setpoint (specified by OpAnL operator control block oper SFC, for
->Real example)
->Byte
Alpha STRUCT Measure of the steepness of the characteristic curve in the neutral point
->Real
->Byte
Conversion of the concentration differences for inputs "CV", "DV", and "SP" is carried out based on parameters "Alpha" and
"Ampl_pH".
Outputs
Output Data type Description
MVHiLim STRUCT Variable upper limit value of manipulated variable MV depending on the feed
->Real amount of input material
->Byte (MVHiLim = 100/Feed_PV_Out/Feed_Scale.Max)
MV_Valve STRUCT Variable manipulated variable (to the valve process tag) depending on the
->Real feed amount of input material
->Byte (MV_Valve = Feed_PV_Out/Feed_Scale.Max * MV)
Interconnection of the inputs and outputs of the manipulated variables/disturbance variables ("MV", "Feed_PV_Out",
"Feed_Scale", "MVHiLim", "MV_Valve") is carried out if it is intended to compensate the feed amount as a disturbance
variable.
NOTE The output variable of the controller (what you can think of as a "concentration") is multiplied by the
(standardized) feed amount of the waste water (input material) to calculate a measure of the required
amount of neutralizer. If manipulated variable limitation in the controller itself were to be constant,
this would result in it only being possible to use the dosing valve for complete control at maximum
waste water flow through. One remedy is to interconnect MV1HiLim dynamically in dependence on
the feed amount.
Inputs
Input Data type Description
Alpha STRUCT Measure of the steepness of the characteristic curve in the neutral point
->Real
->Byte
NOTICE When using the deadtime (pH_DeadTime > 0), you must use a multi-variable controller
(ModPreCon block) for compensation and feedforward injection of disturbance variable.
Outputs
Output Data type Description
To calculate the pH value, you carry out the following calculation steps:
1. Determine the products (multiplication) from the concentration differences and inflow amounts of the input material
and the neutralizer
2. Determine the overall inflow amount
3. Calculate the factor (proportional concentration difference) from the products and the overall inflow amount
4. Convert the concentration difference to the pH actual value
In the simulation, you can adapt both the process-specific characteristics of the titration curve and the effect of the values
of feedforward injection of disturbance variable (change the pH values of the input material by ± 1) and the variable
throughflow amounts (change the inflow amount by ±500 mol/L).
Inputs "ComStruIn"
Input Data type Description
ReStru1 bis STRUCT e.g. transmission von process-, parameter- or limit values
ReStru6 ->Real
->Byte
Outputs "ComStruIn"
Output Data type Description
The ComStuOut block is the opposite to ComStruIn. It deconstructs the cross-chart interconnections input structure from
the signal source into the original individual variables, which can be used individually in the target process tags.
Inputs "ComStruOut"
Input Data type Description
Outputs "ComStruOut"
Output Data type Description
ReStru1 bis STRUCT e.g. transmission von process-, parameter- or limit values
ReStru6 ->Real
->Byte
7. Appendix
7.1. Service and support
SiePortal
The integrated platform for product selection, purchasing and support - and connection of Industry Mall and Online
support. The SiePortal home page replaces the previous home pages of the Industry Mall and the Online Support Portal
(SIOS) and combines them.
Technical Support
The Technical Support of Siemens Industry provides you fast and competent support regarding all technical queries with
numerous tailor-made offers – ranging from basic support to individual support contracts.
Please send queries to Technical Support via Web form: support.industry.siemens.com/cs/my/src