Re: [foxboro] Alarms one line
- From: "Armour, Alan" <aarmour@xxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 26 Oct 2005 07:49:33 +1000
We have been using Matrikon's Alarm Management product (ProcessGuard)
for several years now.It works fairly well. We customised a database to
insert the alarm priority information into the alarm text after it
leaves the printer port. The latest version of ProcessGuard offers this
feature as standard, along with a "reverse engineered" Alarm database.
For later versions of operating systems Matrikon reccommend using OPC
protocol.We also developed an Operator Inhibited Alarm report which
extracts data from the operator action logs. This gives us a time stamp
so we can tell when alarms are inhibited. Also, the inhibited alarms are
cross referenced to work request numbers to fit with our philosophy that
alarms should only be inhibited if something is broken.
=20
=20
Don't Forget Invensys's own "Plant State Suite" which also looks to be
an excellent product!
Regards from Down Under.
Alan Armour =20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: Wednesday, 26 October 2005 1:05 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Alarms one line
Terry Doucet brings up a good point about alarm management that
ties into this thread about historizing and displaying alarms. In order
to know if you really have an alarm problem you need a way to
count/track/measure the alarms that each operator is dealing with on a
daily basis. =3D20 1. The old COMM Processor connected to an alarm
printer did historize the alarms but it really wasn't designed for alarm
analysis unless you like digging through reams of paper. =3D20 2. =
Porting
the printed ASCII text into electronic text files that could be
electronically searched was the next step, and although much better,
left a lot to be desired in terms of compiling and sorting the data. =
=3D20
3. Enter spreadsheets to parse the text based alarm strings into columns
and rows that could be sorted/manually analyzed. 4. Enter packages that
periodically FTP the almhist file from AW's and place it into
proprietary databases that can count and analyze the alarms, but only in
the way the application supports. New queries or features can only be
implemented by the application provider. 5. Enter SQL databases that
automatically collect alarms and operator actions from AW spoolers,
(eliminates COMM Processor interfaces), via 2nd Ethernet and place them
into tables that can be queried via browser based interfaces by anyone
on your intranet. These tables can be relational to other SQL databases
and tables. This enables users access to virtual real-time event
analysis. 6. Enter a WonderWare/Archestra browser based HMI interface
that allows Process-Control/Alarms/Operator-Actions/Sequence-of-Events
info to be displayed and queried in a unified environment along with
other enterprise SQL databases.
Oops. I forgot. Number 6 is not yet available. 1-5 is already
being done and I like #5 the best at this time. We are doing #3 at this
time. My limited research led me to: Ted Jirik, Real Time Solutions,
Inc. Ted.Jirik@xxxxxxxxxxxxxxx He can help users get to #5. I know we
don't encourage vendors to pump their products on this list but if there
are users that have experience with specific vendor products, please
speak up for the benefit of the rest of us.
Cheers,
Tom VandeWater
P.S. More on alarm analysis/strategies in a later note
=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
DISCLAIMER
The contents of this electronic message and any attachments are intended only
for the addressee and may contain legally privileged, personal, sensitive or
confidential information. If you are not the intended addressee, and have
received this email, any transmission, distribution, downloading, printing or
photocopying of the contents of this message or attachments is strictly
prohibited. Any legal privilege or confidentiality attached to this message and
attachments is not waived, lost or destroyed by reason of delivery to any
person other than intended addressee. If you have received this message and
are not the intended addressee you should notify the sender by return email and
destroy all copies of the message and any attachments. Unless expressly
attributed, the views expressed in this email do not necessarily represent the
views of the company.
_______________________________________________________________________
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:
