Software Update Without Using New Functions

Security information 1
Preface 2
Introduction 3
SIMATIC
Overview of the update tasks 4
PCS 7
Software update without utilization Preparing for the software
5
update
of new functions
Installation of PCS 7 and
settings on the ES and OS 6
Service Manual
Adaptations in the PCS 7
project on the ES 7
Downloading to target
systems 8
Activating operator stations 9

Updating SIMATIC BATCH
stations 10
Updating SIMATIC Route
Control stations 11
Migration of archive data
from a central archive server 12
(CAS)
Update by keeping the installed PLC blocks libraries

Valid for PCS 7 as of V8.0 according to V9.0
05/2017
A5E36200133-AA
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.
Siemens AG A5E36200133-AA Copyright © Siemens AG 2017.

Division Process Industries and Drives Ⓟ 05/2017 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Security information......................................................................................................................................7
2 Preface.........................................................................................................................................................9
3 Introduction.................................................................................................................................................13
3.1 Defining a strategy for the software update...........................................................................13
3.2 General requirements............................................................................................................15
3.3 Important Information for Software Update without Utilization of New Functions..................17
3.4 Information on Products from the PCS 7-Add On Catalog.....................................................20
3.5 Licensing with the Automation License Manager...................................................................21
4 Overview of the update tasks.....................................................................................................................23
4.1 Information about software update procedure.......................................................................23
4.2 Overview of the procedure.....................................................................................................24
5 Preparing for the software update..............................................................................................................27
5.1 Overview of the migration of CAS to the Process Historian...................................................27
5.1.1 How to Detach Attached Archive Segments on the Central Archive Server..........................27
5.1.2 Migration of CAS to the Process Historian.............................................................................28
5.2 Preparatory tasks...................................................................................................................30
5.2.1 Overview of preparations.......................................................................................................30
5.2.2 Exchanging data via OPC A&E..............................................................................................30
5.2.3 How to Back Up PCS 7 Project Data.....................................................................................30
5.2.4 How to Back Up User Created Libraries................................................................................33
5.2.5 Operator and Display Texts in Blocks....................................................................................34
5.2.6 How to export operator and display texts...............................................................................34
5.2.7 Backing up pictures for user-defined status displays.............................................................35
5.2.8 Backing Up the License Keys and Authorizations..................................................................35
6 Installation of PCS 7 and settings on the ES and OS.................................................................................37
6.1 Overview of Installation and Settings on the ES and OS.......................................................37
6.2 How to Update PCS 7............................................................................................................38
6.3 How to enable encrypted communication between the PC stations......................................40
6.4 Installation of Additional PCS 7 Libraries...............................................................................42
6.5 How to Install Additional PCS 7 Libraries...............................................................................43
7 Adaptations in the PCS 7 project on the ES...............................................................................................45
7.1 Updating a PCS 7 project.......................................................................................................45
7.2 General adaptations...............................................................................................................46
7.2.1 Overview of General Adaptations in the Project....................................................................46
7.2.2 Changing the Configuration of Multilingual Texts...................................................................46
Software update without utilization of new functions

Service Manual, 05/2017, A5E36200133-AA 3
Table of contents
7.2.3 Importing Data from the User Archives..................................................................................46

7.2.4 How to update the configuration of the operator stations.......................................................47
7.2.5 How to Check the Plant Hierarchy Consistency.....................................................................48
7.2.6 How to update the hardware configuration for SIMATIC PCS 7 BOX RTX and SIMATIC
PCS 7 AS RTX.......................................................................................................................48
7.2.7 How to configure the SIMATIC PDM Server..........................................................................49
7.3 Adaptations in NetPro and conversion of the CFC/SFC charts.............................................52
7.3.1 How to Check and Adapt the Connection Data in NetPro......................................................52
7.3.2 How to convert the CFCs and Shared Declarations..............................................................53
7.4 Adaptation of OS-relevant settings........................................................................................55
7.4.1 Overview of Adaptation of OS-relevant Settings....................................................................55
7.4.2 Synchronization of OS Basic Pictures, Local Computer Actions and Faceplates..................55
7.4.3 How to Synchronize OS Basic Pictures, Local Computer Actions, and Faceplates..............55
7.4.4 Mixed operation and visualization of AS blocks from different PCS 7 versions.....................58
7.4.5 How to Update the Picture Objects........................................................................................59
7.5 Adaptations for the Process Historian....................................................................................61
7.5.1 Adaptations for the Process Historian at a glance.................................................................61
7.5.2 How to update the Process Historian and Information Server...............................................61
7.5.3 How to replace the CAS with the PH.....................................................................................62
7.6 Adaptations for the Maintenance Station...............................................................................64
7.6.1 Overview of the Maintenance Station update........................................................................64
7.6.2 How to change the OPC Server, adapt the SNMP configuration and update SIMATIC
PDM ......................................................................................................................................64
7.6.3 How to update the diagnostics settings..................................................................................66
7.6.4 How to update the diagnostics screens.................................................................................67
7.7 Additional options...................................................................................................................69
7.7.1 Overview of additional options...............................................................................................69
7.7.2 Updating the PCS 7 Web Option for OS................................................................................69
7.7.3 Updating PCS 7 Components that Use SIMATIC Logon Services........................................69
7.8 Work for the OS in SIMATIC Manager...................................................................................70
7.8.1 Overview of compiling............................................................................................................70
7.8.2 How to Compile the OS..........................................................................................................70
8 Downloading to target systems..................................................................................................................73
8.1 Downloading to target systems..............................................................................................73
9 Activating operator stations........................................................................................................................75
9.1 Overview of activating the operator stations..........................................................................75
9.2 How to Check the settings on the OS Servers.......................................................................76
9.3 How to Check the settings on the OS Clients........................................................................77
10 Updating SIMATIC BATCH stations...........................................................................................................79
11 Updating SIMATIC Route Control stations.................................................................................................81
12 Migration of archive data from a central archive server (CAS)...................................................................83
12.1 Archive migration at a glance.................................................................................................83
12.2 How to migrate the archives in the Process Historian............................................................84

4 Service Manual, 05/2017, A5E36200133-AA
Table of contents
Index...........................................................................................................................................................87

Table of contents

Security information 1
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines, and 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. For more information about industrial security, please visit:
http://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 under
http://www.siemens.com/industrialsecurity.

Security information

Preface 2
Purpose of this documentation
This documentation provides a comprehensive overview of the steps you must take to adapt
your existing PCS 7 process control system to the new SIMATIC PCS 7 version. It supports
you in updating PCS 7 projects and guides you through installation and commissioning of the
current software.
The contents of the documentation are directed toward service personnel, commissioning
personnel, and experienced PCS 7 users with the necessary system knowledge. The
documentation provides instructions for carrying out the software update.
Refer to the documentation for specific products for information regarding the handling of these
products.
Scope of the documentation

This documentation applies to the software package Process Control System; SIMATIC PCS 7
V9.0.

Preface
Options for accessing PCS 7 documentation

The documentation required for PCS 7 includes the following types:
● PCS 7 Readme
The readme file is available in two versions:
– PCS 7 Readme (offline)
This version is installed by PCS 7 Setup. The file only contains general information and
links to documents on the Internet.
– PCS 7 Readme (online)
This version contains all information on the installation and use of PCS 7 in the format
which is already familiar to you. The file is only available on the Internet to keep it always
up-to-date.
Note
The information provided in the PCS 7 Readme (online) on the Internet takes
precedence over all other PCS 7 documentation.
Read this PCS 7 Readme carefully, because it contains important information and
amendments on PCS 7.
● PCS 7 System Documentation

System documentation contains information that covers several products, such as
configuration manuals and Getting Started manuals. This documentation serves as a
guideline for the overall system and explains the interaction between the individual
hardware and software components.
Read the information on "PCS 7 Documentation Portal Setup" in the product overview
Process Control System PCS 7; PCS 7 ‑ Documentation; Section "Options for accessing
the documentation".
● PCS 7 Product Documentation
Product documentation contains information about special hardware and software
components. The individual documents provide detailed information on the specific
component.
Full versions of the documentation are available from the "Technical Documentation SIMATIC
PCS 7" website:
http://www.siemens.com/pcs7-documentation (http:\\www.siemens.com/pcs7-documentation)
You can find additional information in the product overview Process Control System PCS 7;
PCS 7 - Documentation; Section "Options for accessing the documentation".

Preface
Documentation for the software update

You can find all documentation on the topic of "Software update" on the Internet.
Documentation Contents
Manual Software update without utiliza‐ Describes the procedure for the software update of PCS 7
tion of new functions projects without utilization of new functions.
● Original version of the existing project:
PCS 7 as of V8.0 or higher.
● Project to be updated to the following version without
utilization of new functions:
PCS 7 V9.0
Manual Software update with utilization Describes the procedure for the software update of PCS 7
of new functions projects with utilization of new functions.
● Original version of the existing project:
PCS 7 as of V8.0 or higher.
● Project to be updated to the following version with
utilization of new functions:
PCS 7 V9.0
Additional documentation for the software update

Additional information from the following documentation is required for carrying out the
software update:
Manual Process Control System PCS 7; Ensuring the availability of a PCS 7 System; contains infor‐
Service Support and Diagnostics mation on creating backups and how to perform firmware
updates.
Manual Process Control System PCS 7 PCS 7 PC - Hardware and Installation;
PCS 7 PC Configuration Windows settings and tools;
Software packages and required license keys.
Configuration manual Process Control Guide to configuration steps in SIMATIC Manager, CFC,
System PCS 7; Engineering System SFC, NetPro
Configuration manual Process Control Guide to configuration steps in WinCC
System PCS 7; Operator Station
Function manual Process Control Sys‐ Guide to configuration steps for High Availability process
tem PCS 7; High Availability Process control systems
Control Systems
Documentation All modules released for SIMATIC PCS 7 are listed together
Process Control System PCS 7; with the following information:
Released Modules ● Product designation
● Article number
● Firmware version
● Brief description
Online help Describes the updating of WinCC projects.
WinCC Information System
Process Control System PCS 7; Web Describes the installation and use of the Web Option for OS
Option for OS manual in PCS 7

Preface
Manual Process Control System PCS 7; Describes how an OPC A&E server with hierarchical access
OpenPCS 7 is used in PCS 7 systems
Function manual Process Control Sys‐ Describes the principles of use of high Availability (redun‐
tem PCS 7; High Availability Process dant) components in SIMATIC PCS 7.
Control Systems
SIMATIC manual S7 F/FH Automation Describes the configuration and programming of S7 F/FH
Systems failsafe systems using S7 F systems.
SIMATIC S7 F Systems Contains important information which must be taken into ac‐
count when installing and using the S7 F system optional
package in PCS 7.
Required basic knowledge

General knowledge in the area of automation engineering and basic knowledge of PCS 7 is
required to understand this documentation. You also need to know how to use PCs with
Windows operating systems.
The following documentation provides basic information on working with PCS 7:
● Configuration manual Process Control System PCS 7; Engineering System
● Configuration manual Process Control System PCS 7; Operator Station
● Getting Started Process Control System PCS 7; Part 1
Conventions
In this documentation, the names of elements in the software 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.
If you use the operating system Windows 10, you can find the Siemens SIMATIC programs in
the "Start" menu under All apps > Siemens Automation.
Changes compared with previous versions

Below, you will find an overview of the most important changes compared with previous
versions:
As of PCS 7 V9.0
● Adaptation to the Windows operating system.
● PCS 7 System ID
As of PCS 7 V8.2 or higher
● Updating block icons containing user customizations.

Introduction 3
3.1 Defining a strategy for the software update
Decision process
The selection and use of the correct documentation depends on the comprehensiveness of
your software update. the current status of the software and any boundary conditions that may
exist.
The figure below shows you the documentation you should use to update a PCS 7 plant.
,QWHUPHGLDWHVWHSVDUHUHTXLUHGIRUXSGDWLQJ\RXU
SURMHFW
'HSHQGLQJRQWKH3&6YHUVLRQRI\RXUSURMHFW
,V\RXUSURMHFWD3&6 1R \RXKDYHWRXSGDWHWKHHQJLQHHULQJV\VWHPDQG
9[SURMHFW"
WKHSURMHFW
7RGRWKLVXVHWKHPDQXDOVIRUWKH
VRIWZDUHXSGDWHRIWKHFRUUHVSRQGLQJ3&6
YHUVLRQ
<HV
'R\RXZDQWWRXVH 1R
WKHQHZIXQFWLRQVRI3&6
9"
'R\RXZDQWWRXSGDWH
DUHGXQGDQWV\VWHPGXULQJ
<HV RSHUDWLRQ"
<HV 1R
3UHVHQW
'RFXPHQWDWLRQ
0DQXDO6RIWZDUHXSGDWH 0DQXDOV6RIWZDUHXSGDWH 0DQXDO6RIWZDUHXSGDWH
ZLWKXWLOL]DWLRQRIQHZ ZLWKRXWXWLOL]DWLRQRIQHZ ZLWKRXWXWLOL]DWLRQRIQHZ
IXQFWLRQV IXQFWLRQV IXQFWLRQV
3&6963RUKLJKHUWR 3&6963RUKLJKHUWR 3&6963RUKLJKHUWR
9 9 9
PCS 7 High Availability Process
Control Systems*XLGHOLQHVIRU
XSGDWLQJDUHGXQGDQW23GXULQJ
RSHUDWLRQ
Note
Operating systems
Observe the requirements for the operating systems. You can find additional information on
this in the documentation Process Control System PCS 7; PCS 7 Readme (online).

Introduction
3.1 Defining a strategy for the software update
Note
Intermediate steps required for the software update
If you cannot directly upgrade to the current PCS 7 version of a PCS 7 project, the intermediate
steps are required. The steps described in the accompanying documentation must be
completed.
See also
General requirements (Page 15)

Introduction
3.2 General requirements
General requirements for updating the software

● Your PC hardware must meet the hardware requirements of the current PCS 7 version.
For additional information, refer to the documentation Process Control System PCS 7;
PCS 7 - Readme (online)
● The PC where the PCS 7 software is installed must meet one of the following requirements:
– It can access the PCS 7 software via a network (sharing of a network folder or DVD
drive).
– It has its "own" DVD drive (example: USB DVD drive).
Note
You must complete the software update before beginning with any additional changes
to the configuration.
● Only use the latest library versions for PCS 7 libraries

– PCS 7 Library V7.1 SP3 Update 4
– PCS 7 Advanced Process Library V8.0 SP2 Update 7
– PCS 7 Advanced Process Library V8.1 Update 5
– PCS 7 Advanced Process Library V8.2 SP1 Update 1
– PCS 7 Advanced Process Library V9.0
– PCS 7 Basis Library V8.0 SP1 Update 8
– PCS 7 Basis Library V8.1 SP1 Update 1
– PCS 7 Basis Library V8.2 Update 1
– PCS 7 Basis Library V9.0
Recommendation:
Check the compatibility of the library versions using the compatibility tool.
Note
If AS blocks from other PCS 7 versions are used in the project, it will be necessary to update
these blocks via a software update using new functions.
You can find the download files for setups of older versions of the PCS 7 Library, the
PCS 7 Basic Library or the PCS 7 Advanced Process Library on the Internet (https://
support.industry.siemens.com/cs/ww/en/view/109480136).
Checking the compatibility

Siemens offers a compatibility tool for automation and drive technology. You can find the
compatibility tool on the Internet: Compatibility tool (https://support.industry.siemens.com/cs/
ww/en/view/64847781).

Introduction
Asian text in PCS 7

In the following cases, you need a USB hardlock for your PCS 7 version:
● You want to install PCS 7 on an Asian operating system
● You want to install an Asian version of PCS 7
● You want to display Asian text in the user interface
The USB hardlock stores the license information you need to operate and configure your
version of PCS 7. Please contact your Siemens representative for information on the available
Asian language versions.
Note
A message indicates missing ASIA hardlock in a non-Asian project
Check the language of the operating system and PCS 7.
When language columns are configured for Asian text in a PCS 7 project and you do not need
this Asian text, you can delete these language columns from the text library of all OS projects.
It is then possible to operate with a license key for the PCS 7 version and without a USB
hardlock.

Introduction
3.3 Important Information for Software Update without Utilization of New Functions
3.3 Important Information for Software Update without Utilization of New

Functions
Requirements for Performing a Software Update

● PCS 7 can only run on operating systems that have been approved for PCS 7. You can
find information on approved operating systems in the Process Control System PCS 7;
PCS 7 Readme documentation (Internet version). This file contains additional information
pertaining to the operating systems and necessary service packs.
The Server operating system is required for the following PC stations:
– Server (redundant and non-redundant) for OS, SIMATIC BATCH, SIMATIC Route
Control
– Server for Web Option for OS
– Server for engineering station with multiproject (central data store) for engineering with
multiple engineering stations
● When the operating system is changed:
Ensure that the hardware of the PC stations is suitable for use with the updated PCS 7
version (e.g. operating systems, network adapter).
Read section "How to Check and Adapt the Connection Data in NetPro (Page 52)".
● The software update of password-protected projects requires SIMATIC Logon on an ES.
● For projects with activated FDA access protection for WinCC tag export, you have to open
the WinCC project in SIMATIC Manager beforehand.
● Ensure that your hardware meets the requirements for PCS 7. You can find more
information in the documentation Process Control System PCS 7 Catalog Overview;
Released Modules. If system components are not suitable for the updated version of PCS
7, you must replace them. In some cases, you must adapt or redo the configuration of the
components that have been replaced in the updated project.
● You need upgrade license keys to update PCS 7:
– V8.x -> V9.0
● The automation system can remain in the RUN state during a software update without
utilization of the new functions. The process can be continued. Program changes can be
downloaded during operation. Functions that require a new library version (for example,
SIMATIC Route Control) require a STOP of the automation system.
● The manual contains some sections that are not listed in the overview. Observe the
information provided in these sections when updating the software and check whether this
information is relevant to your PCS 7 system.
● You do not need any new hardware or firmware for your automation system.
● You want to perform the software update without a great deal of configuration effort.
● The process can always be operator-controlled and monitored, if you use redundant OS
servers and update the software accordingly.
You can find more information about this in the manual Process Control System PCS 7;
High Availability Process Control Systems > Guidelines for updating a redundant OS in
runtime.

Introduction
Note
Projects older than PCS 7 V8.0
If you are running an older PCS 7 (<V8.0) we recommend to update it to PCS 7 V8.2. Follow
the steps in the corresponding manuals.
Note
Archive server
The central archive server (CAS) is not supported. Replace the CAS with the following PC
stations:
● Process Historian as external archive server
● Information Server as reporting system
You can find information on configurations in the documentation Process Control System
PCS 7; PCS 7 PC Configuration.
You can find information on migration in the documentation SIMATIC; Process Historian;
Process Historian Administration.
Software update for Process Historian (PCS 7 V8.0 SP2)

If a Process Historian of version PCS 7 V8.0 SP2 is integrated in the project you wish to update,
updates must be installed on the Process Historian prior to the software update. Read the PH
documentation.
You can find additional information in this documentation and in the Process Historian
documentation:
● Installation manual SIMATIC; Process Historian Installation Notes
● System manual SIMATIC; Process Historian Administration, "Migration" section
Projects with add-on applications/products
Note
In some cases, add-on applications/products require intermediate steps. Read the relevant
documentation before starting the software update.
Downloading Changes
Note
Sequencers from SFC charts are not canceled during a software update, provided no changes
have been made within the sequencer.

Introduction
Libraries
As of PCS 7 V9.0, the libraries of PCS 7 are updated with each PCS 7 version. The following
libraries are installed by default:
● PCS 7 Basic Library
Contains the blocks of the PCS 7 Basic Library of PCS 7.
The PCS 7 Basic Library is a prerequisite for the use of the PCS 7 Library and the Advanced
Process Library.
● Advanced Process Library
Contains the blocks of the PCS 7 Advanced Process Library.
Note
Library required
Installation of additional PCS 7 libraries is required for the software update without utilization
of new functions.
You can find additional information on this in the section "Installation of Additional PCS 7
Libraries (Page 42)".
Utilization of new functions

New functions can be implemented by performing additional steps after the software update.
You can find information on this in the current manual Process Control System PCS 7; Software
update with utilization of new functions.
See also
Defining a strategy for the software update (Page 13)

Introduction
3.4 Information on Products from the PCS 7-Add On Catalog
3.4 Information on Products from the PCS 7-Add On Catalog
Important Information
If you have used PCS 7 add-on products (software packages or hardware components) in your
process control system, ask your SIMATIC PCS 7 contact for advice.

Introduction
3.5 Licensing with the Automation License Manager
Managing the License Keys

Both license keys and authorizations can be transferred using the Automation License
Manager. In the following, the term "license key" is always used even when a product uses
the old license scheme based on authorizations.
Different types of licenses are used in the Automation License Manager.
Each license consists of a basic license type and a license type.
Licensing levels
You can find an overview about licenses and configuration limits in the following documents:
● Catalog ST PCS 7 in the Internet via Technical Support (https://www.siemens.com/
automation/service)
● Documentation Process Control System PCS 7; Licenses and Configuration Limits (see
Preface: Options for accessing PCS 7 documentation)
Additional information
Online help for Automation License Manager

Introduction

Overview of the update tasks 4
4.1 Information about software update procedure
The following tables provide an overview of all of the necessary steps for updating software
without utilization of new functions.
Rules to Follow Based on the Tables

● Use these tables as guidelines for systematically carrying out all of the updating steps in a
sequence.
Note
The exact sequence of configuration steps specified in this documentation must be followed
in order to carry out the software update.
● You will receive information for every step as to where you must carry out the configuration
work.
● You can perform the full functional expansion of the PCS 7 project at a later point in time.

Overview of the update tasks
4.2 Overview of the procedure

The following is a general overview of the procedure for updating software. This document
contains comprehensive instructions on every step in the table below.
Note
You must complete the software update before beginning with any additional changes to the
configuration.
Recommendation:
Finish updating the engineering system and the project before you begin to update the other
PC stations.
Legend for overview

X - perform this step at the relevant stations
X1 - to be performed only for the central archive server
X2 - to be performed only for the Process Historians
Overview of the procedure
Step Action ES OS server OS client AS

Adaptations for central archiving
1 Migration of CAS databases to the Process Historian (Page 27) Only for projects with central archive
server (CAS)
Backing up the PCS 7 project to be updated
2 Backing up project data (Page 30) X
3 Backing up the libraries you created (Page 33) X
4 Exporting operator and display texts (Page 34) X
5 Checking the network adapter X X X
6 Backing Up the License Keys and Authorizations (Page 35) X X X
Installation and settings on the ES and OS
7 Updating PCS 7 (Page 38) X X X
8 Installing additional libraries (Page 42) X X X
General adaptations in the project
9 Updating the OS with the Project Migrator (Page 47) X
10 Checking the PH consistency (Page 48) X
11 Updating the hardware configuration (Page 48) X
(only applies in the current context to SIMATIC PCS 7 BOX RTX and
SIMATIC PCS 7 AS RTX)
12 Configuring the PDM server address (Page 49) X
Adaptations in NetPro and conversion of the CFC/SFC charts
13 Checking and adapting the connection data in NetPro (Page 52) X
14 Converting the CFC charts and SFC charts (Page 53) X

Step Action ES OS server OS client AS

Adaptation of OS-relevant settings
15 Synchronizing OS root screens, local computer actions and face‐ X
plates (Page 55)
16 Updating picture objects (Page 59) X
Adaptations for the Process Historian
17 Updating Process Historian and Information Server (Page 61) X
18 Replacing a central archive server with a Process Historian (Page 62) X
Adaptations for the Maintenance Station
19 Changing the OPC Server and adapting the SNMP configuration X
(Page 64)
20 Updating the diagnostics settings (Page 66) X
21 Updating the diagnostics screens (Page 67) X
Additional options
22 Updating PCS 7 Web Option for OS (Page 69) X X
23 Updating PCS 7 Components that Use SIMATIC Logon Services X X X
(Page 69)
Work for the OS in SIMATIC Manager
24 Compiling the OS (Page 70) X
Downloading to target systems
25 Downloading to target systems (Page 73) X X X X
For more information on the download options, refer to the Process
Control System PCS 7; Engineering Station Configuration Manual.
Activating operator stations
Sequence for activating process mode (Runtime):
● Process Historian (if available in the project)
● Master server (OS server)
● Standby server (redundant OS server)
● OS clients
26 Checking the settings on the OS servers (Page 76) X
27 Checking the settings on the OS clients (Page 77) X
SIMATIC BATCH software update
28 Updating SIMATIC BATCH stations (Page 79) Only for projects with SIMATIC BATCH
SIMATIC Route Control software update
29 Updating SIMATIC Route Control stations (Page 81) Only for projects with SIMATIC Route
Control
Migration of archive data from a central archive server (CAS)
30 Migrate the archives in the Process Historian (Page 83) Only for projects in which the central ar‐
chive server (CAS) has been replaced
with a Process Historian.


Preparing for the software update 5
5.1 Overview of the migration of CAS to the Process Historian
The Central Archive Server (CAS) is not released for PCS 7 V8.1 or higher.
Replace the CAS with a Process Historian.
The migration of archive data from a central archive server is possible with data stored with
PCS 7 V7.0 (StoragePlus V1.2) or higher.
If archive data is to be available after the software update, pay particular attention to the section
"How to Detach Attached Archive Segments on the Central Archive Server".
You can find information on this in this documentation and in the documentation on the Process
Historian:
● system manual SIMATIC; Process Historian Administration, "Migration" section
● Installation manual SIMATIC; Process Historian Installation Notes
5.1.1 How to Detach Attached Archive Segments on the Central Archive Server
Requirements
● Before you run the software update, perform these steps directly on the archive server
(Central Archive Server (CAS), or StoragePlus Server).
● You are authorized to access the Windows user interface on the CAS.
Procedure
1. In the Windows Start menu, select the "Administration Console" command from the
SIMATIC > StoragePlus submenu.
2. In the detail view, click "Detach".
The catalog of all linked archive segments which have already been swapped out is
displayed.
3. Select an archive segment you wish to remove from the archive.
4. Click "Open".
The selected archive segment is detached from the archive. Once the archive segment has
been detached from the archive, the archive segment is deleted from the hard disk of the
CAS. A message window shows whether the archive segment has been deleted.

Preparing for the software update
5. Click "OK".
6. Repeat steps 2 through 5 for all closed archives.
5.1.2 Migration of CAS to the Process Historian
Basic procedure
The following figure shows an example of the migration concept for a CAS (Central Archive
Server) database to the Process Historian in a PCS 7 environment.
(QJLQHHULQJ 5XQWLPH
26:LQ&&
(6
&$6
3&6bSURMHFW
26:LQ&&

3UHYLRXVYHUVLRQ
3&69 DVRI:LQ&&9
(6 26:LQ&& '%0LJUDWLRQ7RRO

3&6bSURMHFW 3URFHVV
+LVWRULDQ

26:LQ&&

Legend
1. Installation of a new PC station
Selection for PCS 7: Process Historian
You can find additional information on this in the documentation Process Historian;
Installation Notes.
2. Updating the software of the engineering station.
You can find information on this in the section "Installation of PCS 7 and settings on the ES
and OS (Page 37)".

3. Performing the software update for the PCS 7 project.

You can find information on this in the section "Adaptations in the PCS 7 project on the
ES (Page 45)".
4. Within the PCS 7 project:
Replace the CAS object in the PCS 7 project with a PH object.
You can find information on this in the section "How to replace the CAS with the PH
(Page 62)".
5. Stopping OS servers / OS single-station systems and updating the software.
6. Run "PH-Ready Configuration"
Note
Configuration of Process Historian Ready
The "CCCAPHService" must be configured on the updated OS servers/OS single-station
systems before process mode is activated.
You can find information about this in the documentation Process Historian; Installation
Notes, section 'Installing the Process Historian Ready component'
7. Restarting OS servers/single-station systems

The Process Historian must be operating in the "Active" state before the updated OS
servers are started for the first time. You can find additional information on this in the section
"How to Check the settings on the OS Servers (Page 76)".
Note
Note the start sequence for initial commissioning
Restart process mode for OS servers if necessary in order to establish the connection to
the Process Historian.
8. Starting the migration tool

You can find information on this in the section "How to migrate the archives in the Process
Historian (Page 84)".
The migration of all CAS databases is performed in the background during ongoing
operation.

5.2 Preparatory tasks
5.2.1 Overview of preparations
Note
You must perform the steps listed below prior to carrying out an update in order to prevent
data being lost.
It is essential that you back up your PCS 7 project before you start the software update.
Step Action ES OS serv‐ OS cli‐ AS

er ent
2 Backing up project data (Page 30) X
3 Backing up the libraries you created (Page 33) X
4 Exporting operator and display texts (Page 34) X
5 Checking the network adapter X X X
6 Backing Up the License Keys and Authorizations X X X
(Page 35)
Additional preparations
Note
Updating SIMATIC BATCH
If you want to use and update SIMATIC BATCH in the project, make sure to read the important
information in "Updating SIMATIC BATCH stations (Page 79)" in preparation for the update.
5.2.2 Exchanging data via OPC A&E

If you exchange data in the PCS 7 system by means of OPC A&E, observe the information in
the Process Control System PCS 7; OpenPCS 7 documentation when updating the software.
5.2.3 How to Back Up PCS 7 Project Data

Carry out the following instructions in order.

Requirements
Note
Before you install or update PCS 7, you must prepare and backup your original project so that
you can perform the software update.
NOTICE
Ensuring safe system configuration
If you want to perform a software update in runtime, you must ensure the following:
● All configurations are complete.
Keep this in mind especially when you apply the engineering with several engineering
stations (multi-engineering).
● All changes are loaded in the system.
Archiving a project
1. In SIMATIC Manager, select the menu command File > Archive.
The "Archive" dialog box opens.
2. Select the "Multiprojects" (or "User projects") tab.
3. Select the project from the list that you wish to archive.
4. Click "OK" to save your settings.
The "Archive - Select Archive" dialog box opens.
5. Make the settings for the drive and the folder for the archive file.
Recommendation:
Select a name for the project's archive file which indicates the date on which archiving took
place.
Example: "yearmonthdayprojectname"; 151230pcs7proj
6. Click "Save" to apply your settings.
The archiving process begins.
Note
The archived project reflects the state of the project before the software update.
Comparing Time Stamps

1. Open your PCS 7 project in SIMATIC Manager.
2. In the component view, select the chart folder of an AS.
3. Double-click on any chart.
The CFC editor opens.
4. Select the menu command CPU > Compare.

5. Compare the time stamps "Last compilation" and "Compilation of the loaded program".
If the time stamps are... … then

Identical 1. Click "Close".
The dialog box is closed.
Different 1. Select the menu command CPU > Download.
2. Select the "Changes" check box and apply all other standard
settings.
3. Click "OK".
Changes start to be downloaded.
4. If changes have been downloaded without errors, select the menu
command CPU > Compare.
The "Last offline program change" and "Last online program
change" time stamps must match up.
6. Perform steps 2 to 5 for each automation system.
Reading Back the AS Parameter Settings

If parameters which are not in the configuration have been set in the AS, you will be able to
read these settings back into the project.
CAUTION
Parameters will be overwritten
Please note that the parameters in the configuration will be overwritten. The decision
concerning whether to use this function will depend on the nature of the system involved and
must be made by the skilled personnel with responsibility for the system.
1. Open your PCS 7 project in SIMATIC Manager.

2. In the component view, select the chart folder of an AS.
3. Double-click on any chart.
The CFC editor opens.
4. Select the menu command Chart > Read Back.
5. Select the entries "Program on the CPU" and "Only data relevant for operator control and
monitoring" in the "Read Back" dialog box.
6. Click "OK".
The read-back process begins.
7. Perform steps 2 to 6 for the automation systems whose current parameters you require.
Backing Up OS Data
If you want to operate the OS server on a newly installed PC following the software update,
we recommend you back up the OS project of the OS server.
By default, the configuration data and the archive data of the OS are stored in the OS project
of the OS server.

To back up data, compress the project paths in this folder. Save the backup on a suitable
medium.
SIMATIC PDM
SIMATIC PDM configuration data is included automatically in the backup of a SIMATIC project.
SIMATIC PDM - Device descriptions

These PDM device descriptions are not included in the update installation of PCS 7. By default,
SIMATIC PDM installs the Siemens device descriptions.
● Make sure that the device descriptions utilized in the project are available for the integration.
To do this, create a list of the utilized device descriptions. You can save this list (menu
command Save device list as).
● Recommendation:
Back up the created device libraries with the Device Integration Manager using one of the
following actions:
– Copy
– Save as compressed archive
– Burn to DVD
5.2.4 How to Back Up User Created Libraries
Introduction
Generate a backup copy of any project library that contains a collection of user-specific blocks
for the project to be updated so that you can retrieve this data after having updated the
software. Carry out these steps for each library that you would like to back up.
Procedure
1. Start SIMATIC Manager.
No PCS 7 project must be open.
2. In SIMATIC Manager, select the menu command File > Archive.
The "Archiving" dialog box opens.
3. Open the "Libraries" tab.
4. Select the library to be backed up and click "OK".
The "Archiving - Select an Archive" dialog box opens.
5. Specify the file name and the storage path.
6. Click on the "Save" button.

● Online help for STEP 7
5.2.5 Operator and Display Texts in Blocks
Information in Faceplates
Faceplates visualize processes on the operator station and provide the plant operator with
information, such as:
● Measured values
● Operating limits
● Units
● Block operator texts
Change in Operator and Display Texts in Blocks

If you have modified the operator texts or display texts in the blocks so that they do not
correspond to the delivery state and you want to use the new PCS 7 blocks, you must back
up these "old" operator texts or display texts.
Diagnostic screens with project-specific adaptation

Back up diagnostics screens that have been adapted to a specific project.
Exporting Operator and Display Texts

In the SIMATIC Manager, you can export information from parameters, signals, and messages
to a file (in *.csv format).
You can edit this file in standard MS Office applications such as Excel and Access. The same
mechanisms are used for the export as are used for changeover to project-specific languages.
5.2.6 How to export operator and display texts
Requirement
● The required language is installed in your project.
Note
You can view the languages available in the project in SIMATIC Manager using the menu
command Options > Language for Display Devices. The number of available languages is
specified when Windows is installed (system characteristics).

Procedure
1. Open the project to be updated in the SIMATIC Manager.
2. Select the master data library folder in the Component View.
If this folder is not available, select the project folder.
3. Select the Options > Manage Multilingual Texts > Export menu command.
The "Export user texts" dialog opens.
4. Make the following settings:
– Select the storage location and format of the export file (*.xls or *.csv) in the "Text tables"
area.
– Select the target language and source language that correspond with the display
language in the "Language" area.
5. Click "OK".
6. If you have to manage several project-specific languages, repeat steps 3 to 5. Please note
that you then have to set different export file names or target directories.
5.2.7 Backing up pictures for user-defined status displays.

If prior to PCS 7 V8.1 you have used your own pictures when creating the status displays for
user-defined extended status displays, you should save these screens (EMF files) in a
separate folder.
Procedure
1. Open the "GraCS" folder in the OS project folder in Windows Explorer.
2. Create a folder for your own pictures.
3. Copy the pictures (EMF files) that are used into the newly created folder.
For more information on user-defined status displays, refer to the Process Control System
PCS 7; Operator Station manual.
5.2.8 Backing Up the License Keys and Authorizations
Introduction
You must backup the license keys/authorizations stored on your hard disks before changing
the operating system or using new PC stations.
Note
You can backup all License Keys to a License Key USB stick that is available as of PCS 7
V7.1 or higher. You must transfer the authorizations to a License Key disk/multi-authorization
disk.

Use the Automation License Manager for this purpose.

After installing the operating system, you can re-install the backed-up license keys using the
"Automation License Manager" program.
An upgrade of the license keys (Upgrade license key and PowerPack license key) is only
possible when the license keys to be updated are available on the corresponding PC station.
● Online help for Automation License Manager
● Online help for WinCC Information System > Authorizations

Installation of PCS 7 and settings on the ES and OS 6
6.1 Overview of Installation and Settings on the ES and OS

er ent
7 Updating PCS 7 (Page 38) X X X
8 Installing additional libraries (Page 42) X X X

Installation of PCS 7 and settings on the ES and OS
6.2 How to Update PCS 7
Requirements
● The PCS 7 project data is backed up.
You can find detailed information about how to back up project data in the Process Control
System PCS 7; Service Support and Diagnostics manual, section "Safeguarding
Availability, Data backup".
● The hardware planning and hardware update are complete.
● The necessary preparations have been made.
● The operating system of the PC station to be updated is updated.
You can find information on approved operating systems in the documentation Process
Control System PCS 7; PCS 7 Readme.
● Read the latest information in the documentation Process Control System PCS 7; PCS 7
Readme.
– Hardware and software requirements, installation
– If you use an INTEL network adapter, install the driver suitable for your device type and
operating system version.
You can find information on the drivers in the documentation Process Control System
PCS 7; PCS 7 - Readme.
– Information on the software for the automation system of SIMATIC PCS 7 BOX:
The software for time synchronization must be installed for an update of SIMATIC PCS
7 BOX and SIMATIC PCS 7 AS RTX.
Note
Software update of password-protected projects
The software update of password-protected projects requires SIMATIC Logon on an ES.
Note
Archive server
The central archive server (CAS) must be replaced with a Process Historian.
You can find information on migration in the section "How to replace the CAS with the PH
(Page 62)".
Note
Sequence for starting Process Historian and OS server
● The Process Historian should be available and in the state "active", before the OS servers
are activated the first time. Otherwise the OS Servers has to be restarted after PH is
available and "active".

SIMATIC PDM
Install SIMATIC PDM on the engineering station if using the Maintenance Station of PCS 7
and if the project contains intelligent field devices configured with SIMATIC PDM. The PDM
Server must be installed on the engineering station for the complete Asset Management
functionality.
Read the information and requirements in the readme for the current version of SIMATIC PDM.
Note
Installing SIMATIC PDM
If you are using a PDM version lower than V8.0 SP1 and want to perform an update installation,
uninstall the old PDM version before the installation.
Installing PCS 7
If you use the "Update" function in the PCS 7 setup, we recommend you reboot the PC before
performing the installation.
1. Insert the Process Control System; SIMATIC PCS 7 DVD into the DVD drive.
2. Select the "Update" setup type.
You can find a detailed description of how to install the required software in the Process
Control System PCS 7; PCS 7 PC Configuration documentation, in the section "How to
Install PCS 7 Software".
Note
During the installation, a message will appear several times prompting you to reboot your
PC. Reboot the PC. The installation then continues automatically.
Microsoft SQL Server

You can find information on the installed version of the Microsoft SQL Server required by PCS
7 in the documentation Process Control System PCS 7; PCS 7 Readme.
Recommendation:
If versions of the Microsoft SQL Server are installed on the PC and they are not required for
PCS 7 or specific purposes in the plant, you should remove this software after the update
installation of PCS 7. You can find the required menu command in the Control Panel.
Note that the following components belong to Microsoft SQL Server 2014:
● Microsoft SQL Server 2008 R2 Management Objects
● Microsoft SQL Server 2008 Setup Support Files
● Microsoft SQL Server 2012 Native Client
● Documentation Process Control System PCS 7; PCS 7 Readme (see "Preface (Page 9)")
● Manual Process Control System PCS 7; PCS 7 PC Configuration

6.3 How to enable encrypted communication between the PC stations
Changing the access protection of communication

Typical situations are:
● Software update of PC stations
● Switching to encrypted communication in non-redundant configurations
● Switching to encrypted communication in runtime in redundant configurations
● Changes to settings for encrypted communication in runtime (for example, changing a
password).
Note
Disruption of communication connections
Activation of the migration mode described below is only required if the communication
connections between the following PC stations must not be disrupted in any way:
● PC stations with access protection for communication
● PC stations without access protection for communication
Activation of the migration mode

If you want to change access protection for the communication in process mode of the plant,
you must adhere to the following sequence of actions:
Note
Change the access protection of communication in process mode of the plant.
This change is only possible for redundant PC stations in process mode of the plant.
Stop the process mode for each of the PC stations on which you currently want to perform the
change. For redundant PC stations, the partner station takes over process mode.
1. Temporarily enable the "migration mode" option for all PC stations for the next procedure.
2. Before activating encrypted communication without migration mode, evaluate the potential
impact.
NOTICE
Encrypted communication in a plant
Before you enable exclusive use of encrypted communication, you must ensure the
following:
● Migration mode must be enabled on all the required PC stations.
● The encrypted communication must be enabled on all the required PC stations.
3. Temporarily disable the "migration mode" option for all PC stations for the next procedure.

Using encrypted communication for a PC station

1. Select the "SIMATIC Shell" folder in the tree view of Windows Explorer on the PC station.
2. Select the "Settings..." command from the shortcut menu.
The "Communication Settings" dialog opens.
3. Enable the "Use encrypted communication" option.
The "Set PSK" dialog box opens.
Note
Changing the PSK
When the "Set PSK" option is enabled, you can change the PSK. Click the "Set" button.
Please note the documentation Process Control System PCS 7; PCS 7 PC Configuration;
section "How to change the PSK for encrypted communication".
4. Enter characters with a high password strength for the key.

The key must be at least 8 characters long and include numbers and symbols in addition
to uppercase/lowercase letters.
5. Confirm your entries. Click "OK".
6. If you want to use an available port instead of the port allocated by default, you can specify
the assignment of the incoming port.
7. Check the setting for the "Migration mode" check box.
Note
Please note the documentation Process Control System PCS 7; PCS 7 PC Configuration;
section "How to use migration mode when changing encrypted communication".
8. Click "OK".
● Please note the documentation Process Control System PCS 7; PCS 7 PC Configuration;
section "How to access PC stations outside a subnet".

6.4 Installation of Additional PCS 7 Libraries
6.4 Installation of Additional PCS 7 Libraries
Post-installing libraries used in the project

Depending on the blocks used, you have to post-install libraries and update the blocks used
in the project with the blocks of the following libraries:
● PCS 7 Basis Library
● PCS 7 Advanced Process Library (PCS 7 APL)
● PCS 7 Library
Download of setups for PCS 7 libraries

We strongly recommend to use the latest library versions for PCS 7 libraries.
You can find the download files for setups of older versions of the PCS 7 Library, the
PCS 7 Basis Library or the PCS 7 Advanced Process Library on the Internet (https://
support.industry.siemens.com/cs/ww/en/view/109480136).
PCS 7 faceplates of the PCS 7 library are contained in the project

● PCS 7 Library used
If you are using the PCS 7 Library in the project to be updated, you must install the PCS
7 Faceplates V7.1.3.1 on the following PC stations after the installation of PCS 7:
– Engineering station
– All operator stations (all types)
Basic Installation Procedure

The procedure is described in the section "How to install additional PCS 7 libraries (Page 43)".
An AS download without a stop is possible. You can find the basic procedure for this in the
Process Control System PCS 7; Engineering System configuration manual.

6.5 How to Install Additional PCS 7 Libraries
Note
Post-installing or removing PCS 7 libraries
If you install or remove an older version of the PCS 7 Library, PCS 7 Basis Library or PCS 7
Advanced Process Library after the installation of PCS 7, you must post-install the current PCS
7 version of the PCS 7 Basis Library. Install the required library by using the PCS 7 Setup.
This applies, for example, to PCS 7 libraries of older PCS 7 versions; see section "Installation
of Additional PCS 7 Libraries (Page 42)".
You can find the download files of the setups for PCS 7 libraries of older versions of the PCS
7 Library, the PCS 7 Basis Library and the PCS 7 Advanced Process Library on the Internet
(https://support.industry.siemens.com/cs/ww/en/view/109480136).
You can find information about the versions of the libraries (including updates) in the file
Process Control System PCS 7; PCS 7 Readme (online) (see "Preface (Page 9)").
Requirements
● The operating system including the required components is installed.
● PCS 7 has been installed.
● All applications are closed.
● The software needed for the required library is available, for example, on a shared drive in
the network.
Procedure
The following steps serve as an example.
1. Run the "SETUP" program.
2. Select a setup language.
3. Click "Next".
4. Follow the instructions of the setup wizard and then close the setup program.
5. After installing all the required libraries, you need to install the following libraries from the
latest Process Control System; SIMATIC PCS 7 DVD over them using the setup of PCS 7:
– PCS 7 Advanced Process Library (APL)
– PCS 7 Basic Library
Note
Installing the current library by means of the PCS 7 setup
The PCS 7 setup always installs the latest version of the library that is available on the
DVD.

You can find additional information on the libraries supplied with PCS 7 on the Internet.
● PCS 7 Basis Library Readme V9.0 (online)
● PCS 7 Advanced Process Library Readme V9.0 (online)
● PCS 7 Basic Faceplates Readme V9.0 (online)
● PCS 7 Library: LIB-Readme.wri file

Adaptations in the PCS 7 project on the ES 7
7.1 Updating a PCS 7 project
Basic procedure
This section describes how to update your PCS 7 project for use with SIMATIC PCS 7. The
PCS 7 project is updated on the ES in offline mode. Thus, system operation is not affected.
The target stations will only be loaded once all the update steps listed below have been
performed. For more information on downloading, refer to the Process Control System PCS
7; Engineering Station Configuration Manual.
Note
If you want to reuse existing projects without updating the automation system, you also need
to install the libraries of the existing project.
You can find additional information on this in the section "Installation of Additional PCS 7
Libraries (Page 42)".

Adaptations in the PCS 7 project on the ES
7.2 General adaptations
7.2.1 Overview of General Adaptations in the Project

er ent
7 Updating the OS with the Project Migrator (Page 47) X
8 Checking the PH consistency (Page 48) X
9 Updating the hardware configuration for the SIMATIC X
PCS 7 BOX and SIMATIC PCS 7 AS RTX (Page 48)
10 Configuring the PDM Server address (Page 49) X
(for projects with SIMATIC PDM V8.0 only)
7.2.2 Changing the Configuration of Multilingual Texts

If you want to use additional interface languages, please take note of the information below.
Changing Multilingual Texts

If you want to display text in more than one language in PCS 7 (for example, message texts
or OS area IDs), always use the export/import function to change the multilingual texts (menu
command Options > Manage Multilingual Texts > Export and then Import after the changes
have been made).
Note
If you change individual texts with the functions in CFC, SFC or PH, be sure to immediately
compile the texts in all locations (for example, all block types and all copies of a block).
Otherwise, inconsistencies may occur and lead to the display of an incorrect language version
of this text.
7.2.3 Importing Data from the User Archives
Import Runtime Data
Note
You must always import runtime data from the user archives in the language in which the
runtime data was exported.

7.2.4 How to update the configuration of the operator stations

If the configuration of an OS in a multiproject or project does not correspond to the installed
PCS 7 version, this is automatically detected in SIMATIC Manager as of PCS 7 V8.0 SP1 or
higher.
Requirements
● Only for password-protected projects:
Deactivate password protection for the following actions.
Procedure
Carry out the following steps for a given OS project:
1. Open your project/multiproject in the component view of SIMATIC Manager.
2. Select an OS project of your choice.
If required, the "Migrator" dialog window is opened by the system.
The message "Migration is required ..." is displayed.
3. Click "Yes".
Note
Declining migration
If you decline the migration, you cannot change the OS project or load it.
You can start the migration at any time. To do this, select the menu command Options >
Migrate OS projects.
4. Check the project language set in the "Migrator" dialog box. If necessary, set the project
language in which the project was created.
Recommendation:
No settings are required in the dialog box.
– If you clear the "Migrate database only..." check box, considerably more time will be
needed for the migration.
– The migration of the excluded components in process mode has no effect on process
mode.
5. Click "Next".
The configuration of all operator stations contained in the multiproject/project is performed.
Duration of the update process
Note
Depending on the scope, the update process can take several hours.

● Online help WinCC Information System > Migration
7.2.5 How to Check the Plant Hierarchy Consistency

This step shows you if all the data in the plant hierarchy is consistent.
Requirement
● The project in SIMATIC Manager is open in the plant view.
Procedure
The following steps can be performed for the multiproject or for each individual project (in the
multiproject).
1. In the tree view, select the object to be checked (e.g., the multiproject).
2. Select the Options > Plant Hierarchy > Check Consistency command.
The program checks the Plant hierarchy.
The "Check Consistency – Log" dialog box opens.
3. Correct any errors if inconsistencies are found.
Note
If you need information on the possible inconsistencies, click the "Help" button in the "Check
Consistency - Log" dialog box.
7.2.6 How to update the hardware configuration for SIMATIC PCS 7 BOX RTX and
SIMATIC PCS 7 AS RTX
The steps described below only have to be carried out for projects with SIMATIC PCS 7 BOX
RTX or SIMATIC PCS 7 AS RTX implementation.
Replacing the automation system in the hardware configuration of the PC station.
Requirements
● The AS version in HW Config is not up to date (Version 3.3 or older)
● The assignments of communication processors to the master systems are known.

Procedure
1. Open the HW Config of the PC station (SIMATIC PCS 7 BOX RTX or SIMATIC PCS 7 AS
RTX).
2. Select the PROFIBUS CP to which the distributed I/O is connected.
3. Select the Edit > Master system > Disconnect menu command.
4. Select the CP.
5. Select the menu command Edit > Delete.
6. Select the "Win LC RTX" CPU in the rack in HW Config.
7. Go to the "SIMATIC PC Station > Controller > Win LC RTX" folder in HW Config.
8. Double-click the object "V4.6".
The "Insert ..." dialog box opens.
9. Click "Yes".
The controller is replaced.
10.Go to the" SIMATIC PC Station > Controller > Win LC RTX > V4.6" folder in HW Config.
11.Select the PROFIBUS CP used (default: CP 5613).
12.Drag-and-drop the selected PROFIBUS CP to the controller slot in the station window.
The "Properties ..." dialog box opens.
13.Select the entry of the associated bus system from the "Subnet" list.
14.Click "OK".
The "Insert master system" dialog box opens.
15.Select the entry of the associated bus system from the "Subnet" list.
16.Click "OK".
17.Select the Station > Save and Compile menu command.
7.2.7 How to configure the SIMATIC PDM Server

This section only applies to plants with a maintenance station.

Requirements
● The project/multiproject has been created.
● The SIMATIC PDM (Server) software package is installed on the Engineering Station.
Note
Requirements for use of SIMATIC PDM
Observe the conditions for the use of SIMATIC PDM versions.
Information is available in the SIMATIC PDM Readme (online).
● Specifying the name of the PC station (computer name)

You can find information about this in the documentation Process Control System PCS 7;
PCS 7 - PC Configuration.
Note
The following names must be identical when you configure an OS or BATCH server and
an engineering station:
● Computer name
● Name of the PC station
Procedure
1. Select the Options > SIMATIC PDM > Settings command in SIMATIC Manager.
The "SIMATIC PDM settings" dialog box opens.
2. Select the "Maintenance Station" tab.
3. Go to the input field and enter the project/multiproject in which you have defined the MS
server or execute the following steps:
– In a multiproject:
Click "Current Multiproject" or "Browse." You can select the current project using the
"Browse" button.
– For a project:
Click on "Current Project" or "Browse." You can select the current project using the
"Browse" button.
4. Click "OK".
5. Open SIMATIC Manager in the component view.
6. In the project, select the engineering station in which you wish to insert the "PDM Server"
object.
7. Double-click the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station opens.
If you cannot see the hardware catalog, select the View > Catalog menu command.
The hardware catalog opens.
8. Select SIMATIC PC Station > PDM Server from the list in the folder.
9. Drag and drop the "PDM Server" object to the PC station of the engineering station.

10.Select the menu command File > Save.

11.Download the configuration to the engineering station.
Requirements for diagnostics with SIMATIC PDM

The following conditions must be met for diagnostics of PDM devices from any station (OS
client, maintenance server, etc.):
● The engineering station is accessible.
● SIMATIC PDM is active. (This is the default scenario after the configuration has been
downloaded.)
● STEP 7 and SIMATIC PDM Online Help
● Whitepaper SIMATIC; Security concept PCS 7 and WinCC - Main document

7.3 Adaptations in NetPro and conversion of the CFC/SFC charts

er ent
11 Checking and adapting the connection data in NetPro X
(Page 52)
12 Converting the CFC and SFC charts (Page 53) X
7.3.1 How to Check and Adapt the Connection Data in NetPro

In NetPro, you check the configuration to the target stations:
● Connection data
● Configuration data
Note
Operating system change
When you change the operating system, the network adapters may be detected in a different
order in the system. This is caused by the operating system.
Take this into consideration with systems with multiple network adapters and adapt the
configuration accordingly in HW Config.
Update the version of the communication components in the Station Configuration Editor and
HW Config.
Requirement
● The PCS 7 project is open on the ES.
Procedure
1. Select the PCS 7 project in SIMATIC Manager.
2. Select the menu command Options > Configure Network.
NetPro opens.
3. Select the menu command View > Cross-Project Network View.
The cross-project network view is displayed.
This allows you to toggle directly between all projects in the multiproject.

4. Check the connections to the various stations: AS-OS, AS-AS, ES-AS.

You can make any necessary changes when the "cross-project network view" is
deactivated.
You must configure the connection between the ES and AS if you want to check the
communication for process mode (runtime) on the ES. This requires the following steps to
be taken:
– Select the menu command New Connection in the shortcut menu of the WinCC
application.
– Select the destination: AS or OS.
– Select the connection.
– Select the name for the connection.
– Click "OK".
Recommendation
To enable you to easily identify the connections, we recommend that they be assigned
default names in accordance with the name of the target.
Example:
You configure an OS to AS_X connection.
The corresponding connection name could be "ASX_connection".
5. If you use time synchronization, you must check the time settings of the network adapters
(e.g. CP 1623) in the ES and OS. Double-click the network adapter of the OS/ES. Time-of-
day mode must be selected for time synchronization on the "Options" tab.
6. If you have made changes in NetPro, you must perform a "Save and Compile" operation
with the "Save and Compile All" option.
7.3.2 How to convert the CFCs and Shared Declarations
Requirement
● The PCS 7 project is open on the ES.
Converting CFC charts
Note
This procedure must be carried out for all S7 programs in your PCS 7 project.
1. Open a CFC chart and move any block it contains.

This change immediately start the conversion dialog.
2. Click "Yes".
The "Convert Format" message window opens.
3. Click “Yes".
4. Click "OK".

5. Execute a complete compilation of the S7 program.

6. Download changes to the automation system.
NOTICE
Updating a redundant OS in runtime
Updating according to the manual Process Control System PCS 7, High Availability
Process Control Systems; Guidelines for updating a redundant OS in runtime
If you update a redundant OS during operation, do not load the AS until phase 3 (in step
6 of the Process Control System PCS 7; High Availability Process Control Systems
manual).
Note
If you use SFCs in your project, please note that you need to update the SFC blocks.
Converting shared declarations

This procedure must be carried out for all projects in your PCS 7 multiproject.
Note
This procedure must be carried out for all projects in your PCS 7 multiproject.
1. Open the "Shared declarations" folder in the project.

2. Click these objects, e.g. Units (display them).
3. Make any necessary adjustments (e.g. create new unit).
The change starts the conversion dialog immediately.
Note
Beside CFCs, the "Shared Declarations" has to be migrated also.
SFC Readme

7.4 Adaptation of OS-relevant settings
7.4.1 Overview of Adaptation of OS-relevant Settings

er ent
15 Synchronize OS basic pictures, local computer actions, X
and faceplates (Page 55)
16 Updating picture objects (Page 59) X
User interface and design

After the software update, the design of the user interface for process mode must be set to
the following:
WinCC 3D
This setting is available automatically in projects created as of PCS 7 V8.0 or higher.
Other designs are not approved for PCS 7.
You need to check or change this setting for existing projects.
● Ensure that all projects in a plant have uniform settings for the design.
● If you change the setting for the WinCC design, check the appearance of objects you have
created yourself and adapt them if necessary.
7.4.2 Synchronization of OS Basic Pictures, Local Computer Actions and Faceplates

You have to transfer OS basic pictures and local computer actions to your project. The
faceplates of the project can continue to be used.
Synchronization in the OS Project Editor

You perform this procedure with the OS project editor, which is included in WinCC Explorer.
7.4.3 How to Synchronize OS Basic Pictures, Local Computer Actions, and Faceplates
Perform the following steps for the projects of each operator station (server and clients).

Requirements
● The operator stations contained in the PCS 7 project have been updated with the Project
Migrator.
● The PCS 7 OS is open in WinCC Explorer.
Procedure
1. Select the OS Project Editor and select the menu command Open in the shortcut menu.
2. Select the "Complete configuration" check box on the "General" tab.
3. Click the "Layout" tab.
4. Select the required layout and the monitor configuration.
5. Click the "Basic Data" tab. Make the required settings in accordance with the "Basic Data"
table below.
6. Only carry out this step if the "For observation only" authorization level must be activated
for some users after the software has been updated.
Select the "Message Display" tab.
Activate the required message filters (see the "Message Filters" table below).
Note
No settings are necessary for the software update on the remaining tabs. The default
settings can be applied.
7. Click "OK".

Basic Data
Dialog Area Note Action

Top left This window lists all basic pictures having a differ‐ None.
window ent product version and project version change The root screens marked with a red "X" cannot be
date. deselected.
Every basic picture with a selected check box is
overwritten in the project version at the start of the
OS Project Editor with the pictures from the prod‐
uct version.
Top right This window lists all local computer actions having None.
window a different product version and project version The root screens marked with a red "X" cannot be
change date. deselected.
Every local computer action with a selected check
box is overwritten in the project version at the start
of the OS Project Editor with the corresponding
local computer action from the product version.
Bottom left This window lists all faceplates having a different ● If you want to replace the faceplates available in
window product version and project version change date. the project with those of the relevant product
version, select the corresponding check box. The
settings provided by the product will then be
applied.
● If you have made project-specific customizations
to the color ranges of the faceplates of the
Advanced Process Library and do not want to
reset them, make sure that the "Update palette
colors of Advanced Process Library" check box
is not selected. (default setting).
● If you want to restore the default, select the check
box "Update palette colors of Advanced Process
Library".
Note
Projects prior to PCS 7 V8.1
In PCS 7 V8.1 or higher, the Dynamic Wizard has been changed because of the AS-granular
structure types.
Ensure that the "Update Dynamic Wizard Scripts" check box is selected.

Message Filters
Parameters Meaning
Messages that The message windows have two message lists.
can be acknowl‐ One list shows all messages from the area for which the user has access rights for all "operator process
edged in a sepa‐ controls". The user can acknowledge messages in this list.
rate list
The other list shows all messages from the area for which the user has an "authorization for area" but no
access rights for "operator process controls". The user cannot acknowledge messages in this list.
The message line in the overview area only shows messages that can be acknowledged with the access
right for "operator process controls".
Messages that Both of the message pages indicated above are available to the user. Only messages from areas for
can be acknowl‐ which the user has access rights for "operator process controls" are displayed on the message page with
edged on a sepa‐ only one list and in the message line of the overview area.
rate page
(switch-selecta‐
ble)
● Online help WinCC Information System > Options > Options for Process Control > OS
Project Editor
● Online help OS Project Editor
7.4.4 Mixed operation and visualization of AS blocks from different PCS 7 versions
Definition of Mixed Operation

Mixed operation is the visualization of AS blocks from different PCS 7 versions on one OS
client.
Compatibility of the PCS 7 faceplates

The APL faceplates of PCS 7 V9.0 can be used to monitor and control APL blocks of compatible
PCS 7 versions.
You can find additional information about this in the section "General requirements (Page 15)";
General requirements for updating the software
Rules
Process pictures can visualize the signals that AS blocks receive from different APL library
versions.

The same block icons for AS blocks from different library versions can be shown in the process
pictures of an OS. If an OS is assigned to several AS, only AS blocks of the following versions
of the Advanced Process Library can be configured for each AS:
● AS blocks from PCS 7 V8.x
● AS blocks from PCS 7 V9.0
The block icons are inserted into the process pictures when the OS is compiled. The standard
picture "@PCS7TypicalsAPLV8.pdl" serves as template for creating/updating the block icons
of all AS in the process pictures.
7.4.5 How to Update the Picture Objects
Introduction
If you have manually inserted and interconnected picture objects from a template picture into
a process picture, you must manually update these picture objects.
When the picture objects are updated, the block icons of the previous PCS 7 version are
replaced with the block icons of the current PCS 7 version.
You have to use the corresponding template picture that you used for configuration to update
the picture objects.
Recommendation: Perform the update one by one with each template picture of the library
used.
● For block icons of the PCS 7 library:
"@Template.pdl" or "@@PCS7Typicals.pdl"
● For APL block icons
- "@PCS7TypicalsAPLV8.pdl"
- "@TemplateAPLV8.pdl"
Only the block icons of the selected template picture are updated.
Requirements
● The operator stations contained in the PCS 7 project have been updated with the Project
Migrator.
● All basic pictures are replaced with the OS Project Editor.
● Read the following section in the Process Control System PCS 7; Operator Station
configuration manual; section "Rules for using multiple template files".

Procedure
1. Open any WinCC picture containing a picture object in the Graphics Designer. Select the
picture object.
2. In the dynamic wizard, open the "Picture Functions" tab and select "Update Picture
Objects".
This "Dynamic Wizard" dialog opens.
3. Click "Next".
4. Select the "Yes, all pictures" check box.
5. Click "Next".
6. Select the template in the list which has been configured with the picture objects of the OS.
(Default:@Template.pdl)
7. Select the default "TemplateControl.cfg" configuration file in the "Please specify name of
configuration file" field.
8. Click "Next".
9. Click "Finish".
Generation of the picture objects is initiated in the Dynamic Wizard.

7.5 Adaptations for the Process Historian
7.5.1 Adaptations for the Process Historian at a glance

er ent
17 Updating Process Historian and Information Server X
(Page 61)
18 Replacing a central archive server with a Process X
Historian (Page 62)
7.5.2 How to update the Process Historian and Information Server

You must update the following PC stations, if they were present in the PCS 7 project before
the software update:
● Process Historian
You can find information on this in the SIMATIC HMI; Process Historian system manual.
NOTICE
Upgrading Process Historian before the OS servers in runtime
You must first upgrade the Process Historian server to Process Historian as of PCS 7
V9.0 before you
● upgrade a PCS 7 plant to version PCS 7 V9.0 in runtime
● and simultaneously upgrade the operating systems of the OS servers, e.g. Server 2008
to Server 2012
● or replace the hardware of the OS servers
You can only start upgrading the OS servers in runtime when the Process Historian is
in the "Active" operating state and all pending restores have been executed.
Start the restore operation multiple times, if necessary, if you still detect data gaps.
You can start the restore operation manually in the management console or with the
PH tray icon.
● Information Server
You can find information on this in the SIMATIC HMI; SIMATIC Information Server system
manual

7.5.3 How to replace the CAS with the PH
Requirements
● The Process Historian is installed.
● The Process Historian is configured according to the guidelines specific to the plant (new
PC station in the workgroup/domain - network addresses, user etc.).
● The software of the engineering station is updated.
● The PCS 7 project is updated.
Procedure
1. Open the SIMATIC Manager on the engineering station.
2. Open the PCS 7 project in the component view.
3. Do the following in the component view of SIMATIC Manager:
– If the CAS station is located in a separate project in the multiproject:
Select the project of the CAS station.
Select Multiproject - Remove from multiproject from the shortcut menu.
The CAS station is removed from the multiproject.
– If the CAS station is located in a project with other stations:
In the component view of SIMATIC Manager, select the PC station with the "CAS" role.
Select Delete from the shortcut menu. Click "Yes".
The CAS station is removed from the project.
4. Perform the following sequence of tasks for all OSs in the multiproject that have stored data
on the CAS (OS servers and single-station systems):
– Open the "Backup Configuration" tab in the "Properties" dialog of the PC station.
– Clear the "Backup enabled" check box for the following options:
- Tag Logging > Archive configuration > Tag Logging Fast
- Tag Logging > Archive configuration > Tag Logging Slow
- Alarm Logging > Archive configuration > Message archive
Note
CAS backup configuration
If there is no longer a CAS computer in the project but the destination paths are entered,
a process control error is generated at each segment transition.

5. Perform the following sequence of tasks for all operator stations in the multiproject that
have a CAS assignment:
– Select the OS project in the component view of the SIMATIC Manager on the PC station.
– Select the menu command Options > OS > Assign OS Server....
The "Assign OS Server ..." dialog box opens.
– In the list of OS servers, check the following:
Make sure that the check box for the OS server with the data you want to visualize on
this operating station is selected.
– Clear the check box for the PC station of the CAS.
6. Create a new PC station for the Process Historian in the project.
7. Configure a new PC station for the Process Historian.
You can find additional information about this in the documentation Process Control System
PCS 7; Engineering System.
Save and compile the configuration.
8. Set the properties in the SIMATIC Manager. For this purpose, select the Process Historian's
PC station and then select the shortcut menu command Object properties.
9. Enter the computer name in the "Computer name" group or activate the "Computer name
identical to PC station name" check box.
10.Click "OK".
The "Properties" dialog box closes.

7.6 Adaptations for the Maintenance Station
7.6.1 Overview of the Maintenance Station update

Perform additional steps for updating an MS server.

er ent
19 Changing the OPC Server and adapting the SNMP X
configuration (Page 64)
20 Updating the diagnostics settings (Page 66) X
21 Updating the diagnostics screens (Page 67) X
Note
SNMP tag export (export entire plant configuration) has to be executed during the update of
the PCS 7 software to V9.0.
7.6.2 How to change the OPC Server, adapt the SNMP configuration and update
SIMATIC PDM
OPC Server version

The following section provides information on updating the version of the OPC server.
● The OPC server version to be used is V8.2.
● Replace the OPC server if necessary.
Requirements
● The blocks, charts and OS pictures of the project are updated.
● The SIMATIC programs and OS are compiled.
● The PC stations of the Maintenance Station (MS Server and MS Client) are updated in a
similar way to an OS.
● MS single station system
– An OPC server is configured on the PC station of the MS single station system.

● MS multiple station system

– In a system with redundant MS Servers, you configured an OPC Server both for the PC
Station of the MS Server and for the PC Station of the redundant partner.
● Lifebeat monitoring is disabled
If you use the Maintenance Station in the project, lifebeat monitoring must be disabled.
Procedure
1. Select the PC station in the Component View.
– In an MS multiple station system, this is the PC Station of the MS Server or of the
redundant partner.
– In an MS single station system, this is the PC Station of the MS single station system.
2. Double-click the "Configuration" object in the detail view to open HW Config.
The hardware configuration of the SIMATIC PC station opens.
If you cannot see the hardware catalog, select the View > Catalog menu command.
The hardware catalog opens.
3. Select the current version of the OPC Server from the hardware catalog at SIMATIC PC
Station > User application > OPC Server and drag-and-drop it to the position of the OPC
Server.
4. Click "OK" to confirm the replacement of the OPC Server.
5. Save and compile your changes.
6. Select the "OPC Server" object in the rack.
7. Select the menu command Station > Properties.
8. Open the "SNMP" tab.
9. Click the "Export Tags for WinCC" button.
10.Select the Station > Save and Compile menu command.
11.Repeat steps 1 to 5 if using the MS Server in a redundant MS multiple station system.
Updating SIMATIC PDM

Perform the following actions if the project contains field devices that were configured in
SIMATIC PDM:
1. Select the Options > SIMATIC PDM > Settings command in SIMATIC Manager.
The "SIMATIC PDM settings" dialog box opens.
2. Select the "Maintenance Station" tab.
3. Enter the file path of the PCS 7 project.
4. Click "OK".
Install SIMATIC PDM from the Process Control System; SIMATIC PCS 7 DVD. Refer to the
PDM Readme.

When you open a project in SIMATIC Manager, the SIMATIC PDM-related project data is
updated automatically.
Note
Updating SIMATIC PDM up to V9.1
During the update of projects with SIMATIC PDM up to V8.0, new PLT IDs are assigned to the
configured ASSETMON objects. Then, perform the following steps:
● Adapt these PLT IDs to the corresponding ASSETMON block instances.
● Compile the automation systems.
● Create the diagnostics screens again.
● Compile the corresponding operator stations.
7.6.3 How to update the diagnostics settings
Introduction
If you operate a PCS 7 Maintenance Station in your project, various settings must be migrated
when upgrading to the current PCS 7 version.
Requirement
Note
If the project was retrieved
If the project was retrieved to update the software, additional steps are necessary when you
use a Maintenance Station:
1. Compile the hardware configurations of all automation systems.
2. Compile all automation systems with the option "Update module drivers".
Procedure
1. Select the multiproject in the plant hierarchy.
2. Select the Options > Plant Hierarchy > Settings... menu command.
The "Customize Plant Hierarchy" dialog opens.

3. Select the "Migrate diagnostic settings" check box.

Note
This field is grayed out if this action is not required.
4. Click "OK".
Note
If you want to restore the project-specific changes, you have to adapt the automatically
created overview screen. After the "Migrate diagnostic settings" function, copy the project-
specific changes from the renamed overview screen of the project that is to be updated to
the current overview screen.
7.6.4 How to update the diagnostics screens

Updating the diagnostics screens has the following effects:
● Pictures in the AS objects area
Block icons that represent racks will be repositioned in the picture.
You can move the block icons to different positions.
● Pictures in the PC Stations and network objects area
The block icons will possibly overlap in these pictures.
You can move the block icons to different positions.
Requirements
● The OS Project Editor was executed. It is not necessary to make any settings in the OS
project editor.
● A backup copy of the diagnostics screens with project-specific adaptations has been
generated.
● An asset ID has been assigned to each AS and PC station in HW Config.
● Diagnostics settings are updated.
Procedure
1. Select the multiproject (project) in the plant hierarchy.
2. Select the Options > Plant Hierarchy > Create/Update Diagnostics Screens menu
command.
Update the diagnostics screens. You can find information on this in the Process Control
System PCS 7; Operator Station Configuration Manual.
3. Compile the OS of the Maintenance Station.
4. Update the server data of the MS server.
5. Download the MS server.

For information on options for accessing maintenance functions, refer to the following
documentation:
● You can find an explanation of how to work with the maintenance station in process mode
in the Process Control System PCS 7; OS Process Control function manual.
● Function manual Process Control System PCS 7; Maintenance Station

7.7 Additional options
7.7 Additional options
7.7.1 Overview of additional options

er ent
22 Updating the PCS 7 Web Option for OS (Page 69) X X
23 Updating PCS 7 Components that Use SIMATIC Logon X X X
Services (Page 69)
7.7.2 Updating the PCS 7 Web Option for OS
Requirement
In order to utilize the full functional scope of the PCS 7 Web Option for OS, you may only use
blocks from the current PCS 7 library in the PCS 7 project.
Procedure
● You update the OS Web server, an OS client, similar to an OS client.
● The process pictures that will be opened on a Web client must be "published" again.
For more information, refer to the Process Control System PCS 7; Web Option for OS Manual.
7.7.3 Updating PCS 7 Components that Use SIMATIC Logon Services
● Refer to the respective components that use SIMATIC Logon to find detailed instructions
about the setup, configuration and changes needed for SIMATIC Logon.
● You can find basic, generally applicable information about SIMATIC Logon in the online
help for SIMATIC Logon.

7.8 Work for the OS in SIMATIC Manager
7.8.1 Overview of compiling

er ent
24 Compiling the OS (Page 70) X
7.8.2 How to Compile the OS
Requirements
● The PC station has been configured.
● The configuration in CFC and SFC has been completed.
Note
If you have changed unit and operator texts of the block types in the master data library,
be sure to set your default language as the "Language for display devices".
Procedure
Note
You can find additional information about the compilation options in the configuration manual
Process Control System PCS 7; Engineering Station.
1. Select the object (multiproject, project, station) in SIMATIC Manager that you wish to
compile or compile/download.
2. Select the PLC > Compile and download objects command in SIMATIC Manager.
The "Compile and download objects" dialog box opens.
3. Open the tree structure.
4. Activate the check box in the "Compile" column for all objects that you want to compile.
5. Click the "Operating State" button and check the operating states of your objects (RUN,
activated, etc.) so that you can make the correct settings for compilation.
6. Select the OS that you wish to compile.
7. Click "Edit".
The "Settings: Compile OS ... Areas ..." dialog box opens.

8. Click "Next".
The "Settings: Compile OS ... Network Connections ..." dialog box opens.
9. Click "Next".
The "Settings: Compile OS ... Compilation Data and Scope of Compilation" dialog box
opens.
10.In the "Scope" group, activate the "Entire OS" and "With memory reset" check boxes.
11.Click "Apply".
Note
Once you have completed your settings for compiling an operator station, please wait until
the compilation settings have been saved and the download dialog box appears.
12.Make the required settings for the individual objects.

13.Click "Help" in the dialog box for detailed information about the settings.
14.Click the "Start" button.
Compilation starts.
15.Follow the instructions on the screen.
16.If you wish to see a log of the compilation once it is complete, click the following buttons in
the "Display Log" area:
– "Single object": The detailed compilation log of the selected OS is displayed.
– "All": Displays the results of all compilations (without details).


Downloading to target systems 8
8.1 Downloading to target systems
Once you have updated your PCS 7 project offline, you must download the changes to the
target systems.
NOTICE
Updating a redundant OS in runtime
Updating a redundant OS during operation (according to the manual Process Control System
PCS 7, High Availability Process Control Systems; Guidelines for updating a redundant OS
in runtime)
If you update a redundant OS during operation, do not load the AS until phase 3 (in step 6 of
the High Availability Process Control Systems manual).
Requirement
● The network addresses and network settings of the PC stations are configured.
● The configuration of the PC stations match in HW Config and in the Station Configuration
Editor.
● The PC station has been configured.
● The configuration and connection data of all stations has been downloaded via NetPro.
Procedure
1. Use the search box in the start menu to open "Set PG-PC Station".
2. Check the setting of the access points on each PC station (locally).
3. You can successively download all target systems systematically and automatically.
In the SIMATIC Manager, select the menu command Target system > Compile and
Download Objects.
You can find additional information about this in the Process Control System PCS 7;
Engineering System manual.

Downloading to target systems
8.1 Downloading to target systems

Activating operator stations 9
9.1 Overview of activating the operator stations
Introduction
Sequence for activating process mode (Runtime):
● Process Historian (if available in the project)
● Master server (OS server)
● Standby server (redundant OS server)
● OS clients

er ent
26 Checking the settings of the OS Servers (Page 76) X
27 Checking the settings on the OS Clients (Page 77) X

9.2 How to Check the settings on the OS Servers
9.2 How to Check the settings on the OS Servers
Introduction
Before activating the projects downloaded to the various OS servers, you need to check some
of the settings in each OS.
Requirements
● The following applies if a Process Historian is in the project:
– The Process Historian has the "Active" status.
– The "PH-Ready Configuration" is performed on each OS server.
Procedure
1. Open the "Redundancy" editor in WinCC Explorer.
2. Check all settings.
3. Click "OK".
4. Open the "Time Synchronization" editor in WinCC Explorer.
5. Check all of the settings in the dialog box.
6. Click "OK".
7. Repeat steps 1 through 6 for the second OS server and all other redundant OS servers.
Note
If you have installed a new operating system or have changed the settings, restart the
computer.
8. Activate process mode (runtime) on the OS servers.
Note
Process Historian
After activating process mode, the OS server automatically connects to the Process Historian.
● For non-redundant systems, the data is sent to Process Historian starting with the activation
of the process mode.
● For redundant systems, only data from the current master is sent to the Process Historian.
You can now import data segments created before the software update using Process Data
Migrator on the Process Historian.
You can find information on this in the section "How to migrate the archives in the Process
Historian (Page 84)".

9.3 How to Check the settings on the OS Clients

Before activating the projects loaded on the various OS clients, you need to check some of
the settings on each OS.
Requirement
Procedure
1. Open the "Time Synchronization" editor in WinCC Explorer.
2. Check all settings.
3. Click "OK".
4. Repeat steps 1 through 3 for the other OS clients.
5. Activate process mode on the OS clients.


Updating SIMATIC BATCH stations 10
Information on updating SIMATIC BATCH is available in the following documentation:
● Manual Process Control System PCS 7; SIMATIC BATCH
● SIMATIC BATCH Readme; Part B, Installation
Note
Note the following when updating the software to PCS 7 V9.0 (with SIMATIC BATCH):
● No batches should be actively running, because the BATCH database is restored from a
backup for the software update.
● Set the BATCH Start Coordinator to "Manual" start mode before you update the software.
It is essential that you observe these points when you prepare the software update. You can
find additional information on this in the section "Overview of preparations (Page 30)".

Updating SIMATIC BATCH stations

Updating SIMATIC Route Control stations 11
You can find information about this in the Process Control System PCS 7; SIMATIC Route
Control documentation.
Note
Library of SIMATIC Route Control V9.0
You should apply the library of SIMATIC Route Control V9.0 for SIMATIC Route Control V9.0.
The automation system must be in STOP in order to load these libraries.

Updating SIMATIC Route Control stations

Migration of archive data from a central archive server
(CAS) 12
12.1 Archive migration at a glance

er ent
30 Migrating archive data from the CAS (Page 84) Only for projects in which the central
archive server (CAS) has been re‐
placed with a Process Historian.
Reporting system for archive data

The Information Server is the reporting system for the Process Historian. Report templates
and automatic logs from archives must be created again.

12.2 How to migrate the archives in the Process Historian
Requirements
● The CAS databases were created with a central archive server as of PCS 7 V7.0 (Storage
Plus V1.2 )
● The archive data was swapped out with a PCS 7 version (Storage Plus V1.2) >= V7.0.
● The Process Historian is created and configured in the PCS 7 project.
● The Process Historian was started before the OS servers.
● The database of the central archive server is accessible from the Process Historian.
● The OS servers are in process mode. The connection to the Process Historian has been
established.
● The current data is archived on the Process Historian.
Archives on OS servers
The last archive segments of the OS servers are no longer swapped out to the CAS by the
OS servers. You must import these archives directly from the OS servers in the Process
Historian.
Keep in mind that this import must happen rather timely, depending on the setting of the OS
server circulating archives.
Recommendation: Start by importing those archive segments of the OS servers that were not
swapped out to the CAS.
Procedure for the import of CAS segments

1. On the CAS, configure sharing for access to CAS archives for the Process Historian.
2. Configure a network drive for access to CAS archives on the Process Historian.
3. Start the migration tool. Follow the instructions.
You can find detailed information on this in the documentation SIMATIC; Process Historian;
4. Select the CAS database of the server.
5. Assign the data to the subproject.
6. Start the migration process.
Note
All CAS databases are migrated in the background during operation.
You must perform the data migration for each OS subproject.

You can find detailed information on this in the documentation SIMATIC; Process Historian;


Index
Installation and Settings, 37
ES and OS, 37
A
Adaptations
Basic pictures and local reactions of the
L
computer, 55 Library
Archive server Backing up user-created libraries, 33
Adapting Archives, 84 Installing additional libraries, 43
CAS, 27 License key, 21
Detaching archive segments, 27 Licensing with the Automation License Manager, 21
B M
Backup, 30 Migrating diagnostics settings, 66
Mixed operation, 58
C
Central archiving
O
Adaptations, 27 Operating principle, 69
Changing the Configuration of Multilingual Texts, 46 PCS 7 Web Option for OS, 69
Checking and adapting connection data in Operation and display texts
NetPro, 52 Exporting, 34
Checking Plant hierarchy consistency, 48 Operator texts or display texts, 34
Compiling the OS, 70 OS
Converting CFC/SFC charts, 53 Checking the settings on OS clients, 77
Checking the settings on OS servers, 76
Overview of compiling, 70
D Overview of the activation, 75
Updating with the Project Migrator, 47
Documentation
User Interface in Process Mode, 55
Access options, 10
Overview
for planning and configuration, 10
Adaptation of OS-relevant settings, 55
Adaptation on operator stations, 55
Adaptations in NetPro, 52
E Converting CFCs/SFCs, 52
Exporting General adaptations in the project, 46
Operation and display texts, 34 Software update procedure, 24
Overview of activating the operator stations, 75
Overview of additional options, 69
I Overview of downloading, 73
Import Runtime Data, 46
Importing Data from the User Archives, 46
Information on software update, 17
P
Installation Password protection, 47
PCS 7, 38 Preparing for the software update, 30
SIMATIC PDM, 39 Process Historian
Adapting Archives, 84

Index
Project Migrator
Password protection, 47
R
Requirements, 15
Runtime data, 46
S
Selecting the Correct Documentation, 13
StoragePlus
Detaching archive segments, 27
Overview of Adaptations, 27
U
Updating
BATCH, 79
OS with Project Migrator, 47
PCS 7 components that use SIMATIC Logon
services, 69
PCS 7 project, 45
Updating PCS 7, 38
User Interface in Process Mode, 55
W
Web Option for OS, 69
WinCC 3D design, 55


Software Update Without Using New Functions

Uploaded by

Software Update Without Using New Functions

Uploaded by

Security information 1

Activating operator stations 9

Update by keeping the installed PLC blocks libraries

Siemens AG A5E36200133-AA Copyright © Siemens AG 2017.

Software update without utilization of new functions

7.2.3 Importing Data from the User Archives..................................................................................46

Software update without utilization of new functions

Software update without utilization of new functions

Software update without utilization of new functions

Software update without utilization of new functions

Software update without utilization of new functions

Scope of the documentation

Software update without utilization of new functions

Options for accessing PCS 7 documentation

● PCS 7 System Documentation

Software update without utilization of new functions

Documentation for the software update

Additional documentation for the software update

Software update without utilization of new functions

Required basic knowledge

Changes compared with previous versions

Software update without utilization of new functions

Software update without utilization of new functions

Software update without utilization of new functions

3.2 General requirements

General requirements for updating the software

● Only use the latest library versions for PCS 7 libraries

Checking the compatibility

Software update without utilization of new functions

Asian text in PCS 7

Software update without utilization of new functions

3.3 Important Information for Software Update without Utilization of New

Requirements for Performing a Software Update

Software update without utilization of new functions

Software update for Process Historian (PCS 7 V8.0 SP2)

Projects with add-on applications/products

Software update without utilization of new functions

Utilization of new functions

Software update without utilization of new functions

3.4 Information on Products from the PCS 7-Add On Catalog

Software update without utilization of new functions

3.5 Licensing with the Automation License Manager

Managing the License Keys

Software update without utilization of new functions

Software update without utilization of new functions

Rules to Follow Based on the Tables

Software update without utilization of new functions

4.2 Overview of the procedure

Legend for overview

Overview of the procedure

Step Action ES OS server OS client AS

Software update without utilization of new functions

Step Action ES OS server OS client AS

Software update without utilization of new functions

Software update without utilization of new functions

Software update without utilization of new functions

5.1.2 Migration of CAS to the Process Historian

Software update without utilization of new functions

3. Performing the software update for the PCS 7 project.

7. Restarting OS servers/single-station systems

8. Starting the migration tool

Software update without utilization of new functions

5.2 Preparatory tasks

5.2.1 Overview of preparations

Overview of the procedure

Step Action ES OS serv‐ OS cli‐ AS

5.2.2 Exchanging data via OPC A&E

5.2.3 How to Back Up PCS 7 Project Data

Software update without utilization of new functions

Comparing Time Stamps

Software update without utilization of new functions

If the time stamps are... … then

6. Perform steps 2 to 5 for each automation system.

Reading Back the AS Parameter Settings

1. Open your PCS 7 project in SIMATIC Manager.

Software update without utilization of new functions