Process Portal A
Version 2.1
Alarm and Event
User’s Guide
OperateIT
Process Portal A
Version 2.1
In no event shall ABB Automation Technology Products AB 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 Automation Technology Products AB be liable for inci-
dental or consequential damages arising from use of any software or hardware described
in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Automation Technology Products AB, 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 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
TRADEMARKS
Registrations and trademarks used in this document include:
The IndustrialIT wordmark and all product names in the form XXXXXXIT mentioned herein
are registered or pending trademarks of ABB.
Section 1 - Introduction
1.1 Product Overview......................................................................................................21
1.1.1 What You Can Do with Process Portal A Alarm and Event .......................22
1.1.1.1 Alarms Database Configuration ..............................................23
1.1.1.2 Alarm Server and Storage .......................................................24
1.1.1.3 Event Server and Storage ........................................................24
1.2 Prerequisites & Requirements ...................................................................................24
Section 2 - Installation
2.1 Installation Procedures ..............................................................................................25
Section 3 - Configuration
3.1 Getting Started...........................................................................................................27
3.2 How to Connect to the OPC Server (Collector) ........................................................28
3.3 How to add an Alarm and Event List Aspect to an Aspect Object ...........................30
3.4 The Default Aspect Philosophy.................................................................................32
3.5 Configuration of the Alarm and Event Lists .............................................................32
3.5.1 Setting Sort Order .......................................................................................33
Section 4 - Operation
4.1 Getting Started...........................................................................................................71
4.2 Accessing Alarm and Event Lists..............................................................................71
4.3 Working with Alarm and Event Lists ........................................................................74
4.3.1 Alarm and Event List Window....................................................................74
4.3.2 Working within a List..................................................................................74
4.3.2.1 Marking and Selecting Rows in Lists .....................................74
4.3.2.2 Navigating within Message Lists ............................................75
4.3.2.3 Sizing Columns and Rows ......................................................75
4.3.2.4 Sorting on Columns.................................................................75
4.3.2.5 Moving Columns.....................................................................75
4.3.2.6 Error Indication .......................................................................76
4.3.3 Acknowledging Alarms .............................................................................77
4.3.4 Silence Alarms ...........................................................................................77
4.3.5 Deleting Alarms ..........................................................................................77
4.3.6 Stopping and Starting Alarm and Event Updates ......................................78
4.3.6.1 Stopping Updates ....................................................................78
4.3.6.2 Starting Updates ......................................................................78
4.3.7 View List Configuration .............................................................................78
4.3.8 Restoring Default Configuration ................................................................79
4.3.9 Adding Comments for an Alarm.................................................................79
4.3.10 Viewing Alarm and Event Message Detail Information ..........................79
4.3.10.1 Message Detail Dialog Buttons.............................................80
4.3.10.2 Message Detail Definitions ...................................................81
4.3.11 Help Button ..............................................................................................82
Section 7 - Maintenance
7.1 Preventive Maintenance .......................................................................................... 103
0.1 General
This book describes Process Portal A Alarm and Event software functions in
Process Portal A. Alarm and Event allows efficient response to abnormal transient
conditions defined by configurable filters. Alarms and events may be indicated
visually and audible.
Information in this user’s guide is intended for application engineers who configure
the alarm and event database, and operators and plant supervisors who view,
interpret and respond to alarm and event data during runtime.
As a prerequisite, you should understand distributed automated process control,
the hardware and software functionality of IndustrialIT System Products, and
the platform and operating system that the software is operating on.
Other instructions are also required for Process Portal A software as listed in
Related Documentation on page 19. Those people involved in operations should
attend the applicable training courses offered by ABB.
The alarm and event information is collected through a collector (OPC Alarm and
Event Server), which collect the information from the controllers.
You have to define a Logger function in order to get alarm printouts to an alarm line
printer connected to a server. By default the printer is connected to the
Aspect Server.
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.
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, comply fully with all Warning and Caution notices.
0.4 Terminology
The list contains terms and abbreviations that are unique to ABB or have a usage or
definition that is different from standard industry usage.
Term Description
ActiveX Microsoft standard for user interface components, based
on definition of software interfaces.
Aspect An aspect is a description of some properties of a real
world entity. The properties described could be
mechanical layout, how the object is controlled, a live
video image, name of the object etc. In the Aspect
Integrator Platform is an aspect residing in an Aspect
Object. Some examples of aspects are circuit diagram,
process display and control logic.
Aspect Category A specialization of an aspect type. For example, the
aspect type Graphic Display includes the categories
Overview, Group and Object Display.
Aspect Integrator A collection of software that forms the basis for an
Platform IndustrialIT System, and provides the development and
execution environment for IndustrialIT Compliant
applications. The Aspect Integrator Platform includes the
Aspect Framework.
Aspect Objects A computer representation of a real world entity like a
pump, a valve, an order or a virtual object like a service.
This computer representation is implemented by the
Aspect Integrator Platform. An Aspect Object works like
an information container for it’s aspects.
Term Description
Aspect Object Type An Aspect Object Type defines certain characteristics
that are shared between several Aspect Object
instances, such as a basic set of common aspects.
This makes it possible to create and efficiently re-use
standardized solutions to frequently recurring problems.
For example, rather than building an Aspect Object from
scratch for every valve in a plant, you can define a set of
valve types, and then create all valve objects of these
instances.
Aspect Server A server that runs the central functions of the Aspect
Object architecture, such as Aspect Directory, Structure
and Name Server, Cross Referencing, File Set
Distribution, etc.
The Aspect Server is normally used as Windows domain
controller for the control and client/server networks.
Aspect System A software system, which implements one or several
aspect types by providing one or several aspect system
objects.
Client Client is the part of the software that supply data to a
subscriber.
Client/Server Network A client/server network is used for communication
between servers, and between workplaces and servers.
Connectivity Product Connectivity components, up-loader, supporting aspect
systems (e.g for the configuration), and graphical
elements, faceplates, Aspect Object Types, etc.,
bundled together to provide the integration of a certain
type of devices into the IndustrialIT system.
Connectivity Server A server that provides access to controllers and other
sources for real-time data, historical data, and alarm and
event data. A Connectivity Server runs services related
to OPC/DA, OPC/AE, OPC/HDA and SysMag.
Term Description
Faceplate A faceplate is an aspect that provides a graphical
representation of a certain aspect object, with
presentation of certain properties related to the object,
and mechanism for operator interaction such as on/off,
increase/decrease, etc. Aspect Object types often
include several faceplate aspects, providing different
presentation and interaction possibilities.
Graphic Display A graphic display is an aspect that provides a visual
presentation. It consists of static graphics representing
for example tanks, pipes etc., and graphic elements that
present dynamic information. Graphic displays are often
used to present the state of a process or a part of a
process, but are useful in any context where dynamic
graphical information is needed.
IndustrialIT IndustrialIT is the umbrella concept for ABB’s vision for
enterprise automation.
IndustrialIT System A computer system that implements (part of) the
IndustrialIT vision. Aspect Integrator Platform is an
example of such a system.
Node A computer communicating on a network e.g. the
Internet, Plant, Control or IO network. Each node
typically has a unique node address with a format
depending on the network it is connected to.
OPC An application programming interface defined by the
standardization group OPC Foundation. The standard
defines how to access large amounts of real-time data
between applications. The OPC standard interface is
used between automation/control applications, field
systems/devices and business/office application.
Term Description
Plant Explorer An application that is used to create, delete and
organize Aspect Objects and Aspects within the Aspect
Integrator Platform. 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.
Process Portal A Product containing functionality for efficient control and
supervision of an automated process. Key functions are
presentation of process graphics, process dialogs and
presentation of alarms and trends.
Permission A permission groups a set of operations that require the
same authority. For each operation defined for an
aspect, the aspect category specifies the permission
needed to use that interface.
Process Object A process concept/equipment e.g. valve, motor,
conveyor or tank.
Product Family A range of products within a Product Suite, forming a
scalable offering.
Examples: a range of controllers, a family of I/O
Products.
Product Suite Product with similar functionality are kept together in a
suite. Suite names have a superscripted IT-suffix.
Examples: OperateIT, ControlIT, IntegrateITetc.
Property A data field on an aspect of an Aspect Object that can be
accessed through OPC using the standard Aspect
Object reference syntax.
A data field on an ActiveX control accessible from the
Visual Basic editor.
Term Description
Security Security controls a user’s authority to perform different
operations on Aspect Objects, depending on several
parameters:
• The user’s credentials, as provided by Windows
• The node where the user is logged in. This makes it
possible to give a user different authority depending
on where he/she is located, e.g. close to the
process equipment, in a control room, or at home
accessing the system through Internet.
• The operation the user wants to perform the
operation on.
Server A node that runs one or several Afw Services.
It is the part of the software that supply data to a
subscriber.
Structure A hierarchical tree organization of Aspect Objects.
Each structure is used to define a certain kind of relation
between Aspect Object. The functional structure defines
how a function can be divided into sub functions, the
location structure defines how different objects are
located within each other.
The control structure defines how functions are
executed by tasks, controllers etc. An Aspect Object can
be located in several structures, for example both in a
functional structure and in a location structure.
System Application A software package that provides functionality in the
IndustrialIT System. System applications cooperate
according to rules defined by the IndustrialIT
architecture, using mechanism provided by the Aspect
Integrator Platform. They are normally bundled into
System Products. To participate in Aspect Object
operations, and thus be an integrated part of an
IndustrialIT system, a system application must present
itself as an aspect system. When there is no risk for
confusion with user application, the term application may
be used instead of system application.
Term Description
System Extension A system Extension consists of one or more applications
that are bundled as an extension to one or several
existing System Product(s). A System extension can
only be installed if (one of) the corresponding System
Product(s) has been installed previously.
System Product A system product consists of applications bundled
together with relevant parts of the Aspect Integrator
Platform. It is complete from installation point-of-view,
and requires only Windows 2000. Several System
Products can be installed on the same physical node.
Uploader An upload is used to import a configuration from
devices, to read in and build a set of Aspect Objects
from information present in the devices.
User application A configuration of software and hardware components
that applies to a specific problem, e.g. a specific process
control problem. A user application consists of a set of
simple and composite Aspect Object instances, with
parameter values and other configuration data for the
aspects, e.g control logic, process graphics, alarm and
event specifications, reports etc.
View An Aspect can have several ways to be presented
depending on the task performed, like viewing or
configuration. Each presentation form is called a view.
Workplace 1. User interactive functions that are combined for a
particular use, e.g, Operator Workplace.
2. A node that runs one or several workplace
applications.
As an operator, you can view alarms according to the selected filter and presentation
settings or you can easily make changes. For example, a list can be sorted by double
clicking on a head line, columns can be resized or they can be moved using drag and
drop. Filtering and presentation functions let you view alarms in dedicated ways as
well as monitor and maintain the plant in a more effective way.
For example, a list can show all alarms or only those for the associated object and its
descendants. A details page is also associated with each item in the alarms list.
Alarm acknowledgment or silencing of local audible sounds is fast and easy.
You can also acknowledge an alarm when it occurs on an object within process
graphics.
Up to 1000 priorities can be defined with acknowledged and unacknowledged
colors. An audible sound can be set to any file (in .wav format) and played once or
until silencing. Date formats are selectable and time stamps can be generated
(as from the controller). Customized set-ups can be used for other alarm lists.
1.1.1 What You Can Do with Process Portal A Alarm and Event
You can access the alarm functionality as part of the Process Portal A configuration
(Application Bar, Status Bar, display shortcuts) or through aspects selectable from
the Process Portal A Workplace and Plant Explorer. Typical of what you can do
includes:
• Alarm List - view current alarm status for all objects or for a particular set of
object and descendants (optional)
• Event List - view events
• Alarm Acknowledge - you can acknowledge alarms from lists or from Process
Graphics displays or using the context menu Acknowledge verb
• Alarm Band - view the number of Unacknowledged Alarms and use the button
type link to the associated list view (commonly placed in the Application Bar)
• The Sequence Bar is a status display, where the defined number of alarms is
displayed horizontally
• Message List - view selected categories of messages in a list type format
• Logging - printout alarms and or events to a dedicated line printer
Among the things you can configure for each layout are:
• the filtering
• included columns, their size and name
• setting of presentation details, such as alarm color, date & time format
• time range
• sorting of the list
• WAV file alarm annunciation for audible signaling of alarms by priority.
Basic Steps
The basic steps you have to do to configure alarm and event are:
• The alarm and event information is collected through a collector (OPC Alarm
and Event Server), which collects the information from the controllers.
How to connect to the collector is described in How to Connect to the OPC
Server (Collector) on page 28.
• You have to define a Logger function if you want to have alarm printouts to an
alarm line printer. How to add an Alarm Logger aspect is described in
Creating an Alarm Logger aspect on page 65.
• Configuration and adding of Alarm and Event aspects to the Aspect Objects.
8. Mark the Play Alarm Sounds check box, if you want sound when an alarm is
generated. This must be configured under the Priorities tab (see Figure 3-7).
9. If you are adding an Alarm Line, unmark the Show Tool Bar check box,
since it is to large to fit into the Alarm Line area.
You have now added an Alarm and Event aspect to your Aspect Object.
Please note that the filter is located on the template, not on the list. Therefore you
have to make your own template for filtering.
Use the Sort tab, Figure 3-6, to sort a list. The list will be based on three different
sorting criteria and the sort order you set. The sorting criteria depends on the
attribute.
• For text fields such as Condition and Sub Condition, the sorting is Ascending
or Descending alphabetic A, B, C and so forth.
• For numerical values such as Priority Level, the sorting is Hi -> Lo or
Lo -> Hi or for time values such as Event Time and Acknowledge Time it
is Newest -> Oldest or Oldest -> Newest.
• For the remaining attributes the sorting is based on possible values for the
column. For example, Acknowledge State can be Unacknowledged or
Acknowledged.
After selecting a sort criteria, the name of the field is added to the Sort Order list.
Subsequent selections are added to the beginning (up to three, where the last drops
out and the criteria is changed back to a blank).
The Sort Order list will represent the order in which the column sorting is applied.
To remove an item from the list, select the blank area in the Sort Criteria area.
You can change the sort order list by selecting an item and move it up or down in the
list with the arrows on the right side.
Setting Color
To select color for the Ack Text, Ack Back (Acknowledge Background),
UnAck Text and UnAck Back columns click on the respective box, which you
want to set a color for. A new window will appear, with predefined color groups,
so called Logical Colors, see Figure 3-8, or read about them below.
Logical Colors
Some colors have a special meaning for an operator, for example the color on an
active alarm or a warning message. Other colors need to be the same in all places,
to give the system a user friendly look (for example the background colors).
You also want to be able to change these colors in one operation for all occurrences.
Logical colors is the concept used in Process Portal A to be able to fulfill these
needs. A logical color is defined once, and the user of the color refers to it by its
name.
Use the same time separator as defined in Windows Regional Options, to be able
to copy data to other applications such as Excel.
Categories
Description
(Storage Class)
AE Condition Event Used for condition process events (the event carries information about a
condition of the process object, for example, the condition PVLEVEL and
the subcondition can be HI_HI).
AE Simple Event Used for simple process events (does not include any state or condition
of the object).
AE Tracking Event Used for acknowledgement of alarms and other kinds of tracking events.
Audit Event Used for Security tracking events.
Default Class/Storage Used to store messages that haven’t been defined in the system yet.
Network Messages Used for important events that are not directly related to a process
object.
Operation Used to log operator interaction.
Services Used by the Service Manager and Services.
System Administration Used to log administrate actions in the system. This can, for example, be
that an aspect system is loaded to the system.
System Status Used to log status events regarding hardware.
User Annotation Used to log annotations that have been made by a user. This can be an
annotation associated with a process alarm.
Categories Description
Alarm Expressions Used for alarms which are generated from the Alarm Expressions you
have defined. (See Section 5, Alarm Expressions)
Soft Alarms Used by applications to create alarms. (For further information about soft
alarms please see the IntegrateIT Programmer’s Guide)
Please note that if you change the Message Type from Process Alarms to Events,
or vice versa, categories must be selected.
• Default Event List (is used with the Event List aspect, and sets the filter for
event type messages and the columns, that is appropriate, for 500 lines of
events)
• Default Logger Config (is used to configure the Logger function for printout
of Alarm List)
• Default Operator Message Line (is used with the Event List aspect, and sets
the filter for operator type messages and the columns, that is appropriate,
for one line of events)
• Default Operator Message List (is used with the Event List aspect, and sets
the filter for operator type messages and the columns, that is appropriate,
for 500 lines of events)
• Default System Event Line (is used with the Event List aspect, and sets the
filter for system type messages and the columns, that is appropriate,
for one line of events)
• Default System Event List (is used with the Event List aspect, and sets the
filter for system type messages and the columns, that is appropriate,
for 500 lines of events)
• Default Audit List (is used with the Event List aspect, and sets the filter and
columns suitable for audit events generated from Security Definition aspects).,
Figure 3-14. Alarm and Event List Configuration in the Library Structure
5. Mark the Play Alarm Sounds check box if you want sound when an alarm
is generated.
Storage Configuration
All alarms are stored, by default, in the main storage. The Alarm Server is capable
to save the 10000 (default) most recent alarms. Alarms belong to different
categories, and some categories are more important than others.
Less important alarms are therefore capable to cut out the more important ones.
It is possible to define the most important alarms (of a certain category) to be
excluded from the main storage and to be stored in a special storage instead.
If you want to include (in the main storage) an excluded category, just select it and
click on the Include button.
The alarm and event items are stored in one main data base and none, one or
more special data base(s).
Collector Configuration
In the Collector Config area you can set the collector configuration,
see Figure 3-21.
There are three options:
• Supports Refresh
If marked - when a refresh is issued towards the collector, then all alarms not
included in the refresh are removed.
• Supports Disabling
If marked - the possibility to disable alarms are enabled.
• Supports Disabling On Condition
If marked - the possibility to disable individual conditions is enabled.
Special Configuration
Each priority within a message class has its own storage.
You can also manipulate storage information for different message classes through
Edit String dialog, see Figure 3-24 on page 58.
Storage Classes
Under the Storage Classes folder, each defined message class is listed. If a
message is unregistered, (that is not yet defined), it is stored in the Default
Class/Storage with priority 1. This can happen during a startup phase, when an
alarm or event message is sent to the operator before the corresponding message is
registered. In Figure 3-23, Network Messages have storage for messages with
priority 200. The list to the right shows the storage information for this storage.
Default Sizes
The Default Sizes folder defines the storage information for storages that have not
been defined. By default, those storages will get the size specified under this folder.
See Figure 3-23.
Edit String
The list to the right shows the storage information for different storages. The values
can be modified by double clicking the Name field. The following dialog will be
displayed. Make changes in the Value Data field and then click OK.
Click the Apply button on the Special Configuration tab to save the changes.
Values
The special configuration for System Message is shown in Figure 3-23. The storage
Network Messages with priority 200 is selected in the tree view. The list view, to the
right, shows the configuration settings for the selected storage.
The following values for every priority are specified under the Special
Configuration tab:
• File Count
• File Size
• Message Count
• Max File Count
File Size and File Count specify the storage size on the disk that is pre-allocated for
the storage. Message Count specifies the number of messages that the message
server tries to hold.
If the specified storage size (File Size * File Count) is too small to hold the specified
number of messages, the message server will allocate more files on the disk.
Max File Count is the maximum limit of the number of files that can be stored.
The number of files allocated on disk will not exceed Max File Count.
Message sizes may vary, which means that the number of messages that can be
stored is not guaranteed by a certain amount of allocated disk space.
The values that can be configured for each storage are listed in Table 3-2.
Table 3-2 Values that can be Configured on the Special Configuration Tab
The two reasons to change the default values for the system message configuration
are to increase/decrease the number of stored messages, or make sure the system
messages do not overflow the disc. By increasing the Message Count together with
the Max File Count the total number of stored messages increase. The File Size and
File Count should be adapted to the Message Count set.
A mean sized message is 150 bytes. This means that the File Size * File Count
should be close to Message Count * 150. Max File Count larger than File Count
means that more files can be allocated. Our recommendation is to keep the default
File Count and instead change the File Size.
The Message Count is a hard limit. Independent of the size and number of files used
Message Count is the upper limit for number of messages stored.
You could set the Max File Count to the same value as the File Count to be sure that
no extra disc space for the system messages is needed after startup.
Setting FileCount
These settings are made by bringing up the Edit String dialog, by double clicking
the configuration settings for the selected storage in the list view to the right.
Setting MessageCount
These settings are made by bringing up the Edit String dialog, by double clicking
the configuration settings for the selected storage in the list view to the right.
Setting MaxFileCount
These settings are made by bringing up the Edit String dialog, by double clicking
the configuration settings for the selected storage in the list view to the right.
We advice you to use logical colors in order to minimize your work and
maintenance of the system. It will be a lot easier for you to change colors if needed.
1. Create a local printer in Windows, on the same computer as the Alarm Logger
Service (which is located in the Service Structure).
2. Assign the Alarm Logger aspect and use the printer you setup as an alarm
printer in Windows 2000.
3. Select the Functional Structure.
4. Select the object to which you want to add an Alarm Logger aspect.
5. Select New Aspect from the context menu.
6. Go to the Alarm Logger aspect and select it.
7. Change the name to a proper one suitable in your plant.
8. Click on the Create button to create the Logger aspect.
9. Double click on the Logger aspect to edit it.
10. Select a Logger Printer Name from the list of available printers.
11. Select a Logger Configuration Name of Default Logger Config.
Please note that the following configurations are not available for
the Alarm Logger: All settings under the Sort tab, settings for color and sound
under the Priorities tab, and settings for showing row headers, showing column
headers, viewable messages, blink behavior and font under the Column tab.
12. Mark the Logger On or the Logger Off radio button to indicate if you want the
Logger aspect to send info to the printer or not.
13. Click on the Apply button.
5. Select the Alarm and Event List aspects that are to be included in the
Main View of the Alarm Band. Make sure to select an aspect that has
process alarm configuration, and not event configuration.
6. Mark the Include Inherited check box to show (and by default add) any object
with an Alarm List that is a descendant of included objects. You may select to
uncheck any of the inherited lists.
If the Include Inherited check box is selected, this may cause high CPU-load for
a few seconds in the Aspect Server.
7. Mark the New alarmlists default included check box to automatically add a
new Alarm List aspect to the Alarm Band. This is normally not recommended.
8. Mark the Show Caption check box if you want to have a caption above the
alarm button in the Alarm Band.
In the Caption Format text field you can type in your own caption. If you
leave it empty the object name will appear by default.
In the Alarm Text Format text field you can type in your own text which will
be displayed in the Alarm Band button. If you leave it empty the total number
of unacknowledged alarms will be displayed by default.
9. Mark the Use Active Alarms check box if you want to use the active alarms.
If you mark the check box you have to type%3 in the Alarm Text Format
text field.
10. In the Button width and height text fields you can define the size of the Alarm
Band button in pixels.
11. Click Apply.
See Working with Alarm Band on page 83 for operation of the Alarm Band
Main View.
Figure 3-27. The Config View for the Sequence Bar Aspect
See Working with Sequence Bar on page 84 for operation of the Sequence Bar.
3. You can right click on an alarm line to bring up the context menu where you
can perform some action on this alarm line. Using the context menu you can
also e.g. perform some actions on the alarm list or access any aspect of the
object in alarm.
You can work with the Alarm List as described in Working with Alarm and Event
Lists on page 74. Event and System Message Lists are handled in a similar manner.
• Press the Shift key to select a sequential group of rows. For example, select
row 2, hold the Shift key and then select row 9 to select rows 2 through 9.
• Click and drag to select a sequence or rows.
When a row is marked/selected you can take ‘Actions’ on the message or view the
Details. If more than one row is marked then the action takes place on all the
marked rows if the action is applicable. For example, suppose 3 object lines have
been selected and 2 of the 3 objects are unacknowledged, then selecting Ack will
have no effect on the object which is already acknowledged.
3. Click in the table head and drag the column to the new location. A red line
marks the position between columns where you can place the column.
See Figure 4-3.
In a similar manner, two adjacent columns can be selected and moved. This change
is only in effect while this view is active.
A red cross over the Alarm Band indicates that the alarm band does not have contact
with all redundant service providers.
If the cross is green the redundant server is down and the alarm band is trying to
connect to the other server.
A red cross over the Alarm Sequence Bar pop-up window indicates that the alarm
sequence bar does not have contact with all redundant service providers.
If the cross is green the redundant server is down and the sequence bar is trying to
connect to the other server.
Open the context menu to configure the alarms in the Sequence Bar.
• Acknowledge Selected
To acknowledge the alarm you right clicked.
• Delete Selected
To delete the alarm you right clicked.
• Details
A dialog with extended information about the alarm you chose is shown.
If you click on the Next button, information about the alarm to the right is
shown, and if you click on the Previous button, information about the alarm to
the left is shown.
The Alarm Expression is a useful tool to get information in an Alarm and Event list
based on property values. You can define an expression related to a property value
which gives you a predefined message line in the list.
The aspect is configured as shown below:
1. Add an Alarm Expression aspect to a Aspect Object associated to the property.
2. Configure this aspect according to below:
a. Select Process Alarm or Event in the Message Type area.
Note that the text fields Condition, Subcondition and Inactive Message Text are
only valid for alarms.
5. Set the severity. This value shall be between 0 and 1000. The value will give
the color of the alarm list line according to the setting in the Alarm and Event
list definition. In this case we choose severity 1000.
6. Give an expression in the Expression field, in this example
OPC_Property_1==true.
7. Click on the Apply button.
You now have an “alarm expression” that will indicate when the OPC_Property_1 is
true.
Table 5-1. The Valid Operators for the Alarm Expression Aspect
Operator Description
+ Addition
- Subtraction
* Multiplication
/ Division
% Reminder
= Assignment
> Larger than
< Less than
>= Larger than or equal to
<= Lesser than or equal to
== Comparison
!= Not equal to
& Bitwise AND
| Bitwise inclusive OR
^ Bitwise exclusive OR
>> Right shift
<< Left shift
&& Logical AND
|| Logical OR
?: Condition
ex: expr1 ? expr2 : expr3
Table 5-1. The Valid Operators for the Alarm Expression Aspect (Continued)
Operator Description
! Logical NOT
~ Bitwise complement
() Parenthesis, encapsulates expression
iif Condition
ex: iif(expr1,expr2,expr3)
: Resolution
ex: object:value
Field, BitField BitField
ex: BitField(field,shift,mask)
Bit Bit
ex: Bit(variable,bit)
$ Quote
ex: $’Object1:VALUE’
[] Structure specification
ex: $’[Control structure]/Object:VALUE’
true Keyword that can be used as one of two
possible boolean values
false Keyword that can be used as one of two
possible boolean values
If numbers are used as names in the Expression field you must use “ “ around them.
For example: “1”>3.
2. Select the Config view of the Expression List Configuration aspect. Go to the
Filter tab and select Alarm Expression from the Categories.
3. Go to the Column tab and for example uncheck and check so only Event Time,
Object Name and Message Description are set.
You have now configured a special Expression Line, to which you can refer to see
all messages created by you Alarm Expressions.
6.1 General
The External Alarm function provides aspect systems and components to make it
possible to activate and deactivate an external alarm notification.
The user of the external alarm selects an alarm list and a destination output in the
configuration view. The alarm list filter is used to subscribe for alarms and events
from the alarm and event server. Set and silence are done via Data Subscription to
the destination output.
When alarms fulfilling the filtering criteria are received by the external alarm
function the destination output is set.
The operator can silence the external alarm through the silence view. Silence can be
done for all configured alarms or for one explicit external alarm.
Before you add an External Alarm you have to connect to an Alarm and Event
Server. For further information about this please read How to Connect to the OPC
Server (Collector) on page 28.
The destination can be an alterable OPC property. The syntax for the
destination is: <Object:Aspect:Property>.
Note! The digital output signal of an AC 400 must be in ‘Man’ mode to work
properly.
A Configuration
Acknowledge Special 56
Alarm 22 System Message Server 56
Acknowledge State, Sort 34 Configuration Aspect 27
Acknowledge Time, Sort 34 Configuration Name 46
Acknowledged 34 Configuration View
Alarm Show Tool Bar 48
Acknowledge 22
Band 66 D
External 99 Date
Filter 48 Format 40
List 22 Duration of sound 37
Logger 28
Server 24 E
Alarm Band 22, 28 Event List 22
Application Bar 28, 49 Event Server 24
Aspect Event Time, Sort 34
Alarm Band 66 Events
Alarm Logger 65 Filter 42
C F
Column Filter
Header Names 39 Acknowledge Time 42
Move 75 Events 42
Order 39 Process Alarms 42
Size 39 Filter dialog 41
Sort 75 Filter Tab
Column Dialog 38 Check box settings 44
Column Header 75
Condition 34 L
Config View 28 Layout
Column Names 39
Column Order 39
Column Size 39 R
Message Fields 38 Remove
Library Structure 27 item from Sort Criteria 34
Line Printer 65
List S
Alarm 22 Sequence Bar 22
Event 22 Show Tool Bar 48
Selecting Rows 74 Sort
List Window 74 Acknowledge State 34
Logger 28 Acknowledge Time 34
Configuration Name 65, 88 Column 75
Printer Name 65, 88 Condition 34
Logging 22 Criteria
Numerical Values 34
M Text Fields 34
Message Fields 38 Event Time 34
Message List 22 Priority 34
Sub Condition 34
N Sort Dialog 34
Number of Priority Levels 34 Sort Order 34
Sub Condition 34
O System Message Line 49
Operator Message List 50 System Messages
Order of Columns 39 Default Sizes 57
Edit String 58
P File Count 60
Printer File Size 60
Line 65 Max File Count 61
Priorities Message Count 61
Color of 35 Storage Classes 57
Number of 34
Sound of 37 T
Priorities dialog 34 Time/Date dialog 40
Priority 34
Process Alarms U
Filter 42 Unacknowledged 34
Unacknowledged Alarm Indicator 22
Update
Start 78
V
View
Configuration 28
W
WAV file sound 37
http://www.abb.com/control