DNA InstEvent Alarm

OASyS DNA SCADA Suite
Baseline
InstEvent and InstAlarm

Reference
Document Revision 1.1
Telvent
Telvent
10333 Southport Rd., S.W.

Calgary, Alberta, Canada, T2W 3X6
7000A Hollister Rd.

Houston, Texas, U.S.A., 77040-5337
Phone:
Fax:
E-mail:
Phone: +1 713 939 9399

Fax:
+1 713 939 0393
E-mail: info.usa.@telvent.abengoa.com
+1 403 253 8848

+1 403 259 2926
info.canada@telvent.abengoa.com
InstEvent and InstAlarm Reference

Copyright 2003 by Telvent Canada Ltd.
The information contained in this document is confidential and proprietary to Telvent Canada Ltd. It is not to be copied or disclosed for any purpose except as specifically
authorized in writing by Telvent. Although the information contained herein was correct and verified at the time of publication, it is subject to change without notice.
Trademark Acknowledgments
The following is a list of trademarks which may appear in this document:
RealTime Service, XOS, Historical Service, MICRO/1C, PoleCAT, SAGE 2000, SAGE 2100 are all trademarks of Telvent Canada Ltd
AutoCAD is a registered trademark of Autodesk, Inc.
DATEK is a registered trademark of Datek Industries, Ltd.
Ethernet is a registered trademark of Xerox Corporation
MODBUS is a registered trademark of Gould, Inc.
Excel, MS-DOS, WINDOWS, WINDOWS NT are registered trademarks of Microsoft Corporation.
SYBASE, Data Workbench, SQL Server, are registered trademarks of Sybase, Inc.
Document Revision History

Baseline
Revision
SIG
Revision
Date
Additions and Changes
1.0
2003/03/14
Initial release of OASyS DNA.
1.1
2003/05/26
XOS 7.3.1 release and SPR fixes. Updated for RealTime Services 7.3.1; this
RealTime Service release did not require a document release.
1.1
2003/10/31
Updated DNA components.
1.1
2004/02/06
Release for OASyS DNA 7.4
Contacts
Lead Writer:
Project Manager:
Project Leader:
Author variable
PM variable
PL variable
Software Version
This document describes the following components of OASyS DNA:

RealTime 7.4
XOS 7.4
Baseline
Proprietary and Confidential to Telvent
Baseline
Table of Contents
Document Revision History
Table of Contents
List of Figures
List of Tables
MODULE 1
Introduction
1.1 Events ............................................................................................................................................. 1-1
1.1.1 Event Logging....................................................................................................................... 1-1
1.2 Alarms ............................................................................................................................................ 1-2
1.2.1 State-Based Alarming........................................................................................................... 1-3
1.2.1.1 Abnormal State Alarming ........................................................................................... 1-3
1.2.1.2 Return-to-Normal Alarming........................................................................................ 1-3
1.2.2 Commanded status Points Alarming.................................................................................... 1-3
1.2.2.1 Uncommanded Change-of-State ................................................................................ 1-4
1.2.2.2 Command Failure Alarming........................................................................................ 1-4
1.2.3 Timeout Alarms .................................................................................................................... 1-4
1.2.3.1 Command Failure Timeout Alarming ......................................................................... 1-5
1.2.3.2 Command Timeout Alarming ..................................................................................... 1-5
1.2.4 Communication Alarms........................................................................................................ 1-5
1.2.5 Communication Timeouts .................................................................................................... 1-5
1.2.5.1 Network Alarms........................................................................................................... 1-6
1.2.6 Non-Covered Alarms ............................................................................................................ 1-6
1.2.7 Logging Commanded COS and Setpoints ........................................................................... 1-7
1.2.8 The almsum Table.................................................................................................................. 1-7
1.3 Configuring Alarm Attributes ...................................................................................................... 1-8
MODULE 2
Alarm Configuration
2.1 The Analog Alarm Configure Dialog Box .................................................................................... 2-1
2.1.1 Instrument Failure Checking................................................................................................ 2-3
2.1.2 Deadbands ............................................................................................................................ 2-3
2.1.3 Alarm Limits .......................................................................................................................... 2-4
2.1.4 Rate-of-Change Checks ........................................................................................................ 2-4
2.1.5 Creep Detection.................................................................................................................... 2-5
2.2 The Rate Alarm Configure Dialog Box......................................................................................... 2-5
2.3 The Status Alarm Configure Dialog Box ...................................................................................... 2-6
2.4 The Status States Dialog Box ........................................................................................................ 2-7
2.5 Inhibiting Alarming and Logging................................................................................................. 2-8
2.5.1 Inhibiting status Alarms and Logs ........................................................................................ 2-8
2.5.2 Inhibiting Other Alarms and Logs ....................................................................................... 2-9
Baseline
InstEvent and InstAlarm Reference - Baseline
Contents - 2
MODULE 3
Alarm Suppression
3.1 The Alarm Suppression Current Configuration Window ............................................................ 3-1
3.2 The Alarm Suppression Edit Dialog Box....................................................................................... 3-2
3.2.1 Parent Control Alarm Suppression ...................................................................................... 3-4
3.2.2 Parent Alarm Suppression.................................................................................................... 3-5
3.2.2.1 Parent Alarm Timeout................................................................................................. 3-6
3.2.2.2 Parent Return-to-Normal Timeout ............................................................................. 3-7
3.2.3 Transient Alarm Suppression ............................................................................................... 3-8
3.2.4 Alarm Hold-off...................................................................................................................... 3-8
3.2.4.1 Communication Order and Alarm Suppression ......................................................... 3-8
3.3 Interaction Between Suppression Types ...................................................................................... 3-9
3.3.1 Alarm Suppression Overview ............................................................................................. 3-10
3.3.2 Alarm Suppression Behavior .............................................................................................. 3-11
3.4 Alarm Disturbance Mode............................................................................................................ 3-11
3.4.1 The Alarm Disturbance Mode Edit Dialog Box ................................................................. 3-12
MODULE 4
Message Sets and Alarm Presentation
4.1 State Message Sets ........................................................................................................................ 4-1
4.1.1 analog and rate Messages ..................................................................................................... 4-3
4.1.2 Remote Message Set ............................................................................................................ 4-3
4.1.3 Status Message Set ............................................................................................................... 4-3
4.1.4 Configuring Message Sets.................................................................................................... 4-4
4.2 Alarm Presentation Attributes ..................................................................................................... 4-6
4.2.1 The Alarm Attribute Edit Dialog Box .................................................................................. 4-7
Index
Baseline
List of Figures
Figure 1-1
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 3-7
Figure 3-8
Figure 3-9
Figure 4-1
Figure 4-2
Figure 4-3
Figure 4-4
Figure 4-5
Alarm Attributes - DMT.............................................................................................................1-8

Analog Alarm Configure dialog box ........................................................................................2-2
Deadband Example....................................................................................................................2-4
Rate Alarm Configure dialog box.............................................................................................2-5
Status Alarm Configure dialog box ..........................................................................................2-6
Status States dialog box ............................................................................................................2-7
Status Inhibit dialog box ...........................................................................................................2-8
Analog Inhibit dialog box .......................................................................................................2-10
Alarm Suppression Current Configuration window ................................................................3-1
Alarm Suppression Edit dialog box...........................................................................................3-3
Parent Control Alarm Suppression Example ............................................................................3-5
Parent Alarm Suppression Example..........................................................................................3-6
Parent Return-to-Normal Suppression Example ......................................................................3-7
Transient Alarm Suppression Example .....................................................................................3-8
Alarm Hold-off Example............................................................................................................3-9
Alarm Suppression Overview window.................................................................................... 3-10
Alarm Disturbance Edit dialog box.........................................................................................3-12
Message Set Edit dialog box .....................................................................................................4-5
Message Set Add dialog box.....................................................................................................4-5
Message Edit dialog box ...........................................................................................................4-6
Alarm Attribute Edit dialog box ...............................................................................................4-7
WAV File Select dialog box .......................................................................................................4-8
Baseline
Figures - 2
Baseline
List of Tables
Table 1-1
Table 1-2
Table 1-3
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 3-1
Table 3-2
Table 3-3
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 4-5
Network communication alarm text ........................................................................................1-6

Fields in the RealTimeDB almsum table ....................................................................................1-7
Alarm Attribute Buttons on the DMT ......................................................................................1-9
Fields and check boxes on the Analog Alarm Configure dialog box .....................................2-2
Fields and check boxes on the Rate Alarm Configure dialog box ..........................................2-6
Items on the Status Alarm Configure dialog box ....................................................................2-7
Check boxes on the Status Inhibit dialog box.......................................................................... 2-9
Check boxes on the points Inhibit Dialog box ......................................................................2-10
Normal and Off-normal state determinants ..........................................................................2-11
Items on the Alarm Suppression Current Configuration Window .........................................3-2
Buttons and fields on the Alarm Suppression Edit dialog box ...............................................3-3
Fields and Buttons on the Alarm Disturbance Edit dialog box.............................................3-12
Typical message sets in the message table...............................................................................4-2
analog and rate alarm messages ................................................................................................4-3
status alarm text .........................................................................................................................4-4
Typical alarm severity color assignment...................................................................................4-6
Fields on the Alarm Attribute Edit dialog box.........................................................................4-7
Baseline
Tables - 2
Baseline
MODULE 1
Introduction
InstEvent and its sub-component InstAlarm provide wide-ranging capability for monitoring
the conditions of both the system and the field devices that the system controls.
An event is a record of conditions and activity within the system. The event history provides
a chronological record of changes in the systems condition, as well as actions taken by
system users over time. An alarm is used to announce a significant event that requires an
operators immediate attention. The generation of an alarm also creates a corresponding
event record. However, the generation of an event does not necessarily create a
corresponding alarm.
You can configure conditions for the following:
Generation of alarms
Annunciation and display of alarms
Suppression of alarms by conditions in other related points
Printing of event logs
1.1
Events
The Event Summary window provides a detailed summary of the operational activity on
the SCADA system. Events are recorded both for operator-initiated actions and for
application-generated activities. A record is generated in the event summary when any of
the following occur:
The system detects an alarmable condition
A significant event occurs in an application
The user issues commands to field devices
The user modifies system configuration parameters
The user acknowledges an alarm
1.1.1
Event Logging
When an event is generated, it is recorded in two locations. First, a copy is stored in the
HistoricalDB event table (refer to the Historical Services Configuration and Administration
Reference). You can view the event through the Event Summary window in XOS, as
discussed in the Operation and Control Reference).
Second, the event message is formatted and placed in the queue for the appropriate
spooler. The spooler process records the event on the appropriate log printer or in a log
file. The event message takes the form of a single line of text stating the nature of the
occurrence. For more information, refer to the Historical Services Configuration and
Administration Reference. The group to which the field device is assigned determines
Baseline
1-2
which spooler is used. The designated system spooler is used for events that do not have
an appropriate group. (Groups are discussed in detail in the RealTime Services
Configuration and Administration Reference).
The event database will quickly fill with data if you do not empty or purge it periodically.
The archive/cleanup process performs the necessary database purging. If you store events in
a log file, you should periodically delete old entries from the log file. Spooling events to a
file is also discussed in the Historical Services Configuration and Administration Reference.
1.2
Alarms
The system generates two kinds of alarms: database alarms and system alarms. A database
alarm is always associated with a specific point in RealTimeDB. A condition that generates a
system alarm may or may not have a specific RealTime record associated with it. Most
alarms are database alarms.
Alarms refer to either a state or a significant event. If the alarm refers to a state, it persists
until the operator clears the condition that caused the alarm. For example, a value that
moved an analog point into a high alarm state would generate a state alarm, which persists
for the entire time that the point remains in that state. Even if the operator acknowledges
the alarm, the point remains in the Alarm Summary until the points value moves out of
that high alarm state.
If the alarm is caused by a transient condition or an event, the alarm is not persistent: it
vanishes from the Alarm Summary after the operator acknowledges it. For example, a rateof-change (ROC) alarm for an analog point is a non-persistent alarm. Such an alarm serves
to notify the operator of a condition that has occurred, even though the point may still be
well within its normal operational range.
InstAlarm automatically suppresses alarms that may occur when a point has recently been
commanded to change state, or when its alarm state has just changed. This component
helps reduce the number of nuisance alarms. For example, starting a pump could create a
pressure wave that causes several sensors downstream from the pump to go into an alarm
state temporarily. You can configure InstAlarm to suppress these alarms in the downstream
devices.
The alarm/event inhibit features available through XOS provide you with the flexibility to
specify whether or not a given point generates event messages or alarms.
The following baseline windows notify the operator of alarms:
The Alarm Summary window
The Newest Priority Alarms window
The Station Alarm Summary window
Alarm summaries for individual tables, such as analog, rate, and status
For more information on these windows, refer to the Operation and Control Reference.
NOTE Within XOS, the system identifies an alarm condition by replacing the color of the
affected device or monitored value with a different solid or flashing color.
Baseline
1-3
Module 1 - Introduction
1.2.1
State-Based Alarming
State-based alarming is implemented for analog, rate, and status points. Both analog and
status points implement Intelligent Alarm Suppression. State-based alarming helps
prevent nuisance alarms, which occur when the actions of devices affect the readings of
other devices. High/low/creep/rate-of-change alarm checking is implemented for tables
that hold floating point values, such as analog and rate points.
status points can be configured to have normal and abnormal states. analog points have
lowlow/low/high/highhigh abnormal states and a normal state.
1.2.1.1
Abnormal State Alarming

Unless alarming of the state for a given status point is inhibited and the point shifts to an
abnormal state, the following occur:
The point goes into alarm
The appropriate workstation displays an alarm message
The alarm message is spooled to the event log
If the alarm represents an abnormal state, it remains in the alarm summary as a nonflashing alarm after it is acknowledged; it is then cleared from the Newest Priority Alarms
window. The name of the point, its associated remote, and its description field appear in
both the alarm message and the event log.
1.2.1.2
Return-to-Normal Alarming
When an alarm condition clears, the system:
Generates a return-to-normal alarm message
Clears the alarm from the alarm summaries after the operator ackowledges it
Spools the return-to-normal alarm message to the event summary
When the alarm message is generated, it flashes until the user acknowledges it. After the
user acknowledges it, it stops flashing and is deleted from the alarm summary unless the
status point has been configured to sustain off-normal alarms. When the point returns to
normal, the return-to-normal alarm message appears on the users workstation and the
message begins flashing again. When the user acknowledges the alarm, the return-tonormal alarm disappears from the alarm summary.
If the point returns to normal before the user acknowledges the alarm, the return-tonormal alarm message is submitted to the user and remains flashing until it is
acknowledged. Even if the alarm condition clears before the alarm is acknowledged, the
user must still acknowledge the alarm.
NOTE An alarm is not generated if the user commands a status point to an abnormal
state.
1.2.2
Commanded status Points Alarming

Two types of alarm processing are associated with commanded status points:
uncommanded Change-Of-State (COS) and command failure.
Baseline
1-4
NOTE State-based alarming is triggered whenever an uncommanded status change

occurs. A status point with a configured output can generate a state-based alarm if it
changes state without being commanded.
1.2.2.1
Uncommanded Change-of-State
An uncommanded change of state occurs when a status point changes state without being
commanded. The alarm message and event log will display the name of the status point, its
associated remote, and its description field.
When the user acknowledges an uncommanded change-of-state alarm, the alarm normally
disappears immediately from the alarm summary. However, if the status point has been
configured to sustain off-normal alarms, the system consults the abnormal state table. If the
state changed to an abnormal state, the alarm remains in the alarm summary even if the
user has acknowledged it.
Like state-based alarming, it is possible to independently disable alarming of transitions to
normal or abnormal states, as well as the logging of an uncommanded change-of-state.
NOTE An alarm is not generated if the user commands a status point to an abnormal
state.
1.2.2.2
Command Failure Alarming

There are two alarms associated with command failures: change-of-state failure alarm and
command failure timeout alarm.
The system generates a change-of-state alarm is generated when a device, which has been
directed or commanded to change state, takes a long time to change from its present state.
Some devices, such as large block valves, can take several minutes to attain the commanded
state. Rather than waiting for several minutes to generate a command failure alarm, you
can specify a maximum amount of time to wait for the device to change state. The state
which the device failed to reach is likely not the final state, but the fact that a change has
occurred indicates that the commanded action is taking place.
NOTE A change-of-state alarm applies only to status points configured as outputs.
The system generates the command failure timeout when the commanded device does not
reach the final commanded state within the maximum time allowed. Refer to Command
Failure Timeout Alarming (Section 1.2.3.1).
The only limitation on the time specifications is that the command failure timeout for the
final commanded state must be larger than the change-of-state failure timeout.
1.2.3
Timeout Alarms
User commands that are sent to analog and status points require a timeout period in which
to allow the device to perform the operation. If the operation is not performed within this
time, InstAlarm generates a timeout alarm.
Baseline
1-5
NOTE rate points are typically flow measuring devices with no control capabilities;
therefore, rate records do not have this facility.
1.2.3.1
Command Failure Timeout Alarming

For status points, the timeout period for command failure (in seconds) is configured
through the Cmd Failure Timeout: field on the Status Output dialog box, as described in
the RealTime Services Configuration and Administration Reference. This is the maximum
period of time for a command to succeed, after which the system issues a failure alarm.
The state that the device changes to is likely not the final state, but the fact that a change
has occurred indicates that the commanded action is taking place. A typical value would
be three to five seconds, but this is device dependent. If the device does not change state
within the specified period, the system generates an alarm.
If a command can not be sent to the status point due to communication problems, the
system generates an alarm and logs the event.
1.2.3.2
Command Timeout Alarming

For analog points, the timeout period for setpoint commands, in seconds, is configured
through the Command Timeout: field on the Analog Output dialog box. Because analog
values do not immediately stop at the setpoint, there is also a Setpoint Tolerance value. A
setpoint is reached when the value is within the tolerance boundary (the setpoint value
plus or minus the Setpoint Tolerance value). The operation of the instrument plays an
important role in determining the correct timeout period. Generally, the correct timeout
period will be arrived at by trial and error in the testing of a commanded output. For more
information on the Analog Output dailog box, refer to the RealTime Services
Configuration and Administration Reference.
If a command can not be sent to the analog point due to communication problems, an
alarm is generated and the event is logged. All generated alarms are cleared from the
alarm summary upon acknowledgement.
1.2.4
Communication Alarms
The communication line between the RTU and the host computer may encounter minor
errors and problems. The statistics for communication errors are recorded in the remote
table, and then transferred to the HistoricalDBs CommStats database, where they are
stored in the RemPeriodStats table. The connection statistics are recorded in the
connection table, and then transferred to the HistoricalDBs CommStats database, where
they are stored in the ConnPeriodStats table.
To view historical results, click any field of a points information line on the Remote
Summary, Remote Primary Statistics Summary, or Remote Alternate Statistics Summary
window. (For more information on these summary windows, refer to the Operation and
Control Reference.) When the action menu appears, click Historical Statistics to open the
Communications Statistics Edit dialog box, which displays historical results.
1.2.5
Communication Timeouts
The system reports most types of communication failures as soon as they occur (e.g.
security error, illegal message, short message). However, if the remote fails to
Baseline
1-6
communicate, the system generates a no-reply alarm if the failure lasts for longer than the
no-reply timeout period.
1.2.5.1
Network Alarms
InstAlarm and InstEvent can also generate alarms related to critical network components
and the network communication between the host computers and the terminal servers. For
example, if the primary LAN fails over to the secondary LAN, an alarm message is generated
to indicate that a failover has occurred.
The following tables shows the messages for the internal network failover flag alarms
defined in the cpu message set.
Table 1-1 Network communication alarm text

Alarm Text
1.2.6
Description
Fail
The workstation CPU is failing over to backup unit (or there is a failing
LAN).
Pending
The workstation CPU is attempting to start up.
Init
The workstation CPU is in the initialization stage of recovery.
Standby
Workstation CPU is in standby mode ready to go live if all conditions are

right.
Hot
Workstation CPU is hot or live operational state.
Switch
The host CPU and its LAN is failing, requiring a LAN switch. (This is also
used for device failover to another unit.)
Doswitch
This is the process of switching LANs during a host CPU failover. (This is
also used for device failover to another unit.)
Non-Covered Alarms
There are situations when an alarm is generated from an area that is currently not selected
for control by any user. (This may happen on a night shift, for example, when fewer users
are on duty.) Any or all of the workstations can be configured to receive such non-covered
alarms.
When alarms are being generated for an area that is controlled by an operator, noncovered alarms from another area occur only if alarm cover checking is enabled. If alarm
cover checking is disabled, the system will not generate non-covered alarms. For related
information, see Area Edit dialog box in the RealTime Services Configuration and
Administration Reference.
NOTE If a user receives a non-covered alarm, she does not automatically have the
authority to acknowledge it or to control the necessary devices in that area. First, she
must be able to select the area with the non-covered alarm for control, which can only
occur if the workstation rights and/or user rights allow it. At any given time, therefore, at
least one user should have rights to control each area. (Area of responsibility is discussed
in the RealTime Services Configuration and Administration Reference.)
Baseline
1-7
1.2.7
Logging Commanded COS and Setpoints

User-commanded status Change-Of-State (COS) and analog setpoints are both logged as
events. Successful commands are only logged with a success statement if Log Command
Success is selected in either the Analog Output dialog box or Status Output dialog box
(refer to the RealTime Services Configuration and Administration Reference).
The system will record any permitted command issued by the operator (i.e. if the
command is aborted due to a command tag, the system will not record the event).
Unsuccessful commands are logged with the command and either a communication failure
statement, if communication failure prevented the command from reaching the remote,
or a command failure statement, as explained in Command Failure Timeout Alarming
(Section 1.2.3.1) and Communication Timeouts (Section 1.2.5).
Most protocols process an output command at the RTU when the RTU is successful in
receiving the command.
1.2.8
The almsum Table

When an alarm is generated, the system writes a record to the RealTimeDB almsum table.
Each record stores information about the alarm including the following:
The name of the point, table, and group with which the alarm is associated
The severity of the alarm
The type of alarm
The message text
Whether or not the alarm is persistent (a persistent alarm remains in the alarm summary even after the user acknowledges it)
The following table lists all of the fields in the almsum table.
Table 1-2 Fields in the RealTimeDB almsum table

Internal
Field Name
Data Type
Description
category
pntname
The alarm category (e.g. command-failure, rate-ofchange, or hi-state).
covered
oas_boolean_t
This indicates whether or not this alarm is currently in an

XOS control area.
dbname
pntname
The name of the table with which the alarmed point is

associated. For system alarms, this field is set to SYSTEM.
DBnPnt
almsum_dbpnt
The database key field.
flashing
oas_boolean_t
When the alarm is flashing, it is unacknowledged.
fldname
fieldname
The name of the field in alarm.
group
groupslot
The group with which this point is associated for alarming.
host
pntname
The host machine name.
inalarm
oas_boolean_t
This indicates whether or not the alarm is persistent.
message
almsumMsg
The alarm message text.
pntdesc
pntdescription
The point description.
Baseline
1-8
Table 1-2 Fields in the RealTimeDB almsum table (Continued)

Internal
Field Name
Data Type
Description
ptname
almsum_key
The name of the point in alarm.
purgetimer
short
The purge timer, in seconds, is used when a non-persistent alarm is to remain in the summary for a time after
alarm acknowledgement.
rtu
remoteslot
The remote point.
severity
sev_enum
The alarm severity.
Sevtime
alm_sevtime_t
The severity and timestamp combined, which is used as a

database key.
timestamp
internaltime
The time, in number of seconds, from 00:00:00 hours

(GMT), January 1, 1970, when the alarm occurred.
timestampstr
alm_timestr_t
The timestamp as a string in local time format.
type
almTypeEnum
The alarm type (e.g. database or system).
The almsum table is not accessible through the DMT. Use the following to access or modify
the table:
acknowledge
addDBalarm
addSYSalarm
filteralm
Each of these is described in the Business Object Reference.
1.3
Configuring Alarm Attributes

Alarm attributes are configured using several dialog boxes that are opened through the
Database Management Tool (DMT). Alarm Attributes - DMT (Figure 1-1) shows a section of
the DMT that deals with alarm attributes.
Figure 1-1 Alarm Attributes - DMT
Baseline
1-9
Table 1-3 Alarm Attribute Buttons on the DMT

Button
Description
Message
Click this to open the Message Set Edit dialog box

(Figure 4-1). Refer to State Message Sets (Section 4.1).
Alarm Attr.
Click this to open the Alarm Attribute Edit dialog box

(Figure 4-4). Refer to Alarm Presentation Attributes
(Section 4.2).
Disturbance Mode
Click this to open the Alarm Disturbance Edit dialog box

(Figure 3-9). Refer to Alarm Disturbance Mode
(Section 3.4).
Suppression Overview
Click this to open the Alarm Suppression Overview window (Figure 3-8). Refer to The Alarm Suppression Current
Configuration Window (Section 3.1).
Baseline
1-10
Baseline
MODULE 2
Alarm Configuration
This module discusses analog, rate, and status alarm configuration.

Support is provided for a number of alarm conditions for analog and flow rate points,
including:
Instrument failure checking
Hi/Lo operating-range checking
HiHi/LoLo operating-range checking
Rate-of-Change checking
Creep Detection or instrument-deviation checking
Each of these can be configured and enabled or disabled independently. You can set the
conditions in the points record, or in the points XOS control panel via the Alarm Limits
window in XOS (refer to the Operation and Control Reference).
rate points that use accumulator pulse counts (as opposed to ones that use analog inputs)
calculate the pulse rate and use it for alarm generation. When status points undergo
uncommanded state changes, alarms are generated.
This module covers the following interfaces that are used in configuring alarms:
The Analog Alarm Configure Dialog Box (Section 2.1)
The Rate Alarm Configure Dialog Box (Section 2.2)
The Status Alarm Configure Dialog Box (Section 2.3)
2.1
The Analog Alarm Configure Dialog Box

The Analog Alarm Configure dialog box (Section Figure 2-1) is used to configure an analog
points alarm.
Baseline
2-2
Figure 2-1 Analog Alarm Configure dialog box
Opening the Analog Alarm Configure dialog box

1
Click Analog on the Database Management Tool to open the Analog Edit dialog box.
For more information, refer to the RealTime Services Configuration and Administration
Reference.
Type or select the name of the analog point in the Name: field.
Click Alarming....
The following table provides information on each of the items that appear on the dialog
box.
Table 2-1 Fields and check boxes on the Analog Alarm Configure dialog box
Field/Check box
Reference
Instrument Fail Check
Instrument Failure Checking (Section 2.1.1)
Alarm Deadband:
Deadbands (Section 2.1.2)
Hi/Lo Alarm Check

Lo Alarm Limit:
Hi Alarm Limit:
Alarm Limits (Section 2.1.3)
HiHi/LoLo Alarm Check

LoLo Alarm Limit:
HiHi Alarm Limit:
Rate of Change Alarm

Rate of Change Limits:
Rate-of-Change Checks (Section 2.1.4)
Baseline
2-3
Module 2 - Alarm Configuration
Table 2-1 Fields and check boxes on the Analog Alarm Configure dialog box (Continued)
Field/Check box
2.1.1
Reference
Creep Detection
Deviation Alarm Limit:
Creep Detection (Section 2.1.5)
Alarm Suppression:
The Alarm Suppression Current Configuration Window

(Section 3.1)
Instrument Failure Checking

Sometimes, due to instrument or sensor malfunction, analog and rate instruments and/or
their associated transducers try to send a value to the RTU that is outside of the RTUs
measurable range. If the Instrument Fail Check check box is selected for RTUs capable of
sensing instrument failures, an analog or rate point alarm is generated when an
instrument failure occurs.
For an RTU that is not capable of sensing out-of-range failures, selecting Instrument Fail
Check causes the generation of alarms whenever the RTU encounters a raw value that is
outside its measurable range.
If the RTU is not capable of sensing out-of-range failures, select Instrument Fail Check to
generate alarms whenever the raw value is not within the raw value range.
NOTE Instrument failure handling is protocol-specific. For more information, refer to
the Communication Management Reference.
2.1.2
Deadbands
The Alarm Deadband: field controls the sensitivity of the high and low alarms. These
alarms are always triggered when the value being monitored crosses the high or low limit.
The value that causes the alarm state to end depends on the deadband. When the point is
in the high alarm state, it remains in that state until it drops below the high limit minus
the deadband, as shown in the Deadband Example (Figure 2-2). These conditions prevent
minor fluctuations from repeatedly putting the value into and out of the alarm state.
Similarly, when a point is in the low alarm state, it remains in that state until it rises above
the low limit plus the deadband. If the deadband is set to zero, this feature is disabled.
These deadband rules apply in the same manner to the HiHi and LoLo limits.
Baseline
2-4
Figure 2-2 Deadband Example

H
HH
High-High
Limit
High Limit
Low Limit
deadband
deadband
Low-Low
Limit
HH
H
L
2.1.3
= point in High-High alarm state

= point in Highalarm state
= point in Low alarm state
Alarm Limits
Standard normal operating values for the analog and rate points lie within certain Hi and
Lo limits. When a measured value exceeds the high limit, or goes below the low limit, a
state alarm is generated to indicate that a condition requires attention. A second set of
limits, known as HiHi and LoLo, are above and below the high and low limits. When a
measured value exceeds the HiHi, or goes below LoLo limits, a state alarm is generated to
indicate that a critical condition has occurred.
Typically, a higher severity is assigned to HiHi / LoLo conditions than to the Hi/Lo. Refer to
State Message Sets (Section 4.1).
2.1.4
Rate-of-Change Checks
analog and rate instruments register a value that increases or decreases depending on
process conditions. InstAlarm can monitor the rate-of-change (ROC) in the value. Rate-ofchange is determined by normalizing the last scan value and the current value to the unit
time (in seconds):
lastvalue currentvalue
ROC = -------------------------------------------------------------------time
Some instruments have a manufacturers specification indicating that errors can occur if a
certain ROC value is exceeded. At times, a monitored process variable can require a ROC
limit to prevent errors based on rapid adjustments to the system. In these cases, select the
Rate of Change Alarm check box on the Analog Alarm Configure dialog box (Figure 2-1)
and enter the maximum allowable rate-of-change (in engineering units per second) in the
Baseline
2-5
Rate of Change Limit: field. An alarm is generated if the calculated rate of change is
greater than this amount.
The correct limit is determined by the instrument specifications and the process
limitations.
2.1.5
Creep Detection
You may need to properly calibrate analog and rate instruments to ensure that their
values are accurate and do not creep out of the calibrated state. analog and rate points
have an option that allows you to store an initial value or creep setpoint, updated on
startup and whenever a creep alarm is generated. This initial value can then be compared
to all subsequent values. This comparison measures any creep deviation of the input value.
The amount of creep is the absolute difference between the current scan value and the
creep setpoint that was set when the last creep alarm occurred:
creep = currentvalue setpoint
If the analog point is supposed to test for creeping, select the Creep Detection check box
on the Analog Alarm Configure dialog box (Figure 2-1). You should do this when the
instrument specifications indicate a maximum raw deviation value that is acceptable
before calibration deterioration occurs. Convert this raw value to the applicable
engineering units for the point and enter it in the Deviation Alarm Limit: field. An alarm is
generated if the calculated creep exceeds this limit.
2.2
The Rate Alarm Configure Dialog Box

The Rate Alarm Configure dialog box (Figure 2-3) is used to configure a rate points alarm.
Figure 2-3 Rate Alarm Configure dialog box
Baseline
2-6
Opening the Rate Alarm Configure dialog box

1
Click Rate on the DMT to open the Rate Edit dialog box. This dialog box is also
discussed in the RealTime Services Configuration and Administration Reference.
In the Name: field, type or select the name of a rate point.
Click Alarming....
box.
Table 2-2 Fields and check boxes on the Rate Alarm Configure dialog box
Field/Check box
2.3
Reference
Instrument Fail Check
Instrument Failure Checking (Section 2.1.1)
Alarm Deadband:
Deadbands (Section 2.1.2)
Hi/Lo Alarm Check

Lo Alarm Limit:
Hi Alarm Limit:
HiHi/LoLo Alarm Check

LoLo Alarm Limit:
HiHi Alarm Limit:
Rate of Change Alarm

Rate of Change Limits:
Rate-of-Change Checks (Section 2.1.4)
Creep Detection
Deviation Alarm Limit:
Creep Detection (Section 2.1.5)
Alarm Suppression:
The Alarm Suppression Current Configuration Window

(Section 3.1)
The Status Alarm Configure Dialog Box

The Status Alarm Configure dialog box (Figure 2-4) is used to configure a status points
alarm
Figure 2-4 Status Alarm Configure dialog box
Baseline
2-7
Opening the Status Alarm Configure dialog box

1
Click Status on the DMT to open the Status Edit dialog box. For more information on
this dialog box, refer to the RealTime Services Configuration and Administration
Reference.
Click Alarming....
box.
Table 2-3 Items on the Status Alarm Configure dialog box

Item
2.4
Description
Sustain COS Alarms
Select this check box to allow alarms to remain in the Alarm Summary window as long as the point remains in the abnormal state.
The beeping stops when the user acknowledges them, but they
are only removed from the window when the point returns to the
normal state.
If Sustain COS Alarms is not selected, alarms disappear from the
Alarm Summary window as soon as they are acknowledged.
Alarm Suppression
Clicking the arrow next to this field opens the Alarm Suppression
Current Configuration window (Figure 3-1). Refer to The Alarm
Suppression Current Configuration Window (Section 3.1).
The Status States Dialog Box

The Status States dialog box (Figure 2-5) is used to configure abnormal state alarming. For
more information, refer to Abnormal State Alarming (Section 1.2.1.1).
Figure 2-5 Status States dialog box
Opening the Status States dialog box
Click Abnormal States... on the Status Edit dialog box. For more information on this
dialog box, refer to the RealTime Services Configuration and Administration Reference.
Baseline
2-8
Configuring a status points abnormal states
2.5
Click Status on the Database Management Tool. This opens the Status Edit dialog box.
Refer to the RealTime Services Configuration and Administration, for more
information on this dialog box.
Select or type the name of the point the Name: field
Click Abnormal States.... This opens the Status States dialog box (Section Figure 2-5).
Select the appropriate state for the messages.
Inhibiting Alarming and Logging

Alarms are normally annunciated and displayed in XOS. However, for some conditions, it
may be desirable to inhibit specific alarms.
NOTE In a distributed installation, alarm acknowledgement is local to a system and is
not replicated to other systems. Hence, for the same point, an operator on one system
handles alarm acknowledgment completely independent of operators on the other systems. Alarms are distributed to other systems depending on the alarm configuration
option specified.
2.5.1
Inhibiting status Alarms and Logs

Alarms and the resulting logs caused by uncommanded changes, such as uncommanded
changes to normal state, are inhibited using the Status Inhibit dialog box (Figure 2-6).
Figure 2-6 Status Inhibit dialog box
Opening the Status Inhibit dialog box

1
Click Status on the DMT to open the Status Edit dialog box, as discribed in the
RealTime Services Configuration and Administration Reference.

2
Click Inhibit....
Baseline
2-9
box.
Table 2-4 Check boxes on the Status Inhibit dialog box

Check box
Description
Inhibit alarming of
uncommanded
changes to normal
state
If selected, the system alarms are not generated when the point
undergoes an uncommanded change to the normal state.
If an unacknowledged abnormal state alarm exists, the change
to normal state alarm will occur whether or not Inhibit alarming of uncommanded changes to normal state is selected.
This ensures that the operator is aware that the points alarm
state has changed.
Inhibit logging of
uncommanded
changes to normal
state
If selected, the system events are not logged when the point
undergoes an uncommanded change to the normal state.
Inhibit alarming of
uncommanded
changes to abnormal
state
If selected, the system alarms are not generated when the point
undergoes an uncommanded change to an abnormal state.
Inhibit logging of
uncommanded
changes to abnormal
state
If selected, the system events are not logged when the point
undergoes an uncommanded change to an abnormal state.
NOTE Uncommanded changes are those that occur without the users intervention.
For example, if someone in the field opens a valve, the change is considered to be
uncommanded since the change did not result from the operators action.
NOTE You configure certain states as abnormal via the Status States dialog box
(Figure 2-5).
2.5.2
Inhibiting Other Alarms and Logs

You can inhibit alarms and events caused by state changes, such as a change of state from
normal to off-normal, and vice versa, using inhibit dialog boxes similar to the Analog
Inhibit dialog box (Figure 2-7).
Baseline
2-10
Figure 2-7 Analog Inhibit dialog box
Opening a points Inhibit dialog box

This procedure applies when configuring analog, connection, modem, rate, or remote records.
1
Open the specific edit dialog box. If it is an analog point, open the Analog Edit dialog
box.
Click Inhibits....
The following table lists the check boxes that appear on the dialog box.
Table 2-5 Check boxes on the points Inhibit Dialog box

Check box
Description
Off-Normal Alarm
Selecting this check box inhibits off-normal alarming. Select this if

you do not want the system to generate alarms when the point
changes from a normal state to an off-normal state.
Normal Alarm
Selecting this check box inhibits normal alarming. Select this if

alarms are not supposed to be generated when the point changes
from an off-normal state to a normal state.
If an unacknowledged off-normal alarm exists, the return-to-normal alarm occurs whether or not normal alarming is inhibited. This
ensures that the operator is aware that the points alarm state has
changed.
Off-Normal Log
Select this check box if events are not supposed to be logged when
the point changes from normal state to off-normal state.
Normal Log
Select this check box if events are not supposed to be logged when
the point changes from off-normal state to normal state.
The operator can also inhibit alarms generated from analog, rate, and status points through
the points XOS control panels. For remote points, the operator can put an RTU offscan, but
cannot actually disable alarming for all points.
While the user can inhibit alarm generation through XOS, only the system administrator can
inhibit event logging through RealTimeDB records via the DMT.
Baseline
2-11
The following table lists conditions that determine normal and off-normal states.
Table 2-6 Normal and Off-normal state determinants

Table
Condition/Determinant
analog
analog alarm limits; refer to Alarm Limits (Section 2.1.3)
connection
alarms that are usually related to the following:

Modem failure (connection lost, unable to establish connection)
Configuration errors (cannot assign device)
Dialup line communication errors
rate
rate alarm limits; refer to Alarm Limits (Section 2.1.3)
remote
no-reply timeouts, security errors, short messages, and illegal messages (Normal alarms are generated and logged. For more information on remote, refer to the the Communication Management
Reference.)
Baseline
2-12
Baseline
MODULE 3
Alarm Suppression
InstAlarm manages alarms through the following:

Parent Control Alarm Suppression (Section 3.2.1)
Parent Alarm Suppression (Section 3.2.2)
Transient Alarm Suppression (Section 3.2.3)
Alarm Disturbance Mode (Section 3.4)
NOTE Alarm suppression applies to current value alarms (such as data krunching
alarms) and does not block other types of alarms (such as command failure alarms).
3.1
The Alarm Suppression Current

Configuration Window
The Alarm Suppression Current Configuration window (Figure 3-1) displays all the
suppression criteria that are configured for a point. This window provides a way of adding,
modifying, and deleting suppression criteria.
Figure 3-1 Alarm Suppression Current Configuration window
Baseline
3-2
Opening the Alarm Suppression Current Configuration window

The Alarm Suppression Current Configuration window (Figure 3-1) displays all the suppression
criteria that are configured for a specific analog or status point.
1
Click Analog or Status on the DMT. This opens the Analog Edit dialog box or the Status
Edit dialog box. For more information on these dialog boxes, refer to the RealTime
Services Configuration and Administration Reference).
Type or select the name of the point in the Name: field.
Click Alarming.... This opens the Analog Alarm Configure dialog box (Figure 2-1) or the
Status Alarm Configure dialog box (Figure 2-4).
Click the arrow that corresponds to Alarm Suppression.
The following table lists the column heading names and buttons that appear on the Alarm
Suppression Current Configuration window (Figure 3-1)
Table 3-1 Items on the Alarm Suppression Current Configuration Window

Column Heading/Button
Parent Point
Suppress Method
Suppression Method: field
Table
Table: field
Point
Point: field
Alarm/Control
Parent Alarm/Control: field
Timers
(Seconds)
Return to Normal
Parent Return to Normal: field
Alarm Holdoff
Alarm Holdoff: field
State Based
Check State
Corresponds to Valid for Specific State: check box
Alarm State
Alarm State: field
Add
3.2
Refer to Buttons and fields on the Alarm

Suppression Edit dialog box (Section Table 3-2)
Click this to open the Alarm Suppression Edit dialog box

(Figure 3-2).
The Alarm Suppression Edit Dialog Box

The Alarm Suppression Edit dialog box (Figure 3-2) is used to configure parent control,
parent alarm, and transient alarm suppression.
Baseline
3-3
Module 3 - Alarm Suppression
Figure 3-2 Alarm Suppression Edit dialog box
Opening the Alarm Suppression Edit dialog box

The Alarm Suppression Edit dialog box (Figure 3-2) configures parent control, parent alarm, and
transient alarm suppression for an analog or status point.
1
Open the Alarm Suppression Current Configuration window (Figure 3-1). For more
information, refer to The Alarm Suppression Current Configuration Window
(Section 3.1).
Click Add.... to open the Alarm Suppression Edit dialog box (Figure 3-2).
NOTE You should see the points name in the upper, right-hand corner of the dialog
box.
The following table provides brief descriptions of the fields and buttons on the dialog box.
Table 3-2 Buttons and fields on the Alarm Suppression Edit dialog box
Field/Button
Description/Reference
Suppression Method:
Parent Control
Parent Alarm
Transient
Refer to:
Parent Control Alarm Suppression (Section 3.2.1)
Parent Alarm Suppression (Section 3.2.2)
Transient Alarm Suppression (Section 3.2.3)
Table:
This is not available for the Transient Suppression

Method. You can choose either Analog or Status.
Point:
This is not available for the Transient Suppression

Method. This is the parent point.
Baseline
3-4
Table 3-2 Buttons and fields on the Alarm Suppression Edit dialog box
Field/Button
3.2.1
Description/Reference
Parent Alarm/Control:
This field applies only when Suppression Method: is set

to Parent Control or Parent Alarm. Refer to Parent
Alarm Timeout (Section 3.2.2.1)
Parent Return to Normal:

to Parent Alarm. Refer to Parent Return-to-Normal Timeout (Section 3.2.2.2)
Alarm Holdoff:

to Parent Alarm or Transient. Refer to Alarm Hold-off
(Section 3.2.4)
Valid for Specific State:
Select this check box to enable the Alarm State: field.
Alarm State:
Select the state for which the alarm suppression configuration is valid. For analog, it might be high alarm state; for
status, it might be the opened state. The alarm state
options that are provided are sensitive to the child point
being edited. Only the valid child states are shown.
Parent Control Alarm Suppression

Parent control alarm suppression handles alarms by inhibiting alarm events that are a direct
and predictable result of an operators command to a field device. Starting a pump, for
instance, results in a pressure wave in the pipe. A pressure sensor further down the pipeline
from the pump would likely go into alarm when the pressure wave hits. By configuring the
sensor as a child of the pump device, it is possible to inhibit the alarm.
Relationships between parent and child points are configured in the RealTimeDBs
almsuppression table. The Alarm Suppression Current Configuration window (Figure 3-1)
and the Alarm Suppression Overview window (Figure 3-8) both offer a visual look at the
relationship. Extensions that are added to alarm suppression, such as alarm suppression
based on state, are also available for parent control alarm suppression. For more
information, refer to Parent Alarm Suppression (Section 3.2.2).
When an operator issues a control (e.g. setpoint) command to a field device, and the
command arrives successfully, the almsuppression records that have the controlled point as
parent are marked as suppressed. The alarm suppression timeout is set up, and at
expiration, the childrens alarm conditions are reevaluated. If at reevaluation the child is in
a different alarm state from where it was when the parent was commanded, the system
generates an alarm. The parent control alarm suppression is then cleared. If the control
command failed to execute at the remote, then the alarm suppression timeout is cancelled
and any suppressed child alarm is immediately evaluated.
Baseline
3-5
Child State
Figure 3-3 Parent Control Alarm Suppression Example
hi hi alarm
hi alarm
control suppression timeout
normal
0
Parent is commanded
at time 0 and child is
marked for alarm
suppression.
10
20
50
New value arrives

indicating that the child
is in alarm, but the alarm
is suppressed.
100
120 Time (seconds)
Child state is reevaluated. It

is found to be the same as at
time 0; therefore, no alarm is
generated.
In the Parent Control Alarm Suppression Example (Figure 3-3), the state of the child goes
into alarm shortly after the command is sent to the parent. The child returns to normal at
the 100-second mark. If the control suppression timeout is set to a value greater than 100
seconds, then the child will not alarm: it has returned to normal before the alarm
suppression timeout expired. If the timeout value were shorter, for instance 90 seconds,
then the child alarm is generated after 90 seconds.
NOTE If a parent is commanded while a control suppression timeout is already under
way, then the control suppression timeout will be reset. However, when the updated
alarm suppression timeout value expires, control suppression does not record a new
child state value for evaluation.
NOTE Only child state alarms that result from data krunching are suppressed by parent
control alarm suppression. Other types of alarms (e.g. command failure) execute as
normal. Parent control alarm suppression is supported for analog and status points.
3.2.2
Parent Alarm Suppression

With parent alarm suppression, child alarms are suppressed on the basis of the parents
alarm state.
When a parent with alarm suppression records goes into alarm, the childrens alarms are
suppressed for a configured amount of time (i.e. a timeout value). Child alarm suppression
is cancelled after the timeout value has expired. When the timeout value expires, the
system reevaluates the alarm state of the children.
NOTE Timeout values are not reset if the parent toggles between alarm states.
In the case of alarm suppression based on the child alarm state, child alarm suppression is
cancelled when a non-suppressed state is reached. In this event, the parent alarm timers
Baseline
3-6
for alarm, return-to-normal, and alarm hold-off are either cancelled or prevented from
being triggered. For example, assume that a child is configured for parent alarm
suppression in the normal, hi, and low alarm states. If the points parent changes alarm
state, the parents alarm remains suppressed while it remains in the normal, hi, or low alarm
state. If the parent reaches the high-high or low-low alarm state, its alarm suppression is
cancelled immediately and the system generates an alarm.
Parent alarm suppression only suppresses child state alarms that result from data krunching.
Other types of alarms (e.g. command failure) execute as normal. Parent alarm suppression is
supported for analog and status points.
3.2.2.1
Parent Alarm Timeout

When a parent point goes into alarm or enters a different alarm state, the children (i.e. the
almsuppression records that have the alarmed point as their parent) are marked as
suppressed. The alarm suppression timeout is set up, and, at expiration, the childrens alarm
conditions are reevaluated. If at the time of reevaluation the child is in a different alarm
state than where it was when suppression was triggered, the system generates an alarm.
The alarm suppression is cleared once the alarm suppression timeout expires.
If configured for state-specific suppression, the child alarms that come into the system are
checked to ensure that they match the configured state(s) to be suppressed.
Figure 3-4 Parent Alarm Suppression Example
Alarm State
Parent
alarm
Child1
Child2 alarm suppression timeout
Child1 alarm suppression timeout
normal
10
Parent goes into alarm

and children are marked
for alarm suppression
Child2
60
Child alarms
are suppressed
100
115
Child1 returns to
normal without
generating alarms
Parent returns
to normal
130
Time (Seconds)
Child2 is in a different state from

where it was at the time of alarm
suppression; therefore, an alarm is
generated for Child2.
In the Parent Alarm Suppression Example (Figure 3-4), the parent alarm occurs and the
children alarms are suppressed. The parent returns to normal before the alarm suppression
timeout value expires.
Children alarms are reevaluated when the parent alarm timeout value expires. This value
can be set to a relatively short value or to a value that is beyond the parents alarm
duration.
NOTE The alarm suppression timeout value is not reset if the parent transitions to normal and then back to alarm state before the timeout value expires.
Baseline
3-7
3.2.2.2
Parent Return-to-Normal Timeout

The parent Return-to-Normal (RTN) timeout value assists in suppressing child alarms that
are held until after the parent returns to normal. This timeout value can be used either
with or without a configured parent alarm timeout value.
In the Parent Alarm Suppression Example (Figure 3-4), if Child2 stays in alarm for a period
of time after the parent returns to normal, then the parent RTN timeout is used rather
than the parent alarm timeout. In this case, the parent alarm timeout is set to zero, which
causes the indefinite suppression of the children alarms while the parent is in the alarm
state. This timeout value is set so that child alarm reevaluation is made after the parent
has been in the normal state for the timeout duration (e.g. 80 seconds).
Figure 3-5 Parent Return-to-Normal Suppression Example
Parent
Alarm State
alarm
Child
Alarrm Suppression Timeout
RTN Suppression Timeout
normal
20
Parent goes into alarm and

child alarms are
suppressed.
40
Alarm suppression timer

is cancelled and RTN timer
is created.
100
Time (Seconds)
Child returns to normal

without generating alarms.
The parent RTN alarm suppression timeout can be used in combination with the parent
alarm suppression timeout. The Parent Return-to-Normal Suppression Example (Figure 3-5)
shows both timeout values configured. In this case, the parent returns to the normal state
and the RTN alarm suppression timeout extends the suppression interval. As the child
returns to the same state it was in at the time of suppression, the system will not generate
any child alarms. If the parent stays in the alarm state for more than 40 seconds, the RTN
timer is not triggered; the system reevaluates the child and, consequently, generates an
alarm.
NOTE If only the RTN suppression is configured (i.e. alarms are indefinitely suppressed
while the parent is in alarm), then the suppression is cleared if the remote containing
the parent goes stale due to communication failure or the remote being placed offscan.
NOTE Regardless of the configuration of the timeout values, the childs state is compared to its state when the parent went into alarm after all timers have expired. The
childs alarm state is not reevaluated as each timeout value (or timer) expires.
Baseline
3-8
The timeout values are not reset during transitions between alarm states or during
transitions between normal states. The alarm suppression timeout value is cleared when the
parent shifts into a normal state and after the successful setup of the RTN alarm suppression
timeout. However, if the parent shifts back into an alarm state while the RTN timer is active,
then the system will neither clear the RTN alarm suppression timeout value, nor set up an
alarm suppression timeout value. This avoids the indefinite suppression of alarms when the
parent toggles continuously between abnormal and normal states.
3.2.3
Transient Alarm Suppression

Transient alarm suppression is invoked when a status point changes state or an analog
point changes between the high/low alarm states. In this case, the child does not have a
parent. When triggered, the alarm hold-off timer records the childs current state and
marks the child as alarm-suppressed. When the alarm hold-off timer expires, the system
determines if it should generate an alarm by comparing the current state of the child to the
recorded state at the time the hold-off timer is triggered.
Alarm State
Figure 3-6 Transient Alarm Suppression Example
alarm
Child
Hold-off Timeout
normal
Time (Seconds)
Child goes into

alarm and hold-off
timer is triggered.
Child returns to normal before

hold-off timeout expires; therefore,
no alarm is generated.
The alarm hold-off timer is not triggered anew if a new telemetry value is received for the
child while the alarm hold-timer is in effect.
3.2.4
Alarm Hold-off
Alarm hold-off is used to temporarily suppress child state alarms that result from data
krunching. Other types of alarms, such as command failure, execute as normal. Alarm holdoff is supported for analog and status points.
3.2.4.1
Communication Order and Alarm Suppression

Communication order can cause real-time events to be reported in an order that differs
from the actual order in which they occurred. This can result in false alarms that would
normally be suppressed using Alarm Suppression. The alarm hold-off timer helps delay
alarm processing to counter the effects of communication order. The Alarm Hold-off
Example (Figure 3-7) illustrates the concept.
Baseline
3-9
Figure 3-7 Alarm Hold-off Example

Telemetered Child
Alarm State
Real Parent
Telemetered
Parent
alarm
Alarm Suppression Timeout

Hold-off
Timeout
normal
Time (Seconds)
Real Parent
goes into alarm.
Child goes into the

alarm state but
alarming is delayed
by the Alarm Holdoff timer.
Parent suppresses
child alarm and
Alarm Hold-off
timer is cancelled.
Child returns to
normal without
generating alarms.
If there is no method to delay the evaluation of the childs alarm state until the parent
alarm state is updated, then suppression occurs after the child has gone into alarm. Both
alarm and RTN alarm events are generated for the child. The alarm hold-off timer
postpones the alarm long enough to receive the updated parent value.
In the Alarm Hold-off Example (Figure 3-7), alarm hold-off is triggered when the child
enters the alarm state. The alarm hold-off saves the childs previous value for comparison
with the value when the timer expires. The parent goes into alarm, sets the alarm
suppression timeout, and cancels the alarm hold-off timer. However, the parent does not
change the child value that is saved by the alarm hold-off. When the alarm suppression
timeout expires, the child is back to its original state; therefore, no alarm is generated.
NOTE The alarm hold-off timer is triggered when the points alarm state changes and
neither its parent alarm nor return-to-normal alarm has suppressed it. The alarm holdoff timer is cancelled if its parent goes into an alarm state before the hold-off timeout
expires.
3.3
Interaction Between Suppression Types

The combination of alarm suppression types does not affect the performance of each type.
An alarm is suppressed when it satisfies one of the suppression criteria.
The following illustrates the interaction of the different suppression types:
When the alarm hold-off timer prevents a point from being alarmed, then alarms
are suppressed for any child records of the point that are specified for parent
alarming or transient alarm suppression.
When the child of a point that is specified for parent alarming goes into alarm,
and its alarm is suppressed, the child suppresses alarming of any of its children that
are configured for parent alarm suppression.
When a points alarm is reevaluated at expiration of a suppression timer (e.g. parent alarm timer), the system evaluates any suppression criteria before generating
an alarm.
Baseline
3-10
3.3.1
Alarm Suppression Overview

The Alarm Suppression Overview window (Figure 3-8) provides a visual view of the different
alarm suppression types and the points with which a selected point is involved.
Opening the Alarm Suppression Overview window
Click Suppression Overview on the DMT.
Figure 3-8 Alarm Suppression Overview window
The window shows a selected point with a parent point that triggers parent control alarm
suppression for the point. It also shows a child point for which this point triggers parent
alarm suppression. Any transient alarm suppression configured for the point is also
displayed. If the selected point had multiple parent alarm-suppression triggers, or multiple
children for which it triggered alarm suppression, then they would also be displayed.
Selecting a point to view on the Alarm Suppression Overview window

Refer to the Alarm Suppression Overview window (Figure 3-8) to complete these steps.
1
Click the Table drop down arrow and select the table to which the point belongs.
In the Point: field, type or select the name of the point.
The selected points parents and children are displayed.
Baseline
3-11
NOTE Clicking the parent and child Edit buttons reveals details about the alarm suppression relationship between the selected point and its parent and child. You can also
modify the relationship using the Edit button.
3.3.2
Alarm Suppression Behavior

The suppression behaviors are additive. For example, if a child point is configured for
parent control, parent alarm, and transient alarm suppression, then timers for all the
configured suppression types may be active at any time. However, to determine if an
alarm should be generated, the system compares the alarm state when the first
suppression is triggered to the state when the last suppression timeout ends.
If, for instance, (a) a control suppression event is followed by a parent alarm suppression
event, and (b) the child points state changes, then after the control suppression timeout
expires, the system does not generate an alarm because the child is still suppressed by
parent alarm suppression. In the event that the parent alarm suppression timeout expires,
and no suppression timeout exists for the child, then the child points current state is
compared to the state when the control suppression trigger occurred. If it is different,
then the system generates an alarm.
In addition, XOS summary and annotated displays show the alarm icon next to the child
data whenever the child is in the alarm state, regardless of alarm suppression. The
suppression only applies to the alarm summary displays.
The alarm event is also recorded within the event summary. If the child points alarm state
changes during the suppression timeout, the summary shows when the system triggers
and cancels alarm suppression.
The analog and status summaries can show filtered lists of points that are currently in
alarm suppression. The summaries show child points actively suppressed if they have
undergone an alarm state change since alarm suppression was triggered.
3.4
Alarm Disturbance Mode

In alarm disturbance mode, the system suppresses alarms whose severity level is lower than
a configured severity. This mode of suppression applies to all types of alarm, such as statebased alarms and command failure alarms.
Return-to-normal state alarms are typically configured with low severity levels. Instead of
updating the alarm summary to show that the alarm has returned to the normal state,
alarm disturbance mode purges the alarm from the alarm summary. Alarm processing
requires considerable resources. Alarm disturbance mode helps reduce alarm processing
when the system is inundated with alarms. It also reduces the number of alarms submitted
to the operator.
The database administrator configures a maximum-severity-to-suppress, which takes
effect without the need to restart RealTime services.
The operator is provided with an interface to enable or disable alarm disturbance mode
(see the Alarm Summary window in the Operation and Control Reference). A developer
can also write an application to automatically enable or disable alarm disturbance mode.
Enabling or disabling alarm disturbance mode in one system does not affect the mode
setting in another system.
Baseline
3-12
When an operator disables alarm disturbance mode, the system regenerates suppressed
state-based alarms, such as those resulting from data krunch. Other low priority alarms,
however, such as command failure alarms and system alarms, are not regenerated. The
system reevaluates non-inhibited alarm records of analog, status, and rate points for which
no alarm record exists in the alarm summary.
3.4.1
The Alarm Disturbance Mode Edit Dialog Box

Use the Alarm Disturbance Edit dialog box (Figure 3-9) to suppress alarms whose severity
level is lower than a configured severity.
Figure 3-9 Alarm Disturbance Edit dialog box
Table 3-3 Fields and Buttons on the Alarm Disturbance Edit dialog box
Field/Button
Description
Record Name:
Name of the record whose alarm is being

configured
NOTE Record and system names are often the

same value.
System:
Name of system which owns the record

being configured
Maximum Severity:
Record alarms whose severity is lower than or equal to the one set by
this field setting are suppressed
For more information on the buttons, refer to the Standard Navigation and Configuration Information Guide.
Configuring alarm disturbance mode

1
Click Disturbance Mode on the DMT to open the Alarm Disturbance Edit dialog box
(Figure 3-9).
Select a record by clicking the arrow button next to the Record Name: field.
Select the system by clicking the arrow button next to the System: field.
Baseline
3-13
NOTE Record and system names are often the same value.
4
In the Maximum Severity: field, assign a maximum severity to suppress.
Do one of the following:

If you are adding a new configuration, click Add.
If you are reconfiguring a record, click Modify.
Click Dismiss.
Baseline
3-14
Baseline
MODULE 4
Message Sets and Alarm

Presentation
The application code that generates an alarm manages all aspects of system alarm
presentation. The user has no control over the way in which these alarms appear. Database
alarm presentation, however, is more flexible. For each point, telemetry tables (e.g.
analog, rate, status) can be configured individually for the following:
The severity assigned to the alarms
The message text applied to a state
The color of the point in any given state
In addition, alarm/event inhibiting allows the user to decide whether or not the point
generates alarms and events.
The system administrator level of access allows configuration of XOS colors in alarm
summary displays and the annunciation of alarms.
This module covers the following topics:
State Message Sets (Section 4.1)
Alarm Presentation Attributes (Section 4.2)
4.1
State Message Sets

Telemetered tables (analog, rate, remote, connection, and status) rely on the definitions in
the RealTimeDBs message table to provide the following:
Text messages associated with the current state of a point
Color, which is used with dynamic values in the table summaries and user drawings
Alarm severity information, which is used in the presentation of alarms in the interface
The base + offset scheme is used to access various state messages that apply to a given
device. During configuration of a RealTime record, a base message is specified in the base
message field. To generate a message, use the record defined by this base message plus an
offset determined by the state of the device.
Message sets are used to define states that apply to particular situations. For example,
specific names for hardware components may be used in defining applicable states for
these components.
NOTE Alarms may be generated for each of the states in the message table. The state
names defined in a message set are shown in the alarm and event messages.
Baseline
4-2
The following table shows the message sets that are used.
Table 4-1 Typical message sets in the message table

Set used for
analog and
rate points
Sets used for
remote points
Sets used for
connection
points
Sets used
for
omnicomm
points
Base Message
analog
rtu
conmsg
omnicomm
Record # 1
Normal
No Reply
No Connection
Inactive
Record # 2
High
Normal
Connected
Startup
Record # 3
High
Normal
Connected
Active
Record # 4
Low
Security Error
Connecting
Shutdown
Record # 5
Deviation
Long Message
Failed
Record # 6
High-high
Short Message
Error
Record # 7
Low-low
Wrong Remote
Retry
Record # 8
Instrument fail
high
Offline
Normal
Record # 9
Instrument fail
low
SBO Rly Fail
Bad Message
Record # 10
Rate of Change
Database Error
Poll Cycle
Record # 11
Off Scan
Offline
Record # 12
Illegal Message
Config Error
Record # 13
SBO Select Fail
Unavailable mdm
Record #14
Line Failure
Reservation mdm
Record #15
Hang-up mdm
Record #16
TX Error
Record #17
TX Short
Record #18
RX Error
Record #19
RX Short
Record #20
RX None
Record #21
Success
Baseline
4-3
Module 4 - Message Sets and Alarm Presentation
4.1.1
analog and rate Messages

The following tables shows the message texts used to indicate analog and rate alarms, as
set up in the message table.
Table 4-2 analog and rate alarm messages

Alarm Text
4.1.2
Description
Normal
Value is in the acceptable (normal) state
High
Value has exceeded the high limit (taking into account the deadband)
Low
Value has exceeded the low limit (taking into account the deadband)
Deviation
The instrument creep (deviation) limit has been exceeded
Hihi
Value has exceeded the high-high limit
Lolo
Value has exceeded the Low-low limit
Instrument fail hi
The analog/rate instruments upper limit has been reached. The upper limit is
configured in the Maximum (raw): field on the Analog Input dialog box or
on the Rate AnalogInput dialog box (refer to the RealTime Services Configuration and Administration Reference).
Instrument fail low
The analog/rate instruments lower limit has been reached. The lower limit is
configured in the Minimum (raw): field on the Analog Input dialog box or
on the Rate AnalogInput dialog box (refer to the RealTime Services Configuration and Administration Reference).
ROC
The rate at which the change in value has exceeded the specified limit
Remote Message Set

The first record (i.e. Record #1) in each telemetered points message set usually indicates
the condition that is considered normal. However, for the remote set, instead of the first
record, the second record (i.e. Record #2) contains the normal state. This exception to the
rule exists because fields containing real-time data (such as the remote records comsta
field) are initialized to zero when the system starts up with a cold start. Therefore, the
communication status summary shows no reply for the remotes until they are all
successfully polled.
4.1.3
Status Message Set

The base message for status points depends on whether the device is a two-state or a fourstate device. A two-state device only uses two messages: one state for the normal
condition and the opposite state for the off-normal condition (e.g. open and closed or
vice versa). A four-state device may have an additional transit state when the unit is in the
process of performing a state transition, and an error condition when the unit is not
working.
Different message text groups are defined in the message table according to the type of
status device. status alarm text (Table 4-3) lists the messages that are typically used for the
different states of a valve, a pump, and a breaker. The text may vary to represent the
interpretation of the various on/open/start or off/close/stop states and the different error
or transitional states.
Unless the Normally Open option is selected for the status point, an Open/Running/Trip
state of a field device should never be described as a Close/Off state. If the Close/Off state,
Baseline
4-4
for example, is used for a valve instead of the Open/Running/Trip state, the SCADA system
interprets the valve state as Close when it is actually Open. Selecting the Normally Open
option for the status point inverts the sense when the status raw value is converted to its
EGU value.
Table 4-3 status alarm text

Alarm Text
Description
Valve
Error
Valve is not operating (error).
Open
Valve is open.
Close
Valve is closed.
Transit
Value is in transit from open to closed or from closed to open.
Pump
Error
Pump is not operating (error).
Running
Pump is operating.
Off
Pump is not operating.
Sequence
Pump is in transit between running and off, such as ramp up sequencing.
Breaker
Error
Breaker is not operating (error).
Trip
Breaker has tripped (no electricity flowing).
Close
Breaker has closed (electricity is now flowing).
For two-state status records (i.e. one-bit status), the middle two messages of the message
set are used so that the same message set can be used for one-bit and two-bit status points.
The second message in the set must be for the Open/Start/On/Trip state, and the third
message must be for the Close/Stop/Off state. If the field device does not return a value of 1
to indicate the Open/Start/On/Trip state, then invert the sense of the status valve.
Configuration of status inputs is discussed in the RealTime Services Configuration and
Administration Reference.
4.1.4
Configuring Message Sets

Message sets can be created as system needs arise. However, baseline message sets should
not be altered because these provide a test set that has been proven to be valid.
Creating a new message set

1
Click Message on the DMT to open the Message Set Edit dialog box (Figure 4-1).
Baseline
4-5
Figure 4-1 Message Set Edit dialog box
In the Set Name: field, type the name of the new message set.
Click Add. This opens the Message Set Add dialog box (Figure 4-2).
Figure 4-2 Message Set Add dialog box
Type the number of states in the set.
Click Create Set.
Modifying a message set

Initially the names of the states are set to the same name as that of the message set. To change
these names, and to configure each member of the set, follow the steps outlined in this procedure.
1
Click Message on the DMT. This opens the Message Set Edit dialog box (Figure 4-1).

Type the message set name then click Search.
Select the message set name.
The Message Set Edit dialog box (Figure 4-1) should now show the states of the
selected message set.
Baseline
4-6
Double-click the state to be modified. This opens the Message Edit dialog box
(Figure 4-3).
Figure 4-3 Message Edit dialog box
Select a foreground color. The Foreground color: field determines the real-time color
of attach objects, such as devices and text messages, as they appear on the XOS dialog
boxes and windows.
Select a state severity.

NOTE The attributes of these alarm severity ratings are defined through the Alarm
Attribute Edit dialog box (Figure 4-4).
NOTE Typical color assignments for alarm severity levels are red for high, yellow for
medium, and green for low severity. If a message state is severe enough to justify attaching a red color (Foreground color: field is set to red), then the state severity should
match this message state (State Severity: field should be set to high). If a message
state uses a color (such as magenta, cyan, white) that is not defined for an alarm level, it
is recommended that this message state be assigned a low state severity level.
6
4.2
Click Modify.
Alarm Presentation Attributes

The severity of an alarm is indicated by color on various XOS alarm summary windows. A
severity level is assigned a specific color, as shown in the following table.
Table 4-4 Typical alarm severity color assignment

Severity Level
Color Assignment
High
Red
Medium
Yellow
Low
Green
Alarm severity is also indicated by the frequency and duration of beeping. More severe
alarms are typically configured to beep more rapidly. All alarms, regardless of severity, are
usually configured to beep until they are acknowledged.
Baseline
4-7
NOTE Information on alarm severity ratings are stored in the RealTimeDBs xosalmattr
table.
4.2.1
The Alarm Attribute Edit Dialog Box

The Alarm Attribute Edit dialog box (Table 4-4) is used to configure the presentation of
alarms.
Figure 4-4 Alarm Attribute Edit dialog box
The following table provides descriptions of the fields on the dialog box.
Table 4-5 Fields on the Alarm Attribute Edit dialog box

Field
Description
Name:
The name of the alarm attribute that is being configured.
Sound File:
The wave file that is used to announce any alarm of this severity.
Alarm Severity:
Refer to Typical alarm severity color assignment (Table 4-4).
Severity Color:
The alarm color is set via this field. For alarms in the alarm summary, the number of available severity levels is pre-defined.
Refer to Typical alarm severity color assignment (Table 4-4).
Beep Cycle Time (sec):
This field sets the length of the beep cycle.
Number of Beeps/Cycle:
This field sets the number of beeps per cycle. Higher priority
alarms should have more beeps per second than low priority
alarms.
Number of Cycles:
This field determines how often the cycle of beeps is repeated.

The cycle stops when either this number is reached, or the user
acknowledges the alarm, whichever comes first. For example, setting Number of Cycles: to 20 gives a repeat of 20 cycles before
the alarm sound disappears (if the alarm is not acknowledged
before that). If Number of Cycles: is set to -1, which is a common setting, the alarm is sent continuously and indefinitely until
the alarm is acknowledged.
Baseline
4-8
Configuring an alarm attribute

For more information, refer to Fields on the Alarm Attribute Edit dialog box (Table 4-5).
1
Click Alarm Attr. on the DMT. This opens the Alarm Attribute Edit dialog box
(Figure 4-4).
In the Name: field, type or select the alarm attribute.
Click the arrow next to the Sound File: field. This opens the WAV File Select dialog box
(Figure 4-5).
Figure 4-5 WAV File Select dialog box
Click the file name to select the file. To test the file before selection:
a Click the glue icon.
b Click the file name.
c
Click Test to play it.
d Click Dismiss after a suitable sound file has been chosen.

5
Select the alarm severity.
Select the severity color.
Type the length of the beep cycle in seconds.
Type the number of beeps per cycle.
Type the number of cycles.
10

If this is a new alarm attribute, click Add.
If you are modifying an existing alarm attribute, click Modify.
11
Click Dismiss.
Baseline
Index
A
Abnormal State Alarming .....................................1-3
acknowledge..........................................................1-8
addDBalarm ...........................................................1-8
addSYSalarm ..........................................................1-8
alarm ......................................................................1-1
alarm attribute
configuring .........................................................4-8
Alarm Attribute Edit dialog box ...........................4-7
Alarm Severity ....................................................4-7
Beep Cycle Time (sec) .........................................4-7
Number of Beeps/Cycle ......................................4-7
Number of Cycles................................................4-7
Severity Color......................................................4-7
Sound File ...........................................................4-7
Alarm Deadband ...................................................2-3
.............................................................................2-2
Alarm Disturbance Mode ....................................3-11
Alarm Hold-off.......................................................3-8
Alarm Holdoff ........................................................3-4
alarm limits ............................................................2-4
Alarm Presentation Attributes..............................4-6
Alarm Severity........................................................4-7
alarm severity
color assignment ................................................4-6
Alarm State ............................................................3-4
Alarm Suppression ......................................... 2-3, 2-7
Alarm Suppression Behavior ...............................3-11
Alarm Suppression Current Configuration...........3-1
Alarm Suppression Current Configuration window .
3-1
opening the ........................................................3-2
Alarm Suppression Edit Dialog Box ......................3-2
Alarm Suppression Edit dialog box.......................3-3
opening the ........................................................3-3
Alarm Suppression Overview ..............................3-10
alarms
database..............................................................1-2
limits....................................................................2-4
network alarms...................................................1-6
non-covered........................................................1-6
return-to-normal ................................................1-3
system alarms......................................................1-2
almsum Table .........................................................1-7
analog ..................................................................2-11
Analog Alarm Configure Dialog Box....................2-1
Analog Alarm Configure dialog box ....................2-2
Analog and Rate Messages ...................................4-3
Analog Inhibit dialog box ...................................2-10
archive ....................................................................1-2
D
database alarms .....................................................1-2
Deadband
Example...............................................................2-4
Deviation Alarm Limit ...........................................2-3
Deviation alarm limit.............................................2-5
E
Events .....................................................................1-1
events
event logging......................................................1-1
F
filteralm..................................................................1-8
Foreground color ...................................................4-6
H
Hi Alarm Limit ........................................................2-2
Hi/Lo Alarm Check .................................................2-2
Hi/Lo operating-range checking ...........................2-1
Hierarchical Alarm Suppression ............................3-5
Hierarchical Alarm Timeout ..................................3-6
Hierarchical Return-to-Normal Timeout...............3-7
HiHi Alarm Limit ....................................................2-2
HiHi alarm limit......................................................2-4
HiHi/LoLo Alarm Check..........................................2-2
HiHi/LoLo operating-range checking....................2-1
Historical Statistics .................................................1-5
B
Base Message .........................................................4-1
base plus offset ......................................................4-1
Beep Cycle Time (sec) ............................................4-7
C
cleanup ...................................................................1-2
Cmd Failure Timeout .............................................1-5
command failure....................................................1-3
Command Failure Alarming ..................................1-4
Command Timeout ................................................1-5
Command Timeout Alarming ...............................1-5
Commanded Status Points Alarming....................1-3
CommStats ..............................................................1-5
Communication Order and Alarm Suppression ...3-8
Configuring a status points abnormal states ......2-8
Configuring alarm disturbance mode ................3-12
Configuring an alarm attribute ............................4-8
connection............................................................2-11
ConnPeriodStats .......................................................1-5
Control-Initiated Alarm Suppression ....................3-4
creep .......................................................................2-5
Creep Detection ...................................... 2-1, 2-3, 2-5
creep detection ......................................................2-5
Inhibit alarming of uncommanded changes to

abnormal state ................................................2-9
Inhibit alarming of uncommanded changes to normal state ..........................................................2-9
Inhibit logging of uncommanded changes to abnormal state ..........................................................2-9
Inhibit logging of uncommanded changes to normal
state .................................................................2-9
Inhibiting Alarming and Logging .........................2-8
Baseline
Index - 2
Inhibiting Other Alarms and Logs ........................2-9

Inhibiting Status Alarms and Logs ........................2-8
InstAlarm ................................................................1-2
InstEvent.................................................................1-1
Instrument Fail Check .................................... 2-2, 2-3
Instrument failure checking ..................................2-1
instrument failure checking ..................................2-3
Interaction Between Suppression Types...............3-9
L
Lo Alarm Limit .......................................................2-2
Log Command Success...........................................1-7
Logging Commanded COS and Setpoints ............1-7
logging events .......................................................1-1
LoLo Alarm Limit ...................................................2-2
LoLo alarm limit .....................................................2-4
M
Message Edit dialog box
Foreground color................................................4-6
State Severity ......................................................4-6
Message Set Add dialog box.................................4-5
Message Set Edit dialog box .................................4-5
message sets
remote.................................................................4-3
status ...................................................................4-3
message table
message sets .......................................................4-2
messages
analog and rate alarm .......................................4-3
Modifying a message set.......................................4-5
N
network alarms ......................................................1-6
Network communication alarm text ....................1-6
non-covered alarms ...............................................1-6
Normal Alarm ......................................................2-10
Normal and Off-normal state determinants ......2-11
Normal Log ..........................................................2-10
Number of Beeps/Cycle .........................................4-7
Number of Cycles ...................................................4-7
O
Off-Normal Alarm................................................2-10
Off-Normal Log....................................................2-10
Opening a points Inhibit dialog box .................2-10
Opening the Alarm Suppression Current Configuration window ....................................................3-2
Opening the Alarm Suppression Edit dialog box 3-3
Opening the Rate Alarm Configure dialog box...2-6
Opening the Status Alarm Configure dialog box 2-7
Opening the Status Inhibit dialog box .................2-8
Opening the Status States dialog box ..................2-7
P
Parent Alarm ..........................................................3-3
Parent Alarm/Control ............................................3-4
Parent Control .......................................................3-3
Parent Return to Normal.......................................3-4
R
rate .......................................................................2-11
Rate Alarm Configure Dialog Box ........................2-5
Rate Alarm Configure dialog box
opening the ........................................................2-6
Rate of Change Alarm ................................... 2-2, 2-4
Rate of Change Limit.............................................2-5
Rate of Change Limits ...........................................2-2
rate-of-change .......................................................2-4
Rate-of-Change checking ......................................2-1
rate-of-change checks ...........................................2-4
remote ..................................................................2-11
Remote Message Set..............................................4-3
remote message set ...............................................4-3
RemPeriodStats ........................................................1-5
return to normal alarm .........................................1-3
Return-to-Normal Alarming..................................1-3
return-to-normal alarms........................................1-3
ROC .........................................................................2-4
S
Selecting a point to view on the Alarm Suppression
Overview window .........................................3-10
Setpoint Tolerance.................................................1-5
Severity Color .........................................................4-7
Sound File...............................................................4-7
State Message Sets.................................................4-1
State Severity .........................................................4-6
State-Based Alarming ............................................1-3
State-based alarming.............................................1-4
Status Alarm Configure Dialog Box......................2-6
Status Alarm Configure dialog box ......................2-6
opening the ........................................................2-7
Status Inhibit dialog box
opening the ........................................................2-8
Status Message Set ................................................4-3
status message set .................................................4-3
Status States dialog box ........................................2-7
opening the ........................................................2-7
Suppression Method
Parent Alarm.......................................................3-3
Parent Control ....................................................3-3
Transient .............................................................3-3
Suppression Overview .........................................3-10
Sustain COS Alarms................................................2-7
system alarms .........................................................1-2
T
Tables
almsum ................................................................1-7
tables
xosalmattr ...........................................................4-7
Timeout Alarms......................................................1-4
timeouts .................................................................1-5
Transient.................................................................3-3
Transient Alarm Suppression ................................3-8
U
Uncommanded Change-of-State ..........................1-4
Baseline
Index - 3
V
Valid for Specific State ..........................................3-4
W
WAV File Select dialog box ...................................4-8
X
xosalmattr table.....................................................4-7
Baseline
Index - 4
Baseline

DNA InstEvent Alarm

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DNA InstEvent Alarm

Uploaded by

Copyright:

Available Formats

OASyS DNA SCADA Suite

InstEvent and InstAlarm

10333 Southport Rd., S.W.

7000A Hollister Rd.

Phone: +1 713 939 9399

+1 403 253 8848

InstEvent and InstAlarm Reference

Copyright 2003 by Telvent Canada Ltd.

Document Revision History

Additions and Changes

Initial release of OASyS DNA.

Updated DNA components.

Release for OASyS DNA 7.4

This document describes the following components of OASyS DNA:

OASyS DNA SCADA Suite

Document Revision 1.1

OASyS DNA SCADA Suite

Document Revision 1.1

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

OASyS DNA SCADA Suite

Document Revision 1.1

Alarm Attributes - DMT.............................................................................................................1-8

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

OASyS DNA SCADA Suite

Document Revision 1.1

Network communication alarm text ........................................................................................1-6

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

OASyS DNA SCADA Suite

Document Revision 1.1

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

OASyS DNA SCADA Suite

Document Revision 1.1

Abnormal State Alarming

Commanded status Points Alarming

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

NOTE State-based alarming is triggered whenever an uncommanded status change

Command Failure Alarming

OASyS DNA SCADA Suite

Document Revision 1.1

Command Failure Timeout Alarming

Command Timeout Alarming

OASyS DNA SCADA Suite

Document Revision 1.1

InstEvent and InstAlarm Reference - Baseline

Table 1-1 Network communication alarm text

The workstation CPU is attempting to start up.

The workstation CPU is in the initialization stage of recovery.

Workstation CPU is in standby mode ready to go live if all conditions are

Workstation CPU is hot or live operational state.

OASyS DNA SCADA Suite

Document Revision 1.1

Logging Commanded COS and Setpoints

The almsum Table

The severity of the alarm