Professional Documents
Culture Documents
Contents
8 AS – OS Communication .......................................................................... 29
8.1 Telegram Length.................................................................................................................. 29
8.2 Acknowledgement Triggered reporting of messages ..................................................... 29
8.3 Change-Based reporting of process data......................................................................... 29
8.4 Variables Connections........................................................................................................ 30
9 Archive System ................................................................................................ 31
9.1 Tag Logging ......................................................................................................................... 31
9.2 Alarm Logging ..................................................................................................................... 34
10 Component Configurator ................................................................................ 37
11 User Administrator........................................................................................... 39
12 Visual Basic...................................................................................................... 40
13 Horn 43
1 What's New
OS Project Editor
- Central project design tool for the runtime OS system settings in PCS 7
Optimized AS – OS interface
- Allows client pictures to access data from multiple servers within the same picture.
- Supports data exchange between OS servers and the Archive server
- The extended status display makes it easier to graphically represent a process object with multiple
dynamic states. Without scripting, four states and the alarm status can be represented.
- The new high-performance archive system uses the MS SQL server database and allows the
process value archiving function to be separated from the OS server function.
2 PCS 7 OS
In version 6 the robustness and performance of PCS 7 OS has been further enhanced.
Scalability has been extended. For small-scale plant installations up through very large projects,
PCS 7 provides a cost-effective high performance solution.
- OS Project Editor
- Component List Editor
- Faceplate Designer
- Global Script / VBS Editor
- Horn
2.2 Licenses
The former two-tier licensing concept has been expanded to five tiers, to improve scalability.
The license for the PCS 7 Engineering System (AS and OS) is subdivided into the following levels in
V6:
Each of these licenses includes an archiving license for 512 archive (process) variables.
The archiving license can be expanded to 30,000 archive variables. When SP1 becomes available,
this number will expand to 80,000.
No separate license is required for archiving of messages.
For projects migrated from V5.x, there will be equivalent licenses available.
3 OS Project Editor
Extends the existing base data to include additional basic project setting functions:
Functions:
- 1152x864 and above, 4 monitors in landscape (side by side) format not possible
- 1600x1200 and above, 3 monitors in landscape (side by side) format not possible
Area overview Buttons: Up to 64 areas can be configured, depending on the monitor resolution.
Click the Suggestion button to call up a suggested basic setting based on the number of areas already
configured.
Click the Preview button to view the chosen layout and to experiment with changes.
In the Message Configuration window an area can be assigned to messages with no specific plant
area (such as system diagnostics).
By setting the "Message priority" you define a priority for the messages that are created by OS Project
Editor. The default is 0 = lowest priority, 16 = highest priority.
The operation of the message configuration tab depends on the setting of the “Activities when
processed by project editor” setting in the General tag. When this parameter is set to “Configuration
that support online Delta loading only”, changes are not permitted within the Message configuration
tab.
3.3 Areas
Controls the arrangement of the areas in the plant overview
The sequencing of the areas can be configured, and any pre-configured areas, such as those not yet
implemented in the plant in the course of commissioning, can be removed from the plant overview.
With the "Empty Button“ area a placeholder can be assigned in the hierarchy for areas still to be
configured. As a result, the area distribution will not change for the operator when these areas are
added at a later time.
Click the Detail button to set the positioning by entering numerical values or via a slider.
In the "Message filter" box on the "Runtime window" tab you define how the message screens
supplied by PCS 7 are displayed in runtime.
You have the following setting options:
• "No filter". The messages are not filtered. All messages are shown and can be acknowledged,
regardless of the area they are assigned to. This corresponds to the function in version 5.x. when
By way of the "Extended message line" you can define the size of an optional alarm window to be
displayed in the working area.
In the Basic Data window you can see which base data of the project have been changed relative to
their original delivery status. The time stamp serves as a distinguishing feature.
You can define which data are retained specific to the project when the Project Editor is saved, and
which data are adjusted to the system's as-delivered configuration.
3.6 General
On the General tab you configure whether delta loading capability is to be retained for your project
when the Project Editor is used. To retain online delta loading capability, no alarm or startup list
configuration must be done. (See section 4.2 Message Configuration)
You define the mode of logging by the Project Editor: log file in text or HTML format, display mode and
the option if a log file already exists (overwrite/append).
4 Technological Hierarchy
The basic Technological Hierarchy settings have not changed.
The number of included subsidiary hierarchy levels is now selectable when deriving the Block Icons
from the hierarchy.
The "Create/Update Block Icons" function is also executed optimally when compiling the operator
stations. If variable names (including the instance names of charts or hierarchy folders, for example)
have been changed, it is advisable to run this function in the course of compiling the operator stations.
The altered connections may otherwise not be recognized in the Create/Update Block Icons" function
and the block icons in question would lose their positions in the display.
5 Graphics Designer
The extended status display standardizes the configuration of the process dynamics or a process
object symbol. They can be incorporated in user objects, and can be edited centrally using the
Graphics Update Wizard. Using them reduces the need for scripting, resulting in higher system
performance. The facility to link to a total of four status words ensures a high degree of adaptability to
existing blocks. The extended status display of new blocks is enabled by connection only to the status
word VSTATUS.
With the extended status display you can define any number of different dynamic states desired on the
basis of one or more variables and assign them to basic and flashing displays (basic picture/flash
picture). As the status variable you preferentially use the variable VSTATUS or any numeric variables
from the WinCC variables library.
These status variables can be combined with alarm information.
The extended status display is configured in two stages. In the first stage you define which bits of the
status words are relevant to the visual display and whether the group value of the block is to be
incorporated into the display. For the group value you define the priorities of the individual alarms ( 0=
inactive, 1= top priority, 6= low priority).
In the second stage you can assign a basic picture and an optional flash picture for all resultant
combinations (relevant bits of the status words and states of the group value of the block = max 478
states).
A selection of pictures is stored in the GraCS folder. Custom pictures can be created in the Graphics
Designer and saved in the GraCS folder using the Export function.
In the PCS 7 OS Configuration Manual is a detailed description of the extended status display and
how the “Status” represents the bit combination of the statuswords.
Application example:
In the Valve block the status values QOPENED; QCLOSED,, QOPENING; QCLOSING can be used to
provide custom displays for the "open", "closed", "opening" and "closing" states and can be combined
with the "Fault" alarm state.
With the extended analog display you can display the value of an analog variable in runtime in various
colors dependent on alarm state. The alarm state is determined by evaluating the group value.
The extended analog display is configured in two stages. First you define the foreground and
background colors of the analog value for each of the individual message (alarm) classes.
In the Properties dialog box you configure the variable which represents the value of the alarm state of
a block. Then you configure the group value of a block.
You can also configure behavior specific to simulation. This will enable you to simulate a specific
situation. The displayed value is colored regardless of the alarm status of the block. The simulation
variable is only evaluated in the "OK" alarm state.
When linking variables by way of the "ES Variables" option the connection and the alarms are
automatically placed in the background.
The flags in the Picture Tree are not updated.
Consequently, the operator stations do necessarily have to be compiled later on to complete the
configuration process. When SP1 becomes available, this update will be performed automatically
when the operator stations are loaded.
Selection of the block icons can be configured on an instance-by-instance basis for each CFC. This
makes it possible to assign different block icons to the blocks in the CFC. Enter "2“ in the "Block
symbol" box in the Valve function block to select vertical alignment of the valve in the system diagram.
If custom picture blocks are configured, they can be assigned to a function block by means of their
picture names. A picture block with the Attribute “type” named @Valve/Compressor can be assigned
in the Valve function block in the CFC by the entry "Compressor“ in the block symbol box.
The "Select Block Icon" function is only relevant in conjunction with the "Create/Update Block Icons"
function. The picture blocks provided by the system are stored in "@@PCS7Typicals".
6 Faceplate Designer
A new version of the Faceplate Designer is included in PCS 7 V6 in the component libraries.
The layout of the view’s for faceplates is created in the Faceplate Designer Editor.
Insert in the box “Type” the name of the faceplate you want to create and click the “Generate” button.
For adding new view’s to an existing faceplate, use the “More” button.
The individual views of the faceplate can then be configured in the Graphics Designer. For the
Standard view, for example, the picture @PG_<faceplate name>_Standard.pdl is provided in the
GraCS folder.
The picture @pcs7elements.pdl contains template elements for designing the view’s of the faceplates
for PCS 7 V6.
7 Server – Client
7.1 General
Client/Server functionality, data access to up to 12 servers
(Archives, messages, tags, variables)
This means it is possible to access data from multiple servers within a single client picture.
For the sake of compatibility, a standard client will be available for migrated projects from version 5.
Health-check:
All individual processes running on the servers are checked continuously. In the event of failure of a
process, a redundancy switch is made.
The new functionality means it is no longer necessary to configure a project design on a client locally.
The entire project can be designed on the ES.
The packages are handled on the ES, and are distributed from there to all connected clients.
The Create Server Data function is activated automatically when a client is connected.
In the event of configuration changes on the server, packages are created automatically and loaded
manually/automatically. The function is activated on downloading to the OS servers. The clients are
then notified of the change.
- Process data – the OS client receives this data directly from the OS servers.
- Message data – the OS client receives this data directly from the OS servers.
- Archive data – the OS client receives this data from the archive server.
Configuration of the central archive server is detailed in the PCS 7 OS Configuration Manual.
The redundancy synchronization is now executed by copying individual segments of the MS SQL
database (files). As a result, a synchronization of redundant archives is executed very quickly.
There is a dedicated serial link between redundant servers to increase availability and to provide a
very reliable connection.
It permits rapid detection of the system status of the redundancy partner independent of the network.
The servers are interconnected via the selectable COM ports by means of a Null modem cable
(RS232).
8 AS – OS Communication
Acknowledgement-triggered reporting of alarms ensures that identical alarms are not re-reported until
the previous instance is acknowledged. this ability to suppress “alarm chatter” is configured on a CPU-
by-CPU basis via HW config in the “Diagnostics/clock” tab.
The effective AS-OS communication bandwidth has been increased by the incorporation of event (or
change) –based reporting of data.
Event-based communication can be used along with active cyclic read services. Data is then
transferred from the AS only when a value changes, and once per AS cycle. This function must be
supported by the particular model of AS and firmware version.
The AS and the AS-OS communication are subjected to less load from cyclic services and by change-
based reporting, as read commands do not have to be continually sent to the AS for processing.
A stabilization of analog values can be attained by means of an user application.
9 Archive System
The new high-performance archive system uses the MS SQL server database.
Features:
- High Performance
- OS storage option no longer required
- Loop archives with built-in backup facility
- Storage with data compression
- Fast synchronization of redundant systems
- Online configuration
- Preliminary/planned
- Recording and archiving of 1000 process values per second on an OS server
- Recording and archiving of 30 messages per second on an OS server
- Message surge up to 3,000 messages in 10 seconds
- Archiving of 10,000 process values per second on central archive server
- Central redundant archive server for process values (no messages)
- Archive-relevant data configurable in ES – via Process Object List
- Migration V5 Æ V6 (conversion)
Tag logging must be activated in the startup list of the archive server.
Alarm logging must also be activated, so that messages such as redundancy switches and hard disk
full notifications can be detected throughout the system.
Tag logging should be deactivated on the other servers (default setting).
Main screen
The system decides which value is saved to which archive based on the configured recording cycles
of the individual values.
This differentiation speeds up saving of the values.
Access to slow values from the archive is also improved as a result.
Archive Configuration
An archive is configured in two stages:
separately for the TagLoggingFast and TagLoggingSlow processes,
taking into account the total available memory.
Under "Time of the segment change" you can set the time and calendar day on which a new segment
is created.
You configure whether the archive data are to be stored on a backup data medium.
You can specify two possible backup data media locations. If the first data medium is not available, the
backup is saved to the second.
The specified path may be on the local computer or a network path.
Notes:
In a PCS7 environment it is not possible at present to use a dedicated archive server, as it is not
possible to split messages and their variables connections across different computers.
Configured messages in PCS 7 are archived by default. Archiving can be disabled in the popup for the
specific message.
Archive Configuration
An alarm is configured in two stages:
Under "Time of the segment change" you set the time and calendar day on which a new segment is
created.
10 Component Configurator
All PC stations must be configured in accordance with the settings of the Component Configurator.
11 User Administrator
System capacities:
- 999 access privileges, (8 fixed)
- 128 users
- 128 groups
- 256 areas
The "Just monitor" function is for observers with no process controlling access privileges who
nevertheless want to be able to see the messages.
Web Navigator
12 Visual Basic
VBS runs interpretatively. Consequently, solutions capable of operating at SIMATIC-AS level should
not be implemented with scripting. The performance of the overall system should be the primary
concern when using VBS.
Details:
Online Help / Configuring with WinCC / Creating procedures and actions in VB script
Note:
VBS provides you with access from WinCC to all the subobjects of the Windows Scripting Host
(WSH), but no direct access to the WSH object itself.
VBA is used in the WinCC Configuration environment to support customization of the Graphics
Designer and to simplify and automate the configuration process. VBA programs run only in the
configuration environment of WinCC.
In contrast to VBA, VB-Script run only in the WinCC runtime environment, providing you with access
from there to graphical objects and variables. With VBS, as opposed to VBA, you cannot create or
modify objects or pictures.
Procedures: A procedure corresponds to a function in C. In procedures you store code which you want
to use at multiple points in your configuration. You call up the code in an action or another procedure
by calling the procedure name. In WinCC you can create procedures with or without return values.
Procedures have no trigger of their own, they are always initiated by an action.
Modules: In modules you group the procedures into logical units. You create modules for procedures
used in a specific picture, for example, or relating to a specific subject matter, such as auxiliary
mathematical functions and database access functions.
Actions: Actions are always initiated by a trigger (triggering event). Actions are configured for
properties of graphical objects, for events occurring in a graphical object, or globally within the project.
In actions you can call up code which you use more than once in the form of procedures.
- In Global Script Global actions, not specific to a picture, accessible in the project
- In Graphics Designer For properties or events in graphical objects, stored in the picture
Both Visual Basic and Visual C can be used within a project each within separate actions. It is not
possible to access VB from C or vice versa within a single action!
A great deal of detailed information on these topics is available in the Online Help.
13 Horn
The horn is no longer configured by way of the Alarm Logging Wizard, but in the Horn Editor.
Message assignment
Message response: Set signal variable for incoming messages:
- for each incoming message
- not for an unacknowledged incoming message (to suppress alarm chatter messages and ensure
that the horn is only triggered once unless the message is acknowledged)
Horn Reset
If the horn is reset by way of an OS in a system of coordinated WinCC clients/servers you need one or
more additional reset variables. The reset variables must already be configured on the server of the
WinCC client or on other servers, and the variable name must be suffixed by "@HornReset". A binary
variable in the AS can also be used, for a horn reset button for example.
The additional reset variables are synchronized with the local @HornReset variable. As soon as a
reset variable for an active signal is deactivated by reset, the local @HornReset variable is reset,
thereby deactivating all signal transmitters.
The wav files can be stored in the project folder ...wincproj/<OS>/Horn or be referenced by way of
their absolute path (as a project security measure!).
14 Time Synchronization
This permits system configurations in which the automation system is in a different time zone to the
operator station, for example. If required, the plant operator can also switch on-demand during runtime
to display UTC time or local time.
The following example shows the setting for the OS server with time synchronization via the windows
domain controllers.
In the PCS 7 OS Configuration Manual you find detailed description for the setting of OS server and
clients und the synchronization via DCF77 / GPS, SICLOCK TM and Domain Controllers.
The Component List Editor lists the measuring points with their attributes.
It provides an overview in table form of the existing measuring points and allows assignment of which
picture or group display is to be calles up via the loop-in-alarm button.
Click on any of the column headers to sort the table by that column.
The Project Editor creates the attributes (measuring point, type, area,...) − that is, the columns in the
block list. The items of data themselves are entered during OS compilation.
In the "Edit measuring point" dialog box you can edit the entry point picture. The entry point picture
defines the display for the loop-in alarm.
If no entry point picture is configured, the default is the corresponding group display.
If there is no AS-OS Engineering in the ES, you can configure the measuring points manually by
choosing "Create measuring point" from the menu.
16 Report System
Changes in V6
- Dynamic report parameters (via a WinCC tag or dialog; eg the timespan of a curve report)
- Import of third-party data from CSV files in table or trend curve form; COM port
18 SIMATIC LOGON
In Windows 2000 each user is defined in the standard Windows User Administration function and
assigned to a group in it. Only the group with its access privileges is now created in PCS 7 User
Administrator, and no longer the individual users.
This means the benefits of the Windows User Administration access protection facility are also usable
for PCS 7 OS and SIMATIC BATCH.
This extract from the installation instructions for SIMATIC LOGON illustrates how to integrate it into
PCS 7 OS (WinCC).
Procedure
To gain acces to the SIMATIC Logon Admin Tool, create in the Windows 2000 useradministration an
User Group with the name Logon_Administrator and assign a user to it with Power User rights.