Documente Academic
Documente Profesional
Documente Cultură
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
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
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
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
8 2PAA111695-600 G
Table of Contents
2PAA111695-600 G 9
Table of Contents
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
2PAA111695-600 G 11
Table of Contents
INDEX
12 2PAA111695-600 G
1 About this User Manual 1.1 Version Described in 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.
2PAA111695-600 G 13
1 About this User Manual 1.3 Warning, Caution, Information, and Tip I
Warning icon indicates the presence of a hazard which could result in personal
injury.
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.
2PAA111695-600 G 15
16 2PAA111695-600 G
2 Introduction
2 Introduction
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
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.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
2PAA111695-600 G 21
2 Introduction 2.7 Online Upgrade
22 2PAA111695-600 G
2 Introduction 2.7 Online Upgrade
2PAA111695-600 G 23
24 2PAA111695-600 G
3 Considerations and Upgrade F 3.1 Considerations
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
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.
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.
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
2PAA111695-600 G 31
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
32 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
2PAA111695-600 G 33
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
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
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
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
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.
38 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
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.
2PAA111695-600 G 41
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
42 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
2PAA111695-600 G 43
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
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.
44 2PAA111695-600 G
3 Considerations and Upgrade F 3.3 Online Upgrade Flow
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
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
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.
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.
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.
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
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
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
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.
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.
58 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow
5. After excluding all the nodes except primary Aspect server, click 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
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
2PAA111695-600 G 63
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow
64 2PAA111695-600 G
3 Considerations and Upgrade F 3.4 Offline Upgrade Flow
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.
2PAA111695-600 G 67
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures
68 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.2 System-Wide Pre-Upgrade Procedures
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
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
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
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
74 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
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.
2PAA111695-600 G 77
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
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.
80 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
2PAA111695-600 G 81
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
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.
2PAA111695-600 G 83
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
84 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
2PAA111695-600 G 85
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
2PAA111695-600 G 87
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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
(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
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.
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.
94 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.3 Pre-upgrade Procedures before Maintenanc
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.
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.
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.
98 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba
2PAA111695-600 G 99
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba
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
2PAA111695-600 G 101
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba
102 2PAA111695-600 G
4 Pre-Upgrade Procedures 4.5 Pre-Upgrade Procedures for Local Data Ba
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.
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
106 2PAA111695-600 G
5 Post-Upgrade Procedures 5.2 Compare the Number of Aspects and Object
2PAA111695-600 G 107
5 Post-Upgrade Procedures 5.3 Reconfigure Aspects Created By System Ex
108 2PAA111695-600 G
5 Post-Upgrade Procedures 5.3 Reconfigure Aspects Created By System Ex
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}
2PAA111695-600 G 109
5 Post-Upgrade Procedures 5.4 Configure Hot key for the New Find Tool
110 2PAA111695-600 G
5 Post-Upgrade Procedures 5.6 IEC 61850 Connect
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.
112 2PAA111695-600 G
5 Post-Upgrade Procedures 5.6 IEC 61850 Connect
2PAA111695-600 G 113
5 Post-Upgrade Procedures 5.7 Customized Alarm Priority Mapping Aspect
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.
2PAA111695-600 G 115
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
• 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
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
6. Select the first option in the System Restore Wizard(2) as shown in Figure 5.7
and click Next.
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
8. Click Next to confirm the extract of device types as shown in Figure 5.9.
2PAA111695-600 G 119
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
10. Click Next to re-install the device types as shown in Figure 5.11.
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
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.
2PAA111695-600 G 121
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
122 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
2PAA111695-600 G 123
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
6. Click Exit.
124 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
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.
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
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.
2PAA111695-600 G 127
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
128 2PAA111695-600 G
5 Post-Upgrade Procedures 5.10 Device Management and Fieldbuses
2PAA111695-600 G 129
5 Post-Upgrade Procedures 5.11 PROFINET IO Feature Pack 1.2
130 2PAA111695-600 G
5 Post-Upgrade Procedures 5.12 800xA for Advant Master and 800xA for S
2PAA111695-600 G 131
5 Post-Upgrade Procedures 5.13 800xA for AC 100
132 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100
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.
134 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100
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
136 2PAA111695-600 G
5 Post-Upgrade Procedures 5.13 800xA for AC 100
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
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.
2PAA111695-600 G 139
5 Post-Upgrade Procedures 5.14 800xA for DCI
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.
2PAA111695-600 G 141
5 Post-Upgrade Procedures 5.15 800xA for Harmony
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.
2PAA111695-600 G 143
5 Post-Upgrade Procedures 5.15 800xA for Harmony
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.
2PAA111695-600 G 145
5 Post-Upgrade Procedures 5.16 800xA for AC 870P/Melody
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.
2PAA111695-600 G 147
5 Post-Upgrade Procedures 5.18 PLC Connect
148 2PAA111695-600 G
5 Post-Upgrade Procedures 5.18 PLC Connect
2PAA111695-600 G 149
5 Post-Upgrade Procedures 5.19 Asset Optimization
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
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.
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.
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
2PAA111695-600 G 155
5 Post-Upgrade Procedures 5.21 PC, Network and Software Monitoring Dev
156 2PAA111695-600 G
5 Post-Upgrade Procedures 5.22 800xA for Harmony and AC 870P/Melody Co
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.
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.
2PAA111695-600 G 159
5 Post-Upgrade Procedures 5.24 Batch Management
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
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.
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.
162 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management
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.
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.
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
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.
2PAA111695-600 G 167
5 Post-Upgrade Procedures 5.26 Information Management
168 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management
2PAA111695-600 G 169
5 Post-Upgrade Procedures 5.26 Information Management
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
170 2PAA111695-600 G
5 Post-Upgrade Procedures 5.26 Information Management
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.
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.
2PAA111695-600 G 173
5 Post-Upgrade Procedures 5.30 800xA 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.
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.
2PAA111695-600 G 175
5 Post-Upgrade Procedures 5.32 Engineering Studio
176 2PAA111695-600 G
5 Post-Upgrade Procedures 5.32 Engineering Studio
2PAA111695-600 G 177
5 Post-Upgrade Procedures 5.32 Engineering Studio
178 2PAA111695-600 G
5 Post-Upgrade Procedures 5.32 Engineering Studio
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*).
2PAA111695-600 G 179
5 Post-Upgrade Procedures 5.33 Process Engineering Tool Integration
180 2PAA111695-600 G
5 Post-Upgrade Procedures 5.35 Online Upgrade of a Multisystem Integra
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
2PAA111695-600 G 183
5 Post-Upgrade Procedures 5.38 System Backup
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
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
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.
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.
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.
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
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.
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.
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.
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
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
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
198 2PAA111695-600 G
A Migrate Redundant Domain Con A.7 Installing an Additional Windows Server
2PAA111695-600 G 199
200 2PAA111695-600 G
B Troubleshooting B.1 Errors and Warnings during Upgrade
Appendix B Troubleshooting
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.
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).
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.
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.
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.
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.
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.
• 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
2PAA111695-600 G 209
B Troubleshooting B.2 Troubleshooting during Deploy
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
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
This appendix lists the compatibility issues when upgrading from 800xA 5.0 SP2 to
800xA 6.0.
2PAA111695-600 G 213
214 2PAA111695-600 G
D Online Upgrade Controller Le D.1 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.
2PAA111695-600 G 215
D Online Upgrade Controller Le D.1 Online Upgrade Controller Level
216 2PAA111695-600 G
D Online Upgrade Controller Le D.2 Flowchart for Upgrading Controller Level
2PAA111695-600 G 217
D Online Upgrade Controller Le D.3 Flowchart for Extending Controller Level
218 2PAA111695-600 G
E 800xA for Harmony Online Upg E.1 Prerequisites
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).
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
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.
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.
222 2PAA111695-600 G
E 800xA for Harmony Online Upg E.3 800xA for Harmony Upgrade Procedure
2PAA111695-600 G 223
224 2PAA111695-600 G
F 800xA 6.0 Service Group and
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)
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)
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)
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)
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)
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)
230 2PAA111695-600 G
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300
2PAA111695-600 G 231
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300
232 2PAA111695-600 G
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300
2PAA111695-600 G 233
F 800xA 6.0 Service Group and F.1 ABB 800xA for MOD 300
234 2PAA111695-600 G
F 800xA 6.0 Service Group and F.2 ABB 800xA for DCI
F.1.2 Renaming MOD 300 AE Service Group and Service Provider Names
Perform this procedure after deploying all System 800xA 6.0 nodes.
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.
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
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
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
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)
240 2PAA111695-600 G
F 800xA 6.0 Service Group and F.3 800xA for AC 800M
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
242 2PAA111695-600 G
F 800xA 6.0 Service Group and F.4 ABB Asset Optimization
2PAA111695-600 G 243
244 2PAA111695-600 G
G Identifying Node Functions a G.1 Collecting Data from Existing System 800
2PAA111695-600 G 245
G Identifying Node Functions a G.1 Collecting Data from Existing System 800
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.
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.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*).
2PAA111695-600 G 249
G Identifying Node Functions a G.4 Identifying System Functions
250 2PAA111695-600 G
G Identifying Node Functions a G.4 Identifying System Functions
2PAA111695-600 G 251
G Identifying Node Functions a G.4 Identifying System Functions
252 2PAA111695-600 G
G Identifying Node Functions a G.4 Identifying System Functions
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
254 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions
For more information on planning System Functions, refer to System 800xA System
Guide Technical Data and Configuration (3BSE041434*).
2PAA111695-600 G 255
G Identifying Node Functions a G.5 Identifying Node Functions
256 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions
2PAA111695-600 G 257
G Identifying Node Functions a G.5 Identifying Node Functions
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.
2PAA111695-600 G 259
G Identifying Node Functions a G.5 Identifying Node Functions
260 2PAA111695-600 G
G Identifying Node Functions a G.5 Identifying Node Functions
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
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*).
2PAA111695-600 G 263
264 2PAA111695-600 G
H Footprint Reduction during U H.1 Introduction
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
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
2PAA111695-600 G 267
H Footprint Reduction during U H.4 Source System Workflow
268 2PAA111695-600 G
H Footprint Reduction during U H.5 Target System Workflow
2PAA111695-600 G 269
H Footprint Reduction during U H.5 Target System Workflow
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.
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.
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.
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
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
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.
2PAA111695-600 G 277
H Footprint Reduction during U H.6 Node Function Configuration
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.
278 2PAA111695-600 G
H Footprint Reduction during U H.6 Node Function Configuration
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.
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
2PAA111695-600 G 281
H Footprint Reduction during U H.6 Node Function Configuration
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
2PAA111695-600 G 283
H Footprint Reduction during U H.6 Node Function Configuration
284 2PAA111695-600 G
H Footprint Reduction during U H.7 Remove Nodes
2PAA111695-600 G 285
286 2PAA111695-600 G
I Revision History I.1 Updates in Revision Index B
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
2PAA111695-600 G 287
I Revision History I.2 Updates in Revision Index C
288 2PAA111695-600 G
I Revision History I.6 Updates in Revision Index G
Revision Index F.
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
292 2PAA111695-600 G
Contact us
2PAA111695-600 G