Вы находитесь на странице: 1из 293

System 800xA

5.0 SP2 to 6.0 Upgrade


System Version 6.0
System 800xA
5.0 SP2 to 6.0 Upgrade

System Version 6.0

Document Number: 2PAA111695-600


Document Revision: G
Release: November 2017
NOTICE
This document contains information about one or more ABB products and may include a description
of or a reference to one or more standards that may be generally relevant to the ABB products. The
presence of any such description of a standard or reference to a standard is not a representation that
all of the ABB products referenced in this document support all of the features of the described or
referenced standard. In order to determine the specific features supported by a particular ABB product,
the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property
in the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as
a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate
information and data via a secure network. It is the sole responsibility of the system/product owner to
provide and continuously ensure a secure connection between the product and the system network
and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not
limited to, the installation of firewalls, application of authentication measures, encryption of data,
installation of antivirus programs, and so on, to protect the system, its products and networks, against
security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or
information.
ABB verifies the function of released products and updates. However system/product owners are
ultimately responsible to ensure that any system update (including but not limited to code changes,
configuration file changes, third-party software updates or patches, hardware change out, and so on)
is compatible with the security measures implemented. The system/product owners must verify that
the system and associated products function as expected in the environment they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of
any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or
consequential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from
ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized
purpose.
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license. This product meets the
requirements specified in EMC Directive 2014/30/EU and in Low Voltage Directive 2014/35/EU.

TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2004-2017 by ABB.
All rights reserved.
Table of Contents

Table of Contents

1 About this User Manual


1.1 Version Described in this User Manual .................................................................... 13
1.2 User Manual Conventions ........................................................................................ 13
1.3 Warning, Caution, Information, and Tip Icons ......................................................... 14
1.4 Terminology ............................................................................................................. 14
1.5 Related Documentation ............................................................................................ 15

2 Introduction
2.1 Virus Scanning Configuration During Installation and Post Installation ................. 18
2.2 Planning for the Upgrade ......................................................................................... 18
2.3 Supported Operating Systems ................................................................................. 20
2.4 Precautions ............................................................................................................... 20
2.5 System Language Package ....................................................................................... 21
2.6 Footprint Reduction during Upgrade ....................................................................... 21
2.7 Online Upgrade ........................................................................................................ 22

3 Considerations and Upgrade Flow


3.1 Considerations .......................................................................................................... 25
3.2 Upgrade .................................................................................................................... 28
3.3 Online Upgrade Flow ............................................................................................... 29
3.3.1 Preparing System 800xA 5.0 SP2 .............................................................. 29
3.3.2 Preparing and Setting Up System 800xA 6.0 ........................................... 31
3.4 Offline Upgrade Flow .............................................................................................. 51
3.4.1 Preparing the 800xA 5.0 SP2 System ........................................................ 51
3.4.2 Preparing the 800xA 6.0 System (Offline Upgrade) ................................. 53
3.4.3 Setting Up 800xA 6.0 System ................................................................... 57

2PAA111695-600 G 5
Table of Contents

4 Pre-Upgrade Procedures
4.1 Pre-Upgrade Procedure Steps ................................................................................... 67
4.2 System-Wide Pre-Upgrade Procedures .................................................................... 67
4.2.1 Configure IPSec ...................................................................................... 68
4.2.2 Consistency Check .................................................................................... 69
4.2.3 Migrating Visual Basic Process Graphics Aspects to Process Graphics
Aspects ....................................................................................................... 72
4.2.4 Faceplates .................................................................................................. 72
4.2.5 Record the Number of Aspects and Objects .............................................. 73
4.3 Pre-upgrade Procedures before Maintenance Backup .............................................. 74
4.3.1 Batch Management .................................................................................... 75
4.3.2 Customized Alarm Priority Mapping Aspects ........................................... 76
4.3.3 800xA for AC 800M ................................................................................. 76
4.3.4 Engineering Studio ................................................................................... 78
4.3.5 Device Types in System 800xA ................................................................. 80
4.3.6 Device Management FOUNDATION Fieldbus ........................................ 80
4.3.7 PROFINET IO Feature Pack 1.2 ............................................................... 80
4.3.8 800xA for Advant Master and 800xA for Safeguard ............................... 81
4.3.9 800xA for AC 100 ..................................................................................... 82
4.3.10 800xA for DCI ........................................................................................... 83
4.3.11 800xA for Harmony ................................................................................... 83
4.3.12 800xA for AC 870P/Melody .................................................................... 84
4.3.13 800xA for MOD 300 ................................................................................. 85
4.3.14 IEC 61850 Connect ................................................................................... 86
4.3.15 Freelance Connect ..................................................................................... 87
4.3.16 PLC Connect .............................................................................................. 87
4.3.17 Asset Optimization .................................................................................... 87
4.3.18 PC, Network and Software Monitoring ..................................................... 91
4.3.19 PC, Network and Software Monitoring Device Library ............................ 92
4.3.20 SMS and e-mail Messaging ....................................................................... 92
4.3.21 Information Management .......................................................................... 93
4.3.22 Application Scheduler and Calculation Server .......................................... 96
4.3.23 800xA History ........................................................................................... 96

6 2PAA111695-600 G
Table of Contents

4.3.24 Process Engineering Tool Integration ........................................................ 97


4.4 System 800xA Maintenance Backup ....................................................................... 97
4.5 Pre-Upgrade Procedures for Local Data Backup ..................................................... 98
4.5.1 800xA for AC 800M ................................................................................. 98
4.5.2 Information Management .......................................................................... 99
4.5.3 Basic History Service Data ........................................................................ 103

5 Post-Upgrade Procedures
5.1 Post-Upgrade Procedure Steps ................................................................................. 105
5.2 Compare the Number of Aspects and Objects ......................................................... 106
5.3 Reconfigure Aspects Created By System Extensions .............................................. 108
5.4 Configure Hot key for the New Find Tool ............................................................... 110
5.5 Correct Alarm and Lock Indication in Faceplates .................................................... 110
5.6 IEC 61850 Connect ................................................................................................. 111
5.6.1 Upgrade CET Project ................................................................................. 111
5.7 Customized Alarm Priority Mapping Aspects ......................................................... 114
5.8 Reconfigure Group Displays .................................................................................... 114
5.9 Configuring Alarm Property Server Service ............................................................ 114
5.10 Device Management and Fieldbuses ........................................................................ 115
5.10.1 Restore Device Types ................................................................................ 116
5.10.2 Device Management PROFIBUS & HART ............................................. 122
5.10.3 License Count Tool .................................................................................... 125
5.10.4 Device Management FOUNDATION Fieldbus ...................................... 127
5.11 PROFINET IO Feature Pack 1.2 .............................................................................. 130
5.12 800xA for Advant Master and 800xA for Safeguard .............................................. 130
5.12.1 Copy the Advant Master Controller Licenses.txt ...................................... 130
5.12.2 Update the Configuration Files .................................................................. 131
5.12.3 Copy the DATHR Files .............................................................................. 131
5.12.4 Reconfigure RTA Board Control Aspect Settings .................................... 131
5.13 800xA for AC 100 .................................................................................................... 132
5.13.1 Configuration and Operation ..................................................................... 133
5.13.2 Time Synchronization and Daylight Saving Time ..................................... 133
5.13.3 Installation Verification (Optional) ............................................................ 134

2PAA111695-600 G 7
Table of Contents

5.13.4 Product Verification ................................................................................... 137


5.14 800xA for DCI ......................................................................................................... 139
5.14.1 Deleting Additional Control Network ....................................................... 139
5.14.2 Configure a Single NIC Interface to the DCU ........................................ 140
5.14.3 Enable DCI OPC AE Service Group(s) ..................................................... 141
5.15 800xA for Harmony ................................................................................................. 141
5.15.1 Harmony API Configuration ..................................................................... 141
5.15.2 Harmony Configuration Server Information ............................................. 142
5.15.3 Restart Connectivity Server ....................................................................... 143
5.16 800xA for AC 870P/Melody .................................................................................... 145
5.16.1 Restore 800xA for AC 870P/Melody Information .................................... 146
5.16.2 Additional 800xA for AC 870P/Melody Configuration Steps .................. 147
5.17 800xA for MOD 300 ................................................................................................ 147
5.18 PLC Connect ............................................................................................................ 148
5.18.1 Restoring the Pretreat dll ........................................................................... 148
5.18.2 Update the Sattbus Configuration .............................................................. 149
5.18.3 Redeploy the PLC Connect Configuration ................................................ 149
5.19 Asset Optimization ................................................................................................... 150
5.20 PC, Network and Software Monitoring .................................................................... 153
5.20.1 Restarting the Event Collector Service ...................................................... 153
5.20.2 Configure the Service Provider and Service Group .................................. 154
5.20.3 Migrate the IT Asset Monitors .................................................................. 155
5.21 PC, Network and Software Monitoring Device Library .......................................... 156
5.22 800xA for Harmony and AC 870P/Melody Connectivity Server Node Update ...... 157
5.22.1 Determining the Node Running ShadowOPC Server as AfwService ....... 158
5.22.2 Applying the Update .................................................................................. 158
5.23 SMS and e-mail Messaging ...................................................................................... 159
5.24 Batch Management ................................................................................................... 159
5.24.1 Activate Batch Redundancy ...................................................................... 159
5.24.2 Batch Management Post Installations ....................................................... 159
5.24.3 Shutdown Script ........................................................................................ 160
5.24.4 Batch Management Toolbar ....................................................................... 160
5.24.5 Set Date and Time for Batch Servers ........................................................ 160

8 2PAA111695-600 G
Table of Contents

5.25 Basic History Service ............................................................................................... 161


5.26 Information Management ......................................................................................... 162
5.26.1 Reconfiguring the IM Log Configuration ................................................ 163
5.26.2 Information Management History Backup/Restore Utility ....................... 163
5.26.3 Restoring Other Information Management Related Files .......................... 168
5.26.4 Starting PAS ............................................................................................... 169
5.26.5 Updating Archive Logs ............................................................................. 170
5.26.6 Information Management Maintenance ..................................................... 170
5.26.7 Running hsDBMaint -stagger .................................................................... 171
5.27 Desktop Trends ......................................................................................................... 172
5.28 Calculations Service ................................................................................................. 173
5.29 Scheduling Service (Application Scheduler) ........................................................... 173
5.30 800xA for AC 800M ................................................................................................ 174
5.30.1 Load 800xA for AC 800M High Integrity Extension ................................ 174
5.31 Control Builder M Projects ...................................................................................... 175
5.31.1 AC 800M Fingerprint Tool ........................................................................ 176
5.31.2 Start Values Analyzer Tool ........................................................................ 176
5.32 Engineering Studio ................................................................................................... 176
5.32.1 Convert Diagram References/Variables from Aspect Objects to Symbol
Objects ....................................................................................................... 177
5.32.2 Check and Repair AES Variable Table ...................................................... 177
5.32.3 Remove EBService Node from the Service Structure ............................... 177
5.32.4 Function Designer Diagram Upgrade ........................................................ 177
5.32.5 Conversion of Global Variables (Diagram Variables) into Communication
Variables .................................................................................................... 179
5.33 Process Engineering Tool Integration ...................................................................... 180
5.34 Add Autostart Shortcut ............................................................................................. 180
5.35 Online Upgrade of a Multisystem Integration System ............................................. 181
5.36 Load System Extensions .......................................................................................... 181
5.37 Changing Aspect Precedence List ............................................................................ 183
5.38 System Backup ......................................................................................................... 184
5.39 Consistency Check ................................................................................................... 184

2PAA111695-600 G 9
Table of Contents

Appendix A Migrate Redundant Domain Controllers


A.1 Prerequisites ............................................................................................................. 187
A.2 Preparation ............................................................................................................... 188
A.2.1 Preparing a Domain for Windows Server 2012 / Windows Server 2016 ... 188
A.3 Removing the Redundant Domain Controller .......................................................... 189
A.4 Installing an Additional Windows Server 2012 / Windows Server 2016 Domain
Controller ................................................................................................................ 190
A.5 Transferring the FSMO Roles to the Secondary Domain Controller ....................... 193
A.5.1 Transferring the Schema Master Role ....................................................... 193
A.5.2 Transferring the Domain Naming Master Role ......................................... 195
A.5.3 Transferring the RID Master, PDC Emulator, and Infrastructure Master
Roles .......................................................................................................... 196
A.6 Removing the Remaining Windows Server 2003 Domain Controller ..................... 198
A.7 Installing an Additional Windows Server 2012 / Windows Server 2016 Domain
Controller ................................................................................................................. 199
A.8 Required 800xA Software ........................................................................................ 199

Appendix B Troubleshooting
B.1 Errors and Warnings during Upgrade ....................................................................... 201
B.1.1 Failed to Serialize Aspect .......................................................................... 201
B.1.2 ASO Object Class xxxx ............................................................................. 201
B.1.3 UnplacedObjects.afw ................................................................................. 202
B.1.4 The System Cannot Find the Path Specified ............................................. 202
B.1.5 System Extension ´xxxx´ with ID ´Guid` is not Installed on this Node .....203
B.1.6 Timeout by External Service ..................................................................... 203
B.1.7 Graphic Aspect = xxx Cannot be Imported ............................................... 204
B.1.8 Too Many Aspects of Category ................................................................. 204
B.1.9 Aspect Category is Missing ....................................................................... 205
B.1.10 Unknown Transaction Error ...................................................................... 205
B.1.11 Import/Export Error ................................................................................... 206
B.2 Troubleshooting during Deploy ............................................................................... 207

10 2PAA111695-600 G
Table of Contents

Appendix C Control Builder M Compatibility Check


C.1 800xA 5.0 SP2 to 800xA 6.0 Compatibility Issues .................................................. 213

Appendix D Online Upgrade Controller Level


D.1 Online Upgrade Controller Level ............................................................................. 215
D.2 Flowchart for Upgrading Controller Level .............................................................. 217
D.3 Flowchart for Extending Controller Level ............................................................... 218

Appendix E 800xA for Harmony Online Upgrade


E.1 Prerequisites ............................................................................................................ 219
E.2 Node Order .............................................................................................................. 219
E.3 800xA for Harmony Upgrade Procedure ................................................................. 220

Appendix F 800xA 6.0 Service Group and Service Provider


Names
F.1 ABB 800xA for MOD 300 ....................................................................................... 231
F.1.1 800xA for MOD 300 Batch ...................................................................... 234
F.1.2 Renaming MOD 300 AE Service Group and Service Provider Names ..... 235
F.2 ABB 800xA for DCI ................................................................................................ 235
F.3 800xA for AC 800M ................................................................................................ 240
F.4 ABB Asset Optimization .......................................................................................... 243
F.5 ABB PC, Network and Software Monitoring .......................................................... 243

Appendix G Identifying Node Functions and System Functions


G.1 Collecting Data from Existing System 800xA 5.0 SP2 ............................................ 245
G.2 Node Functions and System Functions .................................................................... 247
G.3 Definitions ................................................................................................................ 248
G.3.1 System Functions ....................................................................................... 249
G.3.2 Node Types ................................................................................................ 249
G.3.3 Node Functions .......................................................................................... 249
G.3.4 Options ...................................................................................................... 249
G.4 Identifying System Functions ................................................................................... 249
G.4.1 Planning System Functions ....................................................................... 254

2PAA111695-600 G 11
Table of Contents

G.5 Identifying Node Functions ...................................................................................... 255


G.5.1 Planning Node Functions ........................................................................... 262

Appendix H Footprint Reduction during Upgrade


H.1 Introduction .............................................................................................................. 265
H.2 Example .................................................................................................................... 265
H.3 Considerations ......................................................................................................... 266
H.4 Source System Workflow ......................................................................................... 267
H.4.1 Preparing the 800xA 5.0 SP2 System ........................................................ 267
H.5 Target System Workflow .......................................................................................... 269
H.6 Node Function Configuration ................................................................................... 277
H.6.1 OPC Server for AC 800M ......................................................................... 278
H.6.2 PLC Connect and Softpoint ....................................................................... 278
H.6.3 PROFIBUS and HART .............................................................................. 279
H.6.4 Asset Optimization .................................................................................... 279
H.6.5 PC, Network and Software Monitoring ..................................................... 281
H.6.6 IEC 61850 Connect ................................................................................... 282
H.6.7 FOUNDATION Fieldbus Connectivity services ....................................... 283
H.6.8 Advant Master Connectivity Services ....................................................... 283
H.6.9 SMS and E-mail Messaging ...................................................................... 284
H.7 Remove Nodes ......................................................................................................... 285
H.8 Post Upgrade Procedures ......................................................................................... 285

Appendix I Revision History


I.1 Updates in Revision Index B .................................................................................... 287
I.2 Updates in Revision Index C .................................................................................... 288
I.3 Updates in Revision Index D ................................................................................... 288
I.4 Updates in Revision Index E .................................................................................... 288
I.5 Updates in Revision Index F .................................................................................... 288
I.6 Updates in Revision Index G ................................................................................... 289

INDEX

12 2PAA111695-600 G
1 About this User Manual 1.1 Version Described in this User Manual

1 About this User Manual

Any security measures described in this user manual, for example, for user access,
password security, network security, firewalls, virus protection, and so on, represent
possible steps that a user of an 800xA System may want to consider based on a
risk assessment for a particular application and installation. This risk assessment,
as well as the proper implementation, configuration, installation, operation,
administration, and maintenance of all relevant security related equipment,
software, and procedures, are the responsibility of the user of the 800xA System.
This user manual describes how to upgrade System 800xA 5.0 SP2 to 800xA 6.0
latest release.
This user manual does not include information on site planning, engineering planning,
software configuration, network design, security measures, tools, maintenance, and
so on that can be found in other 800xA user manuals.
Unless otherwise noted, the procedures described require Windows Administrator
privileges.

1.1 Version Described in this User Manual


Unless otherwise noted, the versions of all 800xA Base System and Functional Area
software being upgraded to in this user manual are the latest release of 800xA 6.0.

1.2 User Manual Conventions


Microsoft Windows conventions as defined in the Microsoft Manual of Style are
normally used for the standard presentation of material when entering text, key
sequences, prompts, messages, menu items, screen elements, and so on.

2PAA111695-600 G 13
1 About this User Manual 1.3 Warning, Caution, Information, and Tip I

1.3 Warning, Caution, Information, and Tip Icons


This user manual includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to point
out useful hints to the reader. The corresponding symbols should be interpreted as
follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.

Caution icon indicates important information or warning related to the concept


discussed in the text. It might indicate the presence of a hazard which could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function.
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that operation
of damaged equipment could, under certain operational conditions, result in degraded
process performance leading to personal injury or death. Therefore, fully comply with
all Warning and Caution notices.

1.4 Terminology
A complete and comprehensive list of terms is included in System 800xA Terminology
(3BSE038018*). The listing includes terms and definitions that apply to the 800xA
System where the usage is different from commonly accepted industry standard
definitions and definitions given in standard dictionaries such as Webster’s Dictionary

14 2PAA111695-600 G
1 About this User Manual 1.5 Related Documentation

of Computer Terms. Terms that uniquely apply to this instruction are listed in the
following table.
Table 1.1: Terminology

Term/Acronym Description
Backup 800xA Backup: Backup using the 800xA Backup Definition aspect.
Functional Area Backup: Backup through defined tools or copy of
Functional Area configuration and/or data to a safe media for items
not covered by 800xA Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance
(3BSE046784*) for same version to same version backup and restore.
Restore 800xA Restore: Restore through the Configuration Wizard.
Functional Area Restore: Restore through defined tools or copy of
Functional Area configuration and/or data from a safe media for items
not covered by 800xA Backup.
The specific operations called out for the Functional Area within the
Backup/Restore procedure in System 800xA Maintenance
(3BSE046784*) for same version to same version backup and restore.
Upgrade Moving from one 800xA release to a later 800xA release, whether it
be a major or minor release.
Update Adding revisions, feature packs, service packs, patches, hot fixes,
or rollups to an existing 800xA System.

1.5 Related Documentation


Refer to System 800xA Released User Documents (3BUA000263*) for a complete
list of all product documentation applicable to the 800xA System that are included
on the Release Notes/Documentation media provided with the system or available
from myABB/My Control System. This document is provided in PDF format and is
also included on the Release Notes/Documentation media. It is updated with each
release and a new file is provided.
The asterisk (*) appended to each document number is a wildcard character used
in place of the document revision. The wildcard allows searches in myABB/My
Control System to be independent of revision. All revisions of the document will
be displayed in the search result.

2PAA111695-600 G 15
16 2PAA111695-600 G
2 Introduction

2 Introduction

The latest version of this manual is available in myABB/My Control System.

This document reflects 800xA System and Functional Area software at the time
of release. All 800xA System and Functional Area Release Notes must be read
and understood before performing any upgrade procedures. The Release Notes
contain any last minute changes that must be performed when installing or
upgrading the 800xA System. All Release Notes can be found on the System
800xA media under the Release Notes folder.
Visual Basic Process Graphics (VBPG) is not supported beginnig System 800xA
6.0. It is mandatory to migrate all VBPG to PG2 graphics before performing the
upgrade. Plan for the migration in advance. During Upgrade all the VB PG graphics
elements, VB PG graphic displays contents will be cleaned up. Also the standard
VB graphics and AC 800M Classic library system extensions installed in the
system are unregistered and deleted.
This user manual describes the procedure to upgrade from the last revision of 800xA
5.0 SP2 to 800xA 6.0 latest release, using the supported tools provided by the System
Installer.
The following are the different phases of a system upgrade:
• Plan
• Prepare
• Upgrade
• Configure
For more details on each system upgrade phase along with the workflow, refer to
System 800xA Installation and Upgrade Getting Started (2PAA111708*).

2PAA111695-600 G 17
2 Introduction 2.1 Virus Scanning Configuration During Inst

2.1 Virus Scanning Configuration During Installation


and Post Installation
The user should make sure that the installation procedure completes without
exposing the computers to malware or malicious network traffic of any sort.
This can only be done by limiting the communication to the system and by
performing separate virus scanning of any portable media or disks before
connecting them to the system nodes during the installation. After completing the
system installation and configuration (post installation) it is recommended to
perform a full virus scan of all computers in the system.
For better performance during 800xA installation and post installation procedures
disable virus scanning software. For virus scanners recommended by ABB for use
with System 800xA refer to McAfee Integration and Symantec sections in System
800xA Installation and Upgrade Getting Started (2PAA111708*).

2.2 Planning for the Upgrade


Visual Basic Process Graphics (VBPG) is not supported beginnig System 800xA
6.0. It is mandatory to migrate all VBPG to PG2 graphics before performing the
upgrade. Plan for the migration in advance. During Upgrade all the VB PG graphics
elements, VB PG graphic displays contents will be cleaned up. Also the standard
VB graphics and AC 800M Classic library system extensions installed in the
system are unregistered and deleted.
Planning for the upgrade can save time and resources. The instruction in this user
manual are presented in sequential order; however, depending on the plant performing
the upgrade, some of the actions can be performed in advance or in parallel. For
example, the upgrade flows are written to reflect upgrading and using existing servers
and clients. If new servers and clients are being used, prepare those before beginning
the upgrade (load and configure the Windows Operating System, third party software,
and so on.), or while performing the pre-upgrade procedures.
For third party software prerequisites, refer to System 800xA Third Party Software
(3BUA000500). This document is accessible from myABB/My Control System.
The prerequisites depend on the system and node functions installed in the system.
For more details on supported operating systems and prerequisites, refer to Prerequisite
Section of System 800xA Installation and Upgrade Getting Started (2PAA111708*).

18 2PAA111695-600 G
2 Introduction 2.2 Planning for the Upgrade

The hardware specifications such as the memory size and the processor speed will
determine the system performance after a system upgrade. Refer to Certified products
for use with ABB System 800xA for a list of verified hardware.
1. 800xA Licensing: The license model enforces licensing for the 800xA Hardware
components including controllers and Communication Interfaces have changed
beginning with 800xA Version 6.0. Each installed 800xA Hardware component
requires a separate Hardware license.
ABB requires data from the existing system in order to generate the Hardware
license for each Hardware component. The data is collected by running the ABB
Control Hardware Report Tool (2PAA114472*) in the existing system before
upgrade. This tool is available in myABB/My Control System.
Refer to System 800xA Licensing Information (2PAA111691*) for information
on the Control Hardware Report Tool.
Order the 800xA licenses required for the latest system version to which its
intended to upgrade. The licenses from the previous system versions will not work.

The following considerations may vary depending on the system version being
upgraded and if the upgrade will be performed online or offline.
Concurrent access to the current 800xA System version and the 800xA 6.0 system
is recommended until the upgrade has been performed. This makes it possible
to easily retrieve any data or files that have been missed. Concurrent access
depends upon many different factors, including:
• Configuration of the existing system.
• Desired configuration of the 800xA 6.0 system.
• Server and client use strategy.
• Configuration of user and user groups.
• Use of service accounts.
• Domain controllers.
• Redundancy.
• Logical and physical networks.
One strategy is to leave a minimal part of the existing system intact, such
as an Aspect Server, while preparing a major part of the 800xA 6.0 System.
Another strategy is to prepare a minimal 800xA 6.0 System.

2PAA111695-600 G 19
2 Introduction 2.3 Supported Operating Systems

Retaining an Aspect Server from the existing system minimizes the time it
takes to retrieve data or files from it. A disk drive image provides a quick
way to recover, but often it requires no hardware upgrade. Try to delay the
upgrade of the hardware in one Aspect Server as long as possible.
It is highly recommended to retain the Aspect Directory node after taking the
maintenance backup on the 800xA 5.0 SP2 System. This will not only act as a
reference node post-upgrade, but will also ensure that the changes made to the
aspects created by the System Extensions can be reapplied in the new system, if
lost during an upgrade.
If it is not necessary to do the complete upgrade in one process, it may be
possible to perform the upgrade in steps by stopping selected system functions
or by stopping some parts of the plant, or a combination of the two.
2. Identify the device types used in the system. The latest version of the Device
Libraries are required during the upgrade. These files will be made available on
the System 800xA Installation media. Check for newer versions of the Device
Libraries in myABB/My Control System.

2.3 Supported Operating Systems


System 800xA runs only on 64-bit (x64) operating systems beginning System 800xA
6.0.
The supported operating systems, service packs, and hot fixes are listed in System
800xA Third Party Software (3BUA000500). This document can be found in
myABB/My Control System.
Server Operating System and Workstation Operating System will be used
throughout the remainder of this document.
The US English version of the operating system is required even if a translation NLS
package for System 800xA is used.
For more details on supported operating systems and prerequisites, refer to Prerequisite
Section of System 800xA Installation and Upgrade Getting Started (2PAA111708*).

2.4 Precautions
There are third party backup/restore and disk imaging utilities that are useful when
software or data becomes corrupted to the point that the node will no longer function

20 2PAA111695-600 G
2 Introduction 2.5 System Language Package

correctly. A limited number of hardware failures can also be compensated for by


using these utilities. However, it is important to understand the limitations and
ramifications associated with these utilities. In some cases (such as corrupted data,
corrupted software, or hard disk failures) these utilities can be useful while in other
cases (such as replacing a node) these utilities may be of limited use.
It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) an image of node hard disks after installation
of third party software and/or after installing all software.
The 800xA System import/export utility can be used to save 800xA System
information one portion at a time. However, the 800xA System backup utility is the
functional equivalent of exporting all 800xA System information at one time. The
critical difference between these utilities is that individually exported portions of
800xA System information can be imported back into the original system or into a
completely different system while backed up 800xA System information can only be
used to restore a specific system on specific nodes. The 800xA System allows for
scheduled 800xA System backups. Refer to System 800xA Maintenance
(3BSE046784*) for information on performing precautionary scheduled 800xA System
backups.

2.5 System Language Package


The 800xA System includes support for the default language, which is US English.
Translations of the operator interface (System 800xA Language Packages) are released
separately after the main release of the 800xA System. Upgrade of a system including
a Language Package requires an upgrade of the Language Package when it is released.
Refer to the Language Package release notes for information on upgrading a Language
Package to System 800xA 6.0.

2.6 Footprint Reduction during Upgrade


System 800xA makes better use of hadware than older system versions beginning
System 800xA Version 6.0. The hardware footprint reduction is acheived by
combinning multiple node functions on a single node. The movement of node functions
can be acheived during the upgrade process. Refer to Appendix H for performing
footprint reduction during upgrade.

2PAA111695-600 G 21
2 Introduction 2.7 Online Upgrade

2.7 Online Upgrade


Online Upgrade makes it possible to upgrade an existing 800xA System without a
process shutdown. Plant operations are not disturbed while upgrading server and
client software, including OCS connectivity services, and AC 800M Controllers
(processor units and communication interfaces (CI)). The 800xA System being
upgraded must have redundant Aspect and Connectivity Servers.
Online Upgrade Controller Level allows AC 800M controllers to be upgraded with
new firmware versions online. Online upgrade is initiated from Control Builder by a
nine-step wizard. Refer to 800xA Online upgrade and Co-existence, versions
compatibility (3BSE080447) in the myABB/My Control System for the supported
upgrade paths.
You can upgrade the connectivity services online. However, use the following
rules to upgrade the overall system.
It is required to maintain Time Synchronization among all the nodes during the
complete upgrade process.

The nodes are upgraded in the following order:


• Domain Controllers.
• One redundant Aspect Server.
• 800xA for AC 870P/Melody Configuration Server.
• One redundant Connectivity Server for each redundant Connectivity Server
configuration.
• Third Aspect Server (if 2oo3 redundancy).
• Some clients.
• IM Server.
• All other Application Servers (Batch, Asset Optimization, PC, Network and
Software Monitoring, and so on.).
• All other nodes except Primary Aspect Server.
• Primary Aspect Server.
The client and server level is upgraded and the plant is fully operable, although the
controllers are not upgraded. The controller level is upgraded as follows:
• Some redundant Controller pairs (and CEX units if needed).

22 2PAA111695-600 G
2 Introduction 2.7 Online Upgrade

• Remaining redundant Controller pairs (if desired).


• Nonredundant controllers (no CEX units). Upgrading nonredundant controllers
will require minimal plant downtime.
This instruction does not contain procedures for upgrading the AC 800M controller
level. Refer to Appendix D for a general description.
Perform the online upgrade procedures on 800xA for Harmony systems as given
in Appendix E.

2PAA111695-600 G 23
24 2PAA111695-600 G
3 Considerations and Upgrade F 3.1 Considerations

3 Considerations and Upgrade Flow

This topic describes the considerations to be taken before planning an upgrade of


System 800xA 5.0 SP2 to System 800xA 6.0 and the workflow for upgrading.

Figure 3.1: Upgrading System 800xA - Overview

3.1 Considerations
The following considerations must be taken into account before performing the
upgrade.
• Unless otherwise indicated, the person performing this upgrade must use the
same user account that was used during the installation of the 800xA System
software.
• To guarantee the functionality of the upgraded system, follow these instructions
carefully and perform them in a well defined order.
• It is recommended that a disk image be taken of all disks on each node before
beginning and after completing the upgrade.
• Backing up the aspect directory (800xA System Backup), reports, history data,
graphics, and other application data is required before performing the upgrade.

2PAA111695-600 G 25
3 Considerations and Upgrade F 3.1 Considerations

• Take an inventory of all software on all nodes in the 800xA System before
performing the upgrade.
• Many functions in System 800xA require the local clocks in the different system
nodes to be synchronized. How the time synchronization is best done differs
between systems.
Refer to System 800xA Network Configuration (3BSE034463*) that describes
number of different time synchronization schemes. Ensure proper time
synchronization scheme is in place before and after upgrade.
• Refer to the compatibility issues detailed in Appendix C before beginning the
upgrade.
Online upgrade and coexistence between different Controller versions is listed
in document 800xA Online upgrade and Co-existence, versions compatibility
(3BSE080447) available on myABB/My Control System.
• Visual Basic Process Graphics (VBPG) is not supported in System 800xA
beginning System 800xA 6.0. It is mandatory to migrate all VBPG to Process
Graphics 2 (PG2) before performing upgrade. Plan for the migration in advance.
During Upgrade all the VB PG graphics elements, VB PG graphic displays
contents will be cleaned up. Also the standard VB graphics and AC 800M Classic
library system extensions installed in the system are unregistered and deleted.
Refer to System 800xA Engineering Process Graphics Migration Tool
(3BSE049231*) available in myABB/My Control System.
The System 800xA VBPG Search Tool is used to find VBPG aspects in 800xA
system that need to be migrated prior to a system upgrade. The tool can also
identify PG2 and Faceplate aspects that have references to VBPG aspects. For
more information on the tool, refer to System 800xA VBPG migration and System
800xA VBPG Search Tool (3BSE081093).
All VBPG aspects Main View in System 800xA 6.0 and later will show a message:
This aspect is not supported and will not be available for operator actions.

Symbol Factory Controls are no longer installed with the standard ABB 800xA
installation. A separate installation (ABB 800xA Symbol Factory) is needed to
use the Symbol Factory Controls. The ABB 800xA Symbol Factory installation
package is available on the media. A separate license is required to use the ABB
800xA Symbol Factory Controls.

26 2PAA111695-600 G
3 Considerations and Upgrade F 3.1 Considerations

• If Foundation FIELDBUS is used in the system and if Visual Basic Graphics or


Faceplates are not used in the system, contact your local Support Organization
on how to do Online Upgrade.
• If 800xA History is used in the system, contact your local Support Organization
on how to do Upgrade.
• Perform the online upgrade procedures on 800xA for Harmony systems as given
in Appendix E.
• If Batch Management is installed and running, all batches must be in the complete
state (no running batches or active phases) before upgrade.
• If 800xA for Melody / AC 870P is used in System 800xA 5.0 SP2, the
Configuration Server database upgrade workflow to System 800xA 6.0 is a
two-step procedure, because of the incompatibility issues between the Microsoft
SQL Server versions on both the systems.
1. Upgrade Configuration Server database to System 800xA 5.1.
2. Upgrade Configuration Server database to System 800xA 6.0.
Contact your local Support Organization for more information.
• If IEC 61850 is used in System 800xA 5.0 SP2, upgrade of CET OPC Server
Project to System 800xA 6.0 is a two-step process.
1. Upgrade CET project from System 800xA 5.0 SP2 to 800xA 5.1.
2. Upgrade CET project from System 800xA 5.1 to System 800xA 6.0.
Contact your local Support Organization for more information.

2PAA111695-600 G 27
3 Considerations and Upgrade F 3.2 Upgrade

After upgrade, make sure not to index the following folders under any
circumstances, or the entire volume that contains them. These folders can exist
on one or more disks and should not be indexed on any of them.
• OperateITData: Runtime data from services is stored here.
• OperateITTemp: Runtime data for client processes is stored here.
• ProgramData: Various other runtime data is stored here.
• HsData, Oracle: Applies only for Information Management Servers.
• ABBIndustrialIT Data: User data is stored here.
Refer to Microsoft Windows help for more information on the Windows Search
Indexing feature and recommendations on types of folders to index and not to
index.

3.2 Upgrade
System 800xA supports Online upgrade and Offline upgrade. The detail workflow
is giving in the following sections.
Online Upgrade makes it possible to upgrade an existing 800xA System without a
process shutdown. Plant operations are not disturbed while upgrading server and
client software, including connectivity services, and AC 800M Controllers (processor
units and communication interfaces (CI)).
The 800xA System being upgraded online must have redundant Aspect and
Connectivity Servers, and redundant AC 800M Controllers consisting of two redundant
processing units connected to I/O modules either directly to the modulebus or using
various CI modules. The client and server level can be upgraded without upgrading
the controllers.
800xA Systems without redundant Aspect and Connectivity Servers require a
process shutdown and must be upgraded offline.

Redundancy is not supported for the Batch Management and Information


Management combined node type.
This instruction addresses only the client and server level software. It does not
provide detailed instruction for upgrading the controller level; however, a high
level discussion about the controller level appears in Appendix C.

28 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Perform the online upgrade procedures on 800xA for Harmony systems as given
in Appendix E.

3.3 Online Upgrade Flow


This section provides detailed information and procedures for doing an Online Upgrade
of an 800xA System. Refer to Online Upgrade for additional information and ideas
on how to streamline the upgrade process.
The topic is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the
current or upgraded system.
It is important to create backups of node hard disks (using a third party
backup/restore and/or disk imaging utility) and the 800xA System before starting
the upgrade procedures. Valid backups ensure that the system can be restored if
necessary.
Place the process in a low level of production where the likelihood of process
upsets is minimized.
Online Upgrade workflow is divided into following sections:
• Preparing System 800xA 5.0 SP2: The procedures for preparing System 800xA
5.0 SP2 involves system wide Pre-Upgrade steps that needs to be done before
upgrade. The node wise Pre-Upgrade procedures need to be executed during the
Online Upgrade of that specific node.
• Preparing and Setting Up System 800xA 6.0 (Online Upgrade): The procedures
for Online Upgrade covers the node order and the workflow to be followed across
the 800xA system.
• Configuring System 800xA 6.0: Perform the post upgrade procedures for different
node types as described in Post-Upgrade Procedures.

3.3.1 Preparing System 800xA 5.0 SP2


The procedures for preparing System 800xA 5.0 SP2 involves system wide
Pre-Upgrade steps that needs to be done before upgrade. The node wise Pre-Upgrade
procedures need to be executed during the Online Upgrade of that specific node.
The following are the system-wide Pre-Upgrade procedures:

2PAA111695-600 G 29
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

1. Document all Windows settings including the domain, DNS, policies, users, and
so on.
2. Collect the information about the System Functions, Node Functions and their
configurations from existing System 800xA 5.0 SP2. This information can be
obtained from existing plant documentation.
The information about existing System 800xA 5.0 SP2 must be used while
planning a similar System 800xA 6.0.
Diagnostics Collection Tool can also provide some information about existing
System 800xA 5.0 SP2. For more details, refer to Appendix G.
3. Migrate the existing Visual Basic Process Graphics (VBPG) aspects to the
corresponding Process Graphics 2 aspects. Refer to System 800xA Engineering
5.0 SP2 Process Graphics Migration Tool (3BSE049231*) available in
myABB/My Control System.
Visual Basic Process Graphics (VBPG) is not supported in System 800xA
beginning System 800xA 6.0. It is mandatory to migrate all VBPG to PG2 graphics
before performing upgrade.
The System 800xA VBPG Search Tool is used to find VBPG aspects in 800xA
system that need to be migrated prior to a system upgrade. The tool can also
identify PG2 aspects that have references to VBPG aspects. For more information
on the tool, refer to System 800xA VBPG migration and System 800xA VBPG
Search Tool (3BSE081093).
All VBPG aspects Main View in System 800xA 6.0 and later will show a message:
This aspect is not supported and will not be available for operator actions.

Symbol Factory Controls are no longer installed with the standard ABB 800xA
installation. A separate installation (ABB 800xA Symbol Factory) is needed to
use the Symbol Factory Controls. The ABB 800xA Symbol Factory installation
package is available on the media. A separate license is required to use the ABB
800xA Symbol Factory Controls.
4. The 800xA System and software require preparatory procedures before performing
the upgrade. These pre-upgrade procedures are dependent on the products installed
in existing 800xA System and are classified as:
a. System-wide Pre-Upgrade Procedures
b. Pre-upgrade Procedures before Maintenance Backup
c. System 800xA Maintenance Backup

30 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

d. Pre-upgrade Procedures for Local Data Backup


Perform the applicable procedures in the order presented in Pre-Upgrade
Procedures section before proceeding.
If performing an online upgrade, you must perform the pre-upgrade procedures
described in this section on a node-to-node basis. Refer to the Preparing and Setting
Up System 800xA 6.0 section to know the node order to be followed.
If performing an offline upgrade, save the data obtained during the pre-upgrade
procedures in node-specific folders.

3.3.2 Preparing and Setting Up System 800xA 6.0


This section details the node order and the corresponding steps for each node that
needs to be followed during an online upgrade procedure.
The nodes are upgraded in the following order for online upgrade of System 800xA:
• Domain Controllers.
• One redundant Aspect Server.
• 800xA for AC 870P/Melody Configuration Server.
• One redundant Connectivity Server for each redundant Connectivity Server
configuration.
• Third Aspect Server (if 2oo3 redundancy).
• Some clients.
• IM Server.
• All other Application Servers (Batch, Asset Optimization, PC, Network and
Software Monitoring, and so on.).
• All other nodes except Primary Aspect Server.
• Primary Aspect Server.
The client and server level is upgraded and the plant is fully operable, although the
controllers are not upgraded. The controller level is upgraded as follows:
• Some redundant Controller pairs (and CEX units if needed).
• Remaining redundant Controller pairs (if desired).

2PAA111695-600 G 31
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

• Nonredundant controllers (no CEX units). Upgrading nonredundant controllers


will require minimal plant downtime.
This instruction does not contain procedures for upgrading the AC 800M controller
level. Refer to Appendix D for a general description.
Perform the online upgrade procedures on 800xA for Harmony systems as given
in Appendix E.

Figure 3.2 shows a high level workflow of Online Upgrade.

32 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Figure 3.2: High level Workflow for Online Upgrade

2PAA111695-600 G 33
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Domain Controller Migration


Domain Controllers must be upgraded as the first step while upgrading the 800xA
System online. Refer to Appendix A for the steps to upgrade the Domain Controllers.
This step can be skipped if 800xA system is in a workgroup environment.
In case if the Aspect server is combined with a Domain Controller, only the
redundant Domain Controller should be upgraded first. The primary Aspect /
Domain Controller will be upgraded as the last step in the Online Upgrade Flow.
If you want to use IPSec functionality to secure 800xA system, it must be
configured for a migrated Domain Controller after upgrading to the 800xA 6.0
version. For information on configuring the IPSec settings, refer to System 800xA
Post Installation (2PAA111693*).

Redundant Aspect Server


The following are the procedure for upgrading redundant Aspect Servers.
1. Stop the redundant Aspect Server from the 800xA 5.0 SP2 System using the
Stop Server feature in the Configuration Wizard. This server can be a stand-alone
Aspect Server or it can be combined with a redundant Connectivity Server.
2. Remove the redundant Aspect Server from the 800xA 5.0 SP2 System using the
Remove Server feature in the Configuration Wizard. If working in a domain
this server needs to be removed from the Domain Controller. When this server
is upgraded it will become the Primary Aspect Server in the 800xA 6.0 System.
The other redundant Aspect Server, if running 2oo3 redundancy, will be removed
from the 800xA 5.0 SP2 System later.
3. Reformat the hard drive.
4. Install the new operating system defined for the 800xA 6.0 System.
5. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
6. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.

34 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
7. Launch System Configuration Console tool as the 800xA Installing User from
ABB Start Menu > ABB IndustrialIT > System.
8. Go to Create System task to create a System on the Primary Aspect Server node
and making the node ready for System deploy.
9. Go to Configure System task in SCC, plan the 800xA 6.0 System identical to
800xA 5.0 SP2 system. Refer to System 800xA Installation and Upgrade Getting
Started (2PAA111708*) on how to plan the system.
To identify System functions and node functions, refer to Appendix G.
During planning 800xA 6.0 system, few node functions require service group
name and service provider name to be entered. For standard nomenclature of
service group names and service provider names, refer to Appendix F.
During Online Upgrade, the Primary Aspect Server of 800xA 5.0 SP2 system
becomes the Secondary Aspect Server of 800xA 6.0 system and vice versa.
Hence all node functions of 800xA 5.0 SP2 Primary Aspect Server are now to be
planned on 800xA 6.0 Secondary Aspect Server and vice versa, while planning
the system using SCC Tool.
For Batch Redundancy, a server node in the system needs to be configured and
designated as the Batch Witness Server. Refer to System 800xA Batch Management
Configuration (3BUA000146*) for more information.
For Advant Master Connectivity Server node function, it is mandatory to configure
Network Group Number, Network 1, Network 2, and Node Number. These
numbers are documented in the Pre-Upgrade Procedures.
10. In the System Configuration Console Tool, under System Setup > Configure
System > System nodes, exclude all other nodes apart from Primary Aspect
Server node using Node actions... > Exclusion... option.

2PAA111695-600 G 35
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Figure 3.3: System Configuration Console - Exclusion

11. After excluding all the nodes except primary Aspect server, click Deploy
system....

36 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Figure 3.4: System Configuration Console - Deploy System

12. Export and save the System Configuration and System Configuration State aspects
from: Admin Structure > Administrative Objects > Domains > <System
Name>,Domain

2PAA111695-600 G 37
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Figure 3.5: System Configuration and System Configuration State Aspect

Do not open SCC before import and after export of System Configuration and
System Configuration State aspects.

13. Delete the newly created 800xA system (in Step 8.).
Stop the system before deleting.

a. Go to the Configuration Wizard and select System Administration, and


click Next.
b. Mark the system you want to delete. Click Next.
c. Select Systems and click Next.
d. Select Delete, click Next.

38 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

e. Select system and click Next.


f. Click Finish in the Apply Settings dialog box.
g. Wait a few minutes, and when the Configuration Wizard appears again with
the System dialog box the deletion of the system is completed.
h. Click Exit.
14. Reboot the node.
15. Install the 800xA 6.0 compatible custom libraries and extensions on the Primary
Aspect Server Node.
16. Restore the 800xA 5.0 SP2 System backup on the Primary Aspect Server.
The User Account that is used for 800xA System restore using the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser
• IndustrialITAdmin
• Local Administrators
The backup/restore utility supports the restoring of 800xA System information.
The following steps outline the 800xA System restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.
To start the restore procedure:
a. Open the Configuration Wizard.
b. In the Select Type of Configuration dialog box, select Restore System, and
then click Next.
c. When a dialog box appears with the Generate new system id check box
available, select the check box. This is necessary because there will be two
systems in one network during an online upgrade.
d. Enter a system name and click Next.
e. Rename the first Aspect Server to the last Aspect Server (this is now going
to be the Primary Aspect Server) in the Node Configuration dialog box under
the Primary nodes frame.

2PAA111695-600 G 39
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

If the Aspect Servers is combined with any other 800xA Server, naming of user
configured Service Group(s) and Service Provider(s) needs to be handled manually
after upgrade.
f. Rename the last Aspect Server to the first Aspect Server in the Primary nodes
frame and click Next.
Verify and review the message with missing System extensions. Ignore the missing
VB Graphics Extensions. However, it is important to verify and review all other
missing system extensions.
17. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Troubleshooting to resolve any received warning
or error messages.
Restart the node when advised during the restore procedure.

18. Check the CPU load in the node. The System Message service may generate a
high load (>90%). If this continues for longer than approximately 10 minutes,
restart the service.
If a message appears stating that a full deploy of the Generic Control Network is
needed, click OK.
19. Import the System Configuration and System Configuration State aspects from
Step 12..
The aspects are to be imported to the below path:
Admin Structure > Administrative Objects > Domains > System
Name,Domain
20. To make the future updates and upgrades easier, the Service Group names and
Service Provider names must match either the default names for System 800xA
6.0 or the configured names for node functions with Server Groups and Providers
configured in Step 11.. It is mandatory to rename the Service Group and Provider
names on the Primary Aspect Server as per the default format before we proceed.
For more information about the correct names for service groups and providers,
refer to Appendix F.

40 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

If the Service Group names and Service Provider names do not match in the
configuration created by the system installer and imported in Step 19., Deploy
can fail or duplicate Service Groups and Providers may be created after upgrade.
In this case the duplicate Service Groups and Providers needs to be cleaned up
from 800xA 6.0 system looking at 800xA 5.0 SP2 reference System.
21. Refer to Compare the Number of Aspects and Objects and record the number of
aspects and objects in the system. Compare these values to those recorded when
the system was backed up.
22. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (2PAA111693*) for more information on how to configure
affinity.
23. Refer to Consistency Check and perform the necessary consistency checks.

800xA for AC 870P/Melody Servers


While performing an online upgrade, ensure that the upgrade of the Melody
Connectivity Server and the Melody Configuration Server is performed on the
same calendar day. The reason being:
A subscription (date stamp) is added to the upgraded Configuration Server by the
running Connectivity Server. If the upgrade of the servers are not performed on
the same calendar day, there would be a mismatch in this subscription, thus not
allowing the upgraded Connectivity Server to start after the system upgrade.

Redundant Connectivity Servers


The following are the procedures for upgrading redundant Connectivity Servers.
1. Perform node specific Pre-Upgrade Procedures depending on the node functions
assigned on the node.
2. Stop a redundant Connectivity Server from the 800xA 5.0 SP2 System using the
Stop Server feature in the Configuration Wizard.
3. Remove the redundant Connectivity Server from the 800xA 5.0 SP2 System
using the Remove Server feature in the Configuration Wizard. If working in a
domain this server needs to be removed from the Domain Controller.
4. Reformat the hard drive.
5. Install the new operating system defined for the 800xA 6.0 System.

2PAA111695-600 G 41
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

6. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting


Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
7. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
8. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
This information is applicable only if system has ABB 800xA for AC 100.
If you have made a copy of the Bus Configuration Database (BCD) folder in the
pre-upgrade procedure, copy the saved BCD file folder to the planned AC 100
Connectivity Server node on 800xA 6.0 system before proceeding to next step.
9. Deploy this redundant Connectivity Server node from 800xA 6.0 Primary Aspect
Server using Deploy system option of SCC Tool. Before deploying, this node
is to be removed from Exclusion.
a. Open System Configuration Console Tool.
b. Navigate to System Setup > Configure System > System Nodes.
c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.
Deploying a node involves deploying of allocated node specific functions
on that node and connect node to the Primary Aspect Server.
10. Refer to Post-Upgrade Procedures and perform the applicable post-upgrade
procedures for the upgraded server.
11. Repeat this procedure for every redundant Connectivity Server.
Upgrade the servers one-by-one in order to keep redundancy of the system as long
as possible.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

42 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Redundant Aspect Server (2oo3 Redundancy Only)


Perform this procedure only if the Aspect Servers in the 800xA System have 2oo3
redundancy.
The following are the procedures for upgrading redundant Aspect Servers (2oo3
redundancy only).
1. Stop the other redundant Aspect Server (if 2oo3 redundant) from the 800xA 5.0
SP2 System using the Stop Server feature in the Configuration Wizard.
2. Remove the other redundant Aspect Server from the 800xA 5.0 SP2 System
using the Remove Server feature in the Configuration Wizard. If working in a
domain this server needs to be removed from the Domain Controller.
3. Reformat the hard drive.
4. Install the new operating system defined for the 800xA 6.0 System.
5. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
6. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
7. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
8. Deploy this redundant Aspect Server node from 800xA 6.0 Primary Aspect Server
using Deploy system option of SCC Tool. Before deploying, this node is to be
removed from Exclusion.
a. Open System Configuration Console Tool.
b. Navigate to System Setup > Configure System > System Nodes.
c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.

2PAA111695-600 G 43
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

9. Refer to Post-Upgrade Procedures and perform the applicable post-upgrade


procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the
800xA 5.0 SP2 System at this point in the upgrade process.

Clients
The following are the procedure to upgrade 800xA clients.
1. Remove some clients from the 800xA 5.0 SP2 System using the Remove Client
feature in the Configuration Wizard. If working in a domain the clients need to
be removed from the Domain Controller.
Do not remove all of the clients from the 800xA 5.0 SP2 System at this point.
Keeping some clients in the 800xA 5.0 SP2 System will allow the operators to
continue to observe and control the process.
The procedure for the client nodes can be performed one-by-one or in a group.

2. Reformat the hard drive on each client.


3. Install the new operating system defined for the 800xA 6.0 System.
4. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
5. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
NPT installs Core products and creates a local media repository required to
continue the Deploy. Wait until the node re-starts before proceeding.
6. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
7. Deploy the Client(s) from 800xA 6.0 Primary Aspect Server using Deploy system
option of SCC Tool. Before deploying, this node is to be removed from Exclusion.

44 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

a. Open System Configuration Console Tool.


b. Navigate to System Setup > Configure System > System nodes.
c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.
Operation and monitoring of the plant is only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

Information Management Server


The following are the procedure to upgrade the Information Management Server.
1. Check that history and event data storage is available in the Connectivity Servers
to overlap, with margin, the time it takes to upgrade the IM Server. This includes
time to:
• Reformat the hard drive.
• Load all required software.
• Connect the IM Server to the 800xA 6.0 System.
• Reboot the IM Server.
• Collect data from the Connectivity Servers from the time when the IM Server
was removed from the 800xA 5.0 SP2 System.
2. Perform the Information Management pre-upgrade procedures. Refer to
Information Management.
3. Stop the IM Server from the 800xA 5.0 SP2 System using the Stop Server feature
in the Configuration Wizard.
4. Remove the IM Server from the 800xA 5.0 SP2 System using the Remove Server
feature in the Configuration Wizard. If working in a domain this server needs to
be removed from the Domain Controller.
5. Reformat the hard drive.
6. Install the new operating system defined for the 800xA 6.0 System.
7. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,

2PAA111695-600 G 45
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
8. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
The Installation Type options are to be selected while running NPT, based on
the node functions selected on that node.
Information Manager - IM (Oracle) needs to be selected while running NPT on
an Information Management Server.
9. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
10. Deploy this Information Management Server node from 800xA 6.0 Primary
Aspect Server using Deploy system option of SCC Tool. Before deploying, this
node is to be removed from Exclusion.
a. Open System Configuration Console Tool.
b. Navigate to System Setup > Configure System > System nodes.
c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.
11. Verify that the ABB Process Administration Service (PAS) is set to manual in
the Services Control Panel (run Services.msc from the Run dialog box). Stop
the service if it is running.
12. Reboot the node.
13. Refer to Information Management and perform the applicable post-upgrade
procedures for the upgraded server.
Operation and monitoring of the plant are only possible from clients in the 800xA
5.0 SP2 System at this point in the upgrade process.

46 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Application Servers
Perform the procedures for the Application Servers (Batch Management, Asset
Optimization, PC, Network and Software Monitoring, etc.) one at a time.

When upgrading redundant Batch Management Servers, the Primary Batch Server
must be upgraded first, followed by the Secondary Batch Server. Do not upgrade
the Secondary Batch Server followed by the Primary Batch Server.
For Batch Redundancy, a server node in the system needs to be configured and
designated as the Batch Witness Server. Refer to System 800xA Batch Management
Configuration (3BUA000146*) for more information.
The following are the procedure to upgrade the Application Servers.
1. Perform node specific Pre-Upgrade Procedures depending on the node type.
2. Stop an Application Server from the 800xA 5.0 SP2 System using the Stop
Server feature in the Configuration Wizard.
3. Remove the Application Server from the 800xA 5.0 SP2 System using the
Remove Server feature in the Configuration Wizard. If working in a domain
this server needs to be removed from the Domain Controller.
4. Reformat the hard drive.
5. Install the new operating system defined for the 800xA 6.0 System.
6. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
7. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
NPT installs Core products and creates a local media repository required to
continue the Deploy. Wait until the node re-starts before proceeding.
The Installation Type options are to be selected while running NPT, based on
the node functions selected on that node.

2PAA111695-600 G 47
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

Figure 3.6: Installation Type

8. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
9. Deploy the Application Server node from 800xA 6.0 Primary Aspect Server
using Deploy system option of SCC Tool. Before deploying, this node is to be
removed from Exclusion.
a. Open System Configuration Console Tool.
b. Navigate to System Setup > Configure System > System nodes.
c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.

48 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

10. Refer to Post-Upgrade Procedures and perform the applicable post-upgrade


procedures for the upgraded server.
11. Repeat this procedure for every Application Server.
The 800xA System is now running in nonredundant mode in both the 800xA 5.0
SP2 and the 800xA 6.0 systems. Operation and monitoring of the plant are possible
from clients in both systems at this point in the upgrade process.
12. Operators should move to the 800xA 6.0 System to operate and control the plant
at this point in the upgrade process.

Remaining Nodes
Remove the remaining nodes in the 800xA 5.0 SP2 System and follow the above
procedures based on node type, except for the 800xA 5.0 SP2 Primary Aspect Server.
Operation and monitoring of the plant are only possible from clients in the 800xA
6.0 System at this point in the upgrade process.

Primary Aspect Server


Before proceeding with this step, make sure that all other nodes in the system are
upgraded to 800xA 6.0.

The following are the procedure to upgrade the Primary Aspect Server.
1. Use the Configuration Wizard to stop the 800xA 5.0 SP2 System on the Primary
Aspect Server.
2. Use the Configuration Wizard to delete the system from the Primary Aspect
Server.
3. Reformat the hard drive.
4. Install the new operating system defined for the 800xA 6.0 System.
5. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
6. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.

2PAA111695-600 G 49
3 Considerations and Upgrade F 3.3 Online Upgrade Flow

The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
7. Install the 800xA 6.0 compatible custom libraries and extensions on this Node.
8. Verify the Aspect Directory Services in 800xA 6.0 System to ensure that Aspect
Servers are in correct order.
a. Open the Plant Explorer Workplace on the Primary Aspect Server node of
800xA 6.0 system.
b. Navigate to Service Structure > Services >AspectDirectory > Basic,
Service Group.
c. In the Service Group Definition aspect, click the Configuration tab.
d. Verify if the 800xA 6.0 Primary Aspect Server node deployed is first in the
list followed by other Aspect Servers. If necessary, correct the order.

Figure 3.7: Order of Aspect Directory Services

9. Deploy this node from 800xA 6.0 Primary Aspect Server using Deploy system
option of SCC Tool. Before deploying, this node is to be removed from Exclusion.
a. Open System Configuration Console Tool.
b. Navigate to System Setup > Configure System > System nodes.

50 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

c. Select the node to be deployed and enable for deployment using Node
actions... > Exclusion... > Include in deployment option.
d. Select the node and click Deploy system... to deploy this node.
10. Perform the 800xA full backup from the Maintenance Structure (Aspect
Directory backup type) and ensure that there are no new errors and warnings.

3.4 Offline Upgrade Flow


This section provides detailed information and procedures for doing an Offline
Upgrade of an 800xA System. Refer to Online Upgrade on page 22 for additional
information and ideas on how to streamline the upgrade process.
The topic is organized so that the instructions are presented in the proper upgrade
order. Do not skip any steps that pertain to 800xA software being used in the
current or upgraded system.
It is important to create backups of node hard disks (using a third party
backup/restore and/or disk imaging utility) and the 800xA System before starting
the upgrade procedures. Valid backups ensure that the system can be restored if
necessary.
Offline Upgrade workflow is divided into following sections:
• Preparing the 800xA 5.0 SP2 System: The procedures cover system wide and
node specific steps that need to be done on a 800xA 5.0 SP2 System before doing
an upgrade.
• Preparing the 800xA 6.0 System (Offline Upgrade): The procedures cover the
workflow to be followed for preparing 800xA 6.0 system during an Offline
Upgrade.
• Setting Up 800xA 6.0 System: The procedures cover the workflow to setup the
800xA 6.0 System including offline upgrade.

3.4.1 Preparing the 800xA 5.0 SP2 System


Perform the following to prepare an 800xA 5.0 SP2 System for an upgrade:
1. Document all Windows settings including the domain, DNS, policies, users, and
so on.

2PAA111695-600 G 51
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

2. Collect the information about the System Functions, Node Functions and their
configurations from existing System 800xA 5.0 SP2. This information can be
obtained from existing plant documentation.
The information about existing System 800xA 5.0 SP2 can be used while planning
a similar System 800xA 6.0.
Diagnostics Collection Tool can also provide some information about existing
System 800xA 5.0 SP2. For more details, refer to Appendix G.
3. Migrate the existing Visual Basic Process Graphics (VBPG) aspects to the
corresponding Process Graphics aspects. Refer to System 800xA Engineering 5.0
SP2 Process Graphics Migration Tool (3BSE049231*) available in myABB/My
Control System.
Visual Basic Process Graphics (VBPG) is not supported in System 800xA
beginning System 800xA 6.0. It is mandatory to migrate all VBPG to PG2 graphics
before performing upgrade.
The System 800xA VBPG Search Tool is used to find VBPG aspects in 800xA
system that need to be migrated prior to a system upgrade. The tool can also
identify PG2 aspects that have references to VBPG aspects. For more information
on the tool, refer to System 800xA VBPG migration and System 800xA VBPG
Search Tool (3BSE081093).
All VBPG aspects Main View in System 800xA 6.0 and later will show a message:
This aspect is not supported and will not be available for operator actions.

Symbol Factory Controls are no longer installed with the standard ABB 800xA
installation. A separate installation (ABB 800xA Symbol Factory) is needed to
use the Symbol Factory Controls. The ABB 800xA Symbol Factory installation
package is available on the media. A separate license is required to use the ABB
800xA Symbol Factory Controls.
4. The 800xA System and software require preparatory procedures before performing
the upgrade. These pre-upgrade procedures are dependent on the products installed
in existing 800xA System and are classified as:
a. System-wide Pre-Upgrade Procedures
b. Pre-upgrade Procedures before Maintenance Backup
c. System 800xA Maintenance Backup
d. Pre-upgrade Procedures for Local Data Backup

52 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Perform the applicable procedures in the order presented in Pre-Upgrade


Procedures section before proceeding.
5. After taking the maintenance backup, retain the Aspect Directory node with the
800xA 5.0 SP2 System.
It is highly recommended to retain the Aspect Directory node after taking the
maintenance backup on the 800xA 5.0 SP2 System. This will not only act as a
reference node post-upgrade, but will also ensure that the changes made to the
aspects created by the System Extensions can be reapplied in the new system, if
lost during an upgrade.
Refer to Reconfigure Aspects Created By System Extensions in Post-Upgrade
Procedures for information on evaluating and reapplying the changes to the System
Extension aspects.

3.4.2 Preparing the 800xA 6.0 System (Offline Upgrade)


Figure 3.8 shows a high level flow of the preparing and configuring 800xA 6.0 system
during Offline Upgrade.

2PAA111695-600 G 53
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.8: Preparing and Configuring 800xA 6.0 System - Offline Upgrade

Prepare the following to prepare an 800xA 6.0 System for an upgrade:


1. Order the System 800xA licenses required for the 800xA 6.0 System. Refer to
System 800xA Licensing Information (2PAA111691*) for more information.

54 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

2. Order new hardware and third-party software required for the 800xA 6.0 System.
Refer to System 800xA Installation and Upgrade Getting Started (2PAA111708*)
for more information.
If you have chosen to upgrade the 800xA System online, after completing Step
2., perform all the specific steps for an online upgrade described in the Online
Upgrade Flow section.
3. Migrate the redundant Domain Controllers. Refer to the Appendix A for more
information.
If it is a workgroup system, ignore this step.
4. Reformat the hard drives of all 800xA System nodes or use the new hardware
for the 800xA 6.0 System
5. Install the new operating system defined for the 800xA 6.0 System.
6. Refer to Prerequisite Section of System 800xA Installation and Upgrade Getting
Started (2PAA111708*) and perform all procedures relating to operating system
settings, Windows service packs, miscellaneous Windows components installation,
other third party software, group policy, 800xA Service User privileges, and
Windows updates and hot fixes.
7. Run Node preparation tool on all 800xA nodes.
Launch the Node Preparation Tool (NPT) by starting the Setup.exe from the
root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment of
an 800xA System.
The Installation Type options are to be selected while running NPT, based on
the node functions selected on that node.

2PAA111695-600 G 55
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.9: Installation Type

The User Account that is used for 800xA System installation must be a member
of the following groups:
• IndustrialITUser
• IndustrialITAdmin
• Local Administrators

Configure IPSec
If you want to view all exemptions using the new ABB 800xA IPSec Configuration
Tool in 800xA 6.0, then follow the procedure as in the IPsec Configured in Source
System .

56 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

IPsec Configured in Source System . If the IPsec is configured in the source system
(800xA 5.1) then after the domain controller is upgraded, perform the following steps
on the domain controller before upgrading other nodes:
1. Disable the existing group policy from the domain group policy object.
a. Go to Group Policy Management and choose Group Policy Objects.
b. Right-click the existing group policy.
c. Select GPO Status.
d. Select All Settings disabled.
2. Disable the link of the existing group policy.
a. Right-click the existing group policy and clear the Link Enabled option.
3. Delete the existing group policy.
a. Right-click the existing group policy in the Group Policy Objects and click
Delete.
4. Follow the procedure mentioned in System 800xA Post Installation
(2PAA111693*) to configure the rules.

IPsec not Configured in Source System. If IPsec is not configured in the source
system and if IPSec is required after upgrade, then follow the procedure mentioned
in System 800xA Post Installation (2PAA111693*) to configure the rules.

3.4.3 Setting Up 800xA 6.0 System


Perform the following on the node designated to be Primary Aspect Server of the
upgraded 800xA 6.0 system:
1. Launch System Configuration Console tool as the 800xA Installing User from
ABB Start Menu > ABB IndustrialIT > System.
2. Go to Create System task to create a System on the Primary Aspect Server node
and making the node ready for System deploy.
3. Go to Configure System task in SCC, plan the 800xA 6.0 System identical to
800xA 5.0 SP2 system. Refer to System 800xA Installation and Upgrade Getting
Started (2PAA111708*) on how to plan the system.

2PAA111695-600 G 57
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

During planning 800xA 6.0 system, few node functions require service group
name and service provider name to be entered. For standard nomenclature of
service group names and service provider names, refer to Appendix F.
For Batch Redundancy, a server node in the system needs to be configured and
designated as the Batch Witness Server. Refer to System 800xA Batch Management
Configuration (3BUA000146*) for more information.
For Advant Master Connectivity Server node function, it is mandatory to configure
Network Group Number, Network 1, Network 2, and Node Number. These
numbers are documented in the Pre-Upgrade Procedures.
4. In the System Configuration Console Tool, under System Setup > Configure
System > System nodes, exclude all other nodes apart from Primary Aspect
Server node using Node actions... > Exclude/Include... option.

Figure 3.10: System Configuration Console - Exclude

58 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

A popup appears to Exclude the node.

Figure 3.11: System Configuration Console - Popup to Exclude

5. After excluding all the nodes except primary Aspect server, click Deploy
system....

Figure 3.12: System Configuration Console - Deploy System

6. Export and save the System Configuration and System Configuration State aspects
from: Admin Structure > Administrative Objects > Domains > System
Name,Domain

2PAA111695-600 G 59
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.13: System Configuration and System Configuration State Aspect

7. Delete the newly created 800xA system (in Step 2.).


a. Go to the Configuration Wizard and select System Administration, and
click Next.
b. Mark the system you want to delete. Click Next.
c. Select Systems and click Next.
d. Select Delete, click Next.
e. Select system and click Next.
f. Click Finish in the Apply Settings dialog box.
g. Wait a few minutes, and when the Configuration Wizard appears again with
the System dialog box the deletion of the system is completed.

60 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

h. Click Exit.
8. Install compatible custom libraries and extensions on all 800xA 6.0 nodes.
9. Restore the 800xA 5.0 SP2 System backup on the Primary Aspect Server.
The User Account that is used for 800xA System restore using the Configuration
Wizard must be a member of the following groups:
• IndustrialITUser
• IndustrialITAdmin
• Local Administrators
The backup/restore utility supports the restoring of 800xA System information.
The following steps outline the 800xA System restore procedure.
Refer to System 800xA Maintenance (3BSE046784*) for more information on
restoring the system.
To start the restore procedure:
a. Open the Configuration wizard.
b. In the Select Type of Configuration dialog box, Select Restore System and
click Next.
c. In the Restore Selection dialog box, navigate to the path of 800xA 5.0 SP2
System Backup and click Next.
d. In the System Directories Selection dialog box, accept the default selections
and click the Next.
e. In the Node Configuration dialog box, check node name in the backup,
original node name and click Next.
f. In the Apply Settings dialog box, check summary info of selection and click
Finish.
Restart the node when advised during the restore procedure.
10. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Errors and Warnings during Upgrade to resolve
any received warning or error messages.
Restart the node when advised during the restore procedure.

2PAA111695-600 G 61
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

11. Import the System Configuration and System Configuration State aspects from
Step 6..
The aspects are to be imported to the below path:
Admin Structure > Administrative Objects > Domains > System
Name,Domain
12. To make the future updates and upgrades easier, the Service Group names and
Service Provider names must match either the default names for System 800xA
6.0 or the configured names for node functions with Server Groups and Providers
configured in Step 5.. It is mandatory to rename the Service Group and Provider
names on the Primary Aspect Server as per the default format before we proceed.
For more information about the correct names for service groups and providers,
refer to Appendix F.
If the Service Group names and Service Provider names do not match in the
configuration created by the system installer and imported in Step 11., Deploy
can fail or duplicate Service Groups and Providers may be created after upgrade.
In this case the duplicate Service Groups and Providers needs to be cleaned up
from 800xA 6.0 system looking at 800xA 5.0 SP2 reference System.
13. Refer to Compare the Number of Aspects and Objects and record the number of
aspects and objects in the system. Compare these values to those recorded when
the system was backed up.
14. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (2PAA111693*) for more information on how to configure
affinity.
15. Verify the Aspect Directory Services to ensure that Aspect Servers are in correct
order.
a. Open the Plant Explorer Workplace.
b. Navigate to Service Structure > Services >AspectDirectory > Basic,
Service Group.
c. In the Service Group Definition aspect, click the Configuration tab.
d. Verify if the Primary Aspect Server node deployed is first in the list followed
by other Aspect Servers. If necessary, correct the order.

62 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.14: Order of Aspect Directory Services

In the System Configuration Console Tool, under System Setup >


Configure System > System nodes, select the node to be deployed and
enable for deployment using Node actions... > Exclude/Include in
deployment option.

2PAA111695-600 G 63
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.15: System Configuration Console - Include

A popup appears to Include the node.

64 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow

Figure 3.16: System Configuration Console - Popup to Include

Perform this action to include all remaining nodes.


This information is applicable only if system has ABB 800xA for AC 100.
If you have made a copy of the Bus Configuration Database (BCD) folder in the
pre-upgrade procedure, copy the saved BCD file folder to the planned AC 100
Connectivity Server node on 800xA 6.0 system before proceeding to next step.
16. From Primary Aspect Server, deploy all the remaining nodes. Refer to System
800xA Installation and Upgrade Getting Started (2PAA111708*), for more
information.
17. Perform post upgrade procedures as mentioned in Post-Upgrade Procedures on
all applicable nodes.

2PAA111695-600 G 65
66 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.1 Pre-Upgrade Procedure Steps

4 Pre-Upgrade Procedures

The 800xA System and software require preparatory steps before performing the
upgrade. Perform the applicable procedures in the order presented, based on the
installed system.
If performing an online upgrade, you must perform the pre-upgrade procedures
described in this section on a node-to-node basis. Refer to the Online Upgrade
Flow section to know the node order to be followed.
If performing an offline upgrade, save the data obtained during the pre-upgrade
procedures in node-specific folders.

4.1 Pre-Upgrade Procedure Steps


Perform the following pre-upgrade procedures for all the applicable system/node
functions based on the installed system configuration:
• System-Wide Pre-Upgrade Procedures
• Pre-upgrade Procedures before Maintenance Backup
• System 800xA Maintenance Backup
• Pre-Upgrade Procedures for Local Data Backup

4.2 System-Wide Pre-Upgrade Procedures


Perform the following pre-upgrade procedures on all the nodes based on the installed
system.
• Configure IPSec
• Consistency Check
• Migrating Visual Basic Process Graphics Aspects to Process Graphics Aspects
• Faceplates

2PAA111695-600 G 67
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

• Record the Number of Aspects and Objects

4.2.1 Configure IPSec


If you want to view all exemptions using the new ABB 800xA IPSec Configuration
Tool in 800xA 6.0, then follow the procedure as in the IPsec Configured in Source
System .

IPsec Configured in Source System


If the IPsec is configured in the source system (800xA 5.1) then after the domain
controller is upgraded, perform the following steps on the domain controller before
upgrading other nodes:
Changing IPSec policies during Online upgrade is not recommended as this
severely impacts the proper running of the system.
1. Disable the existing group policy from the domain group policy object.
a. Go to Group Policy Management and choose Group Policy Objects.
b. Right-click the existing group policy.
c. Select GPO Status.
d. Select All Settings disabled.
2. Disable the link of the existing group policy.
a. Right-click the existing group policy and clear the Link Enabled option.
3. Delete the existing group policy.
a. Right-click the existing group policy in the Group Policy Objects and click
Delete.
4. Follow the procedure mentioned in System 800xA Post Installation
(2PAA111693*) to configure the rules.

IPsec not Configured in Source System


If IPsec is not configured in the source system then follow the procedure mentioned
in System 800xA Post Installation (2PAA111693*) to configure the rules.

68 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

4.2.2 Consistency Check


This topic describes the consistency check performed on the 800xA System.
Perform a consistency check before performing the 800xA System backup. Failing
to do so could result in problems when restoring the system after the upgrade. Any
changes to the aspects and objects must be done before taking the backup.
The following is an overview of the consistency check functionality in the 800xA
System.
• Perform consistency checks both before and after the upgrade.
• The consistency check is continuously improved between releases. If a consistency
error is detected after the upgrade, it does not necessarily mean that the error was
introduced by the upgrade process. It might have been there from the beginning,
but went undetected.
• Try to correct all consistency errors before the upgrade. This will make the
upgrade process easier. Consistency errors may cause the upgrade to either fail,
or continue, but without having done exactly what was intended. Since it is very
difficult to know where the upgrade handling will do changes, it is desirable to
make the system as consistent as possible before the upgrade. It is also good to
keep a system with the old version running so it is possible to go back and do
more corrections in the old system if problems occur during the upgrade.
– However, the upgrade will often work even though there are some remaining
consistency errors. In some cases it is easiest to correct the errors after the
upgrade (because the repair functionality has been improved in the new
release), so it may be worth an attempt at continuing with the upgrade. It is
recommended to keep a list of the detected consistency errors for future
reference.

2PAA111695-600 G 69
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

During the consistency check the following error messages might come from
PROFIBUS Hardware Libraries in system version 5.0 SP2 and later:
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Aspect Category
Definition'. ... : Library Version Definition
[Error] Aspect 'ABB_TFx12_PA 1.2-
0:Hardware Library' contains multiple library
keys. ... : Library Version Definition
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Object Type
Structure'. ... : Library Version Definition
3 error(s) reported by 1 aspect(s).
1 aspect(s) can be repaired

This will have no impact on system upgrade.


• In 800xA 5.0 SP2 and later, perform the consistency check with the Consistency
Check tool (started by clicking the question mark icon in top right corner of Plant
Explorer Workplace).
• Perform consistency checks on the user-defined libraries in the Object Type
Structure or Library Structure, the Control Project in Control Structure, and
the Functional Structure.
• The general part of the upgrade process consists of importing new versions of
standard libraries, and propagating object type changes to user libraries and user
applications. It is only necessary to correct consistency errors regarding object
type, object type references, and similar configurations for the general part of
the upgrade process to work. Other inconsistencies such as unresolved references
should normally not lead to problems.
– However, special upgrade handling designed by the Functional Areas may
also update the references of aspects, so it is best to correct also broken
references before the upgrade.
– In the Library structure, navigate to Library Version Definition aspect present
in the user defined libraries. Select the Consistency tab and click Check
Consistency. Correct any errors that may appear during the consistency
check.
In 800xA5.0 SP2 and later, perform the consistency check with the Consistency Check
tool (started by clicking the question mark icon in top right corner of Plant Explorer

70 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

Workplace). This instruction only includes the 800xA 5.0 SP2 and later procedure.
Refer to System 800xA Tools (2PAA101888*) for more detailed information on running
the 800xA 5.0 SP2 consistency check.
Perform a consistency check before performing the 800xA System backup. Failure
to do so could result in problems when restoring the system after the upgrade.

If using Asset Optimization, be sure to run the Consistency Check tool and delete
any inconsistent Asset Monitor Control Connection Properties aspects.
Perform the following to perform a consistency check:
1. Open a Plant Explorer Workplace.
2. Click the Consistency Check Tool icon at the top of the Plant Explorer
Workplace to launch the Consistency Check Tool.
Rather than performing Step 3. through Step 6. it is also possible to drag the desired
items to the Consistency Check Tool.
3. Click Add Item to open the Select Item dialog box.
4. Browse to the desired location.
5. Select the desired items (use Ctrl+Click or Shift+Click to select multiple items).
If a subtree is selected, all objects and aspects in the subtree will be selected. If
a library or application is selected, everything in this entity will be selected.
6. Click Add and Close.
7. Click Check.
8. If errors are found, and they are marked Repairable, perform an automatic repair
by selecting Repair Aspect in the context menu.
9. If errors are found that are not automatically repairable, try to manually
reconfigure the aspects to repair the consistency errors.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

2PAA111695-600 G 71
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

4.2.3 Migrating Visual Basic Process Graphics Aspects to Process


Graphics Aspects
Visual Basic Process Graphics (VBPG) is not supported in System 800xA begenning
System 800xA 6.0 and the graphic aspects based on VB can no longer be edited.
It is mandatory to migrate all user defined VBPG graphics to PG2 graphics before
performing upgrade. Refer to System 800xA Engineering 5.0 SP2 Process Graphics
Migration Tool (3BSE049231*) available in the myABB/My Control System for
information about the migration process.
The System 800xA VBPG Search Tool is used to find VBPG aspects in 800xA
system that need to be migrated prior to a system upgrade to System 800xA 6.0.
The tool can also identify PG2 aspects that have references to VBPG aspects. For
more information on the tool, refer to System 800xA VBPG migration and System
800xA VBPG Search Tool (3BSE081093).
All VBPG aspects Main View in System 800xA 6.0 and later will show a message:
This aspect is not supported and will not be available for operator actions.

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.2.4 Faceplates
The faceplates that were not migrated to Process Graphics 2 before the upgrade have
to be migrated for the following reasons:
• Better runtime performance, as no name server access is required when a faceplate
is opened.
• More reliable because the references continue to work even if the target object
is renamed.
• Microsoft Corporation has withdrawn support for Visual Basic.
• Upgraded faceplates function efficiently with the Consistency Checker and
Reference Tool. This behaves similar to a Process Graphics 2 graphic aspect.
• The upgrade to new reference handling can also repair some broken references.
Refer to the Upgrading Faceplates appendix in System 800xA Engineering Process
Graphics (3BSE049230*) for the procedure to upgrade the faceplates.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

72 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures

4.2.5 Record the Number of Aspects and Objects


This topic helps you compare the number of aspects and objects in the system before
the 800xA System Backup and after the 800xA System Restore.
Perform the following procedure to record the number of aspects and objects in the
800xA 6.0 system and compare the number with the 800xA 5.0 SP2 system.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Admin Structure.
3. Use the Object Browser to navigate to:
Administrative Objects\Domains\system_name, Domain

4. Select Domain Definition in the Aspect List Area.


5. Record the number of objects and aspects listed in the System Size Information
area in the Preview Area.
6. Use the Structure Selector to open the Control Structure.
7. Use the Object Browser to navigate to:
control_network_name, Control Network

of one of the control networks contained in the system.


8. Right-click the Control Structure aspect and select Details.
9. Click the Statistics tab.
10. Record the number of objects listed.
Step 11. through Step 15. are not applicable to systems with only 800xA for
Harmony.
11. Right-click the Control Structure aspect within a controller project of the control
network selected in Step 7..
12. Select Details from the context menu.
13. Record the number of objects listed.
14. Repeat Step 11. through Step 14. for all the controller projects within the control
network.
15. Repeat Step 7. through Step 14. for every control network in the system.

2PAA111695-600 G 73
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

The number of aspects and objects after system restoration should be in the same
range as those recorded during the system backup, although there will be a few
more aspects and objects.
16. Use the Object Browser to navigate to:
HSE_Subnet name, HSE Subnet

of one of the HSE Subnets contained in the system.


17. Right-click the Control Structure aspect and select Details.
18. Select the Statistics tab.
19. Record the number of objects listed.
20. Repeat Step 16. through Step 19. for every HSE Subnet in the system.
21. Use the Object Browser to navigate to:
MB300 name, MB300 Network

of one of the MB 300 Networks contained in the system.


22. Right-click the Control Structure aspect and then click Details.
23. Click the Statistics tab.
24. Record the number of objects listed.
25. Repeat Step 21. through Step 24. for every MB300 network in the system.
The number of aspects and objects after system restoration must be in the same
range as those recorded during system backup, although there will be a few more
aspects and objects recorded in the 800xA 6.0 system.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3 Pre-upgrade Procedures before Maintenance


Backup
This section details the pre-upgrade procedures that must be performed on the 800xA
5.0 SP2 system before taking the maintenance backup.
• Batch Management
• Customized Alarm Priority Mapping Aspects

74 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

• 800xA for AC 800M


• Engineering Studio
• Device Types in System 800xA
• Device Management FOUNDATION Fieldbus
• PROFINET IO Feature Pack 1.2
• 800xA for Advant Master and 800xA for Safeguard
• 800xA for AC 100
• 800xA for DCI
• 800xA for Harmony
• 800xA for AC 870P/Melody
• 800xA for MOD 300
• IEC 61850 Connect
• Freelance Connect
• PLC Connect
• Asset Optimization
• PC, Network and Software Monitoring
• PC, Network and Software Monitoring Device Library
• SMS and e-mail Messaging
• Information Management
• Application Scheduler and Calculation Server
• 800xA History
• Process Engineering Tool Integration

4.3.1 Batch Management


This topic describes the pre-upgrade procedure for Batch Management.
1. Verify all the scheduled batches are completed or terminated.

2PAA111695-600 G 75
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

2. Verify the Batch Management Servers are operating normally before and during
800xA System backups of systems containing Batch Management nodes. This
will ensure the backup of all batch data.
After the upgrade to the new version of Batch Management, the batch data in the
previous Batch database will no longer be available.

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.2 Customized Alarm Priority Mapping Aspects


Some customized Alarm Priority Mapping Aspects may be overwritten during the
upgrade. Record all values in the Alarm Priority Mapping aspects before beginning
the upgrade so that they can be recreated after the upgrade.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object Browser to navigate to:
Alarm & Event > Alarm Collection Definitions, Alarm Collection
Definitions

4. Select a Alarm Collection Definition object with customized Alarm Priority


Mapping Aspect.
5. Select Alarm Priority Mapping in the Aspect List Area.
6. Record the values in the Alarm Priority Mapping aspects.
7. Repeat for all customized Alarm Priority Mapping aspects.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.3 800xA for AC 800M


Perform the following procedures on all AC 800M Connectivity Servers:
1. Control Builder stores its settings (systemsetup.sys) on disk in the following
...\ABB Industrial IT Data\Engineer IT Data\Control Builder M Professional
Copy this systemsetup.sys file to a safe media. This step needs to be executed on
all nodes where Control Builder M is installed.

76 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

2. Save OPC configurations by selecting File > Save Configuration in the OPC
Server Panel.
3. The OPC Server stores configuration files (*.cfg) and settings (systemsetup.sys)
on disk. Copy these files to a safe media. The systemsetup.sys file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server for AC 800M
The configuration files are stored in the Files folder in the same location.

AC 800M Fingerprint Tool


AC 800M Fingerprint tool is a data collection tool, which collects diagnostic data
from all the controllers on the network. This tool can be used on the 800xA 5.0 SP2
system to collect data about the firmware versions, CPU load, hardware revisions
and so on. The data is collected in tab-separated text files and is saved with the
IP address and the controller name in a separate folder on the system. The data in the
text files can also be exported to a spreadsheet for data analysis.
Run the AC 800M Fingerprint tool before the upgrade to collect data from the 800xA
5.0 SP2 System. Similarly, run the tool after an upgrade to collect the data on the
800xA 6.0 System. The data collected before and after the upgrade can be compared
to analyze and verify the changes that may have occurred during the upgrade process.
Refer to System 800xA Control AC 800M Configuration (3BSE035980) for more
information on the AC 800M Fingerprint tool.
The Fingerprint tool is located in ...\Engineering\Control Builder M\Tools\AC 800M
Fingerprint in 800xA 6.0 installation media. Start the Fingerprint Tool after copying
it to local node.

Start Values Analyzer Tool


A firmware upgrade of the controller may reset variables to their initial value. This
happens in case the cold retain attribute has not been set. The Start Values Analyzer
tool, introduced in System 800xA 6.0, can check if the attributes and parameters set
to the variables are changed after an upgrade. The tool displays a list of the variables
that may be set to the initial values after an upgrade. The output from this tool can
be exported to a spreadsheet for data analysis.
Run this tool before an upgrade and collect the data regarding the variables and the
associated attribute values. Run this tool after an upgrade, record the data, and compare
the results with the data collected before the upgrade. If certain variables are set to
the initial value during an upgrade, it can be reset to the last configured value based

2PAA111695-600 G 77
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

on the collected data. Refer to System 800xA Control AC 800M Configuration


(3BSE035980) for more information on the Start Values Analyzer tool.
The Start Values Analyzer tool is located in ...\Engineering\Control Builder
M\Tools\StartValuesAnalyzer\SV50SP2_SV51\ in 800xA 6.0 installation media. Start
the Start Values Analyzer Tool after copying it to local node.

Replacing Obsolete Libraries


If the system to be upgraded originates from System Baseline 2.1 and has been
upgraded in steps through system versions, verify that the Control Builder projects
do not use the old obsolete libraries of System Baseline 2 (Libraries of version 1.0-0).
For example: ControlStandardLib 1.0/0 and AC 800M Classic libraries (like
ProcessObjBasicLib-1-0-5, SupervisionLib-1-0-7, and so on).
These old obsolete libraries must be replaced with new versions of the respective
library before upgrading the system. This can be done using Replace Library option
in the Control Builder M Professional.
For more information on replacing a library, refer Library Handling appendix in
System 800xA Configuration (3BDS011222) manual.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.4 Engineering Studio


Use the following procedures to prepare for the Engineering Studio upgrade.
All the local language parameters used in the Function Designer need to be changed
to English before the upgrade. Usage of non-English parameters in the Function
Diagrams results in errors while generating configuration data.

Engineering Studio Add-Ins


Before updating/upgrading the system from previous release to the latest release
ensure the Engineering Studio Add-Ins are listed in Active Application Add-Ins in
MS-Excel.
Ensure to verify the add-ins only on the Engineering nodes that have Microsoft
Office installed.

78 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

If the Add-ins are not listed, perform Step 3. through Step 5. to enable them in the
MS-Excel:
1. Open MS-Excel.
2. Navigate to File > Excel Options > Add-Ins > Active Application Add-ins.
Refer to Figure 4.1 to view the Engineering Studio Add-ins.

Figure 4.1: Engineering Studio Add-Ins

3. Select COM Add-ins from Manage drop-down and click Go... List of COM
Add-ins window appears.
4. Select all the Engineering Studio Add-ins from the list and click OK.
5. View the Add-Ins in the Active Application Add-ins panel on the Excel Options
window.
Open MS-Excel and perform the recommended settings, if prompted.
Navigate to File > Excel Options> Trust Center Settings > Macro Settings,
and clear the Show the Start screen when this application starts check box.

2PAA111695-600 G 79
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.5 Device Types in System 800xA


Identify the device types used in the system. The latest version of the Device Libraries
are required during the upgrade. Compatible version of the Device Libraries are
available on the System 800xA 6.0 Installation media. Check for newer versions of
the Device Libraries if any in myABB/My Control System.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.6 Device Management FOUNDATION Fieldbus


Perform the following to prepare for the Device Management FOUNDATION
Fieldbus.
User-made modifications to library objects representing FF standard blocks (these
are blocks supported by the Device Type Standard FBs as indicated in the Block Info
tab of the block class parameter dialog box) will be overwritten during upgrade. If
such changes have been made, they can be reconstructed manually as a post upgrade
procedure.
The different resource ID’s for redundant OPC server FF in System 800xA 5.0
SP2 is changed in System 800xA 6.0. In System 800xA 6.0 a unique Subnet ID
must be used for both redundant OPC server FF. Use the Subnet ID 1 during
planning an upgrade.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.7 PROFINET IO Feature Pack 1.2


Some settings on CI871 are reset to default values when performing the upgrade of
PROFINET IO Feature Pack 1.2. The following are affected:
• Default Gateway.
Check the CI871 settings after upgrade and enter the previous values if the settings
are changed.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

80 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

4.3.8 800xA for Advant Master and 800xA for Safeguard


PU515A RTA Board is not supported in System 800xA 6.0, use PU410 RTA Unit
instead.
Perform the following to prepare for the 800xA for Advant Master and 800xA for
Safeguard upgrade.
• Save the Advant Master Controller Licenses.txt.

Save the Advant Master Controller Licenses.txt


Perform the following on the Primary Aspect Server in the original version of the
800xA system:
Save the Advant Master Controller Licenses.txt file to a safe location.
The default location for the file is:
...\Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\Licenses

Save the Configuration Files


The configuration files in the Connectivity Servers can contain special configuration
settings for Alarm and Event or Data access. Refer to 800xA for Advant Master,
Configuration (3BSE030340*) for more information about these special configuration
settings.
If such changes are available in the configuration files, perform the following on each
800xA for Advant Master and 800xA for Safeguard Connectivity Server node:
Save the following files to a safe location:
• AdvDsMasterAdapter.csv
• AdvMbAeOPCServer.csv
from the folder:
...\Program Files\ABB Industrial IT\Operate IT\AC 400 Connect\Bin

Save the DATHR Files


Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
1. Make an RTA Board backup.

2PAA111695-600 G 81
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

2. Save the following files to a safe location:


• DATHR1.CD
• DATHR2.CD
• DATHR3.CD
from the folder:
...\Program Files\ABB Industrial IT\Operate IT\AC 400
Connect\AdvantBase\Data\RTA\Init\
and record which files belong to which node.

Document the RTA Board Settings


Perform the following on each 800xA for Advant Master and 800xA for Safeguard
Connectivity Server node:
• Document the following settings in the RTA Board Control aspect for
re-configuration after the upgrade.
– MB300 Network 1, Network 2 and Node Number. These numbers must
later be used in the SCC tool when configuring the Node Roles of System
800xA 6.0.
– The value (selected or cleared) of the 800xA as Clock Master
(REVERSED_SYNC_MODE) check box.
• Document the Network number found on the MB 300 Net aspect. This aspect
is found in the MB300 Network object parent to each MB300 RTA Board object:
This number must later be used as Network Group Number in the SCC tool
when configuring the Node Roles of System 800xA 6.0.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.9 800xA for AC 100


Perform the following to prepare for the 800xA for AC 100 upgrade:
For each 800xA for AC 100 Connectivity Server node, document the settings in the
Configuration Wizard for these action groups:
• AF100 Network

82 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

If you have stored a local copy of the Bus Configuration Database (BCD) file in the
Connectivity Server node, copy the BCD file folder to a safe location.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.10 800xA for DCI


Perform the following to prepare for the 800xA for DCI upgrade:
1. Use the import/export utility to export all DCI OPC Server Network objects and
all their children from the Control Structure.
The exported file will be used only if there is a problem with the upgrade.

2. If any modifications and/or additions were made to Symphony DCI object types
in the Object Type Structure, export only those changes using the import/export
utility.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.11 800xA for Harmony


If 800xA for Harmony is used in the system, 800xA for Harmony Standalone
ConfigServer Export Tool must be run before performing the 800xA System Backup.
Perform the steps as described in the Save 800xA for Harmony Configuration Server
Information section to prepare for the 800xA for Harmony upgrade.

Save 800xA for Harmony Configuration Server Information


Perform the following steps once on each 800xA for Harmony Configuration Server
and on each combined 800xA for Harmony Configuration and Connectivity Server
node in the system:
1. Install the Standalone ConfigServer Export Tool from the following directory
on the System 800xA 6.0 installation media:
800xA Connectivities\800xA for Harmony\Standalone ConfigServer Export Tool
a. Double-click Standalone ConfigServer Export Tool.msi.
b. On the welcome screen of the InstallShield wizard, click Next to start the
installation.

2PAA111695-600 G 83
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

c. Select Finished when the installation is complete.


2. Select Start, click Run, and enter SymHarmExporter to launch the export tool.
3. In the Harmony Exporter window, select Browse.
4. In the Save As window, enter a File name for the ConfigServer Export file, choose
a folder location to save the file, and then click Save.
5. In the Harmony Exporter window, select Start Export. The Output Log will
display export status information. An Export Completed at date/time message is
displayed when the export is completed.
6. Close the Harmony Exporter window. The saved ConfigServer Export file will
be needed to upload the ConfigServer data into the 800xA 6.0 system after the
upgrade is complete.

Config Server Backup


Use the following procedure to create a 800xA 5.0 SP2 backup version of the 800xA
for Harmony Configuration. This backup is not needed for the upgrade to System
800xA 6.0, but would be needed to recreate a 800xA 5.0 SP2 system if necessary.
1. On the 800xA for Harmony Configuration Server, select:
Start Menu > All Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Backup Configuration
2. Click Connect.
3. Click Browse to name the backup file and choose a location to save it.
4. Click Backup.
5. After the backup is completed, click Exit.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.12 800xA for AC 870P/Melody


Disable the Melody AutoConfigurator service in Plant Explorer > Service
Structure (the service must be disabled when the system maintenance backup is
started).

84 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

Back up project specific changes (if applicable):


• DHCP Server Configuration.
• ETC Host files for Melody Connectivity Servers from:
...\Windows\system32\Drivers
• Changes in the Default Object Types (e.g. manual changes for permissions
in Control Connection Aspects).
• ConvDB changes only on Configuration Server, change to the directory
ABB Industrial IT\Configuration in the Program Files folder and back up the
ConvDB.mdb and ConvDB_Hostname> .mdb files.

ConfigServer node: Ensure that no Commissioning will be done from the Melody
Composer during this upgrade.
Use the following procedure to save 800xA for AC 870P/Melody information:
1. Log in to the 800xA Service account on the Configuration Server node.
2. Select from the Start Menu:
All Programs > ABB Industrial IT 800xA > 800xA for Melody >
Configuration > Backup Configuration
3. Click Connect.
Save the backup file to a safe media like a network share or removable disk.
Otherwise, the file will be deleted once an upgrade occurs due to a reload of the
node.
4. Click Backup.
5. Click Exit when the backup is complete.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.13 800xA for MOD 300


Ensure that the configuration data noted in the Customized Data for Backup appendix
in 800xA for MOD 300 Configuration (3BUR002417*) has been recorded.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

2PAA111695-600 G 85
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

4.3.14 IEC 61850 Connect


1. This procedure only applies if IEC 61850 Connect is installed, which uses a
user-defined Graphic Library for applications.
While updating from a previous system version, it is observed in the Functional
Structure that all Process Graphics 2 Faceplate Elements and Process Graphics
2 Graphic Element aspects have the same name as the Faceplate Element.
Before performing System Backup in the previous system revision, select:
Object Type Structure > IEC61850 user-defined Library
and perform the following for all Process Graphics 2 Faceplate Elements and
Process Graphics 2 Graphic Element aspects of all Conducting Equipment objects:
• Right-click the aspect and select Details.
• In the Aspect info tab:
- Remove the Auto Instantiate aspect and Template aspect.
- Select the Inheritance Enabled option.
• Perform an upload operation with the relevant scd file.
Use the updated scd file if Step 1. is performed in running Plant conditions, to
ensure that there are no disturbances after performing the upload operation.

2. Make backups for the IEC 61850 CET OPC Server projects.
a. Open the CET Tool.
b. Select File > Open/Manage project. Select the project that needs to be
exported.
c. Click Export Project and click Open Project.
d. Save the Exported file in a safe location.
Refer to Section 2, 800xA IEC61850 OPC Server, CET Project Maintenance of
System 800xA IEC 61850 Connect Configuration (9ARD171387*) for more
information.
Handling of IET/CCT, CCT600, IET600, and PCM 600 projects are not described
here as they are external tools contributing to the IEC 61850 workflow. They do
not reside on the 800xA System nodes.

86 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.15 Freelance Connect


When upgrading to Freelance Connect 6.0.3 un-install the older version manually
and then use System Installer to install the new version.
During upgrade, log in on the Freelance Connect connectivity servers, as they start
up, otherwise the OPC Server will not start and this will cause the upgrade to hang.

4.3.16 PLC Connect


Perform the following procedure to prepare for the PLC Connect upgrade.
1. If the PLC Connect Communication Server Pre Treatment function is being used
in the application (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information), make a backup of the Pretreat dll
(Pretreat3.dll or <user-defined>.dll, be sure to select the version used). The
Pretreat dll is located in the following folder on the PLC Connect Connectivity
Server:
...\ABB Industrial IT\Operate IT\PLC Connect\Bin
The path is the default location of the file. If it has been placed somewhere else,
make a backup from that location.
2. Make a backup of the application project and source files for the Pretreat dll.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.17 Asset Optimization


Preparing for the Asset Optimization upgrade requires backing up data to a safe media.
Use the following procedure to back up Asset Optimization information (perform
only the steps applicable to the system):
1. Asset Monitoring:
Asset Monitoring directories will be found on every Asset Optimization Server
node and any other node defined as an Asset Monitoring Server.
a. If Runtime Asset Monitors are being used in the system, save the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to a safe

2PAA111695-600 G 87
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

media. This directory stores the runtime information calculated by the


Runtime Asset Monitors running in this node. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
b. If XY Profile Deviation Asset Monitors are being used in the system, save
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to a safe media. This directory is located in:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
c. If Counter Check Asset Monitors are being used in the system, save the
Counter Check Asset Monitors data directory named:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}

to safe media. This directory exists for each AO Server in the system. These
directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat\<Counter Check ID>
Where each <AO Server ID> directory represents one AO Server instance
running on the selected node. The <AO Server ID> directory name is
formatted as two consecutive GUIDs, for example:
{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-41C6-A981-FAB4386D5701}.

For correct system operation it is important that only the directories identified by
the Counter Check Asset Monitor category GUID be saved, as other data in the
tree structure above these directories will not be consistent with a restore.
2. Maximo Integration:
If using Maximo Integration, the Maximo Integration information (Maximo
Equipment ID and Maximo Credentials aspects) must be saved from all Asset
Optimization Server nodes. Refer the Service Structure for the name of the Asset
Optimization Server nodes.
a. The MxDef files provide the mapping between the 800xA System
environment and the Maximo system. If the MxDef files were customized
per the instructions in System 800xA Asset Optimization Configuration
(3BUA000118*) back up the customized MxDef files to safe media.

88 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

• The customized MxDef Files for Maximo versions 4.1 and 4.1.1 are
located in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\
• The customized MxDef files for Maximo version 5.1 and 5.2 are located
in the following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\ABBAO\Services\MOM\MxDefs\Maximo5\MxServer
• The customized MxDef files for Maximo version 6.2 are located in the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MaximoDef
i. Back up the AOMaximoModel.xml file to a safe location. A backup
of AOMaximoModel.xml is necessary because the ECS model for
Maximo also needs to be modified if the MXDef files are
customized.
The model file is available at the following location:
...\Program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure:
...\OperateITData\OptaoACDs
Backup the entire OptaoACDs folder.
3. SAP/PM Integration:
If using SAP/PM Integration, the SAP/PM Integration information (SAP Equipment
ID and SAP Credentials aspects) must be saved from all Asset Optimization Server
nodes. Reference the Service Structure for the name of the Asset Optimization
Server nodes.
a. Although the SAP/PM system is separate from the 800xA System, it is a
good idea to back up the system in use. Follow SAP/PM standard practices
for SAP/PM system backup.

2PAA111695-600 G 89
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

b. The SAPPMDef files provide the mapping between the 800xA System
environment and the SAP/PM system. If the SAPDef files were customized
per the instructions in System 800xA Asset Optimization Configuration
(3BUA000118*), back up the customized SAPDef files to safe media.
The customized SAPPMDef files for SAP version 4.7 are located under:
...\Program Files\ABB Industrial IT\Optimize IT\
Asset Optimization\AOECSConnector\SAPPMDef
c. Back up the AOSAPModel.xml file to a safe location. A backup of
AOSAPModel.xml is necessary because the ECS model for SAP also needs
to be modified if the SAPPMDef files are customized.
The model file is available at the following location:
...\Program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
The pending fault reports residing in the system are available in the following
directory structure. Backup the entire OptaoACDs folder.
...\OperateITData\OptaoACDs
Where:
<SAPSERVERIP>\<SYSTEM>\<CLIENT> is the combination of the SAP
Server Name|IP, and the SAP System Number and SAP Client Number
fields from the SAP Equipment ID aspect. These fields are configured in
the Aspect System Structure in the SAP Equipment ID aspect.
For example, the resultant path to the customized SAPDef files will look
like:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AoAIPSAPWebSrv\SAPXML\10.127.5.55\00\800
-or-
equivalently, if the DNS name corresponding to 10.127.5.55 is, for example,
the resultant path to the customized SAPDef files will look like:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AoAIPSAPWebSrv\SAPXML\moriah\00\800
Record the value of the SAPAOWebServer property in the ProviderProperties
aspect in:

90 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

Aspect System Structure > SAP Equipment ID


This property provides a link for SAP portal web pages that are installed on
the AOWebServerNode. This value will not be updated and will need to be
configured manually after the upgrade.
4. DMS Calibration Integration
The DMS Calibration Integration approach is changed in 800xA 5.1. Upgrade of
DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.18 PC, Network and Software Monitoring


Use the following procedure to prepare for the PC, Network and Software Monitoring
upgrade.
1. If there are user defined Script, Resource, and Assembly files they need to be
backed up. The user files are located in:
...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\bin\Configuration\Scripts\User
...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\bin\Configuration\Assemblies\User
...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\bin\Configuration\Resources\User directory
Copy the files in these directories to a safe location.
2. Disable the PC, Network and Software Monitoring service.
a. Use the Structure Selector to open the Service Structure in the Plant
Explorer Workplace.
b. Use the Object Browser to navigate to:
Services > OpcDA_Connector, Service > SG_IT Server, Service
Group > OPCDA_Provider_Node Name, Service Provider

(where Node Name is the name of the PC, Network and Software Monitoring
Server node).

2PAA111695-600 G 91
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

c. Select Service Provider Definition in the Aspect List Area.


d. Click the Configuration tab to produce a view in the Preview Area.
e. If the Enabled check box is selected, clear it and click Apply.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.19 PC, Network and Software Monitoring Device Library


Use the following procedure to prepare PC, Network and Software Monitoring Device
Library upgrade:
1. Back up MOF files (if they exist) to a safe location. The MOF files are located
at:
...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\MOFS
2. Back up Custom Asset Monitor dlls to a safe location if object types with Custom
Asset Monitors are loaded. The dlls are located at:
...\Program Files\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\Asset Monitoring\Bin
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.20 SMS and e-mail Messaging


Save all GSM Device hardware information. Record information for the GSM device
on the SMS and e-mail Messaging Reconfiguration GSM Hardware Setup Worksheet
shown in Table 4.1.
Table 4.1: SMS and e-mail Messaging Reconfiguration GSM Hardware Setup
Worksheet

Item Setting/Value
General Settings
Interval for Checking for Incoming Value: _____ Seconds/Minutes
Messages (circle one)
Unicode Checked or Unchecked (circle one)

92 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

Table 4.1: SMS and e-mail Messaging Reconfiguration GSM Hardware Setup
Worksheet
(Continued)

Item Setting/Value
Modem Settings
Available COM Ports Value: COM _____
Baud Rate Value: _____
PIN Value: _____
Preferred SMSC Number Value: _____

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.21 Information Management


Perform the following procedures to prepare for the Information Management upgrade
before taking a maintenance backup.

Verifying Information Management Database Sizing


Verifying HS_Index sizing
While upgrading to 800xA 6.0, a new index is added for the message logs. This new
index will use the space proportional to the configured message log capacity.
Generally, 1 GB of space per million messages is required in the History Runtime
Indexes Tablespace for storing the message logs.
To check and verify the tablespace sufficiency:
1. Navigate to the Node Administration structure.
2. For the Information Management server, add the configured capacity for the
IMMSGLOG and the PDLMSGLOG. Round up the result to the nearest million.
If IMMSGLOG has six million capacity and the PDLMSGLOG has 400,000
capacity, round up the result to seven million. This example will require 7 GB
of additional index space.
3. Open the Oracle Instance Wizard and review the storage for the History Runtime
Indexes. Verify that the difference between the current usage and the maximum
usage is greater than the calculated value from Step 2.. If the available space is

2PAA111695-600 G 93
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

less than the calculated space, increase the maximum size of the tablespace. If
the maximum size of the tablespace is greater than 32 GB, a second database file
(DBF) must be added.
4. Review and update any other tablespaces that are at or near 100%.
5. Apply the changes and exit from the Oracle Instance Wizard.
Verifying US_IPDL table sizing
The upgrade will modify/create additional indexes to improve PDL performance.
These indexes may require additional tablespace. Use the following procedure to
make any necessary adjustments. Proper sizing will insure the upgrade runs properly.
If multiple IM servers exist in the system, this procedure is required on each IM
server.
1. Login to the IM server as the "800xAInstaller" user.
2. open a cmd.exe widow.
3. run SQLPLUS.exe /@localhost
4. at the SQL prompt, type
SQL> select * from ops$ocshis.pdl_tables;
SQL> exit;
5. Using the row counts returned,use this equation to deteming the additional space
required.
HS_IPDL extra space = HISTORY_ASSOC_OCC_END*75 +
HISTORY_ASSOC_OCC_START*75 + RESOURCE_TRANSACTIONS*30
+ TASK_VARIABLES*30 + TASK*85
6. Open the IM Oracle Instance Wizard.
7. Increase the HS_IPDL maximum size by the calculated amount. If the tablespace
is close to 32GB, add an additional datafile as needed.
8. Review TEMP and UNDO tablespace. For large configurations, configurations
with 12 million entry messages logs, the maximum sizes for temp and rollback
should be in the 8-12GB range.

Cleaning the History Database


It is recommended that the history database be cleaned before making the backup.

94 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

ABB Process Administration Service (PAS) service must be stopped before


cleaning the History Database.
1. Open a Windows Command Prompt and enter hsDBMaint -checkDB.
2. If any problems are found, enter hsDBMaint -clean to fix them.

Verifying Service Provider Name Format


The Inform IT History Service Provider name is created automatically by the software
when the IM node is first created. If a user modifies the name, errors will be generated
while accessing a few utilities or while performing an upgrade. These errors can be
avoided by checking the name and correcting the name if necessary. The procedure
to check and change the Service Provider name is as follows:
1. In the Node Administration Structure, navigate to the IM History Configuration
group as shown in Figure 4.2.

Figure 4.2: History Configuration - Service Provider Name

2. Verify if the History Service Provider Name format is:


IM_Inform IT History_<hostname>

where <hostname> is the hostname of the IM server.


3. If the name does not match this format, use the workplace to correct the name.

2PAA111695-600 G 95
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc

If a maintenance backup was taken before the name change, a new maintenance
backup must be taken to reflect the change in the Service Provider name.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.22 Application Scheduler and Calculation Server


This procedure only applies to installations using the Application Scheduler and/or
Calculation Server services. If the services are installed and enabled, they must be
disabled before the Maintenance backup is taken. If they exist, perform the following
for each:
• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Service Structure.
• Select the Scheduler Service Object/Calculation Server Object.
• Select the Service Definition aspect.
• Click the Configuration tab.
• Clear the Enabled check box and click Apply.
The Scheduler/Calculation server services will have to be manually enabled after the
upgrade.
If performing an online upgrade, you can restart the Application Scheduler and/or
Calculation services after the PPA maintenance backup is completed. There is no
need to restart these if performing an offline upgrade as all nodes are offline before
any restoration begins.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.23 800xA History


Perform the following on the 800xA History Embedded Data Collectors:
1. Open Plant Explorer.
2. Navigate to the Service Structure and disable the services of the 800xA History
SyncService, 800xA History Event Collector, and the 800xA History EventServer
(available only in 800xA History 2.0 and its rollups).
3. Close Plant Explorer.

96 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.4 System 800xA Maintenance Backup

Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.3.24 Process Engineering Tool Integration


Perform the following to back up Process Engineering Tool Integration information.
The project data is located in the following directory:
...\Program Files\ABB Industrial IT\Engineer IT\Engineering Studio\Process
Engineering Tool Integration\Xml
Save the entire Xml data directory to a safe media such as a network share or
removable disk. The directory contains the default mapping files (*.dmf) modified
on the project, accelerator files (*.acc), and configuration files (*.pcf and *.fcf).
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.4 System 800xA Maintenance Backup


1. All system extensions that are part of the system must be installed and loaded
on the node where the backup will be taken (usually the primary Aspect Server
node).
The 800xA Backup/Restore function makes it possible to make an online backup
of the Aspect Directory on the Primary Aspect Server in the 800xA 5.0 SP2
System and restore it to the new Primary Aspect Server in the 800xA 6.0 System.
A full backup stores all aspect objects and aspect data (application data) in the
Aspect Directory.
2. Perform the 800xA System backup from the Maintenance Structure (Aspect
Directory backup type).
Do not make any configuration changes such as modifying displays, modifying
or deleting objects as these changes made to the system will be lost from this point
forward.
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Maintenance Structure.
c. Create a Full Backup Definition object.
d. Configure the Scope and Storage tabs.

2PAA111695-600 G 97
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

e. Check the disk space and path in the Storage tab. A large configuration
could require a minimum of five gigabytes of free space.
f. Start the backup process.
Refer to the How to Make a Full Backup topic in System 800xA Maintenance
(3BSE046784*) for more detailed information on performing the 800xA
System Backup.
Backing up a Production System will not save the contents of the Engineering
Environment. Use the Export function to save the contents of the Engineering
Environment. Modifications can be made in the Engineering Environment while
backing up a Production System but all Load Evaluate Go sessions must be closed.
Only the Production Environment is restored when a Production System is restored.
All other environments are removed. Do not restore a Production System while a
Load Evaluate Go session is active or modifications are being made in the
Engineering Environment.
For more information, refer System 800xA Engineering and Production
Environments (3BSE045030*).
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.5 Pre-Upgrade Procedures for Local Data Backup


• 800xA for AC 800M
• Information Management
• Basic History Service Data
After taking a maintenance backup and before doing an upgrade, the local data (the
run-time data that was not previously backed up) needs to be backed up. This section
describes the steps for a few Functional Area software that need to be performed to
back up the local data before an upgrade.

4.5.1 800xA for AC 800M


After taking a maintenance backup and before performing an online upgrade, ensure
to back up the run-time data from the Aspect Server as detailed in the following
section.

98 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

Compiler Output File Helper Tool


The compiler output files are created for every application and controller configuration
that will be downloaded to the controller. After a successful download of the
application and controller configuration to the controller, the compiler output files
are transferred to the Aspect Server.
The maintenance backup, before an upgrade will include the backup of the compiler
output files. However, there may be instances when some change to the applications
or controller configuration is downloaded after taking the maintenance backup. In
this case, the compiler output files need to be handled to ensure that a warm download
can be performed after the upgrade.
The Compiler Output File Helper tool, introduced in System 800xA 6.0, extracts the
compiler output files from the Aspect Server and stores it on a local disk. The same
tool is also used to import the collected files to the Aspect Server after the upgrade.
If changes have been downloaded to the controllers after taking the maintenance
backup, run the Compiler Output File Helper tool on the retained 800xA 5.0 SP2
Aspect Server to extract the compiler output files. After the upgrade to System 800xA
6.0, run the tool to import those files. Refer to System 800xA Control AC 800M
Configuration (3BSE035980) for more information on the Compiler Output File
Helper tool.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.5.2 Information Management


Perform the following procedures to prepare for the Information Management upgrade.

End Microsoft Excel Process using Windows Task Manager


Use Windows Task Manager to manually end the EXCEL.EXE process.

ABB Process Administration Service (PAS)


Perform the following procedure to run the PAS utility.
1. Run the Process Administration Service (PAS) utility on the Information
Management Application Server node. From the Control Panel select:
Administrative Tools > PAS > Process Administration

2PAA111695-600 G 99
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

This opens the Process Administration Service dialog box.


2. Click Stop All to stop all processes under PAS supervision.
3. Click Close when the dialog box indicates that all processes are stopped.
4. Use standard Windows procedures, select the Services from Administrative Tools
in Windows Control Panel, to place the ABB Process Administration Service
into manual and insure that it is stopped.

Information Management History Backup and Restore Utility


The IM Server must be connected to an active aspect system at this time. The
following steps require acesss to the aspect directory.
Use the Information Management History Backup/Restore utility to create all the
backup files that are required to completely back up the Information Management
History database. This includes all configuration data, log data from both file-based
and ORACLE -based logs, and the Aspect System definition file.
During a backup operation, all data in the Oracle database owned by the Oracle History
user is exported to the specified destination and compressed into a zipped archive,
along with any files that have been created to store file-based property log entries
(called flat files).
The History database can be backed up to any drive, including any mapped network
drives. The disk type should be NTFS for the backups.
To avoid any ambiguity, the backup operation produces a zipped archive of compressed
History database files for each drive that contains at least some portion of the database,
where each archive contains only the database files that are stored on the corresponding
drive. The backup utility uses the naming convention name-drive.zip for the zipped
archives that it produces. For example, if the History database is located entirely on
the C:\ drive and you wish to back up the database to a zipped archive called hist, the
backup operation will compress the database files into a zipped archive named
histDB-C.zip.
If the data files exceed two gigabytes, or if there are more than 25,000 files, then
multiple zip files will be created using the following naming convention:
• First File name-drive.zip
When backing up the History database, make sure the disk is ready and available on
the node on which the procedure is to occur. The log file should be checked after the
backup operation to make sure that the backup operation completed successfully.

100 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

Make sure the system drive is not getting full. Temp space is required to make the
backup. If the log file indicates that the Oracle export failed, additional options can
be passed to hsBAR to use another disk for the Oracle export.
To make a backup:
1. Select Backup and Restore Utility from: Start Menu > All Programs > ABB
Industrial IT 800xA > Information Mgmt > History > Backup and Restore.
2. Verify the Create Backup Files of Current Configuration option is enabled
in the IM Historian Backup/Restore Utility window.
3. Click Next. A window for setting up the backup operation is displayed.
4. Specify the location where the backup files are to be created in the New Directory
Path for the Backup field. Create a new directory such as E:\IMbackupSV5.0SP2.
The backup of the History data must be in a directory of its own, not the
D:\HSDATA\History directory. If the data is put into the D:\HSDATA\History
directory, it will get lost.
a. Specify additional hsBAR options if needed. When the system drive is low
on space, it is typical to specify:
-a D:\Export

The -a option enables an alternate location for temporary and Oracle DB


export files during the backup process. The folder should be created ahead
of time and the files system must be NTFS. Use this option to specify a
different folder for the oracle export file.
5. Verify the Only Generate Aspect Definition File option is disabled.
6. Click Next. The HsBAR Output Window is displayed.
7. Select the Automatically Close Upon Completion option.
8. After the HsBAR Output Window closes, monitor the progress in the Progress
Status area of the IM Historian Backup/Restore Utility window and click Finish
when the backup is complete.
If a message appears stating that there are inconsistencies between the log
configurations in the Aspect System and the log configurations in Oracle, it may
be because the database was not cleaned before running the backup. Use the
hsDBMaint -clean function to clean the database and then rerun the backup. If
this does not fix the problem, contact ABB Technical Support for further assistance.

2PAA111695-600 G 101
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

Saving Other Information Management Related Files


There are several other files related to Information Management to be saved as part
of a total system backup.
• History Archive Data: For each archive device, go to the location specified by
the Device Filename and copy the folders under that directory to a safe location.
Do this even if automatic backup is configured. If the automatic backups are on
local disks, locate these folders and back them up to a safe location.
• History Archive State Information: The folder that holds the last archive time
and other archive state information must be copied to a safe location. The folder
name is Archive and it is located at:
...\Documents and Settings\All Users\Application Data\ABB\IM\Archive
Copy the entire folder.
• Reports: Save any report template files created in Microsoft Excel, DataDirect,
and/or Crystal Reports ®. Also save report output files created as a result of
running these reports using the Scheduling Services.
• Desktop Trends: Back up trend display, ticker display, and tag explorer files.
– Ticker files are located at:
...\Documents and Settings\~username\My Documents\ABB Industrial
IT\Inform IT\DesktopTrends\Ticker Files
– Trend Files are located at:
...\Documents and Settings\~username\My Documents\ABB Industrial
IT\Inform IT\DesktopTrends\HTML
– Tag Explorer files are located at:
...\Documents and Settings\~username\ApplicationData\ABB Industrial
IT\Inform IT\Desktop Trends
• Display Services: Back up the directories for custom users, as well as display
and user element definitions.
...\Program Files\ABB Industrial IT\Inform IT\DisplayServices\Server\Data
Save the user-built .svg and .uet files.
• DataDirect: Back up custom text files for object, object type, and attribute menus
used on the DataDirect windows. The files are located in:

102 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba

...\Program Files\ABB Industrial IT\Inform IT\Data Direct\etc.


Save the user-built text files.
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

4.5.3 Basic History Service Data


On nodes that have the Basic History installed, stop the Service Provider of all
the nodes, and back up the Basic History Service data. The backed up data will
be restored on the new system after the upgrade.
To save Basic History Service data:
1. Stop the Basic History Server from the Service Structure by the following
procedure:
a. Open a Plant Explorer Workplace.
b. Use the Structure Browser to open the Service Structure.
c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service Group Definition aspect.
e. Click the Configuration tab.
f. Clear the Enabled check box and click Apply.
2. Use Windows Backup (not the 800xA Backup) or manually copy the folder to
a safe location to backup the files in the following directory:
...\OperateITData1\History\{provider ID}
Refer to Pre-Upgrade Procedure Steps to go to the next pre upgrade step depending
on the installed system.

2PAA111695-600 G 103
104 2PAA111695-600 G
5 Post-Upgrade Procedures 5.1 Post-Upgrade Procedure Steps

5 Post-Upgrade Procedures

The 800xA System and software require steps to be done after performing the upgrade.
Perform the applicable procedures in the order presented based on the installed system.

5.1 Post-Upgrade Procedure Steps


Click the proper link to go directly to the post-upgrade procedure based on the installed
system.
• Compare the Number of Aspects and Objects
• Reconfigure Aspects Created By System Extensions
• Configure Hot key for the New Find Tool
• Correct Alarm and Lock Indication in Faceplates
• IEC 61850 Connect
• Customized Alarm Priority Mapping Aspects
• Reconfigure Group Displays
• Configuring Alarm Property Server Service
• Device Management and Fieldbuses
• PROFINET IO Feature Pack 1.2
• 800xA for Advant Master and 800xA for Safeguard
• 800xA for AC 100
• 800xA for DCI
• 800xA for Harmony
• 800xA for AC 870P/Melody
• 800xA for MOD 300

2PAA111695-600 G 105
5 Post-Upgrade Procedures 5.2 Compare the Number of Aspects and Object

• PLC Connect
• Asset Optimization
• PC, Network and Software Monitoring
• PC, Network and Software Monitoring Device Library
• 800xA for Harmony and AC 870P/Melody Connectivity Server Node Update
• SMS and e-mail Messaging
• Batch Management
• Basic History Service
• Information Management
• Desktop Trends
• Calculations Service
• Scheduling Service (Application Scheduler)
• 800xA for AC 800M
• Control Builder M Projects
• Engineering Studio
• Process Engineering Tool Integration
• Add Autostart Shortcut
• Online Upgrade of a Multisystem Integration System
• Load System Extensions
• Changing Aspect Precedence List
• System Backup
• Consistency Check

5.2 Compare the Number of Aspects and Objects


This topic helps you compare the number of aspects and objects in the system before
the 800xA System Backup and after the 800xA System Restore.
Perform the following procedure to record the number of aspects and objects in the
800xA 6.0 system and compare the number with the 800xA 5.0 SP2 system.

106 2PAA111695-600 G
5 Post-Upgrade Procedures 5.2 Compare the Number of Aspects and Object

1. Open a Plant Explorer Workplace.


2. Use the Structure Selector to open the Admin Structure.
3. Use the Object Browser to navigate to:
Administrative Objects\Domains\system_name, Domain

4. Select Domain Definition in the Aspect List Area.


5. Record the number of objects and aspects listed in the System Size Information
area in the Preview Area.
6. Use the Structure Selector to open the Control Structure.
7. Use the Object Browser to navigate to:
control_network_name, Control Network

of one of the control networks contained in the system.


8. Right-click the Control Structure aspect and select Details.
9. Click the Statistics tab.
10. Record the number of objects listed.
Step 11. through Step 15. are not applicable to systems with only 800xA for
Harmony.
11. Right-click the Control Structure aspect within a controller project of the control
network selected in Step 7..
12. Select Details from the context menu.
13. Record the number of objects listed.
14. Repeat Step 11. through Step 14. for all the controller projects within the control
network.
15. Repeat Step 7. through Step 14. for every control network in the system.
The number of aspects and objects after system restoration should be in the same
range as those recorded during system backup, although there will likely be more.
16. Use the Object Browser to navigate to:
HSE_Subnet name, HSE Subnet

of one of the HSE Subnets contained in the system.


17. Right-click the Control Structure aspect and select Details.

2PAA111695-600 G 107
5 Post-Upgrade Procedures 5.3 Reconfigure Aspects Created By System Ex

18. Select the Statistics tab.


19. Record the number of objects listed.
20. Repeat Step 16. through Step 19. for every HSE Subnet in the system.
21. Use the Object Browser to navigate to:
MB300 name, MB300 Network

of one of the MB 300 Networks contained in the system.


22. Right-click the Control Structure aspect and then click Details.
23. Click the Statistics tab.
24. Record the number of objects listed.
25. Repeat Step 21. through Step 24. for every MB300 network in the system.
The number of aspects and objects after system restoration must be in the same
range as those recorded during system backup, although there will be a few more
aspects and objects recorded in the 800xA 6.0 system.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.3 Reconfigure Aspects Created By System


Extensions
A system upgrade may overwrite the modifications done to certain aspects created
by System Extensions. You may need to reapply the modifications based on the
previous system information. The aspects that are overwritten will be included in the
Configuration Wizard log, which is generated during an upgrade.
To reapply the configuration settings to the aspects created by System Extensions:
1. Identify the aspects that are modified using the Configuration Wizard log
generated during the system upgrade. Figure 5.1 shows an example of the
Configuration Wizard log that contains information about the aspects that are
overwritten during the upgrade.

108 2PAA111695-600 G
5 Post-Upgrade Procedures 5.3 Reconfigure Aspects Created By System Ex

Figure 5.1: Configuration Wizard Log

2. Use the Aspect Directory node retained from the 800xA 5.0 SP2 System to know
the configuration changes that were overwritten during the upgrade. With the
help of the Find tool and the GUID obtained from the Configuration Wizard log,
navigate to the modified aspects in the 800xA 5.0 SP2 System.
3. Analyze the aspects in the 800xA 5.0 SP2 System for any modifications. Based
on the analysis, redo the same modifications in the 800xA 6.0 System, if required.
Not all modifications to the aspects listed in the Configuration Wizard log need
to be reapplied after an upgrade. You can ignore certain messages such as the
following, if listed in the Configuration Wizard log:
Tue Aug 26 02:11:37 2014: [Object Type Structure]Object Types/
Control System/AC 800M\/C Connect/CBM_Signals/CBM_DINTOS:
Function Parameters {5090672F-82AD-4D4D-BEE1-E134ADB1455A}:
{471E37E4-8ABA-4B0F-81D4-7FFFBD762E8D}

Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending


on the installed system.

2PAA111695-600 G 109
5 Post-Upgrade Procedures 5.4 Configure Hot key for the New Find Tool

5.4 Configure Hot key for the New Find Tool


Perform the following procedure to configure the Ctrl + F hot key for the Find Tool:
1. Open Hot keys aspect for any workplace in the workplace structure.
2. Select Ctrl + F hot key in the hot keys list and then remove.
3. Add the hot key by entering the combination Ctrl + F in the hot key area with
context global and with Action Execute Verb.
4. In Aspect, navigate to the Global verbs aspect in the Web system workplace.
5. From Verb select Show_FindTool. Add the newly Configured Find Tool Hot
key in the hot keys list aspect.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.5 Correct Alarm and Lock Indication in Faceplates


To correct Alarm and Lock indication in Faceplates, perform the following on Primary
Aspect Server node:
1. Open Plant Explorer Workplace.
2. Navigate to: Graphics Structure > Graphics Tools VB6 > Special
3. Delete AlarmControl aspect of Aspect Category Graphic Element.
4. Delete LockControl aspect of Aspect Category Graphic Element.

110 2PAA111695-600 G
5 Post-Upgrade Procedures 5.6 IEC 61850 Connect

Figure 5.2: Correct Alarm and Lock indication in Faceplates

Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending


on the installed system.

5.6 IEC 61850 Connect


Handling of IET/CCT projects, CCT600, IET600, and PCM 600 projects are not
described here as they are external tools contributing to the IEC 61850 workflow.
They do not reside on the 800xASystem nodes.

5.6.1 Upgrade CET Project


Upgrade of CET OPC Server Project from System 800xA 5.0 SP2 is a two-step
process.
1. Upgrade CET project to System 800xA 5.1.
2. Upgrade CET project from System 800xA 5.1 to System 800xA 6.0.

Upgrade CET Project to System 800xA 5.1


Import the System 800xA 5.0 SP2 project into System 800xA 5.1 using CET Tool
and export it. This upgraded project is used in next step.

2PAA111695-600 G 111
5 Post-Upgrade Procedures 5.6 IEC 61850 Connect

Upgrade CET project from System 800xA 5.1 to System 800xA 6.0
To upgrade the Backup for CET OPC Server Project to new version, perform the
following:
1. From CET Menu, click File > Open / Manage Project.
2. In Open / Manage Project dialog, click Import Project.
3. Browse .pcmp file for CET OPC Server Project backup to be imported.
4. In Open / Manage Project dialog, select the project under Projects made with
previous product versions.
5. Click Open Project.

Figure 5.3: Upgrading CET Project

6. In Project Conversion Wizard dialog, click Next.


7. In Select Version dialog, select new version and click Ok.
For revision release, the Select Version window will list versions 3.x.

112 2PAA111695-600 G
5 Post-Upgrade Procedures 5.6 IEC 61850 Connect

8. Click Next and wait until the project conversion is complete.


9. Click Finish to initiate the CET OPC Server project conversion.
10. Import CET Event Categories.
The CET Event Categories are not available in the upgraded project in CET
version 6.0.x. To import the CET Event Categories, perform the following:
If the project is upgraded from System 800xA 5.1 FP4 or later Feature Packs,
ignore the Step a. through Step d. to import the CET Event Categories.
a. In the CET Tool, Open the upgraded Project.
b. Open Event Template Tool from Computer Node context Menu.
c. Click Open Template and then browse ...\Program Files (x86)
\ABB\61850 OPC Server to import CETEventCategories.xml.
d. Ensure the Overwrite existing Definitions in import option is selected
during import.
This will update only default Event Classes with Event categories. Condition
category and Simple Event category of User Defined Event Classes should
be updated accordingly by the user.
11. Perform the following to Update/Reload of the upgraded project in CET Tool.
a. Right-click on Computer Node.
b. Select Management.
c. Click Update & reload configuration.
12. Restart IEC 61850 Connectivity Server Node.
13. Perform the following steps after Primary and secondary IEC 61850 Connectivity
servers are restarted.
a. In Plant Explorer Workplace, navigate to Service Structure > Event
Collector, Service.
b. Perform an Upload for all IEC61850 Alarm and Event Service Groups.
c. Navigate to Library Structure > Alarm & Event > Alarm Collection
Definitions, Alarm Collection Definition.

2PAA111695-600 G 113
5 Post-Upgrade Procedures 5.7 Customized Alarm Priority Mapping Aspect

d. Verify all IEC61850 Alarm Collection Definition Objects. If any Category


Group is uncategorized, then manually categorize the group using respective
Alarm Collection Definition Aspect.
For details on applying the categories, refer to System 800xA IEC 61850 Connect
Configuration (9ARD171387*).
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.7 Customized Alarm Priority Mapping Aspects


Some customized Alarm Priority Mapping Aspects may have been overwritten during
the upgrade. Recreate the Alarm Priority Mapping Aspects using the data recorded
during Customized Alarm Priority Mapping Aspects in Pre-Upgrade Procedures.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.8 Reconfigure Group Displays


New Group Display aspects that are created and configured in the Object Type
Structure on the object types and instances in System 800xA 5.0 SP2 will work
correctly even if there is more than one aspect with the same name but each aspect
has a different Aspect Category.
Configured Group Display aspects that existed in the Object Type Structure and
on the object types and instances in System 800xA 5.0 SP2 should have their Aspect
Categories reconfigured for the aspects to display correctly. (This is required for the
reference to an aspect to be stored along with its Category ID.)
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.9 Configuring Alarm Property Server Service


Alarm Property Server Service needs to be configured manually for Primary Aspect
Server after upgrading the system.
1. Navigate to Service Structure > Services > Alarm Property Server, Service.
2. Create a new Service Group.

114 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

3. Create a new Service Provider with name: Alarm Property Server on node
<Primary Aspect Server node name>.
4. Navigate to Service Provider Definition Aspect.
5. In the Configuration tab, select the Primary Aspect Server node in the drop-down.
6. Click Apply.
Alarm Property Server Service for other Aspect Servers is handled automatically
during Deploy.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.10 Device Management and Fieldbuses


Ensure that all the DLW Services in the DLW Server (Primary Aspect Server) are
started in 800xAService account.

Figure 5.4: DLW Services on Primary Aspect Server

2PAA111695-600 G 115
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

5.10.1 Restore Device Types


Third party software, such as Device Type Managers for the Device Type must be
reinstalled because the hard drive of the 800xA System node has been reformatted.
The following steps for Fieldbus Device Types need to be carried out on the Primary
Aspect Server node.
Starting with 800xA 6.0, the restore of the Device Types must be done only on
the Primary Aspect Server node. The Device Types will be copied to the clients
after the restoration is complete on the Primary Aspect Server node.
If the system contains FOUNDATION Fieldbus Device Types, check the following
before proceeding to the next step:
• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Object Type Structure > FF Libraries.
• Check to see if there is more than one entry of FF H1 Device Library, FF
Object Type Group.

• If there is more than one entry, perform FF Upload once so there is only one
instance of FF H1 Device Library, FF Object Type Group present. If
there is only one entry, proceed to the next step using the Device Library
Wizard.
1. Start the Device Library Wizard. Select:
ABB Start Menu > ABB Industrial IT 800xA > Device Mgmt > ABB Device
Library Wizard
If the Device Library Wizard - Client has not been connected to the Device Library
Wizard - Server, navigate first to:
Device Library Wizard Administration > Connect Client
and follow the Device Library Wizard Procedure.
2. Select the Enable Trace File check box as shown in Figure 5.5.

116 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.5: Enabling the Trace File

3. Click Main Menu to open the main menu of the Device Library Wizard.
4. Navigate to Device Type Administration > System Restore Wizard
5. Select the second option in the System Restore Wizard(1) as shown in Figure
5.6 and click Next.

2PAA111695-600 G 117
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.6: System Restore Wizard (1)

6. Select the first option in the System Restore Wizard(2) as shown in Figure 5.7
and click Next.

Figure 5.7: System Restore Wizard (2)

7. Enter the path to the device types in the next screen in the wizard as shown in
Figure 5.8, and click Next.

118 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.8: Path to Device Types

8. Click Next to confirm the extract of device types as shown in Figure 5.9.

Figure 5.9: Device Types to be Extracted - Confirmation Dialog

9. Click Next on the Selection Summary screen as shown in Figure 5.10.

2PAA111695-600 G 119
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.10: Device Types to be Extracted - Selection Summary

10. Click Next to re-install the device types as shown in Figure 5.11.

Figure 5.11: Re-install Device Types

11. Click Finish to complete the procedure to extract and re-install device types on
the Primary Aspect Server as shown in Figure 5.12.

120 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.12: Selection Summary

The device types on the Primary Aspect Server can be transferred to the client nodes
in one of the following two ways:
• Device types installed in Device Library Wizard server gets automatically copied
to client node on invoking the Device Library Wizard as shown in the Figure
5.13.

Figure 5.13: Synchronizing Device Types in Client

• Using the Synchronize option in the Device Library Wizard Administration


window as shown in the Figure 5.14.

2PAA111695-600 G 121
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.14: Object Type Transfer Progress

5.10.2 Device Management PROFIBUS & HART


AC800M Connect and AC800M High Integrity system extensions must be loaded
before loading PROFIBUS Device Integration Library - Basic and HART Device
Integration Library - Basic system extension. Therefore, install AC800M Connect
and AC800M high Integrity also when installing Device Management PROFIBUS
and HART.
After the system upgrade, perform the following to compress the aspect data using
the Data Compression Tool:
1. Double-click and open the Data Compression Tool from the following location:
C:\ProgramFiles(x86)\ABBIndustrialIT\EngineerIT\FieldbusBuilder\bin\DMAspectDataCompression.exe
The Data Compression Tool is opened as shown in Figure 5.15.
The callouts in Figure 5.15 represent the corresponding steps in this procedure.

122 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.15: Data Compression Tool

2. Select Control Network on the Data Compression Tool.


3. Expand the Control Network group and select a project or a controller from the
list.
4. Click BrowsePath to browse and select a folder location to save the .csv file.
5. Click Compress to compress the aspect data.
A message will be displayed stating the actual number of device instances in the
project and the actual number of device instances that are compressed using the
tool as shown in Figure 5.16.

2PAA111695-600 G 123
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.16: Data Compression Details Message

The Data written successfully in the following path: <path specified


in Step 4.> will be displayed at the bottom of the tool upon successful completion
of aspect data compression as shown in Figure 5.17.

Figure 5.17: Successful Completion of Device Types Compression

6. Click Exit.

124 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

OPC Server PROFIBUS & HART


After system upgrade, PH OPC service providers may be reconfigured. For more
information on configuration of PROFIBUS & HART devices (Fieldbus Builder
PROFIBUS/HART, OPC Server, DTM’s and Device Type Objects in 800xA), refer
to System 800xA Device Management PROFIBUS & HART Configuration
(3BDD011934*) manual.
This step must be performed after project upgrade as mentioned in 800xAfor AC
800M Post-upgrade procedures.

5.10.3 License Count Tool


After the system upgrade, the licenses required for the device types in the new system
must be checked and verified. Perform the following to count and verify the licenses
for the device types in the system:
1. Run the License Count Tool from the following location:
C:\Program Files(x86)\ABBIndustrialIT\EngineerIT\Fieldbus
Builder\bin\LicenseCounting.exe
2. On the License Counting wizard, expand the Root element, select the Control
Network, and then click Count License as shown in Figure 5.18.

Figure 5.18: License Count Tool Wizard

2PAA111695-600 G 125
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

If there is more than one control network, you need to individually select the
network and click Count License to know the number of licenses used per control
network.
A message stating the number of device type instances in the system and the
number of licenses required is displayed as shown in the Figure 5.19.

Figure 5.19: License Count Message

3. Perform the following to verify the number of licenses used in the system:
a. Open a Plant Explorer workplace.
b. Use the structure selector to select the Control Structure.
c. Click Root and select License Usage in the Aspect List area.
d. Check the number of licenses used in the system for the 800xA FIELDBUS
Profibus and Hart feature. Refer to Figure 5.20 for more information.

126 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

Figure 5.20: License Usage Aspect in Control Structure

The number of licenses displayed by the License Count Tool and the number
displayed against the License Usage aspect in the Control Structure must be the
same.

5.10.4 Device Management FOUNDATION Fieldbus


Do not change the IP address of the OPC server FF during the online plant update.
Changing the HSE IP address of the PC changes the HSE Default Gateway entry
in the HSE subnet network configuration dialog, which in turn reboots all CI860
at subsequent configuration downloads.
The different resource ID’s for redundant OPC server FF in System 800xA 5.0
SP2 is changed in System 800xA 6.0. In System 800xA 6.0 a unique Subnet ID
must be used for both redundant OPC server FF. Use the Subnet ID 1 during
planning an upgrade.
Perform the following to complete updating Device Management FOUNDATION
Fieldbus.

2PAA111695-600 G 127
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

1. Update LD 800HSE Linking Devices: Update all LD 800HSE linking devices


to the latest firmware version released for this system environment following the
update procedure described in the user instructions for the particular device.
Refer to Field IT, Foundation Fieldbus Linking Device, LD 800HSE, Version
Table (3BDS009910) in myABB/My Control System for the latest linking device
firmware released for this system environment.
From Downloads Explorer, navigate to:
Control Products and Systems/800xA/Device Management Foundation
Fieldbus/Foundation Fieldbus Linking Device LD 800HSE

2. Check, Save, and Upload FF Libraries:


a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Object Type Structure.
c. Use the Object Browser to navigate to:
FF Libraries, Object Type Group

d. Select FF Management in the Aspect List Area.


e. Click Open Project.
f. Check the libraries for plausibility.
g. Exit Fieldbus Builder FF and save changes if prompted to do so.
h. Return to the Plant Explorer Workplace and select FF Upload in the Aspect
List Area.
i. If the traffic light symbol shows red, click Upload.
The green traffic light symbol indicates that the FF libraries have been
synchronized.
3. Optional: Reconstruct User-made Changes to Library Objects representing FF
Standard Blocks:
This step is only required if changes were made to library objects representing FF
standard blocks.
During upgrade, user-made changes to library objects representing FF
standard blocks have been overwritten. Important substitutions have been
logged.

128 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses

a. If such changes were made, display the substitutions as follows:


• Open a Plant Explorer Workplace.
• Use the Structure Selector to open the Object Type Structure.
• Use the Object Browser to navigate to:
FF Libraries, Object Type Group

• Select FF Upload in the Aspect List Area.


• Select Library Merge Logger tab and read the log.
b. For reconstructing user-made changes, reapply the changes to the library
objects manually.
4. Check, Save, Commission, and Upload the HSE Subnet.
Perform the following procedure for each HSE Subnet.

a. Open a Plant Explorer Workplace.


b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to HSE Subnet.
d. Select FF Management in the Aspect List Area.
e. Click Open Project.
f. Check to see if the configured HSE subnet ID is used for the OPC Server
FF configuration in FF Network > Properties and modify it if required.
g. Check whole project for plausibility.
h. If required, perform device assignment for all linking devices LD 800HSE.
Typically, no device assignment is lost during the upgrade.
i. If required, perform precommissioning/commissioning for all objects for
which this is necessary (discernible from engineering status). A
precommissioning may be required if the firmware has been changed.
To assign all H1 devices in one step, use the Assign all devices function from the
HSE Subnet context menu: Object > Assign all devices...
For downloading use the online dialog from the HSE Subnet context menu: Object
> Online Dialog...

2PAA111695-600 G 129
5 Post-Upgrade Procedures 5.11 PROFINET IO Feature Pack 1.2

j. Exit Fieldbus Builder FF and save changes if prompted to do so.


k. Return to the Plant Explorer Workplace and select FF Upload in the Aspect
List Area.
l. If the traffic light symbol shows red, click Upload HSE Subnet.
The green traffic light symbol indicates that the HSE Subnet has been
synchronized.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.11 PROFINET IO Feature Pack 1.2


Some settings on CI871 are reset to default values when performing the upgrade of
PROFINET IO Feature Pack 1.2 to 800xA 6.0. The following are affected:
• Default Gateway
Check the CI871 settings after upgrade and enter the previous values if the settings
are changed.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.12 800xA for Advant Master and 800xA for Safeguard


Perform the following post upgrade procedure steps for 800xA for Advant Master
and 800xA for Safeguard.
• Copy the Advant Master Controller Licenses.txt.

5.12.1 Copy the Advant Master Controller Licenses.txt


Perform the following on the Primary Aspect Server in the 800xA 6.0 System:
• Copy the following updated file from the safe location:
Advant Master Controller Licenses.txt

to the default location in the 800xA 6.0 system:


...\Program Files (x86)\ABB 800xA\AC 400 Connect\Licenses

130 2PAA111695-600 G
5 Post-Upgrade Procedures 5.12 800xA for Advant Master and 800xA for S

5.12.2 Update the Configuration Files


For each Connectivity Server, compare the following files saved in a safe location
during the 800xA for Advant Master pre upgrade phase:
• AdvDsMasterAdapter.csv
• AdvMbAeOPCServer.csv
with the installed version of the files at the following location:
...\Program Files (x86)\ABB 800xA\AC 400 Connect\Bin.
If any customization was done to the old files, update the installed version of the files
with the corresponding changes.

5.12.3 Copy the DATHR Files


Perform the following on each Connectivity Server node:
1. Copy the saved files from the safe location:
• DATHR1.CD
• DATHR2.CD
• DATHR3.CD
to the following folder in the Connectivity Server:
...\ProgramData\ABB\AC400Connect\AdvantBase\Data\
RTA\Init\

5.12.4 Reconfigure RTA Board Control Aspect Settings


If the RTA board IP is configured different than the default IP (172.16.168.50),
change the RTA board IP in the registry of Advant Connectivity Server before
proceeding.
Path: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services
> PU410 > Parameters > slvBoard
Change the IP in string IpAddress.
1. Open the MB 300 RTA Settings dialog box in Configuration Wizard and
reconfigure:
• MB 300 Node and Network Numbers.

2PAA111695-600 G 131
5 Post-Upgrade Procedures 5.13 800xA for AC 100

• Check 800xA as Clock Master (REVERSED_SYNC_MODE) in case the


time synchronization key REVERSED_SYNC_MODE was previously
enabled.
2. If redundant cables are supervised between PU410 and the computer.
a. Open Plant Explorer Workplace.
b. Navigate to RTA Board Control aspect in: Control Structure > MB300
Network > MB300 RTA Board (Of upgraded Advant Connectivity Server
node)
c. Check PU410 redundant cable supervision option.
3. Always restart the RTA board.
4. The Audible property must be 0 for events and 1 for alarms 800xA for Advant
Master version 4.1 SP1 RU6 and newer. Refer to System 800xA Configuration
(3BDS011222*) for configuration of audible alarms.
Safeguard standardevent 300 - 326 does not comply with this rule before 800xA
for 800xA for Advant Master Version 5.0 SP2. The Event numbers where the
Audible property should be changed from 1 to 0 are:
• EVENT302.
• EVENT305.
• EVENT310.
• EVENT312.
• EVENT320.
• EVENT321.
• EVENT322.
• EVENT325.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.13 800xA for AC 100


Perform the following post upgrade procedure steps for 800xA for AC 100:

132 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100

5.13.1 Configuration and Operation


All software products for using the Advant Controller 100 Series in an 800xA System
are now installed and ready to use. Refer to 800xA for AC 100 Configuration and
Operation (3BDS013989*) or more information on configuration and operation; for
example, procedures to connect an 800xA System to an AC 100 OPC Server. Refer
to the Data Access topic in System 800xA Configuration (3BDS011222*) to connect
via DCOM, and to use the DCOMCNFG tool to set the DCOM security setting.

5.13.2 Time Synchronization and Daylight Saving Time


There are a number of ways to configure the clock synchronization for an Advant
Fieldbus 100 network along with a network of System 800xA products. The Advant
Fieldbus 100 network has its own clock synchronization. Refer to Advant Fieldbus
User Manual (3BSE000506*) for functionality and configuration details, and in the
corresponding reference manual for the data base elements of each controller.
A System 800xA network consists of one or several servers and a number of clients
connected via TCP/IP. Synchronization of that network of servers and clients in itself
is supported by the 800xA System. This is described in System 800xA Administration
and Security (3BSE037410*). One clock server synchronizes the other servers and
clients in the network.
The AC 100 OPC Server can function as the time master or as a slave versus the
Advant Fieldbus 100 network.
The information in the remainder of this topic represents the recommended
Configuration.
All servers and clients in an Advant Fieldbus 100 network must be configured to the
same time zone and must be time synchronized.
It is recommended that you set-up an 800xA Connectivity Server, that hosts the AC
100 OPC Server, as time master. It will be time master both for the System 800xA
network as well as for the Advant Fieldbus 100 network.
Any adjustment of the network time is done (from the time server) using the Windows
Date and Time dialog box in the Windows Control Panel.
To set up the 800xA System for such a configuration:
1. Set up the selected server node as the time server. If there are several server
nodes, set up the others to request the correct time from the time server.
2. Set up all the workstation nodes to accept the clock synchronization.

2PAA111695-600 G 133
5 Post-Upgrade Procedures 5.13 800xA for AC 100

3. Make sure that the Automatically adjust clock for Daylight Saving Time
setting is selected is set on all server and workstation nodes.
4. Set the time synchronization of the AC 100 OPC Server to Master according to
the instructions in AC 100 OPC Server Configuration and Operation
(3BDS013988*).
5. Set the time synchronization of other Advant OPC Servers for Advant
Fieldbus 100 to None according to the instructions in AC 100 OPC Server
Configuration and Operation (3BDS013988*).
6. Those nodes will collect their time from the time server.
The result of this solution is as follows for time tagged data:
• Alarm data and Historical data are stored according to UTC time. The local time
does not matter.
• Alarm and History data presentation manages the presentation of data with the
local time.

5.13.3 Installation Verification (Optional)


After performing the software and hardware installation, it is recommended that you
verify that the AC 100 OPC Server has been properly installed. To accomplish this:
1. Check that the AC 100 OPC Server utilities are available from the Start menu.
Select:
ABB Start Menu > ABB Industrial IT 800xA > 800xA for OCS Systems >
AC 100 > About AC 100 OPC Server
For more information on ABB Start Menu, refer to System 800xA Tools
(2PAA101888*).
2. Select:
Control Panel > Programs and Features
to view if ABB AC 100 OPC Server is properly listed here.
3. Check the Windows Device Manager (Figure 5.21) and make sure that the CI527A
device and driver are working properly.
a. The Device Manager is started by: Control Panel > Device Manager
b. To find the CI527A Driver select: View > Devices by type

134 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100

c. Expand the AF100 icon.

Figure 5.21: Device Manager

d. Right-click ABB AF100 CI527A - PNP and then click Properties to open
the ABB AF100 CI527 - PnP Properties dialog box.
e. In the Details tab, select Device instance path in the Property drop-down
(Figure 5.22) to find the correct version of the CI527A Hardware IDs: This
must contain DEV_0862 as shown in Figure 5.22.

2PAA111695-600 G 135
5 Post-Upgrade Procedures 5.13 800xA for AC 100

Figure 5.22: CI527A Version Information

4. Verify that the services


• ABB AC 100 CI52X Manager
• ABB AC 100 OPC Server
• ABB AC 100 VFI Server
are listed and running by selecting:
Control Panel > Administrative Tools > Services
5. Use the Details tab in Windows Task Manager to verify that the following
processes are running, and that the User name is 800xA Service account:
• wiaopc.exe
• wiaci526.exe
• wivserver.exe

136 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100

5.13.4 Product Verification


After performing the initial configuration of the AC 100 OPC Server, it is
recommended that you verify that the software has been properly configured and that
the system has contact with the Advant Fieldbus 100 network. To do this:
1. Verify that the About OPC Server box is shown correctly by starting the About
AC 100 OPC Server dialog box (Figure 5.23):
ABB Start Menu > ABB Industrial IT 800xA > 800xA for OCS Systems >
AC 100 > About AC 100 OPC Server

Figure 5.23: About AC 100 OPC Server Dialog Box

2. Verify that the board is operational and all stations are reachable by viewing the
AF 100 Diagnostics dialog box (Figure 5.24). For more information about the
Diagnostics function, refer to AC 100 OPC Server Configuration and Operation
(3BDS013988*).
Select:
ABB Start Menu > ABB Industrial IT 800xA > 800xA for OCS Systems >
AC 100 > AF 100 Diagnostics

2PAA111695-600 G 137
5 Post-Upgrade Procedures 5.13 800xA for AC 100

Figure 5.24: AF 100 Diagnostics Dialog Box

3. Check Windows Event Viewer to ensure that no fatal errors are reported from
the ABB AC 100 OPC Server. Select:
Control Panel > Administrative Tools > Event Viewer >
Windows Logs > Application
4. If the recommended verifications show problems, check the hardware of the
CI527A by doing the following:
a. Check that the green P (power) is lit.

138 2PAA111695-600 G
5 Post-Upgrade Procedures 5.14 800xA for DCI

b. Check that the yellow RX (receive) LED is lit (if other stations on the Advant
Fieldbus 100 network are up and running).
c. When the Advant Fieldbus 100 Interface is started, check that the yellow
TX (transmit) LED starts to blink.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.14 800xA for DCI


5.14.1 Deleting Additional Control Network
1. Delete the newly created DCI Control Network Object.
a. Open Plant Explorer Workplace.
b. Navigate to Control Structure > Root.
c. Identify and delete the newly created DCI Control Network object.
Newly created object will have the name in format: DCI%DciOpcDaID%, Symphony
DCI OPC Server Network.

Figure 5.25: Deleting newly created DCI Control Network Object

2PAA111695-600 G 139
5 Post-Upgrade Procedures 5.14 800xA for DCI

5.14.2 Configure a Single NIC Interface to the DCU


The DCI control network must be Class A (127.0.0.0 or less) and must have a
subnet mask of 255.0.0.0.

AbbDciSelectNetwork.exe modifies the registry. You must have Administrative


rights to use this program.
Most 800xA for DCI installations use the ABB ECC MUX to communicate with
Distributed Control Unit (DCU) controllers in order to take advantage of the redundant
network. However, a single NIC may be used to communicate with the DCUs if
redundancy is not an issue. If a single NIC is used, then it must be designated as the
one used for the DCI Control Network (CNET) as follows:
If the ABB ECC MUX Redundant Ethernet driver has not been installed, configure
the path for the network services by performing the following steps:
1. Select:
ABB Start Menu > ABB Industrial IT 800xA > 800xA OCS Systems > DCI
> DCI Select Network
For more information on ABB Start Menu, refer to System 800xA Tools
(2PAA101888*).
The AbbDciSelectNetwork dialog box will appear (Figure 5.26). The X in the
first row indicates that no network is selected.

Figure 5.26: AbbDciSelectNetwork Dialog Box

140 2PAA111695-600 G
5 Post-Upgrade Procedures 5.15 800xA for Harmony

2. Choose the network that 800xA for DCI will use by clicking on the row of the
desired network adapter.
Choose the network by IP address. The physical name is provided for help in the
Description column.
3. Click OK. The network is now selected.
4. Restart the node to activate the selection.
5. The next time the network service is run, it will automatically default to the last
chosen network. If desired, repeat Step 1. through Step 4. to choose a new
network.

5.14.3 Enable DCI OPC AE Service Group(s)


1. Open Plant Explorer Workplace.
2. Navigate to Service Structure > Event Collector, Service and expand it.
3. Select the DCI AE Service Group(s).
4. Select Enabled check box, if it is not already checked.
5. Click Apply.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.15 800xA for Harmony


5.15.1 Harmony API Configuration
The Harmony API software is installed on every Harmony Connectivity Server during
Deploy.
To configure Harmony API, run the Harmony API Configuration utility on each
Harmony Connectivity Server node.
1. Double-click the shortcut on the Windows Apps Screen created during installation.
It is listed in ABB Symphony Plus.
2. Click Help to view the ICI to Computer Interface Setup guide provided with the
HarmonyAPI. Follow the instructions in the guide to configure the Harmony
API for the ICI type present on the node.

2PAA111695-600 G 141
5 Post-Upgrade Procedures 5.15 800xA for Harmony

Figure 5.27: Harmony API Configuration Dialog Box

5.15.2 Harmony Configuration Server Information


Use the following procedure to upload the 800xA for Harmony Configuration Server
Information that was saved during the 800xA for Harmony Pre-Upgrade phase into
the Aspect Directory.
1. Open the Plant Explorer window and navigate to the
Harmony OPC Server Network object in the Control Structure.
2. Select the Uploader aspect.
3. On the Import tab, select Browse, and navigate to the location of the Harmony
ConfigServer Export file that contains the tags for the Harmony Server object
assigned to this Harmony OPC Server Network object.
4. Select the Tag Table for the primary Harmony Server tag object associated with
the Harmony OPC Server Network object.
5. Select Start Import.

142 2PAA111695-600 G
5 Post-Upgrade Procedures 5.15 800xA for Harmony

6. Repeat Step 1. through Step 5. for each 800xA for Harmony OPC Server
Network object in the system.

5.15.3 Restart Connectivity Server


After the upload of the 800xA for Harmony Configuration Server Information, perform
the following procedure to restart the Connectivity Servers:
1. Open Plant Explorer and navigate to Service Structure > Services > Harmony
Executive, Service > Basic, Service Group > Harmony Executive Service
Provider.
2. Select the Service Provider Definition aspect as shown in Figure 5.28.

2PAA111695-600 G 143
5 Post-Upgrade Procedures 5.15 800xA for Harmony

Figure 5.28: Restart of Harmony Executive Service

3. Click the Configuration tab and clear the Enabled check box.
4. Click Apply and wait for the current status of the service to change to Undefined.
5. Select the Enabled check box and wait for the current status of the service to
change to Service.
6. Restart the Connectivity server.

144 2PAA111695-600 G
5 Post-Upgrade Procedures 5.16 800xA for AC 870P/Melody

From System Version 6.0 onwards, the 800xA for Harmony Configuration Server
nodes are no longer required. If the system being upgraded contained any
standalone 800xA for Harmony Configuration Servers, use the following procedure
to remove the Harmony Executive Service Providers for those nodes:
1. Open Plant Explorer and navigate to Service Structure > Services >
Harmony Executive, Service > Basic, Service Group.
2. Select the Harmony Executive Service Provider configured for the
standalone Harmony Configuration Server node.
3. Press the Delete key or right-click the object and select Delete.
4. Click OK when the Delete Object dialog is displayed.
5. Repeat Step 1. through Step 4. for each previously configured standalone
800xA for Harmony Configuration Server node.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.16 800xA for AC 870P/Melody


Restore existing backups for project specific changes (if available) for: (Refer to
800xA for AC 870P/Melody in Pre-Upgrade Procedures for more information.)
• DHCP Server Configuration.
• ETC Host files for 800xA for AC 870P/Melody Connectivity Servers.
• Changes in the Default Object Types.
• ConvDB changes of the Configuration Server.
Perform the following post upgrade procedures for 800xA for AC 870P/Melody.
• Restore 800xA for AC 870P/Melody Information.

2PAA111695-600 G 145
5 Post-Upgrade Procedures 5.16 800xA for AC 870P/Melody

5.16.1 Restore 800xA for AC 870P/Melody Information


The Configuration Server database restore procedure from a 800xA 5.0 SP2 system
to a 800xA 6.0 system is a two-step procedure, because of the incompatibility
issues between the Microsoft SQL Server versions on both the systems. The backup
must be first restored on a 800xA 5.1 system and then on the 800xA 6.0 system.
To restore the backup on a 800xA 6.0 system, perform the following steps:
1. Install a 800xA 5.1 Melody Configuration Server node.
Note: It is not required to have an 800xA System or to perform any post
installation or configuration steps.
2. Restore the backup taken from the 800xA 5.0 SP2 System on the newly
installed 800xA 5.1 Melody Configuration Server node.
3. Back up the Configuration Server database on the 800xA 5.1 System.
4. Restore the backup taken from the 800xA 5.1 System on the 800xA 6.0 system.
Perform the following procedure to restore 800xA for AC 870P/Melody information:
1. Log in to the 800xA Installing User account (or the 800xA Service account) on
the Configuration Server node.
2. Restore the 800xA for AC 870P/Melody Configuration information that was
saved during 800xA for AC 870P/Melody in Pre-Upgrade Procedures..
a. Select Restore Configuration from the Start menu.
b. Click Connect in the Melody Connect Configuration Backup/Restore
window.
c. Enter the name of the Melody Configuration Server database backup file in
the Backup File field.
d. Click Restore.
e. If a prompt appears indicating that the system version does not match the
backup version, click OK.
f. If the message Services must be stopped, REBOOT system now then
restart this application! is displayed, restart the node and repeat Step
a. through Step e..
g. Click Exit when the restore operation is complete.

146 2PAA111695-600 G
5 Post-Upgrade Procedures 5.17 800xA for MOD 300

If there are specific faceplates in use (process industries or utilities), the faceplates
must also be upgraded. Refer to the faceplate related documents for further
instructions.

5.16.2 Additional 800xA for AC 870P/Melody Configuration Steps


Perform the following configuration steps after adding each 800xA for AC
870P/Melody Connectivity Server to the 800xA System.
Refer Base Configuration Section of 800xA for AC 870P/Melody Configuration
(3BDD011741*) to Configure
1. Internet Explorer Security Settings.
2. Configure Access Rights.
3. Adjust PNSM configuration.
4. Enable the Melody AutoConfigurator service in Plant Explorer > Service
Structure.
If the upgrade of the Melody Connectivity Server and the Melody Configuration
Server were not performed on the same calendar day, there may be a problem with
starting the upgraded Connectivity Server in the 6.0 system.
The following is the workaround if the upgrade of the servers were not performed
on the same calendar day:
Remove the subscription added to the Configuration Server by performing a backup
of the upgraded Configuration Server before starting the upgraded Connectivity
Server.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.17 800xA for MOD 300


Rename MOD 300 Event Collector Service Group(s) and Service Providers as per
the instructions in Renaming MOD 300 AE Service Group and Service Provider
Names.

2PAA111695-600 G 147
5 Post-Upgrade Procedures 5.18 PLC Connect

If the RTA board IP is configured different than the default IP (172.16.168.50),


change the RTA board IP in the registry of MOD 300 Connectivity Server before
proceeding.
Path: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services
> PU410 > Parameters > slvBoard
Change the IP in string IpAddress.
1. Reverse_Time synch will be disabled following the re-installation of PAS. If the
Connectivity Server node sets the time on the Real-Time Accelerator
Board(RTAB), Reverse_Time_Synch must be enabled.
a. Select:
ABB Start Menu > ABB Industrial IT 800xA > PAS Management >
PAS Control
b. Click Advanced, advanced options dialog appears.
c. Select Comm Settings to open a new window.
d. Select Enabled from the drop-down menu for Reverse Time Sync.
e. Click OK.
2. If any objects were customized, those changes must be implemented again
onobjects delivered with 800xA for MOD 300 Version 6.0.
3. Update the registry settings previously recorded. Refer to 800xA for MOD 300
Configuration (3BUR002417*).
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.18 PLC Connect


Perform the following post upgrade procedures for PLC Connect.

5.18.1 Restoring the Pretreat dll


To restore the Pretreat dll:
1. If the PLC Connect Communication Server Pre Treatment function is being used
in the application, copy the Pretreat dll file (Pretreat3.dll or Pretreat4.dll) from
the backup location to the same folder as it was backed up from on the PLC
Connect Connectivity Server. If the default folder is used, that location is:

148 2PAA111695-600 G
5 Post-Upgrade Procedures 5.18 PLC Connect

...\ABB Industrial IT\Operate IT\PLC Connect\Bin


2. Register the Pretreat dll file (refer to System 800xA PLC Connect Configuration
(3BSE035041*) for more information).
3. Restart the PLC Connect Connectivity Server for the changes to take effect.
4. Restore the project and source files for the Pretreat dll.

5.18.2 Update the Sattbus Configuration


Perform the following if the Sattbus protocol is used for any of the controllers:
1. Select the PLC Controller Configuration aspect for the controller that uses Sattbus
protocol and click Edit Driver.
2. Configure the Common System Settings and click OK.
3. Restart the Connectivity Server.

5.18.3 Redeploy the PLC Connect Configuration


To redeploy the PLC Connect configuration:
1. Use the Structure Selector to open the Control Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the first Generic Control Network object.
3. Select Deploy in the Aspect List Area.
4. Press the SHIFT key and click Deploy in the Preview Area to ensure that a full
deploy is done.
5. The deploy begins and the progress is displayed in the Preview Area. The deploy
is completed when Deploy ended is displayed.
6. Repeat the procedure for any additional Generic Control Network objects.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

2PAA111695-600 G 149
5 Post-Upgrade Procedures 5.19 Asset Optimization

5.19 Asset Optimization


Use the following procedure after updating Asset Optimization. Perform only the
steps applicable to the system.
1. Asset Monitoring:
Asset Monitoring directories must be restored on every Asset Optimization Server
node defined in the system.
a. If Runtime Asset Monitors are being used in the system, restore the Runtime
Asset Monitor data directory (DeviceRunTimeMSLogicStore) to the
following directory:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
The saved data contains the Runtime Asset Monitor data present at the time of the
save. Use the Runtime Asset Monitor faceplate to reset the Asset Monitors by
adding the lost time to their accumulated run time or with some known values
based on other records. Ignore any alarms occurring during the backup.
b. If XY Profile Deviation Asset Monitors are being used in the system, restore
the XY Profile Deviation Asset Monitor data directory
(XY_Reference_Profiles) to the following directory:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\Asset
Optimization\AssetMonitorEnvironment\Bin
c. If Counter Check Asset Monitors are being used in the system, restore the
Counter Check Asset Monitors data directory named:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}

from safe media. This directory exists for each AO Server in the system.
These directories are located in:
<install drive>:\OperateITData\AoEng\<AO Server ID>\
AmCat
Where each <AO Server ID> directory represents one AO Server instance
from which the directory:
{66E71F7B-90D6-4E62-9881-38388B24CBDF}

was originally saved from. The <AO Server ID> directory name is formatted
as two consecutive GUIDs, for example:

150 2PAA111695-600 G
5 Post-Upgrade Procedures 5.19 Asset Optimization

{F9C150F5-2929-4A12-BC28-E00ED6DB1585}{B925E77F-2A82-41C6-A981-FAB4386D5701}.

2. Maximo Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access Maximo Server Version 6.2.
The Maximo Integration information (Maximo Equipment ID and Maximo
Credentials aspects) must be restored on all Asset Optimization Server nodes.
Reference the Service Structure for the Asset Optimization Server.
a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
to configure ECS.
b. If the MxDef files were customized, restore the MxDef files to the following
directory:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\MaximoDef\
Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
for more information on MxDef files.
c. Restore the AOMaximoModel file to the following location if the ECS model
was customized:
...\program files (x86)\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
d. Ensure that the ABB Maximo Connectivity system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
3. SAP/PM Integration:
cpmPlus Enterprise Connectivity Version 4.0 (ECS 4.0) must be installed in order
to access SAP Server Version 4.7.
The SAP/PM Integration information (SAP Equipment ID and SAP Credentials
aspects) must be restored on all Asset Optimization Server nodes. Reference the
Service Structure for the Asset Optimization Server.

2PAA111695-600 G 151
5 Post-Upgrade Procedures 5.19 Asset Optimization

a. Refer to System 800xA Asset Optimization Configuration (3BUA000118*)


to configure ECS.
b. If the SAPDef files were customized, restore the SAPDef files to the
following directory:
...\Program Files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\SAPPMDef
c. Restore the AOSAPModel file to the following location if the ECS model
was customized:
...\program files\ABB Industrial IT\Optimize IT\Asset
Optimization\AOECSConnector\ECSDefinitions
Refer to System 800xA Asset Optimization Configuration (3BUA000118*)
for more information on SAPDef files.
d. Ensure that the ABB SAP Connect system extension is loaded.
The pending fault reports residing in the system can be restored to the following
directory structure:
...\OperateITData\OptaoACDs
Restore the entire OptaoACDs folder.
4. DMS Calibration Integration.
The DMS Calibration Integration approach is changed in 800xA 5.0 SP2. Upgrade
of DMS Calibration Integration is not supported. Reconfigure the DMS Calibration
Integration based on an engineered solution.
Contact ABB technical support for more information.
5. Asset Monitors that are assigned (use the Configure option drop-down list box
on the Asset Monitor Instance on an Object) to a particular AO Server object
and Asset Optimization Server aspect (by Object name:Aspect name pair), will
not be correctly configured after the upgrade. The AOServer property will be
unconfigured and the following error message will appear:
Unable to resolve AO Server for this Asset Monitor configuration

This must be resolved before the Asset Monitor Logic can be loaded into an AO
Server:Asset Optimization Server for execution. Refer to the Object Type
Structure for Asset Optimization, Object Type Group:AO Server, Object Type.

152 2PAA111695-600 G
5 Post-Upgrade Procedures 5.20 PC, Network and Software Monitoring

6. After a restore of a 800xA 5.0 SP2 system, the Asset Optimization Server
(Monitor Server/Engine) is running. The AO Server tab of the Asset Monitoring
Server aspect will show a status of good: AM Engine running.
a. Clicking the Asset Monitors tab and selecting AMs assigned to this AO
Server will show that the values in the Status column are NOT Loaded,
enabled.

b. Click Load all AMs to reload all enabled Asset Monitors assigned to this
AO Server.
The Enable Write Access check box must be selected in the Asset Monitor Data
Source aspect before loading Runtime Asset Monitors into the AO Server. Refer
to System 800xA Asset Optimization Configuration (3BUA000118*) for more
information.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.20 PC, Network and Software Monitoring


5.20.1 Restarting the Event Collector Service
Restart the event collector service for the following Products:
• SMS and E-mail Messaging.
• AC 800M Status Monitoring.
• Asset Optimization.
• PC, Network and Software Monitoring.
Perform the following steps to see events in the Event Log:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to:
Event Collector,Service > ABB 800xA System Message Server,Service
Group > Event Collector_ABB 800xA System Message Server_NodeName,
Service Provider

2PAA111695-600 G 153
5 Post-Upgrade Procedures 5.20 PC, Network and Software Monitoring

where NodeName is the node where the service is registered which is generally
the Aspect Server node.
4. Select Service Provider Definition in the Aspect List Area.
5. Clear the Enabled check box and click Apply.
6. Select the Enabled check box and click Apply.
7. Repeat Step 4. through Step 6. for:
Event Collector,Service > ABB 800xA Soft Alarm OPC Server,Service
Group > Event Collector_ABB 800xA Soft Alarm OPC Server_NodeName,
Service Provider.

This will restart the Event Collector_ABB 800xA System Message, Server_NodeName
service, and Event Collector_ABB 800xA Soft Alarm OPC Server_NodeName
services and the Event Log will display all events.

5.20.2 Configure the Service Provider and Service Group


Perform the following steps on the PC, Network and Software Monitoring Server
node.
1. Use the Structure Selector to open the Service Structure in the Plant Explorer
Workplace.
2. Use the Object Browser to navigate to the:
Services > OpcDA_Connector, Service > SG_IT Server

object. If there is no object to navigate to, skip to Step 12. (letter l, not number
1).
3. Open the OPCDA_Provider_<servername> object and double-click on the Service
Provider Definition aspect.
4. On the Configuration tab, clear and select the Enabled check box and click
Apply. The Current field should change to Service.
5. Use the Structure Selector to open the Control Structure.
6. Use the Object Browser to navigate to the IT Server object.
7. Double-click OPC Data Source Definition in the Aspect List Area.
8. Click on the Service Group drop-down menu and select the SG_IT Server.
9. Click on the OPCDA_Provider_<servername> which was configured in Step 3..

154 2PAA111695-600 G
5 Post-Upgrade Procedures 5.20 PC, Network and Software Monitoring

10. Click Apply.


11. Skip to Migrate the IT Asset Monitors.
12. Use the Structure Selector to open the Control Structure.
13. Use the Object Browser to navigate to the IT Server object.
14. Double-click OPC Data Source Definition in the Aspect List Area.
15. Select New.
16. Click Add and select the appropriate Service Provider from the list.
17. Click OK twice.
18. Click Apply.

5.20.3 Migrate the IT Asset Monitors


If Asset Optimization and PC, Network and Software Monitoring were installed on
the original system, then the following must be done for any existing IT Assets that
had IT Asset Monitors configured for them.
1. Use the Find Tool in the Plant Explorer Workplace to locate all the IT Asset
Monitor aspect instances in the Control Structure.
2. Right-click on each of the found aspects and select Goto Object.
3. Open the IT Device Manager aspect and click Generate to recreate the IT Asset
Monitor.
4. Repeat Step 3. for each object in the Find list.
5. Use the Object Browser to navigate to:
Root, Domain > Asset Optimization, Asset Optimization > AO Server
1, AO Server

6. Select Asset Optimization Server in the Aspect List Area.


7. Select the Enabled check box in the AO Server tab and click Apply.
Click Load all AMs in the Asset Monitors tab.
Basic Computer Monitoring will not upgrade properly from a previous version to
the current version. Use the Basic Computer Monitoring Configuration Tool to
recreate the configuration.

2PAA111695-600 G 155
5 Post-Upgrade Procedures 5.21 PC, Network and Software Monitoring Dev

Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending


on the installed system.

5.21 PC, Network and Software Monitoring Device


Library
Perform the following post upgrade procedure for PNSM Device Library:
1. Copy the MOF files from the safe location to the directory, if MOF files were
backed up:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\MOFS
2. Copy the Custom Asset Monitor dlls from the safe location to the following
location for object types with Custom Asset Monitors:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\Asset Monitoring\Bin
Use the Register.dll bat file present in the Object Type to register this dll
automatically.
3. Copy the Windows Management Instrumentation (WMI) repository to the
directory if the files were backed up. Perform the following steps to back up and
restore the the WMI repository.
a. Right-click Computer and select Manage. Computer Management is
displayed.
b. Expand Configuration on the left panel. Select WMI Control.
c. Right-click WMI Control and select Properties. The Properties dialog box
is displayed.
d. Click Backup/Restore Tab.
e. Click Back Up Now..., Specify a name for your backup file window is
displayed.
f. Enter the name of the backup file and click Save.

156 2PAA111695-600 G
5 Post-Upgrade Procedures 5.22 800xA for Harmony and AC 870P/Melody Co

Figure 5.29: WMI Backup File

g. Click Restore Now..., Specify a backup file to restore window is


displayed.
h. Select the file and click Open to restore the backed up file.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.22 800xA for Harmony and AC 870P/Melody


Connectivity Server Node Update
The following procedure is only applicable to 800xA for Harmony and
AC 870P/Melody Connectivity Server nodes.

2PAA111695-600 G 157
5 Post-Upgrade Procedures 5.22 800xA for Harmony and AC 870P/Melody Co

Do not perform this procedure on a server node that is running Shadow OPC
Server as AfwService.

5.22.1 Determining the Node Running ShadowOPC Server as AfwService


To identify the node that is running ShadowOPC Server as AfwService:
1. Refer to System 800xA PC, Network and Software Monitoring Configuration
(3BUA000447*) and verify that the Shadow OPC Service is configured.
2. Open a Plant Explorer Workplace.
3. Use the Structure Selector to open the Control Structure.
4. Use the Object Browser to navigate to:
IT Server, IT OPC Server Network

5. Select OPC Data Source Definition in the Aspect List Area.


6. Click View in the Preview Area to launch the Service Group Definition dialog.
7. Select service provider from the Providers list.
8. Click View to launch the Service Provider Definition dialog.
9. The Node in the Configuration tab is the name of the node that is running
ShadowOPC Server as AfwService.
10. Close all dialogs.

5.22.2 Applying the Update


Perform the following procedure on all 800xA for Harmony and 800xA for Melody
Connectivity Server nodes.
1. Insert the System Version 5.0 SP2 Released Documents CD into the drive.
2. Use Windows Explorer to locate and copy ABBShadowOPC.exe.config in the
Updates directory on the CD.

3. Use Windows Explorer to navigate to the following directory on the local hard
drive:
...\Program Files (x86)\ABB Industrial IT\Optimize IT\PC, Network and Software
Monitoring\bin
4. Make a backup of the existing ABBShadowOPC.exe.config file.

158 2PAA111695-600 G
5 Post-Upgrade Procedures 5.23 SMS and e-mail Messaging

5. Paste the file copied in Step 2. to the hard drive location navigated to in Step 3..
6. Restart the node.
7. After the restart, use Windows Task Manager to verify the KeepAliveApp.exe
is not in the list of processes.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.23 SMS and e-mail Messaging


Reconfigure the GSM Device hardware information recorded in the save operation
during the pre-upgrade procedures.
It may be necessary to stop and start the Messenger Server Service in the Service
Structure after the SMS and e-mail Messaging restore operation.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.24 Batch Management


5.24.1 Activate Batch Redundancy
If redundant Batch Servers are used, Batch Redundancy must be activated after
upgrading both the Batch Servers to System 800xA 6.0.
For detailed procedure to activate Batch Redundancy, refer Batch Management Section
in System 800xA Post Installation (2PAA111693*).

5.24.2 Batch Management Post Installations


Wait until the Primary Batch Server node is in primary mode by viewing a P in
the Windows Taskbar of the selected Primary Batch Server. The length of time
for the P icon to appear depends on the size of configuration (number of batch
units) and the number of nodes in a system. There is generally no configuration
in the system at this point, so the P icon should appear within couple of minutes.

2PAA111695-600 G 159
5 Post-Upgrade Procedures 5.24 Batch Management

5.24.3 Shutdown Script


The batch_shutdown.bat script shuts down the Batch application properly and must
be installed on all Batch Servers. To install this script:
1. Click Start and type gpedit.msc in the text box and then click OK.
2. Select Computer Configuration > Windows Settings > Scripts
(Startup/Shutdown).

3. Double-click Shutdown.
4. Click Add and then Browse.
5. Select: <DRIVE>:\Program Files(x86)\ABB Industrial IT\Produce
IT\Batch\bin\batch_shutdown.bat

in the Script Name field and click Open.


6. Click OK twice to complete the installation and close the Group Policy dialog
box.

5.24.4 Batch Management Toolbar


Batch Management provides a Toolbar that contains buttons for the Batch Overview,
Batch History Overview, and Equipment Overview dialog boxes. If desired, refer to
System 800xA Batch Management Configuration (3BUA000146*) for information
about enabling this Toolbar.

5.24.5 Set Date and Time for Batch Servers


Batch Primary and Redundant servers require a specific time format for the service
account. All other users on the batch server and other nodes can keep the US - English
defaults.
Perform the following to verify/modify the formats for the <800xA Service Account>
on the batch servers:
1. Login to the <800xA Service Account> on the Primary/Secondary Batch server.
2. Open Windows Control Panel.
3. Click Region, Region dialog appears. Perform the following to set the formats
for Date and Time:
a. Click the Format tab.

160 2PAA111695-600 G
5 Post-Upgrade Procedures 5.25 Basic History Service

b. The default value for the Short Date format is M/d/yyyy. Change the Short
Date format to MM/dd/yyyy and click Apply.
c. The default Short time format is hh:mm tt. Change the value to HH:mm and
click Apply.
4. Click Apply.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.25 Basic History Service


Restore the Basic History Service data as follows. Perform this procedure on every
node where the Basic History Service is running.
1. Stop the Basic History Server from the Service Structure by the following
procedure:
a. Open a Plant Explorer Workplace.
b. Use the Structure Browser to open the Service Structure.
c. Select the Basic History, Service > Basic, Service Group.
d. Select the Service provider object that is running on this node.
e. Select the Service Provider Definition aspect.
f. Click the Configuration tab.
g. Clear the Enabled check box and click Apply.
2. If it is necessary to keep historical data for the time since the upgraded system
was started, copy the current Basic History log files in the following directory:
...\OperateITData1\History\{provider ID}
to a temporary directory.
These files will be inserted by using the Archive Tool.
3. Delete all files under:
...\OperateITData1\History\{provider ID}
4. Restore the files from the backup of Basic History Service Data to:
...\OperateITData1\History\{provider ID}

2PAA111695-600 G 161
5 Post-Upgrade Procedures 5.26 Information Management

5. Start the Basic History Service Provider from the Service Structure.
6. If Step 2. was performed:
a. Open the AdvHtArchiveTool located by default in the following directory:
C:\Program Files(x86)\ABB 800xA\Base\bin\
AdvHtArchiveTool.exe
b. Use the File/Select/Open Archive command and browse to the directory
containing the history log files.
c. Open the Action/Insert Data into Logs command.
d. Accept the default values in the Time Selection dialog box.
e. Click OK to start the insertion of the saved data to the logs.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.26 Information Management


Perform the following post upgrade procedures for Information Management. Files
only have to be restored when a new node is being loaded from backups. The Oracle
upgrade and database conversion procedure will upgrade existing or restored files.
When creating the Oracle instance, select I am upgrading or restoring from a
SV3.x or newer database backup in the Configuration File Options dialog box
to prevent the wizard from creating a history database. This will prevent History
from starting until after the History Database is restored.
The procedures presented here are different than those in System 800xA Post
Installation (2PAA111693*). Unless otherwise noted, perform the procedures
presented here.
When creating the database, it is possible to select small, medium, or large for the
database size. If it is not known what the size of the database will be, select large.
PAS is not initialized at this point in the process, and it should not be.

162 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management

5.26.1 Reconfiguring the IM Log Configuration


When the procedure is followed, the IM service group is preserved and all Log
Configurations should have a valid setting. If there is not a valid setting, a previous
step was not followed and this procedure will correct the problem.
After restoring a system containing IM logs, the Service Group for the IM log template
configuration might be missing. The IM log templates must be checked, and if the
Service Group is missing, a new Service Group must be configured.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Library Structure.
3. Use the Object Browser to navigate to:
History Log Templates, History Log Template Library > Default Log
Templates, History Log Template Library

4. Select a log template.


5. Select Log Template in the Aspect List Area.
6. Select the Log Definition tab in the Preview Area.
7. If the Service Group in the Service Group drop-down list box is missing, it must
be reconfigured. The Service Group drop-down list box contains all History
servers defined in the system. Use this list to specify the server where this log
will reside.
8. Repeat this procedure for all of the log templates.

5.26.2 Information Management History Backup/Restore Utility


Select the Information Management History Backup/Restore utility from:
ABB Start Menu > ABB Industrial IT 800xA > Information Mgmt > History >
IM Backup and Restore
to restore the Information Management History database and synchronize the Aspect
Directory contents with the current Information Management History database
configuration.
During the restore, the existing database is dropped, and a new one is created. Mount
points and additional table spaces are created based on the database being restored.
Oracle data is imported, and the file-based property logs are copied back into the

2PAA111695-600 G 163
5 Post-Upgrade Procedures 5.26 Information Management

system. Unless a different mount point is specified, the History database will be
restored to its original location (its location prior to being backed up).
The History database can be restored from any drive, including any mapped network
drives. The restore utility will first search a specified location for zipped archives
matching a specific name and fitting the form name-drive.zip (such as histDB-C.zip,
histDB-A.zip, and histDB-D.zip), and will then restore the compressed database files
contained within the archives to their respective original locations (their locations
prior to being backed up).

Considerations
When restoring the History database, make sure the disk is ready and available on
the node on which the procedure is to occur. Also, ensure that no applications are
accessing the Oracle database. The log file should be checked after the restore
operation to make sure that the restore operation completed successfully.

Running the Information Management History Backup/Restore Utility


To restore a backed up History database:
This procedure can also be performed by using the pasgui command in the Run
dialog box.
1. Verify that the ABB Process Administration Service (PAS) is set to manual in
the Services Control Panel (run Services.msc from the Run dialog box). Stop the
service if it is running.
If PAS is not in the manual mode, it is possible the log configuration has been
modified and will not match the IM backup. If this is the case, the 800xA System
Restore may have to be repeated to correct the problem.
2. If it is suspected that the Inform IT History Service Provider has not stopped, it
can be stopped now by selecting the Inform IT History Service Provider for this
node in the Service Structure, selecting the Configuration tab on the Service
Provider Definition aspect, disabling Enabled, and clicking Apply.
3. Ensure that no third party applications access the Oracle database during the
restore operation.
4. Before restoring the database, it is necessary to create an Oracle database to
restore the backup.
a. Start the Oracle Instance wizard using:

164 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management

ABB Start Menu > ABB Industrial IT > Information Mgmt > History > IM
Oracle Instance Wizard
b. Create a database to restore by selecting I am upgrading or restoring from
a SV3.x or newer database backup. Be sure to select the correct size for
the database. If the previous system had more than four million entry message
logs, select large, for one to four million select medium, and for less than
one million select small.
If a database previously existed, drop it and create the correctly sized database.

5. Restore the database. Select:


ABB Start Menu > ABB Industrial IT 800xA > Information Mgmt > History >
IM Backup and Restore.
6. Verify Restore configuration from a backup file(s) is enabled in the Welcome
to IM Historian Backup and Restore Utility dialog box.
7. Click Next. IM Historian Database Restore dialog box appears (Figure 5.30).

Figure 5.30: IM Historian Database Restore Dialog Box

2PAA111695-600 G 165
5 Post-Upgrade Procedures 5.26 Information Management

8. Specify the location of the backup files in the Path of IM historian backup:
field (Figure 5.30).
If new mount points need to be specified for file-based logs and/or a new Oracle
tablespace definition file, click Browse. This will be required if the partition letters
where the IM data is stored have changed.
9. Click Next. The HsBAR Output Window appears.
10. Select the Automatically close upon completion check box.
11. Monitor the progress in the Progress Status area of the IM Historian
Backup/Restore Utility window. Ignore the error messages indicating errors
deleting aspect.
Following the message indicating the import is complete, the database conversion
tool will run automatically. Feedback will be provided in the HsBAR window.
Shortly after the message indicating the database conversion is complete, the
history synchronization tool will run automatically. Again, feedback will be
provided in the HsBAR window.
The restore of the system requires an instance that matches the size of the database
being restored. When creating the instance, be sure to select Small, Medium, or
Large based on the size of the message log in the backup being restored. Select
Large if the size is not known. If the wrong size is selected, the restore operation
may fail with the Oracle Error Message 1652 - Unable to extend tmp segment
in tablespace temp. Repeat the restore with the correct instance settings if the
error occurs. This will not happen if the correct database for upgrade is selected.
For example, if the database is using a 12 million entry OPC message log, the
large option should be selected. This will insure that enough TEMP and rollback
are created.
12. Click Finish when a message stating the execution is complete is displayed as
shown in Figure 5.31.

166 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management

Figure 5.31: Execution is Complete Message

If the Progress Status dialog box has warning messages with possible solutions as
indicated in Figure 5.32, read the possible solutions carefully, then click Finish and
proceed with the solution that best fits your problem. Refer to the Information
Management Release Notes for further guidelines.

Figure 5.32: Progress Status Dialog Box

2PAA111695-600 G 167
5 Post-Upgrade Procedures 5.26 Information Management

5.26.3 Restoring Other Information Management Related Files


There are several other files related to Information Management that need to be
restored as part of total system restore.
• History Archive Data: For each archive device, copy the appropriate folders
from the safe media to the location specified by the Device Filename. If the disk
configuration has changed from the previous system to the new system (i.e. letter
designations for disks have changed: C, D, E, etc.), check the archive device
configurations to make sure the Archive Path specification points to the correct
disk drive and directory, as shown in Figure 5.33. Repeat for the backup archive
path if configured.

Figure 5.33: Checking the Archive Path Specification

• History Archive State Information: Stop the Industrial IT Archive service in


the Service Structure. Copy the folder that holds the last archive time and other
archive state information from the safe media to:
c:\ProgramData\ABB\IM\Archive
• Reports: Restore any report template files created in Microsoft Excel, DataDirect,
and/or Crystal Reports. Also restore report output files created as a result of
running these reports using the Scheduling Services. The function references in
the old excel report templates need to be updated after upgrading to 800xA 6.0.

168 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management

Refer to System 800xA Information Management Data Access and Reports


(3BUF001094*) for the steps to update the function references.
• Desktop Trends: For each user, restore the trend display, ticker display, and tag
explorer files, if any to the following location:
C:\Users\<user>\AppData\Roaming\ABB Industrial IT\Inform IT\Desktop Trends
• Display Services: Restore the directories for custom users, as well as display
and user element definitions to the following path:
C:\ProgramData\ABB\IM\Display\Data
• DataDirect: Restore custom text files for object, object type, and attribute menus
used on the DataDirect windows to the following path:
C:\ProgramData\ABB\IM\DataDirect\etc

5.26.4 Starting PAS


1. Open the Services Control Panel (run Services.msc from the Run dialog box),
set the ABB Process Administration Service (PAS) to Automatic and start it, if
not already configured properly.
2. Open the Information Management Configuration Assistant (ABB Start Menu >
ABB Industrial IT > Information Mgmt > IM Configuration Assistant) and
perform any incomplete steps.
3. Select the Basic History Service Provider object for the Information Management
node in the Service Structure in the Plant Explorer.
4. Select the Service Provider Definition aspect.
5. Select the Configuration tab.
6. Clear the Enabled option.
7. Click Apply.
8. Select the Enabled option.
9. Click Apply.

2PAA111695-600 G 169
5 Post-Upgrade Procedures 5.26 Information Management

5.26.5 Updating Archive Logs


Absolute names are now included as part of the archive storage. Archive links now
use an absolute reference that is independent of the name of the log. Run the archive
maintenance to update the _RST log references to use the absolute log reference.
This procedure is not necessary if archives are not being used.

This procedure only needs to be performed one time no matter how many
Information Management nodes are in the system.
1. Open a Plant Explorer Workplace.
2. Use the Object Browser to navigate to:
IM Node > Archive Service Provider

3. Click Archive Service Aspect in the Aspect List Area.


4. Click Maintenance in the Preview Area to launch the Maintain Archive
References dialog box.
5. Click Validate Archive Logs.
6. Run a consistency check on all log configurations.

5.26.6 Information Management Maintenance


Perform this procedure on all Information Management Server nodes.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Node Administration Structure.
3. Use the Object Browser to navigate to:
All Nodes, Node Group > IM Node > Inform IT History_IM Node,
Service Provider > Inform IT History Object, Inform IT History
Object

4. Select Inform IT History Control in the Aspect List Area.


5. Expand the Maintenance tree in the Preview Area and select Synchronization.
The Inform IT History Manager shown in Figure 5.34 appears in the Preview
Area.

170 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management

Figure 5.34: Inform IT HIstory Manager

6. Click Check Names.


7. A blank dialog box should appear. If it does, click OK. If it does not click
Resynchronize Names.
8. Click Check Synchronization.
9. A blank dialog box should appear. If it does, click OK. If it does not click Force
Synchronization.

5.26.7 Running hsDBMaint -stagger


It is recommended to run hsDBMaint -stagger for all IM configurations. The defaults
are adequate for most configurations. If the average request rate is near or over 1,000
per minute, refer to System Information Management, Configuration (3BUF001092*)
for hsDBMaint -stagger recommendations.
1. Open an Administrator Windows Command Prompt and enter hsDBMaint
-stagger.

2. When the operation is complete run the Process Administration Service (PAS)
utility on the Information Management Application Server node. Open:

2PAA111695-600 G 171
5 Post-Upgrade Procedures 5.27 Desktop Trends

ABB Start Menu > ABB Industrial IT 800xA > PAS Management > PAS
Control
This opens the Process Administration Service dialog box.
3. Click Restart All to restart all processes under PAS supervision.
4. Click Close when the dialog box indicates that all processes are restarted.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.27 Desktop Trends


Perform the following to solve the compatibility issue related to the migrated Desktop
Trend files from earlier versions of 800xA:
To resolve the issue a compatibility tag needs to be added to the saved Trend file.
1. Open the Desktop Trend HTML file with Notepad. The first few lines looks as
follows:

2. Insert the following line of text between the <HEAD> and <TITLE> tags in the
HTML file.
<META http-equiv="X-UA-Compatible"
content="IE=EmulateIE8,requiresActiveX =true">

172 2PAA111695-600 G
5 Post-Upgrade Procedures 5.28 Calculations Service

3. Save the HTML file and exit Notepad. The Desktop Trend file should now display
properly.

5.28 Calculations Service


Calculations that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Calculations dialog box. Refer to the section on Calculations
in System 800xA Information Management Data Access and Reports (3BUF001094*).
To enable the Calculations Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Calculations Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.29 Scheduling Service (Application Scheduler)


Schedules that were disabled prior to the upgrade must be enabled by selecting the
Enabled check box in the Scheduling dialog box. Refer to the section on Scheduling
in System 800xA Information Management Data Access and Reports (3BUF001094*).
To enable the Scheduling Service:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Select the Scheduling Service Object.
4. Select the Service Definition aspect.
5. Click the Configuration tab.
6. Select the Enabled check box and click Apply.

2PAA111695-600 G 173
5 Post-Upgrade Procedures 5.30 800xA for AC 800M

Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending


on the installed system.

5.30 800xA for AC 800M


Use the following procedure to restore 800xA for AC 800M information:
1. Control Builder stores its settings (systemsetup.sys) on disk in the following
directory:
...\ABB Industrial IT Data\Engineer IT Data\Control Builder M
Professional

Add the file saved on the safe media to the system.


2. The OPC Server stores configuration files (*.cfg) and settings (systemsetup.sys)
on disk. Add the files saved on the safe media to the system. The systemsetup.sys
file is located in:
...\ABB Industrial IT Data\Control IT Data\OPC Server
for AC 800M

The configuration files are stored in the Files folder in the same location.
1. Restore OPC configurations by selecting File > Load Configuration in the OPC
Server Panel.
Remember to enable autoloading of the configuration and provide the correct path
to the file.

5.30.1 Load 800xA for AC 800M High Integrity Extension


If AC 800M HI (PM865HI) controllers are used in System 800xA 5.0 SP2, AC 800M
High Integrity Extension is to be loaded manually after upgrade. Perform the following
procedure, to load the system extension manually:
1. Start the Configuration Wizard from the primary Aspect Server node.
Select: ABB Start Menu > ABB Industrial IT 800xA > System >
Configuration Wizard
2. Navigate to open the System Extension Load dialog box:
System Administration > Select System > System Extension Load
The System Extension Load view appears with the available system extensions
listed in the left pane.

174 2PAA111695-600 G
5 Post-Upgrade Procedures 5.31 Control Builder M Projects

3. Select AC 800M High Integrity in the list in the left pane and move it to the
list in the right pane by clicking >. To move all the system extensions from the
left pane to the right pane, click >>.
4. Click Next and the Apply Settings dialog box appears.
5. Click Finish to load all system extensions.

5.31 Control Builder M Projects


After upgrading a configuration containing one Engineering and one Production
system to 800xA 6.0, the Control Builder M projects in the two systems must be
made identical using the Import/Export tool, Engineering Repository, or by
recreating the Engineering System using Backup/Restore before engineering work
is restarted. Otherwise there will be a lot of false differences on the AC 800M
aspects reported in the import difference report when moving solutions between
the systems.
After an upgrade to 800xA 6.0, if you may need to work with objects having VB
PG aspects, ensure to start Control Builder as an Administrator. Right-click the
tool and select Run as Administrator... from the context menu. The tasks such
as copy-paste of an object having VB PG aspects may not be possible in Control
Builder if you are not logged-in as an Administrator.
800xA 6.0 has introduced a new (major) version (6.0-0) of BasicHWlib. The 800xA
5.0 Service Pack 2 of BasicHWlib (5.0-2) can coexist with the new version (6.0-0)
in the 800xA System, and must be used if any controllers are going to stay with the
firmware from 800xA 5.0 Service Pack 2.
The Control Builder project upgrade will be started automatically the first time the
project is opened. It can also be explicitly triggered by starting an empty Control
Builder and selecting:
Tools > Maintenance > Upgrade Project
During the upgrade, a message appears asking users it they want to use the new (6.0-0)
or old (5.0-2) BasicHWLib version for the controllers in the project. If the intention
is to upgrade controller firmware the new version should be selected. If the intention
is to not upgrade controller firmware the old version must be selected.

2PAA111695-600 G 175
5 Post-Upgrade Procedures 5.32 Engineering Studio

5.31.1 AC 800M Fingerprint Tool


Run the AC 800M Fingerprint tool on the upgraded system to collect data about the
firmware versions, CPU load, hardware revisions, and so on. Compare the data
obtained on the upgraded system with that of the data obtained from the old system
to check if there were any changes during the upgrade process.
Refer to System 800xA Control AC 800M Configuration (3BSE035980) for more
information on the AC 800M Fingerprint tool.

5.31.2 Start Values Analyzer Tool


Run the Start Values Analyzer tool after an upgrade and collect the data regarding
the variables and the associated attribute values. Compare the results with the data
collected while performing the Pre-upgrade procedures. If certain variables are set
to the initial value during an upgrade, it can be reset to the last configured value based
on the collected data before the upgrade.
Refer to System 800xA Control AC 800M Configuration (3BSE035980) for more
information on the Start Values Analyzer tool.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.32 Engineering Studio


Perform the following post upgrade procedures for Engineering Studio:
1. From the Engineering Workplace, navigate to Object Type Structure >
Functional Planning > Settings > Function Upgrade.
2. Select the following options:
• Convert Diagram References/Variables from Aspect Objects to Symbol
Objects.
• Check and Repair AES Variable Table.
• Remove EBService Node from the Service Structure.
• Function Designer Diagram Upgrade.
3. Click Apply.
4. Click Run Upgrade.

176 2PAA111695-600 G
5 Post-Upgrade Procedures 5.32 Engineering Studio

5.32.1 Convert Diagram References/Variables from Aspect Objects to


Symbol Objects
In the 800xA 5.1 System, Diagram References and Diagram Variables are by default
created as Symbol Objects. This is not true for Diagram References and Diagram
Variables created during upgrade from 800xA 5.0 SP2 Systems. Convert the references
and variables from Aspect Objects to Symbol Objects using the conversion function
described in System 800xA Engineering, Function Designer (3BDS011224*).

5.32.2 Check and Repair AES Variable Table


The Check and Repair AES Variable Table (Applications, Controllers,
Diagrams/SCMs, and Diagram (CM Types) function can be used to:
• Correct possible inconsistent data used for display of online values and external
cross references.
Executing the Check and Repair AES Variable Table procedure makes the
environment support work for Function Designer.

5.32.3 Remove EBService Node from the Service Structure


The upgrade deletes the Engineering Base Service from Service Structure.

5.32.4 Function Designer Diagram Upgrade


The Function Diagram Upgrade can be carried out from the Engineering Workplace
by navigating to Object Type Structure > Functional Planning > Settings >
Function Upgrade.
Following are the prerequisites for the Function Diagram Upgrade:
• Engineering Workplace Service should be enabled.
• Function Diagram Upgrade must be done with the 800xAInstaller account,
or using an account that is a member of IndustrialITAdmin and local
administrators group.
• Control Builder M projects should be upgraded prior to the Function Diagram
Upgrade.
The setting of the Function Diagram Upgrade in the workplace is as shown in the
Figure 5.35.

2PAA111695-600 G 177
5 Post-Upgrade Procedures 5.32 Engineering Studio

Figure 5.35: Settings of Function Diagram Upgrade

On initiating the Function Diagram Upgrade a new Engineering Workplace opens


up. Function Diagram Upgrade iterates through all the Function Diagrams under
Functional Structure and performs the upgrade.
If the Function Diagram Upgrade terminates for some reason, such as, in-sufficient
memory, then the Engineering Workplace re-starts and the upgrade resumes from the
point where it stopped last.
Following are the changes due to the library update:
The Function Diagram Upgrade process may take several minutes/hours till it is
completed. Engineering Workplace may not be available for performing other
operations.
During the upgrade/update process if a message appears, user needs to intervene and
update as required. The settings dialog box shows the status bar with the current
diagram being upgraded and the progress in percentage (%), see Figure 5.36.

178 2PAA111695-600 G
5 Post-Upgrade Procedures 5.32 Engineering Studio

Figure 5.36: Function Diagram Upgrade

A log is generated and updated during the Function Diagram Upgrade. It can be
accessed from the aspect Function Upgrade Log, or from the temp folder in the C
drive. The location for the log created in C drive is C:\ProgramData\ABB\Engineering
Studio\Function Designer\ logname.log.
For more information on Function Designer Diagram Upgrade refer Appendix B of
System 800xA Engineering, Function Designer (3BDS011224*).

5.32.5 Conversion of Global Variables (Diagram Variables) into


Communication Variables
It is recommended to convert Global Variables (Diagram Variables) of existing
projects into Communication Variables. This is optional.
For more information, refer to Section: Configuration in System 800xA Engineering,
Function Designer (3BDS011224*).
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

2PAA111695-600 G 179
5 Post-Upgrade Procedures 5.33 Process Engineering Tool Integration

5.33 Process Engineering Tool Integration


Use the following procedure after updating Process Engineering Tool Integration:
Restore the backed up data directory (in preparation-step prior to upgrade) to the
installed directory of Process Engineering Tool Integration. Restore the entire Xml
directory contents to:
C:\ProgramData\ABB\Process Engineering Tool Integration\XML
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.34 Add Autostart Shortcut


If it is desired to enable the autostart of the Operator Workplace on client nodes,
perform the following:
1. Login to the client using the user in which autostart needs to be configured.
2. Click ABB Start Menu on desktop.
3. Open ABB Workplace Login window as an administrator (Run as Administrator)
from: ABB Industrial IT 800xA > System > Workplace
4. Select the Workplace from the list of available workplaces.
Click Set as Autostart.

180 2PAA111695-600 G
5 Post-Upgrade Procedures 5.35 Online Upgrade of a Multisystem Integra

Figure 5.37: Configuring Autostart for the Workplace

Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending


on the installed system.

5.35 Online Upgrade of a Multisystem Integration


System
Perform the following to upgrade a Multisystem Integration 800xA System online.
1. Refer to Considerations and Upgrade Flow and perform all steps for the Subscriber
System.
2. Refer to Considerations and Upgrade Flow and perform all steps for each Provider
System where it is required to perform an upgrade.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.36 Load System Extensions


All the required system extensions are loaded into System 800xA 6.0 during upgrade
process. If not, manually load the required extensions.
To load the system extensions manually:

2PAA111695-600 G 181
5 Post-Upgrade Procedures 5.36 Load System Extensions

1. Start the Configuration Wizard from the primary Aspect Server node. Select:
ABB Start Menu > ABB Industrial IT 800xA > System >
Configuration Wizard
2. Open the System Extension Load dialog box by going to:
System Administration > Select System > System Extension Load
3. A view appears with the available system extensions listed in the left pane. Select
the system extension to load in the list in the left pane and move it to the list in
the right pane by clicking >. To move all the system extensions from the left
pane to the right pane, click >>.
4. The red cross, green check mark, and warning icons indicate the status of the
dependency evaluation.
• The green check mark indicates that the system extension must be loaded
first.
• The red cross icon indicates that the system extension can not be loaded
until the one with the green check mark icon is loaded.
• The warning icon indicates that the system extension can be loaded, but that
there is additional information available in the Description frame in the lower
part of the dialog box. The additional information can, for example, be that
the system extension contains aspect types that are not environment aware.
5. If the list in the right pane contains more than one system extension, click Press
header to autosort to sort the system extension load order with regard to
dependencies.
6. All system extensions in the right pane should be marked with the green check
mark or the warning icon.
7. Click Next and the Apply Settings dialog box appears.
8. Click Finish to load all system extensions.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

182 2PAA111695-600 G
5 Post-Upgrade Procedures 5.37 Changing Aspect Precedence List

5.37 Changing Aspect Precedence List


Visual Basic Process Graphics (VBPG) is not supported in System 800xA begenning
System 800xA 6.0. After upgrade, Aspect Precedence list must be changed so that
PG2 has the highest Precedence.
Clicking on a VBPG aspects in System 800xA will generate a license violation
pop-up.

1. Open Plant Explorer Workplace.


2. Navigate to Aspect Precedence List aspect located in:
Library Structure > Preferences & Customizations > Aspect Precedence
Lists > Default Precedence List
3. In the Configuration Tab, ensure that PG2 Aspects have the highest precedence.
If not change it manually.

Figure 5.38: Aspect Precedence List

For more information on changing Aspect Precedence list, refer to Workplace


Configuration section of System 800xA Operations, Operator Workplace
Configuration (3BSE030322*).
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

2PAA111695-600 G 183
5 Post-Upgrade Procedures 5.38 System Backup

5.38 System Backup


Make complete hard disk and 800xA System backups of the upgraded system.
Refer to Post-Upgrade Procedure Steps to go to the next post-upgrade step depending
on the installed system.

5.39 Consistency Check


This topic describes the consistency check performed on the 800xA System.
The following is an overview of the consistency check functionality in the 800xA
System.
• Perform consistency checks both before and after the upgrade.
• The consistency check is continuously improved between releases. If a consistency
error is detected after the upgrade, it does not necessarily mean that the error was
introduced by the upgrade process. It might have been there from the beginning,
but went undetected.
• Try to correct all consistency errors before the upgrade. This will make the
upgrade process easier. Consistency errors may cause the upgrade to either fail,
or continue, but without having done exactly what was intended. Since it is very
difficult to know where the upgrade handling will do changes, it is desirable to
make the system as consistent as possible before the upgrade. It is also good to
keep a system with the old version running so it is possible to go back and do
more corrections in the old system if problems occur during the upgrade.
– However, the upgrade will often work even though there are some remaining
consistency errors. In some cases it is easiest to correct the errors after the
upgrade (because the repair functionality has been improved in the new
release), so it may be worth an attempt at continuing with the upgrade. It is
recommended to keep a list of the detected consistency errors for future
reference.

184 2PAA111695-600 G
5 Post-Upgrade Procedures 5.39 Consistency Check

During the consistency check the following error messages might come from
PROFIBUS Hardware Libraries in system version 5.0 SP2 and later:
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Aspect Category
Definition'. ... : Library Version Definition
[Error] Aspect 'ABB_TFx12_PA 1.2-
0:Hardware Library' contains multiple library
keys. ... : Library Version Definition
[Error] Library key must not be used on
'ABB_TFx12_PA 1.2-0:Object Type
Structure'. ... : Library Version Definition
3 error(s) reported by 1 aspect(s).
1 aspect(s) can be repaired

This will have no impact on system upgrade.


• In 800xA 5.0 SP2 and later, perform the consistency check with the Consistency
Check tool (started by clicking the question mark icon in top right corner of Plant
Explorer Workplace).
• Perform consistency checks on the user-defined libraries in the Object Type
Structure or Library Structure, the Control Project in Control Structure, and
the Functional Structure.
• The general part of the upgrade process consists of importing new versions of
standard libraries, and propagating object type changes to user libraries and user
applications. It is only necessary to correct consistency errors regarding object
type, object type references, and similar configurations for the general part of
the upgrade process to work. Other inconsistencies such as unresolved references
should normally not lead to problems.
– However, special upgrade handling designed by the Functional Areas may
also update the references of aspects, so it is best to correct also broken
references before the upgrade.
– In the Library structure, navigate to Library Version Definition aspect present
in the user defined libraries. Select the Consistency tab and click Check
Consistency. Correct any errors that may appear during the consistency
check.
In System 800xA5.0 SP2 and later, perform the consistency check with the Consistency
Check tool (started by clicking the question mark icon in top right corner of Plant

2PAA111695-600 G 185
5 Post-Upgrade Procedures 5.39 Consistency Check

Explorer Workplace). This instruction only includes the 800xA 5.0 SP2 and later
procedure. Refer to System 800xA Tools (2PAA101888*) for more detailed information
on running the 800xA 5.0 SP2 consistency check.
Perform a consistency check before performing the 800xA System backup. Failure
to do so could result in problems when restoring the system after the upgrade.

If using Asset Optimization, be sure to run the Consistency Check tool and delete
any inconsistent Asset Monitor Control Connection Properties aspects.
Perform the following to perform a consistency check:
1. Open a Plant Explorer Workplace.
2. Click the Consistency Check Tool icon at the top of the Plant Explorer
Workplace to launch the Consistency Check Tool.
Rather than performing Step 3. through Step 6. it is also possible to drag the desired
items to the Consistency Check Tool.
3. Click Add Item to open the Select Item dialog box.
4. Browse to the desired location.
5. Select the desired items (use Ctrl+Click or Shift+Click to select multiple items).
If a subtree is selected, all objects and aspects in the subtree will be selected. If
a library or application is selected, everything in this entity will be selected.
6. Click Add and Close.
7. Click Check.
8. If errors are found, and they are marked Repairable, perform an automatic repair
by selecting Repair Aspect in the context menu.
9. If errors are found that are not automatically repairable, try to manually
reconfigure the aspects to repair the consistency errors.

186 2PAA111695-600 G
A Migrate Redundant Domain Con A.1 Prerequisites

Appendix A Migrate Redundant Domain


Controllers

There may be some 800xA software on nodes (such as 800xA RNRP on the
Domain Controller node) that does not include Process Portal software. The
operating system and 800xA software on these nodes also requires an reinstallation.
This section covers the following:
• Migrating redundant Domain Controllers from Windows Server 2003 to Windows
Server 2012 / Windows Server 2016.
• Replacing server hardware without losing contact with the Active Directory (AD)
and Domain Name Service (DNS).
The order of migration described in this section must be changed when upgrading
800xA Systems with combined Domain Controllers/Aspect Servers. Rather than
upgrading both the Domain Controllers before everything else in the 800xA System,
the first Domain Controller must stay a part of the 800xA 5.0 SP2 Rev E System until
the end of the upgrade, after which it will be migrated with the upgrade of the 800xA
6.0 Primary Aspect Server.

A.1 Prerequisites
The following is required before starting the procedure to migrate the Domain
Controller:
• Must be logged on to the schema master as a member of the Enterprise Admins,
Schema Admins, and Domain Admins groups in the forest root domain.
• Ensure that replication is working throughout the entire forest. Ensure that all
Domain Controllers are up and running and that the schema master has been up
long enough for a complete replication cycle to occur for the Schema partition.
Check Event Viewer for any issues.

2PAA111695-600 G 187
A Migrate Redundant Domain Con A.2 Preparation

A.2 Preparation
Prepare for the migration by ensuring that the following are available:
• Windows Server 2012 / Windows Server 2016 Installation media.
• IP addresses planned for the new servers.
• Firewall disabled on the Windows Server 2003 Domain Controllers as well as
on the new servers.
• Backups/disk images taken on both Windows Server 2003 Domain Controllers.
Firewall must be enabled after the Migration of Domain Controllers is completed.

A.2.1 Preparing a Domain for Windows Server 2012 / Windows Server


2016
Perform the following to identify the domain infrastructure operations master (also
known as flexible single master operations or FSMO) role holder.
• This procedure must be performed on the Domain Controller that holds the
schema master role.
• Administrative credentials: An account that is a member of the Domain Admins
group is required to perform this procedure. Membership in the Enterprise Admins
group is not sufficient to perform this procedure.
Run netdom query fsmo on any Domain Controller to ensure which Domain
Controller hosts the schema master role. Additionally, make a record of the different
roles available.
If all the roles are not hosted by one Domain Controller, ensure to transfer all the
roles to one Domain Controller.
1. Login as a member of the Domain Admins group to the Domain Controller
node that holds the schema master role.
1. Open Administrative Tools > Active Directory Domains and Trusts.
2. Verify that the available Domain Functional Level is set to Windows Server
2003 at minimum. If not, raise the Domain Functional Level to Windows Server
2003 or later.

188 2PAA111695-600 G
A Migrate Redundant Domain Con A.3 Removing the Redundant Domain Controller

3. Verify that the available Forest Functional Level is set to Windows Server 2003
at minimum. If not, raise the Forest Functional Level to Windows Server 2003
or later.
4. Click OK.

A.3 Removing the Redundant Domain Controller


A redundant Windows Server 2003 Domain Controller can be removed using the
Windows interface.
Perform the following to remove the redundant Windows Server 2003 Domain
Controller by using the Windows interface.
• This procedure must be performed on the redundant Windows Server 2003
Domain Controller.
• Administrative credentials: An account that is a member of following group is
required to perform this procedure:
– Domain Admins.
1. Verify that both the Domain Controllers are global catalog servers.
a. Start AD Sites and Services.
b. Navigate to NTDS Settings of one Domain Controller in the left
pane.
c. Right-click NTDS Settings and select Properties to open the NTDS
Settings Properties dialog box.
d. Verify that the Global Catalog check box is selected under the
General tab.
e. Repeat Step b. through Step d. for the other Domain Controller.
1. Under the General tab of the NTDS Settings Properties dialog box, clear the
Global Catalog check box, of the domain controller which is been migrated.
click Apply, and then click OK to continue.
2. Type dcpromo in the Run dialog box and click OK.
3. Click Next in the Active Directory Installation Wizard dialog box.
4. Make no selection in the This server is the last domain controller in the domain
dialog box and click Next.

2PAA111695-600 G 189
A Migrate Redundant Domain Con A.4 Installing an Additional Windows Server

5. Type and confirm a secure password for the local Administrator account in the
Administrator Password dialog box and click Next.
6. Review the information in the Summary dialog box and click Next.
7. Click Finish when the message stating the successful completion of the operation
is displayed.
8. Restart the machine to complete the process.
9. Open Administrative Tools on the Domain Controller that having FSMO roles.
a. Verify that the redundant Domain Controller node has been removed from
Active Directory Users and Computers. If it has not, remove it manually.
b. Verify that the redundant Domain Controller node has been removed from
Active Directory Sites and Services. If it has not, remove it manually.
c. Verify that the redundant Domain Controller node has been removed from
DNS. If it has not, clean all the traces in the Name Server Tab for both
Forward Lookup and Reverse Lookup Zones.
10. Remove the node from the Domain.

A.4 Installing an Additional Windows Server 2012 /


Windows Server 2016 Domain Controller
Perform the following to install an additional Windows Server 2012 / Windows Server
2016 Domain Controller in an existing domain using the Windows interface.
Install the new operating system defined in System 800xA Installation and Upgrade
Getting Started (2PAA111708*) and perform all the procedures related to the
operating system settings, Windows Service Packs, miscellaneous Windows
components installation, other third-party software, network settings, time
synchronization, and Windows updates and hot fixes.
Login as a local administrator to perform the following procedure.

1. Open Windows Control Panel.


2. Double-click Administrative Tools.
3. Double-click Server Manager to launch the Server Manager.
4. Click Add Roles and Features in the Roles Summary.

190 2PAA111695-600 G
A Migrate Redundant Domain Con A.4 Installing an Additional Windows Server

5. Follow the Add Roles and Features wizard till Server Roles dialog box.
6. Select the Active Directory Domain Services check box in the Select Server
Roles dialog box. Select Add Features on the popup that is displayed, and then
click Next.
7. Follow the Add Roles and Features wizard till Confirmation dialog box.
8. Click Install in the Confirm Installation Selections dialog box.
9. In the Installation Results dialog box click Close this Wizard after installation
has succeeded.
Ensure that all networks are disabled except networks that are used for the 800xA
System (Plant Network and/or Control Network).
10. Click the Notification icon in Server Manager dialog box and click
Promote this server to a domain controller.
11. Select Add a Domain Controller to an Existing Domain. Type the Domain
Administrator credentials, select the Domain using the Select button, and then
click Next.
12. Make the following selections in the Domain Controller Options dialog box and
click Next.
• DNS Server: This option is selected by default so that the Domain Controller
can function as a Domain Name System (DNS) server.
• Global Catalog: This option is selected by default. It adds the global catalog,
read-only directory partitions to the Domain Controller, and enables global
catalog search functionality.
• Read-only Domain Controller: This option is not selected by default and
should be kept as it is.
ABB recommends disabling the IPv6 protocol.

If static IPv4 and IPv6 addresses are not assigned to the network adapters, a
warning message box might appear advising the setting of static addresses for
both of these protocols before continuing. If static IPv4 address have been assigned
to the network adapter and the organization does not use IPv6, this message can
be ignored by clicking Yes, the computer will use a dynamically assigned IP
address (not recommended).

2PAA111695-600 G 191
A Migrate Redundant Domain Con A.4 Installing an Additional Windows Server

A message box may appear that indicates that a DNS delegation for the DNS
server could not be created, and that a DNS delegation to the DNS server to ensure
reliable name resolution should be manually created may appear if the option to
install a DNS server was selected. It is not required to create the DNS delegation
if the additional Domain Controller is being installed in either the forest root
domain or a tree root domain. Click Yes and disregard the message if this is the
case.
13. Type and confirm the restore mode password in the Directory Services Restore
Mode Administrator Password dialog box and click Next. This password must
be used to start AD DS in Directory Service Restore Mode (DSRM) for tasks
that must be performed offline.
14. In Additional Options Window, select the Primary Domain Controller for
replication from the drop-down and click Next.
15. Type or browse to the volume and folder locations for the following in the
Location for Database, Log Files, and SYSVOL dialog box, and then click Next.
• Database folder.
• Directory service log folder.
• System volume (SYSVOL) folder.
Windows Server Backup backs up the directory service by volume. For backup
and recovery efficiency, store these files on separate volumes that do not contain
applications or other non-directory files.
16. Review the selections in the Summary dialog box. Click Previous to change any
selections. Click Next when the selections are accurate to install.
To save the selected settings to an answer file that can be used to automate
subsequent AD DS operations, click View Script, type the name for the answer
file, and click Save.
17. Click Install if All prerequisite checks passed successfully message appears.
18. Click Finish in the Completing the Active Directory Domain Services Installation
Wizard dialog box.

192 2PAA111695-600 G
A Migrate Redundant Domain Con A.5 Transferring the FSMO Roles to the Secon

A.5 Transferring the FSMO Roles to the Secondary


Domain Controller
Perform the following to transfer the FSMO roles to the Secondary Domain Controller:
This procedure must be performed on the new Domain Controller for every Role
transfer.

• Transferring the Schema Master Role on page 193.


• Transferring the Domain Naming Master Role on page 195.
• Transferring the RID Master, PDC Emulator, and Infrastructure Master Roles
on page 196.

A.5.1 Transferring the Schema Master Role


Perform the following to transfer the Schema Master Role.
To transfer the Schema Master Role it is necessary to:
• Register the Schmmgmt.dll.
• Run the Active Directory Schema Master snap-in.

Registering Schmmgmt.dll
Perform the following to register Schmmgmt.dll.
1. Enter regsvr32 schmmgmt.dll in the Run dialog box and click OK.
2. Click OK when the message indicating that the operation succeeded appears.

Running the Active Directory Schema Master Snap-in


Perform the following to run the Active Directory Schema Master Snap-in.
1. Enter mmc in the Run dialog box and click OK.
2. Click Add/Remove Snap-in on the File menu.
3. Click Active Directory Schema.
4. Click Add.
5. Click OK.

2PAA111695-600 G 193
A Migrate Redundant Domain Con A.5 Transferring the FSMO Roles to the Secon

6. Right-click Active Directory Schema in the console tree and then click Change
Active Directory Domain Controller... to launch the Change Directory Server
dialog box (Figure A.1).
The status of the newly added Windows Server 2012 / Windows Server 2016
Domain Controller in the Change Directory Server dialog box may show as
Unavailable. To change the status to Online, for one time, enable and disable
TCP/IPv6 on the client-server network.

Figure A.1: Change Directory Server

7. In the Change to category, select This Domain Controller or AD LDS instance.


8. From the list provided, select the new Domain Controller machine, and then click
OK.
9. A warning stating that the Active Directory Schema is not connected to the
Operations Master will appear. Click Ok to close the warning message.
10. Right-click Active Directory Schema in the console tree and then click
Operations Master....
11. In the Change Schema Master dialog box, click Change to transfer the schema
master role to the 2012/2016 Windows Server Domain Controller.
12. Click Yes to confirm the transferring of the role.

194 2PAA111695-600 G
A Migrate Redundant Domain Con A.5 Transferring the FSMO Roles to the Secon

13. Click Ok on the message that appears after a successful transfer of the Operations
Master.
Run the netdom query fsmo query to ensure that the role changes are reflected.

A.5.2 Transferring the Domain Naming Master Role


Perform the following to transfer the Domain Naming Master Role.
1. Open Active Directory Domains and Trusts from Administrative Tools.
2. Right-click Active Directory Domains and Trusts [Domain Name] and then
click Change to Active Directory Domain Controller to launch the Change
Directory Server dialog box.
3. Select New Domain Controller (2012/2016 Server) from Select an available
domain controller and click OK.
4. In the Change to category, select This Domain Controller or AD LDS instance.
5. From the list provided, select the new Domain Controller machine, and then click
OK.
6. Right-click Active Directory Domains and Trusts and then click Operations
Master... (Figure A.2).

Figure A.2: Operations Master Schema

7. Review the data and click Change to transfer the Domain Naming Master role.

2PAA111695-600 G 195
A Migrate Redundant Domain Con A.5 Transferring the FSMO Roles to the Secon

8. Click Yes to confirm the transferring of the role.


9. Click Ok on the message that appears after a successful transfer of the Domain
Naming Master role.

A.5.3 Transferring the RID Master, PDC Emulator, and Infrastructure


Master Roles
This procedure must be performed on the new Domain Controller.

Perform the following to transfer the RID Master, PDC Emulator, and Infrastructure
Master Roles.
1. Expand Active Directory Users and Computers from Administrative Tools.
2. Right-click the Domain name and then click Operations Masters... to launch
the Operations Masters dialog box (Figure A.3).

196 2PAA111695-600 G
A Migrate Redundant Domain Con A.5 Transferring the FSMO Roles to the Secon

Figure A.3: Active Directory Users and Computers Window

3. Click the appropriate tab for the master role to transfer RID Master, PDC, and
Infrastructure. Review the information and click Change.

2PAA111695-600 G 197
A Migrate Redundant Domain Con A.6 Removing the Remaining Windows Server 20

Figure A.4: Operations Master Tabbed Interface

4. Click Yes to confirm transferring of the role.


5. Click OK on the message displaying the successful completion of the role transfer.
Run the netdom query fsmo query to ensure that the changes to the roles are
applied.

A.6 Removing the Remaining Windows Server 2003


Domain Controller
The remaining Windows Server 2003 Domain Controller can be removed using the
Windows interface.
Refer to Removing the Redundant Domain Controller for the procedure to remove
the remaining Windows Server 2003 Domain Controller.

198 2PAA111695-600 G
A Migrate Redundant Domain Con A.7 Installing an Additional Windows Server

A.7 Installing an Additional Windows Server 2012 /


Windows Server 2016 Domain Controller
Refer to Installing an Additional Windows Server 2012 / Windows Server 2016
Domain Controller to install an additional Windows Server 2012 / Windows Server
2016 Domain Controller in an existing domain using the Windows interface.

A.8 Required 800xA Software


The Domain controllers must be prepared using the Node Preparation Tool to install
the required 800xA software by using Generic Node option. Refer to the System
800xA Installation, Update and Upgrade Getting Started ( 2PAA111708*) for detailed
procedure.

2PAA111695-600 G 199
200 2PAA111695-600 G
B Troubleshooting B.1 Errors and Warnings during Upgrade

Appendix B Troubleshooting

This section is divided into:


• Errors and Warnings during Upgrade
• Troubleshooting during Deploy

B.1 Errors and Warnings during Upgrade


The warning and error messages that can be generated by the 800xA backup/restore
function are described in the following topics. Suggested solutions are also provided.

B.1.1 Failed to Serialize Aspect


Example
Tue Jul 01 08:41:03 2003 [Error]: Failed to serialize aspect 'Operator Messages Link
Display' on object 'Web System Workplace'
Reason
It is not possible for the Backup function to save the aspect data.
Solution
Check in the system for the behavior of this aspect.

B.1.2 ASO Object Class xxxx


did not Implement IAfwAspectSystemObject. Failed to Create ASO. Forgot to Register
dll?
Example
Tue Jun 10 19:02:17 2003 [Error]: ASO object class
{7B7A13B3-8BB4-42A3-8289-987C579797C2}did not implement
IAfwAspectSystemObject Failed to create ASO. Forgot to register dll?

2PAA111695-600 G 201
B Troubleshooting B.1 Errors and Warnings during Upgrade

Reason
This often occurs when a system extension is used, but not installed on the node from
where the backup is taken. It can also happen if an update of a system extension has
been installed, but not added to the system.
Solution
Install all system extensions on the node from where the backup is taken. Make sure
that the correct version of the system extension is installed.

B.1.3 UnplacedObjects.afw
Example
[Warning] c:\PPABackup\MyBackup\UnplacedObjects.afw created
Reason
During backup process, the backup tool goes through all structures, if there is an
object that doesn't exist in any structure, it will be placed in UnplacedObjects.afw
and write a warning in the backup log, therefore, UnplacedObjects.afw is used for
all objects which miss the structure.
Solution
Check if there is any important object in UnplacedObjects.afw. If there is an important
object in UnplacedObjects.afw, your backup is considered to be not complete. In such
case, investigate what kind of object it is, and try to repair the system. One solution
could be to add the object into the structure it should belong to. Take another backup.

B.1.4 The System Cannot Find the Path Specified


Example
Error detected for aspect 'Empty A3P' of object 'Document Manager
Templates/Document Manager File Templates/Drawings'
Tue Jun 08 00:43:30 2004 The system cannot find the path specified.
EbServiceHandler: Object Id = {9AFACBA5-6B6A-462A-9EDF-78765740CD52},
Aspect Id = {89F8A8C4-10F7-4874-B77D-A8E6445D5C93}
EbServiceHandler: Failed to load document into stream!

202 2PAA111695-600 G
B Troubleshooting B.1 Errors and Warnings during Upgrade

Reason
When the backup was taken, the FSD cache was set too low. All data has NOT been
backed up. There should be warnings in the System Event list about overflow in the
Fsd cache.
Solution
Increase the Fsd Cache size (for all nodes).

B.1.5 System Extension ´xxxx´ with ID ´Guid` is not Installed on this


Node
Example
System extension 'Engineering Base' with id
{B775BEA4-7859-4649-AE16-901790822886} is not installed on this node.
System extension 'AC800M Con 31SP1' with id
{6F388AEC-E4FF-4614-AF80-1D37EC3B141F} is not installed on this node.
Reason
There is a system extension, which is not available in the node where the backup is
taken, or which is not properly removed. The latter can be the case if AC800 Connect
has been upgraded and the old version is still registered in Industrial IT 800xA.
Solution
Use a backup node where all system extensions are installed.

B.1.6 Timeout by External Service


Example
Thu Mar 04 02:34:55 2004 #1: Receiving files
Thu Mar 04 02:34:56 2004 #1: Receiving files
Thu Mar 04 02:34:57 2004 #1: Receiving files
Thu Mar 04 02:34:57 2004 #1: Finishing
Thu Mar 04 02:34:58 2004
Thu Mar 04 02:35:08 2004 TimeOut by External Service

2PAA111695-600 G 203
B Troubleshooting B.1 Errors and Warnings during Upgrade

Reason
History or System Message data was backed up using the backup/restore function.
This functionality is not yet supported.
Solution
History and System Message data has to be saved manually, as described in reference
[2] Release Notes. Create a new backup, without including History or System Message
data.

B.1.7 Graphic Aspect = xxx Cannot be Imported


Example
Mon Mar 29 19:52:32 2004 [Error]: Object = WI Mezzanine Deck, graphic aspect =
Page Prev cannot be imported. Source directory =
d:\OperateITData\Temp\ActiveGraphics\{800BA917-3D7F-44B6-B647-90C4B06A98FA}.restore.2.
Reason
Could be different reasons.
Solution
Check the source directory specified in the error message. The log file in this directory
should give some hints of what caused the problem.

B.1.8 Too Many Aspects of Category


Example
Sat Jun 05 17:04:33 2004: Too many aspects of category 'Name' on object
'{82416BDF-5464-4422-A443-35E08E1065BE}'
Sat Jun 05 17:04:34 2004: Import/Export Error: Object
{82416BDF-5464-4422-A443-35E08E1065BE}
({82416BDF-5464-4422-A443-35E08E1065BE}) -
E_AFW_AD_TOO_MANY_ASPECTS (0x8abb081b) To many aspect of a specific
type.
Sat Jun 05 17:04:34 2004: Failed to restore file C:\BWSC\BWSC Full Backup;
2004-06-03; 03-00\Control Structure28.afw. The importer returned hr = 0x8abb081b

204 2PAA111695-600 G
B Troubleshooting B.1 Errors and Warnings during Upgrade

Reason
The system was inconsistent at backup time (there were more than one aspect of
category 'Name' on an object). The backup does not react on this, but restore will fail.
The restore part will be fixed in a later release (it will be possible to import such an
object, but a warning will be granted).
Solution
Open the file (in this case Control Structure28.afw) with the old import/export utility
(<Install path>\bin\AfwImportExport_obsolete.exe), search for the aspect category
and manually remove one of the two aspect categories.

B.1.9 Aspect Category is Missing


Example
Sat Jun 05 16:41:27 2004: Aspect '{506D9D24-E22A-4EDB-AFB0-0753B6DB6990}'
on object 'SoftPoint Object Types' cannot be restored because the aspect category is
missing
Sat Jun 05 16:41:27 2004: ObjectId: {9574CC3B-0E5E-4B14-A83E-F483CCDE6E44}
Sat Jun 05 16:41:27 2004: AspectId:
{506D9D24-E22A-4EDB-AFB0-0753B6DB6990}
Reason
One or more aspect categories have been removed, while there are aspects of that
category still in the system. This inconsistency was present in the system when the
backup was taken.
Solution
If the aspect category has been removed then these aspects may not be of interest any
more. Check if the aspects are needed. If not, ignore this message.

B.1.10 Unknown Transaction Error


Example 1
Mon Apr 19 13:39:40 2004: Unknown transaction error
Reason
If this is the only error message, there is probably a problem with some windows
resources.

2PAA111695-600 G 205
B Troubleshooting B.1 Errors and Warnings during Upgrade

Solution
Check your windows resources.
Example 2
Mon Jun 28 08:37:08 2004: Loading C:\BACKUP\Full Backup; 2004-06-23;
10-39\Aspect System Structure0.afw ...
Mon Jun 28 08:37:09 2004: Aspect 'Batch Management Operation' on object 'Batch
Management Documents' failed to unserialize itself.
Mon Jun 28 08:37:09 2004: ObjectId:
{814786F8-E6CC-44B0-9A2A-1787FADDFE6F}
Mon Jun 28 08:37:09 2004: AspectId:
{2CE41978-DE94-44AC-9D38-B216FBA93C3A}
Reason
It is not possible for the Restore function to restore the aspect data.
Solution
No solution available.

B.1.11 Import/Export Error


Description
Restore of 800xA back-up on a node with Engineering Studio installed, may result
in the following error in the Configuration Wizard log:
" Importing files for ABB Engineering Base ...
Loading C:\Program Files (x86)\ABB Industrial IT\Engineer IT\Engineering
Studio\Engineering Base\import\10_Workplace_Structure_EngineeringStudio.afw
...
Import/Export Error: Engineering Workplace:AC 800M/C Colors - Missing color
definition
Engineering Workplace:AC 800M/C Colors - Missing color definition
Import/Export Error: Aspect 'AC 800M/C Colors' reported aspect hook error
(PrepareCommit):
** Aspect Hook Error **

206 2PAA111695-600 G
B Troubleshooting B.2 Troubleshooting during Deploy

Reason
AC 800M/C Colors aspect definition is not yet loaded in the system.
Solution
No solution exists. Users can ignore this error.

B.2 Troubleshooting during Deploy


The error messages that can be generated while deploying a node are described in
the following topics. Suggested solutions are also provided.
1. Problem: In very rare circumstances running Node Preparation Tool (NPT) will
create an error due to failure in stopping WMI Performance Adapter service.
Workaround: Stop and disable the WMI Performance Adapter service
manually from windows services and restart the node. After restart NPT will run
automatically.
2. Problem: During deploy of a node in very few cases, 800xA Notification Icon
on the node will display bad status and deploy might not proceed.

Figure B.1: Notification Icon

Workaround: The node needs to be disconnected and connected back to the


800xA System for deploy to proceed.
a. Right-click on the Notification Icon and open Configuration Wizard.
b. Select Disconnect Node and click Next. Proceed to disconnect the node.
c. After node is disconnected, select Connect Node and click Next.
d. Select Primary Aspect Server Node from drop-down and click Next.
e. Proceed to connect the node back to 800xA System.
3. If due to any reasons, Deploy System fails in the SCC Tool with an error on a
node(s), the user has following options available.
• Click Retry and proceed

2PAA111695-600 G 207
B Troubleshooting B.2 Troubleshooting during Deploy

In few cases, clicking on the Retry button can be a quick solution. If Retry
button is enabled in Deploy window, prefer this as first option before trying
out other options.

Figure B.2: Retry Option

• If the reason of failure is known, you can choose to manually resolve the
issue with that particular node function(s) and proceed with deployment of
rest of the nodes in the system.
a. On the Deploy window, expand the node where Deploy failed.
b. Right-click on the node function that failed.
c. Select Manually Resolve.
d. Click OK.
This will ensure only the node function(s) that is failed is skipped and
rest of the system deployment continues as planned.

208 2PAA111695-600 G
B Troubleshooting B.2 Troubleshooting during Deploy

Figure B.3: Manually Resolve

• If there are multiple failures on the node(s) which cannot be resolved


immediately (like Hardware failure), you can choose to skip the deployment
of entire node(s) that have failed and continue with the deployment on rest
of the nodes in the system.
a. On the Deploy window, click Abort > Abort deploy in progress.

Figure B.4: Aborting the Deploy

2PAA111695-600 G 209
B Troubleshooting B.2 Troubleshooting during Deploy

b. In the System Configuration Console window, use Exclusion option


to exclude the node(s) that are failed and click Deploy system.

Figure B.5: Node Exclusion

This will ensure only the node(s) that is failed is skipped and rest of the
system deployment continues as planned.
Once the errors are rectified and the failed node(s) are ready for
re-deployment, do the following.
c. Open System Configuration Console Tool on the Primary aspect server.
d. Select Configure system > System nodes.
e. Replace the node(s) in the plan where the deploy failed by selecting
that node and clicking Node actions... > Replace node... option.

210 2PAA111695-600 G
B Troubleshooting B.2 Troubleshooting during Deploy

Figure B.6: Replacing the node in the plan

f. Select the node and click Node actions... > Deploy.... This will re-deploy
the selected node and all its node functions.

2PAA111695-600 G 211
212 2PAA111695-600 G
C Control Builder M Compatibil C.1 800xA 5.0 SP2 to 800xA 6.0 Compatibility

Appendix C Control Builder M Compatibility


Check

This appendix lists the compatibility issues when upgrading from 800xA 5.0 SP2 to
800xA 6.0.

C.1 800xA 5.0 SP2 to 800xA 6.0 Compatibility Issues


Table C.1 lists and describes Control Builder M compatibility issues, including
solutions to the issues, when upgrading from 800xA 5.0 SP2 to 800xA 6.0. .
Table C.1: 800xA 5.0 SP2 to 800xA 6.0 Control Builder M Compatibility Issues

Application Issue Solution


CI851 and CI852 are no - They should be replaced with CI854 and CI860 instead.
longer supported

2PAA111695-600 G 213
214 2PAA111695-600 G
D Online Upgrade Controller Le D.1 Online Upgrade Controller Level

Appendix D Online Upgrade Controller Level

The information in this appendix is intended only as a high level introduction to the
online upgrade of the controller level. Detailed information appears in the controller
and control software instructions.

D.1 Online Upgrade Controller Level


Redundant AC 800M controllers can be upgraded with new firmware versions online.
Online upgrade is initiated from Control Builder by a nine-step wizard. Refer to the
Maintenance and Troubleshooting section in 800xA - Control and I/O, Basic Control
Software, Introduction and Configuration (3BSE035980R*) for more information.
In order to use online upgrade for the controller level:
• Refer to the Control and I/O, Control Software for AC 800M section of System
800xA Release Notes New Functions and Known Problems (2PAA106188*) for
the controller versions that support online upgrade.
• AC 800M Controllers require the client and server level to be of the same or
higher 800xA System version/revision. Refer to 800xA Online upgrade and
Co-existence, versions compatibility (3BSE080447) in the myABB/My Control
System for the supported upgrade paths.
• AC 800M Controllers must be redundant. A redundant controller consists of two
redundant processing units connected to I/O modules or CI modules.
• AC 800M Controller firmware and its CI modules can be upgraded independently.
– AC 800M controller firmware and the SM810, SM811, SM812 (safety)
CI modules must be upgraded simultaneously.
• Different AC 800M Controllers with different 800xA System versions/revisions
can coexist. This allows for extensions of an 800xA System with new AC 800M
Controllers or other new 800xA System functionality without having to upgrade
all existing controllers.

2PAA111695-600 G 215
D Online Upgrade Controller Le D.1 Online Upgrade Controller Level

– Starting from 800xA 5.0, upgrading to newer versions of Control Builder


and/or OPC Server does not require a controller upgrade. Controllers with
different firmware versions can coexist in the same network, and newer
versions of Control Builder and OPC Server can connect to controllers of
older versions (not older than 800xA 5.0). Refer to the Control and I/O,
Control Software for AC 800M section of System 800xA Release Notes New
Functions and Known Problems (2PAA106188*) for the controller versions
that support coexistence. Refer to 800xA Online upgrade and Co-existence,
versions compatibility (3BSE080447) in the myABB/My Control System
for the supported upgrade paths.
– Hardware types can coexist in different 800xA System versions/revisions
in the same 800xA System.
– Controllers that need to take advantage of new functionality are the only
ones that have to be upgraded. Other controllers can remain untouched. This
backwards compatibility is typically kept for two previous system versions.
• Upgrading nonredundant AC 800M Controllers is accomplished with minimized
plant disturbance by stopping and upgrading one controller at a time. The client
and server level can still be upgraded online, as long as the conditions are met
for performing an online upgrade on the client and server level.
Hot swap is the method to be used for a nonredundant AC 800M controller with
redundant CI modules and unchanged controller firmware.

216 2PAA111695-600 G
D Online Upgrade Controller Le D.2 Flowchart for Upgrading Controller Level

D.2 Flowchart for Upgrading Controller Level


Figure D.1 shows the upgrade flow for the controller level.

Figure D.1: Online Upgrade Flowchart for Controller Level

2PAA111695-600 G 217
D Online Upgrade Controller Le D.3 Flowchart for Extending Controller Level

D.3 Flowchart for Extending Controller Level


Figure D.2 shows the flow for extending the controller level to add new AC 800M
Controllers with the latest 800xA System version/revision to an existing plant with
or without upgrading the existing AC 800M Controllers.

Figure D.2: Flowchart for Extending Plant with New Controllers

218 2PAA111695-600 G
E 800xA for Harmony Online Upg E.1 Prerequisites

Appendix E 800xA for Harmony Online


Upgrade

This appendix describes the 800xA for Harmony online upgrade procedures.

E.1 Prerequisites
Two additional network switches are required for network isolation when
performing an online upgrade.
When an online upgrade of an 800xA 5.0 SP2 system is performed on a system that
includes 800xA for Harmony, the 800xA 5.0 SP2 and 800xA 6.0 systems must be
kept on separate network(s) until the 800xA 5.0 SP2 system is no longer required.
For more information, refer to the Upgrade Flow procedure provided in Considerations
and Upgrade Flow. An online upgrade requires redundant Aspect Servers, Harmony
Connectivity Servers, and Domain Controllers in the case of a domain.
Do not make any configuration changes on the 800xA system running the older
version during the online upgrade.
During an online upgrade the second domain controller must be promoted to a primary
domain controller, upgraded to Server Operating System, the domain roles transferred
to the node and finally moved to the isolated 800xA 6.0 network(s).

E.2 Node Order


This node order is different than what is described in Introduction.

2PAA111695-600 G 219
E 800xA for Harmony Online Upg E.3 800xA for Harmony Upgrade Procedure

From System Version 6.0, the 800xA for Harmony Configuration Server is not
available. Standalone Configuration Server nodes can remain in the system as
Application Server nodes or they can be removed from the system. The combined
800xA for Harmony Configuration and Connectivity Server nodes will be 800xA
for Harmony Connectivity Server nodes in the upgraded system (800xA 6.0
System).
The upgrade is a node-by-node procedure that must be performed in the following
node order:
Online Upgrade Node Order
• Redundant Domain Controller
• Redundant Aspect Server(s)
• Redundant 800xA for Harmony Connectivity Server(s)
• Application Server(s) and Configuration Server(s) that are to be used as
Application Server(s)
• Client(s)
• Primary Connectivity Server(s) and combined Configuration and Connectivity
Server(s)
• Primary Aspect Server
• Primary Domain Controller

E.3 800xA for Harmony Upgrade Procedure


Perform the procedure as follows:
1. Perform the applicable pre-upgrade procedures from Pre-Upgrade Procedures
for 800xA 5.0 SP2 to 800xA 6.0 upgrade.
2. Create a backup of the 800xA System from the Maintenance structure. Refer to
System 800xA Maintenance (3BSE046784*) user manual.
The 800xA for Harmony Standalone ConfigServer Export tool must be run before
performing the 800xA System backup. Refer to 800xA for Harmony pre-upgrade
procedures for more information.
3. Prepare System 800xA for upgrade. Refer Preparing System 800xA 5.0 SP2.

220 2PAA111695-600 G
E 800xA for Harmony Online Upg E.3 800xA for Harmony Upgrade Procedure

4. For an online upgrade in a domain environment, prepare the node to move to the
isolated network(s) by performing the following steps:
Skip this step if System 800xA is configured in a Workgroup Environment.

a. Disable Firewall on Primary Domain Controller 2003 before performing the


upgrade of Redundant Domain Controllers.
b. Migrate the redundant Domain Controller as per instructions inMigrate
Redundant Domain Controllers and perform following steps.
- Preparing a Domain for Windows Server 2012 / Windows Server 2016.
- Remove the Redundant Domain Controller.
- Install an Additional Windows Server 2012 / Windows Server 2016 Domain
Controller.
- Transfer the FSMO Roles to the Secondary Domain Controller.
c. Move the new Domain Controller to isolated 800xA 6.0 network(s).
d. Install 800xA software on Domain Controller once the machine is on the
isolated 800xA 6.0 network(s) as per instructions in Required 800xA
Software.
When an online upgrade of an 800xA 5.0 SP2 System is performed on a system
that includes 800xA for Harmony, the 800xA 5.0 SP2 and 800xA 6.0 Systems
must be kept on separate network(S) until the 800xA 5.0 SP2 System is no longer
required.
5. Upgrade Redundant Aspect Server, refer Redundant Aspect Server.
6. Upgrade Redundant Connectivity Servers, refer Redundant Connectivity Servers.
7. If 800xA System has 2oo3 redundancy, upgrade the other Redundant Aspect
Server. Refer Redundant Aspect Server (2oo3 Redundancy Only).
8. Upgrade some of the operator clients, refer Clients.
9. If 800xA system has Information Management Server, upgrade the server. Refer
Information Management Server.
10. Upgrade the Application Servers and Harmony Configuration Servers (If planned
to be used as other application server). Refer Application Servers.

2PAA111695-600 G 221
E 800xA for Harmony Online Upg E.3 800xA for Harmony Upgrade Procedure

11. Upgrade the remaining nodes except the Primary Aspect Server, refer Remaining
Nodes.
12. Upgrade the Primary Aspect Server, refer Primary Aspect Server.
13. Remove the remaining Windows Server 2003 Domain Controller.
Skip this step if System 800xA is configured in a Workgroup Environment.

a. Load the operating system of the remaining Domain Controllers installing


an additional Server Operating System Domain Controller to Server
Operating System outlined in Migrate Redundant Domain Controllers. Ensure
that the hard drive is reformatted during the operating system load.
b. Move remaining Domain Controllers to isolated 800xA 6.0 network(s).
A message appears while installing Additional Domain Controller, check Allow
domain controller reinstall option. (see Figure E.1)

Figure E.1: Domain Controller reinstall

222 2PAA111695-600 G
E 800xA for Harmony Online Upg E.3 800xA for Harmony Upgrade Procedure

c. Install the remaining Domain Controller as an Additional Domain Controller.


Refer to the instructions in Installing an Additional Windows Server 2012
/ Windows Server 2016 Domain Controller
d. Install required 800xA software on Domain Controller once the machine is
on the isolated 800xA 6.0 network(s). Refer to the instructions in Required
800xA Software.

2PAA111695-600 G 223
224 2PAA111695-600 G
F 800xA 6.0 Service Group and

Appendix F 800xA 6.0 Service Group and


Service Provider Names

To make the future updates and upgrades easier, the Service Group names and Service
Provider names must match either the default names for System 800xA 6.0 or the
configured names for node functions with Server Groups and Providers configured
in SCC Tool. It is mandatory to rename the Service Group and Provider names on
the Primary Aspect Server as per the default format before we proceed.
If the Service Group names and Service Provider names do not match in the
configuration created by the system installer, Deploy can fail or duplicate Service
Groups and Providers may be created after upgrade. In this case the duplicate
Service Groups and Providers needs to be cleaned up from 800xA 6.0 system
looking at 800xA 5.0 SP2 reference System.
Table F.1 shows the default service group and service provider names in 800xA 6.0.
Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)

Service Name Service Group Name Service Provider Name


Alarm Manager Basic Alarm Manager_Basic_nodename
AspectDirectory Basic AspectDirectory_Basic_nodename
BackupService Basic BackupService_Basic_nodename
Cross referencing server Basic Cross referencing server_Basic_nodename
Event Collector ABB 800xA Soft Alarms Event Collector_ABB 800xA Soft Alarms
OPC Server OPC Server_nodename
Event Collector ABB 800xA System Event Collector_ABB 800xA System
Message Server Message Server_nodename
File Set Distribution Basic File Set Distribution_Basic_nodename
Lock Server Basic Lock Server_Basic_nodename
Soft Alarms Basic Soft Alarms_Basic_nodename

2PAA111695-600 G 225
F 800xA 6.0 Service Group and

Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)
(Continued)

Service Name Service Group Name Service Provider Name


System Message Server Basic System Message Server_Basic_nodename
System Status Basic System Status_Basic_nodename
Workplace Service Basic Workplace Service_Basic_nodename
Event Storage Basic Event Storage_Basic_nodename
Alarm Analysis Alarm Analysis Alarm Analysis on nodename
Alarm Logger Alarm Logger Alarm Logger on nodename
Basic History Basic History Basic History on nodename
name - can be any logical Note: If there is more than one service
name to differentiate group in the system, the service group name
multiple Basic History must be unique. The relationship between
service groups. the nodes and service groups must be
recorded, so the matching service providers
and groups are properly renamed.
Basic History Service Group and providers
names on IM servers or 800xA History
Archive servers do not need to be renamed.
These names are not set by the System
Installer.
External Alarm External Alarm External Alarm on nodename
Property Transfer Property Transfer Property Transfer on nodename
Batch Service Batch Primary
Secondary
Event Collector Batch Primary
Secondary

226 2PAA111695-600 G
F 800xA 6.0 Service Group and

Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)
(Continued)

Service Name Service Group Name Service Provider Name


Calculation Server Calculation Group Calculations_nodename
Note: If there is more than one service
group in the system, the service group name
must be unique. The relationship between
nodes and service groups must be recorded
so the matching service providers and
groups are properly renamed.
In System 800xA 6.0 latest release, only the
service group and provider name on the
aspect server needs to be modified. All
Service group and provider names will be
corrected during the deploy of the other
nodes.

2PAA111695-600 G 227
F 800xA 6.0 Service Group and

Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)
(Continued)

Service Name Service Group Name Service Provider Name


Scheduler Scheduler Group Scheduler_nodename
For system with more than one Scheduler
group, it is recommended that the scheduler
service group names be configured in the
system installer to match the names in the
system being restored. If the name does not
match, All action aspects that reference a
specific scheduler group will have to be
reconfigured to point to the correct
scheduler group when the upgrade is done.
Without this, all actions will run from the
default group.
Note: If there is more than one service
group in the system, the service group name
must be unique. The relationship between
nodes and service groups must be recorded
so the matching service providers and
groups are properly renamed.
In System 800xA 6.0 latest release, only the
service group and provider name on the
aspect server needs to be modified. All
Service group and provider names will be
corrected during the deploy of the other
nodes.

228 2PAA111695-600 G
F 800xA 6.0 Service Group and

Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)
(Continued)

Service Name Service Group Name Service Provider Name


Harmony Executive Basic Systems having Separate Aspect Server
and Harmony CS:
• After restoring the 800xA Backup on
the Aspect Server, delete all Harmony
Executive Service Provider(s).
• New Service Provider(s) will be created
automatically during deploy of the
Connectivity Server(s).
Systems having Combined Aspect
Server and Harmony CS:
• After restoring the 800xA Backup on
the Aspect Server, the Service Provider
for the first Aspect Server\Connectivity
Server must be renamed as it is the
first node in the System 800xA 6.0. The
format is as follows:
HarmonyExec_nodename
• Any remaining Harmony Executive
Service Provider(s), including one’s
associated with other combined Aspect
Server\Connectivity Server should be
deleted. New Harmony Executive
Service Provider(s) will be created
automatically during Deploy of the
Connectivity Server(s).

2PAA111695-600 G 229
F 800xA 6.0 Service Group and

Table F.1: Default Service Group and Service Provider Names in 800xA (Continued)
(Continued)

Service Name Service Group Name Service Provider Name


Event Collector ABB 800xA Harmony Systems having Separate Aspect Server
AE_PrimaryCSnodename and Harmony CS:
• After restoring the 800xA Backup on
the Aspect Server, delete all Harmony
Event Collector Service Provider(s).
• New Service Provider(s) will be created
automatically during deploy of the
Connectivity Server(s).
Systems having Combined Aspect
Server and Harmony CS:
• After restoring the 800xA Backup on
the Aspect Server, the Service Provider
for the first Aspect Server\Connectivity
Server must be renamed as it is the
first node in the System 800xA 6.0. The
format is as follows: Event
Collector_ABB 800xA Harmony
AE_nodename
• Any remaining Harmony Event
Collector Service Provider(s), including
one’s associated with other combined
Aspect Server\Connectivity Server must
be deleted. New Harmony Event
Collector Service Provider(s) will be
created automatically during Deploy of
the Connectivity Server(s).
Asset Monitoring AssetMonitoring SG_1 AssetMonitoring SP_1
Refer ABB Asset Optimizationfor additional
Steps.
Messenger Server Messenger SG_1 Messenger SP_1
OpcDA_Connector SG_IT Server_nodename OPCDA_Provider_nodename
IT SNMP Trap Service SG_PNSM_Trap SG_PNSM_Trap_nodename
Server_nodename Refer ABB PC, Network and Software
Monitoringfor additional Steps.

230 2PAA111695-600 G
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300

F.1 ABB 800xA for MOD 300


This procedure is applicable only if the system consists of 800xA for MOD 300.
After the 800xA 5.x backup is restored on 800xA 6.0 Primary Aspect Server, follow
the instructions in this section before deploying other nodes.
800xA for MOD 300 Event Collector service group(s) require separate workflow
to be followed. Before deploying MOD 300 Connectivity servers, check if the
existing MOD Event Collector Service Group(s) name is in different format than
MOD_AE_SG_%GroupName% else rename it to a different format.
1. Make a note of the Service Group name that is given while configuring 800xA
6.0 System using SCC Tool.

Figure F.1: Service Group Name for MOD 300

This Group name is to be provided in place of %GroupName% in Table F.2.

2PAA111695-600 G 231
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300

2. Modify OPC DA Service Group and Service Providers.


Table F.2: Default OPC DA Service Group and Service Provider Names for MOD 300

Service Name Service Group Name Service Provider Name


OPCDA_Connector MOD_DA_SG_%GroupName% Systems having Separate Aspect Server
and MOD CS:
• After restoring the 800xA Backup on
the Aspect Server, delete all MOD
OPC DA Service Provider(s).
• New Service Provider(s) will be
created automatically during deploy
of the Connectivity Server(s).
Systems having Combined Aspect
Server and MOD CS:
• After restoring the 800xA Backup on
the Aspect Server, the Service
Provider for the first Aspect
Server\Connectivity Server must be
renamed as it is the first node in the
System 800xA 6.0. The format is as
follows: MOD_DA_nodename
• Any remaining MOD OPC DA Service
Provider(s), including one’s
associated with other combined
Aspect Server\Connectivity Server
should be deleted. New MOD OPC
DA Service Provider(s) will be created
automatically during Deploy of the
Connectivity Server(s).

232 2PAA111695-600 G
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300

3. Modify the MOD OPC Server Network Object:


a. Open Plant Explorer Workplace.
b. Navigate to Control Structure > Root > MOD Control Network name,
MOD OPC Server Network.
c. Ensure that the existing MOD OPC Server Network as per default
nomenclature for 800xA 6.0: MOD_SG_%GroupName%
If not, rename it accordingly.

Figure F.2: Renaming MOD Control Network

2PAA111695-600 G 233
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300

F.1.1 800xA for MOD 300 Batch


If 800xA for MOD 300 system uses Batch Management, perform the following before
proceeding to next step.
Table F.3: Default OPC DA Service Group and Service Provider Names for MOD 300 with Batch
Management

Service Name Service Group Name Service Provider Name


OPCDA_Connector MOD_Batch_DA_SG_%GroupName% Systems having Separate Aspect
Server and MOD 300 Batch Server:
• After restoring the 800xA
Backup on the Aspect Server,
delete all MOD Batch DA
Service Provider(s).
• New Service Provider(s) will be
created automatically during
deploy of the Connectivity
Server(s).
Systems having Combined Aspect
Server and MOD 300 Batch Server:
• After restoring the 800xA
Backup on the Aspect Server,
the Service Provider for the first
Aspect Server\Connectivity
Server must be renamed as it is
the first node in the System
800xA 6.0. The format is as
follows:
MOD_Batch_DA_nodename
• Any remaining MOD Batch DA
Service Provider(s), including
one’s associated with other
combined Aspect
Server\Connectivity Server
should be deleted. New MOD
Batch DA Service Provider(s)
will be created automatically
during Deploy of the
Connectivity Server(s).

234 2PAA111695-600 G
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI

1. Modify the MOD Batch OPC Server Network Object:


a. Open Plant Explorer Workplace.
b. Navigate to Control Structure > Root > MOD Batch Control Network
name, MOD Batch OPC Server Network.
c. Ensure that the existing MOD Batch OPC Server Network as per default
nomenclature for 800xA 6.0: MOD_Batch_SG_%GroupName%
If not, rename it accordingly.
2. Continue with deploy of the nodes as per the upgrade workflow.

F.1.2 Renaming MOD 300 AE Service Group and Service Provider Names
Perform this procedure after deploying all System 800xA 6.0 nodes.

1. Deployment of MOD 300 Connectivity server creates additional MOD Event


Collector Service Group(s) and Service Providers.
2. After all System 800xA 6.0 nodes are deployed, the newly created MOD Event
Collector (AE) service group(s) must be deleted from the service structure. This
newly created service group(s) can be identified by checking the Enabled state.
AE service groups created during the deployment of System 800xA 6.0 are
disabled (Enabled option is unchecked) by default.
3. The existing AE service group(s) and service providers must be renamed to match
the default System 800xA 6.0 nomenclature.
Table F.4: Default AE Service Group and Service Provider Names for MOD 300

Service Name Service Group Name Service Provider Name


Event Collector MOD_AE_SG_%GroupName% MOD_AE_nodename

F.2 ABB 800xA for DCI


This procedure is applicable only if the system consists of ABB 800xA for DCI.
After the 800xA 5.x backup is restored on 800xA 6.0 Primary Aspect Server, workflow
is as follows:

2PAA111695-600 G 235
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI

1. Make a note of the OPC DA ID that is given while configuring 800xA 6.0 System
using SCC Tool.

Figure F.3: DCI OPC ID

This OPC ID is to be provided in place of %DciOpcDaID% in Table F.5.


2. Modify all OPC DA Service Group(s) and Service Providers as in Table F.5.

236 2PAA111695-600 G
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI

Table F.5: Default OPC DA Service Group and Service Provider Names for DCI

Service Name Service Group Name Service Provider Name


OPCDA_Connector SG_DCI%DciOpcDaID%_DA Systems having Separate Aspect Server
and DCI CS:
• After restoring the 800xA Backup on the
Aspect Server, delete all DCI OPC DA
Service Provider(s).
• New Service Provider(s) will be created
automatically during deploy of the
Connectivity Server(s).
Systems having Combined Aspect Server
and DCI CS:
• After restoring the 800xA Backup on the
Aspect Server, the Service Provider(s)
for the first Aspect Server\Connectivity
Server must be renamed as it is the first
node in the System 800xA 6.0. The
format is as follows:
SG_DCI%DciOpcDaID%_DA_nodename
• Any remaining DCI OPC DA Service
Provider(s), including one’s associated
with other combined Aspect
Server\Connectivity Server should be
deleted. New DCI OPC DA Service
Provider(s) will be created automatically
during Deploy of the Connectivity
Server(s).

3. As in Step 1., if DCI for Batch is used, make a note of the OPC Batch ID for
DCI Batch that is given while configuring 800xA 6.0 System using SCC Tool.
This OPC Batch ID is to be provided in place of %DciOpcBaID% in Table F.6.

2PAA111695-600 G 237
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI

Table F.6: Default Service Group and Service Provider Names for DCI Batch

Service Name Service Group Name Service Provider Name


OPCDA_Connector SG_DCI%DciOpcBaID%_Batch_DA Systems having Separate Aspect Server
and DCI CS:
• After restoring the 800xA Backup on
the Aspect Server, delete all DCI
Batch DA Service Provider(s).
• New Service Provider(s) will be
created automatically during deploy
of the Connectivity Server(s).
Systems having Combined Aspect
Server and DCI CS:
• After restoring the 800xA Backup on
the Aspect Server, the Service
Provider for the first Aspect
Server\Connectivity Server must be
renamed as it is the first node in the
System 800xA 6.0. The format is as
follows:
SG_DCI%DciOpcBaID%_
Batch_DA_nodename
• Any remaining DCI Batch DA Service
Provider(s), including one’s associated
with other combined Aspect
Server\Connectivity Server(s) should
be deleted. New DCI Batch DA
Service Provider(s) will be created
automatically during Deploy of the
Connectivity Server(s).

4. As in Step 1. make a note of the OPC AE ID that is given while configuring


800xA 6.0 System using SCC Tool. This OPC ID is to be provided in place of
%DciOpcAeID% in Table F.7.

238 2PAA111695-600 G
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI

Table F.7: Default OPC AE Service Group and Service Provider Names for DCI

Service Name Service Group Name Service Provider Name


Event Systems with separate Aspect Server Systems with separate Aspect Server
Collector and DCI CS: and DCI CS:
• After restoring the 800xA Backup • After restoring the 800xA Backup on
on the Aspect Server, delete all the Aspect Server, verify all DCI
existing DCI OPC AE Service Event Collector Service Provider(s)
Group(s) along with their Service are deleted.
Provider(s) before Deploy of DCI • New Service Provider(s) will be
Connectivity Server(s). created automatically during deploy
• Service Group(s), along with their of the Connectivity Server(s).
Service Provider(s) will be created • Enable the DCI OPC AE Service
automatically during Deploy of the Group from Service Structure >
Connectivity Server(s). Event Collector, Service.
Event Systems with combined Aspect Systems with combined Aspect Server
Collector Server and DCI CS: and DCI CS:
(Continued) After restoring the 800xA Backup on After restoring the 800xA Backup on the
the Aspect Server, delete all DCI OPC Aspect Server, verify all DCI Event
AE Service Group(s) along with their Collector Service Provider(s) are deleted
Service Provider(s) before Deploy of before Deploy of remaining DCI
remaining DCI Connectivity Server(s). Connectivity Server(s).
On the Primary Aspect Server + DCI On the Primary Aspect Server + DCI
CS: CS:
For creation of Service Group, along • Run the AbbDciPostInstall.exe task
with the Service Provider of Primary to create the DCI AE Service Group
AS\DCI CS follow the steps mentioned and Service Provider.
in Service Provider column. AbbDciPostInstall is located in the
On the Redundant Aspect Server + C:\Program Files (x86)\ABB Industrial
DCI CS and Other DCI CS(s): IT\800xA\DCI Library\DciConnect\bin
folder.
The DCI AE Service Group along with
Service Provider will be handled • Enable the DCI OPC AE Service
automatically with the deploy of the Group from Service Structure >
redundant AS+CS and other DCI CS(s). Event Collector, Service.

2PAA111695-600 G 239
F 800xA 6.0 Service Group and F.3 800xA for AC 800M

Table F.7: Default OPC AE Service Group and Service Provider Names for DCI
(Continued)

Service Name Service Group Name Service Provider Name


On the Redundant Aspect Server + DCI
CS and Other DCI CS(s):
The DCI AE Service Provider will be
created automatically with the deploy of
the redundant AS+CS and other DCI
CS(s).

5. Enable all the Service Groups if not already enabled.


6. Continue with deploy of the nodes as per the upgrade workflow.

F.3 800xA for AC 800M


This procedure is applicable only if the system consists of 800xA for AC 800M.
After the 800xA 5.x backup is restored on 800xA 6.0 Primary Aspect Server, follow
the instructions in this section before deploying other nodes.
1. Make a note of the group properties and node specific properties of all AC 800M
connectivity servers that is given while configuring 800xA 6.0 System using
SCC Tool.

240 2PAA111695-600 G
F 800xA 6.0 Service Group and F.3 800xA for AC 800M

Figure F.4: Properties for OPC Server for AC 800M

2. Modify OPC DA Service Group and Service Providers.

2PAA111695-600 G 241
F 800xA 6.0 Service Group and F.3 800xA for AC 800M

Table F.8: Default OPC DA Service Group and Service Provider Names for AC 800M

Service Name Service Group Name Service Provider Name


OPCDA_Connector AC 800M service group name AC 800M service provider on
name: can be any logical name to differentiate nodename
multiple AC 800M service groups
Event Collector AC 800M service group name AC 800M service provider on
name: can be any logical name to differentiate nodename
multiple AC 800M service groups

3. Modify the Control Network Object:


a. Open Plant Explorer Workplace.
b. Navigate to Control Structure > Root > Control Network name , Control
Network.
c. Ensure that the existing Control Network name matches with the name
mentioned in the Properties for OPC Server for AC 800M in SCC.
If not, rename it accordingly.

Figure F.5: Renaming Control Network

242 2PAA111695-600 G
F 800xA 6.0 Service Group and F.4 ABB Asset Optimization

Figure F.6: Properties for OPC Server for AC 800M

F.4 ABB Asset Optimization


This procedure is applicable only if the system consists of ABB Asset Optimization.
After upgrade to System 800xA 6.0, refer to 800xA 5.x reference note and do the
following.
• Delete additional AO Server object created in the Control Structure under the
Asset Optimization object.
• Delete additional Asset Monitoring Service Group and related Service Provider
in the Service Structure.

F.5 ABB PC, Network and Software Monitoring


This procedure is applicable only if the system consists of ABB PC, Network and
Software Monitoring.
After upgrade to System 800xA 6.0, refer to 800xA 5.x reference note and do the
following.
• Delete additional IT OPC Server Network object created in the Control
Structure.
• Delete additional IT Server Service Group and related Service Provider in the
Service Structure.

2PAA111695-600 G 243
244 2PAA111695-600 G
G Identifying Node Functions a G.1 Collecting Data from Existing System 800

Appendix G Identifying Node Functions and


System Functions

G.1 Collecting Data from Existing System 800xA 5.0


SP2
This topic describes the workflow for collecting existing System 800xA 5.0 SP2
information using System Checker Tool. This data can be used while planning the
System 800xA 6.0.
1. On any 800xA 5.0 SP2 node, open System Checker Tool from:
Start menu > All Programs > ABB Industrial IT 800xA > System > System
Checker Tool > System Checker Tool.exe.
2. Select 800xA System Report and click Next.
3. Select a folder for saving the systemReport.ini file.
Wait until Industrial IT 800xA System Collection Wizard completes collecting
data.

2PAA111695-600 G 245
G Identifying Node Functions a G.1 Collecting Data from Existing System 800

Figure G.1: Industrial IT 800xA System Collection Wizard

4. Open the Excel file System Report Analyzer from below location:
Start menu > All Programs > ABB Industrial IT 800xA > System > System
Checker Tool
5. Click Convert Checker Report, and Navigate to the systemReport.ini file from
step c.
6. Click OPEN. This step extracts all the required system information onto multiple
tabs in the SystemCheckHelper excel file.
The Summary tab in this Excel sheet can be used to retrieve information from
the 800xA 5.0 SP2 System. This data can be used while planning the 800xA 6.0
System.
• To create the list of all services in service structure, Click Create
Node-Service Relation.
• To create a list of installed software on all 800xA nodes, Click Create
Node-Application Relation, select All software and click OK.

246 2PAA111695-600 G
G Identifying Node Functions a G.2 Node Functions and System Functions

• To retrieve basic node type information, click Advanced and Select Fetch
Node Type Information.

Figure G.2: Advanced - Node Application Relation

G.2 Node Functions and System Functions


The 800xA System functionality is divided into a Base System and a set of options.
The options represent functions that can be added to the system based on the needs
of the process that should be controlled. The system functionality is grouped in a set
of functional areas for an easier overview of the complete system functionality.
The System 800xA structure is summarized as follows:
• Base System is the system base software. It consists of:
– DCS Base System Functionality.
– Integration of ABB Controllers as well as other PLCs / RTUs.

2PAA111695-600 G 247
G Identifying Node Functions a G.3 Definitions

– System Options (for example, OLE-DB Real Time Data Client Connection,
Audit Trail (Security Events and Configuration Changes), Advanced Access
Control, SMS and e-mail Messaging, and so on).
• System 800xA consists of the following Functional areas:
– Operations.
– Batch Management.
– Information Management.
– Control and I/O, including SIL (Safety Integrity Level) 3 Safety Control.
– Engineering.
– Asset Optimization.
– Device Management.
– Multisystem Integration.
• Additional supporting hardware and software components are:
– AC 800M Hardware.
– S800 I/O.
– PROFIBUS Network Components.
– FOUNDATION Fieldbus Network Components.
– HART Multiplexer Network Components.
– IEC 61850 Network Components

G.3 Definitions
Below procedures are applicable to both 800xA 5.0 SP2 and 800xA 5.1 systems,
which will be referred to as 800xA 5.x systems.
Before upgrading an existing 800xA 5.x System to 800xA 6.0, it is important to
understand how the System and node functions are configured in the existing 800xA
5.x System. 800xA 6.0 system should be planned similar to 800xA 5.x system.
The following definitions helps in understanding the node and system functions in
800xA 6.0 Systems.

248 2PAA111695-600 G
G Identifying Node Functions a G.4 Identifying System Functions

G.3.1 System Functions


System Functionality consists of number of selectable functions which are intended
to be part of the installed System 800xA.

G.3.2 Node Types


The node type determines the main use of an 800xA system node as a client node, or
as a server node, or as a combined client and server node. This is used to determine
which software media folders need to be copied locally to the node during installation.

G.3.3 Node Functions


System 800xA functionality consists of a number of selectable functions. The System
Installer installs and activates relevant software components on relevant system nodes
to support the selected functions.

G.3.4 Options
System functions may have selectable options to determine functional characteristics
or behavior. The System Installer activates options on relevant nodes to reflect the
selections.
For more information on the Node Functions and System Functions, refer to System
800xA System Guide Technical Data and Configuration (3BSE041434*).

G.4 Identifying System Functions


System Functionality consists of number of selectable functions which are intended
to be part of the installed System 800xA.
System Functions in current 800xA 5.x system can be identified as follows:
1. Analyzing the Installed software on the nodes - Following System Functions can
be identified by analyzing the installed software on nodes in 800xA 5.x System.
Refer to Collecting Data from Existing System 800xA 5.0 SP2, on how to collect
installed software information using System Checker Tool.

2PAA111695-600 G 249
G Identifying Node Functions a G.4 Identifying System Functions

Table G.1: Identifying System Functions using Installed Software

System Function to be selected while


Check for the following in 800xA 5.x System
planning 800xA 6.0 System
Installed software: "ABB Inform IT - DataDirect Data Direct Services
Installed software: "ABB Inform IT - Display Services" Information Management - IM Desktop Tools
and "ABB Inform IT - Desktop Trends"
Note: On Client nodes and non-IM History Services
Servers.
Installed software: "ABB Device Library Wizard - Device Library Wizard
Server " or "ABB Device Library Wizard - Client"
Installed software: " ABB Inform IT - PDL Browser Information Management - IM Services: PDL
Light" Browser
Note: This is only installed on IM Servers.
Installed software: " ABB Inform IT - Profile Client" If this software is installed on IM Servers,
select: Information Management - IM
Services: Profile Client
If this software is installed on non-IM Servers,
select: Information Management - IM Profile
Client
Installed software: "ABB HART Multiplexer Connect Device Management PROFIBUS and HART:
Package" HART Multiplexer Connect
Installed software: "ABB Base Software for AC 800M SoftController
SoftControl"

1. Analyzing the loaded 800xA system extensions - Following System Functions


can be identified by analyzing the system extensions loaded in the 800xA 5.x
System. To check the list of loaded system Extensions,
a. Open Plant Explorer Workplace
b. In the Admin Structure, Navigate to Administrative Objects > Domains
> System Name, Domain
c. Select System Extensions aspect.
d. Refer to the below table to identify the system functions on an existing
800xA 5.x system.

250 2PAA111695-600 G
G Identifying Node Functions a G.4 Identifying System Functions

Table G.2: Identifying System Functions using Loaded System Extensions

System Function to be selected while


Check for the following in 800xA 5.x System
planning 800xA 6.0 System
System Extension Name = "Snapshot Reports for 800xA" Snapshot Reports
System Extension Name = "ABB Inform IT Calculations" Calculations Services
System Extension Name = "ABB Inform IT Scheduler" Application Scheduler Services
System Extension Name = "ABB SMS and Email SMS and E-Mail Messaging
Messaging"
System Extension Name = "ABB SoftPoint Server" SoftPointServer
System Extension Name = "ABB 800xA History Information Management - 800xA History
Connectivity"
System Extension Name = "ABB Industrial IT Archival” Information Management - 800xA History
Archive
System Extension Name = "ABB Asset Optimizer Server" Asset Optimization
System Extension Name = "ABB Maximo Connectivity" Asset Optimization: Maximo Integratiion
System Extension Name = "ABB SAP Connect System Asset Optimization: SAP Integration
Extension"
System Extension Name = "ABB Batch" Batch Management
System Extension Name = "ABB Device Management Device Management FOUNDATION
FOUNDATION Fieldbus" Fieldbus
System Extension Name = "ABB Inform IT History" Information Management - IM Services
System Extension Name = "ABB PC, Network and PC, Network and Software Monitoring
Software Monitoring"
System Extension Name = "ABB PROFIBUS Device Device Management PROFIBUS and
Integration Library - Basics" HART
System Extension Name = "ABB HART Device
Integration Library - Basics"
System Extension Name = "ABB DCI Extension" 800xA for DCI
System Extension Name = "ABB DCI Batch Extension" 800xA for DCI: Batch for DCI
System Extension Name = "Harmony Connect" 800xA for Harmony

2PAA111695-600 G 251
G Identifying Node Functions a G.4 Identifying System Functions

Table G.2: Identifying System Functions using Loaded System Extensions


(Continued)

System Function to be selected while


Check for the following in 800xA 5.x System
planning 800xA 6.0 System
System Extension Name = "Advanced Harmony Control 800xA for Harmony: CNAM
System Monitoring"
System Extension Name = "Harmony Batch Connect" 800xA for Harmony: Batch for Harmony
System Extension Name = "MOD300 Connect" 800xA for MOD 300
System Extension Name = "MOD300 Batch Connect" 800xA for MOD 300: Batch for MOD 300
System Extension Name = "ABB IEC61850 Connect 800xA for IEC 61850
System Extension"
System Extension Name = "ABB IEC61850 Operation 800xA for IEC 61850: IEC61850
Library for Substation Equipment" Operation Library for Substation
Equipemnt
System Extension Name = "AC800M Connect" 800xA for AC 800M
System Extension Name = "AC800M High Integrity" 800xA for AC 800M: AC800M HI
Extension
System Extension Name = "ABB AC800M Status AC 800M Status Monitoring Services
Monitoring"
System Extension Name = "ABB 800xA for Advant 800xA for Advant Master
Master"
System Extension Name = "ABB 800xA for Safeguard" 800xA for Advant Master: 800xA for
Safeguard
System Extension Name = "ABB 800xA for AC870P / 800xA for AC 870P/Melody
Melody"
System Extension Name = "ABB PLC Connect" PLC Connect
System Extension Name = "TRIO" TRIO Connect
System Extension Name = "ABB 800xA for AC100" 800xA for AC 100
System Extension Name = "Process Engineering Tool Process Engineering Tool Integration
Integration"
System Extension Name = "ABB Engineering Base" Engineering Workplace

252 2PAA111695-600 G
G Identifying Node Functions a G.4 Identifying System Functions

Table G.2: Identifying System Functions using Loaded System Extensions


(Continued)

System Function to be selected while


Check for the following in 800xA 5.x System
planning 800xA 6.0 System
System Extension Name = "ABB ACM" Engineering Workplace: Application
Change Management
System Extension Name = "ABB Reuse Assistant" Engineering Workplace: Reuse Assistant
for Engineering Studio
System Extension Name = "ABB Script Manager" Engineering Workplace: Script Manager
for Engineering Studio
System Extension Name = "ABB Topology Designer" Engineering Workplace: Topology
Designer for Engineering Studio
System Extension Name = "ABB SFC Viewer" Sequential Function Chart (SFC) Viewer
System Extension Name = "ABB EOW" Extended Operator Workplace (EOW)
System Extension Name = "ABB Multisystem Integration" Multisystem Integration
System Extension Name = "ABB VideONet Connect" Video Surveillance

Following are the System Functions that are configured on all 800xA 6.0 Systems
by default:
• Base System
• Central Licensing System
• Diagnostics Collection Tool
System Function: Symbol Factory Controls needs to be selected only if the
Symbol Factory Controls are used in VBPG graphics of existing 800xA 5.x System.
For more information, contact ABB Technical Support.

2PAA111695-600 G 253
G Identifying Node Functions a G.4 Identifying System Functions

Figure G.3: Symbol Factory Graphic Elements

G.4.1 Planning System Functions


The information collected from an existing 800xA 5.x system must be used to plan
the system functions in System 800xA 6.0 using System Configuration Console (SCC)
Tool.
SCC Tool > System Setup > Configure System > System Functions tab > Edit
Functions...

254 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions

Figure G.4: Planning System Function using SCC Tool

For more information on planning System Functions, refer to System 800xA System
Guide Technical Data and Configuration (3BSE041434*).

G.5 Identifying Node Functions


It is important to identify different node function(s) in current 800xA 5.x System and
the nodes they are configured on, so as to plan similar 800xA 6.0 system.
Configuration of Node Functions in current 800xA 5.x system can be identified as
follows:

2PAA111695-600 G 255
G Identifying Node Functions a G.5 Identifying Node Functions

1. Analyzing the Installed software on the nodes - It is possible to identify where


a Node Function(s) is configured by analyzing some installed software on nodes
in 800xA 5.x System. Refer to Collecting Data from Existing System 800xA 5.0
SP2, on how to collect installed software information using System Checker
Tool.
Table G.3: Identifying Node Functions using Installed Software

Node Function to be selected in 800xA 6.0


Where it was configured in 800xA 5.x System
System
Profibus and HART Connectivity Services Check for node with installed Software: "ABB
Profibus Device Integration Library"
AC100 Connectivity Services Check for node with installed Software: "ABB AC
100 OPC Server"
AC 800M SoftController Check for node with installed Software: "ABB Base
Software for SoftControl"

2. Fetch Node Type Information using System Checker Tool -


System Checker Tool has the functionality to identify the Node Type information
of an 800xA 5.x system. Refer to Collecting Data from Existing System 800xA
5.0 SP2, on how to collect Node Type information using System Checker Tool.
Following Node functions can be identified automatically using System Checker
Tool functionality.
Table G.4: Identifying Node Types using System Checker Tool

Node Function to be selected in 800xA 6.0


Where it was configured in 800xA 5.x System
System
Asset Optimization Services Node Identified: AO
Asset Optimization Services Additional Node Identified: AO
Batch Management Primary Services Node Identified: Batch
Batch Management Secondary Services Node Identified: Batch
Information Manager - IM Services Node Identified: IM

256 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions

To identify if a Batch Server identified by System Checker Tool is Primary or


Secondary, check the Value of the following registry entry on the batch servers:
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Produce IT\Batch\
BatchNodetype.
3. Analyzing the 800xA Service Structure - Service Structure of existing 800xA
5.x system can be analyzed to find where specific node function(s) are configured.
a. Open Plant Explorer Workplace.
b. Navigate to Service Structure >Services > ServiceName, Service >
ServiceGroup Name, Service Group > Service Provider Name, Service
Provider.
c. Select Service Provider Definition aspect.
d. The Node field in Configuration Tab gives the node where a node function
is configured.

Figure G.5: Service Provider Configuration

2PAA111695-600 G 257
G Identifying Node Functions a G.5 Identifying Node Functions

Table G.5: Identifying Node Functions using Service Structure

Node Function to be selected in


Where it was configured in 800xA 5.x System
800xA 6.0 System
Alarm Analysis Services Check the configuration of Service: "Alarm Analysis"
Alarm Logger Services Check the configuration of Service: "Alarm Logger"
Basic History Services Check the configuration of Service: "Basic History"
Note: On nodes with Information Management - IM
History Services or Information Management - 800xA
History Archive, Basic history is automatically configured.
There is no need to add the Basic History node function or
record/modify the Basic History Service provider and group
names for nodes with either the Information Management
- IM History Services or Information Management -
800xA History Archive node function.
External Alarm Services Check the configuration of Service: "External Alarm"
Property Transfer Services Check the configuration of Service: "Property Transfer"
Calculation Services Check the configuration of Service: "Calculation Server"
NOTE: If more than one service group exists, identify the
service group names, the service provider names for each
service group and the nodes the service provider are
running on.
Application Scheduler Services Check the configuration of Service: "Scheduler"
NOTE: If more than one service group exists, identify the
service group names, the service provider names for each
service group and the nodes the service provider are
running on.
Advant Master Connectivity Services Check the configuration of Service: MasterBus 300 RTA
Management

4. Analyzing the 800xA Control Structure - Configuration of Control Structure of


existing 800xA 5.x system can be analyzed to find where specific node function(s)
are configured.
a. Open Plant Explorer Workplace
b. Navigate to the OPC data source aspect as mentioned in Table G.6.

258 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions

c. Click View.
d. Select any one of the providers, click View.
e. The Node field in Configuration Tab gives the node where a node function
is configured.

Figure G.6: OPC Source Configuration

Table G.6: Identifying Node Functions using Control Structure

Node Function to be selected in


Where it was configured in 800xA 5.x System
800xA 6.0 System
SoftPoint Services a) Navigate to Control Structure > Soft Point Server, Soft
Point Generic Control Netwrok.
b) Check the configuration of aspect: Adapter Data Source
Definition
Foundation Fieldbus Connectivity a) Navigate to Control Structure > Subnet name, HSE Subnet
Services b) Check the configuration of aspect: OPC Data Source
Definition

2PAA111695-600 G 259
G Identifying Node Functions a G.5 Identifying Node Functions

Table G.6: Identifying Node Functions using Control Structure


(Continued)

Node Function to be selected in


Where it was configured in 800xA 5.x System
800xA 6.0 System
PC, Network and Software a) Navigate to Control Structure > IT Server, IT OPC Sever
Monitoring services Network
b) Check the configuration of aspect: OPC Data Source
Definition
PC, Network and Software a) Navigate to Control Structure > IT Server, IT OPC Sever
Monitoring services Additional Network
b) Check the configuration of aspect: OPC Data Source
Definition
DCI Connectivity Services a) Navigate to Control Structure > Symphony DCI OPC
Server Network.
b) Check the configuration of aspect: OPC Data Source
Definition
800xA for Harmony Connectivity a) Navigate to Control Structure > Harmony, Harmony OPC
Services Server work.
b) Check the configuration of aspect: OPC Data Source
Definition
800xA for MOD 300 Connectivity a) Navigate to Control Structure > MOD OPC Server Network
Services b) Check the configuration of aspect: MOD OPC Data Source
Definition
IEC 61850 Connectivity Services a) Navigate to Control Structure > IEC OPC Server Instance
name, IEC61850 OPC Serve
b) Check the configuration of aspect: OPC Data Source
Definition
OPC Server AC 800M a) Navigate to Control Structure > Control Network Name,
Control Network
b) Check the configuration of aspect: OPC Data Source
Definition

260 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions

Table G.6: Identifying Node Functions using Control Structure


(Continued)

Node Function to be selected in


Where it was configured in 800xA 5.x System
800xA 6.0 System
800xA for AC870P/Melody a) Navigate to Control Structure > Melody system, Melody
Connectivity Services System > Melody Network Name, Melody Network
b) Check the configuration of aspect: OPC Data Source
Definition
PLC Connectivity Services a) Navigate to Control Structure > PLC Controlnetwork name
, PLC Generic Control Network
b) Check the configuration of aspect: Adapter Data Source
Definition

Following node functions are configured on Primary Aspect Server node by default.
• Aspect Services
• Event Storage Services
• Central Licensing System
• Device Library Wizard Services
Node Function: OPC Client Connection Services, need to be selected manually
if the node is hosting third party OPC Clients.
Following node functions were installed on all nodes by default in 800xA 5.x
systems but in 800xA 6.0, you can choose where to install them.
• Information Manager Desktop Tools
• Bulk Data Manager
In 800xA 5.x systems, the node having the folder configserver in 800xA Installation
drive (default is C:\configserver) is to be planned as Melody configuration server
with Node function: 800xA for AC870P/Melody Configuration Services.
Harmony Configuration Server is not required anymore in 800xA 6.0 system.

2PAA111695-600 G 261
G Identifying Node Functions a G.5 Identifying Node Functions

G.5.1 Planning Node Functions


The information collected from an existing 800xA 5.x system must be used to plan
the node functions in System 800xA 6.0 using System Configuration Console (SCC)
Tool. The node functions in System 800xA 6.0 depends on the system functions
selected while configuring the system.
SCC Tool > System Setup > Configure System > System Nodes tab > Allocate
functions...

Figure G.7: Planning Node Function using SCC Tool

262 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions

For more information on planning Node Functions, refer to System 800xA System
Guide Technical Data and Configuration (3BSE041434*).

Figure G.8: System Functions

2PAA111695-600 G 263
264 2PAA111695-600 G
H Footprint Reduction during U H.1 Introduction

Appendix H Footprint Reduction during


Upgrade

H.1 Introduction
System 800xA 6.0 makes better use of hardware than previous system versions. The
introduction of the Node Function concept allows more functionality per node.
This appendix describes the workflow and procedure to take advantage of the smaller
footprint in System 800xA during upgrade from previous system versions. The
procedure enables the reduction of number of nodes in the upgraded system.
The footprint reduction is achieved by identifying the node functions to be moved
and combined with other node functions in a node. Through this consolidation of
800xA functionality the number of nodes can be reduced during the upgrade while
keeping the same overall functionality of the System 800xA.

H.2 Example
The example illustration below demonstrates a simple example of moving the node
functions from the connectivity server to the aspect server during the upgrade to
reduce the footprint of the 800xA System.

2PAA111695-600 G 265
H Footprint Reduction during U H.3 Considerations

Figure H.1: Example

H.3 Considerations
The considerations to be taken before planning for an upgrade with footprint reduction:
• Footprint reductions is performed only during offline upgrade.
• Footprint Reduction of 800xA for AC 800M Connectivity Servers located in
different Control Network Areas is not supported.
• The following services are supported from one node to another during upgrade:
– OPC Server for AC 800M.
– PROFIBUS and HART Connectivity Services.
– PC, Network and Software Monitoring Services.
– Asset Optimization Services.
– IEC 61850 Connectivity Services.
– PLC Connect Services, SoftPoint Services.
– FOUNDATION Fieldbus Connectivity services
– Basic History Services.
– Advant Master Connectivity Services.

266 2PAA111695-600 G
H Footprint Reduction during U H.4 Source System Workflow

Performing Footprint Reduction for Advant Master Connectivity Services will


result in loss of any user defined aspect created for MB300 RTA Board Object
and RTA Load Object
• The intended reduction by combining the node functions must be as per the
constraints and specifications specified in the System 800xA System Guide
Technical Data and Configuration (3BSE041434*).

H.4 Source System Workflow


The preparation and planning for upgrade of System 800xA must be started in enough
time before the actual upgrade. The source system must be analyzed and respective
node functions needs to be moved must be identified and the final system must be
according the specification of the System 800xA 6.0.

Figure H.2: Source System Workflow

H.4.1 Preparing the 800xA 5.0 SP2 System


System 800xA 5.0 SP2 must be prepared in order to be upgraded to System 800xA
6.0:
1. Migrate the existing Visual Basic Process Graphics (VBPG) aspects to the
corresponding Process Graphics aspects. Refer to System 800xA Engineering
Process Graphics Migration Tool (3BSE049231*) available in myABB/My
Control System.

2PAA111695-600 G 267
H Footprint Reduction during U H.4 Source System Workflow

Visual Basic Process Graphics (VBPG) is not supported in System 800xA


beginning System 800xA 6.0. It is mandatory to migrate all VBPG to PG2 graphics
before performing upgrade.
The System 800xA VBPG Search Tool is used to find VBPG aspects in 800xA
system that need to be migrated prior to a system upgrade. The tool can also
identify PG2 aspects that have references to VBPG aspects. For more information
on the tool, refer to System 800xA VBPG migration and System 800xA VBPG
Search Tool (3BSE081093).
All VBPG aspects Main View in System 800xA 6.0 and later will show a message:
This aspect is not supported and will not be available for operator actions.

2. Document following Windows settings:


a. Domain related information
b. DNS Settings
c. Users, groups and memberships
d. Other custom Windows settings.
The same settings must be use in the 6.0 System.
1. Collect the information about the System Functions, Node Functions and their
configurations from existing System 800xA 5.0 SP2. This information can be
obtained from existing plant documentation.
The information about existing System 800xA 5.0 SP2 can be used while planning
a similar System 800xA 6.0.
System Checker Tool can also provide some information about existing System
800xA 5.0 SP2. For more details, refer to Appendix G.
2. The 800xA System and software require preparatory procedures before performing
the upgrade. Perform the applicable procedures in the order presented in
Pre-Upgrade Procedures section before proceeding.
Symbol Factory Controls are no longer installed with the standard ABB 800xA
installation. A separate installation (ABB 800xA Symbol Factory) is needed to
use the Symbol Factory Controls. The ABB 800xA Symbol Factory installation
package is available on the media. A separate license is required to use the ABB
800xA Symbol Factory Controls.

268 2PAA111695-600 G
H Footprint Reduction during U H.5 Target System Workflow

H.5 Target System Workflow


The target system must be prepared with the similar workflow as described in the
Considerations and Upgrade Flow. The modification to the workflow described in
Considerations and Upgrade Flow are listed in Figure H.3.

Figure H.3: Target System Workflow

Prepare the following to prepare an 800xA 6.0 System for an upgrade:


1. Order the System 800xA licenses required for the 800xA 6.0 System. Refer to
System 800xA Licensing Information (2PAA111691*) for more information.
Order new hardware and third-party software required for the 800xA 6.0 System.
Refer to System 800xA Installation and Upgrade Getting Started (2PAA111708*)
for more information.
2. Migrate the redundant Domain Controllers. Refer to the Migrate Redundant
Domain Controllers appendix for more information. If it is a workgroup system,
ignore this step.
3. If the IPsec is configured in the source system (800xA 5.0 SP2) then after the
domain controller is upgraded, perform the following steps on the domain
controller before upgrading other nodes:
• Disable the existing group policy from the domain group policy object.

2PAA111695-600 G 269
H Footprint Reduction during U H.5 Target System Workflow

a. Go to Group Policy Management and choose Group Policy Objects.


b. Right-click the existing group policy.
c. Select GPO Status.
d. Select All Settings disabled.
• Disable the link of the existing group policy.
Right-click the existing group policy and clear the Link Enabled option.
• Delete the existing group policy.
Right-click the existing group policy in the Group Policy Objects and click
Delete.
• Follow the procedure mentioned in System 800xA Post Installation
(2PAA111693*) to configure the rules
4. If IPsec is not configured in the source system and if IPSec is required after
upgrade, then follow the procedure mentioned in System 800xA Post Installation
(2PAA111693*)to configure the rules.
5. Install the new operating system defined for the 800xA 6.0 System. Refer to
Prerequisite Section of System 800xA Installation and Upgrade Getting Started
(2PAA111708*) and perform all procedures relating to operating system settings
and pre-requisites.
6. Run the Node Preparation Tool (NPT) on all 800xA nodes.
a. Launch the Node Preparation Tool (NPT) by starting the Setup.exe from
the root level of the installation media to prepare the node.
The NPT copies the installation files to the local drive on the computer and
installs the 800xA Base Software. Thus preparing the node for deployment
of an 800xA System.
b. The Installation Type options are to be selected while running NPT, based
on the node functions selected on that node.
c. The User Account that is used for 800xA System installation must be a
member of the following groups:
IndustrialITUser
IndustrialITAdmin
Local Administrators

270 2PAA111695-600 G
H Footprint Reduction during U H.5 Target System Workflow

d. Click Start. The NPT prepares the node by installing the core products.
Click Close.
7. Perform the following to Create System on the node designated to be Primary
Aspect Server of the upgraded 800xA 6.0 system:
a. Launch System Configuration Console tool (SCC) as the 800xA Installing
User from ABB Start Menu > ABB IndustrialIT > System > System
Configuration Console.
b. Go to Create System task to create a System on the Primary Aspect Server
node and making the node ready for System deploy.
New System is created temporarily to create and export the system configuration
information that will be imported later on the upgraded system.

8. The System Configuration as intended in System 800xA 6.0 with consolidation


must be planned to capture the System Configuration information.
The consolidated plan must be include all the System functions and node functions
part of the source system, the consolidation is achieved to move functions from
one node to another node to reduce the number of servers. The system restore will
fail if any of the functions are missed in the plan.
Perform the following to plan the System 800xA 6.0 using System Configuration
Console.
a. Go to System Setup > Configure System task in SCC, plan the 800xA 6.0
System identical to 800xA 5.0 SP2 system. Refer to System 800xA
Installation and Upgrade Getting Started (2PAA111708*) on how to plan
the system.
b. Select the System Functions tab and select all the System functions part of
the source system
c. Select the node functions tab and add all the nodes as intended in the 6.0
(do not the add the nodes which are intended to be removed in 6.0). Select
the node functions for each node based on the intended configuration as per
footprint reduction.
During planning 800xA 6.0 system, few node functions require service group
name and service provider name to be entered. For standard nomenclature of
service group names and service provider names, refer to Appendix F.

2PAA111695-600 G 271
H Footprint Reduction during U H.5 Target System Workflow

For Batch Redundancy, a server node in the system needs to be configured and
designated as the Batch Witness Server. Refer to System 800xA Batch Management
Configuration (3BUA000146*) for more information.
For Advant Master Connectivity Server node function, it is mandatory to configure
Network Group Number, Network 1, Network 2, and Node Number. These
numbers are documented in the Pre-Upgrade Procedures.
9. The new plan created must be deployed only on the Primary Aspect Server to
import the System Configuration Aspects. All other nodes must be excluded
from the deployment. Perform the following to exclude all nodes except Primary
Aspect Server from deploy:
a. In the System Configuration Console Tool, under System Setup > Configure
System > System nodes,
b. Select and exclude all other nodes apart from Primary Aspect Server node
using Node actions... > Exclusion... option.

Figure H.4: System Configuration Console - Exclusion

272 2PAA111695-600 G
H Footprint Reduction during U H.5 Target System Workflow

10. Deploy system with only Primary Aspect Server by clicking on the Deploy
System.

Figure H.5: System Configuration Console - Deploy System

11. After successful deployment, export and save the System Configuration and
System Configuration State aspects from: Admin Structure > Administrative
Objects > Domains > <System Name>,Domain.

2PAA111695-600 G 273
H Footprint Reduction during U H.5 Target System Workflow

Figure H.6: System Configuration and System Configuration State Aspect

12. Delete the newly created 800xA system (see Step 7.).
a. Go to the Configuration Wizard and select System Administration, and
click Next.
b. Mark the system you want to delete. Click Next.
c. Select Systems and click Next.
d. Select Stop and click Next.
e. Select <system name> and click Next.
f. Select Delete, click Next.
g. Select <system name> and click Next.
h. Click Finish in the Apply Settings dialog box.

274 2PAA111695-600 G
H Footprint Reduction during U H.5 Target System Workflow

i. Wait a few minutes and when the Configuration Wizard appears again with
the System dialog box the deletion of the system is completed.
j. Click Exit.
k. Restart the Primary Aspect Server node.
13. Restore the 800xA 5.0 SP2 System backup on the Primary Aspect Server using
configuration Wizard. The User Account that is used for 800xA System restore
using the Configuration Wizard must be a member of the following groups:
• IndustrialITUser
• IndustrialITAdmin
• Local Administrators
Perform the following to restore the system using Configuration Wizard:
a. Open the Configuration wizard.
b. In the Select Type of Configuration dialog box, Select Restore System
and click Next.
c. In the Restore Selection dialog box, navigate to the path of 800xA 5.0
SP2 System Backup and click Next.
d. In the System Directories Selection dialog box, accept the default
selections and click the Next.
e. In the Node Configuration dialog box, check node name in the backup,
original node name and click Next.
f. In the Apply Settings dialog box, check summary info of selection and
click Finish.
g. Restart the node when advised during the restore procedure.
14. Check for messages in the log file (select the View Log check box in the
Configuration Wizard). Refer to Errors and Warnings during Upgrade to resolve
any received warning or error messages. Restart the node when advised during
the restore procedure.
15. Import the System Configuration and System Configuration State aspects. The
aspects are to be imported to the below path: Admin Structure > Administrative
Objects > Domains > System Name,Domain

2PAA111695-600 G 275
H Footprint Reduction during U H.5 Target System Workflow

16. To make the future updates and upgrades easier, the Service Group names and
Service Provider names must match either the default names for System 800xA
6.0 or the configured names for node functions with Server Groups and Providers
configured. It is mandatory to rename the Service Group and Provider names on
the Primary Aspect Server as per the default format before we proceed.
For Advant Master: Delete the Old MB300 RTA Board object (s) under Control
Structure > Root, Domain > MB300 Network object.
For more information about the correct names for service groups and providers,
refer to Appendix F.
If the Service Group names and Service Provider names do not match in the
configuration created by the system installer and imported in Step 15., Deploy
can fail or duplicate Service Groups and Providers may be created after upgrade.
In this case the duplicate Service Groups and Providers needs to be cleaned up
from 800xA 6.0 system looking at 800xA 5.0 SP2 reference System.
17. Refer to Compare the Number of Aspects and Objects and record the number of
aspects and objects in the system. Compare these values to those recorded when
the system was backed up.
18. Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (2PAA111693*) for more information on how to configure
affinity.
19. Verify the Aspect Directory Services to ensure that Aspect Servers are in correct
order.
a. Open the Plant Explorer Workplace.
b. Navigate to Service Structure > Services >Aspect Directory > Basic,
Service Group.
c. In the Service Group Definition aspect, click the Configuration tab.
d. Verify if the Primary Aspect Server node deployed is first in the list followed
by other Aspect Servers. If necessary, correct the order.

276 2PAA111695-600 G
H Footprint Reduction during U H.6 Node Function Configuration

Figure H.7: Order of Aspect Directory Services

20. In the System Configuration Console Tool, under System Setup > Configure
System > System Nodes, select the node to be deployed and enable for
deployment using Node actions... > Exclusion... > Include in deployment option.
Perform this action to include all remaining nodes.
21. If system has ABB 800xA for AC 100 then copy the saved BCD file folder to
the planned AC 100 Connectivity Server node on 800xA 6.0 system.
22. From Primary Aspect Server, deploy all the remaining nodes. Refer to System
800xA Installation and Upgrade Getting Started (2PAA111708*), for more
information.

H.6 Node Function Configuration


This procedure must be performed after deploying all nodes in System 800xA.

2PAA111695-600 G 277
H Footprint Reduction during U H.6 Node Function Configuration

H.6.1 OPC Server for AC 800M


The OPC server must be configured in the new target node.
Table H.1: Service Provider Configurations

Service Name Service Provider Configuration


OpcDA_Connector Node function OPC Server for AC 800M if included in Primary Aspect
Basic History Server:
• The service providers of the following services configured for the old
node must be configured to use the new target node.
Node function OPC Server for AC 800M if included other than Primary
Aspect Server:
• The service providers of the following services targeting the old node
must be deleted, as a new service provider will be created after deploy.

Time Service, if there is already a time service on the new target node then delete the
old service provider.
Perform the following procedure to configure the History Source:
1. Open Plant Explorer Workplace.
2. Use the Structure Selector to open the Control Structure.
3. Navigate to the path using the Object Browser: Root, Domain > Control
Network object
4. Click History Source aspect and verify the Service Group.
5. Change the Service Group, if required.

H.6.2 PLC Connect and Softpoint


Perform the following to move PLC Connectivity Service:
1. Perform the following procedure to configure Server settings and Alarm and
Event settings:
a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to: Root, Domain > PLC Generic
Control Network Object

278 2PAA111695-600 G
H Footprint Reduction during U H.6 Node Function Configuration

d. Click on Generic Control Network Configuration aspect.


e. Re-Configure Server Settings and Alarm and Event Settings.
2. Service Provider Configurations
Table H.2: Service Provider Configurations

Service Name Service Provider Configuration


Basic History Node function PLC Connect Services if included in Primary Aspect Server:
• The service providers of the following services configured for the old node
must be configured to use the new target node.
Node function PLC Connect Services if included other than Primary Aspect
Server:
• The service providers of the following services targeting the old node must
be deleted, as a new service provider will be created after deploy.

3. Perform the following procedure to configure History source:


a. Open a Plant Explorer Workplace.
b. Use the Structure Selector to open the Control Structure.
c. Use the Object Browser to navigate to: Root, Domain > PLC Generic
Control Network object
d. Click History Source Aspect and verify the Service Group.
e. Change the Service Group if required.

H.6.3 PROFIBUS and HART


The service providers of the following services configured for the source node must
be configured to use the new target node.
• OpcDA_Connector

H.6.4 Asset Optimization


Perform the following procedure to assign the Asset Optimization service group:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Control Structure.

2PAA111695-600 G 279
H Footprint Reduction during U H.6 Node Function Configuration

3. Use the Object Browser to navigate to: Root, Domain > Asset Optimization,
Asset Optimization > AO Server Object.
4. Click on Asset Optimization Server aspect and assign the Service Group.
For post upgrade steps, refer to the Asset Optimization in Post-Upgrade Procedure
Steps.

Asset Tree Service Provider Node


If the Asset Tree service was running on the replaced AO node then perform the
following steps to set the new Asset Tree Service Provider Node:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to: Services > AssetTree, Service >
AssetTree SG_1, Service Group > AssetTree SP_1, Service Provider
4. Select Service Provider Definition in the Aspect List Area.
5. Clear the Enabled check box and click Apply.
6. Set the Asset Tree Service Provider node to the new node designated to run the
Asset Tree Service in the Node: drop-down list box.
7. Select the Enabled check box and click Apply. This will set the Service Provider
hostname.
8. Verify that Service Status is Service.

AoWebServerNode
If the replaced AO Server node was designated as the AO Web Server then perform
the following steps to set the new AO Web Server Node.
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Control Structure.
3. Use the Object Browser to navigate to: Root, Domain > Asset Optimization,
Asset Optimization
4. Select Asset Optimization Configuration Properties in the Aspect List Area.
5. In the Preview Area, set the AOWebServerNode property to the new AO server
node.

280 2PAA111695-600 G
H Footprint Reduction during U H.6 Node Function Configuration

H.6.5 PC, Network and Software Monitoring


Perform the following to move PC, Network and Software Monitoring Service:

IT OPC Server Service Provider Node


Perform the following steps to set the new PC, Network and Software Monitoring
Service Provider Node:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to: Services > OpcDA_Connector > SG_IT
Server, Service Group > OPCDA_Provider_Nodename, Service Provider
4. Select Service Provider Definition in the Aspect List Area.
5. Change the service provider node name to the new target node and click apply.

IT SNMP Trap Service Provider Node


If the IT SNMP Trap service was running on the replaced PNSM node then perform
the following steps to set the new SNMP Trap Service Provider Node:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to: Services > IT SNMP Trap Service >
SNMP_Trap_Server, Service Group > SNMP_Trap_Server, Service Provider
4. Select Service Provider Definition in the Aspect List Area.
5. Clear the Enabled check box and click Apply.
6. Set the IT SNMP Trap Service Provider node to the node designated to run the
Trap Service in the Node: drop-down list box.
7. Select the Enabled check box and click Apply. This will set the Service Provider
hostname.
8. All the devices must be configured to point to the new trap server.

2PAA111695-600 G 281
H Footprint Reduction during U H.6 Node Function Configuration

Basic Computer Monitoring Configuration Tool


Perform the following procedure to start the configuration tool.
1. Open ABB Start Menu > ABB Industrial IT 800xA > Asset Optimization >
PC, Network and Software Monitoring.
2. Start Basic Computer Monitoring Configuration Tool.

H.6.6 IEC 61850 Connect


The service providers of the following services configured for the source node must
be configured to use the new target node.
• Event Collector
• OpcDA_Connector
Table H.3: Service Provider Configurations

Service Name Service Provider Configuration


Basic History Node function IEC61850 Connectivity Services if included in Primary
Aspect Server:
– The service providers of the following services configured for the old node
must be configured to use the new target node.
Node function IEC61850 Connectivity Services if included other than
Primary Aspect Server:
– The service providers of the following services targeting the old node must
be deleted, as a new service provider will be created after deploy.

Perform the following procedure to configure the IEC 61850 History Source:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Control Structure.
3. Use the Object Browser to navigate to: Root, Domain > IEC61850 OPC Server
object
4. Click History Source Aspect and verify the Service Group.
5. Change the Service Group if required.

282 2PAA111695-600 G
H Footprint Reduction during U H.6 Node Function Configuration

H.6.7 FOUNDATION Fieldbus Connectivity services


1. Perform FFUpload from Object Type Structure > FFLibraries, Object Type
Group.
2. Open Project from Control Structure > Root, Domain > HSE Subnet Object >
FF Management aspect.
3. Perform Check if required.
4. In the Fieldbus Builder, navigate to FF Network > Network Configuration
(Context Menu).
5. Change the IP address of OPCServerFF for Client/Server Network and HSE
Subnet IP if required.
6. Save the Project and Reconcile the OPCServerFF.
Table H.4: Service Provider Configurations

Service Name Service Provider Configuration


Basic History Node function FOUNDATION Fieldbus Connectivity services if included
in Primary Aspect Server:
• The service providers of the following services configured for the old node
must be configured to use the new target node.
Node function FOUNDATION Fieldbus Connectivity services if included
other than Primary Aspect Server:
• The service providers of the following services targeting the old node must
be deleted, as a new service provider will be created after deploy.

H.6.8 Advant Master Connectivity Services


Node function Advant Master Connectivity Services if included in Primary Aspect
Server:
1. Go to Configuration Wizard > System Administration.
2. Select the System> Add RTA
3. Edit the Properties, same as provided for Node function Advant Master
Connectivity Services in Primary Aspect Server while planning in System
Configuration Console.
4. Click Next and Finish.

2PAA111695-600 G 283
H Footprint Reduction during U H.6 Node Function Configuration

5. Select MB 300 RTA Settings


6. Edit the Properties, same as provided for Node function Advant Master
Connectivity Services in Primary Aspect Server while planning in System
Configuration Console.
7. Click Next and Finish.
Table H.5: Service Provider Configurations

Service Name Service Provider Configuration


Basic History Node function Advant Master Connectivity Services if included in Primary
Aspect Server:
• The service providers of the following services configured for the old node
must be configured to use the new target node.
Node function Advant Master Connectivity Services if included other than
Primary Aspect Server:
• The service providers of the following services targeting the old node must
be deleted, as a new service provider will be created after deploy.

H.6.9 SMS and E-mail Messaging


If the Messenger service was running on the replaced node then perform the following
steps to set the new SMS and E-mail Messaging Service Provider Node:
1. Open a Plant Explorer Workplace.
2. Use the Structure Selector to open the Service Structure.
3. Use the Object Browser to navigate to: Services > Messenger Server, Service >
Messenger SG_1, Service Group > Messenger SP_1, Service Provider
4. Select Service Provider Definition in the Aspect List Area.
5. Clear the Enabled check box and click Apply.
6. Set the SMS and e-mail Messaging Service Provider node to the node designated
to run the Messenger Service in the Node: dropdown list box.
7. Select the Enabled check box and click Apply. This will set the Service Provider
hostname for SMS and e-mail Messaging.

284 2PAA111695-600 G
H Footprint Reduction during U H.7 Remove Nodes

H.7 Remove Nodes


The following procedure to be performed to remove the node from System after all
the node functions associated to that node are moved to other node.
Verify that there are no services associated to the node to be removed by Navigating
the Node Administration Structure > Node Administration > All Nodes> Node
to be removed.
1. Open the Configuration wizard.
2. Select System Administration, Click Next.
3. Select the <System Name>, Click Next.
4. Select Nodes, Click Next.
5. Select Remove Server, Click Next.
6. Select the server intended to remove.
7. Clear the update remote node check box.
8. Click Next and then click Finish.
Verify the affinity settings to ensure best system performance. Refer to System
800xA Post Installation (2PAA111693*) for more information on how to configure
affinity.

H.8 Post Upgrade Procedures


Perform the post upgrade procedures for different node types as described in
Post-Upgrade Procedures.
For the functions moved to the new target node the post upgrade procedures must
be performed on the new target node.

2PAA111695-600 G 285
286 2PAA111695-600 G
I Revision History I.1 Updates in Revision Index B

Appendix I Revision History

The revision index of this User Manual is not related to the 800xA 6.0 System
Revision.
The following table lists the revision history of this User Manual.

Revision
Description Date
Index
A Published for 800xA 6.0 release April 2015
B Published for 800xA 6.0.1 release October 2015
C Published for 800xA 6.0.1 release October 2015
D Published for 800xA 6.0.1 release December 2015
E Published for 800xA 6.0.2 release April 2016
F Published for 800xA 6.0.3 release September 2016
G Published for 800xA 6.0.3.1 release November 2017

I.1 Updates in Revision Index B


The following table shows the updates made in this User Manual for
Revision Index B.

Updated Section/Sub-section Description of Update


Appendix H Footprint Reduction during Added
Upgrade
All sections Launchpad changes, VB changes
Appendix F 800xA 6.0 Service Group and AC 800M Service group and service
Service Provider Names provider updates

2PAA111695-600 G 287
I Revision History I.2 Updates in Revision Index C

I.2 Updates in Revision Index C


The following table shows the updates made in this User Manual for
Revision Index C.

Updated Section/Sub-section Description of Update


Section 4 Post-Upgrade Procedures Added a note under Application Change
Management
Appendix B Troubleshooting Added Import/Export Error

I.3 Updates in Revision Index D


The following table shows the updates made in this User Manual for
Revision Index D.

Updated Section/Sub-section Description of Update


Appendix H Footprint Reduction during Updated for Footprint reduction
Upgrade

I.4 Updates in Revision Index E


The following table shows the updates made in this User Manual for
Revision Index E.

Updated Section/Sub-section Description of Update


Appendix H Footprint Reduction during Updated for Footprint reduction for
Upgrade Advant Master and SMS and E-mail
Messaging

I.5 Updates in Revision Index F


The following table shows the updates made in this User Manual for

288 2PAA111695-600 G
I Revision History I.6 Updates in Revision Index G

Revision Index F.

Updated Section/Sub-section Description of Update


Appendix A Migrate Redundant Domain Removed “(Windows 2012 Server)”
Controllers reference on Page 205

I.6 Updates in Revision Index G


The following table shows the updates made in this User Manual for
Revision Index G.

Updated Section/Sub-section Description of Update


All Update supported operating system
related information across the document

2PAA111695-600 G 289
Index

Index
Numerics
800xA for AC 870P/Melody C
Preparation, 85 Calculations
800xA for MOD 300 Post upgrade, 173
Preparation, 85 Calculation service
800xA system backup Preparation, 96
Pre-upgrade, 97 Consistency check
Pre-upgrade, 41, 71, 186
A Controller online upgrade, 215
About this book, 13
AC 800M E
Post upgrade, 174 Engineering studio
Advant master Function designer system extensions
Post upgrade, 131 Preparation, 78
Pre-upgrade, 81–82, 130 Event collector service, 153
Alarm priority mapping aspects
Post upgrade, 114 F
Pre-upgrade, 76 FOUNDATION fieldbus
Asset optimization Post upgrade, 127
Post upgrade, 150 Pre-upgrade, 80
Preparation, 87
Autostart shortcut, 180 I
Information management
B Post upgrade, 162
Basic history service Preparation, 93, 99
Post upgrade, 161 Information management maintenance, 170
Basic history service data
Preparation, 103 M
Batch management Melody
Preparation, 75 Post upgrade, 146
Batch Management Minimum hardware requirements, 19
Shutdown script, 160
Toolbar, 160 O
Online upgrade controller level, 215

290 2PAA111695-600 G
Index

P RTA board
PC, network and software monitoring Post upgrade, 131
Preparation, 91
Planning, 18 S
PLC connect Safeguard
Post upgrade, 148 Post upgrade, 131
PreTreat2.dll, 87 Pre-upgrade, 81–82, 130
Post upgrade Scheduler service
AC 800M, 174 Preparation, 96
Advant master, 131 Scheduling
Alarm priority mapping aspects, 114 Post upgrade, 173
Asset optimization, 150 Shutdown script, 160
Basic history service, 161 SMS and e-mail messaging
Calculations, 173 Post upgrade, 159
FOUNDATION fieldbus, 127 Preparation, 92
Information management, 162 Restarting event collector service, 153
Melody, 146 System backup, 184
PLC connect, 148 System language package, 21
Process engineering tool integration, 180 System preparation
Reconfiguring group displays, 114 800xA for AC 870P/Melody, 85
RTA board, 131 800xA for MOD, 85
Safeguard, 131 Asset optimization, 87
Scheduling, 173 Basic history service data, 103
SMS and e-mail messaging, 159 Batch management, 75
PreTreat2.dll, 87 Calculation service, 96
Pre-upgrade, 30, 52, 67, 105 Information management, 93, 99
800xA system backup, 97 PC, network and software monitoring, 91
Alarm priority mapping aspects, 76 Process engineering tool integration, 97
Consistency check, 41, 71, 186 Scheduler service, 96
Engineering studio SMS and e-mail messaging, 92
Function designer system extensions, 78 System restore, 39, 61
FOUNDATION fieldbus, 80
Process engineering tool integration T
Post upgrade, 180 Toolbar, 160
Preparation, 97
U
R Upgrade order, 29, 51
Reconfiguring group displays, 114
Restarting event collector service, 153

2PAA111695-600 G 291
Index

W Warning and error messages, 201

292 2PAA111695-600 G
Contact us

www.abb.com/800xA Copyright © 2017 ABB.


www.abb.com/controlsystems All rights reserved.

2PAA111695-600 G