Re: [foxboro] Alarm management

  • From: "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 14 Oct 2011 13:18:59 -0500

First Problem - If the contents of the file are identical, you can use a 
Solaris link (ln -s <file> <linedFile>) or a Windows shortcut and name the file 
after the CB.AlarmType. This is a bit of a maintenance effort, but...

You could also maintain that association (CBP to file name) in a file and have 
your script search the association file (grep) for the file name to display. 
This is much better, but requires a bit more script work. I'd go this way.


Second Problem - The most common thing is to run two CADs on the WP and use a 
filter to segregate the displayed messages. It works well.

Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1944 (SSC Fax)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of dirk.pauwels@xxxxxxxxxx
Sent: Friday, October 14, 2011 5:00 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Alarm management

We're starting an alarm management project soon, probably based on ISA 18 
or EEMUA
By the time the project reaches implementation we will probably be an all 
windows 8.4 I/A site (now we have mesh, unix&Windows 8.4)

Analyzing the alarms is no problem, we have Foxray, which is a great help. 
Cleaning up the alarms and re-assigning priorities is no problem either.

We're faced with a few items on which we need some more info.

First problem:

Process engineering would like to tie some kind of "what to do" - 
flowcharts or text to an alarmpage button. So hitting an "alarm action" 
button when a certain alarm is selected should produce a flowchart or 
plain text display related to the comp:block. I can figure out how to call 
a text file or a flowchart display related to a certain comp:block, but I 
can't imagine us creating seperate text files or displays for each block 
that has an alarm configured. Any one using this approach and how did you 
configure it? Did you go for 3th party software or did you use the I/A 
functions?

Second problem:

Now we use priority 5 for stuff that's not considered as an alarm, but 
does need some operator attention. These items appear on the alarm page, 
(which is always up)  so the operator is notified.

In the new approach they won't be considered as alarms anymore, Therefore 
they're not supposed to appear on the alarm page,  but we still need some 
way of informing the operator these items need some attention.
Does anyone uses something like this and how did you configure it?

Thanks & Rgds,

Dirk

 
 
_______________________________________________________________________
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
 


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).


 
 
_______________________________________________________________________
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: