b0193rv e Dispalarmmngr
b0193rv e Dispalarmmngr
REV E
I/A Series®
Workstation Alarm Management
March 30, 2001
Horns
Alarm
Messages
Alarm Displays
Process Displays
Foxboro, Fox, and I/A Series are registered trademarks of The Foxboro Company.
Invensys is a trademark of Invensys plc.
Intel is a trademark of Intel Corporation.
Solaris and SunOS are trademarks of Sun Microsystems, Inc.
UNIX is a registered trademark of X/O Open Company, Ltd.
VENIX is a trademark of VenturCom, Inc.
Windows NT is a trademark of Microsoft, Inc.
All other brand names may be trademarks of their respective companies.
Preface................................................................................................................................. xiii
Audience ........................................................................................................................... xiii
Revision Information ........................................................................................................ xiii
Reference Documents ........................................................................................................ xiii
Document Conventions .................................................................................................... xiv
Typographical Conventions ........................................................................................... xv
Terms ........................................................................................................................... xvi
iii
B0193RV – Rev E Contents
iv
Contents B0193RV – Rev E
v
B0193RV – Rev E Contents
vi
Contents B0193RV – Rev E
vii
B0193RV – Rev E Contents
viii
Contents B0193RV – Rev E
ix
B0193RV – Rev E Contents
6. Tutorial – Configuring AMs and DMs with Standard Defaults .................................... 191
Alarm/Display Manager Configurator ................................................................................... 191
Default dmcfg File ........................................................................................................... 191
Accessing the Alarm/Display Manager Configurator ........................................................ 192
Initializing a New dmcfg Configuration File .................................................................... 192
Configuring the Display Managers ................................................................................... 193
Configuring the Alarm Managers ..................................................................................... 195
Creating the Second Alarm Manager ........................................................................... 196
Associating the DMs and AMs ......................................................................................... 197
Saving the Alarm Manager Configuration File .................................................................. 198
Creating the AM/DM Install Files from the .am File ........................................................ 198
Contents of the Configured dmcfg File ............................................................................ 199
Distributing the Install Files to the Workstations ............................................................. 200
x
Figures
Example of the Traditional (Pre-V4.2) Display Manager’s Environment Menu Bar ... xiv
Example of the new (FoxView) Display Manager ........................................................ xv
2-1. Process Alarm Overview .............................................................................................. 10
2-2. Information Movement ............................................................................................... 12
2-3. Sort Option ................................................................................................................. 14
2-4. Alarm Display Customized with a Trend Point Button ............................................... 19
2-5. Trend Generated for a Selected Alarm ......................................................................... 20
2-6. Display Manager Association with Alarm Managers .................................................... 23
2-7. Example Display Manager Usage Summary Display ................................................... 25
2-8. Standard Annunciator Keyboard on (50 Series System) ............................................... 31
2-9. Software Emulation of an Annunciator Keyboard (70 Series System) .......................... 31
3-1. Parts of an Alarm Display ............................................................................................ 64
3-2. Example of Current Alarm Display ............................................................................. 66
3-3. Example of Most Recent Alarm Display ...................................................................... 67
3-4. Example of Alarm Summary Displays ........................................................................ 69
3-5. Example of Alarm History Display .............................................................................. 70
3-6. Default Operations Display ......................................................................................... 71
3-7. Using the Find Command to Locate Particular Alarms ............................................... 76
3-8. Using the Match Command to Locate Particular Alarms ............................................ 77
3-9. Alarm Detail Window ................................................................................................. 78
3-10. Parts of an Alarm Display ............................................................................................ 84
4-1. ADMC Main Browser Window ................................................................................ 112
4-2. Relationship of Alarm Manager Schemes .................................................................. 113
4-3. Alarm Manager Schemes ........................................................................................... 114
4-4. Schemes used by the Foxboro Supplied Default Alarm Manager ............................... 116
4-5. Example of foxFullScreen AM Property Scheme (MRA) ........................................... 119
4-6. Examples of foxQuarter AM Property Scheme (CAD and MRA) .............................. 119
4-7. Examples of foxOldCAD AM Property Scheme (CAD and AHD) ........................... 120
4-8. Example of foxFullSq AM Property Scheme (NEWALM) ........................................ 120
4-9. Examples of foxStrips AM Property Scheme (CAD and NEWALM)
used with a Foxboro Default-Size Display Manager .................................................. 121
4-10. Examples of foxGrids AM Property Scheme (CAD, MRA, and NEWALM) ............. 122
4-11. ADMC Main Browser Window ................................................................................ 124
4-12. Configuring a New Alarm Manager .......................................................................... 131
4-13. Alarm Manager Property Scheme and Alarm Manager Display Type Dialog Boxes ... 132
5-1. ADMC Main Browser Window ................................................................................ 134
6-1. A Portion of the Default dmcfg File .......................................................................... 192
8-1. Emulation of Current Alarm Display ........................................................................ 227
8-2. Current Alarm Display with Operations Button ....................................................... 228
8-3. Operations Display Window ..................................................................................... 229
xi
B0193RV – Rev E Figures
xii
Preface
The I/A Series system provides flexibility in the presentation of process alarms. This document
focuses on the relationship of the Alarm Manager with respect to:
♦ Display managers
♦ Alarm alert database
♦ Common Alarm Groups
♦ Annunciator keyboards, FoxPanels, and internal and external horns
Audience
This document is intended for process engineers for Model 51 and 70 Series workstations. The
document assumes that the process engineer has configured the control database and devices to
receive process alarms (workstations, Historians, and printers) using the Integrated Control Con-
figurator (ICC), or that the process engineer is familiar with the configured control database and
the process alarm requirements. It is also assumed that the process engineer is familiar with display
managers.
System alarming is addressed as it relates to the alarm alert database resident in each workstation.
Revision Information
For Release 6.3, the following changes were made:
Chapter 7 “Tutorial – Customizing an Alarm Manager”
♦ Modified the instructions for customizing alarm displays indicating that you should
not customize the Alarm History format for a 10th of a second alarm value.
Reference Documents
Display Engineering for 50 Series Workstations (B0193MQ)
Display Engineering (Windows NT Operating System) (B0400MQ)
Display Manager/FoxView Calls (B0193DF)
FoxView (B0193WH)
FoxDraw (B0193WG)
Display Builder for 50 Series Workstations (B0193MP)
Display Configurator for 50 Series Workstations (B0193NL)
Process Alarm Configuration FoxPanels Configurator for Windows NT and Solaris (B0400AU)
Process Alarm Configuration (non-51 and non-70 Series workstations) (B0193AU)
Workstation Configuration (B0193AG)
Integrated Control Blocks Description (B0193AX)
Integrated Control Software Concepts (B0193AW)
Integrated Control Configurator (B0193AV)
xiii
B0193RV – Rev E Preface
Document Conventions
The configurator software and run-time software described in this document can be run on mul-
tiple platforms: UNIX and Windows NT. Because of this, this document describes the behavior
of the software on both platforms. Although most of the software’s capabilities are similar, there
are slight differences.
♦ Most of the illustrations of windows and dialog boxes in this document show the
UNIX version of displays. Windows and dialog boxes on a Windows NT platform are
slightly different, but contain the same information. Significant differences between
the two versions are noted.
♦ File paths are different between the two operating systems. Examples in this document
show UNIX file paths. When necessary, differences between the two operating sys-
tems are noted.
This document refers to the FoxView display manager. Optionally, your system may be config-
ured to use the display manager of previous software releases (called Display Manager).
The following illustrations show the traditional (pre-Version 4.2) Display Manager and the Fox-
View display manager.
Click here
xiv
Preface B0193RV – Rev E
Typographical Conventions
The paper form of this document uses these typographical conventions (fonts).
Example Purpose
Enter date (mm/dd/yy): In an example, shows the workstation’s output
or display
AMNAME 54AW51 54AW51 .- foxDefault In an example, shows actual content of a file
almack or dmcmd In a paragraph, identifies the name of a
command or utility
compound:block.parameter.bitextension In a syntax statement, shows parts of a
command
cd \usr\display In an example, shows a user entry
Process or File or Save In a paragraph, identifies a button, field, or
menu item on the workstation’s user interface.
xv
B0193RV – Rev E Preface
Example Purpose
bold text In a paragraph, emphasizes a word
Workstation Alarm Management In a paragraph, identifies the name of a
document. In a note, however, a document’s
title is not italicized
The on-line form of this document uses these typographical conventions (fonts).
Example Purpose
Enter date (mm/dd/yy): In an example, shows the workstation’s output
or display
AMNAME 54AW51 54AW51 .- foxDefault In an example, shows actual content of a file
almack or dmcmd In a paragraph, identifies the name of a
command or utility
compound:block.parameter.bitextension In a syntax statement, shows parts of a
command
cd \usr\display In an example, shows a user entry
Process or File or Save In a paragraph, identifies a button, field, or
menu item on the workstation’s user interface.
bold text In a paragraph, emphasizes a word
Workstation Alarm Management In a paragraph, identifies the name of a
document. In a note, however, a document’s
title is not italicized
Terms
This document uses the following terms.
Term Meaning
display manager The workstation’s display manager (either the traditional
Display Manager or the FoxView display manager)
Display Manager The traditional (Pre V5.0) display manager
FoxView The new (V5.0) display manager
Remote terminal A terminal running X windows
These action terms are used throughout this document and the on-line help.
Term Meaning
Click Move the mouse pointer over an item and quickly press and release the left
button.
xvi
Preface B0193RV – Rev E
Term Meaning
Choose Carry out an action. You usually click the left mouse button on an item to:
Designate a menu bar field from a menu bar
Run a command from a drop-down menu
Run a command from a button
Select Mark an item (often shown when the item is highlighted, or boxed).
Sometimes you can use the TAB key or an arrow key to move the cursor to
the item. Selection does not start an action.
Also, the terms control station and control processor are used interchangeably.
xvii
B0193RV – Rev E Preface
xviii
1. Introduction to Workstation
Alarm Management
This chapter defines the terms “display manager” and “Alarm Manager”. It also describes the
available on-line help.
The I/A Series system offers many ways to manage the receipt of alarm information. From the
perspective of the workstation, you configure the presentation of alarm displays to meet your site’s
objectives.
A display manager (DM) provides access to process displays and applications in the I/A Series
environments including Alarm Manager display windows. Each DM is a window and is indepen-
dent of other DMs. The I/A Series includes two display managers: Display Manager and Fox-
View. Refer to Display Engineering documentation for more information.
An Alarm Manager (AM) provides a graphical user interface in which to view alarm information.
The view is comprised of a set of customizable display windows, representing different views of a
workstation’s alarm alert database. Each AM’s display windows are independent of the display
windows on other AMs. For each AM, all AM display windows can be simultaneously open, pro-
viding multiple views of the alarm alert database.
Users of Pre-V4.2 versions of the I/A Series software are familiar with the Display Manager, which
handled the Current Alarm Display (CAD) and Alarm History Display (AHD). The Alarm Man-
ager now handles these displays and five additional displays. Refer to Chapter 3 “Alarm Manager
Displays”.
This document focuses on Alarm Managers and display managers, which are two software tasks
that you can configure. In general, you set up properties for the display managers and Alarm
Managers that determine the presentation of alarm information at the workstations. This docu-
ment is supplemented by on-line Help available while you are running various applications.
This chapter introduces the information in this document and provides a starting point for learn-
ing how to configure your site’s workstations with regard to the presentation of process alarms
information.
Alarm Management
Each site has its own objectives and needs. Depending on your system’s hardware configuration
(number and type of workstations, CRTs or heads, Annunciator keyboards or FoxPanels,
and printers) and software licences, you can configure these alarm-related items:
♦ Alarm alert database attributes
♦ Environments and access levels
♦ Workstation groupings (Common Alarm Groups)
♦ Annunciator keyboards, FoxPanels windows, and workstation horns
♦ Display coordination (also called display redirection)
♦ Alarm recovery
1
B0193RV – Rev E 1. Introduction to Workstation Alarm Management
Workstations
Each site has its own array of hardware (workstations). Your site can include these UNIX-based
and Windows NT-based workstations:
♦ 50 Series workstations (single- or dual-headed)
♦ 70 Series workstations (single-, dual-, or quad-headed)
♦ Remote X terminals
♦ WP20, WP30, or PW workstations
Document Content
The primary focus of this document is process alarm management from the perspective of the
workstation. The document includes conceptual information and tutorials. Much of the how-to
information you will need to configure your system is in this document and also in on-line Help.
Descriptions of options within windows and dialog boxes are available in this document and also
through on-line Help.
This document is split into these parts:
Subject Refer to
Alarm subsystem background information Chapter 2 “Alarm Subsystem”
Alarm Manager displays Chapter 3 “Alarm Manager Displays”
Configuring Alarm Managers and display managers Chapter 4 “Configuring Alarm Managers
and Display Managers”
Using the Alarm/Display Manager Configurator Chapter 5 “Using the Alarm/Display
Manager Configurator”
Setting up additional display managers and Alarm Chapter 6 “Tutorial – Configuring AMs
Managers using default values and DMs with Standard Defaults”
Customizing Alarm Manager displays Chapter 7 “Tutorial – Customizing an
Alarm Manager”
Emulating Pre-V4.2 alarm displays Chapter 8 “Emulating Pre-V4.2 Alarm
Displays”
On-Line Help
Many I/A Series applications include on-line Help, which provide how-to and reference informa-
tion.
These are the help files associated with Alarm Managers and the Alarm/Display manager Config-
urator:
2
1. Introduction to Workstation Alarm Management B0193RV – Rev E
Each of these help files describe customizing the alarm alert database, working with CAGs, pro-
cess display call-up, and include other workstation-related information.
NOTE
The Annunciator Configurator/FoxPanels Configurator’s help file is
foxpancf.hlp. The FoxPanels Runtime Manager’s help file is foxpanel.hlp.
NOTE
Alarm Manager help is currently not available from the Alarm Manager application
(that is, there is no method of entry such as a help menu or button). Use one of the
following methods to view Alarm Manager help file (am.hlp), which is located in
the /usr/fox/wp/bin directory.
Document Content 3
B0193RV – Rev E 1. Introduction to Workstation Alarm Management
/opt/windu/bin/hyperhelp filespec
filespec refers to the path and filename of the on-line help file.
NOTE
Omitting filespec calls up a browser window, allowing you to locate the file.
Considerations
Read and become familiar with the following considerations.
NOTE
Review your resource needs when adding additional Alarm Managers.
4
1. Introduction to Workstation Alarm Management B0193RV – Rev E
6
2. Alarm Subsystem
This chapter describes how the alarm system operates.
These topics are described:
♦ Alarm subsystem
♦ Alarm notification
♦ Process alarms
♦ Responding to alarms
♦ Alarm alert database defaults
♦ Alarm Manager
♦ Display managers
♦ Security
♦ Alarm Manager Object Manager connections
♦ Annunciator keyboards and lights and FoxPanels windows
♦ Horn management
♦ Common Alarm Groups
Read this chapter before configuring the display managers and Alarm Managers at your site.
Alarm Subsystem
A workstation’s alarm subsystem software comprises three distinct key processes:
Process Function
Alarm Alert (AA) Receives process alarm messages from the control stations and
maintains the workstation’s list of alarms in a database (alarm
alert database). This process also maintains status information
for setting Annunciator keyboard and FoxPanels lights.
Alarm Server Task (AST) Distributes alarm information maintained by AA to each of the
alarm display processes (AMs) as it is updated by AA.
Alarm Manager (AM) Displays alarm information in a graphical user interface using a
set of pre-configured displays.
Alarm Notification
Develop an understanding of how the Alarm Manager receives alarm information and what hap-
pens when an alarm occurs.
7
B0193RV – Rev E 2. Alarm Subsystem
Types of Alarms
The I/A Series system supports two types of alarms:
♦ Process alarms, indicating alarm conditions generated by the software (compounds
and blocks) resident in control stations.
♦ System alarms, indicating hardware failures from network or station equipment. Refer
to System Management Displays (B0193JC) for information about system alarms.
Process Alarms
There are many potential process alarms, such as:
♦ Out-of-range conditions
♦ Deviation alarms
♦ Measurement alarms
♦ State alarms
♦ Confirmation messages (FoxBatch)
The destinations for these alarm messages are configured using the Integrated Control Configura-
tor (ICC). Standard I/A Series alarm destinations are workstation(s), printer(s), and Historian(s).
8
2. Alarm Subsystem B0193RV – Rev E
Each block within a control station maintains an alarm status parameter (ALMSTA) to which
both I/A Series system graphics and user graphics can be connected. The ALMSTA parameter
indicates current outstanding alarm conditions within the block and the alarm acknowledge state
of the block. Refer to Integrated Control Software Concepts (B0193AW) and Integrated Control
Block Descriptions (B0193AX) for more information.
NOTE
Be aware that alarm message generation and detection can be inhibited. Refer to
Integrated Control Block Descriptions for more information.
Physical Notification
The Process button (FoxView) or Alarm button (Display Manager) indicates the current status
of alarm(s) in the workstation’s database. Clicking the Process/Alarm button accesses the alarm
displays from which to access these process displays:
♦ Block Detail Displays
♦ The top priority display
♦ User-built displays
On a 70 Series workstation configured with a sound circuitry and speakers, a horn may sound, or
a sound file (.WAV file) may be played. Also, an Annunciator key or FoxPanels button may light
up.
In response to an outstanding alarm condition, an operator may initiate an action from the work-
station using:
♦ Alarm displays
♦ Annunciator keys (or FoxPanels buttons on 70 Series workstations)
♦ Process displays (Block Detail Displays and user-defined graphics)
Alarm Notification 9
B0193RV – Rev E 2. Alarm Subsystem
Horns
Alarm
Messages
Alarm Displays
Process Displays
10
2. Alarm Subsystem B0193RV – Rev E
Certain alarm displays set up Object Manager connections to the control processor. These alarm
displays are immediately updated with changes to the alarmed analog parameter value and status
information, that is, the return-to-normal and block acknowledgment state transitions. The
CAD, when optionally configured, can form an Object Manager connection only to a control
processor’s analog value parameter (not to the ALMSTA status parameter). CAD updates repre-
senting return-to-normal and acknowledge status changes are dependent upon the reception of
return-to-normal and acknowledge messages being received from the control stations.
NOTE
If a connection cannot be made, such as when a cable disconnects, the color of the
value and alarm tag turn cyan; refer to Process Operations And Displays.
Therefore, when the block comes out of the alarm state, the control processor sends a return-to-
normal message to the alarm alert database. Due to their Object Manager connection to the
ALMSTA parameter, certain alarm displays reflect this returned-to-normal transition.
Alarm Notification 11
B0193RV – Rev E 2. Alarm Subsystem
CP Workstation
Sends a message
Block Alarm
Alert
Database
12
2. Alarm Subsystem B0193RV – Rev E
Historian Interface
Alarm messages may be configured with the Integrated Control Configurator to be directed to an
Historian database.
Any Historian on the I/A Series system may supply alarm information to the Alarm History Dis-
play. On 50 Series and 70 Series stations, a list of Historians is available for selection. The default
Historian is located on the logical host of the workstation.
Configurable Options
You customize an alarm alert database by modifying the values of options in a workstation’s
init.user start-up file. Refer to the Alarm Manager on-line help for information for configuration
procedures, available options, and the valid values each option can take.
NOTE
Maintain a consistent configuration scheme for alarming options across all the
workstations in your I/A Series system.
Each workstation’s alarm alert database initially contains default attributes. These attributes affect
information in alarm displays and horn notification.
These are the init.user file default attributes:
Attribute Default
Number of alarm entries in 200
memory (MAX_CAD)
Attribute Default
Alarm entry sort By in-alarm versus return-to-normal, by acknowledged, by
(SORT_CFG) priority, and then by time
Clear alarm button option Clear the alarm from the database only on the workstation
(CLR_OPT) initiating the action. The associated annunciator light or any
control block is unaffected
Return-to-normal action Maintain the alarm entry in the list and designate it as returned-
(RTN_DROP) to-normal and unacknowledged. The annunciator light associated
with the block continues to flash until acknowledged
Figure 2-3 shows an example of a site’s alarm alert database. In this example, the alarms are sorted
first by in-alarm vs. return-to-normal, then each group is sorted into acknowledged and unac-
knowledged alarms. Next, the alarms in each of the four groups are sorted by priority. Last, the
alarms within each of the priority groups are sorted by time. The alarm indicated as “Time 1” at
the top of the illustration would be the top priority alarm. Also note that the group of alarms
shown as Time 1 through Time N is the most recent alarms.
Time 1
Time 2 Highest
Priority 1
Time 3
Priority 2 .
Time 4
Unacknowledged Priority 3 Time N
Priority 4 .
Priority 5
In-Alarm
Priority 1
Priority 2
Priority 3
Acknowledged Priority 4
Priority 5
Alarms in the
Alarm Alert Database Priority 1
Priority 2
Unacknowledged Priority 3
Returned-to- Priority 4
Lowest
Normal Priority 5
NOTE
Acknowledged return-to-normal alarms are removed from the alarm alert database.
14
2. Alarm Subsystem B0193RV – Rev E
Configurable Options
The values of the ALMPRI and ALMRTN alarm alert database attributes affect the ALMTXT
and ALMCNT workstation globals.
Attribute Default
Alarm text string save priority option (ALMPRI) Only alarm Priorities 1 and 2 cause updates
Alarm message types save option (ALMRTNS) Only in-alarm messages cause updates
To indicate the alarm text string and the current number of alarms, connect the ALMTXT and
ALMCNT workstation globals to display objects. For more information about these globals, refer
to the Alarm Manager on-line help.
Requirements
Proper use of alarm recovery requires that the control stations are configured to send the same set
of alarms to both workstations. This way, each workstation maintains the same active alarm alert
database information.
In addition, the backup workstation must also be configured with the same Annunciator key-
board (or FoxPanels window) control block assignments as the requesting workstation.
NOTE
If a 50 Series or 70 Series station recovers alarm alert database information from a
non-50 Series or non-70 Series station (such as a WP20/30), the alarm timestamp
does not include the number of milliseconds.
Alarm Manager
The Alarm Manager (AM) is the entity running on a workstation that provides a set of display
windows (alarm displays) from which to view:
♦ Alarm alert database information
♦ Alarm status information from control processors
An Alarm Manager provides a set of displays (six alarm displays and an Operations display) that
work in conjunction with the workstation’s display managers, allowing easy access to process dis-
plays through alarm display menu commands and buttons. You can respond to process alarm con-
ditions using customized graphics for your needs.
The Object Manager connection updates the parameter value in alarm on an alarm display.
The AM, which is modeled after the workstation’s display manager, incorporates these display
manager features:
♦ User-specific environments and security access
♦ Operator Action Journaling (OAJ)
♦ The ability to process AM-specific built-in commands
NOTE
If you have assigned access classes to Pre-V4.2 displays, make similar assignments to
Alarm Manager alarm displays. For more information, refer to the Alarm Manager
on-line help.
You associate an environment script with an Alarm Manager by means of the Alarm Manager’s
property scheme. Similar to the DM, you may assign the Alarm Manager an operating class, such
as Boot or Operator. By means of the Alarm Manager’s user interface scheme, you set an access
code (protection code from 0 to 255) that restricts the use of display functions.
16
2. Alarm Subsystem B0193RV – Rev E
Alarm Displays
Unlike the display manager, which provides information in a single display window, one instance
of an Alarm Manager can display alarm information to six distinct display windows:
♦ Current Alarm Display (CAD)
♦ Most Recent Alarm Display (MRA)
♦ New Alarm Display (NEWALM)
♦ Acknowledged Alarm Display (ACKED)
♦ Unacknowledged/Returned-to-Normal Alarm Display (UNACK)
♦ Alarm History Display (AHD)
The NEWALM, ACKED, and UNACK displays are referred to as summary displays.
You can customize most of the alarm displays’ aspects to suit your site’s requirements. Alarm dis-
plays are described in Chapter 3 “Alarm Manager Displays”, and the Alarm/Display Manager
Configurator used to customize the alarm displays is described in Chapter 4 “Configuring Alarm
Managers and Display Managers” and Chapter 5 “Using the Alarm/Display Manager Configura-
tor”.
Alarm Manager 17
B0193RV – Rev E 2. Alarm Subsystem
the Alarm Manager on-line help for information about configuration procedures and the available
options and the valid values each option can take.
NOTE
Maintain a consistent configuration scheme for alarming options across all the
workstations in your I/A Series system.
Each workstation’s alarm alert database initially contains default attributes which affect informa-
tion in alarm displays and the horn configuration. These are the default display attributes:
Default Color
Attribute Priority (foreground/background)
Unacknowledged alarm priority colors Priority 1 White/Red
Priority 2 White/Magenta
Priority 3 White/Brown
Priority 4 White/Cyan
Priority 5 White/Dark gray
Acknowledged alarm priority colors Priority 1 Red/Gray
Priority 2 Magenta/Gray
Priority 3 Brown/Gray
Priority 4 Cyan/Gray
Priority 5 Dark gray/Gray
Return-to-normal priority colors Priority 1 White/Red
Priority 2 White/Magenta
Priority 3 White/Brown
Priority 4 White/Cyan
Priority 5 White/Dark gray
18
2. Alarm Subsystem B0193RV – Rev E
Alarm Manager 19
B0193RV – Rev E 2. Alarm Subsystem
This next user-supplied application with the compound name, block name, and alarm type of the
selected alarm as arguments to the application. You could assign the following command to a but-
ton labeled “Notepad”:
run /opt/bin/attach_notes <Compound> <Block> <AlarmType>
NOTE
The Current Alarm Display can optionally be configured to form an Object Man-
ager connection to update the alarmed parameter of an analog alarm entry.
20
2. Alarm Subsystem B0193RV – Rev E
NOTE
The Current Alarm Display can optionally be configured to form an Object Man-
ager connection to update the alarmed parameter of an analog alarm entry.
The Alarm Manager, similar to the display manager, forms Object Manager connections
to control stations, enabling rapid presentation of a change to the alarm status information. When
an alarm becomes acknowledged, the MRA and summary displays are not impacted by delays
caused by:
♦ The time required for a control station to send alarm acknowledge messages to each
alarm destination
♦ The time latency due to the internal workstation processing through the Alarm Alert
subsystem
♦ The display’s refresh rate
Each connectable AM display is limited to one OM list, which holds a maximum of 255 points.
Each alarm can require up to two points in the list: one for the block’s alarm status parameter
(ALMSTA) and one for the analog parameter in alarm, such as MEAS. If multiple alarms exist
within the block, the AM optimizes the number of points in the list by sharing the ALMSTA
point between two or more alarm entries.
Unlike the display manager, which connects to a fixed set of control stations based upon the con-
trol parameters configured in a graphic display, AM connections are dynamic. AM connections
depend upon the control stations that have generated alarms to the workstation at a particular
time and are currently in view on a workstation. The situation at that moment dictates the con-
Alarm Manager 21
B0193RV – Rev E 2. Alarm Subsystem
trol stations to which the AM will establish connection. An hour later, for example, the same AM
display may be connected to a different set of control stations.
Connection Points
The following OM connection points background information is provided to help you apply
match/filter criteria to a display to limit the number of control station connections established by
the Alarm Manager for any of its connected alarm displays.
OM Connection Points
The AM adds OM connection points only to the open list for alarms shown in the display. For
example, a New Alarm Display might contain 436 alarm entries, but only 30 are in view at any
one time. The AM adds points to the list associated with only those 30 alarm entries.
When an alarm has a connection that is no longer displayed, the AM deletes the connection for
that alarm, but not immediately.
Because alarms can oscillate, the following rules prevent the unnecessary addition (or deletion) of
connection points, which would place a burden on the system.
♦ An alarm must be present in the display window for a minimum of two seconds
before the AM adds connection points for it. This prevents extraneous connections
from being made when an operator scrolls through a display.
♦ An alarm must be off the display window for a minimum of thirty minutes before the
AM removes a connection point.
♦ Any time the OM list becomes full, the entire list is closed and is reopened afresh.
Closing the entire list and reopening it uses fewer system resources than performing
a multitude of dynamic deletions from the list.
♦ When an alarm appears in a display window, a delay of up to 8 seconds is possible
before the first update occurs. The delay is equivalent to the sum of:
OmConnectDelay + OmActivateDelay + OmRefRate
Delay Specifies
OmConnectDelay How long an alarm must be in the display window
before the AM starts to add points for it to the OM
list (2 second default).
OmActivateDelay How often the AM is allowed to perform an
“activate” on the list; essentially, an add must be
followed by an activate to make it occur. This
allows the AM to optimize the number of activates
needed for multiple additions. (1 second default).
OmRefRate How often the OM should provide updates
regardless of how often the data is actually changing
in the control station (5 second default).
Though each AM display is limited to one OM list, this maps to a variable number of workstation
IPC connections, each for a different control processor from which alarms have been received and
22
2. Alarm Subsystem B0193RV – Rev E
are displayed. Take these considerations into account when determining the number of AMs to
display alarms on a given workstation.
♦ From the control station perspective, consider the number of workstations and associ-
ated Alarm Manager displays from which alarm conditions are to be viewed when
establishing alarm destinations.
DM/AM Association
A display manager accesses the Alarm Manager with which it is associated.
Each DM can access its own dedicated AM, or multiple DMs can access the same AM; refer to
Figure 2-6. Associating multiple display managers with a single Alarm Manager, however, offers
the best use of a workstation’s memory and computing power.
Display Manager
Alarm Manager
Display Manager
NOTE
Associating one display manager with two Alarm Managers is not a valid associa-
tion.
Clicking the Process/Alarm button silences the horn(s) and accesses the alarm displays for analyz-
ing, acknowledging, and clearing alarms.
24
2. Alarm Subsystem B0193RV – Rev E
For example, Figure 2-7 shows the station letterbug as DMWP50, and the display manager as
DMWP50.
Restrictions
Although licensing allows one AM to be run per DM on a workstation, memory constraints and
the computing power of an individual workstation may require that multiple DMs access a single
instance of an AM.
NOTE
With the functional capabilities of a single AM (seven display windows), configur-
ing multiple DMs to access a single AM is appropriate for most sites.
Before you can use an additional license, you must configure the additional DM(s) and AM(s).
The minimum information required are the names of additional DMs and AMs.
For flexibility, you can configure more display managers and Alarm Managers than the number of
available licenses. At any given time, however, the number of DMs running on a 50 Series or
70 Series station is limited to the number of licenses available on that station. Refer to the display
engineering documents for size and style considerations. Refer to the System Operations Guide
(B0193CR) document for information on starting and stopping additional DMs.
! CAUTION
Observe caution if you use a text editor to modify the dmcfg file.
The information in the dmcfg file determines where each DM window and each set of AM dis-
play windows appears (the same monitor, either monitor of a dual-headed workstation, or a
remote terminal running X Windows).
DM/AM association is not bidirectional. Association refers only to a display manager having
access to an Alarm Manager.
26
2. Alarm Subsystem B0193RV – Rev E
Security
You can control your system’s security by using the I/A Series environments and by setting up
access levels and passwords.
Security Access
The Alarm Manager and display manager use password protection to limit user access to particu-
lar I/A Series environments. This type of protection enables access to menus, menu items, and
buttons within an environment via access codes and protect/unprotect commands.
By default, remote Alarm Managers and view-only Alarm Managers disable the security-sensitive
capability to:
♦ Acknowledge alarms
♦ Clear alarms
♦ Silence horns
♦ Mute and unmute horns
Disabling this capability disables (grays) the buttons.
By default, remote display managers and view-only DMs disable:
Security 27
B0193RV – Rev E 2. Alarm Subsystem
28
2. Alarm Subsystem B0193RV – Rev E
Security 29
B0193RV – Rev E 2. Alarm Subsystem
OAJ. The AM sends messages to the same printer and Historian that was configured for the DM
with the same name. If no DM has the same name, the AM follows the behavior of the letterbug
DM.
These alarm-related operations are included in the OAJ with other process-related operations:
♦ Alarm acknowledgment
♦ Horn muting/unmuting
♦ Environment changes
NOTE
When configuring AMs and DMs, carefully consider the naming conventions used
if one or more OAJs are to be used.
The logging of alarm-related actions is configured per Alarm Manager. An Alarm Manager’s log-
ging behavior is based on the logging behavior of the same-named display manager. An AM logs
to the printer and Historian configured for the same-named DM.
When the DM processes an ojinit command (following a change to the OJLOG variable), it noti-
fies the appropriate AMs so they will respond to the logging behavior changes.
30
2. Alarm Subsystem B0193RV – Rev E
Pressing an annunciator key (or clicking a FoxPanels button) can run a program, display a
graphic, or both. This capability is achieved by configuring an annunciator key (or FoxPanels but-
ton) to invoke the assigned program(s) and display(s). Customized graphics for the particular set
of compounds and blocks (control assignments) enable an operator to quickly address alarm con-
ditions.
Use the FoxPanels Configurator graphical user interface to create Annunciator and FoxPanels
configuration files. The configuration task is further simplified, if desired, by permitting the con-
figurator software to automatically extract control assignments from a user graphic being assigned
to the key and assigning them to the annunciator light (or FoxPanels button). Complete descrip-
tions of configuration tasks are in the FoxPanels Configurator on-line help.
Annunciator Keyboards
WP51 and AW51 workstation support a maximum of two annunciator keyboards (four for
WP/AW51 workstations with dual CRTs). The keyboards may be annunciator keyboards
or annunciator/numeric keyboards, or one of each. Each workstation has a console horn,
and each keyboard has a horn.
When configured with the FoxPanels Configurator, horns may sound and the lights associated
with keys on the annunciator panels may flash or go steady to indicate the following process alarm
conditions:
♦ A block alarm condition
♦ A block return-to-normal
♦ An unacknowledged or acknowledged block
When an annunciator light flashes, pressing the associated annunciator key initiates a previously
configured display and/or program and/or display manager command(s).
If nothing is configured, a Block Detail Display appears, depending on the block(s) assigned
to the light in alarm.
If multiple blocks assigned to a light are in alarm, the Block Detail Display associated with the
highest priority block alarm (according to the sort option in the alarm alert database) is accessed.
The FoxPanels Configurator can also associate process displays with the block(s) for direct access
and for alarm display access. Assignment can be made to the AAtab file to call up user displays
from alarm displays without requiring the user to push an Annunciator key or press a FoxPanels
button. Refer to the FoxPanels Configurator on-line help.
NOTE
You can achieve the same display call-up without Annunciator hardware if assign-
ments are made in the AAtab file.
Annunciator Lights
Annunciator lights display theses conditions:
NOTE
The “annun” built-in command provides the capability to transition annunciator
lights to indicate an application-generated error rather than block-generated error.
Refer to the display engineering documentation for details.
32
2. Alarm Subsystem B0193RV – Rev E
Pressing a button/key on that panel sends the associated key configuration to the target DM for
execution. If no target DM name is specified in the configuration, the target DM defaults to the
letterbug DM.
An individual alarm panel key/button can be configured with a target DM, overriding any exist-
ing panel redirection. The key is not redirected when the panel is redirected, and the key’s com-
mands are sent to the configured DM name, regardless of annunciator panel redirection. Refer to
Process Alarm Configuration (B0193AU) for more information.
FoxPanels
The FoxPanels Configurator supports any combination of soft alarm panels. The total number of
alarm keys and buttons cannot exceed 192.
Horn Management
Three types of optional horns can sound when a system alarm or process alarm occurs:
♦ Two keyboard horns per WP/AW51 (four keyboard horns per a dual-headed CRT
WP/AW51
♦ One console horn per WP/AW51 (two console horns per WP/AW51s with dual-
headed CRTs)
♦ Six horns external to the I/A Series equipment
Depending on the alarm priority, a horn can sound for a system alarm, process alarm, or both.
The keyboard and console horns for alarm priority or system alarms have up to three configurable
tone levels. 70 Series systems configured with a sound board and speakers can additionally play a
.WAV file. The horn tone changes only when the priority of the new alarm is higher than the pri-
ority of the alarm that originally caused the horn to sound.
External horns, which do not support configurable tone levels, require that you specify a separate
digital output parameter for each of the alarm priorities and the system alarm.
NOTE
By default, the capability to mute a horn is accessible from the Alarm Manager’s
Operations display. When muted, “Horns Muted” appears in the status area of an
alarm display on 50 Series and 70 Series stations. If non-50 Series or non-70 Series
stations are members of the same Common Alarm Group, the Horns Muted mes-
sage appears on the message line when the CAD is active or refreshed.
Horn Management 33
B0193RV – Rev E 2. Alarm Subsystem
NOTE
Maintain a consistent configuration scheme for alarming options across all the
workstations in your I/A Series system.
Each workstation’s alarm alert database initially contains default attributes which affect informa-
tion in alarm displays and the horn configuration. These are the default horn attributes:
Attribute Default
Horn option Manual silencing via the display. Regardless of the configured
(HORN_OPT) horn option, the ACK button on an annunciator keyboard
continues to silence horns.
Resounding option The action of the horns when unmuted (if alarms have
(RESOUND) occurred during the muted period). The default is to not
resound the horn.
34
2. Alarm Subsystem B0193RV – Rev E
NOTE
If a 50 Series or 70 Series station recovers alarm alert database information from a
non-50 Series or non-70 Series station (such as a WP20/30), the alarm timestamp
does not include the number of milliseconds.
Each workstation in the system can be configured as part of one large Common Alarm Group,
one smaller subgroup, or two smaller subgroups. If a workstation is a member of two CAGs, issu-
ing a Clear Alarm command or Silence Horn command from that workstation affects all the
workstations in both CAGs. This configuration enables one workstation to control many others.
Although a workstation can be a member of no more than two CAGs, there is no limit to the
number of Common Alarm Group names in an I/A Series system.
Settings in the Common Alarm Group file (commgrp.cfg) direct workstation alarm recovery
backup and the process display call-up.
To run CAGinit
1. Type:
cd /usr/fox/alarmsx (on a UNIX workstation)
cd \usr\fox\alarms (on a Windows NT workstation)
2. Type:
CAGinit (on a UNIX workstation)
sh CAGinit.ksh (on a Windows NT workstation)
The commgrp.cfg file then contains a list of all workstations throughout the system and the infor-
mation for these capabilities:
♦ CAG-related common horn silence
♦ CAG-related common horn mute
♦ CAG-related alarm clear (using the CLR ALM button)
♦ Workstation alarm recovery
♦ Process display call-up
NOTE
A workstation need not be a member of a Common Alarm Group to configure WP
alarm backup or process display call-up.
The following information may be optionally configured for every workstation listed in the con-
figuration file:
♦ The name of the CAG with which the workstation is associated.
♦ The name of a second CAG with which the workstation is associated.
♦ The letterbug of a backup workstation from which to recover the current alarm list
and annunciator panel LED settings, should a reboot be required. (Reboot clears
alarm information.)
♦ The names of DMs to which the following alarm displays may be redirected when
accessed from an alarm display: Block Detail Display, top priority alarm display, and
user display.
Each workstation’s alarm alert database initially contains default attributes. These attribute in the
init.user file that affects Common Alarm Groups is:
Attribute Default
Clear alarm button option Clear the alarm from the database only on the workstation
(CLR_OPT) initiating the action. The associated annunciator light or any
control block is unaffected.
Display Button
Block Detail Display for the selected alarm Block Detail
User display or Block Detail Display for the highest priority alarm Top Priority
in the alarm alert database (based on the sort order)
User display for the selected alarm User Disp
Process displays (Block Detail Displays, top priority displays, and user displays) accessed from
alarm displays are sent to a display manager (DM) with the same name running on the same
server as the Alarm Manager (AM). If no DM with the same name is found, any DM running on
the same server is used. Otherwise, an error message occurs.
Each AM on the workstation directs displays and commands according to the display configura-
tion specified in the Common Alarm Group file (commgrp.cfg file). You can override this default
configuration for any instance of AM by issuing commands that alter the process display call-up
variables. You can configure buttons on alarm displays to dynamically alter process display call-up.
An AM displaying on a remote station directs its displays and commands to the display manager
displaying on the same remote station unless otherwise overridden.
36
2. Alarm Subsystem B0193RV – Rev E
♦ The display file must reside on the workstation or host AP of the workstation to
which it is being directed.
♦ The configuration information in the commgrp.cfg file for a workstation applies to all
display managers that are activated on that workstation, that is, the same process dis-
play call-up applies to all alarm displays for all Alarm Managers on the workstation
independent of the DM menu bar from which it was called.
♦ The configuration file may contain DM names instead of WP letterbugs for the pro-
cess display call-up assignments. The DMs may be configured on the local
workstation or a remote workstation.
♦ Each DM and AM configured on a workstation has an individual set of WP
read/write environment variables. You can configure these variables in the com-
mgrp.cfg file (“Configuring Common Alarm Groups” on page 35) or by assigning
values at runtime by means of pref commands (refer to setenv built-in commands in
the Alarm Manager on-line help).
♦ An AM displaying remotely will not use these variables. It will direct the display to a
DM also displaying to that screen.
1. The Alarm Manager checks for a display manager with the same name on the same
X window server and Head 0. If the DM is running and displaying, the requested pro-
cess display appears there.
2. If a DM is not found, the Alarm Manager checks for a DM with the same name run-
ning and displaying on the same X window server and Head 1. If the DM is running
and displaying, the requested process display appears there.
3. If a DM is not found, the Alarm Manager looks for a floating DM with the same
name running on the same X window server. If the DM is running and displaying, the
requested process display appears there.
4. If a DM is not found, the Alarm Manager finds any DM running on the same
X window server and displays to that DM.
NOTE
If no DM is found, an error message appears.
NOTE
If you have an existing customized init.user file, compare the init.user file against
the init.user.rel file to determine whether there are differences. Decide whether to
copy the init.user.rel file to the init.user file or to append/enter enhancements to the
init.user file.
38
2. Alarm Subsystem B0193RV – Rev E
The changes take effect when the revised start-up file is read.
In the above example, if the workstation is part of a CAG, perform the same edits at the CAG
members.
NOTE
Maintain a consistent configuration scheme for alarming options across all the
workstations in your I/A Series system. Each workstation should have the same val-
ues for the CLR_OPT, RTN_DROP, SORT_CFG, HORN_OPT, and
RESOUND options.
Each workstation’s alarm alert database initially contains default attributes. These attributes affect
information in alarm displays and the horn configuration.
NOTE
To indicate the alarm text string and the current number of alarms, you can connect
the ALMTXT and ALMCNT workstation globals to display objects. Refer to the
display engineering documentation for information.
Configurable Items
You can configure the following items in the alarm alert database.
Format
MAX_CAD=<value>
For example, MAX_CAD=1000 sets the number of alarm entries at 1000.
To accommodate new alarms received after the list is full, alarms are dropped based on the config-
ured sort option (SORT_CFG) as follows:
First Lowest ordered unacknowledged return-to-normal entry
Next Lowest ordered acknowledged alarm
Last Lowest ordered alarm, if and only if the new alarm would be placed
higher in the list, in accordance with the configured sort option.
The drop order depends on the sort option. For example, if the sort option is by time only
(SORT_CFG=4), the oldest alarm is dropped without regard to acknowledge state or return-to-
normal state.
Dropping an alarm to accommodate a new alarm results in Annunciator/FoxPanels light process-
ing as usual and the sounding of a horn, if appropriate/configured. The block is not acknowl-
edged; the block’s UNACK parameter remains unchanged in the control station.
NOTE
For FoxBatch, active suspended alarms remain in the database at the risk of losing
higher priority alarms (when CONF_RTN=Y).
40
2. Alarm Subsystem B0193RV – Rev E
Format
SORT_CFG=<value>
<value> Description
0 (default) Sort first by in-alarm or return-to-normal, then acknowledge
state, then priority, and last by time.
1 Sort first by acknowledge state, then priority, and then time.
2 Sort first by acknowledge state and then time.
3 Sort first by priority and then time.
4 Sort by time.
Format
MAX_ACTIONS=<value>
<value> Description
2000 The maximum number of block assignments that can be assigned
to the Annunciator keys is 10,000. The range is 2000 to 10,000.
The default number is 2000.
Format
AM_DISP=<value>
<value> Description
CAD (default) Current Alarm Display
MRA Most Recent Alarms Display
NEWALM New Alarms Display
ACKED Acknowledged Alarms Display
UNACK Unacknowledged Returned-to-Normal Alarms Display
AHD Alarm History Display
OPR Operations Display
Return-to-Normal Action
The value of the RTN_DROP option in the init.user.rel file sets the return-to-normal action.
Format
RTN_DROP=<value>
<value> Description
0 (default) The returned-to-normal alarm is kept in the Alarm Alert internal
database. Based on the sort configuration (SORT_CFG), the alarm entry
may also be repositioned in the database. When the block is
acknowledged, this alarm entry is removed from the database. In
addition, the Annunciator light associated with a block that has returned
to normal continues to flash until the block has been acknowledged.
1 The returned-to-normal alarm is removed from the Alarm Alert internal
database regardless of the block acknowledgment state. As a result of this
configuration option, the Unacknowledged Return-to-Normal Alarms
Summary display is always empty. In addition, the Annunciator light
blinking or solid) associated with a block that has returned to normal is
extinguished regardless of the block acknowledgment state.
If an Annunciator key has more than one block assignment currently in alarm, the Annunciator
light is affected by all the block conditions associated with that key.
NOTE
When the Alarm Alert subsystem receives a DISABL message (for example, when a
compound is turned off), all alarms in its internal database for the designated com-
pound:block are removed. The system no longer expects return-to-normal messages
for those alarms.
Refer to Process Operations And Displays for additional information regarding disabled blocks with
outstanding alarms and return-to-normal conditions.
Format
CLR_OPT=<value>
<value> Description
0 (default) The selected alarm entry is deleted from the Alarm Alert internal
database only on the workstation from which the selection is made.
The associated Annunciator LED (if configured) or any block
parameter is unaffected.
1 The selected alarm entry is deleted from the Alarm Alert internal
database on all workstations defined in the same Common Alarm
Group(s) as the workstation from which the selection is made.
42
2. Alarm Subsystem B0193RV – Rev E
<value> Description
2 The selected alarm entry is deleted from all the Alarm Alert internal
database on all workstations defined in the same Common Alarm
Group(s) as the workstations from which the selection is made. In
addition, the block is marked as acknowledged, and the alarm
condition of the Annunciator LED associated with the block (if
configured) is set to returned-to-normal.
A Clear Alarm button configured with CLR_OPT=1 or CLR_OPT=2 clears (on CAD) or grays
(on MRA and summary displays) the selected alarm from the alarm displays on all workstations in
the same Common Alarm Group as the requesting workstation.
Format
ALMCLR=<value>
ACKCLR=<value>
RTNCLR=<value>
Alarm Priority
Color Option Color Values Description
ALMCLR= 00,07,07,07,07,07, Unacknowledged alarm priority colors – the
01,05,03,06,08 color associated with each unacknowledged
alarm priority displayed in alarm displays. The
priority number and the background color for
the Unacknowledged indicator are shown in
default colors. The default foreground color for
each of the alarm priority is white (07). The
default background colors are:
Priority 1 – Red (01)
Priority 2 – Magenta (05)
Priority 3 – Brown (03)
Priority 4 – Cyan (06)
Priority 5 – Dark Gray (08)
Alarm Priority
Color Option Color Values Description
ACKCLR= 00,01,05,03,06,08, Acknowledged alarm priority colors - the color
15,15,15,15,15 associated with each acknowledged alarm
priority displayed in alarm displays. The priority
number is shown in the default color. The
default background color for each of the prior
ties is gray (15). The default foreground colors
are:
Priority 1 - Red (01)
Priority 2 - Magenta (05)
Priority 3 - Brown (03)
Priority 4 - Cyan (06)
Priority 5 - Gray (08)
RTNCLR= 00,07,07,07,07,07, Return-to-normal priority colors - the color
01,05,03,06,08 associated with each unacknowledged return-to-
normal alarm priority displayed in alarm
displays. The priority number and background
for return-to-normal and the unacknowledged
indicators are shown in default colors. The
default foreground color for each of the alarm
priorities is white (07). The default background
colors are:
Priority 1 – Red (01)
Priority 2 – Magenta (05)
Priority 3 – Brown (03)
Priority 4 – Cyan (06)
Priority 5 – Dark Gray (08)
On UNIX systems, besides setting the colors, you can make them blink.
44
2. Alarm Subsystem B0193RV – Rev E
5. Set the desired text background and foreground color for each process alarm when
unacknowledged (ALMCLR), when acknowledged (ACKCLR), when returned-to-
normal (RTNALM).
6. Reboot the workstation to make the changes take effect.
Resound Horn
The value of the RESOUND option in the init.user.rel file sets the resound horn action when the
mute condition is cleared.
Format
RESOUND=<value>
<value> Description
0 (default) Horns do not resound when the mute condition is cleared
(Mute command from Operations display).
1 Horns resound when the mute condition is cleared (if alarms
arrived during the mute period, horns will sound).
Horn Silence
The value of the HRN_OPT option in the init.user.rel file sets the horn silencing action for man-
ual or automatic horn silencing. This applies to the local workstation horn or the horns through-
out the Common Alarm Group.
Format
HRN_OPT=<value>
<value> Description
0 (default) Horn is silenced manually only via the ACK button on
Annunciator or alphanumeric keyboard, any Annunciator
panel key, and accessing the Alarm field in a display manager
I/A Series environment.
1 Horn is silenced automatically when all blocks are acknowl-
edged regardless of priority. Manual silence is also allowed.
2 Horn is silenced automatically when all blocks are returned
to normal. Manual silence is also allowed.
3 Horn is silenced automatically when all blocks are acknowl
edged regardless of priority or all blocks are returned to
normal. Manual silence is also allowed.
NOTE
The HRN_OPT option applies only to alarms of compound:blocks that have an
Annunciator assignment.
Format
ALMPRI=<value>
<value> Description
0 No saves are performed.
1 Priority 1 alarms are saved.
46
2. Alarm Subsystem B0193RV – Rev E
<value> Description
2 (default) Priority 1 and 2 alarms are saved.
3 Priority 1, 2, and 3 alarms are saved.
4 Priority 1, 2, 3, and 4 alarms are saved.
5 Priority 1, 2, 3, 4, and 5 alarms are saved.
The value of the ALMRTNS option defines the type(s) of alarm messages saved for alarm text
string updates and the alarm count (ALMCNT) variable.
Format
ALMRTNS=<value>
<value> Description
0 (default) The ALMTXT string and ALMCNT variable are updated for
in-alarm messages only.
1 The ALMTXT string and ALMCNT variable are updated for
both in-alarm and return-to-normal messages.
For non-analog alarms, such as STATE, an asterisk (*) appears in place of the parameter.
Format
LIA_OLDEST=<value>
<value> Description
Y Selects the oldest highest priority alarm.
N (default) Selects the most recent highest priority alarm.
NOTE
The top priority display is a Block Detail Display or user-defined display that per-
tains to the highest priority alarm, according to the sort configuration of the alarm
alert database.
Considerations
♦ The LIA_OLDEST option invokes displays for alarm entries in the workstation’s
alarm alert database that are unacknowledged and in-alarm based on oldest-to-newest
priority. When all the in-alarm unacknowledged alarms have been traversed, pressing
the Top Priority button displays the oldest, highest priority, unacknowledged, return-
to-normal alarm entry in the database. When all the unacknowledged return-to-nor-
mal alarms have been acknowledged, the oldest, highest priority acknowledged alarm
entry is used to call up a graphic.
♦ If the alarm is not acknowledged at the time the Top Priority button graphic is pre-
sented, a subsequent selection of Top Priority recalls the same display.
♦ If no user graphic is associated with the alarm, the Block Detail Display is called up.
♦ The standard CAD display continues to show the newest, highest priority alarm at the
top with the oldest, lowest priority alarm at the bottom (which is the default for the
SORT_CFG option).
Format
CONF_RTN=<value>
<value> Description
Y The Alarm Manager monitors a suspended FoxBatch block’s
SUSPND parameter and prevents the clearing of the CONF
message. When an unsuspend command is issued (or a timeout
occurs), the CONF message is removed.
N (default) The Alarm Manager does not monitor FoxBatch block SUSPND
parameters and allows an operator to clear a CONF message.
48
2. Alarm Subsystem B0193RV – Rev E
Format
CAD_UPDATES=<value>
<value> Description
Y Turns on real-time parameter updates to the CAD.
N (default) Turns off real-time parameter updates to the CAD.
For information about Object Manager connections, refer to Workstation Alarm Management.
ALMCNT Variable
The Alarm Manager monitors the ALMCNT variable. When the ALMCNT variable changes:
♦ The Alarm Manager executes a user-defined action
♦ The New Alarms button on alarm displays indicates that new alarms have arrived in
the internal alarm alert database since the display has been called up. On a UNIX
workstation, the button illuminates and flashes. On an Windows NT workstation, the
button illuminates.
NOTE
Proper use of alarm recovery requires that the control stations are consistent in
Alarm Manager configuration options and in Annunciator/FoxPanels configurator
options. This way, each workstation maintains the same active alarm alert database
information. Refer to “Creating a Common Alarm Group File” on page 50.
The backup workstation must also be configured with the same Annunciator keyboard
(or FoxPanels window) assignment as the requesting workstation.
When a workstation requires rebooting, the alarm alert database is transferred over the network
from the backup workstation. Alarm recovery to a 50 Series or 70 Series workstation results in
Alarm Manager notification of alarm recovery with a message dialog box. All displays are auto-
matically refreshed with the recovered alarm information, and Annunciator LEDs (or FoxPanels
buttons) are reset.
NOTE
If a 50 Series or 70 Series station recovers alarm alert database information from a
non-50 Series or non-70 Series station (such as a WP20/30), the alarm timestamp
does not include the number of milliseconds.
To create, configure, and install the file containing the CAG information
1. On a UNIX-based workstation, in the VT100 mode, run the
/usr/fox/alarms/CAGinit script.
-or-
On a Windows NT-based workstation, from the \usr\fox\alarms directory, type:
sh CAGinit.ksh
This creates the /usr/fox/alarms/commgrp.cfg file, which contains a list of config-
urable fields and a list of all the workstation letterbugs on the I/A Series network
to which the alarm features apply (all non-WP10 workstations). Each workstation let-
terbug entry defaults to no assignment, for example, "--------------".
2. Using a text editor, open the /usr/fox/alarms/commgrp.cfg file and type the configura-
tion information for each workstation.
You can use display manager names in place of workstation letterbugs for display
coordination. This is an example of a previously configured CAG configuration file.
# (CAD Coordination)
# WP CAG Backup BLK TOP USER CAG
# LBUG NAME1 LBUG DTL PRIO DISP NAME2
###### ############ ###### ###### ###### ###### ############
WP20D1 TOWER1_NORTH WP30D1 WP30D1 WP30D2 WP30R3 -------
WP30D1 TOWER1_NORTH WP20D1 ------ ------ ------ -------
.
.
50
2. Alarm Subsystem B0193RV – Rev E
NOTE
The CAG NAME1 field and CAG NAME2 field may include up to 12 characters.
3. After creating and configuring the information, install the file on all APs, 50 Series,
and 70 Series workstations hosting the member workstations throughout the network.
Copy the /usr/fox/alarms/commgrp.cfg file to each AP, PW, and 50 Series worksta-
tion.
4. Reboot each workstation.
Considerations
♦ Although a WP may be a member of up to two CAGs, the CAGinit file may contain
any number of Common Alarm Group names per system.
♦ A top priority display or user display that is directed to another WP must reside in the
AP hosting the WP to which it is directed.
♦ Maintain a consistent configuration scheme for alarming options across all the work-
stations in your I/A Series system. Each workstation should have the same values for
CLR_OPT, RTN_DROP, SORT_CFG, HRN_OPT, and RESOUND.
Configuration Files
These configuration files affect the alarm subsystem:
NOTE
In case files are shared between platforms, observe case sensitivity.
File Description/Purpose
/usr/fox/alarms/horn.cfg Configuration of horns.
Refer to the Foxpanels Configurator on-line Help.
/usr/fox/alarms/commgrp.cfg Common Alarm Group (group name,
workstation used for alarm recovery, Block Detail
Display, top priority display, and user display
call-up) created by running a script
/usr/fox/wp/data/init.user Alarm sorting options
Return-to-normal message processing
Alarm clearing options
Alarm type text colors
/usr/fox/alarms/<LNNAME>AAtab Annunciator keyboard LED control assignments
-or- -or-
/usr/fox/alarms/<CAGNAM>AAtab FoxPanels button control assignments.
Refer to the Foxpanels Configurator on-line Help.
/usr/fox/alarms/<LNNAME>AApan Annunciator key press or FoxPanels button press
actions.
Refer to the Foxpanels Configurator on-line Help.
/usr/fox/wp/data/foxboro.cdf Standard templates and schemes provided by The
Foxboro Company
/usr/fox/customer/alarms/cfg/am_def.cfg Default AM configuration
/usr/fox/ A configured Alarm Manager configuration; also
customer/alarms/cfg/AMNAME.cfg called an install file
/usr/fox/customer/config/filename.am An AM database file that includes both display
manager and Alarm Manager information
usr/fox/customer/hi/dmcfg Lists the properties for display managers and
Alarm Managers
Keywords
Use Alarm Manager built-in commands and keywords to use alarm tasks and alarm information
in other applications.
AM built-ins are normally used to configure button actions, menu items, and new alarm actions.
Use keywords and modifiers to configure the content of each alarm type message. At runtime, the
Alarm Manager replaces keywords with text derived from alarm messages generated by the control
software.
Built-ins and keywords extend Alarm Manager functionality and facilitate a link from the Alarm
Manager to your own applications to meet your plant-specific needs. Example uses include
52
2. Alarm Subsystem B0193RV – Rev E
calling up operator instructions for a selected alarm from a user-defined alarm response manual
application, or selecting a point in alarm and automatically trending the point.
Keywords are delimited by “<“ and “>” and correspond to data in the alarm message. The set of
valid keywords varies by alarm type. At runtime, the Alarm Manager replaces the keywords with
text copied or derived from the corresponding fields in the alarm message.
List of Keywords
These are the valid Alarm Manager keywords.
Keyword Width Displayed As Description
AckState - Formatted indicator Acknowledged state
AlarmName 12 Text User-defined alarm text
AlarmNumber - Integer text Index of the alarm entry in the
display's alarm list
AlarmState - Formatted indicator Alarm state and Priority
AlarmType 6 Text Type of alarm, for example,
HIABS
BadIO 32 Text BADIO, State, or Trip state text
Block 12 Text Block name
BlockDesc 32 Text Block description
BlockException 1 Integer text Standard block exception handler (0-5)
Case 2 Integer text Case number
Compound 12 Text Compound name
Date - Formatted string Date
DisSpc 32 Text Disable or SPC alarm text
Limit - Floating-point string Alarm limit
Operational 4 Text Operational text for MON, EXC,
IND, DEP alarms
OptionText 32 Text User-defined optional text
ParamName 7 Text Name of the Parameter in alarm
Point 2 Integer text Boolean input Parameter number
Priority 1 Integer text Alarm Priority 1 - 5
Range 4 Text Optional text
RangeAlarm 32 Text User-defined text
SPCAlarm 6 Text SPC state text
Statement 4 Integer text Statement number
Step 3 Integer text Step number
Subroutine 3 Integer text Subroutine number
SystemTime 14 Text System-formatted time/date
Tenths 1 Integer text The tenths of a second part of the
time-stamp
Time - Formatted string Time
Keywords 53
B0193RV – Rev E 2. Alarm Subsystem
Keyword Modifiers
Keyword modifiers are delimited by [ and ]. Modifiers vary by keyword.
Keyword Field Description
Text A modifier of the form [x-y] specifies a range of characters
(from x to y) to display from the alarm message text. If no
modifier is specified, the entire string displays.
Time and Date A modifier configures the time/date format. For example,
<time[%H:%M]> specifies the hour and minute separated by a
colon (:). Most common American and international formats
are selectable. Access to this field is provided for special-purpose
formats or local overrides of the default for the display.
Keyword Examples
This Specifier Displays this Text
<Time[%H-%M-%S %p]> 05-22-56 A.M.
<BlockDesc[1-32]> Stand 4 Tension Control
<Value> <Units[1-6]> 1545 Deg. C
<BlockDesc[1-17]>-<AlarmName1-12> Laying Head Entry-Cobble
<Compound[1-12]>:<Block[1-6]> Feedwater:FIC101
54
2. Alarm Subsystem B0193RV – Rev E
NOTE
Commands without a [disp] parameter are performed on the initial alarm display or
the active display set with the setdisp command.
Command Descriptions
= wp-var value Sets the WP variable to that value
== value1 value2 command Compares value 1 with value 2. If equal, the specified
command is run.
!= value1 value2 command Compares value 1 with value 2. If not equal, the specified
command is run.
ackalm Acknowledges the blocks associated with the user-selected
alarms.
ackcmp Acknowledges the compounds associated with the user
selected alarms.
ackpage [disp] Acknowledges the alarms present in the alarm display;
defaults to initial alarm display if disp is not specified.
ackpage_cmp [disp] Acknowledges the compounds present in the alarm window;
defaults to initial alarm display if disp is not specified.
almdisp disp [-match Initiates the specified alarm display, if not already active.
filename][-historian If already active, but obscured, this command raises the dis-
histname][-refresh]
play to the front of the screen.
[stop_match]
If already active but iconified, the command opens it and dis-
plays it on the front of the screen.
If an alarm match is specified, then it is applied to the display.
If filename has no path, the default path/usr/fox/cus-
tomer/alarms/amspec is searched for the file.
The historian (histname) can be specified if disp specifies
AHD.
Refresh is used by AM to refresh the display, if active.
Stop match turns off the matching associated with the display.
blk_dtl Calls up the Block Detail Display of the selected alarm on the
DM identified by the display direction (process display call-
up) configuration. If more than one alarm is selected, the
command is applied to the first selected alarm.
Command Descriptions
chngenv [env_name] Changes to the environment identified by the env_name
path.
If env_name is not an absolute path, $ENV_DIR is
prepended to env_name to form the complete path to the
environment file.
If env_name is not specified, an environment selection
dialog box is popped up, with $ENV_DIR as the directory
root, allowing the user to select an environment name.
If env_name specifies an absolute directory path, an
environment selection dialog box is popped up, with the spec-
ified directory as the root, allowing the user to select an envi-
ronment name.
If a password is configured for the environment, the user must
supply it. If verified, then the new environment is entered,
otherwise the environment is not entered.
clear_alm Clears user selected alarms from the Alarm Alert alarm
database on the active display.
clear_page [disp] Clears all alarms visible in the alarm window of the specified
display.
If disp is not specified, it defaults to the initial alarm display, if
active.
deselect Deselects all alarms in the display.
detail_alm Invokes the Alarm Detail window for the selected alarm.
If more than one alarm is selected, only the first in the list is
shown.
disable function Disables the Alarm Manager from performing the specified
function. The function parameter may be:
ack alarm acknowledgment
clear alarm clearing
horns silencing/muting/unmuting horns
all all functions
dismiss Dismisses the associated display. All OM connections are
closed and the alarm display is removed from the screen.
enable function Enables the Alarm Manager to perform the specified
function. The function parameter may be:
ack alarm acknowledgment
clear alarm clearing
horns silencing/muting/unmuting horns
all all functions
exit[exit_num origina- Terminates the AM. When exit_num and originator are speci-
tor] fied, the AM exits with the specified exit code.
Originator is a text string used to specify the originator of the
exit request. If you choose to include exit_num and
originator, you must specify both parameters.
56
2. Alarm Subsystem B0193RV – Rev E
Command Descriptions
find Invokes the Find Alarms dialog box, allowing you to locate
specific alarms on the associated alarm display.
getenv env-var wp-var Sets the WP variable wp-var to the value of the environment
variable env-var.
hide MenuBar | Title | Removes component from active display. Use the show com-
ButtonArea | StatusArea mand to restore the component to the active display.
hist_file [name] Displays the specified history archive file.
This command applies only to the active AHD.
historian [name] If name is specified, the named Historian is used as the source
of historized alarms for the associated AHD display.
If name is not specified, a dialog box is popped up, allowing
you to select a Historian name.
If you select an Historian name and press OK, the named
Historian is used as the source of historized alarms for the
associated AHD display.
If you press Cancel, the Historian selection is canceled.
match [filename] If filename is specified, the alarm match criteria in the file is
applied to the associated alarm display.
If filename is not specified, the alarm dialog window is
popped up allowing you to configure/apply/clear alarm
matching for the associated alarm display.
If filename has no path, the default path /usr/fox/cus-
tomer/alarms/amspec is searched.
minimize [disp] Iconifies (minimizes) the associated alarm display.
The optional disp parameter minimizes the active or default
display.
mute_all_horns Disables the sounding of alarm horns at this WP/AW and
throughout the Common Alarm Group(s), if configured.
mute_horns Disables the sounding of alarm horns at this workstation.
ojinit Re-reads OJLOG to get updated logging directives.
page [+/-][num/last] If no arguments are provided, this command pops up the "Go
To Page" dialog box which allows you to page through the
alarm list.
If num is specified, page num is displayed the alarm window.
The syntax +num is used to page ahead num pages, and -num
is used to page back num pages.
The last argument means to go to the last page. The pages are
1-based.
page_setup (Windows NT only) Invokes a Page Setup dialog box,
allowing you to set margins and add header and footer infor-
mation to the printed pages.
pause Pauses the alarm updates to the associated MRA or CAD dis-
play.
Command Descriptions
print (Solaris systems) Prints alarm entries or a saved file to a system
printer.
A dialog box allows you to choose: whether to print a file or
alarm entries, the name of the system printer, and a print
script.
(Windows NT systems) Invokes the standard Windows Print
dialog box, allowing you to select the printer and choose vari-
ous print options.
print_preview (Windows NT only) Shows the report as it will appear when
printed.
print_setup (Windows NT only) Invokes the standard Windows Print
Setup dialog box, allowing you to select a printer and choose
options such as the number of copies and the paper
orientation.
protect type locks Protects the specified access key locks.
This command has the same syntax and meaning as the Dis-
play Manager protect command.
quitam on | off Enables or disables the user from exiting the Alarm Manager.
refresh Refreshes an alarm display with the latest set of alarms.
This is useful to get the latest "snapshot" of the alarm database
on summary displays or the MRA display.
run prog [args...] Runs the specified program with the specified arguments.
save_to_file [filename] If filename is specified, the contents of the associated alarm
[-format CSV] window are saved to the file.
If filename is not specified, then a file dialog window is
popped up, allowing you to specify a file to which the alarms
are saved.
After the filename is chosen, the alarms are saved to the file.
The -format CSV option specifies that the alarms should be
written in comma-separated value (CSV) format.
select Selects all alarms in the display.
send_to_dm [-dm dmname] Sends the specified DM built-in command to the DM
dm-builtin-command specified by dmname.
If a DM name is not specified, the DM defaults to the name
specified by the CADUS variable.
If the dmcmd contains a variable (var) that is to be evaluated
by the DM, express the variable as $$var to avoid evaluation
by AM.
setacl number <+-> Changes the specified access key locks.
This command has the same syntax and meaning as the dis-
play manager setacl command.
setdisp disp Identifies the default alarm display to receive commands from
an external source, such as a pref command.
setenv var value Sets AM’s environment variable (var) to the value (value).
58
2. Alarm Subsystem B0193RV – Rev E
Command Descriptions
setenv_default var Resets the AM’s environment variable (var)to its configured
value.
show MenuBar | Title | Shows (makes visible) the specified display component.
ButtonArea |StatusArea This is the opposite of the hide command.
silence_horns Silences horns at this WP and throughout CAG(s), if
configured.
stop_match Clears the current match from the display.
top_prio Calls up user graphic or Block Detail Display on the DM
identified by display direction (process display call-up)
configuration.
unmute_all_horns Enables the sounding of alarm horns at this WP/AW and
throughout the Common Alarm Group(s), if configured.
unmute_horns Enables the sounding of alarm horns at this workstation.
unpause Unpauses the alarm updates to the associated MRA or CAD
display.
unprotect type locks Unprotects the specified access key locks.
This command has the same syntax and meaning as the dis-
play manager unprotect command.
user_disp Calls up the user graphic on DM identified by display
direction (process display call-up) configuration.
view_all on|off Enters or exits the View All alarms mode (all entries in alarm
database) available on summary displays.
Time/Date Modifiers
You can also use these time/date modifiers:
Format String Meaning
%a Abbreviated weekday name
%A Full weekday name
%b Abbreviated month name
%B Full month name
%c Date and time representation appropriate for locale
%d Day of month as decimal number (01 - 31)
%H Hour in 24-hour format (00 - 23)
%I Hour in 12-hour format (01 - 12)
%j Day of year as decimal number (001 - 366)
%m Month as decimal number (01 - 12)
%M Minute as decimal number (00 - 59)
%p Current locale’s A.M./P.M. indicator for 12-hour clock
%S Second as decimal number (00 - 59)
60
2. Alarm Subsystem B0193RV – Rev E
62
3. Alarm Manager Displays
This chapter describes Alarm Manager displays and how you work with them.
The Alarm Manager’s multiple windows provide alarm displays, which in turn provide access to
process displays in a display manager window. By default, there are seven alarm displays, but you
can configure your site to use only the displays that you need.
The alarm displays include:
♦ Current Alarm Display (CAD)
♦ Most Recent Alarm Display (MRA)
♦ Alarm History Display (AHD)
♦ Summary displays:
♦ New Alarms Display (NEWALM)
♦ Unacknowledged Alarms Display (UNACK)
♦ Acknowledged Alarms Display (ACKED)
In addition, an Operations display provides access to horn silencing, horn muting/unmuting, and
to other user environments.
Use alarm displays to assess the criticality of process alarm(s) before acknowledging and resolving
alarm condition(s).
Using the Alarm/Display Manager Configurator, you can configure many aspects, such as appear-
ance, of these displays.
63
B0193RV – Rev E 3. Alarm Manager Displays
Menu Bar
New
Alarms
Dynamic Indicator
Time
and Date Scroll
Bar
Alarm
Area
(Alarm
Displays
only)
Button Area
Status Area
Alarm Entries
Within alarm displays, alarm entries provide information such as the time/date of the alarm,
source of the alarm, the process alarm type, the alarm priority, the return-to-normal state, and the
alarm acknowledge state.
All the alarm displays use the same sort order (“Configurable Options” on page 13), but you can
customize each alarm display’s properties “Items that can be Configured” on page 123) such as
displaying alarms from bottom to top, to affect the display.
The default sort order is: first by in-alarm or return-to-normal state (R), then by acknowledgment
state (A), then by priority (P), and last by time (T). The sort order is configured by an option
entry the init.user file. Refer to “Alarm Entries” on page 80 for information about default color
codes and indicators for the alarm state and alarm status fields.
64
3. Alarm Manager Displays B0193RV – Rev E
NOTE
Clicking the New Alarms button does not acknowledge the alarm.
The New Alarms button is different from the Process (or Alarm) button. The Process button
represents every alarm in the entire alarm alert database. Unlike the Process button, the
New Alarms button does not silence a horn.
The action of the New Alarms button is controlled by configurable values of the ALMPRI and
ALMRTN options in the init.user file.
65
B0193RV – Rev E 3. Alarm Manager Displays
The Clear Alarms and Clear Page buttons clear the alarms from the alarm alert database regardless
of state.
The size of the alarm alert database is indicated in the display’s status area as “Alarm # of #”, which
indicates the sequential number of the alarm entry at the top of the current page with respect to
the total number of alarms. Use the Go To Page command from the View menu or the scroll bar
to move through the pages.
66
3. Alarm Manager Displays B0193RV – Rev E
By default, new alarm entries originate in the upper left of the display and add to the display each
update period overwriting the oldest alarm entry. An alarm remains on the screen in its original
location until it is overwritten by a newer alarm.
By default, the most recent (newest) alarm entry on the display is bounded by a box and has a
striped background (diagonal lines) to distinguish it from other alarms on the screen. In the case
of a point re-alarming, if the alarm returns to normal and then goes back into alarm, the current
alarm entry, if still visible, is rewritten (by default) with the new alarm information and is consid-
ered a new alarm entry.
Alarms that are both acknowledged and returned-to-normal result in the alarm entries being
“grayed”. Additionally, the operator can mark alarms as acknowledged with the Ack Alarm, Ack
Compound, and Ack Page buttons or can clear alarms with the Clear Alarm and Clear Page but-
tons.
Refreshing the display removes alarm entries marked cleared or acknowledged/returned-to-normal
from the alarm display. The alarm alert database is reread and the current information is dis-
played.
67
B0193RV – Rev E 3. Alarm Manager Displays
As changes occur in a control station, the AM software connections to the control database imme-
diately update the alarm state, alarm acknowledgment status, and alarmed analog measurement
and output values on the screen. Digital, state, trip, and sequence alarms are not updated.
Summary Displays
Summary displays provide a stable environment from which to perform analysis and to take
action (for example, acknowledging or clearing alarms). Alarm entries dynamically reflect up-to-
date status and value information.
The three multi-page summary displays provide snapshots of the alarm alert database in the
default order (newest to oldest) with new alarm entries originating in the upper left of the display.
Display Shows
New Alarms All active, unacknowledged alarms. Entries in this display are not removed
Display or added until the alarm alert database is reread by a manual refresh;
(NEWALM) however, values and statuses are dynamically updated via direct connections
to the control software in the control stations.
Unacknowledged All unacknowledged alarms that have returned to normal. Entries in this
Alarms Display display are not removed or added until the alarm alert database is reread
(UNACK) with a manual refresh; however, values and statuses are dynamically updated
by direct connections to the control software in the control stations.
Acknowledged All active acknowledged alarms. Entries in this display are not removed or
Alarms Display added until the alarm alert database is reread with a manual refresh;
(ACKED) however, values and statuses are dynamically updated by direct connections
to the software in the control stations.
Entry order depends on the alarm entry list order selected for the AM properties (via the
Alarm/Display Manager Configurator) and the sort order configured for the alarm alert database.
68
3. Alarm Manager Displays B0193RV – Rev E
The number of entries and the position of those entries on the display do not change. Following
the initial display call-up, no new entries are added to or removed from the display. The AM soft-
ware connections to the control database provide immediate update to the alarmed analog mea-
surement and output values on the screen as their values change in the control station. Digital,
state, trip, and sequence alarms are not updated. Additionally, the alarm priority and the block
alarm status information, such as UNACK state, are immediately updated.
When a returned-to-normal alarm is acknowledged by clicking Ack Alarm, Ack Compound, or
Ack Page button or when an alarm is cleared by clicking the Clear Alarm or Clear Page button,
the entry is “grayed” until the display is manually refreshed.
69
B0193RV – Rev E 3. Alarm Manager Displays
Click here
to access
the list of
Historians
Use the Alarm History Display (AHD) to select the Historian from which to retrieve alarm mes-
sages. The Historian name appears in the display’s status area. The default Historian is the Histo-
rian associated with the workstation’s logical host. Click the Historian button to select a remote
Historian on the system.
Use the display’s scroll bar to move through the alarm entry list.
NOTE
Although not recommended, you can acknowledge alarm entries from the AHD if a
customized button has been configured. This, however, is not efficient due to
increased system loading.
Operations Display
Use the Operations display to operate horns and access another environment. Refer to “Environ-
ments” on page 71.
70
3. Alarm Manager Displays B0193RV – Rev E
Window System Menu Display Title Application Title Bar New Alarm Status
Menu Title
Dynamic Time
and Date
Button Area
Environments
You can configure an Alarm Manager to start up in a specified I/A Series environment. By default,
the initial environment is the Init_Env (Initial Environment). The Operations display provides
access to a list of configured I/A Series environments that can be selected to provide additional
security or less security, depending on the current user.
To access the alarm display associated with the Process or Alarm button
Perform one of these actions:
♦ Click the Process button (FoxView) Alarm button (Display Manager).
♦ (UNIX only) With the cursor positioned on the screen background, press the right
mouse button. The workspace pop-up menu appears. From the Program menu,
choose I/A Series Alarm Manager.
♦ Initiate the Alarm Manager (\usr\fox\wp\bin\am.exe) from a command line.
By default, the Current Alarm Display window appears. The number of Alarm Managers you are
allowed to start up depends on licensing and the number of active Alarm Managers currently run-
ning.
NOTE
You can change the initial alarm display from the CAD to another alarm display by
changing the value of the AM_DISP option in the init.user file.
71
B0193RV – Rev E 3. Alarm Manager Displays
NOTE
Bootable AMs are not quittable. If an operator tries to exit a non-quittable AM, a
message dialog box indicates that the AM is not quittable.
NOTE
Solaris only. In Windows Off mode, the Alarm Manager does not terminate when
you dismiss the display.
♦ From the last open Alarm Manager display window, choose Quit from the Control
menu. From the subsequent dialog box, choose OK to confirm the exit.
TIP
You can also access displays from pop-up menus.
72
3. Alarm Manager Displays B0193RV – Rev E
Changing Displays
Although certain Alarm Manager displays may be on a screen, depending on your configuration,
you can call up other displays. In addition, you can dismiss a display and iconify/minimize a dis-
play.
Acknowledging Alarms
From alarm displays, you can click buttons to acknowledge alarms. You can acknowledge:
♦ One or more alarms selected manually
♦ Particular alarms using the Find Alarms command from the Edit menu
♦ The entire page of alarms
♦ All alarms related to blocks in the same compound
Access process displays by clicking the Top Priority, Block Detail, or User Display button. Analyze
alarm information on the resulting displays to respond to the alarm condition.
NOTE
A Find operation has no bearing on determining the highest priority alarm.
If the sort order is by time, the top priority display is the display associated with the most recent
alarm.
The value of the init.user file’s LIA_OLDEST option also affects the operation of the Top Priority
button.
Attribute Default
Operation of the Top Priority button (LIA_OLDEST) Most recent highest priority alarm
Use To
Match Display only alarms that meet the match/filter criteria
Find Highlight the alarms that meet the match/filter criteria. The same
alarms appear on the display, but the found alarms are selected.
NOTE
You do not have to re-invoke a match to a dynamic alarm display (CAD, MRA) to
view newly added alarm entries.
Use any of these match or filter specifications to limit the display of alarms:
♦ Match specifications
♦ Blocks (letterbugs, compounds, blocks)
♦ Time (start time and end time)
♦ Alarm types
♦ Alarm state (in-alarm/returned-to-normal, acknowledged/unacknowledged,
alarm priority)
♦ Filter specifications
♦ Blocks (letterbugs, compounds, blocks)
♦ Time (start time and end time)
♦ Alarm types
♦ Alarm state (in-alarm/returned-to-normal, acknowledged/unacknowledged,
alarm priority)
74
3. Alarm Manager Displays B0193RV – Rev E
NOTE
Alarm State fields are available only on the CAD, MRA, and AHD (no Ack state).
Summary displays no not use the data in the Alarm State fields located in a Find
dialog box or Match dialog box.
After applying a match/filter, the alarm display shows only those alarms that meet the match crite-
ria and pass the filter criteria. The status area, for safety reasons, indicates that there is an alarm
match specification active for the display. Use the match capability to focus on a particular group
of alarms or to filter out nuisance alarms.
76
3. Alarm Manager Displays B0193RV – Rev E
TIP
A handy method of invoking a match specification is by configuring the match
specification file (.ams) to a button or menu item.
78
3. Alarm Manager Displays B0193RV – Rev E
NOTE
You cannot save/print this information from the CAD. Instead, use a summary dis-
play.
If a match specification had been applied to the display, that information is also saved or printed.
By default, the file is saved to the /usr/fox/customer/alarms/reports directory. On UNIX-based
systems, you can obtain different report formats by applying print scripts. On Windows NT sys-
tems, use the page setup feature to choose items that will appear in the printed pages’ header and
footer positions.
NOTE
Depending on the alarm type, other fields will be present (for example, units, alarm
limit, OPER, STEP/STM/SUB/SBX, or CASENO).
Alarm Entries
Alarm entries appear with the following default colors and indicators for the alarm state and alarm
status fields:
Color
Alarm Acknowledge Alarm Foreground/ Alarm Acknowledgment
State State Priority Background Indication Indication
In-alarm UNACK 1 White/Red 1 U
In-alarm UNACK 2 White/Magenta 2 U
In-alarm UNACK 3 White/Brown 3 U
In-alarm UNACK 4 White/Cyan 4 U
In-alarm UNACK 5 White/Dark gray 5 U
In-alarm ACK 1 Red/Gray 1 gray box
In-alarm ACK 2 Magenta/Gray 2 gray box
In-alarm ACK 3 Brown/Gray 3 gray box
In-alarm ACK 4 Cyan/Gray 4 gray box
In-alarm ACK 5 Dark gray/Gray 5 gray box
80
3. Alarm Manager Displays B0193RV – Rev E
Color
Alarm Acknowledge Alarm Foreground/ Alarm Acknowledgment
State State Priority Background Indication Indication
In-alarm UNACK 1 White/Red 1 U
RTN UNACK 1 White/Red R U
RTN UNACK 2 White/Magenta R U
RTN UNACK 3 White/Brown R U
RTN UNACK 4 White/Cyan R U
RTN UNACK 5 White/Dark gray R U
NOTE
There is no entry for an acknowledged return-to-normal alarm because this state
does not exist.
Pop-Up Menus
Each alarm window has its own pop-up menu. The pop-up menu associated with each of the
alarm display windows provides quick access to frequently used functions.
The pop-up menu appears within the corresponding display when you press the right mouse but-
ton. These are the default commands in the pop-up menu for each display.
MRA CAD NEWALM UNACK ACKED AHD
Refresh Refresh Refresh Refresh Refresh
Pause/Unpause Pause/
Unpause
Most Recent Most Most Recent Most Most
Alarms Recent Alarms Recent Recent
Alarms Alarms Alarms
Example
Objective: Pressing the Clear Alarm button does not clear the alarm unless the alarm is
either already acknowledged or the condition has returned-to-normal.”
This is accomplished by:
♦ Changing the acknowledge indicator to “A” (via an edit to the alarm format scheme)
♦ Replacing the existing command behind the CAD’s “Clear Alarm” button with the
following:
== <AckState> A clear_alm
== <AlarmState> R clear_alm
== <AckState> U deselect
NOTE
The Clear Alarm button could just as easily have been set up to apply this restric-
tion only to priority 1 alarms.
82
3. Alarm Manager Displays B0193RV – Rev E
Example
Objective: For a selected alarm, inhibit alarms of a particular type.
The following UNIX shell script, called do_in, was written, and an Alarm Manager command
button was set up to execute the script from a summary display.
# Inhibit Individual Alarms
CB=”$1”
TYPE=”$2”
LBUG=”$3”
# Determine which bit mask to use
case $TYPE in
HIABS)
MSK=”HMA” ;;
LOABS)
MSK=”LMA” ;;# etc., etc.
*)
MSK=”MSK=””
esac
if [ "$MSK” != “” ]
then
/usr/local/pref -$LBUG dmcmd “setb $CB:INHALM.$MSK FFFFFFFF”
fi
A new button was added was assigned this action:
run /usr/fox/alarms/do_in <Compound>.<Block> <AlarmType> $GCLBUG
This command makes the AM run the “do_in” script, passing to it the compound name, the
block name, and the alarm type fields from the selected alarm. Compound, Block, and Alarm-
Type are Alarm Manager keywords for the selected alarm’s sub-fields.
This example shows how the AM can pass portions of alarm information originally received from
the control station associated with a selected alarm to a subsequently started script or application.
Besides passing the compound and block names, the AM can also pass the block descriptor text,
date, time, priority, or any other information sent to the workstation.
More Examples
Here are some more examples of capabilities you can implement by extending the interface to the
Alarm Manager:
♦ Selecting an alarm and displaying a trend graphic of the alarmed parameter in the dis-
play manager window
♦ Selecting an alarm, and saving an operator’s comment to be recalled at a later time
♦ Showing all OUTPUT alarms in yellow, and showing all MEAS alarms in red
♦ Differentiating HIGH-HIGH alarms entries from HIGH alarm entries by setting
their background color to red for the entire expanse of the alarm entry
♦ Viewing alarms by priority on a summary display, from oldest to newest
♦ Pre-defining a set of buttons, with matching and filtering, such that clicking one of
the buttons quickly zooms in on only the alarms associated with a small subset of
alarms at your site
Menu Bar
New
Alarms
Dynamic Indicator
Time
and Date Scroll
Bar
Alarm
Area
(Alarm
Displays
only)
Button Area
Status Area
Display Title
The display title shows the current time and date, the name of the display, and the New Alarms
button.
84
3. Alarm Manager Displays B0193RV – Rev E
If a match is active and the match includes a match description, the match description text dis-
plays in the display title.
The New Alarms button illuminates to notify you that an alarm condition has occurred while an
Alarm Manager display (regardless of the display type) is active. To indicate that you are aware of
the receipt of new alarms(s), click the New Alarms button. This stops the illumination.
Summary displays are not automatically updated with new alarms. Therefore, when notified,
an operator can access an MRA or CAD display or refresh a summary display to view the new
alarm(s).
NOTE
The values of ALMPRI, ALMRTNS, and ALMCNT in the init.user file affect the
New Alarms button. By default, only Priority 1 alarms and Priority 2 alarms, and
in-alarm messages cause this button to change color.
The New Alarms button is different from the FoxView Process button. Unlike the Process button,
the New Alarms button does not silence a horn.
Menu Bar
These are the default menu bar entries:
♦ File Menu
♦ Edit Menu
♦ View Menu
♦ Display Menu
File Menu
Choose To
Save Save the contents of all the alarm entries associated with the display to a file
in normal or CVS format. Alarm information in CSV format can be
imported into spreadsheets such as Lotus or Excel or databases such as Access
for further analysis. (Not available for CAD display.)
Print Print all the alarm entries associated with the specified display or print a
previously saved file. A Print dialog box allows you to specify the file and the
desired printer. (Not available for CAD display.)
Dismiss Close the current alarm display window
Edit Menu
Choose To
Select All Select all the alarms in the current alarm window. You might do this before
performing an operation such as Acknowledge Alarms or Clear Alarms.
Deselect All Deselect all previously selected alarms.
Choose To
Find Alarms Access the Find Alarms dialog box to specify the criteria for selecting alarms
on the display. You can then perform a subsequent action, such as
acknowledging or clearing the alarms.
View Menu
Choose To
Refresh Refresh the information on the alarm display. The AM retrieves an up-to-
date snapshot of alarm information from the alarm alert database. Cleared
and acknowledged/return-to-normal alarm entries, as appropriate, are
removed from the MRA and summary displays. Refreshing the display
updates the time and date in the status area.
Match Alarms Access the Match Alarm dialog box to specify criteria for filtering alarms.
After running this command, the alarm display presents only the alarms that
match the specified criteria (for example, specific type within timeframe, or
a specific control station and compound). Use Match Alarms to filter out
nuisance alarms or analyze specific alarms. For example, you can analyze
alarm activity within a timeframe for auditing purposes or quality assurance.
When saved to a file in Comma-Separated Value (CSV) format, the infor-
mation can be imported into Lotus 1-2-3 to be presented in graph or chart.
Enable View All Access a snapshot of the entire alarm alert database in the configured order.
Mode This mode is accessible from summary displays. Alarm indicators and values
are not updated. Use this command, for example, to save and/or print the
alarm entries in the database or apply a match/filter specification to the
entire database at the time of access for analysis.
Disable View Dismiss the View All mode from a summary display. An automatic refresh is
All Mode performed, and the alarms that meet the display’s criteria are displayed.
Go To Page Access a dialog box for paging through the alarm list. This command is
available on summary displays, the Alarm History Display, and the CAD.
Use this command on touchscreens as an alternative to using the scroll bar.
Hide Controls Hide all menus and buttons from the selected display. The number of alarms
per screen automatically increases. To redisplay the controls, issue the Show
Controls command from the pop-up menu.
Display Menu
86
3. Alarm Manager Displays B0193RV – Rev E
Status Area
This is a horizontal portion near the bottom of the alarm display that provides the following
information:
Message/Information Meaning
Match Active A match/filter specification has been applied to the display, limiting
the displayed alarm entries.
Horns Muted Horns have been muted for the local workstation or the Common
Alarm Group
Number of Alarms This is the sequential position of the alarm that appears at the top of
the current page compared to the total number of alarms associated
with the display type. When resizing displays, these numbers help
you determine the number of alarms per screen load
% Number Displays while the Historian database is being read into an Alarm
History Display.
Historian Name The Historian associated with the Alarm History Display.
Time and Date The time and date the display was initiated or refreshed:
HH:MM:SS (Hours:Minutes:Seconds) and MM-DD-YR (Month-
Day-Year)
Paused New alarm entries to the MRA or CAD will not appear until you
issue an Unpause command. This message appears briefly during
alarm selection and while a Find dialog box is active.
No Updates Appears when a Find dialog box is visible for the MRA, NEWALM,
ACKED, and UNACK displays, indicating that Object Manager
updates are postponed until the Find dialog box is removed. This
message also appears when View All mode is enabled.
Button Area
An alarm display’s button area contains buttons to perform commands in the selected window.
Button accessibility depends on user access level assignments and the appropriateness of the
action. For example, if an acknowledged alarm entry is selected, the ACK ALARM button is not
available.
These are each display’s default set of command buttons.
CAD MRA NEWALM UNACK ACKED AHD OPR
Ack Alarm X X X X
Ack Compound X X X X
Ack Page X X X X
Clear Alarm X X X X X
Displays Menu
Choose To Access the
Current Alarms Current Alarm Display
Most Recent Alarms Most Recent Alarms display
New Alarm Summary New Alarm summary display
Unacknowledged Alarm Summary Unacknowledged Alarm summary display
Acknowledged Alarm Summary Acknowledged Alarm summary display
Alarm History Display Alarm History Display
Operations Operations display
Horns Menu
Choose To
Silence Horns Silence local Annunciator/workstation horns. If the station is
in Common Alarm Group, silence all horns within the group.
Mute Horns Temporarily mute (until unmute is issued or reboot)
Annunciator/workstation local horns. A “Horns Muted”
message appears in the status area.
Mute CAG Horns Temporarily mute (until unmute is issued or reboot) all
Annunciator/workstation horns in the Common Alarm
Group to which the workstation is a member. “Horns Muted”
appears in the status area. If the workstation is not a member
of a Common Alarm Group, this command is ignored.
88
3. Alarm Manager Displays B0193RV – Rev E
Choose To
Unmute Horns Unmute local Annunciator/workstation horns.
Unmute CAG Horns Unmute all horns in the Common Alarm Group.
Button Area
The button area includes these buttons:
Choose To
Top Priority Access the top priority alarm, depending on the sort order
(SORT_CFG and LIA_OLDEST) of the alarm alert database.
Environments Access another I/A Series environment with alarm-related permissions
♦ (UNIX workstations) From the Window System menu of the display window, choose
Close.
♦ (Windows NT workstations) From the Window System menu, choose Minimize.
An icon appears with the following information:
Item What it means
# (UNIX workstations) A number (0 through 3), indicating the
status of the Process button:
0 = Normal state (no alarms
1 = No alarms; previous alarm(s) still unacknowledged
2 = Acknowledged process alarm condition
3 = Unacknowledged process alarm condition
Horn state (UNIX workstations) “not muted” or blank (horns are unmuted)
Display type OPR, MRA, CAD, AHD, NEWALM, UNACK, or ACKED
Name Alarm Manager name
On Windows NT workstations, move the mouse pointer over the application name in the task
bar. The display will show the name of the letterbug:AMNAME and the name of the alarm dis-
play.
Resizing an AM Window
The capability to resize an AM window is configurable from the Alarm/Display Manager Config-
urator. Resizing can be enabled or disabled; if enabled, resizing limits can be imposed.
NOTE
The ability to resize depends on how the display is configured; for example, whether
the Resize option is selected.
90
3. Alarm Manager Displays B0193RV – Rev E
Responding to Alarms
Use alarm display windows to respond to process alarm conditions by:
♦ Viewing a list of alarms and viewing an alarm’s detail information
♦ Accessing process displays (for example, resolving an alarm condition from a user
graphics display or a Block Detail Display)
♦ Acknowledging alarms
♦ Clearing alarms from the alarm alert database
Responding to Alarms 91
B0193RV – Rev E 3. Alarm Manager Displays
92
3. Alarm Manager Displays B0193RV – Rev E
TIP
You can also view additional alarm information by double-clicking an alarm entry.
(This is the default setting for the double-click action.
TIP
Or right click the mouse to view a pop-up menu, and choose Alarm Details.
Responding to Alarms 93
B0193RV – Rev E 3. Alarm Manager Displays
To select or find alarms related to a specific match criteria and/or filtering criteria
♦ Refer to “Locating Alarms” on page 94.
Locating Alarms
Within an alarm display, you can locate specific alarms that match various criteria. After locating
alarms, you can then perform an action, such as acknowledging alarms or clearing alarms on the
selected entries.
If you must repetitively locate specific alarms that match various criteria, you can save time by sav-
ing match/filter criteria to a match specifications file (.ams file) and using this file to perform a
match or find operation. Alarm displays offer two commands for locating alarms.
Each command brings up a dialog box for match criteria and filter criteria. You can specify multi-
ple entries and wildcards in the dialog box. The two dialog boxes are virtually identical, but have
some slight differences with regard to control buttons at the bottom of each dialog box. You can
use an .ams file in a Find or Match dialog box.
Character Refers to
? (question mark character) A single character
* (asterisk character) Multiple characters
Use a comma (,) to separate multiple entries in the CP letterbug, Compounds, Blocks,
Block Description, Point Name, Alarm Text, and Loop ID fields.
Multiple entries within a field are ORed. Entries between fields are ANDed.
94
3. Alarm Manager Displays B0193RV – Rev E
Responding to Alarms 95
B0193RV – Rev E 3. Alarm Manager Displays
Acknowledging Alarms
From alarm displays, you can select an alarm and click a command button to acknowledge the
alarm. You can acknowledge:
♦ One or more alarms selected manually
♦ Particular alarms using the Find Alarms command from the Edit menu
♦ The entire page of alarms
♦ All alarms related to blocks in the same compound
The following table describes button functions.
Button Acknowledges
Ack Alarm All alarms associated with the block containing the selected alarm(s)
Ack Compound All alarms located in the same compound as the selected alarm(s)
Ack Page All alarms associated with the blocks on the current page
Acknowledgment is achieved at the control processor, therefore all the connected Alarm Managers
will receive the updated acknowledge status. Alarm displays on other workstations that receive the
same alarms are also updated.
TIP
You can also acknowledge alarms by clicking the right mouse button, which invokes
a pop-up menu. Choose an acknowledge command from the menu.
96
3. Alarm Manager Displays B0193RV – Rev E
All alarms located in the same compound as the selected alarm(s) are acknowledged.
TIP
You can also acknowledge alarms by clicking the right mouse button, which invokes
a pop-up menu. Choose an acknowledge command from the menu.
TIP
You must first select an alarm before clicking Block Detail or User Display.
Button Configuration
The Top Priority, Block Detail, and User Display buttons can be configured to call up process dis-
plays to another workstation or to a specified display manager. Process display call-up is controlled
by the Common Alarm Group configuration file and redirection variables.
Clearing Alarms
Clearing an alarm removes the alarm from the alarm alert database, regardless of its active or
acknowledged state. Cleared alarms are grayed and are unselectable until a manual or automatic
refresh of the display is performed.
98
3. Alarm Manager Displays B0193RV – Rev E
To save
1. From the File menu, choose Save.
The default directory is /usr/fox/customer/alarms/reports. If you want to save to a dif-
ferent directory, choose it.
2. Choose an existing filename to overwrite the file, or type a new filename to save
alarms to a new file.
3. Choose Normal or CSV.
On a UNIX workstation, choose the Normal or Comma Separated radio button.
On a Windows NT workstation, name the file with a .CSV extension for CSV for-
mat; otherwise, the file defaults to Normal format.
4. Choose OK.
Normal format
Alarm Manager: Y1AP51:SAMENM Display: MRA
Date: Fri Oct 27 08:49:08 1995
08:48:22 Y16CP3_01:PID_10. 77.08 LOABS 5 U
08:48:22 Y16CP3_02:PID_10. 77.08 LOABS 5 U
Select To
no script or lpr Send alarms directly to the printer.
mp Using a PostScript printer, print alarms in two
columns, representing two alarm pages.
pr Print each page with a header that includes the
page number and time and date of printing.
a2ps Using a PostScript printer, print alarms on the
PostScript printer within a box, and print the
time and date of the printing.
100
3. Alarm Manager Displays B0193RV – Rev E
NOTE
Optional print scripts use UNIX utilities to customize the print format. Print
scripts are defined in the /usr/fox/customer/alarms/reports/pscripts file and may be
edited with a text editor.
6. Choose OK.
NOTE
You can also use the page_setup and print_setup Alarm Manager built-in com-
mands to set page margins and set print options, respectively.
NOTE
On summary displays, you can choose View All mode to obtain a snapshot of the
entire alarm alert database at a given time.
When a match/filter specification is applied to a display, for safety reasons, “Match Active”
appears in the status area, indicating all the alarms associated with the display are not visible. Also,
the match description, if present, is shown in the display title.
Match/filter and Find operations follow rules.
Match/filter and Find specification field entries support these wildcard characters:
Character Refers to
? (question mark character) A single character
* (asterisk character) Multiple characters
Use a comma (,) to separate multiple entries in the CP letterbug, Compounds, Blocks,
Block Description, Point Name, Alarm Text, and Loop ID fields.
Multiple entries within a field are ORed. Entries between fields are ANDed.
To create a match specification for filtering alarms on the associated alarm display
NOTE
You need not enter information in every field. Only enter criteria pertaining to the
alarms you choose to locate.
1. From an alarm display, choose Match Alarm from the View menu.
The Alarm Match dialog box appears.
NOTE
You can optionally type a description in the Find/Match description field at the top
of the dialog box. This description text appears at the top of the alarm display when
you perform a match operation but does not appear when you perform a find oper-
ation.
2. In the Match Specification block fields, type the information as required to create a
subset of the alarms currently associated with the display.
You can supply information (separated with commas) in one or more of these entry
fields: CP Letterbugs, Compounds, Blocks, Block Description, Alarm Text,
Point Name, and Loop ID).
3. Type the Time specifications.
The Select Date and Time dialog box appears to aid in the entry of date and time
information.
Time Fields Description
Set Time Enter the start time.
Clear Time Enter the end time.
Depending on the entered criteria (start time, duration, end time), information is
automatically generated. For example, entering the start time and duration results in
the end time being supplied.
A 30-day month is used in the calculation. If the duration is two months, the end date
is equal to the start date plus 60 days. For example, a March 1 start date plus 60 days
results in an April 29 end date.
4. Scroll through list of alarm types and select desired alarm type(s).
102
3. Alarm Manager Displays B0193RV – Rev E
NOTE
You cannot select Alarm State options on summary displays. However, if you create
and save an .ams file from a display that permits the entry of alarm state, you can
read that .ams file from a summary display. You cannot select the Unacknowledged
and Acknowledged options from an Alarm History Display.
6. Type the desired filtering specifications to limit the included alarms. Filtering passes
alarms that do not match the filter criteria.
You can supply information (separated with commas) in one or more of these entry
fields: CP Letterbugs, Compounds, Blocks, Block Description, Alarm Text,
Point Name, and Loop ID).
7. Set Time filter options.
Click the Set Time and Clear Time buttons to bring up a dialog box for time filter cri-
teria entry.
8. Click the necessary command buttons:
Choose To
OK Apply the match/filter specification to the display and dismiss the dialog
box
Apply Apply the match/filter specification to the display and maintain the
dialog box
Stop Remove the applied match/filter specification from the display and
maintain the dialog box.
Load Access the File Selection dialog box so you can select an existing
specification file to be loaded and applied to the display
Save Access the File Selection dialog box to save the specification to a file.
Clear Remove the match/filter specifications from the fields in the dialog box.
Close Dismiss the Alarm Match dialog box without applying or saving the
matching/filtering specification
Once you have entered a match specification and chosen OK or Apply, the corresponding display
presents “Match Active” in the left corner of the status bar.
NOTE
If you set up a match for TARG, save the alarm match information to a file, and
load the .ams file, both TARG and HHABS are pre-selected. Selecting HHABS,
saving to a file, and loading the .ams file pre-selects TARG. Similarly, selecting
PTARG or HIOUT pre-selects the other option.
104
3. Alarm Manager Displays B0193RV – Rev E
The alarm match specification information is removed from the dialog box.
To invoke a display with a match active or refresh a display if the display is already active
1. Set up an alarm match specification and save it to a file.
2. Configure a button (for example, called MATCH ACTIVE DISP) with the action:
almdisp <name of display> -match <pathname>/<filename> [-refresh]
The following procedures demonstrate how to create alarm match specification files for use from
a customized pull-down menu.
To create and save an alarm match specification file for critical alarms
1. From an alarm display’s View menu, choose Match Alarms.
The Alarm Match dialog box appears.
2. In the Alarm Priority box, select 1 and 2.
3. Choose Apply.
The alarm display shows only Priority 1 and Priority 2 alarms.
4. Click the Save button.
5. Type critical as the filename.
The match/filter specification is saved to
/usr/fox/customer/alarms/amspec/critical.ams
To create and save a match specification file to view specific alarms for specific compounds
This example shows how you can view sequence alarms for specific units, such as UNIT23 and
UNIT24, by applying a match based on the compound names with a UNIT23 or UNIT24 pref-
ace and the alarm type.
1. From an alarm display’s View menu, choose Match Alarms.
The Alarm Match dialog box appears.
2. Type a match description such as Units 23/24 Sequence Alarms.
3. In the Compounds field, type UNIT23*, UNIT24*.
Be sure to include the asterisks (*), which represents any number of characters.
4. In the Alarm Types list box, select CONF, EXC, IND/DEP, INFO, MON, and SEQ6.
5. Choose Apply.
The alarm display shows only the sequence alarms for blocks with compound names
beginning with “UNIT23”or “UNIT24” and the display title shows the match
description text of Step 2.
6. Click the Save button and type units23_24 as the filename.
The alarm match specification is saved to
/usr/fox/customer/alarms/amspec/units23_24.ams
106
3. Alarm Manager Displays B0193RV – Rev E
The display shows only alarms other than the low alarms that were not specified.
4. Click the Save button and type nolows as the filename.
The alarm match specification file is saved to
/usr/fox/customer/alarms/amspec/nolows.ams
Silencing Horns
The operator can silence the Annunciator keyboard (or FoxPanels) horn, console horn, and exter-
nal horns associated with a workstation.
If the workstation is configured in a Common Alarm Group, all the horns throughout the Com-
mon Alarm Group are silenced.
Muting/Unmuting Horns
You may choose to temporarily override the pre-configured sounding of alarm horns during sys-
tem start-up and testing. Muting a horn shuts off the horn.
Muting and unmuting can be directed to an individual workstation or throughout an entire
Common Alarm Group of which the workstation is a member. You can mute a Current Alarm
Group and unmute locally.
For safety reasons, the alarm display's status area shows “Horns Muted” when either muting
option is selected.
Be cautious when muting horns within a Common Alarm Group. 50 Series and 70 Series work-
stations within the CAG display “Horns Muted”. Other workstations (WP20/30s) display the
message in the message line each time the Current Alarm Display is refreshed.
Use a pref command to determine the status of alarm horns on non-50 Series and non-70 Series
workstations. For example, pref -DMNAME dmcmd “horns -2 0 0".
The default value of the init.user file’s RESOUND option is to not resound horns (if any alarms
causing a horn(s) to sound occurred during the period the horns were muted) after unmuting
horns.
For a recovery reboot, the mute horn status is retained for members of a Common Alarm Group.
However, individual stations are initialized to come up with horns sounding (unmuted).
108
3. Alarm Manager Displays B0193RV – Rev E
NOTE
If the workstation is not a member of a Common Alarm Group, the Mute All
Horns command is ignored.
NOTE
Protection classes (access levels) are applied to the AM display.
110
4. Configuring Alarm Managers and
Display Managers
This chapter provides conceptual information about the Alarm/Display Manager Configurator
(ADMC).
The chapter describes:
♦ The items that you can configure
♦ Schemes and templates
♦ Invoking the ADMC
♦ The AM database (.am file) used in Alarm Manager configuration
♦ Configuration philosophy and decisions you need to make
Refer also to Chapter 5 “Using the Alarm/Display Manager Configurator”, which is composed of
how-to (procedural information) found in the ADMC’s on-line Help.
111
B0193RV – Rev E 4. Configuring Alarm Managers and Display Managers
Control Menu
Main Menu
Configuration Philosophy
There are three general categories of users:
♦ Most users are satisfied using the Foxboro supplied schemes. These users need only
configure the Alarm Manager names and display manager names, stations, and so on,
as described in Chapter 5 “Using the Alarm/Display Manager Configurator”. This
category of user does not need to develop customized schemes.
♦ Some users want to make minor changes to their user interface, display positions, or
alarm formats. The recommended approach they should take is to copy existing
schemes and edit the copies. They should not directly edit the Foxboro supplied
schemes. These users must understand the relationships among scheme types.
♦ Some users want to create their own schemes. These users will copy and edit existing
schemes, or create entirely new schemes. These users must understand how schemes
are employed. They may chose to create and use templates.
Schemes
A scheme is a named set of configuration settings.
Each Alarm Manager (AM) uses configuration data in an Alarm Manager (AM) property scheme.
The AM property scheme specifies settings such as:
♦ The action to be taken upon the receipt of a new alarm
♦ The initial I/A Series environment in which the AM starts up
112
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
Schemes 113
B0193RV – Rev E 4. Configuring Alarm Managers and Display Managers
AM Property Scheme
Class
Initial Environment
New Alarm Action
Most Recent Alarm Display Settings
Current Alarm Display Settings
New Alarm Display Settings
Unacknowledged Alarm Display Settings
Acknowledged Alarm Display Settings
Alarm History Display Settings
Operations Display Settings
• Menu Configuration
• Button configuration
• Pop-up menu configuration
• Double-click action
• Button row/column layout
• Alarm row/column layout
• Alarm Format Settings
114
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
Templates
Templates are provided as a configuration aid for advanced users. A template provides default val-
ues when you create a new “object” with the ADMC main browser window’s New button. For
example, choosing Alarm Managers from the select list on the ADMC main browser window and
clicking the New button creates a new Alarm Manager object.
When you create a new display manager or Alarm Manager, a name is automatically generated,
and default settings/record names from the template are automatically provided.
The template provides default information that automatically appears in DM or AM configura-
tion dialog boxes or in newly created schemes.
By means of a single set of templates, you can quickly and easily configure multiple DMs and
AMs to use a common set of settings or records.
Each DM or AM template represents a default record that is part of the DM or AM configura-
tion. You can use the Alarm/Display Manager Configurator (ADMC) to customize the set of the
Foxboro supplied templates. Templates can be saved and used in new configurations.
Templates 115
B0193RV – Rev E 4. Configuring Alarm Managers and Display Managers
foxMRA foxCAD
Alarm Format Scheme Alarm Format Scheme
• Alarm field positions and lengths • Alarm field positions and lengths
• Alarm field colors and fonts • Alarm field colors and fonts
Figure 4-4. Schemes used by the Foxboro Supplied Default Alarm Manager
116
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
Examples of Schemes
Give each scheme a unique name that characterizes the information that it contains. For example,
an AM property scheme named “Cascade” could be a scheme in which alarm displays are defined
to come up in an overlapping fashion.
UNACK
NEWALM
AHD
MRA
CAD
An AM alarm format scheme, “BlockType”, for example, could be a scheme that displays alarm
text information as follows.
BOILER1
10:12:06 HIABS
A user interface scheme named “VertStrip”, for example, may provide an alarm window that dis-
plays to the right of the standard display manager window.
NOTE
The foxFullSq, foxStrips, and foxGrids schemes illustrate how you can achieve dif-
ferent effects, such as different alarm formats, square buttons for Touchscreens,
strips and grids.
The following figures show examples of displays associated with various AM Property Schemes.
118
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
120
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
Figure 4-10. Examples of foxGrids AM Property Scheme (CAD, MRA, and NEWALM)
122
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
Items you can configure are grouped under buttons in the Select box buttons (right side of win-
dow). The following list shows the name of the button and its configurable items.
Display Managers
♦ Display manager name
♦ Station letterbug
♦ Screen (local station, remote station, screen list, or undedicated)
♦ Display manager property scheme
♦ Create Alarm Manager (checkbox)
DM Properties
♦ Display manager class (Boot-Up, Operator, Engineer, or View Only)
♦ Environment script
♦ Initial display size and position
Alarm Managers
♦ Alarm Manager name
♦ Station letterbug
♦ Screen (local station, remote station, screen list, or undedicated)
♦ Alarm Manager property scheme
124
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
AM Properties
♦ Alarm Manager class (Boot-Up, Operator, Engineer, or View Only)
♦ Environment script
♦ New Alarms button action
♦ For each display type (for example, MRA):
♦ Scroll origin
♦ Scroll direction
♦ Initial display size and position
♦ Additionally, some display types allow further definition (overlay on re-alarm,
refresh data, data refresh rate, alarm entry list order)
User Interfaces
♦ Alarm format scheme
♦ Menu bar items and commands
♦ Pop-up menu commands
♦ Number of alarm rows and alarm columns
♦ Number of button rows and button columns
♦ Double-click action (required access code, and the command to be run)
Alarm Formats
♦ Default font for an alarm cell and the indicator font
♦ Alarm cell foreground and background color
♦ Format used for time and date
♦ Alarm cell contents (font grid, cell contents, field location and size)
♦ Alarm state indicators and acknowledgement state indicators
Screen Lists
♦ Groups of screens
Associations
♦ DM/AM association
Pre-Configuration Decisions
Before using the Alarm/Display Manager Configurator, you should decide how many display
managers and Alarm Managers your system requires.
The Foxboro Company recommends that you photocopy the attached worksheets. Use one set of
worksheets for each display manager or Alarm Manager. Fill in the blanks on the worksheets so
you will be prepared to make selections while using the ADMC.
126
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
128
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
The Foxboro Company recommends using a single (master) database file. A single source file for
all the workstations simplifies many aspects of file maintenance (file naming, archiving, and mul-
tiple versions in many locations). Maintaining a single file and configuring all the workstations
from that file helps to avoid potential problems at a later date.
NOTE
An update to the AM .cfg file can be realized without a reboot.
NOTE
You need not reconfigure the default Alarm Manager supplied with each worksta-
tion unless you want to customize default settings for that Alarm Manager. AM
configuration is required to run multiple Alarm Managers on one workstation.
Use the Alarm/Display Manager Configurator to configure a set of alarm displays to meet your
site’s needs. You can configure multiple Alarm Managers, however, the number of Alarm Manag-
ers running at one time must be equal to or less than the number of purchased display manager
licenses.
130
4. Configuring Alarm Managers and Display Managers B0193RV – Rev E
NOTE
A workstation without optionally purchased display manager and Alarm Manager
licenses has one letterbug display manager and one letterbug Alarm Manager. You
do not have to configure this workstation, but may customize it.
Figure 4-13. Alarm Manager Property Scheme and Alarm Manager Display Type Dialog Boxes
132
5. Using the Alarm/Display
Manager Configurator
This chapter describes the Alarm/Display Manager Configurator (ADMC) used to configure all
aspects of alarm displays: menus, buttons, alarm entries, position of displays, and so on.
You also use the ADMC to configure multiple instances of Alarm Managers and display manag-
ers.
You use the Alarm/Display Manager Configurator (ADMC) to configure all aspects of alarm dis-
plays: menus, buttons, alarm entries, position of displays, and so on. You also use the ADMC to
configure multiple instances of Alarm Managers and display managers.
NOTE
Alarm alert database attributes such as alarm entry sort options, return-to-normal
action, and Clear button action, affect the contents of all the alarm displays for all
the Alarm Managers running on that workstation. You do not use the ADMC to
configure these attributes; refer to the init.user file located in the /usr/fox/wp/data
directory.
You customize your site’s presentation of alarm displays. You can customize schemes and/or tem-
plates for use in configuring display managers and Alarm Managers, refer to “Working with
Alarm Managers” on page 154.
This chapter contains information from the ADMC’s on-line Help. Refer to Chapter 4 for a con-
ceptual description of the ADMC. This chapter describes:
Information Location
ADMC window “ADMC Main Browser Window” on
page 134
Steps used to configure Alarm Managers “AM/DM Configuration – Major Steps”
and display managers on page 136
Customizing Alarm Managers and display “AM/DM Customization” on page 143
managers
Operations you can perform on Alarm “Working with Alarm Managers” on
Managers page 154
Customizing the menus available from an “Customizing Alarm Display Menus” on
alarm display page 163
Customizing an Alarm Manager’s User “Configuring a User Interface Scheme or
Interface scheme Template” on page 170
Configuring the presentation of alarm “Configuring an Alarm Format Scheme”
messages on page 173
Alarm Manager default settings “Alarm Manager Displays – Default Set-
tings” on page 182
133
B0193RV – Rev E 5. Using the Alarm/Display Manager Configurator
Control Menu
Main Menu
The ADMC main browser window enables you to customize the template set and/or create new
customized schemes before configuring Display Managers and Alarm Managers.
The main browser window includes these parts:
♦ Menu bar
♦ List box
♦ Command buttons
♦ AM/DM title bar
♦ Select box
134
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
File Menu
Choose To
New Create a new unnamed AM database (.am) file using standard the
Foxboro supplied templates, or using existing customized templates.
Optionally, you can include or exclude existing display manager
information from the file.
Open Open an existing AM database file (.am file) for viewing or editing.
Import "dmcfg" Import an existing dmcfg file into the current AM database (.am) file.
This overwrites records with the same name. You use this to import a
"local" dmcfg file from \usr\fox\customer\hi to a master file.
Save Save the information to an existing or new AM database (.am) file. If the
-or- database file is unnamed, the Save Configuration As dialog box appears.
Save As
Save Defaults Save customized templates, schemes, or both as a .cdf file for use in other
AM database files. Do not overwrite the standard templates provided by
The Foxboro Company which are located in
/usr/fox/up/data/foxboro.cdf.
Validate Records Verify the names and referenced records in the AM database file (.am file).
Create Install Create subdirectories for each workstation and place the required display
Files manager and Alarm Manager configuration information in these worksta-
tion subdirectories. Note that these subdirectories are on the local work-
station and that the files will have to be copied to the destination worksta-
tions. The AM database (.am) file is validated before creating install files.
Exit Leave the Alarm/Display Manager Configurator. If changes have been
made, a dialog box queries whether to save the AM database information
before exiting. (An asterisk in the title bar indicates that un-saved changes
have been made to the .am file.)
Edit Menu
Choose To
Template Edit a template required for the DM/AM database. Templates include
default values for: display manager properties, Alarm Manager properties,
a user interface scheme for each type of alarm display, alarm entry formats,
and screen lists.
NOTE
Changing a template does not affect existing display manager or Alarm Manager
configurations.
136
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
These procedures are described next. It is assumed that the ADMC window is open on your
workstation. The remainder of this chapter is a text copy of the ADMC on-line Help’s “how to”
information.
Refer also to “Tutorial – Configuring AMs and DMs with Standard Defaults” on page 191
to learn how to quickly configure AMs and DMs using default values.
Click To
Standard Include standard default information (supplied by Foxboro).
Click To
Other Display the Load Configuration Defaults dialog box to select another
set of previously saved customized templates/defaults (.cdf) file.
Click To
None Include no existing dmcfg file (display manager) information
Local Include the local dmcfg file information to provide additional DM
property scheme information and previously configured DM/AM
information
Other Display the Load DMCFG File dialog box to include another dmcfg
file in the configuration file.
NOTE
The Load DMCFG File dialog box loads only one dmcfg file into the configuration
file. To load multiple dmcfg files, issue the Import dmcfg command.
4. Choose OK.
The information loads into the configuration file.
The template/default information is available from the main browser window.
5. Perform one of these actions:
♦ Configure the display managers and Alarm Managers.
♦ Customize the appropriate display manager or Alarm Manager schemes before
configuring the display managers and Alarm Managers.
NOTE
If install files have previously been generated from the AM database (.am) file,
a <filename>.dir directory appears in the /usr/fox/customer/config directory.
2. Select the name of the AM database file or the workstation configuration file: <file-
name>.am.
3. Choose OK to confirm the file name.
138
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
To import additional dmcfg information (other than local dmcfg) into the AM database file
1. Copy each remote dmcfg file to a unique file name in a local directory (for example,
/usr/tmp/dmcfg.<letterbug>).
2. From the ADMC’s File menu, choose Import dmcfg.
The Import dmcfg dialog box appears.
The dialog box defaults to the /usr/tmp directory.
3. Select the desired dmcfg file to be imported.
4. Choose OK to confirm the file name.
5. Repeat Steps 1 through 4 for each required dmcfg file.
! CAUTION
The standard templates and schemes provided by Foxboro are stored
in /usr/fox/wp/data/foxboro.cdf. Do not alter this file.
NOTE
A saved AM database file (.am file) includes the set of defaults used in the configu-
ration.
3. Choose OK.
NOTE
When left blank, referenced names default to the Foxboro supplied values. For
example, leaving the “Alarm Manager Property Scheme” blank (rather than entering
“foxDefault”) automatically uses the foxDefault scheme. Note, however, using the
default (thus, not typing the name of the scheme) produces a smaller .am file. To
conserve diskspace, do not type the name of the default scheme.
140
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
The Validate Database dialog box describes problem and shows the record name
requiring correction. These action buttons may be available:
Choose To
Clear Clear the reference from the Record Name box
Select Access a list of records. Click a record to replace the invalid
reference. Select the replacement and choose OK.
Create Create a new record with the listed record name. Choose OK.
Ignore Ignore this validation problem and searches for the next invalid
record.
NOTE
Only screen lists and DM/AM property schemes can be cleared from the reference
box if invalid. Once cleared, the Screen option is set to Undedicated, and the DM
or AM property scheme reverts to the Foxboro supplied DM or AM defaults.
NOTE
The Ignore button is not accessible if invalid records are found when running the
Create Install Files command.
If created/saved during “Create/Install files”, the AM database (.am) file is checked for
valid record names. If the configuration file records are valid, a Progress Log message
box indicates the information related to the creation of the install files.
NOTE
If a scheme (record) is invalid or has an invalid scheme (record) associated with it,
the Validate Database dialog box appears.
NOTE
The AM database file (<filename>.am) is required when adding or reconfiguring
DM and AM information for a workstation. The AM database file contains the
information required to create the install files.
142
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
For UNIX, use the rmount command to remotely mount and copy files to the appro-
priate remote workstation directories.
! CAUTION
Do not manually update the dmcfg file after using the Alarm/Display Manager
Configurator (ADMC) to configure the dmcfg file. Use the ADMC to change the
<filename>.am file, then generate the install files and distribute the files to the
appropriate workstation(s).
NOTE
Only perform this procedure to use a customized configuration. For details about
Alarm Manager start-up, refer to “Display manager and Alarm Manager Start-Up”
on page 63.
1. From a VT100 window or DOS window, type these commands to preserve the origi-
nal AM database file:
cd /usr/fox/customer/alarms/cfg
cp am_def.cfg am_def.cfg.fox
You must now install this file from a VT100 window.
2. Type these commands:
cd /usr/fox/customer/config/<filename.dir>/<letterbug>
cp <am_name1>.cfg /usr/fox/customer/alarms/cfg/am_def.cfg
AM/DM Customization
Use the following procedures to customize Alarm Managers and display managers.
! CAUTION
Back up the default database file (foxboro.am) before making edits.
cd /usr/fox/customer/config
cp foxboro.am customer.am
compress foxboro.am
Associating a DM with an AM
A display manager can be associated with one Alarm Manager only. This association determines
the Alarm Manager called when the display manager's Process (or Alarm) button is pressed. To
better utilize a workstation's memory and computing power, associate multiple display managers
with the same Alarm Manager.
NOTE
The ADMC prohibits you from assigning multiple AMs to the same DM.
4. Choose OK.
144
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
If you plan to cascade several displays, choose the quarter screen size.
146
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
You can copy it remotely. You need not physically be on each individual worksta-
tion.
NOTE
To test only the new dmcfg file, reboot the workstation. To test only the
AMNAME.cfg file, restart the Alarm Manager.
3. Click the Process (or Alarm) button on the display manager window.
This initiates the same Alarm Manager to start again with the new configuration.
NOTE
You cannot edit the template name.
6. When you have completed editing the templates, perform one of these actions:
♦ Configure the required display managers and/or Alarm Managers.
♦ Save the templates for configuring DMs and AMs at a later date.
NOTE
Previously created external .cfg files that had been based on the edited template do
not automatically acquire the updates.
To import a scheme
1. From the ADMC main browser window, select the scheme type from the Select box.
2. From Alarm/Display Manager Configurator main browser, click the Import button.
The Import dialog box appears.
3. Click the Library button.
The Open Configuration dialog box appears.
4. Depending on your system’s AM database, select foxboro.am or <customer.am>.
The Import dialog box appears.
5. Indicate the records to be imported into your AM database.
148
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
To have X terminal names appear in the station list for selection, type X terminal
names (one per line) in the /usr/fox/customer/config/xterms file. Restart the
Alarm/Display Manager Configurator (ADMC) each time you change this file.
To remove a station from the configuration, select the name in the list box and choose
Remove. The name of the station returns to the station list.
6. Choose OK.
NOTE
You cannot edit the name of a Screen List template.
2. If the display manager that you want is not listed, from the File menu, choose Open.
The Open Configuration dialog box appears.
3. Select the desired AM database file in which the display manager resides.
4. From the list box, perform one of these actions:
♦ Double-click the name of the display manager to be edited.
♦ From the list box, select the name of the display manager to be edited and choose
Edit.
The Display Manager dialog box appears.
5. Make the appropriate changes.
6. Choose OK.
150
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
A display manager can use a screen list created for an Alarm Manager configuration.
Use standard (default) templates as a starting point for customizing templates or individual dis-
play managers.
NOTE
Environment script files contain access code information and passwords to ensure
security access. Refer to Workstation Configuration (B0193AG) and Display Man-
ager/FoxView Calls (B0193DF) for information on environment script files.
5. Choose OK.
6. From the Display Manager Property Scheme dialog box, set the initial display size and
position as follows:
a. Click the button associated with the monitor to select the DM window size:
♦ Foxboro default size
♦Full size
♦ Intermediate size
♦ Quarter screen
b. For the intermediate size or quarter screen, choose the display window’s initial
location (Top/Bottom, Right/Left).
c. If desired, select one or both of these check boxes:
♦ Display is Re-Sizable
♦ Resizable to a Fixed Minimum Size (for font readability)
7. Choose OK.
NOTE
You cannot edit the name of a Display Manager Property Scheme template.
2. Continue with Step 2 under “Creating a New DM Property Scheme” on page 151.
NOTE
The following procedure assumes the availability of appropriate DM property
schemes and screen lists. If they are not available, configure the desired schemes
before configuring the DM.
152
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
Selecting Template does not allow you to edit the DM name.
2. Click the Station Letterbug combo box button and select the station to which the
DM is assigned, or type the letterbug.
3. Click the Screen prompt button to select the station or screens on which the DM can
display.
The Station Screen Selector dialog box appears.
The first three options indicate dedicated screens:
To Choose
Choose First Head, Second Head, or Both Heads. Local Station
Enter the name of a remote station Remote Station
Select (or type) the name of a pre-configured screen Screen list
list, indicating the workstations on which the DM
can appear. If an appropriate screen list is not
available, customize a screen list.
Display the DM on any screen Undedicated
NOTE
To include X Terminal names in the station list, type the X Terminal names (one per
line) in the /usr/fox/customer/config/xterms file. Restart the ADMC each time you
change the xterms file to make the changes available.
Choose OK to confirm the selection and return to the Display Manager dialog box.
4. If the default display manager Property Scheme is not appropriate:
a. Click the combo box button.
A list of available DM Property Schemes appears.
b. Type a DM Property Scheme name, or leave it blank to use a default DM prop-
erty scheme. If an appropriate scheme is not available, refer to “Importing Exist-
ing dmcfg Information into an AM Database File” on page 139.
5. Select the Create Alarm Manager check box to create an Alarm Manager with the
same name.
Without a DM/AM association, a display manager automatically accesses (via the
Process/Alarm button in the I/A Series environment) an Alarm Manager with the
same name or the letterbug AM.
A display manager can be associated (at most) with one Alarm Manager. Multiple
DMs can invoke the same Alarm Manager. Refer to “Associating a DM with an AM”
on page 144. Multiple DMs access the same Alarm Manager via DM/AM association
on a first-come/first-served basis.
6. Choose OK.
If the AM was previously created during display manager configuration, refer to “Editing an
Alarm Manager” on page 155.
You can create a new Alarm Manager using existing defaults, or you can customize a new Alarm
Manager.
154
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
If appropriate user interface schemes are not already configured, configure them for
each alarm display type (such as CAD) before configuring the AM property scheme.
Refer to “Customizing an AM Property Scheme or Template” on page 155.
Scheme Relationships
Each Alarm Manager must be assigned an AM property scheme.
An AM property scheme references one or more User Interface schemes, one for each alarm dis-
play window. You can use the same UI scheme for all the display windows, or a unique UI scheme
for each display window (each display window having its own set of menu selections and but-
tons).
Each UI scheme must be associated with an Alarm Format scheme, which defines each alarm
entry’s information and presentation.
156
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
The Alarm Manager name is automatically generated with “AM” and a four-digit
number (0000-9999). The automatic generation of AM names starts with AM0000
and skips existing AM names with four-digit numbers. Or, you can type an Alarm
Manager name (up to six alphanumeric uppercase characters and unique throughout
the network).
2. Click the Station Letterbug combo box button, or type a letterbug.
3. Click the Screen prompt button.
The Station Screen Selector dialog box appears.
4. Indicate the type of station or screens on which the AM can display.
Click a button to indicate the screen to which the AM is to appear.
To Choose
Choose First Head, Second Head, or Both Heads. This Local Station
is a dedicated screen.
Type the name of a remote station Remote Station
Select (or type) the name of a pre-configured screen list, Screen list
indicating the workstations on which the DM can
appear. This is a dedicated screen. If an appropriate
screen list is not available, customize a screen list.
Display the DM on any screen Undedicated
5. Choose OK to confirm your selection and return to the Alarm Manager dialog box.
6. If the default Alarm Manager Property Scheme is not appropriate, click the combo
box button to access the list of available AM Property Schemes, then type the name of
an AM Property Scheme (or it leave blank to use AM Property default values).
If an appropriate scheme is not available, Refer to “Customizing a Screen List” on
page 148 or “Associating a DM with an AM” on page 144.
7. Choose OK to confirm the Alarm Manager configuration record.
NOTE
You can use a screen list created for a display manager configuration in an Alarm
Manager configuration.
To Import Choose
Only the selected schemes or records Selected Records
Only
Lower-level referenced records within the schemes. All Referenced
For example, the Alarm Manager property scheme ref- Records
erences a User Interface Scheme for each display, and
each UI Scheme references an Alarm Format Scheme.
Configuring AM Properties
Configuring Alarm Manager Class and Environment Properties
158
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
To Choose
Start automatically at boot time Boot
Start manually Operator
Start manually (displays more slowly than Operator class) Engineer
Start manually (for viewing process information only, or for View Only
remote users where process security is an issue). Process
variables cannot be set; they can only be read.
NOTE
Environment script files contain access code information and passwords to ensure
security access. Refer to Workstation Configuration (B0193AG) and Display Man-
ager/FoxView Calls (B0193DF) to learn about environment script files.
6. Choose OK.
The Command List dialog box appears, listing all the Alarm Manager commands.
4. Perform an action:
To Do This
Add a Select the appropriate command. The command appears in
command the Edit box. Select the line in the list box where the com-
mand is to be added and click the Add button. Click OK.
Edit a In the list box, double-click the command to display it in the
command Edit box. Edit as required in the Edit box. Click the Replace
button to replace the command. Click OK.
Replace a Click the prompt button to access the list of commands.
command Select the appropriate command. Select the command in the
list box to be replaced and click the Replace button. Click
OK.
Delete a Select the entry in the list box and click the Delete button.
command Click OK.
160
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
The options in the Alarm Manager Display Type dialog box will vary, depending on
the display type. Refer to the above table.
NOTE
Each User Interface scheme uses information (records) from a customizable Alarm
Format scheme.
NOTE
Click the EDIT window or the title bar of the Alarm Manager Display Type dialog
box (or border) to bring the EDIT window to the foreground for sizing or entering
configuration information.
162
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
2. From the User Interface Scheme dialog box, click on the EDIT window to bring it to
the foreground.
3. In the EDIT window, click the command button to be configured.
The Pushbutton Editor dialog box appears.
4. In the Pushbutton Editor dialog box’s Label field, type the button name (up to 32
characters). For example, type “Ack Alarm”.
5. In the Label field, type the button name (up to 32 characters). For example, type
“Ack Alarm”.
For multi-line button names, use “\n” (a backslash character and an lower-case N) in
the button name to indicate the start of a new line in the character string.
6. In the Access Code field, type the desired protection code associated with the button.
Valid access codes are 0-255. For example, type “0”.
7. Perform one of these actions.
♦ Type the desired command.
♦ Choose the prompt button to access the list of available commands.
a. Select the appropriate command(s) for the button. For example, select “ackalm”.
The command appears in the Edit box.
b. Perform an action:
To Do This
Add a Select the line in the list box where the command is to
command be added and click the Add button. Click OK.
Edit a Double-click the command in the list box to display it
command in the Edit box. Edit as required in the Edit box. Click
the Replace button to replace the command. Click
OK.
Replace a Select the command in the list box to be replaced and
command click the Replace button. Click OK.
Delete a Select the entry in the list box and click the Delete
command button. Click OK.
c. To add additional commands to an entry, choose the prompt button again and
select the additional command for the menu entry action. Choose OK. Select the
position of the new command and choose Add. Repeat as required.
8. Choose OK to confirm the button command.
NOTE
The following procedures assume that the ADMC is open, you have opened an AM
database, and you have selected a particular user interface scheme.
NOTE
A menu entry can have a command or a lower-level submenu associated with it.
164
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
To create a submenu
After having chosen New Submenu, the Menu Editor dialog box appears. Enter the data associ-
ated with that submenu.
1. In the Name field, enter the name of the submenu.
2. Define the entries for the submenu by clicking the New Command button.
3. In the subsequent dialog boxes, enter the required information and choose OK for
each entry required.
4. Choose OK to confirm the new submenu name and the associated entries.
5. Choose OK to return to the Menu Editor dialog box, displaying the configured
menu bar or pop-up field entries.
To create a separator
1. From the appropriate Menu Editor dialog box, select the list box entry over which the
separator is to appear.
2. Choose New Separator.
To reposition an entry
1. From the appropriate Menu Editor dialog box, select an entry in the list box.
This is the entry that you want to reposition.
2. Choose Cut.
3. Select the new location in the list box.
4. Choose Paste.
5. Choose OK to confirm the change.
166
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
Access codes enable or disable command availability, depending on the Environ-
ment script file associated with the Alarm Manager using this user interface. Plan
your security measures accordingly. Refer to Workstation Configuration
(B0193AG) and Display Manager/FoxView Calls (B0193DF).
c. In the Mnemonic field, type the letter (for example, S) for alternate access to the
menu entry. This letter must be a character in the label.
4. Click the prompt button.
A list of available commands appears in a Command List dialog box.
5. Select the appropriate command(s) for the menu entry label (for example,
save_to_file) and choose OK.
The command appears in the Button Actions box on the Menu Command Editor
dialog box.
6. Perform an action:
NOTE
If you do not select the position of a new command, it is added at the end.
To Do This
Add a Select the line in the list box where the command is to be added
command and click the Add button. Click OK.
Edit a Double-click the command in the list box to display it in the
command Edit box. Edit as required in the Edit box. Click the Replace
button to replace the command in the desired location.
Replace a Click the prompt button to access the list of commands. Select
command the appropriate command. Select the command in the list box
to be replaced and click the Replace button. Click OK.
To Do This
Delete a Select the entry in the list box and click the Delete button.
command
NOTE
This example shows how to add a submenu to one of the menu bar's fields. Use the
same procedure to add a submenu to a cascading menu by first navigating to the
menu position.
1. From the Menu Editor dialog box, perform one of these actions:
♦ Select the menu and choose Edit.
A dialog box opens with the name of the selected menu in the title bar.
Select a position and click New Submenu button.
♦ Select the location for the new entry and then click the New Submenu button.
The Menu Editor dialog box for that entry appears.
By default all new entries appear at the bottom of the current list.
2. Select fields as follows:
a. In the Name field, type the name of the menu.
b. Choose New Submenu.
c. In the subsequent Menu Command Editor and Command List dialog boxes,
enter the required information and choose OK.
d. Repeat for each entry required in the submenu.
e. Choose OK to confirm the new menu name and the associated entries.
f. Choose OK.
The Menu Editor dialog box appears, displaying the configured menu bar field
entries.
168
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
To create a separator
1. From the Menu Editor dialog box, select the entry over which the separator is to
appear.
2. Choose New Separator.
The separator appears above the selected entry.
To reposition an entry
1. From the Menu Editor dialog box's list box, select the entry to be repositioned.
2. Choose Cut.
3. Select the new location in the list box.
4. Choose Paste.
5. Choose OK to confirm the change.
NOTE
This procedure assumes that appropriate Alarm Format Scheme are available. If
they are not, refer to “Configuring an Alarm Format Scheme” on page 173.
To customize a User Interface scheme’s layout (rows and columns) and Alarm Format Scheme
1. From the ADMC’s main browser window:
♦ Choose User Interface and New.
♦ Choose Template from the Edit menu to customize the template.
♦ Choose User Interface, selecting a scheme from the list box, and choosing Edit to
edit an existing User Interface scheme.
The User Interface Scheme name is automatically generated with “UI” and a four-
digit number (0000-9999) starting with 0000 and skipping any existing UI names
with four-digit numbers. You can type the User Interface Scheme name. Valid charac-
170
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
ters include upper or lowercase alphanumeric characters, period (.), hyphen (-), and
underscore (_).
You cannot edit the name of a User Interface Scheme template.
2. Click the Alarm Format Scheme combo box.
A list of available schemes appears.
3. Select the desired Alarm Format scheme, or type a name.
If the desired scheme(s) are not available, refer to “Configuring an Alarm Format
Scheme” on page 173.
4. From the Alarm Rows box and Alarm Columns box, type the number of alarm rows
and alarm columns for the display.
5. From the Button Rows box and Button Columns box, type the number of button
rows and button columns for the display.
6. Choose Preview to view the layout in the EDIT window.
Refer to:
♦“Configuring a User Interface Scheme’s Command Buttons” on page 162
♦ “Configuring a User Interface Scheme’s Pop-Up Menu” on page 164
♦ “Configuring Double-Click Action” on page 171
♦ “Configuring a User Interface Scheme’s Menu Bar” on page 172
7. Choose OK to confirm the UI Scheme configuration.
NOTE
You cannot edit the name of a User Interface Scheme template.
To Do This
Add a Select the line in the list box where the command is to be added
command and click the Add button. Click OK.
Edit a Double-click the command in the list box to display it in the
command Edit box. Edit as desired. Click the Replace button to replace
the command. Click OK.
Replace a Select the appropriate command. Select the command in the
command list box to be replaced and click the Replace button. Click OK.
Delete a Select the entry in the list box and click the Delete button.
command Click OK.
5. If you require that multiple commands be performed for the double-click action,
repeat Steps 3 through 4.
6. Choose OK to confirm the command assignment.
NOTE
The arrow is to the right of the menu bar entry fields.
The Menu Editor dialog box appears. Without any defaults, <empty> appears in the
menu bar.
172
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
Examples
These examples show how keywords and text are used to create alarm messages on alarm displays.
The text between “<” and “>” is interpreted as a keyword. Other text is simply echoed.
The following is displayed as indicated below the formatted text:
If a message item is to be displayed starting in a certain column location, it must be the first item
in a separate field. A single concatenated field, for example, is formatted and appears as follows
(time information does not start in specific location):
Multiple fields are formatted and appear as follows (time field starts in the specified location):
To configure the default font for the alarm cell and the indicator font
1. Perform one of these actions:
♦ To edit alarm format fonts, from the ADMC’s main browser window, click the
Alarm Formats button, select an existing alarm format from the list box, and
choose Edit.
♦ To create a new Alarm Format scheme, from the ADMC’s main browser window,
click the Alarm Formats button and New.
174
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
The Alarm Format Scheme name is automatically generated with “AF” and a four-
digit number (0000-9999) starting with 0000 and skipping any existing AF
names with four-digit numbers. If you choose, type an Alarm Format name. Valid
characters include uppercase and lowercase alphanumeric characters, period (.),
hyphen (-), and underscore (_).
The Alarm Format Scheme dialog box appears.
2. From the Alarm Format Scheme dialog box, click the Default Font button.
The Fonts and Colors dialog box appears.
3. From the Fonts and Colors dialog box, click the Font Selection button.
The Font dialog box appears.
4. Select the default font for alarm cells.
5. Choose OK to return to Fonts and Colors dialog box.
6. If you do not want to change the foreground and background colors, choose OK.
to return to the Alarm Format Scheme dialog box. If you want to change these colors,
refer to “Configuring Foreground and Background Colors for Alarm Cells” on
page 175.
7. From the Alarm Format Scheme dialog box, click the Indicator Font button to change
the default font for the indicator for the alarm state (alarm priority or return-to-nor-
mal indicators) and acknowledgment state (acknowledged or unacknowledged indica-
tors).
8. From the Fonts and Colors dialog box, click the Font Selection button.
The Font dialog box appears.
9. Select the default font for the indicators.
10. Choose OK to return to Fonts and Colors dialog box.
If the Alarm Format scheme configuration is complete, choose OK. Otherwise, configure the
other configurable items such as alarm cell colors, indicators for alarm states and acknowledge
states, and time and date format.
To configure the system dynamic colors (as set in the init.user file)
1. From the Alarm Format Scheme dialog box, click the Default Font button or the Indi-
cator Font button.
The Fonts and Colors dialog box appears.
2. From the Fonts and Colors dialog box, select Use System Dynamic Colors.
NOTE
Options in the init.user file define alarm priority colors for unacknowledged and
acknowledged alarms.
3. Choose OK.
If the Alarm Format scheme configuration is complete, choose OK. Otherwise, configure the
other configurable items such as alarm cell fonts, indicators for alarm states and acknowledge
states, and time and date format.
176
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
The indicators are displayed in the current font. The keywords in the alarm cell that
represent indicators are:
If the Alarm Format scheme configuration is complete, choose OK. Otherwise, configure the
other configurable items such as alarm cell fonts, colors, and time and date format.
NOTE
Default cell formats are used unless you have customized alarm cell contents.
The following procedure assumes that the ADMC window is open, you have opened an AM con-
figuration, that you have selected an alarm format scheme, and that you have the Alarm Format
Scheme dialog box and EDIT window open.
1. In the Alarm Format Scheme Name box, type the name of the alarm format scheme
you want to configure.
2. Click the Cell Format Editor button.
The Cell Format Editor dialog box appears.
3. In the Character Rows field, type the font grid size (cell height) of the alarm cell.
4. In the Character Columns field, type the font grid size cell width.
NOTE
The columns assume average-size characters. There are limitations in the aspect
ratio when proportional fonts are used.
5. Click Apply.
6. View the grid in the EDIT window.
Configure the alarm entry information as needed.
2. Click the Prev button and the Next button to move through the list of alarm classes
and alarm types within those classes.
178
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
NOTE
Alarm types initially default to the settings in the generic alarm classes. When cus-
tomizing alarm types, click the Initialize button to view a copy of the generic alarm
classes as a starting point for customization. An alarm type with no configured fields
uses the defaults of the alarm class to which it belongs. Changing generic alarm class
defaults affects only default alarm types. Previously customized alarm types are not
affected.
NOTE
To expand characters for emphasis, grab handles and stretch vertically. The font size
increases in proportion to the height of the rows. For example, if the characters are
two rows high, the characters become twice as wide due to the aspect ratio.
NOTE
The configured cell fills the screen. The next configured cell displays alternately
with the previous cell(s).
7. If you want to change the font and/or colors for a selected field or alarm type cell,
refer to “Overriding the Font for a Selected Alarm Entry Field” on page 180.
8. When all of the cell entry information for the various alarm types have been config-
ured as needed, choose OK.
180
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
3. From the Fonts and Colors dialog box, select the desired font and/or colors for the
entire alarm cell.
4. Choose OK.
5. From the Cell Format Editor dialog box, choose OK when all the desired information
has been configured.
To clear the override (field or cell) and return to the default font and color
1. From the Cell Format Editor dialog box, select the field or cell with a font override
assignment.
2. Click the Cell Font Override button or the Field Font Override button.
The Fonts and Colors dialog box dialog box appears.
3. Choose Clear.
NOTE
The text between angle brackets (< and >) is interpreted as a keyword. Other text
is echoed.
NOTE
In the above example, multiple fields are formatted.
Command
Buttons CAD MRA NEWALM UNACK ACKED AHD OPR
Ack Alarm X X X X
Ack Compound X X X X
Ack Page X X X X
Clear Alarm X X X X X
Clear Page X X X X X
Alarm Detail X X X X X X
Top Priority X X X X X X X
User Display X X X X X
Block Detail X X X X X X
Historian X
Environments X
182
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
Default Menus
Menu/Menu Options CAD MRA NEWALM UNACK ACKED AHD OPR
File X X X X X X X
Save X X X X X
Print X X X X X
(NT)
Dismiss X X X X X X X
Exit X
Edit X X X X X
Select All X X X X X
Deselect All X X X X X
Find Alarms X X X X X
View X X X X X X
Refresh X X X X X X
Enable View All
Mode X X X
Disable View All
Mode X X X
Match Alarms X X X X X X
Go To Page X X X X X
Hide Controls X X X X X X
Displays X X X X X X X
Current Alarms X X X X X X X
Most Recent Alarms X X X X X X X
New Alarms Summary X X X X X X X
Unacknowledged Alarm X X X X X X X
Summary
Acknowledged Alarm X X X X X X X
Summary
Alarm History X X X X X X X
Operations X X X X X X X
Horns X
Silence Horns X
Mute Horns X
Mute CAG Horns X
Unmute Horns X
Unmute CAG Horns X
184
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
Alternative Configurations
Foxboro provides alternative User Interface schemes and AM Property schemes located in the
/usr/fox/customer/alarms/cfg directory. These have been created for alternative Pre-V4.2 configu-
rations. Select these schemes for additional customization.
Alarm Format schemes are named foxCADdbl (2-line entry) or foxCADsgl (1-line entry).
Alarm Display AM Property User Interface
Configuration File Type Scheme Scheme
CAD1WN.cfg CAD oldCAD1wn foxCAD1wn
AHD foxAHD10wn
CAD2WN.cfg CAD oldCAD2wn foxCAD2wn
AHD foxAHD20wn
CAD3WN.cfg CAD oldCAD3wn foxCAD3wn
AHD foxAHD10wn
CAD4WN.cfg CAD oldCAD4wn foxCAD4wn
AHD foxAHD20wn
CAD1WF.cfg CAD oldCAD1wf foxCAD1wf
AHD foxAHD10wf
CAD2WF.cfg CAD oldCAD2wf foxCAD2wf
AHD foxAHD20wf
AM Property
Scheme Description
foxDefault Foxboro defaults. The foxDefault AM Property scheme appears in the
list box when a new file is initialized with standard defaults.
186
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
AM Property
Scheme Description
foxFullScreen Full screen (recommended for Windows Off Mode)
foxQuarter Quarter screens
foxOldCAD Old style CAD/AHD
foxFullSq Full screen with large square buttons and alternative alarm formats
foxStrips Vertical and horizontal strip displays
foxGrids Grid-type displays
NOTE
The foxFullSq, foxStrips, and foxGrids schemes achieve effects, such as different
alarm formats, square buttons for touchscreens, strips and grids. Use elements of
schemes as a starting point for customizing your site’s schemes.
These are the User Interface schemes and Alarm Format schemes referenced in the alternative AM
property schemes:
User Interface Referenced Alarm
Scheme Format Scheme Description
foxHStrip1 foxMRA Horizontal strip with one alarm
foxHStrip2 foxShort1 Horizontal strip with column of five alarms
foxHStrip3 foxShort3 Horizontal strip with one alarm
foxMRAGrid foxShort1 Grid with column of five alarms
foxVStrip foxNumbered Vertical strip w/numbered alarms
Alarm Format
Scheme Description
foxCAD Default for CAD, AHD, and summary displays*
foxMRA Default for MRA*
foxSummary1 Alternative format for CAD, AHD, and summary displays
foxSummary2 Same as foxSummary 1 using Dingbats;
Compound:Block.Parameter fields--dynamic color
foxShort1 Block name, alarm type, statuses--dynamic color for all
foxShort2 Alarm state, optional text
foxShort3 Compound:Block, alarm type, statuses--dynamic color for all
foxShort4 Block name--dynamic color
foxNumbered Simple example showing how to number alarm entries
*These default Alarm Format schemes automatically appear in the list box when a new file is initialized
with the standard defaults.
NOTE
This is a pref to the AM's command variable (amcmd), not to the display manager's
command variable (dmcmd).
To use these as the basis upon which to add or modify the base configuration
♦ Type:
cd /usr/fox/customer/config
uncompress oldFoxboro.am
cp oldFoxboro.am <yourname>.am
(this preserves the original)
Refer to “Alternative Configurations” on page 185 for the names of the User Interface Scheme
and Alarm Property Scheme created for this alternative set of configurations. Select these schemes
for additional customization. The Alarm Format Schemes are named either foxCADdbl (2 line
entry) or foxCADsgl (1 line entry).
Modify the User Interface Schemes for these items:
♦ Button labels
♦ Button commands
♦ Button access classes
188
5. Using the Alarm/Display Manager Configurator B0193RV – Rev E
The CAD5WF.cfg and CAD5WN.cfg configuration emulates the V4.1 CAD, but adds access to
many of the new Alarm Manager features through the additional Operations button located at the
bottom-right of the CAD window. Clicking the Operations button displays the References
The AM knows that it is running in Windows Off mode, and instead of attempting to close the
Current Alarm Display window, the AM automatically moves the DM window forward.
/usr/fox/alarms/show_dm is a display manager script that brings the DM’s display window for-
ward (to the front of the AM’s CAD window). The CAD window is still active behind the DM
window.
The contents of this script file is:
dmcmd script
dmcmd run /usr/fox/wp/bin/tools/show_win "FOXBORO: Display
Manager $GCLBUG:$DMNAME"
In Windows Off mode, the AM maintains only one of its display windows open at a time.
In Windows On mode, up to seven AM windows may be open at the same time.
190
6. Tutorial – Configuring AMs and
DMs with Standard Defaults
This chapter is a tutorial that shows how to use standard defaults to quickly configure display
managers and Alarm Managers on a local Model 51 Application Workstation.
The steps in this tutorial configure a dual-headed AW51 (letterbug 54AW51) with:
♦ Three display managers (DMs)
♦ A bootable DM for an operator dedicated to both heads (54AW51)
♦ A DM for an auxiliary operator; undedicated (DM0000)
♦ A DM an for engineer; undedicated (DM0001)
♦ Two Alarm Managers (AMs)
♦ An AM for an operator dedicated to both heads (54AW51)
♦ An undedicated AM for an operator (AM0000)
Refer to other parts of this document for a description of the Alarm/Display Manager Configura-
tor and detailed procedural information.
NOTE
Only the end of the file is shown; the initial descriptive information has been omit-
ted to save space.
191
B0193RV – Rev E 6. Tutorial – Configuring AMs and DMs with Standard
#
#SCREEN <screen_variable> <monitor1> <monitor2> . . . .
#
#TYPE <type> <window attributes> <class> <environment>
#
TYPE Operator - B Proc_Op_Env
TYPE AuxillaryOper QLRSM O Proc_Op_Env
TYPE RemoteOperator - O Proc_Op_Env
TYPE Engineer - E Proc_Eng_Env
TYPE View_Only - V -
#
#AMTYPE <type> <class> <environment>
#
AMTYPE Operator B Proc_Op_Env
AMTYPE AuxillaryOper O Proc_Op_Env
AMTYPE RemoteOperator O Proc_Op_Env
AMTYPE Engineer E Proc_Eng_Env
AMTYPE View_Only V - -
#
#NAME <lbug> <dmname> <dedicated monitor(s)> <type>
NAME 54AW51 54AW51 .0 -
192
6. Tutorial – Configuring AMs and DMs with Standard Defaults B0193RV – Rev E
NOTE
If the local dmcfg file had previously been configured (pre-Release 4.2) with multi-
ple DMs, the DM names and configuration information is loaded into the dmcfg
configuration file with the default DM property schemes.
3 8
a c
b
Leaving the Display Manager Property Scheme field blank automatically supplies Foxboro
defaults.
A display manager accesses the Alarm Manager with the same name or the Alarm Manager with
which it is associated. See “Associating the DMs and AMs” on page 197.
Configure the other two display managers and associate them with the same Alarm Manager
(AM0000).
194
6. Tutorial – Configuring AMs and DMs with Standard Defaults B0193RV – Rev E
Field Setting
Display Manager Name DM0000 (this is automatically generated)
Station Letterbug 54AW51
Screen Undedicated
Display Manager Property Scheme Auxiliary Operator
Field Setting
Display Manager Name DM0001 (automatically generated)
Station Letterbug 54AW51
Screen Undedicated
Display Manager Property Scheme Engineer
NOTE
An Alarm Manager named 54AW51 was automatically created earlier by having
selected the Create Alarm Manager check box on the Display Manager dialog box
when you configured the 54AW51 display manager. Refer to “Configuring the Dis-
play Managers” on page 193.
2 54AW51 3
54AW51
1
a c
b
196
6. Tutorial – Configuring AMs and DMs with Standard Defaults B0193RV – Rev E
Field Setting
Alarm Manager Name AM0000 (automatically generated)
Station Letterbug 54AW51
Screen Undedicated
Alarm Manager Property Scheme FoxDefaults
Leaving the Alarm Manager Property Scheme field blank automatically supplies Foxboro defaults.
NOTE
The display manager named 54AW51 and the Alarm Manager named 54AW51 are
already associated.
5
3 4
The Display/Alarm Manager Associations dialog box creates an association between a display
manager and an Alarm Manager for alarm display call-up when the Alarm button in an I/A Series
environment is pressed. When configured, multiple display managers can access the same Alarm
Manager.
3
2
1. From the File menu, choose Save. The Save Configuration As dialog box
appears.
2. Type the name of the configuration file (/usr/fox/customer/config/boiler1) in
the File Name text box. An .am extension is automatically supplied.
3. Choose OK.
NOTE
If an error is located during validation, the install files are not created.
198
6. Tutorial – Configuring AMs and DMs with Standard Defaults B0193RV – Rev E
1. From the File menu, choose Create Install Files. A Progress Log
message box appears.
2. Choose Save to File to save a record of the installation file names and
locations in a log file. Type the filename and choose OK in the subsequent dialog
box. The.log file is written in the directory created for the install files for each
workstation (usr/fox/customer/config/boiler1.dir/boiler1.log).
3. Choose Done.
Files Description
/usr/fox/customer/config/boiler1.am Alarm Manager
database file
/usr/fox/customer/config/boiler1.dir/dmcfg display manager
configuration file
/usr/fox/customer/config/boiler1.dir Letterbug AM
/54AW51/54AW51.cfg configuration file
/usr/fox/customer/con- Second AM
fig/boiler1.dir/54AW51/AM0000.cfg configuration file
200
6. Tutorial – Configuring AMs and DMs with Standard Defaults B0193RV – Rev E
Files Description
/usr/fox/customer/con- Log file of generated
fig/boiler1.dir/boiler1.log install files (optional)
Destination Directories
Source Files and Files
/usr/fox/customer/config/boiler1.dir/dmcfg /usr/fox/customer/hi/dmcfg
/usr/fox/customer/config/boiler1.dir /usr/fox/customer/alarms/cfg
/54AW51/54AW51.cfg /54AW51.cfg
/usr/fox/customer/config/boiler1.dir /usr/fox/customer/alarms/cfg
/54AW51/AM0000.cfg /AM0000.cfg
202
7. Tutorial – Customizing an Alarm
Manager
This tutorial shows you how to customize an Alarm Manager.
The AM database (.am file) is used to create Alarm Manager configuration (.cfg) files for your
site. The following tutorial uses the Alarm/Display Manager Configurator (ADMC) to edit the
.am file. The tutorial shows you how to:
♦ Add a command button to an alarm display
♦ Change a button’s access class
♦ Change the number of alarms on an alarm display
♦ Add a tenths of a second field to the timestamp of an analog alarm message
♦ Add a command to a menu and create a submenu with a separator
The tutorial assumes that you have the Alarm/Display Manager Configurator’s main browser win-
dow open and that you are going to modify the foxDefault AM property scheme.
! CAUTION
Verify that you open the correct .am file before making modifications. There may
be many .am files in the directory.
203
B0193RV – Rev E 7. Tutorial – Customizing an Alarm Manager
204
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
5. Look at the User Interface Scheme field in the Alarm Manager Display Type dialog
box and record the name of the User Interface scheme used by the CAD.
In this example, the CAD uses the foxCAD User Interface scheme.
6. Click OK to close the dialog box.
7. Click OK to close the Alarm Manager Property Scheme dialog box.
8. From the main browser window, choose User Interfaces.
9. Under “User Interface Scheme Name”, choose foxCAD.
10. Click Edit.
The User Interface Scheme dialog box and EDIT window appear.
206
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
20. Delete the descriptive information and type 1, which indicates the first page.
208
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
210
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
27. From the User Interface Scheme dialog box, click OK.
28. From the Alarm Manager Property Scheme dialog box, click OK.
Deleting a Button
Deleting a button follows many of the steps previously described under “Adding a Command
Button to the CAD” on page 203. When you delete a button, you can:
♦ Delete the command associated with the button, which disables the button
♦ Delete both the command that the button runs and the button’s label
Either way, clicking the button runs no command.
To delete a button
1. Choose a user interface scheme from the ADMC’s main browser window.
2. Click the Edit button.
3. From the EDIT window, click the button that you want to delete. For example, click
the Clear Page button.
The Pushbutton Editor dialog box appears.
212
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
3. Click Edit.
The User Interface Scheme dialog box and EDIT window appear.
4. In the EDIT window, click the button whose access class you want to change.
The Pushbutton Editor dialog box appears.
5. In the Access Code field, type an access class.
For example, change the access class from 0 to 1 to restrict the button’s use.
6. Click OK.
7. From the User Interface Scheme dialog box, click OK.
Moving the dark line downward decreases the size of the buttons and increases the size
of the alarm entry area.
The number of alarm entries remains the same.
5. In the User Interface Scheme dialog box’s Alarm Rows field, type the number of alarm
rows. Use 6 in this example.
6. In the User Interface Scheme dialog box’s Alarm Columns field, type the number of
alarm columns. Use 3 in this example.
NOTE
The product of the number of rows and number of columns yields the number of
alarm entries on the display.
214
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
8. From the Alarm Manager Property Scheme dialog box, click OK.
216
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
5. In the Alarm Type field at the bottom of the Cell Format Editor dialog box, select
ANALOG.
6. In the Select Field list box, select <SystemTime[1-14]>.
<SystemTime[1-14]> is copied to the Alarm Field Editor text box.
7. In the Alarm Field Editor text box, type . (a period) after <SystemTime[1-14]>.
The period is the separator between the units and tenths digits.
Note that while the same display mechanism is used for the Alarm History display as
for other displays, only a subset of alarm data fields is valid for historian alarms. This
means that you should not customize the Alarm History format for a 10th of a second
alarm value. If you do, a 0 (zero) is displayed for the 10th of a second alarm value
when called up in Alarm History. The return to normal 10th of a second value will
not display the intended data in Alarm History. The Alarm History display does not
integrate with this feature of the AMDM.
8. In the Alarm Message Items list box, select Tenths.
9. Click the Add Item button.
<Tenths> appears after the period after <SystemTime[1-14]>.
10. Click the Apply button.
NOTE
Since two additional characters (a period and a digit) have been added to the Sys-
temTime field, as follows, you must now adjust the fields to the right of the System-
Time field to accommodate the addition of two new characters.
11. Click the title bar of the EDIT window to activate this window.
12. Click the window’s handle (corner of window) and drag it to increase the window’s
size.
This is necessary to view the details in this window.
13. Using the mouse, select the bottom-right corner of the SystemTime field and drag it
to the right.
NOTE
Dragging the side of this field moves this field, but does not change its size.
Watch as the field’s Width indicator (below the menu bar) changes to 16.
218
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
5. In the Menu Entries list box, click the menu bar field (for example, File) in which to
add a new command.
6. Click the Edit button.
A dialog box appears with the name of the menu bar field in the title bar.
NOTE
Access codes enable or disable command selectability, depending on the Environ-
ment script file associated with the Alarm Manager using this user interface scheme.
Plan your security measures accordingly. Refer to Workstation Configuration
(B0193AG) and Display Manager/FoxView Calls (B0193DF).
c. In the Mnemonic field, type the letter (for example, S) for alternate access to the
menu entry. This letter must be a character in the label.
9. Click the prompt button.
The command appears in the Menu Entries list box in the File dialog box.
If you did not select the position of the new command, it is added at the bottom of
the list.
11. Click OK.
The Menu Editor dialog box appears.
Creating a Submenu
This procedure creates a menu item that opens into a submenu.
1. From the Menu Editor dialog box, select the menu (for example, File).
2. Click the Edit button.
The Menu Editor dialog box for that entry appears.
220
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
222
7. Tutorial – Customizing an Alarm Manager B0193RV – Rev E
2. Select “Find”.
The new separator will be placed above the selected command.
3. Exit the dialog boxes by clicking OK.
The separator appears above the selected entry as a light gray line.
224
8. Emulating Pre-V4.2 Alarm
Displays
This chapter describes options available to sites that choose to emulate the Current Alarm
Display (CAD) and the Alarm History Display (AHD) of the pre-V4.2 software.
Refer to Chapter 4 “Configuring Alarm Managers and Display Managers” to learn how to config-
ure alternative defaults.
225
B0193RV – Rev E 8. Emulating Pre-V4.2 Alarm Displays
elect to use these alternative configurations to emulate the old style (pre-V4.2) Display Manager
CAD and AHD.
NOTE
Using these alternative configurations greatly reduce access to many of the Alarm
Manager’s powerful features such as access to the alarm summary displays, which
show updating alarm parameters.
226
8. Emulating Pre-V4.2 Alarm Displays B0193RV – Rev E
The following table identifies the alternative set of configuration files, located in the /usr/fox/cus-
tomer/alarms/cfg directory, that may be used to emulate the Pre-V4.2 Display Manager alarm
displays.
The CAD5WF.cfg/CAD5WN.cfg configuration emulates the V4.1 CAD, but adds access to many
of the new V4.2 features through the additional Operations button located at the bottom-right of
the CAD window (see Figure 8-2). Clicking the Operations button displays the new Operations
Display window (see Figure 8-3).
Operations Display
From the Operations display, you can:
♦ Access the four new alarm display windows
♦ Mute or unmute alarm horns (either locally or throughout the Common Alarm
Group)
♦ Change Alarm Manager user environments
228
8. Emulating Pre-V4.2 Alarm Displays B0193RV – Rev E
230
Index
A
AApan File 52
AAtab File 52
Access Class 4, 28
changing 145
Access Key Lock Commands 28
Access Level
setting 29
ACKCLR 43
ACKED 68
Acknowledge State
customizing indicators 176
Acknowledged Alarms Display 68
addalmpnl 60
ADMC 111
accessing 192
description of 111
AHD 70
Alarm
accessing a specific display 97
acknowledging 73
adding a tenths field 203
analyzing alarm conditions 98
backing up 49
configuration overview 8
database attributes 1
default color codes 64
detail information 78
entries in an alarm display 64
fields in the message 80
finding 74
invoking another application 18
message 13
notification 7
printing detail information 78
process 8, 9
231
B0193RV – Rev E Index
recovering information 15
saving detail information 78
state and status indicators 64
suing a different format 186
top priority alarm 73
updating alarm text in a process display 46
viewing detailed information 91
Alarm Alert
subsystem 7
Alarm Alert Database 52
changing options 38
configurable options 13
configuring 13, 38
customizing 18, 39
description of 39
Alarm Cell
configuring contents 178
configuring font grid 177
customizing color 175
Alarm Detail Button 78
Alarm Display
accessing another window 72
Alarm History Display 70
capabilities 17
configuring 63
configuring attributes 160
configuring capabilities 17
current 65
Current Alarm Display 21
iconified 73
Most Recent Alarm 21
parts of 63
positioning 145
refreshing 92
setting Clear Alarm button action 42
setting the initial 41
Alarm Displays 225
alarm area 79
customizing 82
description of 20
examples of 119
list of 63
multiple 26
pop-up menu 81
printing information 100
saving 99
working with 72
Alarm Entry
configuring location and size 179
232
Index B0193RV – Rev E
233
B0193RV – Rev E Index
234
Index B0193RV – Rev E
235
B0193RV – Rev E Index
control assignments 52
display call up 32
keypress actions 52
lights 32
Associating DMs and AMs 197
AST commands 60
B
Block
ALMSTA parameter 9
Built-In Commands 18
Alarm Manager 54
Button
adding 203
Alarm Detail 78
changing access class 145, 203
customizing for match/filter operation 105
New Alarms 8, 15, 64, 65, 131, 159
Operations 227
Process 9, 24
Buttons
ADMC 136
Alarm Manager 87
alternative shapes 186
configuring 162
default 182
setting the number of rows and columns 171
C
CAD 65
setting update preference 49
CAD_UPDATES 49
CAG 35
File 50
Change Environment
enabling/disabling 28
Class
configuring for Alarm Manager 158
CLR_OPT 42
clralmpnl 60
Color
customizing for alarm cells 175
Colors
configuring blinking 44
Comma Separated Value Format 17
Command
access key lock 28
adding to a menu 203
236
Index B0193RV – Rev E
AST 60
changing access class 145
Command Buttons
adding 203
ADMC 136
changing access class 203
configuring 162
default 182
Command Interface
Alarm Manager 18, 28
Commands
Alarm Manager 51
Comma-Separated Value Format 99
commgrp.cfg File 50, 52
Common Alarm Group 35
configuring 35
horns 34, 46
Common Alarm Group File 50, 52
CONF_RTN 48
Configuration
alarm 1
decisions 125
Configuration Files
distributing 142
Connection Point
Object Manager 22
CSV Format 17, 99
Current Alarm Display 65
emulating the pre-V4.2 version 225
setting update preference 49
Windows On/Off Mode 190
D
Database
alarm alert 13, 18, 34, 36, 38
Database File
AM 129
Date
configuring format 177
Default AM
associating to an AM property scheme 145
default values 115
Detail Information
alarm 78
Display
Acknowledged Alarms Display 68
alarm 20
Alarm History Display 70
call up 36
237
B0193RV – Rev E Index
238
Index B0193RV – Rev E
E
Edit Menu
ADMC 135
Emulating pre-V4.2 displays 225
Environment
changing 109
configuring for Alarm Manager 158
current operating 16
selecting another 71
Environments 4
F
File
.am 52, 129, 198
.ams 103
.cfg 191, 201
AApan 52
AAtab 52
alarm match specification 102
alarms.cfg 226
am_def.cfg 52
commgrp.cfg 50, 52
Common Alarm Group 50
DM/AM properties 52
dmcfg 26, 52, 129, 191, 192, 199, 201
foxboro.cfd 52
horn.cfg 52
init.user 13, 14, 17, 18, 34, 38, 52
init.user.rel 38
File Menu
ADMC 135
Filter Specification
saving 77
Finding Alarms 74
Fonts
customizing for an Alarm Format Scheme 174
FoxBatch
handling of Confirm messages 48
foxboro.cfd File 52
FoxPanels
buttons 33
configurator 30, 31
control assignments 52
keypress actions 52
G
Grids
alternative 186
239
B0193RV – Rev E Index
H
Help
on-line 2, 3
Historian
accessing a remote 99
changing 99
interface 13
selecting a remote 70
Horn
external 33
internal 33
Horn Configuration File 52
horn.cfg File 52
Horns
setting resound action 45
setting silence action 46
working with 34, 108
HRN_OPT 46
I
init.user File 13, 14, 17, 18, 34, 38, 52
init.user.rel File 38
Init_Env Script 28
Install Files
creating 141
creating.am File
creating install files 198
distributing 200
K
Keyboard
annunciator 29, 31
Keyword
commands that use a keyword 50
customizing alarm messages 18
Keywords
Alarm Manager 52
formatting with 181
modifiers 54
L
LED
annunciator 32
LIA_OLDEST 47
Licenses
AM and DM 24
dedicated vs. undedicated 26
number of 24
240
Index B0193RV – Rev E
Light 32
Annunciator keyboard 32
List Box
ADMC 136
loadalmpnl 60
M
Main Browser Window
ADMC 134
Match Active 101
Match Criteria
for locating alarms 94
Match Filters
using 101
Match Specification
saving 77
Match/Filter Specification
clearing 104
Matching Alarms 74
MAX_ACTIONS 41
MAX_CAD 40
Menu
accessing a pop-up 91
creating a separator 169
creating a submenu 168
previewing a separator 169
repositioning an entry 169
Menu Bar
ADMC 134
Alarm Manager 85
assigning an entry 168
configuring 172
modifying a command 166
Menus
default 183
Message
alarm 13
Mode
View All 69, 78
Most Recent Alarm Display 67
Mouse
configuring double-click action 171
MRA 67
N
New Alarms Button 8, 15, 64, 65, 131
configuring 159
New Alarms Display 68
NEWALM 68
241
B0193RV – Rev E Index
O
OAJ 30
Object Manager
connection points 22
connections 4, 11, 21
updates 20
On-Line Help 2, 3
Operations Button 227
Operations Display 228
changing environment 28
parts of 70, 88
Operator
actions 9, 65
Operator Action Journal 30
P
Password 16
Pop-Up Menu
accessing 91
configuring 164
creating a separator 166
creating a submenu 166
editing commands 165
repositioning entries 166
Pop-up Menu
previewing 164
Pop-Up Menus
alarm display 81
default 184
Pre-Configuration
decisions 125
Pre-V4.2
differences 225
Pre-V4.2 CAD Emulation 4
Pre-V4.2 Configuration
alternative set of files 189
using 188
Pre-V4.2 Configurations 185
Printer
alarm message 13
Printing Alarm Information 100
Process Alarm 8, 9
Process Button 9, 24
configuring 29
state 24
Process Display
updating alarm text 46
Protection Class
changing 28
242
Index B0193RV – Rev E
prtalmpnl 60
R
RESOUND 45
RTN_DROP 41
RTNCLR 43
S
Scheme
definition of 112
importing the default 148
Schemes
alternative 118
AM and DM 117
examples of 117
relationship 113
saving 140
types of 117
Screen List
customizing 148
Security 27
Software
used with alarming 5
SORT_CFG 40
Strips
for touchscreens 186
Submenu
creating 203
Subsystem
alarm 7
Summary Displays 21, 68
examples of 69
T
Template 115
customizing 155
definition of 115
description of 117
editing 147
emulating pre-V4.2 displays 226
Templates
saving 140
using 137
Time
configuring format 177
Time/Date Modifiers 59
Top Priority Alarm
selecting 73
243
B0193RV – Rev E Index
U
UNACK 68
Unacknowledged Alarms Display 68
User Class 131
User Environment
changing 71
User Interface
Alarm Manager 84
User Interface Scheme
configuring 170
configuring buttons 162
configuring double-click action 171
configuring the menu bar 172
customizing 115
User Interface Schemes
alternative 185
V
V4.1
alarm displays 225
View All Mode 69, 78, 95
W
Window
dismissing 89
iconifying/minimizing 89
moving 90
opening 89
resizing 90
Windows
icon 90
Windows Off Mode 4, 26, 189
Windows On Mode 189
Worksheets
configuration 125
Workstation
alarm recovery 16
244
Index B0193RV – Rev E
245
B0193RV – Rev E Index