[foxboro] Alarm Manager - Unique Sounds / Filtering / Environments

As a custom app, we wrote a program to recieve alarm messages as
an OM Process on an AW.  Based on compound name, this program would
sett a bit of an OM object when an alarm matched one of a set of 
compounds.  The bits set in our case were passed thru a PLB block
to close FBM outputs which went to an electronic noise box.  Each
of seven outputs caused a different noise, each for a single plant
area.

We also had a scheme for using each ops console for a specific
plant area, but capable of adding any/all other plant areas to
its function. This meant that the alarm ack button would sometimes
silence one alarm sound, and at other times silence other (s).
We used horn.cfg to point each console to an IND block, Boolean
input.  That IND block also recieved the set bits from the 
costom program mentioned above.  Logic in the IND would decide
which horn was silenced by which console pushbutton.  Results
of this logic were what was actually sent to the afore mentioned
PLB.  Other inputs to the IND bllock showed which consoles were
being used for each process unit.

We had all alarms sent to all consoles, and to the custom program.
At each console we had filtering set up to only show the alarms for
the process unit(s) that console was covering at the time.  When
that mix of covered process units changed, the filter was changed 
with a script on the WP.  As all alarms went to all consoles, the
filter change showed immediate display of all relavant alarms.

Using Backup WP and Common alarm group configuration we had reliable
recovery of alarm functions after WP failures.

This scheme was first done in 2000/2001 on 6.1(6.2?) software, and 
has been upgaded a few times.  It now runs unmodified on 6.5.1.

So.  Other that being a show off, what's the point?

a) we couldnt find a better way to get multiple alarm sounds for
   different plant units while maintaining a console backup scheme.

b) (this is relavant to another thread being discussed today) use of
   alarm filters is viable in the IA alarm manager, even switching 
   them under program control, and on the fly, so to speak. This 
   is also true for alarm environment switching.  Both can be done
   quite effectively by program control, in responce to ops input,
   equipment failure, etc.

c) can't forget that external alarm functions use OM functions.
   This gives us a chance to get into the process with a little
   custom logic and tweak it to our specific needs.

d) our custom program might be replaced by CALC/LOGIC/IND blocks
   which monitor UNACK and ALMLEV parameters from compounds, and
   set/clear external alarm noise makers through FBM outputs.

Dare I say, "Just a thought" ?

Regards,

William C. Ricker
FeedForward, Inc.
Marietta, GA  USA
770.426.4422
wcricker @ feedforward.com
 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Dennis Stone
Sent: Tuesday, June 21, 2005 3:58 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Unique Alarm Sounds 


Our facility will have an integrated control room, 3 separate units
being operated by three separate operators from the same control room
with six screens per operating unit.  My problem is with alarming,
currently only one operator is operating from this control room now but
will be joined by another in a couple of months.  How can I
differentiate alarms based on sound so that each operating area has a
unique sound?  I tinkered with the built-in alarm sounds and these are
unacceptable due to lack of volume or tone.  Does anyone have any ideas
short of outputting the existing horn output to a distortion device and
then to an amp connected to a set of external speakers?
 

Any help would be greatly appreciated. 

 

Dennis Stone

Process Control Engineer

Hunt Refining Company

dstone@xxxxxxxxxxxxxxxx <mailto:dstone@xxxxxxxxxxxxxxxx> 

(205) 391-3345

(205) 391-3564 FAX

 


 
 
_______________________________________________________________________
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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: