Ice Cream Demo DOC PCS7V91 SP2 En-1

Siemens
Industry
Online
Support
APPLICATION EXAMPLE
L PCS 7 Unit Template
PCS 7 Unit Template

“Ice Cream Production”
SIMATIC PCS 7 V9.1 SP2
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 produ cts. 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 t ype 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 prov isions
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 documentati on 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 versi ons 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.
Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 2

Table of contents
Table of contents
1. Introduction ...................................................................................................................................6
1.1. Overview ............................................................................................................................................................ 6

1.2. Mode of operation .............................................................................................................................................. 7
1.3. Components used ............................................................................................................................................... 9
2. Preperation and commissioning ....................................................................................................10
2.1. Preparation ....................................................................................................................................................... 10

2.2. Taks on the multiproject ................................................................................................................................... 13
2.3. Commissioning ................................................................................................................................................. 19
2.4. Operation of the Application Example .............................................................................................................. 22
2.4.1. Overview .......................................................................................................................................................... 22
2.4.2. Scenario A "Dosing Ingredients" ........................................................................................................................ 22
2.4.3. Scenario B "Pasteurization"................................................................................................................................ 24
2.4.4. Scenario C "Transport to the Freezer" ................................................................................................................ 25
3. Engineering .................................................................................................................................28
3.1. Overview of the plant units ............................................................................................................................... 28

3.2. Technical functions and process tags of the mixing system (mixing) ................................................................ 29
3.2.1. Dosing of cane sugar ........................................................................................................................................ 30
3.2.2. Dosing of whey powder .................................................................................................................................... 35
3.2.3. Dosing of cocoa ................................................................................................................................................ 40
3.2.4. Transfer out of the premixer ............................................................................................................................. 44
3.2.5. Dosing of water ................................................................................................................................................ 46
3.2.6. Dosing of milk ................................................................................................................................................... 54
3.2.7. Dosing of oil...................................................................................................................................................... 61
3.2.8. Dosing of the rework ........................................................................................................................................ 67
3.2.9. Transfer into the main mixer............................................................................................................................. 73
3.2.10. Transfer out of the main mixer ......................................................................................................................... 76
3.3. Technical functions and process tags of the buffer tank (Mix Buffer) ................................................................ 79
3.3.1. Agitator buffer tank 1 ....................................................................................................................................... 80
3.3.2. Transfer into buffer tank 1 ................................................................................................................................ 82
3.3.3. Transfer out of buffer tank 1 ............................................................................................................................. 85
3.3.4. Agitator buffer tank 2 ....................................................................................................................................... 88
3.3.5. Transfer into buffer tank 2 ................................................................................................................................ 90
3.3.6. Transfer out of buffer tank 2 ............................................................................................................................. 93
3.4. Technical function and process tags of the pasteurizer ..................................................................................... 96
3.5. Technical function and process tags of the storage tank (Mix Storage) ........................................................... 104
Table of contents
3.5.1. Filling of the storage tank ............................................................................................................................... 105

3.5.2. Emptying of the storage tank .......................................................................................................................... 110
3.5.3. Agitator buffer tank 1 ..................................................................................................................................... 115
3.5.4. Tank management storage tank 1................................................................................................................... 117
3.5.5. Agitator buffer tank 2 ..................................................................................................................................... 124
3.5.6. Tank management storage tank 2................................................................................................................... 127
3.6. Sequences....................................................................................................................................................... 133
3.6.1. EMP_WAY_CTR ................................................................................................................................................ 133
3.6.2. EQM_DOS_FLD................................................................................................................................................ 138
3.6.3. EQM_DOS_SLD................................................................................................................................................ 141
3.6.4. FIL_WAY_CTR .................................................................................................................................................. 144
3.6.5. PASTEUR ......................................................................................................................................................... 149
3.6.6. TANK_AGI ....................................................................................................................................................... 155
3.6.7. TANK_CTR ....................................................................................................................................................... 159
3.6.8. TRANS_IN ........................................................................................................................................................ 163
3.6.9. TRANS_OUT_BUF ............................................................................................................................................ 165
3.6.10. TRANS_OUT_MIX ............................................................................................................................................ 167
3.6.11. TRANS_OUT_PRE ............................................................................................................................................. 170
3.7. SIMATIC BATCH ............................................................................................................................................... 174
3.7.1. Production recipe "ICE CREAM MIX"................................................................................................................. 174
3.7.2. Transfer recipe "PASTEURIZING" ...................................................................................................................... 176
3.7.3. Transfer recipe "EMPTYING TO FREEZER" ......................................................................................................... 178
3.7.4. Batches ........................................................................................................................................................... 180
4. Useful information ..................................................................................................................... 181
4.1. Basics .............................................................................................................................................................. 181

4.1.1. Description of the individual functions............................................................................................................ 181
4.1.2. PI process flow diagrams ................................................................................................................................. 182
4.2. Process engineering ........................................................................................................................................ 185
4.3. Report function ............................................................................................................................................... 186
4.4. Extension by Clean in Place ............................................................................................................................. 188
4.5. Integrating the unit template in the user project ............................................................................................ 189
4.5.1. Preparation ..................................................................................................................................................... 189
4.5.2. Copying templates .......................................................................................................................................... 189
4.5.3. Copying units .................................................................................................................................................. 190
4.5.4. Adapting the OS project .................................................................................................................................. 191
4.6. Automation technology .................................................................................................................................. 192
4.7. Project structure.............................................................................................................................................. 193
4.7.1. CFC chart naming convention ......................................................................................................................... 193
4.7.2. Plant view ....................................................................................................................................................... 194
4.7.3. Abbreviations.................................................................................................................................................. 200

Table of contents
5. Appendix ................................................................................................................................... 201
5.1. Service and support ........................................................................................................................................ 201

5.2. Links and literature ......................................................................................................................................... 202
5.3. Change documentation .................................................................................................................................. 202

Introduction
1. Introduction
1.1. Overview
In the food and beverage industry many factors must be considered: The consistent high quality, maximum plant
availability, optimal resource efficiency – and ever more pronounced, the greatest possible flexibility, in order to fulfill
customer requests that are becoming ever more individual.
In facilities for the production of food or pharmaceutical products and their technical processes certain process steps,
procedures and devices are repeated in the same or similar form.
In this application example a process plant for the production of ice cream is described. The different varieties of ice
cream are produced in batches. This is why in addition to SIMATIC PCS 7, SIMATIC BATCH is also used.
This application example is modularly structured and can be extended with additional modules as needed, e.g. a Cleaning
In Place (CIP) module. An appropriate example is provided in the article "PCS 7 Unit Template CIP – Cleaning in Place" via
the following link:
https://support.industry.siemens.com/cs/ww/en/view/78463886
Description
In the "Ice Cream Plant" the ingredients required to produce the ice cream are dosed and mixed. First, the solid ingredients
are premixed in the "pre-mixer" before they are mixed in the "main mixer". To produce different ice cream varieties the
ingredients must be placed in the mixing system in different quantities. The necessary quantities of ingredients are dosed
automatically in the desired quantity. To obtain a fast and precise dosing result, dosing occurs in two stages. In the first
stage dosing runs with greater quantities into the tank. If the defined limit of course dosing is reached the remaining dose
with a significantly smaller quantity that flows into the tank will be continued until the dosing quantity is reached.
Before the product is further-processed the ice cream is transported into the "Mix Buffer" buffer tank. The second task is
pasteurization, in this process the product is heated in the pasteurizer for a preset period of time. After pasteurization the
finished product is forced out of the pasteurizer with water and transferred into a "Mix Storage" storage tank.
In the storage tank the ice cream is held until it is frozen in the "Freezer" as finished ice cream product and further
transported to the filling system. The valves required for filling and emptying of the storage tank are opened and the
pump is started.
Benefits
This application offers you the following benefits:
• Implementation of an ice cream plant with blocks from standard libraries

• Implementation of an ice cream plant in accordance with ISA S88.01
• Description of the most important automation functions for an ice cream plant
Required knowledge
Basic knowledge of the following technical areas is a prerequisite:
• Configuring with SIMATIC PCS 7, SIMATIC BATCH and the APL library
• Knowledge of control technology
• Basic knowledge of process technology

Introduction
1.2. Mode of operation

Process image
The figure below shows schematically the structure of the solution:
The "Ice Cream Plant" application example is implemented as a SIMATIC PCS 7 multiproject and consists of an AS project
(user program), and OS project (visualization with process images) as well as a SIMATIC batch plant (production recipes
and transfer recipes). The AS project was created with the APL library (Advanced Process Library) and SIMATIC BATCH
blocks.
Core functionality
The "Ice Cream Plant" application example includes the user program with typical process tags of an ice cream plant.
The plant view (PV) is structured according to ISA S88.01. The technical equipment necessary for the ice cream plant is
defined. A plant overview image, four plant section images, and a BATCH overview image are included for operation. The
plant overview image presents the status of the plant. In the individual plant section images all observation and control
functions for the plant section are presented. In addition the BATCH overview image offers the possibility of operating the
batch processes from a PCS 7 OS client. This is a template image that is available after installation of SIMATIC BATCH and
it contains all relevant SIMATIC BATCH OS Controls functions.

Introduction
The following illustration shows the BATCH overview image
A SIMATIC BATCH backup with multiple sample recipes is included for creation of the ice cream batches, these recipes are:
• Production recipes for production of ice cream with 50% chocolate content
• Production recipes for production of ice cream with 100% chocolate content
• Transfer recipes for pasteurization of the ice cream
• Transfer recipes of the finished ice cream to the freezer
The application example contains a simple simulation based on CFCs. The setpoints in the recipes are freely selected and
may differ from one plant to another. The equipment modules and measurement points are used as an exemplary
template and with plant-specific adaptations can be applied to a real production plant.
The ice cream recipes must be created for the available plant sections depending on the structure and product. The
sample recipe merely describes the basic structure.
NOTE The technical process within the ice cream plant is not simulated.

Introduction
1.3. Components used

This application example has been created with the following hard- and software components:
Component Number Article Number Note
SIMATIC PCS 7 ES/OS For the PCS 7 V9.1 SP2 example project
IPC547G W7
SIMATIC PCS 7 V9.1 SP2 Part of SIMATIC PCS 7 ES/OS IPC547G W7
S7-PLCSIM Not part of PCS 7; appropriate licenses are required.
Advanced Process Library Component of SIMATIC PCS 7 V9.1 SP2

(APL) Library V9.1
BCMs Library V9.1 https://support.industry.siemens.com/cs/us/en/view/109475748
Table 1-1
You can purchase these components from the Siemens Industry Mall.
This application example consists of the following components:
Component File name Note
PCS 7 V9.1 SP2 sample project 109755537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip

and SIMATIC BATCH backup
Documentation 109755537_Ice_Cream_Demo_DOC_de.pdf This document
Table 1-2

Preperation and commissioning
2. Preperation and
commissioning
2.1. Preparation
The following instructions describe how to launch the application example by emulating the controller with the "S7-
PLCSIM" program. If there is a real controller, you must configure existing hardware components in HW Config.
Preparation in Windows
The following instructions describe the steps that must be performed in Windows:
1. Click on "Start".
2. Right-click on "Computer" and open the menu item "Administrative Tools". "Computer Management" will be opened.
3. On the left side of the screen click on the menu item "Local Users and Groups > Groups". Select the menu item "New
Group" The "New Group" window opens.
4. In the "Group name" field enter "IceDemoUser".
5. Add the username with which you are currently logged in to Windows, to this group.
6. Click on "Create".
7. On the left side of the window, select the item "Local users and Groups > Users". On the right side, right-click the
username with which you are currently logged in. Select the "Properties" menu item. This opens the "Properties"
window.
8. Go to the "Member of" tab and check whether the user is a member of the following groups:
If the user is not included in all the groups, add him to the missing ones.
Preparing the project

1. Copy the file "109755537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip" and
"109755537_Ice_Cream_Demo_BATCHV91_SP2.sbb" to any folder on the configuration PC and then open SIMATIC
Manager.
2. In the menu bar click "File > Retrieve" and select the file "109755537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip".
Then confirm with "Open".

3. Select the folder in which the project will be saved and confirm with the "OK" button.
The project will be extracted.
4. In the "Retrieve" dialog, click the "OK" button and then click "Yes" in the dialog to open the project.
5. Right-click "UT_ICD_OS > SVES4ALL04" and click the "Object Properties" menu item.
6. Enter the name of your PC in the "Name" field and click "OK".
7. Right-click "UT_ICD_OS > Name of your PC > WinCC Appl > OS (1)" and click the "Open Object" menu command.
8. Confirm the "Configured server is not available" dialog with "OK".
9. In the WinCC Explorer, open the properties of your computer and, in the open Properties dialog, click the "Use local
computer name" button. Confirm the "Change computer name" message with "OK".
10. In WinCC Explorer, click on "File > Exit" and in the subsequent dialog select "Terminate WinCC Explorer and close
project". Confirm your selection with clicking on the "OK" button.
11. Reopen the WinCC Explorer as described in step 7.
12. Open by double-clicking the "OS project editor".
13. In the "Layout" tab under "Available Layouts", select the "SIMATIC Standard" screen corresponding to the screen
resolution that is set.
Click "OK" to apply the settings and close the "OS project editor".

14. Exit the WinCC Explorer as described in step 10.

15. Reopen the WinCC Explorer as described in step 7.
16. In the WinCC Explorer click Graphic Designer and open the screen "Reoprts.PDL"
17. Click the WinCCWebBrowser window, and under Properties specify the standard path for storing the BATCH reports.
NOTE The standard path for storing the BATCH reports is provided in "Options > Settings > Project Settings >
Report Creation > Default directory for PDF files"
18. Save the change and close the Graphic Designer.

19. Exit the WinCC Explorer as described in step 10.

2.2. Taks on the multiproject

The following instructions describe the tasks that must be performed on the multiproject. The prerequisites are that
SIMATIC Manager must already be open and the project must have been selected in the component view.
1. Right click on "UT_ICD_AS > AS1 > CPU 410-5H > S7 Program(1) > Plans" and click the menu command "Compile".
2. In the "Compile program" dialog, select the "Entire program" item and activate the "Generate module drivers" option
then confirm this dialog with "OK".
3. Close the compiler log.

4. Right click on "UT_ICD_AS > AS1 > CPU 410-5H > S7 Program(1) > Plans > PLC" and click the menu command
"Download".
5. In the "Download" dialog, select the "Entire program" item and confirm this dialog with "OK".
6. Right-click on "UT_ICD_OS > SVES4ALL04 (name of the PC station) > WinCC Appl > OS (1)" and click the menu item
"Compile". The compiler dialog opens.
7. Click "Next".
8. Ensure that all areas are selected and click on "Next".
9. Select the following settings and click "Next".

10. Click on "Compile".

11. Confirm the "Compile OS" dialog with "OK".
12. In SIMATIC Manager, right click the "UT_ICD_MP" multiproject and select the "SIMATIC BATCH > Open configuration
dialog" menu command. The SIMATIC BATCH configuration dialog opens.
13. Select the "UT_ICD_MP" multiproject and click on "Settings".
The "Settings" window opens.

14. In the "Distribution" tab, click "Update".

15. In the "OS objects" tab, click on "Update".
16. In the "Process cells" tab, click on "Update".

17. Click on "OK" to exit the "Settings" window.

18. Select the "BATCH types" item and click "Generate".
20. Click on "Close".
21. Select the "BATCH instances" item and click "Merge".


24. Select the "IC Production" item and click "Download".

27. Exit the SIMATIC BATCH configuration dialog with "OK".

28. Right-click on the multi-project "UT_ICD_MP" in the SIMATIC Manager and select the menu command "SIMATIC BATCH
> Compile/load...". The SIMATIC BATCH project engineering dialog is opened.
Click "OK".
29. In the windows task bar, right-click the icon for the SIMATIC BATCH Launch Coordinator and select the "Change start
mode from > Automatic to manual" menu command.

NOTE The SIMATIC BATCH Launch Coordinator starts automatically when the PC is started. If SIMATIC BATCH
Launch Coordinator does not start, proceed as follows:
Click on "Start > All programs > Siemens Automation > SIMATIC > BATCH Launch Coordinator".
NOTE In case you have reinstalled SIMATIC Batch you have to configure the security settings on the SIMATIC
BATCH server before.
For detailed information refer to the manual "SIMATIC Process Control System PCS 7 SIMATIC BATCH
V9.1 SP2" under chapter 4.8 "Configuring the security settings on the SIMATIC BATCH server":

2.3. Commissioning
The following instructions describe how the "Ice Cream Plant" application example is initialized.
For commissioning, SIMATIC Manager must already be open and the project must have been selected in the component
view.
Starting the simulation (S7-PLCSIM)

To start the simulation, proceed as follows:
1. Select "Options > Simulate Modules" from the menu.
The "S7-PLCSIM" dialog window opens.
2. Select the "Open PLC" option in the "File" dialog.
3. Select the file "ICECREAM.plc" from the path <project path>UT_ICD_MP\UT_I_MP\ICECREAM.plc>
4. Change "PLCSIM(MPI)" to "PLCSIM(TCP/IP)" in the drop-down list.
Activate OS (WinCC runtime)

To activate the OS, proceed according to the following instructions:
1. Right click "UT_ICD_OS > SVES4ALL04> WinCC Appl. > OS" and click the menu item ("Open Object").
2. Select "File > Activate" in the WinCC Explorer menu.
3. Log into the SIMATIC Logon Dialog using your Windows user ID.
4. Select "Mix Plant" in the image area
Activating SIMATIC BATCH

To activate SIMATIC BATCH, proceed according to the following instructions:
1. Press the Windows logo key on your keyboard to bring up the Windows task bar.
2. There is a green "Stop" symbol in the icon for the SIMATIC BATCH Launch Coordinator . The currently loaded
"UT_ICD_MP" project is displayed as a tooltip text.
3. Right-click the icon for the SIMATIC BATCH Launch Coordinator and select the "BATCH Runtime > Start" menu
command to start SIMATIC BATCH Runtime.

There will be an "hourglass" in the icon for the SIMATIC BATCH Launch Coordinator. This indicates that the SIMATIC
BATCH server is about to be started. The "hourglass" changes to a "Play" symbol . The SIMATIC BATCH server is now in
the "Run" state.
4. Click Start > All programs > Siemens Automation > SIMATIC > BATCH Control Center").
The BATCH Control Center opens.
5. Click "Options" menu item and select the "Restore" menu command.
The Restore dialog opens.

6. Navigate to the storage location of the "10955537_Ice_Cream_Demo_BATCHV91_SP2.sbb" file and select it.
7. Click on "Open".
8. Click on the "Options" menu item and select the "Role Management" menu command.
"SIMATIC Logon Role Management" opens.
9. In the "Configured roles and assignment types" window, right-click "Roles > Superuser > Groups and users". Select the
"Edit" menu command.

The "Edit groups and users" window will open.

10. Click on the "List" button.
All the available groups and users will be listed for you.
11. Remove the User that is present.
12. Add the group "IceDemoUser" to "Configured groups and users".
13. Click the "OK" button to exit the "Edit groups and users" window.
14. In the "SIMATIC Logon Role Management" window, click "File > Save".
15. In the "SIMATIC Logon Role Management" window, click "File > Exit".
16. Click on the left window click the "IC Production" process cell symbol and click the menu command "Update the
process cell".
17. Confirm the "Update the plant" dialog with "OK".

2.4. Operation of the Application Example

2.4.1. Overview
The following sections describe the operation of the application example. Three different scenarios will be described:
• Creating and starting a production batch from the SIMATIC BATCH Control Center for dosing the ingredients.
• Creating and starting a transfer batch from the SIMATIC BATCH Control Center to the pasteurizer.
• Creating and starting a transfer batch with the SIMATIC BATCH controls directly from WinCC Runtime to the freezer.
2.4.2. Scenario A "Dosing Ingredients"

A description of how to use these functions with SIMATIC BATCH and how to dose the ingredients is provided below.
Here, operation is carried out from the SIMATIC BATCH Control Center.
Requirement
The following points are prerequisites:
• WinCC Runtime is active

• The S7 program is loaded in "S7-PLCSIM" and the key switch is set to Run (-P)
• The SIMATIC BATCH server is in the "Run" state
• The supplied backup has been imported
• Role management has already been undertaken
Execution
1. Open the "Mix Plant" process image in WinCC Runtime
2. Click the "Key set change" button in the key area.
3. Klicken Sie im Tastenbereich auf die Schaltfläche "BATCH Control Center".
Das SIMATIC BATCH Control Center öffnet sich.

4. Rechtsklicken Sie auf "Aufträge" ("Orders") und wählen Sie den Menübefehl "Neu" ("New").
This opens the "Generate order category" window.

5. In the "Name" field, enter a suitable name (e.g. ICD).

6. Click on the "OK" button.
7. Right-click "ICD" and select the "New" menu command.
The "Create order" window opens.
8. In the "General" tab, enter a suitable name (e.g. MixDarkChoco) in the "Names" field and click on the "OK" button.
9. Right-click "MixDarkChoco" and select the "New" menu command. The "Add Batch(es)" window opens.
10. Click on the "New" button.
The "Selection of formula or master recipe" window opens.
11. Select the formula "Mix Dark Schoko 100% V01.00".
13. Give the batch in the "Add Batch(es)" window a suitable name.
14. Click on the "OK" button in the "Add Batch(es)" window.
15. Right-click the batch and select the "Release" menu command.
16. Confirm the dialog window that opens with "Yes".
You have now created and released a batch

17. Double-click the batch.
The control recipe will be displayed for you.
18. Right-click the batch and select the "Start" menu command.
The batch starts. SIMATIC BATCH now reserves the plant sections and starts the SFCs. All the control strategies are
completed one after the other.
20. Switch to the WinCC Runtime in the "Mixing" process picture and observe how the individual valves and pumps are
activated and thus the ingredients are dosed.
The batch is exited automatically. The SFCs that were started are terminated and reset to the "IDLE" state by SIMATIC
BATCH. The result of the bath is that the ingredients have been dosed and have been transported into buffer tank 1.

2.4.3. Scenario B "Pasteurization"

In Scenario A you dosed the individual ingredients and buffered them in the buffer tank. The following scenario describes
how you pasteurize these ingredients and transport them to the storage tank. Here, operation is carried out from the
SIMATIC BATCH Control Center.
Requirement

• The SIMATIC BATCH Control Center is open
• Role management has already been carried out
• The order "Mix Dark Choco 100% V01.00" has been executed in the SIMATIC BATCH Control Center
Execution
1. Switch to the SIMATIC BATCH Control Center and right-click “MixDarkChoko" and select the menu command "New".
The "Add Batch(es)" window opens.
2. Click the "New" button.
The "Selection of formula or master recipe" window opens.
3. Select the formula "Pasteurizing MBT -> MST V1.0".
4. Click the "OK" button.
5. Give the batch in the "Create order" window a suitable name.

6. Click on the "OK" button in the "Create order" window.
7. Right-click the batch and select the "Release" menu command.

9. Double-click the batch.

The control recipe will be displayed for you.
10. Right-click the batch and select the "Start" menu command.
The batch starts. SIMATIC BATCH now reserves the plant sections and starts the SFCs. All the control strategies are
completed one after the other.
12. Switch to the WinCC Runtime in the "Pasteurizer" process picture and observe how the individual valves and pumps are
activated and thus the ingredients are pasteurized.
BATCH. The result of the bath is that the finished ice cream is pasteurized and has been transported into storage tank 1.
2.4.4. Scenario C "Transport to the Freezer"

In Scenario A you dosed the individual ingredients and buffered them in the buffer tank. In scenario B thereafter you have
pasteurized the ingredients and transported the finished ice cream into the storage tank for storage. In the following,
how to empty the storage tank transport the contents to the freezer will be described. In this regard, operation takes
place in WinCC Runtime via the overview screen of SIMATIC BATCH OS controls.
Requirement

• Role management has already been carried out
• The order "Pasteurizing MBT -> MST V1.0" was executed in the SIMATIC BATCH Control Center
Execution
1. Open the Batch overview picture "BATCH OS Controls" in WinCC Runtime.
2. Right-click on the "UT_ICD_MP" project in the "SIMATIC BATCH OS Master".
3. Select the "Connect project" menu command.
4. In "SIMATIC BATCH OS Batch Creation" click on the button next to "Formula".

5. Select the "Emptying MST -> Freezer" recipe in the "Select Recipe/Formula" window.
7. Enter a suitable name in the "Name" field in "SIMATIC BATCH OS Batch Creation".
8. Adjust the star time in "SIMATIC BATCH OS Batch Creation"
9. In "SIMATIC BATCH OS Batch Creation", click on the "Release batches automatically" button.
10. Click on the "Yes" button in the "Confirm" dialog.
The batch is released.
11. Click on ("Release batch(es)") and confirm the messages with "OK"
12. In the "SIMATIC BATCH OS Process Cell" right-click on the batch that you have previously created.
13. Select the "Start batch" menu command.

14. Click on "Yes" in the "Confirm" dialog box.

15. You can see the plant sections occupied by the batch in the "SIMATIC BATCH OS Allocation".
16. Double-click e of the occupied plant sections.
The control recipe is displayed in the "SIMATIC BATCH OS Properties".
BATCH. The result of the batch is that the finished ice cream has been transported to the freezer.

Engineering
3. Engineering
3.1. Overview of the plant units
The "Ice Cream Plant" application example is comprised of various plant sections with technical functions and process
tags. In a PCS 7 project, all the process tags, including the CMT, are based on the master data library. SFC types, which are
also included in the master data library, are used to describe the technical functions.
In the following chapters you will find information on the structure of the individual technical functions.
The individual parts of an ice cream plant are described below. The entry point is the process image of the visualization
screen.
1
2
3
4
The process image of the ice cream plant consists of the following plant sections:
1. Mixing system (Mixing)
2. Buffer tank (Mix Buffer)
3. Pasteurizer
4. Storage tank (Mix Storage)

Engineering
3.2. Technical functions and process tags

of the mixing system (mixing)
The "Mixing" unit consists of the "Premixer" for dosing solid ingredients and the "Mainmixer" for dosing liquid ingredients.
The solid ingredients from the premixer are transported into the main mixer after dosing is concluded. If all ingredients
are dosed in the main mixer, the ingredients will then be mixed. The quantities of the ingredients to be dosed are defined
via the recipes in SIMATIC BATCH. Dosing occurs with the aid of batches and thus it is also logged.
1 2 3
5 6 7 8
4
9
10
The "Mixing" process image consists of the plant unit "Premixer" and "Mainmixer".
The premixer includes the following technical functions:
1. Dosing of cane sugar
2. Dosing of whey powder
3. Dosing of cocoa
4. Transfer out oft he premixer
The main mixer includes the following technical functions:

5. Dosing of water
6. Dosing of milk
7. Dosing of oil
8. Dosing oft he rework
9. Transfer into the main mixer
10. Transfer out of the main mixer

Engineering
3.2.1. Dosing of cane sugar

The ingredient cane sugar is routed into the premixer via the dosing. The quantities in which the ingredient must be
mixed are determined via the recipes from SIMATIC BATCH and thus are logged. In this processing the dosing occurs in
two stages. In the first stage the tank is filled via a large inflow until the set limit is reached. Thereafter filling occurs via a
significantly lower fill quantity until the dosing quantity has been reached. This enables a fast and yet precise dosing.
Setup
The figure below shows the structure of the dosing for cane sugar.
The instance of the SFC type "EQM_DOS_FLD" takes the valves, the motor and the dosing block into automatic mode and
starts the dosing process. The opening and closing of the valves is handled by the dosing block.
The following table provides an overview of the elements and CMTs used.
Designation Technical function/ Description

CMT
EQM_MAA_PMX SFC-Typ "EQM_DOS_SLD" Automatic mode of the valves

Starting of the dosing process
FIC_PMX001 "Dose" Process tag for coarse and fine dosing
YS_PMX001 "Vlv" Process tag valve coarse dosing
YS_PMX002 "Vlv" Process tag valve fine dosing

Engineering
Process tag interconnection

The following figure shows schematically the dosing device including the overarching connections or SFC accesses that
span the CFC diagram.
EQM_MAA_PMX FIC_PMX001 YS_PMX001
Dose Valve
EQM_MAA_PMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAA_PMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_PMX002
StartAut Valve
StopAut FbkOpenOut
CancelAut RdyToStart
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
ModLiOp
AutModLi
RstLi
Parameter assignment
The parameter assignment for the individual process tags is described below. A detailed description of the SFC type is
provided in Chapter "3.6 Sequences".
FIC_PMX001
In the "FIC_PMX001" process tag, the dosing amount of the ingredient in the premixer is regulated. The setpoint is
specified via the "EQM_MAA_PMX" SFC type instance. The process tag "FIC_PMX001" opens and closes the valves
"YC_PMX001" and "YS_PMX002". Process tag "FIC_PMX001" is an instance of the "Dose" control module type with the
following selected variants:
• PV_In
• PV_Scale
The following table shows the interconnections to other process tags and parameters:
Block Connection Value Use
PV_Scale HiScale 2000 High limit for the flow
PV_Unit IN 1323 Unit of the process value in kg/min

Engineering
D TI 60 Dosing delay
DQ_HiLim 2000 High limit for dosing
SP_HiLim 500 High limit for the coarse flow
SP2_HiLim 50 High limit for the fine flow
SP_LiOp Activation command for SFC operation

(EQM_MAA_PMX\CANESUGAR.
DOSE_SP_LiOp)
Ctrl Activation command for coarse dosing

(YS_PMX001\Y.OpenAut)
(YS_PMX001\Y.CloseAut)
Ctrl2 Activation command for fine dosing

DQ_Out Display of the dosed quantity

(EQM_MAA_PMX\CANESUGAR.Mat_AI
(Sim_PMX_EQM_TRI\1.In2)
PV_Out Output of the flow

(EQM_MAA_PMX\CANESUGAR.CoarseFeed_AI)
(EQM_MAA_PMX\CANESUGAR.FineFeed_AI)
PV_In SimOn Simulated process value active

(Activate_Simulation\SimAct.Out)
SimPV_In Interconnection for the simulated process

value (Sim_PMX_EMQ_TRI\RANDOM_01_02.
VALUE_SIM)
NOTE When "D.SP_LiOp" and "CANESUGAR.DOSE_SP_LiOp" are interconnected, all other interconnections
between the dosing block and the SFC type instances are also created automatically. These are not
listed in the above table.
YS_PMX001
The valve that is activated by the "YS_PMX001" process tag controls the inflow for the coarse dosing of cane sugar. In the
application example, the activation of the process tag occurs through the "EQM_MAA_PMX" SFC type instance. The
activation command for the process tag for opening and closing the valve occurs through the dosing block "FIC_PMX001".
Process tag "YS_PMX001" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock

Engineering
FbkOpen SimOn Use simulated value


value (Sim_YS_PMX001\SimFbkClose.In)
FbkClose SimOn Use simulated value


value
(Sim_YS_PMX001\SimFbkClose.InvOut)
Y OpenAut Activation order for opening in automatic

mode
(FIC_PMX001\D.Ctrl)
CloseAut Inverted Activation command for closing in

automatic mode
(FIC_PMX001\D.Ctrl)
ModLiOp Activation command for SFC operation

(EQM_MAA_PMX\CANESUGAR.V1_ModLiOp)
Ctrl Interconnection to the simulated feedback

(Sim_YS_PMX001\SimFbkOpen.In)
(Sim_YS_PMX001\SimFbkClose.In)
Opened Interconnection for simulation of the

control value
(Sim_PMX_EQM_TRO\DOSING.In1)
Interconnection for simulation of the
process value
(Sim_PMX_EQM_TRI.SEL COARSE 01.K)
Intlock InvIn01 1 Inverting of the interlock input 1
NOTE When "Y.ModLiOp" and "CANESUGAR.V1_ModLiOp" are interconnected, all other interconnections
between the valve block and the SFC type instances are also created automatically. These are not listed
in the above table.
YS_PMX002
The valve that is activated by the "YS_PMX002" process tag controls the inflow for the fine dosing of cane sugar. In the
application example, the activation of the process tag occurs through the "EQM_MAA_PMX" SFC type instance. The
• FbkClose
• FbkOpen
• Intlock

Engineering




value

mode
(FIC_PMX001\D.Ctrl2)

automatic mode

(EQM_MAA_PMX\CANESUGAR.V2_ModLiOp)


control value
process value
NOTE When "Y.ModLiOp" and "CANESUGAR.V2_ModLiOp" are interconnected, all other interconnections
in the above table.

Engineering
3.2.2. Dosing of whey powder

The ingredient whey powder is routed into the premixer via the dosing. The quantities in which the ingredient must be
Setup
The figure below shows the structure of the dosing for whey powder.
starts the dosing process. The opening and closing of the valves is handled by the dosing block.

CMT
EQM_MAB_PMX SFC-Typ "EQM_DOS_SLD" Automatic mode of the valves


Engineering

EQM_MAB_PMX FIC_PMX002 YS_PMX003
Dose Valve
EQM_MAB_PMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAB_PMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_PMX004
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
ModLiOp
AutModLi
RstLi
FIC_PMX002
In the "FIC_PMX002" process tag, the dosing amount of the whey powder ingredient in the premixer is regulated. In the
application example, the setpoint is specified via the "EQM_MAB_PMX" SFC type instance. The process tag "FIC_PMX002"
opens and closes the valves "YC_PMX003" and "YS_PMX004". Process tag "FIC_PMX002" is an instance of the "Dose"
control module type with the following selected variants:
• PV_In
• PV_Scale

Engineering

(EQM_MAB_PMX\WHEYPOWDER.
DOSE_SP_LiOp)



(EQM_MAB_PMX\WHEYPOWDER.Mat_AI

(EQM_MAB_PMX\WHEYPOWDER.CoarseFeed_AI)
(EQM_MAB_PMX\WHEYPOWDER.FineFeed_AI)

SimPV_In Interconnection for the simulated process value

(Sim_PMX_EMQ_TRI\RANDOM_03_04.
VALUE_SIM)
NOTE When "D.SP_LiOp" and "WHEYPOWDER.DOSE_SP_LiOp" are interconnected, all other interconnections
YS_PMX003
The valve that is activated by the "YS_PMX003" process tag controls the inflow for the coarse dosing of improvement. In
the application example, the activation of the process tag occurs through the "EQM_MAB_PMX" SFC type instance. The
• FbkClose
• FbkOpen
• Intlock

Engineering




value (Sim_YS_PMX003\SimFbkClose.InvOut)

mode
(FIC_PMX003\D.Ctrl)
CloseAut Inverted Activation command for closing in automatic

mode
(FIC_PMX003\D.Ctrl)

(EQM_MAB_PMX\WHEYPOWDER.V1_ModLiOp)

Opened Interconnection for simulation of the control

value
Interconnection for simulation of the process
value
NOTE When "Y.ModLiOp" and "WHEYPOWDER.V1_ModLiOp" are interconnected, all other interconnections
in the above table.
YS_PMX004
The valve that is activated by the "YS_PMX004" process tag controls the inflow for the fine dosing of whey powder. In the
application example, the activation of the process tag occurs through the "EQM_MAB_PMX" SFC type instance. The
• FbkClose
• FbkOpen
• Intlock

Engineering




value (Sim_YS_PMX004\SimFbkClose.InvOut)

mode
CloseAut Inverted Activation command for closing in automatic

mode

(EQM_MAB_PMX\WHEYPOWDER.V2_ModLiOp)

Opened Interconnection for simulation of the control

value
Interconnection for simulation of the process
value
NOTE When "Y.ModLiOp" and "WHEYPOWDER.V2_ModLiOp" are interconnected, all other interconnections
in the above table.

Engineering
3.2.3. Dosing of cocoa

The ingredient cocoa is routed into the premixer via the dosing. The quantities in which the ingredient must be mixed are
determined via the recipes from SIMATIC BATCH and thus are logged. In this processing the dosing occurs in two stages.
In the first stage the tank is filled via a large inflow until the set limit is reached. Thereafter filling occurs via a significantly
lower fill quantity until the dosing quantity has been reached. This enables a fast and yet precise dosing.
Setup
The figure below shows the structure of the dosing for cocoa.
Die Instanz des SFC-Typs "EQM_DOS_SLD" nimmt die Ventile und den Dosierbaustein in den Automatikbetrieb und startet
den Dosiervorgang. Das Öffnen und Schließen der Ventile übernimmt der Dosierbaustein.
In der folgenden Tabelle erhalten Sie eine Übersicht der Bestandteile und der verwendeten CMTs.

CMT
EQM_MAC_PMX SFC-Typ "EQM_DOS_SLD" Automatic mode of the valves


Engineering

EQM_MAC_PMX FIC_PMX003 YS_PMX004
Dose Valve
EQM_MAA_PMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAA_PMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_PMX005
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
ModLiOp
AutModLi
RstLi
FIC_PMX003
In the "FIC_PMX003" process tag, the dosing amount of the whey powder ingredient in the premixer is regulated. In the
application example the setpoint is specified via the "EQM_MAC_PMX" SFC type instance. The process tag "FIC_PMX003"
opens and closes the valves "YC_PMX005" and "YS_PMX006". Process tag "FIC_PMX003" is an instance of the "Dose"
• PV_In
• PV_Scale

Engineering

(EQM_MAC_PMX\CACAO.DOSE_SP_LiOp)



(EQM_MAC_PMX\CACAO.Mat_AI

(EQM_MAC_PMX\CACAO.CoarseFeed_AI)
(EQM_MAC_PMX\CACAO.FineFeed_AI)

SimPV_In Interconnection for the simulated

process value
(Sim_PMX_EMQ_TRI\RANDOM_05_06.
VALUE_SIM)
NOTE When "D.SP_LiOp" and "CACAO.DOSE_SP_LiOp" interconnected, all other interconnections between
the dosing block and the SFC type instances are also created automatically. These are not listed in the
above table.
YS_PMX005
The valve that is activated by the "YS_PMX005" process tag controls the inflow for the coarse dosing of cocoa. In the
application example, the activation of the process tag occurs through the "EQM_MAC_PMX" SFC type instance. The
• FbkClose
• FbkOpen

Engineering
• Intlock


process value


process value
Y OpenAut Activation order for opening in

automatic mode
(FIC_PMX005\D.Ctrl)

automatic mode
(FIC_PMX005\D.Ctrl)

(EQM_MAC_PMX\CACAO.V1_ModLiOp)
Ctrl Interconnection to the simulated

feedback

process value
NOTE When "Y.ModLiOp" and "CACAO.V1_ModLiOp" are interconnected, all other interconnections between
the valve block and the SFC type instances are also created automatically. These are not listed in the
above table.
YS_PMX006
The valve that is activated by the "YS_PMX006" process tag controls the inflow for the fine dosing of cocoa. In the
application example, the activation of the process tag occurs through the "EQM_MAC_PMX" SFC type instance. The

Engineering
• FbkClose
• FbkOpen
• Intlock


process value

SimPV_In Interconnection to the simulated process

value

automatic mode

automatic mode

(EQM_MAC_PMX\CACAO.V2_ModLiOp)
Ctrl Interconnection to the simulated process

value (Sim_YS_PMX006\SimFbkOpen.In)

control value
NOTE When "Y.ModLiOp" and "CACAO.V2_ModLiOp" are interconnected, all other interconnections between
above table.
3.2.4. Transfer out of the premixer

After dosing the solid ingredients in the premixer the ingredients are routed out of the premixer and into the main mixer.
The activation for this occurs from SIMATIC BATCH. At transfer, the empty status is detected by a sensor; if this is reached
in addition the system will wait for a parameterized time to ensure that the premixer is completely emptied.

Engineering
Setup
The figure below shows the structure for the transfer out of the pre mixer.
The instance of the "TRANS_OUT_PRE" SFC type monitors the emptying process of the premixer.

CMT
EQM_TRO_PMX SFC-Typ "TRANS_OUT_PRE" Monitoring of the emptying procedure
LSL_PMX001 "MonDi" Process tag for detection of premixer

emptied

Engineering

The following figure shows schematically the transfer device including the overarching connections or SFC accesses that
LSL_PMX001 TRANSER_OUT
Out Empty
LSL_PMX001
The display process tag "LSL_PMX001" is used for detecting and displaying the emptied status of the premixer. Process tag
"LSL_PMX001" is an instance of the "MonDi" CMT with "In" variant selected.
In SimOn Simulated process value active

SimPV_In Interconnection to the simulated

process value
(Sim_PMX_EQM_TRO\
LVL CAPPED.Out)
S Out Digital output value

(EQM_TRO_PMX\TRANSFER_OUT.
EMPTY)
3.2.5. Dosing of water

Water is routed into the main mixer via the dosing. The quantities in which the ingredient must be mixed are determined
via the recipes from SIMATIC BATCH and thus are logged. In this processing the dosing occurs in two stages. In the first
stage the tank is filled via a large inflow until the set limit is reached. Thereafter filling occurs via a significantly lower fill
quantity until the dosing quantity has been reached. This enables a fast and yet precise dosing.
Setup
The figure below shows the structure of the dosing for water.

Engineering
starts the dosing process. The opening and closing function of the valves as well as the starting of the motor is handled by
the dosing block.

CMT
EQM_MAA_MMX SFC-Typ "EQM_DOS_FLD" Automatic mode of the valves and of

the motor, starting of the dosing
process
FIC_MMX001 "Dose" Process tag for coarse and fine dosing
NS_MMX001 "Mot" Process tag for pump drive for dosing

water
YS_MMX001 "Vlv" Process tag valve coarse dosing
YS_MMX002 "Vlv" Process tag valve fine dosing

Engineering

EQM_MAA_MMX FIC_MMX001 YS_MMX001
Dose Valve
EQM_MAA_MMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAA_MMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_MMX002
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
NS_MMX001
ModLiOp
Motor
AutModLi
GrrErr
RstLi
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
FIC_MMX001
In the "FIC_MMX001" process tag, the dosing amount of the ingredient in the premixer is regulated. The setpoint is
specified via the "EQM_MAA_MMX" SFC type instance. The process tag "FIC_MMX001" starts the motor "NS_MMX002" and
opens and closes the valves "YC_MMX001" and "YS_MMX002". Process tag "FIC_MMX001" is an instance of the "Dose"

Engineering
• PV_In
• PV_Scale

(EQM_MAA_MMX\WATER.DOSE_SP_LiOp)

(YS_MMX001\Y.OpenAut)
(YS_MMX001\Y.CloseAut)
(NS_MMX001\V1 or V2 open.In1)


(EQM_MAA_MMX\Water.Mat_AI)
(Sim_MMX_EQM_TRI\9.In2)

(EQM_MAA_MMX\WATER.DOSE_PV_Out)


value
(Sim_MMX_EMQ_TRI\RANDOM_01_02.
VALUE_SIM)
NOTE When "D.SP_LiOp" and "WATER.DOSE_SP_LiOp" are interconnected, all other interconnections between
above table.

Engineering
NS_MMX001
The pump that is activated by the "NS_MMX001" process tag doses the ingredient water. In the application example,
activation of the process tag occurs through the SFC type instance "EQM_MAA_MMX" and the process tag "FIC_MMX001".
Process tag "NS_MMX001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1
The process tag has been expanded to incorporate the following functions:
• Or04 – "V1 or V2 open"

Fbk SimOn Simulated process value active


process value
(Sim_NS_MMX001\SimFbkRun.Out)
V1 or V2 open In1 Start pulse

(FIC_MMX001\D.Ctrl)
In2 Start pulse

(FIC_MMX001\D.Ctrl2)
Out Start pulse

(NS_MMX001\U.StartAut)
(NS_MMX001\U.StopAut)
U ModLiop Changeover of operating mode

selection manual/interconnection
(EQM_MAA_MMX\WATER.M2_ModLiOp)
Start Interconnection to the simulated

feedback
(Sim_MMX_NS001\SimFbkRun.In)
GrrErr Group error active

(NS_MMX001\Intlock.In1)
NOTE When "U.ModLiOp" and "WATER.M1_ModLiOP" are interconnected, all other interconnections between
the motor module and the SFC type instances are also created automatically. These are not listed in
the above table.
YS_MMX001
The valve that is activated by the "YS_MMX001" process tag controls the inflow for the coarse dosing of water. In the
application example, the activation of the process tag occurs through the "EQM_MAA_MMX" SFC type instance. The
activation command for the process tag for opening and closing the valve occurs through the dosing block
"FIC_MMX001". Process tag "YS_MMX001" is an instance of the "Vlv" control module type with the following selected
variants:
• FbkClose

Engineering
• FbkOpen
• Intlock


process value
(Sim_YS_MMX001\SimFbkClose.In)


process value
(Sim_YS_MMX001\SimFbkClose.InvOut)

automatic mode
(FIC_MMX001\D.Ctrl)

automatic mode
(FIC_MMX001\D.Ctrl)

(EQM_MAA_MMX\WATER.V1_ModLiOp)

feedback
(Sim_YS_MMX001\SimFbkOpen.In)

control value
(Sim_MMX_EQM_TRO\DOSING.In1)
process value
(Sim_MMX_EQM_TRI.SEL COARSE 01.K)
NOTE When "Y.ModLiOp" and "WATER.V1_ModLiOp" are interconnected, all other interconnections between
above table.

Engineering
YS_MMX002
The valve that is activated by the "YS_MMX002" process tag controls the inflow for the fine dosing of water. In the
application example, the activation of the process tag occurs through the "EQM_MAA_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode

automatic mode

(EQM_MAA_MMX\WATER.V2_ModLiOp)

feedback

control value
process value

Engineering
NOTE When "Y.ModLiOp" and "WATER.V2_ModLiOp" are interconnected, all other interconnections between
above table.

Engineering
3.2.6. Dosing of milk

Milk is routed into the main mixer via the dosing. The quantities in which the ingredient must be mixed are determined
via the recipes from SIMATIC BATCH and thus are logged. In this processing the dosing occurs in two stages. In the first
stage the tank is filled via a large inflow until the set limit is reached. Thereafter filling occurs via a significantly lower fill
Setup
The figure below shows the structure of the dosing for milk.
the dosing block.

CMT
EQM_MAB_MMX SFC-Typ "EQM_DOS_FLD" Automatic mode of the valves and of

process

water

Engineering

EQM_MAB_MMX FIC_MMX002 YS_MMX003
Dose Valve
EQM_MAB_MMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAB_MMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_MMX004
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
NS_MMX002
ModLiOp
Motor
AutModLi
GrrErr
RstLi
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
FIC_MMX002
In the "FIC_MMX002" process tag, the dosing amount of the ingredient in the premixer is regulated. In the application
example the setpoint is specified via the "EQM_MAB_MMX" SFC type instance. The process tag "FIC_MMX002" starts the
motor "NS_MMX002" and opens and closes the valves "YC_MMX003" and "YS_MMX004". Process tag "FIC_MMX002" is an
instance of the "Dose" control module type with the following selected variants:

Engineering
• PV_In
• PV_Scale

(EQM_MAB_MMX\MILK.DOSE_SP_LiOp)



(EQM_MAB_MMX\MILK.Mat_AI)

(EQM_MAB_MMX\MILK.DOSE_PV_Out)


process value
VALUE_SIM)
NOTE When "D.SP_LiOp" and "MILK.DOSE_SP_LiOp" are interconnected all other interconnections between
above table.

Engineering
NS_MMX002
activation of the process tag occurs through the SFC type instance "EQM_MAB_MMX" and the process tag "FIC_MMX002".
• Interlock
• Fbk1


process value

(FIC_MMX002\D.Ctrl)
In2 Start pulse

Out Start pulse

U ModLiop Changeover operating mode selection

manual/interconnection
(EQM_MAB_MMX\MILK.M2_ModLiOp)

feedback
NOTE When "U.ModLiOp" and "MILK.M1_ModLiOP" are interconnected, all other interconnections between
the above table.
YS_MMX003
The valve that is activated by the "YS_MMX003" process tag controls the inflow for the coarse dosing of milk. In the
application example, the activation of the process tag occurs through the "EQM_MAB_MMX" SFC type instance. The

Engineering
variants:
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode
(FIC_MMX002\D.Ctrl)

automatic mode
(FIC_MMX002\D.Ctrl)

(EQM_MAB_MMX\MILK.V1_ModLiOp)

feedback

control value
process value
NOTE When "Y.ModLiOp" and "MILK.V1_ModLiOp" are interconnected, all other connections between the
valve block and the SFC type instances are also created automatically. These are not listed in the above
table.

Engineering
YS_MMX004
The valve that is activated by the "YS_MMX004" process tag controls the inflow for the fine dosing of milk. In the
application example, the activation of the process tag occurs through the "EQM_MAB_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode

automatic mode

(EQM_MAB_MMX\MILK.V2_ModLiOp)

feedback

control value
process value

Engineering
NOTE When "Y.ModLiOp" and "MILK.V2_ModLiOp" are interconnected, all other connections between the
table.

Engineering
3.2.7. Dosing of oil

Oil is routed into the main mixer via the dosing. The quantities in which the ingredient must be mixed are determined via
the recipes from SIMATIC BATCH and thus are logged. In this processing the dosing occurs in two stages. In the first stage
the tank is filled via a large inflow until the set limit is reached. Thereafter filling occurs via a significantly lower fill
Setup
The figure below shows the structure of the dosing for oil.
the dosing block.

CMT
EQM_MAC_MMX SFC-Typ "EQM_DOS_FLD" Automatic mode of the valves and of

process

water


Engineering
EQM_MAC_MMX FIC_MMX003 YS_MMX005
Dose Valve
EQM_MAC_MMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAC_MMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_MMX006
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
NS_MMX003
ModLiOp
Motor
AutModLi
GrrErr
RstLi
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
FIC_MMX003
example the setpoint is specified via the "EQM_MAC_MMX" SFC type instance. The process tag "FIC_MMX003" starts the
motor "NS_MMX003" and opens and closes the valves "YC_MMX005" and "YS_MMX006". Process tag "FIC_MMX003" is an
• PV_In
• PV_Scale

Engineering

(EQM_MAC_MMX\OIL.DOSE_SP_LiOp)



(EQM_MAC_MMX\OIL.Mat_AI)

(EQM_MAC_MMX\OIL.DOSE_PV_Out)


process value
VALUE_SIM)
NOTE When "D.SP_LiOp" and "OIL.DOSE_SP_LiOp" These are not listed in the above table.
NS_MMX003
activation of the process tag occurs through the SFC type instance "EQM_MAC_MMX" and the process tag "FIC_MMX003".
• Interlock
• Fbk1

Engineering


process value

(FIC_MMX003\D.Ctrl)
In2 Start pulse

Out Start pulse

U ModLiop Changeover operating mode

selection manual/interconnection
(EQM_MAC_MMX\OIL.M2_ModLiOp)

feedback

NOTE When "U.ModLiOp" and "OIL.M1_ModLiOP" are interconnected, all other interconnections between the
motor module and the SFC type instances are also created automatically. These are not listed in the
above table.
YS_MMX005
The valve that is activated by the "YS_MMX005" process tag controls the inflow for the coarse dosing of oil. In the
application example, the activation of the process tag occurs through the "EQM_MAC_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


process value


process value

automatic mode
(FIC_MMX003\D.Ctrl)

automatic mode
(FIC_MMX003\D.Ctrl)

(EQM_MAC_MMX\OIL.V1_ModLiOp)

feedback

control value
process value
NOTE When "Y.ModLiOp" and "OIL.V1_ModLiOp" are interconnected, all other connections between the
table.
YS_MMX006
The valve that is activated by the "YS_MMX006" process tag controls the inflow for the fine dosing of oil. In the
application example, the activation of the process tag occurs through the "EQM_MAC_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen

Engineering
• Intlock


process value


process value

automatic mode

automatic mode

(EQM_MAC_MMX\OIL.V2_ModLiOp)

feedback

control value
process value
NOTE When "Y.ModLiOp" and "OIL.V2_ModLiOp" are interconnected, all other connections between the
table.

Engineering
3.2.8. Dosing of the rework

Via the dosing the material for rework is routed into the main mixer. The quantities in which the ingredient must be
Setup
The figure below shows the structure of the dosing for rework.
the dosing block.

CMT
EQM_MAC_MMX SFC-Typ "EQM_DOS_FLD" Automatic mode of the valves and of

process

water


Engineering
EQM_MAD_MMX FIC_MMX004 YS_MMX007
Dose Valve
EQM_MAD_MMX
FbkOpenOut
Ctrl
RdyToStart
Ctrl2
RdyToReset
GrrErr
FbkCloseOut
AutAct
Ctrl
SP_ExtAct
AutAct
Valve
Dose
ModLiOp OpenAut
SP_LiOp ModLiOp
EQM_MAD_MMX
AutModLi AutModLi
SP_ExtLi RstLi
RstDQ
RstLi YS_MMX008
StartAut Valve
StopAut FbkOpenOut
DQ_Ext RdyToReset
DQ2_Ext FbkCloseOut
SP_Ext Ctrl
SP2_Ext AutAct
Valve
OpenAut
NS_MMX004
ModLiOp
Motor
AutModLi
GrrErr
RstLi
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
FIC_MMX004
example the setpoint is specified via the "EQM_MAD_MMX" SFC type instance. The process tag "FIC_MMX004" starts the
motor "NS_MMX004" and closes and opens the valves "YC_MMX007" and "YS_MMX008". Process tag "FIC_MMX004" is an
• PV_In
• PV_Scale

Engineering

(EQM_MAD_MMX\REWORK.DOSE_SP_LiOp)



(EQM_MAD_MMX\REWORK.Mat_AI)
PV_In PV_Out Output of the flow

(EQM_MAD_MMX\REWORK.DOSE_PV_Out)
SimOn Simulated process value active

NOTE When "D.SP_LiOp" and "REWORK.DOSE_SP_LiOp" are interconnected all other interconnections
NS_MMX004
activation of the process tag occurs through the SFC type instance "EQM_MAD_MMX" and the process tag "FIC_MMX004".
• Interlock
• Fbk1

Engineering


value (Sim_NS_MMX004\SimFbkRun.Out)

(FIC_MMX004\D.Ctrl)
In2 Start pulse

Out Start pulse

U ModLiop Changeover of operating mode selection

manual/interconnection
(EQM_MAD_MMX\REWORK.M2_ModLiOp)

feedback

NOTE When "U.ModLiOp" and "REWORK.M1_ModLiOP" are interconnected, all other interconnections
between the motor module and the SFC type instances are also created automatically. These are not
YS_MMX007
The valve that is activated by the "YS_MMX007" process tag controls the inflow for the coarse dosing of rework. In the
application example, the activation of the process tag occurs through the "EQM_MAD_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen
• Intlock


Engineering

process value


process value

mode
(FIC_MMX004\D.Ctrl)

automatic mode
(FIC_MMX004\D.Ctrl)

(EQM_MAD_MMX\REWORK.V1_ModLiOp)

feedback

control value
process value
NOTE When "Y.ModLiOp" and "REWORK.V1_ModLiOp" are interconnected, all other interconnections
in the above table.
YS_MMX008
The valve that is activated by the "YS_MMX008" process tag controls the inflow for the fine dosing of rework. In the
application example, the activation of the process tag occurs through the "EQM_MAD_MMX" SFC type instance. The
variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


process value


process value

mode

automatic mode

(EQM_MAD_MMX\REWORK.V2_ModLiOp)

feedback

control value
process value
NOTE When "Y.ModLiOp" and "REWORK.V2_ModLiOp" are interconnected, all other interconnections
in the above table.

Engineering
3.2.9. Transfer into the main mixer

After dosing the solid ingredients in the premixer the ingredients are routed out of the premixer and into the main mixer.
The activation for this occurs from SIMATIC BATCH. At transfer the valve in the main mixer is opened. Via a sensor the full
status is detected, if this status is reached the further filling of the main mixer will be halted and the valve will be closed.
Setup
The figure below shows the structure for the transfer into the main mixer.
The instance of the "TRANS_IN" SFC type monitors the emptying filling process of the main mixer.

CMT
EQM_TRI_MMX SFC-Typ "TRANS_IN" Monitoring of the filling process
LI_MST01_001 "MonAn" Process tag for detecting the fill-level

of the main mixer
LSH_MMX001 "MonDi" Process tag for detection of main mixer

full
YS_MMX020 "Vlv" Process tag filling valve main mixer

Engineering

LI_MMX001 EQM_TRI_MMX YS_MMX020

Valve
PV_AH_Ac EQM_TRI_MMX
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
LSL_MMX001
Ctrl
Out
AutAct
SimPV_In
Valve
OpenAut
ModLiOp
EQM_TRI_MMX
AutModLi
RstLi
LI_MMX001
The display process tag "LI_MMX001 "is used for detecting and displaying the full status of the main mixer. Process tag
"LI_MMX001" is an instance of the "MonAn" control module type with the following selected variants:
• PV_In
• PV_Scale
PV_Scale HiScale 8000 High limit for the display
LoScale -10 Low limit for the display
PV_Unit IN 1088 Unit of the process value in kg


process value
(Sim_MMX_EQM_TRO\6.Out)
I PV_Out Analog output value

(Sim_MMX_EQM_TRO\LVL
Capped.In1)
PV_AH_Li 7950 Limit value for high alarm

Engineering
PV_AH_Ac Alarm high limit reached

(LSH_MMX001\In.SimPV_In)
LSH_MMX001
The display process tag "LSH_MMX001" is used for detecting and displaying the full status of the main mixer. Process tag
"LSH_MMX001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
(LI_MMX001\I.PV_AH_Act)

(EQM_TRI_MMX\TRANSFER_IN.
HOLD)
YS_MMX020
The valve that is activated by the "YS_MMX020" process tag controls the inflow into the main mixer. In the application
example, the activation of the process tag occurs through the "EQM_TRI_MMX" SFC type instance. Process tag
"YS_MMX020" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode
(EQM_TRI_MMX\TRANSFER_IN.
V1_OpenAut)

Engineering

feedback
(Sim_PMX_EQM_TRO\LVL CAPPED.
SetLi)
NOTE When "Y.OpenAut" and "TRANSFER_IN.V1_OpenAut" are interconnected, all other interconnections
in the above table.
3.2.10. Transfer out of the main mixer

After dosing the ingredients in the main mixer the ingredients are transported out of the main mixer, this is controlled via
a pump in the outlet of the main mixer. The activation for this occurs from SIMATIC BATCH. Via a sensor the empty status
is detected; if this is reached in addition the system will wait for a parameterized time to ensure that the main mixer is
completely emptied.
Setup
The figure below shows the structure for the transfer out of the main mixer.
10
The instance of the "TRANS_OUT_MIX" SFC type monitors the emptying process of the main mixer.

CMT
EQM_TRO_MMX SFC-Typ "TRANS_OUT_MIX" Monitoring of the emptying procedure

Engineering

CMT
LSL_MMX001 "MonDi" Process tag for detection of main mixer

emptied
NS_MMX021 "Mot" Process tag for pump drive for transfer

out of the main mixer

LSL_MMX001 EQM_TRO_MMX NS_MMX021
Out EQM_TRO_MMX Motor

GrrErr
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
EQM_TRO_MMX StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
LSL_MMX001
The display process tag "LSL_MMX001" is used for detecting and displaying the emptied status of the main mixer. Process
tag "LSL_MMX001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
(LI_MMX001\I.PV_AH_Ac)

(EQM_TRO_MMX\TRANSFER_OUT.
EMPTY)

Engineering
NS_MMX021
The pump that is activated by the "NS_MMXS021" process tag is used to empty the main mixer. In the application
example, the activation of the process tag occurs through the "EQM_TRO_MMX" SFC type instance. Process tag
"NS_MMX021" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
U StartAut Start command in automatic mode

(EQM_TRO_MMX\TRANSFER_OUT.
M1_StartAut)

feedback

NOTE When "U.StartAut" and "TRANSFER_OUT.M1_StartAut" are interconnected, all other interconnections

Engineering
3.3. Technical functions and process tags

of the buffer tank (Mix Buffer)
The buffer tank gets the ingredients after dosing buffers them before they are further conveyed into the pasteurizer. The
transport of materials is defined via the recipes in SIMATIC BATCH. This occurs with batches and thus it is also logged.
2 5
1 4
3 6
The process image "Mix Buffer" consists of the plant units Buffer Tank 1, "Mix Buffer 1", and Buffer tank 2 "Mix Buffer 2"
Puffer tank 1 includes the following technical functions:
1. Agitator buffer tank 1
2. Transfer into buffer tank 1
3. Transfer out of buffer tank 1
Puffer tank 2 includes the following technical functions:

4. Stirring buffer tank 2
5. Transfer into buffer tank 2
6. Transfer out of buffer tank 2
NOTE Through the identical structure of the units buffer tank 1 and buffer tank 2 the assignment of the units
as parameters is possible in SIMATIC BATCH.

Engineering
3.3.1. Agitator buffer tank 1

When filling, emptying and for storage of the ingredients after dosing in buffer tank 1, the filling process is started. The
activation for this occurs from SIMATIC BATCH. The agitating process is started from a defined fill level and runs until the
tank has been emptied, thus the agitating process runs in a manner that is batch-overarching.
Setup
The figure below shows the structure of the agitator of buffer tank 1:
The instance of the SFC type "TANK_AGI" starts the motor.


CMT
EQM_AGI_MBT01 SFC-Typ "TANK_AGI" Starting of the agitating process
NS_MBT01_001 "Mot" Process tag for the agitator drive

Engineering

The following figure shows schematically the agitator device including the overarching connections or SFC accesses that
EQM_AGI_MBT01 NS_MBT01_001
EQM_AGI_MBT01 Motor
GrrErr
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
EQM_AGI_MBT01 StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
NS_MBT01_001
The motor that is activated by the "NS_MBT01_001" process tag, starts the agitator of the buffer tank. In the application
example, the activation of the process tag occurs through the "EQM_AGI_MBT01" SFC type instance. Process tag
"NS_MBT01_001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
(Sim_MBT01_NS001\SimFbkRun.Out)

(EQM_AGI_MBT01\AGITATOR.
M1_StartAut)

feedback
(Sim_MBT01_NS001\SimFbkRun.In)

(NS_MBT01_001\Intlock.In1)

Engineering
NOTE When "U.StartAut" and "AGITATOR.M1_StartAut" are interconnected, all other interconnections
3.3.2. Transfer into buffer tank 1

After dosing the ingredients, the ingredients are routed out of the main mixer and into the buffer tank. The activation of
which buffer tank is used for storage occurs from SIMATIC BATCH and thus is logged. If transfer into buffer tank 1 is
selected, the in valve in buffer tank 1 will be opened. Via a sensor the full status is detected, if this status is reached the
further filling of the buffer tank will be halted and the valve will be closed.
Setup
The figure below shows the structure for the transfer into buffer tank 1.
The instance of the "TRANS_IN" SFC type monitors the filling process of the buffer tank.

CMT
EQM_TRI_MBT01 SFC-Typ "TRANS_IN" Monitoring of the filling process
LSH_MBT01_001 "MonDi" Process tag for detection of buffer tank

1 full
YS_MBT01_004 "Vlv" Process tag filling valve buffer tank 1

Engineering

LSH_MBT01_001 EQM_TRI_MBT01 YS_MBT01_004

Valve
Out EQM_TRI_MBT01
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
Ctrl
AutAct
Valve
OpenAut
ModLiOp
EQM_TRI_MBT01
AutModLi
RstLi
LSH_MBT01_001
The display process tag "LSH_MBT01_001" is used for detecting and displaying the full status of the buffer tank. Process
tag "LSH_MBT01_001" is an instance of the "MonDi" CMT with "In" variant selected.


(EQM_TRI_MBT01\TRANSFER_IN.
HOLD)
YS_MBT01_004
The valve that is activated by the "YS_MBT01_004" process tag controls the inflow into buffer tank 1. In the application
example, the activation of the process tag occurs through the "EQM_TRI_MBT01" SFC type instance. Process tag
"YS_MBT01_004" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


Engineering

value
(Sim_MBT01_YS004\SimFbkClose.In)


value
(Sim_MBT01_YS004\SimFbkClose.InvOut)

mode
V1_OpenAut)
Ctrl Interconnection for the simulated

feedback
(Sim_MBT01_YS004\SimFbkOpen.In)

(YS_MBT01_004\Intlock.In1)
Opened Valve open

(Sim_MBT01_EQM_TRO\LVL
CAPPED.RstLi)
in the above table.

Engineering
3.3.3. Transfer out of buffer tank 1

After intermediate storage of the ingredients in the buffer tank the ingredients will be further transported to
pasteurization. The activation of which buffer tank is used for storage and should be emptied occurs from SIMATIC BATCH
and thus is logged. If transfer from buffer tank 1 is selected, the valve out of buffer tank 1 will be opened. Via a sensor the
empty status is detected; if this is reached in addition the system will wait for a parameterized time to ensure that the
buffer tank is completely emptied.
Setup
The figure below shows the structure for the transfer out of buffer tank 1.
The instance of the "TRANS_OUT_BUF" SFC type monitors the emptying process of the buffer tank.

CMT
EQM_TRO_MBT01 SFC-Typ "TRANS_OUT_BUF" Monitoring of the emptying procedure
LSL_MBT01_001 "MonDi" Process tag for detection of buffer tank

1 empty
YS_MBT01_001 "Vlv" Process tag emptying valve buffer tank

1

Engineering

LSL_MBT01_001 EQM_TRI_MBT01 YS_MBT01_001

Valve
Out EQM_TRI_MBT01
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
Ctrl
AutAct
Valve
OpenAut
ModLiOp
EQM_TRI_MBT01
AutModLi
RstLi
LSL_MBT01_001
The display process tag "LSL_MBT01_001" is used for detecting and displaying the empty status of storage tank 1. Process
tag "LSL_MBT01_001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
CAPPED.Out)

(EQM_TRO_MBT01\TRANSFER_OUT.
EMPTY)
(EQM_MGR_MBT01\MBT_MGR.EMPTY)
YS_MBT01_001
The valve that is activated by the "YS_MBT01_001" process tag empties buffer tank 1. In the application example, the
activation of the process tag occurs through the "EQM_TRO_MBT01" SFC type instance. Process tag "YS_MBT01_001" is an
instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


value


value

mode
V1_OpenAut)

feedback

Opened Valve open

CAPPED.SetLi)
NOTE When "Y.OpenAut" and "TRANSFER_OUT.V1_OpenAut" are interconnected, all other interconnections
in the above table.

Engineering

When filling, emptying and for storage of the ingredients after dosing in buffer tank 2, the filling process is started. The
activation for this occurs from SIMATIC BATCH. The agitating process is started from a defined fill level and runs until the
tank has been emptied, thus the agitating process runs in a manner that is batch-overarching.
Setup
The figure below shows the structure of the agitator of buffer tank 2:


CMT
EQM_AGI_MBT02 SFC-Typ "TANK_AGI" Starting of the agitating process
NS_MBT02_001 "Mot" Process tag for the agitator drive

Engineering

EQM_AGI_MBT02 NS_MBT02_001
EQM_AGI_MBT02 Motor
GrrErr
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
EQM_AGI_MBT02 StopAut
AutModLi
RstLi
ModLiOp
NS_MBT02_001
The motor that is activated by the "NS_MBT02_001" process tag, starts the agitator of the buffer tank. In the application
example, the activation of the process tag occurs through the "EQM_AGI_MBT02" SFC type instance. Process tag
"NS_MBT02_001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
(Sim_MBT02_NS001\SimFbkRun.Out)

(EQM_AGI_MBT02\AGITATOR.
M1_StartAut)

feedback
(Sim_MBT02_NS001\SimFbkRun.In)

(NS_MBT02_001\Intlock.In1)

Engineering
3.3.5. Transfer into buffer tank 2

After dosing the ingredients, the ingredients are routed out of the main mixer and into the buffer tank. The activation of
which buffer tank is used for storage occurs from SIMATIC BATCH and thus is logged. If transfer into buffer tank 2 is
selected, the in valve in buffer tank 2 will be opened. Via a sensor the full status is detected, if this status is reached the
further filling of the buffer tank will be halted and the valve will be closed.
Setup
The figure below shows the structure for the transfer into buffer tank 2.
The instance of the "TRANS_IN" SFC type monitors the filling process of the buffer tank.

CMT
EQM_TRI_MBT02 SFC-Typ "TRANS_IN" Monitoring of the filling process
LSH_MBT02_001 "MonDi" Process tag for detection of buffer tank

2 full
YS_MBT02_004 "Vlv" Process tag filling valve buffer tank 2


Engineering
LSH_MBT02_001 EQM_TRI_MBT02 YS_MBT02_004

Valve
Out EQM_TRI_MBT02
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
Ctrl
AutAct
Valve
OpenAut
ModLiOp
EQM_TRI_MBT02
AutModLi
RstLi
LSH_MBT02_001
The display process tag "LSH_MBT02_001" is used for detecting and displaying the full status of the buffer tank. Process


HOLD)
YS_MBT02_004
The valve that is activated by the "YS_MBT02_004" process tag controls the inflow into buffer tank 2. In the application
example, the activation of the process tag occurs through the "EQM_TRI_MBT02" SFC type instance. Process tag
"YS_MBT02_004" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


value

Engineering


value

mode
V1_OpenAut)

feedback

Opened Valve open

CAPPED.RstLi)
in the above table.

Engineering
3.3.6. Transfer out of buffer tank 2

After intermediate storage of the ingredients in the buffer tank the ingredients will be further transported to
pasteurization. The activation of which buffer tank is used for storage and should be emptied occurs from SIMATIC BATCH
and thus is logged. If transfer from buffer tank 2 is selected, the valve out of buffer tank 2 will be opened. Via a sensor the
empty status is detected; if this is reached in addition the system will wait for a parameterized time to ensure that the
buffer tank is completely emptied.
Setup
The figure below shows the structure for the transfer out of buffer tank 2.
The instance of the "TRANS_OUT_BUF" SFC type monitors the emptying process of the buffer tank.

CMT
EQM_TRO_MBT02 SFC-Typ "TRANS_OUT_BUF" Monitoring of the emptying procedure
LSL_MBT02_001 "MonDi" Process tag for detection of buffer tank

2 empty
YS_MBT02_001 "Vlv" Process tag emptying valve buffer tank

2


Engineering
LSL_MBT02_001 EQM_TRI_MBT02 YS_MBT02_001

Valve
Out EQM_TRI_MBT02
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
Ctrl
AutAct
Valve
OpenAut
ModLiOp
EQM_TRI_MBT02
AutModLi
RstLi
The parameter assignment for the individual process tags is described below. A detailed description of the
SFC type is provided in Chapter "3.6 Sequences".
LSL_MBT02_001
The display process tag "LSL_MBT02_001" is used for detecting and displaying the empty status of the buffer tank. Process
tag "LSL_MBT02_001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
CAPPED.Out)

EMPTY)
(EQM_MGR_MBT02\MBT_MGR.EMPTY)
YS_MBT02_001
The valve that is activated by the "YS_MBT02_001" process tag empties buffer tank 2. In the application example, the
activation of the process tag occurs through the "EQM_TRO_MBT02" SFC type instance. Process tag "YS_MBT02_001" is an
instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


value


value

mode
V1_OpenAut)

feedback

Opened Valve open

CAPPED.SetLi)
NOTE When "Y.OpenAut" and "TRANSFER_OUT.V1_OpenAut" are interconnected, all other interconnections
in the above table.

Engineering
3.4. Technical function and process tags

of the pasteurizer
The pasteurizer heats the ice cream from the buffer tank before the finished product is pumped into one of the storage
tanks. Pasteurization is used to make the ice cream stable (longer shelf life). The complete sequences is to extensive,
consequently only the possible integration of the unit in the recipe system is shown. After pasteurization the ingredients
are forced out of the pasteurizer with water. The post-rinsing duration is determined via the recipes from SIMATIC BATCH
and thus is logged.
Setup
The figure below shows the structure of the pasteurizer:
The instance of the "EQM_PAS" SFC type starts the transfer into and out of the pasteurizer.
NOTE Only the transfer of the ice cream into and out of the pasteurizer is activated, because the activation of
the pasteurizer is executed separately with a local control element.

CMT
EQM_PAS SFC-Typ "PASTEUR" Starting the pasteurization
NS_PAS001 "Mot" Process tag for pump drive for

pasteurization
YS_PAS001 "Vlv" Process tag pasteurization valve inflow
YS_PAS002 "Vlv" Process tag pasteurization valve

outflow
YS_PAS003 "Vlv" Process tag pasteurization valve in

circuit 1

Engineering

CMT
YS_PAS004 "Vlv" Process tag pasteurization valve in

circuit 2
YS_PAS005 "Vlv" Process tag valve pasteurization post-

rinsing

Engineering

The following figure shows schematically the pasteurization device including the overarching connections or SFC accesses
that span the CFC diagram:
EQM_PAS NS_PAS001 YS_PAS001

Valve
EQM_PAS Motor
FbkOpenOut
GrrErr
RdyToStart
RdyToSta
RdyToReset
RdyToRes
FbkCloseOut
Start
Ctrl
AutAct
AutAct
FbkRunOu
Valve
Motor
OpenAut
StartAut
ModLiOp
EQM_PAS StopAut
AutModLi
AutModLi
RstLi
RstLi
ModLipOp
ModLiOp
YS_PAS002
Valve
FbkOpenOut
YS_PAS004 RdyToStart
Valve
RdyToReset
FbkOpenOut
FbkCloseOut
RdyToStart
Ctrl
RdyToReset
AutAct
FbkCloseOut
Ctrl Valve
AutAct OpenAut
ModLiOp
Valve
AutModLi
OpenAut
RstLi
ModLiOp
AutModLi
RstLi YS_PAS003
Valve
FbkOpenOut
YS_PAS005
RdyToStart
Valve
RdyToReset
FbkOpenOut
FbkCloseOut
RdyToStart
Ctrl
RdyToReset
AutAct
FbkCloseOut
Ctrl Valve
AutAct OpenAut
ModLiOp
Valve
AutModLi
OpenAut
RstLi
ModLiOp
AutModLi
RstLi
NS_PAS001
The pump that is activated by the "NS_PAS001" process tag transports the ice cream into the pasteurizer. In the
Application Example, the activation of the process tag occurs through the "EQM_PAS" SFC type instance. Process tag
"NS_PAS001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1

Engineering


process value
(Sim_PAS_NS001\SimFbkRun.Out)

(EQM_PAS\PASTEURIZING.M1_StartAut)

feedback
(Sim_PAS_NS001\SimFbkRun.In)

(NS_PAS001\Intlock.In1)
NOTE When "U.StartAut" and "PASTEURIZING.M1_StartAut" are interconnected, all other interconnections
YS_PAS001
The valve that is activated by the "YS_PAS001" process tag controls the inflow into the pasteurizer. In the Application
Example, the activation of the process tag occurs through the "EQM_PAS" SFC type instance. Process tag "YS_PAS001" is
an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value
(Sim_PAS_YS001\SimFbkClose.In)


process value
(Sim_PAS_YS001\SimFbkClose.InvOut)

Engineering

automatic mode
(EQM_PAS\PASTEURIZING.V1_OpenAut)

(YS_PAS001\Intlock.In1)

feedback
(Sim_PAS_YS001\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "TANK_IN.V1_OpenAut" are interconnected, all other interconnections
between the valve module and the SFC type instances are also created automatically. These are not
YS_PAS002
The valve that is activated by the "YS_PAS002" process tag controls the outflow from the pasteurizer. In the Application
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode


Engineering

feedback
NOTE When "Y.OpenAut" and "PASTEURIZING.V2_OpenAut" are interconnected, all other interconnections
in the above table.
YS_PAS003
The valve that is activated by the "YS_PAS003" process tag controls the pasteurizer in the circuit. In the Application
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode


feedback

Engineering
in the above table.
YS_PAS004
The valve that is activated by the "YS_PAS004" process tag controls the pasteurizer in the circuit. In the Application
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode


feedback
in the above table.
YS_PAS005
The valve that is activated by the "YS_PAS005" process tag controls the discharge of material from the pasteurizer. In the
Application Example, the activation of the process tag occurs through the "EQM_PAS" SFC type instance. Process tag
"YS_PAS005" is an instance of the "Vlv" control module type with the following selected variants:

Engineering
• FbkClose
• FbkOpen
• Intlock


process value


process value

automatic mode


feedback
in the above table.

Engineering
3.5. Technical function and process tags

of the storage tank (Mix Storage)
After pasteurization the storage tanks get the finished ice cream and store it before it is transported to filling via the
freezer. The transport of materials is defined via the recipes in SIMATIC BATCH. This occurs with the aid of batches and
thus it is logged.
1 1
3 5
4 6
1 1
2 2
The "Mix Storage" process image consists of the units "Filling", "Emptying", "Mix Storage 1", and "Mix Storage 2"
Filling consists of the technical functions:
1. Filling of the storage tank
Emptying consists of the technical functions:

2. Emptying of the storage tank
Storage tank 1 consists of the technical functions:

4. Tank management storage tank 1
Storage tank 2 consists of the technical functions:

6. Tank management storage tank 2
Through the identical structure of the units storage tank 1 and storage tank 2 the assignment of the units as parameters is
possible in SIMATIC BATCH.

Engineering
3.5.1. Filling of the storage tank

After pasteurization of the ice cream it is transferred out of the pasteurizer into the storage tank. The activation for this
occurs from SIMATIC BATCH thus is logged. In this regard the valve from the pasteurizer to the storage tanks, as well as
the valve to the drain are opened and the pump is started. Via a sensor the full status of the selected storage tank is
detected, if this status is reached the further filling of the storage tank will be halted and the motor will be stopped.
Setup
The figure below shows the structure for the transfer into the storage tank.
1 1
1 1
The instance of the SFC type "FIL_WAY_CTR" starts the filling process of the storage tank containers.

CMT
EQM_CTR_FIL SFC-Typ "FIL_WAY_CTR" Start the filling of the storage tank

containers
LSH_MST01_001 "MonDi" Process tag for detecting storage tank

1 full
LSH_MST02_001 "MonDi" Process tag for detecting storage tank

2 full
NS_FIL001 "Mot" Process tag for pump drive for filling

the storage tank container
YS_FIL001 "Vlv" Process tag valve storage tank inflow
YS_FIL002 "Vlv" Process tag valve storage tank drain


Engineering
EQM_CTR_FIL NS_FIL001 YS_FIL001

Valve
EQM_CTR_FIL Motor
FbkOpenOut
GrrErr
RdyToSta RdyToStart
RdyToReset
RdyToRes
Start FbkCloseOut
Ctrl
AutAct
FbkRunOu AutAct
Valve
Motor
OpenAut
StartAut
ModLiOp
EQM_CTR_FIL StopAut
AutModLi
AutModLi
RstLi
RstLi
ModLipOp
ModLiOp
YS_FIL002
LSH_MST01_001
Valve
Out FbkOpenOut
RdyToStart
RdyToReset
LSH_MST02_001
FbkCloseOut
Out
Ctrl
AutAct
Valve
OpenAut
ModLiOp
AutModLi
RstLi
LSH_MST01_001
The display process tag "LSH_MBT01_001" is used for detecting and displaying the full status of storage tank 1. Process


(EQM_CTR_FIL\MST01_Active&Full.In1)
LSH_MST02_001
The display process tag "LSH_MST02_001" is used for detecting and displaying the full status of storage tank 2. Process
tag "LSH_MST02_001" is an instance of the "MonDi" CMT with "In" variant selected.

Engineering


(EQM_CTR_FIL\MST01_Active&Full.In1)
NS_FIL001
The pump that is activated by the "NS_FIL001" process tag transports the finished ice cream into the storage tank
containers. In the application example, the activation of the process tag occurs through the "EQM_CTR_FIL" SFC type
instance. Process tag "NS_FIL001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
(Sim_FIL_NS001\SimFbkRun.Out)

(EQM_CTR_FIL\FILLING.M1_StartAut)

feedback
(Sim_FIL_NS001\SimFbkRun.In)

(NS_FIL001\Intlock.In1)
NOTE When "U.StartAut" and "FILLING.M1_StartAut" are interconnected, all other interconnections between
the above table.
YS_FIL001
The valve that is activated by the "YS_FIL001" process tag controls the inflow into the storage tank containers. In the
application example, the activation of the process tag occurs through the "EQM_CTR_FIL" SFC type instance. Process tag
"YS_FIL001" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


process value
(Sim_FIL_YS001\SimFbkClose.In)


process value
(Sim_FIL_YS001\SimFbkClose.InvOut)

automatic mode
(EQM_CTR_FIL\FILLING.V1_OpenAut)

(YS_FIL001\Intlock.In1)

feedback
(Sim_FIL_YS001\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "FILLING.V1_OpenAut" are interconnected, all other interconnections between
above table.
YS_FIL002
The valve that is activated by the "YS_FIL002" process tag controls the supply to the drain when post-rinsing. In the
application example, the activation of the process tag occurs through the "EQM_CTR_FIL" SFC type instance. Process tag
"YS_FIL002" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value

Engineering


process value
(Sim_FIL_YS002\SimFbkClose.InvOut)

automatic mode
(EQM_CTR_FIL\FILLING.V2_OpenAut)

(YS_FIL002\Intlock.In1)

feedback
(Sim_FIL_YS002\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "FILLING.V2_OpenAut" are interconnected, all other interconnections between
above table.

Engineering
3.5.2. Emptying of the storage tank

After storage of the finished ice cream in the storage tank it is transported to the freezer and then to filling. The activation
for this occurs from SIMATIC BATCH thus is logged. In this case the valve from the storage tank to the freezer, as well as
the valve for the water rinsing are opened and the pump is started.
Setup
The figure below shows the structure for the transfer out of the storage tank containers.
2 2
The instance of the SFC type "EMP_WAY_CTR" starts the emptying procedure of the storage tank containers.

CMT
EQM_CTR_EMP SFC-Typ "EMP_WAY_CTR" Start emptying of the storage tank

containers
LSX_EMP001 "MonDi" Process tag for detecting freezer ready
NS_EMP001 "Mot" Process tag for pump drive for

emptying the storage tank
YS_EMP001 "Vlv" Process tag valve storage tank outflow
YS_EMP002 "Vlv" Process tag storage tank valve post-

rinsing


Engineering
EQM_CTR_EMP NS_EMP001 YS_EMP001

Valve
EQM_CTR_EMP Motor
FbkOpenOut
GrrErr
RdyToSta RdyToStart
RdyToReset
RdyToRes
Start FbkCloseOut
AutAct Ctrl
FbkRunOu AutAct
Valve
Motor
OpenAut
StartAut
ModLiOp
EQM_CTR_EMP StopAut
AutModLi
AutModLi
RstLi
RstLi
ModLipOp
ModLiOp
LSX_EMP001 YS_EMP002
Valve
Out
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
Ctrl
AutAct
Valve
OpenAut
ModLiOp
AutModLi
RstLi
LSX_EMP001
The display process tag "LSX_EMP001" is used for detecting and displaying the fill level in the detergent tank. Process tag
"LSX_EMP001" is an instance of the "MonDi" CMT with "In" variant selected.

SimPV_In 1 Interconnection to the simulated

process value

(EQM_CTR_EMP\Hold.In3)

Engineering
NS_EMP001
The pump that is activated by the "NS_EMP001" process tag transports the finished ice cream out of the storage tank
containers. In the application example, the activation of the process tag occurs through the "EQM_CTR_EMP" SFC type
instance. Process tag "NS_EMP001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


value (Sim_EMP_NS001\SimFbkRun.Out)

(EQM_CTR_EMP\EMPYTING.M1_StartAut)

feedback
(Sim_EMP_NS001\SimFbkRun.In)

(NS_EMP001\Intlock.In1)
NOTE When "U.StartAut" and "EMPYTING.M1_StartAut" are interconnected, all other interconnections
YS_EMP001
The valve that is activated by the "YS_EMP001" process tag controls the outflow from the storage tank containers. In the
application example, the activation of the process tag occurs through the "EQM_CTR_EMP" SFC type instance. Process tag
"YS_EMP001" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value
(Sim_EMP_YS001\SimFbkClose.In)

Engineering


process value
(Sim_EMP_YS001\SimFbkClose.InvOut)

automatic mode
(EQM_CTR_EMP\EMPYTING.V1_OpenAut)

(YS_EMP001\Intlock.In1)

feedback
(Sim_EMP_YS001\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "EMPYTING.V1_OpenAut" are interconnected, all other interconnections
in the above table.
YS_EMP002
The valve that is activated by the "YS_EMP002" process tag controls the supply of water for post-rinsing. In the application
example, the activation of the process tag occurs through the "EQM_CTR_EMP" SFC type instance. Process tag
"YS_EMP002" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value


process value
(Sim_EMP_YS002\SimFbkClose.InvOut)

Engineering

automatic mode
(EQM_CTR_EMP\EMPYTING.V2_OpenAut)

(YS_EMP002\Intlock.In1)

feedback
(Sim_EMP_YS002\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "EMPYTING.V2_OpenAut" are interconnected, all other interconnections
in the above table.

Engineering

When filling, emptying, and storing the ingredients in storage tank 1, the stirring process is started. The activation for th is
occurs from SIMATIC BATCH. The agitating process is started from a defined fill level. The agitating process is started from
a defined fill level and runs until the tank has been emptied, thus the agitating process runs in a manner that is batch-
overarching.
Setup
The figure below shows the structure of the agitator of storage tank 1.


CMT
EQM_AGI_MST01 SFC-Typ "TANK_AGI" Starting of the agitating process
LI_MST01_001 "MonAn" Process tag for collecting the fill level

of storage tank 1
NS_MST01_001 "Mot" Process tag for the agitator drive

storage tank 1


Engineering
LI_MST01_001 EQM_AGI_MST01 NS_MST01_001
PV_AH_Ac EQM_AGI_MST01 Motor

GrrErr
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
EQM_AGI_MST01 StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
LI_MST01_001
The display process tag "LI_MST01_001"is used for detecting and displaying the full status of storage tank 1. Process tag
"LI_MST01_001" is an instance of the "MonAn" control module type with the following selected variants:
• PV_In
• PV_Scale


process value
(Sim_MST01_LI001\Lagertank 1.Out)

(EQM_CTR_MST01\TANK_CONTROL.
MAT_AI)
(EQM_AGI_MST01\AGITATOR.LEVEL_AI)

Engineering
NS_MST01_001
The motor that is activated by the "NS_MST01_001" process tag, starts the agitator of the storage tank. In the application
example, the activation of the process tag occurs through the "EQM_AGI_MST01" SFC type instance. Process tag
"NS_MST01_001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
(Sim_MST01_NS001\SimFbkRun.Out)

(EQM_AGI_MST01\AGITATOR.
M1_StartAut)

feedback
(Sim_MST01_NS001\SimFbkRun.In)

(NS_MST01_001\Intlock.In1)
3.5.4. Tank management storage tank 1

After pasteurization of the ice cream it is transferred out of the pasteurizer into storage tank 1 or storage tank 2 and
stored. After storage the finished ice cream is transported out of the storage tank to the freezer and then transported to
the filling. The activation for the filling and emptying of storage tank 1 occurs from SIMATIC BATCH and thus is logged. In
this regard the valve for storage tank 1 as well as the double-seat valve for the filling process or the 2-way valve for the
emptying process is opened.
Setup
The figure below shows the structure of the tank management of storage tank 1.

Engineering
The instance of the "TANK_MGR" SFC type manages the filling and emptying of storage tank 1.

CMT
EQM_AGI_MST01 SFC-Typ "TANK_MGR" Management of storage tank 1
LSL_MST01_001 "MonDi" Process tag for detecting storage tank

1 emptied
TI_MST01_001 "MonAn" Process tag for detecting the fill level

in storage tank 1
YS_MST01_001 "Vlv" Process tag storage tank valve 1
YS_MST01_002 "ValDs" Process tag double-seat valve storage

tank 1
YS_MST01_003 "Val2Way" Process tag 2-way valve storage tank 1

Engineering

The following figure shows schematically the tank equipment including the overarching connections or SFC accesses that
span the CFC diagram:
EQM_CTR_MST01 YS_MST01_001 YS_MST01_002

Valve Valve
EQM_CTR_MST01
FbkOpenOut FbkOpenOut
RdyToStart RdyToStart
RdyToReset RdyToReset
FbkCloseOut FbkCloseOut
Ctrl Ctrl
AutAct AutAct
SLTop
Valve
SLBtm
OpenAut
ModLiOp Valve
EQM_CTR_MST01
AutModLi OpenAut
RstLi StopAut
ModLiOp
AutModLi
LSL_MST01_001
RstLi
Out
SLTopAut
SLBtmAut
TI_MST01_001
PV_Out YS_MST01_003
Valve
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
GrrErr
Pos0
Pos1
Pos2
AutAct
CtrlV0
CtrlV1
CtrlV2
Valve
Pos0Aut
Pos1Aut
Pos2Aut
ModLiOp
AutModLi
RstLi
Fbk0
Fbk1
Fbk2

Engineering
LSL_MST01_001
The display process tag "LSL_MST01_001" is used for detecting and displaying the emptied status of the storage tank 1.
Process tag "LSL_MST01_001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
(Sim_MST_01_LSL001\MST01_full.
InvOut)

EMPTY)
TI_MST01_001
The display process tag "TI_MST01_001" is used for detecting and displaying the temperature in storage tank 1. Process
tag "TI_MST01_001" is an instance of the "MonAn" control module type with the following selected variants:
• PV_In
• PV_Scale


process value

(LIC_MST01_001\Temp_In.SimPV_In)
YS_MST01_001
The valve that is activated by the "YS_MST01_001" process tag controls the inflow and outflow of storage tank 1. In the
application example, the activation of the measuring point occurs through the "EQM_CTR_MST01" SFC type instance.
Process tag "YS_MST01_001" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


Engineering

process value
(Sim_MST01_YS001\SimFbkClose.In)


value
(Sim_MST01_YS001\SimFbkClose.InvOut)

mode
V1_OpenAut)

(YS_MST01_001\Intlock.In1)

feedback
(Sim_MST01_YS001\SimFbkOpen.In)
NOTE When "Y.OpenAut" and "TANK_CONTROL.V1_OpenAut" are interconnected, all other interconnections
in the above table.
YS_MST01_002
The double-seat valve that is activated by the "YS_MST01_002" process tag controls fresh water inflow into the storage
tank 1. In the application example, the activation of the measuring point occurs through the "EQM_CTR_MST01" SFC type
instance. Process tag "YS_MST01_002" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock


process value

Engineering


value

mode
V2_OpenAut)


feedback
in the above table.
YS_MST01_003
The 2-way valve that is tripped by the process tag "YS_MST01_003" controls the rinsing with water at emptying of storage
tank 1. In the application example, the activation of the measuring point occurs through the "EQM_CTR_MST01" SFC type
• FbkOpenV0
• FbkOpenV1
• FbkOpenV2
• Intlock
FbkOpenV0 SimOn Use simulated value


process value
(Sim_MST01_YS003\SimFbkOpenV0.Out)


Engineering

process value


process value
Y Pos0Aut Activation command for position 0 in

automatic mode
V3_Pos0Aut)

CtrlV0 Interconnection for the simulated

feedback V0
(Sim_MST01_YS003\SimFbkOpenV0.In)

feedback V1

feedback V2
SafeV0 1 Safety position for cone V0 is open
DefPos1 6 Definition of the activation of the cones

for Pos1

for Pos2
NOTE When "Y.OpenAut" and "TANK_CONTROL.V3_Pos0Aut" are interconnected, all other interconnections
in the above table.

Engineering

When filling, emptying, and storing the ingredients in storage tank 2, the stirring process is started. The activation for this
occurs from SIMATIC BATCH. The agitating process is started from a defined fill level. The agitating process is started from
a defined fill level and runs until the tank has been emptied, thus the agitating process runs in a manner that is batch-
overarching.
Setup
The figure below shows the structure of the agitator of storage tank 2.
55


CMT
EQM_AGI_MST02 SFC-Typ "TANK_AGI" Starting of the agitating process
LI_MST02_001 "MonAn" Process tag for collecting the fill level

of storage tank 2
NS_MST02_001 "Mot" Process tag for the agitator drive

storage tank 2


Engineering
LI_MST02_001 EQM_AGI_MST02 NS_MST02_001
PV_AH_Ac EQM_AGI_MST02 Motor

GrrErr
RdyToSta
RdyToRes
Start
AutAct
FbkRunOu
Motor
StartAut
EQM_AGI_MST02 StopAut
AutModLi
RstLi
ModLipOp
ModLiOp
LI_MST02_001
The display process tag "LI_MST02_001"is used for detecting and displaying the full status of storage tank 2. Process tag
"LI_MST02_001" is an instance of the "MonAn" control module type with the following selected variants:
• PV_In
• PV_Scale


process value
(Sim_MST02_LI001\Lagertank 2.Out)

MAT_AI)
(EQM_AGI_MST02\AGITATOR.LEVEL_AI)

Engineering
NS_MST02_001
The motor that is activated by the "NS_MST02_001" process tag, starts the agitator of the storage tank. In the application
example, the activation of the process tag occurs through the "EQM_AGI_MST02" SFC type instance. Process tag
"NS_MST02_001" is an instance of the "Mot" control module type with the following selected variants:
• Interlock
• Fbk1


process value
(Sim_MST02_NS001\SimFbkRun.Out)

(EQM_AGI_MST02\AGITATOR.
M1_StartAut)

feedback
(Sim_MST02_NS001\SimFbkRun.In)

(NS_MST02_001\Intlock.In1)

Engineering
3.5.6. Tank management storage tank 2

After pasteurization of the ice cream it is transferred out of the pasteurizer into storage tank 1 or storage tank 2 and
stored. After storage the finished ice cream is transported out of the storage tank to the freezer and then transported to
the filling. The activation for the filling and emptying of storage tank 2 occurs from SIMATIC BATCH and thus is logged. In
this regard the valve for storage tank 1 as well as the double-seat valve for the filling process or the 2-way valve for the
emptying process is opened.
Setup
The figure below shows the structure of the tank management of storage tank 2.
The instance of the "TANK_MGR" SFC type manages the filling and emptying of storage tank 2.

CMT
EQM_AGI_MST02 SFC-Typ "TANK_MGR" Management of storage tank 2
LSL_MST02_001 "MonDi" Process tag for detecting storage tank

2 emptied
TI_MST02_001 "MonAn" Process tag for detecting the fill level

in storage tank 2
YS_MST02_001 "Vlv" Process tag storage tank valve 2
YS_MST02_002 "ValDs" Process tag double-seat valve storage

tank 2
YS_MST02_003 "Val2Way" Process tag 2-way valve storage tank 2

Engineering

The following figure shows schematically the tank equipment including the overarching connections or SFC accesses that
span the CFC diagram:
EQM_CTR_MST02 YS_MST02_001 YS_MST02_002

Valve Valve
EQM_CTR_MST02
FbkOpenOut FbkOpenOut
RdyToStart RdyToStart
RdyToReset RdyToReset
FbkCloseOut FbkCloseOut
Ctrl Ctrl
AutAct AutAct
SLTop
Valve
SLBtm
OpenAut
ModLiOp Valve
EQM_CTR_MST02
AutModLi OpenAut
RstLi StopAut
ModLiOp
AutModLi
LSL_MST02_001
RstLi
Out
SLTopAut
SLBtmAut
TI_MST02_001
PV_Out YS_MST02_003
Valve
FbkOpenOut
RdyToStart
RdyToReset
FbkCloseOut
GrrErr
Pos0
Pos1
Pos2
AutAct
CtrlV0
CtrlV1
CtrlV2
Valve
Pos0Aut
Pos1Aut
Pos2Aut
ModLiOp
AutModLi
RstLi
Fbk0
Fbk1
Fbk2

Engineering
LSL_MST02_001
The display process tag "LSL_MST02_001" is used for detecting and displaying the emptied status of the storage tank 2.
Process tag "LSL_MST02_001" is an instance of the "MonDi" CMT with "In" variant selected.


process value
(Sim_MST_02_LSL001\MST02_full.
InvOut)

EMPTY)
TI_MST02_001
The display process tag "LI_MST02_001" is used for detecting and displaying the temperature in storage tank 2. Process
tag "TI_MST02_001" is an instance of the "MonAn" control module type with the following selected variants:
• PV_In
• PV_Scale


process value

(LIC_MST02_001\Temp_In.SimPV_In)
YS_MST02_001
The valve that is activated by the "YS_MST02_001" process tag controls the inflow and outflow of storage tank 2. In the
application example, the activation of the process tag occurs through the "EQM_CTR_MST02" SFC type instance. Process
tag "YS_MST02_001" is an instance of the "Vlv" control module type with the following selected variants:
• FbkClose
• FbkOpen
• Intlock

Engineering


process value


value

mode
V1_OpenAut)


feedback
in the above table.
YS_MST02_002
The double-seat valve that is activated by the "YS_MST02_002" process tag controls fresh water inflow into the storage
tank 2. In the application example, the activation of the process tag occurs through the "EQM_CTR_MST02" SFC type
• FbkClose
• FbkOpen
• Intlock


Engineering

process value


value

mode
V2_OpenAut)


feedback
in the above table.
YS_MST02_003
The 2-way valve that is tripped by the process tag "YS_MST02_003" controls the rinsing with water at emptying of storage
tank 2. In the application example, the activation of the process tag occurs through the "EQM_CTR_MST02" SFC type
• FbkOpenV0
• FbkOpenV1
• FbkOpenV2
• Intlock


process value


Engineering

process value


process value
Y Pos0Aut Activation command for position 0 in

automatic mode
V3_Pos0Aut)


feedback V0

feedback V1

feedback V2

for Pos1

for Pos2
NOTE When "Y.OpenAut" and "TANK_CONTROL.V3_Pos0Aut" are interconnected, all other interconnections
in the above table.

Engineering
3.6. Sequences
The ice cream plant is configured for batch operation. Within the system there are various SFC type instances with diverse
tasks. According to ISA 88, the SFC-type instance describes the equipment module, additional information concerning ISA
88 is provided in Chapter "4.6 Automation technology". These will be described in the following sections.
The following table provides you with an overview of the SFC types present in the application example.
SFC type Comment
EMP_WAY_CTR Activation of transfer out of the storage tank
EQM_DOS_FLD Activation of the dosing for liquids
EQM_DOS_SLD Activation of dosing for solids
FIL_WAY_CTR Activation of the transfer into storage tank
PASTEUR Activation of the pasteurizer
TANK_AGI Activation of the agitator in the storage tank
TANK_CTR Activation of the path control
TANK_MGR Activation of tank management
TRANS_IN Activation transfer into the mixing system
TRANS_OUT_BUF Activation transfer out of the buffer tank
TRANS_OUT_MIX Activation of transfer out of the mixing system
TRANS_OUT_PRE Activation transfer out of the premixer
3.6.1. EMP_WAY_CTR
The SFC type instance is started by SIMATIC BATCH in the production and opens the valves to the freezer. In the
"WAY_CONTROL" control strategy the valves from the storage tank to the freezer are opened and the pump is started. In
the "WAY_CTR_WATER" control strategy the valves are opened and the pump and a timer are started.
Control strategies
Control strategy Comment
WAYCONTROL
WAY_CRTL_WATER
Setpoints
Setpoint name Data type Connection name Unit Comment
RINSE_TIME REAL RINSE_TIME s

Engineering
Block contacts
Name Block Connection name Comment
V1 Vlvl V1
V2 Vlvl V2
M1 MotL M1
Timer1 BlTimer TIMER1
Sequences
The following sequences are configured in the SFC type "EMP_WAY_CTR":
• WAY_CONTROL
• WAY_CTRL_WATER
• RESUMING
• HOLDING
• COMPLETING_ABORT
WAY_CONTROL
The sequence "WAY_CONTROL" executes the following functions
• Activate automatic mode of valve V1 and open valve V1

• Check for valve V1 open
• Start automatic mode of pump M1, and start pump M1
• Check for pump M1 started
The start conditions for the "WAY_CONTROL" sequence are listed in the following table:
SFC status = Value Logic
RUN = Run
READY_TC = 0 AND
QCS = 1

Engineering
The figure below shows the structure of the "WAY_CONTROL" sequence:
Start
Activate automatic mode of

valve V1 and open valve V1
Way control fromMix Storage

Valve V1
open?
WAY_CONTROL
yes
Start automatic mode of

pump M1, and start pump
M1
Pump M1
started?
yes
End
WAY_CTRL_WATER
The sequence "WAY_CTRL_WATER" executes the following functions:
• Activate automatic mode and open the valves V1 and V2, reset the timer
• Check for valves V1 and V2 open
• Start and stop automatic mode of the pump
• Checking for pump started
• Start timer
• Check for time reached
The start conditions for the "WAY_CTRL_WATER" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 2

Engineering
The figure below shows the structure of the "WAY_CTRL_WATER" sequence:
Start
Activate automatic mode

and open the valves V1 and
V2
Valves V1
and V2
open?
yes
Start and stop automatic
WAY_CTRL_WATER
mode of pump M1
Way control water

Pump M1
started?
yes
Sart timer T1
Time
reached?
yes
End
RESUMING
The "RESUMING" sequence performs the following actions:
• Activate and start automatic mode of pump M1

The start conditions for the "Resuming" sequence are listed in the following table:
RESUMING = Resuming OR
The figure below shows the design of the "RESUMING" sequence:
Start
Activate and start

automatic mode of pump
M1
Resuming the pimp
RESUMING
Pump M1
started?
yes
End
HOLDING
The "HOLDING" sequence executes the following actions:
• Deactivate and stop automatic mode of the M1 pump

• Checking for pump stopped

Engineering
The start conditions for the "HOLDING" sequence are listed in the following table:
HOLDING = Holding OR
The figure below shows the structure of the "HOLDING" sequence:
Start
Deactivate and stop

automatic mode of the M1
pump
Stopping the pump
HOLDING
Pump M1
stopped?
yes
End
COMPL_ABORT
The "COMPL_ABORT" sequence executes the following actions:
• Stop M1 pump
• Close valves V1 and V2
• Check for valves closed
• Deactivate SFC operation of pump M1 and of valves V1 and V2 and reset the timer
The start conditions for the "COMPL_ABORT" sequence are listed in the following table:
ABORTING = Aborting
OR
COMPLETING = Completi

Engineering
The figure below shows the structure of the "COMPL_ABORT" sequence:
Start
Stop pump
Pump
stopped?
Aborting Mix Storage emptying

yes
COMPL_ABORT
Close valves
Valves
closed?
yes
Deactivate SFC operation

of pump M1 and of
valves V1 and V2 and
reset the time
End
3.6.2. EQM_DOS_FLD
The SFC type instance is started by SIMATIC BATCH in the production and doses the liquid ingredients into the mixing
tank.
Control strategies
DOSING
Setpoints
DosingMaterial PI MAT_QTY kg
FineFeed REAL FineFeed kg/min
Coarse REAL Coarse kg/min
Block contacts
DOSE DoseL DOSE

Engineering
M1 MotL M1
V1 VlvL V1 Coarse Valve
V2 VlvL V2 Fine Valve
Sequences
The following sequences are configured in the SFC type "EQM_DOS_FLD":
• DOSING
• RESUMING
• HOLDING
• COMP_ABORT
• Error
DOSING
The "DOSING" sequence executes the following functions
• Activate automatic mode of the dosing

• Checks for dosing in automatic mode
• Reset dosing quantity
• Checks for errors
• Doses up to the prescribed setpoint
• Ends the dosing
The start conditions for the "DOSING" sequence are listed in the following table:
RUN = Run
AND
QCS = 1

Engineering
The figure below shows the structure of the "DOSING" sequence:
Start

the dosing
Dosing in
automatic
mode?
yes
Reset dosing quantity
Dosing liquid materials
DOSING
Is there an
error?
no
Dosing starts
Setpoint
reached?
Stops the dosing
End
RESUMING
The start conditions for the "RESUMING" sequence are listed in the following table:
In this sequence there are neither operations nor conditions.
HOLDING
ERROR
The start conditions for the "ERROR" sequence are listed in the following table:
ERROR = Error AND

Engineering
COMPL_ABORT
• Canceling automatic mode reset the dosing quantity

The start conditions for the "COMP_ABORT" sequence are listed in the following table:
ABORTING = Aborting
OR
Start
Aborting dosing
COMPL_ABORT
Deactivate SFC
operation of dosing
End
3.6.3. EQM_DOS_SLD
The SFC type instance is started by SIMATIC BATCH in the production and doses the solid ingredients into the mixing tank.
Control strategies
DOSING
Setpoints
FineFeed REAL FineFeed kg/min
CoarseFeed REAL CoarseFeed kg/min
Material PI Mat kg

Engineering
Block contacts
DOSE DoseL DOSE
V1 VlvL V1 Coarse Valve
V2 VlvL V2 Fine Valve
Sequences
The following sequences are configured in the SFC type "EQM_DOS_SLD":
• DOSING
• RESUMING
• HOLDING
• Error
DOSING
The "DOSING" sequence executes the following functions
• Activate automatic mode of the dosing

• Checks for dosing in automatic mode
• Reset dosing quantity
• Checks for errors
• Doses up to the prescribed setpoint
• Ends the dosing
The start conditions for the "DOSING" sequence are listed in the following table:
RUN = Run
AND
QCS = 1

Engineering
The figure below shows the structure of the "DOSING" sequence:
Start

the dosing
Dosing in
automatic
mode?
yes
Reset dosing quantity
Dosing of liquid materials
DOSING
Is there an
error?
no
Dosing starts
Is the
setpint
reached?
Dosing stops
End
RESUMING
HOLDING
ERROR
The start conditions for the „ERROR“ sequence are listed in the following table:
ERROR = Error AND

Engineering
COMPL_ABORT
• Canceling automatic mode reset the dosing quantity

ABORTING = Aborting
OR
Start
Aborting dosing
COMPL_ABORT
Deactivate SFC
operation of dosing
End
3.6.4. FIL_WAY_CTR
The SFC type instance is started by SIMATIC BATCH in the production and opens or closes the valves to the storage tank
containers. In the "WAY_CONTROL" control strategy the valves are opened and the pump is started. In the
"WAY_CTR_WATER" control strategy the valves are opened and the pump and a timer are started.
Control strategies
WAYCONTROL
WAY_CRTL_WATER
Setpoints
RINSE_TIME REAL RINSE_TIME s
Block contacts
V1 Vlvl V1

Engineering
V2 Vlvl V2
M1 MotL M1
Timer1 BlTimer TIMER1
Sequences
The following sequences are configured in the SFC type "FIL_WAY_CTR":
• WAY_CONTROL
• WAY_CTRL_WATER
• RESUMING
• HOLDING
WAY_CONTROL
The sequence "WAY_CONTROL" executes the following functions
• Activate and open valve V1

• Check for valve V1 open
The start conditions for the "WAY_CONTROL" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 1

Engineering
The figure below shows the structure of the "WAY_CONTROL" sequence:
Start
Activate and open automatic

mode of valve V1
Control of Mix Storage way

Valve V1
open?
WAY_CONTROL
yes
Activate and start

M1
Pump M1
started?
yes
End
WAY_CTRL_WATER
The sequence "WAY_CTRL_WATER" executes the following functions:
• Activate automatic mode and open the valves V1 and V2, reset the timer
• Check for valve V1 and V2 open
• Start and stop automatic mode of the pump
• Start timer
• Checking for timer end
The start conditions for the "WAY_CTRL_WATER" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 2

Engineering
The figure below shows the structure of the "WAY_CTRL_WATER" sequence:
Start
Activate automatic mode

and open the valves V1 and
V2
Valves V1
and V2
open?
ja
Activate and start

WAY_CTRL_WATER
Control way water
M!
Pump M1
started?
ja
Timer T1 starten
Timer end
reached?
ja
End
RESUMING

Start
Activate and start

Resuming the pump
M1
RESUMING
Pump M1
started?
yes
End

Engineering
HOLDING
• Activate and stop automatic mode of pump M1

Start
Activate and stop automatic

mode of pump M1
Stopping the piump
HOLDING
Pump M1
stopped?
yes
End
COMPL_ABORT
• Stop M1 pump
• Close valves V1 and V2
• Check for valves closed
• Deactivate SFC operation of pump M1 and of valves V1 and V2 and reset the timer
ABORTING = Aborting
OR

Engineering
Start
Stop the pump
Pump
stopped?
Aborting Mix Storage filling

yes
COMPL_ABORT
Close vavles
Vavles
closed?
yes
Deactivate SFC operation

of pump M1 and of
valves V1 and V2 and
reset the timer
End
3.6.5. PASTEUR
The SFC type instance is started by SIMATIC BATCH in the production and starts the pasteurization of the ingredients from
the buffer tank. In the Control strategy "PAST_ACTIV" the ingredients are pasteurized. The pasteurization in the circuit is
operated in the "PAST_CIRC" control strategy. In the Control strategy "PAST_PUSH" all valves are opened, so that the
material can be forced out.
Control strategies
PAST_ACTIV Pasteurization is running
PAST_CIRC Material circulation active
WATER_PUSH_COM Force the material out of the pasteurizer and the

circulation line.
WATER_PUSH Push material out of the pasteurizer
Setpoints
TIME_STEP REAL TIME_STEP sec

Engineering
Block contacts
V1 VlvL V1
V2 VlvL V2
V3 VlvL V3
V4 VlvL V4
V5 VlvL V5
M1 MotL M1
T1 BlTimer T1
Sequences
The following sequences are configured in the SFC type "TANK_AGI":
• PAST_ACTIV
• PAST_CIRC
• WATER_PUSH_COM
• WATER_PUSH
• RESUMING
• HOLDING
PAST_ACTIV
The "PAST_ACTIV" sequence executes the following actions:
• Activate automatic mode of valves V1, V2, V3, V4, V5 and the pump M1, reset the timer, open valves V1 and V2, start
pump M1
• Check for valves V1, V2, open and motor M1 started
The start conditions for the "PAST_ACTIVE" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 1

Engineering
The figure below shows the design of the "PAST_ACTIV" sequence:
Start

valves V1, V2, V3, V4, V5
and the pump M1, reset the
timer, open valves V1 and
Control of pasteurizing
V2, start pump M1
PAST_ACTIV
Valves V1,
V2 open and
motor M1
started?
yes
End
PAST_CIRC
The "PAST_CIRC" sequence executes the following actions:
motor M1
The start conditions for the "PAST_CIRC" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 2
The figure below shows the structure of the "PAST_CIRC" sequence:
Start

Circulated pasteurizing
V4, start motor M1

PAST_CIRC
Valves V3,
V4 open and
motor M1
started?
yes
End
WATER_PUSH_COM
The sequence "WATER_PUSH_COM" executes the following functions:
• Activate automatic mode of valves V1, V2, V3, V4, V5, and the pump M1, reset the timer, open valves V1, V2, V3, V4,
and V5 start pump M1

Engineering
• Check for V1, V2, V3, V4, V5 open and motor M1 started
• Start timer
• Close valves V1, V2, V3, V4, and V5, stop motor M1 and timer
The start conditions for the "WATER_PUSH_COM" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 3
The figure below shows the structure of the "WATER_PUSH_COM" sequence:
Start

valves V1, V2, V3, V4, V5,
timer, open valves V1, V2,
V3, V4, and V5 start pump
M1
Ventile V1,
V2, V3, V4
and V5 open
and motor
WATER_PUSH_COM
M1 started? Psuhing material out
yes
Start timer
Time
reached?
yes
lose valves V1, V2, V3, V4,

and V5, stop motor M1 and
timer
End
WATER_PUSH
The sequence "WATER_PUSH" executes the following functions:
• Activate automatic mode of valves V1, V2, V3, V4, V5 and the pump M1, reset the timer, open valves V1, V2, and V5,
start pump M1
• Check for valves V1, V2, V5 open and motor M1 started
• Start timer
• Close valves V1, V2, and V5, stop motor M1 and timer
The start conditions for the "WATER_PUSH" sequence are listed in the following table:
RUN = Run AND

Engineering
READY_TC = 0
QCS = 3
The figure below shows the structure of the "WATER_PUSH" sequence:
Start

timer, open valves V1, V2,
and V5, start pump M1
Valves V1,
V2, V5 open
and motor
Pushing material out

M1 started?
WATER_PUSH
yes
Start timer
Time
reached?
yes
Close valves V1, V2, and V5,

stop motor M1 and timer
End
RESUMING
pump M1

Engineering
Start

V2, start pump M1
Resuming pasteurizing
RESUMING
Valves V1,
V2, open
and motor
M1 started?
yes
End
HOLDING
• Take valves V1, V2, V3, V4, V5 and the motor M1, reset the timer, open valves V3 and V4, start motor M1 and reset
timer
Start
Take valves V1, V2, V3, V4,

V5 and the motor M1, reset
the timer, open valves V3
and V4, start motor M1 and
reset timer
Holding pasteurization
HOLDING
Valves V3,
V4, open
and motor
M1 started?
yes
End
COMPL_ABORT
The "COMPLETING_ABORT" sequence performs the following actions:
• Close valves V1, V2, V3, V4, and V5, stop motor M1, reset timer, take valves V1, V2, V3, V4, V5, and take motor M1
out of automatic mode
• Check for timer reset

Engineering
ABORTING = Aborting
OR
Start
Close valves V1, V2, V3, V4,

and V5, stop motor M1,
reset timer, take valves V1,
V2, V3, V4, V5, and take
Completing pasteurization
motor M1 out of automatic
mode
COMPL_ABORT
Timer reset?
yes
End
3.6.6. TANK_AGI
The SFC type instance is started by SIMATIC BATCH in the production and starts the stirring process in the buffer tank.
Control strategies
FILLING
STORAGE
EMPTYING
Setpoints
LEVEL REAL LEVEL l
Block contacts
M1 MotL M1

Engineering
Sequences
The following sequences are configured in the SFC type "TANK_AGI":
• FILLING
• STORAGE
• EMPTYING
• HOLDING
• ABORT_COMP
FILLING
The "FILLING" sequence executes the following actions:
• Check whether the fill level has reached the setpoint

• Put motor M1 in automatic mode and start
• Check for motor M1 started
The start conditions for the "FILLING" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 1
The figure below shows the structure of the "FILLING" sequence:
Start
Fill level >

setpoint
Starting the mix procedure during filling
yes
FILLING
Put motor M1 in automatic

mode and start
Motor M1
started?
yes
End
STORAGE
The "STORAGE" sequence executes the following functions

The start conditions for the "STORAGE" sequence are listed in the following table:

Engineering
RUN = Run
READY_TC = 0 AND
QCS = 2
The figure below shows the structure of the "STORAGE" sequence:
Start
Fill level >

setpint
Starting the mix procedure during storage

yes
STORAGE
mode and start
Motor M1
started?
yes
Ende
EMPTYING
The "EMPTYING" sequence executes the following actions.

The start conditions for the "EMPTYING" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 2

Engineering
The figure below shows the structure of the "EMPTYING" sequence:
Start
Fill level >

Setpoint
Starting the mixing procedure during emptying

yes
EMPTYING
mode and start
Motor M1
started?
yes
End
HOLDING
COMPL_ABORT
• Stop motor M1 and take it out of automatic mode

• Check for motor M1 stopped
ABORTING = Aborting
OR

Engineering
Start
Close valves V1, V2, V3, V4,

and V5, stop motor M1
stoppen, reset timer
Take valves V1, V2, V3, V4,
Ending mixing procedure

V5 and motor M1 out of
automatic mode
COMPL_ABORT
Timer reset?
yes
End
3.6.7. TANK_CTR
The SFC type instance is started by SIMATIC BATCH in the production and starts the filling and the emptying of the storage
tank.
Control strategies
FILLING
STORAGE
EMPTYING
Setpoints
LEVEL REAL LEVEL l
STORAGE_TIME REAL STO_TIME h
RunOutTime REAL RunTime sec
Prozesswerte
Name Data type Connection name Comment
EMPTY BOOL EMPTY

Engineering
Steuerwerte
STATUS BOOL STATUS
Block contacts
V1 VlvL V1
V2 VlvDS V2
V3 Vlv2WayL V3
ST_TIMER BlTimer ST_TIMER
T1 BlTimer T1
Sequences
The following sequences are configured in the SFC type "TANK_CTR":
• FILLING
• STORAGE
• EMPTYING
• HOLDING
• RESUMING
• ABORT_COMP
FILLING
The "FILLING" sequence executes the following actions:
• Take valves V1 and V2 into automatic mode

• Check for automatic mode of valves V1 and V2 active
• Open valves V1 and V2
• Checks for valves V1 and V2 opened
The start conditions for the "FILLING" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 1

Engineering
The figure below shows the structure of the "FILLING" sequence:
Start
Take valves V1 and V2

into automatic mode
Valves V1
and V2 in
Filling Mix Storage

automatic
mode?
FILLING
yes
Open valves V1 and V2
Pump
M1
started?
jyes
End
STORAGE
The "STORAGE" sequence executes the following functions
• Reset and start timer T1

• Check for timer end reached
The start conditions for the "STORAGE" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 2
The figure below shows the structure of the "STORAGE" sequence:
Start
Reset and start timer T1

Completing pasteurization
STOARGE
Timer end
reached
yes
End
EMPTYING
The "EMPTYING" sequence executes the following actions.
• Take valves V1 and V3 into automatic mode

• Check for automatic mode of valves V1 and V3 active
• Open valves V1 and V3 and move into Pos1
• Check for valves V1 open and valve in Pos1
The start conditions for the "EMPTYING" sequence are listed in the following table:

Engineering
RUN = Run
READY_TC = 0 AND
QCS = 3
The figure below shows the structure of the "EMPTYING" sequence:
Start
Take valves V1 and

V2 into automatic
mode
Valves V1
and V2 in
automatic
mode?
yes
Open valve V2 and
Mix Storage entleeren

move valve V1 into
PS 3
EMPTYING
Valve V2
open and
valve V3 in
PS 3?
yes
Start Timer T1
Timer end
reached?
yes
End
HOLDING
RESUMING
COMPL_ABORT
• Close valves V1, V2, and V3 and reset timer T1

Engineering
• Check for valves V1, V2, and V3 closed

• Take valves V1, V2, and V3 out of automatic mode
ABORTING = Aborting
OR
Start
Close valves V1, V2, and V3

and reset timer T1
Tankmanagend Mix Storage abschließen
COMPL_ABORT
Valves V1, V2,
and V3
closed?
Valves V1, V2, and V3 out of

automatic mode
yes
End
3.6.8. TRANS_IN
The SFC type instance is started by SIMATIC BATCH in the production and opens the valves from the premixer to the main
mixer.
Control strategies
TRANS_IN
Block contacts
V1 VlvL V1
Sequences
The following sequences are configured in the SFC type "TRANS_IN":
• TRANSFER
• RESUMING
• HOLDING
• COMPL_ABORT

Engineering
TRANSFER
The "Transfer" sequence executes the following actions:
• Activate automatic mode of valve V1 and open

• Check for valve V1 opened
The start conditions for the "TRANSFER" sequence are listed in the following table:
RUN = Run
READY_TC = 0 AND
QCS = 1
The figure below shows the structure of the "TRANSFER" sequence:
Start
Starte Transfer von Premixer in Mainmixer

valve V1 and
TRANSFER
Valve V1
open?
yes
End
RESUMING
HOLDING
COMPL_ABORT
• Close valve V1 and deactivate SFC operation

ABORTING = Aborting OR

Engineering
Start
Transfer beenden
COMPL_ABORT
Close valve V1 and
deactivate SFC
operation
End
3.6.9. TRANS_OUT_BUF
The SFC type instance is started by SIMATIC BATCH in the production and starts the transfer out of the buffer tank.
Control strategies
TRANSFER
Setpoints
Prozesswerte
EMPTY BOOL EMPTY
Block contacts
V1 VlvL V1
T1 BlTimer T1

Engineering
Sequences
The following sequences are configured in the SFC type "TRANS_OUT_BUF":
• TRANSFER
• RESUMING
• HOLDING
• COMPL_ABORT
TRANSFER
The "TRANSFER" sequence executes the following actions:
• Activate automatic mode of valve V1 and open the valve, start timer
• Check for containers empty and time reached
• Activate closing of valve V1 and automatic mode
• Check for valve V1 closed
RUN = Run
READY_TC = 0 AND
QCS = 1
Start

valve V1 and open,
start timer
Container
empty and
Starte Transfer aus dem Buffer
time
reached?
TRANSFER
yes
Close valve V1 and

deactivate automatic mode
Valve V1
closed?
yes
End
HOLDING

Engineering
RESUMING
COMPL_ABORT
• Close valve V1 and deactivate SFC operation

• Check for valve V1 closed
ABORTING = Aborting
OR
Start
Close valve V1 and

deactivate SFC operation
Transfer beendem
COMPL_ABORT
Valve V1
closed?
yes
End
3.6.10. TRANS_OUT_MIX
The SFC type instance is started by SIMATIC BATCH in the production and starts the transfer out of the main mixer.
Control strategies
Transfer

Engineering
Setpoints
Prozesswerte
EMPTY BOOL EMPTY
Block contacts
M1 MotL M1
T1 BlTimer T1
Sequences
The following sequences are configured in the SFC type "TRANS_OUT_MIX":
• TRANSFER
• RESUMING
• HOLDING
• COMPL_ABORT
TRANSFER

• Start timer
• Check for containers empty and time reached
• Stop M1 pump
RUN = Run
READY_TC = 0 AND
QCS = 2

Engineering
Start
Activate and start

M1
Pump M1
started?
yes
Transfer aus dem Mixer

Start timer
TRANSFER
Container
empty and
time
reached?
yes
Stop pump M1
Pump
stopped?
yes
End
RESUMING

Start
Activate and start

Wiederanlauf der Pumpe
M1
RESUMING
Pump M1
started?
yes
End
HOLDING
• Deactivate and stop automatic mode of the M1 pump

Engineering

Start
Deactivate and stop

automatic mode of
pump M1
Stoppen der Pumpe
HOLDING
Pump M1
stopped?
yes
End
COMPL_ABORT
• Deactivate and stop automatic mode of the M1 pump, reset timer

ABORTING = Aborting
OR
Start
Deactivate automatic mode

of pump M1 and stop,
reset timer
Transfer abschließen
COMPL_ABORT
Pump M1
stopped?
yes
End
3.6.11. TRANS_OUT_PRE
The SFC type instance is started by SIMATIC BATCH in the production and starts the transfer out of the premixer.

Engineering
Control strategies
Transfer
Setpoints
Prozesswerte
EMPTY BOOL EMPTY
Block contacts
T1 BlTimer T1
Sequences
The following sequences are configured in the SFC type "TRANS_OUT_PRE":
• TRANSFER
• RESUMING
• HOLDING
• COMPL_ABORT
TRANSFER
• Start timer
• Check for tank empty and time reached
RUN = Run
READY_TC = 0 AND
QCS = 1

Engineering
Start
Starte Transfer aus dem Premixer

Start timer
TRANSFER
Tank
empty and
time
reached?
yes
End
HOLDING
RESUMING
COMPL_ABORT
• Reset timer
ABORTING = Aborting
OR

Engineering
Start
Transfer beenden
COMPL_ABORT
Reset timer
End

Engineering
3.7. SIMATIC BATCH

SIMATIC BATCH is used for production of batches. Batch processes are processes for the temporally limited production of
products in allocated equipment modules (units) with defined raw materials and workflow specifications. Control recipes
provide the information as to how different plant sections participating in the processes must be integrated. Control of
the batch processes is described in the industry standards, such as ISA S88, other information in this regard is provided in
chapter "4.6 Automation technology". The recipes can also be modified by operating personnel. The complete recipe
procedure with messages and measured values, as well as the operator interventions, is logged.
In this unit template a recipe for the production of the product is used, and two others are used for the material
replacement between the plant sections.
NOTE The recipes must be understood as a reference point and they may have to be modified for use on real
plants.
3.7.1. Production recipe "ICE CREAM MIX"

The production recipe is for intermittent dosing of ingredients of ice cream.
Information contained in the recipe

The production recipe can contain the following information:
• Plant section to be used

• The dosing quantities of the ingredients
Different production recipes can be created for the plant section. These differ in the above-mentioned points. For example
the differences depend on the type of ice cream and occupied plant sections, that are occupied by ice cream previously
produced in the plant.
Structure of an example recipe

The sample production recipe "ICE CREAM MIX" in the "Ice Cream Plant" application example is for the dosing and
intermediate storage of the chocolate ice cream in the buffer tank. It consists of the partial recipe procedures (PRPs)
"Premix", "Mixer", and "MBT_XX". The assignment of which buffer tank is used, can be selected as parameter when
creating the material parameters and production parameters (formula). For this, when creating a recipe the available
plant sections can be selected and all common technical functions can be used for recipe control. The implementation for
selection of the occupied plant unit is presented in the following figure.

Engineering
The table below lists the PRPs of the "ICE CREAM MIX" production recipes:
PRP Occupied plant section
Premix PMX
Mixer MMX
MBT_XX <alle>
Different recipe operations (ROP) exist for PRP. The names of the recipe operations correspond to the actual production
phase. The recipe functions (RFs) are called up within the ROPs.
The table below lists the RFs of the "ICE CREAM MIX" production recipe:
TRP ROP RF Control strategy
Premix Dosificar WHEYPOWDER DOSING
CACAO DOSING
CANESUGAR DOSING
Transfer out TRANSFER_OUT TRANSFER
Mixer Vacuum&Dosing VACUUM VACUUM
WATER DOSING
Transfer in TRANSFER_IN TRANS_IN

Engineering
Dosing MILK DOSING
REQORK DOSING
Transfer to buffer tank TRANSFER_OUT TRANSFER
TRANSFER_IN TRANS_IN
AGITATOR FILLING
There are synchronization lines between the ROPs so that the process runs synchronously in the PRPs. There is an NOP
step at the end of the recipe. This is necessary so that the last two ROPs will also run synchronously with one another.
The figure below shows the structure of the "ICE CREAM MIX" production recipe contained in the "Ice Cream Plant"
application example:
The stirring process in the selected buffer tank that is started in the production recipe, remains active until the buffer tank
has been emptied. Emptying of the buffer tank is started through the transfer recipe "PASTEURIZING".
3.7.2. Transfer recipe "PASTEURIZING"

The transfer recipe is used for intermittent pasteurization of ice cream.

The following information can be contained in the transfer recipe:

Engineering
Plant section to be used
• The shut-off delay after the tank is empty

• The duration of the post-rinsing with water
Different transfer recipes can be created for the plant section. These differ in the above-mentioned points. For example

The sample "PASTEURIZING" recipe in the "Ice Cream Plant" application example is for pasteurization and subsequent
storage of ice cream in the storage tank. It consists of the unit recipe procedures (PRP) "MBT_XX", "Pasteur", "Filling", and
"MST_XX". The assignment of which buffer tank and which storage tank are used, can be selected as parameters when
creating the material and production parameters (formula). For this, when creating a recipe the available plant sections
can be selected and all common technical functions can be used for recipe control.
The table below lists the PRPs of the "ICE CREAM MIX" production recipes:
TRP Occupied plant section
MBT_XX <all>
Pasteur Pasteurizer
Filling FIL
MST_XX <all>
The table below lists the RFs of the "PASTEURIZING" transfer recipe:
MBT_XX Transfer to MST TRANSFER_OUT TRANSFER
AGITATOR EMPTYING
Pasteur Pasteurise PASTEURIZING PAST_ACTIV
Water PASTEURIZING PAST_PUSH
Water PASTEURIZING PAST_PUSH
Filling Push out water FILLING WAYCONTROL_WATER
Filling MSTXX FILLING WAYCONTROL
Water to drain FILLING WAYCONTROL_WATER
MST_XX Filling TANK_CONTROL FILLING
AGITATOR FILLING
Storage AGITATOR FILLING

Engineering
NOTE The transfer recipe "PASTEURIZING" does not result in a cleaning of the selected buffer tank.
There are synchronization lines between the ROPs so that the process runs synchronously in the PRPs. There is an NOP
step at the end of the recipe. This is necessary so that the last two ROPs will also run synchronously with one another.
The figure below describes the structure of the transfer recipe "PASTEURIZING" contained in the "Ice Cream Plant"
application example:
The stirring process in the selected buffer tank that is started in the transfer recipe, remains active until the storage tank
has been emptied. Emptying of the storage tank is started through the transfer recipe "EMPTYING TO FREEZER".
The duration of the re-flushing with water in the two ROPs "Water into Drain" and "Water to Drain" is synchronized so that
length of re-flushing duration is set in the ROP "Water into Drain" and is applied for the ROP "Water to Drain". To do this,
the parameter that serves as template is selected as target, as shown in the figure below. The parameter that must be
synchronized to do this, is defined as source, in the same manner.
3.7.3. Transfer recipe "EMPTYING TO FREEZER"

The transfer recipe is used for intermittent transport of the ice cream from the storage tank to the freezer.

Engineering

The following information can be contained in the transfer recipe:
• Plant section to be used

• The shut-off delay after the tank is empty
• The duration of the post-rinsing with water
Different transport recipes can be created for the plant section. These differ in the above-mentioned points. For example

The sample transfer recipe "EMPTING TO FREEZER" in the "Ice Cream Plant" application example is for the emptying of the
storage tank and subsequent transport to the freezer. It consists of the partial recipe procedures unit (PRP) "MST_XX" and
"Emptying". The assignment of which buffer tank is used, can be selected as parameter when creating the material
parameters and production parameters (formula). For this, when creating a recipe the available plant sections can be
selected and all common technical functions can be used for recipe control. The implementation for selection of the
occupied plant unit is presented in the following figure.
The table below lists the PRPs of the "EMPTYING TO FREEZER" cleaning recipe:
TRP Occupied plant section
MST_XX <all>
Emptying EMP
The table below lists the RFs of the "EMPTYING TO FREEZER" transfer recipe:
MST_XX Emptying TANK_CONTROL EMPTYING
AGITATOR EMPTYING
Emptying Transfer from MSTXX EMPTYING WAYCONTROL
Flushing EMPTYING WAYCONTROL_WATER
NOTE The transfer recipe "EMPTYING TO FREEZER" does not result in a cleaning of the selected buffer tank.
There are synchronization lines between the ROPs so that the process runs synchronously in the PRPs.
The figure below describes the structure of the transfer recipe "EMPTYING TO FREEZER” contained in the "Ice Cream Plant"
application:

Engineering
3.7.4. Batches
The batches are created as a job in SIMATIC BATCH. The recipe for production or transfer is defined when the batch is
created.
Thus it is possible to start the production batch automatically immediately at the end of a cleaning batch. Thus it can be
detected that after the transfer of a preceding batch the occupied plant section can be used for the subsequent
production.

Useful information
4. Useful information
4.1. Basics
4.1.1. Description of the individual functions
The individual parts of an ice cream plant are described below. The entry point is the process image of the visualization
screen.
1
2
3
4
The process image of the ice cream plant consists of the following plant sections:
1. Mixing system (Mixing)
2. Buffer tank (Mix Buffer)
3. Pasteurizer
4. Storage tank (Mix Storage)
1. Mixing system
The mixing system is used for dosing and mixing of the ingredients. At dosing, the solid ingredients, such as cocoa or
cane sugar, are first dosed in the premixer (premixer). After dosing the solid ingredients, the solid ingredients are
conveyed into the main mix, where the liquid ingredients have already been dosed.
2. Buffer tank
In the buffer tank the finished dosed ingredients for pasteurization are stored. The tanks can be filled until they are full.
During filling, emptying, and storage a fill-level dependent start of the stirring process is possible.
3. Pasteurizer
The ice cream is continuously pumped through the pasteurizer, in this process it is heated to a defined temperature and
held at this temperature. If the intermediate tank is empty or the pasteurization is aborted, the ice cream will be forced
out of the pasteurizer with water. Thereafter the finished product is pumped into one of the storage tanks.
4. Storage tank
The storage tank gets the finished ice cream after the pasteurization process, to do this valves in the inflow and to the
channel are opened and the pump in the inflow is started. In addition the double-seat valve and valve for the selected
container will be opened. The tanks can be filled until they are full.
During filling, emptying, and storage a fill-level dependent start of the stirring process is possible.

Useful information
With the emptying process of a tank the valve of the selected tank is opened and the 2-way valve is opened so that an
emptying of the tank is enabled. Moreover, at emptying of the valves to the freezer and to the fresh water will be opened
and the pump to the freezer will be started. The emptying process will be stopped as soon as the freezer no longer
carriers the "good" status.
Advantages of this solution

• A reduction of the knowledge necessary to develop applications
• A reduction in the configuration effort
• More flexible structure and adaptation due to technical functions
• Standardized structures
4.1.2. PI process flow diagrams

The figure below shows the PI flow diagram for the plant unit "Mixing" of the ice cream system. The process tags that are
contained in the project have been entered.
Kandiszucker Molkenprotein Kakao Wasser Milch Öl Nachbesserung
FIC FIC FIC

PMX001 PMX002 PMX003
NS NS NS NS
MMX001 MMX002 MMX003 MMX004
YS YS YS
FIC FIC FIC FIC
YS YS YS MMX001 MMX002 MMX003 MMX004
YS YS YS YS
YS YS YS YS
Premixer
LSH
MMX001
LSL
PMX001 YS Mainmixer
MMX020
LI
MMX001
LSL
MMX001
Mix Buffer
NS
MMX021
The figure below shows the PI flow diagram for the plant unit "Mix Buffer" of the ice cream system. The process tags that
are contained in the project have been entered.

Useful information
Mainmixer
YS YS
MBT01_004 MBT02_004
LSH LSH
MBT01_001 MBT02_001
Mix Buffer 1 Mix Buffer 2
NS NS
M M
MBT01_001 MBT02_001
LSL LSL
MBT01_001 MBT02_001
YS YS
MBT01_001 MBT02_001
Pasteurisierer
The figure below shows the PI flow diagram for the plant unit "Pasteurizer" of the ice cream system. The process tags that
YS YS
PAS003 PAS004
Wasser
YS YS
YS PAS001 PAS002
PAS005
Mix Buffer Pasteurisierer Mix Storage
NS
PAS001
The figure below shows the PI flow diagram for the plant unit "Mix Storage" of the ice cream system. The process tags that

Useful information
NS NS
MST01_001 MST02_001
LSH LSH
MST01_001 MST02_001
LI LI
MST01_001 M MST02_001 M
Mix Storage 1 Mix Storage 2

LSL LSL
MST01_001 MST02_001
YS YS YS YS YS
FIL002 FIL001 MST01_001 MST02_001 FIL001
Pasteurisierer
LSX
YS YS EMP001 Kanal
MST01_002 MST02_002
YS YS YS
EMP002 EMP001 EMP001
Wasser Gefrierer
YS YS
MST01_003 MST02_003

Useful information
4.2. Process engineering

With the ice cream plant the different ingredients are dosed in a specific mixing ratio. The ingredients are held in the
buffer tank before they are heated in the pasteurizer. After pasteurization the finished ice cream is stored in the storage
tanks. The ice cream is transported to filling via the freezer.

Useful information
4.3. Report function

In addition to the sample project, the "Mix Plant" ice cream plant includes the "Reports" process picture, this image offers
fast access from the WinCC Runtime to the filing of the reports. The following figure shows the overview screen.
SIMATIC BATCH provides a report for all types of batches. This represents all objects that can occur in a batch with a flat or
hierarchical recipe structure. Often however, the information contained in the report can be very extensive and only
needed in part in specific applications.
The zip file "109755537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip", in addition to the sample project and the batch
backup, also includes the file "FuBTEMPLATE4Batch_batch.rdl". This file is a reporting template based on the Microsoft
Reporting Services that creates an optimized report. This template enables the situation that only the selected batch data
is displayed, in which the prefixes of the batches are evaluated. Consequently for the "Ice Cream Mix" production batches,
the prefix "Mix", and for the transfer batches "Emptying to Freezer" and "Pasteurizing" the prefix "Tra" must be put in front.
If the unit template "Cleaning in Place" is also integrated in the project, here the prefix "CIP" can be prefixed. This
generates a sample cleaning report.
NOTE Additional information on how you can upload the reporting template and or on the parameterization
and generation of your own report templates is in the article "Configuring SIMATIC BATCH Reports on
the Practical Example" under the following link:
In the two following figures the standard report is compared with the provided "Fubtemplate4batch" report template on
the specific application.
Standard report
The figure below shows the fourth page of the standard report of the "ICE CREAM MIX" production batch. For the standard
report all recipe elements that were executed in this batch, will be listed in the report. This includes for example, the
dosing of cane sugar and the recipe functions that were used for dosing the ingredients. Through the quantity of different
information the length of the report is 14 pages.

Useful information
Report template "Fubtemplate4batch"

With the provided "Fubtemplate4batch" report template an example is shown how a report adapted for the application
can be created. Through the selective omission of the non-relevant information the length of the report can be reduced to
five pages. An additional advantage of the provided report template is the summary of the most important information,
such as setpoints and actual values, on the first page Thus the most important information is presented at a glance. The
other pages of the report are also more clearly organized, as shown in the in the following figure.

Useful information
4.4. Extension by Clean in Place

The application example is modularly structured and can be extended with additional modules as needed, e.g. a Cleaning
In Place. Instructions for how you can combine the plant units are described in Chapter 4.5 "Integrating the unit template
in the user project".
The term "Cleaning in Place", or CIP for short, designates a procedure that is used in the process industry for cleaning plant
sections. The advantage of the process is that the cleaning takes place locally directly on the plant section, without it
having to be dismantled.
A separate plant section is added to the plant for the CIP process. The cleaning fluid is prepared and stored here. The plant
sections to be cleaned are designed so that they can be connected to the CIP plant section. The CIP plant section is
positioned so that the paths to the plant sections to be cleaned are as short as possible.
An appropriate example is provided in the article "PCS 7 Unit Template CIP – Cleaning in Place" via the following link:

Useful information
4.5. Integrating the unit template in the

user project
4.5.1. Preparation
1. Copy the "10955537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip" on the configuration computer, and then open
SIMATIC Manager.
2. In the menu bar click "File > Retrieve" and select the file "10955537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip". Then
click "Open" to confirm.
3. Select the folder in which the project will be saved and confirm with the "OK" button.
The project will be extracted.
4. In the "Retrieve" dialog, click the "OK" button and then click "Yes" in the dialog to open the project.
5. Go to the "Plant View".
6. In parallel open the project in which the unit template must be integrated.
4.5.2. Copying templates
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.
1. Go to the plant view.

2. Copy the folder containing the CMTs from the master data library and paste it into the target project.
3. Copy the listings from the master data library and paste them into the target project.

Useful information
4.5.3. Copying units

1. Copy the hierarchy folder "IC Production" from the AS project of the unit template to the plant view of the target
project.
2. Likewise copy the process images "Overview_Mixplant", "Mixing", "Puffertank", "Pasteurizer", and "Storage Tank "from
the OS project of the unit template into the plant view of the unit template.
NOTE When copying the process screens, make sure that you copy the images to the hierarchy level of the
target project, which is configured as an OS area.

Useful information
4.5.4. Adapting the OS project

In order to facilitate the changing of colors in the process picture template at a central point, a central color palette was
created in the OS project of the Unit Template. To display these colors in the process screen of your own project, you must
import the relevant color palette.
1. Select "OS(1)" in WinCC Explorer and choose "Project Properties" in the context menu.
2. Choose the "User Interface and Design" tab and click the "Edit" button.
3. Import the palette into your own project by means of the "Overwrite" option. The color palette is located in the project
folder of the unit template at the path: "<project path> \UT_ICD\UT_ICD_O\wincproj\OS(1)\GraCS
UnitTemplate.xml>". All existing colors will be replaced.
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.

Useful information
4.6. Automation technology

The "unit" concept
In this application example, the "IC Production" plant section can be regarded as a unit.
The term "unit" means a unit in process-related plants (plant section, apparatus, machines) including the sensors,
actuators and the assigned automation software that is frequently required in this configuration of components. The unit
as a "Type" is used as a template for generating many different programmable instances.
ISA-88
The application example is configured in accordance with the ISA-S88 standard. The standard describes a process with
reference to the equipment available (physical model), the defined technical process (process model) and the equipment
that is used to produce a batch (procedural control model).
The figure below shows the structure of the ISA S88 standard.
NOTE You will find detailed information on ISA-S88.01 in the manual entitled "PCS 7 SIMATIC BATCH V9.1
SP2 Process Control System", in the chapter entitled "Technological basics complying with ISA-88.01".
You will find this manual at the following link:

Useful information
4.7. Project structure

4.7.1. CFC chart naming convention
A uniform naming convention has been used for identifying the measurement points - the function is named according to
the European standard EN 62424. The following figure shows the composition of a process tag name:
LIC_MST01_001
Function Name
L = level (first letter)
I = indication (subsequent letter)
C = control (subsequent letter)
The following table contains the letters used in the application and their meanings:
First letter Meaning
F Flow
L Level
N Motor
P Pressure
Q Master value
S Speed (velocity, rotational speed, frequency)
T Temperature
X Freely selectable first letter
Y Control valve
Subsequent letter Meaning
C Control
F Fraction
I Indication
S Switching (binary control function or switching function

non-safety-related)
T Monitoring (transmitter, analog value processing)
H High (top)
L Low (bottom)

Useful information
4.7.2. Plant view

The plant view of the application example "Ice Cream Plant" is configured in accordance with ISA S88.01.

Useful information
AS Project
In the AS project "UT_IC_AS", the first technology level "IC Production" is defined as plant and it contains the neutral
hierarchy folder:
• "Mix Plant" contains the hierarchy folders defined as unit "Mix Buffer", "Mix Storage", "Mixing", and "Pasteurizer".
• "BATCH OS Controls" does not contain any other objects
• "Simulation" contains the simulation plans for the application example
The plant unit "Mix Buffer" contains the subordinate plant unit "MBT_01" and "MBT_02" The two subordinate units are
structured identically and each have the CFC plan "MBT0X_Unit" with the "UNIT_PLC" block and the hierarchy folder for
the equipment modules "MBT0X_EQM_AGI", "MBT0X_EQM_MGR", "MBT0X_EQM_TRI", and "MBT0X_EQM_AGI". The
necessary process tags are in these folders.
The plant unit "Mix Storage" contains the subordinate plant unit "EMP", "FIL", "MST_01", and "MST_02". The two
subordinate units "MST_01" and "MST_02" are structured identically and each have the CFC plan "MST0X_Unit" with the
"UNIT_PLC" block and the hierarchy folder for the equipment modules "MST0X_EQM_AGI", and "MST0X_EQM_CTR". The
subordinate unit "EMP" has the CFC plan "EMP_Unit" with the "UNIT_PLC" block and the hierarchy folder for the technical
device "EMP_EQM_CTR". The subordinate unit "FIL" has the CFC plan "FIX_Unit" with the "UNIT_PLC" block and the
hierarchy folder for the technical device "EMP_EQM_CTR". The necessary process tags are in the folders for the equipment
modules.
The plant unit "Mixing" contains the subordinate plant unit "MMX" and "PMX". The subordinate unit "MMX" has the CFC
plan "MMX_Unit" with the "UNIT_PLC" block and the hierarchy folder for the equipment modules "MMX_EQM_MAA",
"MMX_EQM_MAB", "MMX_EQM_MAC", "MMX_EQM_MAD", "MMX_EQM_TRI", "MMX_EQM_TRO", and "MMX_EQM_VAC".
The subordinate unit "PMX" has the CFC plan "PMX_Unit" with the "UNIT_PLC" block and the hierarchy folder for the
equipment modules "PMX_EQM_MAA", "PMX_EQM_MAB", "PMX_EQM_MAC", and "MMX_EQM_TRO". The necessary
process tags are in the folders for the equipment modules.
The "Pasteurizer" unit contains the CFC plan "PAS_Unit" with the "UNIT_PLC" block and the hierarchy folder for the
equipment modules "PAS_EQM_TRI". The necessary process tags are located in this folder.
NOTE The simulation plans are intended to illustrate the application example and are not further explained.

Useful information
The following figures show the structure of the AS project:
IC Production AS - Projekt
Mix Plant
Mix Buffer
MBT_01
CFC CFC CFC CFC

EQM_AGI_MBT01 EQM_MGR_MBT01 EQM_TRI_MBT01 YS_MBT01_004
CFC CFC CFC CFC

MBT01_Unit LIC_MBT01_001 LSH_MBT01_001 EQM_TRO_MBT01
CFC CFC CFC

NS_MBT01_001 YS_MBT01_001 LSL_MBT01_001
MBT_02
CFC CFC CFC CFC

EQM_AGI_MBT02 EQM_MGR_MBT02 EQM_TRI_MBT02 YS_MBT02_004
CFC CFC CFC CFC

MBT02_Unit LIC_MBT02_001 LSH_MBT02_001 EQM_TRO_MBT02
CFC CFC CFC

NS_MBT02_001 YS_MBT02_001 LSL_MBT02_001
Pasteurizer
CFC CFC CFC CFC

PAS_Unit NS_PAS001 YS_PAS001 YS_PAS002
CFC CFC CFC

YS_PAS003 YS_PAS004 YS_PAS005

Useful information
Mix Plant
Mix Stoarge
EMP
CFC CFC CFC CFC

EMP_Unit NS_EMP001 YS_EMP001 YS_EMP002
CFC
EQM_CTR_EMP
FIL
CFC CFC CFC CFC

FIL_Unit NS_FIL001 YS_FIL001 YS_FIL002
CFC
EQM_CTR_FIL
MST_01
CFC CFC CFC CFC

MST01_Unit LI_MST01_001 LSH_MST01_001 NS_MST01_001
CFC CFC CFC CFC

LIC_MST01_001 TI_MST01_001 YS_MST01_001 YS_MST01_002
MST_02
CFC CFC CFC CFC

MST02_Unit LI_MST02_001 LSH_MST02_001 NS_MST02_001
CFC CFC CFC CFC

LIC_MST02_001 TI_MST02_001 YS_MST02_001 YS_MST02_002

Useful information
Mix Plant
Mixing
MMX
CFC CFC CFC CFC

MMX_Unit FIC_MMX001 YS_MMX001 YS_MMX002
CFC CFC CFC CFC

EQM_MAA_MMX NS_MMX001 EQM_MAB_MMX FIC_MMX002
CFC CFC CFC CFC

YS_MMX003 YS_MMX004 NS_MMX002 EQM_MAC_MMX
CFC CFC CFC CFC

FIC_MMX003 NS_MMX003 YS_MMX005 YS_MMX006
CFC CFC CFC CFC

EQM_MAD_MMX FIC_MMX004 NS_MMX004 YS_MMX007
CFC CFC CFC CFC

YS_MMX008 EQM_TRI_MMX LSH_MMX001 YS_MMX020
CFC CFC CFC CFC

EQM_TRO_MMX LI_MMX001 LSL_MMX001 NS_MMX021
CFC CFC CFC

EQM_VAC_MMX PI_MMX001 YS_MMX029
PMX
CFC CFC CFC CFC

PMX_Unit EQM_MAA_PMX FIC_PMX001 YS_PMX001
CFC CFC CFC CFC

YS_PMX002 EQM_MAB_PMX FIC_PMX002 YS_PMX003
CFC CFC CFC CFC

YS_PMX004 EQM_MAC_PMX FIC_PMX003 YS_PMX005
CFC CFC CFC

YS_PMX006 EQM_TRO_PMX LSL_PMX001

Useful information
OS project
The plant hierarchy in the OS project is derived from the plant view of the AS project. The neutral hierarchy folders "Mix
Plant" and "BATCH OS Controls" contain the images "Overview_Mixplant.pdl" and "simatic_batchos.pdl" In the hierarchy
folder "Mix Plant" the hierarchy folders "Puffertank", "Storagetank", "Mixing" and "Pasteurizer" are subordinate. In this case
these hierarchy folders contain the overview images of the same name for the respective plant unit. The other
subordinate file folders of "Mix Plant" and the subordinate folder of "BATCH OS Controls" do not contain any other objects.
The following figures show the structure of the AS project:

IC PRODUCTION OS- Projekt
BATCH OS Controls
PDL
simatic_batchos
MIX PLANT
Mix Buffer Mix Storage
PDL PDL PDL

Overview_Mixplant Mix_Buffer Mix_Storage
Mixing Pasteurizer
PDL PDL
Mixing Pasteurizer

Useful information
4.7.3. Abbreviations
The following abbreviations are used for the plant structure (plant view):
Abbreviation Meaning
MMX Main mixer
PMX Premixer
MBT Buffer tank tank
PAS Pasteur
MST Mixed storage tank
FRZ Freezer
EMP Emptying
FIL Filling
AGI Agitator
MGR Manager
EQM Equipment module
CTR Control
TRI Transfer In
TRO Transfer out
VAC Vacuum
MAA, MAB, etc. Material A, material B, etc.

Appendix
5. Appendix
5.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.
• Products & Services

In Products & Services, you can find all our offerings as previously available in Mall Catalog.
• Support
In Support, you can find all information helpful for resolving technical issues with our products.
• mySieportal
mySiePortal collects all your personal data and processes, from your account to current orders, service requests and
more. You can only see the full range of functions here after you have logged in.
You can access SiePortal via this address: sieportal.siemens.com
Industry Online Support

Industry Online Support is the previous address for information on our products, solutions and services.
Product information, manuals, downloads, FAQs and application examples - all information is available with just a few
mouse clicks: support.industry.siemens.com
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
SITRAIN – Digital Industry Academy

We support you with our globally available training courses for industry with practical experience, innovative learning
methods and a concept that’s tailored to the customer’s specific needs.
For more information on our offered trainings and courses, as well as their locations and dates, refer to our web page:
siemens.com/sitrain
Industry Online Support app

You will receive optimum support wherever you are with the "Industry Online Support" app. The app is available for iOS
and Android:

Appendix
5.2. Links and literature

Nr. Thema
\1\ Siemens Industry Online Support

https://support.industry.siemens.com
\2\ Link to this entry page of this application example https://support.industry.siemens.com/cs/ww/en/view/xxx
\3\
Table 5-1
5.3. Change documentation

Version Date Modification
V1.0 06/2018 First version
V2.0 09/2023 Version update and revision
Table 5-2

Ice Cream Demo DOC PCS7V91 SP2 En-1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ice Cream Demo DOC PCS7V91 SP2 En-1

Uploaded by

Copyright:

Available Formats

Siemens

L PCS 7 Unit Template

PCS 7 Unit Template

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 2

1.1. Overview ............................................................................................................................................................ 6

2. Preperation and commissioning ....................................................................................................10

2.1. Preparation ....................................................................................................................................................... 10

3.1. Overview of the plant units ............................................................................................................................... 28

3.5.1. Filling of the storage tank ............................................................................................................................... 105

4. Useful information ..................................................................................................................... 181

4.1. Basics .............................................................................................................................................................. 181

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 4

5. Appendix ................................................................................................................................... 201

5.1. Service and support ........................................................................................................................................ 201

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 5

• Implementation of an ice cream plant with blocks from standard libraries

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 6

1.2. Mode of operation

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 7

The following illustration shows the BATCH overview image

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 8

1.3. Components used

Component Number Article Number Note

SIMATIC PCS 7 V9.1 SP2 Part of SIMATIC PCS 7 ES/OS IPC547G W7

S7-PLCSIM Not part of PCS 7; appropriate licenses are required.

Advanced Process Library Component of SIMATIC PCS 7 V9.1 SP2

BCMs Library V9.1 https://support.industry.siemens.com/cs/us/en/view/109475748

This application example consists of the following components:

Component File name Note

PCS 7 V9.1 SP2 sample project 109755537_Ice_Cream_Demo_PROJ_PCS7V91_SP2.zip

Documentation 109755537_Ice_Cream_Demo_DOC_de.pdf This document

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 9

Preparing the project

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 10

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 11

14. Exit the WinCC Explorer as described in step 10.

18. Save the change and close the Graphic Designer.

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 12

2.2. Taks on the multiproject

3. Close the compiler log.

9. Select the following settings and click "Next".

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 13

10. Click on "Compile".

The "Settings" window opens.

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 14

15. In the "OS objects" tab, click on "Update".

16. In the "Process cells" tab, click on "Update".

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 15

17. Click on "OK" to exit the "Settings" window.

21. Select the "BATCH instances" item and click "Merge".

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 16

24. Select the "IC Production" item and click "Download".

27. Exit the SIMATIC BATCH configuration dialog with "OK".

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 17

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 18

Starting the simulation (S7-PLCSIM)

Activate OS (WinCC runtime)

4. Select "Mix Plant" in the image area

Activating SIMATIC BATCH

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 19

The Restore dialog opens.

Entry ID: 109755537 | V2.0 | 09/2023 © Siemens 2023 | 20