PCS 7 - System Documentation - Readme

SIMATIC
PCS 7 System Documentation V7.0 SP1

Notes on the Documentation
Please read the notes carefully as they contain important information and additions to the manuals of the PCS 7
system documentation.
The electronic manuals supplied in PDF format are for the most part identical to the contents of the online help
("PCS 7 Basic Documentation") in the SIMATIC Manager (Help > Topics). There may be minor deviations
between the electronic manuals and the online help due to the technical process associated with the publishing
deadlines. If there are discrepancies, the information in the online help and readme file can be considered more
up-to-date.
When printing the file, ensure that the left and right margins are set to a width of 25 millimeters
(approximately 1 inch) for A4 portrait.
Contents
1
Notes on the Product Documentation
PC Configuration and Authorization Manual
Getting Started
Engineering System Configuration Manual
Operator Station Configuration Manual
Operating instructions PCS 7 OS Process Control
"PCS 7 Basic Documentation" Online Help in the SIMATIC Manager
High-precision Time Stamping Manual
10
PCS 7 Security Concept
11
Integration of MES Functions
12
Information on PCS 7: WinCC OPC A&E Server
-------------------------------------------------------------
Notes on the Product Documentation
Names of the user interface elements, such as menu command and dialog box
names
The German/English/French user interface names are used depending on the language of the
manual. If you have installed a multi-language package, some of the designations will be displayed
in the base language of the operating system after a language switch and will therefore differ from
the designations used in the manual.
What's new?
In the foreword of the manuals, you will find specific information concerning the changes in
comparison to the previous version of the respective manual.
Conventions
In the documentation, the designations of elements of the user interface are specified in the
language of this documentation. If you have installed a multi-language package for the operating
system, some of the designations will be displayed in the base language of the operating system
after a language switch and will, therefore, differ from the designations used in the documentation.
Readme file
Contrary to the description in the documentation, the following files ar only available in RTF format.
PCS 7 System Documentation - Readme.rtf

pcs7-readme.rtf
PC Configuration and Authorization Manual

OPC XML DA
OPC XML DA has not been approved for PCS 7 V7.0.
Driver for smart card reader

Using the USB smart card reader OMNIKEY CardMan 3121 USB
USB smart card readers can only be used with SIMATIC Logon. The sentence "Required drivers
are installed automatically with PCS 7." in the overview of the section "Additional devices and
drivers for PCS 7" only applies to smart card readers with a COM port!
The driver for using the USB smart card reader must be installed manually using the Windows
Computer Administration > Device Manager --> Driver on the "PCS 7 Toolset" DVD under Additional
Products > Drivers > SMART CARD > CardMan 3121 USB.
Licensing for network adapters with integrated terminal bus

You require a BCE license for using a CP 1613 on the system bus and to configure the terminal bus
in NetPro (not required for system functionality).
Calculation of the number of process objects for the selection of a "WinCC RC PO"
license for the Engineering Station
The number of process objects must be determined for each OS.
The number of process objects is calculated based on:
The number of process objects of the SIMATIC stations assigned to the corresponding OS (refer
to chapter 4.6.4)
The number of tags configured "manually in WinCC (WinCC tag / 25 = 1PO)

The OS which contains the highest calculated number of process objects is decisive for the license
to be selected.
Upgrade of a "non-redundant" CAS to a redundant CAS

Initial situation:
A system with PCS 7 V7.0 SP1 contains a non-redundant CAS, for example after the software of
the PCS 7 system has been updated from PCS 7 V7.0 to PCS 7 V7.0 SP1.
Requirements:
Software updating of the PCS 7 system is completed.

All the archive segments connected to CAS (called CAS1 in this document) are disconnected.
Procedure:
1) Determine the path of the project directory at CAS1. The project directory is located at the ES
project under Object Properties/Target OS/"Path to target OS computer" in the project of
"WinCC CAS Appl." of the CAS1.
2) Determine the name of the StoragePlus database. The name is contained in the StoragePlus
Administration Console under System Configuration/Common Database Name (for example
"_ARCHIVE_01_.*).
3) Determine the path of the StoragePlus database in the installation directory. You can determine
the path in the Windows Explorer by searching for the name of the database that you
determined under Item 3 (for example ...\StoragePlus\Database\).
4) Install a PC station CAS2 with Windows Server2003 SP2 as the operating system and all the
required operating system settings and required components.
5) Change the configuration at the ES from a "non-redundant" CAS to a redundant CAS.
6) Terminate the process operation at CAS1. Restart the CAS1 PC station.
7) Terminate the "SQL Server (WinCC)" service by using the service console (note: administrator
rights required).
8) Copy the StoragePlus databases with the path of CAS1 (PC station) to CAS2 (PC station).
9) Copy the project from CAS1 (PC station) to CAS2 (PC station).
10)Restart the CAS1 PC station.
11) Carry out a full download for CAS1 and start the process operation.
12) Install the CAS on the PC station CAS2 from the PCS 7 V7.0 SP1 DVD "Central Archive
Server".
13)Adapt the path and name for the StoragePlus databases to the previously copied folder and
database name.
14) Complete the installation of the CAS2.
15) Load the target system for the operator stations that swap to the CAS Archive.
16) Carry out a full download for CAS2 and start the process operation.
Getting Started
Libraries
The libraries of the example projects for Getting Started located on the DVD may need to be
updated.
Videos on Windows Server 2003

The videos integrated in the Getting Started cannot run on Windows Server 2003.
Engineering System Configuration Manual

Changing the cyclic interrupt time in the RUN of a CPU
Each change to the cyclic interrupt time of a CPU requires compilation of the program. Otherwise,
the CPU_RT block continues to work using the old values.
Configuring the local PC station

When configuring the local PC station, the "Use configured target computer" check box must be
deactivated (in the SIMATIC Manager: Menu command PLC > Configure...).
CiR synchronization time:

The CiR synchronization time is relevant when you activate a configuration change in the RUN
operating mode.
A CiR action interrupts operation on the AS at a maximum for this time. This is set by the system to
a high limit of 1 second and is monitored by the system. During this time, process outputs and
process inputs are kept at the last valid values.
Ensure you do not exceed a CiR synchronization time of 1 second.
SCF 104 may not be used to set the CiR synchronization time in PCS 7.
Multilingual project/display languages

For multilingual projects, you must add all display languages that will later be needed in the
SIMATIC Manager (menu command Options > Language for display devices before the first OS
compilation, and supplement all required languages to "Languages installed in the project").
The OS transfer must be performed in the same language in which the changes were made.
For example, if you import Spanish texts (language for display devices: Spanish), you must also
perform the OS transfer in this language. Otherwise the changed texts will not be added to the
WinCC text library. If prior to this, however, you set German, for example, and then perform the OS
compiling, no change (in German text) is recognized and no text is transferred.
In order to also use texts from the PCS7 library in WinCC, you can only select the following S7
languages in the SIMATIC Manager under "Language for display devices":
German (Germany)
English (USA)
French (France)
Italian (Italy)
Spanish (international sorting)
The texts for Spanish (international) are converted to texts for Spanish (traditional) when the OS is
compiled. The same applies if you want to translate your own texts into one of the five main
languages and import them into your project using the menu command Options > Manage
multilingual texts. For other languages, refer to the languages available in WinCC. It is not possible
to use different variants or sortings of a language in parallel for WinCC, i.e. you cannot use English
(USA) alongside English (UK) or Spanish (international sorting) alongside Spanish (traditional
sorting) or Dutch (Netherlands) alongside Dutch (Belgium).
Renaming process tags

After renaming process tags and subsequently compiling the OS, all interconnections in pictures
and archives as well as tags in script are automatically adapted. Only the names of the archive tags
are currently not adapted, they continue to show the old process tag names. You can change the
archive tag names accordingly if you wish. In this case, be sure to also adapt the associated trend
controls.
The correction of the interconnections is only made for the local process tags of the OS. Any
interconnections to process tags on other OS via server-server communication are not adapted.
Please adapt these interconnections yourself.
Matching numbers or names for block names

Simultaneous use of the libraries "Standard Library" (STEP 7), "CFC Library" (ES/CFC), "PCS 7
Library": The libraries of STEP 7, ES, and PCS 7 contain blocks with the same name but with
different functions, as well as different blocks with the same FB number.
CONT_C/CONT_S/PULSGEN/CTU/CTD/CTUD
For these blocks, use the blocks from the CFC Library, since these are better adapted to the PCS 7
environment.
Matching numbers
for: FC 61 ...125 in the libraries "Standard Library - S5-S7 Converting Blocks" and "Standard Library
- TI-S7 Converting Blocks" and "CFC Library ELEMENTA"
for: FC 1 ... FC 40 in the libraries "Standard Library - Communication Blocks", "Standard Library IEC Function Blocks" and the reserved FC inventory in CFC.
Remedy: The blocks must be assigned free FB/FC numbers in the block folder.
Open PCS7 - Transparent OPC A&E access to historical alarms (Historical A&E) on a
central archive server (CAS)
Configure the following items in order to include access to OS alarms in a CAS archive when
reading alarms on the Operator Station by means of OPC Alarms & Events:
1) Open the Object Manager and also assign the CAS to the OS server while configuring in the
SIMATIC Manager (right-click the OS project, select "Assign server" and then select "CAS").
2) Deactivate the "All servers" check box in all the alarm controls of the OS server and explicitly
select the servers (without the CAS) from which you want to read alarms.
---------------------------------------------------------------------------------------------------------------Note
Alarms archived on the CAS are included automatically if you specify a time range in an Alarm
Control, irrespective of whether the CAS is excluded in your server selection.
----------------------------------------------------------------------------------------------------------------
Using updated blocks

An update of the PCS 7 channel blocks within SIMATIC PCS 7 was included in V7.0 and in the
enhancements of Maintenance Station functionality. Channel blocks of version 6.x neither
supported the output of a faulty process value including the corresponding "quality code", nor the
implementation of corresponding failure alarm functionality in accordance with NAMUR
recommendation NE 107 on the OS. The following states were displayed after the failure of a
process value:
Simulation (corresponds to a manipulated process value)

Substitute value (corresponds to a manipulated process value)
The new channel blocks provide a distinctive and clear representation of these states. The
adaptation of functionality has also change the default response, that is, as of the PCS 7 V7.0
library a signal failure the process value failure is now displayed without project-specific settings on
the OS as failed value and with quality code.
Observe this item when migrating to the process control system V7.x.
Operating HART field devices on redundant HART-AI/AO modules

Configure the following items:
1) Configure the modules required in HW Config, including the necessary redundancy parameters.
2) Configure the channels of modules with HART field devices. One field device must be assigned
to each one of the two redundant module channels.
3) Open PDM. By opening PDM you define the device to be used and initiate the implicit integration
of the corresponding device at the redundant channel.
Operator Station Configuration Manual

Multilingual project/display languages
See information for Engineering System Configuration Manual
ES/OS Compiling and downloading objects downloading OS data

Before you trigger a download, ensure that there is sufficient free space for storing project data and
server data (reserve enough space for 1 x server data) on the hard disk of the OS runtime systems
(servers, clients or single stations). If the OS system has insufficient space for data during the
download, an error message appears which you must confirm. This message currently also appears
when downloading with "Compile and Download Objects" and must also be explicitly acknowledged
in this case.
Contrary to the online help, no status is shown with "Compile and Download Objects" for WinCC
objects.
Reading swapped-out archives on a central archive server

To be able to display data from swapped-out archives from predecessor version of PCS 7 V7.0 on a
central archive server, you need to read and attach the archives. Once archives are attached for the
first time, process mode of the archive server must be stopped and then started again.
When you read swapped-out archives on a central archive server, they are only available on this
archive server (even when using a redundant central archive server).
Automatic notation of the range of values of tags

In order to enable automatic activation of minimum/maximum values and of the names derived from
the corresponding PCS 7 block for visualization of the range of values of tags in the Online Trend
Control of the process control system, the following conditions must be met:
The "S7_trend" attribute is assigned to the block type for the block I/O which represents the tag.
For additional information, refer to the Process Control System PCS 7; Engineering System
Manual.
The I/O names and the block I/O which represent the minimum/ maximum range of values of the
tag were entered in the "Value" column for the "S7_trend" attribute. The I/O names are
separated by comma.
The unit is assigned to the block I/O of the block instance.

For additional information, refer to the Process Control System PCS 7; Engineering System
Manual.
The OS is compiled.
Operating instructions PCS OS process control

List of "Highest-priority alarms"
The button for calling the list of "Highest-priority alarms" is displayed on the left side of the alarm
line if at least an alarm of priority class 16 is active (incoming alarm or incoming alarm
acknowledged status).
The button is hidden if no further alarm of priority class 16 is active (incoming alarm or incoming
alarm acknowledged status).
By contrast to group displays, the button also flashes to indicate active acknowledged alarms.
Click this button to display list of "Highest-priority alarms". It is not possible to acknowledge alarms
within this list.
Priority 16 alarms in the list of "Highest-priority alarms"

Each active priority 16 alarm (incoming alarm or incoming alarm acknowledged status) is
displayed in accordance with alarm filter settings in the OS Project Editor ("Alarm
representation" tab, "Alarm filter" group).
One alarm representative without area assignment is generated when Priority 16 alarm
events that are assigned to the "Diagnostics" area occur.
This draws the attention of users who are not authorized to access the "Diagnostics" area to
the fact that at least one priority 16 alarm is active in the "Diagnostics" area.
Behavior of alarms in the list of "Highest-priority alarms"

Alarms without configured outgoing state
Alarms are no longer displayed in the list of "Highest-priority alarms" after acknowledgment
"Disable alarms"
Disabled alarms are not displayed in list of "Highest-priority alarms" and do not trigger an
acoustic alarm signal
"Hide alarms "

Hidden alarms are not displayed in list of "Highest-priority alarms" and do not trigger an
acoustic alarm signal
Hiding/ showing alarms

An operator who manually sets up the hide / show alarms function must have been granted access
rights to "Higher-priority process control".
Filtering alarms
The dialog boxes and procedures described in the documentation are not implemented in PCS 7
V7.0 SP1. For information with regard to dialog boxes and filter settings, refer to the WinCC
Information System, chapter "Working with WinCC > Structure of an alarm system >
Visualization of alarms in Runtime > Operating in Runtime > How to select
alarms".
Message about an invalid or a non-existing PCT ID

If the message about an invalid or a non-existing PCT ID is displayed in the maintenance station in
a diagnostic faceplate, proceed as follows:
Check whether the project for this maintenance station is entered in the SIMATIC Manager
under Options > SIMATIC PDM > Settings in the "Maintenance Station" tab.
Note: When such error messages occur, the following menu command is activated for the
respective project (the multiproject): Options > SIMATIC PDM > Disconnect MS Connections.
If the correct (multi)project is entered as an MS project, carry out the following menu command:
Options > SIMATIC PDM > Disconnect MS Connections.
Save and compile the HW Config.

Generate or update the diagnostic screens in the technological hierarchy. Carry out compilation
and a download (of changes) for the AS and OS.
Software Update Manuals

Performing the software update
Note that you need to complete the software update before beginning any additional changes in the
configuration.
Step sequencers (SFC) for software updates without use of new functions
Note that step sequencers must be stopped for downloading changes.
Software update V6.x -> V7.0

You can find the documentation for software updates from PCS 7 V6.x to V7.0 on the PCS 7 Toolset
DVD PCS 7 V7.0.
Software update V5.1/5.2 -> V7.0

Additional quick instructions are available for updating PCS 7 projects from V5.1/V5.2 to PCS 7
V7.0.
The quick instructions SW Update PCS 7 V5.1/V5.2 to PCS 7 V7.0 and the SW Update PCS 7 V5.x
to PCS 7 V6.x manuals are available in the Internet under Service & Support:
Product Information > Process Automation > Process Control Systems >
SIMATIC PCS 7 > System Documentation > "Manual/OI" tab
Conditions for performing the software update

In the SW Update manual; section 1.5, "Faceplates of PCS 7 V6.1" is cited in the "Requirements"
column for the "Locking and unlocking of messages for blocks and OS areas" function.
The correct requirement is "Library of PCS 7 V6.1".
PA devices with a profile earlier than 3.0 and slave family 12

As of PCS 7 V5.2 including Service Pack 3, PA devices are supported by the new signal and
diagnostic blocks. This includes the "Generate module driver" function. For this PCS 7 function to
be executed correctly, the GSD file (Rev. 3) of the respective device must contain the entry "Slave
Family = 12". If it does not, contact the device manufacturer to obtain a corrected GSD file.
Upgrading PCS 7 earlier than V6.0 including Service Pack 3 to PCS 7 V7.0 when
using FM355
Since PCS 7 V6.1 including Service Pack 1, you obtain modified blocks for high-performance
support of FM 355 modules (FMCS_PID block (FB 114)) or FM355-2 modules FMT_PID (FB 77) in
version 4.0 of the PCS 7 library.
The use of these new blocks requires the use of the new block FM_CO (FB 79). This coordinates
the access to FM 355 and needs to be correspondingly integrated and interconnected by the user.
Read the information about this in the online help for the block.
NOTICE: If you wish to use these new blocks, you can only do so after a complete compilation and
download, which requires a CPU stop!
Software update PCS 7 V5.x -> PCS 7 V6.0

Section 3.1 of the manual "Software Updates from PCS 7 V5.x to PCS 7 V6.0" states the following:
"In order to utilize new V6 functions, you have to use the new IM 153-2 or IM 157 and the new bus
modules (6ES7 195-7HD10-0XA0 or 6ES7 195-7HD80-0XA0)."
This statement applies to redundant, fault-tolerant systems. The bus module 6ES7 195-7HA000XA0 can continue to be used in a non-redundant configuration.
Chapter 4.3.11 in "SW update from PCS 7 V5.x to PCS 7 V6.0" contains the following information:
"Note:
The new faceplates in PCS 7 V6.0 are compatible with the technological blocks of PCS 7 V5.x. The
faceplates of V6.0 can be used to operate and monitor blocks of PCS 7 V5.x and V6.0"
Supplementary information:
Note that the tag required for visualization must have been assigned the "S7_m_c = true" attribute
at the S7 block.

Note the following regarding the texts in faceplates when performing the tasks for the software
update PCS 7 V5.x -> PCS 7 V6.0 based on the SW Update PCS 7 V5.x to PCS 7 V6.0 manual:
You only need to perform this action:
If you want translate texts to be display texts in faceplates from the default English into other
languages, such as German or French.
If you want to retain old operator texts (with PCS 7 V5.x) from your project.
Texts for analog value and binary value conditions in faceplates are taken from the new V7.0 blocks
in PCS 7 V7.0. The default texts, which are read from the "s7_shortcut", "S7_string_0",
"S7_string_1" and "S7_unit" parameter attributes, are only available there in one language and not
in several languages as was previously the case in WinCC.
The operator texts of the updated faceplates are lost if you use the new faceplates. If, in PCS 7
V7.0, you wish to continue using operator texts (created with PCS 7 V5.x), which are anchored to
the faceplates, you need to append the operator texts in the function block.
Since you are exchanging the blocks (with PCS 7 V5.x) with the new V7.0 blocks, it is important that
you manually change the English default text for function blocks to the desired language in a PCS 7
project which is not to be configured with the English default texts. To change the default texts,
replace the blocks (created with PCS 7 V5.x or PCS 7 V6.0) with the V6.1 blocks in the master data
library.
---------------------------------------------------------------------------------------------------------------Note
If you have changed the operator texts in the block instances in your CFC charts, you can no longer
update the operator texts by importing the block type. You can then only change the operator texts
in the block instances.
----------------------------------------------------------------------------------------------------------------

If you use IN/OUT blocks in your project, note the following when upgrading a project from PCS 7
V5.x to PCS 7 V7.0:
For technical reasons, some INOUT parameter were already moved in the IN section in PCS 7
Library V6.0.
If these new blocks are exchanged in older programs (prior to PCS 7 V6.0), as of version PCS 7
V7.0 the interconnections to INOUT parameters are retained as so-called textual interconnections
at the new IN parameters. You can convert these open textual interconnections to real
interconnection using the command "Make Textual Interconnections" from the "Options" menu of
the CFC Editor. Textual interconnections that are still open or cannot be completed are recorded in
the log as warnings.
Migration of PCS 7 V6.0.3 H systems

If you configure a cyclic alarm with the default priority (>=15) as an OB with special handling in PCS
7 V6.0.3, the changes of the AS can only be downloaded with STOP. Please configure the priority of
the OB with special handling as described in the documentation "Automation System S7-400H
Fault-tolerant Systems".
Software update PCS 7 V7.0 SP1

You can find the libraries of the "older" PCS 7 versions in the software package of the respective
version.
Renaming archives created by the Mapper

Note the following information if using the trend view in the faceplate with archive tags (refer to
'PCS 7 Block programming instructions', chapter 2.1.8 Configuring the trend view):
In order to enable use of the trend view in the faceplate with archive tags, the corresponding archive
in PCS7 V6 must be named 'Process_Value_Archive' and be set up manually in WinCC Tag
Logging.
PCS 7 V6.1 or higher supports automatic generation of archive tags for process values identified
accordingly. This functionality requires identification of the I/O in the CFC as being archive-relevant
by setting the 'archiving' attribute. These archive tags are generated automatically in an archive
named 'SystemArchive'.
Automatic generation of archive tags is set by default in PCS7 V7.0 SP1 or higher for control blocks
of 'PCS 7 Library V7.0', for the control quality block and for the multiple variable control block of
'PCS 7 APC V7.0'. The archive values of the control blocks are required for statistic evaluation.
Corresponding archive tags are generated automatically in 'SystemArchive' after one of these
blocks was reconfigured and the trend view in the faceplate with archive tags is only going to use
the 'SystemArchive'.
It is advisable to make the following changes when upgrading PCS7 V6 projects to PCS7 V7.0 SP1:
All block symbols which are configured in the pictures and assigned the StandardTrend > 2
property must be supplemented in the ReturnPath property with the
archivename:process_value_archive parameter*. Use the corresponding options as described in
the 'PCS 7 Configuring Manual Operator Station', chapter 9.2 'Function and usage of block
symbols and faceplates'.
The enhancement of functionality of the trend view in the faceplate with archive tags also modifies
the default response of parameter *asia: (add server prefix in archive tag) in the ReturnPath
property. The default response in PCS7 V7.0 SP1 or higher does not depend on the server prefix in
the "tagname" of the block symbol if parameter *asia: is not being used. Any server prefix is now
ignored in the derivation of the archive tag name.
It is advisable to make the following changes if you already configured archive tags with server
prefix:
Supplement all block symbols with server prefix in the "tagname" and StandardTrend > 2 property
you configured in pictures with parameter *asia:MyServerPrefix in the ReturnPath property.
Using tags for Tag Logging
The Tag Logging archives are generated automatically in the "System archives" folder in PCS 7
V6.1 or higher. Any archives created by users are retained in parallel.
Observer the following information with regard to archives named "Process value archive" used in
combination with PCS7 faceplates:
Faceplates of V7.0.2 or higher only use the default archives generated by the system.
Additional parameters must be configured in order to enable the use of previous archives named
"Process value archive, that is, existing parameters must be supplemented with the
*archivname:process_value_archive attribute in Block symbol -> Object properties -> Styles ->
ReturnPath.
The archive tag name may not contain a server prefix.

If archive tag names with server prefix were configured in PCS 7 V6.0 or higher, the
parameterization must be supplemented with the "*asia:MyServerPrefix attribute in Block
symbol -> Object properties -> Styles -> ReturnPath..
Individual ASSET export
An update of the project SW in accordance with the "PCS 7 SW Update with utilization of new
functions" Manual is prerequisite for using the individual ASSET export function for projects created
in PCS 7 V7.0.1 or earlier. Carry out the following additional steps:
Procedure:
1) In order to generate the ASSET ID, open HW Config of each AS and PC station, select the
"Assign Asset ID" dialog box and then compile and save the HW configuration data.
2) Deactivate the "Derive diagnostics pictures from the plant hierarchy" function in the plant
hierarchy settings for your (multi-)project.
Note: All diagnostics pictures will be deleted if you deactivate this function. Create a backup
copy all updated project-specific diagnostics pictures before you carry out this operation.
3) Activate the "Derive diagnostics pictures from the plant hierarchy" function in the plant hierarchy
settings for your (multi-)project.
4) Select the "Generate/update diagnostics pictures" function in the plant hierarchy in order to
create the diagnostics structure in the plant hierarchy. The final dialog tells you which AS and
OS projects must be compiled and downloaded. Do not execute this step until you reached item
6.
5) Copy the backed up diagnostics pictures which contain project-specific changes (as described in
item 2) to your project. Execute the "Derive diagnostics pictures from the plant hierarchy"
function once again in the plant hierarchy in order to update these pictures.
6) Compile and download all AS and OS projects defined in item 4.
For information on generally valid settings required for using the individual ASSET export function,
refer to the "PCS 7 Configuration Manual; Operator Station", chapter 15.13.2 "Individual export".
"PCS 7 Basic Documentation" Online Help in the

SIMATIC Manager
Since PCS 7 V6.0 SP3, you can also open the complete system documentation for PCS 7 in the
online help format within the SIMATIC Manager through the help topics. You can open the "PCS 7
Basic Documentation" online help with the menu command Help > Topics in the SIMATIC
Manager.
High-precision Time Stamping Manual

Interface modules for PROFIBUS DP
Accuracy
Order no.
Distributed I/O
device
Module
Revision
1 ms
6ES7 153-2BA01-0XB0
ET 200M
IM 153-2
All
1 ms
6ES7 153-2BA02-0XB0
ET 200M
IM 153-2
All
1 ms
6ES7 153-2BA81-0XB0
ET 200M
IM 153-2
All
1 ms
6ES7 153-2BA82-0XB0
ET 200M
IM 153-2
All
10 ms
6ES7 153-2AA02-0XB0
ET 200M
IM 153-2
>=7
10 ms
6ES7 153-2AB01-0XB0
ET 200M
IM 153-2 FO
>=6
10 ms
6ES7 153-2BA00-0XB0
ET 200M
IM 153-2
>=3
10 ms
6ES7 153-2BB00-0XB0
ET 200M
IM 153-2 FO
>=3
20 ms
6ES7 152-1AA00-0AB0
ET 200iSP
IM 152-1
1.0
20 ms
6ES7 152-1AA00-0AB0
ET 200iSP
IM 152-1
>=2.0
20 ms (for fail-safe signal

acquisition)
6ES7 153-2BA02-0XB0
ET 200M
IM 153-2
All
6ES7 153-2BA82-0XB0
Digital input modules

Order no.
Distributed I/O
device
Module
Use as
6ES7 321-7BH00-0AB0
ET 200M
SM 321
Module for acquisition of

process signals:
16 electrically isolated inputs
(24 V DC) and diagnostic
messages
6ES7 321-7BH80-0AB0
ET 200M
SM 321

process signals:
16 electrically isolated inputs
(24 V DC)
6ES7 321-7TH00-0AB0
ET 200M
SM 321

process signals:
16 inputs (NAMUR)
6ES7 321-7RD00-0AB0
ET 200M
SM 321

process signals:
4 inputs (NAMUR), hazardous
areas
6ES7 326-1BK01-0AB0
ET 200M
SM 326
6ES7 321-7BH01-0AB0
process signals, fail-safe signal

acquisition
24 inputs for use in interface

module
6ES7 153--2BA02
12 inputs
(CH 00 to CH 11) for use
with interface module
6ES7 153-2BA01
6ES7 131-7RF00-0AB0
ET 200iSP
SM 131

process signals:
8 inputs (NAMUR)
10
PCS 7 Security Concept

Security concept for PCS 7 in open plants
For PCS 7, we recommend you implement measures and plant layouts to make intended external
access to a PCS 7 plant (connection to external networks/applications) as secure as possible and to
prevent unauthorized access to PCS 7 data or falsification of data from PCS 7. This also includes
secure access through the PCS 7 OS Web Option function and conformity to requirements of the
FDA guidelines.
1. Documentation about the security concept for PCS 7 is available in the Internet under Service &
Support:
Product Information > Process Automation > Process Control Systems >
SIMATIC PCS 7 > System Documentation > "Manual/OI" tab
11
Integration of MES Functions

"Using SIMATIC IT to integrate MES functionality in PCS 7" manual
Documentation about integrating MES functions will be made available in the Internet under Service
& Support upon completion.
When available, you can find the "Using SIMATIC IT to integrate MES functionality in PCS 7"
manual in the PCS 7 documentation portal at the following Internet address:
"http://www.siemens.de/simatic-tech-doku-portal" under the link "SIMATIC PCS 7 Process Control
System and Migration".
The manual will first be made available in English.
It offers the following information:
Overview of the most important functions from SIMATIC IT for all those who until now have
only known PCS 7
Overview of the most important functions from PCS 7 for all those who until now have only
known SIMATIC IT
Description of the interfaces between SIMATIC IT and PCS 7

Description of application examples for integrating MES functions in PCS 7
12
Information on PCS 7: WinCC OPC A&E Server
12.1
WinCC V6.2 SP2: OPC A&E server with hierarchical access for
use in PCS 7
Introduction
WinCC V6.2 SP2 offers OPC A&E server with hierarchical access for PCS 7.
The OPC A&E server with hierarchical access is configured differently for use in WinCC and in PCS
7.
You can find documentation for its use in WinCC in the WinCC Information System in the section
"Interfaces > OPC - OLE for Process Control > WinCC OPC A&E Server > OPC A&E Server with
Hierarchical Access".
The documentation for the use in PCS 7 is located in the following sections.
---------------------------------------------------------------------------------------------------------------Note
Documentation of new functions for PCS 7
The use of the OPC A&E server with hierarchical access for PCS 7 is not described in the online
help of WinCC V6.2 SP2.
----------------------------------------------------------------------------------------------------------------
12.2
Functionality of the OPC A&E server

Introduction
The OPC A&E server uses DCOM services for transferring messages between OPC-capable
applications. The OPC A&E server supports the specification OPC Alarm&Event 1.10.
The following chapter explains the representation of the WinCC message system on OPC A&E with
hierarchical access and the attributes supported by the OPC A&E server. This documentation
includes an overview of the specific information. For more information, refer to the "OPC Alarms &
Events 1.10" specification.
Principle
The OPC A&E client receives WinCC messages via subscription. You can use the subscription filter
to reduce the number of events that will be transferred with a subscription. The OPC A&E client can
be set for every event category that displays message attributes.
Installation
The OPC A&E server is installed along with the installation of PCS 7 with Open PCS 7. After the
installation, the OPC A&E server can be run on a server or a client without any configuration.
Licensing
In order to operate the OPC A&E server, one of the following licenses must be installed on each
computer running an OPC A&E server:
Open PCS 7 station

Open PCS 7 station / WinCC basic system
Event types
The OPC A&E server with hierarchical access supports conditional events, simple events and
tracking events.
Condition related events

With a condition related event, the event is associated with a condition. The condition, for example,
may be the exceeding of a tag's limit . This limit violation generates a message that is shown as an
alarm with OPC A&E.
Simple events
Simple events are messages that inform the OPC A&E client about events. Simple events include
the launching and closing of programs.
---------------------------------------------------------------------------------------------------------------Note
Note the following when using redundant systems:
Simple events that switch to internal tags are sent twice while comparing tags.
The first message is triggered by master, the second from standby.
----------------------------------------------------------------------------------------------------------------
Tracking events
A tracking event is sent with an operator input message to the OPC A&E client. An operator input
message is triggered by manual intervention in the process.
---------------------------------------------------------------------------------------------------------------Note
When filtering for all alarms of a plant section, note that you need to replace the source with a wild
card in the filter text, since the source is only generated in runtime for tracking events. For example,
the filter text for all events from the "Plant1/Unit1/Tank1" section is "Server
prefix::*Plant1/Unit1/Tank1*" and not "Server prefix::Plant1\Plant1/Unit1/Tank1*".
----------------------------------------------------------------------------------------------------------------
OPC A&E client

All OPC A&E clients conforming to the OPC Alarms & Events 1.10 specification can access the
OPC A&E server. The OPC A&E client may also be a proprietary client. By creating proprietary OPC
clients, most user-specific requirements can be met. An OPC A&E client, for example, may be used
for analysis and joint archiving of alarms from different OPC A&E servers. The acknowledgement of
archived messages is not possible; only current alarms and events can be acknowledged.
---------------------------------------------------------------------------------------------------------------Note
Documentation on OPC
You can find additional information on OPC in the WinCC Information System in Chapter "Interfaces
> OPC - OLE for Process Control".
----------------------------------------------------------------------------------------------------------------
12.3
OPC A&E server with PCS 7 V7.0 SP1
12.3.1
Differences between OPC A&E and OPC A&E with hierarchical access
Displaying messages with OPC A&E
The OPC A&E server supports "conditional events" and "simple events" for accessing the message
system. With "conditional events", the message numbers are shown for each source. Since an OS
server can hold many more message numbers, it is hard to keep an overview of the messages.
The following figure shows an example of the display in an OPC browser:
Displaying the messages with OPC A&E and hierarchical access

The OPC A&E server with hierarchical access supports the event types, conditional events, simple
events and tracking events.
With "conditional events, the source of the messages is determined by the area and the source. The
area can be a system area, a diagnostics area or an alarm hiding group. The string "EventID xx" is
used instead of the text for alarms in which the WinCC "Source" text block for the source is not
configured. "xx" here represents the unique WinCC message number. This syntax is used for the
sources in the Area Browser and for the message itself.
Tracking events occur when operator input messages are triggered in the system.
The following figure shows an example of the display of conditional events in an OPC browser. The
"Condition" is shown in addition to "Area" and "Source":
Recommendation
Use an OPC A&E server with hierarchical access when creating a new project.
If you upgrade an existing project to PCS 7 V7.0 SP1, the OPC A&E server can be used as before
or the OPC A&E server can be converted to hierarchical access. The conversion can be undone
again without any loss of data. You can find additional information under "How to upgrade the OPC
A&E to PCS 7 V7.0 SP1".
12.3.2
How to upgrade the OPC A&E to PCS 7 V7.0 SP1

Introduction
OPC A&E has been expanded by the hierarchical access to the message system with PCS 7 V7.0
SP1. You can still use the non-hierarchical OPC A&E server.
Upgrading OPC A&E

If you are using the OPC A&E with hierarchical access and want to use all functions, you need to
expand the currently used OPC A&E client.
Starting with the PCS 7 version of your project, possible upgrade scenarios are described for OPC
A&E:
Upgrading the project from PCS 7 V6.1 SP1 to PCS 7 V7.0 SP1
Upgrading the project from PCS 7 V7.0 to PCS 7 V7.0 SP1
The project is created with PCS 7 V7.0 SP1.
Upgrading from PCS 7 V6.1 SP1 to PCS 7 V7.0 SP1

You can upgrade a project with PCS 7 V6.1 SP1 with OPC A&E to PCS 7 V7.0 SP1 with OpenPCS
7 Station as follows:
Switching to OPC A&E with hierarchical access

If you want to use OPC A&E with hierarchical access, ensure that the "CcAeProvider.ini" file exists
in the project folder of your WinCC project. Delete all of these files on the OS server projects and on
the ES server projects before upgrading. The project folder is located in "wincproj" sub-folder on the
ES.
Retaining OPC A&E without hierarchical access

If you want to continue working with the previously used OPC A&E server, copy the file
"CcAeProvider.ini" into the project folder of the ES projects. You can find the file on the Product
DVD under "AdditionalProducts\OPC_A&E_Server\PCS7_V70". Run a complete download
afterward.
---------------------------------------------------------------------------------------------------------------Note
Changed server prefix for the local computer
Pay attention to the changes in OPC A&E, even if you want to continue working with the previously
used OPC A&E server.
The server prefix of the local computer is now called "@LOCALMACHINE" instead of "localhost".
----------------------------------------------------------------------------------------------------------------
Upgrading from PCS 7 V7.0 to PCS 7 V7.0 SP1

Switching to OPC A&E with hierarchical access
If you want to use OPC A&E with hierarchical access, ensure that the "CcAeProvider.ini" file exists
in the project folder of your WinCC project. Delete all of these files on the OS server projects and on
the ES server projects before upgrading. The project folder is located in "wincproj" sub-folder on the
ES.
Retaining OPC A&E without hierarchical access

If you want to continue working with the previously used OPC A&E server, copy the file
"CcAeProvider.ini" into the project folder of the ES projects. You can find the file on the Product
DVD under "AdditionalProducts\OPC_A&E_Server\PCS7_V70". Run a complete download
afterward.
Creating a project with PCS 7 V7.0 SP1

Projects that are created with PCS 7 V7.0 SP1 use the OPC A&E server with hierarchical access.
You do not have to make any additional settings.
If you want to work with the OPC A&E server without hierarchical access, proceed as follows:
1. After upgrading, copy the "CcAeProvider.ini" file to the project folder of the ES projects. You can
find the file on the Product DVD under "AdditionalProducts\OPC_A&E_Server\PCS7_V70".
2. Perform a complete download for the OS server.
12.4
Mapping the WinCC Message System on OPC A&E
12.4.1
Mapping the WinCC message system

Introduction
The WinCC message system resulting from the configuration defines which event in the process will
generate a message. This message is shown as an event notification in OPC A&E.
Mapping the WinCC message system on OPC A&E with hierarchical access
The OPC source of the WinCC user text block "Source" and the OPC message of WinCC user text
block "Message text" are used in PCS 7 as a default setting for mapping the WinCC message
system.
Overview
The following table shows the most important attributes of the event notifications and the respective
information from the WinCC message system.

The events that use the configured attributes are shown in the third column of the table:
"S" means a simple event
"C" means a conditional event

"T" means a tracking event
OPC
WinCC message system
Area
An area is an area in PCS 7, a diagnostics area or an alarm hiding group. If there is no S, C,

area, diagnostic area or alarm hiding group configured for the message, only the OPC
area corresponding to the server prefix is available.
Source
Indicates the source of a message. The source has the format "<Server
S, C,
prefix>::Area\Source". The server prefix of a local computer is "@LOCALMACHINE".
The server prefix always shows the top Areas in the hierarchy of the server.
Time
Issues a time stamp for received, sent and acknowledged messages. Issues a time
stamp in UTC (Universal Time Coordinated).
S, C,
Type
Indicates whether the event is a simple, tracking or conditional event.
S, C,
Severity
Returns the priority of the message.
S, C,
EventCategory
Indicates the message class. "Event Category" is made up of the "CategoryID" and
the "Category Description". "CategoryID" corresponds with the internal ID of the
message class. "Category Description" corresponds with the name of the message
class.
S, C,
Message
Indicates the message text of the corresponding message number.
S, C,
Condition
Indicates the message type. The message types "Alarm", "Warning" and "Tolerance"
are combined and shown under designation "Level" in PCS 7.
Sub Condition
Corresponds with the "Condition" parameter. Identical to the condition for single state C
conditions in PCS 7. The following subconditions are mapped for the "Level" multistate
condition in PCS 7:
Alarm low
Alarm high
Warning low
Warning high
Tolerance low
Tolerance high
Even
ChangeMask
Specifies the change of the condition. For more information, refer to "Acknowledgment C
policy".
NewState
Indicates the current status of the condition. For more information, refer to
"Acknowledgment policy".
ConditionQuality
Returns the quality of the message. For more information, refer to "Quality codes".
AckRequired
Indicates whether the message requires acknowledgment (receipt).
EventAttribute
Lists the attributes required for the respective message. For more information, refer to C
"Attributes of the WinCC message system".
Quality
Returns the quality code of the message.
Cookie
Does not include any usable information for the client
ActorID
Indicates which user acknowledged the message.
---------------------------------------------------------------------------------------------------------------Note
The message classes and message types must be configured identically on the connected OS
servers, if you run the OPC A&E server as follows:
On a WinCC Client
On a Connectivity station
In the context of Open PCS7
If the OS server is not configured identically, the OPC client that is used must access the respective
OS server directly.
----------------------------------------------------------------------------------------------------------------
12.4.2
Mapping the message priority

Introduction
The priority of messages is mapped by the OPC A&E server to the attribute "Severity".
When configuring alarms in the messaging system, you can configure a priority between "0" and
"16". The OPC A&E specification defines a value range of "1" to "1000" for the severity. In this case,
"1" stands for the lowest and "1000" for the highest severity.
Therefore, the values of the priority are suitably displayed to the OPC severity. In the standard
mapping, priority "0" is assigned to OPC severity "1" and priority "16" to OPC severity "1000". All
other priority values are interpolated linearly between "0" and "1000".
12.4.3
Attributes of WinCC message system

Introduction
The following table lists the OPC attributes of the WinCC message system. The attributes are
configured in the WinCC message system. Some attributes are intended for internal use in WinCC
only and are therefore not relevant to an OPC A&E client. These attributes are not contained in the
table.
Attributes
OPC attributes
WinCC message system
ClassName
Returns the message class name.
Type name
Returns the message type name.
ForeColor
Returns the text color for the display of received, sent and acknowledged
messages.
BackColor
Returns the background color for the display of received, sent and acknowledged
messages.
FlashColor
Returns the flashing color.
Flags
Indicates whether the message requires acknowledgment (receipt).
Source
Returns the content in the source.
Area
Returns the content of the area.
Event
Returns the content in the event.
Batch name
Indicates the batch name.
Operation
Returns the content of operator message.
Text06
Returns the content of UserTextBlock06.
Text07
Text08
Text09
Text10
ProcessValue01
Returns the content of ProcessValueBlock01.
ProcessValue02
ProcessValue03
ProcessValue04
ProcessValue05
ProcessValue06
ProcessValue07
ProcessValue08
ProcessValue09
ProcessValue10
StateText
Returns the status message.
InfoText
Returns the information text for the message.
LoopInAlarm
States if LoopInAlarm has been configured.
ClassID
Returns the message class ID.
TypeID
Returns the message type ID.
AG_Number
Returns the number of the automation device that generated the message.
CPU_Number
Returns the number of the CPU that generated the message.
Duration
Indicates the period of time between message received, sent and acknowledged.
QuitStateText
Indicates whether the message has been acknowledged.
Priority
Indicates the configured priority of the message.
12.4.4
Acknowledgement theory
Introduction
For WinCC, the acknowledgment policy is how a message is displayed and processed from "came
in" to "went out". On the OPC A&E server, this message status is displayed in the "ChangeMask"
and "NewState" parameters.
Conditional events, simple events and tracking events

Messages from the system are sent to the client as conditional events with acknowledgment.
In order for a message to be treated as a simple event, the message class of the message must
meet the following conditions:
"Acknowledgment Came In" is not activated.
"Message Without Status Went Out" is activated.

The following messages are sent as tracking events in PCS 7:
Messages of the "Operator message" message class.
Messages of "System, does not require acknowledgment" message class with the "Operator
message" message class.
---------------------------------------------------------------------------------------------------------------NOTICE
Messages with "System, does not require acknowledgment" message class and "Process control
system" message type are transferred as simple events with the "System message" event category.
----------------------------------------------------------------------------------------------------------------
ChangeMask
The "ChangeMask" parameter keeps track of where the message status was changed.
Parameter values:
OPC_CHANGE_ACTIVE_STATE
OPC_CHANGE_ENABLE_STATE
OPC_CHANGE_ACK_STATE
NewState
The "NewState" parameter indicates the message status after a change.
Parameter values:
OPC_CONDITION_ACTIVE
OPC_CONDITION_ENABLED
OPC_CONDITION_ACKED
Overview
WinCC
NewState
ChangeState
Received message
Sent message with receipt
Sent message without receipt
Acknowledged messages (message

pending)
OPC_CONDITION_ACKED
Acknowledged messages (message no

longer pending)
Locked message
--------------------------------------
OPC_CHANGE_ENABLED_STATE
Unlocked message
OPC_CHANGE_ENABLED_STATE
Received, acknowledged message
OPC_CONDITION_ACKED
Received, sent message with receipt
Received, sent message without receipt
Message acknowledged by the system

(message pending)
OPC_CONDITION_ACKED
Message acknowledged by the system

(message no longer pending)
Emergency-acknowledged message
(message pending)
OPC_CONDITION_ACKED
Emergency-acknowledged message
(message no longer pending)
---------------------------------------------------------------------------------------------------------------Note
Historical alarms and events are not acknowledged. The OPC A&E historical events interface only
has read access.
----------------------------------------------------------------------------------------------------------------
12.5
Quality Codes for OPC A&E
Introduction
Quality codes are used to evaluate the status and quality of a message. The table below lists the
quality codes for OPC A&E.
Quality codes
Code
Quality
Status
0xC0
OPC_GOOD
OK
0x40
OPC_UNCERTAIN
Returned in cases of uncertainty, for example

in the event of delayed acknowledgment
(receipt).
0x00
OPC_BAD
Returned if the connection to the source is

interrupted.
12.6
PCS 7 application example OPC A&E with hierarchical access
12.6.1
Example 1: Messages are not assigned an area

Introduction
Process control messages, batch server messages and route control server messages are not
assigned an area or group. For these messages, no designated area is assigned in the structure of
the OPC A&E access.
Requirement
Process control messages are created on the OS servers.

Batch server messages and route control server messages are created on the dedicated
message servers.
No diagnostics area is not provided.

Structure for access to messages via the OPC A&E interface
The general reference to the OPC A&E interface appears as follows:
OPC Server
OS Server
Source
Condition
Sub Condition
Example for a hierarchy without assignment

The following example shows the hierarchy of messages in a browser, which can be sent to the
client as a "conditional event":
12.6.2
Example 2: Messages are assigned an area

Introduction
A system project is normally divided into several system areas and diagnostic areas. This assigns
the messages to the areas.
The areas are shown as a hierarchy level in OPC A&E for the hierarchical mapping.
Requirement
The system project contains areas or diagnostic areas.
Structure for access to messages via the OPC A&E interface

OPC Server
OS Server
Area / Maintenance Area
Source
Condition
Sub Condition
Example for a hierarchy with an area

The following examples show the hierarchy of messages in a browser, which can be sent to the
Example with areas:
Example with diagnostic areas:
1.6.3
Example 3: Messages of an area are assigned with an alarm hiding group

Introduction
Alarm hiding groups are used in a system project to hide certain messages automatically. An alarm
hiding group can contain messages from several areas.
This chapter describes how OPC A&E accesses these messages.
Requirement
Alarm hiding groups are configured in WinCC with the engineering.
Access to the messages via the OPC A&E interface

The messages of an area are only shown in the alarm hiding group. The messages are no longer
visible in the area.
OPC Server
OS Server
Alarm Hiding Group
Source
Condition
Sub Condition
Example for a hierarchy with an alarm hiding group.

The following example shows the hierarchy of messages in a browser, which can be sent to the

PCS 7 - System Documentation - Readme

Uploaded by

Copyright:

Available Formats

PCS 7 - System Documentation - Readme

Uploaded by

Document Information

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

PCS 7 - System Documentation - Readme

Uploaded by

Copyright:

Available Formats

SIMATIC

PCS 7 System Documentation V7.0 SP1

Notes on the Product Documentation

PC Configuration and Authorization Manual

Engineering System Configuration Manual

Operator Station Configuration Manual

Operating instructions PCS 7 OS Process Control

"PCS 7 Basic Documentation" Online Help in the SIMATIC Manager

High-precision Time Stamping Manual

PCS 7 Security Concept

Integration of MES Functions

Information on PCS 7: WinCC OPC A&E Server

Notes on the Product Documentation