Industrial IT, 800xA - System, Post Installation 800xA... · In no event shall ABB be liable for...

IndustrialIT800xA - SystemSystem Version 4.1

Post Installation

NOTICEThe information in this document is subject to change without notice and should not beconstrued as a commitment by ABB. ABB assumes no responsibility for any errors thatmay appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB beliable for incidental or consequential damages arising from use of any software or hard-ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-mission from ABB, and the contents thereof must not be imparted to a third party nor usedfor any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license.

This product meets the requirements specified in EMC Directive 89/336/EEC and in LowVoltage Directive 72/23/EEC.

Copyright © 2003-2005 by ABB. All rights reserved. Release: June 2005Document number: 3BUA000156R4101

TRADEMARKSAll rights to trademarks reside with their respective owners.

3BUA000156R4101 5

TABLE OF CONTENTS

About This BookGeneral ............................................................................................................................13

New Installations .............................................................................................................13

Upgrades..........................................................................................................................13

System Installer ...............................................................................................................14

Intended User...................................................................................................................14

Use of Warning, Caution, Information, and Tip Icons ....................................................14

Document Conventions ...................................................................................................15

Version Numbers in Screen Captures ..............................................................................16

Related Documents..........................................................................................................16

Section 1 - IntroductionGeneral ............................................................................................................................19

System Checker ...............................................................................................................24

Section 2 - System Level TasksIntroduction .....................................................................................................................25

Creating a System............................................................................................................25

Adding System Extensions..............................................................................................31

Shared Folder for PROFIBUS and HART Device Integration.............................37

Shared Folder for FOUNDATION Fieldbus Device Integration..........................37

Specifying the Common Path for Fieldbus Builder Data.....................................38

Adding Connectivity and Application Servers ................................................................39

Adding Clients.................................................................................................................41

Redundancy .....................................................................................................................42

Overview .............................................................................................................42

Table of Contents

6 3BUA000156R4101

Redundant Aspect Servers .................................................................. 42

Redundant Connectivity Servers......................................................... 43

Configuring Redundancy ..................................................................................... 44

Adding Redundant Aspect Servers ..................................................... 44

Adding Redundant Connectivity Servers............................................ 45

Verifying the System and Servers Are Working as Configured........................... 45

Affinity ............................................................................................................................ 46

Overview ............................................................................................................ 46

Planning Load Balancing..................................................................................... 47

Load Balancing and System Performance ........................................................... 49

Affinity Configuration Procedures....................................................................... 50

Defining Users................................................................................................................. 58

User Roles ....................................................................................................................... 60

Core Function Setup for Scheduler and Calculations ..................................................... 60

Section 3 - SoftPoint ServerIntroduction ..................................................................................................................... 63

SoftPoint Server Configuration ....................................................................................... 63

Alarm and Event Configuration ...................................................................................... 69

Redundant Service Providers .......................................................................................... 73

Section 4 - Diagnostics Collection ToolIntroduction ..................................................................................................................... 75

Post Installation ............................................................................................................... 75

ABBResults Directory Share ............................................................................... 75

Configuring the ABBResults Directory Share..................................................... 77

Section 5 - SMS and e-mail MessagingIntroduction ..................................................................................................................... 79

Creating the Service Group and Service Provider .......................................................... 79

Configuring the Location of the Application Server....................................................... 81

Table of Contents

3BUA000156R4101 7

3BUA000156R4101 7

Section 6 - AC 800MIntroduction .....................................................................................................................83

Control Builder Configuration.........................................................................................83

Control Builder M Configuration Planning .........................................................83

Define Number of OPC Alarm and Event Subscriptions.....................................85

Downloading AC 800M Controller Firmware and Setting the IP Address .....................87

Download of Controller Firmware via Serial Line ..............................................87

Setting the IP Address for AC 800M ...................................................................90

Configuring IP Addresses on Redundant CPUs..................................92

Ethernet Download of Controller or Communication Interface Firmware ..........93

OPC Server Configuration...............................................................................................95

OPC Server for AC 800M Configuration Planning .............................................95

Additional Parameters ..........................................................................................97

Connect to Controllers .........................................................................................98

Saving Cold Retain Values.................................................................................100

Configure an OPC Data Access Connection......................................................101

Configure OPC Data Access Redundancy .........................................................104

Configure OPC Server for Alarm and Event Collection....................................104

Verify OPC Server Configuration ......................................................................108

System Alarms From AC 800M.........................................................................109

Section 7 - 800xA for TRIOIntroduction ...................................................................................................................111

Install TRIO Software ...................................................................................................111

Load TRIO System Extensions .....................................................................................111

Load Hardware Definition Files ....................................................................................112

Load Firmware ..............................................................................................................112

Section 8 - HART Device IntegrationIntroduction ...................................................................................................................115

Adaptation of the DCOM Settings ................................................................................115

Windows XP and Windows Server 2003 ...........................................................115

Windows 2000....................................................................................................116

Server Path Settings.......................................................................................................117

Table of Contents

8 3BUA000156R4101

Section 9 - PROFIBUS Device IntegrationIntroduction ................................................................................................................... 119

Adaptation of the DCOM Settings ................................................................................ 119

Windows XP and Windows Server 2003 ........................................................... 119

Windows 2000 ................................................................................................... 120

Section 10 - 800xA for Advant MasterIntroduction ................................................................................................................... 123

Connectivity Server Configuration................................................................................ 123

Add Multiple Connectivity Servers to the Same MB 300 Network .................. 123

Add the RTA Board............................................................................................ 124

RTA Board Network Settings........................................................................................ 125

Clock Synchronization....................................................................................... 126

Verify the RTA Board Network Settings............................................................ 127

Section 11 - 800xA for DCIIntroduction ................................................................................................................... 129

Creating a Symphony DCI OPC Server Object ............................................................ 129

Section 12 - 800xA for HarmonyIntroduction ................................................................................................................... 133

Initial Harmony Network Setup .................................................................................... 133

Harmony Alarm and Event OPC Provider Setup .......................................................... 134

Import the Harmony Configuration............................................................................... 135

New Installations ............................................................................................... 135

Reloading when a Backup Exists....................................................................... 136

Reloading when a Backup does not Exist.......................................................... 136

Synchronize the Aspect Directory................................................................................. 137

Configure Internet Explorer Options............................................................................. 137

SemAPI Information ..................................................................................................... 138

Setting Up the SCSI Device After Installation .................................................. 138

Windows Server 2003 ....................................................................... 138

Windows 2000 Server ....................................................................... 139

ICI Device Configuration Changed After Installation....................................... 139

Table of Contents

3BUA000156R4101 9

3BUA000156R4101 9

Section 13 - 800xA for MelodyIntroduction ...................................................................................................................141

Melody Alarm and Event OPC Provider Setup.............................................................141

Configure Internet Explorer Options.............................................................................143

Section 14 - 800xA for MOD 300Introduction ...................................................................................................................145

Setting Up Time Synchronization .................................................................................145

800xA System is Master Timekeeper ................................................................145

MOD 300 System is Master Timekeeper ...........................................................146

Time Synchronization on the MOD 300 Connectivity Server ...........................146

Time Synchronization on the Domain Controller ..............................................147

Time Synchronization on the MOD 300 Client .................................................147

Time Synchronization on the Service Provider Definition Aspect ....................148

Communication Settings ...............................................................................................148

Redundancy ...................................................................................................................150

Add Hyper Terminal ......................................................................................................151

Section 15 - PLC ConnectIntroduction ...................................................................................................................153

Basic Setup ....................................................................................................................153

Control Network Setup.......................................................................................154

Establish Control Network Connections ...........................................154

Create a New Control Network Object .............................................154

Create an Adapter Data Source Definition Aspect............................155

Configure the Adapter Data Source Definition Aspect.....................156

Add Service Provider ........................................................................157

Change Adapter Identity ...................................................................158

Create Control Network Objects for Other Control Networks .........159

Configure Source Definition Aspects................................................160

Change Service Group Names for the PLC Server ...........................160

Change Service Group Names for the SoftPoint Server ...................163

Create Source Definition Aspects .....................................................165

Table of Contents

10 3BUA000156R4101

Drag SoftPoint Object....................................................................... 166

Alarm and Event Setup ...................................................................................... 167

IEC 60870 Licensing..................................................................................................... 171

Software keys..................................................................................................... 171

Licensing Procedure .......................................................................................... 171

Enabling Temporary Authorization .................................................. 171

Complete and Send the License Files ............................................... 172

Complete Formal Licensing.............................................................. 173

Transferring the Software License..................................................................... 174

Other Licensing Options .................................................................................... 174

PLC Server .................................................................................................................... 175

Configure PLC Server Processes ...................................................... 175

Service Structure Example................................................................ 176

Section 16 - Asset OptimizationIntroduction ................................................................................................................... 177

AoWebServerNode........................................................................................................ 177

AssetMonitoring Service Provider Node ...................................................................... 178

Adding Additional AO Servers to the System .............................................................. 179

Asset Optimization Aspect Permissions Configuration ................................................ 182

Web-Enabled Views on Non-Industrial IT Systems...................................................... 183

DMS Calibration Integration......................................................................................... 183

DMS Software Users Configuration .................................................................. 184

DMS Server Configuration on non-800xA System Node ................................. 184

Changing the DMS Server Location.................................................................. 184

Recreate DMS Scheduled Tasks ........................................................................ 185

SAP/PM Integration ...................................................................................................... 187

Internet Explorer Configuration .................................................................................... 188

Excel Initialization ........................................................................................................ 188

Section 17 - Production ManagementIntroduction ................................................................................................................... 189

Batch Management........................................................................................................ 189

Table of Contents

3BUA000156R4101 11

3BUA000156R4101 11

Batch Management System Service Definitions................................................189

Shutdown Script .................................................................................................193

Print BMA Report Configuration.......................................................................193

Internet Explorer Configuration .........................................................................194

Initialize Office for Batch Users ........................................................................195

Batch Management Toolbar ...............................................................................195

Using Batch Management Advanced Templates Only.......................................195

Manufacturing Management..........................................................................................196

Create Virtual Directory .....................................................................................196

Create User Account ..........................................................................................199

Create Database..................................................................................................200

Database Layout Guidelines .............................................................200

Preliminary Tasks..............................................................................200

SQL Server Prerequisites ..................................................................201

Database Creation for SQL Server 2000...........................................201

Configure Plant Explorer ...................................................................................204

Configure Database Connection........................................................204

Internet Explorer Configuration .........................................................................204

Batch Management/Manufacturing Management Connection ..........................205

Component Security Configuration ...................................................................205

Install FrontPage Add-in ....................................................................................206

Section 18 - Information ManagementIntroduction ...................................................................................................................209

Information Management Setup ....................................................................................209

Other Post Installation Procedures .....................................................................211

Setting the User Information Management Services.....................................................212

Creating a Database Instance.........................................................................................213

Starting Process Administration Supervision (PAS) .....................................................222

Configuring the DBA (ADO) Data Provider for Oracle Data .......................................223

Create an ODBC Data Source for the Oracle Database ................................................224

Edit the ADO Data Provider Configuration ..................................................................226

Troubleshooting Install Errors.......................................................................................229

Table of Contents

12 3BUA000156R4101

Database Instance Errors ................................................................................... 229

Drive Space Configured Incorrectly ................................................. 229

Available Diskspace Changes Before You Run the Wizard.............. 230

Insufficient Space for Oracle System Files....................................... 231

Verifying Oracle Service Names........................................................................ 231

Information Management Profiles Client Post Installation........................................... 234

INDEX

3BUA000156R4101 13

About This Book

GeneralThis book describes post installation and system setup for the IndustrialIT ™ 800xA System Version 4.1.

The procedures described in this book require Windows ® Administrator privileges.

New InstallationsIf the system is not pre-installed, refer to Section 1, Introduction for guidelines on how to proceed with the post installation and system setup.

UpgradesIf an existing system requires upgrading from System Baseline 2.1/2 to System Version 4.1, from System Version 3.1 SP2 to System Version 4.1, or from System Version 4.0 to System Version 4.1, refer to Industrial IT, 800xA - System, Upgrade and Installation.

The security measures described in this document, for example, for user access, network security, firewalls, virus protection, and so on, represent possible steps that a user of an Industrial IT Extended Automation 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 Industrial IT Integrated Automation System.

System Installer About This Book

14 3BUA000156R4101

System InstallerA new system installation can be executed either semi-automatically using the System Installer as described in Industrial IT, 800xA - System, Automated Installation, or manually as described in this instruction.

Intended User This instruction is intended for installation engineers with experience with process control systems and Microsoft® Windows operating systems. In general, Microsoft Windows functions are not described in this instruction.

Use of Warning, Caution, Information, and Tip IconsThis publication includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows:

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

The System Installer does not install Manufacturing Management or 800xA for TRIO.

Electrical warning icon indicates the presence of a hazard which could result in electrical shock.

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

Caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to use a certain function

About This Book Document Conventions

3BUA000156R4101 15

in degraded process performance leading to personal injury or death. Therefore, comply fully with all Warning and Caution notices.

Document ConventionsThe following conventions are used for the presentation of material:

• The words in names of screen elements (for example, the title in the title bar of a window, the label for a field of a dialog) are initially capitalized.

• Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the ENTER key.

• Lowercase letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key, and so on.

• Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case).

• Press ESC E C indicates that you press and release each key in sequence (to copy a selected object in this case).

• The names of push and toggle buttons are boldfaced. For example, click OK.

• The names of menus and menu items are boldfaced. For example, the File menu.

– The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: select File > New > Type.

– The Start menu name always refers to the Start menu on the Windows Task Bar.

• System prompts/messages are shown in the Courier font, and user responses/input are in the boldfaced Courier font. For example, if you enter a value out of range, the following message is displayed:

Entered value is not valid. The value must be 0 to 30.

You may be told to enter the string TIC132 in a field. The string is shown as follows in the procedure:

TIC132

Variables are shown using lowercase letters.

sequence name

Version Numbers in Screen Captures About This Book

16 3BUA000156R4101

Version Numbers in Screen CapturesThe version numbers shown in some figures in this instruction are just examples and may not correspond to the current version.

Related DocumentsTable 1 lists the documentation referred to this instruction.

Table 1. Related Documentation

Category Title Description

System Administration

Industrial IT, 800xA- System, Administration and Security

3BSE037410R4101

Installation Industrial IT, 800xA - System, Installation

3BSE034678R4101

Industrial IT, 800xA - System, Automated Installation

3BSE034679R4101

Industrial IT, 800xA - System, Upgrade and Installation

3BSE036342R4101

Industrial IT, 800xA - System, System Checker

3BSE041447R4101

Software Industrial IT, 800xA - System, 800xA for Advant Master, Configuration

3BSE030340R4101

Industrial IT, 800xA - Production Management, Batch Management, Configuration

3BUA000146R4101

Industrial IT, 800xA - Information Management, Configuration

3BUF001092R4101

Industrial IT, 800xA - Information Management, Operation

3BUF001094R4101

Industrial IT, 800xA - Information Management, Configuration for Display Services

3BUF001093R4101

About This Book Related Documents

3BUA000156R4101 17

Software (continued)

Industrial IT, 800xA - System, 800xA for Melody, Configuration

3BDD011741R4001

Industrial IT, 800xA - Engineering, Engineering Workplace, Basic Engineering Functions

3BDS011223R4101

Industrial IT, 800xA - System, 800xA for Harmony, Configuration

3BUA000157R4101

Industrial IT, 800xA - System, 800xA for MOD 300, Configuration

3BUR002417R4101

Industrial IT, 800xA - Control and I/O, Basic Control Software, Introduction and Configuration

3BSE035980R4101

Industrial IT, 800xA - Control and I/O, OPC ® Server for AC 800M, Installation and Configuration

3BSE035983R4001

Industrial IT, 800xA - Asset Optimization, Configuration

3BUA000118R4101

Industrial IT, 800xA - Asset Optimization, Operation

3BUA000150R4101

Industrial IT, 800xA - Device Management, HART, Configuration

3BDD011748R4001

Industrial IT, 800xA - Device Management, PROFIBUS, Configuration

3BDD011750R4001

Industrial IT, 800xA - Device Management, FOUNDATION Fieldbus, Configuration

3BDD012902R4101

Other Industrial IT 800xA System - Automation System Network - Design and Configuration

3BSE034463R4101

Table 1. Related Documentation (Continued)

Category Title Description

Related Documents About This Book

18 3BUA000156R4101

3BUA000156R4101 19

Section 1 Introduction

GeneralBefore performing the procedures in this section:

• Install all 800xA System software.

• Install software keys for the purchased products. The software keys must be in place in order to complete some procedures in this section.

Refer to Industrial IT, 800xA - System, Installation for procedures on installing 800xA System software and software keys.

Table 2. Post Installation Sequence

Node Type Step

System Level Tasks Create a system. Perform this step at the designated Aspect Server. Refer to Creating a System on page 25.

Add system extensions. Mandatory for all systems. Refer to Adding System Extensions on page 31.

Add Connectivity and Application Servers. Mandatory for all systems, except single node systems.

Note: Application Servers (Information Management, Batch Management, and Asset Optimization) must also be added to the system as Connectivity Servers.

Refer to Adding Connectivity and Application Servers on page 39.

Add clients. Mandatory for all systems, except single node systems. Refer to Adding Clients on page 41.

Add redundant servers. Optional depending on redundancy requirements. Refer to Redundancy on page 42.

General Section 1 Introduction

20 3BUA000156R4101

System Level Tasks (continued)

Configure affinity. Optional depending on redundancy requirements. Refer to Affinity on page 46.

Define users. Optional. Refer to Defining Users on page 58.

Clock synchronization. Mandatory for all systems. Refer To Industrial IT, 800xA - System, Automation System Network, Design and Configuration.

Core function set-up: scheduler, calculations, softpoints. If you install Application Scheduler or Calculations without installing the Information Management Server, you must manually create the corresponding Service Group/Service Provider objects for each node where these services will run. Refer to the applicable documentation for details. This is done automatically (as part of standard post-installation) when you install these functions on an Information Management Server.

SoftPoint Server also requires some manual setup. Refer to Section 3, SoftPoint Server.

Check DCOM settings based on installed components and node type. Refer to Appendix A, DCOM Settings.

SoftPoint Server SoftPoint Server Configuration on page 63.

Redundant Service Providers on page 73.

Alarm and Event Configuration on page 69.

Diagnostics Collection Tool

Post Installation on page 75.

SMS and e-mail Messaging

Creating the Service Group and Service Provider on page 79.

Configuring the Location of the Application Server on page 81.

AC 800M Control Builder Configuration on page 83.

Downloading AC 800M Controller Firmware and Setting the IP Address on page 87.

OPC Server Configuration on page 95.

Table 2. Post Installation Sequence (Continued)

Node Type Step

Section 1 Introduction General

3BUA000156R4101 21

800xA for TRIO Install TRIO Software on page 111.

Load TRIO System Extensions on page 111.

Load Hardware Definition Files on page 112.

Load Firmware on page 112.

HART Device Integration

Adaptation of the DCOM Settings on page 115.

Server Path Settings on page 117.

PROFIBUS Device Integration

Adaptation of the DCOM Settings on page 119.

Server Path Settings on page 117.

800xA for Advant Master

Connectivity Server Configuration on page 123.

RTA Board Network Settings on page 125.

800xA for DCI Creating a Symphony DCI OPC Server Object on page 129.

800xA for Harmony Initial Harmony Network Setup on page 133.

Harmony Alarm and Event OPC Provider Setup on page 134.

Import the Harmony Configuration on page 135.

Synchronize the Aspect Directory on page 137.

Configure Internet Explorer Options on page 137.

SemAPI Information on page 138.

800xA for Melody Melody Alarm and Event OPC Provider Setup on page 141.

Configure Internet Explorer Options on page 143.

800xA for MOD 300 Setting Up Time Synchronization on page 145.

Communication Settings on page 148.

Redundancy on page 150.

Add Hyper Terminal on page 151.


Node Type Step

General Section 1 Introduction

22 3BUA000156R4101

PLC Connect Basic Setup on page 153.

IEC 60870 Licensing on page 171.

PLC Server on page 175.

Asset Optimization AoWebServerNode on page 177.

AssetMonitoring Service Provider Node on page 178.

Adding Additional AO Servers to the System on page 179.

Asset Optimization Aspect Permissions Configuration on page 182.

Web-Enabled Views on Non-Industrial IT Systems on page 183.

DMS Software Users Configuration on page 184 (only if using DMS Calibration Integration).

DMS Server Configuration on non-800xA System Node on page 184 (only if using DMS Calibration Integration).

Changing the DMS Server Location on page 184 (only if using DMS Calibration Integration).

Recreate DMS Scheduled Tasks on page 185 (only if using DMS Calibration Integration).

SAP/PM Integration on page 187 (only if using SAP/PM Integration).

Internet Explorer Configuration on page 188.

Excel Initialization on page 188.


Node Type Step

Section 1 Introduction General

3BUA000156R4101 23

Production Management

Batch Management Batch Management System Service Definitions on page 189.

Shutdown Script on page 193.

Print BMA Report Configuration on page 193.


Initialize Office for Batch Users on page 195.

Batch Management Toolbar on page 195.

Using Batch Management Advanced Templates Only on page 195.

Manufacturing Management

Create Virtual Directory on page 196.

Create User Account on page 199.

Create Database on page 200.

Install FrontPage Add-in on page 206.

Configure Plant Explorer on page 204.


Batch Management/Manufacturing Management Connection on page 205

Information Management

Information Management Setup on page 209.

Setting the User Information Management Services on page 212.

Creating a Database Instance on page 213.

Starting Process Administration Supervision (PAS) on page 222.

Configuring the DBA (ADO) Data Provider for Oracle Data on page 223.

Create an ODBC Data Source for the Oracle Database on page 224.

Edit the ADO Data Provider Configuration on page 226.

Troubleshooting Install Errors on page 229.


Node Type Step

System Checker Section 1 Introduction

24 3BUA000156R4101

System CheckerThe System Checker is designed for the purpose of checking, verifying, documenting, and troubleshooting an 800xA System. It includes the following:

• Node Report tool.• System Checker tool.• System Information Collector tool.• System Report tool.

The System Checker supports 800xA System Versions 3.x and 4.x. It also supports System Baseline 2.x with some limitations. Those limitations, as well as the installation and use of the System Checker is described in Industrial IT, 800xA - System, System Checker.

3BUA000156R4101 25

Section 2 System Level Tasks

IntroductionThis section describes post installation tasks that must be done at the 800xA System level before proceeding with the post installation tasks for the individual functional areas. These tasks include:

• Configure RNRP. Refer to Industrial IT, 800xA - System, Automation System Network, Design and Configuration.

• Creating a System.• Adding System Extensions.• Adding Connectivity and Application Servers.• Adding Clients.• Redundancy.• Affinity.• Defining Users.• User Roles.• Core Function Setup for Scheduler and Calculations.

Creating a SystemCreating a system will create the first Aspect Server (the Primary Aspect Server). Perform this on the node designated to be the Primary Aspect Server.

When the system is created, the user currently logged in is added to the system as a member of the Everyone, System Engineer, and Application Engineer IndustrialIT groups.

Use the same user account as the one used for installation when creating the system.

Creating a System Section 2 System Level Tasks

26 3BUA000156R4101

1. Start the Configuration Wizard on the node designated to be the Primary Aspect Server. Select:

Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard

2. The Select Type of Configuration dialog appears as shown in Figure 1. Select Create System and click Next.

Figure 1. Select Type of Configuration Dialog

Section 2 System Level Tasks Creating a System

3BUA000156R4101 27

3. The Define Name and Description of the System dialog appears as shown in Figure 2. Use Table 3 to configure this dialog.

Table 3. Create New System Dialog Settings

Field Description/Setting

Name Enter the system name.

Description Enter the system description (optional).

Server Node The current node (not an editable field).

Server Type Select Aspect Server if a dedicated node is used for the Primary Aspect Server (distributed configuration).

Select Aspect Server and Connectivity Server for single-node or small system configurations, where the Aspect and Connectivity Servers are combined.

Select Aspect Server and Connectivity Server for Information Management Consolidation nodes.

Figure 2. Define Name and Description of the System Dialog


28 3BUA000156R4101

4. Click Next.

5. The Define Paths to Data Directories dialog appears as shown in Figure 3. Specify the paths to data directories (or accept the defaults) and click Next.

Use a local disk on the Aspect Server node. Using a network disk will severely decrease the performance of the Aspect Server and risk availability of the entire system.

Figure 3. Define Paths to Data Directories Dialog

Section 2 System Level Tasks Creating a System

3BUA000156R4101 29

6. The Configure RNRP dialog appears as shown in Figure 4.

For a system application to comply with RNRP requirements, all communication should be made on the primary network interface. Therefore, filters must be specified for the System. The filters make sure the right path across the network is used by system software. Single node configuration also needs to configure RNRP. RNRP is always used by the system and should be configured according to Industrial IT, 800xA - System, Automation System Network, Design and Configuration.

The Configure RNRP dialog is used to specify the number of network areas where client and server nodes communicate with each other. Do not count network areas where only controllers and Connectivity Servers are connected.

To Apply filters to the system, select the Using RNRP check box and specify the number of areas in the Number of areas: field. Click Next and continue with Step 7.

Figure 4. Configure RNRP Dialog


30 3BUA000156R4101

7. The Configure Network Addresses dialog appears as shown in Figure 5.

The Configure Network Address dialog is intended for 800xA System applications if a redundant client server network is used, or if clients and/or servers are connected to a network in addition to the client server network. The purpose is to prevent the slow failover times.

The dialog has sets of three address fields:

– Primary Network Address.– Secondary Network Address.– Network address mask.

The number of sets is equal to the number of areas specified in Step 6.

Fill in the dialog with the proper information and click Next.

The Configure Network Address dialog does not configure whether RNRP will be or will not be used. RNRP will be used if its configuration is done implicitly or explicitly as described in Industrial IT, 800xA - System, Automation System Network, Design and Configuration.

Figure 5. Configure Network Addresses Dialog

Section 2 System Level Tasks Adding System Extensions

3BUA000156R4101 31

8. The Apply Settings dialog appears. Click Finish to accept the settings and create the system, or click Back to make changes. System creation takes some time.

The System creation is finished when the wizard shows the dialog in Figure 1.

9. Exit the Configuration Wizard.

10. To verify the system is running, hover the cursor over the ABB System Supervisor symbol in the Windows Notification area shown in Figure 6. The pop-up message should indicate that the system is Enabled.

Adding System Extensions800xA System functions have system extensions that must be added to the Aspect System. The system extensions must be installed on the primary Aspect Server Node. The available system extensions are listed in Table 4.

Figure 6. ABB System Supervisor Symbol

ABB recommends backing up OperateITData\ServiceManager\SMData.dat.

If adding system extension for PROFIBUS ® Device Integration or HART ®

Device Integration, follow the instruction for creating a shared folder before adding the system extensions. Refer to Shared Folder for PROFIBUS and HART Device Integration on page 37.

If adding system extensions for FOUNDATION ™ Fieldbus, follow the instructions for creating a shared folder before adding the system extensions. Refer to Shared Folder for FOUNDATION Fieldbus Device Integration on page 37.

Adding System Extensions Section 2 System Level Tasks

32 3BUA000156R4101

Table 4. System Extensions and Installation Sequence 1

Application System Extension

AC 800M AC800M Connect

AC800M SB2 Libraries

NOTE: This system extension is optional and should only be loaded if upgrading from System Baseline 2 (SB2). It includes libraries compatible with SB2. These libraries are not part of the AC800M Connect system extension.

Production Management Batch Management

Batch Advanced Templates

Manufacturing Management

Information Management (IM)

Industrial IT Archival

Inform IT Calculations (add manually if not installing IM application)

Inform IT History

Inform IT ODA

Inform IT Scheduler (add manually if not installing IM application)

SoftPoint Server ABB SoftPoint Server

Asset Optimization Asset Optimizer Server

Asset Monitor Environment

DMS Calibration Connect

Maximo Connectivity or SAP Connect System Extension (choose only one)



PC, Network and Software Monitoring

PC, Network and Software Monitoring


3BUA000156R4101 33

Engineering Studio Engineering Base

NOTE: If you intend to work with Absolute Reference Designations (ARD), configure the Plant Explorer according to the Engineering Workplace section of Industrial IT, 800xA - Engineering, Engineering Workplace, Basic Engineering Functions.

DM & PM Application

AC800M Signal Extensions

Function Designer

Reuse Assistant

Script Manager

Topology Designer

Function Designer for AC800M

Topology Designer for AC800M

Function Designer for AC 800M SB2 Libraries

NOTE:

This system extension is optional and should only be loaded if AC 800M SB2 Libraries have been loaded.

Table 4. System Extensions and Installation Sequence 1 (Continued)



34 3BUA000156R4101

Fieldbus Products

NOTES:

1. BEFORE running the system extension, follow the instruction for the specific Device Integration software described in Shared Folder for PROFIBUS and HART Device Integration on page 37 or Shared Folder for FOUNDATION Fieldbus Device Integration on page 37.

2. Follow the instructions in Specifying the Common Path for Fieldbus Builder Data on page 38 AFTER adding the FOUNDATION Fieldbus system extensions.

Fieldbus Builder PROFIBUS/HART

PROFIBUS Device Integration Library - Basics

PROFIBUS Device Integration Library - Asset Monitoring

HART Device Integration Library - Basics

HART Device Integration Library - Asset Monitoring

NOTE:

The HART Device Integration Library - Basics system extension must be loaded, even if only PROFIBUS Device Integration is used.

Function Designer for FB P/H

NOTE:

This system extension should only be loaded if Fieldbus Builder PROFIBUS/HART system extensions have been loaded.

Fieldbus Builder FF

FF Device Integration Library - Basics

FF Device Integration Library - Asset Monitoring

800xA for DCI DCI Connect

800xA for Safeguard Safeguard Connect

AC 400 Connect

800xA for MOD 300 MOD300Connect

MOD300OPCConnect

PLC Connect PLC Connect

800xA for Harmony Harmony Connect

800xA for Melody Melody Connect




3BUA000156R4101 35

To add the system extensions:

1. Start the configuration wizard on the primary Aspect Server node. Select:


2. Open the System Extension Load dialog by going to:

System Administration > Select System > System Extension Load

This produces a view similar to the one shown in Figure 7, with the available system extensions listed in the left pane.

Central Licensing System

Central Licensing System

800xA Documentation System Instructions

NOTE:1. The 800xA for TRIO system extension must be loaded separately after installation of 800xA for TRIO, which can

not be installed until the AC 800M system extensions are loaded. Refer to Section 7, 800xA for TRIO to install 800xA for TRIO and load its system extension after performing all other post installation procedures.

TC08045A

Figure 7. System Extension Load Dialog




36 3BUA000156R4101

3. 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 Thumb up/down icon indicates the status of the dependency evaluation. If the list in the right pane contains more than one system extension, click Press header to autosort to sort the system extensions load order with regard to dependencies.

5. All system extensions listed in the right pane should be marked with the Thumb up icon. Click Next and the Apply Settings dialog similar to the one shown in Figure 8 appears.

6. Click Finish. The system extensions will load into the system.

7. A progress dialog is shown during the load. Click View Log to view log messages during load.

8. When the load operation has finished, click Finished and view the Configuration Wizard log to verify that no errors occurred during the load.

9. Close the Configuration Wizard.

TC08046A

Figure 8. Apply Settings Dialog

Section 2 System Level Tasks Shared Folder for PROFIBUS and HART Device Integration

3BUA000156R4101 37

Shared Folder for PROFIBUS and HART Device Integration

Device Type Managers (DTM), installed on each client, may store their private internal data in a separate file on the hard disk. This private data could be; for example, log files, last open view, etc. However, private internal data does not mean the instance data set of the device parameter. As a default, the DTM stores the private data locally on each client.

This path must be configured in the Plant Explorer Workplace to ensure the synchronization of private data of DTMs.

A directory must be enabled for DTM access on every system node (redundant servers as well). Use the following directory:

<system drive>:\ABB Industrial IT Data\Engineer IT Data\Fieldbus Builder PH

Use the Windows file sharing functionality to enable access to this file directory on each Aspect and Connectivity Server.

1. Select the Fieldbus Builder PH folder that was created.

2. Right-click and select Sharing ... from the context menu that appears.

3. Choose Share this folder.

4. All 800xA System users must have full permissions for the shared folder. Access rights shall be limited to the IndustrialITUsers group.

Shared Folder for FOUNDATION Fieldbus Device Integration

1. Share the following folder for OPC Server data on all FOUNDATION Fieldbus Connectivity Server nodes:

<system drive>:\Program Files\ABB Industrial IT\Engineer IT\Fieldbus Builder FF\opcsrv

All 800xA System users must have full permission for the shared folder. Access rights shall be limited to the IndustrialITUser group.

To synchronize private data of a DTM, a specific file directory should be released for access from every client where the DTM is used. File/directory sharing allows other users to access this directory and make changes to its files.

Specifying the Common Path for Fieldbus Builder Data Section 2 System Level Tasks

38 3BUA000156R4101

2. Create and share a folder for the HSE Subnet configuration data of Fieldbus Builder FF on a primary Aspect Server, so that it is accessible from all 800xA System nodes, e.g.:

<system drive>:\ABB Industrial IT Data\Engineer IT Data\Fieldbus Builder FF Data

The shared folder shall be hidden. All 800xA System users must have full permissions for the share and the folder in the file system. Therefore, access rights shall be limited to the IndustrialITUser group.

Specifying the Common Path for Fieldbus Builder Data

After adding the system extensions for FOUNDATION Fieldbus, the prompt shown in Figure 9 appears asking for the common path for Fieldbus Builder FF data.

Select the path to the folder containing the FBB FF HSE Subnet configuration data. This is the same folder that was shared in Step 2 on page 38.

To hide a shared resource from users, type $ as the last character of the shared resource name. The $ then becomes part of the resource name. Users can map a drive to this shared resource, but they are unable to see it when they browse for it.

Storage of FBB FF HSE Subnet configuration data on a server is not redundant even if this server is redundant.

tc05721a

Figure 9. Common Path for FBB FF Data

Use an UNC path name in the form: \\node name\share name\.... Use an UNC path name in a single node system as well. This makes it easier to expand the system later.

Section 2 System Level Tasks Adding Connectivity and Application Servers

3BUA000156R4101 39

Adding Connectivity and Application ServersThis procedure is required for all Connectivity Servers, and for Application Servers (IM Servers, Batch Servers, MM Servers, AO Servers, and other applications such as 800xA for Harmony Configuration Server and 800xA for Melody Configuration Server) in a distributed (multinode) system.

1. Start the configuration wizard on the Primary Aspect Server.

2. Select System Administration and click Next.

3. Select the system and click Next.

4. Select Nodes and click Next.

5. Select Add Connectivity Server and click Next.

Do not use the SUBST command for the shared folder to associate the path with a drive letter.

Application Servers are added to the system as Connectivity Servers. There is not a separate option for adding Application Servers.

When a Secondary Batch Server is added, it must be added as a redundant Connectivity Server as described in Redundancy on page 42.

This procedure is not required when setting up a single node system.

Before adding any node, make sure that the node to be added has all required software installed. It must also have the same versions of system extensions software installed as the Aspect Server.

Adding Connectivity and Application Servers Section 2 System Level Tasks

40 3BUA000156R4101

6. The Add Connectivity Server Node dialog appears. Select the node from the drop-down list box as shown in Figure 10 and click Next.

7. Repeat Step 5 and Step 6 for all Primary Connectivity Servers (e.g. one for the 800xA for Advant Master Connectivity Server and one for the AC 800M Connectivity Server), but not the (optional) redundant Connectivity Servers. Redundant servers will be added in Redundancy on page 42. When all Connectivity Servers have been added, proceed to Step 8.

8. Verify that all Connectivity Servers are running after they are added.

a. Open a Plant Explorer Workplace.

If a node is not present in the drop-down list box, it could be due to configuration issues with name lookup. The node name can be typed in manually.

TC05971A

Figure 10. Add Connectivity Server Node Dialog

If a node is acting as a Connectivity Server for 800xA for Harmony or 800xA for Melody, add the node installed as the Primary Connectivity Server using this procedure. Refer to Adding Redundant Connectivity Servers on page 45 when adding the backup Connectivity Server.

Section 2 System Level Tasks Adding Clients

3BUA000156R4101 41

b. Use the Structure Selector to open the Node Administration Structure.

c. Use the Object Browser to select All Nodes, Node Group as shown in Figure 11.

d. Select System Status Viewer in the Aspect List Area.

e. The status is shown in the Preview Area.

Adding ClientsThis procedure is required for all workplace client nodes including Operator Workplace Clients, Engineering Studio Clients, IM Client Toolkit nodes, Batch Clients, MM Clients, and AO Clients.

TC05745A

Figure 11. Verifying that Servers and Services Are Running

Before adding any node, make sure that the node to be added has all required software installed. It must also have the same versions of system extensions software installed as the Aspect Server.

Redundancy Section 2 System Level Tasks

42 3BUA000156R4101

To add a client follow the steps:





5. Select Add Client and click Next.

6. The Add Client Node dialog appears. Select the node from the drop-down list box and click Next.

7. Repeat Step 5 and Step 6 for all Clients.

Redundancy To increase the uptime and eliminate loss of data, the 800xA System supports redundant server configurations. This is optional. One of the key features of redundancy and parallel servers is the fail-over functionality from one Service Provider to another. If the Service Provider with which a client application is communicating fails, or if the whole server node where the Service Provider is running fails, the client node will perform a fail-over and connect to a redundant Service Provider on another server node. Future transactions will be transferred to the redundant Service Provider.

Performance can be increased by load balancing. Refer to Affinity on page 46.

Overview

Redundant Aspect Servers

This section provides guidelines for planning a redundant installation, and instructions for configuring redundancy.

The redundant Aspect Server configuration is based on a one-out-of-two or two-out-of-three system.

Section 2 System Level Tasks Overview

3BUA000156R4101 43

In a redundant configuration of Aspect Servers the following base services are redundant:

• File Set Distribution (FSD) Service• Aspect Directory Service.• Cross Referencing Service.• System Message Service (parallel).• Time Service.• Alarm Manager Service.• Soft Alarms Service.• External Alarm Service.

The following base services are not redundant and will be running only on the Primary Aspect Server:

• Alarm Logger Service.• Licence Service.

Two redundant Aspect Servers must be working to allow client applications to read and write configuration data in the Aspect Directory database. Data is always automatically replicated between the server nodes in the Server Group. If only one Aspect Server is left, the system goes into a read-only mode in a two out of three system. This is to avoid inconsistency in the Aspect Directory database.

Redundant Connectivity Servers

The redundant Connectivity Server configuration is based on running two servers in parallel.

In a redundant configuration of Connectivity Servers, the following base services are parallel:

• Event Collector Service.• Basic History Service.• OpcDA_Connector Service.• OpcDA_Direct Server Service.• Property Transfer Service.• Time Service.

Services of the Connectivity Server are not fully redundant, but they are parallel. This means that they will not replicate data between Service Providers.

Configuring Redundancy Section 2 System Level Tasks

44 3BUA000156R4101

Only one redundant Connectivity Server is required for client applications to read and write process data.

Configuring Redundancy

Adding Redundant Aspect Servers

Before adding a redundant Aspect Server, verify that:

• The system exists and that the Primary Aspect Server is up and running. This is the node where the system was created (Creating a System on page 25).

• The node to be added has all required software installed. It must also have the same versions of system extensions software installed as the Aspect Server.





5. Select Add Redundant Server and click Next.

6. The Select Redundant Node dialog appears showing all available server nodes (Aspect and Connectivity Server nodes) as shown in Figure 12. Select the Aspect Server node to be duplicated and click Next.

7. In the next dialog box, select the node that will function as the redundant Aspect Server from the Server Node drop-down list box.

8. Select the Update remote node check box to update and activate the remote server node.

9. Click Next.

10. In the next dialog, click Apply.

11. For a two-out-of-three system, repeat these steps to add a third Aspect Server node.

Section 2 System Level Tasks Verifying the System and Servers Are Working as Configured

3BUA000156R4101 45

Adding Redundant Connectivity Servers

Use the procedure under Adding Redundant Aspect Servers on page 44 to add redundant Connectivity Servers, except select the Connectivity Server to duplicate in Step 6.

Verifying the System and Servers Are Working as Configured

To verify that the system is running, and that all servers are working as configured:

1. Open a Plant Explorer Workplace.

2. Use the Structure Selector to open the Node Administration Structure.

TC05972A

Figure 12. Select Redundant Node Dialog

If the system has both 800xA for Advant Master and AC 800M Connectivity Servers, perform the procedure for each one of them.

If a node is acting as a Connectivity Server for 800xA for Harmony or 800xA for Melody, perform the procedure for the backup Connectivity Server only.

When a redundant Connectivity Server is added, OPC Data Access redundancy must be configured manually. Refer to Configure OPC Data Access Redundancy on page 104.

Affinity Section 2 System Level Tasks

46 3BUA000156R4101

3. Use the Object Browser to select All Nodes, Node Group as shown in Figure 11.

4. Select System Status Viewer in the Aspect List Area.

5. The status is shown in the Preview Area.

AffinityAffinity is a means to ensure a predictable system configuration. It is optional and in most cases not necessary. This section provides a brief overview of the affinity concept, guidelines for planning affinity, and instructions for configuring affinity in the system.

Overview

Balancing the client load within a server group will achieve a predictable and stable running condition. This is especially important for Connectivity Servers, which handle large amounts of process data. Without load balancing, the problem can arise where one server node handles the larger part of the client node load, while the other server nodes are idling.

Affinity is configured using an affinity aspect placed in the Administration Structure. It specifies the order for which a client should pick servers for a certain service. For example, Client A must always connect to Connectivity Server A (when available) and Client B to Connectivity Server B. Refer to Figure 13 for an example of load balancing.

Different services may use different affinity settings. Affinity settings for clients to services provided by Connectivity Servers differs from the settings for services provided by Aspects Servers.

There are three basic steps:

• Create the Affinity aspect.• Configure the Affinity aspect.• Apply affinity settings to desired services.

These steps are described in detail in Affinity Configuration Procedures on page 50.

If affinity is not configured, clients will randomly select providers for their services.

Section 2 System Level Tasks Planning Load Balancing

3BUA000156R4101 47

Planning Load Balancing

Affinity can be configured for redundant Aspect Servers as well as Connectivity Servers. Before configuring affinity, you must plan how to balance the client load between the redundant servers of the system.

When developing a new load balancing plan it is always recommended to maintain a triangle-relationship between a particular client, Aspect Server, and Connectivity Server as shown in Figure 14. This is to minimize disturbance.

This means, for example, if Client 1 primarily accesses Aspect Server 3 and Connectivity Server 2, then Aspect Server 3 should also primarily access Connectivity Server 2, in order to maintain the triangle-relationship between Client 1, Aspect Server 3, and Connectivity Server 2.

Figure 13. Configuration Example of Load Balancing.

Figure 14. Triangle-Relationship for Planning Affinity

CLIENTA

CLIENTB

CONNECTIVITYSERVER

A

CONNECTIVITYSERVER

B

ASPECTSERVER

T05243A

CLIENT

CONNECTIVITYSERVER

ASPECTSERVER

T05244A

Planning Load Balancing Section 2 System Level Tasks

48 3BUA000156R4101

Relationships are always planned and drawn from the client point of view. The relationship between the Aspect Server and the Connectivity Server is bidirectional, as both servers can act as clients and access the other one.

If one server of a triangle fails and the client fails over to the next server, the triangle-relationship is lost. There are no lower prioritized triangle-relationship setups for failure conditions.

The planned affinity settings are then transferred into a load balancing table. This table is later used as base reference in the affinity configuration steps in Affinity Configuration Procedures on page 50. The numbers within the table indicate the order in which clients fail over to different servers. All triangle-relationships are entered into this table using the highest order number (1), indicating that this is the preferred access under normal running system conditions. Remaining cells are filled with lower order numbers, but they do not follow any triangle-relationships.

Figure 15 shows an example of a load balancing plan for a system with 2 clients, 3 Aspect Servers, and 2 Connectivity Servers. Bold numbers in Table 5 are results taken from the corresponding triangle-relationships.

The triangle-relationship is kept only under normal running conditions of the system.

It is not always possible to create triangle-relationships covering all servers without producing any conflicts in the load balancing table. The primary goal of planning load balancing is to define as many conflict free triangles as possible for the preferred client-server relationships, mainly for the operator stations, under a normal running system condition.

Figure 15. Load Balancing Plan Example

CLIENT 1

CONNECTIVITYSERVER 2

ASPECTSERVER 3

T05245A

CLIENT 2

CONNECTIVITYSERVER 1

ASPECTSERVER 2

Section 2 System Level Tasks Load Balancing and System Performance

3BUA000156R4101 49

Load Balancing and System Performance

Using affinity for load balancing optimizes the use of available system resources. However, a redundant configuration of Aspect or Connectivity Servers behaves differently from the classical redundancy concept, if affinity is applied.

In a normal redundant configuration without affinity, if a redundant server fails, all client connections will fail over from the used Service Provider to an idling machine and the performance of the redundant server cluster will remain constant.

If a redundant server fails in a redundant configuration with affinity defined, the fail-over functionality adds the work load of the failed server to a redundant server already in use. The additional work load could overload that server and degrade the performance of the redundant server cluster.

Table 5. Load Balancing Table for Load Balancing Plan in Figure 15

AffinityAspect

Server 1Aspect

Server 2Aspect

Server 3Connectivity

Server 1Connectivity

Server 2

Client 1 3 2 1 2 1

Client 2 2 1 3 1 2

Aspect Server 1

— — — 2 1

Aspect Server 2

— — — 1 2

Aspect Server 3

— — — 2 1

Connectivity Server 1

3 1 2 — —

Connectivity Server 2

2 3 1 — —

NOTE:Bold entries are results taken from the corresponding triangle relationships.

Affinity Configuration Procedures Section 2 System Level Tasks

50 3BUA000156R4101

Consider the following item for load balancing:

• To achieve best performance when all redundant servers are operating, and accept lower performance if one server node fails. In this case, ABB recommends defining affinity for redundant servers.

-or-

• To achieve predictable performance, both when redundant servers are operating normally and when one server node fails. In this case, ABB recommends to not use affinity for redundant servers.

Affinity Configuration Procedures

In this example, two Affinity Objects are created: CS and AS. This is the recommendation for a redundant system.

Recommendations:

• Set up a redundant system first, and verify it, before setting up the affinity.

• Use the following services when using affinity:

– File Set Distribution (FSD) Service.– Aspect Directory Service.– Basic History Service.– Cross Referencing Service.– Opc_DA Connector Service– System Message.

There basic steps are:

• Create the Affinity Objects.• Configure the Affinity Aspects.• Apply Affinity Settings to the Services.

For the client node, the affinity should be set in such a way that for all services running on an Aspect Server, the affinity is pointing to one (the same) Aspect Server in a 2 out of 3 setup. Do not point to different Aspect Servers for different services. This is also true for redundant (parallel) Connectivity Server pairs. The client should point to all services on one Connectivity Server, rather than mixing affinity settings.

Section 2 System Level Tasks Affinity Configuration Procedures

3BUA000156R4101 51

• Set Delay Fallback Time and Delay Fallback Time Spread.

Create the Affinity Objects. To create the Affinity objects:


2. Use the Structure Selector to open the Admin Structure.

3. Use the Object Browser to navigate to:

Administrative Objects > Inventory Object> Affinity

4. Right-click on the Affinity aspect type object and select New Object from the context menu that appears.

5. The New Object dialog appears as shown in Figure 16. Create a new object of type Affinity.

Make the changes under Set Delay Fallback Time and Delay Fallback Time Spread on page 54 only if the system is large and is experiencing poor performance when clients are reconnecting to a server. As a rule of thumb, only make these changes if the reconnection time is longer than 15 minutes and there are more than five clients on the server.

TC05726A

Figure 16. New Object Dialog


52 3BUA000156R4101

6. Specify a name (CS_Affinity) for the Affinity Object in the Name field.

7. Repeat the procedure to create and name the AS Affinity Object.

Configure the Affinity Aspects. To configure the Affinity aspects:

1. Select the Affinity Definition Aspect of an Affinity object in the Aspect List Area.

2. Select the Configuration tab in the Preview Area (Figure 17).

3. Click Add under the Selection Group/Node list to add clients to the list.

4. In the Item Contents list (to the right) specify the server nodes and server node groups and the order in which the client must connect to the servers. The client nodes select the server in order from top to bottom.

TC05724A

Figure 17. Configuring Affinity Aspects


3BUA000156R4101 53

5. Click Apply.

6. Verify the configuration in the Affinity Summary tab (Figure 18), which lists the configuration that has been done for all the nodes in the system.

7. Repeat this procedure for the AS affinity.

Apply Affinity Settings to the Services. ABB recommends setting up Affinity for services according to Table 6.

Configure the Services. ABB recommends setting up Affinity for services according to Table 6.

When the Affinity aspects have been configured, they must be set up to be used by the services in the system.

TC05746A

Figure 18. Affinity Summary Tab

Table 6. Affinity Services

Affinity objects Services

AS_affinity FSD, AspectDirectory, Cross referencing server, System Message

CS_affinity Basic History, OpcDA_Connector


54 3BUA000156R4101

1. Use the Structure Selector to select the Service Structure.

2. Use the Object Browser to select the service to be load balanced.

3. Select the Service Definition aspect in the Aspect List Area.

4. Select the Configuration tab in the Preview Area as shown in Figure 19.

5. Select the desired Affinity aspect from the Affinity drop-down list box and click Apply.

Set Delay Fallback Time and Delay Fallback Time Spread. The Delay Fallback Time defines how long a client will wait before it reconnects to a server that is

TC05725A

Figure 19. Configuring Affinity for a Service


3BUA000156R4101 55

restarting. The Delay Fallback Time Spread prevents the clients from reconnecting at the same time.

Values for these two parameters depend on the size and load of the system. Different values may have to be tried to find settings that suit the system best. As a rule of thumb, set the Delay Fallback Time to a time that equals the reconnection time (the time Aspect Directory needs to synchronize) if it is greater than 15 minutes. The Delay Fallback Time Spread can be set to as many minutes as there are clients connected to the server.

The Delay Fallback parameters are defined in the Registry for each of the clients.

To find out the reconnection time (the Aspect Directory synchronization time):

1. Open the Plant Explorer Workplace.



Services > AspectDirectory, Service > Basic, Service Group > AspectDirectory_Basic_The AspectDirectory of the Service of the server, AspectDirectory

as shown in Figure 20.

4. Select the Service Provider Definition aspect in the Aspect List Area.

5. Select the Configuration tab in the Preview Area.

6. Deselect the Enabled check box and click Apply.

7. Select the Enabled check box and click Apply.

Make these changes only if the system is large and it is experiencing poor performance when clients are reconnecting to a server. As a rule of thumb, only make these changes if the reconnection time is longer than 15 minutes and there are more than five clients on the server.


56 3BUA000156R4101

8. Measure the time during which the status text Current indicates

Synchronizing. If it is longer than 15 minutes, continue with this procedure to change the Delay Fallback Time.

9. Select:

Start > Run

to launch the Run dialog.

10. Enter regedit in the Open field to open the Registry Editor.

11. Navigate to the registry folder:

TC05736A

Figure 20. Measure the Synchronization Time

Be extremely careful when making changes in the registry. Do not make any changes in the registry without first making a backup copy of the registry. Refer to the online help for the registry editor on how to create a backup.

The remainder of this procedure must be performed on each client node.


3BUA000156R4101 57

My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > ABB > Afw > System Modules > AfwCSLib > 1.0-0 > private.

12. Double-click the DelayFallback entry to open the DelayFallback Settings dialog shown in Figure 21.

13. Enter the time in milliseconds in the Value data: field and click OK.

14. Double-click the DelayFallback_Spread entry to open the DelayFallback_Spread settings dialog shown in Figure 22.

15. Enter the time in milliseconds in the Value data: field and click OK.

16. Close the registry editor.

17. Restart the node.

Figure 21. DelayFallback Time Settings Dialog

Figure 22. DelayFallback_Spread Dialog

Defining Users Section 2 System Level Tasks

58 3BUA000156R4101

Defining Users The Users icon in the Configuration Wizard activates the User Administration dialog.

1. Start the configuration wizard on the Primary Aspect Server. Select:


2. The Select Type of Configuration dialog appears. Select System Administration and click Next.

3. The Select System dialog appears. Select the system and click Next.

4. The Select Type of Configuration for System dialog appears. Select Users and click Next.

5. The User Configuration dialog shown in Figure 23 appears. The upper frame shows the users in the Industrial IT 800xA System. Users can be added and deleted. To delete a user select the user in the upper frame and click Delete User.

TC05938A

Figure 23. User Configuration Dialog

Section 2 System Level Tasks Defining Users

3BUA000156R4101 59

6. To add a Windows user to an Industrial IT system group:

a. Click Add Windows Accounts.

b. The Add Windows Account dialog similar to the one shown in Figure 24 appears showing the Windows users of the domain that is selected in the Show members of drop-down list box. Select the Windows users to add to the Industrial IT system users and click Add.

c. Repeat until all desired Windows users are added to the Add names frame and click OK.

7. In the User Configuration dialog (Figure 23), it is possible to select the Industrial IT groups to which a Windows user must be a member. Select the Windows user in the upper frame and use Remove and Add to move Industrial IT groups to the Member of the field.

Click Reset to reset the group membership for a user to the state it was before any changes were made.

TC05939A

Figure 24. Add Windows Account Dialog

User Roles Section 2 System Level Tasks

60 3BUA000156R4101

User RolesUser roles help customize the environment to suit the needs of each user. This means that the operations that users need to act on are visible for them.

The following User Roles exist:

• Operator role must be held by all operators in a plant. The role makes it possible to use process control dialogs, acknowledge alarms, etc.

• Application Engineer role allows a user to do engineering operations and work with objects and applications built for objects (programs, graphics, etc.)

• System Engineer role must be held by a user that works with service, node, or user administration.

The user roles are associated with the Industrial IT groups. When a Windows user is added to an Industrial IT group, that user is assigned the corresponding role.

Core Function Setup for Scheduler and CalculationsCalculations and Application Scheduler may also be installed and run on other types of server nodes in the 800xA system (not Information Management Servers). In this case, the service group/service provider objects for those services must be created manually for each of those non-Information Management Servers.

You cannot enable a calculation until it has been assigned to a specific service group or service provider. If a calculation is using a softpoint as an input or an output, it is recommended to have the calculation aspect execute on the same computer.

After manually adding the system extension there are a number of configuration steps you need to perform to get the Scheduler service running.


2. Use the Structure Selector to open the Service Structure.

3. Create the service group object under the applicable service container in the Service structure for example, Calculation Server.

The Application Engineer role does not have an Operator role by default. This means that there are tasks an Operator can perform, that an Application Engineer can not.

Section 2 System Level Tasks Core Function Setup for Scheduler and Calculations

3BUA000156R4101 61

a. Select the service container, right-click and choose New Object from the context menu.

b. Assign a name to the new object. Typically, the name is based on the node node, then select Create.

4. Create the service provider object under the new service group object.

a. Select the new service group object, right-click and choose New Object from the context menu.

b. Assign a name to the new service provider object. The name is typically based on the node, then select Create.

5. Configure the service provider object to point to the node where the service (in this case Calculations) must run.

a. Select the Service Provider object in the object browser.

b. Select the Service Provider Definition aspect from the object’s aspect list.

c. Select the Configuration tab.

d. Use the Node pull-down list to select the node where the service will run.

e. Check the Enabled check box.

f. Click Apply.

Core Function Setup for Scheduler and Calculations Section 2 System Level Tasks

62 3BUA000156R4101

3BUA000156R4101 63

Section 3 SoftPoint Server

Introduction

The section describes how to configure the installed SoftPoint Server software. Configuration consists of:

• SoftPoint Server Configuration.• Alarm and Event Configuration.• Redundant Service Providers.

SoftPoint Server ConfigurationAfter adding the system extension there are a number of configuration steps you need to perform to get the SoftPoint Server service running.



3. Create a Service Group and Service Provider, under Softpoint Server, Service.

This section describes the SoftPoint Server as installed on any server. This server can be a Connectivity, Information Management, or Aspect Server.

If the 800xA System has several servers with the SoftPoint Server, create and configure one Service Group and Service Provider for each server. For redundant SoftPoint Server configurations add one service group for each redundant pair. Refer to Redundant Service Providers.

SoftPoint Server Configuration Section 3 SoftPoint Server

64 3BUA000156R4101

4. Set the correct node for the Service Providers. Refer to Figure 25.

5. Use the Structure Selector to open the Control Structure.

6. Create a SoftPoint Generic Control Network under the root object.

a. Select the Root, domain object and create a New Object.

b. In the New Object dialog, open Object Types, SoftPoint Basic Object Types and select SoftPoint Generic Control Network.

TC05969A

Figure 25. Service Structure

Section 3 SoftPoint Server SoftPoint Server Configuration

3BUA000156R4101 65

c. Enter a Name for the object and select Create.

7. Create the Adapter Data Source Definition aspect. Refer to Figure 26.

If the 800xA System has several servers with the SoftPoint Server, create and configure one SoftPoint Generic Control Network for each server.

TC05963A

Figure 26. Adapter Data Source Definition Aspect


66 3BUA000156R4101

8. Change the original Data Source Key:

...00000000}

to a non-zero value, for example:

....000001}

Make sure the keys are different in a multiserver environment. Use, for example:

....00002}

for the second one, and:

....00003}

for the third one.

9. Click New in the Preview Area to add a new OPCDA Service Group. The New Service Group dialog appears as shown in Figure 27.

10. Click Add, and select the server node. For redundant SoftPoint Server configurations refer to Redundant Service Providers.

TC05965A

Figure 27. New Service Group Dialog

Section 3 SoftPoint Server SoftPoint Server Configuration

3BUA000156R4101 67

11. Click OK.

12. Click Apply.

13. Click View in the Adapter Data Source Definition aspect in the Preview Area.

14. The Service Group Definition dialog is shown. See Figure 28 for Steps 15 through 17.

15. Select the Special Configuration tab. If running nonredundant Connectivity Servers, deselect the Allow parallel redundancy check box. This check box is enabled by default.

16. Change the Adapter identity from:

{00000000-0000-0000-0000-000000000000}

to:

ABB.AdsOPCAdapter.1

17. Click Apply and close the dialog.

TC05967A

Figure 28. Special Configuration Tab


68 3BUA000156R4101

18. Add the Source Definition aspect and connect the SoftPoint Server Service Group previously created. Refer to Figure 29.

TC05968A

Figure 29. Connecting the SoftPoint Service Group

Section 3 SoftPoint Server Alarm and Event Configuration

3BUA000156R4101 69

Alarm and Event Configuration Since the SoftPoint Server has built-in alarm and event detection for Boolean signals changing their values, as well as for Integer/Real signals exceeding or falling below a preset limit value, you may want to display those alarms in an 800xA System.

Figure 30 through Figure 33 show the configuration necessary.

TC05959A

Figure 30. AlarmManager Service

Alarm and Event Configuration Section 3 SoftPoint Server

70 3BUA000156R4101

1. Figure 30 shows the recommended setup for the AlarmManager Service.

2. For each server where SoftPoints services runs, the Event Collector Service must have a Service Group Service Provider created and set (also see Redundant Service Providers). This Service Group and Service Provider are specifically for alarm and event messages related to SoftPoints. Refer to Figure 31.

Deselecting Make new alarm entry each time a condition gets active is a system wide setting. This is only a recommendation for SoftPoint Server. It may conflict with other applications.

TC05960A

Figure 31. Node Settings

Section 3 SoftPoint Server Alarm and Event Configuration

3BUA000156R4101 71

3. In Special Configuration tab of the Service Group, select the SoftPoint Server alarm server:

Ads OPC Event Server

4. If an Ads OPC Event Server Collection Definition is not already created, click New to create one. Refer to Figure 32.

Figure 32. Collection Definition

Alarm and Event Configuration Section 3 SoftPoint Server

72 3BUA000156R4101

5. Click Edit to access the Alarm Collection Definition configuration where you set the functionality of the SoftPoint Server's alarm server. Refer to Figure 33.

6. Click Apply and close the dialog.

7. Click Apply in the Preview Area of the Service Group Definition aspect.

TC05962A

Figure 33. Configuration Tab

Section 3 SoftPoint Server Redundant Service Providers

3BUA000156R4101 73

Redundant Service Providers SoftPoint Redundancy is supported on an Information Manager Server pair. When installed on a redundant Connectivity Server, it should follow the rules as established in the connectivity for configuration. For greatest efficiency between Calculations and SoftPoints, put the Calculation Server (not redundant) on the same machine as the primary SoftPoint Server.

1. Configure a service group for each redundant pair of SoftPoint Servers.

2. Create two service providers, one for each SoftPoint Server, Figure 34.

Figure 34. Redundant Service Providers

Redundant Service Providers Section 3 SoftPoint Server

74 3BUA000156R4101

3. Configure the Adapter Data Source Definition aspect for the generic softpoint network, use the New Service Providers dialog to specify both service providers (one for each of the redundant SoftPoint Servers), Figure 35.

4. Configure the Event Collector Service Group with two service providers, Figure 36.

Figure 35. Specifying Redundant SoftPoint Service Providers

Figure 36. Redundant Service Providers

3BUA000156R4101 75

Section 4 Diagnostics Collection Tool

IntroductionThis section contains post installation procedures for the Diagnostics Collection Tool (DCT) software.

Post InstallationPost installation procedures include setting permissions on the ABBResults directory share (if required), and configuring the location of the ABBResults directory share.

ABBResults Directory Share

The default path for the folder created for ABBResults is:

...\ABBResults

It is set to be shared with full access rights for the service account. The installation is able to set the required permission on Windows XP Professional, Windows Server 2003, Windows 2000 Server with SP1 through SP3, but not on Windows 2000 Server with SP4, unless Microsoft hotfix KB817478 is installed.

To manually change the folder permissions on Windows 2000 SP4 nodes (without Microsoft hotfix KB817478 installed):

1. Use Windows Explorer to navigate to the ABBResults folder.

The following procedure, which only applied to Windows 2000 Server with SP4, in not necessary if Microsoft hotfix KB817478 is installed. This hotfix (Windows2000-KB817478-x86-ENU.exe) is available on 800xA System Installation DVD 1 in the following folder:

System1\Software\Microsoft\Hotfixes

ABBResults Directory Share Section 4 Diagnostics Collection Tool

76 3BUA000156R4101

2. Right-click on the folder and select Properties from the context menu that appears to open the ABBResults Properties dialog.

3. Select the Sharing tab to produce the view shown in the left portion of Figure 37.

4. Make sure Share this folder is selected. If it is not, select it.

5. Click Permissions to open the Permissions for ABBResults dialog shown in the right portion of Figure 37.

6. If only Everyone appears and is set to Read, click Add to open the Select Users and Groups dialog.

7. Add the service account used when the program was installed from the Select Users and Groups dialog and click OK.

TC05503A

Figure 37. Setting Permissions on ABBResults Folder for Windows 2000 SP4

Section 4 Diagnostics Collection Tool Configuring the ABBResults Directory Share

3BUA000156R4101 77

8. Select the service account added in Step 7 in the Permissions for ABBResults dialog.

9. Check the Full Control check box in the Allow column in the Permissions frame of the ABBResults dialog and click Apply and then OK.

Configuring the ABBResults Directory Share

The user can change the location of the ABBResults directory share. The ABBResults directory share is where the Diagnostics Collection Tool stores previously generated cabinet (cab) files. To change the location of the ABBResults directory share:

1. Run the ABBResults Directory Configuration program by selecting:

Start > All Programs > ABB Industrial IT 800xA > System > Diagnostics Collection Tool > ABBResults Directory Configuration

2. This launches the ABBDiagnostics Utility - Configuration dialog shown in Figure 38.

3. Select the desired folder for the ABBResults directory share and click OK.

4. Restart Diagnostics Collection Tool.

TC05464A

Figure 38. ABBDiagnostics Utility - Configuration Dialog

Configuring the ABBResults Directory Share Section 4 Diagnostics Collection Tool

78 3BUA000156R4101

3BUA000156R4101 79

Section 5 SMS and e-mail Messaging

IntroductionThe procedure in this section is required to correctly configure the location of an Application Server for SMS and e-mail Messaging in the Service Structure.

Post installation steps for SMS and e-mail Messaging include:

• Creating the Service Group and Service Provider.• Configuring the Location of the Application Server.

Creating the Service Group and Service Provider1. Open a Plant Explorer Workplace.



Services > Messenger Server, Service

4. Right-click on Messenger Server, Service and select New Object from the context menu that appears.

5. This opens New Object dialog. Type a name in the Name field and click Create. This creates a Service Group object.

6. Right-click on the newly created Service Group object and select New Object from the context menu that appears.

7. This opens New Object dialog. Type a name in the Name field and click Create. This creates a Service Provider object.

Creating the Service Group and Service Provider Section 5 SMS and e-mail Messaging

80 3BUA000156R4101

8. Figure Figure 39 shows the newly created Service Group and Service Provider objects.

9. Select Service Provider Definition in the Aspect List Area. This opens the Configuration tab.

10. Select the Messenger Service Provider Node (the node where the Messenger Service is running) in the Node: drop-down list box and click Apply.

11. The Current field should change from Undefined to Service.

Figure 39. Creating the Service Group and Service Provider Objects

Section 5 SMS and e-mail Messaging Configuring the Location of the Application Server

3BUA000156R4101 81

Configuring the Location of the Application Server1. Open a Plant Explorer Workplace.



Services > Messenger Server, Service > Basic, Service Group > Messenger Service_Basic_Node Name, Service Provider

(where Node Name is the name of the Primary Aspect Server node).

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

5. Click the Configuration tab in the Preview Area to produce a view such as the one shown in Figure 40.

6. If the Enabled check box is selected, deselect it and click Apply.

7. Select the Enabled check box and Click Apply.

TC05459B

Figure 40. Configuration Tab

Configuring the Location of the Application Server Section 5 SMS and e-mail Messaging

82 3BUA000156R4101

3BUA000156R4101 83

Section 6 AC 800M

IntroductionThis section contains procedures for:

• Control Builder Configuration.• Downloading AC 800M Controller Firmware and Setting the IP Address.• OPC Server Configuration.

Control Builder Configuration

Control Builder M Configuration Planning

The Control Builder M software needs to be configured by setting a number of parameters. The following is a summary of the most important parameters:

• Memory usage: The default value for the heap size may need to be increased for large applications. Select:

Help > About...

to see the remaining heap size. It must not be below 30 percent.

• File locations: Each user can have an individual Working Folder. Control Builder M installations on separate nodes must never have exactly the same working folder.

Before starting to make applications, carefully read Industrial IT, 800xA - Control and I/O, Basic Control Software, Introduction and Configuration to help plan and specify the following before starting to make the applications:

Select Help > About... with the project open in Control Builder.

Control Builder M Configuration Planning Section 6 AC 800M

84 3BUA000156R4101

• Tasks: Number of tasks, their names, cycle time, and time offset.

• IEC 61131-3 languages to use: ST, FBD, IL, LD, SFC.

• Using Control Modules or IEC 61131-3 Function Blocks.

• Applications: Number of applications, their names, and distribution to different controllers.

• Programs: Number of programs, their names, associated Tasks, and location to different controllers.

• Control Module types, Function Block types, and Functions: Reusable entities, plan any new ones needed in the applications.

If changes are needed to the Control Builder default settings:

1. Run the Setup Wizard (on the Engineering Station and other nodes where the Control Builder is installed). Select:

Start > All Programs > ABB Industrial IT 800xA > Engineering > Utilities > Setup Wizard

Figure 41 shows the Setup Wizard.

You must have Windows Administrator privileges to change the settings.

Figure 41. Control Builder Setup Wizard

Section 6 AC 800M Define Number of OPC Alarm and Event Subscriptions

3BUA000156R4101 85

2. Enter the required configuration parameters under System and Product.

3. Click Show Settings and check the settings (good summary of all configuration parameters).

4. To make additional changes refer to the other items under:

Tools > Setup > Station

in Control Builder M Professional.

Refer to the Online Help for detailed information on these items.

Define Number of OPC Alarm and Event Subscriptions

The controllers are by default set to deliver Alarm and Event data to only one OPC Server. If there is more than one OPC Server connected to a given controller, then adjust this setting. This is typically the case in redundant configurations.

The following procedure describes how to define the number of OPC Alarm and Event subscriptions.

Come back to this step at a later time if no controller applications are created at this point.

The number is 1 by default. This is how many OPC Servers will receive Alarm and Event data. The number should be adjusted to the number of OPC Servers connected to the controller. It should not be larger than the number of connected OPC Servers, as that will increase the memory load in the controller.

Perform the following procedure for each of the controllers in the network:

1. Open Control Builder (on the Engineering Station).

Start > All Programs > ABB Industrial IT 800xA > Engineering > Control Builder M

2. Control Builder must be in Offline mode. If it is not, click the Offline icon in the Control Builder (Figure 42).

Define Number of OPC Alarm and Event Subscriptions Section 6 AC 800M

86 3BUA000156R4101

3. Double click to open the “0” item for the controller as shown in Figure 42.

4. Select the Settings tab to view the parameters as shown in Figure 43.

5. Change AE Max number of event subscriptions to the amount of OPC Servers connected to this controller. This number is 1 by default. It should not be larger

TC05888A

Figure 42. Go offline by clicking the Offline icon

TC05894A

Figure 43. Parameters Under the Settings Tab

Section 6 AC 800M Downloading AC 800M Controller Firmware and Setting the IP Address

3BUA000156R4101 87

than the number of OPC Servers, as this would increase the memory load in the controller.

6. Click the Save and Close icon when finished.

7. Repeat Step 3 through Step 6 for each of the controllers in the network.

8. Click the Download Project and Go Online icon (Figure 44) in the Control Builder toolbar when finished.

Downloading AC 800M Controller Firmware and Setting the IP Address

This section describes how to download firmware for AC 800M - the basic runtime software in the controllers and its (optional) communication interfaces. It also describes how to initially set the IP address in the controllers.

Download of Controller Firmware via Serial Line

The Firmware for AC 800M must be downloaded to each AC 800M controller before it can be used. The factory supplied Firmware needs to be replaced by a Firmware version that matches the version of the Control Builder M.

At the first download of the Firmware, a serial RS-232 tool cable TK212 or TK212A is needed to connect the controller and the Control Builder M node, as well as the Control Builder M running on the node.

TC05886A

Figure 44. Click Download Project and Go Online

The version of the controller firmware for an AC 800M High Integrity Controller and the Control Builder must both be Version 4.1. The version of the controller firmware for a normal AC 800M Process Controller can be at Version 4.0 or Version 4.1 for use with the Control Builder Version 4.1.

Download of Controller Firmware via Serial Line Section 6 AC 800M

88 3BUA000156R4101

To download the firmware:

1. Connect the serial RS-232 tool cable between the node running the Control Builder and the Controller to the tool port, as specified in Table 7.

2. Select the appropriate COM port for the node (default COM 1).

3. Power up the controller.

4. Select:

Start > All Programs > ABB Industrial IT 800xA > Engineering > Utilities > Serial Firmware Upgrade

5. Select Settings from the dialog, followed by the COM port selected in Step 2.

6. Click Connect and hold down the Init/Reset pushbutton on the controller (for at least three seconds). The green R LED will start to blink. When this happens, release the button and the controller will perform a cold test. Wait about a minute until a message appears.

In the event of an error message:

Connect failed

check the cables and repeat the steps thus far in this procedure (refer to the Serial Firmware Upgrade Online Help).

Table 7. Cable Connection

Controller Tool Port Connector Cable Name

AC 800M COM 4 RJ 45 TK212 or TK212A

No program capable of blocking the selected COM port must be running during the upgrade procedure.

Section 6 AC 800M Download of Controller Firmware via Serial Line

3BUA000156R4101 89

If the connection is correct, then the following Serial Firmware Upgrade dialog appears as shown in Figure 45.

7. Select the Firmware and Control Builder versions.

8. Click Upgrade and wait five to ten minutes. The LED behavior during the upgrade procedure is described in the Serial Firmware Upgrade Online Help.

9. Hold down the Init/Reset pushbutton on the Controller (for at least three seconds). For redundant controllers, repeat this procedure for both CPUs.

Verification:

Before checking the Firmware download, or connecting an AC 800M Controller to a Control Network, its IP address must be set. Refer to Setting the IP Address for AC 800M.

Figure 45. Serial Firmware Upgrade Dialog

The version of the controller firmware for an AC 800M High Integrity Controller and the Control Builder must both be Version 4.1. The version of the controller firmware for a normal AC 800M Process Controller can be at Version 4.0 or Version 4.1 for use with the Control Builder Version 4.1.

Setting the IP Address for AC 800M Section 6 AC 800M

90 3BUA000156R4101

Setting the IP Address for AC 800M

Each AC 800M controller must have a unique IP address and associated subnet mask before it can be used in a Control Network. The IP address can be initially set after the firmware for the controller has been installed. The IP address can be changed via the Control Network once it has been initially set.

At the first setting of an IP address in a controller, a serial RS-232 tool cable TK212 or TK212A is needed to connect the controller and the Control Builder M node as well as the Control Builder M installed on the node.

Installation procedure:

1. Connect the RS-232 serial tool cable between the node running the Control Builder and the Controller to the tool port, as specified in Table 8. The serial line should still be connected to the primary CPU and the power on the backup CPU should be off. This should only be done if the controller is redundant.

2. Select the appropriate COM port for the node (default COM 1).

3. Select:

Start > All Programs > ABB Industrial IT 800xA > Engineering > Utilities > IPConfig

4. In the Settings menu, select Advanced mode.

5. Click Connect and hold down the Init/Reset pushbutton on the Controller (for at least three seconds) and wait up to one minute. If the connection procedure fails, then a time out message will appear. Check the cables and repeat the steps

Check that the Serial Firmware Upgrade tool is not running. If it is, that application will allocate the com port.

Table 8. Cable Connection

Controller Tool Port Connector Cable Name

AC 800M COM 4 RJ 45 TK212 or TK212A

No program capable of blocking the selected COM port must be running during the upgrade procedure.

Section 6 AC 800M Setting the IP Address for AC 800M

3BUA000156R4101 91

in this procedure up to this point. If OK, the current IP settings (the IP Ethernet® address and its associated Subnet mask) will be displayed in the IP Config dialog shown in Figure 46 (settings not shown in figure).

6. To connect to a redundant controller, refer to Configuring IP Addresses on Redundant CPUs on page 92.

7. Enter a unique Primary Ethernet Interface IP Address and Subnet mask according to the Planning and Preparation topic in Industrial IT, 800xA - System, Installation.

Example: IP address 172.16.0.201, Subnet mask, 255.255.252.0.

8. Click Set IP in the IPConfig dialog to send the new address to the controller.

9. If using a redundant CPU, set the addresses as described in Configuring IP Addresses on Redundant CPUs on page 92.

10. Restart controller, for example with the Init/Reset pushbutton.

TC05889A

Figure 46. IPConfig Dialog

Enable Autostart must normally be disabled. Refer to the IPConfig Online Help.

Setting the IP Address for AC 800M Section 6 AC 800M

92 3BUA000156R4101

Configuring IP Addresses on Redundant CPUs

For an AC 800M with redundant CPUs (e.g. PM861) four Ethernet IP addresses need to be entered:

• Primary Ethernet port on the Primary CPU.• Secondary Ethernet port on the Primary CPU.• Primary Ethernet port on the Backup CPU.• Secondary Ethernet port on the Backup CPU.

These four addresses must be known by both the Primary CPU and the Backup CPU, but you need only to set the IP addresses in the primary CPU. The backup CPU will be automatically configured by the primary.

When connecting with IPConfig in Step 5 under Setting the IP Address for AC 800M on page 90, first power off the backup CPU and connect the serial line to the primary, and connect the RCU link.

To set the two Backup IP addresses with IPConfig:

1. Make sure that the Primary Ethernet Interface IP-Address is correct (as set in Step 7 Setting the IP Address for AC 800M on page 90).

2. Select

Settings > Set Backup IP Addresses

3. Select:

Ethernet 1

4. Select the Obtain an IP address by using default rule check box.

5. Click Store Interface Settings.

6. Click OK when the dialog appears stating:

This will update the IP settings for the Backup CPU’s Ethernet interface 1. Continue?


Backup CPU’s Ethernet interface 1 stored successfully.

8. Select Ethernet 2.

9. Select the Obtain an IP address by using default rule check box.

Section 6 AC 800M Ethernet Download of Controller or Communication Interface Firmware

3BUA000156R4101 93

10. Click Store Interface Settings.


This will update the IP settings for the Backup CPU’s Ethernet interface 2. Continue?


Backup CPU’s Ethernet interface 2 stored successfully.

When powering up the backup CPU, its IP addresses will be assigned.

All addresses except the one for the secondary Ethernet port on the Primary can be set with IPConfig. That address is set in the Project created with the Control Builder (refer to Control Builder Configuration on page 83).

Verification:

Before connecting an AC 800M controller to a Control Network, its IP address can be checked by connecting to the controller again via the IPConfig tool.

Connect the network cable between CN1 on the controller CPU and the Control Network.

The controller IP address and connect status can be checked by opening a Command Prompt window on a node connected to the network, and entering:

ping <IP-address>

The controller should answer the ping command in a correct way.

The Windows Hyperterminal may also be connected via the serial line to the controller. The controller will write its status, e.g. the addresses it uses, to the terminal when a reset is made on the controller. (Select COM port, 9600 bit/s, 8 data bits, no parity bit, 1 stop bit, no flow control.)

Ethernet Download of Controller or Communication Interface Firmware

After the initial download of the controller firmware and setting of the IP address in the controller, further upgrades can be done via Ethernet (the Control Network). This also includes downloading or upgrading the firmware in communication interfaces connected to the controller (e.g. PROFIBUS DP - CI854).

Ethernet Download of Controller or Communication Interface Firmware Section 6 AC 800M

94 3BUA000156R4101

The download is done via the Control Builder M running on a node connected to the same Ethernet network as the controller. You can only upgrade firmware when the controller has no application program.

Download procedure:

1. On the control Builder M, select:

Tools > Maintenance > Remote System...

2. Click Show Remote Systems and select the controller, or type in the IP address of the controller and click Enter.

3. Select Show Firmware Information.

4. Evaluate the information for the current firmware in the controller CPU and other units. Firmware available on disk is presented in the combo boxes as shown in Figure 47.

5. If the desired firmware version you want to use is not listed in the combo boxes consider using the Browse button to go to another firmware directory. You may

This step requires the controller to be present in the currently opened project.

Each controller has to be updated individually (power up one/switch off the other) in a redundant pair.

TC05887A

Figure 47. AC 800M Firmware Information

Section 6 AC 800M OPC Server Configuration

3BUA000156R4101 95

find the version you require on the local hard disk, on the product CD-ROM or via the network in the list of firmware in the firmware.txt file. By selecting another firmware.txt, you can instruct the selected unit to use firmware other than the default firmware. You must update the firmware information by clicking the Update Information button.

6. Choose the new alternative (or the same) firmware for each unit and enable the corresponding Load new check box to the right.

7. Click the Download firmware button to start downloading.

8. The new firmware is downloaded after the old version has been removed from the controller CPU. When the upgrade is complete, the controller restarts automatically. During this sequence you cannot communicate with the controller.

Verification:

Confirm that the upgrade is complete by testing the firmware, or by reading the system log of the controller. If the upgrade program in the controller detects any errors while performing the upgrade, they are written to the system log of the controller.

OPC Server Configuration

OPC Server for AC 800M Configuration Planning

Before using this procedure, read the configuration procedure in Industrial IT, 800xA - Control and I/O, OPC Server for AC 800M, Installation and Configuration.

The OPC Server must be configured to specify which controllers will provide the OPC Data Access Server and the OPC Alarm and Event Server with data, and make other settings necessary for the operation of the OPC Server. The OPC Server is set up via an OPC Server Configuration panel.

When connected, the OPC Server has access to all relevant data in the controllers. The panel has two controller specification tabs, one for data access and one for alarms and events.

• OPC Server Data Access: Add IP address and connect all controllers that the OPC Data Access Server must provide data from/to.

OPC Server for AC 800M Configuration Planning Section 6 AC 800M

96 3BUA000156R4101

• OPC Server Alarm and Event: The OPC Alarm and Event Server gets data from controllers via subscription. Make the subscription by using the controller IP address. When the subscription of Alarm and Event is added to a controller, the address of the OPC Server will be stored in the controller. All Event Notifications from the controller will be transferred to the OPC Server.

In the OPC Server panel menu Settings, there are a number of setting alternatives to study, and possibly consider changing:

• Autoload Configuration: The configuration settings are saved in a file, and automatic load (autoload) can be enabled or disabled of an OPC Server configuration when the OPC Server starts up by selecting the Enable Autoload Configuration check box. Deselected check box is the default.

• Time Synchronization: If the time synchronization is enabled, by selecting the Enable check box, the OPC Server will time synchronize all connected controllers at a certain interval. Deselected check box is default.

• Update Rate: The cache update rate, set in milliseconds, controls how often the OPC Data Access Server updates its internal cache with data from a certain controller. To distinguish between fast and slow update rates there are five categories for simple values (integer, real, bool) and a separate category for strings.

• MaxNoOfAlarms: This setting can be found under

Settings > AE Settings

The OPC Server contains a list of all alarms that are not idle in the connected controllers. The MaxNoOfAlarms system variable defines the maximum number of alarms in the list. On overflow, the latest alarm is deleted and a system simple event is generated to announce the overflow. The list must be filled with less than 90 percent of the MaxNoOfAlarms value before a new system simple event can be generated. The range of values for MaxNoOfAlarms is 100 to 10,000. The default value is 5,000.

• Alarm and Event Queue size: This setting can be found under:

Settings > AE Settings

When the OPC Server is started the values are set to the default values. A golden rule is that the OPC Server must fetch the data twice as fast as the clients ask for it.

Section 6 AC 800M Additional Parameters

3BUA000156R4101 97

Every OPC Alarm and Event client holds a queue in this gateway to buffer event notifications. This number specifies the maximum number of items in every queue. Each queue has the same limitations. The default value is 2,000, the minimum value is 1,500 and maximum value is 5,000.

The Tools > Save cold retain values... menu in the OPC Server Panel displays the dialog for setting save cold retain values using the OPC Server. Cold retain values are values from control applications needed at a cold restart of a controller. Saving via the OPC Server can be done manually or periodically.

The option Save cold retain values is only available if the data access view is active and a controller is successfully connected. Refer to Saving Cold Retain Values on page 100.

Additional Parameters

If changes are required to the OPC Server default settings as described in OPC Server for AC 800M Configuration Planning on page 95:

1. Open the configuration dialog (normally on the Connectivity Servers). Select:

Start > All Programs > ABB Industrial IT 800xA > Control and I/O > OPC Server for AC800M 4.1 > OPC Server for AC 800M 4.1

2. Select Settings and select the menu item that you want to change.

3. Make the desired changes.

4. Click File > Save Configuration....

5. Select the file name of the OPC Server configuration, and save the file.

If additional parameters require changes:

1. Run the Setup Wizard (on the Engineering Station). Select:

Start > All Programs > ABB Industrial IT 800xA > Control and I/O > OPC Server for AC800M 4.1 > Setup Wizard

2. Enter the required configuration parameters under System and Product, for example change the heap size to a larger value. The heap must be set to the size of the application, but must not exceed the maximum recommended heap size. Start by using the default value and then increase the value according to the demands of the application.

Connect to Controllers Section 6 AC 800M

98 3BUA000156R4101

Connect to Controllers

To connect to controllers:

1. Open the configuration dialog (on Connectivity Servers and other nodes where the OPC Server is installed). Select:


2. Select the Data Access tab.

3. Select:

View > Available Controllers

4. Drag the IP address of the requested controllers to the Controller identity field in the OPC Panel window (clear old contents first) and click Connect. Refer to Figure 48.

If the service account (800xA Service account as entered in the System software user settings dialog) has not been specified yet, do this now. To get the service account information, launch the configuration wizard:

Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard, then select System software user settings dialog.

Figure 48. Drag the IP Address to the OPC Panel Window and Click Connect

Section 6 AC 800M Connect to Controllers

3BUA000156R4101 99

5. Do the same for Alarm and Event Server (the second tab in the OPC Panel window).

6. If the OPC Server asks to browse needed files when trying to connect, answer NO.

7. Select:

Settings > Time Synchronization

8. The Time Synchronization dialog appears. Deselect Enable as shown in Figure 49.


10. Enter a name for the configuration file and save the file.

11. Select

Settings > Autoload Configuration

12. Select the Enable Autoload Configuration check box.

If CNCP or SNTP is used on the Control Network, the MMS Time Synchronization from the OPC Server must be disabled.

Figure 49. Disable MMS Time Sync in OPC Server

Saving Cold Retain Values Section 6 AC 800M

100 3BUA000156R4101

13. Enter the name of the configuration file saved in Step 10, as shown in Figure 50.

14. Click Apply and Close.


16. Select the file name chosen in Step 10, and save the file.

Saving Cold Retain Values

The OPC Server for AC 800M can periodically save the Cold Retain values of the controllers, i.e. transfer them from the controllers and save the values into the Aspect Directory. This is configured in the OPC Server.

1. Open the configuration dialog (normally on one of the Connectivity Servers). Select:


TC05881A

TC05882A

Figure 50. Autoload Configuration

Section 6 AC 800M Configure an OPC Data Access Connection

3BUA000156R4101 101

2. Select the Data Access tab.

3. Select:

Tools > Save cold retain values

4. Select the Automatically check box.

5. The Save Cold Retain Values dialog appears as shown in Figure 51. Enter a suitable period time.

6. To start the saving of Cold Retain values, click Activate in the Save cold retain values dialog. This can also be done later. Click Close.


8. Select the file name of the OPC Server configuration, and save the file.

Configure an OPC Data Access Connection

An OPC Data Access connection can be located, established, and verified with the OPC Connector in the Connectivity Server.

1. Start the workplace login and open the Plant Explorer workplace (on the Connectivity Server).

TC05891A

Figure 51. Save Cold Retain Values Dialog

Configure an OPC Data Access Connection Section 6 AC 800M

102 3BUA000156R4101


3. Create a Control Network object under the root object:

a. Select the root object.

b. Right-click and choose New Object from the context menu that appears.

c. The New Object dialog appears. Select the Control Network object type and click Create.

4. Select the OPC Data Source Definition aspect for the Control Network object in the Aspect List Area.

5. Select the Connectivity tab in the Preview Area as shown in Figure 52.

TC05884A

Figure 52. Data Source Definition Aspect

Section 6 AC 800M Configure an OPC Data Access Connection

3BUA000156R4101 103

6. Click New. The New Service Group dialog appears as shown in Figure 53.

7. Click Add. The Add Service Provider dialog appears as shown in Figure 54.

8. Select the node name of the Connectivity Server as the OPC Server Provider and click OK.

9. Repeat Step 7 and Step 8 for an optional redundant Connectivity Server.

10. Click OK in the New Service Group dialog.

11. Click Apply in the Data Source Definition aspect.


Figure 54. Add Service Provider

Configure OPC Data Access Redundancy Section 6 AC 800M

104 3BUA000156R4101

Configure OPC Data Access Redundancy

After a redundant Connectivity Server has been added, OPC Data Access redundancy must be configured manually. The Data Source Definition aspects (OPC Data, Adapter Data, and Generic Data) that point to service groups that run on the redundant Connectivity Server must be configured. If several Data Source Definition aspects point to the same Service Group, it is sufficient to add redundant providers for one of them.

1. Go to the Data Source Definition aspect as shown in Figure 52.

2. Select the Connectivity tab in the configuration view of the aspect.

3. Click Modify. The Modify Service Group dialog appears.

4. Click Add. The Add Service Provider dialog appears.

5. Select the node name of the redundant Connectivity Server and click OK.

6. Click OK in the Modify Service Group dialog.

7. Click Apply in the Data Source Definition aspect.

Configure OPC Server for Alarm and Event Collection

An OPC Alarm Server (collector) must be connected for AC 800M Connect before getting any alarms and events.

Set up this collector connection as follows:

1. Make sure that the OPC Server is running with the controllers connected and configured.


3. User the Structure Selector to select the Service Structure.

The 800xA System Alarm and Event Server and OPC Server must run in the same node.

Section 6 AC 800M Configure OPC Server for Alarm and Event Collection

3BUA000156R4101 105


Services > EventCollector, Service


5. Create the Service Group and Service Provider Objects in Step 6 through Step 14, if they do not already exist.

6. Right-click on EventCollector, Service and select New Object from the context menu that appears.

7. The New Object dialog appears. Select Service Group and enter a name, such as AC800XGx (where x is a running number) and click Create.


TC05883A

Figure 55. Configure Alarm and Event

Configure OPC Server for Alarm and Event Collection Section 6 AC 800M

106 3BUA000156R4101

9. The New Object dialog appears. Select Service Provider and enter a name, such as AC800SP_nodename (where nodename is a Connectivity Server name) and click Create.

10. Select the Service Provider Definition aspect for the AC800SP_nodename Service Provider Object in the Aspect List Area.

11. Select the Configuration tab in the Preview Area as shown in Figure 56.

12. Select the name of the AC 800M Connectivity Server in the Node drop-down list box.

13. Click Apply.

14. Repeat Step 8 through Step 13 for a redundant Connectivity Server.

15. Use the Object Browser to navigate to the Event Collector Service Group previously created.

16. Select the Service Group Definition aspect in the Aspect List Area.

TC05890A

Figure 56. Node Settings for the Event Collector Service Provider

Section 6 AC 800M Configure OPC Server for Alarm and Event Collection

3BUA000156R4101 107

17. Select the Special Configuration tab in the Preview Area as shown in Figure 57.

18. Select OPC AE Server for AC 800M in the Alarm Server drop-down list box.

19. Click Apply.

20. Verify that OPC AE Server for AC 800M is set in the Collection Definition drop-down list box.

TC07436A

Figure 57. Service Group Settings for the Event Collector

Additional settings can be made from the Alarm Manager object in the Service Structure.

Verify OPC Server Configuration Section 6 AC 800M

108 3BUA000156R4101

21. Verify the connection by checking the status: Click on the Status tab on the Event Collector object and verify that the state is Service. Refer to Figure 58.

Verify OPC Server Configuration

Refer to Figure 48 and verify that the OPC Server is running, and its connection status for the controllers can be viewed in the OPC Server panel.

If the connection to controllers has been done in the OPC Server, and there is a valid control application downloaded to one or more of the controllers, the OPC Server will start transferring values and events from the controllers to any OPC client requesting such values. OPC clients are e.g. the Operator Workplace displays and event lists. The statistics of the current OPC Server traffic can be viewed as follows:

1. Open the configuration dialog (normally on the Connectivity Servers). Select:


2. Select:

Tools > Display OPC statistics > Data Access

TC05896A

Figure 58. Verify the Connection

Section 6 AC 800M System Alarms From AC 800M

3BUA000156R4101 109

3. To open the OPC Statistics - Data Access dialog shown in Figure 59. .

System Alarms From AC 800M

To get System alarms from AC 800M in the Common System Alarm List, change the configuration in the following way:


2. Use the Structure Selector to select the Library Structure.

3. Use the Object Browser to expand Alarm & Event Configurations.

4. Use the Object Browser to expand Default Configurations.

5. Select Common System Alarm List.

6. Select Alarm and Event List Configuration in the Aspect List Area.

7. Select the Filter tab.

8. In the Categories list, select System Condition Event.

9. Click Apply.

Figure 59. View OPC Server Statistics

System Alarms From AC 800M Section 6 AC 800M

110 3BUA000156R4101

To get System alarms from AC 800M in the Common System Event List, you have to change the configuration in the following way:


2. Use the Structure Selector to select the Library Structure.

3. Use the Object Browser to expand Alarm & Event Configurations.

4. Use the Object Browser to expand Default Configurations.

5. Select Common System Event List.

6. Select Alarm and Event List Configuration in the Aspect List Area.

7. Select the Filter tab.

8. In the Categories list, select System Condition Event and System Simple Event.

9. Click Apply.

3BUA000156R4101 111

Section 7 800xA for TRIO

IntroductionThis section describes the following:

• Install TRIO Software on page 111.• Load TRIO System Extensions on page 111.• Load Hardware Definition Files on page 112.• Load Firmware on page 112.

Install TRIO SoftwareRun the InstallShield Wizard for TRIO on all 800xA System nodes as follows:

1. Insert 800xA System Installation DVD 1 into the DVD drive.

2. Use Windows Explorer to locate setup.exe in the following directory:

Connects2\Trio Connect

3. Double-click Setup.exe to begin the installation.

4. Follow the Installation Wizard to complete the installation. Perform the following when the indicated dialogs appear:

Load TRIO System Extensions1. Refer to Adding System Extensions on page 31 and follow the procedure for

using the Configuration Wizard to load the TRIO system extension.

The AC 800M software must be installed and the AC800M Connect system extension must be loaded prior to installing 800xA for TRIO software and loading its system extension.

Load Hardware Definition Files Section 7 800xA for TRIO

112 3BUA000156R4101

2. Use the Plant Explorer Workplace to verify the TRIO system extensions as follows:

a. Open the Plant Explorer Workplace.

b. Select the information icon to open the About Industrial IT window.

c. Verify the TRIO Version 4.1-0 is present.

Load Hardware Definition FilesHardware definition files for TRIO must be manually loaded onto each and every Control Builder project that uses TRIO. If this is not done, the CI862 TRIO Interface will not be present as a new unit.

Use the Control Builder to install the TRIO Hardware Definition Files as follows:


2. Open or create a Control Builder project.

3. Select:

File > Insert Hardware Definition

4. From the Open dialog, go to the location of the TRIO .hdw files:

...\Program Files\ABB Industrial IT\Control IT\TRIO

5. Select all TRIO .hdw files and then select Open.

6. Click OK to insert the hardware definition files. Control Builder will read the files and then restart automatically.

Control Builder can now be used to configure TRIO I/O.

Load FirmwareBefore beginning any configuration activities, be sure that the latest firmware is installed on the controller and the CI862.

1. Download the firmware by selecting Remote System ... from the controller context menu

Section 7 800xA for TRIO Load Firmware

3BUA000156R4101 113

2. Select the Show Firmware Information button on the Remote System dialog. The Firmware Information dialog will show the current version and what is available on disk.

3. Select the Browse button.

4. Select the firmware_citrio.txt file in the default bin directory and then select Open.

5. Select the check box for Load New in the row containing the CI862.

6. Select the Download Firmware button and Continue when prompted.

Load Firmware Section 7 800xA for TRIO

114 3BUA000156R4101

3BUA000156R4101 115

Section 8 HART Device Integration

IntroductionThe user must have a basic knowledge of Windows user rights making the DCOM settings described in this section.

Adaptation of the DCOM SettingsBefore working with HART Device Integration, certain software components must be adapted for various Windows user groups. These adaptations must be performed on every 800xA System node to ensure communications between the Device Type Manager (DTM) (system) and the device.

The user account is configured using the Windows system tool DCOMcnfg.

1. Select:

Start > Run

2. The Run dialog appears. Enter dcomcnfg and click OK.

Windows XP and Windows Server 2003

In Windows XP and Windows Server 2003, a dialog opens in which the DCOM settings are stored in the following folder structure:

Component Services > Computers > My Computer > DCOM config

Plant Explorer, Control Builder M, and open DTMs must be closed before adaptation of DCOM settings.

Windows 2000 Section 8 HART Device Integration

116 3BUA000156R4101


Windows 2000

In Windows 2000, a dialog opens in which you can select the Applications tab (Figure 61).

Figure 60. Windows XP DCOM Settings

Calling DCOMcnfg the first time, a windows message box may appear offering to record changes in the DCOM settings. Click Yes and continue with the procedure.

Figure 61. Windows 2000 DCOM Settings

Section 8 HART Device Integration Server Path Settings

3BUA000156R4101 117

3. Select the relevant program and click Properties, and adapt them to the DCOM settings as listed in Table 9.

Server Path SettingsSet the 800xA System Server Path settings according to the Getting Started section in Industrial IT, 800xA - Device Management, HART, Configuration.

Table 9. DCOM Settings

Installed Components Settings

DeviceManagementServer Identity: This User (800xA Service Account)

HartServer Identity: This User (800xA Service Account)

Only on Server node of the HART Server

ABB Fieldbus OPC Server DA Identity: This User (800xA Service Account)

Server Path Settings Section 8 HART Device Integration

118 3BUA000156R4101

3BUA000156R4101 119

Section 9 PROFIBUS Device Integration

IntroductionThe user must have a basic knowledge of Windows user rights making the DCOM settings described in this section.

Adaptation of the DCOM SettingsBefore working with PROFIBUS Device Integration, certain software components must be adapted for various Windows user groups. These adaptations must be performed on every 800xA System node to ensure communications between the Device Type Manager (DTM) (system) and the device.

The user account is configured using the Windows system tool DCOMcnfg.

1. Select:

Start > Run

2. The Run dialog appears. Enter dcomcnfg and click OK.

Windows XP and Windows Server 2003

In Windows XP and Windows Server 2003, a window opens in which the DCOM settings are stored in the following folder structure:

Component Services > Computers > My Computer > DCOM config

Plant Explorer, Control Builder M, and open DTMs must be closed before adaptation of DCOM settings.

Windows 2000 Section 9 PROFIBUS Device Integration

120 3BUA000156R4101


Windows 2000

In Windows 2000, a window opens in which you can select the Applications tab (Figure 63).

Figure 62. Windows XP DCOM Settings

Calling DCOMcnfg the first time, a windows message box may appear offering to record changes in the DCOM settings. Click Yes and continue with the procedure.

Figure 63. Windows 2000 DCOM Settings

Section 9 PROFIBUS Device Integration Windows 2000

3BUA000156R4101 121

1. Select the relevant program and click Properties, and adapt them to the DCOM settings as listed in Table 10.

Table 10. DCOM Settings


DeviceManagementServer Identity: This User (800xA Service Account)

ABB Fieldbus OPC Server DA Identity: This User (800xA Service Account)

Windows 2000 Section 9 PROFIBUS Device Integration

122 3BUA000156R4101

3BUA000156R4101 123

Section 10 800xA for Advant Master

IntroductionIf using 800xA for Advant Master connectivity to access data from controller stations, the appropriate Network, RTA Board, and controller objects must be created in the Control Structure of the Aspect System.

Connectivity Server Configuration

Connect Several MB 300 Networks to an 800xA System

Multiple Connectivity Servers allow you to connect several MB 300 control networks from a common 800xA System.

To add multiple Connectivity Servers to your Aspect System, follow the steps in Adding Connectivity and Application Servers on page 39.

Add Multiple Connectivity Servers to the Same MB 300 Network

One Connectivity Server (single or redundant pair) can be connected to up to 20 controllers on a MB 300 network. If the number of controllers on the MB 300 network exceeds this number, a second Connectivity Server (single or redundant pair), can be connected to handle an additional 20 controllers, provided that the maximum number of tags supported are not exceeded. A Secondary Connectivity Server can also be added to the same MB 300 network to reduce the data and history subscription load on each Connectivity Server.

The Application Engineer or System Engineer has to be a member of the Microsoft Windows Power Users group or the Administrators group to be able to perform the configurations.

Add the RTA Board Section 10 800xA for Advant Master

124 3BUA000156R4101

To connect a second Connectivity Server:

1. Follow the description in Add the RTA Board on page 124, with the following exception:

The logical net address entered in Step 5 under Add the RTA Board on page 124 should have the same decade as in the actual network address but 3, 5, or 7 shall be used as the last digit; that is, 13 when the primary network address is 11. The real network address shall, however, be entered as the RTA Board address.

2. Event Filtering has to be configured to avoid duplicated alarms. Refer to the Alarm and Event section in Industrial IT, System - 800xA for Advant Master, Configuration.

3. Add the additional controllers you want to subscribe for data on, via the Secondary Connectivity Server, by adding these to the secondary MB 300 network object in the Control Structure.

Add the RTA Board

1. Start the Configuration Wizard on the Aspect Server. Select:




4. The Select Type of Configuration for System dialog appears. Select Add RTA and click Next.

Section 10 800xA for Advant Master RTA Board Network Settings

3BUA000156R4101 125

5. The Add RTA dialog shown in Figure 64 appears. Select the primary network number from the Network drop-down list box, or enter it yourself.

6. Select the server node from the Server node drop-down list box and click Next.

7. When the Apply Settings dialog appears, click Apply.

8. Repeat the procedure for all your 800xA for Advant Master Connectivity Servers (i.e. the redundant servers).

RTA Board Network Settings1. Start the Configuration Wizard on the Aspect Server. Select:




Figure 64. Add RTA Dialog Box

Clock Synchronization Section 10 800xA for Advant Master

126 3BUA000156R4101

4. The Select Type of Configuration for System dialog appears. Select MB 300 RTA Settings and click Next.

5. The MB 300 RTA Network Settings dialog shown in Figure 65 appears. Select the name of the 800xA for Advant Master Connectivity Server in the AC 400 Server drop-down list box and click Next.

6. When the Apply Settings dialog appears, click Apply.

7. Repeat the procedure for all 800xA for Advant Master Connectivity Servers.

Clock Synchronization

The default clock synchronization settings in 800xA for Advant Master is defined for a system where an AC 400 Series controller is set as Clock Master. Refer to Industrial IT, 800xA - System, Automation System Network - Design and Configuration for a thorough description of synchronization strategies and overall configuration, and to Industrial IT, 800xA-System, 800xA for Advant Master - Configuration for 800xA for Advant Master configuration details.

Figure 65. MB300 RTA Network Settings Dialog

Section 10 800xA for Advant Master Verify the RTA Board Network Settings

3BUA000156R4101 127

Verify the RTA Board Network Settings

Verify that the RTA boards are running by inspecting the RTA Board Control aspect on the RTA Board objects in the Control Structure as shown in Figure 66.

Figure 66. Inspect the RTA Board Status

Verify the RTA Board Network Settings Section 10 800xA for Advant Master

128 3BUA000156R4101

3BUA000156R4101 129

Section 11 800xA for DCI

IntroductionPost installation for 800xA for DCI consists of creating a Symphony DCI OPC Server object.

Creating a Symphony DCI OPC Server ObjectCreate a Symphony DCI OPC Server object by performing the following steps:

1. In the Plant Explorer Workplace, select the Control Structure.

2. Use the Object Browser to right-click Root Domain and select New Object from the context menu that appears.

3. The New Object dialog appears. Select the Common tab.

4. Expand the

Object Types > Control System > Symphony DCI

tree.

5. Select Symphony DCI OPC Server Network from the Symphony DCI tree as shown in Figure 67.

6. Enter a name for the Symphony DCI OPC Server Network.

7. Select the Next button.

8. Select Add from the Additional Arguments dialog as shown in Figure 68.

a. Select a Connectivity Server from the list.

b. Click OK.

Creating a Symphony DCI OPC Server Object Section 11 800xA for DCI

130 3BUA000156R4101

9. Select ABB.Dci800xADAServer.1 from the Selected OPC Server, ProgID drop-down list box.

a. Click Create.

b. Verify that the following Aspects appear in the Aspect list:

– Alarm Review.– Control Connection.

TC05676A


TC05677A

Figure 68. Additional Arguments Dialog

Section 11 800xA for DCI Creating a Symphony DCI OPC Server Object

3BUA000156R4101 131

– Control Structure.– DCI System Status.– DCI Tag Import File Name.– DCI Tag Import Properties.– DCI Tag Importer.– Event Review.– Symphony DCI OPC Server Network Type Reference.– Message Review.– Name.– Object Icon.– OPC Data Source Definition.

10. In Plant Explorer Workplace, select the Service Structure.


Services > Event Collector, Service

12. If they do not already exist, create the Service Group and Service Provider Objects by right-clicking on EventCollector, Service and select New Object from the context menu that appears.

13. The New Object dialog appears. Select Service Group and enter a name, such as DCI_AE_SGx (where x is a running number) and click Create.


15. The New Object dialog appears. Select Service Provider and enter a name, such as DCI_AE_SP_nodename (where nodename is a Connectivity Server name) and click Create.

16. Select the Service Provider Definition aspect for the DCI_AE_SP_nodename Service Provider Object in the Aspect List Area.

17. Select the Configuration tab in the Preview area.

18. Select the name of the DCI Connectivity Server in the Node drop-down list box.

19. Click Apply.

20. Repeat Step 14 through Step 19 for a redundant Connectivity Server.

Creating a Symphony DCI OPC Server Object Section 11 800xA for DCI

132 3BUA000156R4101


22. Select the Service Group Definition aspect in the Aspect list.

23. Select the Special Configuration tab in the Preview Area.

24. Select ABB DCI 800xA OPC Alarm & Event Server in the Alarm Server drop-down list box.

25. Click New and verify that ABB DCI 800xA OPC Alarm & Event Server appears in the Collection Definition drop-down list box.

26. Click on Edit.

27. The Alarm Collection Definition dialog appears. Select the Supports Refresh check box.

28. Click Apply.

29. Verify the connection by clicking on the Status tab on the Event Collector object and verify that the state is Service.

30. Close the dialog.

31. Click Apply.

3BUA000156R4101 133

Section 12 800xA for Harmony

IntroductionPost installation for 800xA for Harmony consists of:

• Initial Harmony Network Setup.• Harmony Alarm and Event OPC Provider Setup.• Import the Harmony Configuration.• Synchronize the Aspect Directory.• Configure Internet Explorer Options.• SemAPI Information.

Initial Harmony Network SetupCreate the Harmony Network by performing the following:



3. Create a new Harmony OPC Network on the Configuration Server with Connectivity Server node or Connectivity Server node following the procedures outlined in Industrial IT, 800xA - System, 800xA for Harmony, Configuration.

4. Create a new NetConfig aspect on the Configuration Server with Connectivity Server node or Connectivity Server node following the procedures outlined in Industrial IT, 800xA - System, 800xA for Harmony, Configuration.

For a redundant setup, only one Connectivity Server node must be selected when creating a new network.

For a redundant setup, only one Connectivity Server node must be selected when creating a new NetConfig aspect.

Harmony Alarm and Event OPC Provider Setup Section 12 800xA for Harmony

134 3BUA000156R4101

Harmony Alarm and Event OPC Provider SetupThis requires the user to add the Harmony OPC alarm server program ID to a Service Group under the Event Collector category in the Service structure:

1. In Plant Explorer Workplace, select the Service Structure.



3. If they do not already exist, create the Service Group and Service Provider Objects by right-clicking on EventCollector, Service and select New Object from the context menu that appears.

4. The New Object dialog appears. Select Service Group and enter a name, such as Harmony_AE_SGx (where x is a running number) and click Create.


6. The New Object dialog appears. Select Service Provider and enter a name, such as Harmony_AE_SP_nodename (where nodename is a Connectivity Server name) and click Create.

7. Select the Service Provider Definition aspect for the Harmony_AE_SP_nodename Service Provider Object in the Aspect List Area.


9. Select the name of the Harmony Connectivity Server in the Node drop-down list box.

10. Click Apply.

11. Repeat Step 5 through Step 10 for a backup Connectivity Server.




15. Select ABB Maestro/OPC Event Server (InProc) in the Alarm Server drop-down list box.

Section 12 800xA for Harmony Import the Harmony Configuration

3BUA000156R4101 135

16. Select Harmony Alarms in the Collection Definition drop-down list box.

17. Verify the connection by clicking on the Status tab on the Event Collector object and verify that the state is Service for the Primary Connectivity Server and Standby for the Redundant Connectivity Server.

18. Use the Object Browser to navigate to AlarmManager, Service and expand it.

19. Select Basic, Service Group


21. Deselect the Make new alarm entry each time a condition gets active check box.

22. Click Apply.

Import the Harmony ConfigurationThe following scenarios cover importing the Harmony Configuration. Perform the one that applies to your system.

• New Installations.• Reloading when a Backup Exists.• Reloading when a Backup does not Exist.

New Installations

Use the Tag Importer utility in the 800xA for Harmony program group to import the Harmony Configuration.

1. On the Configuration Server node or Configuration Server with Connectivity Server node select:

Start > All Programs > ABB Industrial IT 800xA >800xA for OCS Systems > Harmony > Configuration >Tag Importer Exporter

2. Select Import Existing Configuration Data.

Deselecting Make new alarm entry each time a condition gets active is a system wide setting. This is only a recommendation for 800xA for Harmony. It may conflict with other applications.

Reloading when a Backup Exists Section 12 800xA for Harmony

136 3BUA000156R4101

3. Select the appropriate import options and click Next to continue.

4. Select the file that is to be imported and click Next to continue.

Reloading when a Backup Exists

If the Harmony Connect tag objects already exist in the Aspect Directory (due to a reload of the Harmony Configuration Server node), and a backup exists, perform the following steps:

1. Log onto the local service account.

2. On the Configuration Server node or Configuration Server with Connectivity Server node select:

Start > All Programs > ABB Industrial IT 800xA >800xA for OCS Systems > Harmony > Configuration >Restore Configuration

3. Click Connect.

4. Choose the backup file name to restore.

5. Click Restore.

Reloading when a Backup does not Exist

If the Harmony Connect tag objects already exist in the Aspect Directory (due to a reload of the Harmony Configuration Server node), and a backup does not exist, perform the following steps.


2. Use the Structure Selector to select the Control Structure.

3. Use the Object Browser to select the OPC Server Network object.

4. Select the Harmony Synchronizer aspect in the Aspect List Area.

5. In the Preview Area:

a. Deselect all Import from Configuration Server options.

b. Select all Export to Configuration Server options.

Refer to Industrial IT, 800xA - System, 800xA for Harmony, Configuration for detailed information.

Section 12 800xA for Harmony Synchronize the Aspect Directory

3BUA000156R4101 137

c. Select the Advanced tab.

d. Select the Export option under Disconnected Tag Options.

e. Select the General tab.

f. Select Synchronize.

6. Perform the steps under New Installations on page 135.

Synchronize the Aspect DirectorySynchronize the Aspect Directory with the Harmony Configuration Server using the Harmony Synchronizer aspect, which is part of the Harmony OPC Network. Refer to Industrial IT, 800xA - System, 800xA for Harmony, Configuration for more detailed information.

Configure Internet Explorer Options1. Launch Internet Explorer.

2. Select:

Tools > Internet Options > Connections > Setup.

3. From the Internet Connections Wizard, select the desired method of connecting the node to the Internet.

4. Click Next.

5. Enter the desired method of getting an Internet protocol address when a local area network is being used.

6. Click Next.

7. Specify that the Internet mail account should be set up later.

8. Click Next.

9. Click Finish.

10. Select:

Tools > Internet Options

SemAPI Information Section 12 800xA for Harmony

138 3BUA000156R4101

11. Select the Security tab.

12. Set the Zone to Local Intranet.

13. Select Custom Level.

14. Enable the Initialize And Script ActiveX Controls Not Marked As Safe check box.

15. Click OK.

16. Click Yes when prompted if the security settings for this zone are to be changed.

17. Click OK.

SemAPI InformationThere are some common SemAPI setup issues that may be encountered.

Setting Up the SCSI Device After Installation

Windows Server 2003

On an 800xA for Harmony Connectivity Server node using a SCSI interface with Windows Server 2003 installed as the Operating System, a message box can pop up indicating a new device has been found. It is reported as a Bailey IIMCP02 device. The Hardware Wizard is launched prompting the operator to add the device to the Operating System. The procedure to do this is as follows:

1. Select Install from a list or specific location (advanced) and click Next.

2. Select Don't search, I will choose the driver to install and click Next.

3. Select Show All Drivers in the list and click Next.

4. Scroll down until Unknown is displayed in the Manufacturer list.

5. Select Unknown.

6. In the Model list, select Unsupported device and click Next.

The Internet Explorer security configuration change to enable the Initialize and Script Active X Controls Not Marked as Safe check box needs to be performed from each user account.

Section 12 800xA for Harmony ICI Device Configuration Changed After Installation

3BUA000156R4101 139

7. Click Yes when the Update Driver Warning dialog appears.

8. Click Finish.


Windows 2000 Server

On an 800xA for Harmony Connectivity Server node using a SCSI interface with Windows 2000 Server installed as the Operating System, a message box can pop up indicating a new device has been found. It is reported as a Bailey IIMCP02 device. The Hardware Wizard is launched prompting the user to add the device to the Operating System. The procedure to do this is as follows:

1. Click Next.

2. Select Display a list of the known drivers so that I can choose a specific driver and click Next.

3. Scroll down until Other devices is displayed in the Hardware Type box.

4. Select Other devices and click Next.

5. In the Select a Device Driver box, on the left side, under Manufacturers, scroll down and highlight Unknown. On the right side under Models, select Unsupported device.

6. Click Yes at the Update Driver Warning dialog.

7. Click Next at the Start Driver Installation dialog.

8. Click Finish.


ICI Device Configuration Changed After InstallationThe following example contains the instructions necessary when modifying the ICI Device Configuration from a serial device to a SCSI device. It is an example only and may differ from other specific applications.

ICI Device Configuration Changed After Installation Section 12 800xA for Harmony

140 3BUA000156R4101

Manually enter the following commands if the ICI Device Configuration is modified after installation:

1. Select:

Start > Run

and enter:

...\Program Files\ABB Industrial IT\SemAPI\EXE\WINNT\DeviceAsServiceU.exe' -u dd_com2

where, _com2 is the port used during installation.

2. Click OK.

3. Select:

Start > Run

and enter:

...\Program Files\ABB Industrial IT\SemAPI\EXE\WINNT\DeviceAsServiceU.exe' -i dd_s003

where, _s003 is the SCSI port number in semAPI.

4. Click OK.

3BUA000156R4101 141

Section 13 800xA for Melody

IntroductionPost installation for 800xA for Melody consists of:

• Melody Alarm and Event OPC Provider Setup.• Configure Internet Explorer Options.

For further post installation issues refer to Appendix C, Base Configuration Overview in Industrial IT, 800xA - System, 800xA for Melody, Configuration.

Melody Alarm and Event OPC Provider SetupThis requires the user to add the Melody OPC alarm server program ID to a Service Group under the Event Collector category in the Service structure.





4. Right-click on EventCollector Service and select New Object from the context menu that appears.

5. Select Service Group.

6. Enter a descriptive name such as Melody EventCollector in the Name field and select Create.


Melody Alarm and Event OPC Provider Setup Section 13 800xA for Melody

142 3BUA000156R4101

8. Select Add in the Preview Area to add a Service Provider for the Connectivity Server and enter a descriptive name such as:

Melody_EventCollector_Provider_node

where node is the name of the Connectivity Server node.

9. Select OK.

10. Select Apply in the Service Group Definition aspect.

11. In the Providers list box, double-click the newly created EventCollector Service Provider.

12. The Service Provider Definition aspect should be displayed in the Preview Area. Select the name of the appropriate Connectivity Server from the Node drop-down list box and click Apply.

13. Close the Service Provider Definition dialog.

14. Repeat Step 7 through Step 13 to add and configure an Event Collector Service Provider for the redundant Connectivity Server if one exists.

15. Select the Special Configuration tab in the Service Group Definition aspect.

16. Select Maestro/OPC EventServer (InProc) option in the Alarm Server configuration field.

17. Select the Melody Alarm option in the Collection Definition configuration field if it is not already selected.

18. Click Apply.



Services > Alarm Manager, Basic, Service Group


22. Deselect the Make new alarm entry each time a condition gets active check box.

23. Click Apply.

Deselecting Make new alarm entry each time a condition gets active is a system wide setting. This is only a recommendation for 800xA for Melody. It may conflict with other applications.

Section 13 800xA for Melody Configure Internet Explorer Options

3BUA000156R4101 143

Configure Internet Explorer OptionsThe Internet Explorer application must be configured for all 800xA for Melody users on all workplaces.

1. Launch Internet Explorer.

2. Select Setup in the Connections tab from Internet Options (Tools > Internet Options > Connections > Setup...) as shown in Figure 69.

3. Click Next.

4. From the (Internet) New Connections Wizard, select the desired method of connecting the node to the Internet and click Next.

5. Enter the desired method of getting an Internet protocol address when a local area network is being used and click Next.

6. For Windows 2000 Server: Specify that the Internet mail account should be set up later and click Next.

TC03684B

Figure 69. Connections Tab

Configure Internet Explorer Options Section 13 800xA for Melody

144 3BUA000156R4101

7. Click Finish.

8. Select the Security tab from Internet Options (Tools > Internet Options > Security).

9. For Windows 2000 Server set the Zone to Local Intranet.

For Windows Server 2003/Windows XP Professional, it is possible to add the Local Intranet to Trusted Sites (optional).

10. Select Custom Level... (Figure 70).

11. Enable the Initialize And script ActiveX® Controls Not Marked As Safe check box.

12. Click OK.

13. Click Yes when prompted if the security settings for this zone are to be changed.

14. Click OK.

MC070A

Figure 70. Customize Level Settings

3BUA000156R4101 145

Section 14 800xA for MOD 300

Introduction1. Set up time synchronization as described in Setting Up Time Synchronization

on page 145.

2. Verify redundancy setting as described in Redundancy on page 150.

3. Complete the system services communications settings described in Communication Settings on page 148.

4. Add Hyper Terminal Windows component on a Windows Server 2003 as described in Add Hyper Terminal on page 151.

Setting Up Time Synchronization

800xA System is Master Timekeeper

When the 800xA System is the master timekeeper, follow the instructions for setting up time on the 800xA System and then set the 800xA for MOD 300 Connectivity Server so reverse time synchronization is enabled. This will allow the RTAB clock the ability to update the MOD 300 system if it is made the master timekeeper (refer to the Advant Station 500 Series with AdvaCommand / AdvaBuild User Guide for additional information). Specifically, set the following:

• Enable Reverse Time Synchronization: REVERSED_SYNC_MODE = 1

Registry Location: HKEY_LOCAL_MACHINE\Software\ABB\SystemServices\DxBase\dxTimeSync

MOD 300 System is Master Timekeeper Section 14 800xA for MOD 300

146 3BUA000156R4101

MOD 300 System is Master Timekeeper

Time Synchronization on the Windows side of a Connectivity Server node can be set so Reverse Time Synchronization (RTS) is disabled. This allows the host Connectivity Server to constantly be updated by the Real-time Accelerator Board (RTAB) clock which gets its time from the MOD 300 System Master Timekeeper over the DCN. The host node then broadcasts this time to the other MOD 300 nodes on the 800xA system as well as the domain controller.

MOD 300 Connectivity Servers, Clients and the associated Domain Controller all need to be set up to handle getting time from the MOD 300 system through the RTAB on the Connectivity Servers.

Time Synchronization on the MOD 300 Connectivity Server

Reverse time synchronization is disabled on these nodes to allow the MOD 300 system to update the RTAB clock on the Connectivity Server. In addition, these servers act as an SNTP server for the Domain Controller. Specifically, set the following:

• Disable Reverse Time Synchronization: REVERSED_SYNC_MODE = 0

Registry Location: HKEY_LOCAL_MACHINE\Software\ABB\SystemServices\DxBase\dxTimeSync

• SNTP Registry parameter NtpServer = time.windows.com,0x1

Registry Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

• Set the Windows Time (W32Time) in the Services window via:

Start > Control Panel > Administrative Tools > Services

as follows:

– Startup Type is Automatic

– Status is Started

• Set the SNTP to fetch the time from itself. From the command prompt enter:

net time /setsntp:a.b.c.d

where a.b.c.d is the IP address of the Connectivity Server (itself).

Section 14 800xA for MOD 300 Time Synchronization on the Domain Controller

3BUA000156R4101 147

Time Synchronization on the Domain Controller

The Connectivity Servers act as an SNTP server for the Domain Controller which then distributes time to all nodes in the domain. This is handled with the default settings for W32Time. Specifically, set the following:

• Set the Windows Time (W32Time) in the Services window as follows:

– Startup Type is Automatic

– Status is Started

• SNTP Registry parameter:

– Windows 2000 Domain Controller: LocalNTP = 0

– Windows 2003 Domain Controller: NtpServer = time.windows.com,0x1


• SNTP Configuration, from the command prompt enter:

net time /setsntp:a1.b1.c1.d1:a2.b2.c2.d2

where a1.b1.c1.d1 and a2.b2.c2.d2 are the IP addresses of the Connectivity Servers

Time Synchronization on the MOD 300 Client

Client nodes get their time from the Domain Controller and are set up as SNTP clients. Specifically, set the following:

• Set the Windows Time (W32Time) in the Services window as follows:

– Startup Type is Disabled

– Status is Stopped

• SNTP Registry parameter default:

– Windows XP or 2003: NtpServer = time.windows.com,0x1


Time Synchronization on the Service Provider Definition Aspect Section 14 800xA for MOD 300

148 3BUA000156R4101

Time Synchronization on the Service Provider Definition Aspect

To complete time synchronization setup, the Service Provider Definition aspect must be set up as described in Industrial IT, 800xA - System, 800xA for MOD 300, Configuration the Set Up System Structure section. At that time, set up the Service Provider Definition aspect (located in the Service Structure as part of the Time Service object) for client nodes by unchecking the Enabled box in the Configuration tab and applying. This function is enabled by default and must be left enabled on the Connectivity Servers.

Communication Settings

1. After the node is restarted, initialize the OMF settings to start system services. Use the Administrative Tools in the Window Control Panel to select:

PAS > Settings.

This displays the Communications Configuration Tool shown in Figure 71.

a. Select Yes at the message

Would you like to revert back to saved settings?

This opens the Communication Settings display.

b. Select OK on the Communication Settings display to save the settings and close the window.

c. Select OK to the message:

Settings have been saved . ...

d. Restart Windows (step 6).

2. Configure the Control Network section. Select MOD300 to connect this node to a MOD 300 Distributed Communications Network (DCN). The network address parameters are displayed in the Network Address section.

The PAS System Services will not start until you initialize the communications settings as described in the next steps.

The message: Would you like to revert back to saved settings?

is displayed if settings were previously saved. To restore the previous settings, do steps a through d as follows.

Section 14 800xA for MOD 300 Communication Settings

3BUA000156R4101 149

3. Configure the Network Address section.

Both the DCN Address and the E-DCN Network Addresses (1 and 2) must be set to valid values whether you are connecting to the DCN or E-DCN.

The DCN Address is required for both DCN and E-DCN connections. This is the device number on the DCN. Set the DCN address to the same decimal value as the Physical Device number specified on the node’s GENERICD object in the ABB OCS database (refer to Industrial IT, 800xA - System, 800xA for MOD 300, Configuration for guidelines). Valid entries are 2 - 255 decimal that represent the hexadecimal address (1 is reserved for the MOD engineering station).

TC05929A

Figure 71. Communications Configuration Tool

When you connect to the standard DCN, you can leave the E-DCN addresses at their default values.

Redundancy Section 14 800xA for MOD 300

150 3BUA000156R4101

For E-DCN connection, follow these guidelines to configure the E-DCN addresses:

E-DCN Network Address 1 must be set to match the E-DCN Network Address 1 value for all other nodes connecting to that media. E-DCN Network Address 1 must be an even number, for example 6.

E-DCN Network Address 2 must be set to match the E-DCN Network Address 2 value for all other nodes connecting to that media. E-DCN Network Address 2 must be an odd number, for example 7.

4. Set OMF Shared Memory Size to 32 MByte if not already set.

5. Select OK to apply the changes. There is no need to change the other settings (your displayed settings may be different and may show TCP/IP not checked for example).

6. Select OK at the informational message that the settings have been changed. You must always restart if you change the Control Network Setting, OMF Memory, or TCP/IP enabled setting.

7. Re-start Windows. Re-start Windows at this time.

RedundancySet redundancy in the registry as follows.

Redundant Partner = computer name of other connectivity serverwhere the redundancy registry location is:

HKEY_LOCAL_MACHINE\Software\ABB\AdvOPCAEServer\config

Enter the name of the redundant partner Connectivity Server if the two servers are redundant. Do this for both servers. Leave the setting blank if no redundancy is required.

Section 14 800xA for MOD 300 Add Hyper Terminal

3BUA000156R4101 151

Add Hyper TerminalHyperTerminal is not installed when loading Windows Server 2003 and is a required component for MOD 300 software. To add the HyperTerminal component:

1. Select:

Start > Control Panel > Add/Remove Programs

2. Select Add/Remove Windows Components.

3. Check Accessories and Utilities and then select the Details button.

4. Check Communications and then select the Details button.

5. Check the HyperTerminal component and then select OK and Apply as required to install the component.

Add Hyper Terminal Section 14 800xA for MOD 300

152 3BUA000156R4101

3BUA000156R4101 153

Section 15 PLC Connect

IntroductionThe section describes how to configure the installed PLC Connect software. It contains procedures for doing the following:

• Basic Setup.• IEC 60870 Licensing.• PLC Server.

Basic SetupBefore starting to engineer the system, by creating process objects and signals, etc., a basic setup must be performed.

Refer to PLC Server on page 175 only if needed for information on how to configure PLC Connect specific server processes. For example, to use a program of your own together with the system.

Control Network Setup Section 15 PLC Connect

154 3BUA000156R4101

Control Network Setup

Establish Control Network Connections

For each Control Network, you have to establish a connection between the Control Network and its PLC Connect Connectivity Server; that is, a Connectivity Server node with the PLC Connect system extension. This is necessary in order to gain access to the dynamic process data that the Connectivity Servers provide.

Create a New Control Network Object



The SoftPoint Server is a subset of PLC Connect. Both use the same server processes and share a common RTDB. PLC Connect and the SoftPoint Server can coexist in the same system, but the setup differs somewhat depending on whether PLC Connect and the SoftPoint Server are installed in the same node, or on separate nodes. Refer to Figure 72 for an example.

Figure 72. PLC Connect and SoftPoint Server Coexistence

ASPECTSERVER B

T05246A

CONNECTIVITYSERVER C

(PLC CONNECT ANDSOFTPOINT SERVER

INSTALLED)

CONNECTIVITYSERVER A

(ONLY PLC CONNECTINSTALLED)

ASPECTSERVER A

CONNECTIVITYSERVER B

(ONLY SOFTPOINTSERVER INSTALLED)

Section 15 PLC Connect Control Network Setup

3BUA000156R4101 155

3. Use the Object Browser to select the Root, Domain object.

4. Right-click the Root, Domain object, and select New Object from the context menu that appears.

5. The New Object dialog appears. Select the List Presentation check box.

6. From the left-hand list, select PLC Generic Control Network.

7. In the Name box, enter the name of the Control Network the object will represent.

8. Click Create.

Create an Adapter Data Source Definition Aspect

1. Use the Object Browser to right-click the Control Network object created under Create a New Control Network Object on page 154.

2. Select New Aspect from the context menu that appears.

3. The New Aspect dialog appears. Select the List Presentation check box.

4. From the left-hand list, select Adapter Data Source Definition.

5. Click Create.

For example, include the node name as part of the Control Network name.

Accept the default name. Do not change it.


156 3BUA000156R4101

Configure the Adapter Data Source Definition Aspect

1. Select the created Adapter Data Source Definition aspect in the Aspect List Area. Figure 73 shows the aspect in the Preview Area.

Figure 73. Adapter Data Source Definition Aspect


3BUA000156R4101 157

2. The Data Key box contains a Data Key GUID. Change it to something that is not equal to null. For example, change it from its default value:

{00000000-0000-0000-0000-000000000000}

to:

{00000000-0000-0000-0000-000000000001}

3. Click Apply.

Add Service Provider

1. Click New in the Adapter Data Source Definition aspect in the Preview Area. The New Service Group dialog box appears as shown in Figure 74.

No two Control Networks in a system can have the same Data Key GUID. If there are several Control Networks; that is, several Connectivity Servers, in the system, make sure the value of the different Data Key GUIDs are not the same.

For example, when adding a second Control Network, change its Data Key GUID to: {00000000-0000-0000-0000-000000000002}.



158 3BUA000156R4101

2. Click Add. The Add Service Provider dialog appears as shown in Figure 75.

3. Select the PLC Connect Connectivity Server.

4. Click OK in the Add Service Provider dialog.

5. Click OK in the New Service Group dialog.

6. Click Apply in the Adapter Data Source Definition aspect in the Preview Area.

Change Adapter Identity

1. Click View in the Adapter Data Source Definition aspect in the Preview Area. The Service Group Definition aspect appears.

2. Select the Special Configuration tab.

3. Change the Adapter Identity from:

{00000000-0000-0000-0000-000000000000}

to:

ABB.AdsOPCAdapter.1


4. If running nonredundant Connectivity Servers, deselect the Allow parallel redundancy check box. This check box is enabled by default.

5. Click Apply.

6. Close the window.

Figure 75. Add Service Provider Dialog


3BUA000156R4101 159

Create Control Network Objects for Other Control Networks

1. Repeat the procedures performed thus far in this section for each Control Network in the system. When finished, there should be one configured Control Network object for each Control Network in the system.

Figure 76. Service Group Definition Aspect with Change Adapter Identity


160 3BUA000156R4101

Configure Source Definition Aspects

A Source Definition Aspect must be configured for each Control Network object. This must be done in order to get the Deploy functionality to work. Figure 77 shows an example system with three Control Networks, each one representing a PLC Connect Connectivity Server.

1. If the PLC Connect and the SoftPoint Server are installed in the same node, skip the next steps and continue with Change Service Group Names for the SoftPoint Server on page 163. Otherwise, continue with Change Service Group Names for the PLC Server on page 160.

Change Service Group Names for the PLC Server


Figure 77. Multiple Control Networks

This configuration is optional, but is recommended if there is more than one Service Group. This will avoid confusion with Service Groups having the same name.


3BUA000156R4101 161

2. Use the Object Browser to expand the PLC Server, Service object. The Service Groups in the PLC Server will be shown. Figure 78 shows an example with four Service Groups, three representing the PLC Connect Connectivity Servers and one representing the Aspect Server (in this example Computer4).

3. Select a Service Group that represents a PLC Connect Connectivity Server.

4. Select the Name aspect in the Aspect List Area.

Figure 78. PLC Server, Service Object


162 3BUA000156R4101

5. Change the name from Basic to something easily associated with the correct Service Group; for example, the node name as shown in Figure 79.

6. Click Apply.

7. Repeat Step 3 to Step 6 for all Service Groups representing PLC Connect Connectivity Servers.

8. Continue with Create Source Definition Aspects on page 165.

Figure 79. Name Aspect


3BUA000156R4101 163

Change Service Group Names for the SoftPoint Server


2. Use the Object Browser to expand the SoftPoint Server, Service object. The Service Groups in both the SoftPoint Server and the PLC Server will be shown. When a Service Group is expanded, the corresponding Service Provider name shows if it belongs to the SoftPoint Server or PLC Server.

Figure 80 shows an example with four Service Groups belonging to the PLC Server and one belonging to the SoftPoint Server. Of the four Service Groups belonging to the PLC Server, three represent the PLC Connect Connectivity Servers and one represents the Aspect Server (in this example Computer4).

This configuration is optional, but is recommended if there is more than one Service Group. This will avoid confusion with Service Groups having the same name.

Figure 80. SoftPoint Server, Service Object


164 3BUA000156R4101

3. Select a Service Group that represents a PLC Connect Connectivity Server.

4. Select the Name aspect in the Aspect List Area.

5. Change the name from Basic to something easily associated with the correct Service Group; for example, the node name.

6. Click Apply.

7. Repeat Step 3 to Step 6 for all Service Groups representing PLC Connect Connectivity Servers.

8. Use the Object Browser to select a Service Group belonging to the SoftPoint Server.



11. Deselect the Enabled check box as shown in Figure 81.

Figure 81. Disabling a Service Group


3BUA000156R4101 165

12. Click Apply.

13. Repeat Step 8 to Step 12 for any other Service Groups belonging to the SoftPoint Server.

Create Source Definition Aspects


2. Use the Object Browser to right-click a Control Network object.

3. Select New Aspect from the context menu that appears.

4. The New Aspect dialog appears. Select the List Presentation check box.

5. From the left-hand list, select Source Definition.

6. Click Create.

7. Select the created Source Definition aspect in the Aspect List Area (Figure 82).

Figure 82. Source Definition Aspect


166 3BUA000156R4101

8. From the Service Group drop-down list box, select the Service Group the Control Network is to use, that is, select the Service Group representing the PLC Connect Connectivity Server that is connected to the Control Network.

9. Click Apply.

10. Repeat Step 2 to Step 9 for each other Control Network object.

11. Use the Configuration Wizard to restart each server in the system.

12. If both the PLC Connect and the SoftPoint Server are installed in the same node, continue with Drag SoftPoint Object on page 166. Otherwise, continue with Alarm and Event Setup on page 167.

Drag SoftPoint Object


2. Use the Object Browser to drag the SoftPoints, SoftPoints Type object from a SoftPoint Generic Control Network to the corresponding PLC Generic Control Network. Place the object at the same level as the Controllers, PLC Controller Type object as shown in Figure 83.

3. Use the Object Browser to select the PLC Generic Control Network containing the dragged object.

4. Select the Deploy aspect in the Aspect List Area.

5. Click Deploy in the Preview Area.

6. Repeat Step 2 to Step 5 for any other SoftPoint Generic Control Networks.

7. Continue with Alarm and Event Setup on page 167.

Figure 83. Dragged Object

Section 15 PLC Connect Alarm and Event Setup

3BUA000156R4101 167

Alarm and Event Setup

The alarm and event system must be configured manually in order to function correctly.



3. Use the Object Browser to expand the AlarmManager, Service object as shown in Figure 84.

4. Select the Service Group object.



The connection between the PLC Connect Event Server and the System Event Server needs to be set up manually.

Figure 84. Service Structure

Alarm and Event Setup Section 15 PLC Connect

168 3BUA000156R4101

7. Configure the event handling according to Figure 85:

– Deselect Make new alarm entry each time a condition gets active.

– Select Log Acknowledge.– Select Log Active->Inactive change.– Select Log Enable/Disable.– Deselect Log Hidden -> Not Hidden change.

8. Click Apply.

9. Create the Service Group and Service Provider Objects in Step 10 through Step 17, if they do not already exist.

10. Right-click on EventCollector, Service and select New Object from the context menu that appears.

11. The New Object dialog appears. Select Service Group, enter a name easily associated with the Service Group; for example, the node name, and click Create.


Figure 85. Alarm and Event Setup

Deselecting Make new alarm entry each time a condition gets active is a system wide setting. This is only a recommendation for PLC Connect. It may conflict with other applications.

Section 15 PLC Connect Alarm and Event Setup

3BUA000156R4101 169

13. The New Object dialog appears. Select Service Provider, enter a name, and click Create.

14. Use the Object Browser to select the Service Provider object under the selected Service Group object, as shown in Figure 86.

15. Select the Service Provider Definition aspect in the Aspect List Area.

16. Select the relevant node in the Node: drop-down list box.

17. Click Apply.

18. Repeat Step 12 through Step 17 for other PLC Connect Connectivity Servers.

Figure 86. Service Provider Object

Alarm and Event Setup Section 15 PLC Connect

170 3BUA000156R4101




22. Select Ads OPC Event Server in the Alarm Server: drop-down list box.

23. If an Ads OPC Event Server Collection Definition is not already created, click New to create one.

24. Click Apply.

25. Click Edit in the Collection Mapping frame.

26. The Alarm Collection Definition aspect appears. Configure it according to Figure 87.

– Select Supports Refresh.– Select Supports Disabling.– Deselect Supports Disabling on condition.– Deselect Inhibit Event Logging.

27. Click Apply.

28. Repeat Step 19 through Step 27 for all Service Groups representing PLC Connect Connectivity Servers.

Figure 87. Alarm Collection Definition Aspect

Section 15 PLC Connect IEC 60870 Licensing

3BUA000156R4101 171

IEC 60870 Licensing

Software keys

The software key for the IEC 60870 driver is specific to the node on which it is installed. A new software key may also be required if the configuration of the node is changed. The licensing procedure for a node is described below.

If necessary, you can also transfer a license from one node to another, see Transferring the Software License on page 174. Other licensing options are described in Other Licensing Options on page 174.

Licensing Procedure

The following must be done to license the IEC 60870 driver for a node:

1. Enable temporary authorization to use the driver up to 30 days.

2. During installation of PLC Connect with the IEC 60870 driver option on a node, all license related data is stored in two files. Complete and send them to ABB.

3. Within a week from request ABB will send back a file with a software key. Use it to complete the formal licensing.

Enabling Temporary Authorization

A temporary key allows the IEC 60870 driver to run in fully functional mode for 30 days from the installation date.

1. Log on, with Administrator privileges, to a node with the IEC 60870 driver option installed.

2. Start the software authorization licensing program:

Start > All Programs > ABB Industrial IT 800xA > PLC Connect > IEC60870 > License Utility

The MTK Software Authorization dialog box is displayed.

Licensing Procedure Section 15 PLC Connect

172 3BUA000156R4101

3. Select Enable temporary authorization as shown in Figure 88.

4. Make sure the path is correct; \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870. If necessary, use the button to locate the file.

5. Click OK.

The application processes the key file and a confirmation message verifies that the software has been successfully licensed. If an error occurs, note the error information carefully, and contact ABB Service.

Complete and Send the License Files

1. During installation of PLC Connect with the IEC 60870 driver option on a node, all license related data is stored in two files: Software Key Request.doc and AuthorizeRequest.MTK. The two files are created in the folder \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870.

2. Fill out the Software Key Request file. (The file AuthorizeRequest.MTK is automatically generated).

3. Send the two files by e-mail to [email protected].

Figure 88. MTK Software Authorization Dialog Box

Section 15 PLC Connect Licensing Procedure

3BUA000156R4101 173

Complete Formal Licensing

1. Within a week from a request ABB will issue a software license key file named Authorize.MTK and send it to your e-mail address.

2. Log on, with Administrator privileges, to the node for which you requested the license.

3. Copy the file Authorize.MTK to the folder \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870.

4. Run the Software Authorization licensing program (Figure 89).

5. Select License this software.

6. Use the button to locate the authorization file. Make sure the path is correct; \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870.

7. Click OK.

The application processes the key file and a confirmation message verifies that the software has been successfully licensed. If an error occurs, note the error information carefully, and contact ABB Service.

8. Backup all licensing files, *.MTK, from the folder \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870 to removable media.

Figure 89. Licensing the IEC 60870 Driver

Transferring the Software License Section 15 PLC Connect

174 3BUA000156R4101

Transferring the Software License

If you are transferring a license from one node to another node, you need to do the following:

1. Locate the file REMOVEREQUEST.MTK on the previously used node. This file was generated during the authorization process, and is located in the folder \..\ABB Industrial IT\Operate IT\PLC Connect\IEC60870. Send the file to ABB together with the two files generated on the new node.

2. When you enter information into the Software Key Request form you must specify “Transfer of software” and state the reason for the transfer.

If you are transferring the software to another node, you can install it there first, and send your new authorization request file along with the remove request file at the same time. ABB will then issue you a license authorization file for the new node.

Other Licensing Options

The rest of the licensing options in the MTK Software Authorization dialog box, see Figure 90, are described in Table 11. When you select an action, the corresponding default path and file name is displayed. The button can be used to locate a file.

Table 11. Other Licensing Options PLC Connect

Function Description

Create authorization request Creates a software license request file. Normally you do not need to use this function, since a request file is generated automatically during installation.

De-license this software Removes the licensing. Use this function if you are requested by ABB to do so, for example to return the software after an evaluation period.

Section 15 PLC Connect PLC Server

3BUA000156R4101 175

PLC ServerThe PLC Server manages all PLC Connect specific server processes. It is configured automatically during the software installation. However, it may be necessary to configure PLC Server processes manually for a specific Control Network, for example, to:

• Restart a server process for the Control Network.

• Add a program as a server process for the Control Network; for example, to use a program of your own together with the system.

Configure PLC Server Processes

To configure PLC Server processes for a specific Control Network:

1. Start a Plant Explorer Workplace.


3. Use the Object Browser to select the object named PLC Server, Service.

Figure 90. Licensing Options

PLC Server Section 15 PLC Connect

176 3BUA000156R4101

4. Select the Service Group object for the desired Control Network (the Service Group object representing the node with the Connectivity Server that is connected to the desired Control Network). An example is presented in Service Structure Example on page 176.


6. Select the Special Configuration tab in the Preview Area to view the server processes for the Control Network.

7. Click Help for more information on how to use the tab.

8. To configure the same server processes for other Control Networks, repeat Step 4 to Step 7 for each.

Service Structure Example

Typically, the names of the Service Group objects are the same as the respective node name. In the example in Figure 91, they are 'Computer1', 'Computer2', and 'Computer3'.

Figure 91. Service Structure Example

3BUA000156R4101 177

Section 16 Asset Optimization

IntroductionThe Asset Optimization functional area includes:

• Asset Optimization.• PC, Network and Software Monitoring.

After loading the system extensions according to Adding System Extensions on page 31, perform the following post installation procedures for Asset Optimization. There are no post installation requirements for PC, Network and Software Monitoring.

Post installation steps for Asset Optimization include:

• AoWebServerNode.• AssetMonitoring Service Provider Node.• Adding Additional AO Servers to the System.• Asset Optimization Aspect Permissions Configuration.• Web-Enabled Views on Non-Industrial IT Systems.• DMS Calibration Integration.• SAP/PM Integration.• Internet Explorer Configuration.• Excel Initialization.

AoWebServerNodeThe following steps are required to correctly set the AO Web Server Node.




Root, Domain > Asset Optimization, Asset Optimization

AssetMonitoring Service Provider Node Section 16 Asset Optimization

178 3BUA000156R4101

4. Select Asset Optimization Configuration Properties in the Aspect List Area.

5. In the Preview Area, set the AoWebServerNode property to the name of the AO Server node designated as the AO Web Server. If Maximo Connectivity is installed, the AoWebServerNode is the location where the Maximo SDK must be installed.

AssetMonitoring Service Provider Node1. Open a Plant Explorer Workplace.



Root, Domain > AO Server 1, AO Server

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

5. Click Navigate to AssetMonitoring Service Provider.

6. The Service Provider Definition dialog shown in Figure 92 appears.

The AO Server node designated as the AO Web Server in a multinode system must be a node using Windows 2000 Server or Windows Server™ 2003 as the operating system.

TC06060A

Figure 92. Service Provider Definition Dialog

Section 16 Asset Optimization Adding Additional AO Servers to the System

3BUA000156R4101 179

7. Select the AssetMonitoring Service Provider Node in the Node: drop-down list box and click Apply.

8. The Current field should change from Undefined to Service.

Refer to Industrial IT, 800xA - Asset Optimization, Configuration for information on how to load the AO Server configuration.

Adding Additional AO Servers to the SystemAsset Monitoring supports a maximum number of four AO Servers, each configured on a different Connectivity Server node. Each AO Server can support a maximum number of 30,000 conditions, which is 2,500 Asset Monitors with 12 conditions each. The total supported Asset Monitors (with an average of 12 conditions each) is 10,000 per 800xA System.

The Asset Optimizer Server System Extension provides the configuration for one AO Server. An AO Server is represented by:

• An AO Server Object located in the Control Structure under the Asset Optimization parent node.

• An AssetMonitoring Service Group and related Service Provider in the Service Structure.

To add an additional AO Server node in an 800xA Systems:



3. Use the Object Browser to navigate to and right-click on:

Services > AssetMonitoring, Service

4. Select New Object from the context menu that appears. This opens the New Object dialog.

5. Select Service Group from the list on the left.

Usually, the AssetMonitoring Service Provider Node is the same one specified by the AoWebServerNode property.

Never delete the Asset Optimization object in the Control Structure since this object has a specific ID.

Adding Additional AO Servers to the System Section 16 Asset Optimization

180 3BUA000156R4101

6. Type a name in the Name field and click Create.

7. Use the Object Browser to navigate to and right-click on the newly created Service Group.

8. Select New Object from the context menu that appears. This opens the New Object dialog.

9. Select Service Provider from the list on the left.

10. Type a name in the Name field and click Create. Figure 93 shows the newly created Service Group and Provider.


12. Use the Object Browser to navigate to and right-click on:

Root > Asset Optimization

TC06974A

Figure 93. Adding Service Group and Service Provider Objects

Section 16 Asset Optimization Adding Additional AO Servers to the System

3BUA000156R4101 181

13. Select New Object from the context menu that appears. This opens the New Object dialog as shown in Figure 94.

14. Select AO Server from the list on the left.

15. Type a name in the Name field and click Create.

16. Use the Object Browser to select the newly created object.

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

TC06975A


Asset Optimization Aspect Permissions Configuration Section 16 Asset Optimization

182 3BUA000156R4101

18. Click Navigate to Data Source Definition (Figure 95) and configure the AM Service Data Source Definition to point to the previously created AssetMonitoring Service Group. The Data Key shown in Figure 95 will be set automatically.

19. Navigate back to the Asset Optimization Server default view aspect.

20. Click on Navigate to AssetMonitoring Service Provider and select the node identified to host this AO Server.

21. Navigate back to the Asset Optimization Server and verify that the Service Status is Service and AM Engine Status is good. Now it is possible to assign Asset Monitors to run in this AO Server. Refer to Industrial IT, 800xA - Asset Optimization, Configuration and Industrial IT, 800xA - Asset Optimization, Operation for more information.

Asset Optimization Aspect Permissions ConfigurationSome Asset Optimization aspects do not have default permissions established. To increase security on these aspects:


2. Use the Structure Selector to open the Aspect System Structure.

TC06976A

Figure 95. Asset Optimization Server Aspect

There can only be one AssetMonitoring service per node.

Section 16 Asset Optimization Web-Enabled Views on Non-Industrial IT Systems

3BUA000156R4101 183

3. Use the Object Browser to navigate to the Aspect Category Definition for each aspect to be modified.

4. Select the Permissions tab in the Preview Area and set permissions on the operations as required.

Web-Enabled Views on Non-Industrial IT SystemsThe software requirements on non-Industrial IT systems required to support web-enabled Asset Optimization views are:

• Internet Explorer 6 or later.• MS XML 3.0 with Service Pack 2 or later.

The maximum security settings on non-Industrial IT systems required to support web-enabled Asset Optimization views are:

• Set Local Intranet security to High.• Select Custom Level and set the following:

– Download signed ActiveX ® controls: Prompt.– Run ActiveX controls and plug-ins: Enable.– Script ActiveX controls marked for safe scripting: Enable.– Active scripting: Enable.

DMS Calibration IntegrationThere are three post installation tasks required when using DMS Calibration Integration:

• DMS Software Users Configuration.• DMS Server Configuration on non-800xA System Node.• Changing the DMS Server Location.• Recreate DMS Scheduled Tasks.

Accessing the Asset Optimization thin client interface always requires user authentication for Asset Optimization web pages.

To access Maximo portal views, set Microsoft VM to High Safety and Scripting of Java™ applets to Enable.

DMS Software Users Configuration Section 16 Asset Optimization

184 3BUA000156R4101

DMS Software Users Configuration

800xA System users must also be configured in the DMS software. Configure all 800xA System users in the DMS software who require access to DMS information, including the 800xA Service User. Refer to the Meriam Process Technologies User Guide Device Management System instruction for information on configuring users.

DMS Server Configuration on non-800xA System Node

If the DMS Server is installed on a non-800xA System node, additional Asset Optimization software components are required.

1. From the DMS Server node, navigate to the Asset Viewer web page at:

http://<aoserver>/abbao

where <aoserver> is the hostname of the Main AO Server node.

2. If prompted to accept the Asset Viewer ActiveX component, accept it. This component is required for connection to the DMS Server.

Changing the DMS Server Location

The DMS Server location is defined by the DMS Server URL configured in the DMS client. In the rare case where a DMS Server must be moved, the location must be changed for all DMS clients on all nodes, and the AO Server must be rebooted. Refer to the Meriam Process Technologies User Guide Device Management System instruction for information on changing the URL.

If using the non-21 CFR Part 11 version of the DMS software, a prompt will appear asking that a password be entered, even for domain users. This is due to creating a DMS account to use if logging into the DMS client without using Windows Integrated Security. This password does not need to match the Windows password and must be between four and ten characters.

Section 16 Asset Optimization Recreate DMS Scheduled Tasks

3BUA000156R4101 185

Recreate DMS Scheduled Tasks

When the DMS Server is installed it creates two scheduled tasks that run daily under the NT Authority\SYSTEM account. These should run under the 800xa Service account and therefore need to be recreated.

Perform the following procedure to create a new scheduled task.

1. Select:

Start > Control Panel > Scheduled Tasks

2. Double-click Add Scheduled Task.

3. The Scheduled Task Wizard appears. Click Next to continue.

4. Click Browse in the next dialog to select the program to run. Navigate to the location where the DMS Server was installed:

...\Program Files\Meriam\DMSServer

and select DMSCacheCleanUp.exe the first time through this procedure and mAMSAlertService.exe the second time through this procedure.

5. Click Open to continue to the next dialog.

6. Type in the name for the scheduled task. The tasks that are being replaced are AT1 and AT2, but the new scheduled tasks can be named for the programs that are run (DMSCacheCleanUp and mAMSAlertService).

Perform this procedure for both DMSCacheCleanUp.exe and mAMSAlertService.exe.

Remove the old scheduled tasks after the new scheduled tasks are created.

Recreate DMS Scheduled Tasks Section 16 Asset Optimization

186 3BUA000156R4101

7. Select Weekly in the Perform this Task list (Figure 96) and click Next to continue to the next dialog.

8. Make the desired selections as shown in the example in Figure 97 and click Next to continue to the next dialog.

Figure 96. Scheduled Task Wizard - Perform the Task Selection

Figure 97. Scheduled Task Wizard - Setting up the Schedule

Section 16 Asset Optimization SAP/PM Integration

3BUA000156R4101 187

9. Select the account used to install the 800xA System to run the task under and click Next to continue to the next dialog.

10. Click Finish to add this task to the Windows scheduler.

11. Repeat the procedure to create the second task.

12. When complete, go to Scheduled Tasks in Control Panel and delete AT1 and AT2.

SAP/PM IntegrationThe Asset Optimization integration with the SAP/PM module requires that your SAP administrator install ABAP code on the SAP/PM production server where the PM module is installed.

1. Navigate to the directory where Asset Optimization software is installed.

2. Use Windows Explorer to locate the following directory:

...\Asset Optimization\SAPConnectivity\SAP-ABAP

3. This directory contains the source for ABB's ABAP integration code and documentation that describes the ABAP code integration.

The ABB ABAP integration code source files are:

– Z_ABB_EQUIPMENT_DETAIL.ABAP.doc– Z_ABB_MS_LIST.ABAP.doc– Z_ABB_NOTIFICATION_CREATE.ABAP.doc– Z_ABB_NOTIFICATION_LIST.ABAP.doc– Z_ABB_OBJECTSTATUS_LIST.ABAP.doc– Z_ABB_WORKORDER_LIST.ABAP.doc

Reference documents include the following:

– SAP RTAO Development.doc– - Z_ABB_PM_FunctionGroup-Modules.doc

Refer to the SAP/PM Basis and ABAP integration personnel for details involving the addition of ABAP-enabled interfaces in SAP/PM.

Internet Explorer Configuration Section 16 Asset Optimization

188 3BUA000156R4101

Internet Explorer Configuration1. Use standard Windows procedures to access the Local Area Network (LAN)

Settings dialog shown in Figure 98.

2. If proxy configuration is enabled, select the Automatically detect settings check box.

Excel InitializationThe following procedure is necessary if using the XY Profile Deviation Asset Monitor.

1. Use the 800xA Service User account to open Microsoft Excel at least once.

2. Perform the required user setup (first time execution installation user initials).

TC06064A

Figure 98. LAN Settings Dialog

Failure to perform the required Microsoft Excel user setup when using the XY Profile Deviation Asset Monitor may cause the AO Server startup to fail.

3BUA000156R4101 189

Section 17 Production Management

IntroductionThis section provides post installation tasks for the components of the Production Management functional area:

• Batch Management.• Manufacturing Management.

Batch ManagementBatch Management post installation tasks consist of:

• Batch Management System Service Definitions.• Shutdown Script.• Print BMA Report Configuration.• Internet Explorer Configuration.• Initialize Office for Batch Users.• Batch Management Toolbar.• Using Batch Management Advanced Templates Only.

Batch Management System Service Definitions

At this point in the installation process, all Batch applications (servers and clients) should be in client mode. A letter C should be displayed in the Windows Taskbar. Reinstall the appropriate Batch application in any Batch nodes not in this condition.

To define the Primary Batch Server to the Batch service:

1. Verify all (both Primary and Secondary) Batch Servers are in client mode.

2. Open a Plant Explorer Workplace on any Batch node.


Batch Management System Service Definitions Section 17 Production Management

190 3BUA000156R4101

4. Right-click Services\Batch Service, Service.

5. Select New Object from the context menu that appears.

6. Select Service Group in the New Object dialog.

7. Enter a name and, if desired, description of the group, and click Create.

8. Right-click the newly created group object.


10. Select Service Provider in the New Object dialog.

11. Enter a name and, if desired, description of the Service Provider and click Create.

12. Select the Service Provider Definition aspect of the Service Provider object in the Aspect List Area.

13. Select the Configuration tab.

14. Select the name of the Primary Batch Server node in the Node field. Refer to Figure 99.

TC04597A

Figure 99. Service Provider Definition Dialog

Section 17 Production Management Batch Management System Service Definitions

3BUA000156R4101 191

15. Click Apply.

16. Verify the Primary Batch Server node is in primary mode by viewing a P in the Windows Taskbar. This step may require a few minutes to complete.

17. Right-click Services\EventCollector, Service.


19. Select Service Group in the New Object dialog.

20. Enter a name and, if desired, description of the group and click Create.

21. Right-click the newly created group object.






27. Select the name of the Primary Batch Server node in the Node field.

28. Click Apply.

29. Select the EventCollector Service group object created during Step 17 through Step 20.

30. Select the Service Group Definition aspect.

31. Select the Special Configuration tab.

32. Select Produce IT Batch OPC AE Server in the OPC A&E Server area of the dialog.

33. Click New in the Collection Mapping area. This will insert Produce IT Batch OPC AE Server in the field.

34. Click Apply.

35. Verify that Batch event attribute definition aspects are added to the Alarm Manager Service group object.

Batch Management System Service Definitions Section 17 Production Management

192 3BUA000156R4101

To define the Secondary Batch Servers to the Batch service:

1. Right-click the Batch Service group object (created when defining the Primary Batch Server to the Batch service).






7. Select the name of the Secondary Batch Server node in the Node field.

8. Click Apply.

9. Verify the Secondary Batch Server node is in secondary mode by viewing an S in the Windows Taskbar. This step may require a few minutes to complete.

10. Right-click the EventCollector Service group object (created when defining the primary alarm and event server to the Batch service).






16. Select the name of the Secondary Batch Server node in the Node field.

17. Click Apply.

Section 17 Production Management Shutdown Script

3BUA000156R4101 193

Shutdown Script

The batch_shutdown.bat script shuts down the Batch application properly and must be installed on all Batch Servers. To install this script:

1. Run gpedit.msc from the Start menu.

2. Select:

Computer Configuration > Windows Settings > Scripts (Startup/Shutdown)

3. Double click Shutdown.

4. Click Add.

5. Click Browse.

6. Select:

...\Program Files\ABB Industrial IT\Produce IT\Batch\bin\batch_shutdown.bat in the Script Name field.

7. Click OK.

8. Click OK.

9. Close the Group Policy dialog.

Print BMA Report Configuration

In order to print a BMA report, the Batch application must be configured (refer to Industrial IT, 800xA - Production Management, Batch Management, Configuration) and the AT Service Account must be configured to use the settings of a certain account. All print requests for a BMA report from any user will use the settings from this account to print the report.

Internet Explorer Configuration Section 17 Production Management

194 3BUA000156R4101

To configure the AT Service Account:

1. Select:

Start > All Programs > ABB Industrial IT 800xA > System > Configuration Wizard.

2. Double-click Systems Software User Settings.

3. Record the user account name listed in the Service Account, Used by System Software field.

4. Exit the configuration wizard.

5. Use standard Windows procedures to access Scheduled Tasks via Windows Control Panel.

6. Select:

Advanced > AT Service Account

from the menu bar.

7. Select the This Account check box.

8. Enter the user account name recorded in Step 3.

9. Enter the password for the account in the Password and Confirm Password fields.

10. Click OK.

11. Log in as the user recorded in Step 3.

12. Configure a default printer.

Internet Explorer Configuration

To configure the Internet Explorer options:

1. Start Internet Explorer.

2. Select:



4. Select the Local Intranet web content zone.

5. Click Custom Level.

Section 17 Production Management Initialize Office for Batch Users

3BUA000156R4101 195

6. Enable Initialize and script ActiveX controls not marked as safe.

7. Click OK.

8. Click Yes when prompted to confirm that the security changes should be made.

Initialize Office for Batch Users

Each Batch node containing one or more Microsoft Office applications must be initialized to recognized each Batch user that does not have Windows administrator privileges. For each Batch user that does not have Windows administrator privileges:

1. Log into a Batch node as the Batch user being initialized.

2. Open any Microsoft Office application.

3. Close the application.

4. Log out of the Batch node.

5. Repeat Step 1 through Step 4 for all the Batch users being initialized on this node.

6. Repeat Step 1 through Step 5 on all Batch nodes.

Batch Management Toolbar

Batch Management provides a toolbar that contains buttons for the Batch Overview, Batch History Overview, and Equipment Overview dialogs. If desired, refer to Industrial IT, 800xA - Production Management, Batch Management, Configuration for information about enabling this toolbar.

Using Batch Management Advanced Templates Only

In some scenarios, it may be required to use the advanced control modules provided by Batch Management without running Batch procedures from a Batch Server. To use the advanced control modules in this way:

1. Install a Batch Client on all nodes.

2. Add the Batch Management extension and Batch Management Advanced Templates extension on the Primary Aspect Server using the 800xA System configuration wizard.

Manufacturing Management Section 17 Production Management

196 3BUA000156R4101

Manufacturing ManagementManufacturing Management post installation tasks consist of:

• Create Virtual Directory.• Create User Account.• Create Database.• Configure Plant Explorer.• Internet Explorer Configuration.• Batch Management/Manufacturing Management Connection.• Component Security Configuration.• Install FrontPage Add-in.

Create Virtual Directory

A virtual directory must be created on the Manufacturing Management Application/Web Server node. To create the virtual directory:

1. Select:

Start > Control Panel > Administrative Tools >Internet Services Manager

2. Select the node and then Default Web Site in the Internet Information Services dialog.

3. Select:

Action > New > Virtual Directory

4. Click Next in the Virtual Directory Creation Wizard Welcome dialog.

5. Enter EBRWEB in the Alias field of the Virtual Directory Alias dialog.

6. Click Next.

7. Select:

...\Program Files\ABB Industrial IT\Produce IT\Manufacturing Management\EBRWeb in the Directory field in the Web Site Content Directory dialog

8. Click Next.

Section 17 Production Management Create Virtual Directory

3BUA000156R4101 197

9. Enable the Read, Run Scripts, and Browse options in the Access Permissions dialog.

10. Click Next. The Virtual Directory Creation dialog reports successful completion of the virtual directory.

11. Click Finish to complete the operation and return to the Internet Information Services dialog.

12. Right-click EBRWeb.

13. Select Properties in the context menu that appears.

14. Select the Virtual Directory tab in the EBRWeb Properties dialog.

15. Select Scripts and Executables in the Execute Permissions field.

16. Click Apply.

17. Click OK to return to the Internet Information Services dialog.

18. Click the (+) on EBRWeb to display the IFWebNet and MMCommunicator folders.

19. Right-click IFWebNet.


21. Click Create in the IFWebNet Properties dialog.

22. Select the Directory Security tab.

23. Click Edit and enable Anonymous Access.

24. Enter the name and password of a user that has administrative rights.

25. Enable Integrated Windows Authentication.

26. Click OK.

27. Right-click MMCommunicator in the Internet Information Services dialog.


29. Click Create in the MMCommunicator Properties dialog.

30. Select the Directory Security tab.

31. Click Edit and enable Anonymous Access.

Create Virtual Directory Section 17 Production Management

198 3BUA000156R4101

32. Enter the name and password of a user that has administrative rights.

33. Enable Integrated Windows Authentication.

34. Click OK.

35. Click OK in the MMCommunicator Properties dialog.

Perform the following procedure if the Windows 2003 operating system is being used:

1. Select:

Start > Control Panel > Administrative Tools > Internet InformationServices (IIS) Manager

2. Select the local computer in the Internet Information Services dialog.

3. Right-click Application Pools.

4. Select New > Application Pool (from file) in the context menu that appears.

5. Select:

...\Program Files\ABB Industrial IT\Produce IT\Manufacturing Management\EBRWeb\MMWebServerPool.xml

6. Click Read File.

7. Select MMWebServerPool in the Location section.


9. Right-click IFWebNet in the Web Sites\Default Web Site folder.


11. Set the application pool to MMWebServer Pool.

12. Click OK.

13. Right-click EBRWeb\MMCommunicator in the Web Sites\Default Web Site folder.


15. Set the application pool to MMWebServer Pool.

16. Click OK.


Section 17 Production Management Create User Account

3BUA000156R4101 199

Create User Account

This procedure creates a Windows user account and configures the Business Object server to run with the new user identity. The user can be a local or domain user but it must be granted administrative privileges on the Manufacturing Management Application/Web Server. To create the required user account and enable its use:

1. Select:

Start > Control Panel > Administrative Tools >Computer Management

2. Select Local Users and Groups and then Users in the left pane of the dialog.

3. Click Action > New User to create a new user. Set the password (operateit is recommended) to never expire.

4. Add the new user to the Administrators group.

5. Select:

Start > Control Panel > Administrative Tools > Component Services

6. Expand the Component Services structure until BusinessObjects is selected.

7. Select:

Action > Properties

8. Select the Identity tab in the BusinessObjects Properties dialog.

9. Select the This user check box.

10. Enter or select the user name for the account that was created in Step 3.

11. Enter the account password in the remaining fields.

12. Click OK. If the account is accepted, the dialog will close.

13. Close the Component Services dialog.

Verify that the ASP.NET user account is in the Administrators group on Windows 2000 systems. The NT Service account does not need to be in the Administrators group on Windows 2003 systems.

Create Database Section 17 Production Management

200 3BUA000156R4101

Create Database

The Manufacturing Management database uses the Microsoft SQL Server™ 2000 database engine. The MM Server installation program copies an empty Manufacturing Management master database onto the Manufacturing Management Application/Web Server node.

Instructions for restoring the Manufacturing Management database to a running instance of SQL Server 2000 follow.

Database Layout Guidelines

As with most client-server applications, the overall performance of Manufacturing Management applications is largely dependent on the I/O performance of the database server.

To promote optimal I/O performance, it is critical that the tables and indexes in the database be arranged across available disk devices in a manner that evenly distributes the I/O load.

Using a Redundant Disk Array. A redundant array of independent disks, or RAID, can provide large amounts of I/O throughput and capacity. It can appear to the operating system and RDBMS as a single large disk, or as multiple disks, as desired, for manageability.

The use of RAID can greatly simplify the database layout process by providing an abstraction layer above the physical disks, while promoting high performance.

Planning the Distribution of Your Database Objects. Regardless of the RDBMS you implement and your chosen disk arrangement, you must be sure that you properly distribute the following types of database objects:

• Database log or archive files. • Temporary work space used by the database. • Tables and indexes.

Preliminary Tasks

Before restoring the Manufacturing Management database, verify the following information is known or configured:

• SQL Server login ID.

Section 17 Production Management Create Database

3BUA000156R4101 201

• SQL Server password.• Server name (or Server name/Instance name).• An empty database named MMDB has been created.

SQL Server Prerequisites

Manufacturing Management requires the following settings in SQL Server 2000:

• Mixed Mode Authentication.• SQL Server Agent configured and running.• Replication Distributor configured (optional).• Manufacturing Management can use Named or Local instances. Some

configuration steps will be different depending on the type of instance chosen.

The following items should be created in SQL Server:

• One SQL Server Login account with a non-blank password. Use of the sa account is not recommended. The user must have a server role of System Administrator. The login name and password are required in the following section for the MM System Configuration aspect.

• One or more empty databases with data and log files placed as desired for best database performance. Example databases are MMProd for a production database and MMTest for a test/development database.

Database Creation for SQL Server 2000

Manufacturing Management installs a SQL Server backup of an empty database into the Database subdirectory of the Manufacturing Management application. Restore the database backup to a new database created in your instance of SQL Server. Typical location of the master database:

...\program files\ABB Industrial IT\Produce IT\Manufacturing Managment\Database\MMMasterDB.bak

Restore Master Database to an Empty SQL Server Database. To restore the master database:

1. Start the SQL Server Enterprise Manager and browse to the Databases folder.

2. Right-click the Databases folder.

Create Database Section 17 Production Management

202 3BUA000156R4101

3. Select:

All Tasks > Restore Database

from the context menu that appears.

4. Enter the name of the target database. If this database does not exist, it will be created. If it exists, all existing data in it will be lost.

5. Locate the set of options labeled Restore.

6. Enable the From Device option.

7. Click Select Devices in the Parameters area of the Restore Database dialog.

8. Click Add in the Choose Restore Devices dialog.

9. Click Browse next to the File Name field in the Choose Restore Destination dialog.

10. Browse to the location on the database server where the MMMasterDB.bak backup file is located and select it in the Backup Device Location dialog.

11. Click OK in the Choose Restore Destination dialog.

12. Click OK in the Choose Restore Devices dialog.

13. Click OK to return to the Restore Database dialog.

14. Select the Options tab.

15. Enable the Force restore over existing database option.

16. Click OK in the Restore Database dialog. The database should be restored without error.

17. If device activation error or other restore error is received, edit the RestoreAs path (in the Options tab) to indicate the:

...\directory_path\Temporary.mdf

where the database files are to be created.

In the Options tab, review the paths displayed in the Move to physical file name column. This path must exist on the target system. If other databases already exist on this node, it may be preferable to enter the path of the existing files. It is not mandatory to store all databases in a common directory, but it is necessary to enter a valid path in this field. Be sure to leave the file names intact. When ready, click OK.

Section 17 Production Management Create Database

3BUA000156R4101 203

Daemon Installation. A daemon that runs the stored procedure BTSP_DAEMON_EXPIRATION_DATE (installed during the Stored Procedure installation) must be configured on the database server. The stored procedure is installed to the SQL Server Stored Procedures folder of the database created under Create Database on page 200.

This daemon that executes this stored procedure is a scheduled task responsible for the expiration controls within Manufacturing Management. It tracks the controls that have expired and changes the state to the appropriate expired state (i.e., QC Reject).

It is recommended that this task be scheduled to run once per day, preferably when Manufacturing Management usage is at a minimum.

To configure the stored procedure to run as a background process once a day at midnight, the commands in SQL Query Analyzer are as follows:

USE msdbEXEC sp_add_job @job_name = 'Nightly_Updates'

USE msdbEXEC sp_add_jobschedule @job_name = 'Nightly_Updates', @name = 'Run Nightly Updates', @freq_type = 4, -- daily, @freq_interval = 1, @active_start_time = 10000

USE msdbEXEC sp_add_jobstep @job_name = 'Nightly_Updates', @step_name = 'Execute the expiration Daemon', @subsystem = 'TSQL', @command = 'exec BTSP_DAEMON_EXPIRATION_DATE', @retry_attempts = 0, @retry_interval = 0

The database is now ready for use.

The user performing this procedure must be logged in as the Manufacturing Management database user.

Configure Plant Explorer Section 17 Production Management

204 3BUA000156R4101

Configure Plant Explorer

Configure Database Connection

Before starting this procedure, ensure that the Manufacturing Management system extension is installed into the Aspect Directory. Refer to Adding System Extensions on page 31, and return to this section when the system extension is installed.

1. In the Plant Explorer, locate the Library Structure, Manufacturing Management object.

2. Select the MM System Configuration aspect.

3. Enter the SQL Server user account and password.

4. In the Connection field, type the database connect string (SQL Database Service Name).

If an SQL Server instance is used, this will be in the format:

[server_name]\[instance_name]/[database_name]

If there is no instance name, use the format:

[Server Name]\/[Database Name]

5. Click Apply.

Internet Explorer Configuration

To configure the Internet Explorer options:

1. Start Internet Explorer.

2. Select:



4. Select the Local Intranet web content zone.

5. Click Custom Level.

6. Enable Initialize and script ActiveX controls not marked as safe.

7. Click OK.

Section 17 Production Management Batch Management/Manufacturing Management Connection

3BUA000156R4101 205

8. Click Yes when prompted to confirm that the security changes should be made.

9. Select the Content tab.

10. Click AutoComplete.

11. Disable Forms and User names and passwords on forms.

12. Click OK.

Batch Management/Manufacturing Management Connection

The following procedure only applies if Batch Management is installed in the 800xA System.

To connect Manufacturing Management to Batch Management:

1. Log in as a Manufacturing Management user.

2. Select the Library Structure\Manufacturing Management object in the Plant Explorer.

3. Select the MM Server aspect.

4. Select the Manufacturing Management Application Server in the Select MM Server Node To Use field.

5. Click Apply.

Component Security Configuration

Network DTC Access must be enabled on the Manufacturing Management Server node when the Manufacturing Management and Batch Management Servers are on separate nodes.

Network DTC Access must also be enabled on Batch Management Server nodes when:

• Manufacturing Management and Batch Management Servers are on separate nodes.

- and -

• The Batch Management Server node is using the Windows 2003 Server operating system.

Install FrontPage Add-in Section 17 Production Management

206 3BUA000156R4101

To enable Network DTC Access on Windows 2003 Server nodes:

1. Select Program Files > Administrative Tools > Component Services.

2. Expand the Component Services structure until My Computer is selected.

3. Right click My Computer.

4. Select Properties from the context menu.

5. Select the MSDTC tab in the My Computer Properties dialog.

6. Click Security Configuration.

7. Enable Network DTC Access under Security Settings.

8. Click OK.

9. Click OK.

Install FrontPage Add-in

Perform the following procedure only on IForm Developer nodes to install the Manufacturing Management FrontPage® Add-In into Microsoft FrontPage 2003.

If this procedure is performed before a Manufacturing Management database is created, and before the Manufacturing Management System Configuration aspect is configured, then error messages will be generated. These messages mean that the Manufacturing Management FrontPage Add-In is unable to communicate with the Manufacturing Management database. These messages can be ignored. However, the proper functioning of the Add-In should be verified once all installation procedures are complete.

1. Select:

Start > All Programs > Microsoft FrontPage

The Microsoft FrontPage dialog is displayed.

2. Select:

Tools > Add-Ins

3. Click Add in the COM Add-Ins dialog.

Section 17 Production Management Install FrontPage Add-in

3BUA000156R4101 207

4. Browse to:

...\Program Files\ABB Industrial IT\Produce IT\Manufacturing Management\

in the COM Add Add-Ins dialog.

5. Select the EBRCOMAddin.dll file.

6. Click OK. The COM Add-Ins dialog will be updated to include the new add-in the Add-Ins Available area.

7. Click OK to close the COM Add-Ins dialog.

8. Select:

Tools > Customize

9. Select the Commands tab.

10. Select the Format category.

11. Drag the Reformat HTML command from the commands area and drop it at the desired location in the list of menu options available under the Format menu.

12. Exit FrontPage and return to Windows.

Two menu items (IForms and IObjects) have been added to the right side of the Microsoft FrontPage menu bar.

Install FrontPage Add-in Section 17 Production Management

208 3BUA000156R4101

3BUA000156R4101 209

Section 18 Information Management

Introduction

Information Management SetupUse the post installation configuration assistant installed with the Information Management software to ensure that installation and post installation procedures are completed in the correct sequence. To launch the configuration assistant, select:

Start > All Programs > ABB Industrial IT 800xA >Information Mgmt > Configuration Assistant

The Configuration Assistant, Figure 100, lists the installation and post installation requirements in the order in which they must be completed.

Each procedure has a dedicated row. The row indicates whether the procedure is required or optional, whether or not the procedure has been completed, the action to be performed when the procedure is launched from the assistant, and any special considerations and guidelines which apply to the procedure.

The rows are also color-coded. Procedures that have been completed are black. Uncompleted required procedures are red, and uncompleted optional procedures are brown. Some rows are headings for multiple-step procedures, for example, step 4.0 Configuring the DBA (ADO) Data Provider for Oracle. These rows do not have an associated action, since the actions are performed in the steps below. The associated steps are sequentially numbered, for example 4.1, 4.2, and so on. Instructions for the selected procedure (or step) are indicated in the Instructions box in the upper right corner of the display.

Some procedures in this section require administrator-level user privileges. The user must be a domain user with Administrator privileges if the IM Server resides in a domain. Use the 800xA Installing User account.

Information Management Setup Section 18 Information Management

210 3BUA000156R4101

You can confirm all software components have been installed in the Prerequisite Software list in the lower pane. Then use the Configuration Assistant to:

• Modify log on settings for Information Management services (required).

• Create the History database instance (required).

Figure 100. Information Management Configuration Assistant

There are procedures in this section that detail how to perform the following items.

Section 18 Information Management Other Post Installation Procedures

3BUA000156R4101 211

• Initialize communication settings and start Process Administration Supervision (PAS) (required).

• Configure the ADO Data Provider for ORACLE ® Access (DBA) (optional - do this if you require Oracle data access for PDL access for Batch management, and/or history message log access).

Other Post Installation Procedures

When you are finished with the configuration assistant, refer to the list below to determine whether any other post installation is required to set up your system and make it ready for application building. These procedures are covered in the referenced books.

• One or more History Source aspects must be configured to support operator trend and historical data collection. Refer to the section on History Setup in Industrial IT, 800xA - Information Management, Configuration.

• Add-in tools for DataDirect and Information Management History Bulk Configuration are added into Microsoft Excel on a user basis. These add-ins are added by default for the installing user (800xA system Installing User account). If you intend to use these applications as any other user, the corresponding add-ins must be installed in Microsoft Excel for that user. Refer to the section on History Setup in Industrial IT, 800xA - Information Management, Configuration, or DataDirect - Excel Data Access in Industrial IT, 800xA - Information Management, Operation.

• To secure your Information Management database from unauthorized access, change default passwords. See the section on managing users in Industrial IT, 800xA - Information Management, Configuration.

• When using desktop tools with ActiveX controls on Windows XP Professional SP2 nodes, if the default security setting is not changed, a prompt will appear asking whether or not to allow access of blocked controls every time an attempt is made to use a tool that includes an activeX control.

If it is intended to use the 800xA Application Scheduler to run reports created with DataDirect (Excel Data Access), the add-in tools must be added for the 800xAService user account. This is the account used by the Application Scheduler.

Setting the User Information Management Services Section 18 Information Management

212 3BUA000156R4101

1. Launch Internet Explorer.

2. Select:


3. Select the Advanced tab.

4. In the Security section, select the following check boxes:

– Allow active content from CDs to run on My Computer– Allow active content to run in files on My Computer

Setting the User Information Management ServicesThe user account for PAS services must be configured to match the 800xA system service account. This allows related services to log onto the IM Server where they will run. The service account is configured via the 800xA system configuration wizard System Software User Settings dialog when the 800xA core system software is installed. The log on users for these services are configured via the Set PAS Service Account dialog which is accessed via the Information Management Configuration assistant.

Section 18 Information Management Creating a Database Instance

3BUA000156R4101 213

1. Select Set PAS and IM Service Account and Password in the Information Management Configuration Assistant, then click Run Selected Configuration Tool as shown in Step 101.

2. In the Set PAS Service Account dialog, Figure 102, enter the user account and password.

3. Confirm the password, then click OK.

This concludes the procedure for modifying log on settings. Continue with post installation by Creating a Database Instance on page 213.

Creating a Database InstanceUse the DB Instance wizard to create a History database instance. If you are installing Information Management software for an end user, you may not know the

Figure 101. Launching the Set PAS Service Account Dialog

The user account and password information can be obtained via the 800xA Configuration wizard. Launch the configuration wizard via:

Start > All Programs > ABB Industrial IT 800xA >Configuration Wizard

Select System software user settings from the dialog that appears. If you do not know the password, contact the system administrator.

Select this procedure

Creating a Database Instance Section 18 Information Management

214 3BUA000156R4101

History database requirements at this time. In this case, you can use the wizard’s default values to create a default instance sized to fit most History applications. If it is determined later that the default instance is not large enough, the end user can drop this instance and create a new one.

To create the database instance:

1. Launch the DB Instance Wizard from the configuration assistant. Select Create History Database then click Run Selected Configuration Tool.

2. The dialog shown in Figure 103 appears.

3. Use this dialog to:

– Select the drive(s) where Oracle data files and history flat files will be stored. You should select a different drive than the one where you installed

Figure 102. Setting User Name and Password for PAS Services

Figure 103. Selecting the Default Setup


3BUA000156R4101 215

the Oracle program files. Also, it is recommended that you select different drives for Oracle data and for file-based numeric logs.

– Select a base database installation type. The default selection is Standard. This is suitable for small History configurations (typically for demonstrations).

OPC Message base installation is the recommended selection for all actual History configurations. This presets many of the configuration parameters to support a medium to large database configuration with significant message logging capacity.

The MOD 300 and Batch Management options are not applicable for this release.

Click OK when you are finished with this dialog.

4. Use the History Database Instance Sizing dialog, Figure 104, to review the default sizes and change any specifications as required.

Regardless of the option you choose, you must use the wizard to check all settings and make adjustments as required.

Figure 104. History Database Instance Sizing Dialog


216 3BUA000156R4101

– If you are creating a default instance because you do not know the History database requirements at this time, click OK to accept all defaults, then go directly to step 5.

– If you know the database requirements, follow steps a-d to change the defaults as required. Refer to the notes on the following page for considerations regarding DCS message logs and PDLs. DCS message logs are only required when consolidating DCS message logs from earlier Enterprise Historian systems.

– Sizing for a consolidation node should be based on the size of the Information Management/Enterprise Historian nodes from which the consolidation node is consolidating data, as well as any options that will be running on the consolidation node.

a. Select a log type from the list, for example OPC Message Logs.

b. Check the default size as indicated by the selected radio button. For example, in Figure 104, the size specified for OPC Message Logs is Small (up to 500,000 total message log entries). If the default is not appropriate for your application, click the radio button that most closely describes the size for your application.

c. Repeat steps a and b for each log type. If one or more log types are not applicable, click None for those log types.

d. Click OK when you have finished and have specified a size for all log types.

DCS Message Logs - Systems with MOD 300 software typically use one DCS Message Log which is limited to 250,000 entries. MOD 300 users should always select the Small option for DCS Message Log.

Systems with Master software may use up to eight DCS Message Logs which are limited to 250,000 each. The Small option will support two

The wizard will automatically size the applicable Oracle tablespaces according to the size of the OPC message log that you choose. Still it is recommended that you confirm the tablespaces are large enough to support your OPC message log application. Refer to the section on extending tablespace for Oracle-based history files in Industrial IT, 800xA - Information Management, Configuration.


3BUA000156R4101 217

such logs. Select a larger size if you need more than two DCS Message Logs.

PDL - The wizard calculates the PDL tablespace size based on the selected number of PDL logs multiplied by an average PDL record size of 123 bytes. Similarly, the report tablespace is calculated based on the selected number of report logs multiplied by an average report size of 50 Kbytes.

You can adjust the average PDL record and report file sizes if necessary. This is illustrated in Figure 105. If you change the average PDL record or report file size, click Change to accept the change.

Figure 105. Example, Changing Average Report Size


218 3BUA000156R4101

5. Use the Database Instance Drive-Space Configuration dialog to allocate disk space for the database instance, Figure 106.

The note at the bottom of the dialog indicates the minimum space requirement, It is recommended that you allocate space on at least two drives when available. The wizard allocates space for system files on the drive where Oracle is installed. The remaining available space is allocated on the drive that you select in the wizard’s initial dialog (Figure 103).

You can use the default allocation as long as it meets the indicated minimum requirement. A warning message will be displayed if there is not sufficient space available. In this case you must allocate space on another drive.

To change the default disk space allocation:

a. Select a drive from the list. The system drive is selected by default. You may select any drive of the NTFS file type, for example Drive F in Figure 106. Drives that use FAT32 will be marked as Unusable.

The list shows the drive’s total disk space, available space, and space allocated (used) on the drive.

Figure 106. Drive Space Configuration

Selected Drive

Entry for Amountof Space to Use

Minimum AllocationMessage

Click to Auto-ExtendData Files on Drive


3BUA000156R4101 219

b. Enter the amount of space to use on the selected drive in the field below the list. Enter the value in megabyte units, for example 2580.

c. Click the check box if you want data files to auto extend on this drive. This is NOT recommended for the drive where Oracle is installed.

d. Click Apply. This makes a new entry on the line for the selected drive that indicates the amount of disk space to be used for the database instance.

e. Repeat steps a-d for other drives as necessary.

f. Click OK when you are finished.

6. Use the History Flat File Data Drive Space Configuration dialog to specify the amount of disk space to use for storing file-based numeric logs, Figure 107.

If you reduce the disk space allocation on the drive where Oracle is installed to a level that will not support the system files, you will be prompted to re-allocate disk space there. For further information, refer to Database Instance Errors on page 229.

If you get an error message when you exit the Drive Space Configuration dialog, refer to Database Instance Errors on page 229 for guidelines on how to correct the error.

Figure 107. History Flat File Data Drive Space Configuration Dialog


220 3BUA000156R4101

a. Select a drive from the list, for example Drive F. The list indicates the total amount of disk space on the drive as well as the amount of space available to use.

b. Enter the amount of space to use on the selected drive in the corresponding field. Enter the value in megabyte units, for example 3500.

c. Click Apply. This makes a new entry on the line for the selected drive that indicates the amount of disk space to be used for the database instance.

d. Repeat steps a, b, and c for other drives as necessary.

e. Click OK when you are finished.

This displays a report to let you review the database instance configuration, Figure 108. This report is primarily intended to help you troubleshoot in the event of performance problems.

The check box lets you specify whether to create the database instance with or without creating a database. Typically, you should check this box to create a database with the instance. You should leave this box unchecked when you intend to restore a database that you backed up with hsBar, for example when you are performing an upgrade and you need to restore your existing database.

Since volumes that hold historical data must be of the NTFS file type, only volumes of that type are available for selection on this dialog.


3BUA000156R4101 221

7. Click OK to acknowledge.

If there are no errors, the progress bar will be displayed.

When the process is complete, you will see the following message:

If History is running, it must be restarted

and the status will change to Complete.

Figure 108. Review Installation Configuration

If you get an error message when you exit the Drive Space Configuration dialog, refer to Troubleshooting Install Errors on page 229 for guidelines on how to correct the error.

Check to Create History Database with the Oracle Instance

Starting Process Administration Supervision (PAS) Section 18 Information Management

222 3BUA000156R4101

This concludes the procedure for creating the History database instance. Continue with post installation by Starting Process Administration Supervision (PAS) on page 222.

Starting Process Administration Supervision (PAS)PAS manages all Information Management services. PAS must be started after the software has been installed. When you start PAS for the first time you are required to initialize communication settings. This is required for History Services to run. You are not required to configure these settings to their final values at this time, but merely to initialize them.

When the History Service is started under PAS, the following History setup will occur:

• The Service Group/Service Provider structure for the Information Management node will be created in the Service structure.

• The OPC Alarm Server for History will be added for this node’s Alarm and Event Service Group under the Alarm and Event Services category in the Service structure.

• The IM History, IM Archive, and IM Importer links will be added to the Basic History Service Group for this node in the Service structure.

To start PAS and initialize the communication settings, from the configuration assistant, select Enable PAS, then click Run Selected Configuration Tool. This displays the Communication Settings dialog, Figure 109.

You can configure these settings to their final values at this time if you have the required information, or simply initialize them now, and configure them later. This section describes how to initialize the settings. For further guidelines on configuring the settings, refer to Industrial IT, 800xA - Information Management, Configuration.

To simply initialize the current settings and postpone the actual configuration of these communication settings till later, click OK in the Communication Settings dialog.

You are not required to restart at this time. You are only required to restart when you change the OMF Memory or TCP/IP enabled setting. After you respond to this prompt, the processes will be automatically restarted by PAS and the Communication Settings dialog will close.

Section 18 Information Management Configuring the DBA (ADO) Data Provider for Oracle Data

3BUA000156R4101 223

Configuring the DBA (ADO) Data Provider for Oracle Data

The Information Management installation provides two default ADO data providers. One of these data providers is configured to support Oracle data access for the demonstration displays provided with Display Services (refer to Industrial IT, 800xA - Information Management, Configuration for Display Services). This data provider does not require any further configuration.

The second ADO data provider supports the PDL browser for Batch Management, and Oracle data access via DataDirect, Display Services, and Desktop Trends.

This data provider requires some configuration to make it operational for your site. Specifically you must configure a local Net service name and create an ODBC data source for the Oracle database, and then change the StartUpMode of the ADO data provider. Follow these basic steps and refer to the referenced pages for details:

Figure 109. Communication Settings Dialog

Create an ODBC Data Source for the Oracle Database Section 18 Information Management

224 3BUA000156R4101

• Create an ODBC Data Source for the Oracle Database on page 224• Edit the ADO Data Provider Configuration on page 226

Create an ODBC Data Source for the Oracle DatabaseThis procedure shows you how to install and configure a Microsoft ODBC for Oracle driver for the Information Management Oracle database:

1. From the configuration assistant, select Create ODBC Data Source for the Oracle Database, then click Run Selected Configuration Tool.

This displays the ODBC Data Source Administrator, Figure 110.

2. Click the System DSN tab, then click Add to display the Create New Data Source dialog.

Figure 110. ODBC Data Source Administrator

Section 18 Information Management Create an ODBC Data Source for the Oracle Database

3BUA000156R4101 225

3. In this dialog select the Microsoft ODBC for Oracle driver, Figure 12, then click Finish.

4. Use the setup dialog to set the Data Source Name and Server to localhost, Figure 111

Table 12. Selecting the Microsoft ODBC for Oracle Driver

Figure 111. Specifying Data Source Name and Server

Edit the ADO Data Provider Configuration Section 18 Information Management

226 3BUA000156R4101

5. Click OK when you are finished. This returns you to the System DSN tab on the ODBC Data Source Administrator. Here you’ll see the new driver added to the System Data Source list.

6. Click OK to exit the ODBC Data Source Administrator. Then continue with Edit the ADO Data Provider Configuration on page 226.

Edit the ADO Data Provider ConfigurationThis procedure describes how to change the StartupMode for the ADO data provider from MANUAL to AUTOMATIC. To edit the ADO data provider:

1. From the configuration assistant, select Configure ADO Data Provider, then click Run Selected Configuration Tool. This displays the ABB Data Service Supervision dialog.

2. Click the (+) button next to Supervision to expand the navigation tree and show the available data providers, Figure 112.

If you get a tnsnames.ora error message when you attempt to apply these configuration settings, refer to Verifying Oracle Service Names on page 231.

Figure 112. Opening the ABB Data Services Supervision Configuration Dialog

Click here to expand

Section 18 Information Management Edit the ADO Data Provider Configuration

3BUA000156R4101 227

3. Select the ADO data provider, Figure 113.

4. Click the + symbol next to the ADO data provider to show the data provider attributes. Set the StartupMode for this data provider to AUTOMATIC, Figure 114.

Figure 113. Selecting the Existing ADO Data Provider

The data provider must be stopped to configure its attributes. This is the default state. If the data provider is Started, click the Stop button to stop the data provider.

Figure 114. Changing StartupMode to Automatic

ADO Data Provider

Argument Value

Attribute List Expanded

StartupMode Selected

Edit the ADO Data Provider Configuration Section 18 Information Management

228 3BUA000156R4101

5. Click Save to save the changes.

6. To start the ADO data provider, select it and click Start.

7. Then click Close to exit this dialog.

This concludes the procedure for configuring the ADO data provider for Oracle access.

The ADO-DEMO data provider supports demonstration displays. This data provider may be stopped, and its StartupMode may be changed to MANUAL, if you are not using the demonstration displays.

Section 18 Information Management Troubleshooting Install Errors

3BUA000156R4101 229

Troubleshooting Install Errors

Database Instance Errors

This section describes the error messages that you may encounter while creating a History database instance, and provides guidelines for correcting the error.

Drive Space Configured Incorrectly

If you get the message shown in Figure 115, your current drive space configuration cannot support the tablespace required by your database instance. This may occur even though the total space allocated exceeds the minimum disk space requirement. This is because one or more tablespaces are too large to fit on any of the drives where you have space allocated.

When this occurs, you should first try to change the disk space configuration. If this is not possible, go back to the Instance Sizing dialog, and change one or more log specifications to reduce your disk space requirements.

An example is shown in Figure 116. The minimum disk space required is 25807 MB. The total disk space allocated on the C and D drives appears to exceed this requirement (15373 + 10826 = 26199); however, there is a tablespace requirement that is too large to fit on either drive as it is currently configured. Further, neither drive has sufficient space available that would allow changing the disk space allocation. In this case you must change one or more log specifications to reduce your disk space requirements.

Figure 115. Drive Space Configured Incorrectly Message

Database Instance Errors Section 18 Information Management

230 3BUA000156R4101

Available Diskspace Changes Before You Run the Wizard

If you get the message shown in Figure 117, it is probable that the available disk space changed between the time when you configured it, and the time when you actually tried to run the wizard. For example, you may have unzipped a file that consumed a large amount of disk space. When this occurs you must go back to the wizard, drop the current database instance, and create a new instance.

Figure 116. Example Disk Space Configuration

Figure 117. Available Disk Space Changed Message

Section 18 Information Management Verifying Oracle Service Names

3BUA000156R4101 231

Insufficient Space for Oracle System Files

The drive where you install the Oracle software requires a certain amount of disk space for system files. The message shown in Figure 118 is displayed when the drive where Oracle is installed does not have enough disk space allocated. When this occurs, re-allocate disk space to support the system files on that drive.

Verifying Oracle Service Names

Under normal circumstances, Oracle software is installed after the Information Management Application Server has been added to a domain. Oracle detects that the node belongs to a domain, adds a line with the domain name to the sqlnet.ora file, and appends the domain name to all service names defined in the tnsnames.ora file.

If for some reason Oracle is installed before the node is added to a domain, the domain name will not be entered into the sqlnet.ora file. The HSEH service name (created during Information Management software installation), and the LOCALHOST service name (created as a post installation step) will have the domain name appended. This will create a mismatch between these service names and sqlnet.ora file, and cause these service names to fail.

Figure 118. Insufficient Space For Oracle System Files

Verifying Oracle Service Names Section 18 Information Management

232 3BUA000156R4101

To rectify this condition, enter the domain name in the sqlnet.ora file and update any names in the tnsnames.ora file that do not have the domain name extension:

1. Use Windows Explorer to locate and open the sqlnet.ora file. The path is .../Oracle/ora92/network/admin, Figure 119.

2. Open the sqlnet.ora file with a text editor such as notepad, and add the following line (reference Figure 120):

NAMES.DEFAULT_DOMAIN = domainName

for example:

NAMES.DEFAULT_DOMAIN = pttdomain.us.abb.com

3. Save the file when you are done.

4. Open the tnsnames.ora file with the text editor and add the domain name extension to all service names (reference Figure 121).

Figure 119. Using Windows Explorer to Open Oracle Files

Section 18 Information Management Verifying Oracle Service Names

3BUA000156R4101 233

5. Save the file when you are done.

Figure 120. Editing the sqlnet,ora File

If using a workgroup rather than a domain, do not add the domain name where indicated in Figure 121. Also, the domain following localhost (PTTDOMAIN.US.ABB.COM) in Figure 121 will not appear.

Figure 121. Editing the tnsnames.ora File

Add domain name extension



Information Management Profiles Client Post Installation Section 18 Information Management

234 3BUA000156R4101

Information Management Profiles Client Post InstallationThe Profiles Client application runs independent of the Information Management System Services or 800xA System software and is installed on Windows 2000 or XP. To access the Information Management Server, all profile clients nodes can be in the same domain as the Information Management Server and then no post installation changes are required. However, to access the Information Management Server from a machine outside the domain/workgroup that the Information Management Server is part of, the following steps must be taken (Windows Server 2003 SP1 and Windows XP Professional SP2 have the same dcomcnfg views):

1. Start dcomconfg. Use either Start > Run and enter dcomconfg or navigate to Component Services, Computers through the Control Panel and Administrative Tools.

2. Select My Computer and use the context menu to select and open Properties.

3. Select the COM Security tab.

4. Select the Edit Limits button for Launch and Activation Permissions.

5. Set the Remote Activation Permissions for the Everyone user to Allow and then select OK to as required to close the setup windows.

Once this is set, it is also necessary to create the 800xA service account on the Profiles Client. The service account name can be found on the Domain controller. Make sure the name is the same in case and the passwords are identical.

3BUA000156R4101 235

Appendix A DCOM Settings

This section describes the correct DCOM (and COM+) settings for installed components based on node type.

Table 13 describes the settings for the Asset Optimization Application Server, and Single node system.

Table 14 describes the settings for all other node types. This includes the Single Engineering Node, Domain Controller, Aspect Server, Connectivity Server, Combined Aspect/Connectivity Server, Engineering Workplace, System Workplace, and Terminal (Thin Client) Server.

Table 13. AO Server & Single Node System


DCOM DeviceManagementServer Identity: This User (800xA Service Account)

DCOM ABB Fieldbus OPC-Server DA Identity: This User (800xA Service Account)

DCOM OPC Server FF Identity: This User (800xA Service Account)

COM+ DMSComPlus Identity: This User (800xA Service Account)

Table 14. All Other Node Types


DCOM DeviceManagementServer Identity: This User (800xA Service Account)

DCOM ABB Fieldbus OPC-Server DA Identity: This User (800xA Service Account)

DCOM OPC Server FF Identity: This User (800xA Service Account)

COM+ DMSComPlus Identity: This User (800xA Service Account)

Appendix A DCOM Settings

236 3BUA000156R4101

3BUA000156R4101 237

Numerics800xA for Advant Master 123

Connectivity server configuration 123RTA board network settings 125

800xA for DCI 129Symphony DCI OPC server object 129

800xA for Harmony 133, 135, 136, 137Harmony alarm and event OPC provider 134Harmony network 133SemAPI 138

800xA for MOD 300Add HyperTerminal 151Communications settings 148

800xA for TRIO 111

AABBResults directory share 75About this book 13AC 800M 83

Control Builder configuration 83Downloading AC 800M controller firmware 87OPC server configuration 95Setting IP address 87

Adding additional AO servers 179Adding clients 41Adding connectivity and application servers 39Adding system extensions 31ADO provider 226Advanced templates 195Affinity 46

Configuration 50Load balancing and system performance 49Planning load balancing 47

Alarm and event 167Alarm and event configuration 69AoWebServerNode 177

Application serverAdding 39

Aspect directory 137Aspect directory synchronization for 800xA for

Harmony 137Aspect permissions configuration 182Aspect server

Redundancy 44Redundant 42

Asset Optimization 177Adding additional AO servers 179AoWebServerNode 177AssetMonitoring service provider node 178DMS calibration integration 183SAP/PM Integration 187Web-enabled views 183

Asset optimizationAspect permissions configuration 182

AssetMonitoring service provider node 178

BBatch Management 189

Advanced templates 195Connection with Manufacturing Management

205IE configuration 194Initialize office 195Print BMS report configuration 193Shutdown script 193System service definitions 189Toolbar 195

CCaution icon 14Client

Adding 41

INDEX

Index

238 3BUA000156R4101

Index

238 3BUA000156R4101

Communications settings 148Configuration

Affinity 50Alarm and event for SoftPoint Server 69Aspect permissions for Asset Optimization 182IE for Batch Management 194IE for Manufacturing Management 204OPC server for AC 800M 95Print BMA report for Batch Management 193Scheduler 60SoftPoint Server 63

Configuring redundancy 44Connectivity server

Adding 39Configuration for 800xA for Advant Master

123Redundant 43

Control Builder configuration 83Creating the system 25

DDatabase 200, 213DBA (ADO) data provider 223DCOM settings 115, 119, 235Defining users 58Diagnostics Collection Tool 75

ABBResults directory share 75DMS calibration integration 183Document conventions 15

FFOUNDATION fieldbus device integration

Shared folder for HSE subnet configuration data 37

Specifying common path for fieldbus builder data 38

HHarmony alarm and event OPC provider 134Harmony configuration 135, 136Harmony network 133

HART Device Integration 115DCOM settings 115

HART device integrationShared folder 37

HyperTerminal 151

IIE 137IE configuration 194, 204IE configuration for 800xA for Harmony 137IEC 60870 licensing 171Import Harmony configuration 135, 136Information icon 14Information Management 209

Creating database instance 213DBA (ADO) data provider 223Edit ADO data provider configuration 226Log on settings 212ODBC data source 224Setup 209Starting PAS 222Troubleshooting 229

Initialize Office 195Intended user 14

LLoad balancing 47Load balancing and system performance 49Log on settings for Information Management

services 212

MManufacturing Management

Connection with Batch Management 205Create database 200Create virtual directory 196FrontPage

FrontPage 206IE configuration 204Plant Explorer 204User account 199

Index

3BUA000156R4101 239

NNew installations 13

OOPC server configuration 95OPC server object, Symphony DCI 129Oracle 223, 224

PPAS 222Plant Explorer 204PLC Connect 153

Alarm and event 167Basic setup 153IEC 60870 licensing 171PLC server 175

PLC server 175Post installation sequence 19Print BMA report configuration 193Production Management

Batch Management 189Advanced templates 195Connection with Manufacturing

Management 205IE configuration 194Initialize Office 195Print BMS report configuration 193Shutdown script 193System service definitions 189Toolbar 195

Manufacturing Management 196Connection with Batch Management 205Create database 200Create virtual directory 196FrontPage 206IE configuration 204Plant Explorer 204User account 199

PROFIBUS Device Integration 119DCOM settings 119

PROFIBUS device integrationShared folder 37

RRedundancy 42

Adding aspect servers 44Configuring 44Redundant aspect servers 42Redundant connectivity servers 43Service providers for SoftPoint Server 73

Redundant Connectivity Servers 150Redundant Partner 150Reference documents 16Reverse Time Synchronization Mode 145REVERSED_SYNC_MODE 145RTA board network settings 125

SSAP/PM Integration 187Scheduler

Configuration 60SemAPI 138Setting IP address 87Shared folder for HSE subnet configuration data 37Shared folder for PROFIBUS and HART device

integration 37Shutdown script 193SMS and e-mail Messaging 79

Location of application server 81SoftPoint Server 63

Alarm and event collection 69Configuration 63Redundant service providers 73

Specifying common path for fieldbus builder data 38

Symphony DCI OPC server object 129System checker 24System extensions 31System installer 14System level tasks 25

Index

240 3BUA000156R4101

Index

240 3BUA000156R4101

Adding clients 41Adding connectivity and applications servers

39Adding system extensions 31Affinity 46

Configuration 50Creating the system 25Defining users 58Redundancy 42Shared folder for HSE subnet configuration

data 37Shared folder for PROFIBUS and HART

device integration 37Specifying common path for fieldbus builder

data 38User roles 60Verifying system and servers 45

System service definitions 189

TTime Synchronization 146Tip icon 14Toolbar 195

UUpgrades 13Users

Account for Manufacturing Management 199Defining 58Roles 60

VVerifying system and servers 45Virtual directory 196

WWarning icon 14Web-enabled views on non-Industrial IT systems

183

3BUA000156R4101. Printed in Sweden June 2005Copyright © 2003-2005 by ABB. All Rights Reserved® Registered Trademark of ABB.™ Trademark of ABB.

Automation Technology ProductsMannheim, Germanywww.abb.de/controlsystems

Automation Technology Products Wickliffe, Ohio, USAwww.abb.com/controlsystems

Automation Technology ProductsVästerås, Swedenwww.abb.com/controlsystems

http://www.abb.com

Industrial IT, 800xA - System, Post Installation 800xA... · In no event shall ABB be liable for...

Documents

Transcript of Industrial IT, 800xA - System, Post Installation 800xA... · In no event shall ABB be liable for...