3BSE040587-601 - en Compact HMI 6.0.1 Getting Started

Compact Product Suite
Compact HMI
Getting Started Guide
System Version 6.0.1
Power and productivity

TM
for a better world
Compact Product Suite
Compact HMI
Getting Started Guide
System Version 6.0.1

NOTICE
This document contains information about one or more ABB products and may include a description
of or a reference to one or more standards that may be generally relevant to the ABB products. The
presence of any such description of a standard or reference to a standard is not a representation that
all of the ABB products referenced in this document support all of the features of the described or ref-
erenced standard. In order to determine the specific features supported by a particular ABB product,
the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property
in the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as
a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate
information and data via a secure network. It is the sole responsibility of the system/product owner to
provide and continuously ensure a secure connection between the product and the system network
and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not lim-
ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-
tion of antivirus programs, and so on, to protect the system, its products and networks, against security
breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.
ABB verifies the function of released products and updates. However system/product owners are ulti-
mately responsible to ensure that any system update (including but not limited to code changes, con-
figuration file changes, third-party software updates or patches, hardware change out, and so on) is
compatible with the security measures implemented. The system/product owners must verify that the
system and associated products function as expected in the environment they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any
nature or kind arising from the use of this document, nor shall ABB be liable for incidental or conse-
quential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from
ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-
pose.
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license. This product meets the require-
ments specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2005-2016 by ABB.

All rights reserved.
Release: February 2016

Document number: 3BSE040587-601
Table of Contents
About This User Manual

General ............................................................................................................................11
User Manual Conventions ...............................................................................................12
Warning, Caution, Information, and Tip Icons................................................................12
Terminology.....................................................................................................................13
Released User Manuals and Release Notes.....................................................................15
Section 1 - Compact HMI Overview
Section 2 - Terms and Common Principles

Aspect Objects.................................................................................................................21
Aspects ............................................................................................................................21
Structures .........................................................................................................................23
The Operator Workplace and Plant Explorer Workplace ................................................23
Section 3 - Installation
Supported Standard PLCs................................................................................................27
Overview..........................................................................................................................28
System Functions and Node Types ......................................................................28
Compact HMI Installation Workflow ..............................................................................29
Prepare ................................................................................................................29
Setup ....................................................................................................................30
Configure .............................................................................................................30
Prerequisites ....................................................................................................................30
For Workgroup Environment ...............................................................................30
For Domain Environment.....................................................................................35
3BSE040587-601 5
Table of Contents
Node Preparation Tool ......................................................................................... 37

Installation of Compact HMI Server ............................................................................... 38
System Configuration Console........................................................................................ 41
Configure System................................................................................................. 41
Installation of Compact HMI Client ............................................................................... 49
Configuring Multiple Network Cards ............................................................................. 53
License Installation ......................................................................................................... 55
Compact HMI Upgrade Workflow.................................................................................. 56
Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to 
Compact HMI 6.0 ................................................................................................ 57
Upgrade to 800xA from Compact HMI .......................................................................... 59
Start Up ........................................................................................................................... 60
Connectivity to AC 800M ............................................................................................... 61
Installation and Configuration of OPC Servers for PLCs ............................................... 67
Connection to Third Party Alarm & Event OPC Server...................................... 67
IP Addresses.................................................................................................................... 71
Section 4 - Engineering
Working with Object Types............................................................................................. 73
Creating an Object Type ...................................................................................... 74
Adding Signals to an Object Type ....................................................................... 75
Adding Graphical Elements................................................................................. 77
Adding Faceplates................................................................................................ 79
Adding Alarm and Event Handling ..................................................................... 80
Adding History Logging ...................................................................................... 81
Adding Trend Display.......................................................................................... 82
Creating the Device Object Instances ............................................................................. 83
Creating Instances................................................................................................ 83
Connecting the Instances to Real Signals ............................................................ 86
Building the Functional Structure ................................................................................... 90
Adding Process Displays ..................................................................................... 95
Adding Trends...................................................................................................... 97
Adding Alarm and Event list for a Plant Area................................................... 100
6 3BSE040587-601
Table of Contents
Basic Navigation ................................................................................................101

Adding Shortcuts for Navigation .......................................................................101
Messaging Configuration ..............................................................................................107
SMS Messaging Configuration ..........................................................................107
e-Mail Messaging Configuration .......................................................................109
Audit Trail .....................................................................................................................110
Security Configuration ..................................................................................................111
Import/Export of Application from Compact HMI .......................................................111
Export of Controller Communication Application from Compact HMI ...........111
Import of Controller Communication Application to Compact HMI ................112
Hardware and Software Supervision .............................................................................113
Section 5 - Operation
Workplace Layout and Tools .........................................................................................115
Tabbed Menu......................................................................................................117
Application Bar ..................................................................................................117
Panel Area ..........................................................................................................118
Display Bar.........................................................................................................119
Tool Bar..............................................................................................................120
Status Bar ...........................................................................................................121
Navigation .....................................................................................................................122
General ...............................................................................................................122
Recommended Tools for Navigation..................................................................122
Faceplate Usage.............................................................................................................128
Trends ............................................................................................................................131
Trend Usage .......................................................................................................131
Alarm and Event Usage.................................................................................................133
Section 6 - Administration
Allocating the Functions to the System and the Nodes .................................................139
Deploying Individual or All Nodes in a System............................................................139
Expanding an Existing System ......................................................................................140
Excluding a Node ..........................................................................................................141
3BSE040587-601 7
Table of Contents
Replacing a Node .......................................................................................................... 141

Adding and/or Removing a Node.................................................................................. 142
Importing and Exporting of Configurations.................................................................. 142
Excluding a Node before Deploy .................................................................................. 143
Excluding a Node during Deploy.................................................................................. 143
Adding New Users ........................................................................................................ 144
Backup and Restore....................................................................................................... 146
Backup and Restore of Configuration Data ....................................................... 146
Store Controller Application in the System ....................................................... 148
Other Maintenance ........................................................................................................ 149
To Stop and Start the System ............................................................................. 149
Autonomous Redundancy Setup........................................................................ 152
Change the Windows Computer Name in the Server Node............................... 152
Change the Windows Computer Name in the Client Node ............................... 159
Connect and Disconnect Client Nodes .............................................................. 159
Defragmentation ................................................................................................ 161
Virus................................................................................................................... 161
Windows Update................................................................................................ 162
Save of OPC IP Address for PLC Connect........................................................ 162
Using Virus Protection with Compact HMI ...................................................... 162
Section 7 - Using the PLC Device Library

Creating PLC Device Library Instances........................................................................ 185
Creating the Display...................................................................................................... 192
Windows Operating System .......................................................................................... 197
Selecting the Windows Operating System......................................................... 197
Considerations for Disks and File System ......................................................... 198
Windows Installation Guidelines ....................................................................... 200
Windows Operating System Updates................................................................. 201
Configuring Network Adapters ..................................................................................... 201
Configuring Domain Controller and DNS Server......................................................... 204
Adding Nodes to a Domain ............................................................................... 210
Configuring Users and Groups...................................................................................... 211
8 3BSE040587-601
Table of Contents
New Organizational Unit....................................................................................215

Groups ................................................................................................................215
Users, Groups, and Rights Assignments ............................................................216
800xA Service User ...........................................................................................218
Other Users.........................................................................................................221
Adding 800xA Domain Users to the Local Administrator Group .....................221
Operating System Setup Use with Compact HMI.........................................................223
Regional and Language Options ........................................................................223
Enable Write Caching on Hard Disks ................................................................224
Internet Explorer Enhanced Security .................................................................225
Internet Security Settings for Digital Signature Validation................................226
Disable Web Browser Popup Blocker ................................................................226
Disable Show Window Contents While Dragging .............................................226
Energy Saver and Screen Saver Configuration ..................................................227
Virus Scanning Configuration During Installation and Post Installation...........227
Windows Update Configuration.........................................................................227
Enable the Change Sharing Options for Different Network Profiles .................228
Disable Server Manager Startup ........................................................................228
Disable ISATAP Setting .....................................................................................228
Group Policy Management.................................................................................229
Remote (Thin) Client for the Server Operating System.....................................232
Other Third Party Software ...........................................................................................233
Microsoft Office Professional ............................................................................233
Microsoft Word ..................................................................................................234
Microsoft Excel ..................................................................................................235
Crystal Reports...................................................................................................236
Autocad Integration............................................................................................237
McAfee Integration ............................................................................................237
Symantec ...........................................................................................................237
Bulk SPL Template ............................................................................................238
Backup Software ................................................................................................238
Index
3BSE040587-601 9
Table of Contents
Revision History
Introduction ................................................................................................................... 243
Revision History............................................................................................................ 243
10 3BSE040587-601
About This User Manual
General
Any security measures described in this User Manual, for example, for user
access, password security, network security, firewalls, virus protection, etc.,
represent possible steps that a user of Compact HMI 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 Compact HMI System.
This User Manual describes the Compact HMI product, System Version 6.0.1. The
Compact HMI product helps the user to operate, configure and administrate a plant.
The Compact HMI is based on 800xA SV 6.0.1, which provides an HMI with easy
installation, configuration and operation suited for connection to PLCs.
For more information on the 800xA Base System, refer to the instructions available
in Reference Documentation or User Documentation in ABB Start Menu >
ABB Industrial IT 800xA > 800xA Documentation.
The following users are recommended to use this document:
• Process operators with experience of process control systems or PLC products.
• System engineers with experience of installation, configuration and set-up of
process control systems or PLC products.
• System administrators with experience of process control systems or PLC
products and Microsoft® Windows® operating systems.
3BSE040587-601 11
User Manual Conventions About This User Manual
User Manual Conventions

Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.
Warning, Caution, Information, and Tip Icons

This User Manual includes Warning, Caution, and Information where appropriate to
point out safety related or other important information. It also includes Tip to point
out useful hints to the reader. The corresponding symbols should be interpreted as
follows:
Electrical warning icon indicates the presence of a hazard that could result in
electrical shock.
Warning icon indicates the presence of a hazard that 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 that could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.
12 3BSE040587-601
About This User Manual Terminology
Terminology
A complete and comprehensive list of terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms. Terms that uniquely
apply to this User Manual are listed in the following table.
Term Description
ActiveX Microsoft standard for user interface components, based
on definition of software interfaces.
AS Aspect Server. The “central” intelligence in the system,
including the aspect directory and other services related
to object management, names, security, etc.
Aspect See Aspects on page 21
Aspect Objects See Aspect Objects on page 21
BDM Bulk Data Manager
CEXbus Communication module expansion bus used in the AC
800M Controller.
CNCP Control Network Clock Synchronization Protocol
COM (Microsoft) Component Object Model
CS Connectivity Servers provide access to controllers and
other data sources.
CTK Configuration Tool Kit
DCS Distributed Control System. A generic term for control
systems for Process Automation, normally with a
distributed database and real time data access.
DCU Distributed Control Unit
3BSE040587-601 13
Terminology About This User Manual
Term Description
DTM The Device Type Manager - DTM - is a software module
delivered by the manufacturer together with a device. As
an “FDT device driver” the DTM contains all device-
specific data, functions, and graphical user interfaces
and provides uniform access to these device-specific
internals via the standardized FDT interfaces.
ECCP Ethernet Communications Controller for the PCI bus
EPA Environmental Protection Agency
ERP Enterprise Resource Planning
ES Engineering System, which is used for engineering and
potential test of applications intended for Production
System.
FDT Field Device Tool. It is an open standardized
communication interface for integrating field devices and
their application into control systems or device
management tools, e.g. Engineering Tools and Asset
Management Tools.
FF FOUNDATION Fieldbus
GSM Global System for Mobile communication
HSE High Speed Ethernet (FOUNDATION Fieldbus)
HSI Human System Interface
HMI Human Machine Interface
MES Manufacturing Execution System
Node A computer communicating on a network, e.g. the
Internet, Plant, Control or I/O network. Each node
typically has a unique node address with a format
depending on the network to which it is connected.
ODBC Open Data Base Connectivity
OCS Open Control System. Similar meaning as DCS
14 3BSE040587-601
About This User Manual Released User Manuals and Release Notes
Term Description
OLE Object Linking and Embedding
OPC OLE for Process Control, a standard interface for data,
event and history access based on COM.
PCA Process Control Aspect
Plant Explorer An application that is used to create, delete and organize
Aspect Objects and Aspects in the 
Compact HMI. The plant explorer organizes the Aspect
Objects in structures according to functionality, location,
etc. You can also use it to browse and search the
structures of the plant.
PLC Programmable Logic Controller. Controller for primarily
discrete logic control.
PNSM PC, Network and Software Monitoring
PS Production System which is used for controlling a real
process.
RNRP Redundant Network Routing Protocol
SIL Safety Integrity Level
SIS Safety Instrumented System
SMS Short Messaging Service
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SOE Sequence of Events
Released User Manuals and Release Notes

A complete list of all User Manuals and Release Notes applicable to System 800xA
is provided in System 800xA Released User Manuals and Release Notes
(3BUA000263*).
3BSE040587-601 15
Released User Manuals and Release Notes About This User Manual
System 800xA Released User Manuals and Release Notes (3BUA000263*) is

updated each time a document is updated or a new document is released. It is in .pdf
format and is provided in the following ways:
• Included on the documentation media provided with the system and published
to ABB SolutionsBank when released as part of a major or minor release,
Service Pack, Feature Pack, or System Revision.
• Published to ABB SolutionsBank when a User Manual or Release Note is
updated in between any of the release cycles listed in the first bullet.
A product bulletin is published each time System 800xA Released User Manuals
and Release Notes (3BUA000263*) is updated and published to ABB
SolutionsBank.
Table 1. Related Documentation
Category Title Description

System System, Post Installation Contains post installation
Administration Setup procedures.
System, Administration and Contains instructions about how
Security to administrate and set security in
the system.
16 3BSE040587-601
About This User Manual Released User Manuals and Release Notes
Category Title Description

Software System, Extended Operation Describes operation of the
Operator Workplace.
System, Operator Workplace Describes configuration of the
Configuration Operator Workplace and Plant
Explorer.
Engineering, Graphics This instruction describes how to
use Graphics.
IndustrialIT PLC Operation Describes operation details of
PLC Connect.
IndustrialIT PLC Configuration Describes configuration details of
PLC Connect.
Other System, Automation System Describes configuration details.
Network, Design and
Configuration
3BSE040587-601 17
Released User Manuals and Release Notes About This User Manual
18 3BSE040587-601
Section 1 Compact HMI Overview
The IndustrialIT Compact HMI is designed to be an HMI to any kind of automation

solution. It interfaces with AC 800M and other PLCs found in the market. It is based
on the IndustrialIT Base standard system. A Compact HMI system consists of one
server and up to nine additional client nodes.
The server can be used for both engineering and operation, the Operational and
800xA Smart Client Thin clients are used only as operator workplaces.
Figure 1. System Overview
The IndustrialIT Compact HMI supports 800xA Smart Client by sharing the
Compact HMI800 Graphics.
3BSE040587-601 19
Section 1 Compact HMI Overview
20 3BSE040587-601
Section 2 Terms and Common Principles
This section describes the terms and principles used in the Compact HMI system.
For more information, refer to System 800xA, Operations, Operator Workplace
Configuration (3BSE030322*) and System 800xA, Operations (3BSE036904*).
Aspect Objects
A plant consists of real entities, such as pipes, tanks, valves, and motors. In the
Aspect Object solution these entities or objects are modeled in the control system. A
modeled object is called an Aspect Object. This can be a simple lowest level object
or can contain other objects. Objects containing other objects are called composite
objects. The Aspect Object system can also handle computer related objects (for
example, user object, node object, and workplace object) similar to real entity
objects.
Aspects
There are a number of different types of information connected to each object.
These types of information are called Aspects in the Aspect Object solution. For
example a valve may have a mechanical drawing, a faceplate (for control purposes),
a graphical representation in a graphical display and so on. Aspect Objects have a
number of default aspects, for example, the Name aspect.
Aspect Objects are visualized with different tools, like Process Graphics, alarm lists,
and Plant Explorer. Right-click an aspect object to display a context menu. This
context menu contains a list of aspects from which a desired aspect can be selected.
Depending on the aspect and the environment, the information will be presented
using the appropriate tool.
3BSE040587-601 21
Aspects Section 2 Terms and Common Principles
Aspect View
A view is a visual representation of an aspect on the screen. Some aspects have
more than one view. For example, a Faceplate aspect can have three views.
Figure 2 shows how the concepts fit together. The physical valve is modeled and
represented in a graphical display. This valve that is now an Aspect Object, has a
number of Aspects, of which four are presented here. Each aspect has at least one
view.
Figure 2. Aspects with Aspect Views
22 3BSE040587-601
Section 2 Terms and Common Principles Structures
Structures
The Aspect ObjectTM concept allows organization of objects and aspects into
different structures, depending on which context is to be viewed.
Structures are the graphical representations of the relations that exist between
different aspect objects. An aspect object can be part of more than one structure
because there exist different types of relation between the objects.
The Plant Explorer includes different structures representing the same plant.
Structures can be built and improved at any time. Examples of the most common
structures are Object Type Structure, Control Structure and Functional Structure.
The Operator Workplace and Plant Explorer Workplace

The Operator Workplace
The Operator Workplace is the environment from which the operator views and
controls the process in the plant. Login as an Operator to start the Operator
Workplace.
The configuration of the workplace is done by the Application Engineer and
intended as a starting point for an Operator controlling the plant.
In Compact HMI, a number of different types of displays are available. The most
important are process displays for supervision, faceplates to control real process
objects, trend displays and alarm displays to monitor process anomalies. These
displays are presented in the Display Area (see Figure 3 below) and may appear as
base displays or overlap displays.
Base displays cover the entire display area while one or more overlap displays cover
a smaller portion of the display area (and the base display).
At the top and the bottom of the Operator Workplace there are tool bars to control
the system and the process.
3BSE040587-601 23
The Operator Workplace and Plant Explorer Workplace Section 2 Terms and Common Principles
These areas contain important information and are never covered by displays. The
tools in these toolbars represented by icons are used to interact with the process and
the Compact HMI.
Figure 3. The Operator Workplace Window
Plant Explorer Workplace

The Plant Explorer is the main tool for exploring and building hierarchically
structured models of a plant or a system. It is also used to create and configure the
objects and aspects of these structures. The information about the plant is stored in a
single place, which means that information only has to be entered once.
The Plant Explorer Workplace is recommended for application engineers to
configure an Operator Workplace.
24 3BSE040587-601
Section 2 Terms and Common Principles The Operator Workplace and Plant Explorer Workplace
General User Interface

Compact HMI workplaces use the window system provided by Microsoft Windows.
They are designed so as to retain a familiar environment. Plant Explorer works in a
similar way as Windows Explorer for the following functions:
• Cut, paste, copy
• Shortcut tools
• Drag-and-drop operations within and between the Workplace panes.
• Context menu (through a right-click operation).
The Plant Explorer Workplace Window

The Plant Explorer Workplace window is the tool used to work with aspect objects,
aspects and structures.
3BSE040587-601 25
The Operator Workplace and Plant Explorer Workplace Section 2 Terms and Common Principles
Figure 4 shows an example of the Plant Explorer window.
Figure 4. The Plant Explorer Workplace Window
For more information on the Plant Explorer, refer to System 800xA, Operations,
Operator Workplace Configuration (3BSE030322*).
26 3BSE040587-601
Section 3 Installation
Compact HMI, System Version 6.0.1 is delivered as a software installation DVD.

The delivery includes a product box including Compact HMI DVD and the Getting
Started manual. A license file can be downloaded from ABB software factory after
purchase of the product license and registration. To get started a time limited license
is included in the installation kit.
Supported Standard PLCs

All PLCs or field devices that are compliant to the following communication
standards are supported; OPC, Modbus RTU, Modbus TCP, SattBus and Comli.
The Compact HMI supports connections to PLCs through OPC. OPC servers are
installed on the server node. OPC servers which requires specific communication
hardware and through serial communication channels needs to be installed together
with the hardware on the server node.
The amount of PLC that can be connected is based on the system load. There is no
hard limit in the system in the number of PLC that can be connected. The limit on
the communication is set to the number of signals communicated to/from the PLCs,
this limit is set by the purchased license.
3BSE040587-601 27
Overview Section 3 Installation
Before proceeding with this chapter, make sure that all prerequisites required to
configure an Compact HMI System are completed, refer Appendix A,
Prerequisites.
Overview
Compact HMI installation includes the following:
• Centralized and automated software installation and configuration
• System deployment
The Compact HMI 6.0.1 is installed with minimal user interaction. It automates the
installation and configuration (adding of System Functions and allocating functions
to nodes) of an existing Compact HMI System. The configuration of all nodes in the
system can be done from one place, except for the preparation of nodes which is
done at each node.
System Functions and Node Types

System Functions define the capability of the System. Functions allocated to the
nodes describe the intended functional behavior and use of a node. The selection of
the System Functions determines the functions available for allocation and deploy
of the nodes.
The Node Types determine the main use of a Compact HMI system node as a:
• Server
• Client
28 3BSE040587-601
Section 3 Installation Compact HMI Installation Workflow
Compact HMI Installation Workflow

The Compact HMI installation is carried out in three phases as shown in Figure 5 :
Figure 5. Compact HMI Installation Workflow
Prepare
The main purpose of this phase is to configure a node to be a Compact HMI node.
Use the System 800xA 6.0 System Guide Technical Data and Configuration
(3BSE041434*), and System 800xA 6.0 System Planning (3BSE041389*)
documents to plan the hardware and software requirements for a Compact Node. A
node must comply with the hardware and Operating System requirements to be
configured as an Compact HMI.
The following tasks are carried out in the prepare phase:
1. Selecting, and installing the Windows Operating System
2. Configuring Network Adapters
3. Configuring Domain Controller and DNS Server
4. Configuring Users and Groups
5. Setting up the Other Third Party Software
6. Preparing the node using the Node Preparation Tool
These procedures remain the same for any node selected to be configured as a
Compact HMI.
See the Industrial IT Certification home page for a complete and up to date list of
certified computers: http://www.abb.com/product/us/9AAC171278.aspx
Note that the certification itself is performed towards one or more specific
versions of Compact HMI.
3BSE040587-601 29
Setup Section 3 Installation
Setup
Select from the list of System Functions applicable to the system and the Node
Functions intended to run on the individual nodes to setup the system.
Deploying the System installs the Compact HMI software on all the nodes in a
centralized approach where the overall progress is indicated on Compact HMI
Server. The system configuration information including system functions, nodes
and associated node functions, node function properties and so on are stored in the
Aspect Directory. This enables and ensures smooth updates and upgrades of the
installed system.
Do not install Compact HMI software product manually. This will cause
inconsistencies in the information stored in the aspect directory which will lead to
unforeseen consequences in future maintenance of the system.
Configure
Most of the post installation configuration of the system and node functions is done
before the system is deployed. However, there are post installation configuration
steps that are not automated. Refer the System 800xA 6.0 Post Installation
(2PAA111693*) manual along with the product specific configuration manuals to
carry out the configurations.
Refer the Product Specific configuration manual for specific configurations related
to specific functions and features.This phase deals with configuring the 800xA Base
System and Functional Areas.
The system is now ready for application engineering.
Prerequisites
For Workgroup Environment
Following are the system setup that has to be done on Workgroup Environment
before starting Compact HMI 6.0.1 installation:
1. Right click on My Computer and click Manage. The Computer
Management window appears.
Computer management can only be done if the logged on user have

administrative privileges.
30 3BSE040587-601
Section 3 Installation For Workgroup Environment
2. Select Users under Computer Management (Local) > System Tools > Local
Users and Groups. All the users of the computer will be listed on the right side
as shown in Figure 6.
Figure 6. Computer Management Window
3. Right click on the window and click New User… to create a new user
SwServiceAccount.
3BSE040587-601 31
For Workgroup Environment Section 3 Installation
4. Fill in the required details such as User Name, Password as shown in Figure 7.
Figure 7. Creating a New User
5. Click Create and Close the window. The SwServiceAccount will appear in the
user list as shown in Figure 8.
Figure 8. User List
32 3BSE040587-601
Section 3 Installation For Workgroup Environment
6. Select Groups under Computer Management (Local) > System Tools >
Local Users and Groups. All the user groups of the computer will be shown
on the right side.
7. Right click and select New Group… to create a new group IndustrialITUser.
See Figure 9.
Figure 9. Adding New Group
8. Similar way, create a new group IndustrialITAdmin.

9. Add SwServiceAccount user to the following groups:
– IndustrialITAdmin
– IndustrialITUser
– Administrators
Follow the steps to add the user to the groups:
a. Double click on SwServiceAccount in Users under Computer
Management (Local) > System Tools > Local Users and Groups. The
SwServiceAccount Properties window appears.
b. Go to Member Of tab in SwServiceAccount Properties window.
c. Click Add… to add SwServiceAccount user as a member of a group.
3BSE040587-601 33
For Workgroup Environment Section 3 Installation
d. In Select Groups window, write the name of the Group and click OK. See
Figure 10.
Figure 10. Adding SwServiceAccount as a Member
34 3BSE040587-601
Section 3 Installation For Domain Environment
e. Similarly, add IndustrialITUser and Administrators. All the three group

name should appear in the Member Of tab of the SwServiceAccount
Properties window. See Figure 11. Click OK.
Figure 11. User Properties Window
10. Log out from the current user and log in as SwServiceAccount.
It is required to reset the password while logging in for the first time in a user
account.
For Domain Environment

Following are the system setup that has to be done on Domain Environment before
starting Compact HMI 6.0.1 installation:
1. Go to Search functionality then type dsa.msc and click OK to open Active
Directory Users and Computers.
3BSE040587-601 35
For Domain Environment Section 3 Installation
2. Add a new user SwServiceAccount as shown in Figure 12.
Figure 12. Adding New User
36 3BSE040587-601
Section 3 Installation Node Preparation Tool
3. Create two groups in Active Directory Users and Computers,

IndustrialITAdmin and IndustrialITUser. See Figure 13.
Figure 13. Creating Groups
4. Add SwServiceAccount in the following groups:

– IndustrialITAdmin
– IndustrialITUser
– Domain Admins
5. Log out from the current user and log in as SwServiceAccount user.
Node Preparation Tool

The Node Preparation Tool (NPT) copies the installation files to the local drive on
the computer and installs the 800xA Base Software. Thus preparing the node for
deployment of Compact HMI.
3BSE040587-601 37
Installation of Compact HMI Server Section 3 Installation
Installation of Compact HMI Server

Follow the steps below to install Compact HMI 6.0.1 Server:
1. Double click on Setup.exe file located in Compact HMI 6.0.1 media. A User
Account Control confirmation message appears.
2. Click Yes. The 800xA System Setup window appears.
Click on the Install Adobe Reader in NPT to install the Adobe PDF reader.
38 3BSE040587-601
Section 3 Installation Installation of Compact HMI Server
3. Enter the Password in the respective field. See Figure 14.
Figure 14. 800xA System Setup Window
4. Accept the License Agreement by selecting the checkbox.

5. Click on Node Options.
3BSE040587-601 39
Installation of Compact HMI Server Section 3 Installation
6. In the Node Options window, select Compact HMI Server Node checkbox
and click OK. See Figure 15.
Figure 15. Node Options Window
7. Click Start node preparation in the 800xA System Setup window. The
preparation process starts. A progress bar shows the progress of the
preparation.
40 3BSE040587-601
Section 3 Installation System Configuration Console
8. On successful completion, click Close on the System 800xA Installation

Progress window. See Figure 16.
Figure 16. Preparation Progress Window
The system reboots when the Compact HMI 6.0.1 preparation is complete. Wait
until all the core products are prepared.
System Configuration Console

Configure System
It helps with the configuration and installation of the system functions and the
functions allocated to the nodes by:
Follow the steps below to configure the system using System Configuration
Console:
1. Run ABB Start Menu shortcut from the desktop.
3BSE040587-601 41
Configure System Section 3 Installation
2. Select System configuration Console from the ABB Start Menu. See
Figure 17.
Figure 17. ABB Start Menu
3. Click Yes on the confirmation message box shown in Figure 18. The System
800xA Configuration Console window appears as shown in Figure 19.
Figure 18. Confirmation Message
42 3BSE040587-601
Section 3 Installation Configure System
Figure 19. System 800xA Configuration Console
3BSE040587-601 43
4. Go to System Setup > Configure System on System 800xA Configuration

Console window. All the System Functions will be displayed with their
property and status. See Figure 20.
Figure 20. Selecting the System Functions
5. Wait till all the functions are deployed.

6. Go to System nodes tab and select Allocate functions…
The Allocate application and service functions window appears. See
Figure 21.
44 3BSE040587-601
Figure 21. Allocate Application and Service Functions(To be updated)
7. Select the following check boxes in Allocate application and service

functions window and click OK:
– Application Scheduler Services
– Basic History Services
– Calculations Services
– SMS and E-Mail Messaging Service
– SoftPoint Servies
– PLC Connect Services
3BSE040587-601 45
8. All the selected functions will be displayed in the System nodes tab with their
Property and Installation status. See Figure 22. Click Deploy system.. to
deploy all the functions.
Figure 22. System Node Functions
46 3BSE040587-601
9. The Deploy window shows the summary of the deploy. It will show the nodes
affected by the deploy and the status. Click Deploy to start the deploy. See
Figure 23.
Figure 23. Deploy
3BSE040587-601 47
10. The deploy progress bar will turn into green color once the deploy is
completed. See Figure 24. Click Close once all the nodes are deployed.
Figure 24. Deploy Complete
48 3BSE040587-601
Section 3 Installation Installation of Compact HMI Client
Installation of Compact HMI Client

Follow the steps below to install Compact HMI 6.0.1 Client:
1. Double click on Setup.exe file located in Compact HMI 6.0.1 media. A User
Account Control confirmation message appears.
2. Click Yes. The 800xA System Setup window appears.
3. Enter the details such as Service account name and Password in their respective
fields. See Figure 25.
Figure 25. 800xA System Setup Window
3BSE040587-601 49
Installation of Compact HMI Client Section 3 Installation
4. Accept the License Agreement by clicking on the checkbox.

5. Click on Node Options.
6. In the Node Options window, select Compact HMI Client Node checkbox
and click OK. See Figure 26.
Figure 26. Compact HMI Client Installation
7. Click Start node preparation in the 800xA System Setup window. The
installation process starts. A progress bar shows the progress of the installation.
50 3BSE040587-601
Section 3 Installation Installation of Compact HMI Client
8. On successful completion, click Close on the System 800xA Installation

Progress window. See Figure 27.
Figure 27. Installation Progress Window
9. Open System Configuration Console on Compact HMI Server node.
3BSE040587-601 51
Installation of Compact HMI Client Section 3 Installation
10. Go to System nodes tab and click Add node… in System 800xA
Configuration Console window. See Figure 28. The Add node window
appears.
Figure 28. Adding a Node
11. In Add node window, enter the hostname. In Node Types, select Client and
click OK. See Figure 29.
Figure 29. Add Node Window
52 3BSE040587-601
Section 3 Installation Configuring Multiple Network Cards
12. Click Deploy system.. in System 800xA Configuration Console window. The
Deploy window appears.
13. Click Deploy to start the deploy. See Figure 30.
Figure 30. Deploy Window
14. The deploy progress bar will turn into green color once the deploy is
completed. Click Close once all the nodes are deployed.
Configuring Multiple Network Cards

It is possible to configure a redundant network in Compact HMI 6.0.1. When there
is a problem in the primary network, the secondary network takes over the primary
network and thus avoid any communication loss. To configure multiple network
cards, follow the steps below:
1. Open System 800xA Configuration Console in Compact HMI Server node.
3BSE040587-601 53
Configuring Multiple Network Cards Section 3 Installation
2. Go to Network > Configure System Network. The Configure System

Network page opens. See Figure 26.
Figure 31. Configuring Multiple Networks
3. Select the Network filtering (Recommended) check box.

4. Enter the number of network areas.
5. In Client/server network areas, enter Primary network address and
Secondary network address.
6. Click Apply to complete the configuration.
54 3BSE040587-601
Section 3 Installation License Installation
License Installation
After purchasing a Compact HMI license the license is downloaded from the ABB
Software Factory (SOFA) or delivered from a sales representative. The download
requires a registration prior to the download. The license is installed in the system
by following the following steps:
1. Log in as SysAdmin.
2. Open the License entry application available in ABB Start Menu > ABB
Industrial IT 800xA > System > Licensing.
Figure 32. ABB Start Menu
3. Select File > Load/Replace Licenses.

4. Browse to the license and click Open.
5. Select Yes to replace existing license.
6. Close the license Entry application. The new license is now ready to be used.
3BSE040587-601 55
Compact HMI Upgrade Workflow Section 3 Installation
Compact HMI Upgrade Workflow

An upgrade to Compact HMI 6.0.1 can be executed by using the System Installer
function in Compact HMI 6.0.1. Figure 33 shows the Overview of the Upgrade.
Figure 33. Upgrading Compact HMI - Overview
To upgrade to Compact HMI 6.0.1:

1. Plan the system upgrade taking into consideration the:
– PC Hardware Compatibility
– Third party software requirements
– Ensure time synchronization for all the nodes on the system
2. Prepare the system being upgraded to include:
– Carry out product wise pre-upgrade procedures
– Identify the Node and System Functions
– Complete the Compact HMI Maintenance backup
– Move the files to a safe location
3. Prepare and deploy the software based on the upgrade strategy (Online/Offline)
selected.
4. Configure the system and node functions based on product- wise post-upgrade
procedures
Refer the Considerations and Upgrade Flow included in the System 800xA 5.1 to
6.0. Upgrade (2PAA111694*) and System 800xA 5.1 FP4 RevD to 6.0 Upgrade
(2PAA111695*) manuals for more information.
56 3BSE040587-601
Section 3 Installation Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to Compact HMI 6.0
Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to 

Compact HMI 6.0
To upgrade Compact HMI client, install Windows 8.1 or Windows Server 2012 R2
on the target machine(s) and install Compact HMI as described in Installation of
Compact HMI Server.
To upgrade Compact HMI server, execute the following steps:
1. Create a backup from the Compact HMI 5.1 FP4 system and store it on an
external media (not on the system disk on your PC).
2. Install Windows 8.1 or Windows Server 2012 R2 on the target PC.
3. To start the installation, insert the Compact HMI 6.0.1 DVD in the target PC. If
Autorun is enabled, the program will start automatically. Otherwise, in the File
Explorer, browse to the root of DVD and double-click Setup.exe.
4. Click Install Compact HMI 800 to start the installation. for more information
refer to section Installation of Compact HMI Server.
5. Navigate to ABB Start Menu> ABB Industrial IT 800xA > System >
Configuration Wizard.
Visual Basic Process Graphics (VBPG) is not supported in Compact HMI 6.0.1.
VBPG based graphics needs to be replaced by Process Graphics 2 displays before
moving applications to Compact HMI 6.0.1.
3BSE040587-601 57
Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to Compact HMI 6.0 Section 3 Installation
6. Select the Restore System.
Figure 34. Configuration Wizard screen
7. click on Next.
58 3BSE040587-601
Section 3 Installation Upgrade to 800xA from Compact HMI
8. Click on Select Path, then click add and browse for the backup folder.
Figure 35. Customize Server Settings
9. Click Next whenever it prompts and click Finish.
Upgrade to 800xA from Compact HMI

The Compact HMI can easily be upgraded to an 800xA system. The upgrade is done
by exchanging the license file to an 800xA license file. Contact the local sales
representative to purchase an 800xA license file. To start using additional 800xA
functions the additional software needs to be installed.
Execute the following steps to upgrade Compact HMI to an 800xA system.
1. Purchase and download the registered 800xA license.
2. Download the 800xA license and install it in the system using the License
Entry application available below ABB Start Menu > ABB Industrial IT
800xA > System > Licensing.
3. Get the 800xA install DVDs and Install and load the additional extensions
needed
3BSE040587-601 59
Start Up Section 3 Installation
4. The 800xA System is now ready to be used.
Connectivity to AC 800M
If AC 800M controllers are used, the Compact HMI is ready to be connected to
the AC 800M controller after installation. The OPC server is installed with the
Compact HMI software install and the Compact HMI is configured accordingly.
The following figure describes how to connect to the AC 800M controller.
Power Cord
Control Network Serial Communi- Tool port, to get log files

cation, like Comli to hyperterminal or to
or Modbus set the IP address
Start Up
After installing the hardware, the system is started as follows:
• Power up network switches and other communication equipment.
• Power up the server node.
• Power up the clients.
• Power up PLCs and other equipment.
60 3BSE040587-601
Section 3 Installation Connectivity to AC 800M
After the system start up, a welcome screen appears for the log in. The normal login
name for application engineering is AppEng (Application Engineer) use this to start
the engineering of the system.
Connectivity to AC 800M
The Compact HMI uses PLC Connect to connect to all PLCs and Controllers.
PLC Connect can be used to connect AC 800M/C controllers versions 3.0- using the
corresponding Control IT OPC Server 3.0-. PLC Connect can also be used to
directly connect AC 800M 2.0/2.1/2.2/3.0/3.1/3.2 and AC800C 2.2/3.2 versions,
using any of the following protocols with PLC Connect acting as master and AC
800M/C as slave:
• Serial connection and the Comli protocol (Limited Comli).
• SattBus on TCP/IP (Ethernet).
Connecting to AC 800M Alarm and event OPC server

If the Alarm and Event OPC server for AC 800M controllers should be used, the
related event collector service needs to be created by following these steps:
1. Log in as SwServiceAccount.
2. Start the AC 800M OPC server, and connect it to a controller with a
downloaded application (as described in the AC 800M OPC manual accessible
below help in the OPC server application).
3BSE040587-601 61
Connectivity to AC 800M Section 3 Installation
3. Browse to the event collector service, right-click and create a new object. In the
dialog give the Service group a name e.g. “AC 800M OPC Collector” and click
Create as shown below in the Figure 36.
Figure 36. Event Collector creation
62 3BSE040587-601
4. Right-click on the created object and select create object, select Service
Provider, give it a name as shown below (e.g. Collector HMI_Server).
Figure 37. Collector Service creation
3BSE040587-601 63
5. Now the service needs to be allocated to the node where it should run. This is
done by selecting the service provider aspect and select the CHMI_Server node
in the Node drop-down list as shown below. Click Apply.
Figure 38. Node selection
64 3BSE040587-601
6. In the created Service Group object (the parent in the structure) double-click
the Service Group Definition aspect. Configure it as shown below and click
Apply.
Figure 39. Special Configuration
3BSE040587-601 65
7. Expand the window to see the bottom part and click Upload as shown below.
Figure 40. Service Group OPC AE Upload
8. When the upload has finished the connection is ready to be used.
66 3BSE040587-601
Section 3 Installation Installation and Configuration of OPC Servers for PLCs
Installation and Configuration of OPC Servers for PLCs

Compact HMI can interface to standard PLCs. The connection is done using a
specific communication driver, or via an OPC server for the PLC. To connect one or
more PLCs via an OPC server follow the description below.
Install the OPC server for the PLC. The OPC server shall be installed as a Windows
service if possible. Below is a typical workflow how to install and set up an OPC
server to correctly interface the Compact HMI software.
2. Install the OPC server.
3. If the server is prepared to be a Windows service, it shall be configured to run
on an account SwServiceAccount.
4. Open the Plant Explorer and go to the Control Structure.
5. Select the OPC server object. See Working with Object Types.
6. Create a new object of the PLC Controller type. Name it to recognize the OPC
server. (For example ABB_OPC_server_1 etc.)
7. Select the protocol to be PLC OPC client.
8. Click Edit Driver.
9. If the OPC server is located in another node than the Compact HMI server, fill
in the server node name.
10. Select the OPC server in the OPC server drop-down list.
11. Click OK and then Create.
The OPC server is now installed.
Connection to Third Party Alarm & Event OPC Server

Use the OPC AE client function of Compact HMI to receive time tagged alarms
from the controller into the Compact HMI alarm list.
To associate an alarm collected from a 3rd party AE OPC server with an aspect
object create an OPC Source Name aspect, or an Aspect Name aspect on the Object.
3BSE040587-601 67
Connection to Third Party Alarm & Event OPC Server Section 3 Installation
This aspect is normally added to the PLC signal object. Put the same name in this
aspect as the name defined as the object name in the controller generating the alarm.
The Name property in the OPC Source Name should be the same as in the OPC
AE server. Do not select the Is an Event and Is an Alarm check boxes in Alarm
Event Configuration for these signals.
Avoid identical names of PLC Process Object and PLC Signal Object.
Configuring a third party AE-OPC Server

The AE OPC Server should be installed on the Compact HMI server node. To attach
the AE OPC server to the Compact HMI system please follow the steps in the
chapter Connecting to AC 800M Alarm and event OPC server.
Using AC 500 with Compact HMI

Install the AC 500 Control Builder and OPC server on the server node to use
Compact HMI with AC 500. It is recommended to use the ModBus TCP driver in
the Compact HMI to access the AC 500 controllers.
While setting up the communication, note the following:
– Ensure to use the same network mask in the AC 500 as in the Compact
HMI, that is, 255.255.252.0.
The following should be done to use the AC 500 OPC Server:
– Set the OPC server (in dcom config) to execute as the same user in AC 500
control builder. Login as SysAdmin and execute the following steps.
1. Go to Search functionality and type “dcomcnfg.exe”. This displays the
application for configuring security for components.
2. Browse for component OPC Server for CoDeSys...
68 3BSE040587-601
Section 3 Installation Connection to Third Party Alarm & Event OPC Server
Figure 41. DCOM Config in Component Services
3. Right-click and select Properties.

4. Select the Identity tab.
3BSE040587-601 69
Connection to Third Party Alarm & Event OPC Server Section 3 Installation
Figure 42. OPC Server for CoDeSys V2.0 Properties
5. Select This user. Provide the user name and password for the user to login
while using the AC 500 Control Builder (typically the user AppEng).
6. Click OK and close the application. The system is ready to be used for both
configuration and operation with the AC 500 controller.
70 3BSE040587-601
Section 3 Installation IP Addresses
IP Addresses
The tables below give a recommendation on IP addresses that will work for most
installations. If this suggestion is followed, the reader can disregard much of the
details about RNRP configuration. Table 2 suggests which NetIDs to use.
Table 2. Suggested NetIDs and Network Area Numbers
Network type NetIDs Network Areas

Client/Server Networks 172.16.x.0 1-10
172.17.x.0
where x=4,8,12 to 40 (steps of 4)
Control Networks 172.16.x.0 20-31
172.17.x.0
where x=80, 84, 88 to 124 (steps of 4)
Use the subnet mask 255.255.252.0 for all network interfaces.
3BSE040587-601 71
IP Addresses Section 3 Installation
Addresses recommended on the Client/Server/Control Network Area 1
Table 3. Suggested Addresses for Nodes on Network Area (1)
Addr on
Node Addr on Primary
Nodes Secondary
number Network
Network
Servers 11-20 172.16.4.11 - 172.17.4.11-
172.16.4.20 172.17.4.20
Workplace Clients 71- 150 172.16.4.71 - 172.17.4.71 -
172.16.4.150 172.17.4.150
Controllers 151- 172.16.4.151 - 172.17.4.151 -
220/255 172.16.4.220/255 172.17.4.220/255
Backup CPUs for 663-767 172.16.6.151 - 172.17.6.151 -
Redundant Controllers 172.16.6.255 172.17.6.255
Switches, Gateways, (501-511) 172.16.5.245- 172.17.5.245 -
Firewalls 172.16.5.255 172.17.5.255
(not RNRP addresses) (1013- 172.16.7.245- 172.17.7.245 -
1022) 172.16.7.254 172.17.7.254
Use the IP address mask 255.255.252.0 for all nodes.

If you do no use the implicit addresses you need to manually configure RNRP.
Refer to System 800xA, Network Configuration (3BSE034463*) for more
information regarding implicit or explicit RNRP address configuration.
To change IP addresses, execute the following steps.
2. Change the IP address of the computer through Windows Control Panel.
3. Update the Host file in the server and all clients to reflect the changed address.
The file can be found in the path C:\WINDOWS\system32\drivers\etc\hosts.
Update the file using Notepad.
4. Restart the system after changing the IP addresses.
For more information refer to System 800xA, Network Configuration
(3BSE034463*).
72 3BSE040587-601
Section 4 Engineering
This section describes the engineering in Compact HMI. The following is a

workflow to engineer the Compact HMI. The first two steps have already been
covered in earlier sections.
1. Connect the PLCs and Controllers to the Compact HMI.
2. Install the PLC tools and configure OPC servers.
3. Define the Device and Process object types visible in the Compact HMI.
4. Create instances of the Types and connect to the PLCs.
5. Structure the control application according to the controlled equipment.
6. Create displays, alarm lists, logs, trends and documentation.
Working with Object Types

Object types are used to define objects that represents the different types of devices
and process objects for which data will be fetched in the PLCs.
Object types hold information and functionality of a specific type of object, for
example, a pump, and valve. This section describes the following:
• Creating an object type.
• Adding signals to an object type.
• Adding Graphical Elements.
• Adding Faceplates.
• Adding Alarm and Event.
• Adding History logging.
3BSE040587-601 73
Creating an Object Type Section 4 Engineering
• Adding Trend display.

The object types that are created can be exported and reused in several projects
using Compact HMI.
Creating an Object Type

The PLC Connect function allows the user to get an object oriented handling of the
properties retrieved from the PLCs. The grouping of signals into objects
representing devices controlled by the PLC is done in the Object Type Structure.
Create an object type for each device type controlled by the PLC. Execute the
following steps to create an object type.
1. In the Plant Explorer, select PLC object type in the Object Type Structure.
2. Right-click and select New Object from the context menu.
Figure 43. New PLC Object Type in the Object Type Structure
3. Enter the name of the device type (for example SimpleOnOffMotor) and click
Create. This creates the object type.
74 3BSE040587-601
Section 4 Engineering Adding Signals to an Object Type
Figure 44. New Object Type- Simple OnOff Motor
The newly created object type can be used to create instances which will be
connected to the individual signals existing in the PLCs.
Adding Signals to an Object Type

Signal objects are used to read and write data from/to the PLCs. For each device
type, the user should define the properties to be read and written from/to the PLC
for this type of device. This is done by creating a PLC signal for each property that
should be accessed.
To configure (for example SimpleOnOffMotor), execute the following:
1. In the Object Type Structure, select the SimpleOnOffMotor.
3BSE040587-601 75
Adding Signals to an Object Type Section 4 Engineering
2. In the preview area you can create signal object by clicking om the I/O icons as
shown below.
Figure 45. Create signal Objects
3. Select the I/O type signal that represents the property to be accessed.
4. Enter the signal name (for example Motor_ON).
Repeat the above procedure for all the signals to be accessed for this device
type.
The OPC Server does not allow names of the signals as two words. The name of
the signal should be, for example, Motor_ON.
For more information on creating instances of this object type, refer to Creating
Instances on page 83.
76 3BSE040587-601
Section 4 Engineering Adding Graphical Elements
Adding Graphical Elements

To be able to present data from instances of the object type in graphical displays, 
a display element must be created. This is done by following the steps below. See
also Section 7, Using the PLC Device Library.
1. In the Object Type Structure, select the device object type created in Creating
an Object Type.
2. Right-click and select New Aspect from the context menu.
3. Select the category Graphical Element PG2 from the available list to create a
new graphic element.
4. Type a name for the graphic element and click Create.
5. In the aspect area, right-click the newly created graphic element and select
Edit. This opens the Process Graphics Editor to edit the graphic element.
6. Drag and drop the Ellipse primitive from Toolboxes > Shapes.
7. To change the color of the ellipse, select the primitive and click
corresponding to the FillColor property. This opens the Expression Editor as
shown in Figure 46.
3BSE040587-601 77
Adding Graphical Elements Section 4 Engineering
Figure 46. Process Data Property Selections
For example, to write an expression to change the color of the ellipse when the value
of Motor_ON is True or False, execute the following steps:
1. In the Expression Editing area, enter if with a <space>.
2. In Process Data, click and browse for the Motor_ON signal object.
3. Select the Value property and click to insert the property into the
Expression Editing Area.
4. In Resources, click to define a color for the property.
5. Select symbol1Normal from Object Colors and click to insert the
property into the Expression Editing Area.
78 3BSE040587-601
Section 4 Engineering Adding Faceplates
6. Similarly select the color to be used if the value of Motor_ON signal object is
False.
The expression should be:
if S’Motor_ON:Value’ then
symbol1Normal
else
deviation
where, symbol1Normal and deviation are Logical Colors.
7. Click Apply and then click OK to save the changes and close the Expression
Editor.
8. Select File > Save to save the graphic element.
9. Select File > Exit to close the Process Graphics Editor.
Figure 47. An Example of a Graphical Element
Adding Faceplates
Faceplates are used to view, interact and change properties for devices and other
process objects. The operator of the plant opens the faceplates by clicking on
objects in graphic displays. For more information about the operator handling of
faceplates, refer to System 800xA, Operations (3BSE036904*).
Consider an example to create a faceplate aspect that activates the start signal for the
SimpleOnOffMotor object type representing a motor. The faceplate is created on the
object type.
Execute the following steps to create the faceplate:
3BSE040587-601 79
Adding Alarm and Event Handling Section 4 Engineering
1. Select PLC Faceplate Templates in the Object Type Structure.

2. Copy the Faceplate Standard aspect.
3. Select the object type for which a faceplate is required. For example, select
SimpleOnOffMotor object type and paste the copied aspect.
4. Right-click faceplate the aspect and select Config View from the context menu.
5. Click the Buttons tab.
6. In the row containing the On icon, click the object field and browse to the
Motor_ON signal.
7. Click the Property Name field and select the Value property.
8. Select Property type as Boolean and Property value as True.
9. Click the Enabled field and edit the expression to:
iif($’./[Control Structure]:ObjectPCA:LOCK’=3,True,False)
10. The 1-Icon button is now configured to send the value True to the PLC signal
Motor_ON if the object is reserved (for example, LOCK=3).
11. Click the Tooltip text column. Select Label and enter Start motor. Click OK.
12. Click Apply to save the changes. This creates a faceplate with a button that sets
a property in PLC. A warning dialog appears, but it can be ignored in this
example.
13. Double-click the faceplate aspect to view the faceplate.
For more information on configuring the faceplates, refer to System 800xA,
Engineering, Process Graphics (3BSE049230*).
Adding Alarm and Event Handling

The Alarm and Event Configuration aspect on the signal objects are used to
generate events and alarms based on the properties received from the PLC.
The events and alarms are viewed and accessed by the operator using alarm and
event lists. A top level alarm list, which is handling all alarms in the installation, is
preconfigured. It is possible to configure other alarm lists on lower levels, for
80 3BSE040587-601
Section 4 Engineering Adding History Logging
example for a section of the site or a single motor. For more information, refer to
System 800xA, Operations, Operator Workplace Configuration (3BSE030322*).
To create an event or alarm, the signal has to be configured. This is done using the
Alarm and Event Configuration aspect on an object type or on the individual signal
instance.
Object instances that generates events and alarms are recommended to be placed in
the Functional Structure to have alarm lists that covers only parts of the plant.
Building the Functional Structure on page 90 describes how to create an appropriate
Functional Structure.
The configuration of an event or alarm can be done either on the signal type or on
each instance. To define an event execute the following steps:
1. Select the device object for which alarm handling is required (either an
instance or an object type). For example, SimpleOnOffMotor in the Object
Type Structure.
2. Create a new signal called Motor_tripped of the type PLC Binary Type
representing the signal for which alarm handling is required.
3. In the Alarm and Event Configuration aspect of the signal below the Event tab,
select Is an event and Log status changes on.
4. Click Apply to save the changes.
The signal object is configured to generate an event when the value changes to on.
An instance of the object type must be created and connected to the PLC to
generate the event.
To see an event for a specific area, select the event list aspect for that area. To define
an alarm for the object select the Alarm tab instead and configure the alarm.
Adding History Logging

The Log Configuration aspect is used to create a history log of a value received from
the PLC. The log can be defined on the signal instances or on the signal types. To
define a log on a type (and by this for all instances), go to the Object Type Structure
and select the type, for example SimleOnOffMotor, and add a Log Configuration
aspect to the Signal object, for example the Motor_ON signal, then go through the
following steps:
3BSE040587-601 81
Adding Trend Display Section 4 Engineering
1. Select Add Property Log in the Log Configuration aspect.

2. Select the property that shall be logged in the list, and then select the log
template OPC. For example, Single Log.
3. Click OK and click Apply to save the changes.
This log configuration will now be active on all instances for this signal object. To
create a log on an individual object add and configure a Log Configuration aspect
to an instance in the Control Structure.
Fore more information regarding History refer to System 800xA, Configuration
(3BDS011222*).
Adding Trend Display

An object type can have a default Object Trend that shows one or more signal values
for the object. To add an Object Trend for all instances, select the object type and
execute the following steps:
1. Create a Trend display aspect on the device object type, for example on the
SimpleOnOffMotor object type.
2. Select the newly created Trend Display. Click the first field in the Object
column. Click ... to browse for an object. Browse to the Motor_ON signal
object and click OK.
3. A default property will automatically be selected. For example, Value property
of the Motor_ON signal. It is possible to change this property by selecting
another from the Property field.
4. Select TRIM as Log Name.
5. Configure additional fields if required. Save the configuration by pressing the
Save icon in the upper left corner of the table. The trend is now configured and
will show up on each instance of this type.
For more information regarding Trends, refer to System 800xA, Operations,
82 3BSE040587-601
Section 4 Engineering Creating the Device Object Instances
Creating the Device Object Instances

Data from the PLCs are received by signal objects defined in the Control Structure.
The signals are grouped below device objects representing devices in the factory. 
To be able to present the data in displays in Compact HMI, the device objects are
equipped with graphics elements.
Device object types with corresponding signals, graphics elements and faceplates
was created in the previous chapter. This chapter describes how these object types
can be instantiated and connected to individual signals in the PLCs.
Before displays are built, the objects are moved to the Functional Structure where
they can be easily addressed by the Graphics engine. For more information, refer to
System 800xA, Operations, Operator Workplace Configuration (3BSE030322*).
Creating Instances
To create device instances that can be utilized for data presentation, do the
following.
1. In the Control Structure and select the OPC server for the PLC that contains the
properties you want to access.
2. Right-click the OPC server and create a New Object. Select any object type,
for example, SimpleOnOffMotor and enter a name (for example, M1).
Figure 48 shows the Control Structure:
3BSE040587-601 83
Creating Instances Section 4 Engineering
Figure 48. Control Structure
To create several objects from one object:

1. Select PLC Connect Servers and then the Generic Control Network
Configuration aspect. Use the icons as shown in Figure 49 to create or delete
several objects.
84 3BSE040587-601
Section 4 Engineering Creating Instances
Figure 49. Yellow Cubes for Object Creation and Deletion
3BSE040587-601 85
Connecting the Instances to Real Signals Section 4 Engineering
2. Click the yellow cube with the star and the dialog as shown in Figure 49.
Figure 50. Create New Object
3. Select the object type used when creating the instances.

4. Enter a name of the new object in the Name of the new object area.
5. Select the controller to which the object will be placed in the Controller drop-
down menu.
6. Select the number of objects required in the Number of new objects area. If
two or more objects should be created the Starting number area will be
enabled. Enter what starting number the first object shall have. The maximum
limit is 999 objects.
Connecting the Instances to Real Signals

The Signal Configuration aspect allows to connect each signal to the corresponding
property in the PLC.
1. To connect the signals, select Connected in Variable connection field.
86 3BSE040587-601
Section 4 Engineering Connecting the Instances to Real Signals
2. Click Browse to connect to the property in the PLC.
Figure 51. Connect the Signals
3. Click Apply in the OPC browser window to save the changes as shown in
Figure 52.
4. Repeat the procedure for configuring each signal.
Note that the Browse function is only available if the OPC server supports
browsing.
A signal can also be connected by adding the address string for the property.
3BSE040587-601 87
Connecting the Instances to Real Signals Section 4 Engineering
Figure 52. OPC Browser Window
5. To test the connection, select the PLC Connect Server objects and the Deploy
aspect. Click Deploy.
88 3BSE040587-601
Section 4 Engineering Connecting the Instances to Real Signals
Figure 53. Deploy
6. Click one of the signal object and select the binary PCA (Process Control
Aspect).
7. Select the Subscribe for live data check box to verify that data is retrieved
from the PLC.
Figure 54. Subscribe for Live Data
Another method to retrieve live data is to select the Object Dialog aspect, see
Figure 55.
3BSE040587-601 89
Building the Functional Structure Section 4 Engineering
This retrieves live data from all the signals that are placed in this object. The alarm
indication icon appears. It also allows the user to view if a signal is forced or not.
Receiving live values for signals indicate that PLC Connect functions as required.
Figure 55. Alternative Way of Subscribing for Live Data
Building the Functional Structure

Objects used to access data from the PLCs are placed in the Control Structure.
The OPC server and PLC contain the retrieved properties based on this. To perform
this, objects should be placed in the Functional Structure to reflect the functions in
the plant. The objects in the Control Structure should be copied into the Functional
Structure.
Building objects are described in System 800xA, Operations, Operator Workplace
Configuration (3BSE030322*).
To create the objects in Functional Structure, execute the following steps:
1. In the Functional Structure, select the “<Plant name>” object.
2. Click the object and select the Name aspect. Change the name to the name of
the Plant.
90 3BSE040587-601
Section 4 Engineering Building the Functional Structure
3. Right-click and select New Object from the context menu to add objects to
define the structure of the plant. Select one of the objects in the list, give it a
name and click Create.
Figure 56. Control Structure and Functional Structure
Use the Bulk Data Manager (BDM) tool to move the device objects in the Control
Structure to the Functional Structure.
4. Switch to the Control Structure and select the root object.
5. Open the Bulk Data Manager from ABB Start Menu > ABB Industrial IT
800xA > Engineering.
6. In the Plant Explorer, right-click the BDM Place Objects aspect in the
Functional Structure and select Edit and Check Out.
3BSE040587-601 91
Delete the data present in the spreadsheet in addition to the column headings.
7. Select one of the OPC servers objects (for example, Matricon OPC Server) in
the Control Structure and drag and drop the values in the Bulk Data Manager.
See Figure 57 below.
Figure 57. The Bulk Data Manager
92 3BSE040587-601
Section 4 Engineering Building the Functional Structure
8. Move contents of column F to column E, select all texts in the column and cut
it and paste it in column E. Deselect the items in column F and click Save all
objects, a button located in the toolbar menu below Add-ins.
Figure 58. Move from column F to column E
3BSE040587-601 93
9. The objects will be placed in the Functional Structure.
Figure 59. Copied Objects
10. Exit the Excel file and do not save the changes.
In the Functional Structure, the objects can be dragged and dropped to the preferred
places.
Figure 60. The Functional Structure
94 3BSE040587-601
Section 4 Engineering Adding Process Displays
To add new objects, simply copy the new or changed objects from column F to
column E.
Adding Process Displays

Structures and relationships between displays, can be defined in the Functional
Structure. The Device Instances that are created in the Control Structure, should
additionally be placed into the Functional Structure.
Execute the following steps to create a process display:
1. Select the Plant object in the Functional Structure.
2. Right-click and select New object from the context menu.
3. Select the required object type and enter a name for the object (for example,
MU1) and click Create.
4. Right-click the newly created object and select New Aspect from the context
menu.
5. Select Graphics Display PG2 from the available list and click Create.
6. Right-click the aspect in the aspect area and select Edit from the context menu
to open the Process Graphics Editor.
7. To add a device to the graphic, select View > Element Explorer.
3BSE040587-601 95
Adding Process Displays Section 4 Engineering
Figure 61. Element Browser
8. In the Element Explorer, select the Control Structure and then browse to the
object containing the graphic element. The graphic elements belonging to the
object are displayed in the lower pane of the element explorer.
9. Double-click the graphic element to add it to the graphic display. The user can
also drag and drop the graphic element to the graphic display.
10. Select View > Toolboxes to view the toolbox of the Process Graphics Editor.
This allows the user to add graphic primitives to the graphic display.
To add a set of symbols to the graphic display, select Symbol Factory Bar
(this primitive adds a bar item) or Symbol Factory Symbol (this primitive adds
a graphic symbol such as motor, or valve) from Toolboxes > Special. 
Right-click the control and select Edit from the context menu to edit the
symbol or bar.
96 3BSE040587-601
Section 4 Engineering Adding Trends
11. Select File > Save to save the graphic display.

For more information refer to System 800xA, Engineering, Process Graphics
(3BSE049230*).
Adding Trends
Follow the steps below to create a Trend Display aspect:
1. Right-click the object to create the Trend Display and select New Aspect from
the context menu.
2. Select the Trend Display aspect category.
3. Enter a name for the aspect and click Create.
There are several different aspect categories of Trend Displays, the Operator
Trend, the Trend Display and the Object Trend.These categories are
dependent on the user roles required to modify them (Operator- and Object-
trend can be accessed by Show All in the new aspect dialog).
4. Select the newly created aspect in the aspect list. Figure 62 shows the Trend
Display.
3BSE040587-601 97
Adding Trends Section 4 Engineering
Figure 62. Trend Display
The Trend Display uses the default Trend Template.
98 3BSE040587-601
Section 4 Engineering Adding Trends
5. In the Config View, select the required Trend Template.
Figure 63. Select another Trend Template
6. To insert an object, execute one of the following:

– Click the Object Name column and enter the object name (or enter a dot).
– Select a signal from the Select Object dialog.
3BSE040587-601 99
Adding Alarm and Event list for a Plant Area Section 4 Engineering
– Drag and drop the object in the Object Name column.
Figure 64. Select Object Pop-Up Dialog
7. Select the Property and Log Name. Modify the data in other columns if
required.
Press SHIFT while selecting property in the Property selection column. This
displays only the logged properties.
If Log Name is not selected, SEAMLESS will be selected by default.
For more information regarding Trends, refer to System 800xA, Operations,
Adding Alarm and Event list for a Plant Area

The Functional Structure can be used as a base for sorting alarms according to the
functional structure of the plant. To configure an Alarm and event list that shows
alarms for a specific part of the plant, execute the following steps:
100 3BSE040587-601
Section 4 Engineering Basic Navigation
1. In the Functional Structure, select an object for which an Alarm and Event list
is required. This includes alarms of all the objects belonging to the selected
object.
2. Right-click the object and select New Aspect.
3. Select the Alarm and Event list category.
For more information refer to System 800xA, Operations, Operator Workplace
Basic Navigation
Below the four most common ways to navigate are listed:
• Shortcuts make it easy to navigate to the most important and/or most frequently
used aspects of different aspect objects. You can find different shortcuts in the
Application Bar.
• To move back to the previous display click the Back to Previous Display
button. If the button is disabled, it is not possible to go backward.
• By clicking the Aspect Menu icon in the Tool Bar the Aspect Menu will be
presented. From the Aspect Menu you can navigate to different displays by
clicking on your Aspect Favorites.
• From the context menu you can e.g. select an aspect, action or a referenced
display for the object or aspect. The contents of the context menu may differ
depending on which object or aspect you have selected.
For more information refer to System 800xA, Operations, Operator Workplace
Adding Shortcuts for Navigation

In Compact HMI, the navigation is done in an object oriented way. When defining
shortcuts for navigation, these are available from all aspects of an object by just
adding the shortcut to the object itself, once as an aspect.
3BSE040587-601 101
Adding Shortcuts for Navigation Section 4 Engineering
This means that by adding a shortcut to the RC1 Robot Cell object, we can use the
shortcut from all views of the cell. For example, to add a shortcut to RC1 that points
to RC2, navigate to RC2 aspects from RC1 Graphical Display, RC1 Trends Display,
RC1 Mechanical Drawing.
The figure below shows how the navigation works:
Added Shortcut
Resulting
Navigation Functions
By adding a shortcut to the RC1 object, pointing to the RC2 Graphic Display, the
RC2 Graphic Display can be accessed both from the RC1 Graphics Display and the
RC1 Trend Display.
102 3BSE040587-601
Section 4 Engineering Adding Shortcuts for Navigation
Shortcuts in the Application Bar

A shortcut in the Application Bar is created to get fast access to any viewable aspect
associated with a particular object.
Application Bar Shortcuts
Figure 65. Application Bar Shortcuts
To create a shortcut in the Application Bar follow the steps:

2. Open the Plant Explorer and expand the Workplace Structure.
3. Right-click the Workplace object and select New Aspect.
4. Select Application Bar Shortcuts category.
3BSE040587-601 103
6. Double-click the aspect to configure the Application Bar Shortcut. This

displays a dialog as shown in Figure 66.
Figure 66. Dialog Box for editing of Application Bar Shortcut
104 3BSE040587-601
Section 4 Engineering Adding Shortcuts for Navigation
7. Click Add. This displays a dialog as shown in Figure 67.
Figure 67. Application Bar Shortcuts Dialog Box
8. Select the structure, object and aspect and click OK.

9. The shortcut is now added to the shortcut list. Repeat the above procedure to
add more shortcuts.
10. Click Apply. Restart the configured workplace to activate the configuration.
Shortcuts in the Display Bar

Shortcut in the Display Bar is a shortcut button used for fast access to any viewable
aspect associated with a particular object and its descendents.
The shortcuts in the Application Bar are associated with the Workplace, and are
available at all times (no matter which Display you have selected). Shortcuts in a
Display Bar are visible only if the Display containing this Display Bar is selected.
Shortcuts make displays related to, and of importance to, a certain display
accessible by a simple click. This can be useful if a number of displays are to be
shown in sequence. Then a click on the shortcut icon switches to the next display in
the sequence.
3BSE040587-601 105
To add a shortcut in the Display Bar follow the steps:

1. Log on as SysAdmin.
2. Open the Plant Explorer.
3. Add Shortcuts aspect to the source object from which the target aspects should
be linked.
4. Double-click the aspect.
5. Click Add and select structure, object and aspect in the dialog box. See
Figure 68.
Figure 68. Add/Edit Display Shortcut Dialog Box
6. Click OK. The shortcut will be added to the shortcut list.
106 3BSE040587-601
Section 4 Engineering Messaging Configuration
7. A Display Shortcut will be displayed in the Display Bar, to the right of the
other tools. See Figure 69.
Display Shortcuts in a Display Bar
Figure 69. Display Bar Shortcuts
Messaging Configuration
The messaging function is used to forward important alarms and/or events to user on
the move. The messages can be forwarded using SMS, e-mail or paging services.
The example below shows how to configure the system to forward messages using
the SMS distribution channel.
To configure the Messenger function, to send alarm and events using SMS
messages, please go through the steps described below. For detailed configuration
information use the help button in the corresponding aspects. Login as a SysAdmin
to continue the process.
SMS Messaging Configuration

Use the shortcut buttons available to the right about the view for quick access to
aspects referenced below:
1. Connect the phone or other SMS capable device to an USB or serial port on the
server computer. Use the normal PC connection cable. The specific drivers are
installed automatically.
3BSE040587-601 107
SMS Messaging Configuration Section 4 Engineering
2. Open the Computer Management tool by right-clicking on My Computer in the

Start menu and select Manage. Click Device Manager and expand Modems.
3. Select the port to connect the new device (normally Com3).
4. Configure the SMS device used to send the messages. This is configured in the
aspect:
[Aspect System Structure]Aspect System Structure/Messenger/SMS
Device/SMS Device:SMS Device
The Messenger Service must be disabled before configuring the SMS Device.
5. In the Services tab, you find the GSM predefined. Manually select the port
being used (normally port 3).
6. In the General tab, activate Outbox and Inbox Spoolers.
7. To configure, click ConfigureSMSDevice and open the Ports tab. Click Add.
8. Select the Port that you got above (normally port 3), click Next.
9. Enter the phone number for the phone that is used including country code.
10. Enter the Initialization string for the phone (look in help for initialization
strings).
For newer models of SonyEricsson phones use the Initialization command
string:
“AT+CBST=0,0,1;+CHSN=4,2,0,12” (omit the “characters)
11. Go to the General tab and select the Activate Outbox Spooler and the
Activate Inbox Spooler check box.
12. Configure the user that is supposed to receive the messages. This is done in the
Message Subscriber and Message Schedule aspects on the user objects in the
User Structure.
13. Define the alarms and events that should be sent as SMS messages by adding
and configure an Alarm and Event list aspect that defines which messages that
should be sent out.
108 3BSE040587-601
Section 4 Engineering e-Mail Messaging Configuration
14. To direct the messages in the list to be sent as SMS messages you need to
configure a Message Handler and an Alarm and Event Message Source aspect
on the same object as where the alarm list is located. (No shortcuts available.)
Enable the function in the Message source tab in the Message Handler aspect.
15. When the configuration is completed, start the messenger service by enabling
the service using the aspect:

[Service Structure]Services/Messenger Server/Basic:Service Group Definition
16. Test the messenger function. A message should be sent by SMS after
generating an alarm that is displayed in the alarm list aspect.
e-Mail Messaging Configuration

The e-mail messaging function forwards alarms as an e-mail to recipients as
specified in the system. The function is using the Internet information service,
Default SMTP Virtual Server, on the server node to connect to an SMTP host that
forwards the messages to the recipient. To configure the e-mail messaging follow
the steps below.
1. To define which alarm list that should be the source for the messages create an
Alarm and Event message source aspect on the same object as where the alarm
list aspect is located. Configure this aspect to refer to the alarm list used as the
source of the messages. To always send messages at least during the setup
phase later, this is normally changed to send only. A message source is defined.
2. Next step is to make it possible for messages to be sent to a specific user. This
is done by adding a Message Subscriber aspect to the corresponding user object
in the user structure. In the configuration of the aspect, click New to define a
method to send the message to the user. In the dialog select SMTP/e-mail and
click OK. Enter the user’s e-mail address. The user will be able to receive mail
messages.
3. To define when messages are sent to the user we need to create a Message
Schedule aspect. In the configuration select Always Deliver messages during
3BSE040587-601 109
Audit Trail Section 4 Engineering
the initial configuration phase, this should be changed later to correspond to the
required function.
4. To link the messages from the messages source to the user, add the Message
Handler aspect to the same object as where the message source aspect is
defined. Click New to select to which user and through which user device these
messages should be sent and click OK. Go to the Message source tab and
select the message source aspect to be used as source.
Select Enabled and click Apply to save the changes. The messages that should
be sent to which user and through which device are defined.
5. To define the information required to send e-mail messages from the system,
open the Aspect System Structure and browse to the object Messenger >
Email Device > Email Device and select the Email Device aspect. In this
aspect specify the e-mail address of the system in From field. This e-mail
address will be shown as the sender in the e-mail when it is received by the
user.
6. The next field is the SMTP Relay server, which can be left blank because the
Default SMTP Virtual Server is used on the server node to path the messages to
an SMTP server according to the suggestion received from the DNS.
Audit Trail
The Audit Trail function is by default enabled in Compact HMI. To view the Audit
Trail, open the Audit Trail List aspect on the plant object in the Functional
Structure.
To enable / disable the Audit Trail function follow the steps below:
2. Open the Plant Explorer and expand the Admin Structure.
3. Select Administrative Objects > Domains > CHMI_ServerSystem > Audit
Trail Config.
4. Double-click the Audit Trail Config aspect to open the configuration view.
5. Clear the selection in the Audit Trail active check box, and click Apply to
disable the Audit Trail function.
110 3BSE040587-601
Section 4 Engineering Security Configuration
6. Select the Audit Trail active check box. This enables the Audit Event
Filtering area.
7. Select the Log Generic Audit Events check box to log all the audit events that
are predefined in the system without details.
8. Select the Log Selected Audit Event Classes check box to select the audit
event message classes to be included.
9. Click Apply to save the changes.
Re-authentication is required to apply changes in the Audit Trail Configuration if
Advanced Access Control is activated.
Security Configuration
The default configuration contains a security setting valid for all objects in the
system. This default configuration is available in Admin Structure >
Administrative Objects > Inventory Object > Domain > [System Name] >
Security Definition.
The default configuration provides permissions for Operators, Application
Engineers and System Engineers.
Consider an example, where there are different groups of operators having different
access rights to application areas. This can be achieved by adding a Security
Definition aspect range on the particular object in the Functional Structure.
Individual objects can also have extended protection by adding a Security Definition
aspect with object range directly on the object.
For more information on configuring security, refer to System 800xA,
Administration and Security (3BSE037410*).
Import/Export of Application from Compact HMI

Export of Controller Communication Application from Compact HMI
To export the controller communication definition part of a PLC Connect based
application in Compact HMI, execute the following:
3BSE040587-601 111
Import of Controller Communication Application to Compact HMI Section 4 Engineering
1. In the Control Structure, open the Import Export tool.

2. Drag and drop the PLC Generic Control Network object to the Import Export
tool.
3. In the Add Item dialog, click OK. All instances are exported with
dependencies, that is, the object types are included in the exported data.
4. Click Done in the Finished adding items dialog.
5. Save the afw-file onto a media by clicking the Save button in the Import Export
tool.
Import of Controller Communication Application to Compact HMI

Manually create PLC Controller Type objects representing the controllers in the
Compact HMI system. This should be done because the configuration of these
objects are dependent on the installation of the drivers in the node. This object
should be created for each controller.
When all controllers are created and configured, continue with the steps below:
1. Copy the afw-file containing the stored configuration to the Compact HMI hard
disc.
2. Double-click the file to start the Import Export tool.
3. Select the Object Type Structure in the Import Export tool.
4. Right-click the PLC Object Types Object and select import and then Finish.
5. Select the Control Structure in the Import Export tool. Browse to the PLC
Controller Type objects.
6. Select the objects in PLC Controller Type.
7. Right-click and select Import from the context menu.
8. In the Importing dialog box, select Import Options and remove the selection
Include Dependencies.
9. Click Finish.
10. When asked for the restore path (Do You want to place manually) select Apply
to all Items and Yes.
112 3BSE040587-601
Section 4 Engineering Hardware and Software Supervision
11. In the Placements dialog right-click on the controller object and select new
insertion point.
12. Select the location of the PLC Controller type object in the Control Structure
and click OK.
13. Click OK for each imported item.
14. Before the objects will start communicating a deploy has to be done on the
PLC Connect Servers object (in the Control Structure).
Hardware and Software Supervision

To supervise the PC hardware, network components and the running software it is
possible to use the PC network and software monitoring functionality (PNSM).
To configure PNSM go though the following steps:
1. To create object to represent the PC nodes in the system their is a tool available
in the start menu ABB Compact HMI 800-Asset Optimization-PC, Network
and Software Monitoring-Basic Computer Monitoring Configuration
Tool. Open the tool and press the Start button, this will create objects in the
Control Structure below the IT Server-Basic Computer Monitoring. These
objects represents the PC computers that are part of the system.
2. To get an object supervising the software services running in the server go to
the Control Structure and select the server node and right-click to create a new
object. Select the IT assets-Computer nodes-PPA Nodes-800xA Combined
AS-CS type, enter a name and create the object.
3BSE040587-601 113
Hardware and Software Supervision Section 4 Engineering
114 3BSE040587-601
Section 5 Operation
This section describes how to operate the IndustrialIT Compact HMI. Also refer to
System 800xA, Operations (3BSE036904*) and System 800xA, PLC Connect,
Operation (3BSE035040*).
Workplace Layout and Tools

The following is an overview of the default screen layout for the Operator when
using IndustrialIT Compact HMI. Tabbed Workplace is the default workplace.
The Operator Workplace can be configured per user or user group, which means that
all users can have different or identical layouts according to their preferences.
Figure 70 shows the different areas in a workplace.
3BSE040587-601 115
Workplace Layout and Tools Section 5 Operation
Figure 70. Tabbed Operator Workplace
Legend Description
1 Tabbed Menu
2 Application Bar
3 Panel Area
4 Display Bar
5 Tool Bar
6 Status Bar
116 3BSE040587-601
Section 5 Operation Tabbed Menu
Tabbed Menu
The Tabbed Menu is used to navigate to the different areas of the plant. Figure 71
shows tabbed menu mapped to the corresponding plant element in the Engineering
Workplace.
Figure 71. Tabbed Menu
Application Bar
The Application Bar is used to show information that must be present all the time,
regardless of what displays are shown. One example is the alarm line. Tools in the
application bar influence the system or handles aspect objects. Some of the tools are
very useful for navigating.
For more information on customizing the Application Bar, refer to Application Bar
on page 125.
3BSE040587-601 117
Panel Area Section 5 Operation
Figure 72. The Application Bar
Legend Element Description

1 Alarm Band The Alarm Band provides a summary display for selected alarm lists. It
provides a link to the corresponding alarm list display. The number on a
button (e.g. 1 for Process Alarms) represents the number of currently
unacknowledged alarms. The color of the button shows the highest priority
of an alarm presented at the moment. To go to an alarm list, click on the
button.
2 Alarm Line The Alarm Line is an Alarm List, specially configured to show the three
latest process alarms.
3 Clock Shows the system clock.
4 ABB logo Shows the company logo.
Panel Area
The Panel is the main area for displays. It is used to show a view of an aspect (a
display), and can be used to present information like process displays, trend
displays, alarm lists, etc. Displays can appear as base displays covering the entire
Display area or as one or more overlap displays. The tools in the Display bar can be
used to control and identify the contents of the Display area.
118 3BSE040587-601
Section 5 Operation Display Bar
Display Bar
The Display Bar is used to navigate between displays. It changes when the base
display is changed.
For more information on customizing the Application Bar, refer to Display Bar on
page 125
Figure 73. Display Bar
Legend Tools Description

1 Back to Previous Display Shows the previous display in the aspect history list.
2 Forward to Next Display Shows the next display in the aspect history list.
3 Aspect History List Shows a listing of the most recently viewed aspects or type of
information (the latest used display on top).
4 Pinned Tool Pins the display like a note on a billboard. The display can not
be changed by clicking the Backward or Forward button, or by
dropping a display on the Drop Target tool.
To enable change of display, remove the pinning of the display
5 Print Tool Used to print the Operator Workplace contents. The screen
where the tool is clicked will be printed on the default printer.
6 Aspect Icon Tool Used, for example, to add the aspect as a favorite by selecting
Add to Aspect Menu in the drop-down menu. You also have
the possibility to display the aspect view on another workplace
by selecting the workplace from the Send To submenu in the
drop-down menu.
7 Acknowledge Alarms Acknowledge all visible alarms
3BSE040587-601 119
Tool Bar Section 5 Operation
Tool Bar
The Tool bar is used to access different aspects and manage workplace.
Figure 74. Tool Bar

1 Find Used for finding the objects and aspects in a system, based on
name, path or guid and other attributes for example aspect
category or creation date.
2 All Process Alarms Shows a list of all alarms from the process.
3 All Process Events Shows a list of all events in the process.
4 Error Messages Shows a list of error messages.
5 System Alarms Shows a list of all alarms in the control system.
6 System Event List Shows a list of all events in the system.
7 System Status Control System Status shows the status of the hardware in the Control
Structure. Possible problems in the control hardware can be
detected.
8 System Status Shows a listing of status information for system services in the
Service Structure
9 External Alarm Silence Used to silence all external alarms
10 Replacement Strategy Allows selection of overlap window behavior. Selection of
Tool Preserve will cause any selection of aspect to occur in a new
overlap window. Selection of Replace will cause the overlap
window to replace its content if the asked for aspect is of the
same type.
11 Filter Limits the aspect information. For example, an object’s context
menu to show only the information that is relevant for you.
There are different filters for different users.
120 3BSE040587-601
Section 5 Operation Status Bar

12 Filter Configuration Enables to configure the filter with the available aspect
categories.
13 Enable/Disable remote Defines if it should be possible to bring up displays from other
access to this workplace workplaces on this workplace.
14 Toggle Browser Switches the Toggle Browser on and off. When it is switched
on, the Toggle Browser is opened in a overlap window. You
can then browse the object structures. The tool has two states
- up and down. When the button is down, the Toggle Browser
is displayed in a separate window. 
When the button is up, the Toggle Browser is closed.
15 Aspect Menu (Favorites) Shows a listing of the aspects that you have chosen to place in
the favorites list for fast access.
16 Close All Overlaps Closes all overlapping windows (overlap windows) opened in
the Operator Workplace.
17 Show Help Shows the On-line Help.
18 About IndustrialIT Shows information about the installed systems and
Compact HMI extensions.
19 Toggle Full Screen Toggles the workplace between full screen and window mode.
20 Close Workplace Closes the Operator Workplace
Status Bar
The Status Bar is used to show who the current user is.
Figure 75. The Status Bar
Users have different roles and privileges depending on security settings. The log-
over function can be accessed from this too.
3BSE040587-601 121
Navigation Section 5 Operation
Navigation
General
An operator working with the Operator Workplace wants to, in an easy way, address
and find elements such as graphic displays, faceplates, trend displays and alarm
lists. The Operator Workplace in IndustrialIT Compact HMI contains a tabbed menu
as a default set of tools to navigate among structures, aspects and objects.
A process industry site is often divided into different process sections, where the top
level display shows an overview of the entire section with details. Underlying
details may be accessed via the top level display or via other tools.
This section includes recommendations of how to use these tools to navigate
through displays. The recommended tools and methods are adequate for most
applications.
In the Compact HMI application the basics for presenting information from the
system is based on the Aspect Object concept.
Recommended Tools for Navigation

The basic recommended tools for navigation between displays are presented below.
For more information, refer to Workplace Layout and Tools on page 115 and System
800xA, Operations, Operator Workplace Configuration (3BSE030322*).
Tabbed Workplace
Tabbed Workplace allows the user to navigate between graphic displays using
buttons, tabs, and drop-down lists. Tabbed Workplace is used for easy navigation
and responsiveness to alarms and events. A Tabbed Workplace is created by copying
predefined Tabbed Workplace, located in the Workplace Structure. This workplace
includes a breadcrumb list and status indicators for each tab.
The Breadcrumb list shows the object path, starting from the currently displayed
object back to the root object (see Figure 76). The breadcrumbs show where the
122 3BSE040587-601
Section 5 Operation Recommended Tools for Navigation
operator has navigated and allows for quick navigation to the immediate parent or to
the overview display.
Objects containing Graphic

Displays, appearing as tab in the
Workplace
Figure 76. Tabbed Workplace (Displaying tabs and Breadcrumb list)
The Status Indicators include an Alarm Indicator and a Status Indicator (see
Figure 77). The Alarm Indicator shows the alarm severity. These indicators guide
the user through the object hierarchy to locate the display that contains the alarm.
This saves engineering time for navigation configuration.
3BSE040587-601 123
Recommended Tools for Navigation Section 5 Operation
The Status Indicator shows the alarm status information. For example, the status can
be hidden or shelved.
Figure 77. Tabbed Workplace (With the Drop-down and Status Indicators)
For more information on configuration, refer to System 800xA, Operations

(3BSE036904*).
Start Display
At log in as an Operator, the start display will be presented on the screen. It is
recommended to program one of the functional keys F1-F12 or the HOME key to
bring up this display.
124 3BSE040587-601
Fixed Process Display

The fixed display gives fast access to different information about the areas in the
plant. A single mouse click brings up the default process display for the clicked
object. A right-click gives access to all other aspects of the objects.
Display Links (Aspect links)

In a Process Graphics display, links to other displays may be defined. These display
links are configured when the Graphic Display is built. The links may lead to other
Graphic Displays, trend displays or alarm lists etc. With this feature it is possible to
define hierarchies and/or find the next display. Left-click on a display link to bring
up next display (graphics, an alarm list etc). Right-click to select among other
available aspects of the linked object. A special case of Display link is when you
open another display by left clicking on an object. Normally that is the Faceplate for
the object, but it might also be configured to be another Graphics display, a trend
display etc. See also Context Menu on page 125.
Display Bar
For more information on Display Bar, refer to Display Bar on page 119.
Application Bar
For more information on Display Bar, refer to Application Bar on page 117.
Context Menu
By right-clicking an object in a display (or alarm list etc), a list of aspects associated
to the object is presented. If right-clicking the background, a list of underlying
displays is presented, provided that they are configured to show up.
By left-clicking an object, the default aspect of the object is invoked. Normally that
is the Faceplate for the object, but it might also be configured to be another Graphics
display, a trend display etc.
3BSE040587-601 125
Recommended Tools for Navigation Section 5 Operation
Hot Keys
A Hot Key is a specific predefined key combination (or a single key) that perform a
specific function. For example opening an aspect view, activating a verb or
accessing an object.
Function keys F1-F12 or any standard key can be configured to bring up displays,
typically different sections of the plant and / or to important displays.
The hot keys operations can be global, i.e. independent of selected or highlighted
object or affect the selected or the highlighted object.
There is a difference between a selected and a highlighted object. Current
selection is displayed in the Object Shortcuts tool. Selection is set for example
when clicking a Graphic Element in the object browser.
An object is highlighted when placing the mouse pointer over a graphic element.
The following tables show available predefined Hot Keys in the Operator
Workplace.
Table 4. Workplace Hot Keys
Hot Key Operation

ALT+HOME Show Cursor
CTRL+F Find tool
CTRL+SHIFT+3 All process alarms
CTRL+SHIFT+4 All process events
CTRL+SHIFT+5 System alarms
CTRL+SHIFT+6 System events
CTRL+SHIFT+7 System status
CTRL+SHIFT+S Direct external alarm silence
CTRL+ALT+F4 Close all overlaps
ALT+F4 Close Active Window
126 3BSE040587-601
Table 4. Workplace Hot Keys (Continued)
Hot Key Operation

F1 Context Sensitive Help
CTRL+SHIFT+F1 Show hot key map
Table 5. Selected Object Hot Keys
Hot Key Operation

CTRL+G Show Object Type
3BSE040587-601 127
Faceplate Usage Section 5 Operation
Faceplate Usage
A Faceplate is a process dialog for supervision and control.
The most common method to open the faceplate for on object is to left-click on the
object in a graphic display.
Click here to open the faceplate
Figure 78. Graphic Display
128 3BSE040587-601
Section 5 Operation Faceplate Usage
A faceplate can have up to three different views. Possible views are:

• Reduced View. This view is optimized to be as small as possible, and yet cover
the most used commands and the most important information on an object.
• Faceplate View. This is usually the default view. It is larger than the reduced
faceplate, and contains more information and normal operator commands.
The different views are presented in the figures below:
Figure 79. Reduced Faceplate and Faceplate View
3BSE040587-601 129
Faceplate Usage Section 5 Operation
• Extended View. This view usually has two groups of tabs with additional
process information and functionality. 
This view is used to display the maximum amount of information and is
intended for the process engineer or the advanced operator.
The active Faceplate view is indicated at the bottom of the Faceplates, the
corresponding view selection button is pressed. A non-existing view has the
corresponding view selection button disabled.
Figure 80. Extended Faceplate
130 3BSE040587-601
Section 5 Operation Trends
Trends
The Trend Display can present data seamlessly from both run-time and historical
data. When a Trend Display for an object is selected all available data can be viewed
via the trend. This also means that it is possible to move the time range back and
forth without worrying about where data is coming from provided that the seamless
function is enabled in the Trend Display.
The Trend Display can hold a number of Trend Traces and it is possible to trend any
numerical property. It is possible to insert new traces for comparison with the
existing in all trends but the modified trend can only be saved if it is an Operator
Trend.
Functions for rulers, time zooming, magnifying glass etc. are available in the Trend
Display. The time-offset function can be used to trace a signal in real time and
compare it with values from yesterday. It is possible to present trend relationship
between two values as XY plots.
Trend Usage
The two most common ways to access a Trend Display for an object are from a
shortcut in the Application Bar or from the context menu.
3BSE040587-601 131
Trend Usage Section 5 Operation
The Trend Display is divided into three areas: the Trend Area, the Tool Bar and the
Trend Table. See Figure 81.
Trend
Areas
Trend
Tool Bar
Trend
Table
Figure 81. Trend Display
Different tools are provided to be able to modify the view of the traces in a variety
of ways. Examples are: Dragging the Split Bar, which is located between the Tool
Bar and the Trend Table, to desired size. Possibilities to enlarge the Trend Table to
visualize all rows in the Trend Area.
There is also a set of keyboard shortcuts that can be used to modify the Trend Area.
The Trend area is edge (border) sensitive. Clicking in the trend area and drag it over
the grid edge, the Trend Area will starts to scroll in that direction.
Each trace can have its number drawn in the Trend Area to help identify the
different traces. The number can be drawn above, below or centered on the trace.
When right-clicking in the Trend Area a pop-up configuration menu is displayed.
Please note that this also can be configured on the Trend Template.
132 3BSE040587-601
Section 5 Operation Alarm and Event Usage
For more detailed information regarding Trends refer to the System 800xA,
Operations (3BSE036904*).
Alarm and Event Usage

Alarms and events from the process and the control system itself can be viewed and
acted upon in the Operator Workplace via lists, alarm summary indication etc. The
main difference between an alarm and an event is that an alarm normally requires an
action by an operator, e.g. acknowledge. An alarm list only includes the alarms that
an operator needs to pay attention to, normally unacknowledged and still active
alarms. Some alarms may be hidden, which means that they will not be included in
the standard alarm list.
Hidden alarms can still be viewed in the event list. Typically alarms generated as a
consequence of another alarm or other alarms that are irrelevant for the operator in
the current process operation mode may be hidden. 
An event list includes the history for both alarms and events. Alarms or events can
have different priorities that are indicated by different colors in e.g. lists.
Process alarm and event lists can either include all process alarms or alarms for a
specific part of the process down to a single process object.
The following pre-configured lists exist to view different types of alarms and events:
• Process alarm list displaying all process alarms except hidden alarms.
• System alarm list displaying all system alarms for the Compact HMI system.
• Process event list displaying the process event history.
• System event list displaying the system event history.
• Alarm lists on standard process objects displaying the alarms for the object.
• Event lists on standard process objects displaying the event history for the
object.
Process Alarms
Process Alarms are alarms that are generated from the process, such as failure in a
valve or pump or an overpressure in a tank.
3BSE040587-601 133
Alarm and Event Usage Section 5 Operation
Examples of how to access different Alarm Lists are listed below.

• Click on the Process Alarm List button in the Application Bar to see a list of all
process alarms, see Figure 82.
• Click on the Alarm List shortcut in a faceplate to see a list of alarms for a
specific object, see Figure 83.
• Click on an Alarm Band button to see a list of all alarms, Figure 83 for a
specific process area, see Figure 82. For more information about Alarm Band
see Alarm Band on page 136.
• From an Alarm Line in the Application Bar using the context menu (see
Figure 82).
Alarm Line
Alarm Band Button
Alarm List Button
Figure 82. Accessing the Process Alarm List
134 3BSE040587-601
Below an example of a Process Alarm List.
Figure 83. Process Alarm List
Right-click on an alarm line to bring up the context menu. From the context menu
you can perform actions on the alarm, or access any aspect of the object in the alarm
state.
You can acknowledge alarms for an object in the following ways:
• By clicking on the Ack State box for the alarm in the list.
• By right-clicking on an alarm land selecting Acknowledge (all alarms for that
object will be acknowledged) or Acknowledge Selected (only the selected
object will be acknowledged) from the context menu.
• By selecting one or several alarms in the alarm list and clicking the
Acknowledge button (green check mark).
• By clicking on the alarm status button in a faceplate.
3BSE040587-601 135
• By using the Hot Key CTRL+SHIFT+Q (all active alarms will be

acknowledged).
To be allowed to acknowledge an alarm you need to be granted permission for
this operation. Default permission to acknowledge is Operate.
Alarm Band
The Alarm Band provides a link to the Alarm List Display. The number within the
band represents the number of unacknowledged alarms. The color of the band
represent the highest priority alarm present. Click on the Alarm Band (button) to go
to the Alarm List.
Alarm Band
Figure 84. Alarm Band
A red cross over the Alarm Band indicates that the alarm band does not have contact
with any server. If the cross is orange some server providing alarms is not
accessible.
If the button looks like in the figure above (Figure 84), the alarm band has lost
contact with some server (partially connected). In this case it is still possible to for
example make acknowledge.
System Alarms
System Alarms are alarms generated from the Compact HMI System, such as
network problems, file system errors or server errors. In many cases these alarms
need to be taken care of by your system administrator. There are several ways to
access the System Alarm List for an object. The following are some typical
examples:
• from the System Alarms button in the Tool Bar.
136 3BSE040587-601
• from an Alarm Line in the Application Bar using the context menu.
• from an Alarm Band button in the Application Bar (Figure 85).
System Alarm Band
Figure 85. Accessing the System Alarm List
Figure 86. System Alarm List
Process Events
There are several ways to access a Process Event List for an object. The following
are some typical examples that may be configured:
• from an Event Line in the Application Bar using the context menu.
3BSE040587-601 137
• from the Process Events List button in the Tool Bar.
Figure 87. Process Event List
System Events
There are several ways to access a System Event List for an object. The following
are some typical examples that may be configured:
• from an Event Line in the Application Bar using the context menu.
• from the System Event List button in the Tool Bar.
138 3BSE040587-601
Section 6 Administration
This section describes how to add users, make a Backup and Restore and other
system administration and maintenance tasks. Also refer to System 800xA,
Allocating the Functions to the System and the Nodes

Before deploying nodes to a System they should be allocated with the required
functions that define the role they play in a System. Select the node in the System
nodes tab and click Allocate functions to select and allocate the node functions.
Provide any additional node level information needed for the specific function and
click Apply to save the system configuration.
A function allocated to a node cannot be removed once the node is deployed.
Refer the System 800xA 6.0 System Guide Technical Data and Configuration
(3BSE041434*) to know and plan the number of nodes and the functions that can
be deployed.
Deploying Individual or All Nodes in a System

Deploying a System involves deploying of allocated System functions and functions
to nodes which makes the System ready for Engineering and Configuration. Refer
System 800xA 6.0 Post Installation (2PAA111693*) to carry out any further
configuration of the system.
3BSE040587-601 139
Expanding an Existing System Section 6 Administration
Expanding an Existing System

Expansion of a System is supported both at the node level and the System Function
Level. This means an expansion based on System Size and/or functions.
Expansion based on Nodes can be done using the System nodes tab of the
Configure System task. To expand a system by adding new nodes:
1. Prepare and configure the node according to the instructions in Appendix A,
Prerequisites.
2. Launch the preparation tool by starting the 'Setup.exe' from the root level of
the installation media.
3. Go to Configure System > System nodes and click Add node....
4. Enter the node name and select the node type.
5. Go to System functions tab, click Edit functions and add the required system
functions.
6. In the System nodes tab, click Allocate functions to select and allocate the
application and service functions to the node.
7. Click Apply to save the configuration or go to Node actions... and click
Deploy.
Deploying the system might cause the nodes to be rebooted based on the
functions selected.
Expansion based on the 800xA products can be done by allocating new functions to
the System and the nodes. To expand the nodes by adding new system functions to
the existing nodes:
1. Go to System functions tab, click Edit functions and add the required system
functions.
2. In the System nodes tab, click Allocate functions to select and allocate the
application and service functions to the node.
3. Click Apply to save the configuration or go to Node actions... and click
Deploy.
Deploying the system might cause the nodes to be rebooted based on the
functions selected.
140 3BSE040587-601
Section 6 Administration Excluding a Node
Ensure that there are no reserved entities in a system before deploying the system
with new System functions. Use the Find Tool to identify the reserved entities
f
and release them. Refer System 800xA Operations 6.0 Operator Workplace
Configuration (3BSE030322*) manual for more information.
Excluding a Node
It might be needed to exclude a node or nodes from being deployed either because:
• It is disconnected from the system
• Is in an error state
• The user does not want to deploy on a particular node.
It is possible to exclude the erroneous node and continue the system deploy process.
A node can be excluded only if it is not already deployed.
It is highly recommended to include all the nodes for a system to be fully
deployed.
Replacing a Node
A node can be replaced by using the Replace node button. It can be used to redeploy
nodes that for example:
• have become corrupt
• have hardware issues.
Replacing a node will reset the node's installation status but it will retain its
configuration (the configured Node Functions and their property values). Once the
replace node process has been initiated, the node status will change to “Needs
Redeploy”.
When a node is replaced, the replacement node needs to have the same computer
name and network configuration.
To replace a node:
1. Restore the faulty node to a clean Windows installation. Prepare it according to
the instructions in Appendix A, Prerequisites.
3BSE040587-601 141
Adding and/or Removing a Node Section 6 Administration
2. Ensure that it has the same computer name and network configuration as
earlier.
3. Run the Node Preparation Tool on it.
4. Go to the node where the deploy was initiated and from the System nodes tab
of the Configure System task, and click on Replace node command on the
node. Once completed, the node's status will be 'Needs Redeploy'
5. Click the Deploy command to install the configuration on the node once again.
6. The node will have the same configuration installed as previously.
Adding and/or Removing a Node

Adding a node to the system makes it possible to allocate functions to the node and
deploy. Use System nodes tab of the Configure System task in the SCC to add a
node and allocate the functions to the node. To deploy a node ensure that the status
of the node is shown as Connected in the System nodes tab.
A node may be removed when reducing the system footprint. Use the Remove node
function from the System nodes tab of the Configure System task to remove a node
and deploy for the change to take effect.
Removing the node from the system causes all the configuration data on the node
to be removed as well.
Once removed the node can no longer connect to the system. To reconnect the node
to the system the node must be prepared, added and the functions allocated to the
node.
Importing and Exporting of Configurations

This saves information about nodes, configured functions and so on to a text file that
can be used for configuring other systems
The Configure System task creates and configures aspects and objects in the
system. Modifying these aspects and objects manually is not allowed and might
cause inconsistencies in the system.
142 3BSE040587-601
Section 6 Administration Excluding a Node before Deploy
Excluding a Node before Deploy

To exclude a node before initiating the deploy phase:
1. Go to the Node functions tab in the SCC.
2. Select the node to be excluded and click on Exclusions... in the Node actions...
button.
3. Follow the screen prompts to complete the node exclusion.
Once the excluded node is available, it can be deployed at a later stage by the user.
Excluding a Node during Deploy

A node might have to be excluded during the deploy phase if the node has failed. To
exclude a node during the deploy phase:
1. Abort the deploy.
2. Go to the Node functions tab in the SCC.
3. Select the node to be excluded and click on Exclusions... in the Node actions...
button.
4. Follow the screen prompts to complete the node exclusion
Once the erroneous node has been excluded and the deploy process is complete on
the other nodes in the system. Follow the procedure as documented in the section
Replacing a Node on page 141 to make an excluded node operable again.
3BSE040587-601 143
Adding New Users Section 6 Administration
Adding New Users

The Compact HMI product is set up to run in Workgroup in Windows.
To add a new user to the Compact HMI after it has been created in Windows, follow
the steps below:
All Users and groups has to be created in all the Compact HMI nodes with the
same spelling and passwords
2. Select ABB Start Menu> ABB Industrial IT 800xA > System > System
Configuration Console to start the System Config Console.
Figure 88. System Configuration Console
3. Click Users.
4. Click Users.
5. Click Add a new User.
144 3BSE040587-601
Section 6 Administration Adding New Users
Figure 89. Adding a new user
6. In User Information, select the user to be added.

7. Select the corresponding user group checkboxes, to which the user should
belong to.
8. Click Apply.
9. Repeat Step 5 to Step 8 for all users to be added.
The Windows user must be a member of the Industrial IT User group to use the
Compact HMI.
3BSE040587-601 145
Backup and Restore Section 6 Administration
Backup and Restore

It is recommended that the Compact HMI server is equipped with two hard drives,
one that is used for the runtime data of the system (disk C), and the other for
backups (disk D).
System Backups are configured as full backups of the Compact HMI system and are
scheduled to be executed once a week. The backup images are saved by default on
the drive C. It is recommended to change this setting to the D disk if available. this
can be done in the Storage tab in the Backup definition aspect described in the next
chapter.
Backup and Restore of Configuration Data

To backup the configuration data of the system follow the steps below. Note that the
data for the applications that are not integrated in the system, needs to be backed up
separately.
2. In the Maintenance Structure, expand the object backup definitions. Select the
Backup definition aspect as shown in Figure 90.
Figure 90. Plant Explorer Workplace - Maintenance Structure
146 3BSE040587-601
Section 6 Administration Backup and Restore of Configuration Data
3. Select the Summary tab and click Start Backup to start the backup procedure.
4. Click OK to start the backup. This also displays the status of the backup
process.
Restore System
To restore the system go through the following steps.
1. In the Configuration Wizard, select Restore System and click Next.
2. If the backup does not show up in the window, click select Path, and add, and
then browse to the folder shown below.
Figure 91. Backup Folder
3. Click OK to proceed.
4. Select the backup and click Next. (If the change of Computer Name has been
done before the system has been configured, use the restore dump available on
the DVD supplied in the Compact HMI delivery (another path needs to be
added)).
5. Select Generate New System ID and enter the system name. For example,
HMI Server55 System and click Next.
3BSE040587-601 147
Store Controller Application in the System Section 6 Administration
Figure 92. System Directories Selection
6. Click Next and then click Finish.

7. Wait until the restore is complete and then click Exit.
Store Controller Application in the System

To include controller configuration data, or other type of information in the
automatic system backup, the data can be stored in the File Viewer Aspects.
To do this follow the steps below:
1. Create a zip-file containing all files included in the controller application.
2. Log in as user AppEng and open the Plant Explorer.
3. Select an object that represents the part of the plant that the control application
covers. For example, a plant section object in the Functional Structure.
4. Right-click the object and select New Aspect.
148 3BSE040587-601
Section 6 Administration Other Maintenance
5. Select the File Viewer aspect and enter a name. For example, Control
Application 1.3-2006-05-23.
6. Right-click the selected aspect and select Config View.
7. Click Attach in the Public Document part of the window, and browse to the
newly created zip-file. Select the file and click Open.
8. The file is now stored in the system and will be part of any future system
backup.
Other Maintenance
To Stop and Start the System
The Compact HMI server nodes contains a set of software services that are running
continuously in the background in the computer. These services are often referred to
as the system or Compact HMI system. During some maintenance activities it is
necessary to stop and start these services. This is described below. When switching
on the power to a Compact HMI server the system is automatically started.
Stop System
To stop the system without switching off the power follow these steps:
3BSE040587-601 149
To Stop and Start the System Section 6 Administration
2. Open the Configuration Wizard (ABB Start Menu> ABB Industrial IT

800xA > System > Configuration Wizard).
Figure 93. Configuration Wizard Main View
3. In the dialog above select System Administration.

4. Then click Next and Next again.
150 3BSE040587-601
Section 6 Administration To Stop and Start the System
5. In the window below select Systems and press Next.
Figure 94. Select Systems
6. Select Stop and press Next and then Finish.

7. Wait until the system has stopped. (the dialog in step 2 shows up).
Start System
To start the system without switching off and on the power follow these steps:
2. Open the Configuration Wizard (ABB Start Menu> ABB Industrial IT
800xA > System > Configuration Wizard).
3. In the dialog above select System Administration.
4. Then click Next and Next again.
5. In the window below select Systems and press Next.
6. Select Start and press Next and then Finish.
3BSE040587-601 151
Autonomous Redundancy Setup Section 6 Administration
7. Wait until the system has started. (The dialog in Step 2 is displayed).
Autonomous Redundancy Setup

Compact HMI supports an autonomous redundancy scheme. This means that two
Compact HMI systems are running in parallel accessing the same controllers. One
of the systems are considered to be the main system and the second is the backup
system.
All configuration changes should be done in the main system and then transferred to
the backup system by using the system backup function.
The setup of an autonomous redundancy configuration is done by the following
main steps:
1. Make a system backup of the configuration in the main system.
2. Install another set nodes with a Compact HMI system, with other node names
and IP addresses. If needed change the windows computer names and IP
addresses in the backup system, including restore of the backup created in 
Step 1.
Step 1 and Step 2 are described in more detail in the chapters Backup and Restore of
Configuration Data on page 146 and Change the Windows Computer Name in the
Server Node on page 152.
Change the Windows Computer Name in the Server Node

To change the Windows Computer Name of the Compact HMI Server node after
installation and configuration, please go through the following steps:
1. Make an image backup of the node, using the Norton Ghost or similar software
2. Make a system backup (will be restored in a later step) as described in Backup
and Restore of Configuration Data on page 146.
4. Stop the system as described in To Stop and Start the System on page 149.
152 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Server Node
5. Delete the system, by opening the Configuration Wizard (ABB Start Menu >
ABB Industrial IT 800xA > System > Configuration Wizard).
Figure 95. Select Type of Configuration
6. Select System Administration and click Next, and then Next again.
7. Select System Start, Stop or Delete and press Next.
8. Select Delete System on a Node and click Next.
9. Be aware of that all configuration data will be lost if you proceed and has not
done step 1 and 2.
10. Click Next and Finish.
11. Now wait until the system has been deleted (the dialog in step 6 shows up, with
some fewer options), then Exit the Configuration Wizard.
12. Restart the computer and log in as SysAdmin.
3BSE040587-601 153
Change the Windows Computer Name in the Server Node Section 6 Administration
13. Now change the Windows Computer Name and if needed the IP address of the
computer. Remember to update the Host file (in both server and clients).
(“C:\WINDOWS\system32\drivers\etc\hosts”).
14. The server address for the license system has to be adjusted. To do this open
ABB Start Menu> ABB Industrial IT 800xA > System > Licensing >
License Status Viewer.
15. Select Tools > Change CLS Machine, to get the dialog below.
Figure 96. Change CLS Machine
16. Enter the new name e.g. “HMI-Server55” and press Apply and exit the License
Status Viewer.
17. Restart the computer and log in as SysAdmin.
18. If you are using the AC 800M OPC server, open the OPC server configuration
dialog and disconnect and connect each of the controllers once. After this save
the configuration.
19. If you are setting up an autonomous redundant backup system (otherwise skip
this step) please copy the backup files from the main system server (typically
from folder located on "Backup Disc:\Backup" in the server workplace) to the
backup system server (same location).
20. Open the Configuration Wizard and select Restore System and click Next.
154 3BSE040587-601
21. If the backup shows up in the window go to step 22. If the backup does not
show up in the window, click select Path and add, and then browse to the folder
shown below.
Figure 97. Backup Folder
22. Click OK and then OK again.

23. Select the backup that was done in Step 2 (or that was copied from the main
system, if you are setting up an autonomous redundant backup system), and
click Next. (If the change of Computer Name is done before the system has
been configured, use the restore dump available on the DVD supplied in the
Compact HMI delivery (another path needs to be added)).
24. Now select Generate New System ID and enter the system name e.g. “HMI
Server55 System” and press Next.
3BSE040587-601 155
Figure 98. System Directories Selection
25. Press Next in the dialog below, and then Finish.

26. Wait until the restore is complete and the press Exit.
27. After restoring the backup the systems references to the OPC servers should be
reconfigured to make sure that the correct OPC servers are used. To do this
follow steps a-e below, for each OPC server.
a. Open Plant Explorer and go to the Control Structure.
156 3BSE040587-601
b. Click on each of the objects of the type PLC Controller Type and select
the PLC controller configuration aspect as shown in the figure below.
Figure 99. OPC reconfiguration
3BSE040587-601 157
c. Click the Edit Driver button and the dialog in the figure below is
displayed.
Figure 100. Communication parameters
d. Click the Update button and select the OPC server to be used as shown
above.
e. Click OK and then Apply to save the new configuration.
28. Select the object PLC Connect Servers and the Deploy aspect.
29. Click Deploy.
30. When deploy has ended, the Node name change for the server is completed.
31. If clients are connected to the server each client needs to be updated as
described in the following four steps:
a. Log in as SysAdmin in the Client.
b. Open the Hosts file using Notepad and update the file with the new name
of the server.
c. Restart the client.
d. Connect the client to the system server as described in Connect and
Disconnect Client Nodes on page 159.
158 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Client Node
Change the Windows Computer Name in the Client Node

To change the Windows Computer Name of a Compact HMI Client node please go
through the following steps
2. Disconnect the client form the servers as described in chapter Connect and
Disconnect Client Nodes on page 159.
3. Change the Computer Name and or IP address of the client.
4. Update the Hosts file in the client and the server with the changes
(“C:\WINDOWS\system32\drivers\etc\hosts”).
5. Remember that if the name of the server has been changed, the License Status
Viewer should be opened, and the CLS machine be changed.
6. Connect the client to the server as described in chapter Connect and Disconnect
Client Nodes on page 159.
7. The node name change of the client is now ready.
Connect and Disconnect Client Nodes

Client nodes have to be connected to the system. This is done in the following steps:
1. Connect the client node to the network.
2. Log in on the server node as SwServiceAccount.
3. Start the System Configuration Console.
4. Select System Setup and click Configure System.
5. Select System nodes tab.
6. Click on Add node.
3BSE040587-601 159
Connect and Disconnect Client Nodes Section 6 Administration
7. In the dialog shown below select the client to be added e.g. HMI-Client01.
Figure 101. Add a Client Node
8. Click OK and then click on deploy system.
Disconnect a Client
To Disconnect a client from a system go through step 1-5 above, and then continue
with these steps:
1. Select Client node and click Remove node.
2. In the dialog below select the client to be removed.
160 3BSE040587-601
Section 6 Administration Defragmentation
Figure 102. Remove a Client Node
3. If the client exists on the network, keep the switch Update Node selected. If the
client is not available on the network remove the switch.
4. Click Next and then Finish.
5. The client has now been removed.
Defragmentation
Defragment the hard drive regularly. This helps keeping the good performance of
your computer.
Virus
Do not connect the computers directly to the internet. The computers must be
protected behind a hardware firewall. Refer to the section about computer security
in the System 800xA, Administration and Security (3BSE037410*) instruction.
3BSE040587-601 161
Windows Update Section 6 Administration
Windows Update
Update Windows regularly. This helps keeping the good performance of your
computer and the stability of your software.
This must be done in a secure manner, as recommended below.
The system administrator or a central engineering department can make the updates
available on a dedicated distribution server on the office or corporate network by
installing them from CD/DVD, or by downloading them from a trusted server e.g.
on the Internet.
Save of OPC IP Address for PLC Connect

Open the OPC server interface and connect your PLCs in the Add Your PLCs.
When all PLCs are connected and the communication is verified, click File and
Save configuration. To enable the Autostart, click Settings and Autoload
Configuration. When the pop-up window shows up, check the Enable Autoload
Configuration check box, and use the browse interface to locate your saved
configuration. All your PLCs are now stored in a file, that is pre-loaded in the OPC-
server at computer startup.
Using Virus Protection with Compact HMI

The description below shows an example of how to set-up virus scan software for
the Compact HMI product. In this example the McAffe software has been used, but
other virus scan products can also be used with Compact HMI by configuring the
relevant functions in the way described in this chapter.
All computer systems should be scanned for viruses at regular intervals. A reputable
and reliable virus scanner should be used and updated regularly. However, when a
virus is found, damage may already have been done. For a mission critical system it
is therefore more important to effectively prevent viruses from being introduced into
the system than to frequent run virus scans.
Virus checking affects the performance and response times of any computer system.
For an automation system such as Compact HMI, where real-time performance and
reaction times must not be compromised, the impact of virus checking must be
limited. This can be accomplished by excluding certain frequently accessed
directories and file types from on-access scanning, and by running on-demand
scanning of excluded files at times when normal system activity is low.
162 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
This section describes how McAfee VirusScan® Enterprise can be configured to

avoid interference with the Compact HMI operation.
Configuration Settings
McAfee VirusScan® Enterprise can be configured for on-access and on-demand
virus scanning.
• On-access scanning is automatically activated at system startup and will check
files as they are accessed. To prevent this from causing performance
degradation, folders containing files that are frequently accessed need to be
excluded from on-access scanning.
• On-demand scanning can be configured to run cyclically at predetermined
times or intervals, or be manually initiated. All files that are excluded from on-
access scanning should be scanned on-demand at regular intervals. However,
since this scanning will impact system performance and reaction times, it
should be done when normal system activity is low.
This section describes the specific VirusScan configuration setting that need to be
made. All other settings should be left at their defaults.
Some of the VirusScan configuration settings require that the computer is
restarted before the changes take effect.
3BSE040587-601 163
Using Virus Protection with Compact HMI Section 6 Administration
On-access Scanning
General Settings. Below the General tab, deselect the Processes on enable check
box. Select Disabled in the Sensitivity level drop-down menu1.
Figure 103. General Settings - General Tab
1. If enabled, when this feature detects a suspicious file it will send a DNS request containing a fingerprint of the
suspicious file to McAfee Avert Labs, which then communicates the appropriate action back to VirusScan
Enterprise 8.7i. This behavior may cause problems in a Compact HMI system.
164 3BSE040587-601
Below the Messages tab, deselect the Delete files check box in the Actions
available to user area.
Figure 104. General Settings - Messages Tab
3BSE040587-601 165
Default Processes Settings.

Below the Processes tab select the Configure different scanning policies for high-
risk, low-risk and default processes radio button.
Figure 105. Default Processes - Processes Tab
166 3BSE040587-601
Below the Scan Items tab click the Additions button.
Figure 106. Default Processes - Scan Items Tab
3BSE040587-601 167
In the Additional File Types dialog box, add the AFW file type in the User-
specified additional file types area. Click OK.
Figure 107. Additional File Types Dialog Box
Below the Exclusions tab click the button Exclusions. A list of disks, files and
folders that are excluded from on-access scanning is presented.
To add items to the list, click Add … and fill in relevant folders, files, and file types
The items that need to be excluded depend on which products are installed. A list
is provided in Folders Excluded from On-access Scanning on page 180.
The file types LDF, MDF, and NDF are related to SQL Server and should be
excluded from scanning. Scanning these files may under certain circumstances
cause a deadlock, see Microsoft KB 309422.
168 3BSE040587-601
Figure 108. Set Exclusions Dialog Box
For each item that is added, select Also exclude subfolders, On read, and On
write, as shown in Figure 109.
Figure 109. Add Exclusion Item
3BSE040587-601 169
Below the Actions tab make the settings shown in Figure 110.
Figure 110. Default Processes - Actions Tab
Settings for Low Risk Processes. Add the Compact HMI system function
Afwworkplaceapplication.exe to the list of low risk processes1.
1. Certain low risk processes may already be listed as defaults by McAfee. These can be left as is.
170 3BSE040587-601
Figure 111. Add Afwworkplaceapplication.exe
Apply the same settings below the Scan Items tab as were made for default
processes (see Figure 106).
Apply the same settings below the Exclusions tab as were made for the default
processes. In addition, exclude the following folder:
\Program Files\ABB Industrial IT\Operate IT\Process Portal A\bin
Apply the same settings below the Actions tab that were made for default processes.
Settings for High Risk Processes. Apply the same settings below the Scan Items
tab as were made for default processes (see Figure 106).
Apply the same settings below the Exclusions tab as were made for the default
processes.
Apply the same settings below the Actions tab that were made for default processes.
3BSE040587-601 171
Additional Exclusions for Windows Domain Controller. In order to avoid serious

performance problems due to file locking, McAfee and Microsoft provide
recommendations regarding exclusions for computers that run the Windows Server
2003 or Windows 2000 domain controller. In an Compact HMI system this applies
to Domain Servers or, in configurations where Aspect and Domain Server functions
are combined in the same server, to Aspect Servers.
For information about these exclusions, please refer to the Microsoft knowledge
base article KB822158.
On-demand Scanning
The folders that are excluded from on-access scanning should be scanned regularly,
either at scheduled intervals, or manually initiated. Note that scanning these folders
will impact system performance and reaction times; it should therefore be done
when normal system activity is low.
In applications where it is not possible to select a regular time when on-demand
scanning can be done without disturbing operation of the system, there should be
procedures for manually initiating the scanning as often as practical.
The default setting for on-demand scanning is to include all local drives. However,
the time to complete the scanning with this setting can be excessive. In order to
minimize this time, scanning could alternatively be limited to those items that are
excluded from on-access scanning.
172 3BSE040587-601
To configure on-demand scanning, right-click on the VirusScan icon in the system

tray. Select On-Demand Scan, and select on the Scan Locations:
Figure 112. Scan Locations Tab
To remove locations for on-demand scanning, click Remove, to add items, click
Add.
At least all items excluded from on-access scanning should be covered by on-
demand scanning (except file types MDF, LDF, and NDF, see below).
Make sure that the scan options Include subfolders and Scan boot sectors are
selected.
3BSE040587-601 173
To specify a schedule, click on Schedule. Select the Scan Item tab and make the
selections shown in Figure 113.
Figure 113. Scan Items Tab
Select the Exclusions tab and click Exclusions … and add the file types LDF, MDF,
and NDF. These file types are related to SQL Server and should be excluded also
from on-demand scanning. Scanning these files may under certain circumstances
cause a deadlock, see Microsoft KB 309422.
174 3BSE040587-601
Figure 114. Set Exclusions Dialog Box
Select the Performance to limit the performance impact from on-demand scanning,
The optimal value for this setting is installation specific and depends on many
factors, including the system configuration and load, the application, and the
operating conditions during the on-demand scanning. The value shown in Figure
13 is intended as guidance only. Try out a value that allows the scanning to finish
within an acceptable amount of time while keeping the impact on system
performance and reaction times at a level that is tolerable.
Select Disabled in the Sensitivity level drop-down menu1.
1. If enabled, when this feature detects a suspicious file it will send a DNS request containing a fingerprint of the
suspicious file to McAfee Avert Labs, which then communicates the appropriate action back to VirusScan
Enterprise 8.7i. This behavior may cause problems in a Compact HMI system.
3BSE040587-601 175
Figure 115. Performance Tab
176 3BSE040587-601
Select the Actions tab and make the settings shown in Figure 116.
Figure 116. Actions Tab
Recovery from a Virus Infection

The security policy for the Compact HMI installation should include procedures for
recovery from a virus infection, and these procedures should be well known by all
operating personnel.
On-demand scanning includes Compact HMI system files. Automatically deleting
or moving these files could lead to system malfunction or failure. Instead, manual
action is required as described below.
There is no simple way to determine which files can be safely moved or deleted
without causing problems in the Compact HMI system. Hence, if VirusScan reports
an infected file that can not be cleaned, the following procedure is recommended:
3BSE040587-601 177
1. If the infected node is critical for the operation of the system, stop the system in
a controlled way. Nodes that are critical should be clearly identified in the
security policy (examples are non-redundant Aspect or Connectivity Servers,
however, this is highly application dependent).
2. Disconnect the infected node from all networks.
3. Restore the infected node from a disk image if available, or re-install from
scratch (see the section about Node Replacement in System 800xA,
4. Verify that the node is no longer infected by running a complete virus scan.
5. Reconnect the node to the network and restart it.
If a virus is found on one node, it is likely that also other nodes are infected. An
on-demand scanning of all nodes is therefore recommended.
Access Protection
Messaging function in System 800xA. In systems where this function is used, the
process AdvMsgEngine.exe therefore needs to be added to the Excluded Processes
list on the server where the Messenger Service runs (normally the Aspect Server).
Open the VirusScan console, right-click on Access Protection and select
Properties.
Figure 117. Virus Scan Console
178 3BSE040587-601
Select the Access Protection tab, then select Prevent mass mailing worms from
sending mail (Port 25) and click Edit…:
Figure 118. Access Protection Properties
In the Processes to exclude area add AdvMsgEngine.exe to the list (separated from
other items by a comma).
3BSE040587-601 179
Figure 119. Rule Details
Click OK twice, and then close the VirusScan Console. SMS & e-mail Messaging
can now send e-mails.
AutoUpdate
AutoUpdate is a feature that can be used to ensure that the latest McAfee virus
definitions are downloaded and installed on every machine. However, this feature
requires a direct connection between the automation system network and the
Internet. Enabling AutoUpdate on hosts connected to the automation system
network is therefore not a recommended practice.
For a more secure and reliable deployment of virus definitions, a central
management and update deployment host can be set up on a corporate intranet. This
allows a system administrator to have control over when updates are made, and an
opportunity to test the updates before they are deployed. The white paper "IS
Security Considerations for Automation Systems" (3BSE032547) provides general
guidelines for how this could be arranged.
Folders Excluded from On-access Scanning

The folders and file types that need to be excluded from on-access scanning depend
on which Base products are installed.
180 3BSE040587-601
The tests were run using the following exclusions:
Table 6. Folders Excluded from On-access Scanning
Product Path
800xA Base System <drive>:\OperateITData*\
<drive>:\OperateITTemp*\
<drive>:\Program Files\ABB Industrial IT\Operate IT\Process Portal
A\AppLog\
<drive>:\Program Files\ABB Industrial IT\Operate IT\Process Portal A\bin\
(for low risk processes only)
File types MDF, LDF, NDF (exclude also from on-demand scanning)
Engineering Studio <drive>:\Program Files\Common Files\ABB Industrial IT\
MSSQL$EBINSTANCE\Data\
Control IT <drive>:\ABB Industrial IT Data\
3BSE040587-601 181
182 3BSE040587-601
Section 7 Using the PLC Device Library
PLC Device Library has a number of predefined object types for motors, valves,
PID, analog types, binary types, etc. with predefined process graphics such as
faceplates, alarm lists and signal lists to facilitate connections to different PLC's.
Information on how to create graphics in general is described in the System 800xA,
Engineering, Process Graphics (3BSE049230*) instruction, which can be found in
ABB Start Menu> ABB Industrial IT 800xA > Engineering.
3BSE040587-601 183
Section 7 Using the PLC Device Library
Figure 120. PLC Device Library
It is also possible to create your own defined objects, see Working with Object
Types on page 73.
The following chapter describes how to create graphic displays by using the
predefined graphic elements and object types in the PLC Device Library.
184 3BSE040587-601
Section 7 Using the PLC Device Library Creating PLC Device Library Instances
The example below will create a graphic display containing a tank, pipes, valves and
a motor representing a chemical process.
To instantiate the different types a PLC Generic Control Connection object is
needed in the Control Structure. This is described in the Installation and
Configuration of OPC Servers for PLCs on page 67 and in Creating the Device
Object Instances on page 83.
Creating PLC Device Library Instances

In the PLC Controller Type object, create the instances needed for this example.
1. Select the PLC Generic Control Network object and select the Generic Control
Network Configuration aspect
2. Click on the New Object icon, see Figure 121.
3BSE040587-601 185
Creating PLC Device Library Instances Section 7 Using the PLC Device Library
Figure 121. New Object Icon
3. In the Create New Object dialog select the VALVtype, the controller and enter
a name for the valve instance. In this case create only one instance even though
it is possible to create several instances at one time.
186 3BSE040587-601
Figure 122. Create New Object
4. Repeat Step 3 for the motor (MOTtype).
3BSE040587-601 187
Figure 123. Motor Object
188 3BSE040587-601
5. Connect the signals for the motor and the valve. The main parameters for the
PLC Device objects are described in the Data Sheet aspect for the represented
object as shown in Figure 124.
Figure 124. Data Sheet
6. Select each of the signal objects in the motor and the valve that has a
representation in the OPC server and select the Signal Configuration aspect.
3BSE040587-601 189
Figure 125. Signal Configuration Aspect
7. To connect the signal, select the Connected radio button and then click Browse
to open the OPC Browser dialog and connect the signals according to the signal
data sheet for the type.
190 3BSE040587-601
Figure 126. OPC Browser
8. Click Apply and click Apply in the aspect.

9. Repeat Step 7 and 8 for each signal necessary.
10. Deploy the configuration by selecting the PLC Generic Control Network object
and select the Deploy aspect. See Figure 127.
3BSE040587-601 191
Creating the Display Section 7 Using the PLC Device Library
Figure 127. Deploy Aspect
The motor and the valve are now configured and deployed and are now ready to be
used in a graphic display.
Creating the Display

1. Open the Plant Explorer and expand the Functional Structure.
2. Select the object where the display shall be located and create an aspect of the
type Graphic Display PG2.
3. Open the Process Graphics Editor by right-clicking on the newly created aspect
and select Edit.
192 3BSE040587-601
Section 7 Using the PLC Device Library Creating the Display
4. Create a tank element by selecting the tank body, tank neck and tank bottom
element from the Shapes toolbox. Also add pipes using the flexible pipes
element.
Figure 128. Process Graphics Editor
5. In the toolbox, select the Element Explorer and browse to the Control Structure
and the motor and the valve created in the previous example.
6. Select the Display Element Reduced Icon for the motor and the valve to insert
them into the display.
3BSE040587-601 193
Figure 129. Display Element Reduced Icon
7. Click Save, and the display is ready for operation, as shown in Figure 130.
194 3BSE040587-601
Section 7 Using the PLC Device Library Creating the Display
Figure 130. Graphic Display
3BSE040587-601 195
196 3BSE040587-601
Appendix A Prerequisites Windows Operating System
Appendix A Prerequisites
The user performing the procedures in this section must be proficient in the use of
Windows Operating Systems. This section may not include detailed procedures
on how to perform the described settings.
There may be differences in accessing the Microsoft Operating System settings
described in this section depending on the selected operating system. It is the
responsibility of the user to consult Microsoft documentation and online help to
accurately make the settings.
Use the System 800xA 6.0 System Planning (3BSE041389*) document to help
plan the requirements, both hardware and software, for the 800xA System.
This section lists the prerequisites required to configure a node for an 800xA
System.
It is recommended to make a full backup of all disks. With such a backup all work
will be saved in the event of a disk crash or other serious malfunction. Make sure
to place proper identification on the backup media or backup files.
Install optional hardware drivers if not supplied by the Windows Operating
System (video card, network adapter, sound card, etc.).
Windows Operating System

This section describes:
• Selecting the Windows Operating System.
• Considerations for Disks and File System.
• Windows Installation Guidelines.
• Windows Operating System Updates.
Selecting the Windows Operating System

System 800xA 6.0 version runs only on 64-bit (x64) operating systems.
3BSE040587-601 197
Considerations for Disks and File System Appendix A Prerequisites
The supported operating systems, service packs, and hot fixes are listed in System
800xA 6.0, 5.1, 5.0, 4.x, 3.1 Third Party Software (3BUA000500). For security
updates refer System 800xA - Third Party Security Updates Validation Status
(3BSE041902). These documents can be found in ABB SolutionsBank.
The US English version of the operating system is required even if a translation
NLS package for System 800xA is used.
The following conditions affect the decision on which operating system to use:
• Server roles can be allocated to nodes running either a workstation or server
operating system of Windows. Using workstation operating system helps in
keeping the cost down for smaller installations. Refer to the System 800xA 6.0
System Guide Technical Data and Configuration (3BSE041434*) for rules that
apply in selecting the type of Operating System.
• There are limitations on number of nodes used in the system when using the
Workstation Operating System for Server nodes. These limitations depend on
Microsoft licensing rules for the Workstation Operating System. Refer to
System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for the details on the limitations.
• The Windows Operating System may be purchased from any Microsoft
reseller.
• The nodes with pre-installed operating system shall be checked and configured
as per the system 800xA specifications.
Considerations for Disks and File System

There are several factors that may have an impact on 800xA System performance,
for example: where the software is installed, the tendency toward fragmentation.
The following are some recommendations regarding these factors:
Multiple Disks and Partitions

Some types of 800xA servers can use significant disk I/O. Creating partitions that
are hosted by different disks or disk arrays can improve performance for these
servers. Aspect Servers, Connectivity Servers, Information Management Servers
and Batch Servers can benefit from additional partitions when configuration data is
distributed over multiple partitions that are hosted by separate disks or disk arrays.
198 3BSE040587-601
Appendix A Prerequisites Considerations for Disks and File System
At least two of these partitions are recommended for Information Management

Servers. See the System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for specific details for Information Management and other server
types.
Installation Directory
It is generally recommended to use the Windows default location, the program files
directory on the boot disk, for installation.
A faster disk subsystem will improve performance.
Defragmenting Disks
The file system must be in a consistent state at all times. Size disks so they will be
25 percent empty for defragmentation purposes. Defragment disks on a regular basis
using the defragmentation software provided with the operating system. Check the
system for fragmented files and defragment them as required:
• On all nodes where trend and history logs reside.
• History Server disks and disks on the Connectivity Servers where trend or
history logs reside as History configuration impacts not only the History Server
disks.
• Extensive use of the Bulk Configuration tool may cause associated disks to
become fragmented.
• Configuration procedures that involve creating, deleting, and then recreating of
a large quantity of objects may cause associated disks to become fragmented.
• Deleting and then creating the Aspect System may cause associated disks to
become fragmented.
3BSE040587-601 199
Windows Installation Guidelines Appendix A Prerequisites
Windows Installation Guidelines

Make a fresh installation of the Windows Operating System.
Before adding applicable service packs, it is important that all the latest device
drivers are installed to match the hardware. This is especially important for elite
server hardware with special RAID hard drives and server specific hardware that
requires the latest drivers or drivers not included in the operating system media.
Follow the installation procedure as described in the documentation provided by
Microsoft.
Table 7 indicates the settings specifically required for the 800xA System
installation.
Table 7. Windows Installation Requirements
Step Description
Choosing a partition for It is recommended that all server nodes (Aspect Directory, Connectivity
installing the operating Servers, Applications Servers, etc.) use at least one additional partition for
system. the operateITData and operateITTemp folders. For best performance, the
additional partition should be on a separate disk or disk array from the
operating system.
There may be additional disk requirements for Applications Servers. If
installing the Information Management Server function on this node, at
least one additional NTFS partition is needed for storing historical data.
This partition can be the same as the operateITData and operateITTemp
partition or be a separate partition. The amount of disks, disk space, and
disk I/O needed for the Information Management node are dependent on
the final configuration for the node.
To maximize the performance for any server, any additional partitions
should be a separate disk or disk array from the root partition.
Selecting Regional Refer to Regional and Language Options on page 223.
Settings
Time Zone Make sure the Automatically adjust clock for daylight saving changes
check box is enabled (if daylight saving time is used).
200 3BSE040587-601
Appendix A Prerequisites Windows Operating System Updates
Windows Operating System Updates

Install Windows hot fixes, and Security Updates approved by ABB (refer to Third
Party Software System 800xA (3BUA000500) and System 800xA Third Party
Security Validation Status (3BSE041902) after installing other third party software.
ABB System 800xA Qualified Security Updates (9ARD183777*) can be used to
install the latest qualified security updates. The tool and the document are accessible
from ABB SolutionBank.
The Windows Operating System Updates (Service Packs, Feature Packs) must be
installed immediately after installing the operating system, and before performing
any other procedures in this instruction.
Configuring Network Adapters

If the Network Adapter supports Receive Side Scaling this feature must be
disabled. Refer to the Network Adapter documentation for information on how to
disable the feature.
Network adapters must be installed and configured to support communication on
the client/server network. This is required on the Domain Server node, and all
800xA System nodes. Typically one network adapter will be provided with the
server or workstation hardware. It may be necessary to install a second network
adapter for redundancy.
All network adapters may be installed and configured at the same time during
system installation; however, the network will not run with redundancy until
Redundant Network Routing Protocol (RNRP) is installed (refer to Product
Installation section for a separate Domain Server node).
If the network adapters are not plug-and-play devices, the installation must be done
manually. If the Windows installation does not include the drivers for the network
adapters the driver software must be installed before the network adapters can be
configured.
The 800xA System relies on TCP/IP as its transport protocol. It is strongly
recommended that TCP/IP is the only protocol in use. If other protocols need to
be installed, make sure that TCP/IP is configured as the primary protocol.
3BSE040587-601 201
Configuring Network Adapters Appendix A Prerequisites
Refer to Windows Help > Networking for more information on how to install and
configure TCP/IP network adapters.
Refer to System 800xA Network Configuration (3BSE034463*) for configuration
of DNS.
The following procedure applies to the Workstation Operating System nodes. The
procedure for the Server Operating System nodes may vary from the one shown
here.
To configure the network adapters:
1. Open Windows Control Panel.
2. Double-click Network and Sharing Center to open the Network and Sharing
Center.
3. Click Change Adapter Settings.
4. Right-click on the network adapter and select Properties from the context
menu to open the Connection Properties dialog box.
5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties to open
the Internet Protocol (TCP/IP) Properties dialog box.
6. Select Use the following IP address.
7. Enter the IP address in the IP address and the subnet mask in the Subnet fields
according to the planning done in Installation and Configuration Parameter
Worksheet.
8. Enter the IP address of the default gateway in the Default gateway field (if
required by topology).
9. Enter the IP address of the Primary Domain Server in the Preferred DNS
server field.
10. Enter the IP address of the Secondary Domain Server in the Alternate DNS
server field.
Always specify the Domain Servers with their primary client/server network
addresses. This is true for all network adapters, including the ones for secondary
client/server networks.
202 3BSE040587-601
Appendix A Prerequisites Configuring Network Adapters
11. Repeat for all network adapters in the servers and workstations.
Use the same DNS settings for all network adapters.
12. For all interfaces on separate Control Networks three configuration changes
(compared to the default settings) must be done to reduce the amount of traffic
on the Control Network.
a. Disable IPv6 by clearing the check box Internet Protocol Version 6
(TCP/IPv6).
b. Click Properties in the Internet Protocol (TCP/IP) Properties dialog to
open the Advanced TCP/IP settings dialog.
c. Click the DNS tab.
d. Clear the check box Register this connection's addresses in DNS.
e. Click the WINS tab.
f. Select Disable NetBIOS over TCP/IP.
13. Click OK as necessary to save the newly configured values, and then click
Close to close the Connection Properties dialog box.
14. Connect the Ethernet cables. Match each of the icons with its corresponding
Ethernet connector on the server or workstation.
15. Use ping -a from a Windows command prompt to verify the server or
workstation has contact with the Domain Controller:
C:\>ping -a 172.16.40.1
Pinging MM-DC1 [172.16.40.1] with 32 bytes of data:
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Ping statistics for 172.16.40.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),
Approximate round trip times in milli-seconds:
3BSE040587-601 203
Configuring Domain Controller and DNS Server Appendix A Prerequisites
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The connection may not work through more than one network adapter before
RNRP is installed.
Verify the port speed and duplex configuration on both ends (Network Adapter
and network switch). Refer to System 800xA Network Configuration
(3BSE034463*).
16. Verify the primary Client Server network is bound first for RNRP
configurations.
From the Change Adapter Settings:
a. Use the Alt key to expose the Advanced Settings menu.
b. Select Advanced Settings.
c. Verify the Primary Client Server Network is bound first and the
Redundant Client Server Network is second.
d. Make corrections as needed.
17. Disable all unused NIC cards.
The primary NIC card can only have one TCP/IP address. If the card consists
more than one TCP/IP address, RNRP will not function correctly.
Configuring Domain Controller and DNS Server
If the Domain Controller uses any network interface in addition to the ones for
the client/server network, the DNS Server need to be configured to only listen to
DNS requests on the client/server network. Perform the following for all Domain
Controllers.
• Open the Interfaces tab under Properties for the DNS Server.
• Make sure that only the IP addresses for the client/server network are
selected.
The below 800xA software must be installed on the standalone domain controllers
manually browsing the media for:
204 3BSE040587-601
Appendix A Prerequisites Configuring Domain Controller and DNS Server
• ABB 800xA Common Third Party Install: go to 3rd_Party_Software->ABB-

>ABB 800xA Common 3rd Party Install and run Setup.exe.
• RNRP: go to Core Functionalities > RNRP and run the ABB 800xA
RNRP.msi
• Diagnostics Collection Tool (DCT): Go to Core Functionalities > Diagnostics
Collection Tool > Diagnostics Collection Tool.msi. To install the DCT plug
ins go to Core Functionalities > Diagnostics Collection Tool > Diagnostics
Collection Tool Plugins.msi.
Specify an Administrative user name and password for the DCT Service account
during installation of the Diagnostics Collection Tool on a Domain Controller
node. Use domain\user name syntax to specify the domain account.
For an 800xA System installation to be used as a production system, set up a new
Domain Server with a domain specifically for the 800xA System, that will exist
independent of any other corporate domains that may already exist. Follow the
procedure in this section, starting at Active Directory Domain Services on First
Forest Root Domain Controller on page 206.
The following are general recommendations:
• One 800xA System may share the same domain with other 800xA Systems
having the same system versions.
• Generally, it is better to create a new, dedicated domain for an 800xA System
as opposed to reusing an old domain.
• Do not create subdomains and avoid complex solutions.
• Generally, it is not recommended to split two redundant Domain Controllers to
host engineering and production systems on two different locations (i.e.
network islands). Splitting two Domain Controllers will make one of the parts
incomplete since the Flexible Single Master Operations (FSMO) roles and
Global Catalog services are not redundant within Microsoft Windows.
Additional guidelines for setting up the 800xA System domain are provided in
System 800xA Network Configuration (3BSE034463*).
Before setting up a new domain, verify that the server hardware being used as the
Domain Server has the Server Operating System installed. The Workstation
Operating System can not be used for a Domain Controller or DNS server.
3BSE040587-601 205
Ensure that Internet Protocol Version 4 (TCP/IP V4) is the only protocol
configured on the node.
Create a new domain by setting up a new Domain Controller and DNS server using
the Server Manager.
To set up a new domain, configure the IP addresses of the Domain Server node if
this is not already done.
• Set the IP addresses.
• Set the IP address of this computer as the Preferred DNS Server on the
primary network adapter.
• If using, or planning on using two Domain Servers, set the IP address of the
other Domain Server as the Alternate DNS Server on the primary network
adapter.
• If using a redundant network, use the same DNS settings on the secondary
network adapter.
Active Directory Domain Services on First Forest Root Domain Controller

The following procedure was prepared using Install AD DS on the First Forest Root
Domain Controller as provided by Microsoft at:
http://technet.microsoft.com/en-us/library/hh472162.aspx
The instructions included here are for the preferred method of installing Active
Directory Domain Services (AD DS). Refer to the Microsoft article if planning
on using alternate methods.
Membership in the local Administrator account is the minimum required to

complete this procedure. Details about using the appropriate accounts and group
memberships can be found at:
http://technet.microsoft.com/en-us/library/dn487460.aspx.
To install AD DS:
1. Go to Server Manager.
2. Select Add roles and features.
206 3BSE040587-601
3. On Before you begin page, click Next.

4. On Select installation type page, select Role-based or feature-based
installation.
5. Click Next.
6. On Select destination server page, click select a server from the pool for
new roles.
7. Select current node, click Next.
8. On Select server roles page, select Active Directory Domain Services (AD
DS) as additional role.
9. Click Add Features on the pop-up to add other AD DS tools.
10. Click Next.
11. On Select features page, Group Policy Management feature is automatically
selected.
12. Click Next.
13. On Active Directory Domain Services page, basic information is displayed
14. Click Next.
15. On Confirm installation selections page, verify and click Install.
16. Click Notification Flag once the installation is complete.
17. Select Promote this server to a domain controller. AD DS configuration
wizard appears.
18. On Deployment Configuration page, select Add a new forest.
19. Enter Root domain name. (For Example: ABB.local)
20. Click Next.
21. On Domain Controller Options page, keep the default values.
22. Enter Directory Services Restore Mode (DSRM) password.
23. Click Next.
24. On DNS Options page, a warning message appears.
3BSE040587-601 207
25. Ignore and click Next.

26. On Additional Options page, verify NetBOIS name assigned to the domain.
27. Click Next.
28. On Paths page, keep default values and click Next.
29. On Review Options page, verify all the selections made.
30. On Prerequisites Check page, verify all the checks passed.
31. Click Install.
Active Directory Domain Services on Second Forest Root Domain Controller

The following procedure was prepared using Install AD DS on the Second Domain
Controller as provided by Microsoft at:
http://technet.microsoft.com/en-us/library/jj574134.aspx
The instructions included here are for the preferred method of installing Active
Directory Domain Services (AD DS). Refer to the Microsoft article if planning
on using alternate methods.
Membership in the Domain Admins group for the domain in which the second
Domain Controller is being installed is the minimum required to complete this
procedure. Details about using the appropriate accounts and group memberships
can be found at http://technet.microsoft.com/en-us/library/dn487460.aspx.
To install AD DS on a Domain Controller in an existing domain:
1. Go to Server Manager
2. Click Add Roles in the Roles Summary dialog box.
3. Review the information in the Before You Begin dialog box (if necessary) and
click Next.
4. Select the Active Directory Domain Services check box in the Select Server
Roles dialog box and click Next.
5. Review the information in the Active Directory Domain Services dialog box
and click Next.
208 3BSE040587-601
6. Click Install in the Confirm Installation Selections dialog box.

7. Click Close this wizard and launch the Active Directory Domain Services
Installation Wizard in the Installation Results dialog box.
8. Click Next in the Welcome to the Active Directory Domain Services
Installation Wizard dialog box.
9. Select Existing Forest and Add a domain controller to an existing domain
in the Choose a Deployment Configuration dialog box. Type the name of the
existing domain in the forest and then take the following actions:
a. Select My current logged on credentials or Alternate credentials under
Specify the account credentials to use to perform the installation and
click Set.
b. Provide the user name and password for an account that can install the
additional Domain Controller (it must be a member of the Enterprise
Admins group or the Domain Admins group) in the Windows Security
dialog box and click Next.
10. Select the domain of the new Domain Controller in the Select a Domain dialog
box and click Next.
11. Select a site from the list, or select the option to install the Domain Controller
in the site that corresponds to its IP address in the Select a Site dialog box and
click Next.
12. Make the following selections in the Additional Domain Controller Options
– DNS Server: This option is selected by default when AD DS integrates
the DNS server service in to the domain so that the Domain Controller can
function as a DNS server (this is the preferred method).
It is recommended that DNS be installed when the Active Directory Domain
Services Installation Wizard is run (keep the default selected), so that the wizard
creates the DNS zone delegation automatically.
– Global Catalog: This option is selected by default. It adds the global
catalog, read-only directory partitions to the Domain Controller, and it
enables global catalog search functionality.
3BSE040587-601 209
Adding Nodes to a Domain Appendix A Prerequisites
– Read-only domain controller: This option is not selected by default. It

makes the additional Domain Controller read-only. For more information
about read-only domain controllers, refer to:
http://technet.microsoft.com/en-in/library/jj574152.aspx
13. In Active Directory Domain Services Installation Wizard, navigate to
Additional Option, and in Replicate From select the Domain Node.
14. Use the default locations in the Location for Database, Log Files, and SYSVOL
15. Type and confirm the restore mode password in the Directory Services Restore
Mode Administrator Password dialog box and click Next.
This password must be used to start AD DS in Directory Service Restore Mode
for tasks that must be performed offline.
16. Review the selections in the Summary dialog box. Click Back if it is necessary
to change any selections.
17. Click Export settings to save the selected settings to an answer file that can be
used to automate subsequent AD DS operations.
18. Type the name for the answer file and click Save.
19. Click Next to install AD DS when the selections are accurate.
20. Click Finish in the Completing the Active Directory Domain Services
Installation Wizard dialog box.
21. A prompt appears asking to restart the server. Select either the Reboot on
Completion check box to restart the server automatically or clear the check
box to restart the server manually to complete the AD DS installation.
System 800xA Network Configuration (3BSE034463*) includes examples of a
correctly configured DNS Server.
Adding Nodes to a Domain

This is required for all member nodes in the 800xA System (not applicable for
single node installations, for example Information Management consolidation node,
210 3BSE040587-601
Appendix A Prerequisites Configuring Users and Groups
or Windows Workgroups). Perform this procedure at each node that needs to be

added to the domain.
This procedure requires an administrator user name and password defined for the
domain. Have this information available before proceeding.
1. Log on to the node as a local administrator.
2. Configure the IP address of this node and ensure the DNS server address points
to the IP address of the DNS server.
3. From the desktop, right-click on Start and select System from the context
menu that appears.
4. Select Change Settings.
5. Select the Computer Name tab and click Change.
6. In the Computer Name Changes dialog box, select Domain Controller.
7. Type the name of the domain in the Domain field.
8. Click OK until all dialog boxes are closed.
9. Click Yes when asked to reboot.
Repeat this procedure to add additional nodes to the domain.
Configuring Users and Groups

This section describes how to create the Windows domain users and groups in the
Active Directory on the Domain Server node.
The prerequisites to configure Users and Groups in a Domain:
• Before setting up Industrial IT users and user groups, verify that a domain has
been created by setting up a Domain Controller and DNS server as described in
Configuring Domain Controller and DNS Server on page 204.
• This procedure requires being logged in as domain administrator. A default
domain administrator is created when the Domain Controller and domain is set
3BSE040587-601 211
Configuring Users and Groups Appendix A Prerequisites
up as described in Configuring Domain Controller and DNS Server on page

204.
Refer to System 800xA Administration and Security (3BSE037410*) for detailed
descriptions of users, user groups, and user roles and permissions.
Refer to Users, Groups, and Rights Assignments on page 216 for listings of
mandatory users and user groups for the 800xA System.
Since the 800xA System user credential concept is built on Windows domains,
local user accounts must never be created and used on the client nodes. Clients
will always connect to the 800xA System using domain accounts. The only
exception is Windows Workgroups where domains are not used. In these cases all
users and groups are local
For 800xA Systems in a Windows Workgroup all the users and groups shall be
created locally on each node with same user group name, user name and
password.
The following procedure is used to create various domain accounts to be used in
System 800xA. Create two domain accounts with administrator privileges.
The 800xA Service User will be reserved for use by the 800xA System Services.
This account will NOT be used for installation, administration, configuration, or any
other system related procedures.
The 800xA Installation account must be created to complete the 800xA System
software installation and post installation procedures. Create other user accounts for
other 800xA System activities such as Application Engineer, System Engineer, and
Operator.
Define separate accounts and different passwords for the 800xA Service User and
the 800xA installing User.
212 3BSE040587-601
Appendix A Prerequisites Configuring Users and Groups
Domain Administrator users are powerful for administrative purposes but could
by this also be dangerous from a security perspective. For security reasons the
number of users in the Domain Administrator group should be kept to a
minimum.
The 800xA Service User and 800xA Installing User do not need to be members
of the Domain Administrators group. They both need to be members of the
Builtin Administrators group on the 800xA System nodes but not on the Domain
Controller, unless it is combined with an 800xA Server.
The 800xA Installing User could be a Domain Administrator but should be set to
passive after the installation of the System. The 800xA Service User should not
be a Domain Administrator and also not a local administrator on the Domain
Controller.
The various users and groups required by the 800xA System are described in
Table 8. All groups/users must reside on the 800xA System domain.
This setup may be performed by yourself, or the domain administrator may perform
the setup. In either case, use the guidelines in Table 8, and follow the step-by-step
procedures following Table 8.
Table 8. Domain Groups/Accounts Required by 800xA System
Groups/Users Description
IndustrialITAdmin Group Create the IndustrialITAdmin Group. All 800xA System
administrators (including the 800xA Service User) must be
a member of the IndustrialITAdmin group.
IndustrialITUser Group Create the IndustrialITUser Group. All 800xA System
users must be a member of the IndustrialITUser group.
3BSE040587-601 213
Configuring Users and Groups Appendix A Prerequisites
Table 8. Domain Groups/Accounts Required by 800xA System (Continued)
Groups/Users Description
800xA Service User Create a new user for 800xA System services. Make this
user a member of the IndustrialITAdmin Group, the
IndustrialITUser Group, and the local administrator group
on every system node.
All 800xA System services will run under this account.
Make the name easy to recognize (for example:
800xAService).
NOTE 1: Creating this user requires being logged in as
domain administrator. Adding this user to the local
administrator group on every system node requires being
logged in as local administrator.
NOTE 2: The 800xA Service User must not be a member
of the Domain Administrator group. These users should be
members of the Built-in Administrators group on the
Domain Controller node.
Other 800xA System users Create additional users for system configuration and
operation. These users are added to the IndustrialITUser
Group. Refer the System 800xA 6.0 Administration and
Security (3BSE037410*) for more information on user
permissions.
214 3BSE040587-601
Appendix A Prerequisites New Organizational Unit
New Organizational Unit

This organizational unit is not mandatory; however, it may be helpful to put all
800xA System groups and users into one container. To create a new unit:
1. Go to:
Administrative Tools > Active Directory Users and Computers
2. In the left pane, right-click on the newly created domain server name, and
select:
New > Organizational Unit
from the context menu that appears.
3. Assign this organization unit the name Industrial IT.
Groups
This procedure assumes the Industrial IT organization unit has been created.
To create the required groups:

1. Right-click on the Industrial IT folder in the left pane and select:
New > Group
from the context menu that appears.
2. Use the New Object - group dialog box to assign the group a name (for
example, IndustrialITAdmin).
3. Set the Group scope to Global, and the Group type to Security.
4. Perform Step 1 through Step 3 for each of the two required groups:
– IndustrialITAdmin.
– IndustrialITUser.
It is recommended to keep the default names of these groups. Systems with Batch
Management should create the groups with default names IndustrialITAdmin and
IndustrialITUser.
3BSE040587-601 215
Users, Groups, and Rights Assignments Appendix A Prerequisites
Users, Groups, and Rights Assignments

This topic defines the default User Groups and Users for the 800xA System.
Windows Workgroups set up the same groups and users as a domain. The user rights
are also the same as in a domain, except all domain policies must be defined on each
local node. No additional policies are required for Windows Workgroups.
Ensure that the User Account names do not exceed the 20 character limit.
User Groups and Users

All users must be members of the IndustrialITUser group if they require the
ability to start a workplace.
Table 9 lists the default User Groups and Users.
Table 9. Default User Groups and Users
Organizational
User Group User Account Description
Unit
Industrial IT IndustrialITAdmin SwServiceAccount CHMI System service account
SysAdmin CHMI System account
Administrator Built-in account
IndustrialITUser SwServiceAccount CHMI System service account
SysAdmin CHMI System account
Operator Default operator 1
AppEng Application Engineer
Administrator Windows default administrator
account
216 3BSE040587-601
Appendix A Prerequisites Users, Groups, and Rights Assignments
Local Groups and Members on Each Node

Table 10 lists the local and domain User Groups and Users for each system node.
Table 10. Local Groups and Members on Each Node in System
Local Group/User Domain Group/User

Administrators (standard default) 800xAService
800xAInstaller
User Rights Assignment

Table 11 lists the user rights assignment.
In case of an Aspect Server combined with a Domain Controller, create a new
Group Policy Object under the Domain Controller object and configure the
security policies listed in Table 11.
The user rights in the Windows security policies shall be configured in 800xA
System to enable users with right permissions to perform various activities in the
system.
For systems using Domain Controllers the user rights assignment security policies
are to be configured from the below location on the Primary Domain Controller:
1. Go to Control Panel > Administrative Tools > Group Policy Management
2. Right click Group Policy Management and select Edit...
3. Navigate to Computer Configurations > Policies > Windows Settings >
Security Settings > Local Policies and click User Rights Assignment
For Systems in Workgroup environment configure the user rights assignment
security policies on each node in the below location:
1. Go to Control Panel > Administrative Tools >Local Security Policy.
2. Navigate to Security Settings > Local Policies > User Rights Assignments.
The security policies listed in Table 11 can be configured by performing the
following on each Security policy under User rights Assignment:
1. Double click on the policy
3BSE040587-601 217
800xA Service User Appendix A Prerequisites
2. Click Add User or Group... button to add the user or groups as per Table 11.
3. Click OK to close the policy.
Table 11. User Rights Assignments
Policy Security Setting

Local Security Policy (each node)
Access this computer from the network IndustrialITUser
Allow log on locally IndustrialITAdmin
Change the system time IndustrialITAdmin
Log on as a batch job 800xAService
800xAInstaller
Log on as a service 800xAService
800xAInstaller
Impersonate a client after authentication SERVICE (Default)
Administrators (Default)
Users that require logover (Process Portal)
800xA Service User

This procedure assumes the Industrial IT organization unit has been created.
Creating this user requires being logged in as domain administrator. Adding this
user to the local administrator group on every system node requires being logged
in as local administrator.
Create the CHMI Service User. This is the user account that all 800xA System
services will run under. Make this new user a member of the following groups:
• IndustrialITAdmin Group
• IndustrialITUser Group
218 3BSE040587-601
Appendix A Prerequisites 800xA Service User
To create this user:

1. Right-click on the Industrial IT organizational unit in the left pane and select:
New > User from the context menu that appears.
2. In the New Object - User dialog box specify the user name and login name.
Make the name meaningful and easy to recognize (for example: SwService).
Figure 131. Create SwServiceAccount
3. Click Next when finished.

4. Specify the user password. Enable the Password never expires check box, and
make sure the password for this user is NEVER CHANGED.
5. Click Next when finished with the password specification.
6. Click Finish in the next dialog box to complete the user specification.
7. Make this user a member of the IndustrialITAdmin Group.
a. Select the Industrial IT organizational unit in the left pane.
3BSE040587-601 219
800xA Service User Appendix A Prerequisites
b. Right-click on the IndustrialITAdmin group in the right pane and choose

Properties from the context menu that appears (or double-click the group
name).
c. Select the Members tab in the Properties dialog box.
d. Click Add. This displays the Select Users, Contacts, or Computers dialog
box.
Figure 132. Add User to IndustrialIT Admin Group
e. Select the new user (for example, SwService) and click Add.
f. Repeat Step e to add other users to the IndustrialITAdmin group.
g. Click OK when finished.
h. Click OK on the Members tab of the Properties dialog box.
8. Add this user to the Built-in Administrators group on the Domain Controller
node.
220 3BSE040587-601
Appendix A Prerequisites Other Users
9. Add this user to the local administrator group on every system node.
Other Users
Add other IndustrialIT users and make them members of the IndustrialIT User
Group. Set passwords according to company policy, and change them frequently.
Examples of users who can be members of the IndustrialITUser groups is as shown
in Table 12.
Ensure that the User Account names do not exceed the 20 character limit.
Do not change the 800xAService user passwords.
Table 12. Examples for User accounts
User Account Descriptions

ApplicationEng Default application engineer
SystemEng Default system engineer
MaintenanceSup Default maintenance supervisor
MaintenanceEng Default maintenance engineer
MaintenanceTech Default maintenance technician
Adding 800xA Domain Users to the Local Administrator Group

The CHMI Service User accounts defined in the domain must be added to the local
Administrator Group on every node in the domain, including the Domain Controller
node. The different procedures to be followed depend on the node type:
• Domain Controller Node
• On All Other Nodes
Domain Controller Node

1. Go to Control Panel > Administrative Tools
2. Select Active Directory Users and Computers to launch the Active Directory
Users and Computers dialog box.
3BSE040587-601 221
Adding 800xA Domain Users to the Local Administrator Group Appendix A Prerequisites
3. In the left pane, navigate to:

Active Directory Users and Computers > Domain Name > Built-in
4. Select Administrators in the right pane to launch the Administrators
Properties dialog box.
5. Select the Members tab.
6. Click Add. This opens the Select Users, Computers or Groups dialog box.
7. Click Locations, select the domain in the Locations dialog box and click OK.
8. Enter the names of the 800xA Service User and Installing User in the text box
and click Check Names.
9. When the dialog box indicates the names have been found, click OK.
10. To finish, click OK in the Administrators Properties dialog box.
On All Other Nodes

1. Log on as a local administrator.
2. From desktop right-click Start and select Computer Management from the
context menu that appears.
3. The Computer Management dialog box appears. In the left pane, navigate to:
Computer Management (Local) > System Tools > Local Users and Groups
> Groups
4. Click Administrators to open the Administrators Properties dialog box.
5. Click Add. This opens the Select Users, Computers or Groups dialog box.
6. Click Locations, select the domain in the Locations dialog box and click OK.
7. Enter the names of the 800xA Service User and Installing User in the text box
and click Check Names.
8. When the dialog box indicates the names have been found, click OK.
9. To finish, click OK in the Administrators Properties dialog box.
222 3BSE040587-601
Appendix A Prerequisites Operating System Setup Use with Compact HMI
Operating System Setup Use with Compact HMI

The following procedures should be carried out in domain account with
Administrator rights (For example: 800xAinstaller).
The following settings are required for use with the 800xA System:
• Regional and Language Options
• Enable Write Caching on Hard Disks
• Internet Explorer Enhanced Security
• Internet Security Settings for Digital Signature Validation
• Virus Scanning Configuration During Installation and Post Installation
• Disable Show Window Contents While Dragging
• Energy Saver and Screen Saver Configuration
• Virus Scanning Configuration During Installation and Post Installation
• Windows Update Configuration
• Enable the Change Sharing Options for Different Network Profiles
• Disable Server Manager Startup
• Disable ISATAP Setting
• Group Policy Management
• Adding Privileges to the 800xA Service User
• Remote (Thin) Client for the Server Operating System
Regional and Language Options

Perform the following procedure to set the regional and language options. These
procedures must be performed for all users on all nodes in the 800xA System.
The procedure differs depending on the operating system. The procedures described
for all other supported operating systems:
1. Open Windows Control Panel.
2. Click Clock, Language, and Region to verify Region and Language
preferences.
3. Click Region and select Formats tab.
4. Select and verify that English (United States) is selected in the Format
section.
5. Click Additional settings... to launch the Customize Format dialog box.
3BSE040587-601 223
Enable Write Caching on Hard Disks Appendix A Prerequisites
6. Verify that the value in the Decimal symbol field drop-down list is a dot (.). If
it is not, change it to a dot (.) and click Apply and then OK.
7. Click the Administrative tab.
8. Click Change system locale... to launch the Region Settings dialog box.
9. Verify that the value in the Current system locale drop-down list is English
(United States). If it is not, change it to English (United States) and click OK
to return to the Administrative tab of the Region dialog box.
10. Click Copy settings to launch the Welcome Screen and New User Accounts
Settings dialog box.
11. Enable the Welcome screen and system accounts and New User Accounts
check boxes and click OK.
12. Click OK to exit the Region dialog box.
13. Close Windows Control Panel.
Enable Write Caching on Hard Disks

To ensure Aspect Directory integrity, the write cache buffer flushing must be left
enabled in the Microsoft Windows Operating System. Depending on the
configuration, choice of driver, type of hard disks, etc, Windows may allow
disabling the write cache buffer flushing on the hard disks to improve performance.
For data integrity this otherwise performance increasing option must not be used.
System 800xA configuration and application data is stored in the Aspect Directory.
The Aspect Directory is transaction driven and enforces a two-phase-commit
scheme. As part of that scheme it ensures that data is written to disk prior to
considering the transaction complete. This behavior is used by several other third-
party databases.
A flush command is used to ensure that data is written to the disk.It is possible to
configure the disk driver to neglect the flush command. This is normally configured
in the Windows disk drives setting.
A consequence of, for example, a power or hardware failure can be that a flushing is
not performed. Potentially the Aspect Directory can then become inconsistent and
the system will no longer start. Furthermore the data and applications become
impossible to recover.
224 3BSE040587-601
Appendix A Prerequisites Internet Explorer Enhanced Security
Refer to Microsoft Knowledge Base article 234656 for more information.

Perform the following procedure on all the Server Operating System hard disks:
1. Launch the Computer Management Console.
2. Select Device Manager in the left pane.
3. Select and navigate through Disk drives in the right pane.
4. Right-click the hard drive and select Properties from the context menu to
launch the hard drive properties dialog box.
5. Select Policies tab.
6. Select the Enable write caching on the device check box for Server and
Workstation Operating System.
For Virtual Nodes: Select Better Performance check box to enable write
caching.
7. Click OK.
8. Close the Computer Management Console.
It may be necessary to verify the Enable write caching on the disk check box is
still enabled after rebooting.
Internet Explorer Enhanced Security

The Internet Explorer Enhanced Security component must be disabled on all the
Server Operating System nodes.
Perform the following steps:
1. Open Server Manager.
2. Select Local Server.
3. In Properties, select Internet Explorer Enhanced Security Configuration.
4. Select Off radio button for Administrators and Users.
5. Click OK.
3BSE040587-601 225
Internet Security Settings for Digital Signature Validation Appendix A Prerequisites
Internet Security Settings for Digital Signature Validation

Perform the following steps on all 800xA nodes:
1. Go to Control Panel.
2. On All Control Panel Items, select Internet Options.
3. In the Internet Properties, click Advanced tab.
4. Scroll to Security and under Security clear the Check for publisher’s
certificate revocation check box.
5. Click Apply and OK.
Disable Web Browser Popup Blocker

Internet Explorer offers web browser popup blocker by default. Disable Popup
Blocker where the thin client portions of the integrated applications (specifically
Asset Optimization) are used, since these applications open child window browsers
to display application data for the user.
Disable Show Window Contents While Dragging

To prevent CPU intensive redrawing of the window, disable the Windows Show
Window Contents while dragging feature.
1. Open This PC.
2. Right-click and select Properties from the context menu to launch the System
3. Select the Advanced System Settings.
4. Click Settings in the Performance frame to launch the Performance Options
dialog box.
5. Select the Visual Effects tab (this should be selected when the dialog box is
launched).
6. Select the Custom option.
7. Clear the Show Window Content while Dragging check box.
226 3BSE040587-601
Appendix A Prerequisites Energy Saver and Screen Saver Configuration
8. Click Apply, wait, and then click OK to close the Performance Options dialog
box.
9. Click OK to close the System Properties dialog box.
Energy Saver and Screen Saver Configuration

It is recommended to NOT have any Energy Saving and screen saver functionality
activated on 800xA System nodes (especially operator Workplace Clients), as this
might lead to longer reaction times in case of an emergency. If the server or
workstation BIOS has an Energy Saver configuration, configure it on a node-by-
node basis. The Windows energy saving data is user dependent.
The energy saving setting may be accessed in two ways. The BIOS setup is
available whenever the server or workstation is powered up. It may also be accessed
via Power Options in Windows Control Panel. The screen saver may be turned off in
the Display Properties option in Windows Control Panel.
Virus Scanning Configuration During Installation and Post Installation

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

Automatic Windows Updates are not recommended for the 800xA node. The
information on service packs, hot fixes are listed in System 800xA 6.0, 5.1, 5.0, 4.x,
3.1 Third Party Software (3BUA000500). For security updates refer System 800xA -
Third Party Security Updates Validation Status (3BSE041902). These documents
can be found in ABB SolutionsBank.
3BSE040587-601 227
Enable the Change Sharing Options for Different Network Profiles Appendix A Prerequisites
To disable the automatic updates by setting the Windows Automatic Updates feature
to never check for updates:
1. Open Windows Update
2. In the left pane, click Change Settings
3. Under Important Updates choose Never check for updates
Enable the Change Sharing Options for Different Network Profiles

Perform the following to enable the following parameters on all the nodes:
1. Go to Control Panel.
2. Click Network & Sharing Center.
3. Click Change Advance Sharing Settings.
4. Select the following in Private or Public or Domain profiles:
– Turn on network discovery in the Network Discovery pane.
If network discovery remains disabled (Turn off), then follow the procedure
mentioned in the Microsoft KB article to enable (Turn on) network discovery.
http://support.microsoft.com/kb/2722035
– Turn on file and printer sharing in the File and printer sharing pane.
Disable Server Manager Startup

Perform the following procedure to disable Server Manager not to start
automatically.
1. Open Server Manager.
2. Click Manage tab and select Server Manager Properties.
3. Select Do not start Server Manager automatically at logon and click OK.
Disable ISATAP Setting

Perform the following procedure on all nodes (800xA or non-800xA) connected on
the same network as the AC 800M Controllers:
228 3BSE040587-601
Appendix A Prerequisites Group Policy Management
1. Open Command prompt with “Run as administrator”.

2. At the command line, to check current ISATAP setting, enter:
netsh interface isatap show state
(Probably responds ISATAP State: default)
3. At the command line, to Disable ISATAP, enter:
netsh interface isatap set state disabled
Group Policy Management

The group policy management procedures differ depending on the environment
(domain or Windows Workgroup).
Domain Environment
Perform this procedure before installing 800xA System and Functional Area
software.
Group Policy. This procedure must be performed on the Primary Domain

Controller. It should be performed after all 800xA System nodes have been added to
the domain so that the new Group Policy will replicate out to all nodes in the
selected domain via the active directory. However, if the system is expanded at a
later time, the Group Policy will replicate to the nodes added during the expansion.
1. Open Group Policy Management Console.
Do not modify the default Group Policy Object itself. Create, link and modify a
new Group Policy Object.
2. Navigate to the following in the left pane of the Group Policy Object Editor:
Forest:domain name >Domains >domain name >Group Policy Objects
3. Right-click on Group Policy Objects in the left pane of the Group Policy
Management Console, and select Create a GPO in this domain from the
context menu to open the New GPO dialog box.
3BSE040587-601 229
Group Policy Management Appendix A Prerequisites
4. Type in a name for the new Group Policy Object in the New GPO dialog box;
for example, IntranetName and click OK to return to the Group Policy
Management Console.
5. Right-click on the new Group Policy Object in the left pane of the Group
Policy Management Console, and select Edit from the context menu to open
the Group Policy Object Editor.
User Configuration > Policies > Administrative Templates > 
Windows Components > Internet Explorer > 
Internet Control Panel > Security Page
7. Double-click Turn on automatic detection of intranet, a dialog box appears.
8. Click Disabled and click OK.
9. Double-click Intranet Sites: Include all local (intranet) sites not listed in
other zones, a dialog box appears.
10. Click Enabled and click OK.
11. Double-click Intranet Sites: Include all sites that bypass the proxy server, a
dialog box appears.
13. Double-click Intranet Sites: Include all network paths (UNCs), a dialog box
appears.
15. Close the Group Policy Object Editor.
16. Reboot the node.
Adding Workstations to the Domain Policy

Perform the following in order to prevent any user from being able to add
workstations to the domain.
1. Open Group Policy Management Console.
2. Navigate to the following:
230 3BSE040587-601
Appendix A Prerequisites Group Policy Management
Forest: Domain Name > Domains > Domain Name > Group Policy
Objects > Default Domain Controllers Policy
3. Right-click Default Domain Controllers Policy and select Edit from
the context menu to launch the Group Policy Management Editor.
4. Navigate to the following:
Default Domain Controllers Policy > Computer Configuration
Policies > Windows Settings > Security Settings > Local Policies >
User Rights Assignment
5. In the right pane, double-click Add workstations to domain to launch the
Add workstations to domain Properties dialog box.
6. Select Authenticated Users and click Remove.
7. Click Add User or Group to launch the Add User or Group dialog box.
8. Click Browse to launch the Select Users, Computers, or Groups dialog box.
9. Select the users and/or groups that are to have the authority to add workstations
to the domain and click OK twice to return to the Add workstations to domain
Click Find Now in the Select Users, Computers, or Groups dialog box to display
the available users and groups.
10. Click Apply and then OK to close the dialog box.
11. Close the Group Policy Management Editor.
Windows Workgroup Environment

Perform this procedure before installing 800xA System and Functional Area
software.
Group Policy. This procedure must be performed on every node in the Windows
Workgroup. If the system is expanded at a later time, this procedure must be
performed on each node added during the expansion.
3BSE040587-601 231
Remote (Thin) Client for the Server Operating System Appendix A Prerequisites
1. Open Local Group Policy Editor.

User Configuration > Administrative Templates > 
Windows Components > Internet Explorer > 
Internet Control Panel > Security Page
3. Double-click Turn on automatic detection of intranet, a dialog box appears.
5. Double-click Intranet Sites: Include all local (intranet) sites not listed in
other zones, a dialog box appears.
6. Click Enabled and click OK.
7. Double-click Intranet Sites: Include all sites that bypass the proxy server, a
dialog box appears.
9. Double-click Intranet Sites: Include all network paths (UNCs), a dialog box
appears.
11. Close Local Group Policy Editor.
12. Reboot the node.
Remote (Thin) Client for the Server Operating System

Perform the following procedure to install the Terminal Server role service and
configure the Terminal Server to host programs:
1. Go to Server Manager.
2. Select Add roles and features.
3. On Before you begin page, click Next.
4. On Select installation type page, select Role-based or feature-based
installation.
5. Click Next.
232 3BSE040587-601
Appendix A Prerequisites Other Third Party Software
6. On Select destination server page, click select a server from the pool for
new roles.
7. Click Next.
8. On Select server roles page, select Remote Desktop Services as additional
role.
If Terminal Services is already installed on the server, the Terminal Services
check box will be selected and dimmed.
9. Click Next.
10. On Select features page, click Next without changing the features.
11. On Remote Desktop Services page, click Next.
12. On Select role services page, select Remote Desktop Licensing role.
If installing the Terminal Server role service on a Domain Controller, a warning
message indicating that Installing the Terminal Server role service on a Domain
Controller is not recommended will appear.
13. Click Add Features and click Next.
14. Verify the added roles and features on Confirm installation selections page
and click Install.
15. Restart the node when the installation is complete.
Other Third Party Software

This section details the installation of other third party software that are required for
the 800xA System.
All 800xA installation must be carried out in 800xA Installer account.
Microsoft Office Professional

The 800xA System supports the U.S. English, 32-bit and 64-bit versions of the
Microsoft Office Professional 2013.
3BSE040587-601 233
Microsoft Word Appendix A Prerequisites
Microsoft Word
When installing Microsoft Word it is required to select Office Shared Features
from the Installation Options dialog box and to accept the default subfeatures
under the Office Shared Features selection.
Microsoft Word, which is part of the Microsoft Office Professional suite, must be
installed on all nodes where the following functions will be used:
• Process Graphics (for Reference Documentation Tool)
• Engineering Studio (for Document Manager Functions)
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.
Macro Security for Microsoft Word

Perform the following procedure for every Industrial IT User on every node, after
installation of Microsoft Word and before continuing installing or working on the
Engineering Platform:
1. Start Microsoft Word.
2. Click the File menu in the left corner.
3. Click Word Options to open the Word Options dialog box.
4. Select Trust Center in the left pane of the Word Options dialog box.
5. Click Trust Center Settings to open the Trust Center.
6. Select Macro Settings in the left pane of the Trust Center.
7. Select Disable all Macros Except Digitally Signed Macros in the right pane
of the Trust Center.
8. Click OK to close the Trust Center.
9. Click OK to close the Word Options dialog box.
10. Repeat this procedure for every Industrial IT User on every node.
234 3BSE040587-601
Appendix A Prerequisites Microsoft Excel
Microsoft Excel
When installing Microsoft Excel 2010 or 2013 it is required to select Office
Shared Features from the Installation Options dialog box and to accept the default
subfeatures under the Office Shared Features selection.
When installing Microsoft Excel, select the Custom installation. When the
Installation Options dialog box appears. select the Visual Basic for Applications
option under Shared Features.
Open Microsoft Excel and perform the recommended settings, if prompted.
Navigate to File > Options > General, and clear the Show the start screen
when this application starts check box.
Microsoft Excel, which is part of the Microsoft Office Professional suite, must be
installed on all 800xA System nodes where engineering tools or Excel based reports
will be used. This can include the following:
• Process Graphics (for Display Documentation Tool)
• Engineering Studio (for Bulk Data Manager Functions)
• DataDirect - Excel Data Access
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.
Macro Security for Microsoft Excel

Perform the following procedure for every Industrial IT User on every node, after
installation of Microsoft Excel and before continuing installing or working on the
Engineering Platform:
1. Start Microsoft Excel.
2. Click the File menu in the left corner.
3. Click Excel Options to open the Excel Options dialog box.
4. Select Trust Center in the left pane of the Excel Options dialog box.
5. Click Trust Center Settings to open the Trust Center.
3BSE040587-601 235
Crystal Reports Appendix A Prerequisites
6. Select Macro Settings in the left pane of the Trust Center.

The macro security setting must be set to Enable all Macros for every Industrial
IT User on every node in the 800xA System if any of the following are true:
• 800xA for Harmony or 800xA for AC 870P/Melody is installed on any node in the
800xA System.
• Engineering templates will be used on any node in the 800xA System.
7. Select Disable all Macros Except Digitally Signed Macros in the right pane
of the Trust Center.
8. Click OK to close the Trust Center.
9. Click OK to close the Excel Options dialog box.
Crystal Reports
Crystal Reports can be used to create reports of System 800xA Data. When used
with the application scheduler, the reports can be automatically executed.
Crystal Reports will typically be installed on nodes where the, Information
Manager, node function is allocated. However, it can be installed on any node that
has access to 800xA data reporting interfaces (800xA DataDirect or ODBC). Follow
the procedure to install Crystal Reports.
System 800xA latest release supports Crystal Reports 2013 version. Table 13 lists
the installed versions and available builds in the SAP portal.
Table 13. Crystal Report Builds
Build Website
Crystal reports 2013 + It will be available as part of Crystal reports 2013
Crystal Reports Runtime install media.
(CRforVS_redist_install_32bit_13_0_14) Download the Crystal Reports Runtime from the
location specified below.
• From the URL
http://scn.sap.com/docs/DOC-7824
• Click 32bit.msi from MSI 32 bit column as
shown in the Figure 133 to install.
236 3BSE040587-601
Appendix A Prerequisites Autocad Integration
Figure 133. Crystal Reports Runtime Install
Autocad Integration
As a prerequisite to use AutoCAD for Document Manager and Parameter Manger,
install AUTOCAD VBA Enabler by downloading the software from the AutoCAD
website.
<
McAfee Integration
McAfee VirusScan® Enterprise has been tested and qualified virus scanner that is
used on all System 800xA servers and workstations. Refer to System 800xA
Installing and Configuring McAfee ePO Server (9ARD107543-005), for more
information.
McAfee need not be disabled during installation, however this might impact
Installation performance of 800xA Software.
Symantec
Symantec Endpoint Protection (SEP) has been tested and qualified virus scanner
that is used on all System 800xA servers and workstations. Refer to System 800xA
Using Symantec Endpoint Protection (9ARD119854-002), for more information.
3BSE040587-601 237
Bulk SPL Template Appendix A Prerequisites
Bulk SPL Template

To work with ABB Engineering Studio BulkSPLTemplate, perform the following:
1. Download and install the following software from Microsoft website:
Microsoft Visual Studio 2010 Tools for Office Runtime (x64).
During the VSTO installation following message may be displayed:
Files in use
Some files that need to be updated are in use by the
applications shown below.
Close these applications and click Retry to continue the
installation. Selecting Ignore will result in a reboot at
the end of installation. Select cancel to exit setup.
Click Ignore to complete the installation.
2. If VSTO is not installed before Engineering Studio installation, perform the
following steps:
a. Follow Step 1 to install VSTO.
b. Open Command Prompt as Administrator and execute the following:
"C:\Program Files (x86)\ABB Industrial IT\Engineer IT\Engineering
Studio\Function Designer\bin\BulkSPLbin\BulkSPLInstall.exe"
"C:\Program Files (x86)\ABB Industrial IT\Engineer IT\Engineering
Studio\\"
Backup Software
It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) server and workstation hard drives. A valid
backup insures that the system can be restored.
238 3BSE040587-601
Index
A
Acknowledge 133
Adding nodes to domain 210
Alarm Band 136
Alarms and events 133
Aspect Object 21
Aspect View 22
Aspects 21
Alarm and Event 80
Alarm and Event Configuration 81
Graphical Elements 77
History Logging 81
Log Configuration 81
Process Displays 95
Security Definition 111
Audit Trail
disable 110
enable 110
Automatic updates 227
B
Back to Previous Display 115, 117, 119
Backup software 238
Backup/Restore
Ghost 146
Breadcrumb list 122
C
Connectivity to AC 800M 60
Context Menu 125
D
Default user groups and users 216
Defragmenting disks 199
Disks and file system 198
Display bar 119
Display links 125
3BSE040587-601 239
E IP addresses 71
Energy saver 227
Excel 235 L
License installation 55
F Log Configuration 81
Faceplate views
Extended 129 M
Faceplate 129 Microsoft Excel 235
Reduced 129 Microsoft Word 234
Faceplates 79
File system 198 N
Function keys 126 Network adapters 201
Functional Structure 90
O
G OPC names 76
Graphical displays 77 OPC Server for PLC 67
Groups 211 Operator Workplace 24
Other Third Party Software 233
H
Hidden alarms 133 P
Hot Keys 126 Plant Explorer 24
Hot keys 124 PLC signal 75
Preparing the node 53
I Process Alarms 133
IE enhanced security configuration 225 Process Event List 137
Installation Process Events 137
Directory 199
Prerequisites R
Adding nodes to domain 210 Remote client 232
Backup software 238
Microsoft Excel 235 S
Microsoft Word 234 security setting 111
Miscellaneous Windows setup 223 Start display 124
Network adapters 201 Status Bar 121
Remote client 232 Structures 23
Terminal server 232 Control Structure 90
Users and groups 211 Object Type Structure 74
Windows 197 Supervision 128
Windows installation guidelines 200 System Alarms 136
240 3BSE040587-601
System Event List 138
System Events 138
System startup 60
T
Terminal server 232
Trend Display 97
U
Upgrade from Compact HMI SP2 Rev C to 5.1 57
Upgrade to 800xA 59
User groups and users
Default 216
Users 211
W
Windows operating system 197
Installation guidelines 200
Miscellaneous setup 223
Word 234
3BSE040587-601 241
242 3BSE040587-601
Revision History
Introduction
This section provides information on the revision history of this user manual.
The revision index of this user manual is not related to the Compact HMI 6.0.1
System Revision.
Revision History
The following table lists the revision history of this user manual.
Revision
Description Date
Index
- First version published for Compact HMI 6.0.1 February 2016
3BSE040587-601 243
Revision History
244 3BSE040587-601
Contact us
www.abb.com/compactproductsuite
3BSE040587-601
Copyright © 2005-2015 by ABB.
www.abb.com/controlsystems All rights reserved.
Power and productivity

for a better worldTM

3BSE040587-601 - en Compact HMI 6.0.1 Getting Started

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

3BSE040587-601 - en Compact HMI 6.0.1 Getting Started

Încărcat de

Drepturi de autor:

Formate disponibile

Compact Product Suite

Power and productivity

System Version 6.0.1

Copyright © 2005-2016 by ABB.

Release: February 2016

About This User Manual

Section 1 - Compact HMI Overview

Section 2 - Terms and Common Principles

Node Preparation Tool ......................................................................................... 37

Basic Navigation ................................................................................................101

Replacing a Node .......................................................................................................... 141

Section 7 - Using the PLC Device Library

New Organizational Unit....................................................................................215

User Manual Conventions

Warning, Caution, Information, and Tip Icons

Released User Manuals and Release Notes

System 800xA Released User Manuals and Release Notes (3BUA000263*) is

Category Title Description

Category Title Description

The IndustrialIT Compact HMI is designed to be an HMI to any kind of automation

Figure 1. System Overview

Figure 2. Aspects with Aspect Views

The Operator Workplace and Plant Explorer Workplace

Figure 3. The Operator Workplace Window

Plant Explorer Workplace

General User Interface

The Plant Explorer Workplace Window

Figure 4 shows an example of the Plant Explorer window.

Figure 4. The Plant Explorer Workplace Window

Compact HMI, System Version 6.0.1 is delivered as a software installation DVD.

Supported Standard PLCs

System Functions and Node Types

Compact HMI Installation Workflow

Figure 5. Compact HMI Installation Workflow

Computer management can only be done if the logged on user have

Figure 6. Computer Management Window

Figure 7. Creating a New User

Figure 8. User List

Figure 9. Adding New Group

8. Similar way, create a new group IndustrialITAdmin.

Figure 10. Adding SwServiceAccount as a Member

e. Similarly, add IndustrialITUser and Administrators. All the three group

Figure 11. User Properties Window

For Domain Environment

2. Add a new user SwServiceAccount as shown in Figure 12.

Figure 12. Adding New User

3. Create two groups in Active Directory Users and Computers,

Figure 13. Creating Groups

4. Add SwServiceAccount in the following groups:

Node Preparation Tool

Installation of Compact HMI Server

3. Enter the Password in the respective field. See Figure 14.

Figure 14. 800xA System Setup Window

4. Accept the License Agreement by selecting the checkbox.

Figure 15. Node Options Window

8. On successful completion, click Close on the System 800xA Installation

Figure 16. Preparation Progress Window

System Configuration Console

Figure 17. ABB Start Menu

Figure 18. Confirmation Message

Figure 19. System 800xA Configuration Console

4. Go to System Setup > Configure System on System 800xA Configuration

Figure 20. Selecting the System Functions