ST-PCS7ASE V8.2.0 en

Course ST-PCS7ASE
6,75$,1
7UDLQLQJIRU,QGXVWU\
SIMATIC PCS 7 AS Engineering
VLHPHQVFRPVLWUDLQ
1 Introduction of the training
SIMATIC PCS 7 Documentation and

2
Online Support
3 PCS7 Project handling
SITRAIN
Training for Industry AS system specification and hardware
4
configuration
5 Type Instance Conceptions in PCS7

SIMATIC PCS 7
AS Engineering
6 Technological Engineering using APL
Course ST-PCS7ASE
7 Advanced Process Control with APL
8 SFC Advanced
9 Syntax Rules
Name: 10 Exercises
Course from: to:
Trainer: 11
Training site:
12
This document was produced for training purposes.
SIEMENS assumes no responsibility for its contents. The
reproduction, transmission, communication or use exploitation
of this document or its contents is not permitted without
express written consent authority. Offenders will be liable to
damages. Non-compliances with this prohibition make the 13
offender inter alia liable for damages.
Copyright © Siemens AG 2016. All rights, including

particularly the rights created by to file a by patent and/or
other industrial property right application and/or cause the
patent and/or other industrial property right to be granted 14
grant or registration of a utility model or design, are reserved.
SITRAIN courses on the internet: www.siemens.com/sitrain

15
Course folder Version: V8.2.0 (for PCS 7 Version 8.2)
Content 1
1 Introduction of the training..................................................................................... 3
1.1 Learning targets ..................................................................................................................... 3
1.2 Concept of this course ........................................................................................................... 3
1.3 Road map of this course ........................................................................................................ 4
1.4 Additional documentation ...................................................................................................... 5
1.5 Training equipment ................................................................................................................ 6
1.5.1 Automation system ................................................................................................................ 6
1.5.2 Signal Box .............................................................................................................................. 7
1.5.3 Combined Engineering/Operator system ............................................................................ 10
1.6 Simulated model plant in this workshop .............................................................................. 11
1.6.1 Functional process description of the Johnsson plant ......................................................... 11
1.6.2 Plant expansion during the workshop .................................................................................. 13
1.6.3 Connection to the Process simulation in this training .......................................................... 17
1.6.4 Overview .............................................................................................................................. 19
1.6.5 Digital Inputs ........................................................................................................................ 20
1.6.6 Digital Outputs ..................................................................................................................... 21
1.6.7 Analog Inputs ....................................................................................................................... 22
1.6.8 Analog Outputs .................................................................................................................... 22
1.7 Simulation Tools .................................................................................................................. 23
1.7.1 Overview .............................................................................................................................. 23
1.7.2 S7-PLCSIM .......................................................................................................................... 23
1.7.3 Steps for changing to PLCSIM ............................................................................................ 24
SIMATIC PCS 7 – Introduction of the training

Course folder, V8.2.0, ST-PCS7ASE 1-1

1-2 Course folder, V8.2.0, ST-PCS7ASE
1 Introduction of the training

1.1Learning target targets
Learning
The participant will learn about

 The learning targets and road map
of this training
 The training equipment, incl.
signal box
 Common simulation tools
Concept of this course

1.2 Concept of this course
General workflow of a PCS 7 project This course
Text
Lists Requirements You work on a training
SITRAIN Diagrams Automation of a plant with project following predefined
Course ST-PCS7ASE 1-3 4 reactors tasks during
Siemens theAG
course
© 2012
Functional process
description
independent from PCS 7 System design Decentralized Process Control Determined by the available
System based on SIMATIC PCS 7, training equipment
using 1 ES/OS, 1 AS with
distributed I/O and Industrial The process behavior is
depending on PCS 7 simulated in the CPU of
Component specification Ethernet as System Bus
the AS
Hardware and Software

Configuration and Implementation
programming
Tasks on different levels using the Getting familiar to the
Test main components of the SIMATIC Engineering Tools by
PCS 7 Engineering Toolset explanations and examples
Commissioning
Including In brief, is main subject to the

Maintenance
optimization PCS 7 service course
Course ST-PCS7ASE 1-3 SITRAIN - Siemens AG © 2016

Road map of this course

1.3 Road map of this course
Project handling
Multiproject and Multi-user engineering, Update of PCS 7 block libraries with CPU410-5H,
Comparing projects, Versioning using Version Trail
Licenses and current license model with CPU 410-5H
System design – Planning and specifying hardware components

Selecting the CPU on a memory and cycle time base, Important CPU settings, Monitoring of cycle time and
CPU behavior with CPU_RT, Time synchronization, Redundancy conception in SIMATIC PCS7
Comparing topology of Profibus vs. Profinet in SIMATIC PCS 7
Type-instance conceptions with SIMATIC PCS7

Central mass data engineering using the Import-Export-Assistant
Structure of the import file, Creating process tag types and process tags,
Adoption of existing process tags, Export, Update of changes
Comparison control module types vs. process tag types, Manual implementation,
Synchronization function and Variants / Optional blocks
Technological Engineering with APL

Basics of APL, Configuration of dose functions
Advanced Process Control with APL

Overview about APC features, Controller optimization using PID tuner and control performance monitoring
Sequential control using SFC-Types

Basics, calculations in SFC, Operating state logic,
Characteristics as interface of SFC types, Changing the control strategy and setpoints
ourse ST-PCS7ASE 1-4 SITRAIN - Siemens AG © 2016

1.4 Additional documentation

Additional to this training manual you will have available a selection of the current
system documentation. References are made using the number in brackets.
Example:
Additional documentation

See [103] PCS 7 V8.2 Engineering System - 03_2016, 2.1.2 for more details
Below you find the way the available documentation is represented
Course ST-PCS7ASE 1-5 SITRAIN - Siemens AG

1.5 Training equipment

Equipment is made available for practicing to support you in getting familiar to the
system. SITRAIN expects you to use the equipment for that reason only. The use of
external storage devices (memory stick etc.) or disks is only allowed with permission of
the trainer.
1.5.1 Automation
Automation Systemsystem
in the Training
A standard automation system is used in our training, consisting of:
AS410S
Industrial
Main Components
Ethernet
• a central rack
• a power supply module
• a CPU 410 with integrated DP and PN interfaces
PN • an Industrial Ethernet communication processor
DP
CP 443-1
• various I/O modules on ET200M via PROFINET
• various I/O modules on ET200M via PROFIBUS DP
• a Signal Box
ET 200M
Process signals
Signal Box
A local network allows you to have access to PC and AS of other students. Please, only
do so with permission of the related persons.
CPU 410-5H
Beginning from PCS 7 version V8.0 SP1 the SIMATIC PCS 7 process control system
offers an exclusive automation system, which can be used in all domains due to its
versatility.
Depending on the requirements, you can configure it as a:
 Standard AS 410S automation system
 High Availability AS 410H automation system
 Safety-related AS 410F/FH automation system
In our training system we use the AS410S, containing the CPU410-5H.
 See [br] SIMATIC PCS 7 CPU 410-5H Process Automation., for more details.

1.5.2 Signal Box

Use of a Signal box connected to the distributed
periphery Extra to the simulated process to be controlled, a Signal Box is available as a part of
your training equipment:
DO16 AO4
DI16 AI8
Analog measurement
Potentiometer
Lamps, relay
Switches and buttons,

relay, emergency switch • Wire break at input
• Ground fault at output,
• Loss of voltage at DI module
Course ST-PCS7ASE
Wiring has been made up to the1 -front
9
connector of the IO modules on the DP ET 200M
SITRAIN - Siemens AG © 2016
rack, containing both a digital and analog input and output module.
The signals can be used in various situations in later tasks.
This chapter’s task will bring the IO signals into the area of configuration: the CFC
charts. Later in this chapter more details.

Layout
DescriptionThe
Signal Boxof the Signal Box have been assigned short names. Initially these
components
Layout names will be used as the so called “symbolic names”. The names me be modified for
specific use of the signals in later tasks.
Emergency
H1 S1
Off
H2 S2
Display 1 Display 2
H3 S3
Source for Source for

Display 1 Display 2
H4 S4
(AO0 or AI0) AI0 (AO1 or AI1) AI1
Wire break Shortened to M No Power

T1 T3 Relay DI#0 DO#0 DI module
Normally Opened
Relay
T2 T4 Normally Closed
(Relay controlled by DO#0)
SITRAIN
Course ST-PCS7ASE
 S1 … S4 are switches to be 1used
- 10
as operator input for binary inputSiemens
signals.
AG © 2012
 T1 … T4 are buttons also to be used as operator input for binary input signals.
 H1 … H4 are lamps indicating binary output signals.
 AI0, AI1 are potentiometers to be used as operator input for analog input signals.
 The displays 1 and 2 are analog measurements indicating analog output signals or
the current input signals as set by the potentiometers.
 The switches below the displays are used to select what the display is indicating: the
analog output or input signal.
 The relay LEDs indicate a valve position simulated by a relay. The relay is controlled
by the digital output signal DO 0.0.

Description
Function diagramSignal
of digitalBox
signals
Function diagram
Please do of digital
realize: this issignals
not a wiring diagram. This drawing supplies you with an
overview of the digital signals of the Signal Box and their connection to the IO modules.
Digital Output – Hardware Channel # (DP ET 200M slot 5)

Q 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7
spare
H1 H2 H3 H4
T1 T2 T3 T4 S1 S2 S3 S4
Relay
Emergency
Off
spare
I 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7
Digital Input – Hardware Channel # (DP ET 200M slot 4)
SITRAIN
Course ST-PCS7ASE 1 - 11 Siemens AG © 2012
Description
Function diagramSignal Box
of analog signals
Function diagram
Please do of analog
realize: signals
this is not a wiring diagram. This drawing supplies you with an
overview of the analog signals of the Signal Box and their connection to the IO modules.
Analog Output – Hardware Channel # (DP ET 200M slot 7)

#0 #1 #2 #3
QW 512 QW 514 QW 516 QW 518
AO0 AO1 AO2 AO3
Display 1 Display 2
AI0 AI1 AI2 AI3 spare
#0 #1 #2 #3 #4 #5 #6 #7
IW 512 IW 514 IW 516 IW 516
Analog Input – Hardware Channel # (DP ET 200M slot 6)
SITRAIN

1.5.3 Combined Engineering/Operator system
In this training …
In this training …
a workstation is used as a combined Engineering/Operator system.
Combined Engineering / Operator station
The operator station is configured as a so-called single station system in this case.
Engineering station and Rack PC‘s of different

operator station performance classes or…
…other computer
Industrial Ethernet
Automation system
AS 400
Distributed IO

Course ST-PCS7OSE
See [102] PCS 7 V8.2 PC Configuration and Authorization - 03_2016, 3.5.3 for more
details
1-4 SITRAIN - Siemens AG © 2015
Network architecture in the course

The engineering/operator system and the automation system have communication to
each other through Industrial Ethernet components. Each set of equipment is using a
Scalance switch (alternatively: OSM switch) for interconnection, also to the other
student groups.
The illustrations show possible network architectures in the course room.
Network architecture in the course
Important configuration details have to be provided by the trainer as:
Use case with 1 computer + VM per training site
 MAC address on your training site
 Used communication protocols
Terminal bus
ES/OS (VM) ES/OS (VM) ES/OS

ES/OS
(VM) (VM)
System bus
AS AS AS AS
Team Team

1 - 10 Course folder, V8.2.0, ST-PCS7ASE
Course ST-PCS7OSE 1-5 SITRAIN - Siemens AG © 2016
1.6 Simulated model plant in this workshop

There are several reasons that we do not offer you a real process for practicing. A
suitable process simulation will replace it, offering you I/O to represent a process in
work.
1.6.1 Functional process description of the Johnsson plant
Johnsson & Co, a company supplying products for the food industry, wants to
modernize their plant to increase the production and to make it fit for stronger
Overview of the
environmental process
protection simulation
amendments. The in this base
installed workshop
consists in a process control
system PCS 7 of version V8.2.
Material tanks Reactors Buffer tanks
Storage Shipping
Office and
control room
Process diagram - Johnsson

Starting point of the model plant & Co
(V111) (V121) (V131)

Course ST-PCS7ASE 1 - 13 SITRAIN - Siemens AG © 2016
M110 M120 M130
LT114 LT124 LT134
6000 kg 6000 kg 4000 kg
Material tanks
4s V112 V122 V132
2s P113 P123 P133
Dose tanks
V221 V231 V241
0,25 s V211 V212
CV218 V222 V232 V242
0,1 s VF211 VF212 V223 V233 V243
FT216 FT217 FT218
5 kg/s
LT214 LT224 LT234 LT244

D210 D220 D230 D240
400 kg 400 kg 400 kg 400 kg
4s V311 V321 V331 V341

TT315 200 C TT325 200 C TT335 200 C TT345 200 C
LT314 CV315 LT324 CV325 LT334 CV335 LT344 CV345

700 kg R310 21 s 700 kg R320 700 kg R330 700 kg R340
2s M316 M326 M336 M346
5s V312 V322 V332 V342

Reactors
2s P313 P323 P333 P343
5s V411 V421
LT414 LT424 Buffer tanks

12000 kg 18000 kg
B410 B420
(V412) (V422)
Course ST-PCS7ASE
The existing plant has to be expanded
1 - 13
by additional units and functions.

Course folder, V8.2.0, ST-PCS7ASE 1 - 11
Starting point
In four different reactors, up to three components are to be dosed, mixed and heated
up.
 Material tanks M110, M120 and M130
The components are coming from three material tanks, two with a capacity of 6000kg
and a third with a capacity of 4000kg. The outlet to the dose tanks is done through a
valve and a pump for each tank.
The filling and refilling of the material tanks is not part of this project. It is done
through valves, which states are offered to the control system for displaying.
 Dose Tanks D210, D220, D230 and D240
Controlling the amounts of the components to be mixed and heated, dose tanks are
used. Dosing is done for one component at a time. The capacity of each of the dose
tanks is 400kg.
 The dose tanks D220…D240 contain 3 inlet valves, one for each component.
 The dose tank D210 is equipped with an additional set of 2 fine dosing valves
and 1 analog control valve CV218 to have better control of dosing flow. The
control range is between 0…100%.
 The binary valves do only permit or stop the coarse flow / fine flow. The different flow
rate for coarse or fine flow is defined inside the Johnsson simulation by fixed
parameters as result of - as example - different planning of valves and pipe
segments. The analog valve is able to scale the flow rate between 0 …maximum
coarse flow rate.
The outlet valve will be the inlet for the related reactor.
 Reactors R310, R320, R330, R340
Four reactors are used for mixing en heating the components. R310 and R320 can
contain 700kg each; R330 and R340 have a capacity of 1100kg. The inlet valve is the
same as the outlet valve of the related dose tank.
Each reactor has a single direction, single speed mixer.
Heating is done by steam piping in the inside of the reactor. A control valve is
controlling the steam flow. There is no cooling circuit.
The outlet of the reactors is done through a valve and a pump, with destination to one
buffer tank.
 Buffer tanks B410 and B420
Two buffer tanks, one with a capacity of 12000kg and one having 18000kg are there
for storing the product, before it is transferred to the shipping area. The buffer tanks
have an inlet valve.
The transfer from the buffer tanks to the shipping area is not part of this project. It is
done through valves, which states are offered to the control system for displaying.

Operation
 Each of the individual devices in the process is to be monitored and operated

manually by the decentralized control system.
 An automatic mode allows the production. The buffer tank has to be operated
manually.
 Every reactor is to be used up to 90 percent of its capacity.
The mixture of the components in percentages and the heating temperature is to be
entered in the system and is valid for the entire production.
1.6.2 Plant expansion during the workshop

Scheduled expansions in our training
1. Modification of the project-structure
1. Modification of the project-structure
MP MP
Pr AS_Pr
AS AS
S7-Prog S7-Prog
• Sources • Sources
• Blocks • Blocks
• Charts • Charts
ES/OS OS_Pr
WinCC-Appl
ES/OS
• Pictures
WinCC-Appl
Lib • Pictures
Lib
You divide the combined AS/OS Project

Course ST-PCS7ASE 1 - 14
into two Projects where the AS and the OS are
in separate projects under the head of the same Multiproject.

2. Project changes with IEA
2. Plant expansion on base of process tag types and IEA
(V111) (V121) (V131)
M110 M120 M130

LT114 LT124 LT134
6000 kg 6000 kg 4000 kg
Material tanks
4s V112 V122 V132
2s P113 P123 P133
Dose tanks
V221 V231 V241
0,25 s V211 V212
CV218 V222 V232 V242
0,1 s VF211 VF212 V223 V233 V243
FT216 FT217 FT218
5 kg/s
LT214 LT224 LT234 LT244

D210 D220 D230 D240
400 kg 400 kg 400 kg 400 kg
4s V311 V321 V331 V341

TT315 200 C TT325 200 C TT335 200 C TT345 200 C

700 kg R310 21 s 700 kg R320 700 kg R330 700 kg R340
2s M316 M326 M336 M346
5s V312 V322 V332 V342

Reactors
2s P313 P323 P333 P343
5s V411 V421
X414_1 X424_1
X414_2 12000 kg
X424_2
18000 kg
X414_3 B410 X424_3 B420
100 % 100 %
(V412) (V422)

The Valves related to the Material Tanks will be configured as Process tags.
Both buffer tanks have to be equipped with additional product concentration monitoring.
Each material 1…3 (corresponding to Material tanks M110…M130) is represented by a
concentration value in range of 0…100%.own analog monitoring process tag:
 In B410
 X414_1 concentration of material 1
 In B420
The concentrations are determined as mass fraction [weight %].

3. Project changes with CMTs / CMs
3. Plant expansion on base of control module types and control modules
(V111) (V121) (V131)
M110 M120 M130

LT114 LT124 LT134
6000 kg 6000 kg 4000 kg
Material tanks
4s V112 V122 V132
2s P113 P123 P133
Dose tanks
V221 V231 V241
0,25 s V211 V212
CV218 V222 V232 V242
0,1 s VF211 VF212 V223 V233 V243
FT216 FT217 FT218
5 kg/s
LT214 LT224 LT234 LT244

D210 D220 D230 D240
400 kg 400 kg 400 kg 400 kg
4s V311 (+Counter) V321 (+Counter) V331 (+Counter) V341 (+Counter)

TT315 200 C TT325 200 C TT335 200 C TT345 200 C

700 kg R310 21 s 700 kg R320 700 kg R330 700 kg R340
2s M316 M326 M336 M346
5s V312 V322 V332 V342

Reactors
2s P313 P323 P333 P343
5s V411 V421
X414_1 X424_1
X414_2 12000 kg
X424_2
18000 kg
X414_3 B410 X424_3 B420
100 % 100 %
(V412) (V422)
Course ST-PCS7ASE
The existing process tags V311…V341
1 - 16
are to be replaces by control module variants on
base of a control module type with an optional counter block and optional locking
functions.
 The counters for the reactor inlet valves V311…V341 are optional extensions of these
process tags. The counter is able to measure operating hours and/or binary signal
changes and does not need an own signal from the field.

4. Project changes with APL dose functions
4. Change of the dose function configuration to use the APL Dose block
(V111) (V121) (V131)
M110 M120 M130

LT114 LT124 LT134
6000 kg 6000 kg 4000 kg
Material tanks
4s V112 V122 V132
2s
1 2 3 P113 P123 P133
Dose tanks
V221 V231 V241
0,25 s V211 V212
CV218 V222 V232 V242
0,1 s VF211 VF212 V223 V233 V243
FT216 FT217 FT218
5 kg/s
LT214 LT224 LT234 LT244

D210 D220 D230 D240
400 kg 400 kg 400 kg 400 kg
4s V311 V321 V331 V341

TT315 200 C TT325 200 C TT335 200 C TT345 200 C

700 kg R310 21 s 700 kg R320 700 kg R330 700 kg R340
2s M316 M326 M336 M346
5s V312 V322 V332 V342

Reactors
2s P313 P323 P333 P343
5s V411 V421
X414_1 X424_1
X414_2 12000 kg
X424_2
18000 kg
X414_3 B410 X424_3 B420
100 % 100 %
(V412) (V422)
Course ST-PCS7ASE
3 different variations of the dosing 1function
- 17
basing on the APL dose block DoseL have
to be implemented for the 3 materials of dose tank D210:
1. Dosing on base of flow rate monitoring FT216 for material 1.
 The DoseL block is used in flow mode.
 The dose flow is controlled using 2 binary valves (coarse / fine flow: V211 /
VF211).
2. Dosing on base of level monitoring LT214 (Weighing of fill volume using dosing
scales) for material 2.
 The DoseL block is used in scaling mode.
 The dose flow is controlled using 2 binary valves (coarse / fine flow: V212 /
VF212).
3. Dosing on base of flow rate monitoring FT218 for material 3.
 The DoseL block is used in flow mode.
 The dose flow is controlled using an analog control valve for material 3 (CV218).
The realization of dosing functions using the DoseL block presumes that all involved
valves are in automatic mode.
The sequential control has to be adapted to the DoseL function.

5. Further functional modifications
5. Further functional modifications
The sequences for the reactors R320…R340 are The SFC type has to be extended by additional steps
configured as instances of a central SFC type and control strategies.
Die temperature control of reactors has to be optimized and

extended by a Control Performance Monitoring.
1.6.3 Connection to the Process simulation in this training
There are several reasons that we do not offer you a real process for practicing.
A suitable process simulation will replace it, offering you I/O to represent a process in
work.
Process Simulation
The picture below gives you an impression of the relationship between process I/O and
Method in this training
the application running in the automation system, and the simulation representing the
process.
Hardware Software
I/O Modules Driver blocks
Process
AI
images
Control block
Pcs7AnIn
AO
Process Pcs7AnOu
DI
Process value
Motor block
Name Pcs7DiIn
DO
Pcs7DiOu
Johnsson
Process
simulation
Symbol table
SITRAIN
SIMATIC
CoursePCS 7 – Introduction of the training
ST-PCS7ASE 1 - 13 Siemens AG © 2012
The process simulation (running in the CPU as a Function Block) is using the original
Process Image as an interface to the application software in the automation system.
This makes it possible for you to configure functions with channel drivers, similar to real
applications.
The symbol table contains the corresponding signal names for the process values in the
Process Image and their addresses. These addresses should not overlap the addresses
of the real hardware.

Method in this training
Example: Valve simulation for V311
Example for V311

Here you see the simulated valve V311 (D210 Dose outlet valve) as an example and a
part of the process simulation:
4
Johnsson
V311_O Pcs7DiIn VlvL block Pcs7DiOu
V311 3
1 V311_C Pcs7DiIn
2 V311
Process
images
1. Simulation of V311, as a part of the Johnsson plant simulation. It is running in a

single function block on a chart called “@Johnsson”. This chart should only be
present in the Charts folder of your AS.
2. Control signal to the valve, using the valve tag name as the symbolic name
SITRAIN
Course ST-PCS7ASE
3. Feedback signals formed by limit switches:
1 - 14 Siemens AG © 2012
 “V311_O” = opened
 “V311_C” = closed
4. A chart with a minimum of blocks to control and monitor the block. This chart is to
appear in the plant hierarchy.
1.6.4 Overview
The number of I/O is based on the devices in the plant.

The following table gives an overview of the number of devices and the related I/O:
number DI DO AI AO
open-close valves 25 50 25
status valves 5 5
motors 11 11 11
level measurement 13 13
temperature measurement 4 4
control valve 4 4 4
total 62 66 36 21 4
number of channels per module 16 16 4 4

number of modules 4,125 2,25 5,25 1
lowest address I 100.0 Q 100.0 IW 208 QW 208

highest address I 110.5 Q 105.1 IW 258 QW 214

1.6.5 Digital Inputs

signal address data type description
name
V111_O I100.0 BOOL M110 Material tank Inlet valve Feedback Opened
P113_O I100.1 BOOL M110 Material tank Outlet pump Feedback On
V112_C I100.2 BOOL M110 Material tank Outlet valve Feedback Closed
V112_O I100.3 BOOL M110 Material tank Outlet valve Feedback Opened
V211_C I102.0 BOOL D210 Dose tank Inlet valve 1 Feedback Closed
V211_O I102.1 BOOL D210 Dose tank Inlet valve 1 Feedback Opened
V311_C I106.0 BOOL R310 Reactor Inlet valve Feedback Closed
V311_O I106.1 BOOL R310 Reactor Inlet valve Feedback Opened
P313_O I106.2 BOOL R310 Reactor Outlet pump Feedback On
V312_C I106.3 BOOL R310 Reactor Outlet valve Feedback Closed
V312_O I106.4 BOOL R310 Reactor Outlet valve Feedback Opened
M316_O I106.5 BOOL R310 Reactor Stirring motor Feedback On

signal address data type description

name
V411_C I110.0 BOOL B410 Buffer tank Inlet valve Feedback Closed
V411_O I110.1 BOOL B410 Buffer tank Inlet valve Feedback Opened
V412_O I110.2 BOOL B410 Buffer tank Outlet valve Feedback Opened
V421_C I110.3 BOOL B420 Buffer tank Inlet valve Feedback Closed
V421_O I110.4 BOOL B420 Buffer tank Inlet valve Feedback Opened
V422_O I110.5 BOOL B420 Buffer tank Outlet valve Feedback Opened
1.6.6 Digital Outputs

signal name address data type description
P113 Q100.0 BOOL M110 Material tank Outlet pump
V112 Q100.1 BOOL M110 Material tank Outlet valve
V211 Q101.0 BOOL D210 Dose tank Inlet valve 1
V311 Q103.0 BOOL R310 Reactor Inlet valve
P313 Q103.1 BOOL R310 Reactor Outlet pump
V312 Q103.2 BOOL R310 Reactor Outlet valve
M316 Q103.3 BOOL R310 Reactor Stirring motor
V411 Q105.0 BOOL B410 Buffer tank Inlet valve
V421 Q105.1 BOOL B420 Buffer tank Inlet valve

1.6.7 Analog Inputs

signal name address data type description low range high range unit
LT114 IW208 WORD M110 Material tank Level 0 6000 kg
LT214 IW216 WORD D210 Dose tank Level 0 400 kg
LT314 IW224 WORD R310 Reactor Level 0 700 kg
TT315 IW226 WORD R310 Reactor Temperature 0 200 degr C
CV315_X IW228 WORD R310 Reactor Temperature control valve feedback 0 100 %
position
position
position
position
LT414 IW256 WORD B410 Buffer tank Level 0 12000 kg
LT424 IW258 WORD B420 Buffer tank Level 0 18000 kg
1.6.8 Analog Outputs

signal name address data type description low range high range unit
CV315 QW208 WORD R310 Reactor temperature control valve 0 100 %

1.7 Simulation Tools

1.7.1 Overview
S7-PLCSIM,Different
SIMITfromSimulation
the method ofFramework
simulating the process in this training, products are
available for simulation:
At present, the products listed below are available for

testing and simulation of an entire SIMATIC PCS 7
system or individual process control levels (automation
level, field level …):
• S7-PLCSIM: SIMATIC PCS 7 standard product for

function testing of CFC/SFC application software
on PGs/PCs;
See main catalog ST PCS 7 for description and
ordering data
• SIMIT Simulation Framework for testing and
commissioning of the project-specific user software
on a partially virtual plant,
See catalog ST PCS 7 T "Process Control System
SIMATIC PCS 7 – Technology components"
 See [005] Catalog ST PCS 7 T Technology Components - 2015, 8 for more details
1.7.2 S7-PLCSIM
Introduction
In S7-PLCSIM you can execute and test your PCS 7 user program in a simulated
programmable logic controller (PLC). The simulation is executed on your PC as an
optional part of the Engineering System ES, you do not require any S7 hardware (CPU
or signal modules)
Prerequisites
The Automation System AS is emulated on the PC, that means: “it can be placed and
handled directly beside the loaded CFC/SFC program”. You can save the actual state:
loaded program – simulated values – operating mode and you can open this state
again!
You can record and play back your actions of simulation to automate tests. You have
memory access via Process Image: so you can change I/O-values for testing the
reaction in your program (I/O-simulation). Here you can use the I/O-address or the
signal name of the Symbol Table.

1.7.3 Steps for changing to PLCSIM

Steps for changing to PLCSIM
Start PLCSIM
Start PLCSIM
1. Select the AS to be simulated.

2. Start PLCSIM with the button „Simulation On/off“on the tool bar.
SITRAIN
Course ST-PCS7ASE
3. Simulation is started. The view
1 - 16
object "CPU" is opened. The PLC Siemens
must be in the
AG © 2012
original state. Access to a real PLC is not possible during this state.
 S7-PLCSIM automatically changes the S7ONLINE Access Point to a simulation

subnet. During simulation, do not change the access point to an access point that is
unknown to S7-PLCSIM with "Set PG/PC interface". S7-PLCSIM will change the
access point back to the original setting when you end the simulation.
4. Switch on the simulated CPU by the option box „RUN-P“.

Download of the S7 program to PLCSIM
Download of the S7 program to PLCSIM
The blocks and hardware configuration are downloaded to the simulated PLC. The
SITRAIN simulation system adopts the identity of the loaded CPU and all configured connection
Course ST-PCS7ASE data. 1 - 17 Siemens AG © 2012
The picture shows the first download to be a complete download. Later downloads can
be started for instance from the CFC editor as download of changes without stop of the
simulated CPU.

Communication to WinCC
Steps for changing interfaces (MPI – TCP/IP – ISO ...) for communication access.
to PLCSIM
There are different
Communication
In PCS7to
weWinCC
usually use a “named connection” between AS and OS. But: PLCSIM in the
current version (V 5.4) does not support the named connection.
g
in
ac
pl
re
1 3
SITRAIN
If you want to have a connection between an simulated AS (by PLCSIM) and an OS,
you have to …
1. Start the compilation wizard for the selected OS.
2. Select the S7-program to be compiled.
3. Open the "Select Network Connection" dialog.
4. Change to the regarded Ethernet connection instead of the “named connection” and
finish the OS compilation.

Result in the OS tag administration
Check if the access point in PLCSIM fits to this connection type
SITRAIN
Course ST-PCS7ASE
1. Open the OS and check if the
1 - 19
tags have moved into the selected Siemens
channel.AG © 2012
2. Check if the access point in PLCSIM fits to this connection type.
 Troubleshooting in case of OS with process tags without connection:

1. Check if the access point in PLCSIM fits to this connection type.
2. Download again a chart to be sure that the PLCSIM is executing a S7 program.

Several instances of running PLCSIM:

Several instances of running PLCSIM:
3
4 2
SITRAIN
Course ST-PCS7ASE
You can simulate up to 8 different
1 - 20
AS (AS "instances"). Siemens AG © 2012
The procedure is in principle similar to the start of the first PLCSIM instance.
1. Open a new PLCSIM instance.
2. The simulation is started. A new PLCSIM object with another "CPU" object inside is
opened.
3. Select another AS to be simulated and download the S7 program to the new
PLCSIM instance.
 See [313] Engineering Tools S7-PLCSIM V5.4 incl. SP3 - 03_2009, 3 for more details

Content 2
2 SIMATIC PCS 7 – Documentation and Online Support ........................................ 3
2.1 Learning target ....................................................................................................................... 3
2.2 Documents available by PCS 7 Installation ........................................................................... 3
2.2.1 Delivered Manuals ................................................................................................................. 3
2.2.2 Delivered Readme Files ........................................................................................................ 4
2.2.3 PCS 7 help system ................................................................................................................ 5
2.2.4 Template for a plant-specific process control manual for operators ...................................... 6
2.3 Additional sources of information........................................................................................... 7
2.3.1 PCS 7 Compendium .............................................................................................................. 7
2.3.2 PCS 7 on Tour (PoT) ............................................................................................................. 8
2.3.3 PCS 7 catalogs ...................................................................................................................... 9
2.3.4 PCS 7 in the inter- / intranet ................................................................................................ 10
2.4 Industry Online Support Internet Portal ............................................................................... 11
2.4.1 Overview .............................................................................................................................. 11
2.4.2 Product support.................................................................................................................... 13
2.4.3 SIMATIC PCS 7 Summary page of the Product Support .................................................... 15
2.4.4 Compatibility tool ................................................................................................................. 16
2.5 Working with mySupport ...................................................................................................... 18
2.5.1 Personal filters and notifications .......................................................................................... 18
2.5.2 Personal documentation ...................................................................................................... 20
2.6 Support Request .................................................................................................................. 22
2.7 Forum - the communication platform for Siemens Industry products .................................. 23
2.7.1 Conferences and Forum management ................................................................................ 23
2.7.2 Interactions in the Forum ..................................................................................................... 25
2.8 Task and Checkpoint ........................................................................................................... 26
SIMATIC PCS 7 – Documentation and Online Support



2 Lernziele
2.1 Learning target

 What types of PCS 7
documentation are available
 Navigation through the Industry
Online Support
 All functions and possibilities of
the Industry Online Support
2.2 Documents available by PCS 7 Installation

2.2.1 Delivered Manuals
The PCS 7 Readme File “pcs7-readme.rtf” contains in section 2.1 “General information”
a complete overview list with PCS 7 Manuals locally available after PCS 7 installation.
Course ST-PCS7SYS 2-2 SITRAIN - Siemens AG © 2014
Pathways to installed manuals

Access to installed manuals
Once you have installed PCS 7 including the PCS 7 documentation on your computer,
you can open this documentation with
Start > SIMATIC > Documentation > English

SITRAIN
Requirements and functional process description 3-3 Siemens AG © 2012
Manuals on SIMATIC PCS 7 DVD

If you do not wish to install this documentation, you can also view it at any time on the
SIMATIC PCS 7 DVD in the following folders:
"_Manuals\English" or "_Product_Information\English".
All the manuals are stored in PDF format. You require Acrobat Reader to open the files.
If necessary, you can install it from the SIMATIC PCS 7 DVD.
 Programming Instructions for creating driver blocks and with the title "SIMATIC
Programming Instructions Driver Blocks" can be ordered separately. These
Programming Instructions help the advanced SIMATIC PCS 7 user to create system-
conform driver blocks, which can be placed like standard blocks on system plans and
automatically parameterized and interconnected in HW Config.
2.2.2 Delivered Readme Files
Pathways to installed Readme files

Once you have installed PCS 7 including the PCS 7 documentation on your computer,
you can open any Readme file with
Start > SIMATIC > Information > English
Reason to have attention to the Readme files
 ATTENTION
Each of the PCS 7 related products come with product-specific information in the
form of readme files.
SITRAIN Readme files contain information which is not included in manuals due to the degree
of topicality.
The information given in Readme files takes precedence over all the PCS 7 manuals.

pcs7-readme.rtf
 Most important Readme file of PCS 7
 Containing information also relevant before PCS 7 installation:
 Licensing of software to be installed
 Hardware pre-requisites and compatibles
 Software requirements regarding the operating system or system settings and the
software to be installed
 Compatibility to 3rd party products (software)
 Required installation steps/ required upgrade steps
 Basic information for update of PCS 7 projects
 Notes on usage of the product
 Summary of changes compared to the former product version
pcs7sysdocu-readme.pdf
 Contains information and additions to the manuals of the PCS 7 system
documentation with higher topicality due to the deadline for generation of electronic
manuals.
 Known misprints in delivered manuals are cleared here.
pcs7new.pdf
 “What’s new in PCS 7?” contains an extract of all new features and changes in the
current PCS 7 version.
 Summarized information given in first section “What’s new” in each product /
operation manual.
2.2.3 PCS 7 help system
Implementation of the PCS 7 help system

The PCS 7 help system, which can be called from SIMATIC Manager, will be updated
regularly as of PCS 7 V8.0. Service packs for PCS 7 and the products in the system
documentation will also be compiled and published.
You have to implement the PCS 7 help system manually in the PCS 7 installation with
copy and paste as follows:
1. Download the zip files of the help system from the Service & Support portal by
clicking .
2. Unzip the help files into a folder.
3. Copy all help files into the folder Siemens > STEP7 > S7BIN in the PCS 7
installation.
When you open the PCS 7 help system again, it will be updated.

Access
Access to PCS to PCSdocumentation
7 System 7 Systembydocumentation
online help by online
Since PCS 7 V6.0 SP3, you can also open the complete system documentation for PCS
help 7 in the online help format within the SIMATIC Manager through the help topics.
 You can open the "PCS 7 Basic Documentation" online help with the menu command
“Help > Topics in the SIMATIC Manager.”
Plant-specific process control manual for operators

2.2.4 Template for a plant-specific process control manual for operators
SITRAIN
Youand
PCS 7 Documentation canOnline
create a process control manual for2 the
Support - 5 operator derived from a source Siemens AG
document of the actual PCS 7 OS Process Control Manual.
 „PCS 7 - Operating Instructions Operator Station Process Control.doc “

 Derived from a source document of the actual PCS 7 OS Process Control Manual
 Covering the well-proven main structure of a control manual for operators
 Available in the "_Manuals\<language*>" folder on your PCS 7 Toolset DVD.
(* Select your regional <language>.)
 Edit the source document with MS Word
SITRAIN

2.3 Additional sources of information

2.3.1 PCS 7 Compendium
Subject of the manual

On the one hand:
 SIMATIC PCS 7 is as a distinctly open system to be flexibly adapted to a wide range
of customer needs.
 Great deal of freedom in terms of the project configuration, as well as in the design of
the program and the visualization.
On the other hand:
 Experience has shown that subsequent modernization or plant expansion work is
made much easier if the project is configured "in conformance with PCS 7" as far as
possible right from the start.
 Certain basic rules absolutely must be adhered to in order to ensure that the system
functions provided will offer optimum usability in the future.
The compendium directly reflects the recommended method for configuration, which is
based on the results of a great deal of practical experience. The description does not
cover the application itself; rather, it relates to handling the project and the parameter
settings of the components it contains.
Links to the Compendium

The compendium is divided into several parts:
 Part A: Configuration Guidelines
https://support.industry.siemens.com/cs/ww/de/view/107196780/en
 Part B: Process Safety
 Part C: Equipment Phases with SFC Types
 Part D: Operation and Maintenance
 Part E: Hardware Setup
 Part F: Industrial Security

Additional sources of information –
PCS 7 Compendium
Here you will find

check lists to
download
 Teil A: Configuration Guidelines

 Teil B: Process Safety
 Teil C: Equipment Phases with SFC Types
 Teil D: Operation and Maintenance
 Teil E: Hardware Setup
 Teil F: Industrial Security
Course ST-PCS7SYS
You can download the documents
2-8
on the website of Industry Online Support, product
support. Search for “Compendium” as shown in the figure below.
Sie können die Dokumente als Beiträge im Produktsupport des Industry Online Support
herunterladen. Suchen Sie nach dem "Kompendium".
Some parts consist in additional check lists supporting a project documentation.
2.3.2 PCS 7 on Tour (PoT)
PCS 7 on Tour is a compact manual with the intend to provide fundamental basics on
the system functions and an approach to engineering and configuring automation tasks.
It covers major components (hardware and software) of the system and intends to
deliver a systematic approach right from the start when you begin to know or use the
system.
The manual PCS 7 on Tour can be ordered via the Siemens Sales Support Process
Automation I IA AS S SUP PA. Please contact your local Siemens promoter or sales
department. The manual is in the following languages available:
German, English, Spanish, Portuguese

2.3.3 PCS 7 catalogs
The catalogs list those products of the Siemens automation product spectrum which are
Weitere Informationsquellen – system SIMATIC PCS 7.
released for the process control
PCS 7 Kataloge
The products contained in this catalog can also be found in the e-Catalog CA 01.
Catalogs are available in print and for download on the Product Support Portal.
Industry Online Support Navigate in the

product tree to
SIMATIC PCS 7
Course ST-PCS7SYS 2-9 SITRAIN - Siemens AG © 2014
SIMATIC PCS 7 System catalog ST PCS 7

The catalog lists the PCS 7 hardware and software products structured in a PCS 7
product structure.
The products are introduced by detailed descriptions and specifications.
Add-On catalog ST PCS AO, Add-Ons for SIMATIC PCS 7

Many supplementary add-on products for SIMATIC PCS 7 have been developed by
Siemens as well as by external partners. These software packages and hardware
components authorized by the system manufacturer enable cost effective
implementation of SIMATIC PCS 7 for special automation tasks.
Catalog PCS 7 Technology Components ST PCS 7 T

With SIMATIC PCS 7 technology components from Catalog ST PCS 7 T that can be
seamlessly integrated into the process control system, you can expand the functional
scope of the system components in a carefully targeted manner for specific automation
tasks.

2.3.4 PCS 7 in the inter- / intranet
Link to PCS 7 Website

The PCS 7 site provides convenient access to the complete PCS 7 documentation – the
latest news about hardware and software components released for PCS 7:
http://www.siemens.com/simatic-pcs7
Get into the world of SIMATIC PCS 7 with the interactive system overview.
The PCS 7 portal contains links also to following sections:

 Presales information
 Online catalog and ordering system
 Technical information
 Support
 Training
 Contact & Partners (Local and Solution partners)

2.4 Industry Online Support Internet Portal

The new Industry Online Support is here (February 2015).
The Industry Online Support is as a comprehensive information system for all Industry
automation and Drive Technologies service & support topics at any time.
Would you like to deepen your product know-how, to inform about services or
participate in a community of automation users?
You reach comfortable functions in the Industry Online Support directly for desired
information purposes. Online Support - always the first step - round-the-clock on 365
days in the year.
https://support.industry.siemens.com/cs/?lc=en-WW
Der neue Industry Online Support ist da!
2.4.1 Overview
12 10 2
3
4 5 6 7
11
Always available (on the right
above the mySupport Cockpit): 9
Course ST-PCS7SYS 1. Registering: Do you want to2 -benefit

11 from all the information available
SITRAIN in OnlineAG © 2014
- Siemens
Support and the personalization options in mySupport?
Then register for Online Support and log in before using it. And all of this is free.
Make the most of your Industry Online Support!
2. Global search: The global search input box is always available at the top right.
Global search searches all entries of Industry Online Support and clearly displays
the results on a separate result page.
In all specific filter areas, another input box is available to start the search. This
search works together with the filters and searches only entries that match the filter
values you have selected.
3. Direct access to four key areas of Online Support:
Product Support, Services, Forum and mySupport

4. Searching for product information: Product Support is the comprehensive

information system in Online Support for all questions about products and solutions
for industry. Most information in Product Support is stored in the form of entries. The
information you will find depends on the respective entry type. You can use filters to
narrow down the displayed list of entries to the desired information.
Many functions and areas of Product Support are only available when you are
logged in to Online Support. These functions include, for example, saving and
loading filter settings or downloading software packages.
5. Service catalog - overview of our services: Do you want to learn about the services
offered by Siemens Industry, find contact persons or obtain specific information on
how to proceed for the individual services? The service catalog provides you with
comprehensive information.
To go to the service catalog, select the "Services" navigation item available on each
page.
6. Forum - the communication platform for Siemens Industry products.
In the Technical Forum, you will meet a strong community that shares information
on Siemens Industry products. The community discusses questions, for example on
configuring, commissioning and product details. Of course, non-registered users
can view and browse the contents as well. If you want to use more functions of the
Technical Forum, please log in with your user name. After logging in, you can ask
questions yourself and participate in discussions.
7. mySupport is your personal workspace in Industry Online Support. In this area, you
can compile the information that is important for your daily work. mySupport offers
you a set of tools to support you in this.
In order to easily and efficiently access your important information at any time,
structure the contents as needed. You can create folders and name them as
desired, e.g. after your projects or products. In addition, you can use your own
"tags" for indexing and add personal notes - customized to your needs.
8. On each page in Online Support, the mySupport cockpit can be found in the right
area of the page. When you are logged in, it always provides direct links to your
favorites or last viewed entries in Online Support.
The mySupport cockpit additionally informs you of new personal messages, status
changes of Support Requests or completed CAx download manager jobs. On the
associated entry, a number in brackets indicates the number of new or changed
objects.
9. Copy URL and Print entry: You can copy the address of the selected entry into the
clipboard or print the entry.
10. Request for the Technical Support (Support Request)
Do you have a technical question and are looking for assistance in finding the right
answer?
The Support Request form in Online Support allows you to submit your question to
our Technical Support directly and without detours. Describe your problem in a few
guided steps and you will immediately be provided with possible suggested
solutions.
If the suggested solutions do not answer your question, a specialist will contact you
in the shortest time.

11. Mobile Use via App - Secure Siemens Support for yourself for on the road!
With our Industry Online Support App you have access to more than 300,000
documents - anytime and anywhere. Whether you have problems during the
implementation of a project, need help for troubleshooting, want to expand your
system or plan a new plant.
12. The HelpCenter will assist you in the best use of the Siemens Industry Online
Support. Here you find user information and hints to support your day-to-day work
with this portal.
2.4.2 Product support
In Product Support, you will find the following:

 Information on Product Details and Technical Data
 Manuals and Operating Instructions
Documents with all information necessary to operate or use a product. There are two
different types of manuals: Classic PDF manuals and configurable manuals (to build
your personal library in mySupport).
 Downloads of Updates, Upgrades, Service Packs and Support Tools.
The downloads are generally free, but you have to be logged in to Online Support.
 Answers to Frequently Asked Questions (FAQ)
"FAQ" is the abbreviation for frequently asked questions: A compilation of frequently
asked questions and the associated answers about a topic.
 Certificates
Approvals for sales in other countries, certificates of the successful check of rated
data according to a specific standard or for special use cases (documents in PDF
format).
 Application Examples
Application examples support you in solving your automation problems. For this
purpose, examples and tools, background knowledge, functional descriptions,
handling instructions, performance data, etc. are available to you. This area does not
focus on a specific product, but on the system-wide interaction of products.
 Characteristics
Pictorial representation of characteristics, e.g. of the current-time response of
overcurrent releases (documents in PDF format).
 Product Notes
Product-related, up-to-date information from marketing and sales; for example, sales
and delivery releases for new products.
 Technical Data
Technical key data of the selected product in a clear table.

Product support – Filters and „Breadcrumb“
navigation
Course ST-PCS7SYS 2 - 12 SITRAIN - Siemens AG © 2014
Functionality of the filters (1)

The filters in Product Support allow you to quickly, easily and conveniently find all the
information you need for your question or product. Use filters to narrow down the great
range of information to the contents of interest to you.
Depending on what you are searching for, the following filters are available:
 Product tree
 (Single-) Product
 Entry type
 Date
However, you can also simply enter one or several terms in the search box. Once you
make settings on a filter, the entry list will display all relevant results. At any time, you
can add more filters or change filters that have already been set to refine your search.
To remove individual filters or all filters, click on the "X" next to a set filter or click on the
"Clear all filters" button.
"Breadcrumb" navigation (2)

The breadcrumb is an important navigation item of Online Support. It allows you to see
at a glance where you currently are.
Click on a link in the breadcrumb to navigate to a page higher in the hierarchy. When
you do not click on a link but move the pointer over it, a drop-down menu will appear
where you can view all available areas of this hierarchy. Click on an entry to go directly
to the relevant area.

2.4.3 SIMATIC PCS 7 Summary page of the Product Support
A so-called PCS 7 summary page (quick start, "landing" Page) provides a direct access
to all relevant PCS 7 topics, technical information and solutions.
www.siemens.com/industry/onlinesupport/pcs7
Benefits of the "landing" page:
 PCS 7-movies/animations, interactive demonstrations, FAQs, new application
examples and much more are listed and sorted.
 A pdf document contains a detailed and graphically enhanced overview of the
available application examples, e.g. as print out in the offer, engineering or presales
phase.
 Icons make the assignment of the documents easier, as example archived
projects/code, step by step instructions, performance statements etc.
 Version-specific access to PCS 7 entries through the Product Views. Select directly
the desired PCS 7 version, to get all results filtered for this version.

2.4.4 Compatibility tool
Compatibility information for Automation and Drive Technology is available in the

Compatibility Tool of the Industry Online Support. The tool is designed to support you in
questions about the compatibility of various hardware and software products.
The database is constantly being revised and extended. In addition, you can use the
tool centrally to download the compatibility lists of the separate product lines as Excel
files.
https://support.automation.siemens.com/kompatool/pages/main/index.jsf
Industry Online Support Portal –

Workflow through the
1. To query thecompatibility tool you require, you must first choose a "master
compatibility information
component" (WinCC, PCS 7, STEP 7 ...).

Industry Online Support Portal –
Workflow durch das "master
2. To these Kompatibilitätstool
components" you can add more components (such as operating
systems, virus scanners ...).
3. Once you have chosen the components you require, you can have the compatibility
list shown by clicking the "Show compatibility" button.

2.5 Working with mySupport

2.5.1 Personal filters and notifications
To distinguish the types of information, mySupport is divided into so-called categories of

information (e.g., Personal messages, Filters, Tags). Each category offers specific
functions, but the operating concept is uniform - to allow you to find your way around
quickly and easily.
Only you can access all contents in the individual categories of mySupport.
Therefore, you have to log in to Online Support before using mySupport. Before logging
in for the first time, you need to register. In order to access your personal information
particularly efficiently, it is also advisable to use permanent login (see Registering and
logging in). Without login, only general information on the individual categories is visible.
Favorites
Favorites are your personal bookmarks in Online Support. Similar to the favorites or
bookmarks of your browser (e.g., Internet Explorer), they quickly take you to your
preferred entries at any time - from anywhere.
You can select your favorites in Product Support, the forum and the service area and
save them in mySupport, organize them in your own folder structure, open and provide
them with tags (keywords) at any time. You can access your saved favorites either via
the "Favorites" category in mySupport or using the "Favorites" link in the mySupport
cockpit in the right navigation pane.
Tags
When you have marked an entry as a favorite, you can additionally provide it with your
own keywords ("tagging"). From these keywords, a "tag cloud" (keyword cloud) is
automatically generated in the mySupport cockpit; the individual terms in the tag cloud
are simultaneously used as links. The more frequently you use a term as a tag, the
larger this term will be displayed. Click on a tag to simply filter your favorite entries -
there is no faster way to access your information.

Saving and managing filter settings

In the mySupport area, you can manage the filters you have created in the "Filters"
category. Simply store the filters in the (folder) structure suitable for you. You can add
notes to filters, e.g. when a particular filter is relevant. Furthermore, you can combine all
filters in a folder to one notification - you will then receive one combined notification for
all changes relating to the filters in this folder.
Working with mySupport –
Personal filters and notifications
Managing notifications
Course ST-PCS7SYS
Do you want to be informed of 2new
- 19
information concerning your interests? Then have
Online Support automatically notify you.
If you are interested in a large number of entries, identify them using a filter. If you are
interested in a single entry, mark it as a favorite.
To enable a notification, proceed as follows:
In both mySupport Filters and Favorites, you can set how you want to receive
notifications. To do so, select "Set options" in the toolbar. In the "Notifications" category,
a list of all active notifications is created based on your configuration, which gives you a
quick and easy overview.
 The transition to the new Online Support included the conversion of your existing
newsletter subscriptions to respective notifications.

Working with mySupport –
Personal
2.5.2
documentation
Personal documentation
Course ST-PCS7SYS Do 2 - 20
you want to combine documents that are particularly important toSITRAIN
you? - Siemens AG © 2014
In the "Documentation" category of mySupport, you can create your personal
document library. You can use this library online in mySupport or generate it in different
formats for offline use.
Naturally, you can also share your personal library with other mySupport users in
mySupport. This allows you to create a collection of relevant documents for your subject
area very efficiently that you can use together with colleagues. Regardless of whether
you are working alone in an office or with colleagues at different locations or traveling,
you can access your personal collection of documents from anywhere.
 Up until now, this function has been offered to you in MyDocumentationManager for
configurable manuals. The integration in mySupport makes it even easier for you to
apply entries to your library. In addition, the entire scope of entries is now available to
you. You can apply all entries from Industry Online Support to your libraries, i.e. also
FAQs or product notes.
And if you have already worked with MyDocumentationManager, all libraries you
have created will, of course, still be available in their entirety in mySupport - none of
your work will be lost.

Arbeiten mit mySupport – SIMATIC PCS 7 AS Engineering
Persönliche Dokumentation
Building your personal library
4 2 3
In your personal library, you can create your own folder structure as you would in the
folder structure of a file board. You can store entries from Online Support in the folders
and build your personal collection of documents. You can customize the structure of the
library to your needs, for example to the structure of your plant or projects.
You can apply entries to your personal library directly from an entry list or the entry
display. Applying an entry to your personal library generates a copy of the original entry
for your own use. This copy will be available to you until you delete it. This applies even
if the original entry is revised or deleted in Online Support.
1. Once a library has been created, you can change it at any time in "mySupport
documentation". Use the "Configure" function in the context menu to show the
structure of your personal library in a second area in addition to the content area. It
allows you to conveniently make comprehensive changes using drag and drop.
Fully configurable manuals are a special case. When you insert a manual of this
type into a folder, the entry will not only be displayed in your folder, but the entire
chapter structure, including contents, will additionally be applied to your folder. This
allows you to easily navigate through the manual. And if you only need parts of a
manual, you can apply only these specific parts to a folder of your library. You can
also subsequently change and restructure a chapter structure that has been
applied.
2. You can let yourself be informed about changes of the entries which are contained
in your personal documentation automatically. You can activate and adapt the
automatic update service with the button "Settings". You select the language, the
interval (day, week, month, quarter) and the norm according to which warning signs
shall be carried out to upcoming updates (ISO, ANSI
3. Using the update function you can synchronize your personal documentation with
the current state of the entries contained in it. This way your documentation always
remains up-to-date. You can take on or reject upcoming updates with the button
"Updates".
4. My productions: When exporting, the contents of the selected folder and all
subfolders are transferred to a file you can save to your location and process. You
can export the contents of any folder of your library - regardless of whether you
have created the folder yourself or applied it from a default document. (In
MyDocumentationManager, these functions were available to you in "Generate".)

2.6 Support Request
To create a Support Request, different options are available to you in Online Support:
 You will find the "Support Request" option in the menu on all Online Support pages.
 Alternatively, you can create a new request in mySupport in the "Requests" category.
 Or directly click on the following link:
http://www.siemens.com/automation/support-request
Tips for creating a request:
 Select your product and use case as accurately as possible; try to avoid selecting
"Other". By doing so, you ensure optimum support by our experts and appropriate
suggested solutions.
 Did other users have a similar problem? This step already offers frequent problems
and solutions. Take a look – it will be worth your while!
 Describe your problem with as much detail as possible. Pictures or explanatory
attachments allow our experts to consider your problem from all sides and develop
solutions. You can upload multiple attachments up to 10 MB per file.
 Before each sending, verify your personal contact information and the data you have
entered. The final step additionally offers the option to print the summary.
As a logged in user, you can track the status of your requests online. To do so, navigate
to "My requests" in the "Requests" category in mySupport.

2.7 Forum - the communication platform for Siemens Industry

Industryproducts
Online Support Internet Portal –
Forum Conferences and Forum management
2.7.1
1
2
Course ST-PCS7SYS
1. On the left side, you will find the so-called conference tree.
2 - 23
It allows you to
navigate through the individual discussion areas.
2. The conference overview is the central discussion area of the Technical Forum.
This is where the community meets to discuss technical questions about Siemens
Industry products.
3. In forum management, you will find your personal control center for the Technical
Forum. It allows you to manage your specific profile data and filters.

Conference filter
Add conferences to your personal filter of preferred conferences.
This allows you to enable a notification that informs you when new topics are started in
these conferences.
In Quicklinks, the Technical Forum additionally offers an overview page that contains all
topics of your preferred conferences.
Managing profile
Profile management provides interesting information and functions:
 You get an overview of your activities in the Technical Forum.
 You can view your rank, any special permissions and your ranking progress.
 You can store a signature and a personal description for your profile in the forum.
 You have direct access to the quick links to get an overview of all topics you have
contributed to.
User filter
Have you found a user in the Technical Forum who posts entries that are particularly
interesting? Then add this user to your list of "preferred users".
This allows you to enable a notification that informs you when the user has posted a
new entry.
In Quicklinks, the Technical Forum additionally offers an overview page that contains all
topics of your preferred users.

Industry Online Support Internet Portal –
Interaction in the conference view
2.7.2 Interactions in the Forum
Creating a new topic in

a conference
Industry Online Support Internet Portal –
Interaction in the forum
Status: Topic from Rating of
solved conference overview the topic
Topic from
conference overview

Creating a new entry
for the topic
Reacting to an
existing entry
Feedback for the

individual entry
Creating a new entry

Do you want to create or format a new entry? The entry editor provides all the
necessary functions.
 You can upload and publish in the forum a file with "Add attachment".
 You would like to check before the publication how your entry will actually look? A
preview is available for this purpose.
 You would like to look at the topic again to which you create an entry? Please, you
used the link over the input area (right mouse button > open in a new tab or window)

Posting / replying to an entry

Do you want to participate in an existing discussion with your own entry? Click on
"Reply" and post your personal entry to support other users in answering the question.
 Use the "Reply" link to go to the entry editor and create a reply without quoting the
entry.
 If you want to quote the entry, possibly only excerpts of it, use the "Quote" link. The
content of the quoted entry is then displayed accordingly in the entry editor.
Rating an entry / saying thank you

Do you find an entry particularly interesting? Use the available functions and rate the
entry or say thank you to provide personal feedback. Ratings and thank yous are the
rewards our community members get for the support they provide. When you rate an
author or entry, this will be added to the already existing ratings. The average value of
all ratings is displayed.
Aside from feedback to the author of the entry, you also draw other readers' attention to
particularly valuable entries and helpful authors.
2.8 Task and Checkpoint
Task: Software compatibility
Goal
Find out which current version of virus scanners is compatible with your engineering
software.
Use all information sources available:
 Readme files in the installation folder
 The compatibility tool of the Industry Online Support
 Entries in the Product support
 Entries in the Forum
 Create a Support Request.
Checkpoint
Checkpoint
Let‘s think about this:

 Name some reasons for
registration in MySupport.
 What do you think is the best way
to have always the latest version
of the required manuals for your
job with you?

Content 3
3 PCS 7 Project handling ........................................................................................... 3
3.2 Multiproject engineering ......................................................................................................... 3
3.2.1 Storage location for multiprojects in case of distributed engineering .................................... 3
3.2.2 Principle of the multiproject .................................................................................................... 5
3.2.3 Project structures ................................................................................................................... 7
3.2.4 Cross-project functions .......................................................................................................... 9
3.2.5 Multiproject: update projects…networks and connections .................................................. 11
3.2.6 Task and checkpoint ............................................................................................................ 13
3.3 TCiR ..................................................................................................................................... 13
3.3.1 The Master Data Library ...................................................................................................... 13
3.3.2 Central update of block types in charts ............................................................................... 16
3.3.3 Data management in case of activated TCiR ...................................................................... 17
3.3.4 How “TCiR: Download required!” Works ............................................................................. 19
3.3.5 TCiR – Block Update after an Interface Change ................................................................. 20
3.3.6 Type change in RUN with local type update in CFC ........................................................... 23
3.3.7 Consequence of TCiR on the OS: Best Practice Procedure ............................................... 24
3.3.8 Summary TCiR .................................................................................................................... 26
3.4 Multiuser engineering - Configuration in the network .......................................................... 29
3.4.1 Preconditions ....................................................................................................................... 30
3.4.2 Parallel working in the AS project ........................................................................................ 31
3.4.3 Overview about distributed project organization .................................................................. 34
3.4.4 Organization in the multiproject net ..................................................................................... 34
3.4.5 Organization without multiproject net .................................................................................. 36
3.4.6 Dividing the multiproject without network interconnection ................................................... 38
3.4.7 Recommendations ............................................................................................................... 39
3.4.8 Tasks and checkpoint .......................................................................................................... 40
3.5 Comparing project versions with the Version Cross Manager ............................................ 41
3.5.1 How to Compare Project Versions ...................................................................................... 42
3.5.2 Result of the comparison ..................................................................................................... 43
3.5.3 Display of Changed States .................................................................................................. 44
3.5.4 Other ways of calling VXM ................................................................................................... 44
3.5.5 Display program changes since last download ................................................................... 45
3.6 Version Trail / Automatic archiving and readback ............................................................... 46
3.6.1 Option package "SIMATIC PCS 7 Version Trail" ................................................................. 46
3.6.2 Version Trail user interface .................................................................................................. 47
3.6.3 Introduction to automatic jobs for archiving and readback .................................................. 48
3.7 License management .......................................................................................................... 50
3.7.1 License types ....................................................................................................................... 50
3.7.2 Handling licenses with the Automation License Manager ................................................... 50
3.7.3 Remotely using License Keys on a license server .............................................................. 52
3.7.4 Checking License Keys ....................................................................................................... 52
3.7.5 Recovering License Keys .................................................................................................... 53
SIMATIC PCS 7 – PCS 7 Project handling

3.7.6 Calculating the process objects for the SIMATIC station ("AS RT PO") and for the OS ..... 55
3.7.7 Booking back Process Objects ............................................................................................ 56
3.8 Current License model with CPU 410-5H ............................................................................ 57
3.8.1 Overview PA Controller CPU 410 V8.1 ............................................................................... 57
3.8.2 System Expansion Card and System Expansion Packages ............................................... 58
3.8.3 Steps for online upgrade of PO volume in brief ................................................................... 61
3.8.4 Creating the PO Activation file ............................................................................................. 62
3.8.5 Sending the PO-Activation file to Siemens .......................................................................... 65
3.8.6 Transferring the PO-Release file and activating the volume ............................................... 67
3.8.7 Use cases for Upgrade of PO volume on redundant AS ..................................................... 69
3.8.8 Online-check of the System Expansion Card ...................................................................... 70
3.8.9 PO-Upgrade - Summary ...................................................................................................... 71
3.8.10 Checkpoint ........................................................................................................................... 71
3.8.11 Changes in the License information .................................................................................... 72
3.8.12 Further facts for compiling and downloading into CPU 410-5H .......................................... 74

3 PCS 7 Project handling

Learning target
3.1 Learning targets

 The features PCS 7 provides for
Multiproject- and Multiuser-Engineering
 The advantages of the Master Data
Library
 The current license conception with the
CPU 410-5H and the steps for the
Online Upgrade of the PO-Volume
The participant will be able to
 Use the possibilities in PCS 7 for

multiproject and multi-user engineering
 Perform a update of block types without
CPU stop
 Compare PCS 7 project versions
 Book back process objects
3.2
Storage Multiproject
location for engineering
Course ST-PCS7ASE
multiprojects in case of
distributed
3.2.1 engineering
Storage location for multiprojects in case of distributed engineering
… prior to the CREATION of the multiproject:

Share the storage location!
Shares are only No additional shares in

permissible on subordinate or
one level! superordinate folders!
Conditions
When projects within a network are distributed among different computers, the following
prerequisites must always be met:
 To work in the network, Windows 2008 Server must be installed on the central
engineering station. The distributed engineering stations can use the Windows 7 or
Windows Server 2008 operating systems.
 The storage location of projects within the network is specified in UNC notation: e.g.
Course ST-PCS7ASE \\computername\sharename\storagepath
and not designated with the letter of the drive
(e.g. D:\projects\storagepath...).

Requirements
If you want to distribute projects on different computers within a network, the following
conditions must always be met:
 The projects are located in folders that are shared for read and write access.
 The folders in which the multiproject or the projects are to be located must be set
for sharing before the multiproject is set up.
 The share names must be unique within the network.
 The shares and share names of the resources (folders) involved in the
multiproject must not be changed.
Reason: when a project is inserted into the multiproject, PCS 7 generates a
reference to the location of this project. The reference depends on the share and
share names of the resources involved.
 A project can only be found using the share name under which it was included in
the multiproject.
 For security reasons complete drives should not be shared.
 Folders must only be shared in one hierarchy level.
 PCS 7 must be installed on the computers where the folders containing the projects
are located. PCS 7 provides the necessary database server functions for accessing
the projects.
 If you include projects for which you have configured messages in a multiproject,
Storage location forthemultiprojects
make sure that inofcase
message number ranges ofdo not overlap if you are
the CPUs
using project-oriented assignment of message numbers. If you use CPU-oriented
distributedmessage
engineering
number assignment, such overlapping does not occur.
If you execute cross-project functions, we recommend consolidating all projects on one
programming device/personal computer.
… prior to the CREATION of the multiproject:
If you want to execute cross-project functions while the projects are distributed on
Share
different computers the
then storage
comply withlocation!
the following:
 All the computers on which the projects and the multiproject are located can be
reached over the network during the entire editing time.
 While class-project functions are executing, no editing must take place.
 If the folder in which you create the multiproject was not shared before creating the
multiproject, the UNC path for the single projects won’t be available in the
Shares are
multiproject. Nevertheless thisonly
can be solved by removing the single projects from the
No additional shares in
multiproject andpermissible
reinserting them
onagain after having shared the containing folder.
subordinate or
one level! superordinate folders!
The figure below shows what the single projects in the multiproject should look like.

Multiproject Engineering –
Principle
3.2.2 of the multiproject
Principle of the multiproject
Engineering Server
Multiproject
Project 1 Project 4 Project 7 Master Data
Library
AS OS ES
Project 2 Project 3 Project 5 Project 6
AS AS AS AS
Engineering Station 1 Engineering Station 2 Engineering Station 3
The multiproject functionality of SIMATIC PCS 7 provides the option of flexible and
performant project engineering for plants. The main emphasis is placed on parallel and
time saving editing of individual projects which can be managed, divided and merged
with system support.
Principle of the multiproject

Multiproject is a higher-level structure in the SIMATIC Manager of the central
Engineering Server. It comprises all projects of an automation solution with its
subordinate objects (automation systems (AS), operator stations (OS), programs, plans,
etc.) as well as master data library.
For processing the contained projects they are distributed between decentralized
Engineering Stations (ES). The engineering process is optimized using additional
memory resources and computer performance. The projects can remain in the
multiproject or be separated from it for the duration of processing. The Engineering
Server on which the multiproject is filed is a complete engineering station in itself, on
which a project or the master data library can be processed.
Despite of the decentralized storage, the individual projects can have interproject
relations such as S7 connections.
All the projects and the S7 programs must have unique names within the multiproject.

Multiproject Engineering –
Benefit by cross-project mechanisms SIMATIC PCS 7 AS Engineering
Benefit of the multiproject
• Master data library with block types, process tag types, control module types and models
• Updating the Plant Hierarchy across all projects or for selected projects
• Functions "Create/Update block symbols" and "Create/Update diagnostics screen" (for identically
named PH) considering all related AS and OS components in the entire multiproject
• Merging subnets and connections with text references of all contained projects
• OS compiling with configuration data of several projects
• Save as (copy of the multiproject with all projects)
• Archiving (zip-archive of the multiproject with all projects)
If projects are part of a multiproject, they can be generated in smaller scope and for
better overview. Inter-project mechanisms ensure that a multiproject can be used as
one project.
Course ST-PCS7ASE Examples of such inter-project 3mechanisms
-5 are: SITRAIN - Siemens AG © 2016
 Master data library for central data management of block types, process tag types,
control module types and models for all projects
 Updating the Plant Hierarchy across all projects or for selected projects
 Considering all related AS and OS components in the entire multiproject for the
functions “Create/Update block symbols“ and “Create/Update diagnostics screen“ (for
identically named PH)
 Merging subnets and connections with text references of all contained projects
 OS compiling with configuration data of several projects
 Save as (copy of the multiproject with all projects)
 Archiving (zip-archive of the multiproject with all projects)
 In the PCS7 environment it is always recommended to set a multiproject with master

data library even if only one project is contained.

3.2.3 Project structures
Project-specific setup
This type of project division is used preferentially if only few project engineers and
engineering stations are available.
Each individual project contains only one AS and one OS, or all AS and OS which a
project engineer is meant to edit.
From a technical
Project structures: point of view, the project
Project-specific setupcontains AS objects, such as CFC and SFC
plans, as well as OS objects, such as images and reports, as illustrated in the figure
below.
AS('s) and corresponding OS('s)

are stored in the same single
project and are engineered by the
same programmer

Advantages Disadvantages
It can be configured and tested in the project, All AS charts can only be assigned to the available OS
complete with AS and OS. in the same project via the plant hierarchy.
The mode of operation during configuration and A later division (outsourcing of individual AS or OS from
commissioning is the same. one project) requires detailed knowledge of the
It is possible to copy complete plant sections corresponding steps necessary. That is why the project
including the update of OS objects. should be divided as well as possible, right from the
beginning.
There is a common view in the plant hierarchy,
which includes the AS and OS in a project.

Station-granular setup
The station-granular setup is recommended if an extensive project is being edited by
several project engineers.
As opposed to the project-specific setup, all AS and OS are filed separately (granular) in
Project structures:
an individualStation-granular
project. setup
Hence, in the AS project there are no OS objects, and no AS objects in the OS project.
AS('s) and corresponding

OS('s) are stored in
different single projects
and can be engineered by
the different programmers

Advantages Disadvantages
The biggest possible division ensures the highest Tests of AS and OS during configuring are carried out
flexibility in the assignment of individual projects on separate ES (provided that the decentralization has
to the project engineers and also offers the best taken place).
performance in processing speed. Changes in the plant hierarchies (PH) of projects have
During commissioning, engineering stations can to be synchronized again in the multiproject after
be added or removed in order to respond flexibly editing.
to varying staff availability. It is not possible to copy complete plant sections
including the update of the OS objects.
 See [1001] Application description 22258951 MP-MU Engineering - 10_2015, 1.3 for
more information.

Boundary conditions
In order to carry out the subsequent project work as rationally as possible, some
preliminary considerations are necessary.
With regard to the issue of how to properly separate the overall task in part
configurations, one must consider individual conditions of the project itself, as well as
those of the available engineering environment. Here are a few examples:
 Number of project engineers: How many automation systems must be configured and
in what time? Where can ratio effects be used when configuring?
 The number of available engineering stations: Each project engineer who is
responsible for one or several automation systems, has an ES available.
 Networking of the engineering stations: Normally, all engineering stations should be
connected consistently to each other via the terminal bus.
 Project complexity: How many areas should be automated in the multiproject. In how
many buildings will there be an ES or an OS server positioned at a later stage?
Which automation systems are assigned to which OS server
 Configuration duration/effort: The duration can be controlled by the number of
planned project engineers.
The following rules apply:
 Only those project components (AS, OS), which are required for the respective
distributed processing should be temporarily moved to a distributed ES.
 Only entire projects can be moved to a distributed ES. If you want to edit and test
individual sections of the plant hierarchy separately from the project, you can apply
the "Branch and merge" concept (refer to the PCS 7 Engineering System manual).
 An ES is defined for each operator station, which allows the OS to be compiled and
the OS project to be downloaded.
Based on these considerations and the background information from the above
comparison, the structure of the multiproject can be predefined.
3.2.4 Cross-project functions
Update access protection

…inherits the access rights to projects defined at the selected project, for which no
access protection has been activated yet, and to the projects for which the user has
been authenticated as project administrator.
To be able to use the function "update in multiproject" you must be authenticated as
project administrator in the SIMATIC Logon Admin Tool: in the SIMATIC Manager under
Options > Access protection > Update in Multiproject
Update shared declarations

…publishes the units / enumerations / equipment properties stored there to all or
selected projects: with right-click and select to "Multiproject" or "Shared declarations" in
project / (master data) library
Shared Declarations > Update in the Multiproject

Update process tags

If you change the process tag type and it is then located in the master data library, the
process tags existing in the multiproject are principally automatically updated. If
changes have caused inconsistencies between process tag type and process tag, (e.g.
because not all process tags of the project could be reached during the automatic
update) the update can also be performed explicitly – of course under the precondition:
the process tags now exist in the multiproject: select the changed process tag type in
the master data library and via right-click and select
Process tags > Update…
Update plant hierarchy

When working in the multiproject it is necessary in some cases to create identical
folders of the plant hierarchy - at least in parts - in all or individual projects of a
multiproject. Two application cases are:
Multiuser operation possible:
 For SIMATIC BATCH the folder labeled as "Plant" is in all projects required in the
first hierarchy level.
 The identical name of the plant hierarchy in the individual projects of the multiproject
enables recognizing related AS and OS parts for the following functions:
 Create/update block icons
 Create/update diagnostic pictures.
Updating the plant hierarchy in the multiproject enables saving multiple configurations
and the project can be protected from unintentional changes which would cancel the
uniform name.
Apply function
There are several ways to call up this function, if you have selected a multiproject, a
project or a hierarchy level in the plant view:
 The menu command
(Options >) Plant hierarchy > Update in the Multiproject…
 via right-click and select: a dialog window is opened in which you can select the
following options:
 Combining all PH of all projects of the multiproject:
All hierarchy folders are determined in the entire multiproject and this total
amount is created in all projects of the multiproject.
 Export PH of a project into other projects:
Depending on the selection the plant hierarchy of a project selected as template
(or a hierarchy level) is exported into other projects of the multiproject. The
export target can be selected in a further dialog field. There all projects of the
multiproject - except the template project - are labeled as selected. The projects
not desired as export target can be deactivated here.
Result:
In the target projects existing hierarchy folders without identical names are created new
and assigned with the properties of the template folder.
The recreated folders are labeled as "Links" and are only contained as representatives
for the template folder in the hierarchy - optically this is represented with the link ion at
the hierarchy folder.

Hierarchy folders with identical name are recognized in the target project and not
created new. However, they also receive the properties of the template folder. The
Multiproject: Adjust
migration of aprojects…
project with already existing redundant PH configuration is possible.
Merging networks and connections
3.2.5 Multiproject: update projects…networks and connections
Multiproject
System bus (universal subnet through update)
Project 1 Project 2
ES1 ES2
PC1 PC2
Network 1 Network 2
Connection 1 Connection 2
with reference with reference
P C XYZ P C
C AS XYZ C AS
S P S P
P 01 P 02
U U
Project 1 If project 1 on ES1 is not yet included in the multiproject, you can use NetPro, for
example, to configure "Network 1" as the system bus. Connections originating from
AS01's CPU to a station that is not in the same project 1 are set up as connections to
Course ST-PCS7ASE a station in an "unknown project".
3 - 8 For this type of connection,SITRAIN
a "Connection
- Siemens AGname
© 2016
(reference)" is entered in the Properties dialog box (e.g. "XYZ"). It is called an "open
connection".
Project 2 The following applies correspondingly: ... a "Connection name (reference)" is also
entered in the Properties dialog box (e.g. also "XYZ").
Updating projects
From SIMATIC Manager
Subnets and connections that were originally created in separate projects can be
merged as part of the "project update" via
File -> Multiproject -> Adjust projects
The subnets that originally had their own names (e.g. "Subnet 1" and "Subnet 2") are
merged under a new name (e.g. "system bus").
"Open connections" from the two projects having the same reference are closed.


 Connections in different projects that will be subsequently combined in the

multiproject must have the same connection name (references = "XYZ").
The procedure described above can be omitted when the projects have already been
added to the multiproject when the connection is created. If this is the case, when you
set up a connection in NetPro, "the other station" in the selection screen form is
offered and selected via the multiproject.
From NETPRO
Merging Subnets in NetPro
Update project-wide networks

The same adjustments made in NETPRO:–
andbeconnections
can also
SIMATIC Manager
Course ST-PCS7ASE 1. Menu vs.
EditNetPro
-> Merge /4 -Unmerge
9 Subnets -> Ethernet subnets
The following variations occur in the execution:
SIMATIC Manager NetPro
In the SIMATIC Manager, the only In NetPro, you can also assign connections that
connections that are merged are those in the have similar or different connection names.
projects that were configured as "Connection
partner in other project" with identical
connection names (reference).
When merging in the SIMATIC Manager, it is When you merge in NetPro, the partner always
not possible to foresee which connection adapts its connection properties to those of the
partner retains the connection properties and local module. Apart from this, it is also possible
which connection partner adapts its to change the properties of connections in the
connection properties (for example, active dialog box for merging connections in NetPro.
connection establishment).
S7 connections to an unspecified partner are S7 connections to an unspecified partner can
ignored. be merged to a cross-project S7 connection in
NetPro.

Course ST-PCS7ASE
3 - 12 3 - 11 SITRAIN
Course - Siemens
folder, V8.2.0,AG © 2016
ST-PCS7ASE
3.2.6 Task and checkpoint
Task: Project-specific to station-granular setup
Goal
Split the project Proj0x into ASProj0x and OSProj0x by moving AS0x to another project
Task: Multiproject engineering
in the multiproject.
Checkpoint
Checkpoint
What do you think …

 Are possible arguments for either
a project-specific or a station-
granular setup?
3.3 TCiR
3.3.1 The Master Data Library
Centralized data storage in the master data library is a requirement for essential PCS 7
The masterfunctions
data library
such as the Import/Export Assistant, the automatic block import into all S7
programs in the multiproject, etc.
… is part of the multiproject

and is therefore also archived!
... is binding for all project
engineers in the entire multiproject!
… is the only library in the

multiproject!
... ensures that the blocks are

consistent in the entire multiproject!
... offers user-friendly

import/export functions!
SITRAIN
 ATTENTION!
Only blocks from the master data library must be used for configuration. This ensures
that all S7 programs will use the same block types. Siemens AG © 2012

The master data library also ensures that all project engineers work on the same
database. This setup facilitates coordination and organization during the engineering
phase as well as subsequent project expansions/upgrades.
Source Library
The following libraries can be used as master data library:
 Existing standard library (e.g. copy of PCS 7 Library)
 Sector-specific library
 A newly generated project-specific library.
"Blocks" folder
Adaption ofInathis
system attribute for a block parameter
folder the block types used in the projects are copied from the existing libraries
in the blockand
folder of ifthe
adapted, master
necessary, e.g.data library
attributes (S7_visible, S7_m_c, etc.); or new blocks are
created in this folder.
Example: “Operator
control and monitoring”
system attribute for the
selected parameter
Additional entries
because the parameter
is an APL structure
To do so, proceed as follows:
Course ST-PCS7ASE
1. Open the "Blocks" folder of3 the
- 15
S7 Program in the component view of the master
data library.
2. Open the desired block in the LAD/STL/FBD editor by double clicking the block.
Confirm the message saying that the block is protected with "OK".
3. Open the declaration table of the block and open the properties of the respective
parameter via right mouse button > Properties.
4. Select the tab "Attributes" and change the desired attributes.
"Charts" folder
The same applies to charts (CFC, SFC and SFC types) or CFC templates, e.g. from the
PCS 7 Library or projects.

"OS" folder
The library can also include OS graphics and reports.
Advantages:
 It is possible to create models containing the interconnected CFC and SFC charts
AND the pictures for the OS. If the model is copied, or replicas are made using the
IEA, the pictures will be automatically adapted.
 It is possible to store process pictures as template in the master data library.
 User faceplates can be stored in the master data library.
 The OS in the master data library can be used as storage location for project
functions, trend picture templates, reports, scripts, etc…
Global Declarations
E.g. units, enumerations (control strategy in BATCH) and Equipment properties
(SIMATIC BATCH).
Plant View
A special feature of a master data library in the multiproject are the folders displayed in
the plant view
 Process tag types and
 Models.
Both are generated by means of the "Import/export assistant" or the PCS 7 "New
Project" wizard.
Process tag types

…are CFC templates / chart templates / "signal-neutral" function-oriented sample charts
that are derived from an original chart by the "Import/export assistant" and which can
then be imported into the project based on the type-instance concept.
Models
…are templates from hierarchy folder (HF), i.e. a hierarchy folder with any subordinate
hierarchy folders + CFCs + SFCs + graphics (when AS+OS are in the same user
project!) of a subsystem.

Updating of block types in charts

3.3.2 Central update of block types in charts
Course ST-PCS7ASE
If a project-specific modification3 -(e.g.
16
changed attributes) is implemented with blocks in
the master data library (or library of the MP) the action above in the SIMATIC Manager
offers a central and simple possibility of updating these blocks in the AS or S7
programs. The blocks to be updated are selected in the folder "Blocks" of the (master
data) library and the update process is started via
Updating of block types in charts
Options > Charts > Update block types…
TCiR activation is only for CPU 410-5H available!
2
3

Step 1(3)
Here it is checked whether these blocks exist in the AS or S7 programs (selectable!) of
the multiproject and whether they differ from the blocks in the master data library (time
stamp).
"Download in RUN" column:
This column displays a check box when the following condition is met:
1. The program is in a CPU 410-5H PA.
2. Downloading of changes is possible for this program, i.e., there is no requirement
that the whole program be downloaded.
By selecting the check box, a type update in RUN can be performed for this program
(possible only in a CPU 410-5H PA). In addition, the “Calculate...” button is displayed in
the "Resources" column.
Step 2(3)
As a result, the programs that contain the block types that differ from the ones in the
master data library are displayed. Furthermore, in the field "Consequences" it is shown
which effects the update has on the respective AS.
The update can now be executed by clicking on "Complete" or it can be canceled.
 "WORST CASE": If, for example, the interface of a block type is changed, in the field
"Consequence" it will be indicated that the AS can now only be loaded in the STOP
mode. If this is not possible at the moment, the process can be canceled and the
update can be implemented as soon as an AS STOP is possible.
Step 3(3)
Here the protocol for the "central type update" is output.
The CPU 410-5H Process Automation (CPU 410-5H) supports the type update in RUN
mode. This function is supported by the CPU 410-5H with FW 8.1 or higher and PCS 7
V8.1.
It allows you to update the instances after making interface changes to block types and
download them to the target system in RUN mode. If you are using a different CPU
type, an interface change is still only possible in STOP mode.
The abbreviation “TCiR” is also used for this function. It stands for “Type Change in
RUN”.
3.3.3 Data management in case of activated TCiR
To ensure that the changed functions can be integrated into the instances without loss
of data, double data storage is temporarily required.
This applies to DBs and PBC instances. The following tables list the data blocks used in
dependence on the functions executed. Furthermore, temporary work memory is
additionally required when downloading and integrating in the AS.

TCiR – Type Change in Run –
Data management SIMATIC PCS 7 AS Engineering
Initial state 5 instances of an integrator block are downloaded in the AS

Block container offline Online AS
Instance Data block Instance online in AS
I1a DB120 I1a DB120
I2a DB121 I2a DB121
I3a DB122 I3a DB122
I4a DB123 I4a DB123
I5a DB124 I5a DB124
State after Block container offline Online AS

compiling Instance Data block Instance Data block
I1n DB120 DB130 I1a DB120
DB‘s are deleted but not yet

released for new allocation
Initial state
In the following example, 5 instances of an integrator block are offline in the block folder
and downloaded in the AS. Each instance uses one data block.
State after compiling

TCiR – Type
AfterChange
the changein
to Run –
the integrator, a type update was performed and therefore the
instances were replaced. Ixa (old) was replaced by Ixn (new). After compiling, a new
Data management
instance DB was created offline for each instance. However, the old instance DBs are
still being used online in the AS.
State during Block container offline Online AS

download of changes Instance Data block Instance Data block
I1n DB120 DB130 I1a I1n DB120 DB130
Moving of parameter values

from old to new DB‘s
State after download Block container offline Online AS

(TCiR completed) Instance Data block Instance Data block
I1n DB130 I1n DB130
I2n DB131 I2n DB131
I3n DB132 I3n DB132
I4n DB133 I4n DB133
I5n DB134 I5n DB134
DB120, 121, 122, 123, 124 are
released for new allocation now.

State during downloading

The changes are transferred to the AS. The AS temporarily contains the “old” and “new”
integrator block. Furthermore, it contains the “old” and “new” instance DBs.
State after downloading (TCiR complete)

When TCiR has been successfully completed, the “double” data blocks are released. In
the CFC, they can now be used for new functions.
Steps of the download procedure
3.3.4 How “TCiR: Download required!” Works
Information from the Update block types with activated TCiR
Copy table and job list

Copying the modified FBs and the new instance DBs
1
into a new memory area of the CPU RAM
Copying the content of the old instance DBs into the

2
new instance DBs, conform the copy table
Cyclic block
processing remains
stopped. Chaining: Switching the execution from the old FBs to
3
the new FBs; assigning the new addresses
Deleting the old instance DBs, releasing old memory

4
areas
The following basic steps are then performed during a subsequent download of changes
of a program with changed interfaces on the block instances:
1. The modified FBs and the new instance DBs are copied to a new memory area of
the CPU RAM without overwriting the old versions.
A copy table is created and downloaded to the CPU as a job list. The information
for this copy table was collected during the previous central type update with the
“TCiR” option checked.
2. If necessary, the current contents of the previous instance DBs for the old FBs
are copied to the new instance DBs according to the copy table.
3. An integration takes place during which editing is switched from the old to the
new FB versions. For processing the FBs (with the same numbers), the new
addresses are assigned in the memory area. Integration also includes the
handling of the PBC instances.
4. The old instance DBs are deleted. The old memory areas for the FBs are
released.
Cyclic program execution of the CPU is stopped for the entire duration of these 4 basic
steps. It does not continue before they are completed.
The number of changed block types and the required modifications to the S7 program
influence the synchronization time.


3.3.5 TCiR – Block Update after an Interface Change
Update block types
A block is updated or a modified block is loaded to the master data library.
1 Activate this option for TCiR!

Update block types with changed default values
3
CPU 410-5H with PCS7 V8.2,

changed default value
1. Start the central update of block types in the SIMATIC Manager via the menu
command:
Options > Charts > Update Block Types…
A dialog box appears where the “Download in RUN” option is checked for the CPU
410-5H. This dialog box also indicates that this function is only possible for the CPU
410-5H.
2. The "calculating…" button provides you with information on the temporary resource
requirements in the AS in which the type change should be made.
3. Click on the “Next” pushbutton. All modified block types in the selected programs
are determined.

4. Beginning from CFC V8.2 it is possible to download block types with modified
TCiR – Type Change – in the interface using the TCiR option too. All changed
in Runvalues
default parameter
parameter
Durchführen der values are listed in detail with the former and the new default value.
Bausteinaktualisierung
Up to PCS 7 V8.1 a download of such blocks was not possible using TCiR and a
CPU stop was required. Confirming this dialog continues to the next page of the
"Update block types" dialog.
CPU 410-5H with FW 8.1:

TCiR is available
5
6
Adapt the new default values conventional CPU,

for already configured blocks, TCiR not available
or keep the old values
5. During the Type change in RUN in case of modified default values, the user can
choose between 2 options, which are applied for all modified default values in all
Course ST-PCS7ASE corresponding instances. A3 -partial
24 SITRAIN values
selection of individual default - Siemens or
AG individual
© 2016
instances is not possible.

 The former default values are kept in all existing instances of the block type.
 The new default values are written in all existing instances of the block type.
6. In this step, the display shows whether the type change can be carried out in the
RUN state on the basis of the resource calculation in the "Consequence" field. The
user has to evaluate that the required resources for the performance of the TCiR
are available.
7. Click "Finish". Wait until the updating procedure has completed successfully. A log
file is displayed at the end of the procedure.
 Determine the number of instances being capable for monitoring and operation, resp.
relevant for communication jobs in the Chart Reference Data, tab "Statistics".
You get the number of temporary required instances per block type from the tab
"Block types".
Use the extended message configuration dialog of a block to determine the number
of PBC.
 See FAQ "How can you determine the quantity framework of the communication
instances (PBC) for PCS 7 automation systems?" for more details.
https://support.industry.siemens.com/cs/de/de/view/2446042/en
 However, if there are not enough free data blocks or PBC in the AS, you cannot
download in RUN despite the calculation with the result that “Download in RUN is
possible”.
Before downloading, make sure that the changed blocks meet the TCiR requirements
and no undesired plant states can be caused by the changes.
The performed update of block types is summarized in a protocol.

TCiR – State TCiR: SIMATIC PCS 7 AS Engineering
Download required!
State TCiR: Download required!
An Block types update has been

passed with the option „Download
in RUN“

If the "Download of changes to CPU in RUN mode" option is enabled, a status indicator
("!" symbol and supplementary text) appears in the status bar of the CFC editor after
closing the dialog box to inform you that a download to the CPU is still required.
The program is subsequently compiled (completely) and downloaded (only changes) as
usual.
If several type updates are carried out prior to downloading and download in RUN mode
should remain possible, the "Download of changes to CPU in RUN mode" option must
be enabled for each type update. This means if one of the previous type updates was
performed with this option disabled, a subsequent download is no longer possible in
RUN.

3.3.6 Type change in RUN with local type update in CFC
Local update of block types in CFC requires that the regarding block types were
TCiR – Typemanually
Change ininto
copied Run the –
offline block folder of the AS program.
Local update in CFC
In CFC editor, the "Block types" dialog is opened with the menu command Options >
Block Types....
TCiR – Type Change

Then, in Runin–the "Chart folder" list and the "New Version ..." button is now
a block is selected
Versionsimport
operable.im CFC
If the block has been changed, clicking the button opens the "Import new
versions - ..." opens the dialog box. In case of modified default values the previous
default values and the new default values are displayed.
Activate this check box for TCiR!
After
Course ST-PCS7ASE confirming with "Yes", the CFC
3 - 26indicates again the status "TCiR:
SITRAINDownload
- Siemens AG © 2016
required!" The local update procedure does not provide a calculation option to estimate
the temporary required resources.

Consequences
3.3.7 of TCiR
Consequence on the
of TCiR – Best Practice Procedure
OSOS:
on the
Best Practice Procedure
Initial state
NP111 NP312 NP111 NP312

DB158 DB159 ES01 AS410 DB158 DB159
OS01 OS02
Consequences of TCiR on the OS –

Best Practice Procedure
State after CFC-compilation with activated TCiR
NP111 NP312 NP111 NP312

DB89 DB90 ES01 AS410 DB158 DB159
New IDBs in ES Old IDBs in AS
OS01 OS02
Connection to old Connection to old

IDBs in OS IDBs in OS

Compiling CFC with activated TCiR option results in the creation of new instance data
blocks. As soon such an S7 program is downloaded without compiling the OS, all
regarding block icons and faceplates lose their data connection. The data connection is
only re-established by a compiling the OS.
In contrast, as soon the OS is compiled without a download of the modified S7 program
before, the data connection is also lost until the AS is updated.

Therefore, the following best practice recommendation can be applied only for system
architectures with more than one OS.
AuswirkungThevon TCiR auf die OS –
main principle of the recommendation is, to compile one of the available OS
Best Practice Vorgehensweise
stations before download into the AS, to get a state, where always one OS has access
to a valid data connection.
State after compilation of OS1 in Project ES01 and download in OS01
NP111 NP312 NP111 NP312

DB89 DB90 ES01 AS410 DB158 DB159
New IDBs in ES Old IDBs in AS
OS01 OS02
Connection to new Connection to old

Auswirkung von TCiR auf die OS –
Best Practice Vorgehensweise
State after download in AS410 with activated TCiR
NP111 NP312 NP111 NP312

DB89 DB90 ES01 AS410 DB89 DB90
New IDBs in ES New IDBs in AS
OS01 OS02
Connection to new Connection to old


Consequences of TCiR on the OS –

Best Practice
OnlyProcedure
after compilation of all involved OS stations, the data connection to the new
instance data blocks in the AS is re-established for all OS stations.
State after compilation of OS2 in Project ES01 and download in OS02
NP111 NP312 NP111 NP312

DB89 DB90 ES01 AS410 DB89 DB90
New IDBs in ES New IDBs in AS
OS01 OS02
Connection to new Connection to new

TCiR - summary
3.3.8 Summary TCiR
Update of block libraries in Run Important hints
• Do not change I/O names and additionally • Create a project backup before running TCiR.
change the block interface: Loss of the • Before running the TCiR, determine the free
process value because interpretation as a data blocks, PBC resources and the available
new block I/O! memory area.
• Avoid a name change of the input parameter • As more instances a downloaded in one step,
for the “MsgEvId” message number. as more temporary resources are required.
• Additional associated values on ALARM_8P • As more instances a downloaded in one step,
or NOTIFY_8P are possible indeed, but this as longer the process is paused.
extension only takes effect after a restart of • The TCiR download of a block with changed
the CPU for system-related reasons. default value is possible still from PCS7 V8.2.
• The download of changes using TCiR is • PCS7 V8.1 allows changes of default values
executed without startup sequence (OB 100). only by STOP of the CPU.
License check
Note that at updating, more AS RT POs may be needed temporarily.
This is the case if counting of AS RT PO is carried out in the CPU by the assigned memory.

Update of block libraries in RUN

To allow mode the download of a new version of a block library with changed block
interfaces during running process plant operation, not only the TCiR function has to be
applied, but also the block code must fulfill additional requirements:
 If an I/O name of a block type is changed and an interface is additionally changed, for
example an I/O is added, the name change is not detected as such.
The I/O with a different name is then interpreted as the new I/O and therefore
assigned the default value of the block type. The process value is lost.
 Avoid a name change of the input parameter for the “MsgEvId” message number. If
you make such a change, you lose the “Download in RUN” download capability.
 If you call, for example, an “ALARM_8P” or “NOTIFY_8P” block in a block and want
to use other associated values on it, a type update in RUN is possible, but, for
system reasons, this extension is only effective after a restart of the CPU.
You can easily bypass this behavior by creating all associated values directly when
creating a block.
 If you add parts relevant to initialization to a block, you have to make sure that these
parts are initialized. However, downloading a change using TCiR is performed
without startup (OB 100).
Therefore, the necessary initialization code must not only be implemented in the
startup sequence (OB 100) while evaluating the cold restart bit, but also outside this
sequence in a new sequence that initializes only the newly introduced part.
For this purpose, a new ID must be introduced that is comparable to the “cold restart
bit” and initiates the editing of the initialization sequence during “cold restart” after the
type update in RUN.
Further hints
 Create a project backup before running TCiR. If the resources are exceeded, this
allows you to transfer the backup back to your system.
 Before running the TCiR, determine the free data blocks, PBC resources and the
available memory area.
 TCiR is only supported by the CPU 410-5H with firmware 8.1 or higher.
 Change only as many block types as necessary and as few as possible.
 Always perform the block update from the master data library. The temporary
resource requirements are calculated only here.
 Create your blocks in SCL in line with the recommendations so that they can later be
changed using TCiR. Before activating “Download in RUN”, make sure that your
blocks are TCiR-capable.
 Always check whether the “Download in RUN” option is checked before you run the
“Update block types” function for a CPU 410-5H. Later downloading in RUN is only
possible when the option is checked during the type update.
 The Type Change in RUN for blocks of a PCS 7-library (APL and Basis Library) is
only released, if in the AS the blocks of a library version >= V8.1 are running.
 See [1028] Application note 96839331 "Process automation with the SIMATIC PCS 7
CPU 410-5H controller" - 04_2016, 2.2 and 2.3 for more details.

Task: Type Change in Run
Goal
Update your AS program with new block types without need of CPU stop.
Optional task: Check the behavior of TCiR when modifying a parameter attribute.
Checkpoint
Checkpoint
How would you answer…

 What are the consequences of TCiR,
if the OS was not compiled?
Kurs ST-PCS7ASE 3 - 34 SITRAIN - Siemens AG © 2016

3.4 Multiuser engineering - Configuration in the network
Application
If several project engineers are working from their engineering stations on one project that is
Multiuser engineering
available on a central server or on a PC with a shared drive, they can also work on specific
parts of the project at the same time.
Engineering Server Engineering Engineering Engineering Engineering

Station 1 Station 2 Station 3 Station 4
AS1_proj
OS1_proj AS1_proj AS1_proj AS1_proj OS1_proj OS1_proj
OS1_proj
Several project engineers working on the CFCs Several project engineers working on the following
or SFCs of an AS: objects of an operator station:
• Editing different charts from different chart • Edit various process pictures of an OS.
folders.
• Editing different charts from the same chart • Edit various reports of an OS.
folder.
• Working on the same chart.
• Edit various scripts of an OS.
Parallel working on an AS project via combined network

The parallel working on one project via combined network is limited to defined parts of
the project. Specific improvements were implemented in CFC/SFC incl. failsafe
functions in order to safeguard system integrity and data consistency if several users
access the same data.
Parallel working on an OS project via combined network

As from PCS 7 V8.1, the multiuser engineering function can be enabled in the OS
project. When the function is active, the OS project can be opened multiple times
remotely. A distinction must be made between file and database-based access.
The individual editors or pictures can each be opened for editing by one person only.
Some editors offer a read-only mode if the editor was opened already.

System requirements
3.4.1 Preconditions
Central Engineering Server Distributed Engineering Stations
For performance reasons: For performance reasons:

Use a supported Windows Server operating system PCs with a high clock speed, larger memory and
on the engineering server. faster disk drive (e.g. SSD)
Proper write permissions on the Engineering Server All engineering stations must have the same PCS 7
and especially on the project folder for the project version and the same options as on the Engineering
engineers of the distributed engineering stations Server.
No administrator rights are required for engineering With regard to the HW Config and PDM, the same
activities. field device descriptions must be integrated in all
engineering stations.
It is necessary to have a Sybase server up and Licenses are either installed locally or else one can
running (coordination of data access to STEP 7 use unallocated licenses, which can be accessed via
configuration data in the data base). network. (License type: "floating"). The floating
You can set up the Sybase server as a service to licenses can be stored on the engineering server or
circumvent the constraint of a logged-in user on the on an additional license server.
Engineering Server Locally installed OS RT in order to test OS functions.
Simultaneous use of an editor on several ES: license
is required several times.
For performance reasons:
Reduced transaction file (SQL data base file*.ldf) of
an OS project
Network structure
To load the AS or test OS functions, the relevant engineering stations must be directly
connected to the system bus. (Routing through the Engineering Server is not possible).
There must be a stable network connection between the participating engineering
stations. All stations must see each other in the network neighborhood or in the
SIMATIC shell.
 See [1001] Application description 22258951 MP-MU Engineering - 10_2015 for more
information about Multi-User engineering.
 The central network server is an engineering station. If this engineering station is

used only for project storage and not for configuration work, you do not need a
license key for it.
 ATTENTION!
The potential danger to a smooth workflow is increased by working via the network. If
the network connection fails during a write process, longer waiting times and possible
inconsistencies in the data management can occur.

Multi-User Engineering –
Parallel working in the AS project
3.4.2 Parallel working in the AS project
Editing… Consequence
• … various charts from different chart folders Mutual interference should not be a problem
• … various charts from the same chart folder • Mutual interference cannot be excluded,
depending on the situation, if CFC test mode
ist used (login/logout actions, deleted blocks)
• Access conflicts when activating CFC test
mode at a running CFC compilation.
• … the same chart • Not recommended because mutual
interference.
• If a chart has already been opened by a project
engineer, each additional project engineer will
be informed of this when opening this chart.
To work parallel in the multiuser mode, the multiproduct is opened on several

engineering stations via network access. In this case the engineering server on which
the project is stored can also serve as working computer.
Access scenarios / special characteristics

The following distinctions are made for the editing of CFC/SFC charts:
 Editing charts of various AS
 Editing various charts of same AS
 Editing the same chart of the same AS
No hindrance is to be expected while working in different AS.
The probability of hindrance is also low while working in different charts of the same AS.
However, conflicts cannot be completely ruled out, since all charts access the same
resources such as the symbol table, run sequence, etc.
If, on the other hand, several project engineers are working on the same chart, this can
lead to mutual conflicts. If, for example, two project engineers are working
simultaneously in the same input mask, the action of the engineer who last clicks
"Accept" is the action that will executed.
 ATTENTION!
If several editors are working on the same chart, the view should be updated
frequently (F5). This ensures that the actual current status is displayed.

Working on the same chart of the same AS
In general, this mode of operation should be avoided. Simultaneous access to the same
resources should be confined to short actions, such as assigning parameters of same
connections of a specific block type.
For long read or write actions, the project engineers must coordinate among
themselves.
If a CFC that has already been opened by a user is opened by another user, a message
is displayed.
.
Now the user can decide whether he/she wants to open the chart a second time.
 The other users who have already opened the chart are not provided with a message
that an additional user is accessing the chart.
Typical conflict situations within CFC and SFC are, for example:
 Getting connection
 Assigning parameters to blocks
 Placing blocks
 Defining steps/transitions
 ATTENTION!
In the case of access conflicts outside CFC/SFC, the operations are rejected (no
multiuser-compliant message). Simultaneous working in SIMATIC Manager is not
supported outside PCS 7 ES.

Multi-User Engineering –
Priorities of actions
Conflict handling according to the priorities of the action
Type of action Prio * Examples

Short read actions 3 • Open charts
(with no resource allocation) • Open run sequence
• Open dialog boxes
Short write actions 2 • Instantiation, parameterization, interconnection, etc.
(with no resource allocation) • Close dialog boxes with OK
Long read actions (with 1 • AS-OS data transfer (OS compilation)
resource allocation) • Displaying chart reference data
Long write actions 1 • Optimization of the run sequence
(with resource allocation) • Compiling and downloading (AS and OS)
• Type import and update / cleanup of block types
• Updating shared declarations
• Generating module drivers
• Readback
• Creating block icons
• Creating diagnostic screens
• Updating the PH in a multiproject
• Import / Export functions of the IEA and of the process object
view
• Import / Export functions of the ES objects of Version Cross
Manager
*) 1 = highest priority, 3 = lowest priority
Kurs ST-PCS7ASE If access conflicts arise, the system
3 - 38 always executes the action assigned
SITRAIN to AG
- Siemens the© highest
2016
priority class. In this case, the lower priority action is cancelled.
 Prio 3 (short read actions)
If additional short read actions are executed in parallel, no conflicts should occur.
Short or long write actions executed in parallel may lead to access conflicts, that is,
the short read action is canceled.
 Prio 2 (short read action)
If a short or long write action is executed in parallel, this can lead to an access
conflict for whichever action was started later.
 Prio 1 (long read or write actions)
If an access conflict does not occur immediately when a long read or write action is
triggered, for example, because a read or write action is already being executed in
parallel; this action is executed with no access conflict.
The first action started is executed if users initiate several actions which are assigned
the same priority class.
 See [1001] Application description 22258951 MP-MU Engineering - 10_2015 for more
information about Multi-User engineering.

Distributed
3.4.3 project
Overview organization
about distributed project organization
Organization in the multiproject net
"Save as..."
Organization without multiproject net
"Remove for editing…"

and
"Reapply after editing…"
Course ST-PCS7ASE
The availability of the communication
3 - 39
partners is particularly important for cross-project
actions, such as the setting up of an AS-AS communication or OS compilation.
The following section deals with distributed configuration with and without shared
network.
3.4.4 Organization in the multiproject net
In the case of permanent network availability, project parts can be moved for editing to
the distributed engineering stations and nevertheless remain simultaneously in the
multiproject.
The project engineers can then access all components of the multiproject at any time.
Besides the required network connection, all PCs that manage such components must
of course be switched on and be accordingly released.
In each case the projects are moved or returned via the system function "Save as…"
with the option of replacing the specific project integrated into the multiproject by the
generated copy.
 For performance reasons, we recommend that you use a supported Windows Server
operating system on the engineering server.

Moving and editing a single project in the

Procedure
multiproject network
 Proceed as follows to move a project to another location:
1. Move (select project): File > Save as…
ES server Settings: ES-x
MP P1 • Without reorganization
• Add to multiproject
P2 • Select "Current multiproject" P2
• Replace current project
LIB
• Browse...UNC path
2. Editing
ES server ES-x
MP P1
P2- Link * P2
old
LIB
*) Link visible in the project tooltip or in the MP detailed view as UNC and computer path!
Fetching back projects
Course ST-PCS7ASE
 Proceed as follows to move 3the
- 40
project back to the original location:
1. Close P2
2. Delete P2-old ES server ES-x
(not the link in the multiproject!) MP P1
P2- P2 link P2
3. P2: Save as… old
LIB
Settings:
• Without reorganization
• Add to multiproject
• Select "Current multiproject"
4. Result
• Replace current project
• Browse...UNC path ES server ES-x
MP P1
P2 P2
LIB

Advantages
 An OS server can at any time compile other projects with the data from AS stations.
 All used program parts are contained in the master data library, which can be
accessed via the network.
 An easy archiving of the entire project including all distributed single projects is
possible on the engineering server.
 A largely distributed-station project structure and its distributed organization is the
configuration option that promises the highest performance in cases where there is
permanent network availability.
 A backup copy of the moved project is kept on the station where the project is moved
from.
Points to note
 If, contrary to expectation, a project is not available in the network, this can lead to
long delays and waiting times.
 In executing cross-project functions the project engineers must coordinate with each
other to ensure that work in not being carried out at that time on one of the included
projects. Otherwise conflicts can arise.
 For performance reasons on the system bus, engineering stations should be
connected to the same switch if possible. By doing so, the data traffic between
engineering stations doesn't appear on the backbone (ring) of the system bus and by
consequence doesn't have an influence on the other communication on the system
bus (AS-AS and AS-OS).
3.4.5 Organization without multiproject net
The multiproject functions of SIMATIC PCS 7 are based on the permanent availability of
all included projects. Long waiting periods can occur if one of the included components
cannot be accessed, for example during the opening of the multiproject or while working
with NetPro.
If a permanent network connection is not available the single projects should be
removed from the multiproject net for distributed editing. Reasons for this are, for
example, that not all computers are permanently in the network or that the projects are
purposely edited outside the network (contract award to engineering office /system
integrator, for example).
The removing and reintegration of the single projects is executed via the system
function "Remove for editing…" or "Reapply after editing…"

Procedure
Remove for editing
Proceed as follows to move a project to another location:
Right-click and select the project: Multiproject > Remove for editing
Right-click and select the project: Multiproject > Remove for editing
Target directory
Original path
Reapply after editing

 Proceed as follows to move the project back to the original location:
Right-click
Right-click and select theand the project: Multiproject
selectMultiproject
project: > Reapply after editing
> Reapply after editing
SITRAIN

Course ST-PCS7ASE ATTENTION! 5 - 14 Siemens AG © 2012
Make sure not to move the project to a different location on the distributed
engineering station. The function "Reapply after editing…" expects the project on the
same location as it was stored by the "Remove for editing…" function.

Advantages
 No unexpected delays or waiting periods occur because of missing projects.
 During the distributed editing, the project cannot be accidentally accessed (for
example, by the execution of cross-project functions).
Points to note
 In working with NetPro, already configured connections can generate warning
messages owing to the missing communication peers. For the duration of the project
splitting, new connections can be created only unspecified via references.
 For the compilation of an OS server, all relevant projects (AS projects and
corresponding OS projects) must be brought together centrally again.
 The master data library must be managed as local backup.
 The individual projects must be archived locally.
3.4.6 Dividing the multiproject without network interconnection

With this variant you divide the multiproject including master data library and the project
which is to be engineered. The other projects should be removed from the multiproject.
This is the preferred method for multiproject engineering.
To distribute the multiproject, archive it and shift the created ZIP archive to the
decentralized ES with Windows means. After dearchiving remove the projects which are
not required from the multiproject and delete them.
When you have edited the project on the decentralized ES, remove it from the
multiproject and re-integrate it into the multiproject on the Engineering Server.
Advantages
 The project engineer can access the master data library.
 The import/export assistant (IEA) functions are available.
 During the distributed editing, the project is protected against undesired access on
the Engineering Server (e.g. due to executing interproject functions).

Note
 Changes in the master data library may only be made at the Engineering Server. The
changes must be made to all decentralized Engineering Stations then.
 If all projects which are not required were deleted according to the recommendation,
connections which have already been configured can create warning messages due
to missing communication partners when you work with NetPro. New connections
can only be created as unspecified connections via references for the period of
project division.
 In order to compile an OS server, all relevant projects (AS projects and
corresponding OS projects) must be recombined centrally.
3.4.7 Recommendations
We recommend the following procedure when working with multiprojects:
 One engineer manages the multiproject centrally. This engineer creates the
structures for the projects. This person also distributes the projects for distributed
editing and returns them again to the multiproject (including synchronization of the
cross-project data and execution of cross-project functions).
 The following activities should only be performed on the central engineering station:
 Moving, copying, and deleting the projects of the multiproject
 Moving projects out of the multiproject for distributed editing
 Merging of the projects into the multiproject following distributed editing
 It is not possible to make a general recommendation about how many stations a
project should have. We recommend that projects on a distributed engineering
station have only one 1 AS or 1 OS.
 Only move the PCS 7 objects to a distributed engineering station that is actually
necessary for editing. This means that all other objects of the multiproject are
available for editing on other distributed engineering stations.
 Keep in mind the number of available project editors when distributing the projects.
 ATTENTION!
If there is only one OS in the project, this must always be recompiled on the central
engineering station. This ensures the correct structure of the cross-project
connections to the automation systems.

3.4.8 Tasks and checkpoint
Task: Move a project to another location using "Save as..."
Goal
Move the ASProj08 to another ES for distributed engineering in the multiproject network.
Task: Move a project to another location using "Remove for editing / Reapply after editing"
Goal
Move the ASProj08 to another ES for distributed engineering without the multiproject
network.
Task: Multi-user engineering
Checkpoint
Checkpoint

 What are the differences between
the "Save as..." method and the
"Remove for editing/Reapply after
editing" method for copying partial
projects to another location?
SITRAIN

3.5 Comparing project versions with the Version Cross Manager
Introduction
The Version Cross Manager (VXM) is a separate application you can order as an
option. The Version Cross Manager enables you to quickly and reliably compare the
project data from two PCS 7 projects in order to identify differences. This feature allows
you to recognize if and what has changed.
Requirements
Archived configuration versions must be compared to determine any changes since the
last supply and acceptance, for example, after it was delivered to the customer or after
certification by the Technical Inspectorate or FDA authorities.
This information is important, for example, in the following areas of application:
 A previously accepted project status is to be approved after changes were made and
expansions were added. You therefore need to know the status of changes since the
last acceptance.
 The contractual and accepted project status has been expanded due to subsequent
changes in requirements and the expansions are to be verified.
 In parallel to the commissioning of a project status at a plant, the status was
expanded at an engineering office. The expansions are to be identified in order to
add them to the current project status.
 The documentation of an already completely documented project status is to be
updated. It is to be determined which object documentation requires revision due to
changes.
 The process control project data of a plant should be synchronized with the planning
data of the plant. To do this, export the project data in the manufacturer-independent
XML-format and import it into CAx systems (CAD, CAE, E-CAD or E-CAE).

How to Compare Project Versions

3.5.1 How to Compare Project Versions
Open first Open first XML

object file
Open second Open second

XML file object
The following objects are supported:

 Project
 Library
 HW configuration
 CFC/SFC engineering data, such as
charts, types, chart folders, block folders.
 Shared declarations
 S7 Program
 S7 blocks
 S7 symbols
 Messages
Procedure
1. Select the menu command

Start > SIMATIC > STEP 7 > VXM - Compare Versions
2. The Version Cross Manager is started.
File > Open/Compare....
The "Open/Compare" dialog box opens.
4. For A, select:
 First Object . Make the selection and settings you require in the
"Open" dialog box.
 First XML File . Select the XML file you require in the "Open"
dialog box.
5. For B, select:
 Compare With Object . Make the selection and settings you require
in the "Select Comparison Object" dialog box.
 Compare With XML File . Select the XML file you require in the
"Select Comparison File" dialog box.
6. If you only wish to see specific objects, click the icon and make the required
filter settings.
7. Click the icon to carry out filtering.

8. Click "OK".

The VXM reads the selected objects/files in, including all lower-level objects, and
carries out a comparison at the same time.
The two objects are superimposed in a comparison tree. The deviations are
displayed with color coding.
9. Navigate in the hierarchy or detail window to the objects for which you require
detailed change information.
File > Print
to print out the results of the comparison.
Result of
3.5.2 the comparison
Result of the comparison
SITRAIN
Course ST-PCS7ASE
After the comparison you get an overview of all the changes between Siemens
5 - 25
the twoAGproject
© 2012
versions. The changes are indicated with the symbols which can be found in the next
paragraph. Using the toolbar in the VXM editor you can browse the changes.
 See [103] PCS 7 V8.2 Engineering System - 03_2016, 13 and the Online help for
more information about the Version Cross Manager.

3.5.3 Display of Changed States
Use the menu command

Options > Display...
to access the "Display Settings" dialog box that shows you the display of the change
states.
3.5.4 Other ways of calling VXM
 In the Version Trail application from the "Compare" function.

Call Version Trail with
Start > SIMATIC > STEP 7 > Version Trail
Select two archives and select "Compare" by clicking the right mouse button.
 In CFC/SFC from the "PLC > Download…" function (See next paragraph)
 When updating the block types for the SFC type
Select the chart folder, then
Options > Charts > Update block types…

DisplayDisplay
3.5.5 program changes
program since
changes lastlast
since download
download
The actual program is

compared with the XML file
generated during the last
download and differences are
displayed in VXM
An XML file is generated during each

download of the program

Task: Display changes since the last download
Goal
Before downloading changes to the AS, a programmer must be certain of the changes
he is downloading. Therefore it is possible to compare the actual version of the project
with a previously downloaded version.
Task: Version Cross Manager
Checkpoint
Checkpoint

 Which objects are considered
when comparing two project
versions?
 And when comparing with the
previously downloaded version?

SITRAIN
3.6 Version Trail / Automatic archiving and readback

As of PCS 7 V8.0 you have the option to automatically archive multiprojects, projects,
and libraries at a point of time defined by you, this archiving function includes version
control. You can define for this archiving procedure, whether or not block parameters
shall be read back from automation systems. In addition, block parameters can also be
read back independently from any archival procedure.
In the course of this chapter we will use the collective term "objects" for multiprojects,
projects, and libraries.
Option package "SIMATIC PCS 7 Version Trail" is used for the function. Automatic,
time-controlled execution is triggered by Windows Task Scheduling.
A separate license is required for Version Trail.
Option package "SIMATIC PCS 7 Version Trail"

3.6.1 Option package "SIMATIC PCS 7 Version Trail"
Important features of Version Trail

• Archiving multiprojects, projects and libraries
including versioning
• Retrieving of versioned project data
• Comparison of archived versions Call of VXM
From PCS 7 V8.0:

• Automatic archiving of project data including
versioning
Call of and collaboration with
• Automatic read back of block parameters including Windows Scheduling
versioning
Important Version Trail features

Version Trail provides the following options:
 You can archive multiprojects, projects, and libraries and assign a version ID to the
data (versioning).
Course ST-PCS7ASE  You can also retrieve and re-use
3 - 54 versioned project data. SITRAIN - Siemens AG © 2016
 Version Trail also takes on the complete management of the version history. This
means that, for example, once you completed a version you cannot change it
anymore. Versioning according to validation aspects is automatically performed by
the system in compliance with defined guidelines. For example, the version number
can be increased in increments of 1. Version Trail makes sure that there is only one
valid version with the same designation in the version history.
 You can compare an archived version with an existing project or a second archived
version. For this comparison the Version Cross Manager (VXM) is opened.
Version Trail extended functionality

 Folders and archives are displayed in a tree structure. Folders are used for the
hierarchical structure. Archives can include multiprojects, projects, libraries, and
AS/CPU as sub-elements.

 You can create automatic archiving jobs for projects, multiprojects, and libraries.
Archive operations will then be performed periodically within the defined time
intervals.
 You can create automatic readback jobs for block parameters. The block parameters
will then be read back periodically from the selected AS within the defined time
intervals. A version ID is also provided for readback.
Limitations
Only one instance of Version Trail can be opened.
This means: If you have Version Trail open and an automatic job is started at the same
time, it will not be executed.
3.6.2 Version Trail user interface

Automatic Archiving and you
Version Trail allows Read back
to create and manage several versioned projects. Each
The newly created versioned
versioned project project
is displayed in a separate versioned project window.
A versioned project window has the following layout:
Versioned project
Multiproject archives
Storage location
Project archives
CPU for Read back Comment field
Version table
Hierarchy window (tree structure)
SITRAIN
Hierarchy window (tree structure)

In a tree structure, all relevant objects are represented by icons and displayed in
hierarchical order. The highest level is always the versioned project.
You can create two types of objects in a versioned project: archives and folders.
 Archives (= versioned archives): Include the project data to be archived. Versioned
archives can be created for the following objects:
 Multiprojects
 Projects
 Libraries

When an archive is created in Version Trail the lower-level structure of the object to be
archived is automatically integrated into the tree structure, AS/CPU objects being
displayed graphically, since these objects can have their own readback jobs assigned.
Information about the storage location of the project data to be archived is required to
be able to create a versioned archive. A useful comment may also be added. If you
select the object of an archive in Version Trail, using your mouse, both pieces of
information will be displayed in separate output fields.
In the version table you can view the list with all archived versions of this object.
Further icons indicate whether there is an automatic archiving or readback job for a
selected object:
An existing job is deactivated (but not deleted). It will not be executed.
The existing job is active and will automatically be executed.
 Folders: These are used exclusively for structured layout and storage of versioned
archives. They may contain versioned archives or additional folders.
Version table
 shows all versions of the selected object
 the following actions can be performed from the context menu of a version:
 Delete version: data is deleted from the hard disk and the entry is removed from
the version table
 Retrieve version: the version is unzipped at a desired storage location.
 Compare version with: if you selected a project, you can compare it with a
different project status. VXM will automatically be started for this comparison,
provided that VXM has been installed on your ES. Projects cannot be compared
on multiproject level.
3.6.3 Introduction to automatic jobs for archiving and readback
Since manual archiving and readback, as described above, always needs to be

triggered by a person, it is very time-consuming. To save time, archiving and readback
can also be performed through time-controlled jobs. This ensures that projects and
parameters are always backed up at predefined points of time. If you use this function,
then you should check whether the function was executed correctly.
Interaction of Version Trail with Windows Task Scheduler

The automatic archiving and readback function is managed through a shared interaction
of Version Trail with Windows Task Scheduler:

Automatic Archiving and Read back
Interaction of Version Trail with windows scheduler
SIMATIC Version Trail Windows Task Scheduling
Versioned project
Aufgabenplanungsbibliothek
Versioned object1 für SIMATIC VT
Creation of a job with Job SIMATIC VT1
standard parameters
Adaption/
modification
of parameters
Job SIMATIC VT1
SIMATIC Version Trail
Processing of cyclic jobs by

Versioned project
starting a VT instance
Versioned objekt 1
Version history
V1.0
V1.1 Archives
V1.3
Version Trail performs 2 tasks:

SITRAIN
 Creation or deletion of automatic5 -jobs
Course ST-PCS7ASE 44
with defined standard presets. Siemens AG © 2012
 Execution of a job (archiving or readback) after it was triggered through Windows

Task Scheduling at the scheduled time.
Windows Task Scheduling is used only as a mechanism for managing and to
parameterize automatic jobs on the operation system level.
One of the advantages of Windows Task Scheduling is the fact that applications can be
started even with active user control on operation system level, without the need to
additionally acknowledge their execution.
Limitations
Only one instance of Version Trail can be opened. If an automatic job (archiving or
readback) is started and Version Trail is already open, the job will not be executed.
 The Task Scheduler of earlier Windows versions was completely revised by Microsoft
as of Windows Vista.
The following sections describe the procedure of creating automatic jobs for PCS 7
V8 and Windows 7. If you use PCS 7 V8 with a different operating system the dialog
may be different from the one described in this document.

3.7 License management

Lizenzen
3.7.1 und Mengengerüste
License types in PCS 7
CoL License Key
Nachweis der Lizenz. „Elektronischer Lizenzstempel“

• Papier oder Download • Ablage und Handhabung auf der PC
• Zur Archivierung Station
• Transfer per USB Stick oder Netzwerk
Lizenz-Grundtyp Lizenz-Typ
• Single license • Unlimited license

• Floating license • Count relevant license
• Countable object license
• Upgrade license
• Rental license
• Pay per use license
• Contact license
• Trial license
• Demo license
Handling licenses with the Automation

License SITRAIN - Siemens AG © 2016
Manager
3.7.2 Handling licenses with the Automation License Manager
SITRAIN
Possible license key storage locations

 License key USB stick

 License key diskettes

 Local storage media
 Storage media on connected computers
 Removable disks (for example USB stick, but not CDs or DVDs)
Options for transferring license keys

The Automation License Manager gives you the following options for transferring
license keys between the various possible storage locations:
 Drag-and-drop
 Cut and paste
 Offline transfer
Procedure - Drag-and-drop
1. Select the appropriate view using the menu command View > Manage.
2. On your own or the connected computer, open the storage location where you wish
to insert the license keys.
3. On your own or the connected computer, open the storage location from where you
wish to remove the license keys.
4. Select the license keys, hold down the left mouse button and drag the license keys
to the folder where you wish to insert them. The license keys are transferred.
Procedure - Cut and paste

1. Select the appropriate view using the menu command View > Manage.
2. On your own or the connected computer, open the storage location from where you
wish to cut the license keys.
3. Select the menu command Edit > Cut.
4. On your own or the connected computer, open the storage location where you wish
to paste the license keys.
5. Select the menu command Edit > Paste.
The license keys are transferred.
Procedure – Offline transfer

The Automation License Manager online help describes how to perform an offline
license key transfer.
 ATTENTION!
As part of the license key safety system, when license keys are transferred, clusters
identified as "defective" are created on the target drive. You must not reconstruct
these clusters, as this will destroy the license keys.

Remotely
3.7.3 using using
Remotely License KeysKeys
License on aonlicense server
a license server
Settings on the license server
SITRAIN
Procedure
1. The Automation License Manager must be installed on the local computer and on
the server.
2. Then in the Automation License Manager on the local computer you must connect
the server via the menu command Edit > Connect Computer.
3. Now you can use the licenses located on the server. If the connection to the server
is interrupted, you can continue to work for another 3 hours before the infobox
comes about the missing license. The licenses remain on the server.
4. In order to be able to transfer the license keys from the server to the local PC you
must clear the setting "Protect local license keys" on the server. You get to
the settings via the menu command
File > Customize....
Without the license you get the message "Zugriff verweigert / Access denied".
WARNING:
If this setting is disabled, anyone connected to the server can download the license
keys from the server!
3.7.4 Checking License Keys
Procedure for Checking License Keys:

1. Select the view using the View > Management menu command.
2. In the object area, select the storage locations (My Computer, network computer)
where the license key should be checked.
3. Select the license key to be checked.

Checking License Keys

4. Select the License Key > Check menu command.
Meaning for
License keys
Meaning for
installed software
SITRAIN
Course ST-PCS7ASE
In the figure above you can find5 -the
86
meaning of the icons used for displaying the status
Siemens AG © 2012
of the license keys
Recovering
3.7.5 License
Recovering KeysKeys
License
Phone Fax E-mail

E urope / Africa +49 180 5050 222 +49 180 5050 223 support.automation@ siemens.com
America Toll free +1 423 262-2200 techsupport.sea@ siemens.c om
+1 800-333-7421
Outside US A
+1 423-262-2522
Asia / Australia +86 10 64 757575 +86 10 64 747474 support.asia.automation@ siemens.com
SITRAIN
Course ST-PCS7ASE
It might be possible to repair a 5defective
- 87
license key or defective authorization. Use the
Siemens AG © 2012
menu command "License Key > Recover" in the ALM (Automation License Manager) to
recover defective license keys and authorizations respectively. It is only possible to use
this function in agreement with Customer Support. Normally you do not need this
function.

You will be in contact over the phone with the licensing hotline during the entire
recovery procedure.
Please have the following information at hand when you call Customer Support:
For a defective license / authorization:
1. Order number (see Certificate of License or Data Medium Designation)
2. Licensing: name of the license key
3. Request code: the code that must be given to the licensing hotline
The hotline then gives you an activation code:
 Enter this activation code and acknowledge with OK to execute the "Recover"
function or
 Click on Cancel if the license key is not to be recovered.
 To save you and and our hotline unnecessary waiting times you can download the
Repair Request Form, fill it in and send it to your hotline. This form can be
downloaded on the Customer Support Site, entry ID 772175.

3.7.6 Calculating the process objects for the SIMATIC station ("AS RT PO")
and for the OS
The required license key for all SIMATIC stations depends on the total number of
process objects loaded and configured in a project (multiproject).
When an AS is loaded, the loaded process objects are evaluated. The following
procedure shows you how to calculate the number of process objects configured in a
project or multiproject.
The number of process objects loaded into the AS is calculated by the executing
application and is subtracted from the available process objects of the license. The
value for the number of available process objects is always updated by the executing
application. The license key "AS RT PO" of the type "Countable Objects" is used.
Licensing of process objects as of V7.0:

AS process objects (license: "AS RT PO")
The following objects each take 1 "AS RT PO" license:
 Block instances that can be monitored/controlled, support messaging and are not
driver blocks
 SFC charts
 SFC type instances
OS process objects (license: "WinCC RT PO" [OS], "WinCC RC PO" [ES])
The following objects each take 1 "WinCC RT PO/WinCC RC PO" license:
 1st Count
 Blocks that can be operated/monitored, support messaging and are not driver
blocks
 SFC charts
 SFC type instances
 25 process tags (rounded up) created in the OS, but not through AS-OS
compilation
 2nd Count (only applicable if this exceeds the number of POs in the 1st count)
 PCS 7 V7.0: 50 tags created in the OS with process interface (rounded up)
 PCS 7 V7.1: 60 tags created in the OS with process interface (rounded up)
 Process objects are taken into account in the first counting.

In the second count, the tags are taken into account, whereby the existing PO license
is multiplied by 50 or 60 (e.g. 1,000 POs = 60,000 tags).
The number of POs in the second count is not displayed in WinCC. However, when
the OS project is opened, an entry is made in the log file "License_Info.log" with the
number of tags used.
 More info in the FAQ: http://support.automation.siemens.com/WW/view/en/38855207

You can start a function in the SIMATIC Manager that identifies all of the process
objects configured and booked in the Automation License Manager (ALM). The result is
Calculatingdisplayed
the process objects
in the "PCS 7 licensefor the SIMATIC
information" dialog box. This allows you to check
whether the existing "SIMATIC PCS 7 AS RT PO" license or the license you intend to
station ("ASorder
RTisPO") and for the OS
adequate for your project and the number of process objects you can still add to
your project.
SITRAIN

Course ST-PCS7ASE
The POs of the 2nd count are 5only
- 88
visible in the Information dialog ofSiemens AG © 2012
the SIMATIC
Manager. In this way, it might happen that the limit of configurable process objects
has already been reached even though according to the WinCC Explorer display, not
all the POs are taken.
Booking
3.7.7 back Process
Booking Objects
back Process Objects
Booking back is required in

the following cases:
 Ceasing to use a CPU
 Deleting projects
 Deleting charts folders
Use the menu command Options > Charts > Book Back Process Objects to book
process objects back into the Automation License Manager in cases where these relate
to a program that is no longer going to run in the CPU.
The program is thereby deleted from the CPU.

SITRAIN
 Downloading in S7-PLCSIM and test CPUs:

No process object count is performed in this case.
 ATTENTION !
It is particularly important to book back licenses if plant engineering is being
performed at different locations, but the process object licenses are required for the
target plant.
Defective CPU:
A new CPU used to replace a defective CPU will be recognized as the previous
download destination, provided that the data stored in the process object info
corresponds to the serial number of the CPU or the memory card. It will be assumed
that the "correct" CPU is connected for older CPU versions that do not allow a serial
number query.
3.8 Current License

Aktuelles modelmit
Lizenzmodell with CPU410-5H
der CPU 410-5H–
Überblick PA Controller CPU 410 V8.1
3.8.1 Overview PA Controller CPU 410 V8.1
Ab FW Stand V8.1
• 2. Ethernet/PROFINET Interface nun verfügbar!
• Online Erweiterung der Kapazität in 100 PO Schritten
• Type Change in RUN
• Freigegeben bis 70 °C (nur mit V8.1 Version!)
Austauschbare
System Expansion Card
Die innovative CPU 410-5H Process Automation des AS 410 beherrscht mit ihrer
leistungsstarken Hardware und optimierter
Kurs ST-PCS7ASE 3 - 43 Firmware das SITRAIN
gesamte Leistungsspektrum
der konventionellen Automatisierungssysteme AS 412 bis AS 417.
Ihre Automatisierungsleistung lässt sich dabei über die Anzahl der SIMATIC PCS 7
Prozessobjekte (PO) sehr flexibel skalieren. Dazu dienen System Expansion Cards für
100, 500, 1000, 1600 oder mehr als 2000 Prozessobjekte (PO).

Online
3.8.2Upgrade der Prozessobjekte
System einerSystem
Expansion Card and CPU 410-5H
Expansion Packages
Austausch der Karte, Stop der CPU Online Upgrade, kein Stop der CPU
100
1600 2k+ 1000 PO
PO PO PO
500
PO
100 500 1000 System Expansion Packs

PO PO PO
CPU 410-5H +
Bei der CPU 410-5H wird das Volumen der ladbaren Prozessobjekte in der System
Expansion
Intern / © Siemens AG 2014. Alle Rechte Card
hinterlegt. Ist das maximal ladbare Volumen erreicht, so können keine
vorbehalten.
Seite 2 13.06.2014 weiteren Prozessobjekte in diese AS geladen werden. I IA AS S SUP PA
Um dem Kunden einen günstigen Einstiegspreis anzubieten kann das Volumen der
Aktuelles Lizenzmodell mit von
System Expansion Card der100 CPU
PO bis 2600 PO –
410-5H skaliert werden.
Überblick Der Kunde hat immer die gleiche leistungsstarke CPU410-5H und kann diese
entsprechend seinen Bedürfnissen erweitern. Dazu kauft er lediglich zusätzliche
Expansion Packs.
6 x CPU416-5H 6 x CPU416-5H
5 x CPU414-3 5 x CPU414-3
S7-400 CPU
3 x CPU416-2 3 x CPU416-2
3 x CPU417-4 3 x CPU417-4
Wechsel der CPU?
Angebots- Vertrags- Detail- Engineering

abschluss
Beschaffung IBS …
erstellung planung Installation
CPU410
~ 12000 PO 27 x PO100 Upgrade
One Controller Konzept
17 x CPU410 17 x CPU410 + PO500

Kurs ST-PCS7V81 4-3 SITRAIN - Siemens AG © 2014
Die System Expansion Card (SEC) wird auf einen Steckplatz auf der Rückseite der
CPU 410-5H gesteckt. Wenn eine defekte CPU ausgetauscht werden muss, dann kann
die noch intakte SEC beibehalten und auf die neue CPU gesteckt werden.

Somit benötigen Sie als Ersatzteil lediglich eine CPU 410-5H mit einem geringen PO
Volumen. Ab PCS 7 Version V8.1 kann das Volumen der SEC feingranular in Stufen
von 100 PO bis zur maximalen Anzahl von 2600 PO erhöht werden. Das Upgrade der
SEC wird mittels Automation License Manager (ALM) durchgeführt.
Für die System Expansion Card wird dabei ein Hardware-Ausgabestand ab V2 benötigt.
Es wird mindestens eine ES mit PCS 7 V8.1 Installation, das Projekt mit der
Hardwarekonfiguration der CPU 410-5H FW 8.1 und eine online Verbindung zur CPU
vorausgesetzt.
Beim Erwerb der CPU410-5H ist die CPU in der Erstausstattung mit folgendem
Volumen auf der System Expansion Card erhältlich:
 100 PO
 500 PO
 1000 PO
 1600 PO
 2600 PO
 Das Maximale PO Volumen einer SEC Karte beträgt 2600 PO

Ab 2600 POs ist die CPU als "unlimited" gekennzeichnet.
Es können auch mehr als 2600 POs geladen werden.
Die Begrenzungen sind dann Arbeitsspeicher, PBK, Anzahl DBs, FCs, etc….
Die System Expansion Card ist nur im Bundle mit einer CPU 410-5H erhältlich.
CPU 410 Expansion Package

Für das Online-Upgrade der Prozessobjekte für eine CPU 410-5H benötigen Sie
mindestens ein CPU 410 Expansion Pack. Dieses Expansion Pack können Sie über
zwei Wege bestellen:
 über Ihren Siemens Ansprechpartner
 online über www.siemens.com/industrymall
Die CPU Expansion Packs sind in folgenden Größen erhältlich:

 100 PO
 500 PO
Sie können beliebig bis zur maximalen Größe kombiniert werden. Dabei ist lediglich zu
beachten, dass Sie bei einem Redundanten System (2 CPU) jede Größe mind. 2-mal
benötigen, abhängig von dem Volumen, um welches Sie erweitern wollen.
Das Volumen eines CPU Expansion Pack ist immer in vollem Umfang einer AS
zuzuweisen. Eine Aufteilung auf mehrere Automatisierungssysteme ist nicht möglich.
Beispiele Volumenerweiterung um 300 PO

 Um bei einer singulären AS die Anzahl der PO um 300 zu erhöhen, benötigen Sie 3
CPU 410 Expansion Packs mit je 100 PO.
 Um bei einer Redundanten AS (2 CPU) die Anzahl der PO um 300 zu erhöhen,
benötigen Sie 6 CPU 410 Expansion Packs mit je 100 PO. Dies ist erforderlich, da ja
beide AS Systeme um 300 PO zu erweitern sind.

CPU 410 Expansion Pack Repair-Funktion

Im Falle eines fehlerhaften Upgrade-Vorgangs darf es nicht zu der Situation kommen,
dass vom Anwender gekaufte System Expansion Packs mit den darauf befindlichen
License Keys wertlos werden. Zu diesem Zweck ist ein besonderes System Expansion
Pack mit einer "Repair"-Lizenz (0 Prozessobjekte) verfügbar.
Wie kann das aktuelle PO Volume geprüft werden?

 Mit PCS 7 V8.0:
 über die PCS 7 Lizenzinformation
 visuell über die Beschriftung auf der SEC
 Ab PCS 7 V8.1:
 über die PCS 7 Lizenzinformation
 visuell über die Beschriftung auf der SEC
 Automation License Manager
 Hardware Konfig Online

Arbeitsschritte beim Online Upgrade des PO-
Volumens
3.8.3 Steps for online upgrade of PO volume in brief
Beschaffung der CPU 410 Über den Siemens-Ansprechpartner oder über

1.
Expansion Packs www.siemens.com/industrymall
2. Vorbereitung
Die ES muss über ein PCS 7-Projekt online auf
ALM mit dem Zielsystem verbinden die hochzurüstende CPU 410 zugreifen können.
(CPU 410, die hochzurüsten ist)
Die License Keys der CPU 410 Expansion Packs
müssen für den ALM auf der ES verfügbar sein.
3. License Keys rangieren Zielsystem License Keys der CPU 410

CPU 410-5H Expansion Packs
Online
Volumens Per Drag & Drop werden die License Keys auf das Zielsystem gezogen.
4. PO-Activation File erzeugen Zielsystem

CPU 410-5H
Online Menübefehl Zielsystem > Upgrade
Das Upgrade wird für die gewählten Komponenten bestätigt (System Expansion Card und CPU Expansion Packs).
PO-Activation File License Keys
Die License Keys der System Expansion Packs werden gelöscht.

Im Benutzerprofil des aktuellen Benutzers der ES wird ein PO-Activation File erzeugt und im ALM angezeigt.
5. PO-Activation File senden Sie übertragen PO-Activation Files per Service Request an Siemens.
PO-Activation File
Eigene Dokumente > Siemens > http://www.siemens.com/automation/support-
Arbeitsschritte
Automation > beim
PCS7 >Online Upgrade des PO-
Activations request
Volumens
Kurs ST-PCS7V81 In einer4Antwortmail

-5 erhalten Sie innerhalb von 48 Stunden
SITRAIN einAG © 2014
- Siemens
6. PO-Release File empfangen PO-Release File pro gesendetem PO-Activation File.
PO-Release File
Eigene Dokumente > Siemens >
support.automation@siemens.com
Automation > PCS7 > Activations
Sie übertragen das PO-Release File in das Verzeichnis im Benutzerprofil des aktuellen Benutzers der ES.
Upgrade mit PO-Release File Per Drag & Drop ziehen Sie
7. Zielsystem das PO-Release File auf das
ALM mit dem Zielsystem verbinden CPU 410-5H Zielsystem.
(CPU 410, die hochzurüsten ist) Das Upgrade wird ausgeführt.
Online Die Dauer ist abhängig von
der Belastung des AS.
Die beiden Dateien im Verzeichnis

Ergebnis: PO-Activation File PO-Release File der ES werden gelöscht.
8.
Der ALM zeigt die aktualisierte System Expansion Card mit der neuen Anzahl der Prozessobjekte an.

Online Upgrade des PO-Volumens –
PO Activation File erstellen
3.8.4 Creating the PO Activation file
1. Der Automation License Manager hat Zugriff auf eine Partition, auf welcher sich die
License Keys der CPU 410 Expansion Packs befinden.
Nach jedem Öffnen des ALM
2. Wählen Siemuss der Vorgang des Zielsysteme verbinden erneut durchgeführt werden.
den Menübefehl
Bearbeiten > Zielsystem verbinden > AS 410verbinden…
Im Dialogfeld "AS 410 verbinden" werden in der Liste die Automatisierungssysteme
PO Activationangezeigt,
File erstellen
die mit dem Automation License Manager verbunden sind, bzw. wieder
verbunden werden können.
3. Wenn
Der ALM benötigt Sie ein
ein PCS weiteresinAutomatisierungssystem
7 Projekt, verbinden
welchem die hochzurüstende CPUwollen, klicken Sie
eingebunden ist. auf
die Schaltfläche "Hinzufügen".
Kurs ST-PCS7V81  Wählen Sie über den Dialog4 "PCS
-8 7-Projekt öffnen" das SITRAIN - Siemens AG © 2014
Automatisierungssystem aus, für das Sie das PO-Upgrade durchführen wollen.
 Beenden Sie anschließen diesen Dialog mit der Schaltfläche "OK".
 Dieser Vorgang setzt voraus, dass die hochzurüstende CPU 410-5H in einem PCS 7-
Projekt eingebunden ist.


Online Upgrade
ACHTUNG !
Benutzendes Experten-Modus nur –
PO-Volumens
Sie den im Notfall und mit Unterstützung der Lizenz-
Hotline.
4. Ziehen Sie per Drag & Drop die License Keys der CPU 410 Expansion Packs auf
das Automatisierungssystem, für das Sie das PO-Upgrade durchführen wollen.
 Wenn Sie zunächst das falsche Automatisierungssystem gewählt haben, können Sie
in dieser Phase die License Keys der CPU 410 Expansion Packs noch beliebig
verschieben.
5. Im nächsten Schritt ordnen Sie die neuen License Keys der System Expansion
Card zu.
 Öffnen Sie in der Baumansicht des Automatisierungssystems den Ordner
"Online".
 Markieren Sie eine Lizenz und wählen Sie "License Key > Upgrade".
Result
Nachdem Sie den Upgrade-Vorgang angestoßen haben, sind die License Keys der
betreffenden CPU 410 Expansion Packs fest dieser SEC zugeordnet. Eine
Verschiebung auf ein anderes AS mit einer anderen SEC ist nun nicht mehr möglich.

Diese Lizenz ist aktuell an

einem Upgradevorgang beteiligt
…vom angemeldeten
Benutzer!
Angelegtes PO-Activation File:

Der Name enthält Informationen über das
Projekt, die CPU und den Zeitstempel
Kurs ST-PCS7V81
 Es wurde ein PO-Activation 4File
- 10
angelegt im Ordner: SITRAIN - Siemens AG © 2014
Eigene Dokument > Siemens > Automation > PCS7 > Activations
 Die License Keys der ausgewählten CPU 410 Expansion Packs werden gelöscht und
stattdessen ein Stellvertreter-Key für das Activation File angezeigt. Im ALM wird z.B.
angezeigt, dass dieses Activation File eine Volumenerweiterung von 600 auf 700 PO
beinhaltet.
 ACHTUNG !
Nachdem Sie ein PO-Activation File für ein AS erstellt haben, erstellen Sie bitte kein
weiteres File, solange die Release-Informationen nicht in das AS übertragen wurden.
Ansonsten verlieren Sie die zugewiesenen CPU 410 Expansion Packs und das
erzeugte PO-Activation File.
Nach dem Erstellen des PO-Activation Files sollten Sie keine größeren
Projektaktivitäten anstoßen, bevor Sie den Vorgang nicht (wie nachfolgend
beschrieben) abgeschlossen haben.
Diese Projektaktivitäten sind z.B. Umbenennung des Projektes oder Umbenennung
des AS, Rückspielen des archivierten Projekts, da das erstellte PO-Activation File
eine Namensinformation des Projekts enthält.

3.8.5 Sending the PO-Activation

PO-Activation-File file to Siemens
über Support Request an Siemens
sendenStarten Sie einen Support Request über die folgende Internetseite:
http://www.siemens.com/automation/support-request
1. Produkt wählen
 Tragen Sie "CPU 410" im Eingabefeld "Produkt/Bestellnummer" ein und klicken

PO-Activation-File über Support
Sie auf die Schaltfläche „Suchen“. Request an Siemens
senden  Aktivieren Sie das Optionsfeld "SIMATIC PCS 7 > CPU 410".
 Aktivieren Sie das Optionskästchen "Problem mit der Autorisierung/Lizenz" und
klicken Sie auf die Schaltfläche „Weiter“.
Kurs ST-PCS7V81 4 - 14 SITRAIN - Siemens AG © 2014
6. Anwendungsfall wählen
 Tragen Sie im Eingabefeld "Upgrade CPU 410" ein und klicken Sie auf die
Schaltfläche "Weiter".
7. Unsere Lösungen
 Klicken Sie auf die Schaltfläche "Weiter".

Kurs ST-PCS7V81
Course folder, V8.2.0, ST-PCS7ASE 4 - 15 SITRAIN - Siemens AG © 20
3 - 65
PO-Activation-File über Support Request an Siemens
senden
8. Problem beschreiben
Mehrere PO-Activation-Files
sind möglich.
 Nehmen Sie die Eintragungen in den Pflichtfeldern vor.

 Tragen Sie im Eingabefeld "Details" den Text "Request PO-Activation-File" ein.
 Fügen Sie das PO-Activation-File über die Schaltfläche "Datei auswählen" ein.
 Klicken Sie auf die Schaltfläche „Weiter“.
Kurs ST-PCS7V81 4 - 16 SITRAIN - Siemens AG ©

9. Kontaktdaten angeben:
 Geben Sie Ihre Kontaktdaten an und klicken Sie auf die Schaltfläche "Weiter".
10. Zusammenfassung & Absenden
 Überprüfen Sie Ihre Angaben und klicken Sie auf die Schaltfläche "Absenden".
Result
In einer E-Mail erhalten Sie innerhalb von 48 Stunden ein PO-Release-File pro
gesendetes PO-Activation-File.

3.8.6 Transferring the PO-Release file and activating the volume

Arbeitsschritte beim
1. Übertragen Online
Sie die erhaltenenUpgrade des
PO-Release-Files PO-
in das folgende Upgrade-
Verzeichnis der Engineering Station:
Volumens
Eigene Dokumente > Siemens > Automation > PCS7 > Activations
2. Öffnen Sie den Automation License Manager und verbinden Sie ihn wieder mit dem
Zielsystem.
PO-Release-Files in dasselbe Upgrade-Verzeichnis ablegen, indem schon das
1
PO-Activation
Bearbeiten > liegt.
File Zielsystem verbinden > AS 410 verbinden...
 Wählen Sie über "Hinzufügen" das entsprechende AS aus oder klicken Sie auf
2 ALM mit dem
"OK" Zielsystem
wenn wieder
sich Ihr AS schon verbinden.
in der Liste der bereits ausgewählten
Automatisierungssysteme befindet.
3. PO-Release File auf die SEC übertragen

 Ziehen Sie per Drag & Drop das PO-Release-File (Stellvertreter-Key) auf den
Online Ordner des AS Systems.
Das Upgrade der SEC wird nun ausgeführt. Die Dauer ist abhängig von der
Belastung des Automatisierungssystems.

Volumens
Result
Anzeige des neuen PO-Volumens

der System Expansion Card im ALM

in der PCS 7 Lizenzinformation
des SIMATIC Managers
Kurs ST-PCS7V81
Der Automation License Manager
4 - 12
zeigt für die aktualisierte System Expansion Card die
neue PO-Anzahl an.
Nach einem erfolgten Upgrade werden die angewendeten Dateien im Upgrade-
Ergebnis: Verzeichnis
Online gelöscht
Upgrade des PO-Volumens
(PO-Release-File und PO-Activation-File).
Des Weiteren können Sie das Volumen der SEC sowie die lizenzpflichtigen
Prozessobjekte auch im Simatic Manager abrufen unter:
Extras > PCS 7 Lizenzinformationen
Weiterhin werden diese auch in HW-Config im Baugruppenzustand der CPU angezeigt.

im Baugruppenzustand

3.8.7 Use cases for Upgrade of PO volume on redundant AS
Standardfall: Redundantes AS und gleiches PO Volumen auf den beteiligten CPU410-5H

Für das Upgrade eines Redundanten Systems (AS410H) müssen sich die beiden
beteiligten CPU 410-5H im gleichen Betriebszustand befinden und die gleiche Anzahl
Volumenerhöhung
POs besitzen.der System Expansion Cards in
einem redundanten System
Der Upgrade-Vorgang ist identisch zum Single System. Dabei ist lediglich zu beachten,
dass Sie bei einem Redundanten System jede Größe des CPU 410 Expansion Packs
mind. 2-mal benötigen. Die Menge ist abhängig von dem Volumen um welches Sie
Redundantes AS und gleiches PO Volumen auf den beteiligten CPU410-5H
erweitern wollen.
License Keys für

redundantem AS, getrennt
durch Semikolon
1 gemeinsames Objekt für
beide CPU in einem
redundantem AS
Regel: Den gleichen Typ der CPU Expansion Packs in einer geradzahligen Anzahl auf das red. AS ziehen.
Beispiel:
• 2 x 100 entspricht Volumenerhöhung um 100 PO oder
• 2 x 100 und 2 x 500 entspricht Volumenerhöhung um 600 PO
Im ALM erkennen Sie die redundanten Systeme an der Darstellung der Symbole.
Das redundante System wird in der Baumansicht des ALM als ein Objekt dargestellt.
Die Anzahl der Lizenzen sowie auch die Lizenznummern der SEC Karten sind bei
einem redundanten System je System einmal vorhanden. Daher sind in obiger
Abbildung unter der Lizenznummer zwei Nummern durch Semikolon getrennt
dargestellt. Es wird nur ein Activation- bzw. Release-File erzeugt, das beide CPU/ SEC
Informationen enthält.
Austauschfall: Redundantes AS und defekte CPU

Für einen redundanten Betrieb eines AS 410H muss sich in beiden beteiligten CPU 410
das gleiche Volumen von PO auf den SEC Karten befinden.
Fällt eine CPU durch Defekt aus, kann diese CPU ausgetauscht und die SEC
umgesteckt werden. Das PO-Volumen bleibt in diesem Fall unverändert.
Austauschfall: Redundantes AS und defekte SEC

Fällt eine CPU incl. der SEC aus (beispielsweise durch einen Wasserschaden), dann
kann die Ersatz-CPU unter Umständen eine SEC mit einem anderen PO-Volumen
enthalten, als es der Redundanzpartner aufweist.
 Eine SEC kann nur im Bundle mit einer CPU 410-5H bestellt werden.

Damit das System in den redundanten Betrieb wechseln kann, muss die PO-Anzahl
vereinheitlicht werden, d.h. auf den größeren Wert:
2. Ermitteln Sie die Differenz der PO auf den beiden SEC Karten.
3. Ziehen Sie per Drag & Drop die entsprechende Anzahl von License Keys der CPU
Expansion Packs auf das Automatisierungssystem.
4. Öffnen Sie in der Baumansicht des Automatisierungssystems den Ordner "Online"
und markieren Sie die Lizenz.
5. Wählen Sie "License Key > Upgrade".
6. Senden Sie das PO-Activation File per E-Mail an Siemens.
7. Spielen Sie nach erhalt das PO-Release File entsprechend der Vorgehensweise bei
einem singulären System das PO-Volumen auf die SEC Karte.
Die Vorgehensweise beim Update eines redundanten Systems unterscheidet sich nicht
von der Vorgehensweise eines singulären Systems.
Beim Vereinheitlichen unterschiedlicher Volumen auf den SEC-Karten in einem
redundanten System weist das Programm automatisch der SEC mit dem geringeren
Volumen die Volumenerhöhung zu.
Online-Überprüfung der SEC Karte
3.8.8 Online-check of the System Expansion Card
Die SEC Karte, sowie z.B. das gleiche Volumen beider SEC Karten bei einem
redundanten System, können Sie mittels ALM überprüfen.
Dazu selektieren Sie für das entsprechende AS "Online" und dann im Feld "License
Keys" – Online den entsprechenden Eintrag.
Sollte ein Defekt vorliegen, so wird neben dem OK Button der Button "Details"
eingeblendet. In den Details erhalten Sie dann den genauen Hinweis für den Defekt
(z.B. Keine online Verbindung von der4ES
Kurs ST-PCS7V81 - 18 zur SEC Karte). SITRAIN - Siemens AG © 2014

3.8.9Zusammenfassende Hinweise
PO-Upgrade - Summary
Wenn für eine CPU ein PO-Activation File erzeugt und Wenn für eine CPU ein PO-Activation File erzeugt und
an die Hotline versandt wurde, dann kein weiteres an die Hotline versandt wurde, dann keine
Update an derselben CPU durchführen, bevor der Namensänderungen an dieser CPU und am Projekt
erste Vorgang nicht abgeschlossen wurde. durchführen, bevor der erste Vorgang nicht
abgeschlossen wurde.
Vor größeren Funktionserweiterung im

Anwenderprogramm auf Notwendigkeit
einer Volumenerhöhung prüfen.
Experten-Modus nur im
Notfall und mit
Unterstützung der Hotline
Reparatur versehentlich überschriebener

PO-Activation-Files oder deaktivierter
CPU 410 Expansion Packs über die
Hotline möglich.
Kurs ST-PCS7V81
 Nachdem Sie ein PO-Activation4 File
- 19
für ein AS erstellt haben, erstellen Sie bitte kein
weiteres File, solange die Release-Informationen nicht in das AS übertragen wurden.
Ansonsten verlieren Sie die zugewiesenen CPU 410 Expansion Packs und das
erzeugte PO-Activation File. Des Weiteren wird das zugehörige Release File
unbrauchbar.
 Zwischen dem Erstellen des PO-Activation Files und dem Einspielen des PO-
Release Files sollten Sie keine größeren Projektaktivitäten anstoßen. Dies sind z.B.
Umbenennung des Projektes oder Umbenennung des AS, Rückspielen des
archivierten Projekts, da evtl. die Namen unterschiedlich sind.
 Benutzen Sie den Experten-Modus nur im Notfall und mit Unterstützung der Hotline.
 Prüfen Sie vor einer größeren Funktionserweiterung, ob das Volumen der SEC
ausreichend ist. So können Sie rechtzeitig die Prozedur zur Volumenerhöhung
angehen.
 Versehentlich überschriebene PO-Activation-Files oder deaktivierte CPU 410
Expansion Packs können über die Lizenz-Hotline wieder aktiviert werden.
Checkpoint
3.8.10 Checkpoint
Wie würden Sie antworten…

 Wo können Sie ein CPU 410 System
Expansion Pack bekommen?
 Welche Voraussetzungen müssen
erfüllt sein, um einen Service Request
für eine Volumenerhöhung Ihrer
System Expansion Card stellen zu
können?

3.8.11 Changes in the License information
Grundlagen zur Zählung und Buchung der PO-Lizenzen

Beim Laden ermittelt der Lader die im Programm vorhandenen Prozessobjekte (PO)
sowie die Seriennummer der CPU und der Memory Card. Mithilfe dieser Nummern wird
die Zuordnung eines Programms zur CPU hergestellt. In der ES-Datenhaltung wird für
jede einmal geladene CPU eine PO-Info angelegt, welche die Identifikatoren und die
Anzahl verbrauchter PO-Lizenzen aufnimmt.
Beim Ladevorgang wird festgestellt, ob und wie viele PO-Lizenzen für die aktuelle CPU
bereits verbraucht wurden. Aus der in der ES-Datenhaltung abgelegten PO-Info wird die
beim letzten Laden ermittelte Anzahl von POs gelesen. Die Differenz zu der jetzt
ermittelten Anzahl wird dann mit den verfügbaren Lizenzen im Automation License
Manager (ALM) verglichen. Werden die benötigten POs durch die Lizenz noch
abgedeckt, wird die Differenz im ALM verbucht und das Laden ausgeführt.
Wenn das aktuelle Programm weniger POs enthält, als das zuvor geladene, wird durch
den Ladevorgang die Anzahl verfügbarer PO-Lizenzen wieder erhöht. Sind nicht mehr
genügend Lizenzen vorhanden, wird wegen der Lizenzverletzung ein entsprechender
Hinweis aufgeblendet, den Sie quittieren müssen. Jetzt können Sie das Laden
abbrechen oder trotzdem laden. Die Anzahl der benötigten aber nicht verfügbaren
Lizenzen wird als Fehlbestand gespeichert. Wenn Sie weitere Lizenzen erworben
haben, wird beim nächsten Laden dieser Fehlbestand bei der Ermittlung der benötigten
Lizenzen mit einbezogen und im ALM entsprechend abgebucht.
Lizenzierung der PO bei der CPU 410-5H PA

Bei der CPU 410-5H PA gelten für die Lizenzierung der PO folgende Eigenschaften
zusätzlich:
 Bei der CPU 410-5H PA wird die Anzahl der PO durch die Hardware lizenziert. Dabei
ist es nicht möglich, eine größere Anzahl an PO in das AS zu laden, als die per
Hardware lizenzierte Anzahl.
 Bei der CPU 410-5H PA wird die Anzahl der Prozessobjekte (PO), die im Automation
License Manager unter der Lizenz "AS RT PO" verbucht sind, verglichen mit der
Anzahl der PO, die in der CPU geladen sind.
 Bein AS Download wird die CPU Kennung und die SEC Kennung auf die ES
gespeichert. Somit kann die CPU oder die SEC ohne Abbuchung von AS RT PO
getauscht werden.
Im SIMATIC Manager können Sie eine Funktion aufrufen, die alle projektierten und PCS
7-lizenzpflichtigen Objekte ermittelt. Damit können Sie überprüfen, ob die erworbenen
oder zu bestellenden PCS 7-Lizenzen für Ihr Projekt ausreichend sind bzw., um wie
viele lizenzpflichtige Objekte sich Ihr Projekt noch erweitern lässt.
8. Selektieren Sie das Multiprojekt oder das Projekt.
4. Wählen Sie im Kontext-Menü den Menübefehl PCS 7 Lizenzinformation…
Alternativ können Sie auch unter dem Menüpunkt "Extras" den Befehl "PCS 7
Lizenzinformation..." auswählen.
Das Dialogfeld "PCS 7 Lizenzinformationen" wird geöffnet.
Im linken Feld werden alle installierten lizenzpflichtigen PCS 7-Komponenten und im
rechten Feld die jeweils dazugehörigen projektierten lizenzpflichtigen Objekte
angezeigt.

In der "PCS 7 Lizenzinformation" werden die vorhandenen, verbuchten und

Auswirkungen der Lizenzinformationen
projektierten AS RT PO Lizenzen angezeigt. Des Weiteren erhalten Sie die Information,
welche PO-Volumen in den CPU 410-5H zur Verfügung stehen.
Alle installierten und lizenzpflichtigen Dazugehörige projektierte und lizenzpflichtige
PCS 7-Komponenten Objekte
PO-Volumen der SEC

projektiert / verbucht stammt aus
Datenhaltung im ES
Anzahl an PO, die in die
CPU des AS geladen sind
Anzahl der projektierten AS RT PO im MP = 1002 400 in AS07 und

602 in AS05 (CPU410-5H)
Anzahl der verbuchten AS RT PO im MP = 1000 398 in AS07 und
602 in AS05 (CPU410-5H)
Auswirkungen derAbbildung
In obiger Lizenzinformationen
ist zu erkennen, dass die Anzahl der vorhandenen AS RT PO
Lizenzen kleiner ist, als die Anzahl der im gesamten Multiprojekt projektierten PO.
Laden ist trotz

Warnung möglich.
• Meldung im OS (damit archiviert)

• Eintrag im Diagnosepuffer des AS
• LED INTF (Sichtbarkeit vor Ort)
Kein CPU Stop!
Kurs ST-PCS7V81
Die nicht ausreichende Lizenzierung
4 - 20
wird angezeigt durch: SITRAIN - Siemens AG © 2014
 Einen Eintrag in den Diagnosepuffer der CPU

 Ansteuern der LED INTF der CPU 410-5H
 Zyklisches Auslösen einer entsprechenden Meldung in SIMATIC WinCC.

Die Meldung wird immer sofort ausgelöst beim Ladevorgang, bei dem die nicht
ausreichende Lizenzierung festgestellt wird, und wenn sich die Differenz durch den
Weitere Ladevorgang ändert.
Besonderheiten Danach
beim erfolgt die Meldung
Übersetzen undimLaden
Abstand von ca. 6 Stunden.
einer CPU 410-5H

Wenn die Prozessobjekte wieder ausreichend lizenziert sind, z. B. durch Nachkauf von
Lizenzen, dann erfolgt diese Meldung nicht mehr. Es wird keine Meldung "GEHEND"
erzeugt.
3.8.12 Further facts for compiling and downloading into CPU 410-5H
Projekttyp "PCS 7-Projekt" ist erforderlich
Laden nur mit CFC möglich
Überwachungsbaustein für Lizenzinformationen
 Projekttyp "PCS 7-Projekt" ist erforderlich

Beim Laden in die CPU 410-5H PA wird geprüft, ob das Projekt den Projekttyp "PCS
7-Projekt" besitzt. Nur wenn das Projekt diesen Projekttyp besitzt, ist ein Laden
möglich!
 Laden nur mit CFC möglich.
Die CPU 410-5H PA kann nur mit CFC V8.0 SP3 (oder höher) geladen werden. Ein
Laden aus anderen STEP7-Editoren ist nicht möglich.
Kurs ST-PCS7V81  Überwachungsbaustein für Lizenzinformationen
4 - 25 SITRAIN - Siemens AG © 2014
Beim Übersetzen wird automatisch ein CFC-Plan "@PA-CPU" erstellt, der eine
Instanz des Bausteins "PA_CPU" enthält. Dieser CFC-Plan wird auch in den OB1
eingebaut.
Der Baustein "PA_CPU" ist in der CPU 410-5H PA erforderlich und dient zur
Lizenzüberwachung. Er ist als FB16 in der CFC-Library im Verzeichnis "ELEM_400"
verfügbar.
Beim Laden in die CPU 410-5 PA wird automatisch der CFC-Plan "@PA-CPU" mit
dem Baustein "PA_CPU" geladen.

Task: Download to a new CPU
Goal
During the development, programmers often use a test CPU in their office. While
programming, the charts are downloaded into this test CPU and by consequence,
process objects are booked and your license will be decremented. After the
development phase, commissioning will start and you will have to download the
program into the customer's AS. In order to avoid booking the PO's twice, the PO's have
Task: to bemanagement
License booked back before starting the commissioning on the new CPU.
Checkpoint
Checkpoint

 Do you have to book back process
objects when downloading to
PLCSIM for test purposes?
SITRAIN

Content 4
4 AS system specification and hardware configuration ......................................... 3
4.1 Learning target ....................................................................................................................... 3
4.2 Memory concept of the S7-400 CPU's .................................................................................. 3
4.2.1 Overview ................................................................................................................................ 3
4.2.2 Load memory ......................................................................................................................... 4
4.2.3 Work memory (Main memory): .............................................................................................. 5
4.2.4 System memory: .................................................................................................................... 6
4.2.5 Online view for memory allocation ......................................................................................... 7
4.3 Important CPU settings .......................................................................................................... 8
4.3.1 Why using process image partitions (PIP) ............................................................................. 8
4.3.2 Cyclic interrupt OB's <> PIP <> I/O module .......................................................................... 9
4.3.3 Startup behavior .................................................................................................................. 10
4.3.4 Cycle settings....................................................................................................................... 11
4.3.5 Local data settings ............................................................................................................... 12
4.3.6 Default Parameters of the CPUs ......................................................................................... 13
4.3.7 PA Controller CPU 410-5H .................................................................................................. 13
4.4 Behavior when maximum cycle time exceeded ................................................................... 15
4.4.1 @CPU_RT chart – CPU_RT block type .............................................................................. 15
4.4.2 CPU_RT: Functions ............................................................................................................. 16
4.4.3 Result in the OS: AS block icon / Faceplate ........................................................................ 17
4.4.4 CPU overload scenarios ...................................................................................................... 20
4.5 Updating the HW Catalog .................................................................................................... 24
4.5.1 Installation of HSP and HUP................................................................................................ 24
4.5.2 Deploying new hardware as replacement ........................................................................... 24
4.5.3 Integrating third-party DP, PA and HART devices with GSD files ....................................... 25
4.5.4 Integrating third-party DP, PA and HART devices with EDD files ....................................... 26
4.6 Time synchronization ........................................................................................................... 27
4.6.1 Time synchronization in a workgroup .................................................................................. 28
4.6.2 Time synchronization in a domain with one hierarchy ......................................................... 29
4.6.3 Time synchronization in a domain with multiple hierarchies ............................................... 30
4.6.4 Selecting the time master .................................................................................................... 31
4.6.5 Additional settings for the CPU ............................................................................................ 33
4.6.6 Time synchronization in SIMATIC mode: Integrated interface of the CPU 410H ................ 34
4.6.7 Time synchronization in NTP mode (For CPU 41x-3IE) ...................................................... 35
4.7 Redundant (Fault tolerant) Automation Systems................................................................. 37
4.7.1 Redundancy Concept of PCS 7 ........................................................................................... 37
4.7.2 Fault-tolerant solutions for the AS ....................................................................................... 38
4.7.3 Fault-tolerant solutions for the IO ........................................................................................ 39
4.7.4 Fault-tolerant solutions for the IO – CFC libraries ............................................................... 40
4.7.5 Y Link: Gateway between redundant and non-redundant PROFIBUS DP ......................... 41
4.7.6 Connection of PROFIBUS PA to a redundant PROFIBUS DP ........................................... 42
4.7.7 Redundant PROFIBUS PA .................................................................................................. 43
4.7.8 Fault-tolerant solutions for the plant bus ............................................................................. 44
SIMATIC PCS 7 – AS system specification and hardware configuration

4.7.9 Network components for a fault tolerant/redundant plant bus ............................................. 45

4.8 PROFIBUS and PROFINET in SIMATIC PCS 7 by comparison ......................................... 46
4.8.1 SIMATIC PCS 7 System architecture .................................................................................. 46
4.8.2 Requirements to PROFINET IO at the PA .......................................................................... 46
4.8.3 PROFIBUS vs. PROFINET .................................................................................................. 47
4.8.4 Redundancy methods in Profinet for PCS 7 ........................................................................ 49
4.8.5 Comparison of topologies .................................................................................................... 52
4.9 Checkpoint ........................................................................................................................... 53

4 AS system specification and hardware configuration

Learning
4.1 target target
Learning

 Memory concept of the S7-400 CPU
 Important CPU settings
 The behavior of a PCS 7 AS program
when maximum cycle time exceeded
 Redundant automation systems
 Architecture and mechanisms of
PROFINET IO in PCS 7 environment
 Possible time synchronization
mechanisms in a PCS 7 plant
 Configure the AS hardware in

accordance with PCS7 requirements
4.2 Memory concept of the S7-400 CPU's

Memory
Course
4.2.1 concept of the S7-400 CPU's
ST-PCS7ASE
Overview 4-2 - Overview SITRAIN - Siemens AG © 2016
SITRAIN
Course ST-PCS7ASE 4-3 Siemens AG © 2012

4.2.2 Load memory
The load memory can be divided into the external and the internal load memories.
Internal load memory

The internal load memory is a RAM memory which is integrated into the CPU. Blocks
can be transferred from the programming device (PG) to the load memory in the CPU
with "PLC/Load". The main memory is updated here at the same time, whereby the
runtime-relevant code and data blocks are transferred to the main memory.
External load memory

The load memory can be extended via a RAM memory card or a flash memory card.
The memory card then acts as the external load memory.
There are two types of memory extension cards with different behavior available:
 RAM memory cards
If a RAM memory card is inserted, the program can be transferred to the CPU via
PLC > Load
The main memory is also updated here at the same time, whereby the runtime
relevant code and data blocks are transferred to the main memory.
The internal RAM load memory is filled first. The other blocks are only written to the
RAM memory card when it is full.
 Flash memory cards
If you have a flash memory card plugged in, transfer blocks to the external load
memory with
PLC > Download user program to memory card
However, in that case, the CPU has to be set to STOP mode first before the user
Memory program
concept of can
thebeS7-400
transferred.
CPUs–
Selection of suitable Memory
All the program Card
blocks and data blocks can be loaded into the load memory via the
programming device (PG).
Choosing the right memory card type
The user program is buffered on the User programs can be set to RUN despite…
Memory Card despite… • Program size is larger than the internal RAM
• loss of power supply
• missing buffer batteries
Use Flash Memory Card Use RAM Memory Card
The program size is restricted by available The user program is not buffered on the
internal load memory. Memory Card in case of…
The user program cannot be set to RUN, if the • loss of power supply
load memory is too small. • missing buffer batteries

The following points determine the decision on which memory card to use:
 Do you wish to retain the user program on the memory card when the power is OFF
and without a back-up battery? If so, this would necessitate the use of a flash
memory card.
 ATTENTION!
If you use a flash memory card without back-up batteries, the blocks in the RAM part
of the load memory and the data (main memory and system memory) will be lost
when the power is OFF.
 Do you wish to be able to change the user program in RUN mode, and is the
program too big for the internal RAM? If so, this would necessitate the use of a RAM
memory card. When using a RAM memory card, the system must be battery-
operated so as to back up the RAM memory card data and the data in the internal
RAM if there is a power failure.
Expanding the load memory with a memory card

If you have a memory card inserted, the operating system asks for an overall reset
(STOP LED flashes slowly at 0.5 Hz).
You can initiate the reset procedure as follows:
 Move the switch to MRES position and then back to STOP again.
The STOP LED then flashes for at least 3 seconds at a rate of 2 Hz (overall reset is
performed) and, after that, lights up permanently.
If you have a flash memory card inserted, following the overall reset the CPU copies
the user program and the saved system parameters from the flash memory card to
the main memory.
Important:
 The memory card must remain inserted while the program is being processed.
 If you insert or remove the memory card while the power is ON, the CPU asks for an
overall reset whereby the STOP LED flashes slowly at 0.5 Hz.
 If you insert or remove the memory card while the power is OFF, the CPU performs
an overall reset automatically after being switched back on.
4.2.3 Work memory (Main memory):
The main memory is divided into two parts.

One of the parts is used for the runtime-relevant code. This part is also used for the
process input image (PII), the process output image (POI) and the diagnostics buffer.
The other part of the main memory is used for the runtime-relevant data and also
contains the data from the local data stack. The main memory is a battery-backed RAM.
Reorganization of main memory

You change the division of the main memory by means of parameter assignment in
HW Config > Object properties >...
The portion of the main memory which can be used for code or data blocks is changed
when the system data is loaded whenever you change the following parameters in:

 Size of the process image (in bytes; in the "Cycle/Clock marker" tab)
 Communication resources (in the "Memory" tab)
 Size of the diagnostics buffer (in the "Diagnostics/Clock" tab)
 Quantity of local data for all priority classes ("Memory" tab)
The main memory is reorganized when the system data is loaded into the CPU. As a
result, data blocks which have been generated by SFC are deleted, and the other data
blocks are preset with initial values from the load memory.
Parameters for portioning of main memory

If you change the system data, you need to allow for the following storage requirements
during parameter assignment:
Parameter Main memory required In the code/data

memory
Size of the process image 12 bytes per byte in the process Code memory
(inputs) input image
Size of the process image 12 bytes per byte in the process Code memory
(outputs) output image
Communication resources 72 bytes per communication job Code memory

(communication jobs)
Size of the diagnostics buffer 32 bytes per entry in the Code memory
diagnostics buffer
Quantity of local data 1 byte per byte of local data in Data memory
the data memory
4.2.4 System memory:
The system memory (RAM) contains the memory elements which any CPU makes
available to the CPU, such as
 markers (M),
 times (T) and
 counters (Z).
Moreover, the system memory also contains the block stack and the interrupt stack.
There is also temporary memory capacity in the CPU's system memory reserved for the
local data stack, for the diagnostics buffer and for communication resources. This data
in the system memory's temporary memory only remains valid while the block is active.
Once the block has been closed, the data is no longer retained in the main memory
(temporary local data).
 Program processing takes place exclusively in the area of the main memory and
system memory.

4.2.5 Online view for memory allocation
Wählen Sie in SIMATIC Manager die gewünschte CPU oder führen Sie den Mauszeiger
nach unten und klicken Sie mit der rechten Maustaste auf
Online view on the memory usage
Zielsystem > Baugruppenzustand > Speicher
Click here to get

more details
about the selected
memory area

Wählen Sie auf der Registerkarte "Speicher" des Dialogfeldes "Baumgruppen-
Zustand" den Speicherbereich aus, über den Sie weitere Einzelheiten erfahren
möchten, und klicken Sie dann auf die Schaltfläche "Details Speicherbereich".

4.3 Important CPU settings

4.3.1 Why using process image partitions (PIP)
Using process image partitions

Either a process image update can be performed in OB 1 (default) for the process
image memory or the process image partition can be updated for each cyclic interrupt
OB.
 As a rule, we recommend the use of process image partitions for PCS 7.
Important CPU settings

Otherwise what is known as a "non-equidistant dynamic response" will occur;
Why using process
particularlyimage partitions
for closed-loop (PIP)
controls, as a result of the free cycle of OB 1. The figure
below is designed to illustrate this:
SITRAIN

Cyclic interrupt
4.3.2 OB's <>
Cyclic interrupt PIP
OB's <><>
PIPI/O
<> module
I/O module
Assign a process image

partition to every cyclic
interrupt OB (OB 30 to
OB 38) containing a
user program.
Assign the module

addresses to a process
image partition and
thereby to the desired
cyclic interrupt OB
Configuration is performed in two steps

1. CPU properties:
Assign one of up to 15 free process image partitions to a cyclic interrupt OB
(e.g. OB 35 – 100 ms).
2. Module properties:
Assign the module addresses to a process image partition and thereby to the
desired cyclic interrupt OB.
The process image partition is automatically updated by the cyclic interrupt OB to which
it was assigned. In rare cases, this can also be caused by system calls configured by
the user.
This ensures that the inputs really are read at the start of a cyclic interrupt OB (for
example, a controller is processed) and also that the outputs are written in accordance
with the cycle (input – process – output: IPO).
 For more details see

[121] PCS 7 Compendium Part A - Configuration Guidelines - 12_2014, 3.1.3 and
[103] PCS 7 V8.2 Engineering System - 03_2016, 9.9.4.8

Startup Startup
4.3.3 behaviour
behavior
Recommended setting!
Reason: in case of a warm restart, the
current process parameters are not
reset to their initial values.
Course ST-PCS7ASE
Make sure to keep the default setting
5 - 19
for "Warm restart." In thisSITRAIN
case,- Siemens
the current
AG © 2014
process parameters are not reset to their initial values.
Another factor, that plays a role in terms of startup characteristics, is the fact that a
PCS 7 AS is always equipped with a backup battery and a RAM memory card.
 See [103] PCS 7 V8.2 Engineering System - 03_2016, 9.9.4.7 for more details

Cycle settings
4.3.4 Cycle settings
Default setting
Should not be changed
Size should be bigger

than the highest I/O
address used in the
configuration
Settings can not be

changed for the CPU 410
Default setting
Should not be changed
Scan cycle monitoring time

The scan cycle monitoring time should not be changed from the default value of '6000
ms' for PCS 7 projects to ensure the effectiveness of CPU performance monitoring and
the emergency stop (shutdown prevention).
Size of the process image of the inputs/outputs

The size of the process image of the inputs/outputs depends on the I/O addresses of all
DP slaves.
You can see an overview of the I/O address space currently in use under the HW Config
menu command "View > Address Overview…” The highest address for inputs or outputs
listed there (without diagnostic addresses) must be within the configured size of the
process image.
All channel driver blocks (e.g. CH_DI) are configured to a symbolic address from the
process image in PCS 7 and do not access the I/O directly.

Consider also the memory concept as described in 4.2.1

4.3.5 Local data settings
Local data is derived from the declaration section of the logic blocks and centrally stored
in the local data storage area. This means that the local data requirement increases
each time instances of FBs or FCs are added to the charts.
On the "Memory" tab, you can define the local data size in the work memory for each
individual OB. This value must always be beyond the particular local data requirement.
Local data settings
Each cyclic interrupt OB is assigned a local data size by means of its priority. OB 32, for
example, has the priority 9 and OB 35 the priority 12.
Amount of local Amount of local Amount of local

data per priority data per priority data per priority
class required class configured class available
by the in HW Config in the AS
CFC/SFC
program
Configuring the local data requirement

It is advisable to set the local data size to 1,024 for the cyclic interrupt OBs used in your
project. It is also important to set the priorities 24 to 28 to a value of 1,024. These
contain OB 100 and the asynchronous error OBs.
If, for example, no blocks are integrated in OB 37 and OB 38, the local data requirement
can be reduced to 256 and the memory that is freed up can be used for other priority
classes.

Consider also the memory concept as described in 4.2.1
Checking the local data requirement

If the local data requirement exceeds the configured amount, the next time charts are
compiled you will see a warning prompting you to increase the local data memory
space.
Use the CFC editor to compare the local data requirement and amount in the CPU. Use
the menu command "Options > Chart > Reference Data" to open the editor in
which the "Local Data" can be viewed. An OB configured too low is shown in red there.

4.3.6 Default Parameters of the CPUs
The following table shows the default parameters regarding the performance of the
CPUs for PCS 7 projects. These values are set as defaults for the configuration of a
CPU with PCS 7 software.
They suffice for typical applications but can be changed within limits as required for
configuration.
Standard AS
4.3.7 PA Controller CPU 410-5H
The CPU 410-5H Process Automation is a controller of the latest generation. This
controller is specifically designed for the SIMATIC PCS 7 control system. As with
previous controllers of the SIMATIC PCS 7 system, the CPU 410-5H Process
Automation can be used in all Process Automation industries. The very flexible
scalability based on PCS 7 process objects makes it possible to cover the entire
performance range from the smallest to the largest controller, in standard, fault-tolerant
and fail-safe applications with only one hardware.
The CPU 410-5H can be used with PCS 7 V8.1 or higher.
To use a CPU410-5H you must create a new configuration. The parameters of a CPU
410-5H are set to PCS 7 default values when a new configuration is created. Some
parameters that were previously freely assignable cannot be changed in the CPU 410-
5H. You can transfer charts from existing PCS 7 projects.

AS410H
 See [103] PCS 7 V8.2 Engineering System - 03_2016, 4.7.4 for Default performance
parameters of the CPUs for PCS 7 projects.
See [513] PCS 7 CPU 410-5H Process Automation - System Manual - 09_2014, for
more information about CPU 410-5H.
Task: Hardware settings
Goal
PCS7 requires some specific hardware settings. In this exercise you will check and if
Task: Important CPU
necessary settings
modify these settings.
Checkpoint
Checkpoint

 Why is it recommended to use
Process Image Partitions in PCS 7?

4.4 Behavior when maximum cycle time exceeded

CPU overload
@CPU_RT
4.4.1 chart –chart
@CPU_RT CPU_RT block
– CPU_RT typetype
block
Generated automatically during

the generation of the module
drivers; contains an instance of
the CPU_RT block type
Course ST-PCS7ASE
The function block CPU_RT automatically
4 - 13
carries out all necessary steps in order to
reduce the cycle over load of a PCS 7 controller.
When compiling the CFC with "Generate Module Drivers", a chart called "@CPU_RT"
will automatically be inserted. This chart already contains the CPU_RT block. The block
is included in all necessary cycles e.g. OB100, OB1, OB3x and OB8x.
New Controller cycle overload behavior

In case of cycle overload of the controller, automatic load shedding prevents the
controller from stopping. The load shedding is carried out by the CPU_RT block and is
achieved by phase offset of run time groups. This condition is called net operation and
the cause needs to be resolved as quickly as possible.
If the cycle time has been exceeded twice or the cycle checkpoint has not been reached
for 12 s, this will lead to emergency operation. The control system message
"Emergency operation, reducing ration of cyclic OBs" is displayed.
During emergency operation all blocks are processed or skipped with the reduction X.
This ensures that all blocks sooner or later are still processed.
The following two escalation levels are available:
 Level 1: The overall cycle time is exceeded twice (approximately 12 sec.). All
released OB3x get the reduction factor 1.
 Level 2: If a time error still occurs, all OB3x are reduced systematically.
The emergency operation is not a permanent condition for the controller overload. The
emergency operation is only used to temporarily handle overload situations.
It is necessary to react on the emergency operation as quickly as possible, e.g.
programming change, undo previous changes or create new program structure.
Therefore the emergency operation will be displayed in Asset Management as a
Maintenance Alarm.

4.4.2 CPU_RT: Functions
The function of the "CPU_RT" block to determine the performance data requires a CPU
firmware version supporting the system function SFC 78. For single CPUs this is
currently firmware V5.0. For H-CPUs (Fault-tolerant Systems) a firmware version
including SFC 78 is in preparation.
 The "CPU_RT" block will be automatically included from the module driver wizard
regardless of the used CPU and CPU FW. With PCS 7 V7.0, and in connection with
the new library, all controllers will get the new cycle overload behavior.
By updating an existing PCS 7 project without using the new functions the CPU_RT
block will not be included by the driver wizard.
For the complete new functionality including cycle over load behavior and cycle
performance analysis, the SFC 78 and the option Asset Management are required.
Depending on the CPU/FW used and whether or not Asset Management is
implemented, the functions of CPU_RT will be displayed and parameterized as follows:
* No operator message "Net time consumption of all OBs exceeds max. limit", as
performance data are not calculated.

4.4.3 Result in the OS: AS block icon / Faceplate
If the option Asset Management is available, then the display of the cycle performance
data is provided on the OS/MS.
With a mouse click on the Asset block symbol (Controller) the faceplate will show the
overall controller load.
CPU overload
Result in the OS: AS block icon / Faceplate – Performance
Performance view
Diagnostics > AS Objects Performance

view
Block icon
for AS
Limit value for the overall

load of the CPU (Can be set
in the "Parameter" view
Net and gross average load of Load of the error

the cyclic interrupt OB's OB's and OB1
 Net runtime
Course ST-PCS7ASE
Net runtime is the runtime required
4 - 15
for the computation of the code placed in OB3x if
it would not be interrupted by higher-priority OBs.
 Gross runtime
Gross runtime is the runtime required for the computation of the code placed in OB3x
if it is interrupted by higher-priority OBs.
 Overall load bar
The vertical bar of the overall utilization in % (overall cycle time of CPU) is the sum of
all net runtimes (cycle times) of all OB3x, OB8x and the OB1
An additional Asset Faceplate is available for the detailed analysis for all different OB
levels.
 The total cycle load of a controller should be not more than 70-75% after
commissioning.
Under the assumption that 20% of the cycle time is used for communication and
acyclic events leaves this a spare time of 5-10 % available for further program
expansions and additional communication jobs
 See [240] PCS 7 Maintenance Station - Function Manual - 03_2016, 6.11.3.10 and
following for the description of AS faceplate views.

CPU overload
Faceplate – OB3x: Runtime of the cyclic interrupt OB's
View OB3x: Runtime of the cyclic interrupt OB's
OB3x view
Reset display of
measurements
Gross runtime of the OB

(interruption of OB's with
higher priority inclusive)
Net runtime of the OB

(without interruption of
OB's with higher priority)
The "OB3x" view offers you the net as well as the gross runtime (in ms) of the individual
CPU overload Faceplate
cyclic – OB8x OB1: Runtime of the error
interrupt OB's.
OB's and OB1
View OB8x OB1: Runtime of the error OB's and OB1
OB8x view
The "OB8x OB1" view offers you the net runtime (in ms) of the individual error OB's and
OB1.

CPU overload Faceplate – Parameter view: DeterminesSIMATIC
the PCS 7 AS Engineering
behavior of the CPU_RT block
Parameter view: Determines the behavior of the CPU_RT block
Parameter
view
If the option Asset Management is used, the parameterization of the overload behavior
will be carried out in the Asset CPU faceplate.
If the option Asset Management is not available, the parameterizations need to be done
Course ST-PCS7ASE directly on the CPU_RT function block. The function block is included
4 - 18 on theAG
SITRAIN - Siemens @CPU_RT
© 2016
chart. The necessary function block parameters are explained below.
The "@CPU_RT" is a system chart. Please do not delete this systems chart!
Reduction factor (maximum number of retrigger attempts):

 Maximum number of all retrigger attempts or MAX_RTRG (CPU_RT)=0:
Controller overload behavior prior to PCS 7 V7.0.
 MAX_RTRG=1:
Only the first level of the new controller overload behavior is used. If the level 1 load
reduction is unsuccessful, the controller will be stopped after exceeding the maximum
cycle time three times (> 18 sec.). The emergency operation level 2 will not be
carried out.
 MAX_RTRG=2:
After exceeding the maximum cycle time three times (18 sec.) the emergency
operation level 2 will automatically be carried out. All OBs are now delayed with an
offset of 1. If this is still unsuccessful, the controller will be stopped after exceeding
the cycle time four times (> 24 sec.).
 MAX_RTRG=x:
An x+2 times exceeding of the cycle time is possible. With each cycle overload the
offset factor is increased.

4.4.4 CPU overload scenarios

CPU overload
Scenario 1: High Controller Cycle Load (Maintenance
demanded)
Scenario 1: High Controller Cycle Load (Maintenance demanded)
SITRAIN
Course ST-PCS7ASE
If the overall utilization, the sum7 -of
50
the average values of all net runtimes (in % of OB3x,
Siemens AG © 2012
OB8x + OB1), exceeds the “Overall Utilization Alarm Limit”, the message “Net Time
Consumption of All OBs Exceeds Max. Limit” will be shown. The maintenance status
MS is set to “Maintenance demand”.
This message is a preventive maintenance message and allows the user to adapt the
CPU program to avoid a CPU overload.
 CPUs without SFC 78 support will not signal the excess of the net time consumption.

Scenario 2: OB Request Error (Maintenance required) – Faceplates

If the overall utilization reaches the 100 % limit, OB request errors may occur, i.e., cyclic
OBs will sporadically not be calculated for one cycle because they are interrupted by
acyclic OBs. The request error is identified in the form of a start event loss of the
particular cyclic OB.
CPU overloadIf the configurable number "Message since request error" of OB 3x events is exceeded,
Scenario 2: OB Request
or the Error
OB 1 event (Maintenance
is detected although required) – was processed (cycle checkpoint
no OB 1 event
Faceplates not reached anymore), the message "OB 3x request error" (x = 0...8) will be displayed.
The maintenance status MS is set to “Maintenance required”.
CPU overload
Scenario 2: OB Request Error (Maintenance required) –
Alarms
SITRAIN
If an OB 1 is subsequently executed again (cycle checkpoint reached), the Maintenance
State will be reset and this control system message will be marked as "going out".
In this case the button will appear in the overview area. Clicking this button will open
SITRAIN
Course ST-PCS7ASE
the "Highest priority alarms" 7window
- 52
in which the cycle time monitoring alarms will be
Siemens AG © 2012
shown.

CPU overload
Scenario 3: Maximum Cycle Time Exceeded behavior
(Maintenance alarm)
Scenario 3: Maximum Cycle Time Exceeded behavior (Maintenance alarm)
text text text

text
SITRAIN
Course ST-PCS7ASE
When the configured scan cycle monitoring time (HW Config -> CPU Siemens
7 - 53
Properties) is
AG © 2012
exceeded (PCS 7 default: 6000ms), the message "Cycle time exceeded: 6001ms,
OB1" is output and the maintenance state of the CPU is changed to "Bad or
maintenance alarm“. The following events can lead to a cycle overload:
 too high communication load
 frequent alarm events
 frequent acyclic fault events (flutter alarms)
 incorrect setting of time interrupts when making additions to the program
 See [622] PCS7_V70_in-practice_CPU_RT_en.pdf for more details

Task: CPU overload
Goal
When generating the module drivers for the very first time during compilation of the
PCS7 program, all error OB's are automatically generated. This causes that the CPU
never goes into STOP mode … unless by a time error due to a CPU overload
(exceeded cycle time of OB1 or OB3x). This exercise shows you the behavior of a
Task: CPU PCS7 program during such a cycle overload.
overload
Checkpoint
Checkpoint

 Which means exist in PCS7 to
prevent the CPU from switching to
STOP mode?
SITRAIN

Upgrade of Hardware catalog

Installation of HSP and HUP
4.5 Updating the HW Catalog
4.5.1 Installation of HSP and HUP
HSP: Hardware Support Package HUP: Hardware Upgrade Package

Software package installed in HW Config; Software package in the form of an installation
facilitates the configuration of new hardware. file, which contains one or more HSPs and the
meta information required to automatically
generate and connect the corresponding PCS 7-
specific module drivers in the S7 program by
means of a wizard.
From PCS 7 V7.1
Monitoring on the system side

The definition specifies that individual HSPs cannot be used with PCS 7 but can only be
used for HUPs approved for PCS 7.
If an HSP is used without accompanying meta information, the module drivers cannot
Course ST-PCS7ASEbe generated as indicated by the4 -message
26 "Module is not supported
SITRAIN by the module
driver". As a result, no diagnostics or status messages of the hardware can be
processed.
 These module drivers and their proper integration into the S7 program form the basis
of hardware component diagnostics and status information.
 New HSPs are released together with new STEP 7 versions. Never install a STEP 7
version which is more recent than the one officially released for the PCS 7 version to
use these HSPs.
 See [124] PCS 7 Compendium Part D - Operation and Maintenance - 01_2015, 3.1
about integration of new hardware using HUP/HSP.
4.5.2 Deploying new hardware as replacement
If no successor module has yet been listed in the manual titled "PCS 7 – Released
Modules", and no related information appears in the PCS 7 Readme (online), the
successor module can be used in spare part-compatible operation. The replacement
scenario is described in the corresponding delivery release.
Spare part-compatible operation

The following always applies when replacing hardware: The old hardware component
has been configured and the new hardware component which is compatible as a
replacement is then deployed.
When a new hardware component is deployed as a replacement, it will not be possible
to use its advanced functions.

4.5.3 Integrating third-party DP, PA and HART devices with GSD files
Field devices made by any manufacturer can be integrated via the standard GSD file
(standard slaves). This type of integration is used for PROFIBUS DP, PROFIBUS PA,
and HART devices.
The configuration is set by means of HW Config. The default parameter assignment for
the device is also defined via the GSD file. Parameter adjustments must then be made
using a proprietary tool; alternatively, in the case of devices integrated via EDD
(Electronic Device Description) files, the adaptations can be made using SIMATIC PDM.
Data can only be exchanged between the master and a field device if the master is
aware of the device-specific parameters and data formats. The field device
manufacturer supplies this "knowledge" in the form of a GSD file.
GSD files contain information about:
 Device manufacturer and identification number
 Transmission rate and bus parameters
 Volume and format of data for cyclic communication
Integrating Inthird-party DP,
HW Config, you can PA and
define whatHART
revision devices
level of the GSD file is installed by right-
with GSD files
clicking on the device to open its object properties, once you have successfully
positioned it on the PROFIBUS.
SITRAIN
Procedure
1. Open the HW Config Tool and close all opened configuration
2. Select Options -> Install GSD file…
3. In the window that pops up, click ‘Browse’ to browse to the GSD-file to be imported
 If a new device for which parameters are to be assigned using SIMATIC PDM is
integrated, the GSD and EDD files of the device must be imported using the PDM
application "Manage Device Catalog...”
4.5.4 Integrating third-party DP, PA and HART devices with EDD files
SIMATIC PDM can be used to assign the parameters for a field device (made by any
manufacturer). The EDD (Electronic Device Description) file forms the basis for the
device specification and for acyclic communication.
EDDL (Electronic Device Description Language) is a script language specified by the
PROFIBUS Foundation and is the only device description standardized by the IEC (IEC
61804).
The device manufacturer supplies the following in an EDD package:
 Device description (EDD file)
 Lexicon/user languages
 Help files (relating to function and operation)
 Manuals (technical documentation)
Integrating third-party DP, PA and HART devices with
EDD files  Communication description (GSD file)
 Pictures
Procedure
1. Open the SIMATIC PDM Manage Device Catalog tool via
Start > SIMATIC > SIMATIC PDM > Manage device catalog
2. Click ‘Browse’ to browse to the EDD-file to be imported.…
3. Click ‘OK’

4.6 Time synchronization

Time synchronization –
Rules
Rules
Only 1 active time master per network
External time source : High-grade internal time sources:

The time within the PCS 7 plant is to Central plant clocks (synchronized with
match the local time. an external time source when available)
WinCC "time synchronization" application: An OS server can be configured as a time

3 possible roles for an OS-Server : master either with or without external time
synchronization.
• time master,
• cooperative time master and A time slave can be the time master for
• time slave lower-level components and systems.
Domain controller in the network:

“High-precision time stamping" function:
• will synchronize all of the nodes
• A direct time synchronization of the plant bus
• additional synchronization corrections using
is necessary, for accuracy reason.
integrated PCS 7 tools (WinCC time
synchronization) required
Course ST-PCS7ASE  A network may only contain 4one

- 29 active time master. SITRAIN - Siemens AG © 2016
 Time synchronization with an external time source (e.g. GPS, DDF 77) is required if
the time within the PCS 7 plant is to match the local time.
 Central plant clocks (synchronized with an external time source wherever possible)
are high-grade internal time sources for PCS 7 plants.
 A time slave can be the time master for lower-level components and systems.
 Any domain controllers that are available in a network will synchronize all of the
nodes in this network. A synchronization cycle using domain controllers has a
duration of eight hours as standard. For reasons of precision, additional
synchronization corrections using integrated PCS 7 tools (WinCC time
synchronization) are required. You can define an interval at which the OS
synchronizes its time with that of an external time source.
 The WinCC "time synchronization" application can be used to configure an OS server
as a time master, a cooperative time master, and a time slave.
 An OS server can be configured as a time master either with or without external time
synchronization.
 A direct time synchronization of the plant bus is necessary if the "high-precision time
stamping" function is used for selected signals in an automation system. The
accuracy for high-precision time stamping is insufficient if the central plant clock fails.
The chronological order of the signals displayed remains intact.

Time synchronization in a workgroup
4.6.1 Time synchronization in a workgroup
With central time master Without central time master
Time master: Time master:

Central plant clock on the plant bus. The OS servers are the time masters for the PCS 7
plant.
(SICLOCK TC 400, SICLOCK TM or SICLOCK TS)
The central plant clock is either synchronized with
an external signal (e.g. GPS), or operates with the
internal real time clock.
 See [141] PCS 7 V8.2 Time synchronization - Function Manual - 03_2016, 4.3. for
more details

Time synchronization
4.6.2
in a domain with one hierarchy
Time synchronization in a domain with one hierarchy
With central time master
Without central time master
With central
Course time master in a Windows domain 4 - 31Without central time master
ST-PCS7ASE in a Windows
with a hierarchy domain with a hierarchy
Time master: Time master:
The SICLOCK central plant clock on the plant bus Domain controller (DC) with PDC emulator
and the terminal bus operation master role.
The central plant clock is either synchronized with
an external signal (e.g. GPS), or operates with the
internal real time clock.
 See [141] PCS 7 V8.2 Time synchronization - Function Manual - 03_2016, 4.4. for
more details.

SIMATIC
TimePCS 7 AS Engineering
synchronization in a domain with multiple
hierarchies
4.6.3 Time synchronization in a domain with multiple hierarchies
The above example shows time synchronization with the following structure:
 Stratum 0
The time source is an atomic clock. This atomic clock synchronizes the GPS
satellites or the DCF 77 senders, for example.
 Stratum 1
The central plant clock (SICLOCK) receives the time via a radio signal (e.g. GPS
decoder or DCF 77 receiver). SICLOCK transfers the time to domain controller 1 in
stratum 2.
 Stratum 2
Domain controller 1 is the time slave of the central plant clock. Domain controller 1
transfers the time to several domain controllers in stratum 3. Domain controller 1 is
the time master of the domain controllers in stratum 3.
 Stratum 3
The domain controllers in stratum 3 synchronize the time of their own process units in
stratum 4. The domain controllers in stratum 3 are the time masters of their own
process units.
 Stratum 4
The process unit components are time slaves.
Meaning of the strata for a PCS 7 plant

The higher the stratum level, the higher the potential time difference in relation to the
original time signal source. As time forwarding in a network also takes time, the time of
lower strata time masters is more precise than the time of higher strata time masters.

Rules for planning a PCS 7 plant taking strata into account

Please observe the following rules when planning time synchronization, to ensure that
the time deviation of the time master is not too high in relation to the components in the
lowest stratum:
 Use as few strata as possible.

 In most cases using a maximum of four strata is recommended.
 Use the same strata for the same structure elements.
When planning a PCS 7 plant to be synchronized, you should define exactly which
hierarchy would be best for receiving and forwarding the time.
 See [141] PCS 7 V8.2 Time synchronization - Function Manual - 03_2016, 3.6 for
more details.
4.6.4 Selecting the time master
Selecting theOntime master PCS 7 plant, you require a time master to which the additional
a time-synchronous
plant components can be synchronized. The table below lists the components that are
used as time masters, depending on the network environment:
Time Master With time source Provide time via … Time master forwards Forwards the time to
… the time to … …
SICLOCK Central clock: Terminal bus Domain controller -

Not synchronized
or Terminal bus OS server Terminal bus with OS
synchronized servers and OS
(e.g. via GPS or clients
DCF77) Plant bus Automation systems -
OS server • BIOS clock Terminal bus OS clients
• GPS
• DCF 77 Plant bus CP of the OS servers that Automation systems
are active time masters
Domain controllers • GPS Terminal bus OS server OS clients

• DCF 77 Plant bus, including
• NTP server the automation
systems
PC • BIOS clock All OS servers as time
• GPS masters
• DCF 77
• NTP
more information about selecting the central plant clock.

Time synchronization – SIMATIC mode: CP settings

Time synchronization – SIMATIC mode: CP settings
-1EX20-
If several CPs are being operated in

the station, the automatic setting can
lead to collisions. To avoid this, you
can specify the direction in which the
frame is forwarded.
Procedure
1. Open the project in SIMATIC Manager.
2. Select the station that will be synchronized.
3. Open the configuration of the hardware.
4. Select the CP 443-1, followed by
Edit > Object Properties.
The "Properties - CP 433-1" dialog box opens.
5. Switch to the "Time-of-Day Synchronization" tab.
6. Activate the "Forward time" check box in the "SIMATIC mode" group.
7. Click "OK".
If you are operating with several SIMATIC 400 stations, repeat this procedure for each
CP.

Additional settings for the CPU

4.6.5 Additional settings for the CPU
Procedure
1. Open the project in SIMATIC Manager and select the station that will be
synchronized.
2. Open the configuration of the hardware. And select the CPU, followed by
Edit > Object properties.
3. The "Properties - CPU..." dialog box opens. Go to the "Diagnostics/Clock" tab.
4. In the "Clock" group select the following:
 For "Synchronization in the AS" select the synchronization mode
"As slave".
 For "Synchronization to MPI" select the synchronization type "None"
5. Click "OK".

Time synchronization – SIMATIC mode

4.6.6 Time synchronization in SIMATIC mode: Integrated interface of the CPU
Integrated interface of the CPU 410H
410H
Properties of an of the integrated

PN interfaces of CPU 410-5H
Course ST-PCS7ASE
If the CPU receives MMS time 4messages,
- 36
the local time is synchronized unless the NTP
mode was configured (MMS = Manufacturing Message Specification).
The advantage of this procedure is that it is generally more precise than the NTP mode.
Synchronization role
You can specify whether the clock of the CPU synchronizes other clocks of devices at
the PROFIBUS or not (setting options depend on the interface).
As a slave: The clock is synchronized by another clock.
As a master: The clock synchronizes other clocks as the master.
None: There is no synchronization.
Time interval
Select the interval at which synchronization is to be carried out (only if "As a master"
was selected as the synchronization role).

4.6.7 Time synchronization in NTP mode (For CPU 41x-3IE)
The CPU with integrated Ethernet interface can only be synchronized via the NTP
mode. We recommend using a SICLOCK TC 400 as an external clock.
Please note the following restriction that is applicable in this case: The SICLOCK
supports a maximum of 50 NTP requests/sec. In the case of previous CPUs, we
recommend that you continue to use S7 mode. These CPU types must not be used in
PCS 7 configurations with only a plant bus (and without a terminal bus).
NTP mode is not yet supported by all PCS 7 components. As a result, both modes must
be used simultaneously in order to perform time synchronization with the IE bundles. If
both time servers are operated on a single PC, poor priority settings can lead to a time
offset. In this case, an effective remedy would be to use a SICLOCK, which supports
both modes.
more reasons to choose NTP mode.
The following describes the configuration of the time synchronization for the CPU types
with integrated Ethernet interface.
Requirements
 These CPUs can only be used in PCS 7 configurations with a plant bus and a
terminal bus.
 CPU with integrated Ethernet interface
Time synchronization
Example: – NTP mode
For CPU 41x-3 PN/DP
CPU 416-3 PN/DP
 CPU 414-3 PN/DP
CPU Properties
Properties of integrated
Ethernet interface

Procedure for setting the CPU

synchronized.
2. Open the configuration of the hardware and select the CPU, followed by
Edit > Object properties.
3. The "Properties - CPU..." dialog box opens. Go to the "Diagnostics/Clock" tab.
4. In the "Clock" group select the following:
 Synchronization method "As master" and a time interval of "10 seconds" for
"in AS" synchronization“
 Synchronization method "None" for "on MPI" synchronization
5. Click "OK".
Procedure for integrated Ethernet interface

synchronized.
2. Open the configuration of the hardware select the PN-IO interface, followed by
Edit > Object properties
3. The "Properties PN-IO" dialog box opens. Switch to the "Time-of-Day
Synchronization" tab.
 Activate in the "NTP Mode" group the check box
"Enable Time-of-Day Synchronization in NTP Mode"
 Enter the IP address of the central plant clock (SICLOCK TC 400 or SICLOCK
TM) as the NTP server address.
 Enter the value "10" in the "Update Interval (Seconds)" input field.
4. Click "OK".

4.7 Redundant (Fault tolerant) Automation Systems
Redundancy
4.7.1 Concept of PCS
Redundancy Concept 77
of PCS
6 7
9
Course ST-PCS7ASE The PCS 7 fault-tolerant components 4 - 38
enable you to achieve the desired form ofSITRAIN
fault - Siemens AG
tolerance in all automation levels:
 Operator stations, BATCH stations, Route Control stations, maintenance stations,
central archive server (control level)
 Bus system
 Automation system (process level)
 Distributed I/O (field level)
1. Several clients (OS clients, BATCH clients, Route Control clients) can access data
on a server (OS server, BATCH server, Route Control server).
2. Communication between the operator stations (client and server) and
communication with the engineering station is over a redundant, fault-tolerant
terminal bus (Industrial Ethernet). The clients and server are connected to the
terminal bus via switches.

3. The servers (OS server, BATCH server, Route Control server, maintenance server,
central archive server) can, when necessary, be set up redundantly.
4. Automation systems communicate with the OS servers/Route Control servers and
engineering stations and among themselves over the redundant, fault-tolerant plant
bus (Industrial Ethernet). The automation system, server and engineering station
are connected to the plant bus via switches.
5. Each part of the redundant, fault-tolerant S7-400H automation systems is
connected to the plant bus with an Ethernet communications processor (CP). Each
part of the AS be connected to several PROFIBUS DP chains. The internal
PROFIBUS DP interfaces or additional communications processors are used for the
attachment.
6. The redundant connection to the DP master system is achieved using two 153-2 IM
modules in each ET 200M.
7. Using redundant digital or analog input/output modules, you can evaluate signals
from sensors/ actuators. If one of the two redundant modules fails, the input/output
signal of the functioning module are evaluated.
8. Fieldbus systems can be connected to the redundant PROFIBUS DP. The
configuration of a redundant fieldbus can be realized with a redundant gateway (for
example, PA link). The field devices are connected to the subsystem (for example,
PROFIBUS PA) via AFD, active field distributors, (or AFS when ring/coupler
redundancy is used).
9. The Y Link allows you to connect non-redundant PROFIBUS distributed I/O devices
to a redundant PROFIBUS DP.
Redundant Automation Systems
Fault-tolerant solutions for the AS
4.7.2 Fault-tolerant solutions for the AS
• Physical separation increases independence

• The synchronization modules can and thus availability
be replaced in runtime. • Can be up to 10 km.
• The same rack number must be set • The synchronization cables must not be
at all synchronization modules up cross-connected.
to firmware V3.x.
S7-400H fault-tolerant programmable controller

Course ST-PCS7ASE
Only a fault-tolerant automation4 -system
39
can ensure an extremely short process safety
time, for example, a switchover time in the milliseconds range. PCS 7 enables you to
configure your process control system with redundancy using the S7-400H fault-tolerant
programmable controller.
The S7-400H programmable controller and all the other components in the PCS 7
environment are tuned to one another.

With this solution, a second backup CPU, which is event-synchronized to the master
CPU, performs the same processing tasks of the user program as the master. If the
active master CPU fails, the standby CPU continues processing the user program
without delay. This type of standby is referred to as "Hot standby".
There are always two central processing units and power supplies in an S7-400H. The
communications processors and I/O modules are expansion modules.
 See [511] PCS 7 V8.2 Fault-tolerant Process Control Systems - Function Manual -
03_2016, 4.2 for more details.
Active redundancy
The automation system consists of two redundantly configured subsystems, which are
synchronized through fiber-optic cables. The two subsystems form a fault-tolerant
automation system that operates according to the principle of active redundancy.
Active redundancy means that all the redundant equipment is permanently in operation
and also takes part in acquisition of the process data. The active redundancy partner is
responsible for executing the control task. The user programs loaded in both CPUs are
fully identical and are run synchronously by both CPUs.
If the active CPU fails, the automation system automatically switches to the redundant
CPU. The failover has no effect on the ongoing process because it is bumpless.
03_2016, 7 for more details about Failure, Switchover and Return of Fault-tolerant
Components.
Redundant
4.7.3 Automation
Fault-tolerant Systems
solutions for the IO
Fault-tolerant solutions for the I/O
The availability of the I/O can be increased through the following configuration options:
Single-channel switched I/O Redundant I/O
Symmetrical design: same slots, identical interfaces, same Profibus addresses of DP-slaves,
identical modules (MLFB, FW-version)!
Course ST-PCS7ASE
 Single-channel switched I/O (distributed I/O)
4 - 40 SITRAIN - Siemens AG © 2016

Single-channel switched I/O describes the situation when the input/output module
(SM) used to process a process signal exists only once. The communication path to
the single channel I/O is redundant and fails over to the functioning communication
path if one of the paths goes down.
 Redundant I/O (distributed I/O)
Redundant I/O describes the situation when the input/output modules (SM) for
processing a process signal are doubly available and can be addressed by both
CPUs. This ensures that the CPU signal or process signal will continue to be
processed by a functioning module even when its partner fails.
 See [511] PCS 7 V8.2 Fault-tolerant Process Control Systems - Function Manual –
03_2016, 4.1 for more details
4.7.4 Fault-tolerant solutions for the IO – CFC libraries
Concept
All redundancy-capable modules released for PCS 7 now support the channel group
specific redundancy via the new library “Redundant IO CGP V5.2“
 See [211] PCS 7 V8.2 Released Modules - Catalog Overview - 03_2016, for the
complete list of modules.
Seesolutions
Fault-tolerant [512] SIMATIC forS7-400H – CFC libraries
the IOFault-tolerant systems - 07_2014, 15.5 for more details
about other options for connecting redundant I/Os.
Formerly known as
"Redundant IO CGP".
Only listed for
compatibility reasons.
Library for channel group

redundancy.
Only this library may be
used in PCS7 V8
Formerly known as
"Redundant IO (V1)".
Only listed for
compatibility reasons.
Course ST-PCS7ASE
Only the library “Redundant IO CGP V5.2” is now used in PCS
4 - 41
7 V8.1.
 Support for channel group specific passivation for all modules. The characteristics of
the module determine if the channel group contains one channel, more than one or
all channels.
 The compiler option ‘Generate module driver’ uses this library for all redundant
ET200M modules only.

Within a multi-project it is possible to use the new drivers of the ‘Redundant IO CGO
V50’ library in a project (with use of new functions after upgrading), and the old drivers
can be used in a different project (without using new functions).
Using the same blocks from different libraries is not allowed within in project or even
more inside a CPU.
CGP: Chanel Group passivation
Y Link: Gateway
MGP: between redundant
Module Group passivation and non-
redundant PROFIBUS DP
4.7.5 Y Link: Gateway between redundant and non-redundant PROFIBUS DP
The Y Link consists of two IM 153-2 interface modules and an Y coupler which are
interconnected through the corresponding bus modules (BM IM/IM and BM Y coupler).
Functionality
The Y Link creates a gateway from the redundant DP master system of a S7-400H to a
non-redundant DP master system. This enables devices with only one PROFIBUS DP
interface to be connected to a redundant DP master system as switched I/O.
The new generation of the Y Link no longer requires a repeater and is capable of
forwarding diagnostics requests from the corresponding function modules or I/O
modules to the CPU.
DPV1 slaves can be connected downstream from the Y Link in addition to the standard
PROFIBUS DP slaves.
03_2016, 4.3.5.3 and 5.4.5 for more details how to configure the Y Link.

Connection of PROFIBUS PA to a redundant
SIMATIC PCS 7 ASDP
PROFIBUS Engineering
4.7.6 Connection of PROFIBUS PA to a redundant PROFIBUS DP
The DP/PA Link allows a connection between PROFIBUS DP and PROFIBUS PA. The
DP/PA Link consists of the IM 153-2 interface module and one or more FDC 157 DP/PA
couplers that are interconnected through the backplane bus.
Functionality
Course ST-PCS7ASE The DP/PA Coupler is a transceiver
4 - 43 that interconnects PROFIBUS DP
SITRAIN and PROFIBUS
PA and decouples the various transmission rates. It is a slave on the PROFIBUS DP
and a master on the PROFIBUS PA. Seen from the automation system, the DP/PA Link
is a modular slave. The individual modules of this slave are the field devices that are
connected to the lower-level PROFIBUS PA lines.
In the automation system, data are transmitted via PROFIBUS DP at a maximum speed
of 12 Mbps with negligible delay. This is currently the fastest connection between
PROFIBUS DP and PROFIBUS PA and can be used by all automation devices with a
PROFIBUS DP interface.
The DP/PA Link decouples the various transmission rates of the bus systems and
brings the lower-level PA devices together at one PROFIBUS DP address. All DP
masters can take advantage of this feature.
03_2016, 4.3.5.4 and 5.4.6 for more details.

Redundanter PROFIBUS PA
4.7.7 Redundant PROFIBUS PA
Connection to redundant PROFIBUS DP Connection to singular PROFIBUS DP
Course ST-PCS7ASE
Functionality 4 - 44 SITRAIN - Siemens AG © 2016
PROFIBUS PA allows the connection of PA devices. A redundant PROFIBUS PA is

connected to redundant FDC 157-0 DP/PA couplers. If the communication path of the
PROFIBUS PA fails, the communication path is preserved as far as the spur line to the
field devices.
Fault-tolerant communication solutions

The following communication solutions are offered to increase the system availability:
 Ring redundancy with AFD (Active Field Distributor)
 Coupler redundancy with AFS (Active Field Splitter)
The DP/PA coupler can be used stand-alone or in the DP/PA Link.
 ATTENTION!
Mixed configurations
You can connect only one redundant DP/PA coupler pair per DP/PA link. In mixed
configurations, you can operate up to 3 additional non-redundant DP/PA couplers.
The coupler pair (FDC 157-0 DP/PA coupler) should be installed for redundant
operation in the last two slots of the ET200 station.
03_2016, 4.3.5.5 for more details.

Redundant
SIMATIC Automation
PCS 7 AS Engineering Systems
Fault-tolerant solutions for the plant bus
4.7.8 Fault-tolerant solutions for the plant bus
 Ring 1 shows the functionally correct structure (shared switches for AS and OS).
Bus1 shows the functionally correct configuration (shared switches for AS and OS).
 Ring 2 shows the typical structure in PCS 7 plants (separate switches for AS and
Bus2 shows the typical configuration in PCS 7 plants (separate switches for AS and OS).
OS).
Functionality – Fault-tolerant plant bus

Course ST-PCS7ASEThe
plant bus connects automation4 - 45systems with servers (OS server,
SITRAIN Route
- SiemensControl
AG © 2016
server). The connection to a fault-tolerant plant bus is implemented with Ethernet
communications processors (CPs) that are installed in each subsystem of the
automation system and in the servers.
Fault-tolerant plant bus can be set up in a ring structure with network components of
SIMATIC NET. The network components ensure unrestricted operation of the plant bus.
For example, a broken cable in the connection between the modules is tolerated and
communication remains uninterrupted.
If the plant bus is disrupted, no process data are transferred between the servers and
the automation systems or between the automation systems themselves.
Functionality – Redundant fault-tolerant plant bus

The plant bus connects automation systems with servers (OS server, Route Control
server). The connection to a redundant, fault-tolerant plant bus is implemented with
Ethernet communications processors (CPs) that are installed in each subsystem of the
automation system and in the servers.
A redundant fault-tolerant plant bus is set up using two identical, linked plant bus rings
(double ring). The network components ensure unrestricted operation of the plant bus. If
a plant bus fails, communication remains possible over the second plant bus.
03_2016, 4.3.4.2 and 4.3.4.3 for more details.

Network components for a fault tolerant/redundant
plant bus
4.7.9 Network components for a fault tolerant/redundant plant bus
Example of a ring structure with SCALANCE X400 and X200

Example of a ring structure with SCALANCE X400 and X200
SCALANCE X414-3E as
redundancy manager
Redundancy manager
• enables the configuration of ring redundancy.

• Network components operating as the redundancy manager
Netzwerkkomponenten
can ensure that the bus connectionsfürremain
einenundisturbed if there
is a fault on a bus line (such as a cable break).
hochverfügbaren/redundanten Anlagenbus
Example
Example of aofring
Course ST-PCS7ASE
a ringstructure
structure with
withSCALANCE
SCALANCEswitches
4 - 46switches SITRAIN - Siemens AG © 2016
Standby-Manager
• allows a redundant coupling of networks
• Redundant coupling of networks is only possible if 2 devices (switches) within a network segment
support the standby manager function.
• One network component becomes the standby manager (master) and the other standby manager
(slave).
• When operation is error-free, the data link running between the redundant networks is active for the
standby manager (master). If this data link fails (e.g., due to a defective device or cable break), the
standby manager (slave) activates its data link while the fault remains pending.
03_2016, 4.3.1 for more details.

4.8PCS 7 PROFIBUS
PROFIBUS andand PROFINET
PROFINET –in SIMATIC PCS 7 by comparison
SIMATIC
4.8.1 PCS 7PCS
SIMATIC V8.1 Systemarchitecture
7 System architecture
PCS
Training7 PROFIBUS
documentation and PROFINET 4 - 54
SP-PCS7CWS SITRAIN - Siemens AG © 2015
Requirements
4.8.2 Requirements to PROFINET IO atIOthe
to PROFINET PA PA
at the
Scalable Redundancy Configuration in Run (CiR)

Primary Backup
DCS
Redundant Controller
Redundant Network Remote I/O

Proxy
Device with redundant Device with singular

connectivity connectivity
Time Synchronization / time stamping Fieldbus integration

System Master Clock DCS
(GPS, DCF77, …)
PROFIBUS DP
IO-Controller 1 IO-Controller 3
IO-Controller 2
Backup
Clock Master PROFINET
HART
PROFIBUS PA
Proxy
Training documentation SP-PCS7CWS 4 - 54 SITRAIN - Siemens AG © 2015

PCS 7 PROFIBUS and PROFINET
by comparison
4.8.3 PROFIBUS vs. PROFINET
Same concept > different names
DP-Master DP-Master IO-Controller IO-Supervisor

Class 2
PROFIBUS DP PROFINET IO
/ RS 485 / Ind. Ethernet

DP-address Devicename
DP-Slave IO-Device
by comparison 1..127 catalyzer XY
PROFIBUS PROFINET is Ethernet

• One line where all • Ethernet is the established standard for fast data transfer
participants
Training documentationconnected.
SP-PCS7CWS in the IT 4world
- 55 (IEEE 802.3) SITRAIN - Siemens AG © 2015
• Performance depends • PROFINET is always full-duplex > simultaneous
directly of the amount of communication in two direction
participants. Controller
100 MBit/s
Master 100 MBit/s
100 MBit/s full-duplex
• PROFINET is always
Slaves „switched Ethernet“

by comparison
Switch connected in a line Devices
• Controllable network load via topology
Limits
Training documentation SP-PCS7CWS

PROFIBUS DP
4 - 56
PROFINET IO
Transmission speed Max. 12 MBit/s 100MBit/s
Cycle time Min. 300µs Min. 31,25µs
Number of IO-Devices / DP-Slaves 125 (limited) 250 (CPU 410)
IO-Data for one IO-Device / DP-Slave 244 Byte 1440 Byte


by comparison
Rules
PROFIBUS DP PROFINET IO
• 32 stations on one copper segment, Repeater • Max. electrical distance between two nodes
counts as device! is 100m, this is an IEEE802.3 rule!
• Terminate each segment (first and last node) • Max. 64 nodes in a line.
• Notice shielding on the connectors and when
going in cabinet
• 10cm distance between cables higher 110V if
not isolate with i.e. grounded metal plate, if not
possible use FO!
• On high Baudrate no spur lines, no cables
shorter 1m
• Segment length depends on Baudrate!

by comparison max. 100m
electrical

Simple commissioning by configuration
Single addressing for each slave of the IO-Devices via IO-Controller and
engineering station.
Simple and fast replacement of IO-Device without exchangeable medium or

engineering station via topology.

4.8.4 Redundancy methods in Profinet for PCS 7
Profinet – Ring redundancy with MRP

Profinet – Ring redundancy with MRP
Redundancy Manager
Ring port 1 Ring port 2
MRP (Media Redundancy Protocol):

• Redundancy Protocol
• Redundancy manager and clients
• OSI model layer 2 protocol
• Max. 50 Devices in the ring
System in PROFINET–norm
redundancy
• Standardized Terms and conditions
• Max. 200ms reconfiguration time
Profinet – System redundancy: Terms and conditions

Application Relationship (AR) Describe the communication relationship between an IO-
Controller and an IO-Device.
Network Access Point (NAP) A NAP equates to an interface of one device, not to be mixed
up with a port.
S1-Device A S1-Device can hold only one AR.

S2-Device A S2-Device can hold two AR.
R1-Device A R1-Device has two NAPs. Each NAP can hold one AR to
one IO-Controller.
R2-Device
A R2-Device has two NAPs. Each NAP can hold two
AR to two IO-Controllers.

System redundancy –
Terms and conditions
System redundancy S1 • Each IO-Device is at least a S1-Device.

• It exist one physical network.
IO-Controller
AR 1
Terms and conditions S1-Device
System redundancy S2 • At the system redundancy S2 exists two IO-Controller.

• The IO-Controller communicate parallel with each S2-Device.
• Every component is arranged in one physical network.
Following IO-Devices support

AR 1 AR 2 the functionality with PCS 7
V8.1 SP1:
S2-Device
• ET 200M
• ET 200SP
• SIMOCODE PN

Terms and conditions SIMATIC PCS 7 AS Engineering
System redundancy R1 • The system redundancy R1 is comparison with the redundancy at

PROFIBUS DP.
Not supported by PCS 7! • The R1-Device has two NAPs and each NAP is connected to one
IO-Controller.
• It exist two physical and logical separate networks.
AR 2
Terms and conditions
AR 1
R1-Device
System
Training redundancy
documentation R2
SP-PCS7CWS • The system redundancy
4 - 64 R2 exist in principle ofSITRAIN
two parallel S2
systems.
Not supported by PCS 7! • Therefor it needs 4 IO-Controller with 4 AR in the system.
• It exist two physical and logical separate networks.
AS 1 AS 2
AR 1.2
AR 2.2
AR 1.1 R2-Device
AR 2.1

Comparison
4.8.5 of topologies
Comparison of topologies
Typical PROFIBUS DP Topology
CPU 410-5H CPU 410-5H
OLM OLM OLM ET 200M
SIMOCODE
ET 200M
Link to single
slaves
Y-Link
SIMOCODE
DP/PA-
Link DP/PA-
AFD Link
PROFIBUS PA
AFD AFD
OLM Link to Profibus

Comparison of topologies ring PA

Typical PROFINET IO Topology
CPU 410-5H
MRP ring
PROFINET ET 200M PN
MRP
ET 200M PN
Weighting system
ET 200SP PN
SIMOCODE PN Link to PROFIBUS PA via
2 ET 200M PN
3 IE/PB Link and DP/PA-coupler
PROFIBUS DP PROFIBUS PA AFD
4 IE/PB-Link DP/PA
Coupler

Profinet IO Topologie in PCS 7 SIMATIC PCS 7 AS Engineering
Open Ring structure with system redundancy S2
Profinet IO Topologie
The network in PCS will
disruption 7 be compensated by the MRP ring. All devices will
communicate still with IO-Controller 1.
MRP ring structure with system redundancy S2
MRP
 The first failure caused by a network disruption will be compensated by the MRP ring.
All devices will communicate still with IO-Controller 1.
 The second failure caused by another network disruption can be compensated by
system redundancy S2. Both IO-Controllers communicate in parallel with the devices
being available for them.
Checkpoint
4.9 Checkpoint

 Which components and which
networks can be implemented
redundantly in PCS 7?

Content 5
5 Type-Instance Conceptions in PCS 7 V8.2 ............................................................ 3
5.2 Import-Export-Assistant (IEA) and IEA File Editor ................................................................. 3
5.2.1 Process Tag Types: Overview of the procedures .................................................................. 5
5.2.2 Creating a process tag type ................................................................................................... 6
5.2.3 Create / Assign File Template ............................................................................................... 7
5.2.4 Structure of the import file and presentation in the IEA File Editor ...................................... 13
5.2.5 Using Microsoft Excel to edit import files ............................................................................. 17
5.2.6 Importing the process tags in the plant view ....................................................................... 19
5.2.7 Task ..................................................................................................................................... 21
5.2.8 Modifying a process tag type and updating the process tags ............................................. 22
5.2.9 Designate existing charts as process tags .......................................................................... 24
5.2.10 Export of existing process tags ............................................................................................ 25
5.2.11 Changing process tag types without automatic update ....................................................... 26
5.3 Tasks and checkpoints ........................................................................................................ 28
5.4 New type conception: Control Module Types ...................................................................... 29
5.4.1 Comparison to process tag types ........................................................................................ 29
5.4.2 Creating Control Module Types from standard Process Tag Types ................................... 31
5.4.3 Create a new control module type starting from an empty template ................................... 33
5.5 Editing the technological I/Os .............................................................................................. 34
5.5.1 Possible objects ................................................................................................................... 35
5.5.2 Editing the technological I/Os with a shortcut menu ............................................................ 35
5.5.3 Editing the technological I/Os using drag & drop................................................................. 36
5.5.4 Data types for control variables and generic data ............................................................... 36
5.5.5 Attributes .............................................................................................................................. 37
5.6 Task ..................................................................................................................................... 42
5.7 Synchronizing Control Module Types .................................................................................. 43
5.7.1 Synchronization means … ................................................................................................... 43
5.7.2 Procedure ............................................................................................................................ 45
5.8 Summary for the synchronization behavior ........................................................................ 47
5.8.1 Changing objects in the technological I/Os ......................................................................... 48
5.8.2 Changing values or interconnections .................................................................................. 49
5.8.3 Changing properties and attributes...................................................................................... 50
5.9 Control module variants ....................................................................................................... 51
5.9.1 Optional blocks .................................................................................................................... 51
5.9.2 Variants of a manually copied control module ..................................................................... 52
5.9.3 Optional blocks connected to the same input ...................................................................... 54
5.10 Tasks and checkpoint .......................................................................................................... 57
SIMATIC PCS 7 – Type-Instance Conceptions in PCS 7 V8.2


5 Type-Instance Conceptions in PCS 7 V8.2

Learning
5.1 targets targets
Learning
The participant knows…

 Differences and features in common with Type
instance conceptions for process tag types and
process tags, as well as control module types and
control modules
 Principle and functionality of IEA as well as
structure and syntax of the import file for the IEA
The participant is able to…

 Create process tag types and process tags by
help of IEA
 Adopt existing charts as process tags and to
modify them afterwards
 Create control module types and control
modules manually
 Synchronize control module types and control
modules as well as to create variants on base of
optional blocks manually
Training Documentation SP-PCS7CWS 5-2 SITRAIN - Siemens AG © 2015
5.2 Import-Export-Assistant (IEA) and IEA File Editor
Pre-requisite
A master data library is required to use the function of the IEA.

The Import Export Assistant (IEA) –
Principle
Principle
Create/Change = I/O point for parameters, signals and

Process Tag Type messages, to appear in the import file
Assign/Create File Template

Tools:
Import File
PTT • IEA editor
Create File Template Copy, • Notepad
Edit • Excel
PT • …
Import PT
PT • …
Update
Import file
Export file
PT
Export PT
PT
When data has been changed in the Process Tags
Process tags are derived as a large number of individual instances from pre-defined
process tag types by use of the Import-Export assistant.
Trainingsunterlage SP-PCS7CWS 5-5 SITRAIN - Siemens AG © 2015
This tool allows to create and to edit a so-called import file. After edition (using IEA, or
any editor like Notepad, Excel), the re-import of the modified file results in automated
creation of a large numbers of process tags correctly placed in the plant hierarchy.
s7jieaEx.exe
The "s7jieaEx.exe" IEA file editor is a separate application. You can also use it
separately from the PCS 7 installation. You can copy it and make it available to system
engineers.
Important use cases

You have created a process tag type or a model You have created a process tag type or a model and
and the import file using the IEA. Based on this the import file using the IEA. You want to modify this
import file, you want to create process tags or process tag type or model, for example, by selecting
replicas of the model. To do this, you must other I/Os, and add these columns to the import file.
increase the number of rows in the import file in
accordance with the number of process tags or
replicas, for example, by copying and editing.
You do not have a tool for creating an import file You want to compare an import file with an export file
and want to use the IEA file editor as an or vice versa. By opening two windows and
engineering tool for creating the structures for the arranging them in the IEA file editor window, you will
columns, column groups and rows in the import have no difficulty in making the required comparison.
file and entering the corresponding values.

5.2.1 Process Tag
Process TagTypes:
Types:Overview
Overviewofof the
the procedures
procedures
Starting point is a Process Tag Located in chart folder.

(chart). The Process Tag has to be tested to avoid
multiplication of failures.
Create a Process Tag Type A wizard creates a Process Tag Type.

It is placed in the Master Data Library
(new folder ‘Process Tag Types’).
Create Importfile / File Template

The Importfile is a template in CSV format. Don’t
forget to save a backup before modification!
Modify Importfile Generate new process tag information by

multiplication and modification of rows in the
Importfile.
Import the modified Importfile

A wizard generates the new Process Tags (charts)
(create charts) following the information in the Importfile.
The Import Export

Starting
Trainingsunterlage Assistant
with
SP-PCS7CWS (IEA)
an existing chart, you–can
5 - 6 create a Process Tag Type.
I/O points for a Process

At the creation the Tag Type
chart will be copied to the Master Data Library, not affecting the chart
you used as a starting point.
Starting point Result
chart
Creating the Process Tag Type
From the chart, the desired I/O 5points

Trainingsunterlage SP-PCS7CWS -7
(for parameters, signals SITRAIN
and messages) have to
be selected to appear in the import file.
Only I/O points represented in the import file can be automated adjusted to the
instances, later derived from the process tag type.

Example:
5.2.2 Level ameasurement
Creating for the reactor
process tag type
The wizard:
I/O points:
 In the “I/Os in the chart of the5 -process

Trainingsunterlage SP-PCS7CWS 8
tag type” window on the left, select the I/O
points for “Parameter” and “Signal”. To do this, double-click or select the I/Os and
click the button.
The I/O point is applied and displayed in bold letters.
 In the "I/O points for parameters/signals" window on the right, you edit the selected
I/O points.
 The “Parameter/signal”, “Process tag I/O” and "Category" columns can be edited via
a drop-down list. Open the drop-down list by clicking in the corresponding edit box.
 In the "I/Os in the chart of the process tag type" window on the left, select the
messages of the corresponding blocks.
The "I/O points for messages" window displays all messages.
 Category is an additional edit box at an I/O used to assign the I/O to a specific
category. You use this category to sort or filter these I/Os in the process object view.
The parameter and signal categories are found in two text files, which you can
edit/expand according to your specific requirements. The "s7jcategory_p.txt" and
"s7jcategory_s.txt" files are found in the "s7bin" folder, in your installation path.
Result:
The new process tag type is stored in the master data library. The CFC chart that is the
source of the process tag type is stored in the S7 program, where you can reuse it or, if
it is no longer required, delete it.
After the completion of this creation procedure, the Process Tag Type will be present in
the Master Data Library:

Example:
5.2.3 Level
Create measurement
/ Assign for the reactor
File Template
The wizard:
Select the
required I/O
points/messages
 In order to verify all the import

Trainingsunterlage SP-PCS7CWS
file information, open it usingSITRAIN
5-9 - Siemens AG © 2015
the "Open file" button
and, if required, edit it in the IEA file editor.
 To assign an existing import file from the project, click "Other file…" and select the
file required in the dialog box.
 To create a new import file, click "Create file template…" and select the
required columns/column groups in the dialog box. Click "Open file" to open the
IEA file editor and edit this template.
 If you select <no import file assigned> from the “Import file” drop-down list, the
“Column title” column can be edited. You can change the titles and then generate the
template file.
In the "Importing" column, a check mark indicates which I/O points exist in the import
file. If no check mark is displayed, the I/O point does exist in the process tag type but
not in the currently assigned import file.
The file will have a default name based on the Process Tag Type name. The default
storage location is the Global folder of the library storage path.

Column selection for the import file
Selection of columns to generate the structure of the import file
Option Meaning
Trainingsunterlage SP-PCS7CWS 5 - 10 SITRAIN - Siemens AG © 2015
PH comment Comment relating to the PH hierarchy folder

The IEA writes this text to the process tag hierarchy folder.
PH author Name of the author of the hierarchy folder.

The IEA writes this text to the process tag hierarchy folder.
Assigned CPU Component path to the corresponding chart folder

The process tag is created here or, if it already exists, moved here. The assignment of
the existing hierarchy folder remains unchanged and a new one created will be
assigned to this CPU.
Path example: "SIMATIC 400\CPU414-3 DP\S7 program(1)"
Function identifier The IEA enters the function identifier (FID) in the text box (for DOCPRO)
TAG location The IEA enters the TAG location (TAGLocation) in the text box (for DOCPRO)
Chart name Name of the CFC chart
Chart comment CFC-chart comment

When this option is selected, the “Chart name” is set at the same time.
Chart author Name of the chart author

When this option is selected, the “Chart name” is set at the same time.
Sampling time The sampling time of the block. It is derived from the cycle time of the OB multiplied
by the reduction ratio of the runtime group.
Block name Instance block name to be received by the block via import.
Block comment Comment at the block

With a chart-in-chart, this is the comment at the nested chart.
Block icon Name of the icon

This icon is used to display the blocks that perform operator control and monitoring in
the OS picture.
Block group Identifier for the blocks that are assigned to a specific alarm group, which is used for
the mode-dependent automatic hiding of alarms.

tion for the import 

file The "Block comment" and "Block icon" columns are inserted only once per block.
Only blocks for which a parameter/signal I/O or a message has been selected are
taken into account.
Option Meaning
CWS 5 - 10 SITRAIN - Siemens AG © 2015
Value Value for the chart/block I/O (e.g., 8.5).
I/O comment Block/chart I/O comment

(e.g., hysteresis of analog input)
Textual interconnection Textual interconnection to a block/chart I/O (CFC\block.I/O). The interconnection

is created immediately during import if the I/O exists, otherwise a textual
interconnection will be inserted. The textual interconnection is not set on outputs
because the multiple interconnections could cause ambiguities.
You can find additional information in the section: "What You Should Know About
Textual Interconnections" of the IEA online help.
ID I/O identifier, if not BOOL (e.g., UL)
Unit I/O unit, if not BOOL (e.g., degrees centigrade)
Text 0 Text for state 0 (false), if BOOL (e.g., Motor OFF)
Text 1 Text for state 1 (true), if BOOL (e.g., Motor ON)
Enumeration Enumeration for I/Os with data type BOOL, BYTE, WORD,
DWORD, INT, DINT. Value: Name of the enumeration
Invisible I/O visible (false) or invisible (true)
MES relevant Identifier for I/Os that are relevant for MES (true)
or not relevant (false)
Archive I/O whose process value will be archived by the WinCC archive system during
runtime. Values: 'false' = No Archiving,
'shortterm' = Archiving, 'longterm' = Long-term archiving
Chart I/O name Name of the chart I/O (e.g., HYS_AI).

SIMATIC PCS 7Column selection
AS Engineering for the import file
Option Meaning
Value Value for the chart/block I/O (e.g., 8.5).
I/O comment Block/chart I/O comment

(e.g., hysteresis of analog input)
Symbol name Name of the symbol used for the interconnection. With shared addresses, you
can decide whether or not to enter the symbol name in the symbol table during
import.
Symbol comment Comment for the symbol that is entered in the symbol table.
When you select the "Symbol comment" option, the "Symbol name" is also set
simultaneously.
Absolute address Absolute address assigned to this symbol

(optional for symbols entered in the symbol table).
When you select the "Absolute address" option, the "Symbol name" is also set
simultaneously.
ID I/O identifier, if not BOOL (e.g., UL)
Unit I/O unit, if not BOOL (e.g., degrees centigrade)
Text 0 Text for state 0 (false), if BOOL (e.g., Motor OFF)
Text 1 Text for state 1 (true), if BOOL (e.g., Motor ON)
Enumeration Enumeration for I/Os with data type BOOL, BYTE, WORD,
DWORD, INT, DINT. Value: Name of the enumeration
Invisible I/O visible (false) or invisible (true)
MES relevant Identifier for I/Os that are relevant for MES (true)
or not relevant (false)

tion for the import file SIMATIC PCS 7 AS Engineering
Option Meaning
CWS 5 - 11 SITRAIN - Siemens AG © 2015
Priority Message priority. The operator can call this function to filter messages according
to their priority.
Infotext Information text entered in the "InfoText" message edit box
Origin Higher-level designation of the block, e.g., "V100/RA1/T1"
OS area OS area text
Event Event text, e.g., "$$BlockComment$$ process value too high"

(this option is set by default)
Batch ID Batch ID for the message
Operator input - not used for PCS 7 -
Free text 1 ... 5 - not used for PCS 7 -

Example: Level measurement for the reactor
Result
After clicking on "Finish", the File

Template will be created, and
5 - 12
will be set as the current
Import File.
 It is recommended to copy the template file and continue with the copy.
Example in the figure above: LIA3x400_First_Run
Because of the matching column title in the import file and process tag type, the
assignment between the I/O points in the import file and process tag type is made
automatically:
The import file is assigned to the process tag type.

5.2.4 Structure of the import file and presentation in the IEA File Editor
Design of the import file

Design of the import file
3 headlines with specified syntax:
1. Header: 2. Header: Column identifiers 3. Header: I/O keywords

Header of column groups • How to interpret the • Which data are imported?
column? • First keyword is required at least.
• In all languages in the same
way
ImportMode; Project; Hierarchy; FID; TAG Chart; High limit; Measured value; High limit
location; alarm;
IM; Prj; H\; F; O.; C|; P|; S|; M|;
; ; ; ; ChName|ChComment; Value|ConComment; SymbolName|SymbolComment; Event|
Data area for editing,

Important ASCII delimiters: 1 line per instance
; (separates column groups)
| (separates columns inside of column groups)
\ (separates hierarchy levels in the PH)
Example of Keyword Syntax

 Parameter at the Block I/O Point
Value | ConComment { | S7_shortcut | S7_unit } .. { | S7_string_0 | S7_string_1 }
 Parameter at the Chart I/O Point
Value | RefName | ConComment { | S7_shortcut | S7_unit } .. { | S7_string_0 |
S7_string_1 }
 Interconnection at the Block or Chart I/O Point (Shared Address)
SymbolName | SymbolComment | ConComment { | AbsAddr | S7_shortcut | S7_unit }
.. { | S7_string_0 | S7_string_1 }
 Signal at the Block or Chart I/O Point (Textual Interconnection)
- Not recommended as of V6.0 -
 Parameter at the Block or Chart I/O Point (Textual Interconnection)
TextRef | ConComment { | S7_shortcut | S7_unit } .. { | S7_string_0 | S7_string_1 } |
BlockComment | BlockIcon
 Message at the Block I/O Point
Priority | Event | { Origin .. FreeText5 }
{ ... } These parentheses enclose the optional keywords.

Representation in the IEA File Editor

Representation in the IEA File Editor
The IEA File Editor: Insert Column Groups:
Expand Column Group G = General, C = Chart P = Parameter, S = Signal, M = Messages
1 row = 1 process tag
Settings for New hierarchy New

import* folders charts
AS assignment
* to get this column : insert it by

Edit  Insert Column Group  General  Import Mode or button:
The IEA file is displayed as a table

with column and row headers.SITRAIN
5 - 14
Certain columns are
grouped into column groups, for example, the Chart column group assigned the
keywords: "ChName" and "ChComment".
You can change the name of the column group. It corresponds to the column title of the
import file. If you only want to use some of the import options, delete columns within a
column group. If you delete all the columns in a column group, this I/O point is lost. This
changes the process tag type/model.
The row headers contain the row numbers. If you select the row header, the entire row
is selected, for example, for copying.
The IEA file editor also provides all the standard editor functions (copy, paste, save,
etc.).
For the insertion of column groups, all the available column group types (General,
Chart, Parameter, Signal, Message) are defined in a submenu and can be selected as
icons in the toolbar.
You can expand the "Chart", "Parameter", "Signal", and "Message" column groups at a
later time by adding columns. The expansion dialog offers only the column titles that do
not already exist in this column group.
You can access all available functions via the menu commands or the icons in the
toolbar.
The further layout of the editor corresponds to the structure of the Import/Export File
(IEA File).

Modify Import File – Signal columns
Column group Signal
Symbol name Absolute IO address,

Required if symbols are to be
Optional: symbol added to the symbol table
comment
Modify Import File – Parameter columns

Column group Parameter
Parameter value
Textual interconnection,
only possible if a textual Target of the textual
interconnection exists in the interconnection
process tag type for this block IO
<chart name>\<block name>.<IO name>

Modify Import File – Block related columns
Column group Parameter
Block comment Block icon
These columns are only available, if at least one

The parameter
Import Export or signal of the block
Assistant (IEA) – in the
is available
process tag type resp. import file
Modify Import File – Message columns
Column group Messages

Message text

Using Microsoft Excel to edit import files (CSV
format)Using Microsoft Excel to edit import files
5.2.5
Same file, but changed extension:
1 column in the
Numeric values Excel sheet,
Column headers must be IEA syntax for with correct cell content
similar to the process tag type the keywords decimal symbol separated by
delimiter
3 columns in the
import file
1 column group in
the import file
Prerequisite
The import/export data are available as text files in CSV format. CSV format is
supported by many applications (Microsoft Excel, Access, etc.) and is thus suitable as a
general data interface between planning tools and the ES.
The IEA expects these files to have the file extension “*.IEA”. If necessary, you must
change this file extension.
CSV stands for "Comma Separated Value" and is an ASCII text format for storing
tabular data. The comma or semicolon is used as the list separator, depending on the
setting made in the Windows Control Panel. Pressing the enter key creates a new row.
You can create and edit a CSV file in a text editor or using spreadsheet programs, such
as Microsoft Excel, or as an export file from a database, such as dBase, Microsoft
Access, etc. You can edit the file with the .IEA extension conveniently using the IEA file
editor.
Opening CSV files in Excel

1. Change the file extension from "*.iea" to "*.csv" in the Windows Explorer.
2. Start Excel.
3. Open the desired .csv file with the menu command "File > Open…".
4. Edit the file and save it.
5. Change the file extension back from "*.csv" to "*.iea" in the Windows Explorer.
6. If needed make more changes in the IEA file editor. Import the process tags.
 If you double click on a CSV-File directly in the Windows Explorer the content is only

filled in one cell instead in a table.

Furthermore, all cells should have a "text" format, otherwise wrong interpretation as
date may happen. For example, the string of digits "1.23" could be interpreted as
"January 23".
Consider also the regional properties settings in your Windows system control panel
to ensure the proper decimal symbol for numeric values.
 ATTENTION!
Changing the column structure of an import file in Excel can damage the data
consistency and result in a corrupt import file.
A column inside of a column group of the IEA is not corresponding to an own column
in the Excel sheet. Furthermore, the column headers in the import file must have the
IEA compatible syntax.
Data exchange with Excel

7. Select the corresponding rows in the IEA file. Then copy these rows and paste them
to Excel.
8. If you created additional process tags in Excel, first insert these additional rows in
the IEA file.
9. Select the respective rows in Excel and copy them to the corresponding IEA file
(Copy – Paste)
 The advantage of this approach is that the IEA Editor ensures consistent structure of
the import file.


Import the
5.2.6 modified
Importing Import file
the process tags(create charts)
in the plant view
The wizard:
The import
Trainingsunterlage SP-PCS7CWS procedure will make5 -as
21 many copies of the process tag type
SITRAIN as there
- Siemens are
AG © 2015
rows in the import file and will make changes in every copy according to the data in the
corresponding rows in the import file.
 Before importing, check the language set for display units. If you have created the
model in German and the current SIMATIC Manager setting is "English", the German
message texts will be written into the English text file.
Starting point is again the chart LIA3x4 in the Master Data Library:
10. Select the required hierarchy folder, project node, process tag library (hierarchy
folder in the master data library) or process tag type.
11. Select the menu command Options > Process Tags > Import...
Include Signal in the Symbol Table

If you have selected this check box, the interconnection descriptions from the import
files are not only written to the assigned I/Os, but also to the symbol tables of resources
for the relevant hierarchy folders. This means that process tags created during import
are linked with the suitable input and output signals.
Make Textual Interconnections

If you have selected this check box, any open textual interconnections are automatically
closed during import. If the textual interconnections cannot be closed, a message is
entered in the log.

Import File <-> Process Tag Type

If you have selected a single hierarchy folder to which an import file is assigned, this
import file is displayed here in this job list and the import is executed for this process tag
type.
If you have selected a higher-level hierarchy folder, for example, the process tag library,
containing several process tag types at lower levels, you will see the paths of all IEA
files and the corresponding process tag types. The import is executed for all process tag
types. Process tag types that you do not want to import must be removed from this list.
If the path name contains the prefix "???", the IEA cannot find the import file in this path,
for example, because a non-existent drive has been specified. In this case, you need to
search for a matching import file using the "Other file…" button.
The following three buttons are available for editing the list:
 Click "Other file…" to open a dialog box in which you can select another import file
and assign it to the current process tag type. The function checks if the structure of
this import file is valid and matches the process tag type.
 Click “Remove” to remove list entries. The button is only visible when there are
multiple entries. These entries will then no longer be included in the import.
 If you have unintentionally removed too many list entries, click "Cancel" to exit this
step and restart the import.
Import Log
A log will be displayed and saved in a file:

Once the import process has been completed, you will see the following in the “Object”,
“Action” and “Log text” columns:
 the affected object
 whether you are dealing with an action (O.K., End, etc.) or an error (Action).
 You see the effects of the action or the cause of the error (Log text).
If you double-click a line in the log in the "Object" column, either the relevant CFC chart
or the import/export file is opened, depending on what is entered in the log line.
Use the “Print” button to print the log file in accordance with the filter that has been set.
Log File
The "Log file" edit box displays the path of the log file that logs all the events and errors
that have occurred during import. Use "Other file..." to open a dialog box in which you
can select another log file.
Final result
 New hierarchy folder with new charts
Import the modified Import file: Final Result
 Data in the chart due to the data in the import file
Changed symbol for a

process tag
Signal was connected to

the symbol
Textual interconnection
was connected to the Values were assigned to
target instance the parameters
 See [103] PCS 7 V8.1 Engineering System – 11_2014, 8.12.7 for more details
5.2.7 Task
Task: Product concentration monitoring for B410 und B420 using the IEA
Goal
You configure the process tags XIA414_1…3 and XIA424_1…3 for the product
concentration in the buffer tanks using the Import/Export Assistant.
Starting point is an existing process tag type for Analog Monitoring.

5.2.8
Import Modifying a process tag
/ Export Assistant – type and updating the process tags
Consistency of process tag type and import file
Consistency between process tag type and import file
I/O Selection in the Process Tag Type: I/O (Column) selection in the Import File:
not activated, if added later to

the process tag type
Columns, later
inserted in the
import file

Change theThe
process taglimit
warning low type – alarm low limit should be added to the process tag type.
and the
Add parameters/signals to the process tag type
Modifying the corresponding process tag type
Low limits should be

included in the PTT
The procedure initially corresponds

Trainingsunterlage SP-PCS7CWS 5 - 23
to the creation of the process tag type, but then
continues as follows:
Updating the existing process tags SIMATIC PCS 7 AS Engineering
1 2 3
12. If there are no process tags of the modified process tag type in the project, click
"Finish".
The assistant is closed.
13. Otherwise: Click on "Next".
The dialog page 3(3), "Do you want to complete the process tag type and apply the
changes to existing process tags?" opens.
14. Click "Finish".
You receive the log of changes.
15. Click "Exit".
The changes to the process tag type and process tags are complete.
The assistant is closed.
 Please note, that the relation between process tag types and process tags is
specified via the process tag connectors and I/O connectors for messages.
Updating process tags means to update number and names of these connectors.
Changes made in the chart of the process tag type (e.g. interconnections, new
blocks, deleted blocks, etc…) will be ignored when you update the process tags.
Explicit update of process tags

If you modify the process tag type, all process tags in the project are automatically
modified accordingly. If, for example, not all of the project’s process tags can be
reached during an automatic update, inconsistencies occur between the process tag
type and the process tags. You must then perform the update explicitly.
Select the menu command Options > Process Tags > Update... to update all
process tags to the modified type.

Update import file to match the new process tag type

After modifying the process tag type, the import file must be modified as well.
The additional signals/parameters must be added to the import file.
For this, the buttons and/or can be used in an already existing import file.
This saves
Update import fileyou
to from creating
match thea new
new import file andtag
process having to copy information from the
type
old to the new import file.
Checked if the column

headers are OK
Change the header to match the ‘Process tag connector’

in the process tag type and specify the parameter values

After this, the process tags can be imported again, overwriting the signals/parameters
with the information in the new version of the import file.
Designate existing charts as process tags

5.2.9 Designate existing charts as process tags
Create PTT Import (*)
(*) Import file:
Only specify the existing

hierarchy folders and chart names

Use case 1
You have created a CFC chart, for example, you have configured a motor control, and
manually copied this chart several times. The copies have been modified or adapted
according to the different requirements.
Use case 2
A CFC chart was a process tag. You have cleared the assignment to the process tag
type for this CFC chart via its object properties. To do this, you have selected the menu
command Object Properties and selected the chart in the “Process tag type” tab and
clicked “Clear”.
In both use cases you want to use the IEA functions in the future and create additional
process tags via import. The charts created previously are still to be used and
designated as process tags, too.
5.2.10 Export of existing process tags
Once you have created process tags by importing or copying in SIMATIC Manager and,
for example, edited various parameter and signal values in the testing and
commissioning phase, export current data in the same way they were imported.
You can use the import/export assistant to export process tag data. All accessible
projects in the multiproject are taken into account.
If you have selected a higher-level hierarchy folder or the project node containing
process tags at lower levels, all the lower-level process tags are selected for export and
the data are exported.
Each process tag type is assigned an export file, each process tag of the process tag
type is assigned a row in the corresponding export file.
The structure of the export file corresponds to that of the import file.
 You must assign a valid import file to the process tag type. The structure of the
individual column groups in the import file is also applied to the export file.
Procedure
16. Select the hierarchy folder of the required model/process tag and select the menu
command
Options > Models > Export… or
Options > Process Tags > Export… to perform the export.
The models/process tags will now be found and listed.
17. On the next dialog page, check whether the correct export files are assigned for the
models/process tags shown.
If you have selected a higher-level hierarchy folder containing process tags at lower
levels, you will see the hierarchy paths of all lower-level process tags here. The
export is executed for all the process tags in this list.
Process tags that you do not want to export must be removed from this list.

If the path name contains the prefix "???", the IEA cannot open or create the export
file in this path, for example, because a drive that does not exist was specified. In
this case, click on "Other file..." to locate a suitable path for the export file.
 Use backup copies to avoid the overwriting of assigned import / export files.
18. On the final dialog page, select the log file and activate or deactivate the filter to
only log error messages and the “Ready” message.
Exit the export by clicking "Finish".
Result
The selected export files are completely overwritten or, if they do not yet exist, created
during export.
 Use backup copies to avoid the overwriting of assigned import / export files in an
earlier stage.
5.2.11 Changing process tag types without automatic update
Existing process tags are updated automatically when changes in the process tag type
are made.
But there changes to the process tag type, where the process tags are no longer
updated automatically, e.g.:
 the adding of new block to the process tag type,
 realization of new interconnections or changes to the parameters.
Please note that the changes described here have no effect on the import file. No new
parameters or signals of the import file are added.
Despite these restrictions, there is an approach to replace the corresponding process
tags.
Prerequisites
 There are process tags in the project and the changed process tag type is in the
master data library.
 There is an import file containing the current values from the process tags in the
project.
 Use the function "Export…" to create a new import file representing the current status
of the corresponding process tags at the declared process tag connectors.

Changing process tag types without automatic
update
Procedure
Existing process tag = existing I/O points for parameters, signals and messages
type
The export file
• get the structure from the import file,
PT
PT • but does contain current values of the
PT process tags at the I/O points
Import file
PT • Duplicate the rows for

Modification PT the process tags
PT
Export file
• Each first row per
Export process tag with
ImportMode = „delete“
PT delete
PT
PT delete modified
PT Import file
PT delete
PT
Changes:
• New blocks Import
• new interconnections
• Changed parameters
modified process tags
Training Documentation SP-PCS7CWS 5 - 27 SITRAIN - Siemens AG © 2015
19. Ensure that the "ImportMode" column (general column group) exists in the import
file.
20. Duplicate each row for the process tags of your import file.
21. Now, in the first of each of the two identical rows you write a "delete" in the "Import
Mode" column.
22. Perform an import of the process tags on base of the modified process tag type
using the import file with doubled number of rows.
 ATTENTION!
During the import, first all rows with the keyword "delete" are executed and the
corresponding objects are deleted. After, the new objects are created. Existing
instance-specific interconnections to these charts are lost.
Result
After successful completion of the import procedure all the process tags are recreated at
exactly the same point in the plant hierarchy and the above-described changes are
available.

5.3 Tasks and checkpoints
Task: Adopt existing charts as process tags
Goal
The valves in the material tanks are already programmed as CFC charts in the plant
view. The goal of this exercise is to create a process tag type for the valves in the rest of
the plant and adopt the existing CFC charts as process tags.
Task: Export process tags and modify process tag type
Goal
The process tag type for the valve should be extended with the static monitoring time
without losing information in the existing process tags. In this task, you will first make an
export of the existing process tags, based on the already assigned import file. Then, you
can add the required signal/parameter to the process tag type and modify the import file
accordingly.
Checkpoint
Checkpoint

 What is the “Update” function of the
process tag type used for?

5.4 New type conception: Control Module Types

5.4.1 Comparison to process tag types
Overview
Control Module
In PCSTypes (CMT)
7, there are process tags and control modules, and their associated types.
ComparisonA process
to Process
tag type Tag Types
or a control module type is a CFC configured for a specific process
control function for the basic automation of a process engineering plant.
• CMTs can be created from standard process tag types.

• Changes to the CMT of which instances already exist are possible
without having to delete the instance.
• Selective synchronization of CMT > CM
User can select what will be synchronized.
• Variants of “types” can be created
Process tags
The following properties are available for using process tags and their types:
When an instance is created and configured from a process tag type, instance-specific
changes are lost when the process tags are imported again with the Import/Export
Assistant.
Multiple process tag types are required for the same technological function, such as
"Measurement", when different input blocks are used, for example. It is not possible to
create different variations of process tags from a single process tag type.
Control modules
When control modules and control module types are used, the above-mentioned
properties do not apply. This is why a control module has the following advantages in
comparison to a process tag:
Instance-specific changes to the instance, the control module, are not lost during
synchronization of type and instance.
It is possible to create different instances from a control module type. The control
module type can also include optional blocks. When the instances are created, you can
determine which of these optional blocks should be inserted into each instance.

New type conception: Control Module Types –
Process Tag Types versus Control Module Types
Process Tag Types versus Control Module Types
Process Tag Types (PTT) Control Module Types (CMT)

• Subsequent changes on a type Delete • Subsequent changes on a type >
process tags (PT) Synchronize changes without
• Loss of engineered data and connections deleting the control modules (CM)
• No loss of data or connections
• Variants: 1Type > different views
PTT „Motor“ CMT „Motor“

Modified Modified
PTT „Motor“ CMT „Motor“
PT „M316“ CM „M316“
new PT
„Motor“
Process Tag Types versus Control Module Types –
Features of PT/PTT and CM/CMT
The following table compares the features of PT/PTT and CM/CMT.
Training Documentation SP-PCS7CWS

Functionality PT/PTT5 - 29 SITRAIN
CM/CMT - Siemens AG © 2015
Change tracking Only with special tools Yes, with the comparison function
of the automation interface.
Variant support No, because a PTT is needed for each Yes, via CMT with selectable
variant variants (options)
System-supported IEA (Import/Export Assistant) With COMOS or Advanced

instantiation Engineering
Enhanced functions Yes, by adapting the PTT and Yes, very comfortable due to the
instantiating with the IEA extended functionality of the CMT
Caution: The export file must be and comparison with the
adapted to the new function. instances.
Specific changes to instances are

lost if not read back.
Type configuration Easy, by placing and interconnecting Somewhat more extensive, as the
the required blocks. technological I/Os have to be also
defined.
 You can drag several interconnections to one input with control module types, which
is not possible with a CFC. The prerequisite for this is that the "Optional" attribute is
activated in the control module type to be configured as interconnection target.

Several ways to create a Control Module Type

Several ways to create a Control Module Type
Only in the master data library
1 Directly from chart 2 From a process tag type 3 As new and empty object
(template from library)
Activate Technological I/Os Create CMT from PTT

Add/edit the
and edit these and add/edit the
Technological I/Os
Technological I/Os
Control Module Types (CMT)

Creating
5.4.2 from existing
Creating Process
Control Module Tagfrom
Types Types
standard Process Tag Types
You can create control module types (CMT) from standard process tag types provided
that the master data library contains the hierarchy folder Process tag types.
Training Documentation SP-PCS7CWS SITRAIN - Siemens AG © 2015
23. Select the hierarchy folder 5Process
- 32
tag types in the plant view of the master data
library and select in the context menu:
Control modules > Create control module from process tag type…
24. A dialog opens which shows all available process tag types in the currently selected
master data library. Select the desired process tag types using the checkboxes.
25. Click the Create button to generate the associated CMT from the selected process
tag types. The process tag types remain unchanged. If the process tag types are
also located in the folder Process tag types, they are still there after the CMT has
been created.
26. Click the Select... button to open any other library for selecting process tag types.
Select process tag types in another library
Select process tag

4 type(s) from the
selected library...

Result
Result
All signals and parameters of the

process tag type have become
signals and parameters of the
control module type
 The new CMT and the PTT which was used as starting point cannot have the same
name. The system adds automatically a number in brackets.
Control modules are color-coded in the CFC Editor. The following objects are available
in the technological I/Os:

 Control modules: Block or block group

 Parameter: Block input or output with preconfigured value or an
interconnection/multiple interconnections, attributes such as unit or value can be
configured
 Signal: Interconnected input value with process value and status (no multiple
interconnection possible, parameter attributes are not present)
 Messages: Messages that are associated with the available CM
 Command and status are required to connect to sequencers.
 In the CFC Editor, elements that belong to the definition of the control module type,
such as blocks and connections, are highlighted in color. You may customize the
colors used with the menu command:
Options > Settings > Colors…
In the following dialog box select the object "Blocks and I/Os of the control module
type" under "Objects".
Attributes
The "Attributes" area shows the available attributes of an object (name, option, value,
unit, etc.) and assigned CM or linked interconnections.
Each object has different attributes. While the name of the connection is being assigned
Control Module Typesfunction
or the "Optional" (CMT)is being set in a block or block group, a process value and/or a
unit can be preset at a lower-level parameter.
Create a new control module type
5.4.3 Create a new control module type starting from an empty template
The green logic functions are

simple standard functions in
COMOS, already predefined
in PCS 7 for data exchange.
You can create a CMT as an empty template in the master data library.
To do so, select the hierarchy folder Process tag types in the plant view and select in
the context menu:
Insert new object > Control module type
Exchange of standard functions in COMOS

You can use the simple standard functions in COMOS, for example, to configure an
interlock logic for control modules. Following data exchange with COMOS, these

standard functions are mapped to control modules. The AND, OR, XOR and NOT
standard functions are predefined in PCS 7. They are available on the "Templates" tab
of the template catalog, provided a control module has been created.
You may define other standard functions. This is done by creating a control module that
has an interface which exactly corresponds to the definition in COMOS. The names of
the control modules and control variables and their data type must match precisely. The
Control check box
Module for the(CMT)
Types "Standard function" attribute must be selected. The PCS 7-specific
implementation of the standard function is defined in the corresponding CFC.
Technological I/Os
5.5 Editing the technological I/Os
Show the
technological I/Os
Interface Properties of the

objects selected object
To open the technological I/Os, click the button or choose the menu command:
View > Technological I/Os
The left hand side shows all available objects of the control module type, whereas the
right hand side shows the properties of the selected object.


PossiblePossible
5.5.1 objects objects
Control module (Chart)
Command (input from equipment module)
Parameter of the command
Control module (Block)
Message of the lower-level control module
Parameter of the lower-level control module
Sub parameter of a STRUCT parameter
Signal of the lower-level control module
Message of the control module
Parameter of the control module
Signal of the control module
Status (output to equipment module)
Parameter of the status

Basically, there are three different objects in the technological I/Os:
 Control module
 Control tag
 Message
However, they can exist at different levels for structuring purposes.
5.5.2 Editing the technological I/Os with a shortcut menu

You can create, copy, and delete these objects with a shortcut menu. To create such an
Editing the technological I/Osmenu with a right-click on the higher-level control module and
object, open the shortcut
then select a new object.
Manually add Control

modules, Control tags
or messages, using
the right mouse
button

5.5.3 Editing the technological I/Os using drag & drop
You can also insert a block from the CFC Editor to the hierarchy of the control module
with drag-and-drop. This block will automatically be given the name of the block and
assigned to it.
The attributes and assignments are located in the right area. The attributes that are
Control Module
displayed depend Types (CMT)
on whether a control module, a control tag or a message is selected.
You can fill the text boxes, depending
Editing the technological I/Os using on the attribute,
drag & dropwith a free text, with drag-and-
drop from the CFC Editor or from a drop-down menu. You cannot edit grayed out boxes.
Drag & drop the

desired block I/O into
the technological I/Os
and change it's name
afterwards
5.5.4 Data types for control variables and generic data
A control variable is either of the "Parameter" or "Signal" variable type, depending on its
assigned block I/O.
Only the REAL, BOOL, INT and DINT data types are valid for the "Signal" variable type
because these define an I/O channel request.
However, the data type at the assigned driver block may also be BYTE or WORD. In
such a case, the data type is mapped as follows:
 BYTE at the driver block is equivalent to BOOL at the control variable
 WORD at the driver block is equivalent to REAL at the control variable
Along with the standard data types, standard functions may be assigned generic data
types ANY_BIT, ANY_NUM, ANY_REAL or ANY_INT. These are displayed in the
technological editor by the "Data type" attribute of control variables. The following rules
apply if a control variable with a generic data type is assigned to a block I/O in the CFC:
 ANY_BIT is assigned BOOL, BYTE, WORD, or DWORD.
 ANY_NUM is assigned REAL, INT or DINT.
 ANY_REAL is assigned REAL.
 ANY_INT is assigned INT or DINT.
Only block I/Os that fulfill the rules described above can be assigned. The user has to
perform the assignment manually.


Attributes for higher-level control module
5.5.5 Attributes
Attributes for higher-level control module
Attribute Description of attribute values

Assigned chart Cannot be edited
Name Can be edited, is forwarded to associated objects.
Gets the name of the assigned chart as default value.
Comment Can be edited, is forwarded to associated objects.
Author
Course ST-PCS7ASE
Can be edited, is not7 -forwarded
12
to associated objects.
Function identifier Can be edited, is forwarded to associated objects.
Location identifier Can be edited, is forwarded to the DOCPRO footer "Code field according to
location" of the assigned chart.
Sampling time Can be edited. All blocks of the assigned chart are installed in the OB with
the most suitable sampling time. The next higher value will be entered in
case of an invalid entry.
The runtime editor is adapted accordingly.
Standard function Can be edited, is used to identify a control module as a standard function.
Standard function name Displays the name of the standard function.
Cannot be edited at the type of the control module.
When the "Standard function" attribute is enabled, the value of the "Name"
attribute is applied automatically.
Can be edited at the instance.
Control module type Cannot be edited, is not forwarded.

Attributes for lower-level control module
Attributes for lower-level control module

Assigned block Cannot be edited
Name Can be edited, is forwarded to associated objects.
Gets the default value "Control module".
Comment Can be edited, is forwarded to associated objects.
Operating icon Can be edited, is forwarded to the block icon (for WinCC) of a block
according to the assignment.
Optional Select the check box for optional activation of this control module.
Author Can be edited, is not forwarded to associated objects.
Control module type Cannot be edited, displays the name of the control.

Attributes for parameters and signals
Attributes for parameters and signals

Assigned I/O cannot be edited
Interconnection to can be edited, the interconnection is displayed here
Name can be edited, is not transmitted
Receives the default value "Control tag".
Comment Can be edited, is not forwarded.
Signal Can be edited. Right-click the text field to open the symbol table of the CFC
using the menu command "New Signal Interconnection". The value is
forwarded to the "Interconnection" property of the assigned I/O.
Value Can be edited, is forwarded to the "Value" property of the assigned I/O.
Negation Select the check box to negate the control variable. The box can only be
selected if there is an interconnection.
Enumeration Can be edited, is forwarded to the "Enumeration" property of the assigned
I/O. The attribute s7_Enum must be configured.
Unit Can be edited, is forwarded to the "Unit" property of the assigned I/O. The
attribute s7_unit must be configured.
Operation identifier Can be edited, is forwarded to the "Identifier" property of the assigned I/O.
The attribute s7_shortcut must be configured
IO type Selecting via drop-down menu
Must match IO type of the assigned I/O.
Data type Selecting via drop-down menu
Must match data type of the assigned I/O.
Variable type "Signal" or "Parameter" (selection via drop-down menu).
Forwarded to the assigned I/O.
Control module type Cannot be edited

Control
SIMATIC PCSModule Types
(CMT)
7 AS Engineering
Attributes for messages
Attributes for messages
Specify the message

identifier

Assigned message cannot be edited
Name can be edited, is not transmitted to associated objects
Receives the default value "Message"
Message class cannot be edited, this value is inherited from the property "Message class" of the
assigned single message.
Priority can be edited, only numbers possible The value "0" is entered in case of an
invalid entry. Is transmitted to the property "Priority" of the assigned single
message.
Message identifier must be entered manually
If an invalid message identifier (e.g. SIG1) is entered, the attributes message
class, event and origin are automatically applied if the assigned block has a
message response.
Event cannot be edited, is inherited from the property "Event" of the assigned single
message
Information Is transmitted to the property "Infotext" of the assigned single message.
Origin Is transmitted to the property "Origin" of the assigned single message.
 It may not be possible to edit some attributes, because of dependencies to other

attributes.
 You can only fill the text boxes of the "Assignment" column with drag-and-drop of
connections or blocks from the CFC Editor or with a right-click on the text box and by
selecting a shortcut menu.
 See [302] PCS 7 V8.1 CFC for SIMATIC S7 - Function Manual - 08_2014 chapter
9.11.5, for more details on the other objects in the control module types.

Assign control module name to chart name
Example: Assign control module name to chart name
Required if you want

Advanced ES to
rename your Control
Modules after copying
Course ST-PCS7ASE
This is a necessary step for specifying
7 - 13
the CFC chart name from Advanced ES. The
latter can only write information to the Attribute values of the attributes of the top level
control module, but it cannot write information directly to the CFC chart. By making the
above shown assignment, the control module name coming from Advanced ES is
forwarded to the name of the CFC chart.
Assigning CM information to block instances
Example: Assign CM information to block instances
Result: Control module

comment, set by AdvES, will
be forwarded to the
comment of the MotL block
Course ST-PCS7ASE
As mentioned above, Advanced ES can write information to the
7 - 17
Comment attribute of
the top level control module, called MotorLean in the picture above. By dragging the

Motor instance onto the Assignment column, the control module comment is
forwarded to the Motor instance comment.
In this way, this comment is included in the alarms in the OS and with the new V8 APL
block icons this comment will be used as tooltip text of the block icon.
5.6 Task
Task: Manual creation of CMT for the reactor inlet valves
Goal
Create a Control Module Type from the existing chart V311. You replace the existing
process tags V311…V341 by the corresponding instances (CMs) of the CMT.

Synchronizing CMs and CMTs –

5.7 Synchronizing
Synchronization meansControl
… Module Types
5.7.1 Synchronization means …
1. Create type (CMT) 2. Derive instances (CMs) 3. Modify instances (CMs)

4. Modify CMT
5. Synchronization CMT > CMs
6. In case of collision >
The user can decide:
What is to be used?
Type (Motor) Instance (M316) Instance (M316)

M M M
FBKRun FBKRun FBKRun
Intlock OUT Intlock OUT Intlock OUT

2 input 2 input 2 input
CSF CSF CSF

&
>1 >1 >1
Intlock Intlock Intlock

2 input 2 input 2 input
CMs can be synchronized with5their

Training Documentation SP-PCS7CWS - 46
CMTs. This means that blocks, interconnections,
connectors, and messages can be added or removed in an existing and already
instantiated CMT. These changes can be passed on to the existing CM.
Even when one or more instances (CM) of a CMT already exist in the project, changes
can be still made to the CMT and transmitted to the existing instances.
A lot of information is synchronized – but not all.
Excluded from synchronization:

 Signals/parameters with attribute "S7_m_c" = true ( OS)
 Signals/parameters with attribute "Block contact" = true ( SFC)
 Connections between signal and HW-channel
 Signals/parameters which are part of Technological I/O
 Parameters with cross-process tag connections
 Connections to "instance specific" blocks in the instance
 See [1036] Description Topic 99861834 Synchronizing control module types -

08_2014, for more details on CM synchronization.

Synchronization of CMT with optional functions –
1 type > n variants
Synchronization of CMT with optional functions: 1 type > n variants
1. Create CMT: Functions which shall not be used in each instance get the attribute “Optional”
2. Instantiate: Select Optional Functions to create Variants
3. Changes in Type: Synchronize in all variants
Instance M316 (default) Instance Variante 1 (M326)

M M
FBKRun FBKRun
OUT Permit OUT
Type (Motor)
M
FBKRun x1 x1
Permit OUT
Instance Variante 2 (M336) Instance Variante 3 (M346)
M M
x1 FBKRun FBKRun
Intlock
OUT Permit OUT
Optional
Intlock x1 Intlock x1
Synchronization of CMT with alternative functions –

1 type – n alternatives
Synchronization of CMT with alternative functions: 1 type > n alternatives
Note: In this use case only one optional function can be selected
Instanz M316 (default) Instanz Variante 1 (M326)

M M
FBKRun FBKRun
Intlock
Intlock Intlock
2 input
OUT OUT
Typ (Motor)
M
FBKRun
Instanz Variante 2 (M336) Instanz Variante 3 (M346)

Intlock
Intlock M M
2 input FBKRun FBKRun
OUT
Intlock
Intlock Intlock
4 input
OUT OUT
Intlock Intlock
8 input 4 input
Intlock
8 input
Optional

Synchronization
5.7.2 Procedure after modifying the CMT
1
This dialog is part of the
automation interface
Synchronize plant types

2
A: Existing data in the project

B: Data in the master data library
5
Show only differences Special button only for
synchronization of
Open table view Refresh the view plant types
Scroll through the differences

27. Select the project in which the CMs should be synchronized with the CMTs
28. Open the context menu and click "Plant Types > Synchronize…"
29. Select the CMTs to be synchronized.
 Filter settings, such as deselecting instances, are discarded after closing the
automation interfaces.
30. Click on the button "Synchronize" to open a Data transfer dialog window.
31. Select the instances (CMs) to be synchronized.
32. Start the synchronization.

Synchronization via the automation interface

The synchronizing function in PCS 7 is done via the automation interface and is carried
out for a project. All instances and observed changes are displayed in the automation
interface. The user can decide selectively at the instance level about which instances
are to be synchronized.
For example, modules that have been added to an instance are ignored during the
synchronization process. On the other hand, blocks or interconnections that have been
added in the type are adopted in the instances when synchronizing.
The comparison dialogue shows all the folders, where the previously selected CMTs
were created as an instance. Changes made to terminals that are not technical
connections, are displayed at the respective instance.
 If two blocks are connected to each other in the Type and the destination connection
is defined as "Technical connection", the change is kept when synchronizing when
the connection in the instance is deleted.
If the two connections are not defined as "Technological I/Os" in the Type and the
connection is deleted in the instance, the original state is restored after
synchronization.
Comparing the run sequence

Comparing the run sequence
Training Documentation SP-PCS7CWS

Start in the 5plant
the synchronization SITRAIN
- 52 view of the project from the - Siemens
shortcut menuAG © 2015
"Technological Types > Synchronize..." and select the desired CMT:

33. In the filter window of the automation interface activate the check box "with run
sequence ".
34. In the Data transfer window select the table view, and show only the differences.
35. Right-click with your mouse on a folder in the table view and select the command
"Display Node Contents". This makes all relative changes visible.
36. Using the context menu of an insertion position you can open the CM and CMT in
parallel and edit the insertion position manually.

Synchronization
5.8 Summarybehavior
for the synchronization behavior
The synchronization behavior depends on the following criteria:
• Type of change (parameter value,

interconnection,...)
• Place of change (CMT or CM)
• Attributes of the changed parameters: – Green: parameters are in the technological I/Os
– S7_m_c: OS relevant parameters
– Miscellaneous
Installation pointer (run sequence ), for new objects (function blocks and/or function charts):
• When synchronizing to the CM, if the newly inserted objects in CMT are placed
in the main sequence group, they are inserted directly behind the same
predecessor blocks that are also available in the CMT.
• The installation pointer in the CM is ignored and remains unchanged.
Deviations from this rule are possible.

5.8.1 Changing objects in the technological I/Os
Change in CMT Change in CM

Add block/chart_in_chart to the technological I/Os
Result after Object is added in CM Object is kept in CM
synchronization
Remark - When synchronizing, interconnections
from a new object to internal objects are
handled like external interconnections
Remove block/chart_in_chart from the technological I/Os
Result after Object is removed from CM Object is available in CMT => Object will
synchronization be recreated in CM
Otherwise: Object is removed
Enable ‘Optional’ attribute to an existing object in the technological I/Os
Result after Object remains visible in CM and is -
synchronization activated in ‘Variants…’ dialog
Remark - Cannot be carried out in CM, because
Dialog is not available
In CMT, drag and drop an object into the technological Ios and enable ‘Optional’ attribute
Result after Object remains visible in CM and is not -
synchronization activated in ‘Variants…’ dialog
If optional block is activated ‘Variants…’
dialog => Object is duplicated in CM, but it
is not installed correctly in the process
dialog is not available
Disable ‘Optional’ attribute from an object in technological connections
Result after If not already activated, the object will be -
synchronization visible in the CM
Object is not available any more in
‘Variants…’ dialog
Dialog is not available
Add signal/parameter to the technological I/Os
Result after Signal/parameter will be available in If a signal/parameter has been applied
synchronization technological I/Os of the CM directly in CM level => setting will be
taken over from CMT
If a signal/parameter was added in
submodule => CM setting is kept
Remove signal/parameter from the technological I/Os
Result after Signal/parameter will be removed from If signal/parameter exists in CMT’s
synchronization technological I/Os technological I/Os => it will be recreated
in CM
Otherwise: signal/parameter is removed
from Tech.I/O

5.8.2 Changing values or interconnections

Add external interconnection to signal/parameter
Result after - Interconnection does not change
synchronization
Remark Cannot be added in CMT -
Change the value of an input parameter
…in technological Value is kept in CM Value is kept in CM
IOs
….Attribute Value is kept in CM Value is kept in CM
‘S7_m_c := true’
….other Value is transferred from CMT to CM Value is transferred from CMT to CM
Block comment and block group (smart alarm hiding)
Result after Text is always kept in CM Text is always kept in CM
synchronization
Remark - -
Changing an ‘Indentifier’
Result after If the “Identifier" field is empty in CMT, the If the “Identifier" field is empty in CMT, the
synchronization entry in the CM is always kept entry in the CM is always kept
Remark - -
Change Text 0 or Text 1
Result after If the "Text 0/1" field is empty in CMT, the If the "Text 0/1" field is empty in CMT, the
synchronization entry in the CM is always kept entry in the CM is always kept
Remark - -

5.8.3 Changing properties and attributes

Changing units of measure (‘PCS7 Library V7.1 style)
…in technological No change in CM; No change in CM;
IOs The unit from the CMT is not accepted The unit is not changed
….Attribute No change in CM; No change in CM;
‘S7_m_c := true’ The unit from the CMT is not accepted The unit is not changed
….other The unit is removed in the CM The unit is removed in the CM
‘Invisible’ attribute in the instance properties – tab ‘Block I/Os’
Result after Setting is transferred from CMT to CM Setting is transferred from CMT to CM ( =
synchronization RESET )
Change ‘OCM possible’ in the instance properties
Result after Setting is not transferred from CMT to CM Setting is kept in CM
synchronization
Change ‘Create block icon’
synchronization
Remark - -
Change ‘Operator authorization level’
synchronization
Remark - -
Change message class
synchronization
Remark - -

5.9 Control module variants

5.9.1 Optional blocks
rol module variants
onal blocks
Principle - Principle
The following figure shows the creation of a control module type with optional blocks
and the creation of possible instances.
-PCS7CWS 3 - 63 Siem

Control module variants
Optional blocks in the control module type
Optional blocks in the control module type
Course ST-PCS7ASE
Proceed as follows to make an7instance
- 82
optional in a control module type:
37. Drag & drop the instance from the CFC work area to the technological I/Os.
A lower level control module is created.
38. Rename this control module.
39. Select the control module and activate the check box of the Optional attribute.
Blocks configured in this way are not used by default in the control module instance.
VariantsVariants
5.9.2 of a manually copied
of a manually control
copied module
control module

Blocks identified as "optional" are not available in the CM after creation. If you want to
use optional blocks in the CM, you can activate them specifically for the instance.
To do so, proceed as follows:
40. Open the configuration area for the Technological I/Os using the icon or the context
menu:
View > Technological I/Os
41. Here you can open the Variants dialog in the context menu of the topmost folder.
The dialog box shows all optional blocks available in the CM.
42. Use the checkboxes to select the optional blocks required for the CM and enable
them with "OK".
 PCS 7 automatically prevents any inadmissible double interconnection of an input. If

several optional blocks are programmed to connect to one input, and if more than one
of these optional blocks is selected as variant, all blocks will be displayed in the CM,
but only one of them is interconnected.

5.9.3 Optional blocks connected to the same input
Principle
In the following example, there are two optional interlock blocks (one with 2 inputs and
one with 4 inputs). Each interlock block has an Out output parameter which should be
interconnected
Optional blocks connected to the Intlock
to the input parameter
same inputof the MotL block.
It is obvious that in the resulting control module instance only one of the two interlock
blocks can be activated.
Merely schematic
representation
Instance with:
Interlock02: visible
Interlock04: invisible
Instance with:
Interlock02: invisible
Interlock04: visible
Control module type with 2 optional blocks:

Interlock02: Optional = True
Interlock04: Optional = True
Motor: Optional = False
Course ST-PCS7ASE
In the figure above, this idea is7schematically
- 85
shown. Of course, it is not possible to
configure this function in this way, but proceed as follows:
Prerequisite
A control module type, consisting of:
An Intlk02 instance, an Intlk04 instance and a MotL instance.
Procedure
43. Drag & drop the two Interlock blocks to the technological I/Os in order to create two
lower-level control modules.
44. Rename both control modules to Interlock02, resp. Interlock04.
45. Drag & drop the Out output parameter of both Interlock blocks onto the respective
control module.
Two lower level control tags are created.
46. Rename these control tags to Out.
47. Drag & drop the Intlock input parameters to the technological I/Os.
A new control tag is created.

48. Rename this control tag to Intlock.

In the properties of this control tag, the interconnection to the Out parameter of the
Interlock02 instance is shown.
49. Drag & drop the Intlock control tag onto the Out control tag of the Interlock04
Optional blocks – Example:
control module. Technological I/Os
Notice the second interconnection in the properties of the Intlock control tag.
This second
interconnection is
created by dragging
'Intlock' onto 'Out'

Optional blocks – Example: Technological I/Os
Course ST-PCS7ASE
50. Activate the Optional checkbox
7 - 86
for both control modules. SITRAIN - Siemens AG © 2014
After being copied,

these instances
will be invisible in
the CM, but can be
set to visible by
chosing a variant

Variant selection
After copying the chart and opening this copy, none of the Interlock instances will be
Optional blocks – Example:
visible. Right click the top-level
Variant control module and select Variants. In the following
selection
window, you select which of the two interlock instances should be used.
Default after
opening the
control module
instance

5.10 Tasks and checkpoint
Task: Synchronization of modified CMT
Goal
The reactor inlet valves of R310…R340 are manually modified from chart to chart.
Despite this, the control module type for these valves is to be changed and
synchronized to these charts.
Checkpoint
Checkpoint

 What is the advantage of using
control module types instead of
process tag types?

Content 6
6 Technological Engineering using the APL ............................................................ 2
6.2 Motivation and positioning for the Advanced Process Library ............................................... 2
6.2.1 Why has Siemens started to develop the Advanced Process Library? ................................. 2
6.2.2 Libraries available with introduction of APL in SIMATIC PCS 7 ............................................ 4
6.3 General engineering functions using the APL ....................................................................... 8
6.3.1 Structures and Signal Status (ST) ......................................................................................... 8
6.3.2 Feature Parameter ............................................................................................................... 11
6.3.3 Units in the APL ................................................................................................................... 12
6.3.4 Design of APL Block Icons .................................................................................................. 13
6.3.5 Design of APL Faceplates ................................................................................................... 15
6.4 Operating modes of APL ..................................................................................................... 16
6.4.1 Overview of the operating modes of APL ............................................................................ 16
6.4.2 Status diagram for the operating modes of APL .................................................................. 17
6.4.3 Operating mode "Manual" and "Automatic" ......................................................................... 19
6.4.4 Operating mode "Local" ....................................................................................................... 20
6.4.5 Simulating, Forcing, Tracking .............................................................................................. 21
6.4.6 Priorities of operating modes and control functions............................................................. 21
6.5 APL Templates .................................................................................................................... 22
6.5.1 Monitoring the feedbacks..................................................................................................... 23
6.5.2 Error handling ...................................................................................................................... 24
6.6 Task and checkpoint ............................................................................................................ 25
6.7 Configuration of dose functions using APL .......................................................................... 26
6.8 DoseL block of the APL in brief ........................................................................................... 28
6.8.1 Dosing states and commands ............................................................................................. 29
6.8.2 Dosing types "flow" and "weight" ......................................................................................... 31
6.8.3 Functional principle of dosing type "Weight" ....................................................................... 32
6.8.4 Functional principle of dosing type "Flow" ........................................................................... 33
6.8.5 Operation of dose block ....................................................................................................... 34
6.8.6 Dribbling ............................................................................................................................... 36
6.8.7 Post dosing .......................................................................................................................... 38
6.8.8 Creep flow ............................................................................................................................ 39
6.9 Collaboration of DoseL and Analog valve / Flow controller ................................................. 40
6.9.1 Application of PID controllers for controlling the dose flow ................................................. 40
6.9.2 Direct application of analog valves for setting the dose flow ............................................... 40
6.10 Task and Checkpoint ........................................................................................................... 43
SIMATIC PCS 7 - Technological Engineering using the APL

6 Technological Engineering using the APL

Learning
6.1 targets targets
Learning
The participant learns about…

 Basic conception and positioning of the APL
 commonalities and differences of the APL in
comparison to former PCS 7 Standard library
 Basic functions of the APL
 essential requirements on dose functions
The participant is able to …

 Operate block icons and faceplates on the OS
 Configure important technological functions
using APL blocks
 Use the DoseL block of the APL for the
configuration of 2-step or 1-step dosing
Motivation und Positionierung – 7Warum

Training Documentation SP-PCS7CWS -2
hat Siemens SITRAIN - Siemens AG © 2015
6.2
die PCSMotivation
7 Advanced and positioning
Process Libraryforentwickelt?
the Advanced Process Library
6.2.1 Why has Siemens started to develop the Advanced Process Library?
• The PCS 7 Library has getting on in years and is no longer „state of the art“ (Release with
PCS 7 V3.0).
• New functions (e.g. Feature parameter) were only in addition possible
• Realization of maintenance functionalities led to the necessity of structure changes
• New customer requirements to functions and structure
• Resource consumption and performance does not meet the requirements any more
• Expansion of the standard functionalities are necessarily to minimized custom-designed
expansions of the library
Training documentation SP-PCS7CWS 3-3 SITRAIN - Siemens AG © 2015

Demands on Advanced Process Library

 The PCS 7 Advanced Process Library (APL) is the standard library in PCS 7.
 APL is delivered on the PCS 7 DVD and available “out of the box”.
 The licensing works via the AS and OS process object. There is no own or special
license required.
 The APL contains a complete portfolio of function blocks, block icons and faceplates.
 The focus of the library is on:
 Efficient engineering of the technical task
 Fast commissioning of the application
 Optimal operation and control
 Due to status as standard maintained and innovated, the APL reduces the life cycle
cost for the customer.
Base for the development of Advanced Process
Library
Base for the development of Advanced Process Library
• Perpetuation of approved functions of the PCS 7 Library V7.0
• Analyze of other proven PCS 7 libraries e.g. Standard Chemical library
(used at BASF)
Interviews/Information and workshops with customer e.g.:

• Bayer
• Wacker (Germany)
• DuPont (USA)
• Air Products (USA)
• Shell (Germany

Libraries available with introduction of APL in
SIMATIC
6.2.2 PCS 7 available with introduction of APL in SIMATIC PCS 7
Libraries
PCS 7 Basic Library V8.1
Diagnostic Drivers
e.g. MOD_1
PCS 7 Advanced
PCS 7 Library V7.1 Process Library V8.1
Only correct
versions are
able to
cooperate!
Technological functions Technological functions
ChnBlocks for PCS 7 V8 Channel Drivers Version 7
Operation and Control Operation and Control
The PCS 7 Advanced Process Library (APL) is a block library for PCS 7 being
Training documentation introduced
in PCS 7 Version 7.1.
SP-PCS7CWS 3 - 7It principally contains all blocks and- Siemens
SITRAIN functions
AG ©of the
2015
former PCS 7 Standard Library. It also offers additional functions in existing blocks as
well as completely new blocks.
The PCS 7 Standard Library, however, is still available. It is also possible to use both
libraries at the same time (i.e. use blocks from both libraries in a CFC).
Because the PCS 7 Standard Library and the PCS 7 APL can be installed either
separately or together, shared blocks are stored in the PCS 7 Basic Library. This
consists largely of driver blocks.
Versioning
The former PCS 7 Standard Library was still updated for a defined time by reasons of
maintenance and compatibility.
The former PCS 7 Library is no longer installed automatically via the frame setup with
the release of PCS 7 V8.0. It is provided in the directory "Additional Products" on the
PCS 7 DVD and can be installed manually by the user if required.
With the release of PCS 7 V8.1, the former PCS 7 Library is not available as version
V8.1, but only as last released version V7.1.3.
The product update of the APL can require own APL service packs inside of a product
update period of PCS 7, resulting in differences for service pack versions between APL
and PCS 7.
As example, PCS 7 V7.1 SP1 includes the APL V7.1 SP3.
Compatibility of channel driver blocks in PCS 7 < V8.1

Some APL innovations provided functional improvements for the interplay with the PCS
7 Asset management. These functional extensions require compatibility between the
PCS 7 Basic Library and the channel driver blocks both of the APL and the PCS 7
Standard Library. The version number of these channel driver blocks may deviate from
the version number of the library:
 Use of the functions in the APL version V8.0 requires the installation of channel driver
blocks of version V7.0, because only these are able to cooperate with the Basic
Library V8.0.
 Therefore, the PCS 7 Standard Library V7.1, delivered with PCS 7 V8.0, included an
additional folder with channel driver blocks V7.0.
Upgrade scenarios for libraries of PCS 7 V8.0 with
 The following figure describes an application example, where in a mixed operation of
use of new functions
APL V8.0 and PCS 7 Standard Library (with the latest updated version) the new
functions of PCS 7 V8.0 can be used.
New asset & diagnostic New technological Updated version
functions functions
PCS 7 Basic APL Faceplates V8.0 PCS7 Faceplates V7.1.3

Faceplates V8.0:
• new Asset Faceplates
in APL style
APL >= V8.0 with PCS 7 Standard Library V7.1.3

Channel blocks of version with
V7.0 Channel blocks of version V7.0
e.g. Pcs7AnIn e.g. CH_AI
Basic Library V8.0 with
Diagnostic drivers, e.g.
Installation via installed
MOD_D1
frame setup manually
Installation via frame setup

The channel blocks of version V7.0
for the PCS 7 Standard library are
located here.

 In contrast, the following figure shows the application case for a mixed operation of
APL V8.0 and PCS 7 Standard Library without use of new functions of PCS 7 V8.0.
Upgrade scenarios for libraries of PCS 7 V8.0
An older version of the Basic Library and compatible versions of the driver blocks
without use of new
have functions
to be used in this scenario. The project is continued with old functionalities, and
the libraries have to be installed manually.
Old asset & diagnostic New technological Updated version
functions functions
PCS 7 Basic APL Faceplates V8.0 PCS7 Faceplates V7.1.3

Faceplates V8.0:
• new Asset Faceplates
in APL style
APL >= V7.1.5 with PCS 7 Standard Library V7.1.3

Channel blocks of version with
Basic Library V7.1.3.3
with Diagnostic drivers e.g.
installed installed
MOD_D1 manually manually
installed manually
 When using Windows 7, only the PCS 7 Library of the PCS 7 V8.0 DVD can be
installed.
Further Usage
Training documentation of PCS 7 Library from
SP-PCS7CWS 3-9 PCS 7 V8.1 – SITRAIN - Siemens AG © 2015
Mixed operation of channel block versions

Compatibility of channel driver blocks in PCS 7 >= V8.1
New asset & diagnostic New technological Updated version
functions functions
APL Faceplates >= V8.1 PCS7 Faceplates V7.1.3.2

PCS 7 Basic
Faceplates V8.1
APL >= V8.1 with PCS 7 Standard Library

Channel blocks of version V7.1.3.2 with
Basic Library V8.1 with
Diagnostic drivers e.g.
Installation via installed
MOD_D1
frame setup manually
Installation via frame setup

The channel blocks of version V7.0
for the PCS 7 Standard library are
located here.

 PCS 7 Library V7.1.3.2 installing: -> PCS 7 DVD V8.1, folder: "Additional Products"
 For engineering use channel blocks of this Library (V7.0).
 Independent of the version due to additional installed XML meta data (e.g.
diagnostics).
 Compatibility for earlier and following PCS 7 versions
 See [111] PCS 7 V7.1 Standard Library - 03_2009, for more details on the former
PCS 7 Standard Library.
See [112] PCS 7 V8.1 Basic Library - 07_2014, for more details on PCS 7 Basic
Library.
See [113] PCS 7 V8.1 Advanced Process Library - 07_2014, for more details on
PCS 7 APL.
See [114] PCS 7 Libraries APL Style Guide - Programming Manual - 10_2010, for
more details on design specifications and rules that you require to adapt project-
specific blocks in conformance with APL.

6.3 General
Engineering the APL – functions using the APL
withengineering
Structures and Signal status (ST)
6.3.1 Structures and Signal Status (ST)
Process Value with Signal Status (Quality)

• Using structured Variables
(Process value with signal state ) Channel
• Status corresponds to PA profile of Function
PROFIBUS & PROFINET international Block
• In the faceplate for each shown process

value the signal state will be displayed
• In the block icon, display of the worst
signal state from the displayed process
values in the faceplate
Process value as Structure
Customer Benefit
• Consistent use of Signal Status
• The signal provides directly the quality of the
process value
A new feature of APL is the use of structures. Each process interconnectable parameter
of a block is of the Structure type. This structure consists at least of 2 bytes, whereby at
least one byte determines the actual value (e.g. type BOOL) and one byte characterizes
the signal status (ST) of the transferred signal.
Analog Value [STRUCT]: Value [REAL] +1 Byte Signal Status (ST) [16#...]
Engineering with the APL –
Binary Value [STRUCT]: Value [BOOL] + 1 Byte Signal Status (ST) [16#...]
Structures and Signal Status (ST)
The following figure shows interconnectable parameters in the CFC and their structure.
Analog value
Binary value
The Signal Status Concept (symbol,

Training documentation SP-PCS7CWS 3 - 12
value status, priority…) fulfils the standard
specification according to PA – Profile PROFIBUS & PROFINET international.

Structures and Signal Status (ST)
The Signal Status (ST) is displayed in different locations as symbols or hexadecimal
values:
Symbol Priority Hexadecimal value Value status
0 16#60 Simulation
1 16#00 Bad, device-related
2 16#28 Bad, process-related
3 16#68 Uncertain, device-related
4 16#78 Uncertain, process-related
5 16#A4 Maintenance request
6 16#80 Good
In technological blocks, a group status is formed from the input parameters (see
description of the relevant blocks) according to the priority table below.
Note: Priority "0" is the highest priority, "6" the lowest.
This group status is displayed in the status bar of the faceplate and of the block icon.
Structures and effect of the Signal Status

The process values of the function blocks are generated and transferred along with a
signal status as a structured variable. This contains a statement about the signal quality.
EngineeringThe
with the APL –
function blocks determine the appropriate signal status for their process outputs
Forming and outputting
depending signal
on the signal status
status for blocks
of the process inputs, which are involved in calculating
the process outputs.
The blocks are grouped into the following

function block groups:
• Technologic blocks
• Digital logic blocks
Block status
• Analog logic blocks better
• Redundancy blocks
• Blocks with configurable status
prioritization
• Interlock blocks
• Mathematical blocks Block status
worse
• PCS 7 channel blocks
• Channel blocks for field devices
The priority list for digital logic blocks or Priorities e.g. for technologic Priorities for
interlock blocks is not shown here! blocks, analog logic blocks redundancy
blocks
All blocks of a group use the same priority specifications and form the signal status of the
process outputs based on them.

If multiple process inputs are involved in calculating a process output, the signal status
is formed according to prioritization defined by function block groups.
The highest priority is the signal status with the value 0.
 The status / quality of control inputs for logic functions and parameters have no
influence on the status / quality of process values and logic functions of the blocks.
The status / quality of process values inherit the results of mathematic and logic
functions, which are directly related to the process value.
The status/quality of process values immediately inherit the results of monitoring and
limiting functions directly related to the process value.
If process values are connected via a channel driver (Pcs7AnIn, Pcs7DiIn, Pcs7DiOu,
etc.) directly with the technological function block (e.g. MotL), the Signal Status is
displayed directly in the faceplate.
For other blocks such as And04 or Or04 the Signal Status is passed on to the output
according to logic.
When the Signal Status of the outputs is formed the following is taken into
consideration:
 If any input of a gate causes a signal change at the output, the worst Signal
Status of the input must be taken as every signal can influence the output.
 If several inputs have equal priority with the effect that the output cannot change,
these inputs will take the best Signal Status as the output is clearly defined by this
signal.
 See [113] PCS 7 V8.1 Advanced Process Library - 07_2014, 1.1.5 for more details on
formation of the Signal Status.

Feature parameters
6.3.2 Feature Parameter
In the APL most blocks have a Feature input parameter. This input can be used to
Training documentationinfluence the
way in which the block
SP-PCS7CWS 3 - 25 works. The Feature parameter
SITRAINenables the© 2015
- Siemens AG
manufacturer to realize sector-specific customer requirements as well as adjust them
afterwards. Furthermore, function expansions can be integrated retrospectively via this
parameter.
It is a structure which consists of 32 Boolean elements which can be used for setting
various behaviors at the block. For the 32 Boolean elements there are pre-assigned bits
and reserve bits. The reserve bits can be assigned by the manufacturer (Siemens) at a
later point in time.
The configuration of the individual bits of the feature parameter occur by double-clicking
the "Feature" input at the block (offline/online) as displayed above. Normally, the feature
bits should be configured in the Master Data Library in order to achieve consistency in
the multi-project.
 Any change of settings on the feature parameter does not influence the block
interface. This allows modifying the block behavior without CPU stop. Advantages of
the reserve bits: Block changes can be loaded without CPU stop. The original block
behavior can further be used.
 See [113] PCS 7 V8.1 Advanced Process Library – 07_2014,

1.1.9 for configurable functions with the Feature I/O (Assignment of Feature-Bits).

Engineering
SIMATIC –
mit der APL
PCS 7 AS Engineering
Technologische Maßeinheiten
6.3.3 Units in the APL
Vollständige Liste der verfügbaren Einheiten siehe Online-Hilfe
Ausgabe der Einheit zur

Verschaltung mit
anderen Bausteinen
The APL-specific procedure for setting the unit for analog signals shall be illustrated at
the example of both blocks Pcs7AnIn (channel driver) and MonAnL (limit value block).
The unit is represented by means of an identification number at the input PV_InUnit.
 Data type, possible identification numbers see Help on the “MonAnl” block under the
keywords “Functions of MonAnl, select unit”.
Number “1342” for example represents the unit “%”. The input channel driver forwards
the unit of "PV_InUnit" to its output "PV_OutUnit". By interconnection to the
"PV_Unit" connection of the limit block the unit “%” is then displayed in the
visualization of the limit value block.
Other advantages
 Based on PA specification according PNO and HCF
 No text but integer value (multilingual on OS)
 Can be transferred via connection in CFC
 Can be changed online without OS compile
 Language neutral
 If PV_Unit input of the MonAnl is configured with 0, the unit can also be specified
according to the current method (attribute “S7_unit” of this connection or in the CFC
the “Unit” column of this connection in the Properties table of the “MonAnl”
connections). Not listed units can be used this way.
 See [113] PCS 7 V8.1 Advanced Process Library – 07_2014, 1.1.12.5 for more
details.

6.3.4 Design of APL Block Icons
Compared with the PCS 7 Standard Library the design of the block icons in the APL has
Design of APL Block
changed Icons (APL
and expanded V8.1)
considerably.
Two different types of block icons exist in APL V8.1:
The status information is arranged above The status information is arranged

the block icon in a line. around the block icon.
(always in case
of valves and
drives)
A huge stock of icons per block3 -type

Training documentation SP-PCS7CWS 29
is provided in @PCS7TypicalsAPLV8.pdl:

Displays and operator controls in APL Block Icons

Displays and operator controls in APL Block Icons
Operable extended status display

(Symbol can be replaced)
Display of alarm high / low
Alarm is triggered
Manual / Automatic / Program / Local / OOS
Internal / External
Signal Status
Bypass active / Forcing / Tracking
Block is interlocked
Message is available in the memo view
instance-specific name
(hidden / unhidden)
 Display of the signal status

This display informs you about the status and quality of the signals. It shows you the
signal status with the highest priority, which depends on the type of process tag.
 Displaying and hiding an instance name for a block icon
Hold down the Shift key and perform a left click on the block icon. The instance name
is displayed and remains visible as long as the current process picture is visible.
 Color change in case of active alarm
Analog monitoring: When in alarm, the displayed value gets a different color. Alarms
are accentuated and therefore better visible in the process picture.
 Display of comments in the process picture
Beginning from APL V8.0, comments on the respective process tag are displayed as
tooltips when you hover the cursor briefly over a block icon. These comments are
defined during configuration and cannot be edited in the operator station (OS).
Status display
The operating status of a device can be indicated by an operable icon. You can use this
icon to open the operating window of the associated faceplate and set the device to a
new operating state. You can start a motor or open a valve, for example. This requires
that you have the appropriate operator permissions.
 Left click: You open the standard view of the corresponding faceplate
 Right-click on the icon of the status display. The operating window of the
corresponding faceplate opens. Click on the button for the desired operating state.

6.3.5 Design of APL Faceplates
Design of APL Faceplates

Compared with the PCS 7 Standard Library the design of the faceplate in the APL has
changed and expanded considerably. This change is also due to the extended
functionalities of the APL.
Display and
operation
Commands and
Status operating modes
displays
Interlocks
Button for
additional
faceplate
Auxiliary values
Operating (max. 2)
area
Comparing Faceplates of PCS 7 Library und APL

Displays and operator controls
Training documentation SP-PCS7CWS
Former PCS 7 Standard Library 3 - 32 SITRAIN
Advanced Process - Siemens AG © 2015
Library
1 2 3 4 6
1 2 4 6 7 5
1. Group display
3 5 2. Status displays (beginning from left)
• Lock alarms via faceplate
1. Group display
• Suppress alarms via FB
2. Lock alarms via faceplate
• Acknowledge alarms
3. Acknowledge alarms
• Worst Signal Status
4. Suppress alarms via FB
• Batch display
5. Block instance allocated by SIMATIC BATCH
• Active alarm delay
6. View selection
• Maintenance request and release
7. Loop View
• Memo display
3. Open views of the faceplate
4. More available views of the faceplate
5. Back to the block icon (e.g. from another picture)
6. Pin the view

Open views of an APL block
 Left clicking shows the view in the same window.
 Right clicking opens a new window.

6.4 Operating modes of APL

6.4.1 Overview of the operating modes of APL
The operating modes are mainly assigned to the block families (drives, channel,
convert, etc.). Three categories are distinguished below:
1. Motors, valves and dosage feeders
2. Controls
Operating modes –without
3. Blocks Overview
“manual” and “automatic mode” (e.g. MonAnL)
Basically the operating modes can be set directly by the operator in the faceplate. In
order to select a particular operating mode the respective conditions must also be
fulfilled (e.g. operator authorization, etc).
Motors, valves, and dosing units

Local operation
Automatic mode
Manual mode
Out of service
Controller
Automatic mode
Manual mode
Program operation
Out of service
Blocks without manual or automatic mode

On
Out of service

Status diagram
6.4.2 for theforoperating
Status diagram modes
the operating modes of APL
Used for
Used for motors,
controllers only
valves, and
dosing units

Number in Condition for status change
graphic (top)
1 Manual (on)  Out of service
 Via faceplate (OosOp = 1), if ModLiOp = 0 or
 Via edge transition 0 → 1 of OosLi, if Feature bit "Reaction to the
out of service mode" = 1
2 Out of service  Manual (on)
 Via faceplate (ManModOp = 1)
3 Local mode  Manual
 Via faceplate (ManModOp = 1), if ModLiOp = 0 and LocalSetting
= 3 or LocalSetting = 4 or
 Via LocalLi = 0, if LocalSetting = 1 or LocalSetting = 2
4 Automatic  Manual
 Via faceplate (ManModOp = 1), if ModLiOp = 0 or
 Via ManModLi = 1, if ModLiOp = 1 and Feature bit "Setting switch
or button mode" = 0 or
 Via AutModLi = 0, if ModLiOp = 1 and Feature bit "Setting switch
or button mode" = 1
5 Manual  Automatic
 Via faceplate (AutModOp = 1), if ModLiOp = 0 or
 Via AutModLi = 1, if ModLiOp = 1
6 Manual  Local mode
 Via faceplate (LocalOp = 1),
if ModLiOp = 0 and LocalSetting = 3 or LocalSetting = 4 or
 Via LocalLi = 1 if LocalSetting = 1 or LocalSetting = 2

Number in Condition for status change

graphic (top)
7 Automatic  Local mode

 Via faceplate (LocalOp = 1), if ModLiOp = 0 and LocalSetting =
3 or LocalSetting = 4 or
 Via LocalLi = 1, if LocalSetting = 1 or LocalSetting = 2
8 Local mode  Automatic
 Via faceplate (AutModOp = 1), if ModLiOp = 0 and LocalSetting
= 3 or LocalSetting = 4 or
 Via LocalLi = 0, if LocalSetting = 1 or LocalSetting = 2.
9 Program mode  Automatic
 Via faceplate (AutModOp = 1), if ModLiOp = 0 or
 Via AutModLi = 1, if ModLiOp = 1 or
 Via edge transition 1 → 0 of AdvCoMstrOn, if automatic is set
before program mode.
10 Automatic  Program mode
Requirement for changeover in program mode: AdvCoEn = 1
 Via faceplate (AdvCoOn = 1), if ModLiOp = 0 or
 Via AdvCoMstrOn = 1
11 Manual  Program mode
Requirement for changeover from manual to program mode: AdvCoEn =
1 and AdvCoModSP = 0
 Via faceplate (AdvCoOn = 1), if ModLiOp = 0 or
 Via AdvCoMstrOn = 1
12 Program mode  Manual
 Via faceplate (ManModOp = 1), if ModLiOp = 0 or
 Edge transition 1 → 0 of AdvCoMstrOn, if manual is set before
program mode.

6.4.3 Operating mode "Manual" and "Automatic"
In "Manual mode" the device is controlled manually by the operator. The operator
decides how the manipulated variable (output signal) for the block is changed. The
manipulated variable can be analog or binary.
In "Automatic mode" the motors, valves and dosage feeders must be controlled by the
Switchover between
block algorithm via inputsoperating modes manual
which are interconnected and by the SFC.
or controlled
automatic
In "Automatic mode" the output signal of the control is automatically calculated by the
block algorithm.
Selection of manual/automatic operating mode with…
ModLiOp = 0 ModLiOp = 1
…Faceplate (or SFC) …CFC / SFC

Au
tM =1
od
Op d L i = 0)
o Li
nM
Ma tMod
=1
ManModOp = 1 (Au AutModLi = 1
(ManModLi = 0)
Manual mode Automatic mode
 Switchover initiated in the faceplate (ModLiOp = 0):

SITRAIN
The changeover between operating modes is carried out in the standard view of the
Other engineering features 12 - 54 Siemens AG © 2012
faceplate. In the function block, the parameters ManModOp for "manual mode" and
AutModOp for "automatic mode" are used.
If both signals (ManModOp =1, AutModOp = 1) are set, then ManModOp = 1 has priority.
 Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1):
The switchover between the operating modes is carried out with an interconnection on
the function block. The parameters ManModLi for "manual mode" and AutModLi for
"automatic mode" are used in pushbutton operation.
In switch mode (requirement: Feature Bit 4 = 1) connection AutModLi is used
exclusively.
If both signals (ManModLi =1, AutModLi = 1 ) are set, then ManModLi = 1 has priority.
Changing the switchover behavior using Feature Bits

Using Feature Bits you can change specific properties of the switchover behavior:
 Enabling bumpless changeover to automatic mode for valves, motors, and dosing
feeders (Feature bit 17)
 Disabling bumpless changeover to automatic mode for controllers (Feature bit 18)
 Resetting the commands for changing the mode (Feature bit 2)

Operating modes in APL –

6.4.4Configurable
Operating“Local
mode "Local"
mode”
This operating mode is used for motors, valves and dosage feeders. Control occurs
directly or via a “local” control station. Additionally, various behaviors can be set via the
LocalSetting parameter. Operating the block in the OS is not possible.
Localsetting 0 1 2 3 4
LocalOp / LocalLi = 1 LocalOp = 1

LocalLi
No Local switchover Switchover via faceplate

switchover
possible
control via DI control directly control via DI control directly
Operating modes in APL –
connected to
the CFC block
via the motor
control
connected to
the CFC block
via the motor
control
Configurable “Local mode”
1 2
• Local switchover via external signal • Local switchover via external signal
• Control signal from CFC block in AS • Control signals from MCC, CFC block in AS is tracked
3 4
• Switchover via OS faceplate • Switchover via OS faceplate

• Control signal from CFC block in AS • Control signals from MCC, CFC block in AS is tracked

In order to exit local mode via the interconnected input parameter, you can configure
various reactions using Feature bit 10 (Exiting local mode).
 See [113] PCS 7 V8.1 Advanced Process Library – 07_2014, 1.1.9 for a description
of these „Feature“-Bits. Also check the online help.

6.4.5 Simulating,
Simulating, Forcing,
Forcing, Tracking
Tracking
Simulating signals
There are two different forms of simulation: block-internal and block-external simulation
• In case of block-external simulation, a signal with simulation state is applied at an input parameter.
• Block-internal simulation means that the "simulation" function is running in the block itself.
• The technological functions are not influenced.
• All the process-related output signals receive the "simulation" status.
Forcing of operating states

Forcing of operating states is only possible in the manual and automatic modes, and has the highest
priority over both operating modes.
Forcing is possible for:
• Forces tracking for closed-loop controllers and control values
• Enabling and disabling at motors
• Opening and closing of valves
Manipulated variable tracking

• Adjustment of the manipulated variable (tracking) allows a bumpless switchover of e.g. controllers
in case of cascade control.
• Forced tracking is used to set the controller output to a value that can be specified
6.4.6 Priorities of operating modes and control functions
To ensure that drives can assume a safe state with different modes and control
functions (Quick Stop/Forcing of operating states), the control commands or modes
Priorities ofmust
operating modes
be assigned different and control functions
priorities.
Thus a drive which is switched off, for example, by the operator at the local control must
not be switched on by an automatic mode command. The priorities for the modes and
functions of the motor are given in the following picture. The hand mode and the
automatic mode have the lowest priority here.
Out of Service
Rapid Stop Motor
BypProt = 0
Local mode LockAct
Localsetting = 2/4)
Priority
Forced operating
State
(Forcing)
Manual/Automatic always Active interlock
Operating modes Conditions/Parameterizing Functions/States

Templates
6.5 APL Templates
Templates (standard types, standard solutions) are provided to support you in the
configuration of a PCS 7 plant in case of recurring technological functions.
The PCS 7 libraries (PCS 7 Advanced Process Library, PCS 7 Basic Library) contain
templates for base control functions (e.g. motor control, valve control, Standard PID
Training documentation control loop) as well as for advanced
SP-PCS7CWS 3 - 26 control functions (e.g. PID control
SITRAIN loop AG
- Siemens with control
© 2015
performance monitoring).
A template is a prepared chart containing already all blocks necessary for the process
tag, in other words not only technologic blocks for the control function, but also driver
blocks and additional logic.
Example ValveLean
Example ValveLean (PCS 7 APL V8.1)
Bad process
„Maintenance
value Connection
release“ status
to output
Input driver blocks

for feedback
Output driver block for

the control signal
Interlock blocks
Valve block
„Out of service“
status
Textual
interconnection Logic to form the control
system fault
Logic to merge the

„Out of service“ status
Trainingsunterlage SP-PCS7CWS 5-4 SITRAIN - Siemens AG © 2015

One possible procedure how to work with templates:

1. Copy the desired template into the master data library of your multiproject. Make
there your adoptions to your specific requirements.
2. Drag the customized template from your master data library into the hierarchy
folder, where the process tag has to be placed.
3. Open the resulting chart and replace all opened textual interconnections by
references to I/Os from the symbol table to connect the chart with hardware signals.
6.5.1 Monitoring the feedbacks
The effectiveness of control signals is not of course known to a technological block. The
internal block logic can recognize and take into account the effectiveness of the control
signal with the help of block inputs for feedback signals. You can use the following
monitoring functions:
Monitoring the start-up and stop characteristics for motors or the runtime of valves
Monitoring of the startup characteristics is implemented using the parameter
MonTiDynamic. The monitoring time specifies the period within which the feedback
value, for example, FbkStart with motors, must be available in response to a control
signal. If this is not the case, the text "Control error" is displayed in the standard view of
the faceplate. An error message is generated at the same time.
The block then goes to its neutral position. In the case of motors, this is always the stop
state. With other blocks, this is an neutral position you have specified (SafePos
parameter). The block signals this at the corresponding output parameter of the error
message with 1, for example, with MonDynErr = 1 for motors.
Parameters are set in seconds.
Monitoring the operation of motors or the maintenance of the position of valves

Monitoring of the operation or the maintenance of the position of valves is implemented
using the parameter MonTiStatic. The monitoring time specifies the period in which
the feedback value can change its value briefly without an error message being output.
An example would be a running motor with the feedback via the input parameter
FbkStart. This parameter should be static in accordance with the control function.
Parameters are set in seconds.
 Please note the following configuration rule:

MonTiDynamic ≥ MonTiStatic and MonTiDynamic ≥ SampleTime
If something is set outside these limits, the block always returns the respective limit at
the input.
Disabling Monitoring
You can activate or deactivate the monitoring of feedbacks.
The monitoring function is enabled via the Monitor = 1 input.
Static and dynamic errors are reset by disabling the monitoring (Monitor = 0). If you
reactivate monitoring during the plant runtime, only dynamic monitoring
(MonTiDynamic) will be performed.

Disabling feedback
You can also disable feedback completely. If you operate a block without feedback, use
the parameter NoFbkxxx = 1. This means, for example, that you do not have any
feedbacks for the opened state of the valve. Monitoring is thus disabled for this
feedback. The feedback at the block is adjusted according to the control signal.
6.5.2 Error handling
The channel and technologic blocks feature error handling routines. A distinction must
be made between the following areas:
 Error numbers
 External process control error (CSF)
 Process-specific errors
 Invalid signal states
 Mode switchover error
 Errors in channel blocks
External process control error (CSF)

An external process control error always lies outside the process - it exists in the form of
device or other hardware faults. If, for example, a run-time error occurs at a valve, there
is an error or fault in the pneumatic system.
A process control error is output if an external error is set at the input CSF. You can
enable this output function, for example, by interconnecting output Bad of the channel
block with input CSF of the technologic block. Several sources (e.g. Bad outputs of
several channel driver blocks) can be interconnected via a digital logic (e.g. OR04).
The error message "$$BlockComment$$ External error occurred" is output at CSF = 1.
With motor, valve and dosing blocks, there is also the possibility that the block switches
to error processing.
Error numbers
Most blocks have an output parameter ErrorNum that can be used to output internal
error states of the block as error numbers.
With some blocks, input parameters are checked for permissible values. If the block
algorithm detects an invalid combination of input signals, then an error number
(ErrorNum) is output depending on the block type.
For example, a valve cannot respond to commands for opening and closing at the same
time.
Outputting group errors

The GrpErr output parameter assembles the faults of a block and makes them
available to you. A group error is compiled from the following error information:
 Feedback errors (static or dynamic feedback monitoring)
 External error (CSF and FaultExt)
 Motor protection (only for motors)
 Module errors (only for hardware controllers)
 I/O access errors (only for hardware controllers)

 Parameter assignment errors (only for hardware controllers)
It is depending on the block type how the signal is formed for the group error.
 The signal status of the individual signals is not taken into consideration for forming
the group error. The outputs therefore always have the status, 16#80.
6.6 Task and checkpoint
Task
Walk-through the APL Start project
Test several functions and familiarize yourself with the operation of APL block icons and
faceplates.
Checkpoint
Checkpoint
How …
 do you parameterize the PCS 7 APL
channel driver so that the output
process value is inverted?

6.7 Configuration of dose functions using APL
Dosing process in brief

Overview about essential
The following terms
figure shows and features
an example – with coarse and fine dosing, a
dosing process
dribbling time, and a dribbling dosing. The dosing starts with coarse dosing and
Dosing process in brief
subsequent fine dosing. A dribbling time has been configured and at the end a dribbling
dosing is required to reach the setpoint.
Quantity
Dribble
correction
Dosing flow
in kg/time
Underdosing – Dosing finishes
Decision for further dosing immediately
SP fine feed
minus dribble
SP coarse feed
Dribbling
Coarse feed flow Fine

dosing
Fine
feed
flow
Dribble
Coarse dosing
flow
Dribble time SP Post dosing time

reached
2 steps: Coarse dosing and fine dosing

4. The dosing procedure starts with a large dosing feed (coarse flow) with the
disadvantage of low accuracy but with the advantage of short dosing time.
5. The second dosing step uses a small dosing feed (fine flow) until the setpoint of
dosing amount is reached. This step needs more time and allows higher accuracy.
Prerequisite for the implementation of a 2-step dosing procedure is the existing process
equipment for feed control, e.g. valves and pipes with different size / dimensions.
Dribbling
If, for procedural reasons, a dribbling quantity is expected after the closing of the valve
when dosing is stopped (in particular with the dosing type "weigh"), a dribbling quantity
as well as a dribbling time can be configured.
If, for example, 100 kg are to be dosed as setpoint and it is expected that after the
closing of the valve another 5 kg will dribble within approx. 5 seconds, a dribbling
quantity of 5 kg and a dribbling time (corresponding to the waiting time) of 7 seconds (>
5 seconds) are configured.
The consequence is that the dosing will be stopped already at 95 kg and then it will be
waited for 7 seconds. During this period, the function block will be in the "Dribble" state.

Only after this dribbling time will it be checked whether the dosed quantity is within the
tolerance range. If the dosing quantity is outside the tolerance, underdosing or
overdosing will be signaled.
Post dosing
In the case of underdosing, a post dosing can be started with the "Continue" command.
This post dosing will run for a configured time, the so-called duration of post dosing. If
the process value is within the tolerance limits, the dribbling time will be terminated
prematurely and the dosing will change to the "End" state.
A dosing can be terminated at any time with underdosing (dosing quantity not within the
tolerance range) via the "Unterdos Quit" button. The dosage feeder will then changes
from the "Off" state to the "End" state.
Creep flow
Creep flow means that despite an inactive dosing process a dose flow >0 can be
observed. Possible reasons are valves being not sealed.

6.8 DoseL block of the APL in brief

6.8.1 Dosing states and commands
 See [113] PCS 7 V8.1 Advanced Process Library - 07_2014, 5.1.3 for more details
Dosing status
The block provides the following states:
 "End"
 "On"
 "Dribbling"
 "Off"
 "Pause"
state change
The following commands can initiate a state change:
 "Start"
 "Cancel"
Dosing can only be started if the dosing setpoint is greater than the current dosing
quantity (DQ_Out) or if Feature Bit 6 (Resetting the dosing quantity when dosing
starts) is set and no interlock is pending.

However, the following status changes are also performed automatically:

Number in the Description
status diagram
1 When the dosing quantity is reached, dosing terminates (DQ_Out ≥ DQ_SP).
2 If the dosing quantity reaches the dribbling quantity (relative to dosing setpoint
DQ_Out ≥ DQ_SP – DribbOut) the dribbling status becomes active.
3 Automatic post dosing in automatic mode via the Feature Bit 12, if an underdosage
was identified after the dribbling time (RelaxTime).
4  Flow alarm (see input parameter Feature Bit 11) or
 Interlock.
 The dosing process of the DoseL block is set to the "Off" state with a process
value status "Bad, device-related" or "Bad, process-related". The response can be
set using Feature bit parameter assignment.
5  The flow alarm is acknowledged (also provided via the "Continue" command if
Feature Bit 9 = 1) or
 The interlock is acknowledged (also provided via the "Continue" command if
Feature Bit 9 = 1).
 "Continue" command after underdosing.
6 Underdosage identified after the dribbling time (RelaxTime).
7 Interlock
8 Dribbling time (RelaxTime) has expired and dosing quantity is above the low
tolerance limit (DQ_Out ≥ DQ_SP_Tol - DQ_AL_Tol)
9 The underdosage is acknowledged or the dosing quantity has been reached
(DQ_Out ≥ DQ_SP) via creep flow, for example
10 Dosing quantity has been reached (DQ_Out ≥ DQ_SP) via creep flow, for example
Switch mode and Button mode

Also for the dosing block a differentiation is made between Switch mode and Button
mode. This setting is made via Feature Bit 4, as in the drive blocks. The following
different controls result from that for the dosing block:
 Commands with Feature Bit 4 = 0 (Button mode)
 StartAut =1 (Start dosing)
 CancelAut =1 (Cancel dosing)
 PauseAut =1 (Pause dosing)
 ContAut =1 (Continue dosing)
 Commands with Feature Bit 4 = 1 (Switch mode)
 StartAut =1 Start dosing
 StartAut =0 Cancel dosing
 PauseAut =1 Pause dosing
 PauseAut =0 Continue dosing
 The command for start dosing in Automatic mode is an edge. It is executed only in
the status "End".

Dosing types "Weight " and “Flow"

6.8.2 Dosing types "flow" and "weight"
Weight Flow
• Quantity is • Flow rate is

measured measured
(scale or level) • Integration of
• Tare weight measured flow
• Calculation of gives a dosed
differences quantity
weighing the removal volume Source tank
Start
AS
End Dq
AS
AS End
Dq
Start
weighing the fill volume Target tank
Dosing type "Weight" (Feature Bit 5 = 1)

The incoming process value is the quantity, e.g. if a tank to be filled stands on a scale.
At dosing start, the current weight is stored (tared). The actually dosed quantity is
calculated from the incoming process value minus this tare weight. This logic applies to
a dosing of the filling type of a tank (MeterType = 0). Whereas for clearing
(MeterType = 1), the following applies: After dosing start and taring, the process value
is deducted from the stored tare weight and thus the clearing, i.e. the reduction of the
tank weight, is represented as quantity increase.
Dosing type "Flow" (Feature Bit 5 = 0)

The incoming process value is a flow and is summed up to a quantity in the block. This
functionality corresponds to an integrator; with the time constant TI and the parameter
Gain for the assessment of pulses in a pulse module. In the case that the flow arrives
via pulse modules, sliding averaging can be activated for the display and flow alarms.
Via the parameter NumSample (default = 0), the number of cycles is defined over which
the average is to be calculated.
Which dosing type is used is configured via Feature Bit 5 "Select dosing type".
Feature Bit 5 = 1 represents the weight mode and Feature Bit 5 = 0 the flow mode.

Functional
6.8.3 principle
Functional of dosing
principle type
of dosing “Weight"
type "Weight"
DoseL
0 (filling) or 1 (removal) MeterType Ctrl

Binary control output (coarse / fine)
Tare signal from scale or Ctrl2
StandStill
1 = Automatic Tare when
dosing starts SP Analog control output (coarse / fine)
DQ_Tare
SP1 Analog control output coarse flow
Measured value weight / level SP2
PV Analog control output fine flow
(from scale / tank)
DQ_Out Used dosing quantity (actual value)
DQ…
Setpoint for dosing quantity
(coarse / fine /) DQ2…
Feature
Feature Bit 5 = 1 (weight)
Feature Bit 7 = 1 (Internal calculation of dosing flow rate)
Tare function: actual scale value is transferred to the tare memory DQ_Tare.
The process value (measured value)

Training Documentation SP-PCS7CWS 7-7
is a level or a weight. SITRAIN - Siemens AG © 2015
Tare
The dosing quantity is determined for a scale dosing in the "Start" state following a
positive edge at the input parameter StandStill. The StandStill input parameter
is a feedback signal of the scale.
The process of determining the dosing quantity stops after the dosing quantity is reset in
the "End" state.
If the signal is no longer available, you need to configure StandStill with 1
permanently; the dosing quantity will then be determined right at the start of the dosing.
Calculation of dosing quantity

When weighing the fill volume (MeterType = 0), the dosing quantity is determined
using the following equations:
DQ_Out = PV_Out − DQ_Tare
When weighing the removal volume (MeterType = 1):
DQ_Out = DQ_Tare − PV_Out
 The DQ_Out output parameter is the dosing quantity and not the actual scale value.
In the "End" state (= following resetting of the dosing quantity), nothing further is
displayed, since the dosing procedure is complete.
When dosing starts, the actual scale value is transferred to the tare memory, and
therefore the dosing quantity always remains 0 after the start of dosing. Therefore,
the actual scale value is not displayed in the "End" state.

Functional principle of dosing type “Flow“

6.8.4 Functional principle of dosing type "Flow"
DoseL
dimensionless conversion factor

TI Ctrl
for time basis Binary control output (coarse / fine)
Ctrl2
Number of values included in NumSample
average calculation
SP Analog control output (coarse / fine)
Proportional factor Gain
SP1 Analog control output coarse flow
Measured flow rate PV
(from flow meter) SP2 Analog control output fine flow
PV_Out Flow rate used in the calculation

DQ…
Dosing quantity (coarse / fine) (current value)
DQ2…
Feature
Feature Bit 5 = 0 (Flow)
Dosing quantity: is implemented using the trapezoid rule, time basis of the measured value acquisition can
be converted by dimensionless conversion factor TI
Average calculation : serves to smooth systematically pulsating measuring signals; 1 <= NumSample <=16
Average calculation for the flow rate
Where
PV_Out(t) = PV · Gain
Determining the dosing quantity

When using flow dosing, the dosing quantity is determined using the following equation:
 The integration of the flow for the dosing quantity is implemented using the trapezoid
rule.
Compared to the summation of rectangles rule, in which the values are simply added
up, the procedural error in the case of the trapezoid rule is smaller for the
determination of the numerical integral value.

Operation
6.8.5 of Dose
Operation of block
dose block
• Dosing can be started only if dosing quantity

setpoint > 0
• Feature Bit6 = 1 enables to reset the dosing
quantity automatically with start command
2 • In case of underdosing the operator can manually
continue the dosing process (post dosing).
Input of dosing • The current value of dosing quantity is displayed,
quantity setpoint in not the current dosing flow rate.
the standard view • The dosing status is displayed in the area for status,
e.g. coarse dosing, fine dosing, etc…
1
Display of
dosing status

Input of setpoints in the OS for 2-step dosing
2-step dosing
Quantity setpoint view

Feature Bit 8 = 0 Feature Bit 8 = 1
Parameter DQ2_ works as rel. factor. Parameter DQ2_ works as absolute value.
Flow setpoint view
Feature Bit 15
Displayed unit in % or
following input PV_Unit

Quantity setpoints
 The block always requires the setpoint for the dosing quantity (dosing setpoint). All
I/Os for the dosing setpoint start with DQ_.... The dosing setpoint is comprised of the
coarse and fine setpoints for the coarse/fine flow control.
 All I/Os for the fine setpoint start with DQ2_.... The coarse setpoint is generated
internally from the dosing and fine setpoints and is displayed at the output with
DQ1_SP.
 If no fine setpoint is available, the coarse setpoint is equal to the dosing setpoint.
Dosing flow setpoints

Flow setpoints can be specified for the coarse/fine flow setpoint specification.
All I/Os for the coarse flow start with SP_..., and all I/Os for the fine flow with SP2_....
The setpoint for coarse or fine flow is displayed at the output SP in the "On" status,
depending on the coarse/ fine flow control.
 In case of dosing type "weight" (scale mode) it is not possible to input analog flow
rate setpoint for coarse and fine flow. The flow setpoint view cannot be selected.
Exception: The calculation of the flow rate for dosing by scale is activated (Feature
Bit 7 = 1). In that case the flow setpoint view is available, but it is not possible to input
setpoints. The calculated value for current flow rate is displayed in this view.
Feature Bit8 "Use an internal or external setpoint for the absolute fine dosing quantity"
Use this Feature bit to determine whether the doser processes the internal and external
setpoint for the fine dosing quantity in an absolute manner and is displayed or operated
in an absolute manner in the faceplate.
The default setting is 0.
 Bit = 0: Deactivated. The internal and external I/Os as well as the display and
operation of the fine dosing quantity setpoint are processed in the % unit.
 Bit = 1: Activated: The internal and external I/Os as well as the display and operation
of the fine dosing quantity setpoint are processed in the unit that was set using the
parameter DQ_Unit.
Feature Bit15: "Flow setpoints in percent"

You can use this Feature bit to specify if the doser block should display the flow
setpoints in the faceplate as percentages.
The default setting is 0.
 Bit = 0: Deactivated. The display of the flow setpoints is made in the unit specified
with the PV_Unit parameter.
 Bit = 1: Activated: The display of the flow setpoints is made in the unit %.

Limit monitoring / alarms
Limit monitoring / alarms
Check for underdosage / overdosage when the

"Dribbling" status has expired -> dosing end
With 100 kg as setpoint the current value must
be between 99,3 kg and 100,3 kg
Monitoring of flow rate limits during all

dosing steps
Monitoring of deviations while dosing is

not active (creep flow), serves also as
threshold for quantity counter
Dribbling
6.8.6Training Documentation
Dribbling SP-PCS7CWS 7 - 11 SITRAIN - Siemens AG © 2015
DoseL The dribbling quantity is a forecast

(a predicted value).
Dribbling quantity DribbIn
Activation of automatic dribbling DribCor

Automatic Direct input via
Limit for automatically determined calculation faceplate or
DribMax
dribbling quantity parameter
Weighting factor of the last DribCor
DribbOut = DribbIn
dosing action as a percentage DCF DribMax
used for automatic determination
DCF
Dribbling time RelaxTime
Feature DribbOut Dribbling quantity used in the block
Feature Bit 27 = 1 (Enable configuration of the dribbling quantity): Dribbling parameters can
changed during dosing in progress as long the dribbling has not yet been
started.
Automatic determination of dribbling quantity: Determines the dribbling quantity from previous
dosing actions automatically.
The "Dribbling" status is entered automatically in accordance with

DQ_Out ≥ DQ_SP – DribbOut
Where:
DQ_Out: Dosing quantity actual value
DQ_SP: Dosing quantity setpoint
DribbOut: Dribbling quantity
The dribbling quantity is specified with the input DribbIn.
Automatic calculation of dribbling quantity

Input DribCor = 1 can be used to automatically determine the dribbling quantity from
previous dosing actions:
DribbOut = DribbOut - (DQ_SP - DQ_Out) · DCF / 100
DCF represents the weighting factor of the last dosing action as a percentage and
cannot be set to below 0 or above 100.
DribbOut is calculated at the end of dosing or the first time an underdosage occurs,
and is limited to DribbMax.
Post dosing is not taken into account.
Dribbling
Operation of dribbling parameters in the Parameter view
Dosing quantity
setpoint 100 L
Stop coarse / fine dosing

at 95 L
After 20 sec
dosing finishes.
Expected
dribbling
quantity 5L

Post dosing
6.8.7 Post dosing
P_DoseTime
Tolerance band
is exceeded
Post dosing until

quantity setpoint
is possible
If an underdosage is detected after

Training Documentation SP-PCS7CWS 7 - 14
dribbling, post dosing can be performed using the
"Continue" command. In automatic mode, Feature Bit 12 can be used to start post
dosing automatically.
Post dosing is active for the period P_DoseTime. The block then enters the "Dribbling"
state or, if that state is deactivated, the "End" state. If the conditions for the "Dribbling"
or "End" states are met within the period P_DoseTime, the block switches to these
states immediately.
Post dosing can also be carried out in the "End" state by increasing the dosing quantity
setpoint and issuing the "Continue" command. Once the dosing quantity has been reset,
post dosing can no longer be carried out by means of increasing the setpoint.
Feature2 Bit 24: With acknowledge overdosage

You can use this Feature2 bit to change the acknowledgment behavior of overdosage
and underdosage. This Feature bit is available from PCS 7 V8.2.
 Bit = 0: After an overdosage is identified, the block changes directly to the “End”
state.
 Bit = 1: After an overdosage is identified, the block changes and continues to be in
the “Off” state. An acknowledgment is necessary to change the dosing state to “End”.
In the standard view, status display shows the state “Ack Dos End”.

Dribbling and post dosing

Dribbling and post dosing
Underdosage – Decision for post dosing

Feature Bit 12 = 1 for automatic post dosing
Real dribbling quantity
lower than expected! DribbOut
DQ_SP
DribbOut This figure shows a situation, where the status
DQ_SP – dribbling quantity
Dribbling was reached already before
DQ expiration of post dosing time.
Therefore the post dosing was finished and
Dose flow Dribbling
flow the post dosing time was neglected.
Time
Coarse-/ Fine dosing Dribbling Post Re-tried
dosing dribbling
Duration of Duration of
dribbling post dosing
phase
RelaxTime P_DoseTime
More Scenarios: Post dosing quantity < Dribbling quantity Post dosing for time P_DoseTime
and P_DoseTime = 0 Post dosing by setting of
Ctrl/Ctrl2 = 1 for one cycle
If the post dosing quantity is smaller

Training Documentation SP-PCS7CWS 7 - 15
than the dribbling quantity, dosing is started for
time P_DoseTime. If no parameter assignment has been made for P_DoseTime, the
coarse flow (Ctrl) or fine flow (Ctrl2) control outputs are set for one cycle.
If no parameter assignment has been made for the dribbling quantity, or the post dosing
quantity is larger than the dribbling quantity, the dosing procedure is continued without
taking time P_DoseTime into account.
6.8.8 Creep flow
The dosing quantity is determined in the "On" and "Dribbling" state.

In the "End", "Off" and "Pause" states, the flow (creep flow) is determined depending on
the Feature Bit 13 "Creep rate is always detected in the dosing quantity" and the value
CR_AH_Lim.
Creep flow monitoring is disabled with CR_AH_En = 0.

6.9 Collaboration of DoseL and Analog valve / Flow controller

Collaboration
6.9.1 of DoseL
Application of PID and Flow controllers
controllers for controlling the dose flow
Flow dosing with 1 PID controller Flow dosing with 2 PID controllers
• Feature Bit 5 = 0
• MeterType without relevance
PIDConL1
DoseL
PIDConL DoseL
PIDConL2
• Analog control output SP provides the setpoint • Analog control output SP1 provides the
for coarse flow and fine flow (step-by-step) setpoint for coarse flow
• Dribbling not necessary, because sensor / • Analog control output SP2 provides the
actuator are together setpoint for fine flow

Collaboration
6.9.2 of DoseL of
Direct application and Analog
analog valve
valves for setting the dose flow
• Setpoint SP (resp. SP1, SP2) for the analog valve

provided always as %
• Process value PV with physical unit
• Bar display is normalized to the process value
DoseL
VlvAnL
DoseL VlvAnL
MV
SP MV_Ext
SP1
Rbk
SP2

Control of an analog control valve and positioner
without auxiliary valve
How VlvAnL works
Feature Bit 5 = 0 (Control without auxiliary valve) Commands for
direct
positioning
Preview
„Auto“
de-energized
state
Input of analog Parameters for

setpoint direct
MV_Int positioning
Use of end
position switches
The control valve is brought to a specified position using an analog activation signal.
The activation signal can be formed by a ramp function in this case.
The block forms the manipulated variable error from the difference between the
activation signal and the acquired position feedback and can monitor it for adherence to
high and low limits.
The control valve is monitored for the "Open"/"Closed" position. The block can be
connected with a digital limit switch for this purpose. The block can generate the digital
position signals itself through the adjustable limits for the "Open"/"Closed" position.
Missing feedback can be derived from the control in the block.
Automatic mode without Auxiliary valve

The analog valve is opened or closed in automatic mode with the automatic commands
OpenAut and CloseAut.
If OpenAut and CloseAut are reset, the output MV is set to MV_Ext.
For "Activate command reset for control settings" (Feature Bit 3 = 1), OpenAut and
CloseAut are reset and the control elements are self-locking. This means the output
MV is only set to MV_Ext after a change of MV_Ext.
Control via switch or button mode (Feature bit 4) does not affect the behavior of
OpenAut and CloseAut.
 If no auxiliary valve is configured, no internal manipulated variable specifications can

be made in "automatic mode". Manipulated variable specification is set to external
when the mode is switched to "automatic".

Automatic mode via Auxiliary valve l

In this case the automatic commands OpenAut and CloseAut control the auxiliary
valve.
 In pushbutton operation (Feature Bit 4 = 0) the automatic commands in automatic
mode are latching, in other words OpenAut, and CloseAut, can be reset to 0 after
changing the control. In manual and local modes, however, the automatic commands
are not saved and in the absence of automatic commands the automatic control is
tracked.
 In switching mode (Feature Bit 4 = 1), control is selected with the static signals
OpenAut. If input OpenAut is not set the auxiliary valve is closed. Control via
Control of an analogis not
CloseAut control
needed.valve and positioner
If the "Activate command reset via
for control settings" function
auxiliary valve
(Feature Bit 3 = 1) is activated, the OpenAut input is reset to the neutral position
after evaluation in the block.
Feature Bit 5 = 1 (Control via auxiliary valve)
controls the
Auxiliary auxiliary valve
valve
Solenoid valve
/ Control valve
Compressed
air supply
• The forcing parameters Open/Close are related to both valves!

• Naming rule for all parameters corresponding to the auxiliary valve „…Aux…“

6.10 Task and Checkpoint
Task: Configuration of dosing material 1…3 into the Dose tank D210
Goal
Until now, the dosing of material was realized using a sequential function control.
You change the dosing configuration now to use of the DoseL block. Hereby, each
material is dosed with another dosing application:
 Material1: Dosing type "Flow" with 2 binary valves for coarse feed and fine feed
 Material 2: Dosing type "Weight (filling)" with 2 binary valves for coarse feed and fine
feed
 Material 3: Dosing type "Flow" with analog valve (without PID controller and without
auxiliary valve)
Checkpoint
Checkpoint

 What is the dose block status
“Off" indicated through?
 What could be missing, if the dose
block is not ready to start in
Automatic mode?

Content 7
7 Advanced Process Control (APC) with APL ......................................................... 3
7.2 Characterizing Control Loops ................................................................................................ 3
7.2.1 Stable and Unstable Control Loops ....................................................................................... 3
7.2.2 Examples of Unstable Control Loops .................................................................................... 5
7.2.3 Determining the step response – Possible loop reactions .................................................... 6
7.2.4 Loops with a pure lag time behaviour .................................................................................... 7
7.2.5 First statements about the loop behavior .............................................................................. 8
7.3 Overview of the APC tools in the PCS 7 Libraries ................................................................. 8
7.3.1 Procedure to Improve Plant Performance ............................................................................. 9
7.3.2 Control performance management ...................................................................................... 10
7.3.3 Extensions to PID Control .................................................................................................... 11
7.3.4 Cost Benefit Analysis ........................................................................................................... 15
7.3.5 Objectives for APC solutions ............................................................................................... 15
7.3.6 Further information .............................................................................................................. 15
7.3.7 Available Example Project in PCS 7 with APC-Templates .................................................. 17
7.3.8 Available APC-Templates in PCS 7..................................................................................... 18
7.4 PID algorithm ....................................................................................................................... 19
7.4.1 P-action ................................................................................................................................ 19
7.4.2 PI-action ............................................................................................................................... 21
7.4.3 PD-action ............................................................................................................................. 22
7.4.4 PID-action ............................................................................................................................ 23
7.4.5 Note on selecting the controller type ................................................................................... 24
7.4.6 Deadband ............................................................................................................................ 25
7.4.7 Filtering ................................................................................................................................ 26
7.4.8 PID Controller Block in the APL: PIDConL in Brief .............................................................. 27
7.4.9 Signal Filter Block in the APL: Smooth ................................................................................ 30
7.5 Control Performance Monitoring (CPM) .............................................................................. 32
7.5.1 Control Performance Index .................................................................................................. 32
7.5.2 Control Performance Monitoring in the APL: ConPerMon in Brief ...................................... 34
7.5.3 Configuring AS functions ..................................................................................................... 36
7.5.4 Configuring OS functions ..................................................................................................... 37
7.5.5 Startup of the CPM .............................................................................................................. 38
7.5.6 Evaluation of stochastic characteristics of the control performance (Steady state) ............ 39
7.5.7 Step evaluation .................................................................................................................... 42
7.5.8 Alternatives for determining the benchmark ........................................................................ 43
7.6 Controller optimization using the PID Tuner ........................................................................ 44
7.6.1 Introduction .......................................................................................................................... 44
7.6.2 Procedure for tuning a controller ......................................................................................... 45
7.7 Task and checkpoint ............................................................................................................ 51
SIMATIC PCS 7 – Advanced Process Control (APC) with APL


7 Advanced Process Control (APC) with APL

Learning
7.1 targets targets
Learning

 The procedure, how to improve Plant
Performance using APC Tools
 Overview about the APC Functions
provided by the APL
 Functionality of Control Performance
Monitoring
 Optimize a PID controller using the

Control Performance Monitoring and
the PID tuning integrated in PCS 7
7.2 Characterizing
Characterizing Control Loops
Control Loops
Stable and
7.2.1 Unstable
Stable Control
and Unstable Loops
Control Loops
SITRAIN
Course ST-PCS7ASE
Most of the control loops in process
11 - 3
plants show a stable behavior Siemens
- after a stepwise
AG © 2012
change in the manipulated variable the control variable shows a transient behavior
reaching a new steady state after some time. The controlled process is “stable” with
respect to systems dynamics, even without a controller.

Example for stable behaviour

The temperature of a reactor is increasing after the heating power is increased
stepwise. With increasing temperature the heat loss of the reactor to the environment is
also increasing, until finally a new equilibrium condition at a higher temperature is
reached, where the increased heat loss is equal to the enlarged heating power, and
compensates for it.
Thought experiment for integral behaviour

Please imagine a reactor with ideal thermal insulation, which means no thermal loss to
the environment. Now, if the heating power is increased stepwise starting from the
equilibrium condition, the temperature starts to rise. The increase of the temperature is
undamped and continuous, as no physical effect in the opposite direction (an increasing
heat flow to the environment according to the rising temperature) exists. Therefore, no
new equilibrium condition is reached, resulting in an unstable control loop with respect
to systems dynamics. This behavior is called integral action.
Other instabilities
There are other forms of instability besides the integrating behavior, e.g. increasing
oscillations. Such behaviors can rather be found in mechanical systems (e.g. the
famous inverse pendulum). In process plants, such instabilities if appearing at all, are
mostly due to inappropriate controller tunings, and only rarely appear in open loop.
Consequences
Unstable control loops cannot be stabilized without a controller. Therefore, switching a
controller in such a loop to manual mode is not allowed for a longer time.
Hence, the recording of measurement data for the process identification (e.g. for the
PID tuner or the MPC configurator) via step experiments in open control loop is not
possible. The model type and the control algorithm of the MPC function block are also
inappropriate for unstable control loops. Therefore, the unstable part transfer functions
have to be stabilized by subordinated slave controllers before the application of the
MPC.

7.2.2 Examples of Unstable Control Loops
Level Control
If the level of a tank with continuous feed is to be controlled via an adjustable drain as
actuator (e.g. pump or valve with or without flow control), the control loop shows
integrating behavior.
An equilibrium condition of the level only exists if the drain is exactly equal to the feed.
The level permanently decreases until the tank is empty, if the drain is increased
Characterizing
stepwise starting atControl Loops
this equilibrium condition. In contrast the level permanently
Examples of the
increases until Unstable Control
tank overflows, if the Loops – Fixedstepwise
drain is decreased Drain starting at the
equilibrium condition.
Fixed drain Fixed drain with Natural drain Drain with flow
with pump pump and valve with flow control control and pump
VFeed VFeed VFeed VFeed
Important:
 Always control loop with integral behaviour
 Nonlinearities caused by pump and valve characteristics
SITRAIN
Pressure Control in Tanks

In some cases the pressure control in tanks behaves in a similar way as the level
control. The control loop shows an integral behavior, if the manipulated variable is a gas
feed (e.g. admission of inerts) and no pressure loss to the environment exists. Typically
a separate purge valve exists in such cases to discharge gases. The pressure controller
uses a split range function to access either the feed valve or the purge valve.
Position Control
The control loop shows integrating behavior if the position of mechanical parts is
controlled and the speed of the actuator is available as manipulated variable. An
"equilibrium condition" without move in the position only exists for a speed equal to zero.
The valve actuator is a common example for position control in process plants.
However, the valve position controllers are mostly integrated in the corresponding
actuators and hence not an issue for the DCS.

Step response – Possible loop reactions
7.2.3 Determining the step response – Possible loop reactions
Manipulated value [%]

Process value [%]
D
C
A
50% Manipulated value [%]
Time
Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic - Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7 für die
Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-3895783401
SITRAIN Determining the step response of the process is the most important tool during the
Course ST-PCS7ASE
commissioning of control loops11is.- 5This test provides very important information
Siemens AG © 2012
for the
parameterization of the controller.
The step response of the loop is the reaction at the measured value of the process to a
stepwise change of the manipulated variable (actuator) with open loop. This response is
the result of the sum of all factors in the loop, e.g. dead times, time delays and
integration times and process gain factors.
For the procedure of determining the step response, it is important to start from a stable
state and to wait for a stable state after the step change.
An unambiguous classification of all control loops existing in practice is almost
impossible. There are different control loop types, which have to be treated separately.
The step response not only provides the information about the loop type, but the user
can also derive a number of time constants and identifiers from the recordings, which
will be important for configuring the controller.
First recording
In order to determine the step response, you should apply a constant manual output
(e.g. 50%) and wait for the process to settle resulting in a stable situation.
The following reactions are possible:

 Control loop A shows a mere lag time characteristic (e.g. pressure control loops). The
measured value reaches a stable end value.
 Control loop B basically also consists of a time lag behavior with a creeping response
(e.g. temperature control loops). The measured value initially behaves as in loop A,
but doesn’t reach a stable condition because of parallel lag factors with different time
constants.
 Control loop C is an oscillating loop. This can be caused by internal, physical links to
other processes or by subordinate PI (D) controllers (e.g. cascade control).
 Control loop D shows an integral factor (e.g. level in a closed tank).

7.2.4 Loops with a pure lag time behaviour
Loops with a pure lag time behaviour
Process value [%]
100
80
60
XO
XI
40
20
0
Time
TU TG
Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic - Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7 für die
Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-3895783401
SITRAIN
Course ST-PCS7ASE
After activating the recording device
11 - 6
a constant manual output value (e.g. 20%) should
Siemens AG © 2012
be issued. Then you have to wait for a stable state in the process. Afterwards, another
constant output value (e.g. 80%) should be output and again, you have to wait until a
stable state is reached. The loop gain can be calculated as follows:
Kps = XI [%] / XO [%]
XI is the absolute value of the actuator step and XO is the absolute value of the step
response. The settling time TG and the dead time TU are determined graphically. To do
so, you have to draw a tangent line in the point of inflection of the measured value trend.
The intersections between this tangent line and the values X 1 (old measured value) and
X2 (new measured value) determine the time values T G and TU.
If this procedure is repeated with further, higher manipulated values, a manipulated
value can surely be found, of which the resulting measured value is in the neighborhood
of the planned setpoint. Afterwards, the same steps are executed in reversed order (e.g.
manipulated value 80%, 50%, 20% and finally 0%).

First statements
7.2.5 aboutabout
First statements the loop behaviour
the loop behavior
Process value [mbar]
2000 Planned
setpoint
1600
1200
800
400
0
Manipulated value [%] Time [s]
100
80
60
40
20
0
Time [s]
Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic - Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7
für die Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-3895783401
SITRAIN
Course ST-PCS7ASE
After analyzing the recordings of this procedure, it is possible to makeSiemens
11 - 7
the first
AG © 2012
statements about the loop behavior.
The loop is symmetrical. The most important time constants are more or less the same
in positive resp. negative direction. Furthermore, the loop is linear, which means that the
most important time constants are the same at 20% and at 80% and have a resulting
value of about 15s. The loop shows pure time lag behavior (of lower order) and the
actuator is well dimensioned.
An actuator output of 50% to 80% delivers the desired setpoint. The actuator has
enough positioning reserve in both directions. Raising the output value by 33% (from
66% to 100%) results in a pressure raise of 850 mbar. In relation to the total range of
2500 mbar, this also corresponds to 33% which results in a loop gain of about 1,0. The
control loop can be adequately controlled (T G / TU > 10).
7.3 Overview of the APC tools in the PCS 7 Libraries

With the APC-Library of Simatic PCS 7 for the first time advanced process control
functions are included in the scope of delivery of the distributed control system (DCS).
Besides the core control algorithms, there are also the related process tag types and
software tools for computer-aided controller configuration available without extra charge.
The APC functions can be divided in three classes:
 Control performance management (CPM)
 Extension to PID control
 Multivariable control

7.3.1 Procedure to Improve Plant Performance
MV: manipulated variable

CV: controlled variable
MIMO control: multi-input multi-output
SISO control: single-input single-output
For the improvement of plant performance using APC tools, a typical procedure with
several steps is established. This description however has to be considered as a rough
framework: during individual applications some steps can be skipped because prior
knowledge is available, or some intermediate steps or iterations are required.
Some extensions to PID control like override control, cascade control, ratio control or
split range control are of structural nature: they are not visible in the figure above, but
they are applied if the respective structure is found in the setting of the task.
If all trials in the SISO case fail, the allocation of MVs and CVs has to be checked, or
actually there is a need for MIMO control (orange arrow).
After successful commissioning, APC functions as well as conventional control loops
should be subject to control performance monitoring (green arrow).
7.3.2 Control performance management
The generic term control performance management includes control performance

monitoring and optimization of control loops.
Empirical studies have shown that many of the control loops in process industries do not
fulfill their requirements properly and there is large potential for improvements. However
not everybody is aware of this.
ConPerMon
Each control loop to be monitored is by default equipped with a dedicated performance
monitoring function block (ConPerMon), like designated in the process tag types of the
Advanced Process Library. Using these process tag types, the engineering effort for
manual linking of monitoring and controller function blocks can be reduced.
In steady state process operation this monitoring function block calculates the following
stochastic features of control performance:
 Mean value, variance and standard deviation of controlled variable,
 Mean value of the manipulated variable and control deviation, Control performance
index,
 Estimated steady state process gain.

For setpoint steps, the following deterministic features of control performance are
evaluated:
 Rise time, settling time and settling ratio,
 Overshoot absolute and relative to the step height.
Other statistical and graphic evaluations of the signals in the control loop over longer,
freely selectable periods are available in the faceplate of the ConPerMon block.
7.3.3 Extensions to PID Control
This generic term summarizes different solution approaches that can be realized by
clever combination of PID controllers with other standard function blocks, and that are
offered as process tag types in PCS 7 Advanced Process Library.
Examples
 Override Control
 PID Gain-Scheduling
Split-range Control
 Smith Predictor Control for Dead time Processes
 Dynamic Disturbance Compensation (Lead-Lag Feed forward Control)
A PID closed-loop controller can use a Split-Range block downstream of the

Split-range Control
controller output to distribute its manipulated variable to several actuators that
A PID closed-loop
influence the samecontroller
control can use a Split-Range
variable based on block downstream
different physical of the controllerand in
principles
output to distribute its manipulated variable to several actuators that influence the same
different
control directions.
variable based A on
typical example
different physicalof such an
principles andapplication is a temperature
in different directions. A
control,
typicalwith heating
example viaanaapplication
of such live steamis avalve and cooling
temperature control, via
withaheating
cooling viawater
a live valve.
steam valve and cooling via a cooling water valve.
SITRAIN
SP-PCS7ZWS / 04 Introduction of APC Tools Page 14 Siemens AG © 2011

SIMATIC PCS 7 Control
Cascade AS Engineering
A cascade
Cascade Control control involves two or more PID controllers connected in series. The
manipulated variable of the primary controller is interconnected to the external
A cascade control involves two or more PID controllers connected in series. The
setpoint of the secondary controller so that both control loops are nested.
manipulated variable of the primary controller is interconnected to the external setpoint
of the secondary controller so that both control loops are nested.
Input Output
disturbance disturbance
Setpoint Override
Master Control
Controller
Slave
Auxiliary Main Process
Controlled
Controller Variable
Process
In override control, two or more controllers share a common actuator.

Override
Depending on the current process state, a decision is made as to which
SITRAIN Control
SP-PCS7ZWS /controller actually
04 Introduction of APC Tools hasPage
access
15 to the actuator; in other words,
Siemens AG © 2011 the variou
In override control, two or more controllers share a common actuator. Depending on the
controllers
current processcanstate,
override each
a decision other.
is made as to which controller actually has access to
the actuator; in other words, the various controllers can override each other.
SITRAIN
SP-PCS7ZWS / 04 Introduction of APC Tools Page 16 Siemen

PID Gain-Scheduling
Many processes have a non-linear response due to non-linear physical, chemical or
thermodynamic effects. When such a process needs to be kept in the close vicinity of a
fixed operating point, the transfer response can be linearized around this operating
point. A linear PID controller can be designed for this linearized transfer function. If,
however, the process has a strongly non-linear response and/or operates at different
operating points, no constantly good control response can be expected throughout the
entire operating range. Due to the non-linearity, various gain factors or process time
constants are in effect at different operating points. In keeping with this, different
controller parameters will be considered to be optimum.
Smith Predict Control for Dead time Processes

A dead time can be recognized from the observation, that after intrusion of an MV move,
there is no reaction of the controlled variable at all for a certain time (the dead time). In
processes with large dead times θ (e.g. θ > 0.25 t1 relative to the dominating lag time
constant t1), a standard PI controller must be tuned very slowly and compromises must
therefore be accepted in the control performance.
The control performance can be significantly improved with a Smith predictor that can
be derived from the IMC principle (Internal Model Control) of model-based control.

Dynamic Disturbance Compensation (Lead-Lag Feed forward Control)

Feed forward disturbance control can be used when a known, strong disturbance affects
the process and its cause can be measured. In these cases, the following general
strategy applies: "Feed forward control as much as possible (as much as known in
advance and described by a model), feedback control as much as necessary (the rest
including the model error and immeasurable disturbances)".
Multi-Variable Control (MPC: Model Predictive Control)

If there are several manipulated and controlled variables (MVs and CVs) in one unit,
that are interacting with each other, you are dealing with a multivariable control situation
(MIMO control: multi-input multi-output, as opposed to SISO control: single-input single-
output). The impact of each MV to each CV is described by a part transfer function.

7.3.4 Cost Benefit Analysis
7.3.5 Objectives for APC solutions

Objectives Aspects
Productivity and Increase throughput
Profitability Minimize energy consumption
Reduce changeover times, e.g. for changes of operation mode, raw material or
target products (grade changes)
Increase yield
Reduce processing time
Quality Increase repeatability; make process operation more steady and smooth
Minimize variance of quality parameters
Reduce effort for chemical analyses
Reduce production of giveaway or inferior qualities
Operability and Increase tolerance against fluctuations in raw material
Availability Reduce sensitivity to disturbances
Increase plant uptime
Avoid plant shutdowns and reduce shutdown times
Increase plant availability, flexibility and robustness
Operator Control Cope with change of operators/shifts
Reduce operator workload
Increase operating comfort
Safety Increase occupational health and safety
Increase process and operational safety
Ecology Minimize environmental impact, pollution and wastage
Minimize emissions
Save effluents and sewage
7.3.6 Further information
 “How to Improve the Performance of your Plant Using the Appropriate Tools of
SIMATIC PCS 7 APC-Portfolio?”
A white paper issued by Siemens in October 2008
© Siemens AG 2008. All rights reserved.
 Template Descriptions in the Manuals of PCS 7 Standard and Advanced Process
Library:

Further Information
Further Information
SITRAIN
SITRAIN

PCS7 Library V7.1
Example
7.3.7 projectExample
Available with APC-Templates
Project in PCS 7 with APC-Templates
Example project with APC-Templates in the

PCS 7 Library V7.1
PCS7 Advanced Process Library

Example project with APC-Templates
Example project with APC-Templates in the

PCS 7 APL

APC templates
7.3.8 Availablein PCS7 LibraryinV7.1
APC-Templates PCS 7
APC templates in
PCS 7 Library V7.1
APC templates in APL Library V8.0
APC templates in the

PCS 7 APL

7.4 PID algorithm

PID algorithm: P-action
7.4.1 P-action
Proportional term Pout  K P et 
SITRAIN
SP-PCS7ZWS / 05 Control Performance Management Page 3 Siemens AG © 2011
Control deviation (error)
The difference between the command variable w (setpoint) and the controlled variable x
(process variable) gives the actual input variable for a controller.
et   wt   xt 
The “pure” proportional controller

The proportional action controller multiplies the control deviation (the input variable) by a
constant KP, also called the proportional gain. The result is provided as output variable
without any lag of time.
Pout  K P et 
A high proportional gain results in a large change in the output for a given change in the
error. If the proportional gain is too high, the system can become unstable. In contrast, a
small gain results in a small output response to a large input error, and a less
responsive or less sensitive controller.
Offset
The most important characteristic of a pure P-control is the offset. A pure proportional
controller will not always settle at its target value, but may retain a steady-state error.

Example: permanent cooling-off by the ambience

Specifically, drift in the absence of control, such as cooling of a furnace towards room
temperature, results in a systematic error in case of a purely proportional controller. If
the drift is downwards, as in cooling, then the offset will be below the set point, hence
the term "droop".
Bias
The steady-state error is an inherent defect of purely proportional control. It may be
mitigated by adding a compensating bias term. This means in case of a droop, to set
the controller setpoint above the true desired value.
P-term
The better way for the elimination of the steady-state error is the combination or
corrected by adding an integral term.
If the proportional gain is too low, the control action may be too small when responding
to system disturbances. Tuning theory and industrial practice indicate that the
proportional term should contribute the bulk of the output change.
Configuration in PID Controller blocks

Standard Library APL
Proportional gain KP Gain Gain
Sign of the controller gain NegGain = 0
(positive controller gain)
NegGain = 1
(negative controller gain)
Activation of the P-action P_Sel = 1 PropSel = 1
Display of the P-action P_Part

PID algorithm: PI-action

7.4.2 PI-action
I out  K i  e  d
t
Integral term
0
SITRAIN
The “pure” integral controller
The control deviation is accumulated over the time (integration). The sum is multiplied
by a constant Ki, also called the integral gain.
I out  K i  e  d
t
0
As long the control deviation is applied, the manipulated variable is increasing.
A purely integral control is slow in comparison to any other control algorithm, but it is
able to eliminate completely the control deviation.
Integral term
Adding an integral term to a P-controller eliminates his typical characteristic of the
steady-state error and retains the fast response.

Integral action time in seconds TN TI
Activation of the I-action IntSel = 1
Freezing of the integrator INT_HNEG = 1 IntHoldNeg = 1
(depending on the direction) INT_HPOS = 1 IntHoldPos = 1
Display of the I-action I_Part

PID algorithm: PD-action

7.4.3 PD-action
et 
d
Derivative term Dout  K d
dt
SITRAIN
D-action (Derivative term)
The D-action considers the slope of the control deviation by calculation of a rate of
change. In other words, the derivative with respect to time is formed and multiplied by a
constant Kd, also called the derivative gain.
et 
d
Dout  K d
dt
The D-action makes a controller able to react already on the “annunciation of a change”.
The controller can react on deviations faster than other algorithms.
Sensitivity to noise
If the sensor signal is noisy, the noise is amplified by the derivative term. Inn case of a
large derivative gain and sufficient noise amplitude of the input signal, the control loop
(the process!) can become instable.
Offset
The disadvantage of purely proportional controllers, the steady-state error, also exists
for a PD-controller!


Derivative gain TV / TM_LAG DiffGain = TD /

(Time lag of D-action)
Derivative action time in seconds TV TD
Time lag of D action in seconds TM_LAG TD / DiffGain
Activation of the D-action TV > 0 TD > 0
Display of the D-action D_Part
PID algorithm: PID-action

7.4.4 PID-action
P K P et 
K i  e  d
t
I 0
et 
d
D Kd
dt
SITRAIN
Graphic
SP-PCS7ZWS / 05 Control representation
Performance Management ofPage
the 6PID-algorithm Siemens AG © 2011
Graphic representation of the PID-algorithm
Ideal parallel type: Standard type:
Kp
Ki Kp 1 / TN
Kd TV
Possible conversions:
Standard PID form
Ki encountered
 is most often K p / TN in industry. TN  K p / Ki
 Kp gain is K d  K p to
applied  TVthe I , and D terms
out out
TV  K d / K p
SIMATIC PCS 7 – Advanced

SITRAIN Process Control (APC) with APL
Course folder, V8.2.0, SP-PCS7ZWS
ST-PCS7ASE / 05 Control Performance Management Page 7 Siemens AG © 2011 7 - 23
 
MV t   K p  et    e d  Td et 
1 t d
 Ti 0 dt 
In this standard form, the parameters have a clear physical meaning:
 Ti is the integral action time (TN in the standard library, TI in the APL)
 Td is the derivative action time (TV in the standard library, TD in the APL)
Ideal parallel form

 is the most general and flexible form.
 The parameters are treated as simple gains.
 The parameters have the least physical interpretation and are generally reserved for
theoretical treatment of the PID controller.
MV t   K p et   K i  e d  K d et 

t d
0 dt
The gain parameters are related to the parameters of the standard form through:
K i  K p Ti and K d  K pTd
Note on selecting the controller type

7.4.5 Note on selecting the controller type
P controller PI controller PID controller

• simplest type of controller • most often used controller • higher control quality than with
• can be used with integrating type the PI controller
processes (for example, level • capable of setting the • faster ramp times for setpoint
controls) and with slave actual value in the closed step changes
controllers of cascades (PI/P control loop to the exact • reduced control deviations with
cascades). value of the setpoint. disturbing influences
• Disadvantage: steady state • preferred when actual • Disadvantage: Higher actuator
errors have to be tolerated values are very noisy or activity, however, may also
• Exception: With integrating when especially sensitive mean higher energy
processes, a P controller mechanical actuators consumption or wear.
operates without a steady (such as valves) are
involved • With binary actuators controlled
state error if disturbances only by pulse-duration modulation
affect the output of the (electrical heaters, for example),
process and not the input of the roughness of the actuating
the integral action signal has no meaning and PID
controllers can therefore usually
be used.

The PID algorithm
Deadband SIMATIC PCS 7 AS Engineering
7.4.6 Deadband
Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic - Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7
für die Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-3895783401
The deadband is used for suppressing very small control errors. It’s an area of
a signal range or band where no action occurs (the system is dead). The purpose is to
SITRAIN
prevent oscillation or repeated activation-deactivation cycles (called 'hunting'
Course ST-PCS7ASE in proportional control systems).
11 - 35 Siemens AG © 2012
The picture above is an example of a 5% deadband function for the control error.
The control error is formed from the effective setpoint SP and the process value
PV (ER = SP - PV_Out) and is available at the ER output.

To suppress disturbances in the steady state, you can assign a dead band (Deadband):
Width of dead band DEADB_W Deadband
DEADB_W = 0: Dead band is disabled Deadband = 0: Dead band is disabled
DEADB_W > 0: Dead band is enabled Deadband ≠ 0: Dead band is enabled

The PID
SIMATIC PCS 7algorithm
AS Engineering
Filtering
7.4.7 Filtering
Current Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic -

Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7 für die
value Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-
U(t) 3895783401
0,63 V(t)
0
TM_LAG t
U = 0 wenn t < 0
Input step:
U = 1 wenn t > 0
Disturbances at the measured value (PV) (e.g. high-frequent superpositions in the
infeed, unallowed reference potential changes, disturbance induction in the
SITRAIN
Course ST-PCS7ASE measurement wiring …) can be 11 suppressed
- 37 or at least reduced by using filterAGfunctions.
Siemens © 2012
The easiest and most used example of such is filter is the first order lag (PT1).
Other possible filters are:
 Second order filter
The second order filter uses half your time constant in each of the two cascaded first
order filters. This results in an overall time constant equivalent to a first order filter.
 Butterworth second order filter
The Butterworth is a high performance second order filter. It is a good filter to
eliminate noise since it causes the lowest quantity of phase addition for the highest
quantity of noise reduction for any of the filters. On a step change, a Butterworth will
have a smaller overshoot.
 Averaging filter
The averaging filter is a moving average filter - for every sample interval it gives the
values average of the previous time constant. If you have a specific frequency you
would like to remove, setting the averaging filter time equals to the period of the noise
or to a multiple of the values and should completely remove it (period is the inverse of
frequency).

7.4.8 PID Controller Block in the APL: PIDConL in Brief
The block is a PID controller with continuous output signal (manipulated variable). It is
used to activate a final controlling element with continuous action input.
The block functions following the PID algorithm with a delayed D action and an
integrator with double precision.

"Manual" and "Automatic" modes for control blocks

In "manual mode", the control settings for the device are made manually by the
operator. The operator decides how to change the block's manipulated variable (output
signal). The manipulated variable can be analog or binary.
In "automatic mode", the control settings for the controller are made automatically as
calculated by the block algorithm.
Changing between operating modes

The switchover between manual and automatic modes takes place as shown in the
following schematic:
 Switchover initiated in the faceplate (ModLiOp = 0): The changeover between
operating modes is carried out in the standard view of the faceplate. In the function
block, the parameters ManModOp for "manual mode" and AutModOp for "automatic
mode" are used.
If both signals (ManModOp =1, AutModOp = 1 ) are set, ManModOp = 1 has priority.
 Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1): The
switchover between the operating modes is carried out with an interconnection on the
function block. The parameters ManModLi for "manual mode" and AutModLi for
"automatic mode" are used in pushbutton operation. In switch mode (requirement:
Feature Bit 4 = 1) connection ManModLi is used exclusively.
If both signals (ManModLi =1, AutModLi = 1 ) are set, ManModLi = 1 has priority.
Program mode for closed-loop controllers - interface for higher-level control functions
The interface for primary controller functions (external Advanced Control software
package) provides primary controller functions, which run on an external PC as an OPC
client, the option of using the control from the controller function block and specifying
the setpoint or manipulated variable from a remote location. This procedure is called
program mode.
You can use the Feature bit 19 (Enabling program mode) to specify whether or not the
controller block is intended for program mode.
Program mode requires an enable signal (input parameter AdvCoEn = 1) from a central
control block. If this enable signal goes from 1 to 0, for example, due to errors in the
OPC communication, the controller block returns to the operating mode it had before
program mode.
Selecting the type of program mode

There are two types of program mode:
 Program mode with setpoint (in automatic mode only)
If you set the input parameter AdvCoModSP = 1, the analog value provided by the
OPC client (AdvCoMV) is used as an external setpoint for the controller. The
controller and faceplate otherwise react as they do with automatic mode and an
external setpoint. Refer to section Setpoint input - internal and external for more
about this.
Requirements for program mode with setpoint:
 AdvCoModSP = 1,
 AdvCoEn = 1,
 The controller is in automatic mode.

 Program mode with manipulated value (in manual mode only, not for step
controllers without position feedback)
If you set the input parameter AdvCoModSP = 0, the analog value provided by the
OPC client (AdvCoMV) is used as an external manipulated value for the controller.
The algorithm of the PID controller is bypassed. The controller and faceplate
otherwise react as they do with tracking (MV_TrkOn = 1).
Requirements for program mode with manipulated value:
 AdvCoModSP = 0,
 AdvCoEn = 1,
 The controller is in manual mode.
Setpoint specification internal & external

First you define whether the setpoint specification is to be carried out by means of a
CFC/SFC program or by means of the faceplate. In the next step you specify whether
the internal or the external setpoint is to be used.
 Setpoint specification by means of faceplate or interconnection
With the SP_LiOp parameter, you define whether the setpoint will be set by a
CFC/SFC program or using the faceplate.
 Parameterize Sp_LiOp with 0 so that the setpoint specification is carried out by
means of the faceplate.
 Parameterize SP_LiOp with 1 so that the setpoint specification is carried out by
means of a CFC / SFC program.
 Setpoint specification internal & external
You have to set the corresponding parameters depending on how the setpoint
specification is to be carried out.
If the setpoint is set in the faceplate (SP_LiOp = 0), you have to set the parameter:
 SP_IntOp = 1 in order to achieve an internal setpoint specification by means of
the faceplate.
 SP_ExtOp = 1 to have an external setpoint set in the faceplate.
If both signals are set, SP_IntOp = 1 has priority. If the setpoint is set by a CFC /
SFC program (SP_LiOp =1), you have to set the parameter:
 SP_IntLi = 1 to have an internal setpoint set by a CFC / SFC program.
 SP_ExtLi = 1 in order to achieve an external setpoint specification by means
of a CFC / SFC program.
If both signals are set, SP_IntLi = 1 has priority.

PID Controller Blocks in the APL
Smooth
SIMATIC in
PCSBrief
7 AS Engineering
7.4.9 Signal Filter Block in the APL: Smooth
Analog input (Process value) Output of the corrected process value

Butterworth filter time constant [s] 1 = Maverick (outlet) detected
Settings for maverick (outlier) detection Output of current error number
Feature parameter
1 = Filter active
Restart the filter algorithm
Area of application for Smooth

The block is used for the following applications:
 Butterworth low-pass filter
 2nd order with maverick detection
How it works
The block is used as a low pass filter. This filter allows the signal portions with
frequencies below the cutoff frequency to pass practically unattenuated, whereas
portions with high frequencies are attenuated. The enables you filter out high frequency
interference in the signal (for example, signal noise) and smooth the signal.
In comparison to a first order low pass filter, the Butterworth filter has the advantage that
the transition from the passing section to the blocking section is sharper in the Bode
diagram. If the frequency area of the interference is known, it can be filtered out with
minimal influence on the wanted signal.
The maverick detection monitors adjacent signals. If signal mavericks are detected, they
are not processed any further. The block outputs the last valid signal.
 A maverick in a continuous physical measurement is a numerical value that changes

from one sampling point to another more than would be physically plausible. In other
words, the difference between two neighboring values is greater than a specified
tolerance range.
The signal status is passed from the input directly to the output.
This block provides the standard function Forming and outputting the signal status for
mathematical blocks. The signal status for the block is formed using the parameter
PV.ST and output at the output parameter CleanPV.
 You can find additional information on forming the signal status under Forming and
outputting the signal status for mathematical blocks.

Configuration
Use the CFC editor to install the block in a cyclic interrupt OB (OB30 to OB38). The
block is also installed automatically in the startup OB (OB100).
You then set the filter time constant for the low pass filter to achieve the desired effect.
To set the filter time constant, it is helpful to observe the original and filtered signals in
the CFC trend plotter. The filtered signal should be smoothed as required but not too
delayed. An increase in the filter time constant increases the smoothing effect but also
increases the delay. Typical starting values for the time constant are around ten times
the sample rate of the signal.
There is a sample project for the Smooth block (APL_Example_xx, xx refers to the
language variant) with an application case for this block:
Filtering of noisy measured values in a control loop

The block provides the following smooth functions:
 Restart low pass filter
You can recalculate the coefficients of the Butterworth filter. To do this, you must
restart filter (Restart = 1).
The filter algorithm is then reinitialized, exactly as it is when the CPU is restarted or a
change is made to the count value at the input parameter TimeConstant.
The coefficients of the Butterworth filter are recalculated and the internal state
memory of the filter is initialized so that the CleanPV output parameter is equal to
the PV input parameter.
 Activate and deactivate maverick detection
The maverick detection (OutlDetOn = 1) monitors the process value PV for the
difference between two sequential sample values. These have to be within a
tolerance range you have specified (OutlTreshold).
If the tolerance is violated, the maverick is set to the most recent valid value. The
most recent valid measured value is then held constant by the block for a maximum
of OutlCycles sample steps. If the maverick continues longer than this, it is
accepted as a valid measured value.

7.5 Control Performance Monitoring (CPM)

ControlControl
7.5.1 Performance Monitoring
Performance Index (CPM)
Control Performance
Control Performance
Setpoint [%] Source: J. Müller, B.-M. Pfeiffer, R. Wieser: "Regeln mit Simatic -
Praxisbuch für Regelungen mit SIMATIC S7 und SIMATIC PCS7 für die
Process value [%] Prozessautomatisierung" 4. Aufl. 2011, Publicis Publishing, ISBN 978-
3895783401
100
80
60
40
20
Time
0
In general, the control performance is a measure for the quality of the control function
SITRAIN or, more scientifically, the control performance is a measure for the sum of all control
errors after a setpoint change resp. after a disturbance. The picture above shows two
different process reactions to the same setpoint step with different controller settings.
The “aggressive” controller setting is indicated in gray, while the more “conservative,
sluggish” controller setting is indicated as hatched. The bigger the surface between the
setpoint and the process value, the worse the control performance is, according to the
“linear absolute value quality criterion”. In the picture, both surfaces are roughly equal,
so both settings are equally good, resp. bad.
In practice, the more sluggish setting is used much more often than the aggressive
setting, because this behavior spares the plant.
 See [1005] Application note 32486166 CPM - 11_2008 for more information about
control performance monitoring.

Control Performance Monitoring (CPM)
Control Performance Index
Control Performance Index
Mean value Variance Standard deviation
Variance of controlled variable in

control loop "good" status
Variance of the
process value
Course ST-PCS7ASE
Due to the approach, the variance
7 - 42
PV_Variance as second moment requires the
calculation of differences of each current measured value from (constant!) mean value.
The standard deviation as the square root of the variance is easier to interpret because
it has the same physical unit as the measured value.
Within the function block, however, a variant of the calculation is used that saves
computing time.
The control performance index CPI (Control Performance Index) in the unit [%]
describes the current variance of the controlled variable relative to a benchmark.
The CPI moves in the 0…100% range. If the current variance corresponds to the
benchmark, the index reaches the value 100. If, on the other hand, the current variance
increases, the control performance index drops accordingly. Ideally, the benchmark is
obtained in a defined good state of the control loop.
 The mean value of a variable relating to an ergodic stochastic process can be

determined from a sliding time window with the length
n = TimeWindow / SampleTime.
An ergodic process in mathematical statistics is a stationary process, in which the
expected value can be estimated by generating the mean value over a time period of
infinite length.

7.5.2 Control Performance Monitoring in the APL: ConPerMon in Brief
Area of application for ConPerMon

 Permanent monitoring of control performance of control loops for early detection of
problems as they develop
 Stochastic characteristics of the control performance with the process in a steady
state
 Mean value, variance and standard deviation of controlled variable
 Mean value of the manipulated variable and control deviation
 Control performance index
 Estimated steady state process gain
 Deterministic characteristics of the control performance with step changes in the
setpoint
 Response time and settling time and the settling ratio
 Overshoot absolute and relative to the step height

Control Performance Monitoring (CPM) –
Area of application for ConPerMon
Definition of limits
for control
performance and
overshoots
Evaluation of Evaluation of a
steady-state step response
control behavior

Other statistical and graphic evaluations of the signals in the control loop over longer,
freely selectable periods are available in the faceplate of the ConPerMon block.
In an overview representation of a plant or unit, you can obtain a clear picture of the
status of all control loops based on ConPerMon block icons (indicator light function).
The aim is to detect problems as they develop and to focus the attention of the user on
the control loops in a plant that are no longer operating correctly.


7.5.3 AS functions
Configuring Configuring AS functions
Manipulated
value
Naming convention:
Setpoint
add “_cpm”
Run sequence:
1 controller
2 ConPerMOn
Process
value
Control loop
closed?

For a PID controller an assigned CPM block is installed into the same CFC plan and
interconnected with the controller. The CPM block is connected with the assigned
controller block via a name convention: The name of the CPM instance corresponds
entirely to the name of the controller instance plus the ending "_cpm".
General Procedure
To configure the CPM block in CFC, proceed as follows:
1. Open the plan with the PID controller block in the CFC editor.
2. Declare the PID controller block as the predecessor for installing the next block.
To do this click with the right mouse-button and select "Predecessor for Insertion
Position“ from the submenu.
3. In the dialog box "Predecessor for Insert Position" you select to which OB the
subsequent blocks are installed (in this example OB35, i.e. the 100ms cycle).
4. The field with the runtime properties in the block header is then shaded in green.
5. Draw the CPM block from the block catalog next to the PID controller block via Drag
& Drop. You find it in the “CONTROL” family.
6. Open the properties dialog of the CPM block and change its label to the name of the
PID controller block followed by “_cpm”.
7. Interconnect the CPM block with the PID controller block.
8. Compile the S7 program and load it into the automating system.


7.5.4 Configuring OS functions
Configuring OS functions
Direct jump
button with
standard text
Course ST-PCS7ASE
Apart from the OS compilation 7no special configuration steps are
- 46
necessary.
The function of Control Performance Monitoring is executed completely in the AS,

therefore no access to any archived values in the OS is required.
Apart from the block icon for the PID controller a separate block icon is generated for
the CPM. This can be moved on demand into a higher-level overview screen. The
respective faceplate can also be opened from the faceplate of the PIDConL.
Predefined button in faceplates of controller blocks

You can open the standard view of the ConPerMon block from the standard view resp.
parameter view of controller blocks (e.g. PIDConL):
 To do this, you need to interconnect the output parameter CPI of the ConPerMon
block to the input parameter CPI_In of the controller block.
 The labels of the buttons cannot be changed here.
Use of free-configurable buttons for direct jump

Free-configurable buttons for direct jump are a APL standard feature:
In the properties of the block icon in WinCC, under Configurations, assign the desired
text to the attribute UserButtonText1 or UserButtonText2.
From APL V8.0 there exists a better way, how to define the labelling text in CFC:
 You can change the button labels in the "OS additional text" attribute to input
parameters SelFp1/SelFp2.

SIMATIC PCS
Control 7 AS Engineering Monitoring (CPM)
Performance
Startup of the CPM
7.5.5 Startup of the CPM
PID in auto mode

SP = operating point
Specify time window
Wait for steady state
Wait while the time

window elapses
Initialize ConPerMon
Start the
initialization from ConPerMon initialized
the Parameter view CPI ≈ 100%
Initialization of CPM
After successful commissioning and optimization of the PID controller to be monitored,

the ConPerMon block is initialized while the process is in a steady state and it stores the
corresponding characteristic values as reference values.
Follow the steps outlined below:
 Change the PID controller you want to monitor to automatic mode and set the
setpoint to the typical operating point. This operating status is intended to represent
the normal operation of the process; in other words, the entire plant/unit should be
running under production conditions. Monitor the process with a trend writer (CFC
trend in the Engineering-System or WinCC Online TrendControl on the Operator
Station) and wait until the process has settled
 To specify the length TimeWindow of the sliding time window, monitor the
PV_Variance block output of the ConPerMon block in a trend. The time window
should be long enough to keep the variance fairly constant in the relevant decimal
places.
If the selected time window is too short in relation to the time constants in the control
loop and the disturbance signal spectrum, the variance will have too much noise and
no useful information.
If the selected time window is too long, it takes longer before any deterioration of the
control quality is detected by the ConPerMon block. It also takes longer following a
step change in the setpoint before the monitoring of the stochastic characteristics can
be resumed.
A good starting value for the TimeWindow parameter is 10 times as long as the
longest process time constant or 20 times as long as the reset time of the PID
controller.

If the controller
 is set perfectly,
 has achieved a steady state,
 the time window has been defined and filled with values from the steady state,
the ConPerMon block can be initialized. You do this by clicking the "Initialize" button in
the parameter view of the ConPerMon faceplate or by setting the InitRefVar = 1
parameter in the CFC block. This saves the PV_Variance parameter in the current
time window as a reference value for calculating the control quality in the block along
with reference values for manipulated variable and process variable.
Result of successful initialization

The Control Performance Index CPI should now be approximately at 100% and
therefore indicate that the control loop is operating correctly. Due to stochastic
fluctuations, the CPI can also temporarily exceed the 100% mark. If, however, the CPI
Evaluation of stochastic characteristics of the control
drops by a significant amount over a longer period, this indicates deterioration of the
performance (Steady
control state)
performance.
7.5.6 Evaluation of stochastic characteristics of the control performance

(Steady state)
Set the time window here, in which the

statistical evaluation is to be performed.
Current benchmark for CPI calculation
Reference value for process value and

the manipulated variable
The CPI moves in the 0 …100% range. If the current variance corresponds to the
benchmark, the index reaches the value 100. If, on the other hand, the current variance
increases, the control performance index drops accordingly. Ideally, the benchmark is
obtained in a defined good state of the control loop and stored when the ConPerMon
block is initialized.
It does not matter if the CPI temporarily reaches values higher than 100%. A CPI >
100% only means that the variance of the controlled variable isSITRAIN - Siemens AG © 2016
currently somewhat
lower than in the reference state. Other alternatives for determining the benchmark will
be explained in a separate section.

CPIPCS
SIMATIC suppression
7 AS Engineering
CPI suppression
ConPerMon
CPI_Suppress Active CPI message suppression

CPI_SuRoot CPI message suppression was
Cancel the suppression of control
performance alarm during a step caused in this control loop.
response manually BreakSuppress
Low-pass filter for CPI,

CPI_FiltFactor
constant for filter time
= TimeWindow x CPI_FiltFactor
Manual suppression of CPI ManSupprCPI

calculation and message, e.g.
during expected disturbances
If a step change in the setpoint is detected in a control loop, the ConPerMon block
freezes the CPI value and automatically suppresses all messages relating to this. As the
user, you can also force the suppression of the messages manually via the binary input:
ManSupprCPI = 1
This setting is useful to avoid false alarms when known disturbances occur, for example
at a load change in a Conti process or a dosing procedure in a Batch process.
Optional filtering
If you consider that the calculated CPI signal is too strongly affected by noise, you can
smooth it using the integrated level pass filter (parameter CPI_FiltFactor) with the
filter time constant TimeWindow x CPI_FiltFactor.

Interpretation of results
Interpretation of results
Increase of CPI
• The time window was changed.
• CPI signal was smoothed before.
• Reference standard deviation > current value
Creeping decrease of CPI

• Abrasion, deposits
• Reference standard deviation < current value
Abrupt decrease of CPI

• Impact of external disturbances
• Setpoint step was not detected.
Creeping increase of process gain Steady-state error

• Should be in range of zero
• Abrasions, deposits
• Insufficient actuator
• Manipulated variable does not influence the process anymore
Remaining control deviation

The mean value of the control deviation in the sliding time frame is displayed in the
standard view of the CPM faceplate. For a controller with I-part (PI or PID controller) is
should be almost equal zero. If not the following problem causes are possible:
 The performance of the final control element is insufficient. As a result the controller
keeps going to the limit with its actuating signal. This may be due to unfavorably
dimensioned final control elements, changed operating conditions or also due to
wear.
 The manipulated variable required by the controller will not be effective in the process
as the final control element is defective or the communication is disconnected, for
example.
Changing or reducing the CPI

 Deterioration of the control performance due to changed control parameters,
changed final control element curve or changed control process parameters
 Stochastic fluctuations may lead to a temporary exceeding of the 100% mark. This
however is unproblematic.
In the following cases the CPI changes naturally without causing any problems in the
control loop:
 The time frame length was changed.
 The distorted CPI signal was smoothed
Changing the process gain

 Signs of wear in the process lead to a gradual change in process gain.
In many cases this affects the control performance.

 Sudden and temporary change indicates an external disturbance impact.

Such disturbances can be avoided by improved controller settings.
Should they occur more often, it may pay off to search for the causes.
Step evaluation
7.5.7 Step evaluation
Monitoring of deterministic characteristics of the control performance

Assessment of the control performance based on the response to a step change in the
setpoint is relatively simple. In the sense of automatic monitoring, the ConPerMon block
is capable of determining the essential characteristics of the control performance
directly from the signal changes so that when necessary a message or an alarm can be
generated automatically by the system.
The first thing to look for is always the overshoot if it is present and clearly distinct from
the noise level. For a positive step response,
OverAbso = max(PV) - SP > 0
is output where is for a negative step response (step response down), and negative
values
OverAbso = min(PV) - SP < 0
are also output.
For normalization, the absolute overshoot is related to the height of the step change in
the setpoint and is therefore always positive.
The relative overshoot (Overshoot) as a percentage is a measure of the damping of the
control loop. If this is more than 20 or 30%, the loop gain (gain of the controller
multiplied by the gain of the control system) is generally too high either because the
controller was badly set from the beginning or because the properties of the control
system have changed over the course of time.
Overshoot too large

If overshoot is significantly too high, the control loop is generating weakly damped
oscillations in the plant. The block sends a message to this effect if the relative
overshoot is above a specified limit.
An important parameter for monitoring the control performance is the overshoot. Too
large overshoots of the step response are due to a wrong gain setting of the controller
or changed control process. If the overshoot is too large, it helps in many cases to
reduce the gain of the controller.
Settling ratio too small

The settling ration, quotient of rise time and settling time, must be larger than 25%. If
Control Performance Monitoring
this is not the case, (CPM)
the reset time at the PID controller is set too slow, which causes a
slow leveling of the actual value with the setpoint value.
Alternatives for determining the benchmark
7.5.8 Alternatives for determining the benchmark
ConPerMon
RefStdDev Standard deviation of controlled

value in control loop "good" status
External reference values for
PV_Variance in control loop PV_VarMin Minimum observed value of the
"good" status RefVarExt process variance (slave pointer)
Internally calculated variance of RefVariance
controlled value in control loop
"good" status
Reference for manipulated variable MV_Ref
Reference value for controlled variable PV_Ref
Use of external reference value ReVaExOn
During planned commissioning of a plant with integrated ConPerMon, following

controller optimization, the ConPerMon block is initialized for every control loop and the
calculated variance stored as the benchmark for calculating the CPI.
Course ST-PCS7ASE - 52 set via the RefVarExt input

As an alternative, a benchmark7 can parameter
SITRAIN by©setting
- Siemens AG 2016
RefVarExtOn = 1. There are various ways of obtaining numeric values for the
benchmark:
 Take the lowest variance that was ever measured in this control loop since the
initialization of the ConPerMon block. This is displayed at the PV_VarMin output
parameter. This value is only useful when the control loop has been in a stable and
desirable operating state for a longer period of time at least once since the
initialization of the ConPerMon block.
 Take the variance of the control loop with a theoretical minimum variance controller
as can be obtained based on archived data using another supplier's CPM application.
This depends only on the process dead time and the disturbance model. This form of
CPI is known as the Harris index and represents a lower barrier that can generally
not be reached by a PID controller which is why CPI seldom reaches the value 100%
even by well-tuned controllers. Low CPI values provide the first indication that the
controller settings could be improved. You should, however, bear in mind that the
minimum variance is only a theoretically achievable value and that the minimum
variance controller has characteristics that are not desired in the real application, for
example extremely high manipulated variable amplitudes. With minimum variance-
based CPI, therefore, it is not worth making every effort to bring this as close as
possible to 100%.

7.6 Controller
Controller optimization
optimization using
using the the PID Tuner
PID Tuner
7.6.1 Introduction
Using the PID tuner, you can tune the following control blocks:
Using the PID tuner, you can tune the following control blocks:
PCS 7 V71 Library PCS 7 APL
CTRL_PID PIDConL
CTRL_S PIDConS (from V8.0 SP1)
FMCS_PID PIDConR
PIDStepL
A prerequisite for control by the PID tuner is that the selected controller block is
functionally compatible to a controller block from the PCS 7 library and known by the
PID tuner.
 The controller modules FM 355-2 C and FM 355-2 S have their own controller
optimization. Therefore, the PCS7 PID Tuner is not designed for optimization of the
Course ST-PCS7ASE FMT_PID block. 7 - 53 SITRAIN - Siemens AG © 2016
The PCS7 PID Tuner requires that the symbolic name CTRL_PID, CTRL_S,
PIDConL, PIDConR, PIDStepL or FMCS_PID is listed in the symbol table.
How it works
With the "Controller tuning" function, you determine the optimum controller settings for a
particular process. A wizard guides you through the individual steps.
The measured data of the controlled system is recorded. The optimum PID parameters
are calculated based on this data and prepared for further use.
You will find additional information on the use of the PID tuner in the corresponding
HELP file. You can call up this help by selecting a block on the chart in CFC and
activating the menu command
Edit > Controller Optimization
 See FAQ “procedure for controller optimization with the PCS7 PID tuner” for more
details:

7.6.2 Procedure for tuning a controller

PID tuner
Enable the PID Controller for optimization
Enable the PID Controller for optimization
Enable optimization
in the OS-Faceplate
or
in the CFC-Chart
PID tuner
Start the PID Tuner
Start the PID Tuner
1. Select Controller block
2. Start Optimization
PID Controller
 The PID Tuner will access to the instance DB of the controller block. The CFC should
be compiled and downloaded before PID tuning. There must be a connection
between the programming device or PC and the CPU.

PID tuner
Start the PID-Tuner Wizard
Curve recorder:
Actual values
shown as trend
csv files are used
to archive the trend
values
Start Controller
Optimization
Course ST-PCS7ASE
Using the "Curve Recorder" function,
7 - 57
you record the changes in the values of the control
loop parameters over a specified period of time and display these values as curves.
You can select up to four parameters for the recording (not with PID controllers).
You can simultaneously archive the curves to files during the recording. You can then
view and process the archived curves at a later time, for example, with MS Excel.
 When you are optimizing the PID controller parameters, the parameters are
permanently assigned to setpoint, actual value and manipulated variable. The fourth
curve field remains constantly grayed out.
When you select a curve with the curve selection switch, the scaling of the curve is
displayed. This is the scaling you have set in the "Settings" dialog box.
The controller parameter assignment (the main window of the standard PID control)
can also be manipulated if you have opened one or more windows of the curve
recorder.

PID tuner
Step 1: Prepare for measured value acquisition SIMATIC PCS 7 AS Engineering
Step 1: Prepare for measured value acquisition
Select the process

behavior
PID tuner
Step 2: Set process to starting point
Step 2: Set process to starting point
Select Operating mode

Closed control
loop behaviour
Open control
loop behaviour Enter starting
setpoint
PID tuner
You are intervening in the process in this situation!
Step 3: Enter the new setpoint
Step 3: Enter the new setpoint
Enter the new

setpoint

PID tuner
Step 4: Measured value acquisition
Step 4: Measured value acquisition
“old”
Setpoint “new”
Setpoint
is enabled only after a

When finished press Next
minimum number of
measuring cycles.
Course ST-PCS7ASE Monitor the curve recorder until

7 - 61 a steady state has been achieved. TheAG
SITRAIN - Siemens actual
© 2016 value and
manipulated variable are almost constant in this state. When disturbance effects are
small, the program recognizes the stationary state and terminates measured value
acquisition automatically.
 Click "Cancel measured value acquisition" in the following situations:
If the manipulated variable and actual value curves in the curve recorder lead you to
believe that the process is at steady state despite disturbances, such as measured
value noise.
If the manipulated variable and actual value curves in the curve recorder lead you to
PID tuner believe that no steady state will be achieved. If processes and controller parameters
are determined without error messages, they have to be tested very carefully.
Step 5: Reset process trigger
Step 5: Reset process trigger
Process trigger
“Reset” or “No reset”
Here, you have the option of removing or maintaining the process excitation achieved in
Step 3. If you have brought the process excitation to the future operating point, it is
advisable not to remove the process excitation.
If you want to remove the process excitation, enter the previous values for the
manipulated variable or setpoint.
Course ST-PCS7ASE 7 - 62 SITRAIN
SIMATIC PCS 7 – Advanced - Siemens
Process AG © 2016
Control (APC) with APL
PID tuner
Step 6: Specify the controller characteristic SIMATIC PCS 7 AS Engineering
Step 6: Specify the controller characteristic
Choose Controller
design
 Optimum disturbance response (with small overshoot):

The controller parameters are calculated so that the so-called optimum of magnitude
results. Normally an overshoot up to 10% of the setpoint step occurs.
 Optimum setpoint response (without overshoot):
The controller parameters are selected so that the actual value settles a periodically
in the closed control loop. However, SITRAIN
if the process settling time - Siemens
is under 10AGseconds,
© 2016
a slight overshoot of the actual value occurs in the closed control loop despite a
periodic settling.
PID tuner
Step 7: results and selection of the controller type
Step 7: Results and selection of the controller type
Identification
result
Select
controller Type
Results stored
in csv files
Course ST-PCS7ASE
 Upper trend display field: The trend of the actual value (green)
7 - 64
is shown together with
the trend derived from the simulated process model (red). The better the model
describes the characteristics of the real process, the better the trends of the output
data match each other.
 Lower trend display field: The corresponding manipulated variable trend is displayed.

PID tuner
Step 8: Simulate control loop with new parameters
Step 8: Simulate a control loop with the optimized parameters
New PID
parameters
Start
simulation
You can simulate the optimized controller with the process model to determine if the
controller has the desired controller characteristics.
When simulation is started, the closed control loop is simulated with the displayed
parameters for the controller and process model and the result is displayed in a graphic
window. During the simulation, the characteristics of the controller is displayed as
realistically as possible, including the delay of the D component and the sampling
Course ST-PCS7ASE effects although the manipulated variable limits and setpoint ramps
7 - 65 SITRAINare not taken
- Siemens into
AG © 2016
consideration.
Deviations may occur between the simulation and the characteristics of the real control
loop due to inaccuracies in the identification of the process model or due to non-
modeled disturbances (including measurement noise).
Therefore, start the simulation with modified controller parameters as many times as
needed until you find satisfactory controller characteristics.
"Display of the simulation results of the closed loop" graphic window

The setpoint and actual value trend of the simulation is displayed in the upper display
field (blue: setpoint, green: actual value). The corresponding manipulated variable trend
is displayed in the lower display field (orange: manipulated variable).
The displayed simulation of a control variable step change is superimposed on a
disturbance step change of 30% of the manipulated variable in the middle of the time
range to enable assessment of the disturbance characteristics of the closed control
loop.

PID tuner
Step 9: Download the optimized parameters SIMATIC PCS 7 AS Engineering
Step 9: Download the optimized parameters
Download
parameters
The old and new controller parameters are displayed in the fields. The old controller
parameters correspond to the offline data from CFC.
The time lag of the D component is always set to one fifth of the derivative action time
and is not displayed.
7.7Course ST-PCS7ASE
Task and checkpoint 7 - 66 SITRAIN - Siemens AG © 2016
Task: Optimization of the PID Controller
Goal
The parameters of the PID controller in the loop TICA315 are not optimal. Use the PID
tuner to optimize the controller and use the "Control performance monitoring" to check
Task: whether
Control the behavior has
performance improved.
monitoring
Checkpoint
Checkpoint

 Which two outputs of the control
performance monitoring can be
used as KPI for determining
whether the control loop performs
well?

SITRAIN
Content 8
8 SFC Advanced ......................................................................................................... 3
8.2 Introduction ............................................................................................................................ 3
8.3 Interconnecting SFC and CFC charts .................................................................................... 4
8.3.1 Variable browser and PCS7 Library V7.1 .............................................................................. 4
8.3.2 Variable browser and structures in PCS7 Advanced Process Library V8.0 .......................... 5
8.3.3 Drag and drop from CFC with PCS7 Library V7.1 ................................................................. 5
8.3.4 Drag and drop from CFC with PCS7 Advanced Process Library V8.0.................................. 6
8.4 External view of the SFC Chart ............................................................................................. 6
8.5 Interconnecting the external view in the CFC editor .............................................................. 7
8.6 Operating State Logic (OSL) ................................................................................................. 8
8.6.1 Diagram of the state changes for SFC OSL .......................................................................... 8
8.6.2 Diagram of the state changes for sequencer OSL ................................................................ 9
8.7 Priority of sequencers .......................................................................................................... 10
8.8 Introduction to SFC Types ................................................................................................... 11
8.8.1 SFC chart and SFC type compared .................................................................................... 11
8.8.2 Creating SFC types in the Component View ....................................................................... 11
8.8.3 Creating the SFC instance in CFC ...................................................................................... 12
8.9 Characteristics of SFC types ............................................................................................... 14
8.9.1 Characteristics – Chart I/O's ................................................................................................ 14
8.9.2 Characteristics – Process values......................................................................................... 16
8.9.3 Characteristics – Control values .......................................................................................... 17
8.9.4 Characteristics – Parameters .............................................................................................. 17
8.9.5 Characteristics – Setpoints .................................................................................................. 18
8.9.6 Characteristics – Block contacts .......................................................................................... 20
8.9.8 Characteristics – Control Strategy (CS) .............................................................................. 24
8.9.9 Setpoints and Control strategies in the OS ......................................................................... 26
8.9.10 Characteristics – Timers ...................................................................................................... 27
8.9.12 Characteristics – Bit memory ............................................................................................... 28
8.9.14 Characteristics – Note Texts................................................................................................ 30
8.9.15 Characteristics – Position Texts .......................................................................................... 31
8.9.16 Note Texts and Position Texts in the OS ............................................................................. 32
8.10 SFC Templates .................................................................................................................... 33
SIMATIC PCS 7 – SFC Advanced


8 SFC Advanced
8.1Learning target targets
Learning

 How to link CFC and SFC
 The operating state logic in SFC
 The SFC templates from the SFC
Library
 Create and use SFC types
8.2 Introduction
Hierarchical software structures are usually created during the automation of batch
processes. These structures are described in standards (see NAMUR NE33, ISA
S88.01).
SITRAIN Both higher-level recipe control and the group control level have an important role to
Course ST-PCS7ASE 9 - 2 software structures, with the latter being
play when it comes to hierarchical Siemensof
AGparticular
© 2012
significance in terms of engineering work. The software blocks used here are known
internationally (S88) as equipment modules (EM) and equipment phases (EPH), whilst
in German-speaking countries (NAMUR) they are known as "Technische Einrichtungen"
and "Technische Funktionen".
 See [123] PCS 7 Compendium Part C - Technical Functions with SFC Types -
01_2015 for more details.

8.3Interconnecting
Interconnecting
SFC andSFCCFCand CFC charts
charts
VariableVariable
8.3.1 browser and PCS7
browser Library
and PCS7 V7.1
Library V7.1
Procedure
SITRAIN
Course ST-PCS7ASE  Click "Browse". The "Browse"
9-3dialog box opens. The dialog box has four AG
Siemens different
© 2012
tabs: Plant View, Component View, Runtime Groups, Icons
 When you browse (through CFC charts in the Plant or Component view, for
example), all the available objects of the chart folder are found and displayed.
You limit the list of inputs/outputs by clicking "Filter...” Then, only the inputs/outputs
relating to the current configuration are shown.
 See [304] PCS 7 V8.2 SFC for SIMATIC S7 - Programming and Operating Manual -
12_2015, 12.4.2.5 for more details on filtering

Interconnecting SFC and CFC charts
Variable browser and structures in PCS7 APL V8.0
8.3.2 Variable browser and structures in PCS7 Advanced Process Library V8.0
Right mouse click
SITRAIN
Procedure
In the steps and transitions of the SFC it is possible to select the structure, value or
status. If, for example, the process value of an analog measuring point is to be read, the
value of the output PV_Out is to be evaluated.
To do so, the block has to be selected first and then the corresponding connection.
Since PV_Out is a structure, double-clicking PV_Out STRUCT would mean that the
Interconnecting
structureSFC and
is taken CFC
over to thecharts
transition. The structure can be opened and the value or
status can then be selected via right mouse click > Open Structure.
Drag and drop from CFC with PCS7 Library V7.1
8.3.3 Drag and drop from CFC with PCS7 Library V7.1
The engineering of the commands in the step blocks is often done in such a way that
the CFC chart and the SFC are opened simultaneously. The block I/O of the block on
the CFC chart is selected and dragged directly into the command line of the SFC chart.

Course folder,
Course V8.2.0, ST-PCS7ASE
ST-PCS7ASE 9-5 SITRAIN - Siemens AG © 2014 8 - 5
Interconnecting SFC and CFC charts
Drag and drop from CFC with PCS7 APL
8.3.4 Drag and drop from CFC with PCS7 Advanced Process Library V8.0
Value is added
automatically
Procedure
The procedure described in the previous paragraph is also possible with the APL
blocks. The .Value structure component is added automatically starting from PCS 7
Course ST-PCS7ASE V7.1 SP2. 9-6 SITRAIN - Siemens AG © 2014
External view of the SFC Chart

8.4Opening the external
External view view
of the SFC Chart
Opens the external

view of the SFC Chart
in the CFC editor

Display
The external view of the SFC chart represents the SFC chart in a CFC chart as a block
with its interface. To distinguish it from CFC blocks and nested charts, the external view
has the "SFC chart" icon in the header.
Purpose
In the external view, you can assign parameters for and interconnect the interface of the
SFC chart for AUTO mode so that the status of the SFC chart can be determined and
the control signals can be derived from it for the SFC chart. This allows you to influence
the processing of the SFC chart via the user program.
If the SFC chart is used in MANUAL mode, only the inputs/outputs that are also
processed in MANUAL mode are relevant in the external view.
External view of the SFC Chart
8.5Interconnecting the external
Interconnecting view in the
the external CFC
view editor
in the CFC editor
Input and output

parameters of the
external view can be
interconnected in CFC
Parameters of the external view

can be accessed by the SFC Chart
itself or by other SFC Charts
Interconnected CFC blocks should

be placed in separate CFC Charts !
Interconnection
You can provide the inputs/outputs with textual interconnection and/or interconnect
them with compatible inputs/outputs of other objects or with shared addresses. You
make all interconnections in the sheet bar. You cannot place any object, such as blocks,
in this window.
12_2015, 13.1 for A complete description on the inputs and outputs of the SFC chart

8.6 Operating State Logic (OSL)
 See [123] PCS 7 Compendium Part C - Technical Functions with SFC Types -
01_2015, 4 for useful information on operating states and state changes.
A complete description on the operating states and the state changes of the SFC
OSL can be found in
[304] PCS 7 V8.2 SFC for SIMATIC S7 - Programming and Operating Manual -
12_2015, 16.2.5.
8.6.1 Diagram of the state changes for SFC OSL
Changing the operating states

The current operating state of the SFC OSL can be changed through the following
events:
 Commands (e.g., Start, Resume, Hold, etc.) in "MANUAL" or "AUTO" mode
 External signals (inputs of the SFC or commands from another SFC, for example)
 Internal signals (commands of own sequencers, from test mode or SFC
Visualization).
 Implicit state change
The operating state logic of an SFC is defined by the following diagram.

8.6.2 Diagram of the state changes for sequencer OSL
Overview
The sequencer OSL controls processing of sequencers.
The operating state logic of the sequencer is defined by the Diagram of the state
changes for sequencer OSL (shown below).
The sequencer OSL is executed independent of the SFC-OSL when a sequencer is
processed. This means that the sequencer has a state which differs from the SFC state.
For example, the state of the SFC OSL can be "Holding", whereas the state of the
sequencer OSL is "Run" (due to the processing of the sequencer to the "Holding" state).
Operating State Logic (OSL)
The processing of the sequencer OSL is subordinated to the SFC OSL. This means that
Diagram of the
thestate
state changes
change for usually
in the SFC OSL sequencer
effects theOSL
state change in the sequencer
OSL.
SITRAIN
 A complete description on the states of the sequencer OSL and the state changes of
the SFC OSL can be found in [304] PCS 7 V8.2 SFC for SIMATIC S7 - Programming
and Operating Manual - 12_2015, 16.2.5.2.

8.7PriorityPriority
of sequencers
of sequencers
Which sequencer will be executed?

1. Start condition = true
2. Highest priority, if more than one start condition = true (1 = lowest priority)
3. Sequencer tab the most to the left, if sequencers have the same priority
SITRAIN
Executing sequencers
If the SFC status is unchanged, the sequencer whose start condition is fulfilled and has
the highest priority of all sequencers with a fulfilled start condition is executed.
If there are several sequences with a fulfilled start condition and the same priority, then
the sequencer with the tab furthest left in the editor is executed (similar to the
processing of alternative branches).
If the sequencer that was processed up to now is different from the sequencer that is to
start processed now, the previous sequencer is aborted and the new sequencer starts.
The start condition triggers the start of a sequencer. While the sequencer is being
processed, it is not necessary for the start condition to remain fulfilled. The sequencer is
processed until it is completed or until a sequencer with a higher priority and fulfilled
start condition has to be processed or the sequencer is aborted or held due to a state
change.
In the "Idle," "Completed," "Aborted," "Stopped," "Held," "Held (Error)," "Error," and
"Run" states (when SELFCOMP=0), sequencers are processed until you exit the state
by means of a command. A sequencer can, therefore, be repeated any number of times
when the corresponding start condition is fulfilled and no command is pending. To
prevent this behaviour, you can configure the final transition of the sequencer with an
unfulfilled condition. This causes the sequencer to "hang" at this transition and to exit
only following a command.

8.8 Introduction to SFC Types

8.8.1 SFC chart and SFC type compared
Common features
An SFC chart and an SFC type have the following common features:
 Standard interface for external control of the SFC (MANUAL/AUTO)
 Sequencers for formulating the control function of the SFC
Differences
An SFC chart and an SFC type differ as follows:
SFC chart SFC type

Direct access to basic automation (CFC) Access to basic automation (CFC) by means
of interface
Can be used once Can be used more than once
Can be modified locally Can be modified centrally
Interface cannot be expanded Interface can be expanded
Maximum of 8 sequencers can be Maximum of 32 sequencers can be
configured configured
SFC Types
Creating
8.8.2 SFC types
Creating in theinComponent
SFC types View
the Component View
SITRAIN
Course ST-PCS7ASE
You create a new SFC type in the
9 - 13
following ways: Siemens AG © 2012
 In the Component view of the SIMATIC Manager
 In the SFC Editor

Creating a type in the SIMATIC Manager

1. Open the chart folder in the Component view of the SIMATIC Manager.
Insert > S7 Software > SFC Type
The SFC type is inserted into the chart folder.
Result
The type is given a default name by the system, for example SFC_Type(1), which you
can change.
The next free FB number is automatically reserved for the SFC type and the type
template (FB 247) is copied to the block folder with this number. This allows you to
configure messages and instances for the type once it is created without having to
compile the type. The FB number can be modified later in the object properties dialog
box.
When you first create an SFC type, the blocks required for compilation and for execution
in the AS are copied to the current program and then managed in the ES. The blocks
are included in the supplied block library.
 SFC types cannot be assigned to a hierarchy folder in the plant view since they
themselves are not relevant to execution (from the perspective of the process to be
automated).
SFC Types
Creating
8.8.3
the SFC instance in CFC
Creating the SFC instance in CFC
If the SFC type was created

or stored in the master
data library
If the SFC type was created or

stored in the Charts folder of the
project

Introduction
The SFC types available in the chart folder are displayed in the CFC block catalog.
They are either in the All blocks directory or in the directory of the family, if they are
assigned to a family, otherwise, they are in the Other blocks directory.
You can also insert SFC types in the CFC chart from the libraries (for example, SFC
library or master data library).
To edit the Family, select the SFC type in the component view and use the menu
command
Right mouse click > Object Properties.
Procedure
In CFC, drag the SFC type into the CFC chart from the block catalog or from a library.
Result
The SFC instance is represented like a CFC instance block. If there is not enough
space to position the SFC instance, it is displayed as an "overlapping block" (light gray
and without visible inputs/outputs). After moving them to a free position in the chart, the
overlapping blocks are displayed as normal blocks again.
You can rename, assign parameters for, and interconnect the SFC instance in the CFC
chart.

8.9SFC Types
Characteristics of SFC types
Characteristics
8.9.1 vs. Chart
Characteristics I/O's
– Chart I/O's
Characteristics
Chart I/O's
SITRAIN
Characteristics editor/interface editor

You use the characteristics editor for the technological configuration of the interface for
an SFC type. You can only work with the editor if an SFC type is open in SFC.
You define the interface inputs/outputs of the SFC type as follows:
 Directly in the interface editor: Call this editor with icon or via menu command
View > Inputs/Outputs
 In the characteristics editor: Call with the icon or via menu command
View > Characteristics
The interface editor and the characteristics editor box are displayed alternatively. This
means that it is not possible to define technological characteristics and interface
inputs/outputs at the same time. You can define characteristics and inputs/outputs in
any order.
 You define individual inputs/outputs in the interface editor. These are available in
addition to the inputs/outputs defined in the characteristics editor. These
inputs/outputs are unknown to the characteristics editor and cannot be handled there.
Setpoints, for example, are created and assigned values during the definition of
characteristics. From this definition, the characteristics editor generates the required
inputs/outputs, which are displayed in the interface editor after it is opened and can be
used to configure the sequential logic.
You cannot change the I/Os generated by the characteristics editor in the interface
editor (except system attributes, initial value, comment).
You can group

Adding/modifying theinputs/outputs
SFC type only in the characteristics editor. These groups are taken
characteristics
into account during compilation in the applicable plausibility checks and status and
message processing.
The values (such as setpoints) required for visualization/operator control on an OS
station that are displayed with the SFC type faceplate are configured in the
characteristics editor.
Effects of the modified SFC type

Modifications to the interface of the SFC type are transferred to the SFC instances
immediately. Changes to the interface include adding and deleting I/Os and changing
data types. You can only download the SFC type and its instances during RUN mode of
the automation system if all the SFC instances of this SFC type are disabled or if you
temporarily disable the SFC instances during downloading. The instances are disabled
Course ST-PCS7ASE during the download following operator
9 - 17 confirmation and restarted after
SITRAIN the download,
again following operator confirmation. The execution of the instance then depends on
the process state and on the configuration of the instances (especially the start
conditions).
 If you perform the download with the SIMATIC Manager function "Compile and
download objects" and the SFCs need to be disabled for this, the SFCs will not be
disabled. In this case, the download will not be performed and an error message is
entered in the log.
While changes are being downloaded, the SFC instances cannot be processed in the
automation system, and the SFC instances cannot be accessed via the interconnections
in the CFC.
You do not have to disable the SFC instances to rename I/Os and characteristics or to
change units and limits.
Changes in the topology (step/transition sequence, jump destination) and the step or
transition configurations are made in the SFC type and do not become effective in the
SFC instances until they are compiled and downloaded. You can download inactive
sequencers following changes to the topology at any time. If you want to download
active sequencers following changes to the topology, you must first disable the SFC
instances before downloading. You can download changes to the step and transition
configuration at any time even if SFC instances of the SFC type are currently being
processed in the automation system.
After changing the configuration, you need to compile the OS to ensure that the current
data is available on the OS.
Effects on SFC instances in the CFC

If you change an SFC type and the instances belonging to it are open in the CFC, you
will have to update (View > Update or F5) the CFC and therefore the SFC instances
after compiling and downloading the changes. If the CFC is in test mode, you must
leave this mode before performing the update.

Effects on SFC instances in the SFC

SFC Types If–you want to change an SFC type and the instances belonging to it are opened in the
Characteristics
SFC and are in test mode, you must leave this mode before changing the type. After
Process values
making the change and compiling and downloading the change, you will have to update
the SFC instances (View > Update or F5). You can then re-enable test mode.
8.9.2 Characteristics – Process values
Process values are used to connect process signals (e.g. level) to the sequencer and to
control the SFC type.
Process values are primarily used for step enabling conditions in step sequencers.
Interface parameter assignments

I/O Meaning
"name" Process value input

SFC Types – Characteristics
Control values
8.9.3 Characteristics – Control values
Control values are used to control blocks which are not connected to the phase via the
CM (Control Module – Block Contact) interface. This can be used, for example, to
separate a cascade controller.

I/O Meaning
"name" Control value output
Parameters
8.9.4 Characteristics – Parameters
Parameters are used to modify

Parameters the behavior
are used to modifyofthe
thebehavior
SFC typeofon anSFC
the instance-specific
type on an
basis (e.g. limitinstance-specific
values, options). basis (e.g. limit values, options).
In the characteristics, the "Faceplate"
 The "Faceplate" columncolumn
definesdefines
whetherwhether the parameters
the parameters are are
available in theavailable
"parameters" tab of the faceplate or not.
in the "parameters" tab of the faceplate or not.

I/O Meaning
"name" Parameter input

Setpoints
8.9.5 Characteristics – Setpoints
Drag & Drop; "Select

Connection" pops up
Setpoints can be used to influence the behavior of the control strategies and the control
of the SFC type. They can be specified by means of operator input or by a higher-level
Course ST-PCS7ASE control (SIMATIC BATCH, for example).
9 - 21 Setpoints can be assigned
SITRAINto individual
- Siemens control
AG © 2014
strategies.
When a setpoint is defined, an input is automatically created for the associated actual
value. Setpoints of an SFC type contain block contacts for process and control values.
The setpoints of an equipment module are batch-relevant and are referred to as
– Characteristics
SFC Types parameters on the higher-level control (e.g. SIMATIC BATCH), although they should not
Setpoints; Use of thewith
be confused the parameters
important of the SFCI/O's
Setpoint type.
Use of the important Setpoint I/O's

Setpoint value in
automatic mode Actually valid setpoint
AUTO value
Setpoint value in "name" "name"_Q
MAN
manual mode Actually valid
"name"_OP
"name"_OPP "name"_QP prepared setpoint
Prepared setpoint MAN
value
value in manual
"name"_AI "name"_AO
mode. Actual process value
Will be copied to output, equal to
"name"_OP at the "name"_AI
next start command
Actual process value

input, e.g. to be
compared with
"name"_Q within the
sequencer

Interface parameter assignments (table is for the data type REAL)

I/O Meaning
"name" Setpoint automatic input
"name"_AI Process value input
"name"_AO Process value output
"name"_CS Enable control strategies: Bit 0..31 = control strategy 1..32
"name"_ENOP Enable operator control of setpoint
"name"_ENOPP Enable operator control of prepared setpoint
"name"_ERR Setpoint error
"name"_HL High limit setpoint
"name"_LL Low limit setpoint
"name"_OP Setpoint operator input
"name"_OPP Prepared setpoint operator input
"name"_Q Setpoint output
"name"_QP Prepared setpoint output
12_2015, 13.2.6.2 (section “Setpoints characteristic”) for more information on this
subject.
Special data types

Special features of setpoints are the "PI" and "PO" data types available, which represent
a REAL setpoint and are supplemented by the additional attributes "Material" and
"Tracking ID". The "PI" and "PO" data types are required for material tracking via
SIMATIC BATCH to SIMATIC IT, for example.
The DEST, SOURCE, VIA, and TKEY data types are also available and you can assign
enumerations to them. These data types are necessary for SIMATIC Route Control and
SIMATIC IT.


Block contacts
8.9.6 Characteristics – Block contacts
Drag & Drop;

"Select Connection"
pops up
Course ST-PCS7ASE
Block contacts are blocks on the control module. The control module
9 - 23
(CM) is activated
by the SFC type. As well as block activation, feedback on the relevant state is also
required. These activations and feedbacks are connected to the SFC type via interface
elements.
A cohesive group of interface elements is called a block contact.
In order to be able to use block contacts to connect basic control blocks, you must
specify at block type level the relevant I/Os for creating a link to an SFC type.
This is achieved by assigning the "S7_contact = true" system attribute to the block I/O.
The technological blocks from the PCS 7 Library are prepared accordingly. If required,
you can make project-specific modifications to the block types supplied in terms of the
relevant I/Os.
Example for the parameter OpenAut of the VlvL block type:

 If you subsequently add or change system attribute "S7_contact" for the I/O of a block
type that is used as a block contact in the SFC type, this has no effect on the block
inputs/outputs of the SFC type.
 If you want these changes to be adopted for the SFC type, note the following:
 Import the changed block type in the CFC with the menu command Options >
Block Types. All block instances of the type are updated during the import.
 Update the block contacts in the SFC with the menu command
Options > Block Contacts
This menu command applies the changes to the interface of the SFC type and to all
SFC instances.
By defining an instance of the "block contact" characteristic in the characteristics editor,

the selected block inputs/outputs are created accordingly in the SFC type. The IN I/Os
of the block type are created as OUT I/Os in the SFC type. The OUT I/Os of the block
type are created as IN I/Os in the SFC type. The IN_OUT I/Os of the block type are
created as OUT I/Os in the SFC type.
This allows you to interconnect a specific CFC instance of the block type to the
corresponding inputs/outputs of an SFC instance. An instance of the "block contact"
characteristic is therefore always assigned to exactly one block type. You must enter the
relevant block type in the "Block" column in the right window pane. The block type must
be present in the ES data management.
This procedure enables you to configure, commission, and visualize basic automation
blocks independently. As a result, you can configure SFC types based on block contacts
and interconnect them later to the basic automation blocks.
When interconnecting the SFC type and the control module (valve, motor …), one
Block contacts in the OS
interconnection is sufficient. All other interconnections between the SFC type and the
CM will be generated automatically according to the interconnection inserted manually.
 Open the "Block contacts" view in the Group display of the

faceplate to get an overview of the control connected process object
modules connected to the SFC type.
Highlight block icon of the process
The list of the control modules displays
object in the process picture
 their type,
 Group display (showing the alarms of the
control module)
 a link to open the process picture where the
block icon is located, with the block icon
highlighted.

Task: Heating and draining R3x0
Goal
Task: SFC types
Complete the steps and transitions regarding heating and draining for reactor R3x0.
Checkpoint
Checkpoint

 Are the differences between
process values, parameters and
setpoints in an SFC type?
SITRAIN



Control Strategy (CS)
8.9.8 Characteristics – Control Strategy (CS)
Different process-engineering sequences within an SFC type can be defined by means

of control strategies. The active part of a sequencer is described in the different control
strategies, which are assigned either to separate sequencers or to alternative branches
within a sequencer.
The sequencer is activated via the starting conditions of the step sequencer with the
control strategy (CS). The output (QCS) must be queried in order to configure the
starting condition.

I/O Meaning
CS AUTO: Prepared control strategy (apply at next "Start")
CS_LL Control strategy "low limit"
CS_HL Control strategy "high limit"
CSP_DEFAULT Initial value of the prepared control strategy
CSP_OP MANUAL: Prepared control strategy by operator (apply at next "Start")
CSSPACCEPT Control strategy and setpoints applied (1 cycle long)
ENCSP Enable for "prepared control strategy"
QCS Current control strategy
QCS_O 1: No control strategy
QCS_1...32 1: Current control strategy 1 – 32
QCSP Prepared control strategy
SELCS Enable control strategies: Bit 0..31: Control strategy 1..32

Do not delete unused control strategy

Control strategies that have already been used, for instance in:
 Start conditions
 Transitions
 Assignment to setpoints
 Control strategy release
Should not be deleted or moved in the characteristics editor, otherwise the control
strategies will be renumbered. This also applied for control strategies that you copy from
an SFC type into a different SFC type.
The numbers of the control strategies in the existing utilization are not adapted. For this
reason, accesses and other mechanisms that reference these numbers no longer
function as originally intended.
Example
You no longer want to use the control strategy with number "2" and delete it.
The control strategies are renumbered. The previous control strategy "3" is given the
number "2"; control strategy "4" is given the number "3", etc.
 ATTENTION!
If you no longer want to use a control strategy, do not delete the control strategy;
rather, rename it as "not used", for example. The numbering and functionality of the
other control strategies is then retained.
 See [304], 15.4 (section Changing the control strategy and setpoints for an SFC
instance) for more information on this subject.
Control Strategy (CS) in the OS-faceplate
Selection of Control strategy by the Operator

In automatic mode, the control strategy is chosen by the interface by means of the input
parameter CS. In manual mode, the control strategy is chosen by the operator in the
faceplate. It can be selected in the drop down menu in the view "Prepared values".
8.9.9 Setpoints and Control strategies in the OS
Setpoints are visible in two views in the faceplate – actual values and prepared values.
In the "actual values" view you can find the setpoint values and measured values for the
actual execution of the sequencer. In the "prepared values" view, the operator can
prepare the setpoints for the next execution of the sequencer (after the next start
command).
Setpoints and Control
Moreover, strategies
only the in theto OS
setpoints assigned the selected control strategy are visible in the
faceplate.

8.9.10 Characteristics – Timers

Timers Times are often needed when implementing SFC types, such as a monitoring time or
run time for a mixer.
MODE Operating mode

0 Pulse timer
1 Extended pulse timer
2 On delay timer
3 On delay timer with memory
4 Off delay timer
Times can be implemented using a default time module (TIMER_P). If the SFC type is
used, then this time module is automatically embedded for editing times.
Course ST-PCS7ASE The time module TIMER_P supports

9 - 30 different modes, with the SITRAIN
advantage that
- Siemens AGthey
© 2014are
incremented by the operating system.

I/O Meaning
SAMPLE_T Task sampling time in sec
(preset to the relevant cycle time by the code generator)
"name"_MODE Operating mode:
0: Start timer as pulse "Pulse"
1: Start timer as extended pulse "ExtP"
2: Start timer with on delay "OnDel"
3: Start timer with retentive on delay "RetOn-D"
4: Start timer with off delay "Off-D"
"name"_TIME0 Time in s
"name"_RESET Reset
"name"_QERR Error
"name"_Q0 Output pulse
"name"_I0 Input pulse
"name"_PTIME Time remaining in s
 For more information on this subject, refer to the online help on the TIMER_P CFC
block type.

Task: Cleaning control strategy
Goal
Create a second control strategy for cleaning the dose tank and the reactor.
Task: Control strategies
Checkpoint
Checkpoint

 Is the link between the selected
control strategy and the sequencer
to be executed?
Bit memory
8.9.12 Characteristics – Bit memory
SITRAIN
Bit memories serve as a clipboard for values. They are created as static variables,
which are not visible on the interface display in CFC.

Course ST-PCS7ASE I/O Meaning 9 - 33 SITRAIN - Siemens AG © 2014
"name" Bit memory (static VAR area)
 Bit memory is an internal variable that does not appear as a visible I/O on the
interface. As a result, for example, you cannot use the "Browse" dialog box or the
interface editor to incorporate this variable in the addresses of the step/transition
properties. You have to enter the I/O name for the bit memory with the keyboard or
drag & drop them from the characteristics window.

Task: Sequencer for holding and resuming
Goal
Task: Hold Hold
the the
process
SFC typein a safe
in such way
a way that the process is held as well.
Checkpoint
Checkpoint

 Is the Step 7 equivalent of the bit
memory characteristic?
SITRAIN

Note Texts
8.9.14 Characteristics – Note Texts
Note texts are used for displaying additional notes on the operator station (OS). They
can also be used to display additional information in tandem with a message in the
event of an error. Configuration work needs to be carried out in order to utilize this
function.
The texts, which are predefined in the characteristics dialog, can be displayed simply by
Course ST-PCS7ASE
setting an output (OPTIPNO) on the interface. These note texts
9 - 36
can be acknowledged
by the operator. A note text is not connected to the signaling system; it is used for
operator prompting (provided that it has been integrated in the signaling system via the
configuration as operator prompting, for example, otherwise the text will only be visible
as additional information).
Using the assignment of a note text number in a step action, the corresponding note text
is displayed in the SFC faceplate.

I/O Meaning
OPTIPNO Note text number for operator
 If OPTIPNO= “0” no Note Text is displayed

Position Texts
8.9.15 Characteristics – Position Texts
Position texts (posis) are used for displaying the current sequence state on the operator
station (OS). Position texts can be set in the sequential control system and displayed on
the SFC type faceplate. Furthermore, the position text can be used in a higher-level
control to query an interim state, for example. An example is the querying of rough/fine
dosing.
When a position text number is assigned in a step action, the corresponding position
text is displayed in the SFC faceplate.

I/O Meaning
POSINO Position text number
 If POSINO = “0” no Position Text is displayed

Note Texts
8.9.16 Noteand Position
Texts TextsTexts
and Position in the OSOS
in the
Acknowledge note text
Task: Operator information
Goal
Provide additional information in the faceplate for the operator.
Whenever a control strategy starts, a note text must be issued. Moreover, a position text
Task: Note must
andbeposition
issued whenever
textsthe state of a control module changes.
Checkpoint
Checkpoint

 Triggers the note and position
texts?

SFC Templates
8.10 SFC Templates
Templates for state- Templates for control

oriented processing (as strategy-oriented
SFC Chart and type) processing
Course ST-PCS7ASE
Several SFC templates are available
8 - 39
in the "SFC Library" by the menu command
SFC Library >Blocks+Templates> Templates
 The TypeStates SFC type already contains several sequencers for state-oriented
processing of the sequential control system.
 You will also find the ChartStates CFC chart with several sequencers for state-
oriented processing of the sequential control system.
 Finally, you will find the TypeCtrlStrategy SFC type. It contains a control strategy-
oriented processing of the sequential control system. You can copy these templates
and change them to suit your purposes.
 Refer to the customer support website

https://support.industry.siemens.com/cs/ww/en/view/33412955
for templates for specification of technical functions with SFC Types.

Content 9
9 Syntax Rules ............................................................................................................ 3
9.1 Special characters ................................................................................................................. 3
9.1.1 General Background Information ........................................................................................... 3
9.1.2 PC(s) ...................................................................................................................................... 4
9.1.3 ES .......................................................................................................................................... 4
9.1.4 OS .......................................................................................................................................... 5
9.2 Maximum Length for Names.................................................................................................. 6
9.2.1 ES – CFC ............................................................................................................................... 6
9.2.2 ES – SFC ............................................................................................................................... 6
9.2.3 ES – Blocks............................................................................................................................ 6
9.2.4 ES - General Naming in Project............................................................................................. 7
9.2.5 OS – Alarm Logging .............................................................................................................. 7
9.2.6 OS – Pictures and Variables.................................................................................................. 7
9.3 Rules for Naming in the PH ................................................................................................... 8
SIMATIC PCS 7 – Syntax Rules


9 Syntax Rules
9.1 Special characters
This section provides information on which special characters should not be used in
your PCS 7 projects.
9.1.1 General Background Information
PCS 7 OS utilizes WinCC in its underlying software and structures the PC, ES, and OS
into common interrelated groups. Therefore the naming within all three of these groups
must follow standards different from typical WinCC standards. The standards apply
specifically to the use of Special Characters (signs).
Each of the three components (PC, ES, & OS) has its own naming requirements which
must be followed. The following Tables indicate the Special Characters (signs) which
should not be used. The underscore (_) is allowed for naming. Within the WinCC
portion of the OS, you may use the ASCII Character set (although, do not use National
special character sets). Avoid all special characters in object names, particularly, if the
object names are used in Scripts. The following tables show the characters which you
may not use in WinCC components, designations and specified names.
Additionally, Microsoft Excel interprets texts with special characters as formulas. For
this reason these characters should not be used as part of object naming schemes
(e.g., “=”, “+”, ‘-“) for group name, variables, texts, etc.

9.1.2 PC(s)
Component Do not use these characters Remarks

Computer name [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] Only capitalization is relevantly
[+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] First indication must be a letter.
[{}] [<] [>] [space]
DNS Hostname [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-]
[+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]]
[{}] [<] [>] [space]
path: [:] [?] ["] [/] [*] [<] [>]
Name of folders
Communication / OPC: [.] [:] [?] ["] ['] [\] [*] [%] [space]
used names
Web Client: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-]
used names [+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]]
[{}] [<] [>] [space]
9.1.3 ES

Hierarchy folder [.] ["] [/] [\] [%]
Global Symbols 0x00 and When using special characters
[‘] [.] [“] [%] [\] [*] [?] [:] [Space] the symbol must stand in
Double underscore quotation marks.
Local Symbols letters, numbers, [_] are allowed
Variables Space and [‘], [.], [%] [-] [/] [*] [+]
CFC-charts
Chartname with OS Space and [‘], [.], [%] [-] [/] [*] [+]
Chartname without OS [.] [%] [\] [“]
Chart comment whole ANSI code is allowed
Run time groups [.] [%] [\] [“]
Task [.] [%] [\] [“]
Blocktypes Made by Step 7
Parameter name Made by Step 7
First character can't be a
number
Parameter comment whole ANSI code is allowed
Name of the [.] [%] [\] [“]
blockinstance
Comment of the whole ANSI code is allowed
blockinstance
Global Variable [“]
S7-Program Space and [‘], [.], [%] [-] [/] [*] [+]
Names of WinCC-Projects [.] [,] [;] [:] [!] [?] ["] ['] [+] [=] [/] [\]
[@] [*] [%] [[]] [{}] [<] [>] [Space]
AS-OS -Interconnections [.] [:] [?] ["] ['] [\][*] [%] [Space] Relevant for OS-Compile
(Netpro)
Variables [‘] [.] [%] [\] [*] [?] [:] [Space] Will be changed into [$]
But [$] is not allowed???
SFC-chart / SFC-Type [/] [\] [.] [“] [%]

9.1.4 OS

WinCC-Project: [.] [,] [;] [:] [!] [?] ["] ['] [+] [=] [/] [\] Case sensitive
Names of WinCC projects [@] [*] [[]] [{}] [<] [>] [Space]
Variables: [:] [?] ["] ['] [\] [*] [$] [%] [Space] Not case sensitive
Variable names "@" is reserved for System
variables
The point is used as separator
for structure variables
Variables: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Names of process tags in Tag [=] [/] [\] [*] [%] [&] [§] [°] [[]] [{}] [<]
Logging [>] [Space]
Variables: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Names of archive variables in [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
Tag Logging [<] [>] [Space]
Variables: [?] ['] [\] [Space] Not case sensitive
Names of variable groups
Structure types: [.] [:] [?] ['] [\] [@] [*] [%] [Space]
Names of structure types,
structure elements, structure
instances
Graphics Designer: [:] [?] ["] [/] [\] [*] [<] [>]
Names of pictures (PDL-files)
Graphics Designer: Avoid using special characters if The name can be no longer
Names of objects in pictures the object name is used in scripts. than 180 characters.
For more detailed information, If you use special characters,
refer to the documentation on VBS the maximum number of
in the section Testing with the characters is further restricted.
Debugger > Action and Procedure
Names in the Debugger.
Graphics Designer: [;] Restriction with assigned and
Object type text list referenced texts
Graphics Designer: [%]
Names in Dynamic Wizard
Alarm Logging: ['] [enter] [linefeed]
Names of message blocks,
message class, type of
message, message texts
Tag Logging: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Archive name [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
[<] [>] [Space]
Tag Logging / Trend control: single "&"-will not be displayed
Label of timeline and value line double "&"-will be displayed as
single.
Report Designer: [:] [?] ["] [/] [\] [*] [<] [>]
Names in page layout und line
layout
User Administrator: ['] [\] Not case sensitive
User names
User Administrator: ['] [\] Case sensitive
Password
User Administrator: ['] [\]
User rights
User Archives: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+] First character must be a letter
Names for archives, fields, [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
views, rows [<] [>] [Space]
Server Data: [,] [/] [\]
Names of Packages National special signs, e.g. é

9.2 Maximum Length for Names

This section describes the allowable maximum length for naming used in various areas
of the ES and OS.
9.2.1 ES – CFC
CFC Chart naming is restricted to a length of 22 characters. Anything longer will be

truncated. Any object placed on the chart, such as a block, has a maximum character
length of 16 for naming.
Component Maximum length Remarks

Chart 22 Name of charts in plant view
Chart comment 7 resp. 14 out of 255 Depends on the size: from the
255, only 7 or 14 are displayed.
In the CFC properties in the
plant view
S7_String_0-1 16 In the block properties in CFC
S7_String_2-25 8 In the block properties in CFC
Textual interconnection 512 Between blocks in CFC
Runtime group 22 The several blocks can be
grouped in runtime groups
Parameter comment 80 In the block settings in the CFC
chart
Name of the block instance 16 In the block settings in the CFC
chart.
Picture.
Comment of the block instance 80 In the block settings in the CFC
chart.
Picture.
9.2.2 ES – SFC

SFC chart 22
SFC type 16
Sequencer name 16
Sequencer comment 80
Criteria 24
Instance name 8-24
Setpoint 16
Timer 16
Block contacts 10
9.2.3 ES – Blocks

Header 8
Author 8
Family 8
Version 4 0.0 up to 15.15
Block comment 16

9.2.4 ES - General Naming in Project

Library names 8 Longer than 8 character will be
cut off
Project names 8 Longer than 8 character will be
cut off
Symbols 24
Symbol comment 80 Via export as *.SEQ it will be cut
off after 40 characters
Variables 128 Attention for the OS: the
Variable name is shorter then
128 signs for some reason
Hierarchy folder 1 up to 12 Depending on the settings of the
Hierarchy 1 -24 but this can’t be
displayed on the OS
9.2.5 OS – Alarm Logging
In the OS, you will configure messages using the alarm logging editor. Using the editor,
you configure the length of texts for messaging. The following table provides the
maximum character lengths allowed.

User blocks 32 out of 255 Time correct alarms
User blocks for bit reporting 1-255 The length can be limited
procedure individually for the individual
columns
9.2.6 OS – Pictures and Variables
The OS Pictures and Variable naming lengths must also be considered at project start.
The following table provides the maximum lengths guidance.

Picture name 24 out of 255 After 24 characters the name is
cut off
Object name 128
Container name in the picture 255 Minus the number of characters
tree for the server prefix
Computer name 21
Archive variable 52
OPC text variable 160

9.3 Rules for Naming in the PH
Extending the Basic Structure

Use the PCS 7 wizard to create a maximum of 8 hierarchy levels without additional
nesting of hierarchy folders. You can further extend this basic structure during
configuration by adding further hierarchy folders and/or technological objects.
When doing this, remember the following rules for naming folders/objects in the plant
hierarchy.
Rules for Naming Folders/Objects

 The following special characters may not be used in the name of a hierarchy folder: [
.][%][/][\]["]
 Note
The characters [ ' ] [ . ] [ % ] [ \ ] [ * ] [ ? ] [ : ] [spaces] within a name are converted to
the substitute character $ when you compile the OS.
The ES separator [ \ ] is converted to the [ / ] character.
If, for example, you assign the name "TICA:1" for a CFC chart (this becomes
"TICA$1" on the OS) and the name "TICA*1" for another CFC chart, (also becomes
"TICA$1"), you will receive an error message when you transfer the second chart
because the chart name already exists.
 The maximum length of a tag name is 128 characters. Remember, however, that
many of the editing windows on the OS can not display 128 characters in their
entirety. You should therefore restrict the length of the HID.
 Remember that special characters associated with certain national languages take
up two characters, thus reducing the maximum name length accordingly.
 Remember that the length of the texts transferred depends on the maximum text
length of a target block in the OS (Tag Logging, for example, event 50 characters;
origin 32 characters). When compiling the "OS" texts up to a maximum length of 255
characters are transferred.
Remedy:
Increase the maximum character length of the user text field or select a shorter HID.
 The message texts of the transfer messages are made up of the hierarchy path, chart
name, and the block name (if you decided to include the names in the HID).

Content 10
10 Tasks ........................................................................................................................ 3
10.1 Retrieve the training project ................................................................................................... 3
10.2 Project-specific to station-granular setup .............................................................................. 4
10.3 Type Change in Run .............................................................................................................. 5
10.4 Move a project to another location using "Save as..." ........................................................... 7
10.5 Move a project to another location using "Remove for editing / Reapply after editing" ......... 8
10.6 Display changes since the last download .............................................................................. 9
10.7 Download to a new CPU ...................................................................................................... 10
10.8 (Optional) S7 Block Privacy ................................................................................................. 11
10.9 Hardware settings ................................................................................................................ 12
10.10 CPU overload....................................................................................................................... 13
10.11 Product concentration monitoring for B410 und B420 using the IEA .................................. 14
10.12 Adopt existing charts as process tags ................................................................................. 16
10.13 Export process tags and modify process tag type ............................................................... 17
10.14 Manual creation of CMT for the reactor inlet valves ............................................................ 18
10.15 Synchronization of modified CMT ........................................................................................ 20
10.16 Walk-through the APL Start project ..................................................................................... 22
10.17 OS operator permissions and time triggered draining of R340 ........................................... 23
10.18 Configuration of dosing material 1…3 into the Dose tank D210 ......................................... 25
10.19 Optimization of the PID Controller ....................................................................................... 26
10.20 Heating and draining R3x0 .................................................................................................. 28
10.21 Cleaning control strategy ..................................................................................................... 30
10.22 Sequencer for holding and resuming ................................................................................... 31
10.23 Operator notifications ........................................................................................................... 32
10.24 (Optional) Calculate cycle time and memory requirements ................................................. 33
SIMATIC PCS 7 – Tasks


10 Tasks
10.1 Retrieve the training project
Goal
Retrieve the archived multiproject as the starting point for implementing the training
application.
Main steps
1. On your D-drive, create a new folder with the name "your name_training".
2. Share this folder.
3. Execute the application "SimaticRights.exe" for this folder. Ask the trainer for the exact
location of the file.
4. Check the settings for default storage location, language, message number assignment
and archiving.
5. Retrieve the multiproject "Johnsson.zip" to the folder you just prepared.
6. Rename Team0x, Proj0x, AS0x, AS0xProg, PC0x, OS0x and Lib0x in the component
view of the multiproject by replacing the x by your team number (e.g. Team0x 
Team02 if your team number is 2).
7. Enter your computer name in the properties of PC0x.
8. Open the hardware configuration of PC0x and enter the correct MAC address for IE
general. In case you are using a CP1613/CP1623 in your ES, replace the IE general by
the respective CP and set the MAC address.
9. Configure and download the Station Configuration Editor.
10. Open the hardware configuration of AS0x and replace the modules if you detect any
differences to your actual hardware. Set the MAC address of your Ethernet CP to 08-00-
06-01-00-0x, where x is your team number.
11. Compile and download the AS hardware configuration. You might need to change the
PG/PC interface temporarily.

10.2 Project-specific to station-granular setup
Goal
Split the project Proj0x into ASProj0x and OSProj0x by moving AS0x to another project
in the multiproject.
Main steps
1. Create a new user project called ASProj0x in the multiproject and rename the project
Proj0x to OSProj0x. Make sure that this project is stored in the same folder as the other
components of the multiproject.
2. Move AS0x and the network called PROFIBUS to ASProj0x.
3. Copy the network SystemBus to ASProj0x.
4. Open NETPRO from the project ASProj0x and connect the CP443-1 to SystemBus.
5. Merge the SystemBus networks of both ASProj0x and OSProj0x.
6. Check the connection Conn_AS0x between the WinCC Application and the CPU.
Replace the x in the connection name with your team number. Save & compile
NETPRO in both projects.
7. Download the connection data into the AS and PC station.

10.3 Type Change in Run
Goal
Update your AS program with new block types without need of CPU stop.
Procedure
1. The AMOUNT block (FB606) is the block type to be updated.

The block is used in the chart R310-Gen (sheet 2) of the training project to calculate a
setpoint for the sequential control of R310. The block instance name is ParaSFC.
It is possible to modify the parameters during CFC test mode. A simplified block icon is
representing the values in the OS process picture, without possibility of operation. Test
the function in CFC and OS runtime.
The block provides a setpoint for a temperature control via its output SP_Out. Inside of
the sequential control this output interconnected to the corresponding step.
The reactor sequence includes an extra condition for reaching the desired reactor
temperature (=setpoint – 2). Until now, the extra calculation was configured in the CFC.
You replace this solution by moving this simple subtraction into the SCL code of the
function block. After this change, the Amount block provides the result as an additional
output parameter SP_OUT2.
2. Create a new chart. Configure a simple technological function to let a lamp of the signal
box blinking in the interval of OB33. This is only to monitor any effects of the type
change in Run feature.
3. Create anymore charts with instances of the AMOUNT block. There is no need for
interconnections. These instances are only for testing purposes.
4. Compile and download the S7 program. Compile the OS.
5. Test the functions in this starting state.
6. Modify the SCL source of the AMOUNT block in order to realize the required simple
subtraction in the SCL code of the block type. The result of the internal calculation
should be available at a block output SP_Out2.
 You may copy the code lines used for the declaration and calculation of the already
existing block output SP_Out in order to create a new block output.
 You change also the version number in the block header to keep an overview about
the versions of the modified block type
 Compile the SCL source in your library.
7. With respect to the modified block type you update all charts and perform a download of
changes without CPU stop.
8. At this moment still do not compile the OS. First, test the functions in CFC test mode
and check also the OS runtime. What is the result in the OS?

9. Now compile the OS and check the runtime again. The OS runtime should be restarted.
You may repeat this part of the exercise anymore by deactivate / activate the additional
parameter in the SCL source (by comment).
Explore during these repetitions, when exactly new instance DB numbers are defined,
and when the new instance DBs are created.
10. Finally you remove all additionally created instances.
Optional task:
Check the TCiR behavior after modifications of the default value for a parameter. For
this purpose, you may change the default values for Percent1, Percent2, Totalkg
or SP_In in the SCL source of the AMOUNT block.

10.4 Move a project to another location using "Save as..."
Goal
Move the ASProj0x to another ES for distributed engineering in the multiproject network.
Main steps
1. Select the single project containing the AS and use the "Save as…" procedure as
described in the theoretical part to move the single project to another engineering
station. If another engineering station is not available, you can move the project to
another location on your own engineering station.
2. Open the project on the other location and modify any parameter in CFC (e.g.
monitoring time of the valves or motor).
3. If available, open the project on both engineering stations at the same time and modify
the same CFC chart. Note that the moved project is still available from the multiproject
on the central engineering station as long as the network connection is available.
4. Compile the charts on one engineering station and try to modify a parameter on the
other engineering station at the same time. A window with a conflict message should
appear.
5. Finally, move back the project to its original location using the "Save as…" procedure
and check whether your modifications are still present.

10.5 Move a project to another location using "Remove for editing /

Reapply after editing"
Goal
Move the ASProj0x to another ES for distributed engineering without the multiproject
network.
Main steps
1. Select the single project containing the AS and use the "Remove for editing…"
procedure as described in the theoretical part to move the single project to another
engineering station. If another engineering station is not available, you can move the
project to another location on your own engineering station.
2. Note that the project is not available any more in the multiproject on the central
engineering station.
3. Open the project on the other location and modify any parameter in CFC (e.g.
monitoring time of the valves or motor).
4. Finally, move back the project to its original location using the "Reapply after editing…"
procedure and check the modification made on the other location.

10.6 Display changes since the last download
Goal
Before downloading changes to the AS, a programmer must be certain of the changes
he is downloading. Therefore it is possible to compare the actual version of the project
with a previously downloaded version.
Main steps
1. Open any CFC chart.
2. Open the Compile/Download settings with "Options  Customize 

Compile/Download"
3. Activate the check box "Generate image of downloaded program for comparison".
4. Compile and download the actual version of the program to the CPU (an XML file will be
generated based on the actual version).
5. Open a CFC chart, a SFC chart, hardware configuration … and make some changes (or
ask someone else to make some changes in your project).
6. Compile the charts.
7. Click the download button, select "Changes only" and click the button "Show Changes"
8. A new XML file will be generated based on the new version and both XML files will be
compared.
9. In the window that appears you will be able to identify the changes since the last
download.

10.7 Download to a new CPU
Goal
During the development, programmers often use a test CPU in their office. While
programming, the charts are downloaded into this test CPU and by consequence,
process objects are booked and your license will be decremented. After the
development phase, commissioning will start and you will have to download the
program into the customer's AS. In order to avoid booking the PO's twice, the PO's have
to be booked back before starting the commissioning on the new CPU.
Main steps
1. Open the Automation License Manager and check the PO count for the license key AS
RT PO. The same information can be found by using the PCS7 license information tool
in the SIMATIC Manager.
2. Select the "Charts" folder of your project and select "Options  Charts  Book Back
Process Objects"
3. Note that the online program will be deleted for booking back the PO's.
4. Check the Automation License Manager or the PCS7 license information tool in the
SIMATIC Manager again to display the number of available PO's on your engineering
station.
5. Afterwards, download your program to the AS again.

10.8 (Optional) S7 Block Privacy
Goal
Explore the possibilities of S7 block Privacy.
Main steps
Block encryption
1. Select the Blocks folder of the library Lib0x.

Right mouse click > Block Privacy.
The S7-Block Privacy dialog opens.
2. Mark the block FB2500 "BlockPrivacy" and encrypt the block.

Right mouse click > Encrypt block…
3. Enter an encryption key and confirm it. Leave the option for decompilation checked.
4. Open the block FB2500. The SCL code will be shown. Obviously this is not wanted for
encrypted blocks…
5. Once more, open the S7-Block Privacy dialog.
6. In this dialog, select the SCL source BlockPrivacyTask.

Right mouse click > Delete source.
7. Still in the same dialog, select the Sources folder.

Right mouse click > Reorganize source folder.
The source file is permanently deleted.
8. Open the block FB2500 again. You will notice that the block is protected.
Block decryption
9. In the S7-Block Privacy dialog, select the encrypted block FB2500.

Right mouse click > Decrypt block…
The block is decompiled.
10. Open the block a last time. Notice the programming language…

10.9 Hardware settings
Goal
PCS7 requires some specific hardware settings. In this exercise you will check and if
necessary modify these settings.
Main steps
1. Make sure all input and output modules as well as OB32 are assigned to process image
partition 2.
2. Activate diagnostics for all input and output modules if possible regarding hardware
wiring.
3. Open the chart V511 and check in CFC test mode whether the inputs/outputs are
updated..
4. Check the startup characteristics.
5. Check the cycle settings.
6. Check the local data requirements.

10.10 CPU overload
Goal
When generating the module drivers for the very first time during compilation of the
PCS7 program, all error OB's are automatically generated. This ensures that the CPU
never goes into STOP mode … unless by a time error due to a CPU overload
(exceeded cycle time of OB1 or OB3x). This exercise shows you the behavior of a
PCS7 program during such a cycle overload.
Main steps
1. In the Charts folder of AS0x you will find the charts Load_OB1, Load_OB32 and
Load_OB35. These charts contain one block containing a loop, which generates a cycle
time increase, depending on the number of executed loops. The execution of the loop
can be switched on and off with the input parameter OnOff and the number of loops can
be defined with the input parameter NrOfLoops.
2. Open these charts and activate test mode.
3. For CPU's with firmware version lower than 5.0:

 In CFC test mode or in the OS runtime in the picture Signalbox, increase the number
of loops in the chart Load_OB1, Load_OB32 or Load_OB35 (of course with OnOff =
1).
 While doing this, note the "Scan cycle time" tab in "Module Information" window for
the CPU.
4. For CPU's with firmware version 5.0 or higher:

 Activate the maintenance station
 Make sure that OS runtime is active and open the picture "Diagnostics\AS objects"
where you will find following block icon: .
 Open the faceplate by clicking and open the view "OB3x". Check the cycle
times for OB32 and OB35.
 Keep track of the cycle times in the OB3x view and the overall CPU load in the
Performance view while you gradually increase the number of loops in the chart
Load_OB1, Load_OB32 or Load_OB35 (of course with OnOff = 1). These cycle
times can also be found in the chart @CPU_RT as output parameters of the CPU_RT
block (note that these parameters might be invisible and not dynamic in test mode).
 Pay attention not to make your increases too big in order to be able to distinguish the
three overload scenarios.

10.11 Product concentration monitoring for B410 und B420 using

the IEA
Goal
You configure the process tags XIA414_1…3 and XIA424_1…3 for the product
concentration in the buffer tanks using the Import/Export Assistant.
Starting point is an existing process tag type for Analog Monitoring.
Procedure
1. Customize a chart as base for the process tag type.

 In the plant view, navigate to the process tag type folder in your master data library.
 Copy the process tag type AnalogMonitoring and rename the duplicate
meaningfully (e.g. concentration).
 The copy has still the status of a type instance (chart). Delete this dependency.
 Open the chart in CFC and modify the unit of measure at the analog input channel
block Pcs7AnIn, to get the process value as %.
 Make the following I/Os visible in the block properties of the MonAnL:
tolerance limits PV_TH_Lim / PV_TL_Lim and the corresponding message enables
PV_TH_En / PV_TL_En.
 The event of tolerance limit violation shall be signalized with time delays. The
required block I/Os (PV_T_DC, PV_T_DC) have to be visible too. The delay for the
coming limit violation event is 10 sec.
 Do not compile this chart.
2. Create a process tag type from this chart.

 Open the dialog "Create/Change Process Tag Type…"
 The process tag type shall have I/O points for following functions:
 Interconnection to a process value (symbolic)
 Unit for the process value
 Limit (low/high) for alarms, warnings and tolerance
11. Create the import file for the process tag type:
 Create a new import file with meaningful name (e.g. XIA4x4_y). The instances will
differ at the naming positions x (1 or 2) and y (1…3).
 Open the import file and insert a column "ImportMode".
 At this time the import file contains only one row. Duplicate the row to prepare the 6
instances XIA414_1, XIA414_2, XIA 414_3, XIA 424_1, XIA 424_2 and XIA 424_3.
 Set the ImportMode to "Ignore" for the starting row.
 The following steps can be carried out by use of Microsoft Excel in the file format
CSV as alternative option.

 Modify the rows for the instances in a kind that these instances are created in the
proper plant hierarchy folders with the correct symbolic interconnections.
 Save a backup version of your import file.
12. Import the file to create the process tags in the project.
 Check in the plant view, if all charts are located in the correct folders and have
correct names.
 Compile and download the charts.
 Compile the OS.
13. Test the functions.

10.12 Adopt existing charts as process tags
Goal
The valves in the material tanks are already programmed as CFC charts in the plant
view. The goal of this exercise is to create a process tag type for the valves in the rest of
the plant and adopt the existing CFC charts as process tags.
Procedure
5. You create a process tag type from one of the existing material tank valves. You modify
the name of the process tag type and use the following I/O points for signals and
accordingly parameters:
Block I/O Signal / Parameter

FbkClose PV_In Signal
FbkOpen PV_In Signal
Output PV_Out Signal
Valve MonTiDynamic Parameter
6. Open the chart of the process tag type and delete the textual interconnections to the
block inputs ModLiOp and AutModLi at the VlvL block.
7. Assign an import file to the process tag type and modify the file to allow the adaption of
existing charts:
PH Chart
Johnsson\Materialtanks\M110\ V112
Delete the content of all other cells to avoid an overwriting of information which is
already configured in the charts.
8. Perform the import and check in the plant view, that…

 …no additional charts are created.
 …the existing charts have the status of instances related to the process tag type
now.

10.13 Export process tags and modify process tag type
Goal
The process tag type for the valve should be extended with the static monitoring time
without losing information in the existing process tags. In this task, you will first make an
export of the existing process tags, based on the already assigned import file. Then, you
can add the required signal/parameter to the process tag type and modify the import file
accordingly.
Procedure
1. Export the process tags, which you adopted in the task before. As default, the export file
is created with the name "<name of process tag type>_Exp.iea", containing all signals
and parameters according to the defined I/O points. Open this export file to check the
content.
14. Expand the process tag type by the parameter MonTiStatic.
15. Assign the export file to the modified process tag type as import file. Pay attention to the
empty check box of the I/O point for the static monitoring time.
16. Open the import file and add a new parameter column. Rename the column header to
"Valve.MonTiStatic" and define the values for the instances.
17. Save and close the import file. Supposing that the column header has the correct syntax
you will realize, the check box of the I/O point for the static monitoring time is now
activated.
18. Perform a reimport of the process tags and check the correct configuration of the static
monitoring time in the charts.

10.14 Manual creation of CMT for the reactor inlet valves
Goal
Create a Control Module Type from the existing chart V311. You replace the existing
process tags V311…V341 by the corresponding instances (CMs) of the CMT.
Procedure
1. Create a new process tag type beginning from chart V311 similar to the tasks before.
 You need the following I/O points:
 PV_In of the digital input channel block FbkClose (signal)
 PV_In of the digital input channel block FbkOpen (signal)
 PV_Out of the digital output channel block Output (signal)
 MonTiDynamic of the Valve block (parameter)
 Rename the process tag type meaningfully, e.g. V3x1
 Make sure, the run sequence group of the chart is located in OB35.
2. Create now a Control Module Type from the process tag type V3x1.
 In the plant view of the SIMATIC Manager navigate master data library and select the
context menu command
Plant Types > Create Control Module Type from Process Tag Type…
 There appears a dialog with a list of available process tag types. Select the desired
process tag type and confirm with "Create".
 The new created CMT has the same name like the process tag type, completed by
an automatically generated extension. Both objects must not have the same name.
3. Create the instances for the reactor inlet valves in R310…R340.

 Copy the new CMT.
 Insert the duplicates in the corresponding hierarchy folders for dosing in
R310…R340. This results in CMs with the same name.
 Delete the existing charts V311…V341
 Rename the new CMs into V311…V341.
 In the Process Object View, interconnect the input signals V3x1_O, F3x1_C for the
feedbacks and the output signalsV3x1 for the control output.
4. Compile and download the program and test the function.
5. The instances V321 and V331 needs the following variation, to be configured in CFC:
 MonTiDynamic = 10 sec (monitoring time at VlvL block in V321)
 If the dose tank D230 is empty, the locking input Permit of the valve V331 shall be
locked.
 You need an additional interlock block Intlk02 (family Interlck) and a compare block
CompAn02 (family LogicAn) for the modification in the chart V331.


10.15 Synchronization of modified CMT

Übungen
Goal
Übung: Synchronisieren Sie einen modifizierten CMT
The reactor inlet valves of R310…R340 are manually modified from chart to chart.
Aufgabenstellung: Der CMT
Despite für die
this, the Reaktoreingangsventile
control wirdvalves
module type for these modifiziert.
is to be changed and
synchronized to these charts.
Es sollen 3 optionale Bausteine verfügbar sein:
TheEin
CMTZählerbaustein fürinlet
for the reactor die Schaltspiele
valve has todes Ventils und3je
be modified. ein
additionally blocks should be
available: One counter block for the valve action and interlockbzw.
Verriegelungsbaustein für den Verriegelungseingang Intlock Permit.
blocks for the locking
inputs Intlock resp. Permit.
Permit Valve Valve_OhSc

Intlk02 VlvL CntOhSc
Ctrl InOh
InCnt
Interlock Permit
Intlk02
Intlock
ExtMsg1 HrsHiL1A
ExtMsg2 CntHiL1A
Procedure
1. Open the chart of the new created CMT for the reactor inlet valve.
2. Insert the necessary block instances in the chart including the interconnections to the
valve block.
 The first interlock block has to be interconnected to the Permit input of the valve.
 The second interlock block has to be interconnected to the Intlock input of the
valve.
 Rename the interlock block instances corresponding to the locking type.
 Use the CntOhSc block of the APL as the counter.
 Interconnect the InCnt input to a switching valve output, to read the valve
action.
 The input parameter InOh needs the same information from the valve block, to
determine the operating hours. Both input parameters can be interconnected to
the same valve output.
 Optionally, you can interconnect the output of the limit monitoring of the counter
block to the inputs for external event signals of the valve block.
 Set the input parameter UpOp to "1", to activate the counting.
3. Open the "Technological I/Os" area of the CMT in the CFC editor and create the
required CMT interface objects by Drag&Drop of the new blocks. Use the same
procedure to create the subordinated parameters (locking inputs of both interlock
blocks).
4. Declare the interlock blocks and the counter block as "Optional".

5. The internal interconnections between the interlock blocks, the counter block and the
valve block must be represented in the CMT interface as well. You may use again the
Drag&Drop procedure for this purpose.
6. Synchronize the modified CMT with the existing CMs in the plant hierarchy.
 Start the synchronization via the context meu command
"Plant Types > Synchronize…" in the Plant view of the user project.
 Select the CMT to be synchronized and start the synchronization.
 Check the CMs. Until now you did not assign variations.
20. Assign different variations to the CMs in the reactors R320…R340 combining the
interlocking functions and the counter.
Interconnect the locking input parameters to the level limit monitoring of the
corresponding dose tanks.

10.16 Walk-through the APL Start project
Goal
You test several functions and make yourself familiar with the operation of the APL.
Procedure
1. The operating mode of all blocks can be switched over individually in the starting
project.
 Test the switchover between manual mode and automatic mode for valves and
pumps of the material tanks:
If these valves and pumps are in automatic mode, then they should react
automatically on material requests: Valve is opening and the pump is starting, if a
dose valve for the corresponding material is opened.
2. Configure a central switchover of the operating mode for all valves and pumps of the
material tanks by use of an APL operator block.
 Open the chart "M-General" in the hierarchy folder Materialtanks/M-General.
 You will find there: one inverter block Not01 and two Or04 blocks.
 Insert an operator control block OpDi03. Rename the instance and interconnect the
outputs Out1…Out3 of the OpDi03 with the inputs of the already existing logical
blocks:
 The Out1 output shall enable the switchover of the operating mode (ModLiOp at the
technological blocks).
 The Out2 output shall be responsible for a central switchover to manual mode via
link (ManModLi at the technological blocks).
 The Out3 output shall be responsible for a central switchover to automatic mode via
link (AutModLi at the technological blocks).
 Open the block properties dialog of the OpDi03 and make the input parameters
SetOp1...SetOp3 visible.
 Open the I/O properties dialog of each of these input parameters and configure a
meaningful labelling text (e.g. "At the block", "Manual", "Automatic").
3. Compile and download the program (without AS stop).
4. Compile the OS and test the operation.
Additionally tasks (optionally)
5. The 3 material tank pumps have to abide a warning time (e.g. 2 sec), before they start in
automatic mode.
6. The temperature controller TICA315 shall track the internal setpoint SP_Int to the
process value PV if running in manual mode. This function allows a bumpless transfer
from manual mode (input of manipulated value, open control loop) to automatic mode
(input of internal setpoint, closed control loop).

automatisch abgelassen werden. Dieser Vorgang soll von einer Meldung begleitet
werden.
Projektieren Sie die zeitgesteuerte Ausgabe des erforderlichen Steuersignals mit
Hilfe des Bausteins TimeTrig. Der Meldetext wird im CFC mit Hilfe des
entsprechenden Konverterbausteins StrgToBy festgelegt.
Die OS-Bedienberechtigung für die Festlegung / Bedienung eines Einzeltriggers
soll nur dann vorliegen, wenn der Reaktor R340 nicht leer ist und sich die
10.17 OS operator permissions
notwendigen and
Aggregate/Ventile time triggered
im Automatikbetrieb draining of R340
befinden.
Projektieren Sie mit Hilfe des StrctCom Bausteins einen Datensatz von OS
Bedienberechtigungen, der auf den OS_Perm Eingang des Bausteins TimeTrig
Goal verschaltet wird.
TimeTrig SFC Ablassen

Logik StrctCom
Trigger
Bitxx
MonAnL
OS_Perm StrgToBy
ExtMsgxx
ExtValyy
The reactor R340 has to be drained

Trainingsunterlage SP-PCS7CWS 8 - 23
automatically after a delaySITRAIN
time defined by the
operator. This action is to be associated with a message.
Configure the time triggered output of a control signal by help of the TimeTrig block.
The message text is provided by the converter block StrgToBy.
The OS operator permissions are fulfilled, if reactor R340 is not empty and all necessary
aggregates (pumps, valves) are in automatic mode.
Configure a dataset of OS permissions by help of StrctCom block, to be
interconnected with the OS_Perm block input of the TimeTrig block.
Procedure
1. Insert a chart Timer in the hierarchy folder "Drain" of reactor R340.
2. Insert an instance of the TimeTrig block and of the StrctCom block in this chart.
3. Determine the necessary bits of the OS_Perm parameter to be changed by use of block
help for the TimeTrig block. The goal is, to inhibit operation and parameterization of the
periodical trigger in the faceplate.
 This is not related to possible operating modes of the TimeTrig block.
4. Configure a block logic providing the required bits for the OS_Perm parameter if the
following conditions are true:
 The level of reactor R340 is larger than 0.
 The draining valve V342 and the draining pump P343 are in automatic mode.
5. Interconnect the result of this logic to the StrctCom block and furthermore the output of
this block to the relevant OS_Perm input parameter of the TimeTrig block. Do not forget
to make a static parameterization of all other bits of the OS_Perm directly at the
StrctCom block.
6. Compile and download the AS program and compile the OS.
7. Test the function of the TimeTrig block.
8. Insert an instance of the StrgToBy block in the chart LIA344. Interconnect this block to
the input ExtVaxxx for associated values of external messages at the MonAnL block.

 The MonAnL accesses to 2 ALARM_8P instances. The associated values

ExtVa104…108 are freely available and related to the signal inputs of the first
ALARM_8P instance. The associated values ExtVa204…208 are corresponding to
the second ALARM_8P instance.
You can recognize the assignment to the ALARM_8P instances easily in the "PCS7
Message Configuration" dialog:
1. ALARM_8P: MsgEvId1 with signal inputs SIG1…8, allocated completely by the
limit monitoring function.
2. ALARM_8P: MsgEvId2 with signal inputs SIG1…8, the inputs SIG1…SIG2 still
allocated by the limit monitoring and the CSF evaluation.
The block inputs ExtMsg1…3 are related to the second ALARM_8P instance with
SIG3...5.
9. Open the "PCS7 Message Configuration" dialog of the MonAnL block and configure the
message text for SIGx in a kind that the associated value is interpreted as String and is
integrated in the message text.
 You can type a static text behind the place holder for the block comment. The
forwarded associated value will become the (dynamic) part of the message text as
long the correct format syntax is used.
 See [641] SIMATIC - Programming with STEP 7 - 03_2006, 16.4 for tips for editing
messages
10. Compile and download the AS program and compile the OS.
11. Test the correct output of the message text.
12. Interconnect the Trigger output of the TimeTrig block to the ExtMsgx input for
external messages of the MonAnL in the level monitoring of LIA344, as well to the
control input to start the sequential control for draining of reactor R340.
13. Compile and download the AS program and test the function.
 The sequential control must be in automatic mode, if you test the automatic draining
function. Furthermore, a SFC cannot be started as long as a start disable bit is active.
Make sure that the output QDIS_START is visible for test purposes.
QDIS_START = 1 means start disable is active.
12_2015, 16.3.4 for more start conditions of a SFC (chart / instance).

10.18 Configuration of dosing material 1…3 into the Dose tank D210
Goal
Until now, the dosing of material was realized using a sequential function control.
You change the dosing configuration now to use of the DoseL block. Hereby, each
material is dosed with another dosing application:
 Material1: Dosing type "Flow" with 2 binary valves for coarse feed and fine feed
 Material 2: Dosing type "Weight (filling)" with 2 binary valves for coarse feed and fine
feed
 Material 3: Dosing type "Flow" with analog valve (without PID controller and without
auxiliary valve)
Procedure
1. Create new charts "Material1"…"Material3". Insert a DoseL block instance (from the
APL) in each of these charts.
2. For Material1 (Flow mode with coarse dosing / fine dosing via V211/VF211):
 Configure the interconnection to the process value (here: flow measured by FIA216).
 Configure the control of the binary valves for coarse flow / fine flow.
 Set the Feature Bit5 for the correct dosing type of the dose block.
 Set the Feature Bit8 for the desired fine dosing quantity (relative or absolute)
 Set the Feature Bit6 for automatic reset dosing quantity at start of dosing.
22. Compile and download the S7 program and compile the OS. Test the basic function.
23. Improve the configuration by additional interconnections and parameterizations required

for monitoring limits, units, and alarms. Define tolerance limits for underdosing /
overdosing.
24. Repeat the steps 2-4 for the other materials.

 Notice, that in case of "Material2" the process value has another meaning. Therefore,
you should give another setting to Feature Bit 5.
 Notice, that in case of "Material3" another type of control output is required for the
analog valve CV218 (via output SP of the dose block). The signal range is 0...100%.
Make the proper setting at Feature Bit 15 to get a correct graphic display of the
range.
25. Optimize the dosing function by suitable parameterization for dribbling resp. post
dosing.

10.19 Optimization of the PID Controller
Goal
The parameters of the PID controller in the loop TICA315 are not optimal. Use the PID
tuner to optimize the controller and use the "Control performance monitoring" to check
whether the behavior has improved.
Main steps
1. Checking the actual step response performance:

 Make sure that the OS runtime is active.
 Open the Default view of the faceplate of the controller TICA315 and set the
controller to auto mode.
 Open the Setpoint view ( ) of the ConPerMon faceplate.

 Increase the controller setpoint by 20°C and wait until a steady state has established
("Constant PV" is indicated by ConPerMon).
 Check the ConPerMon faceplate and write down the results:
Absolute overshoots…
Overshoot…
Settling time...
Settling ratio...
 Change the setpoint to its previous value.
2. Optimize the controller:

 Open the chart TICA315 (R310, Heat).
 Set Input Parameter OptimEn of the PIDConL block to visible.
 Enable the test mode of the CFC-Chart.
 Change the value of the input parameter OptimEn to 1 or enable optimization in the
faceplate of the PID controller (Parameter tab).
 Start the PID tuner in the CFC chart TICA315.
(Select the controller block, start the PID tuner by selecting
Edit –> Optimize PID Controller…
and execute the optimization process as a PI controller)
 Use the new controller parameters.
3. Check the new step response behavior:

 Once more, increase the controller setpoint by 20°C and wait until a steady state has
established.
 Check the ConPerMon faceplate and write down the results:
Absolute overshoots…
Overshoot…
Settling time...
Settling ratio...
 Compare the results with the values before the optimization.

 Change the setpoint to its previous value.
4. Check the steady state behavior:

 Make sure the controller is in auto mode and in a steady state.
 Open the ConPerMon faceplate in the Parameter ( ) view.

 Click the Initialize button (Actual PV and MV are applied as PV reference and MV
reference).
 Check the evolution of the CPI, the standard deviation and the mean values in the
Standard view of the ConPerMon faceplate.

10.20 Heating and draining R3x0
Goal
Complete the steps and transitions regarding heating and draining for reactor R3x0.
Main steps
1. Add the attribute S7_contact = true to the output parameter ER of the PIDConL Block
type in the master data library, update the block type in the multiproject. By doing so,
this parameter can be used to check whether the temperature in the transition
Temp=OK is reached.
2. Open the SFC type R3x0 in the Charts folder in Lib0x.
3. Add a setpoint "Temp" of the data type REAL.
4. Add a block contact "TICA3x5" of the PIDConL block type.
5. Add a process value characteristic "R3x0_Lvl" of the data type REAL for reading the
reactor level.
6. Check, if a timer is already configured and complete its configuration if necessary:

 WT
You may assign the type of the timer WT_Mode (e.g. OnDel) later either in a step of the
sequence of the SFC type or parameterize the timer type on the SFC instance inside of
the chart (external view of the SFC).
The timer value is calculated as result from the reaction time setpoint + additional
constants per material depending on its amount. The calculated time is assigned to the
Timer.
WT_TIME0 := reaction time [s] + 0.15[s/kg] * Q_Mat1 + 0.085[s/kg] * Q_Mat2 +

0.065[s/kg] * Q_Mat3
7. Complete the steps StartHeat and StopHeat and the transitions Temp=OK,
ValveClosed and Empty as described in the step and transition comments using these
newly created characteristics.
Make sure that the PID controller is set to auto mode resp. external setpoint in the step
Auto Mode and that these modes are released again in the step Release modes.

Exercise: Setpoints and block contacts
Heating and draining R3x0 SIMATIC PCS 7 AS Engineering
Switch on the heating: set controller external setpoint
Check whether the setpoint temperature is reached

ER < 2 and ER > -2
Switch off the heating: set controller external setpoint to 0
Check whether heating valve is closed
Check whether Reactor R3x0 is empty
SITRAIN
8.Course ST-PCS7ASEIn the folder R310, delete the SFC chart9R310
- 23 and create a new CFC chart R310. The Siemens AG © 20
chart R310-Gen can be deleted as well.
9. Open the CFC chart R310 and create an instance of the SFC type R3x0, interconnect it
with the control modules and the level and temperature measurements and test your
work in the SFC test mode.
10. Compile and download the AS, compile the OS and check your work in the OS.
Remember to open either V411 or V412 in manual mode in order to drain the reactor.

10.21 Cleaning control strategy
Goal
Create a second control strategy for cleaning the dose tank and the reactor.
Main steps
1. Rename the sequencer RUN to Production.
2. Create a new sequencer called Cleaning.
3. Create the control strategy characteristics, called Production and Cleaning.

Configure the control strategies in such a way that the setpoints are only valid for the
production control strategy.
4. Define the correct start condition for the sequencers Production and Cleaning.
5. Create a timer characteristic, called WaitTime.

Create parameter characteristic, called Time, which will be used to specify the wait
Exercise 32: Control strategies
time.
Cleaning control strategy
6. Program the actions and conditions as shown below.
Switch valves, pumps and

Switch off heating
controller to auto mode
Check operating modes Check heating valve closed
Fill from M130 Open drain valve
Check level 395 kg Check drain valve opened
Close dose valve 3 Start drain pump
Check dose valve closed Check reactor empty
Transfer to reactor Stop drain pump
Check dose tank empty Check drain pump stopped
Close transfer valve Close drain valve
Check transfer valve closed Check drain valve closed
Heat to 100°C, keep for x s. Release operating modes
Check temp OK and time elapsed
SITRAIN
Be smart by copying
Course ST-PCS7ASE
steps and transitions from 9the
- 29
production sequencer. Siemens AG © 2012
7. Compile and download the AS, compile the OS and check your work in the OS.

10.22 Sequencer for holding and resuming
Goal
Hold the SFC type in such a way that the process is held as well.
Main steps
1. Exercise: Hold the

Create adequate bit process in a safefor
memory characteristics way
storing the states of the valves, pumps
Sequencer
and mixer.for holding and resuming
2. Modify the Holding and Resuming sequences as shown in the following picture:
HOLDING RESUMING
Save states of the

control modules to Bit
Memories
Switch valves, pumps and

controller to auto mode
Switch the control Check operating modes

modules to safe state
Restore the states

Check all valves closed saved in the Bit
Check pump stopped Memories
Release operating modes
Be smart by copying from the production sequencer.
3. SITRAIN Compile and download the AS, compile the OS and check your work in the OS.

10.23 Operator notifications
Goal
Provide additional information in the faceplate for the operator.
Whenever a control strategy starts, a note text must be issued. Moreover, a position text
must be issued as long as the mixer is running.
Main steps
1. Define the characteristics "Note texts" and "Position texts".
2. Change the "POSINO" and "OPTIPNO" in the corresponding steps to trigger the correct
message.
3. Compile and download the CFC and SFC, compile the OS and test your work.

10.24 (Optional) Calculate cycle time and memory requirements
Goal
Check whether our training project for the Johnsson plant will run on a CPU 414-3IE.
Main steps
1. Open the ProTime_PCS7_V82.xls Excel file.
2. Open the tab SW_Calc.
3. Select the AS414 IE in the combo box on top of your screen.
4. Apply the values you can find the next table in ProTime. The program should be
executed in OB32 (cycle time = 1s).
number
Open-close valves -> ValveLean 25
Motors -> MotorLean 11
Level measurement -> AnalogMonitoring 13
PID controller -> PIDConrolLean 4
SFC sequencers 4
Total number of sequence steps 84
APL ConPerMon 4
APL Or04 4
5. Evaluate the results regarding cycle time, memory requirements en required PO's for
AS and OS.


ST-PCS7ASE V8.2.0 en

Uploaded by

Document Information

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

ST-PCS7ASE V8.2.0 en

Uploaded by

Copyright:

Available Formats

Course ST-PCS7ASE

SIMATIC PCS 7 Documentation and

3 PCS7 Project handling

5 Type Instance Conceptions in PCS7

Course from: to:

Copyright © Siemens AG 2016. All rights, including

SITRAIN courses on the internet: www.siemens.com/sitrain

SIMATIC PCS 7 – Introduction of the training

SIMATIC PCS 7 – Introduction of the training

1 Introduction of the training

The participant will learn about

Concept of this course

General workflow of a PCS 7 project This course

Hardware and Software

Including In brief, is main subject to the

Course ST-PCS7ASE 1-3 SITRAIN - Siemens AG © 2016

SIMATIC PCS 7 – Introduction of the training

Road map of this course

System design – Planning and specifying hardware components

Type-instance conceptions with SIMATIC PCS7

Technological Engineering with APL

Advanced Process Control with APL

Sequential control using SFC-Types

ourse ST-PCS7ASE 1-4 SITRAIN - Siemens AG © 2016

SIMATIC PCS 7 – Introduction of the training

1.4 Additional documentation

Below you find the way the available documentation is represented

Course ST-PCS7ASE 1-5 SITRAIN - Siemens AG

SIMATIC PCS 7 – Introduction of the training

1.5 Training equipment

SIMATIC PCS 7 – Introduction of the training

1.5.2 Signal Box

Switches and buttons,

SIMATIC PCS 7 – Introduction of the training

Source for Source for

(AO0 or AI0) AI0 (AO1 or AI1) AI1

Wire break Shortened to M No Power

SIMATIC PCS 7 – Introduction of the training

Digital Output – Hardware Channel # (DP ET 200M slot 5)

Analog Output – Hardware Channel # (DP ET 200M slot 7)

AI0 AI1 AI2 AI3 spare

SIMATIC PCS 7 – Introduction of the training

1.5.3 Combined Engineering/Operator system

Engineering station and Rack PC‘s of different

Network architecture in the course

ES/OS (VM) ES/OS (VM) ES/OS

SIMATIC PCS 7 – Introduction of the training

1.6 Simulated model plant in this workshop

1.6.1 Functional process description of the Johnsson plant

Process diagram - Johnsson

(V111) (V121) (V131)

LT214 LT224 LT234 LT244

4s V311 V321 V331 V341

LT314 CV315 LT324 CV325 LT334 CV335 LT344 CV345

5s V312 V322 V332 V342

LT414 LT424 Buffer tanks

SIMATIC PCS 7 – Introduction of the training

SIMATIC PCS 7 – Introduction of the training

 Each of the individual devices in the process is to be monitored and operated

1.6.2 Plant expansion during the workshop

You divide the combined AS/OS Project

SIMATIC PCS 7 – Introduction of the training

M110 M120 M130