Professional Documents
Culture Documents
Content
9
9.2
9.2.1
9.2.2
9.2.3
General ...................................................................................................................................3
Overview .................................................................................................................................3
Single station and multiple station systems............................................................................4
WinCC Explorer / Location of the OS Project.........................................................................6
9.3
9.4
9.5
9.6
9.6.1
9.6.2
9.6.3
Compilation ...........................................................................................................................16
Overview ...............................................................................................................................16
Settings .................................................................................................................................16
Create/ update block icons ...................................................................................................19
9.7
9.7.1
9.7.2
Layout ...................................................................................................................................21
Skin & Design .......................................................................................................................21
Settings for WinCC RT Design .............................................................................................22
9.8
9.8.1
9.8.2
9.8.3
9.8.4
9.8.5
9.8.6
9.9
9-1
9-2
9.1
Learning targets
The participant will learn about
the general function of the OS
the role of OS-AS connections and
of the Plant hierarchy
the mechanism of the create/
update block icons function
9.2
General
9.2.1
Overview
The OS of SIMATIC PCS 7 is based on SIMATIC WinCC.
Process visualization
Motor
ON
Valve closed
Gate closed
Alarm Logging
(message system)
Tag Logging
(archiving)
number ()
float cou
begin
if value > 0
start
cou = cou + 1
end
end
Programming
interface
Standard
interfaces
Logging
ReportSystem
(reporting)
Process
communication
Together with a number of WinCC options and additional tools in SIMATIC Manager it is
used as one of the main components of a PCS 7 configuration: the Operator System.
SIMATIC PCS 7 Basics Operating and Monitoring
Training Documentation, V1.00, ST-PCS7SYS
9-3
9.2.2
OS
Client 1
OS Servers
OS
Client 32
Server 1
Server 12
Terminal bus
(TCP/IP)
ASx
AS1
Servers contain communication to the AS, pictures, logging of tags and messages.
Clients offer the user interface.
With a multi-user system, one or more (up to 12) OS Servers supply up to 32 operator
stations (OS clients) with data (project data, process values, archives, and messages)
via a terminal bus. The terminal bus can share the transmission medium with the plant
bus or it can be designed as a separate bus (Ethernet with TCP/IP).
In this architecture, redundant OS servers may be set up to meet higher availability
requirements. Critical applications are monitored by health check for software faults. If a
fault is detected, switchover to the redundant system is triggered. Synchronization of the
redundant OS servers takes place automatically and at high speed.
The broad colored arrows in the figure above symbolize the exchange of information
between the AS and OS resp. between servers and clients.
The OS Runtime is executed on the OS servers.
Central Engineering
Whatever is the configuration of system components, it is always the Engineering
Station to be the source of everything. All configuration data are loaded from the ES to
the target system. The figure above indicates this by thin black arrows.
OS Simulation
The OS runtime of servers must not be started on an ES station! To provide the
opportunity to test OS configurations on the ES in runtime without disturbing the running
OS server, the OS can be simulated on the ES.
9-4
OS
Terminal bus
(TCP/IP)
AS1
AS99
In single station system architecture, all operator control and monitoring functions for a
complete project (plant/unit) are concentrated in one station. This OS single station can
be operated on the plant bus together with other single-user systems or in parallel with a
multiple station system. Redundant operation of two OS single stations is also possible
(SIMATIC PCS 7 Single Station Redundancy).
Terminal bus
(TCP/IP)
AS1
AS99
The PC station configuration of the ES contains the WinCC application for the OS
project. This is the only case, where the OS Runtime is executed on the ES.
9-5
9.2.3
For editing the contents of an OS, the OS project is opened from the Component View
of the SIMATIC Manager: WinCC Explorer will be launched.
SIMATIC Manager
WinCC Explorer
Content window,
showing objects
related to some
of the editors
List of editors:
Every editor will use its
own application window
(also appearing on the
Windows task bar)
SITRAIN
9-6
9.3
When assigning names, please note that when you compile the OS, the tag name
must not be longer than 128 characters. The name consists of the folder names in the
hierarchy path, the chart name, the block name, the delimiter, and the I/O name.
With delimiter
A delimiter is appended in the HID to the name of the hierarchy folder. Delimiters are
used in the textual representation of the hierarchy path for clearer distinction between
the names of the hierarchy folders. The hierarchy path is the sequence of names of the
hierarchy folders through the hierarchy levels to the current object. The "\" character is
used as the delimiter. Note: There is always a delimiter after the last hierarchy folder
that is included in the designation, which means this option cannot be modified.
OS area
This defines which hierarchy level is to be valid as the OS area level. Only the top three
hierarchy levels are available as OS area levels. The default is level 1.
SIMATIC PCS 7 Basics Operating and Monitoring
Training Documentation, V1.00, ST-PCS7SYS
9-7
The way, how pictures are arranged, can be displayed in the Picture Tree Manager.
The tool is part of the WinCC Explorer.
In OS Runtime, the overview buttons and the content of the Picture Tree Navigator
represent the way pictures are arranged:
9-8
R310
LIA214
MonAnalog
PV.Value
PH Level
Chart name
Block name
I/O name
9-9
Structure tags:
9 - 10
R310
LIA214
MonAnalog
PH Level
Chart name
Block name
See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.4.3 for
more details
9.4
OS-AS Connection
What are the arrows in the figures below standing for?
Multiple Station OS
ES
OS Clients
Terminal bus
(TCP/IP)
OS Servers
ASx
AS1
Single Station OS
OS
ES
Terminal bus
(TCP/IP)
AS1
AS99
Terminal bus
(TCP/IP)
AS1
AS99
9 - 11
It is done by NetPro:
The connection is configured between
the WinCC Application on the PC (starting point of Insert New Connection dialog) and
the CPU as its connection partner on the AS.
3
1
Named
connection
4
9 - 12
3. Select the connection partner. If you started with a WinCC Application, then the
CPU of the desired AS should be the partner.
4. Named connection: Assign a symbolic name to the connection between OS and
AS instead of the default connection ID as substitute for the connection parameters.
Use a meaningful name.
Named connection
This method of procedure is also designated as a "Named Connection". It is also
important for redundant OS server and OS simulation mode.
We recommend to use the name of the connected AS. Once the OS has been
compiled, this name will appear in the "SIMATIC S7 Protocol Suite" of WinCC tag
administration.
Color indicates a
configuration still
not being compiled
1. Use the button Save and Compilein the tool bar of NetPro to start the compilation
of the network configuration.
2. We recommend always including the configuration check.
3. After the configuration was compiled you have to download the new OS-ASconnection.
9 - 13
No stop required
By download the connections only the AS will not be stopped.
9 - 14
9.5
Project type
From origin, a WinCC Application as it is inserted into a PC station configuration is set
as a Multi-User Project.
Single User
If the system is to be used as a Single User Project, have it adapted in Project
Properties:
9 - 15
9.6
Compilation
9.6.1
Overview
A lot of settings to the OS data structure are done in SIMATIC Manager and the tools for
configuring the charts. It is stored in the Project database.
This OS relevant data is transferred into the OS database by a compilation process:
9.6.2
See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.5.1 for
more details.
Settings
Settings for the compilation process are offered to you in dialog windows of a wizard:
9 - 16
See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.5.3 for
more details.
3
4
9 - 17
3
2
9 - 18
9.6.3
Separate task
It can also be done as a separate task from the Plant View window of the project:
Precondition
Picture M110
As comparison
9 - 19
Included levels
Picture R310
The charts are in
the 4th level
PH level: 1 2 3 4
The picture is in
the 3rd level
PH level: 1 2 3 4
In the Lower hierarchy levels included combo box, set the number of AS hierarchy
levels to be taken into consideration when creating/updating block icons.
The need for this setting is based on the different description depth between the AS and
OS.
On the AS side the charts are configured at process tag level. The charts are therefore
inserted at the lowest level and only contain the control modules with the drivers for
process connection. In our example the charts are at level 4.
On the OS side, the aim is different. The pictures do indeed describe the plant for the
lower levels in increasing detail, but not as far as process tag level. In our project the
lowest level for the pictures is level 3.
As there are no pictures at chart level, no block icons would be inserted by the
Create/Update Block Icons wizard either. This problem can be solved by setting
Lower hierarchy levels included to 1. The block icons are then simply inserted in the
pictures that are one level up.
The default setting is 1.
9 - 20
9.7
Layout
9.7.1
Overview area
Work area /
process picture
Key set
The name of the start picture (the first picture being opened after start of OSRuntime) is @screen.pdl
9 - 21
9.7.2
Select a WinCC
skin design
Ensure that all projects in a plant have uniform settings for the design. If you change the
setting of the design, check the visualization of self generated objects and adapt these if
necessary. You can define the appearance of the user interface in process mode by
selecting one of the two designs: WinCC 3D; WinCC Classic
The WinCC designs "Glass" and "Simple" are not supported by PCS 7.
Some restrictions to the global design effects can be activated on the "Runtime" tab in
the "Computer Properties" dialog. You can improve the computer's reaction time by
switching off certain elements of the global design.
The settings made on this tab apply for all WinCC projects run on this computer.
9 - 22
Object properties of
the selected button
Individual color
setting
If nothing else is set in the object properties, the settings of the selected global design
apply to all graphic objects in the project.
9 - 23
9.8
9.8.1
Faceplate,
showing a
standard view
View
selection
Block Icon
Loop display,
showing all views
in one window
Block Icon
Faceplate,
showing a
standard view
9 - 24
View
selection
9.8.2
Display and
operation
Commands and
operating modes
Status
displays
Interlocks
Button for
additional
faceplate
Auxiliary
values (max. 2)
Operating
area
Group display
Lock alarms via faceplate
Suppress alarms via FB
Acknowledge alarms
Worst signal status
Batch display
Not used
Maintenance request and release
Memo display
Open views of the block
Return to block icon
Pin block
Instance name of the block
Icon
Meaning
Standard view
Alarm view
Limits view
Trend view
Ramp view
Parameter view
Preview
Memo view
Batch view
9 - 25
Status displays
This area shows at the top the status (motor, valve icon,...) in the form of an icon or
symbol. Additional information and step functions are shown below it (buttons for
opening a faceplate of another block).
The additional information serves as support for the operator and it informs about the
status of the process instrumentation, e.g. whether a motor is simulated or maintenance
is carried out on it.
Interlocks
The different interlock functions are displayed in this section
Auxiliary values
Up to two additional analog auxiliary values can be displayed in the standard view of
some technological faceplates. They can be used e.g. with motors for displaying the
motor current and the coil temperature.
9 - 26
See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.3 for more details
about the faceplates
9.8.3
Valve block
VlvL
in @PCS7TypicalsAPLV8.pdl
in OS Runtime
Normal Operation,
Normal Operation,
High alarm violated
9.8.4
Normal Operation,
valve opened
Disturbed, with additional
status information
The setting for one of both variants (without / with acknowledgement) can be made
throughout the project via the internal WinCC variable @APLCommandExecutionSteps
being available in the category Split Screen Manager of the internal variables in the
Tag Management of the OS.
SIMATIC PCS 7 Basics Operating and Monitoring
Training Documentation, V1.00, ST-PCS7SYS
9 - 27
Value Representation
Operation via
FB enabled
Message
locked
Sufficient
authorization level
Insufficient
authorization level
Operation via
FB disabled
(OS_Perm)
Value disabled
(e.g. PV_AH_En)
Internally
simulated
Operation due
to process
not possible
Externally
simulated
Value
faulty
Values, limits, etc can be changed from faceplates. A feature available only in APL is
that the operator enables and operator authorization can be graphically displayed. The
operator can distinguish which values can be changed and which can not be changed. It
can be distinguished whether:
The operation at the block is generally blocked.
The operation is blocked process-related.
An operator does or does not have the appropriate authorization.
The value input also happens via a separate operating area below the faceplate. You
open this operating area by a mouse click on an adjustable value (white background
color). The value can be changed in the operating are in three ways:
Via the direct operation, a value can be changed discretely using buttons (e.g. -2.5).
Using the slider control, the value can be set to the desired value.
Via the input field a value can be entered directly.
Via acknowledgement with OK the changed value is sent to the block.
9 - 28
9.8.5
Level 2
Level 3
The following operator authorization levels from user management are used in the APL:
Authorization level = 0
No process controlling, only monitoring.
Authorization level = 1 (Level 5 in the "User administrator")
Process controlling (e.g.manual / automatic switchover, changing setpoint and
manipulated variables)
Authorization level = 2 (Level 6 in the "User administrator")
Higher process controlling (e.g. changing limit values, control parameters and
monitoring times).
Authorization level = 3 (Level 1100 in the "User administrator")
Highest process controlling (e.g.switching simulating on and off). This operator
authorization enables the following operation:
Switching the simulation on and off in the parameter view
Simulating the values is authorization level 1
Switching the release for maintenance on and off in the parameter view
Authorization level = 4 (Level 1101 in the "User administrator")
Advanced operation 1 (free project-specific operator authorization)
Authorization level = 5 (Level 1102 in the "User administrator")
Advanced operation 2 (free project-specific operator authorization)
Depending on the user management and the access authorizations instance-specific
authorizations can be assigned. E.g. all controllable blocks have the OS_Perm input
parameter, which allows you to implement individual operator control strategies by
setting the operator control permissions.
See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, chapter 1.3.2 Operator
permissions
9 - 29
Associated
value with unit
User button for
direct jump
Label of the
associated value
Properties of input
UserAna1
9 - 30
9.8.6
See [1003] Application description 50249288 APL Operator Guide - 01_2012, 5.5.3
for more details about operation of APL faceplates and block icons.
9 - 31
APL Versions before PCS 7 V8.0 delivered another Version of the APL typicals file:
@PCS7TypicalsAPL.pdl
To remain the compatibility to former APL versions this older typical file is also
delivered in PCS 7 Version 8.0 under another name:
@PCS7TypicalsAPLV7.pdl
Each additional library also provides a template picture of this type with the required
block icons. The name of this template picture starts with "@PCS7Typicals" and also
contains a short library designation at the end. The template picture of the standard
library is called "@@PCS7Typicals.pdl".
The Create/Update Block Icons function uses these template pictures to insert the
block icons. All pictures whose names start with "@PCS7Typicals" are identified. These
are sorted alphanumerically in descending order and the top 11 template pictures are
used. A possible processing sequence might therefore be:
@PCS7TypicalsRC.pdl
@PCS7TypicalsBATCH.pdl
@PCS7TypicalsAPLV8.pdl
@PCS7TypicalsAPLV7.pdl
@PCS7TypicalsAPC.pdl
9 - 32
Icon library:
The OS compiler
(more exactly: the wizard Create / update Block
Icons) finds the related block icon by this number:
@TemplateAPL.pdl
In the case of automatic creation, all block icons in the picture which also appear in
@PCS7TypicalsAPLV8.pdl but were not generated via the plant hierarchy are
deleted. For manual configuration and when post-processing pictures, therefore, use
picture @TemplateAPLV8.pdl as the template for block icons, as the type property is
pre-assigned differently in this case.
9 - 33
9 - 34
9.9
Checkpoint
What items
of the OS system do you think
should be customized in a later
stage to fit the best to this plant?
Checkpoint
Did we
forget anything for the level of
M130?
Checkpoint
For what
purpose is a bar graphic useful?
9 - 35