Re: [foxboro] Alarm Management

  • From: "Ghodhbani, Hafedh" <hafedh.ghodhbani@xxxxxxxxxxxx>
  • To: 'Mark Dumond' <mdumond@xxxxxxxxxxxxxx>
  • Date: Tue, 09 Apr 2002 17:37:28 +0100

Mark,
I have copied to Excel alarms for one month.
could you please help how to use Excel in order to count
duplicate alarms. Do you use some macros?

Regards
Hafedh Ghodhbani
Senior C&I Engineer 
British Gas International

-----Original Message-----
From: Mark Dumond [mailto:mdumond@xxxxxxxxxxxxxx]
Sent: 08 April 2002 17:16
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Alarm Management



One of our recent projects here at FeedForward was to help a Foxboro
end-user reduce the number of nuisance alarms.

The approach we took was to identify which alarms occurred most frequently
over a period of time.  We then determined why these high-frequency alarms
were occurring, and took the necessary steps to reduce them.

We classified the results in to the following categories:
    1. Control Problems  (the alarm was caused by issues with the actual
Foxboro control configuration)
    2. Device Problems  (the alarm was caused by faulty devices in the
field)
    3. Process Problems (the alarm is valid, but something in the process is
causing the alarm)

In order to determine which alarms were occurring most frequently:
    1. I built a Unix script to capture alarms sent to the historian to a
file.
    2. After a period of time of capturing alarms (like a month or so), I
imported the alarms into Excel and had Excel count the number of duplicate
alarms
    3. I then sorted the spreadsheet on the number of duplicates
    4. We then went through the most frequent alarms, and determined the
reasons for them, and took the necessary steps to reduce them.

The utility we used to capture alarms in to an Excel spreadsheet is
available on our website for downloading (it has been for a while).  It is
called "Alarm Printer Simulator".  You can find it at:
http://www.feedforward.com/downloads.htm
This utility  assumes that you are using the Legacy historian, that you are
using an AW51, and that you are sending process alarms to the historian.  If
you don't meet this criteria, there are other ways to get your alarms listed
in to a flat file.

Also, there is another download utility that may help you on our website.
It is called "Alarm Report Utility".  This utility reports on all configured
alarms parameters in your system, and reports them to an Excel spreadsheet.
This may also help you out in your efforts.

I hope this helps.

Good Luck!
Mark Dumond
FeedForward, Inc
http://www.feedforward.com






-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of swardvc3@xxxxxxxxxxx
Sent: Monday, April 08, 2002 6:34 AM
To: Foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Alarm Management





Hi Everyone,

We are currently trying to reduce the numbers of process alarms on our
system,
especially when a unit shutdown occurs. We realise that there are a number
of
ways of doing this and know how most of them work, the question is which is
the
best? We have already gone through every alarm and reviewed its necessity
then
set its priority.
Our next phase is to start disabling alarms when they are not required. Mode
driving is one of the options we are considering, i.e. disabling of an alarm
if
it comes as a consequence of something else happening that also produces an
alarm.
I am very interested to hear from anyone who has tackled the problems of
excessive numbers of alarms successfully, what methods have you used and is
maintenance on the system more of a problem than it was previously.

Thanks in advance,

Simon

Simon Ward
VC3 Computer Engineer
VC3 Plant
Castner Kellner Works
Runcorn
Cheshire
WA7 4JE




--
**********************************************************************
The information contained in this message, and any files transmitted with
it, is strictly confidential, intended only for the use of the individual or
entity to whom it is addressed. If the reader of this message is not the
intended recipient, you are hereby notified that any reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this message is strictly prohibited.

If you have received this message in error, please notify us immediately
and destroy/delete the message from your computer.

Postmaster@xxxxxxxxxxx

EVC, 1 Kings Court, Manor Farm Road, Runcorn, WA7 1HR, UK
*************************************************************************



_______________________________________________________________________
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
 

_____________________________________________________________________
This message has been checked for all known viruses by the 
Message Labs Virus Control Centre.

______________________________________________________________________
BG Energy Holdings Limited (a member of BG Group)
Registered in England No: 3763515
Registered Address:
                        100 Thames Valley Park Drive
                        Reading
                        Berkshire   RG6 1PT   UK
Telephone:              +44 (0) 118 935 3222
Website:                http://www.BG-Group.com

This e-mail is intended only for the addressee named above.  As this 
e-mail may contain confidential or privileged information, please 
advise us immediately if you are not the named addressee or the person 
responsible for delivering the message to the named addressee.  The 
contents should not be disclosed to any other person nor copies taken.
______________________________________________________________________
 
 
_______________________________________________________________________
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: