Re: [foxboro] Priority in Alarm messages
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 19 Jan 2007 16:17:39 -0500
Re: I didn't know that the priority did not come out on the printer. Not
really sure why this would be the case, as the Alarm Manager and legacy
historian know about it. Is this true of any non-AM alarm device?
The alarm message carries the priority when it leaves the CP so any
application that can directly receive alarm messages has the data. Such
applications include the historians and FoxPage/EDS.
The filter in the I/A Series printer driver removes the alarm priority
along with any SOE messages that it sees.
I've never understood the motivation of either of these decisions.
Re: As for how the alarm management vendors determine priority, most of
the=20
packages I've seen also import part or all of the system configuration=20
(either periodically from iccprt dumps or live via OPC) and get the=20
priorities from that.
Since alarm priorities can be adjusted on the fly, this technique has
its limitations in some plants.
Regards,
=20
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Friday, January 19, 2007 1:19 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Priority in Alarm messages
Hmm...I didn't know that the priority did not come out on the printer.
Not=20
really sure why this would be the case, as the Alarm Manager and legacy
historian know about it. Is this true of any non-AM alarm device?
To do long-term alarm logging, I have some scripts to read and parse the
almhist file that the legacy historian uses for a circular alarm history
buffer. These were based on some code I found on the Cassandra site and
in some Foxboro HH documents, but I've had to modify them several times
as=20
I've come across weird data the historian puts in this file for certain=20
alarm types, and to add additional features (like putting the year in
the=20
timestamp). It's not real-time (it runs out of cron every hour), but=20
suits my needs. I hope to get this into some kind of database (either
my=20
own or some alarm-management product's) for better analysis
capabilities.
As for how the alarm management vendors determine priority, most of the=20
packages I've seen also import part or all of the system configuration=20
(either periodically from iccprt dumps or live via OPC) and get the=20
priorities from that.
Corey Clingo
BASF Corporation
"Ghodhbani, Hafedh" <Hafedh.Ghodhbani@xxxxxxxxxxxx>=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
01/19/2007 04:32 AM
Please respond to
foxboro@xxxxxxxxxxxxx
To
<foxboro@xxxxxxxxxxxxx>
cc
Subject
[foxboro] Priority in Alarm messages
Hello,
We are sending plant alarms continuously to a PC for analysis.
We would like to add the alarm priority to the alarm message text.
Can you please advise how to proceed.
For your information, this is the alarm message we want to modify the
structure:
PK2103:PC21103.PK2103 HP N2 PURGE GAS
LOABS
01-19-07 09:35:45:2 0.05BAR ( 0.05) LOW ALARMS
ALM
Regards
Lead C&I Eng
BG Group
Tel:+21674259250 ex 574
______________________________________________________________________
BG Energy Holdings Limited
Registered in England & Wales 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.
=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
Confidentiality Notice: =0AThe information contained in this electronic m=
essage and any attachment(s) to this message are intended for the exclusi=
ve use of the recipient(s) and may contain confidential, privileged or pr=
oprietary information. If you are not the intended recipient, please noti=
fy the sender immediately, delete all copies of this message and any atta=
chment(s). Any other use of the E-Mail by you is prohibited.=0A
_______________________________________________________________________
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:
