Re: [foxboro] Alarm manager documentation
- From: "Grace, Kathy" <kathy.grace@xxxxxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 17:29:27 -0400
Tom,
Good point. You still have to send the alarms to all destinations from where
you want to view them.
The beauty with 8.0 is you can send your Unit 1 alarms to your Unit 2
workstations, your Unit 2 alarms to your Unit 2 workstations, etc. You can
then set up an AM on your Unit 1 workstation to view your Unit 1 alarms. You
can then set up a different AM on your Unit 1 workstation to view your Unit
2 alarms (even though they have never been sent to the Unit 1 workstations).
No way to view both Unit 1 and Unit 2 alarms on the same AM however without
sending both Unit 1 and 2 alarms to the workstation running the AM.
You can also switch an AM from viewing Unit 1 alarms to viewing Unit 2
alarms at runtime. Just configure a button to run the set_alarm_source
command.
8.0 AMS (Alarm Management System) also has a lot of other interesting
features, such as dynamic sorting. At runtime you can resort your CAD or
other AM displays (except the MRA and AHD). It uses the same sort options as
are available with SORT_CFG in init.user (RAPT, APT, AT, AP, T). In additon
a PT sort has been added. This is selectable through the match/filter (now a
tabbed match / filter / sort) dialog box.
Kathy
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: Tuesday, June 21, 2005 4:35 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Alarm manager documentation
Stan,
I haven't noticed that anyone has mentioned using the Common Alarm
Group to meet your needs. Even before we centralized our control room we
used this functionality to allow cross-functional ability to acknowledge,
silence horn, and clear alarms at two or more workstations. Here is an
example of what is possible with this tool. In Area One of a plant that is
controlled from one control room:
Operating Seat 1 controls Process 1, 2, and 3 using 01WP01 Operating Seat 2
controls Process 4, 5, and 6 using 01WP02
Alarms are sent from all compounds controlling Processes 1-6 to GRP 1 Which
contain both 01WP01 and 01WP02 as GRP 1 Devices. This means that any alarm
in Processes 1-6 will show up at, and audibly alarm at both 01WP01 and
01WP02. (If you want 01WP01 to receive only Process 1-3 alarms, but 01WP02
to receive Process 1-6 alarms, don't include 01WP01 as a device in Process
4-6 compounds)
Edit the file:
/usr/fox/alarms/commgrp.cfg on both 01WP01 and 01WP02
To look like the following:
# Common Alarm Group (CAG) Configuration File
#
# (CAD Redirection)
# WP CAG Backup BLK TOP USER CAG
# LBUG NAME1 LBUG DTL PRIO DISP NAME2
01WP01 AREA1------- ------ ------ ------ ------ ------------
01WP02 AREA1------- ------ ------ ------ ------ ------------
And then reboot both 01WP01 and 01WP02
With no filtering applied in the Alarm Manager you will be able to
see all alarms, (Process 1-6), on either Alarm Manager and can silence both
01WP01 and 01WP02 alarm horns from a single pick from either station. If
you acknowledge an alarm from the Alarm Manager on 01WP01 it will show
acknowledged on both 01WP01 and 01WP02. If you clear an alarm from the Alarm
Manager on 01WP02 it will clear on both 01WP01 and 01WP02. If you set up an
Alarm Manager filter on 01WP01 to exclude Process 4-6 compounds then you
wouldn't see those alarms on 01WP01 but would continue to see Process 1-6
alarms on 01WP02.
Is this the functionality you are looking for?
If what you want is for all alarms from a failed workstation to be
directed to another WP until the failed workstation is rebooted, you can
configure SysDef to use 01WP02 as Backup WP for 01WP01 and 01WP01 as Backup
WP for 01WP02. We have done this and it works well. The Device Manager
recognizes when a Device fails and then uses this configuration to redirect
all messages to the Backup WP.
Tom VandeWater
Control Systems Developer/Analyst
Dow Corning Corporation
Carrollton, KY USA
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of stan
Sent: Tuesday, June 21, 2005 9:10 AM
To: Foxboro List
Subject: [foxboro] Alarm manager documentation
I geuss it's time to learn how this stuff works :-)
Is there a good documentation that describes aalrm handling in general> We
are using DM if it matters.
--=20
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite
Vietcong Terror=20
- New York Times 9/3/1967
=20
=20 _______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at your
own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at your
own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
