Siemens SIMATIC PCS 7 Installation guide

SIMATIC
Process Control System PCS 7
Compendium Part D -
Operation and Maintenance (V9.0)
Operating Manual
Valid for PCS 7 V9.0
02/2018
A5E43228948
-AA
Security information
1
Preface
2
Installing updates and
service packs
3
Replacing hardware
4
Firmware update of
hardware
5
Service and maintenance of
SIMATIC PDM
6
AS and OS expansions
7
Backing up and restoring
data
8
Service and support
9

Siemens AG
Division Digital Factory
Postfach 48 48
90026 NÜRNBERG
GERMANY
A5E43228948-AA
Ⓟ
02/2018 Subject to change
Copyright © Siemens AG 2017.
All rights reserved
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury
may
result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by
personnel qualified
for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.

Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 3
Table of contents
1 Security information ................................................................................................................................ 5
2 Preface ................................................................................................................................................... 6
3 Installing updates and service packs ....................................................................................................... 8
3.1 Introduction ...............................................................................................................................8
3.1.1 General .....................................................................................................................................8
3.1.2 What must necessarily be taken into account? ........................................................................9
3.1.3 Differences between maintenance and a software update with the redundant OS
server ......................................................................................................................................11
3.2 Checking plant configuration ..................................................................................................12
3.3 Checking plant status..............................................................................................................14
3.3.1 General ...................................................................................................................................14
3.3.2 Status of PC stations using SIMATIC Shell............................................................................15
3.3.3 Time synchronization..............................................................................................................16
3.3.4 Status of OS connections .......................................................................................................16
3.3.5 Standard server settings.........................................................................................................18
3.3.6 Preferred server settings.........................................................................................................20
3.3.7 Redundancy status on the OS server.....................................................................................22
3.3.8 Client-server connections .......................................................................................................26
3.3.9 Archive synchronization of the redundant OS server after a hot restart of the standby
server ......................................................................................................................................26
3.3.10 Process control messages......................................................................................................28
3.4 Checking the WinCC channel diagnostics..............................................................................29
3.5 Checking the OS functionality after restarting an OS server..................................................31
3.6 Deactivating and activating non-redundant OS servers .........................................................32
3.7 Deactivating and activating redundant OS servers ................................................................33
3.8 Additional Information .............................................................................................................34
4 Replacing hardware .............................................................................................................................. 35
4.1 Use of new hardware ..............................................................................................................37
4.2 Deploying new hardware as replacement...............................................................................40
4.3 Procedure for replacing hardware ..........................................................................................41
5 Firmware update of hardware................................................................................................................ 44
5.1 Introduction .............................................................................................................................44
5.2 Downloading the firmware ......................................................................................................44
5.3 Updating firmware of a CPU ...................................................................................................45
5.4 Updating firmware of an H system..........................................................................................45
5.4.1 Updating firmware during operation........................................................................................45
5.4.2 Firmware update using S7-400 Flash memory card...............................................................47

Table of contents
Compendium Part D - Operation and Maintenance (V9.0)
4Operating Manual, 02/2018, A5E43228948-AA
5.5 Updating firmware of a communications processor (CP) ...................................................... 47
5.6 Updating firmware of an interface module (IM)...................................................................... 48
5.7 Updating firmware of I/O modules ......................................................................................... 49
5.8 Updating firmware of network components ........................................................................... 50
6 Service and maintenance of SIMATIC PDM .......................................................................................... 51
6.1 General information on importing devices ............................................................................. 51
6.2 Device import in SIMATIC PDM............................................................................................. 52
6.3 Managing device descriptions in the project.......................................................................... 53
6.4 Updating SIMATIC PDM ........................................................................................................ 57
6.5 Updating device descriptions ................................................................................................. 61
6.6 Replacing/removing field devices .......................................................................................... 62
6.6.1 Scenario 1 - Replacing a device of the same type and with a later version .......................... 63
6.6.2 Scenario 2 - Replacing a device with a different type............................................................ 68
6.6.3 Case 3 – Removing field devices........................................................................................... 71
7 AS and OS expansions ......................................................................................................................... 72
7.1 Changes to the AS configuration ........................................................................................... 72
7.1.1 Changes to the configuration of an automation system that uses PROFINET ..................... 72
7.1.2 Changes to the configuration of a standard AS that uses PROFIBUS DP............................ 73
7.1.3 Changes to the configuration of an H-system that uses PROFIBUS DP .............................. 77
7.1.4 Changes to the configuration of an ET 200iSP...................................................................... 80
7.1.5 Changes to the connection configuration .............................................................................. 81
7.2 Program changes................................................................................................................... 82
7.2.1 Checking the logs................................................................................................................... 83
7.2.2 Checking the delta download capability with time stamp comparison................................... 83
7.2.3 Measures for maintaining delta download capability ............................................................. 84
7.2.4 Parameter changes................................................................................................................ 91
7.2.5 Reading back charts .............................................................................................................. 91
7.3 Changes to the safety program or F signal modules............................................................. 92
7.4 Changes in the OS project..................................................................................................... 93
8 Backing up and restoring data............................................................................................................... 94
8.1 Introduction ............................................................................................................................ 94
8.2 Restore DVDs supplied with bundle PCs .............................................................................. 94
8.3 Rules for creating backups .................................................................................................... 95
8.4 Software for creating backups ............................................................................................... 96
8.5 Creating a backup.................................................................................................................. 96
8.6 Recovery plan ........................................................................................................................ 97
8.7 Storing backups ..................................................................................................................... 97
9 Service and support .............................................................................................................................. 98

Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 5
Security information
1
Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems, machines
and networks. Systems, machines and components should only be connected to the
enterprise network or the internet if and to the extent necessary and with appropriate security
measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. You can find more information about Industrial Security at
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends to apply product updates as soon as available and to
always use the latest product versions. Use of product versions that are no longer supported,
and failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed at https://www.siemens.com/industrialsecurity.

Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 6
Preface
2
Subject of the manual
As a distinctly open system, SIMATIC PCS 7 can be flexibly adapted to a wide range of
customer needs. The system software provides the configuration engineer with a great deal
of freedom in terms of project configuration, as well as in the design of the program and
visualization.
Experience has shown that subsequent modernization or plant expansion work is made
much easier if the project is configured "in conformance with PCS 7" as far as possible right
from the start. This means users must adhere to certain basic rules to ensure that the
provided system functions will offer optimum usability in the future.
This manual serves as a compendium in addition to the product documentation for SIMATIC
PCS 7. The basic tasks for creating and assigning parameters to the project are described in
the form of instructions with numerous illustrations.
The compendium directly reflects the recommended method for configuration, which is
based on the results of a great deal of practical experience. The description relates to
working with the project and the parameter settings of the components it contains but not the
application itself.
The compendium contains the following parts:
●Configuration guidelines including checklist
●Process safety including two checklists
●Equipment phases with SFC types
●Operation and maintenance including checklist
●Hardware installation including checklist
●Industrial Security
Compendium Part D "Operation and Maintenance"
Part D describes several runtime scenarios of a plant, for example, maintenance, expansion
and upgrading.
Particular attention is paid to the following topics in this regard:
●Planning and implementing PCS 7 updates
●Replacing modules as spare parts
●Updating firmware and PDM data
●Adding hardware and functions
●Checklist with important points for preparation and implementation of project changes and
installation of updates.

Preface
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 7
Checklists
You can download the checklists for the SIMATIC PCS 7 compendium part D as a zip file via
the "Appendix" button in the Industry Online Support Portal.
Validity
This documentation is valid for the software packages:
●SIMATIC PCS 7 V9.0
SIMATIC PCS 7 in Industry Online Support
An overview of the most important technical information and solutions for SIMATIC PCS 7 is
available at http://www.siemens.com/industry/onlinesupport/pcs7.
SIMATIC PCS 7 documentation
The complete documentation of PCS 7 is available to you free of charge and in multiple
languages in PDF format at www.siemens.com/pcs7-documentation.

Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 8
Installing updates and service packs
3
3.1
Introduction
3.1.1
General
One scenario which may arise within a PCS 7 plant is the need to install updates or service
packs safely and effectively.
Updates may be:
●PCS 7 updates
●PCS 7 service packs
●Microsoft updates
●Antivirus software updates
●Other software updates
Compendium Part D focuses on the preparations and checks which you need to make
before you start to install PCS 7 updates and service packs or maintain PCS 7 plant
sections. The information applies in particular to redundant plant sections which are to be
maintained or upgraded during operation.
Note
You can find practical information and brief instructions for the PCS 7 software update in
FAQ "Information and brief instructions for updating/upgrading PCS 7 sof
tware"
(
https://support.industry.siemens.com/cs/ww/en/view/39980937).
The procedure for updating software in the context of a PCS 7 project is described in detail
in the following manuals:
●"SIMATIC Process Control System PCS 7 – Software update without utilization of new
functions" (https://support.industry.siemens.com/cs/ww/en/view/109746552)
●"SIMATIC Process Control System PCS 7 – Software update with utilization of new
functions" (https://support.industry.siemens.com/cs/ww/en/view/109746554)
●"SIMATIC Process Control System PCS 7 – Fault-tolerant Process Control Systems"
(https://support.industry.siemens.com/cs/ww/en/view/109746538)

Installing updates and service packs
3.1 Introduction
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 9
You can find information about Microsoft updates and antivirus software in the following
sources:
●FAQ "With what are SIMATIC PCS 7 V8.x, V7.x, V 6.x, V5.x and V4.x compatible?"
(https://support.industry.siemens.com/cs/ww/en/view/64847781)
●FAQ "Which Microsoft Security Patches have been tested for compatibility with SIMATIC
PCS 7?" (https://support.industry.siemens.com/cs/ww/en/view/18490004)
●Manual SIMATIC Process Control System PCS 7 Security Concept PCS 7 & WinCC
(Basic) (https://support.industry.siemens.com/cs/ww/en/view/60119725)
●Manual SIMATIC Process Control System PCS 7 Trend Micro OfficeScan 11.0
Configuration (https://support.industry.siemens.com/cs/ww/en/view/103630611)
●Manual Symantec Endpoint Protection V12.1.6 Configuration
(https://support.industry.siemens.com/cs/ww/en/view/109736192)
●Application example Use of Whitelisting with McAfee Application Control in a PCS 7 /
WinCC environment (https://support.industry.siemens.com/cs/ww/en/view/88653385)
●Manual SIMATIC Process Control System PCS 7 Configuration McAfee VirusScan
Enterprise 8.8 – White Paper
(https://support.industry.siemens.com/cs/ww/en/view/66475606)
●Manual "Security Concept PCS 7 and WinCC (Basic)"
(https://support.industry.siemens.com/cs/ww/en/view/60119725)
3.1.2
What must necessarily be taken into account?
You need to deactivate the OS and restart the PC stations to install a PCS 7 update and
service pack, a Microsoft update or to maintain the OS server and OS client hardware.
Process availability
Operator control and monitoring functions often must continue to run, thus ensuring that the
PCS 7 plant operates safely, while such actions are being performed. The following sections
describe checks, which we recommend you carry out
before, during, and after
an update or
maintenance work.
If it is necessary to restore the plant to the same state it had before the update or service
pack was installed, we strongly recommend that you back up all computers (including the
ES) and the PCS 7 multi-project or keep the backup available. You can find details on this in
the section titled "Backing up and restoring data" (Page 94).
Make sure that all software products and information required for performing the update,
such as additional software, libraries, add-ons, information about non-standard functions
within the project, modified system pictures, or other data specific to the plant, etc. is
available. All project-specific settings, such as PC, network, web server and archiving
system, should also be known. You need to verify this information with the plant operator in
advance, because there may have been changes to the PCS 7 plant since its initial
installation/most recent update.

Installing updates and service packs
3.1 Introduction
Compendium Part D - Operation and Maintenance (V9.0)
10 Operating Manual, 02/2018, A5E43228948-AA
Plant status
You should always evaluate the plant status
before
you start starting work on OS stations in
Runtime.
●Is the OS server system in a redundant status?
●Do all clients have a connection to the OS servers?
Only if you can answer "yes" to these two questions can you start the scheduled update.
You should carry out specific intermediate checks
while
the relevant work is being
performed. You should carry out these checks while updating the PCS 7 project on the ES,
but they should also be performed on the updated OS stations in the plant.
For example, you first install a new PCS 7 service pack on a redundant partner and the
associated OS clients. Then you check whether the plant can be operator-controlled on the
updated stations. If this test is successful, you can continue with the work and update the
remaining OS stations.
After
the work has been completed successfully, you must perform a full check of the plant
redundancy status and its operator control and monitoring functionality.
Note
A guide to checking the redundancy status is available in the section titled "Checking the OS
functionality after restarting an OS server"
(Page 31).
Coordination of timings
You must make sure that matters are organized such that maintenance work is not carried
out on redundant components simultaneously. Actions of this type must be coordinated so
that they are performed one after the other and they must not overlap.
Also note the following regarding the update sequence of the PCS 7 stations:
Before you start to update the OS stations (Runtime), you must have already updated the ES
itself with a new PCS 7 service pack, for example, as well as the PCS 7 project. As part of
this process, it is essential that you have compiled all AS and OS stations with the new PCS
7 service pack for the entire PCS 7 project. We always recommend that you carry out an OS
simulation or a brief test (for example, download the target system for AS and OS in a testing
environment) before starting work on a running plant.
Note
You can find a summary of the individual check points in the "PCS
7 delta configuration"
checklist that is part of the PCS 7 Compendium
Part D.

Installing updates and service packs
3.1 Introduction
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 11
3.1.3
Differences between maintenance and a software update with the
redundant OS server
Maintenance
In this context, maintenance is considered a task performed when the OS server is
deactivated and in which the OS software version is not changed. This may involve cleaning
the OS server hardware, for example.
When a redundant OS server is deactivated, you should avoid the situation where all OS
clients switching from the master server to the standby server at a given time, because this
would render the plant inoperable for the duration of the switchover.
Configuring a preferred server for the OS clients enables you to achieve even distribution
across the master and standby servers. If one of the OS servers is deactivated, only half of
the OS clients will switch to the partner server.
Software update
You must install the same software version on the OS servers and the OS clients connected
to them.
The standby OS server is usually deactivated first and its software updated. Before you
deactivate the standby OS server you must check that the master OS server is fully
functional and a sufficient number of functional OS clients must be connected to that master
OS server.
First update only the OS clients which are interconnected with the standby OS server that
has already been updated or which have defined it as their preferred server. Then update
the OS clients which are interconnected with the master OS server or which have defined it
as their preferred server.
This method is not practical if the maximum number of OS clients must be available for
operator control and monitoring purposes during the software update. In this case, all OS
clients must first be connected to the master server by configuring the preferred server. The
standby server is then deactivated, the OS software updated, and the server started again.
The next step involves deactivating each OS client one after the other, updating the
software, and then connecting each OS client to the standby server by configuring the
preferred server. Once each OS client has been updated, check that its operator control and
monitoring functions are working correctly.

Installing updates and service packs
3.2 Checking plant configuration
Compendium Part D - Operation and Maintenance (V9.0)
12 Operating Manual, 02/2018, A5E43228948-AA
Once all OS clients with their new software version have been connected to the standby
server, the master server will be deactivated and its software updated.
When the redundant servers and the OS clients have the same software version, the OS
clients can be distributed between the master and standby servers with the help of the
preferred server configuration.
Note
In order to guarantee the cont
inuous operator control and monitoring capabilities, the
following conditions must be fulfilled:
•
Before downloading the AS: Operate and monitor the processes through the operator
stations, whose software has not yet been updated.
•
After downloading the AS: Operate and monitor the processes through the operator
stations, whose software has been updated.
3.2
Checking plant configuration
The first step is to check if the OS server to be deactivated is a redundant server pair. If a
redundant OS server is not involved, the plant section will be inoperable for the duration of
the server shutdown. In this case, we recommend you plan to carry out the
maintenance/software update during a regularly scheduled maintenance shutdown of the
plant.
You should be familiar with the plant structure before shutting down an OS server.
Check the following points in the PCS 7 project on the engineering station:
●How many OS servers/redundant OS servers are there in the PCS 7 plant?
If uninterrupted plant operation must be ensured during the shutdown of the OS server, at
least one OS server per OS server pair must continue to run in process mode without
interruption.
●How many automation systems are there in the PCS 7 project?
Which automation systems are assigned to the which OS server/redundant OS server?
If uninterrupted plant operation must be ensured during the shutdown of the OS server, a
corresponding OS server must be available for each AS.
●Is the OS server you want to deactivate a standard server for OS clients?
●Does it involve a PCS 7 plant with SIMATIC BATCH?
Is the OS server to be shut down a message server relevant for BATCH?
Is the OS server you want to shut down also a BATCH server?

Installing updates and service packs
3.2 Checking plant configuration
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 13
If so, no batches should be running or started at the time of the OS server shutdown.
●Does it involve a PCS 7 plant with SIMATIC Route Control?
Is the OS server you want to shut down also a Route Control server?
If so, no material transport should be running or started at the time of the OS server
shutdown.
●Is a higher-level MES system connected to the PCS 7 system?
If so, you need to ensure the MES system will not attempt to access the OS server during
the shutdown period.
Note
Depending on the plant configuration, the additional measures for activating and
deactivating an OS server may
vary.
You should consult with the system administrator responsible for SIMATIC BATCH,
SIMATIC Route Control, PH (Process Historian), MES and other systems to define the
measures that need to be introduced. Also refer to the respective product manuals in t
his
regard.
Note
The system configuration can be checked by the SIMATIC Management Console
(inventory function). You can find additional information in the manual "SIMATIC Process
Control System PCS 7 SIMATIC Management Console"
(
https://support.industry.siemens.com/cs/ww/en/view/109748755).

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
14 Operating Manual, 02/2018, A5E43228948-AA
3.3
Checking plant status
3.3.1
General
To check the current plant status, we recommend carrying out these tests directly on the OS
server and the OS client, as settings may also have been changed directly on the Runtime
computers.
Certain checks must be performed in the WinCC Explorer, which means it will have to be
accessed. If access to the WinCC Explorer is blocked by OS Runtime, you must terminate
OS Runtime operation. In this case, we recommend first carrying out all plant status checks
which can be performed during OS server/OS client Runtime, before terminating that mode.
If settings need to be changed on the OS server or the OS client directly, you must also
incorporate the changes on the ES. This means there will be no difference between the PCS
7 project on the ES and the data on the Runtime system, and the changes will not be lost
after the Runtime system is loaded again.
Note
T
he state monitoring (check for installation readiness) can also be performed with the aid of
SIMATIC Management Console. You can find additional information in the manual "SIMATIC
Process Control System PCS 7 SIMATIC Management Console"
(
https://support.industry.siemens.com/cs/ww/en/view/109748755).

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 15
3.3.2
Status of PC stations using SIMATIC Shell
The "Simatic Shell" dialog is a component of the PCS 7 OS and is used for central
maintenance and diagnostics of all computers integrated in your client-server system. The
"SIMATIC Shell" dialog displays all OS client and OS server computers available on the
network. The status of the computers and the loaded OS client and OS server projects can
be determined using SIMATIC Shell.
Procedure
1. Open the Windows Explorer on the ES.
2. Select the folder "My Computer > Simatic Shell" in the tree view.
Note
You
can use the shortcut menu, for example, to check the redundant connection to the
partner server on an OS server via the menu command "Redundancy Settings".
Note
You can find more information in the WinCC online help and in manual "SIMATIC
Process Cont
rol System PCS 7 - Service Support and Diagnostics"
(
https://support.industry.siemens.com/cs/ww/en/view/109746550).

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
16 Operating Manual, 02/2018, A5E43228948-AA
3.3.3
Time synchronization
Before deactivating an OS server, you should check whether all computers in the PCS 7
plant are running in synchronism. System messages generated by the OS server are
assigned a time stamp by the OS server. If there is no time synchronization set for a
redundant OS server, for example, it is difficult to chronologically track the system
messages.
Note
You can find more information on time synchronization in manual "SIMATIC Process Control
System PCS 7
- Time Synchronization"
(
https://support.industry.siemens.com/cs/ww/en/view/109746544).
3.3.4
Status of OS connections
The current status of all configured connections can be determined with the "Options >
Status - Connections" function in the WinCC Explorer.
Procedure
1. Open the WinCC Explorer on the OS server. The OS project must be in Runtime on the
server.
2. Select the menu command "Options > Status - Connections".

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 17
3. Check the entries in the "Status" column. The "Cleared" entry may indicate an error in the
configuration or hardware.

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
18 Operating Manual, 02/2018, A5E43228948-AA
3.3.5
Standard server settings
Before you deactivate an OS server, check whether it is configured as a standard server.
General information
As a general rule, only a standard server for alarms, the SSM (Split Screen Manager) and
optionally also for user archives is configured for PCS 7.
Standard servers are configured in the "Server Data > Standard Server" menu of the WinCC
Explorer. Such configurations are usually set on the ES and then loaded to the OS client.
Configured standard servers must be checked on the OS client directly, as settings may also
have been changed directly on the OS client. The WinCC Explorer needs to be accessed on
the OS client for this purpose.
The standard server must be checked on every OS client. If deviating settings do arise, the
ES project must be adjusted.
Alarms
If you want to generate operator messages for operations on an OS client, you will have to
specify a standard server for alarms. You cannot configure alarm logging on the OS client
itself. The messages must be archived on an OS server.

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
Operating Manual, 02/2018, A5E43228948-AA 19
SSM (Split Screen Manager)
You must specify a standard server for the SSM component if you want to compile trend
groups or screen compositions on an OS client and store them on the standard server.
If no standard server is configured for the SSM component on the OS client, the compiled
trends are saved locally on this computer. Other OS clients cannot have these trend groups
displayed in the Online Trend Control. The same applies to screen compositions.
When redundancy is configured on an OS server, the data of the trend groups and the
screen compositions are also synchronized on the respective redundant partner server. This
means all compiled trend groups and screen compositions can be called up from all OS
clients when you perform a redundancy switchover.
The configured standard servers will be displayed in the "Server Data" menu in the WinCC
Explorer of the OS client, as shown in the following example.
Example
Loaded server data (package) without standard server
Loaded server data (package) with standard server
Scenario
A PCS 7 plant contains three non-redundant OS servers. The server data from three OS
servers is assigned to an OS client. If a non-redundant OS server has been configured on
the OS client as the standard server for alarms and SSM and this OS server needs to be
deactivated, then:
●The OS areas of an OS server not in process mode cannot be operator-controlled.
●No operator messages will be generated for the OS areas that can still be operator-
controlled while the server is shut down.
●The configured compilations of trends are not available. The same applies to OS servers
still in process mode.
●The configured screen compositions are not available. The same applies to OS servers
still in process mode.

Installing updates and service packs
3.3 Checking plant status
Compendium Part D - Operation and Maintenance (V9.0)
20 Operating Manual, 02/2018, A5E43228948-AA
You should therefore check if a server is a standard server before deactivating runtime on it.
Deactivation of process mode on the OS server must be timed in such a way that the
functionality it provides will not be missed.
Note
When a redundant OS server is used, the functionality of the standard server will be
maintained only if one
computer of the OS server pair is deactivated.
If no standard server is configured for alarms of an OS client, then the OS client will not
generate any operator messages.
3.3.6
Preferred server settings
Function of the preferred server in process mode
If redundant OS servers are used, then the OS client will interconnect with the OS server
which has been configured as the preferred server. If the preferred server fails, the OS client
switches to its partner server. When the failed preferred server returns, the OS client will
switch back to this OS server.
We recommend configuring the preferred server for the OS client on the ES and then loading
the OS client. Because the preferred server can also be configured on the OS client via the
WinCC Explorer, you should check the preferred server directly on the OS client.