09 - Basic Functions For Operator Control & Monitoring - V9 - 12 16 12 22

2
12
SIMATIC PCS 7 System Course
16
12
1
9
og
Contents
Pr
e
g
9 Basic Functions for Operator Control & Monitoring ............................................ 3
En
9.1 Learning objectives ................................................................................................................ 3
7
9.2 General .................................................................................................................................. 3
9.2.1 Overview ................................................................................................................................ 3
S
9.2.2 Single-user and multi-user systems ...................................................................................... 4
22
9.2.3
PC
Flat system architecture......................................................................................................... 6
9.2.4 Configuration limits ................................................................................................................ 7
12
9.2.5 WinCC Explorer / Storage location of the OS project ............................................................ 8
IC
9.3 Settings in the plant hierarchy ............................................................................................... 9
16
AT
9.4 OS-AS connection ............................................................................................................... 13

IM
9.5 Project type .......................................................................................................................... 18
12
9.6 Compiling ............................................................................................................................. 19
-S
9.6.1 Overview .............................................................................................................................. 19

9.6.2 Settings ................................................................................................................................ 20
1
z
9.6.3 Deriving / updating block icons ............................................................................................ 23

Fo
9.7
og
Layout .................................................................................................................................. 25
9.7.1 Skin & Design ...................................................................................................................... 25
Pr
ig
9.7.2 Settings for OS Runtime design .......................................................................................... 26

rF
9.8 Activating OS Runtime......................................................................................................... 28

e
o
9.9 Block icons and faceplates .................................................................................................. 29

g
at
En
9.9.1 Difference between block icons and faceplates .................................................................. 29

9.9.2 General information on faceplates of the APL ..................................................................... 30
ig
9.9.3 Display of block icons .......................................................................................................... 32

7
av
9.9.4 Operator input in faceplates and block icons....................................................................... 32

9.9.5 Operator authorization levels ............................................................................................... 34
S
N
9.9.6 Creating/updating block icons.............................................................................................. 36

PC
9.10 Exercises and checkpoints .................................................................................................. 40

IC
AT
IM
-S
z
Fo
ig
rF
a to
SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

ig
Course folder, V9.0.0, ST-PCS7SYS 9-1

av
2
12
16
12
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig
9-2 Course folder, V9.0.0, ST-PCS7SYS

av
2
12
16
9 Basic Functions for Operator Control & Monitoring
12
Learning objectives
9.1 Learning objectives
1
The participant knows
og
 the basic functions of an OS
Pr
 the importance of the OS-AS connections
and the plant hierarchy
e
 the mechanism for creating/updating
g
block icons
En
The participant can
7
S
 configure an OS with the basic functions
22
PC for operator control and monitoring and
activate it (with standard settings for
12
operator input, layout, window, etc.)
IC
16
AT
IM
9.2 General
General –
12
-S
9.2.1ToolsOverview
for OS engineering
1
z
ST-PCS7SYS 9 - 2on SIMATIC WinCC.

The OS of SIMATIC PCS 7 is based SITRAIN © Siemens AG 2017
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
WinCC is used together with several WinCC options and supplementary tools in
SIMATIC Manager to form a key component of a PCS 7 configuration: the operator
station.
z
ST-PCS7SYS 9-3 SITRAIN © Siemens AG 2017

Fo
ig
rF
a to

ig

av
2
12
16
9.2.2 Single-user and multi-user systems
12
General –An OS can be configured as:
Multi-user system
1
Multi-user system
og
OS Terminals
Pr
ES OS OS
Client 1 Client 40
e
g
En
Terminal Bus
7
OS Servers (TCP/IP)
Server 1 Server 18
22
PC
System Bus (ISO)
12
ASx (Plant Bus)
AS1
IC
16
AT
IM
12
-S
1
z
Servers are responsible for communication with the AS, for screens and for archiving of
Fo
ST-PCS7SYS tags and messages. 9-4

og
SITRAIN © Siemens AG 2017
Client(s) provide the user interface.

Pr
ig
In a multi-user system, one or more OS servers supply up to 40 operator stations (OS

rF
clients) with data (project data, process values, archives, alarms and messages) via a
terminal bus. The terminal bus can share the transmission medium with the plant bus or
o
be implemented as a separate bus (Ethernet with TCP/IP).

at
En
In the case of more stringent availability requirements, the OS servers can also be
ig
operated redundantly. Critical applications are monitored for software errors via a health
7
av
check. If an error is detected, a redundancy failover is made if necessary.

S
Synchronization of the redundant OS servers takes place automatically and at high

N
PC
speed.
The broad colored arrows in the above figure symbolize the information exchange
between the AS and OS or between servers and clients.
IC
The OS Runtime is executed on the OS servers and OS clients.

AT
IM
Central engineering
-S
Whatever the system architecture looks like, the engineering station is always the
source for the complete configuration All configuration data is downloaded from the ES
to the target system. The figure above illustrates that with dashed black arrows.
z
Fo
OS simulation
ig
The OS Runtime of a server must not be activated on an ES! To ensure the possibility
rF
of testing an OS configuration on the ES in Runtime without disturbing the active OS

server, an OS can be simulated on the ES.
a to

ig

av
2
12
General –
16
Single station system
Single station system
12
ES OS
1
og
Pr
Terminal Bus
(TCP/IP)
e
g
En
System Bus (ISO)
(Plant Bus)
AS1 AS64
7
S
22
PC
12
IC
16
AT
In a single-user system, all operator control and monitoring functionality for a project
ST-PCS7SYS (plant/unit) are concentrated in 9one
- 5 station. This OS single station can
SITRAIN be operated
© Siemens AG 2017 on
IM
12
the plant bus together with other single-user systems or in parallel with a multi-user
system. Redundant operation of two OS single stations is also possible (SIMATIC
-S
General – PCS 7 single station redundancy).

Special case: Combined ES/OS
1
z
Fo

og
Pr
ig
ES/OS
rF
e
o
g
at
En
ig
Terminal Bus
av
(TCP/IP)
S
N
PC
System Bus (ISO)

(Plant Bus)
AS1 AS64
IC
AT
IM
-S
z
The single station system is the smallest possible configuration. A PC station that
Fo
ST-PCS7SYS represents both the ES and the OS9 - 6 is created in the PCS 7 project.
If the OS and ES are operated on one computer, you do not have to download the OS
ig
because all the necessary data is already available. Here it's enough to run the
rF
"Compile OS" function.

a to

ig

av
2
12
16
9.2.3 Flat system architecture
12
For small and medium-sized plants, implementation is now also possible in a very flat
system configuration without an OS server. In this case, only OS single-user stations
are used, and the number can be expanded up to a maximum of 8 single-user stations.
1
 The normal separation into a plant bus and terminal bus in an OS server/OS client
og
structure does not happen in this case, which means that each single-user station is
General – connected directly to the AS.
Pr
 With
Flat system architecture
such a configuration, configuring can be streamlined by duplicating a basic
e
project.
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
ST-PCS7SYS
The "flat system architecture" was9previously
-7
released for PCS 7 Version V8.0 SP1 for
at
En
small to medium-sized project sizes with up to 8 OS single station systems and

including a redundant OS single station system.
ig
7
av
This architecture can be expanded to include a web server and web clients (up to 3 web
clients), OPC communication (with OpenPCS 7 license) and SIMATIC Batch.
S
N
PC
Display of operator and process control messages

IC
 Locally generated operator messages and local process control messages are
displayed on an OS single-user station.
AT
 A system-wide overview of the operator and process control messages is provided

IM
with the help of the Process Historian / Information Server.

 The operator messages of the individual OS single-user systems are added back into
-S
the local archive segments of all OS single station systems with the help of the PH
and can thus be displayed in all OS single station systems.
z
Fo
ig
rF
a to

ig

av
2
12
16
9.2.4 Configuration limits
12
OS configuration
Configuration limits for limits
OSexist – of a PCS 7 multiproject:
at each level
stations
 The
Number of stations
maximum number of stations (AS, OS server, OS single user station, OS clients,
1
etc.)
og
Max. 4 per OS station
Max. 40 per system
Pr
ES OS Single OS OS Web
Station
Client Client
e
Monitor
g
Max. 40 per
En
multiproject
Max. 100 per
7
Max. 8 per MS Server OS Server PCS 7 web
S
multiproject server
22
PC
12
1 per Max. 18 per
IC
AS multiproject multiproject
16
AT
Max. 64 per
IM
12
OS server
-S
1
z
Configuration limits
 Maximum for OS
number objects–
stations
of process
Fo
og
Number
ST-PCS7SYS of PO, process
 Maximum tags
number of and
process
9 messages
tags
-8 SITRAIN © Siemens AG 2017
Pr
ig
 Maximum number of configurable messages

rF
ES OS Single
o
OS
g
Station
at
En
Clients
ig
7
av
S
N
PC
Max. 8500 PO MS Server OS Server

Approx. 4500 tags
IC
AT
Max. 12000 PO
AS Approx. 7000 tags
IM
Max. 216000 PO per project Max. 200000

Max. 128000 tags per multi-user configurable
-S
Max. 2600 PO per system messages

CPU 410-5H
z
Fo
ig
rF
ST-PCS7SYS 9-9 SITRAIN © Siemens AG 2017

a to

ig

av
2
12
16
9.2.5General
WinCC
– Explorer / Storage location of the OS project
12
WinCC Explorer / Storage
After insertion location
of a PC station of theapplication
with a WinCC OS projectinto the multiproject, the OS
project is stored in a subfolder of the project path, as shown in the figure:
1
The path to the storage location
og
depends on the structure of the
multiproject and how it was created
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
All pictures of an OS
IM
project are located here
12
-S
1
z

ST-PCS7SYS
The GraCS subfolder contains all9 -pictures
10 of an OS project. SITRAIN © Siemens AG 2017
Fo
og
To enable use of pictures from different multiprojects in your own current OS project,
General – these must first be copied to the GraCS folder!
Pr
ig
Opening anToOS
editproject
rF
the contents of an OS, the OS must be opened from the component view of the
e
SIMATIC Manager: WinCC Explorer then starts.

o
g
at
En
ig
7
av
S
N
PC
IC
AT
SIMATIC Manager WinCC Explorer

IM
Detailed window
-S
with the objects

List of editors: that are being
z
edited by the editor

Fo
Each editor opens its

own application window
ig
or is part of the
Configuration Studio
rF
to
ST-PCS7SYS 9 - 11 SITRAIN © Siemens AG 2017

a

ig

av
2
12
16
9.3 Settings in the plant hierarchy
12
Settings in
Thethe plant
settings hierarchy
for the plant hierarchy affect the content and display of data in the OS.
They are relevant to the structure of the picture hierarchy and the tag names.
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
 Included in HID (HID = plant designation)
1
z

Fo
og
You can select which levels are to be included in the HID through their hierarchy
folder names. Only the hierarchy folders marked for inclusion in the HID have their
Pr
ig
names included in the HID. Hierarchy folders that are not selected for inclusion in the
name can be used to create additional "drawers" (for example, for supplementary
rF
documents, such as plant descriptions, process tag sheets, etc.).

e
o

at
En
When assigning the name, ensure that the tag name does not exceed 128 charac-
ters. This is a requirement for compiling the OS. The name consists of the following
ig
elements: names of the hierarchy folders in the hierarchy path, the chart name, the
7
av
block name, the separator, and the connection name.

S
N
 With separator
PC
With this option, you insert a separator in the HID after the names of hierarchy folders
of this level. Separators are used in the textual representation of the hierarchy path to
IC
better differentiate between the names of the hierarchy folders. The "\" character is
used as the separator.
AT
Note: the last hierarchy folder included in the HID is always followed by a separator
IM
that cannot be deselected.

 OS area
-S
With this option, you can decide which hierarchy level is to be regarded as the OS
area level. Only the top 3 levels can be OS area levels. The default setting is the 1st
z
level. The definition of an OS area is necessary for area-specific messages in

Fo
process mode.
ig
rF
a to

ig

av
2
12
16
Picture Tree Manager
–
12
Settings in The
themanner
plantinhierarchy
which pictures are arranged within the OS areas (picture hierarchy) can
Picture TreebeManager
seen in the Picture Tree Manager. This tool is a component of WinCC Explorer and
is integrated in WinCC Configuration Studio as of PCS 7 V9.0.
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
Effects of the plant hierarchy on the OS areas
12
OS areas can be selected directly via buttons in OS Runtime.
-S
OS operating
1
z
ST-PCS7SYS 9 - 14 areas of the PH

Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
PH level 1
PH level 2 OS area level
-S
PH level 3
ST-PCS7SYS SITRAIN © Siemens AG 2017
The picture hierarchy as is seen in9 -the
14
Picture Tree Manager is reflected in the layout of
selection buttons within the OS areas.
z
Fo
ig
rF
a to

ig
9 - 10 Course folder, V9.0.0, ST-PCS7SYS

av
2
12
16
Settings in the plant hierarchy –
Names of structure tags and tags
Names of tags
12
The names of structure tags (blocks) and tags contain the plant designation (HID):
 Tags:
1
og
Pr
e
g
En
7
S
22
PC
12
IC
Components of the tag name
16
AT
R310 LIA214 MonAnalog .PV#Value

IM
R310 LIA214 MonAnalog .PV#Value
12
PH path Chart name Block name I/O name
PH path Chart name Block name I/O name
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT

IM
-S
z
Fo
ig
rF
a to

ig
Course folder, V9.0.0, ST-PCS7SYS 9 - 11

av
2
12
Settings in the plant hierarchy –
16
Structure tags
 Structure tags:
12
1
og
Pr
e
g
En
7
S
22
Components of the structure name
PC
12
IC
R310 LIA214 MonAnalog
16
AT
Name of the R310 LIA214 MonAnalog

S7 program PH path Chart name Block name
PH path Chart name Block name
IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
See [104] PCS 7 V9.0 Operator Station – Configuration Manual – 05_2017, 6.4.3 for

IC
ST-PCS7SYS further details. 9 - 18 SITRAIN © Siemens AG 2017

AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.4 OS-AS connection
12
OS-AS connection –
Question: What
OSdomulti-user
the arrowssystem
represent in the following figures?
 OS multi-user system
1
og
ES
OS Clients
Pr
e
Terminal Bus
g
OS Servers (TCP/IP)
En
System Bus (ISO)
AS1 ASx
7
S
22
PC
12
IC
OS single station system

 OS single station system
16
AT
ES OS
IM
12
-S
1
Terminal Bus
z
(TCP/IP)
Fo
og
System Bus (ISO)
Pr
ig
AS1 AS64
rF
e
o
g
at
En
ig

7
 Special case:
av
Combined ES/OS
S
N
PC
ES/OS
IC
AT
Terminal Bus
(TCP/IP)
IM
System Bus (ISO)

AS1 AS64
-S
z
Fo
ig
Answer: Communication.
rF
Before communication between an OS and an AS is possible, a connection must be

established between both stations.
a to

ig

av
2
12
16
This is done using NetPro
12
A connection is configured between
 the WinCC application of the PC station (starting point of the "Insert New
NetPro Connection" dialog) and
1
 the CPU as connection partners in the AS.
og
Pr
e
g
3
En
1
7
S
22
PC
12
IC
16
AT
IM
12
Named connection
2
-S
1
z
Fo
ST-PCS7SYS 9 - 22
og SITRAIN © Siemens AG 2017
Named
Pr
ig
connection
rF
4
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
1. Select the object of the WinCC application.

2. Because this object can be connected, a connection table is displayed. Insert a new
z
connection in the table.

Fo
3. Select the connection partner. If you have begun with a WinCC application, the
CPU of the desired AS is the connection partner.
ig
4. Named connection: Instead of the default connection ID, assign a symbolic name
rF
as a placeholder for network parameters of the connection between the OS and AS.
Use a descriptive name.
a to

ig

av
2
12
16
Named connection
12
This principle is referred to as the "named connection". It is also relevant to redundant
OS servers and OS simulation operation.
Recommendation: assign the name of the AS involved to the connection. Once the OS
1
has been compiled, the name appears in the "SIMATIC S7 Protocol Suite" of the WinCC
og
Tag Management.
Pr
 For further details see:
[103] PCS 7 V9.0 Engineering System – 05_2017, 9.14.3 and
e
[104] PCS 7 V9.0 Operator Station – Configuration Manual – 05_2017, 6.2.2
g
En
Saving/compiling and downloading
Saving/compiling and downloading
7
S
22
PC
12
1
IC
16
AT
IM
12
The color indicates that
-S
the configuration has

not yet been compiled
1
z
Fo
og
2
Pr
ig
rF
e
o
g
at
En
ig
3
7
av

S
1. Use the "Save and Compile" button in the element bar of NetPro to start compiling
N
the network configuration.

PC
2. Recommendation: always include the configuration check.

IC
3. Once the configuration has been compiled, you can download the new OS-AS
connection.
AT
 No CPU Stop required:

IM
If only connections are being downloaded, the CPU of the station does not switch to
Stop state.
-S
z
Fo
ig
rF
a to

ig

av
2
12
Other
SIMATIC PCSoptions for downloading
7 System Course
16
 However, several other download options are also available:
12
Downloads not only the connections but also the configuration
of the stations: This requires a CPU STOP!
1
og
Pr
e
g
Downloads only connections and not the station configuration:
En
This does NOT require a CPU STOP!
7
S
22
PC
OS-AS connection – Result in the Station
Result in the Station Configuration Editor
Configuration Editor
12
IC
The Station Configuration Editor shows the result of the connection download:
16
AT

IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT

IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
OS-AS connection – SIMATIC PCS 7 System Course
16
Connection status in NetPro
Connection status in NetPro
12
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.5 Project type
12
A WinCC application is preset as a multiple station project in the original state, just as it
was inserted in the PC configuration.
1
og
Single-user system
Project type
Pr
If the system is to be used as a single station system, this change must be made in the
project properties:
e
g
En
7
S
Do not delete the
22
PC startup list when the
project type
12
changes!
IC
16
AT
IM
12
-S
1
z
Fo
og
 Only members of the SIMATIC HMI user group can edit WinCC projects.
Pr
ig

rF
ST-PCS7SYS See [104] PCS 7 V9.0 Operator Station

9 - 28 – Configuration Manual –SITRAIN
05_2017, 7.3.2
© Siemens AGfor
2017
e
further details on the OS project properties.

o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.6 Compiling–
Compiling
12
Overview
9.6.1 Overview
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
A large part of the OS data structure is specified in SIMATIC Manager and in the
configuration tools for the charts. This9data
- 29
is stored in the project database.
1
z
All the data that is relevant for the OS is transferred to a dedicated OS database using a
Fo
compile operation: og
Pr
ig
 See [104] PCS 7 V9.0 Operator Station – Configuration Manual – 05_2017, 6.5.1 for
rF
further details.
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.6.2 Settings
Compiling –
12
Settings The dialog box of a wizard enables the following settings to be made for the compile
operation:
1
og
Pr
e
g
En
7
S
22
PC
12
IC
Assign OS areas of the PH to an OS server.
16
AT
Assign an S7 program to an OS server.

IM
12
-S
 Area-oriented: With this setting you can assign an OS area from the plant hierarchy
to an OS server. The advantage of this approach is that PCS 7 itself checks which
1
z
ST-PCS7SYS 9 - 30OS server and only compilesSITRAIN

data pertains to the corresponding © Siemens
this data. AG 2017
Starting
Fo
with PCS 7 V6.1, this setting is the default setting.

og
 AS-oriented: With this setting you can assign an S7 program to an OS server. In this
Pr
ig
way you specify which OS is supplied by data of which AS. In this mode, all the data
rF
of an AS is assigned to an OS server. This was the default setting in PCS 7 V6.1 and
e
earlier.
o
g
at
En
 See [104] PCS 7 V9.0 Operator Station – Configuration Manual – 05_2017, 6.5.3 for
ig
further details.
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
Compiling –
16
Parameters
Starting the compilation
12
1
2
og
Pr
e
1
g
3
En
4
7
S
22
PC
12
IC
16
AT
IM
12
ST-PCS7SYS 1. Start the wizard for OS compilation
9 - 31 for the desired OS. SITRAIN © Siemens AG 2017
-S
2. Select the AS program to be compiled.

3. Open the "Select Network Connection" dialog.
1
z
Fo
4. Select "Named Connection" in the dialog. og

Pr
ig
Compilation scope
rF
 Tags: The tags are created below the named connection that was configured for
o
communication between the OS and AS.

g
at
En
 Messages: Message texts are stored in a text library. The number of columns in this
ig
text library is based on the "Language for Display Devices" setting.

7
av
 Units of measure, etc.: The strings for units of measure, identifiers, and block
S
comments are located in the "Internal tags" subfolder.

N
PC
 Structure types: Block types whose instances are inserted into CFC charts are
stored in the OS as structure types.
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
Compiling
SIMATIC – Course
PCS 7 System
Scope
16
However, the wizard needs additional information for the compilation scope:
12
1
3
og
2
OS Runtime must be
Pr
stopped for complete
compilation of the OS 4
e
g
En
1
The OS servers (or single-
user stations) remain in
7
Runtime during compilation
22
PC
1. Delete all AS data present in the operator station.
12
IC
2. This function enables the screen jump function in WinCC Runtime. In addition, the
OS comments are supplemented to include the interconnection partner. The
16
AT
function extends the mapper running times significantly.

The check box is only visible when SFC visualization has been enabled.
IM
12
3. With the "Minimum acquisition cycle" setting, you define the shortest acquisition
-S
cycle for the archiving of tags. The AS-OS engineering derives an acquisition cycle
for a newly created archive tag from the processing cycle of the block and the
1
"Minimum acquisition cycle".
z
Fo
4. "Create server data":

og
For a client in a distributed system to display the process data of different servers, it
Pr
ig
needs information about the corresponding data. To this end, server data
rF
(packages) are created in order to make this data available to the clients. The client
e
requires the server data from all servers whose process information it is to visualize.
o
The server data is automatically created/updated by the system when the OS is

at
En
compiled and downloaded. It can also be generated manually in the shortcut menu
ig
of SIMATIC Manager under "Create server data".

7
av
5. "Language Settings" area

S
N
You can use the button in this area to open a dialog box showing the languages
PC
installed in the PCS 7 multiproject. Each installed language affects the duration of
the OS compilation. You can therefore delete any unneeded languages in the
project here.
IC
Review your settings before starting the compilation. The result of the compilation is
AT
summarized in a log file.

IM
 If you delete an unneeded language in the PCS 7 multiproject, it will be difficult to

-S
restore the language later because even the standard texts (system texts) of this
language are removed from all language tables.
 See [121] PCS 7 Compendium Part A – Configuration Guidelines – 08_2016, 9.4 for
z
Fo
further details.
ig
rF
a to

ig

av
2
12
16
9.6.3 Deriving / updating block icons
12
By default, the block icons are derived or updated from the plant hierarchy of SIMATIC
Manager during the compile operation.
1
Compiling –
og
Stand-alone action
Deriving / updating block icons
This can also be initiated as a stand-alone action (separate from compiling) in the plant
Pr
view of SIMATIC Manager:
e
g
En
7
S
22
PC
12
IC
16
AT
IM
Requirement
12
Compiling –
-S
Deriving / updating block icons
1
z
Fo
og
Picture M110
Pr
ig
rF
Specify the display of the

e
name of the process tag

o
g
at
En
ig
7
av
S
N
PC
IC
AT
Scaling of block
Block icons are icons is possible
positioned at the
IM
top left For comparison …

-S
z
Fo
Based on the configuration in the plant hierarchy, the technological relationships

ST-PCS7SYS between the AS and OS components SITRAIN © can
9 - 34 are already known. This information Siemens
beAG 2017
used
in the plant hierarchy to automatically place and interconnect the ready-made block
ig
icons in the OS pictures selected for this purpose.

rF
Likewise, the block icons can be updated following a change.

a to

ig

av
2
12
16
Deriving / updating block icons Included lower levels
Included subordinate levels
12
1
og
Pr
Picture R310
The charts are in
e
the 4th PH level
g
PH level: 1 2 3 4
En
7
S
22
PC
12
IC
The picture is in
the 3rd PH level
16
AT
PH level: 1 2 3 4
IM
12
ST-PCS7SYS
In the "Lower hierarchy levels included"
9 - 35
combo box, you set the SITRAIN
number of AS
© Siemens AG 2017
-S
hierarchy levels to be taken into consideration when creating/updating block icons.

The background to this setting is the different description depths between the AS and
1
z
OS.
Fo
og
On the AS side, the charts are configured at the level of the process tags. The charts
are therefore inserted at the lowest level and only contain the control blocks with the
Pr
ig
drivers for process interfacing. In our example, the charts are at level 4.
rF
On the OS side, the objective is different. The pictures describe the plant in increasing
e
detail as you go down in level, but not as far as the process tag level. In our project,
o
the lowest level of the pictures is level 3.

at
En
As there are no pictures at the level of the charts, no block icons would be inserted by
ig
the Create/Update Block Icons wizard either. This problem can be solved by setting
7
av
"Lower hierarchy levels included" to 1. The block icons are then simply inserted in the
pictures that are one level up.
S
N
PC
The default setting is 1.

IC
Scalability of block icons

AT
The size of the block icons can now be scaled with the "Create/Update Block Icons"
function. You can thus respond to special requirements of the customer regarding
IM
workstation ergonomics and different screen resolutions.

 A uniform setting applies to all block icons that are introduced into the plant pictures
-S
by the "Create/Update Block Icons" function.

 Your project-specific setting is kept even after a PCS 7 software update.
z
Fo
ig
rF
a to

ig

av
2
12
16
9.7 Layout
12
9.7.1 Skin & Design
Layout – Skin & Design
1
The screen is divided into three areas in OS Runtime (WinCC Runtime):
og
Overview area
Pr
e
g
En
7
Work area /
S
Process pictures
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og Button area
Pr
ig

rF
 The name of the start screen (the first screen after Runtime starts) is @screen.pdl.
e
o
g
at
En
Button area
ig
7
av
Two sets of buttons with standardized operator buttons are defined for process control
from the OS. When you start process mode, button set 1 is displayed. You switch
S
N
between the button sets using operator buttons.

PC
Plant-specific button sets

IC
Starting with PCS 7 V8.2 you can design button sets of the PCS 7 OS on a plant-
AT
specific basis.
IM
 See [231] PCS 7 V9.0 OS Process Control – 05_2017, 3.8 for a description of the
-S
operator control functions in the button area.

See [104] PCS 7 V9.0 Operator Station – Configuration Manual – 05_2017, 6.3.8 for
global adaptation of the button sets in a PCS 7 OS.
z
Fo
ig
rF
a to

ig

av
2
12
16
9.7.2 Settings for OS Runtime design
Settings for the WinCC Runtime design –
12
Global design settings for the project
Global design settings for the project
1
og
Define your
project color
Pr
palette
e
g
Select a WinCC
En
Design
7
S
22
PC
12
IC
16
AT
IM
12
-S
Select the following design for the9 appearance of the user interfaceSITRAIN
in process mode:
1
z
ST-PCS7SYS - 37 © Siemens AG 2017

Fo
WinCC 3D. og
The following WinCC designs are not supported by PCS 7:
Pr
ig
 WinCC Classic
rF
 Glass
e
o
 Simple
g
at
En
 WinCC Dark
ig
Ensure a uniform setting for the design for all projects of a plant. If you change the
7
av
setting of the design, check the display of custom objects and adapt them if necessary.
S
N
Keep the setting in the case of a software update. If the setting for the appearance of
PC
the user interface in process mode is changed when a software update is performed,
this can cause more extensive changes.
IC
 Starting with PCS 7 V9.0, the central color palette and the global design settings can
AT
alternatively be called directly in the Graphics Designer under "Menu > Options".
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
Design restrictions in the computer properties
Design restrictions in the computer properties
12
1
og
Pr
e
g
En
7
S
You define settings for process mode on the "Runtime" tab:
22
PC
 If you are using VB scripts: settings for a VBS debugger in process mode
 Definition of a cache memory for process pictures
12
IC
 Appearance of the mouse pointer for certain actions by the plant operator
16
AT
You can specify all settings that are to apply to the display in process mode on the
"Graphics Runtime" tab. You generally do not have to make any settings on this tab.
IM
12
ST-PCS7SYS As long as you are in test mode, you
9 - 38can, for example, activate the "maximize"
SITRAIN and
© Siemens AG 2017
-S
"minimize" window attributes. The enables you to quickly change from the Runtime
display to other applications while in test mode.
1
z
Note
Fo
og
Always deactivate these settings when the project is used in real operation.
You can make additional settings for the display in the "OS project editor".
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
Settings in the object properties
Design settings in the object properties
12
1
Object properties of
the selected button
og
Pr
e
g
En
7
S
Customized
22
PC color setting
12
IC
16
AT
As long as different settings are not made in the individual object properties, the global
design settings act on all graphic objects in the project.
IM
12
-S
 As long as an attribute is determined by the global design, it is static and can no

longer be dynamized. Only a previously made dynamization is preserved and not
1
z
affected by the global design.

Fo

og
See [104] PCS 7 V9.0 Operator Station - Configuration Manual - 05_2017, 7.3.1 for
an overview of the global and specific settings of a PCS 7 OS.
Pr
ig
rF
Activating OS Runtime
e
9.8 Activating OS Runtime

o
g
at
En
ig
7
av
Activation of
OS Runtime
S
N
PC
When you want to activate Runtime for

an OS project on the ES, you can enable
IC
this option centrally for the project. Necessary for

combined ES/OS
AT
IM
Multi-user systems: Before you can take a project into process mode, you transfer the configured
-S
(OS server / data to the various OS servers and OS clients:

OS clients)
• Download the complete OS (initial download, OS Runtime Stop)
z
•
Fo
Download the OS changes (no OS Runtime Stop)

• OS clients are automatically updated using the server data.
ig
Activate the operator stations directly on the respective computer. Do not

activate the operator stations on the ES.
rF
to

a

ig

av
2
12
16
9.9 Block icons and faceplates
12
9.9.1 Difference between block icons and faceplates
Block icons represent AS functions in the OS.
1
Generally the main information (operating states, process values) of a function/
og
process tag (motor, valve, etc.) is displayed in a block icon. For this reason, PCS 7
provides corresponding block icons for technological blocks (blocks for which operator
Pr
control and monitoring is possible).
The block icons are automatically installed in the process pictures according to the plant
e
hierarchy and interconnected with the relevant process tags.
g
After a single mouse click on the block icon, a faceplate appears …
En
 … to show more details
 … –toOS
Block icons Runtime
7
enable operator inputs (input of setpoints, limit values, etc.)
Example for PCS 7 standard library
S
 Example of the earlier PCS 7 standard library:
22
PC
12
IC
Faceplate,
shows
16
AT
standard view View

selection Block icon
Loop shows all
IM
views in one
12
window
-S
1
z
Fo
og
Pr
ig
rF
Block icons – OS Runtime

o
Example for APL (Advanced Process Library)

at
En
 Example of the APL (Advanced Process Library):

ig

7
av
S
N
PC
Block icon
Faceplate,
IC
shows
standard view
AT
View
selection
IM
-S
z
Fo
ig
rF
to

a

ig

av
2
12
16
9.9.2 General information on faceplates of the APL
12
FaceplateCompared with the PCS 7 standard library, the design of the faceplates of the APL has
changed significantly. This change is due to the increased functionality of the APL.
1
Display and
og
operator control
elements
Pr
e
Commands and
Status operating modes
g
displays
En
Interlocks
7
Jump to
S
other
22
faceplates PC
12
IC
Associated
Operating values (max. 2)
16
AT
area
IM
12
-S
Faceplate – Display and operator control elements

Display and operator control elements
1
z

Fo
og
Right-click to open view
in a new window
Pr
ig
rF
e
o
The faceplate has the following displays and operator control elements:
at
En
1. Group display Symbol Meaning

ig
2. Alarm interlock via faceplate

Standard view
7
av
3. Alarm suppression via function block (FB)

S
4. Alarm acknowledgement Alarm view

N
PC
5. Worst signal status Limit view

6. Batch display
7. Not used Trend view
IC
8. Maintenance demanded and release Ramp view

AT
9. Memo display
Parameter view
10. Open block views
IM
11. Back to block icon Preview

12. Pin block
Memo view
-S
13. Name of block instance

14. Help button Batch view
z
Fo

 Left-click: Replacement of the current view with the desired view.
 Right-click: Additional opening of the desired view.
ig
rF
a to

ig

av
2
12
16
Status displays
12
In this area, the status (motor, valve symbol, etc.) is displayed in symbolic form at the
top. Below this, there is additional information and there are jump functions (buttons to
call a faceplate of a different block).
1
The additional information is intended to help the operator and provides information
og
about the status of the process instrumentation, for example whether a motor is being
simulated or is undergoing maintenance.
Pr
e
Buttons for additional faceplates
g
By clicking on user-configurable buttons in the faceplate, the user can open additional
En
faceplates of his choice.
7
Commands and operating modes
S
Operating mode and command are shown in this area and can be changed under
22
PC
certain conditions (e.g. with adequate operator authorization).
12
Depending on the block, the "Manual", "Automatic", "Program mode", "Local" or "Out of
IC
service" modes can be selected. The commands "Start", "Stop", "Open", "Close" etc.
can be selected.
16
AT
Operating modes and commands can be selected in a separate operating area below
IM
the faceplate. This action can be with or without acknowledgement. This depends on the
12
setting.
-S
Interlocks
1
z
Fo
Here, the various interlock types are displayed. og

Pr
ig
Associated values
rF
In the standard view of some technological faceplates, up to two additional auxiliary

o
analog values can be displayed. For example, these can be used to display the motor
g
at
En
current and winding temperature for a motor.

ig
7
av
Scaling of faceplates
S
N
You can scale the faceplates from 50% to 200%. The value to be scaled is specified
PC
with internal tag "@APLFaceplateScaleFactor", type: 32-bit value without sign. The
default scaling value is 100.
IC
You can scale the faceplates from 101% to 200% by defining a value in the range from
101 to 200 for the internal tag. You can also scale the faceplates from 50% to 99% by
AT
defining a value in the range from 50 to 99 for the internal tag.

The reference for the calculation is the preset faceplate size of 100%.
IM
-S
 See [113] PCS 7 V9.0 Advanced Process Library – 03_2017, 2.3 for further details on
the faceplates.
z
 See [120] PCS 7 V9.0 APL Operator Guide – 05_2017, for a description of the main
Fo
functions of the APL block icons and faceplates.

This description is also available by pressing the Help button of an APL faceplate in
ig
OS Runtime – appropriate for the open faceplate.

rF
a to

ig

av
2
12
16
9.9.3 Display of block icons
12
Compared with the PCS 7 standard library, the design of the block icons of the APL has
changed significantly.
Display ofAnblock icons
1
extensive selection of block icons is located in the @PCS7TypicalsAPLV8.pdl
picture:
og
Analog display block Valve block VlvL
Pr
MonAnL
e
in @PCS7TypicalsAPLV8.pdl
g
En
7
in OS Runtime Normal operation, Normal operation,
S
valve open
22
PC
Normal operation,
Malfunction, with
12
limit violation, high
IC
additional status
alarm
information
16
AT
IM
12
9.9.4 Operator input in faceplates and block icons
-S
Faceplates – Commands / Operating mode selection

Faceplates - Commands / Operating mode selection
1
z
Fo
og
Operating mode selection with @APLCommandExecutionSteps = 3
Pr
ig
rF
e
o
g
at
Operating mode selection with @APLCommandExecutionSteps = 2

En
ig
7
av
S
N
PC
• Value = 3: Operating steps with

Start command with @APLCommandExecutionSteps = 3
acknowledgment (default setting)
• Value = 2: Operating steps
IC
without acknowledgment
AT
IM
Start command with @APLCommandExecutionSteps = 2

-S
z
Fo
ST-PCS7SYS The setting for one of the two variants

9 - 46 (with or without confirmation) is made
SITRAIN project-
© Siemens AG 2017
wide via the properties of the internal WinCC tag @APLCommandExecutionSteps,
ig
which is available in "Split Screen Manager" under "Internal tags" of the Tag
Management of the OS.
rF
a to

ig

av
2
12
16
Value display
Value display
12
Operation
possible
Value bad
1
Value
og
passivated
Pr
External
simulation
e
Message can be disabled/
g
enabled by the operator
En
Message locked Internal
simulation
7
Message temporarily disabled
S
The operation is enabled
22
PC
The operation is not enabled based on the configuration (OS_Perm)
Operation not
12
The operation is not enabled based on the process status possible (no
IC
authorization)
16
AT
Values, limit values, etc. can be changed in faceplates. An APL-specific function is the
IM
12
graphic display of enabled operations and operator authorization. The operator can
distinguish between values that can and cannot be changed. The following can be
-S
distinguished:
 whether operator input is generally disabled for the faceplate
1
z
Fo
 whether operator input is disabled for process-specific reasons

og
 whether an operator has the necessary operator authorization
Pr
ig
The value is also input in a separate operating area below the faceplate. You can open
rF
this operating area by clicking on a modifiable value (value with white background). The
e
value can be changed in the operating area in three ways:

o
g
at
 The value can be changed in discrete increments (e.g. -2.5) via direct operator input
En
with the buttons.

ig
 A desired value can be set with the slider.

7
av
 A value can be directly entered in the entry field. The modified value becomes
N
PC
effective in the faceplate with "OK".

IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.9.5
Operator authorization levels
Operator authorization levels
12
1
Assigned to operator function
"Higher process controlling"
og
Pr
e
Level 2
g
En
7
Level 1
22
PC
12
Level 3
IC
Assigned to "Process Assigned to operator function

controlling" operator function "Highest process controlling"
16
AT
IM
The following operator authorization levels from User Administrator are used in the APL:
12
 Operator authorization level = 09 - 48
-S
No process controlling, only monitoring.
1
z
 Operator authorization level = 1 (level 5 in the User Administrator)

Fo
og
Process controlling (e.g. switching between "Manual"/"Automatic", changing
setpoints and tags).
Pr
ig

rF
Higher process controlling (e.g. changing limit values, control parameters and
o
monitoring times).
at
En

ig
Highest process controlling (simulation of process values). The operator

7
av
authorization enables the following inputs:

S
 Turning the simulation on and off in the parameter view, simulation of values
N
PC
already requires operator authorization level 1

 Turning the release for maintenance on and off in the parameter view
IC

AT
Advanced operation 1 (user-defined project-specific operator authorization)

IM
Advanced operation 2 (user-defined project-specific operator authorization)

-S
Instance-specific authorizations can be assigned depending on the user management

and the access authorization. For example, controllable faceplates have the input
z
parameter OS_Perm, which enables you to implement customized control strategies for
Fo
operators by specifying enabled operations for them.

ig
 See [113] PCS 7 V9.0 Advanced Process Library – 03_2017, 2.3.2 Operator control
rF
permissions
a to

ig

av
2
12
16
Associated values in the faceplate and direct jump to another faceplate
12
From a faceplate it is possible to open other faceplates. Buttons are available for this
purpose (in the standard view and preview). The relationship between the button and
faceplate is established using input parameters SelFp1 (button in the standard view)
and SelFp2 (button in the preview). The buttons are visible and activated as soon as
1
these input parameters are interconnected with any output parameter of the faceplate to
og
be opened. The labeling is done for input parameter SelFp1 or SelFp2 in the CFC
chart.
Pr
In the standard view of some faceplates, you can have up to two auxiliary values
e
displayed, e.g. motor speed. The value that is to be displayed on the OS must be
interconnected with input UserAna1 or UserAna2 in the CFC. The signal status of the
g
associated values is used to control the visibility of the display fields.
En
Block icons
Youand faceplates
specify the labelingofin the APLin–the object properties (I/Os > Identifier) of
the CFC
the faceplate.
Associated values and direct jump to other faceplates
7
The units of the associated values have their own input parameters.
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og
Associated
Pr
ig
value with unit

rF
Button for
Configuration of direct jump button
e
direct jump Label for

and associated associated
values invalue
the faceplate
o
g
at
En
ig
Properties of input
UserAna1
7
av
S
N
PC

IC
AT
IM
-S
Specification of source, label

and unit of the associated value
z
Fo
ig
Specification of
rF
jump destination
a to

ig
Course ST-PCS7SYS
folder, V9.0.0, ST-PCS7SYS 9 - 50 SITRAIN © Siemens AG 9
2017
- 35
av
2
12
Direct control via the block icon
16
Direct control via the block icon
12
1
Open faceplate (left-
og
click anywhere on
the block icon)
Direct setpoint setting
Pr
via the block icon
(right-click on
e
corresponding value)
g
En
7
S
22
PC
12
IC
16
AT
 See [120] PCS 7 V8.2 APL Operator Guide – 08_2016, for more details on operator
control of APL faceplates and block icons.
IM
12
-S
9.9.6 Creating/updating block icons
1
z
Block icons are installed in the process pictures with the help of the "Create/update
Fo
block icons" function.

og
You can call this function:
Pr
ig
 as a sub-step when compiling the OS

rF
Creating/updating block icons –

e
 as a standalone function from the plant hierarchy

Sub-steps of this function
o
A brief description of the sequence of this function:

at
En
ig
7
av
Identifying the OS-relevant blocks in the charts

S
N
PC
Identifying the right Typicals file as the "library" for the

IC
block icons
AT
IM
Identifying the relevant block icons

-S
z
Fo
Copying these block icons to the process picture

ig
rF
Assignment of specific information for the block icon

a to

ig
9 - 36 ST-PCS7SYS 9 - 52 Course folder, V9.0.0,

SITRAIN ST-PCS7SYS
© Siemens AG 2017
av
2
12
16
@PCS7Typicals: "Library of block icons"
12
Creating/updating block
The "Create/update icons"–function creates copies of block icons whose originals
icons
block
are contained in the following template picture:
"Typicals" file
@PCS7TypicalsAPLV8.PDL
1
og
Pr
e
g
En
7
S
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
ST-PCS7SYS  APL versions before PCS 7 V8.0 contain another version of the SITRAIN
9 - 53
og APL "Typicals" file:
© Siemens AG 2017
@PCS7TypicalsAPL.pdl
Pr
ig
 To ensure compatibility with earlier APL versions, PCS 7 V8.0 also contains the old
rF
template file under a new name:

e
@PCS7TypicalsAPLV7.pdl
o
g
at
En
Any further block library also provides its own template pictures with the needed block
ig
icons. The name of these pictures always begins with "@PCS7Typicals" and ends with
an abbreviation that identifies the library. The block icons of the PCS 7 standard library
7
av
are located in template picture "@@PCS7Typicals.pdl".

S
N
The "Create/Update Block Icons" function uses these templates to insert the block
PC
icons in the process pictures. All pictures whose names start with "@PCS7Typicals" are
determined. These are sorted alphanumerically in descending order, and the first 20
template pictures are then used to find the right block icons. One possible order could
IC
be:
AT
 @PCS7TypicalsRC.pdl
 @PCS7TypicalsBATCH.pdl
IM
 @PCS7TypicalsAPLV8.pdl
-S
 @PCS7TypicalsAPLV7.pdl
z
 @PCS7TypicalsAPC.pdl
Fo
ig
rF
a to

ig

av
2
12
16
Variants of block icons
block icons –
12
Creating/updating
There can be multiple variations of block icons for a block type. For example, this
Selection of symbol
supports variant installation in a graphic flow diagram on the OS. You can
the vertical/horizontal
assign the desired variant of the block icon in the CFC for the block instance using the
block properties ("General" tab).
1
og
Block properties in the CFC "Library" of block icons in WinCC:
Pr
e
g
The OS compiler (more precisely: the
En
"Create/update block icons" function) finds the
right block icons based on their number:
7
S
22
PC
12
IC
16
AT
IM
12
-S

@TemplateAPLV8.pdl
1
z
When block icons are created/updated automatically, all block icons in a process picture
Fo
og
that exist in template picture @PCS7TypicalsAPLV8.pdl but are not derived via the
plant hierarchy are deleted.
Pr
ig
For this reason, the same set of ready-made block icons is provided in an
rF
@TemplateAPLV8.pdl file. In this case, the "Type" property is assigned differently in

e
these block icons. From here you can copy the block icons yourself into any picture and
o
@PCSTypicals
connect themand @PCS7Templates
to a structure tag (AS block instance) using the "Connect faceplate to
at
En
process tag" dynamic wizard.

ig
7
av
S
N
PC
IC
AT
IM
-S
Note the @ character

z
in the Type property.

Fo
ig
rF
to

a

ig

av
2
12
16
Consistent plant hierarchy
12
The described mechanism requires that charts that contain blocks for which operator
control and monitoring is possible be located in the same hierarchy path of the plant
hierarchy as the corresponding process pictures.
1
If the AS and PC stations are located in the same user project, this requirement is met
og
automatically.
But this is not the case when the components are distributed among various user
Pr
projects (e.g. separate AS and OS projects). Here it must be ensured that the paths in
the plant hierarchies are identical.
e
The best way to synchronize the plant hierarchy across all projects of a multiproject is to
g
use the following menu command:
En
Options > Plant Hierarchy > Update in the Multiproject…
7
The option to export the PH of a project to other projects is favored here. The individual
sub-hierarchies of the AS projects are mapped in the OS project and the complete
S
structure is mirrored there.
22
PC
12
IC
16
AT
IM
12
-S
1
z
Fo
og
Pr
ig
rF
e
o
g
at
En
ig
7
av
S
N
PC
IC
AT
IM
-S
z
Fo
ig
rF
a to

ig

av
2
12
16
9.10 Exercises and checkpoints
12
Exercise: Quickly creating the OS
1
og
Task
Pr
Create a ready-to-run OS based on the AS functions configured up to this point.
e
g
En
Exercise: M120 and M130
7
Task
22
Configure the AS and OS functions for M120 and M130 based on a copy of M110.
PC
12
IC
Exercise: Objects for level indication in tanks
16
AT
Task
IM
12
Configure correctly interconnected level bargraph displays in the process pictures.
-S
Checkpoint
Checkpoint
1
z
Fo
Which properties …
og
Pr
 of an operator system should be
ig
rF
configured only at a later time?

e
o
g
at
En
ig
Did we …
7
av
 forget something for the fill level

S
N
PC
of M130?
In what cases …
IC
 is a graphic bargraph display

AT
appropriate?
IM
-S
z

Fo
ig
rF
a to

ig

av

09 - Basic Functions For Operator Control & Monitoring - V9 - 12 16 12 22

Uploaded by

Copyright:

Available Formats

You might also like

09 - Basic Functions For Operator Control & Monitoring - V9 - 12 16 12 22

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

09 - Basic Functions For Operator Control & Monitoring - V9 - 12 16 12 22

Uploaded by

Copyright:

Available Formats

2

9.3 Settings in the plant hierarchy ............................................................................................... 9

9.4 OS-AS connection ............................................................................................................... 13

9.5 Project type .......................................................................................................................... 18

9.6.1 Overview .............................................................................................................................. 19

9.6.3 Deriving / updating block icons ............................................................................................ 23

9.7.2 Settings for OS Runtime design .......................................................................................... 26

9.8 Activating OS Runtime......................................................................................................... 28

9.9 Block icons and faceplates .................................................................................................. 29

9.9.1 Difference between block icons and faceplates .................................................................. 29

9.9.3 Display of block icons .......................................................................................................... 32

9.9.4 Operator input in faceplates and block icons....................................................................... 32

9.9.6 Creating/updating block icons.............................................................................................. 36

9.10 Exercises and checkpoints .................................................................................................. 40

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

Course folder, V9.0.0, ST-PCS7SYS 9-1

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

9-2 Course folder, V9.0.0, ST-PCS7SYS

ST-PCS7SYS 9 - 2on SIMATIC WinCC.

ST-PCS7SYS 9-3 SITRAIN © Siemens AG 2017

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

Course folder, V9.0.0, ST-PCS7SYS 9-3

ST-PCS7SYS tags and messages. 9-4

Client(s) provide the user interface.

In a multi-user system, one or more OS servers supply up to 40 operator stations (OS

be implemented as a separate bus (Ethernet with TCP/IP).

check. If an error is detected, a redundancy failover is made if necessary.

Synchronization of the redundant OS servers takes place automatically and at high

The OS Runtime is executed on the OS servers and OS clients.

of testing an OS configuration on the ES in Runtime without disturbing the active OS

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

9-4 Course folder, V9.0.0, ST-PCS7SYS

General – PCS 7 single station redundancy).

Special case: Combined ES/OS

System Bus (ISO)

"Compile OS" function.

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

Course folder, V9.0.0, ST-PCS7SYS 9-5

small to medium-sized project sizes with up to 8 OS single station systems and

Display of operator and process control messages

 A system-wide overview of the operator and process control messages is provided

with the help of the Process Historian / Information Server.

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

9-6 Course folder, V9.0.0, ST-PCS7SYS

Max. 100 per

 Maximum number of configurable messages

Max. 8500 PO MS Server OS Server

Max. 216000 PO per project Max. 200000

Max. 2600 PO per system messages

ST-PCS7SYS 9-9 SITRAIN © Siemens AG 2017

SIMATIC PCS 7 – Basic Functions for Operator Control & Monitoring

Course folder, V9.0.0, ST-PCS7SYS 9-7

project are located here

SIMATIC Manager: WinCC Explorer then starts.

SIMATIC Manager WinCC Explorer

with the objects

edited by the editor

Each editor opens its