Dirk, Re: First problem: displaying "what to do" information If you were using the Invensys preferred Alarm Management Tool (PlantState Suite) then the information from the alarm review process could be captured directly in to the Documentation & Rationalisation (D&R) component of the Advanced Alarm Elements module. It is then pretty straight forward to present this information to the user using picks on the Current Alarm Display (CAD). Some users consider the D&R component to be Master Alarm Database for the asset. For further information contact your regional Alarm Management Subject Matter Expert, your Account Manager (Client Sales Executive) should have the relevant details Regards, Martin Theobald Senior Support Engineer Units 13a and 15, The Genesis Centre Warrington, Cheshire WA3 7BH United Kingdom T +44 1925 859 800 M +44 7767 87 1989 F +44 1925 859 801 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of dirk.pauwels@xxxxxxxxxx Sent: 14 October 2011 17:00 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