SIMATIC BATCH Getting Started Parts 1 To 4
SIMATIC BATCH Getting Started Parts 1 To 4
Contents
Part 1: Introduction
Manual
Video Sequences
Along with this Getting Started, there are video sequences
in which you can follow the step-by-step instructions
as they are performed.
After installing SIMATIC BATCH, the video sequences
are in the sbvideob.zip file in the
...\SIEMENS\BATCH\Manual folder.
The names of the video sequences match
the chapter numbers in the manual.
Note
The name of the sample project is incorrect in some of the
screenshots: the project name should be "Zen33_01"
instead of "Zdt33_01".
Edition 01/2005
A5E00364255-01
Safety Guidelines
This manual contains notices intended to ensure personal safety, as well as to protect the products and
connected equipment against damage. These notices are highlighted by the symbols shown below and
graded according to severity by the following texts:
Danger
! indicates that death, severe personal injury or substantial property damage will result if proper
precautions are not taken.
Warning
! indicates that death, severe personal injury or substantial property damage can result if proper
precautions are not taken.
Caution
! indicates that minor personal injury can result if proper precautions are not taken.
Caution
indicates that property damage can result if proper precautions are not taken.
Notice
draws your attention to particularly important information on the product, handling the product, or to a
particular part of the documentation.
Qualified Personnel
Only qualified personnel should be allowed to install and work on this equipment. Qualified persons
are defined as persons who are authorized to commission, to ground and to tag circuits, equipment, and
systems in accordance with established safety practices and standards.
Correct Usage
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
This product can only function correctly and safely if it is transported, stored, set up, and installed
correctly, and operated and maintained as recommended.
Trademarks
SIMATIC®, SIMATIC HMI® and SIMATIC NET® are registered trademarks of SIEMENS AG.
Third parties using for their own purposes any other names in this document which refer to trademarks
might infringe upon the rights of the trademark owners.
Copyright Siemens AG 2005 All rights reserved Disclaimer of Liability
The reproduction, transmission or use of this document or its We have checked the contents of this manual for agreement with
contents is not permitted without express written authority. the hardware and software described. Since deviations cannot be
Offenders will be liable for damages. All rights, including rights precluded entirely, we cannot guarantee full agreement. However,
created by patent grant or registration of a utility model or design, the data in this manual are reviewed regularly and any necessary
are reserved. corrections included in subsequent editions. Suggestions for
improvement are welcomed.
Siemens AG
Bereich Automation and Drives
Geschaeftsgebiet Industrial Automation Systems Siemens AG 2005
Postfach 4848, D- 90327 Nuernberg Technical data subject to change.
Siemens Aktiengesellschaft A5E00364255-01
Contents
Part 1: Introduction
1 Batch Processes 1-2
1.1 Technical Process Categories.........................................................................1-2
1.2 Characteristics of Continuous and Batch Processes ......................................1-4
1.3 Practice: Where is this Used? .........................................................................1-5
1.4 Branches for SIMATIC BATCH .......................................................................1-7
1.5 Origins of Batch Production: The Kitchen........................................................1-8
1.6 The Cook - Working Environment and Working Procedures...........................1-9
1.7 Batch Terminology.........................................................................................1-10
1.8 The Kitchen: Master Recipes – Header Data ................................................1-11
1.9 The Kitchen: Master Recipes – Procedure (procedural rules) ......................1-12
1.10 The Kitchen: What is Required of the Automation ........................................1-13
1.11 The Kitchen: Automation Concept.................................................................1-14
1.12 Automation Concept- New Approach ............................................................1-15
1.13 Separation of the Automation Level and Recipe Level .................................1-16
1.14 ISA S88.01 - Physical Model .........................................................................1-17
1.15 Procedural Control Model ..............................................................................1-18
1.16 Implementation – Physical and Procedural Model ........................................1-19
1.17 S88.01 Model – PCS 7 ..................................................................................1-20
1.18 Workflow in the Kitchen: Order - Master Recipe - Process Cell....................1-21
1.19 Classification of Batch Process Cells ............................................................1-22
1.20 SIMATIC BATCH: Customer Benefits ...........................................................1-24
Part 1
Introduction
1 Batch Processes
Evaporators Chemical
PIC
Reactor Group
Condenser
PT
Vacuum
Pan to Hot Well
Evaporator PIC
LIC LT PT
Steam
Feed
Feed Condensate
DRC
Product
DT
Batch
Conti
are continuously
optimized
Production cycles
are logged
Batch
are created / modified by operating personnel
Consider examples
Manage various products (on the same for Batch / Conti Processes
plant)
The production sequences are described in recipes that reflect the manufacturing process. In contrast to
typical continuous applications or production engineering applications, the production sequence is not
expressed in the automation solution but is described in a "Recipe".
The production sequences can be adjusted to new products. It is by no means the case that automated
production always produces the same thing, but rather various end products can be produced whose
manufacturing processes are specified in different recipes. These are constantly optimized both in terms
of parameter settings and the production sequences themselves.
In production, it is often vital that the sequences can be documented to allow them to be reconstructed.
This is important for quality assurance and to identify defects.
For many end customers it is decisive that they can adapt the production sequences themselves to
different products allowing them to introduce new products or to modify existing workflow sequences. This
should be possible for the operating personnel without needing to call in system specialists. It should not
be necessary to make changes to the programmable controller itself but rather in the recipes describing
the manufacturing process.
During actual production as described in a recipe, the following question often arises: "Where will
production take place?“. Generally there is more than one production facility capable of performing the
same production sequence (for example several production lines). It should therefore be possible to
assign the production sequences to different production facilities. This ability must also be included in the
system functionality and must not require modifications to the automation program.
Notes:
The best example from daily life is the "Kitchen“ production plant.
Various products are created here. The production method is described in recipes. These can be
constantly optimized and improved and completely new recipes are added.
The cooks are perfectly capable of doing this themselves without needing help from the kitchen
manufacturer. The recipe is often "secret" and contains the know-how for the production of a dish.
When cooking, cooks want to be able to decide which equipment will be used to implement a recipe. If
there are several kitchens (for example in an industrial kitchen), the user can decide which kitchen will be
used to make the recipe. Regardless of the kitchen selected, the same product should result and the
actual production location should only be decided during production scheduling.
It may also be important to document the production sequences (for example for quality assurance for the
health authorities and for guests who want to know how the product they are consuming was actually
produced).
The Cook
Working Environment and Working Procedures
Ingredients+directions (1 portion) for:
-Spaghetti Bolo
-Spaghetti Carbonara
-Beef Stew
-.........
Order
For table 1:
8 portions of Spaghetti Bolo
For 12:30 pm
production order 8 portions of Spaghetti Bolo:
Produce on range 1
4 batches of 2 portions
According to master recipe for
"Spaghetti Bolo"
by 12:30 pm
The working environment of a cook is as follows. The cook has recipes available containing both the
instructions as well as the required ingredients and quantities. These recipes are known as master
recipes.
To produce the product, materials are required that will be used during production.
Before production can be started, an order is necessary. This contains at least the information about what
should be created in which quantity and by when.
To deal with the order, the cook works according to the relevant recipe. The cook must also decide where
(for example on which stove) the dish will be cooked. Normally, several orders are being processed at the
same time so that some production equipment is occupied and not currently available.
The result is the finished product.
Batch Terminology
Master recipe
A type of recipe wich taks into account the equipment
capabilities and may include process cell-specific
information.
Control recipe
A type of recipe witch, through its execution, defines the
manufacture of a single batch of a specific product.
Batch
Apparatus dependent amount of a product, which is
manufactured discontinuously in a defined production
cycle.
Process
Sequence of chemical, physical or biological processes to
recover, produce or eliminate materials or products.
Up to now, we have used terms taken from everyday language. Such terms are, however, liable to
subjective interpretation. The same word may mean different things to different people. This is particularly
the case when people with different occupations talk to each other (for example system engineers,
chemists, production engineers). A chemist might understand a recipe to be the chemical composition of
a product (which should not be revealed at any cost) whereas the system engineer considers it to be an
automated sequence (for example a sequencer).
To create a production facility that operates as required, people from various walks of life must be able to
work together. It is therefore important that everyone speaks the same "language". Definition and
unification of the terminology was the aim of NAMUR and ISA SP88.
We will gradually replace everyday language with the terminology from the standard.
In our kitchen, we will therefore be able to derive a control recipe from the "Spaghetti" recipe for Fred's
kitchen that will decide the production sequences and that will produce a batch of spaghetti after it has
been processed.
This illustrates that the control recipe derived from the master is responsible for production. The control
recipe must therefore know which production facilities it will be using while the master recipe remains
neutral in this respect.
The Kitchen
Master Recipes - Header Data:
Bolognese
What do master recipes contain in detail? Typically, they contain two parts:
A recipe header with general information on the product (name, reference quantity, ingredients,
quantities).
A recipe was also include instructions or procedural rules for production. This is known as a recipe
procedure.
This does not yet contain any information about the equipment that will be used for production.
The recipe procedure forms the instructions for production. It is divided into various sections (unit
recipes). The unit recipes themselves are made up of recipe operations.
We could, for example describe the production of Bolognese sauce required to produce Spaghetti
Bolognese in a unit recipe for Bolognese. We can further refine this procedure by detailing the steps in
recipe operations. In the unit recipe for Bolognese sauce, would therefore start with the "Prepare“ recipe
operation. During the preparation, the input materials onions and tomatoes are chopped, ground meat is
weighed and put in a pan.
At this stage, use of the term pan or pot is still generalized. These are references to the production
facilities that will be required. In the language of the standard, these are known as unit classes. The
master recipe itself is nevertheless "neutral" in terms of the units; in other words there is still no mention
of the unit that will actually be used for production (for example Fred's kitchen and, Fred's favorite pot).
can be modified for new The cook must create new dishes
products
The characteristics of batch processes are illustrated in the example of a kitchen above.
When automating such processes, the above requirements must therefore be met.
Automation Concept
The Kitchen
are written in "Recipes" Could be extremely complex
in some cases, if possible
with AWL.SCL.SFCs WinCC
AWL,SCL,SFCs could be
are continuously modified
optimized
Production cycles
AWL,SCL,SFCs could be
are logged modified
What do these requirements mean when formulating an automation concept ? We can think of PCS 7 as
a system platform.
How can we describe the production sequences in recipes ? –
It is conceivable to structure all possible sequences using CFC and SFC and to map these to "recipes"
using parameters stored on the OS. Structuring the sequences could, however, be extremely complex
since all possibilities must be taken into account. It should also be possible to modify the recipes or to
create new recipes. This could mean that the automation program (CFC, SFC) would have to be
changed. The operating personnel would not be capable of doing this and the automation technician
would have to be called in.
It would be possible to log the sequences using messages output on the OS in the form of reports. This
would have to be implemented separately for each specific project. New and modified recipes would once
again cause problems.
The complexity of the automation solution increases yet again if the sequences need to be extended to
include various units. This would mean that the SFCs would also have to include the unit to be used.
Automation Concept
New Approach
✔Separation of Automation and Recipe
Instructions
1. Make Bolognese
4. Taste
A new approach is required to reduce the complexity, and this is achieved by separating the automation
level from the recipe level.
We assume that the physical structure of the process cell remains the same and that only the sequences
change. We can therefore implement the process cell-specific parts in the program or controller and map
the sequences in a "recipe system" that can be manipulated during operation. This is where the master
recipes are created and maintained.
Control recipes are derived from the master recipes and these access the programmable controller.
Automation Concept
New Approach
✔Separation of the Automation level and Recipe level
In the process cell, we can create a structure consisting of units (scales, pan, mixer,..). These, in turn,
have equipment phases such as weighing dosing etc.
The phases can have parameters such as the quantity parameter of the dosing equipment phase.
This is all mapped in the programmable controller. Here, the term process cell model is used. This
represents the "tool box" for the author of the master recipe.
Within the master recipe, the units along with their equipment phases are used to compose the sequence.
Based on the example of Bolognese sauce, this means that the mixer is necessary. This provides the
equipment phases filling, mixing, chopping. The first step is to put an onion into the machine. This is
followed by four tomatoes. These are then chopped for one minute, etc.
ISA S88.01
Physical Model
Pizza Hut Pizza Hut Company
Company
What should be
Karlsruhe
can contain
used for
Works
manufacturing?
Works
can contain
System-
System-
Storage, Kitchen, complex
complex Outside
Delivery.. can contain of S88
Kitchen
Process cell
Process cell
must contain
Unit
Unit
Cooking pot
can contain
Equipment In PCS7:
Equipment EPH / EOP
Module
Module
can contain can contain
Control
Control
Module
Module can contain
Recipe
Recipe
Procedure (RP) Spaghetti production
Procedure (RP) Spaghetti production
consists of a
defined amount of
Recipe
Recipe
Function (RF) Fill with water, heat, stir, ...
Function (RF) Fill with water, heat, stir, ...
In keeping with the physical model, a hierarchical model to describe the procedures is specified.
Implementing
the physical
ES:
ES: model
SIMATIC
SIMATIC
OS Manager
Manager
TC
LI
t
po
g Implementing
in 0
k
o 51 SIMATIC
SIMATIC the
Co T
BATCH
BATCH procedural
model
PLC
The two models are mapped in the architecture of PCS 7 as shown in the picture. The physical model is
implemented in the PCS7 ES. The program structures produced run on the PLC.
The procedural model is implemented in SIMATIC BATCH. The control recipe is also run in SIMATIC
BATCH and operates on the PLC systems.
Recipe
Process cell Recipe
Procedure
Process cell Procedure
Recipe Unit
Unit Recipe Unit
Procedure
Unit Procedure
Equipment Recipe
Equipment Recipe
Operation
Module Operation
Module
Control Recipe
Control Recipe
Function
Module Function
Module
ISA S88.01 describes various models that can be fully covered with PCS 7 and SIMATIC BATCH.
The process cell model describes the process cell, unit, equipment module and control module level that
is mapped using the plant hierarchy in the plant view of the SIMATIC Manager.
The process cell model is prepared for SIMATIC BATCH so that the procedural model in the form of
recipes can be mapped on it.
• A recipe procedure runs on a process cell to control a process and to create a batch of a product.
• A recipe unit procedure runs on a unit to control a recipe stage. A unit can only be allocated to one
batch at any one time.
• A recipe operation or a recipe phase runs on an equipment module to perform a industrial process
task or function.
• The device control level is not within the scope of the Batch system and is addressed over the
equipment module. The device control level is located completely within the PLC system.
Mike puts in an order for three portions of Piccata Milanese. The order is for table 5 and should be ready
in 40 minutes.
The master recipe "Piccata“ is available for production. It describes the process for one portion. Two pans
are required.
To create three portions at the same time, six pans are therefore needed. This means that three control
recipes must be created (each occupying two pans). Each control recipe produces one batch of Piccata.
If six pans are free, the cook can start the three control recipes at the same time (as shown in the
picture).
If only two pans are free, the three batches can only be produced one after the other.
Ingredients
Line
Product
Line
Product
The first criterion in the categorization is the number of products being produced in the process cell:
• Single-product process cells
• Multi-product process cells
The second criterion is the number of production lines allowing simultaneous product flow.
• Single-line structure
• Multi-line structure
• Network structure (all paths fully flexible)
complex
Simple to complex ...
CH
AT
B
IC
AT
M
SI
Small to large
simple
CH n
AT io
C
B lut
I So small medium large
AT 7
M S
SI PC © 2003 SIEMENS AG All Rights Reserved
or SIMATIC Process Control System 7
With its scalability, SIMATIC BATCH is suitable both for smaller process cells as well as for large
complexes that are now possible with V6. While the previous version was restricted in terms of the
numbers of servers (only one OS server), V6 allows up to 11 OS servers to be used.
The complexity increases with the number of products and the number of lines. With SIMATIC BATCH,
you can automate multi-line, multi-product process cells.
For small process cells that manufacture only one product on one line and do not require flexible recipes,
the user has the choice between a PCS 7 solution and the use of SIMATIC BATCH.
The essential issue here is the license costs compared with the engineering effort to create the solution.
SIMATIC BATCH
Customer Benefits
Production cycles are described in master recipes, which are created / changed by operating personnel at any
time
-> Greater flexibility of production, reduced "Time to market"
Unit allocation can be planned. The allocation planning can be changed right up to the actual allocation.
Simatic Batch supports automatic unit selection.
Production procedures are documented in a batch log (paper or electronic). The production cycles can be
reproduced using recipes.
Part 2
Quick Start
Chap. 1
Retrieving the Project
Chap. 3
Opening the Plant View
Chap. 4
Creating the Batch Process Cell
SIMATIC Manager
Working with the
Chap. 6
Assigning the "EPH" Batch Category
Chap. 10
Downloading the PLC to PLCSim
Chap. 11
Starting the OS
Chap. 12
Starting the BATCH Start Coordinator
Chap. 15
The Recipe for Piccata Milanese Pasta
and Recipe Editor (RP)
Chap. 16
Creating an Output Material
Chap. 20
Creating an Order (Batch)
Process cell
Unit
Equipment modules
Turn
Unit Recipe
Unit Procedure
Equipment
modules Recipe
Operation
Control Module
Recipe Phase
Requirements:
Note:
If SIMATIC Logon is installed, you have to log on every time SIMATIC Batch is started
2. Select the “Server” PC station in the component view and open the object properties. Enter the actual
name of your computer in “Computer name”.
You can check the name of your computer as shown below
The batch process cell data for the entered computer name generated on the ES will be loaded later.
3. Change the computer name in the WinCC Explorer to the name of your computer.
4. Save and compile the hardware configuration of the “Server” PC station with the newly added BATCH
applications.
5. Close HW Config.
Result: After you have performed these steps successfully, a new Batch process cell is created
automatically at the project level (Level 1). The name of the Batch process cell is adapted automatically.
Level 2:
Process cell
Level 3: Level 4:
Unit class Equipment modules
1. Assign the “Desk_1” hierarchy folder the object type “Unit” in the S88 type definition. The “Desk_1”
folder is then displayed green identifying it as a unit according to the ISA S88.01 standard.
2. At the level of the unit, you will also find the corresponding “Unit block” for the unit
“Desk_1”
3. Assign the object type "Unit" to the hierarchy folders “Oven”, “Pan”, “Pot_1”, “Pot_2” and “Pot_3”, as
described in step 1 in S88 type definition.
4. Assign the object type "Equipment module" to the “Drain” hierarchy folder below
Kitchen/Stove_1/Oven in S88 Type Definition. The “Drain” folder is then displayed green and
identified as an equipment module according to the ISA S88.01 standard.
At the level of the equipment modules, you will find the instances of the SFC types and/or the Batch
interface blocks (IEPH, IEPO, IEPAR_xxx).
5. Assign the object type "Equipment module" to the hierarchy folders shown on page 5 (Description of
the model) as equipment modules in the S88 type definition as explained in step 3.
3. Assign the "EPH" Batch category to the remaining SFC types “Stir”, “Drain”, “Fill_Solid”, “Turn” and
“Add_Ingredient” as explained in steps 1 and 2.
4. Close the SFC Editor.
Units of measure You can create new units of measure and change their properties.
Operation types, To allow recipe creation purely on the basis of types, types have to be specified
phase types and process tag without existing block instances.
types 1. Operation types: Type information of the equipment operations (EOP)
2. Phase types: Type information of the equipment phases (EPH)
3. Process tag types: Type information of the TAG_COLL blocks
Operation types, phase types and process tag types can be assigned control strategy
parameters.
1. Open SIMATIC BATCH and select Batch types. Then generate the Batch types and exit the window
with OK.
4. Compile the Batch process cell data. Select your project (Kitchen) in the plant view and select
SIMATIC BATCH > Batch instances >Compile.
2. Download the generated Batch process cell data to the BATCH server and BATCH client. In your
case, the BATCH server and BATCH client are on the same computer.
For this Getting Started, the “Station Configuration Editor” is ignored, because the PLC is
simulated with PLCSim and the ES, the OS server, and the BATCH server are located on a single
workstation (on the same computer).
1. Start PLCSim from the SIMATIC Manager.
3. Close HW Config.
4. Open a chart from the project and download the charts to PLCSim.
7. Save the simulation you have downloaded so that it is not lost when you close PLCSim.
If you close PLCSim without saving, you have to repeat steps 1 to 5 the next time you work with PLCSim.
Saved PLCSim data can be put directly into Run by opening the saved file.
Note
Open the OS-ProjectEditor and click on "OK". This serves to configure the WinCC
runtime interfaces and the alarm system.
2. Start the OS in runtime; the first startup can take several minutes.
Batch BDM
BATCH Control Server
Using the system tray icon, you can configure the start-up behavior of SIMATIC BATCH.
There are three different start-up options for the Batch Start Coordinator (right-click on the Start
Coordinator):
After restarting the BatchCC, the window looks different. The windows Shortcuts, Control and Message
window are opened.
The Batch Control Center is the central component for
• batch scheduling
• batch control
• management of all Batch-relevant data
• libraries, master recipes, formulas, materials
• permission management
1.9 kg pasta
50 g salt
50 g pepper
1 kg tomato sauce
Instructions
Fill a pot with 3 liters of water, add 100 ml of oil and a pinch of
1. Prepare water salt, heat to 100°
2. Cook pasta Put 1.9 kg of pasta in the boiling water and cook for 6 minutes
7. Completed
Zoom bar
Title bar Menu bar Toolbar Buttons for
changing the view
Status bar with Editing window with recipe Editing window with a ROP
context-sensitive structure of a hierarchical sequence (editing level 2)
information master recipe with ROPs
(editing level 1)
Synchronization
line between
RUPs
1. Recipe unit procedure 2. Recipe unit procedure ROP sequence with the SFC
(RUP 1) with recipe (RUP 2) with recipe structure elements, steps,
operations (ROPs) operations (ROPs) transitions, branches etc.
The recipe editor has tools for the simple creation of recipe structures such as:
• Inserting S88 procedure elements such as recipe unit procedures (RUP), recipe operations (ROP)
and recipe phases (RPH)
• Instead of a recipe operation, a referenced library operation (Lib-ROP) can also be inserted
• Inserting operator instructions or operator dialogs
• Inserting transitions
• Inserting simultaneous sequences
• Inserting alternative sequences
• Inserting synchronization lines
• Inserting loops
Creating the Recipe Structure in the Recipe Editor According to the Description in the
Recipe
1. Open the Recipe Editor with your master recipe “Training_Recipe”.
2. Using the tools and the recipe description, create the dish “Piccata Milanese”.
The diagram on this page and the accompanying video will help you (Notes on storing and labeling
videos are available on the first page of this manual).
4. Assign the "Pot_1" unit and the "Preferred unit" strategy to the left RUP.
5. Assign the "Pot_3" unit and the "Preferred unit" strategy to the right RUP.
7. Assign the texts "Prepare Water", "Cook Pasta" and "Prepare Sauce" to the ROPs (recipe
operations).
8. By double-clicking on the "Prepare Water" ROP, insert a recipe phase or NOP (No Operation).
9. Assign the “Add_Ingredient” phase and the “Add_Water” control strategy to the NOP (No Operation)
or recipe phase.
10. Assign the values and information for the input materials and parameters of the “Add_Ingredient”
phase.
The input material “Li_quantity” has to be assigned the material, in this case water, and the amount to
be filled, here 3 l.
Note:
Here, and in all the phases, the "Simutime" parameter is used for simulation (it
has no influence on the runtime behavior of phases in a batch).
12. Add the “Add_Ingredient” recipe phase with the “Add_Oil” control strategy and assign the "Oil"
material to the “Li_quantity” input material and a quantity of “0.1 l”. For the simulation time specify
value of “5” sec.
13. Add the “Heat” recipe phase and assign the value "100 °C" to the "Temp" parameter. For the
simulation time specify value of “300” sec.
14. Within the simultaneous sequence, and a further “Add_Ingredient” recipe phase with the "Add_Salt"
control strategy below the "Add_Ingredient" recipe phase and assign the material "Salt" and the
quantity "0.01 kg" to the "Li_quantity" input material. For the simulation time, specify a value of “5”
sec.
15. Complete the "Cook Pasta" ROP according to the recipe description for “Piccata Milanese.”
16. Complete the "Prepare Sauce" ROP according to the recipe description for “Piccata Milanese.”
17. Insert a synchronization line by selecting the starting position with the mouse and moving to the enter
position while holding down the mouse button.
18. Add the “Serve Pasta” and “Serve Sauce" ROPs (recipe operations) and complete them according to
the recipe description for "Piccata Milanese“.
Note:
To be able to edit recipes that have already been released, the release has to be
revoked. To do this, open the properties dialog in the BATCH Control Center with
Options > Settings and select the “Allow editing of recipes in the "Release
revoked" status“ check box.
3. Create a batch for "Order_GS” with the master recipe “Training_Recipe V1.0”.
2. Release the “Batch1” control recipe. The icon of the control recipe becomes light blue.
3. Start the released control recipe. The icon changes to green and the units are occupied and started
according to the recipe structure.
Part 3
Chap. 2
Expanding the Plant Hierarchy
Chap. 5
Creating an SFC
Chap. 9
Compiling, Transferring the OS and
Downloading Batch
Chap. 11
Expanding a Recipe
Process cell
Unit
Equipment Modules
Turn
Quench
Process values
Process value name Block Data type Comment
string
Quantity IEPAR_PI
real
Duration IEPAR_REAL real
Block contacts
Block name Block Comment
V1 VALVE
Start
V1.LIOP_SEL = TRUE
V1.AUT_L = TRUE
Valve in AUTO
V1.QMAN_OUT=TRUE
Timer ended?
V1.QOPEND=TRUE
Duration _Timer_Q0=FALSE
Close Valve
V1.AUTO_OC = FALSE
Valve closed
V1.QCLOSED=TRUE
End
V1.AUTO_OC = FALSE
Duration_Timer.I0 = FALSE
Start
Close Valve
V1.AUTO_OC = FALSE
Valve closed
V1.QCLOSED=TRUE
End
3. Expand the “Quench” hierarchy folder by adding a hierarchy folder with the name “Quench_Valve”;
this level also contains the control modules (here, the appropriate valve).
2. Open the “Valve” CFC chart and insert a valve block. Give the valve block the block name “V1”.
3. Make the inputs and outputs “QCONTROL”, “BA_EN”, “BA_ID”, “OCCUPIED”, “BA_NA”, and
“STEP_NO” visible.
4. Interconnect the “QCONTROL” output with the “FB_OPEN” and “FB_CLOSE” inputs and invert
“FB_CLOSE”.
2. Open the “Quench_EPH” CFC chart and add the “IEPH”, “IEPAR_PI” and “IEPAR_REAL” blocks
from the “SIMATIC BATCH Blocks” library. For the IEPH block, assign the name “Quench”, and
assign the same name to the “F_TYPE” input. Assign the name "Quantity" to the IEPAR_PI block and
the name "Duration" to the IEPAR_REAL block.
3. Assign the IEPH “Quench” interface block to the IEPAR_PI “Quantity” and IEPAR_REAL “Duration”
parameter blocks.
Interconnect the “EPE_CONN” output of the IEPH block (Quench) with the “EPE_CONN” inputs of
the EPAR blocks (Quantity, Duration).
4. Add a TIMER_P block for the simulation of the “Duration” process value and assign the name
"Duration_Timer" to the block and also assign MODE 1.
Interconnect the IEPAR_REAL block “Duration” with the TIMER_P block as follows.
6. To have the BATCH name, Batch ID, Batch step number, Batch enable, occupied available at the
valve block "V1", the valve block has to be interconnected with the Batch control block IEPH
“Quench”.
Make interconnections as shown below.
As an alternative, BA_EN, BA_ID, BA_NA , OCCUPIED and STEP_NO can be supplied by the Unit
block.
2. Open the SFC chart and configure the RUN sequencer listed in Chapter 1 "Implementation Concept”.
Step: START
Step: END
2
1
2. Open the “Quench_EPH” CFC chart with the “Quench” interface block.
3. Interconnect the “Quench” interface block with the external view of the “Quench_SFC” SFC chart as
follows.
Note:
First, make all parameters of the following list visible.
.
Quench / QSTART with Quench_SFC / START
Quench / QHOLD with Quench_SFC / HOLD
Quench / QSTOP with Quench_SFC / STOP
Quench / QABORT with Quench_SFC / ABORT
Quench / QRESET with Quench_SFC / RESET
Quench / QTERM with Quench_SFC / COMPLETE
Quench / QCONT with Quench_SFC / CONT
Quench / QBA_EN with Quench_SFC / BA_EN
Quench / VSTEP_NO with Quench_SFC / STEP_NO
Quench / VBA_ID with Quench_SFC / BA_ID
Quench / VBA_NAME with Quench_SFC / BA_NA
Quench / Q_OCCUPI with Quench_SFC / OCCUPIED
Quench / USTAT_L with Quench_SFC / BA_STATE
After downloading,
check the CPU state. It
has to be in RUN_P.
2. Select the "Pan" unit block icon and double-click on it to open its properties. In the “Configuration“
box, select the "Pan" unit with the "Browser" button. In the “Selected functions/EPH” field, you will see
the previously configured “Quench” phase. If you double-click with the left mouse button with the
“Quench” phase selected, you add it to the configuration.
The unit faceplate “Pan“ now also includes the “Quench“ phase.
2. The Start Coordinator starts automatically as soon as your WinCC project is in runtime. Wait until it
has started all applications completely (BCS, BDM).
3. Start the Batch Control Center and update the newly downloaded Batch process cell data.
After the update, your newly configured “Quench” phase is available for recipe creation.
4. Open the “Template_Recipe_Getting_Started” master recipe and save it with the name
“Recipe_Quench”.
5. In the “Recipe_Quench” recipe you have just created, insert the newly configured “Quench” phase.
6. Save the recipe and validate it. Then close the Recipe Editor.
7. Release the recipe for production in BatchCC. Then create a new batch with the “Recipe_Quench“
recipe, then release and start it.
Part 4
Chap. 2
Creating the SFC Type “Ventilate”
Working in the SIMATIC Manager
Chap. 3
Creating Sequencers
Chap. 4
Expanding the Plant Hierarchy
Process cell
Unit
Equipment modules
Quench
Control strategies
Control strategy name Comment
Setpoints
Setpoint name Data type Comment
Process values
Process value name Data type Comment
none
Times
Name Data type Comment
Block contacts
Block name Block Comment
Outline of the “Run” Sequencer (Run=1) for “Ventilation” Control Strategy (QCS=1)
Start
V1 Auto
V1_LIOP_SEL=1
V1_AUT_L=1
Set Timer
Open Valve T_Leng_Time0=Durati_Q
V1_Auto_OC=1
Start Timer
T_Leng_IO=1
Valve Opened?:
V1_QOPENED=1
and
Timer started?: Reset Timer Trigger
T_Leng_Q0=1 T_Leng_IO=0
Time over:
T_Leng_Q0=0
Close Valve
V1_Auto_OC=0
Valve closed?:
V1_QCLOSED=1
End
T_Durati_IO=0
The timer of the SFC type behaves like the standard block “Timer_P”.
Start
Close Valve
V1_Auto_OC=0
Valve closed?:
V1_QCLOSED=1
END
2. Open the characteristics dialog of the “Ventilate” SFC type shown below by double-clicking on it.
Select the "Characteristics" menu.
3. Select the “Control strategies” characteristic and enter the name “Ventilate” in the right-hand box.
4. Now select the “Setpoints” characteristic and enter the setpoint name “Duration” in the right-hand
field. Select “REAL” as the data type for duration. Enter "sec" as the unit of measure for duration.
5. In the next step, we will define the timer. Select the “Timers” characteristic. In the right-hand field,
enter the name “T_Length”. The timers that can be used in this way within SFC types, behave like the
standard block “Timer_P” from the PCS 7 library.
6. In the final step, we will create the valve. Select the “Block contacts” characteristic and enter the
name “V1” in the right-hand field. Select the corresponding block types in the “Block” column. In our
case, the block type is “VALVE”.
We have now specified all the characteristics required for the “Ventilate” example. The sequencers now
have to be created and configured.
1. To insert a new sequencer, click with the right mouse button while the mouser pointer is over the
“RUN” tab. Select “Insert Sequence at End”.
2. A new tab is created called “SEQ1”. Set the properties for SEQ1. In the general properties, enter the
name Abort-Hold-Comp.
3. We now configure the start conditions of the sequencer in the properties. In our case, the start
condition is:
- Aborting=True or Holding=True or Completing=True.
- Change to the "Inputs/Outputs" view. The I/Os Aborting, Holding and Completing are located in
“OUT”.
- Drag the I/Os from the upper part to the dialog for configuring the start condition.
Chart I/Os
In the left-hand part of the window, you will see the I/Os of the SFC type “Ventilate” grouped according to
inputs, outputs and in_outs. In the right-hand part, you see the list of corresponding I/Os.
The control outputs for the V1 valve or the T_Leng timer are located in “OUT”.
The feedback messages of the V1 valve are created in “IN”.
5. Drag the I/Os from the upper part to the dialog for configuring the steps/transitions. The Run and the
Abort-Hold-Complete sequencer are structured as shown in Chapter 1.
6. Set the start value for the timer mode used to “1“ (extended pulse).
7. Set the start value for the CS parameter (control strategy) to the default value 1.
2. Create a CFC chart in the “Ventilate” hierarchy folder. This chart “Ventilate_Pot1” is required for the
instance of the SFC types. Create a further folder "Val_Ventilate" in the “Ventilate” folder. Here, you
create the “Pot1_Valve”. In this chart, you configure the valve required to ventilate Pot_1.
4. Open the “Pot1_Valve” chart. Insert a VALVE block with the name P1_V1. To simulate the feedback
messages, interconnect the QCONTROL output with the FB_OPEN input and invert with the
FB_CLOSE input (QCONTROL has to first be made visible). You then get the following screen:
2. Now open the chart “Pot1_Valve” as well and arrange the two windows side by side as shown below.
Note:
You can only do this after the runtime OS has ended.
3. In the Configuration box, select the "Pot_1" unit using the “Browser“ button.
In the “Selected functions/EPH" field, you will see the previously configured “T1_Ventilate" phase.
4. If you double-click with the left mouse button with the “T1-Ventilate" phase selected, you add it to the
configuration.
Doubleclick
2. The Start Coordinator starts automatically as soon as your WinCC project is in runtime. Wait until it
has started all applications completely (BCS, BDM).
3. Start the Batch Control Center and update the newly downloaded Batch process cell data.
4. After updating, your newly configured “Ventilate” phase is available in the “Pot_1” unit.
5. Open the “Template_Recipe_Getting_Started” master recipe and save it with the name
“Recipe_Ventilate”.
Note:
If you cannot modify the recipe, select the option "Allow editing of recipes in the
"Release revoked" status in Options - Settings in the Batch Control Center.
6. Open “the “Recipe_Ventilate” recipe you have just created and insert the newly configured “Ventilate”
phase in the recipe.
7. Save the recipe and validate it. Then close the Recipe Editor.
8. Release the recipe for production in BatchCC. Then create a new batch with the “Recipe_Ventilate“
recipe, then release and start it.