800xA for Safeguard

Configuration
System Version 5.1

Power and productivity

TM
for a better world
800xA for Safeguard
Configuration

System Version 5.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 referenced standard. In order to determine
the specific features supported by a particular ABB product, the reader should consult the
product specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intel-
lectual 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.

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

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

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license. This
product meets the requirements specified in EMC Directive 2004/108/EEC and in Low
Voltage Directive 2006/95/EEC.

TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.

Copyright © 2003-2012 by ABB.

All rights reserved.

Release: June 2012

Document number: 3BNP004848-510 A
 Table of Contents

About This Book

General ..............................................................................................................................7
Document Conventions .....................................................................................................7
Warning, Caution, Information, and Tip Icons..................................................................7
Terminology.......................................................................................................................8
Related Documentation .....................................................................................................9

Section 1 - Introduction
Product Overview ............................................................................................................11
Product Scope.......................................................................................................11
What you can do with 800xA for Safeguard........................................................12
Prerequisites and Requirements ...........................................................................12

Section 2 - Configuration
Before You Start ..............................................................................................................13
Libraries and Object Types..............................................................................................13
Getting Started.................................................................................................................15
Dual Handling .................................................................................................................16
Building the Control Structure ........................................................................................18
MB300 Uploader Aspect .................................................................................................21
Changing Settings of a Dual System ...............................................................................26
Defining Event Treatments using RTA Board Configuration..........................................27
DB Element NODE_DESCR ...............................................................................28
Configuration Example....................................................................................................37
Creating TTD Logs..........................................................................................................43
OPC Clients .....................................................................................................................44

3BNP004848-510 A 5
Table of Contents

NLS Support.................................................................................................................... 45

Appendix A - Event Handling

General ............................................................................................................................ 47
FI Event Handling................................................................................................ 49
GI Event Handling ............................................................................................... 52
Output Stage Event Handling .............................................................................. 54
Operation & Monitoring Event Handling ............................................................ 55
C&E Shutdown Levels Event Handling .............................................................. 57

INDEX

Revision History
Updates in Revision Index A........................................................................................... 63

6 3BNP004848-510 A
 About This Book

General
The 800xA for Safeguard enables the connection of 800xA Operator Workplace to a
MasterBus 300 control network with Safeguard Controllers.
The information in this book is intended for:
• The Engineer that sets up the safety system functionality (including defining
displays, configuring control parameters etc.)
• The System Administrator that sets up the safety system configuration
It is recommended to have a basic understanding of distributed automated process
control, the hardware and software functionality of the 800xA system.
The user should login as an Application Engineer or System Engineer (on the
workplaces) to perform the functionalities of 800xA for Safeguard.

Document 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 publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:

3BNP004848-510 A 7
Terminology About This Book

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

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

Caution icon indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

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

Terminology
A complete and comprehensive list of Terms is included in the System 800xA
Extended Automation Engineering Concepts instruction (3BDS100972*). The
listing included in Engineering Concepts includes terms and definitions as they 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.

8 3BNP004848-510 A
 About This Book Related Documentation

Term/Acronym Description
MB300 MasterBus 300 - the control network communication
protocol that is used by the AC 400 controllers
Safeguard Safeguard 400 Series, ABB’s safety controller based on
the AC400 Series. Also refers to the previous model,
Safeguard 3000.
SCS Safety Control System / Safety Control Station, the dual
safety system configuration of SG 3000 / Safeguard 400
Series consisting of two equally configured safety
controllers.
SC Safety Controller, refers to one of the nodes in a SCS.
SCA The safety controller with the lowest node number in a
SCS.
SCB The safety controller with the highest node number in a
SCS.
ESD system Emergency Shut-Down system.
PSD system Process Shut-Down system.

Related Documentation
A complete list of all documents applicable to the System 800xA Extended
Automation System is provided in Released User Documents (3BUA000263*). This
document lists applicable Release Notes and User Instructions. It is provided in
PDF format and is included on the Release Notes/Documentation media provided
with your system. Released User Documents are updated with each release and a
new file is provided that contains all user documents applicable for that release with
their applicable document number. Whenever a reference to a specific instruction is
made, the instruction number is included in the reference.

3BNP004848-510 A 9
Related Documentation About This Book

10 3BNP004848-510 A
 Section 1 Introduction

Product Overview
The Operator Workplace is used for process monitoring and control. It has a generic
design and can be used for different process control systems.
The 800xA for Safeguard is a software product that enables you to connect an
Operator Workplace to Safeguard Controllers in a MasterBus 300 network.

Product Scope
The 800xA for Safeguard is built on 800xA for Advant Master which is integrated
in the Operator Workplace. This provides the following features:
• Support for single and dual Safeguard controllers.
• Handling of dual controllers as one object in the operator’s workplace.
• Execution of operator commands in both controllers.
• Status and diagnostic display for both single and dual controllers.
• Faceplates, object displays and alarm/event handling consistent with AC400
Controllers.
The supported Safeguard functions and functional units are:
• FI (Fire Input), loop monitored digital inputs.
• FD (Fire Detector), for addressable detectors.
• GI (Gas Input), loop monitored analog inputs.
• Fireguard central, control and monitoring.
• AutroSafe central, control and monitoring.
• C&E shutdown level.

3BNP004848-510 A 11
What you can do with 800xA for Safeguard Section 1 Introduction

• Safeguard system status and control.

What you can do with 800xA for Safeguard

This list is an example of the engineering you can do with 800xA for Safeguard.
• Configure the connection of the workplace to Safeguard controllers on
MasterBus 300 control network.
• Setup the workplace for handling the process data defined in
the Safeguard controller’s database. You do not need to define the database
again, it is uploaded from the controllers over the network.
• Setup the event handling for the process events that are reported from the
Safeguard controllers.
• Collect and present System status for the Safeguard controllers.
• Apply filter to suppress display of events arising from a specified controller.

Prerequisites and Requirements

The general hardware and software requirements for the Operator Workplace
product are described in the instruction System 800xA Manual Installation
(3BSE034678*).

12 3BNP004848-510 A
 Section 2 Configuration

Before You Start

Ensure to have access to one of the following:
• The database instances from the Function Chart Builder.
• The Operator Workplace Connectivity Server connected to the Safeguard 400
controllers through the MasterBus 300 control network.
For more information on the Operator Workplace, refer to System 800xA Operations
Operator Workplace Configuration (3BSE030322*).

Libraries and Object Types

800xA for Safeguard defines a set of object types. An object type is a predefined
aspect object defined in the Object Type Structure.
Object types in 800xA for Safeguard (for example, SG 400 Dual System, MB300
FI, and MB300 GI) represent the data base element types in the AC 400 series
controller.
During upload from controllers, the Uploader aspect creates instances of the
controller objects with the respective object types in Control Structure.
Extension libraries can be easily activated or deactivated in a functioning system.
This is beneficial while working on VB process graphics. The user can deactivate
the PG2 extension, which removes the corresponding aspects from the system. The
extension library can be activated later when required.
The Safeguard object types are included in libraries in the 800xA system version 5.1
and later versions. The Base Library SafeguardObjectTypes defines all Safeguard
object types including the graphics independent aspects. The extension library
SafeguardObjectTypesPG2Ext defines all process graphics aspects, and

3BNP004848-510 A 13
Libraries and Object Types Section 2 Configuration

SafeguardObjectTypesVB6Ext library defines all VB process graphics aspects in the

object types.
The extension libraries SGObjectTypesPG2Ext and SGObjectTypesVB6Ext in the
Advant Master object types define all Safeguard specific PG2 and VBPG graphics.

Figure 1. 800xA for Safeguard Libraries in the Library Structure

Figure 2. Base Library SafeguardObjectTypes in the Object Type Structure

A library is in one of the following states, Open, Closed or Released.

14 3BNP004848-510 A
Section 2 Configuration Getting Started

After installation of the product, libraries are in the Closed state and are protected
from unintentional modifications. Custom modifications are possible if the library is
forced to the Open state. Observe that the modifications may be lost in future system
upgrades/updates.
The extension libraries SafeguardObjectTypesVB6Ext and SGObjectTypesVB6Ext
are included in the system extension, 800xA for Safeguard VB Extension. This
system extension is required for the users of VB process graphics.
For more information on library handling and object types, refer to System 800xA
Configuration (3BDS011222*).

Getting Started
The 800xA for Safeguard comprises operator station functions for a single or dual
controllers with identical data base content.
Consider the following scenarios to configure a Safeguard 400 system.
1. An existing plant where the controllers are configured and are functional.
2. A new plant where the controllers should be configured.

The Steps for an Existing Plant

1. Setup the parameters for the RTA Board (network and node addresses, time
synchronization, Character Conversion).
You can choose No Conversion (English), Swedish or German when configuring the
RTA Board.
2. Build the Control Structure (Retrieve the information about the Process and
System objects).
3. Modify (if required) the Alarm and Event default settings.
4. Retrieve (synchronize) the TTD logs in the controller and the corresponding
log hierarchies above them.

The Steps for the New system

1. Build the Controller Application

3BNP004848-510 A 15
Dual Handling Section 2 Configuration

a. Create and configure Process and System objects

b. Define Log groups (TTD)
c. Write your AMPL applications
2. Setup the parameters for the RTA Board (network and node addresses, time
synchronization).
3. Download the applications to the controllers.
4. Build the Control Structure (Retrieve the information about the Process
and system objects).
5. Modify (if required) the Alarm and Event default setting.
6. Configure the TTD logs in the controller and the corresponding log hierarchies
above them.
The Engineering of the controllers and the various steps to perform is not described
in this book. Please read the corresponding User´s Guides.
On time synchronization and setting up the RTA board refer to System 800xA
Automation System Network Design and Configuration (3BSE034463*).

Dual Handling
To achieve dual handling of controllers in the operator workplace, a dual Safeguard
system has to be specified in the data base element NODE_DESCR on the RTA
board. If a dual system is not specified correctly in the NODE_DESCR the
Safeguard system will be treated as a single controller. Layout of the database
element NODE_DESCR is shown in Section 2, Configuration. An illustration of the
dual handling is given in Figure 3.

16 3BNP004848-510 A
Section 2 Configuration Dual Handling

Operator

COMMAND STATUS

Commands, Indications,
value changes, alarms,
events, trends

Safety controller A

DB
I/O I/O PC

Monitoring
PROCESS Safety controller B
DEVICE
Monitoring

I/O I/O DB PC

Figure 3. Block Diagram of Dual Handling

3BNP004848-510 A 17
Building the Control Structure Section 2 Configuration

Building the Control Structure

The Control Structure is based on the controllers in the MB300 network. To build
the structure, do as follows:
• Create an MB 300 Network object at the top level of the Control Structure. It is
recommended to use the Configuration Wizard (select ‘Add RTA’).
• Select the Network object and add Safeguard nodes below. Figure 4 shows the
possible node types that can be selected.
• Select character conversion on the RTA Board. This to prevent incorrect
naming, for example “[H\G NIV]” instead of “HÖG NIVÅ” in a Swedish
system. When changing character conversion, default databases are loaded to
the RTA board. All created NODE_DESCR are removed, and modified
EVENT databases are overwritten with default parameters. If character
conversion is selected after the upload and a new upload is done, object names
might change and any configuration (like displays) using this object, will be
lost as the object is moved and a new object is created.
• Execute the Upload procedure for each Safeguard system (as described on
the next pages) to display the whole structure of I/O boards and Process and
System objects.
You can display one Safeguard system at a time or one or a couple of object types at
a time. The MB 300 Uploader retrieves the required information from the
controllers and creates the corresponding objects and aspects in the Control
Structure.
To create a complete Control Structure:
1. Select the Control Structure in Plant Explorer.
2. Select New Object from the context menu.

18 3BNP004848-510 A
Section 2 Configuration Building the Control Structure

3. Select the Controller type object. Request creation of a new object and select a
Controller type, see Figure 4. It is recommended to include the node number in
the object name.

Figure 4. Safeguard Node Objects

The following Safeguard Object Types are available for selection:

• Safeguard 3000 Controller, one branch.
• Safeguard 3000 Dual System, two branches.
• Safeguard 9000 Controller, one branch.
• Safeguard 9000 dual system, two branches.
• Safeguard 400 Controller, one branch.
• Safeguard 400 Dual System, two branches.
For older systems of type EBXMP200, use the Safeguard 9000 object types. See
EBXMP200 Node Type on page 36 regarding the EBXMP200 configuration
Do not select Safeguard Single Node Access object. It is created automatically, in
dual systems, as a container of the two control branches.

3BNP004848-510 A 19
Building the Control Structure Section 2 Configuration

4. On Next... the ‘Additional Arguments’ window appears. This depends on the

selection of a single system (see Figure 5) or a dual system (see Figure 6) in the
previous step.
The arguments for a single Safeguard are the same as for an AC410 controller.
Enter the node number and click on the Create button.

Figure 5. Additional Arguments for Single Safeguard

The arguments for a dual Safeguard system are:
– node numbers for each controller (branch of the system).
– virtual node number in the range 200 - 250. This number is assigned to a
virtual Safeguard object that represents the dual Safeguard system in the
control structure.
– upload source controller (branch). Side A or B of the Safeguard system
can be assigned as default source for upload. The value can be altered
later. On the upload function see next section.
– name extension for each branch of a Safeguard system. The extension is
added to object names as a suffix in order to identify which branch of a
system they belong to.

20 3BNP004848-510 A
Section 2 Configuration MB300 Uploader Aspect

Figure 6. Additional Arguments for Dual Safeguard System

5. Select the node and bring up the MB 300 Uploader aspect to start the upload,
see Figure 7.

MB300 Uploader Aspect

MB300 Uploader aspect supports retrieval of data from the controller and
automatically builds up a control structure with objects subordinated to the
controller object. The user can upload all the available objects or only the objects of
one or several object types (e.g. analogue inputs). In the latter case click on the Add
button (see Figure 7) to select the object types for the upload. After you have made
the selection click on Apply. For a controller with many objects of certain types it

3BNP004848-510 A 21
MB300 Uploader Aspect Section 2 Configuration

may be wise to upload at least the most populated object types one by one before
proceeding with the others.
The Function Chart Builder (FCB) uploader released with Control Builder A
does not function with the FI, GI, and FD function units.
The FD objects should be transferred to Fire Input Normally Closed (FINC) or
Fire Input Normally Open (FINO) objects in the source code before translating
the source code to FCB. The FINO, FINC, and GISI (Gas Input Calculated)
objects having the parameters (306,0) / (305.0) on the IO board will not be
uploaded from the FCB in an accurate manner. Update this parameter to an empty
value before translating the source code to FCB.

22 3BNP004848-510 A
Section 2 Configuration MB300 Uploader Aspect

Figure 7. MB300 Uploader Aspect

3BNP004848-510 A 23
MB300 Uploader Aspect Section 2 Configuration

The MB 300 Uploader aspect has two tabs:

• The From Controller tab that contains functions to upload the data directly
from the controllers (via the MB 300 network).
• The From FCB tab that contains functions to upload the data from a source
file. The source file is created with the Function Chart Builder (FCB)
engineering tool. For details on this see 800xA for Advant Master
Configuration (3BSE030340*).

Using the From Controller tab to Upload

Click Add or Remove to modify the list with object types that you want to include
in the Upload. If you leave the list blank, all object types are included (this is
default).
Mark the Create Uploader Source File and the Build Control Structure check
boxes. These check boxes should always be marked. They are only used for fault
tracing and simulation, and should not be modified. They should only be modified
on direct request from the supplier.
Click on Start Upload when you are ready for the upload. The upload process will
start and run automatically until finished.The window in the lower part of the aspect
view displays messages describing the progress, see Figure 7.
Click on Stop Upload if you want to interrupt the upload.
Uploading can take some time. When complete, use Plant Explorer to browse the
control structure and verify that everything is in place as expected.
The uploading process will create control structures for both branches (Side A and
Side B), as well as the virtual Safeguard node when a Safeguard Dual system is
being uploaded.
Figure 8 shows an extract of the control structure after an Upload has been
performed.

24 3BNP004848-510 A
Section 2 Configuration MB300 Uploader Aspect

Figure 8. Board and Channel Objects in a Control Structure after an Upload

3BNP004848-510 A 25
Changing Settings of a Dual System Section 2 Configuration

Changing Settings of a Dual System

The following arguments for a Dual Safeguard system can be changed after a
system has been configured:
• Virtual node number,
• Node numbers of each branch (side A or B),
• Uploader source. The branch which serves as a source for the MB300
Uploader.
To view the current settings select the main view of the Safeguard Dual
Configuration aspect. To change the settings you have to select the configuration
view as shown on Figure 9.

Figure 9. Dual Configuration Aspect

26 3BNP004848-510 A
Section 2 Configuration Defining Event Treatments using RTA Board Configuration

The name extension is entered when a Safeguard object is initially created. It can
not be altered later. Empty string is not allowed as name extension.
When a node number is changed you have to reconfigure the NODE_DESCR
database element (see Section 2, Configuration). This must be done in both
connectivity servers in a redundant pair. A new upload must be performed as
well.

Defining Event Treatments using RTA Board

Configuration
You define the Event treatment by configuring data base elements on the RTA
Board. After setting up the database on the RTA Board, you shall save the database
configuration. For details on RTA Board Control aspects refer to 800xA for Advant
Master Configuration (3BSE030340*).
See Appendix A, Event Handling for configuration of Safeguard specific Event data
base elements.
For each branch of a dual Safeguard system, a database element of type
NODE_DESCR has to be created. This element holds set-up parameters for dual
handling associated with a Safeguard system. It consists of three groups of
parameters:
• Controller’s name, description, network and node number.
• Parameters for dual treatment.
• Test parameters for enabling single node operation.
• Signal filtering.
• Support for EBXMP200 node types.
Start an on-line session towards the RTA board and create a pair of NODE_DESCR
instances for each dual system that is being configured. For details see the next
section.
Whenever a change is made to a NODE_DESCR database element, a backup
and restart of the RTA Board is required. Otherwise the changes made will not
be implemented. The exception is Signal filtering configuration.

3BNP004848-510 A 27
DB Element NODE_DESCR Section 2 Configuration

DB Element NODE_DESCR

NODE_DESCR1

Node Description
(134.1)
S1 Base part
NAME
DESCR S2 Dual Parameters
VERSION
ACT S3 Signal filtering
NETW_NO
NODE_NO S4 Test parameters

Base part S5 EBXMP200 Settings

VIR_NODE ERROR
TTD_SEL
TTD_CONF

Dual Parameters

EVENT SNG_DIAL EBXMP200

STATLIST ACT_SUP OBFGEN
DIAL_SUP
Signal filtering EBXMP200 Settings
Test parameters

Figure 10. NODE_DESCR Element, Overview

NODE_DESCR1
Node Description
Item designation: NODE_DESCRx
(134.1) Data Base Index
Element type: Node Description
Call name: NODE_DESCR

Figure 11. NODE_DESCR Header

28 3BNP004848-510 A
Section 2 Configuration DB Element NODE_DESCR

NODE_DESCR1

Node Description
(134.1)
NODE_DESCR 1 NAME
2 DESCR
7 VERSION
1 3 ACT
0 4 NETW_NO
0 5 NODE_NO

S2 Dual Parameters

S3 Signal filtering

S4 Test Parameters

S5 EBXMP200 Settings

Figure 12. NODE_DESCR Element, Base Part

Table 1. NODE_DESCR element, Base part

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
1 NAME User NODE_ - Controller (node) NAME Max. 12
DESCRx characters
2 DESCR User - - Controller (node) Max. 20
DESCRiption. characters
3 VERSION User - - Controller (node) Max. 12
VERSION designation. characters
4 ACT User 1 - The function is ACTive 1=Active
or disabled.

3BNP004848-510 A 29
DB Element NODE_DESCR Section 2 Configuration

Table 1. NODE_DESCR element, Base part (Continued)

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
5 NETW_NO User 0 - NETWork Number for Values: 0 - 99.
connected controller Redundant
network: Specify
one of the
networks.
Changes require
backup and
restart of the RTA
Board.
6 NODE_NO User 0 - NODE Number for the Values: 0 - 99
controller

NODE_DESCR1

Node Description
(134.1)
S1 Base Part

0 8 VIR_NODE ERROR 9
0 10 TTD_SEL
0 11 TTD_CONF
S3 Signal filtering

S4 Test Parameters

S5 EBXMP200 Settings

Figure 13. NODE_DESCR Element, Dual Parameters

30 3BNP004848-510 A
Section 2 Configuration DB Element NODE_DESCR

Table 2. NODE_DESCR element, Dual parameters

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
8 VIR_NODE User 0 - VIRtual NODE number. Values: 200 ->
For a dual system, two 250.
instances have to be 0 = the node is
specified (Side A and B) not considered
with the same part of a dual
VIR_NODE value. system
10 TTD_SEL User 0 - TTD SELects data from If this parameter
this node. Can be set to is set to false for
true (1) for one of the both branches,
branches in a dual the first to be
system. accessed will be
the log data
source as long as
it is running.
11 TTD_CONF User 0 - TTD is possible to If this parameter
CONFigure even if the is set to 1,
opposite branch is not inconsistency in
available. TTD-logs in the
both branches
may occur.
This parameter is
automatically
reset when both
branches are
available
9 ERROR System - - ERROR indication.
Result of a configuration
error.

3BNP004848-510 A 31
DB Element NODE_DESCR Section 2 Configuration

NODE_DESCR1

Node Description
(134.1)
S1 Base Part

S2 Dual Parameters
13 EVENT
14 STATLIST
S4 Test parameters

S5 EBXMP200 Settings

Figure 14. NODE_DESCR Element, Signal Filtering

Table 3. NODE_DESCR element, Signal Filtering

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
13 EVENT User 0 - Enables/disables event 0 =event reporting
reporting from the 1 = no event
actual controller. reporting to the
current CS(1).
14 STATLIST User 0 - Includes/Excludes the 0 = node is
actual controller from included.
status list searches. 1 = node is
excluded.
(1) Connectivity Server.

32 3BNP004848-510 A
Section 2 Configuration DB Element NODE_DESCR

Event Filtering
The main purpose of the Event Filtering function is to prevent alarm and event
messages from being sent from controllers in one MB300 network to Operator
Workplaces in another, across networks which are interlinked via a gateway node.
The function can be used for filtering within the same network as well. To filter out
event and alarm messages, the NODE_DESCR element properties ACT and
EVENT must be set to “1”.
The filter settings are used by a Connectivity Server to determine which controllers
it should ignore with respect to alarm and event messages.
If the filter settings are updated with a new controller, this new controller will
continue sending alarm and event messages to the Operator Workplaces until it is
restarted. This situation is prevented from occurring if the Connectivity Server
contains a correct NODE_DESCR data base at the time of the initial start-up, or
before any other controllers are connected to the network. To avoid restart of a
controller the following procedure must be followed:
• Connect On-Line Builder to one of controllers to be filtered and give
commands:
LOCPSET: CMDS:TP01.CT
OMVT
• The following menu will appear:
1) List contents of Master View table.
2) Remove a node from Master View table.
3) Remove all nodes from Master View table.
4) Add a node to Master View table.
5) Quit.
• Type 1 for 'List...'
• Type 2 and enter the network/node number for the Connectivity Server (RTA).
• Type 1 for 'List...' to verify that the Connectivity Server node now is removed
from the table.
• Repeat the above steps for all controllers to be filtered.

3BNP004848-510 A 33
DB Element NODE_DESCR Section 2 Configuration

The above procedure can not be used for old MasterPiece controllers.

Status List Filtering

Node = 0 as search key for a status list (Quick List aspect) means that all controllers
in the system will be searched. However, this signal filtering function offers the
opportunity to “filter out” specified nodes from such searches.

For every node not to be included in status list searches, there must be a data base
element of the type NODE_DESCR in the Connectivity Server involved and the
element properties ACT and STATLIST set to “1”.

The filter settings are used by a Connectivity Server to determine which nodes not to
send status list search requests to.

NODE_DESCR1
Node Description
(134.1)

S1 Base Part

S2 Dual Parameters
S3 Signal filtering

24 SNG_DIAL
22 ACT_SUP
23 DIAL_SUP

S5 EBXMP200 Settings

Figure 15. NODE_DESCR Element, Test Parameters

34 3BNP004848-510 A
Section 2 Configuration DB Element NODE_DESCR

Table 4. NODE_DESCR element, Test Parameters

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
24 SNG_DIAL User 0 - Single side Dialog 1 = single side
access. access enabled.
Enables/disables dialog Should be used
access towards objects for test purposes
in the current side of a only.
dual system.
22 ACT_SUP User 0 - Activates suppression Applicable only
of dual handling. Valid when the Single
for all functions except Side Testability
operator commands. option is installed.
23 DIAL_SUP User 0 - Activate suppression of If you are not
dual handling for using this option,
operator commands. keep the default
values.

Single Side Testability

The Single Side Testability function is an extension to Introduction which allows an
operator to temporarily override the dual handling of a Safeguard system and handle
the both sides (branches) as single nodes. The function is intended for use in test
situations when, for instance, an application upgrade is to be tested in an operating
system. Single side handling is initiated when test activities involving Safeguard
systems are carried out. All the Operator Workplaces are then turned to Test mode
of operation and handles the controllers in dual Safeguard systems as single nodes.

3BNP004848-510 A 35
DB Element NODE_DESCR Section 2 Configuration

NODE_DESCR1

Node Description
(134.1)
S1 Base Part

S2 Dual Parameters
S3 Signal filtering

S4 Test parameters

25 EBXMP200
26 OBFGEN

Figure 16. NODE_DESCR Element, EBXMP200 Settings

Table 5. NODE_DESCR element, EBXMP200 parameters

Value PC con-
Termi- Terminal Default
entered nection Description Remarks
nal No Name value
by data type
25 EBXMP200 User 0 - Enable support for
EBXMP200 node type
in the current controller.

26 OBFGEN User 0 - Enable support for GENUSD3 object

OBFGEN database type is occupied
element in the current in the system
controller. when this
property is
applied.

EBXMP200 Node Type

EBXMP200 is designation for a customized node type based on MP200 controllers.
This type of nodes is mostly used in the North Sea oil and gas installations.

36 3BNP004848-510 A
Section 2 Configuration Configuration Example

OBFGEN database
The OBFGEN database element is applicable only in the EBXMP200 controllers.
It provides connection between the related PC element OBFI-G and the Operator
Workplace. All changes on inputs in OBFI-G are transmitted to the Operator
Workplace as events. GENUSD3 object type with its Faceplate aspect is used as
graphical interface. Orders issued via Faceplates are transmitted to the related
OBFI-G outputs.

Configuration Example
The following example focus on a dual Safeguard system as configuring a single
Safeguard system is similar to configuring AC410 controller.
This description of the procedure for configuring a dual Safeguard system assumes
the following configuration:
The created network number is 11, and network name is netw11.
The dual Safeguard system name is System 250.
Virtual node number for the system is chosen to be 250.
Node number of the branch A (side A) is 51 and the branch B 52.
The virtual network number is by default equal to the side A’s network number.
As you create a functioning system, write down the values and parameters you have
chosen, and use those values where needed.
Here follows a step by step tutorial on how to create a dual Safeguard system.
1. Right-click on the already created MB300 network object called netw11 and
select New Object from the context menu.
2. From the list of available node objects select SG400 Dual System and enter a
suitable name in the Name field - here the name is System 250. Click Next.

3BNP004848-510 A 37
Configuration Example Section 2 Configuration

3. In the Additional Arguments tab (Figure 17) enter the virtual node number 250,
the numbers of both branches (51 and 52) as well as the default uploader source
(select Side A). Finally click on the Create button.

Figure 17. Additional Arguments for Safeguard Dual System

38 3BNP004848-510 A
Section 2 Configuration Configuration Example

The control structure created as result of step 3 is shown on Figure 18. Note the SG
Single Node Access object automatically created as a container for the subordinated
system branches (side A and B).

Figure 18. Safeguard Dual System in the Control Structure

4. Select the MB300 Uploader aspect of System 250 and click Start Upload.
Await the progress bar until it is finished. Part of the control structure uploaded
is shown on Figure 19.

3BNP004848-510 A 39
Configuration Example Section 2 Configuration

Figure 19. Safeguard Dual System with Uploaded Objects

5. Select RTA Board Control aspect of the System 250 and in the RTA Board
Configuration tab click on RTA Board Config to start an On-line Builder
session.

40 3BNP004848-510 A
Section 2 Configuration Configuration Example

6. Issue the command crdb node_descr - create two instances and fill in
properties as shown below.

NODE_DESCR1

Node Description
(134.1)

NODE_DESCR1 1 NAME
2 DESCR
7 VERSION
1 3 ACT
11 4 NETW_NO
51 5 NODE_NO

S2 Dual Parameters

S3 Signal filtering
S4 Test Parameters

S5 EBXMP200 Settings

NODE_DESCR1

Node Description
(134.1)
S1 Base Part
250 8 VIR_NODE ERROR 9
0 10 TTD_SEL
0 11 TTD_CONF
S3 Signal filtering
S4 Test Parameters

S5 EBXMP200 Settings

3BNP004848-510 A 41
Configuration Example Section 2 Configuration

NODE_DESCR2

Node Description
(134.2)

NODE_DESCR2 1 NAME
2 DESCR
7 VERSION
1 3 ACT
11 4 NETW_NO
52 5 NODE_NO

S2 Dual Parameters

S3 Signal filtering

S4 Test Parameters

S5 EBXMP200 Settings

NODE_DESCR2

Node Description
(134.2)
S1 Base Part

250 8 VIR_NODE ERROR 9

0 10 TTD_SEL
0 11 TTD_CONF
S3 Signal filtering
S4 Test Parameters
S5 EBXMP200 Settings

7. Issue the command tsess to close the On-line Builder window.

8. Select RTA Board Control aspect and click RTA Board Backup to save your
configuration.
Select the tab RTA Board Control
Click Stop and wait for a while.
Click Start. Await for a message confirming the RTA Board start-up.
The Safeguard dual system is now configured. Proceed with the next system in the
same way.

42 3BNP004848-510 A
Section 2 Configuration Creating TTD Logs

Creating TTD Logs

Configuration of TTD logs, data collection and presentation of trend data in the
Operator Workplace is described in detail in System 800xA Configuration
(3BSDS011222*).
For upload of TTD logs and user interfaces specific for AC400 and Safeguard 400
controllers see System 800xA for Advant Master Configuration (3BSE030340*).
Safeguard specific check box messages may occur during Trend/TTD configuration.
Examples of such a messages are shown on Figure 20 and Figure 21. The messages
are displayed when only one branch of a Safeguard system is in operation. The
messages must be acknowledged by answering OK.

Object Access in a Single Safeguard Branch

Access to objects in a single branch (side A or B) is not allowed when you try to
configure Trend/TTD log in one branch only.

Figure 20. Single Configuration is not Allowed

3BNP004848-510 A 43
OPC Clients Section 2 Configuration

Config not Allowed when one Node is Unavailable

Configuration of Trend/TTD log is not allowed while only one branch is in
operation.

Figure 21. Config not Allowed with only one Branch in Operation.

One side of a dual system can be available for TTD configuration when the single
configuration is enabled in the NODE_DESCR database element.

OPC Clients
Introduction supports the OPC Data Access and OPC Alarm and Event Server
functionality in Process Portal. Using these OPC interfaces any 3rd party OPC
Client may access information on Safeguard objects. Data associated with both
virtual and real objects is available.
A subscription towards a Safeguard object via OPC Data Access will behave
similarly to subscription towards objects in the AC 400 System Extension with one
exception. In a discrepancy situation (unequal status in Side A and B) status data on
the virtual object will be returned with a higher frequency than in a normal situation.
The frequency will also exceed the specified cycle time requested by the subscriber.

44 3BNP004848-510 A
Section 2 Configuration NLS Support

NLS Support
Introduction complies with the Native Language Support (NLS) concept which is
integrated in the 800xA System.
Exception:
Name of the ‘MB300 Uploader Extended Handling’ aspect is not treated by NLS
and shall not be translated to any language. This exception does not apply to the
aspect description.

3BNP004848-510 A 45
NLS Support Section 2 Configuration

46 3BNP004848-510 A
 Appendix A Event Handling

General
This appendix contains a description of alarms and events in the various functional
units applicable with the Safeguard system. The description is given under the
following headings:
• FI Event Handling on page 49
• GI Event Handling on page 52
• Output Stage Event Handling on page 54
• Operation & Monitoring Event Handling on page 55
• C&E Shutdown Levels Event Handling on page 57
Event handling is described in detail in the System 800xA documentation.
AUDIBLE. Must be 0 for events and 1 for alarms. See System 800xA
Configuration (3BDS011222*) for configuration of Audible Alarms.
The event texts for all relevant functional units are also collected in the manuals
800xA for Safeguard Graphic Library (3BSE044423*), giving the user a convenient
quick reference during the application building.

3BNP004848-510 A 47
General Appendix A Event Handling

The event handling is controlled by configuration parameters, EVENT-TREAT

pointers, in the data base element located in the Safeguard controller.

Safeguard 400 Series Advant Station 500 Series Operator Station

Data Base Element

Event Treat
Z Event
X Pointers
Z
:
: Y
:
X

Z Event
Y Pointers

Figure 22. Principle of Event Handling in Fire Input

The Event Treat defines the event handling in the operator station such as audible
alarms, text combinations in event and alarm list, colors, different handling for 0 --
>1 and 1 -->0 transitions.
How different events from the functional units are treated is given in the following
sections.

48 3BNP004848-510 A
Appendix A Event Handling FI Event Handling

FI Event Handling

Event Description with Standard Texts

Table 6. Predefined EVENT Elements for FI

Event
Property
301 302
AUDIBLE 1 0
ALARM_PRIO 2 2
ALARM_TO_BLK F T
ALARM_FROM_BLK T T
PERSIST_LIST_BLK F T
TEXT_TO_BLK F F
TEXT_FROM_BLK F F
TEXT_COMB_CODE 5 5

Table 7. Event Texts for FI

Event Property text Event text

Events Treat Standard Line No in Standard Line No in
pointer text Event Treat(1) text Event Treat(2)
Alarm on AL_TR Alarm 1 On 1
Alarm off AL_TR Alarm 1 Off 2
Manual entry on AL_TR Alarm 2 Value Ch. 3
Manual entry off AL_TR Alarm 2 Value Ch. 4
Prewarn on (3) AL_TR Prewarn 4 On 1
Prewarn off (3) AL_TR Prewarn 4 Off 2

3BNP004848-510 A 49
FI Event Handling Appendix A Event Handling

Table 7. Event Texts for FI (Continued)

Event Property text Event text

Events Treat Standard Line No in Standard Line No in
pointer text Event Treat(1) text Event Treat(2)
Signal error on ERR_TR Sign.Err 1 On 1
Signal error off ERR_TR Sign.Err 1 Off 2
Fatal earth fault on ERR_TR FtEaFlt 2 On 1
Fatal earth fault off ERR_TR FtlEaFlt 2 Off 2
Open circuit on ERR_TR Open C 3 On 1
Open circuit off ERR_TR Open C 3 Off 2
Short circuit on ERR_TR Short C 4 On 1
Short circuit off ERR_TR Short C 4 Off 2
Out of range on ERR_TR Out of R 5 On 1
Out of range off ERR_TR Out of R 5 Off 2
Alarm block on ERR_TR Al.Blk 6 On 3
Alarm block off ERR_TR Al.Blk 6 Off 4
Print block on ERR_TR Pr.Blk 7 On 3
Print block off ERR_TR Pr.Blk 7 Off 4
DB update blocked ERR_TR Upd.Blk 8 On 3
DB updt. deblocked ERR_TR Upd.Blk 8 Off 4
Inhibit on ERR_TR Inhibit 9 On 3
Inhibit off ERR_TR Inhibit 9 Off 4
Power failure on ERR_TR Pow.Fail 10 On 1
Power failure off ERR_TR Pow Fail 10 Off 2

50 3BNP004848-510 A
Appendix A Event Handling FI Event Handling

Table 7. Event Texts for FI (Continued)

Event Property text Event text

Events Treat Standard Line No in Standard Line No in
pointer text Event Treat(1) text Event Treat(2)
Earth fault on ERR_TR EarthFlt 11 On 1
Earth fault off ERR_TR EarthFlt 11 Off 2
Auto Inhibit on ERR_TR Auto.Inh 12 On 3
Auto Inhibit off ERR_TR Auto.Inh 12 Off 4
(1) Line number in indicated EVENT_TREAT element for user-defined property text.
(2) Line number in indicated EVENT_TREAT element for user-defined event text.
(3) Used only by the FD type (variant 5) which is not part of the Safeguard 3000™ product

3BNP004848-510 A 51
GI Event Handling Appendix A Event Handling

GI Event Handling

Event Description with Standard Texts

Table 8. Predefined EVENT Elements for GI

Event
Property
303 304 305
AUDIBLE 1 1 0
ALARM_PRIO 2 2 2
ALARM_TO_BLK F F T
ALARM_FROM_BLK T T T
PERSIST_LIST_BLK F F T
TEXT_TO_BLK F F F
TEXT_FROM_BLK F F F
TEXT_COMB_CODE 5 5 5

Table 9. Event Texts for GI

Property text Event text

Event Treat Line No in Line No in
Events Standard Standard
pointer Event Event
text text
Treat(1) Treat(2)
Low alarm on LO_AL_TR L Alarm 1 On 1
Low alarm off LO_AL_TR L Alarm 1 Off 2
Low alarm changed LO_AL_TR L Alarm 1 Value Ch 6
Manual entry LO_AL_TR ValueLel 3 Value Ch 5
High alarm on HI_AL_TR H Alarm 1 On 1

52 3BNP004848-510 A
Appendix A Event Handling GI Event Handling

Table 9. Event Texts for GI (Continued)

Property text Event text

Event Treat Line No in Line No in
Events Standard Standard
pointer Event Event
text text
Treat(1) Treat(2)
High alarm off HI_AL_TR H Alarm 1 Off 2
High alarm chngd. HI_AL_TR H Alarm 1 Value Ch 5
Signal error on ERR_TR Sign.Err 1 On 1
Signal error off ERR_TR Sign.Err 1 Off 2
Loop fault on ERR_TR Loop Err 2 On 1
Loop fault off ERR_TR Loop Err 2 Off 2
Alarm block on ERR_TR Al.Blk 3 On 3
Alarm block off ERR_TR Al.Blk 3 Off 4
Print block on ERR_TR Pr.Blk 4 On 3
Print block off ERR_TR Pr.Blk 4 Off 4
DB update blocked ERR_TR Updt.Blk 5 On 3
DB updt. deblocked ERR_TR Updt.Blk 5 Off 4
Inhibit on ERR_TR Inhibit 6 On 3
Inhibit off ERR_TR Inhibit 6 Off 4
Power failure on(3) ERR_TR Pow.Fail 7 On 1
Power failure off (3) ERR_TR Pow.Fail 7 Off 2
Calibration error on ERR_TR Cal.Err. 8 On 3
Calibration error off ERR_TR Cal.Err. 8 Off 4
Maintenance status ERR_TR Maintn. 9 On 1
on(4)

3BNP004848-510 A 53
Output Stage Event Handling Appendix A Event Handling

Table 9. Event Texts for GI (Continued)

Property text Event text

Event Treat Line No in Line No in
Events Standard Standard
pointer Event Event
text text
Treat(1) Treat(2)
Maintenance status ERR_TR Maintn. 9 Off 2
off(4)
Calibration on 0% ERR_TR Cal. 12 0% 6
Calibration on X% ERR_TR Cal. 12 X% 5
Start test ERR_TR Test 13 On 7
Reset test ERR_TR Test 13 Off 8
(1) Line number in indicated EVENT_TREAT element for user-defined property text.
(2) Line number in indicated EVENT_TREAT element for user-defined event text.
(3) Used for catalytic gas inputs.
(4) Used for AI type inputs.

Output Stage Event Handling

Output stage errors are annunciated to the operator as alarms to the operator station
alarm list:
• Individual output channel errors are annunciated as OUTPUT ERROR alarm.
• Termination unit isolation errors are annunciated as ISOLATE ERROR alarm.
Two isolation situations are also treated as events:
• The normal operator commands for isolation and reset isolation of all units are
event treated as OUTPUT ISOL. ON/OFF, including side /A or /B.
• Forced isolation due to termination unit channel error is event treated as
FORCED ISOL. ON/OFF, as additional information to the isolate error alarm.
More detailed information about the error situation is given in the Safeguard system
message display.

54 3BNP004848-510 A
Appendix A Event Handling Operation & Monitoring Event Handling

Operation & Monitoring Event Handling

Event Description with Standard Texts

Table 10. Predefined EVENT Elements for the Safeguard status Object

Event
Property
314 315 316 317
AUDIBLE 1 0 1 0
ALARM_PRIO 2 4 2 4
ALARM_TO_BLK F T F T
ALARM_FROM_BLK T T T T
PERSIST_LIST_BLK F T F T
TEXT_TO_BLK F F F F
TEXT_FROM_BLK F F F F
TEXT_COMB_CODE 5 5 5 5

Reported Alarms
The alarm handling is treated as single for each Safeguard controller side. The alarm
texts are identical in both controller sides, but the reporting side is identified by the
addition of /A or /B in the event text section. An alarm is usually accompanied by an
additional message.

3BNP004848-510 A 55
Operation & Monitoring Event Handling Appendix A Event Handling

The alarms defined for Side A are listed below:

Table 11. Reported Alarms from Safeguard System’s Side A

Property text Event text

Event Treat
Events Standard Line No in Standard Line No in
pointer
text Event Treat text Event Treat
IND1_00 on IND1_TR System 1 Alarm /A 1
IND1_00 off IND1_TR System 1 Normal /A 2
IND1_01 on IND1_TR Config 2 Alarm /A 1
IND1_01 off IND1_TR Config 2 Normal /A 2
IND1_02 on IND1_TR I/O 3 Alarm /A 1
IND1_02 off IND1_TR I/O 3 Normal /A 2
IND1_03 on IND1_TR Output 4 Alarm /A 1
IND1_03 off IND1_TR Output 4 Normal /A 2
IND1_04 on IND1_TR Isolate 5 Alarm /A 1
IND1_04 off IND1_TR Isolate 5 Normal /A 2
IND1_05 on IND1_TR Readback 6 Alarm /A 1
IND1_05 off IND1_TR Readback 6 Normal /A 2
IND1_06 on IND1_TR C&E Comm 7 Alarm /A 1
IND1_06 off IND1_TR C&E Comm 7 Normal /A 2
IND1_07 on IND1_TR C&E Int. 8 Alarm /A 1
IND1_07 off IND1_TR C&E Int. 8 Normal /A 2
IND1_09 on IND1_TR Byp.Prew 10 Alarm /A 1
IND1_09 off IND1_TR Byp.Prew 10 Normal /A 2
IND1_10 on IND1_TR Shd.Prew 11 Alarm /A 1
IND1_10 off IND1_TR Shd.Prew 11 Normal /A 2

56 3BNP004848-510 A
Appendix A Event Handling C&E Shutdown Levels Event Handling

Reported Events
The event handling is treated as single for each Safeguard system side. The event
texts are identical in both controllers, but the reporting side is identified by the
addition of /A or /B respectively in the event text section. An event is usually
accompanied with an additional message.
The events defined for Side A are listed below:

Table 12. Reported Events from Safeguard System’s Side A

Property text Event text

Event Treat
Events Standard Line No in Standard Line No in
pointer
text Event Treat text Event Treat
IND2_00 on IND2_TR OutpIsol 1 On /A 1
IND2_00 off IND2_TR OutpIsol 1 Off /A 2
IND2_01 on IND2_TR ForcIsol 2 On /A 1
IND2_01 off IND2_TR ForcIsol 2 Off /A 2
IND2_02 on IND2_TR Byp.Key 3 On /A 1
IND2_02 off IND2_TR Byp.Key 3 Off /A 2

C&E Shutdown Levels Event Handling

ESD level event treatment is normal single event treatment from dual nodes, without
reference to controller side and the ESD level states are treated as events:
ESD COMMANDED - The ESD level is activated by operator.
ESD ON - The ESD level is activated.
ESD OFF - The ESD level is reset.
OVERRIDE ON - The ESD level is overridden.
OVERRIDE OFF - ESD level override is removed.

3BNP004848-510 A 57
C&E Shutdown Levels Event Handling Appendix A Event Handling

How the different events from User Control ESD levels are treated is given in
Table 13 below. This also specifies which event handling is obtained as default and
which alternative standard functions are available.

Table 13. Predefined EVENT Objects for ESD-Level

Event
Property
318 319
AUDIBLE 0 0
ALARM_PRIO 4 4
ALARM_TO_BLK T T
ALARM_FROM_BLK T T
PERSIST_LIST_BLK T T
TEXT_TO_BLK F F
TEXT_FROM_BLK T F
TEXT_COMB_CODE 5 5

Reported Events
The events defined are listed below:

Table 14. Predefined EVENT Objects for ESD-Level

Event
Property
318 319
AUDIBLE 0 0
ALARM_PRIO 4 4
ALARM_TO_BLK T T
ALARM_FROM_BLK T T
PERSIST_LIST_BLK T T

58 3BNP004848-510 A
Appendix A Event Handling C&E Shutdown Levels Event Handling

Table 14. Predefined EVENT Objects for ESD-Level (Continued)

Event
Property
318 319
TEXT_TO_BLK F F
TEXT_FROM_BLK T F
TEXT_COMB_CODE 5 5

3BNP004848-510 A 59
C&E Shutdown Levels Event Handling Appendix A Event Handling

60 3BNP004848-510 A
 INDEX
C
Connectivity Server 13, 33

D
Dual Handling 16

E
EBXMP200 19, 36
Event Filtering 33
Event Handling
General 47

M
MasterBus 300 11
MB300 network 18
MB300 Uploader aspect 21

N
NLS Support 45
NODE_DESCR 16, 28

O
OPC Clients 44

Q
Quick List 34

R
Revision History 63
RTA Board 15

3BNP004848-510 A 61
Index

62 3BNP004848-510 A
 Revision History

This section provides information on the revision history of this User Manual.
The revision index of this User Manual is not related to the 800xA 5.1 System
Revision.
The following table lists the revision history of this User Manual.

Revision
Description Date
Index
- First version published for 800xA 5.1 June 2010
A Updated for 800xA 5.1 Rev B June 2012

Updates in Revision Index A

The following table shows the updates made in this User Manual for 800xA 5.1 Rev
B.

Updated Section/Sub-section Description of Update

Section 1, Introduction Under “The supported Safeguard functions and
functional units are:” below the bullet "• Fireguard
central, control and monitoring.” new bullet
"AutroSafe central, control and monitoring” is added.

3BNP004848-510 A 63
Updates in Revision Index A

64 3BNP004848-510 A
Contact us

ABB AB ABB Automation LLC

Control Technologies Control Technologies
Västerås, Sweden Abu Dhabi, United Arab Emirates
Phone: +46 (0) 21 32 50 00 Phone: +971 (0) 2 4938 000
e-mail: processautomation@se.abb.com e-mail: processautomation@ae.abb.com

3BNP004848-510 A
www.abb.com/controlsystems www.abb.com/controlsystems

ABB Automation GmbH ABB China Ltd

Control Technologies Control Technologies
Mannheim, Germany Beijing, China
Phone: +49 1805 26 67 76 Phone: +86 (0) 10 84566688-2193
e-mail: marketing.control-proucts@de.abb.com www.abb.com/controlsystems
www.abb.de/controlsystems

ABB S.P.A. Copyright © 2003-2012 by ABB.

Control Technologies All rights reserved.
Sesto San Giovanni (MI), Italy
Phone: +39 02 24147 555
e-mail: controlsystems@it.abb.com
www.abb.it/controlsystems

ABB Inc.
Control Technologies
Wickliffe, Ohio, USA
Phone: +1 440 585 8500
e-mail: industrialitsolutions@us.abb.com
www.abb.com/controlsystems

ABB Pte Ltd

Control Technologies
Singapore
Phone: +65 6776 5711
e-mail: processautomation@sg.abb.com
www.abb.com/controlsystems

Power and productivity

for a better worldTM