Recent Services Discussions
Similar Posts
DCS Alarm Propogation From Process Display to Overview Display
Mag meter display
HMI display operation
display unresolved reference
Field Link Display Massage
Share

Alarm Suppression Display Graphic

I would like to create a graphic to show the operators all the alarms that have been shelved by the operators.  I would like it to filter out the alarms that are suppressed by logic.  This would allow the operators to see a list of the alarms that have been shelved by an operator only.  What would be the recommended way to do this?

Kent
  • Matt Stoner
    In v13 this would be very easy to do because there are two different alarm fields for this (OOS-logic use & OPSUP-Operator Shelving) but any other version of DeltaV you will have a very difficult (if not impossible) time doing this because there is only the OPSUP parameter field and the Alarm Enable. You would have to rely on 'other' methods than the alarm suppression summary I describe below to get this accomplished in pre-v13 systems.

    In v13 when configuring the Alarm Summary ActiveX object, you can select on the More Filters tab the options Shelved and/or Removed from Service (OOS). Note that the Alarm Summary Type needs to be set to Suppressed Alarms to be able to get to these selections. Your logic would use the OOS bit and OPSUP would be used for Operator Shelving but this still might not be entirely correct unless you change the OOS field security to a higher level so that unauthorized people can't turn it on from right clicking the alarm on the alarm summary or the OOS checkbox on the Detail display. I've have been suggesting also using the OOS for Maintenance personnel to use while they work on a device and not give any alarms while it is being worked on instead of using Operator Shelving. You can use the Suppression Reason to indicate the reason and have "By Logic" reason set by the logic and that reason not be selectable and be alot more visible of which is by logic or not.

    The big difference between these two alarm fields is that the OOS doesn't have a timeout while the OPSUP does and can be configured so when shelved it would turn itself back on when the time expires. Note that if the timeout for an alarm is 0 then it can NEVER be Shelved.
  • Kent

    In reply to Matt Stoner:

    Thank you for the quick response. The logic that we use for suppressing alarms was originally put in place on version 11.3.1 but is now on a system with version 13. If I am understanding what you are saying, you are recommending changing from suppressing by logic to taking them out of service by logic. So there isn't a place where you can filter by the SUPRSN parameter?
  • Matt Stoner

    In reply to Kent:

    There is no option to filter on the SUPRSN but the SUPRSN is shown as a column on "AlmSupp" graphic but yes I would recommend moving the logic to use OOS as well as adding the setting the SUPRSN to "Suppressed by Logic" (which would be Visible but not User Selectable in the dv_alm_sup_rsn named set) or something else you want. I think this "Suppressed by Logic" will come in v13.3.1 as a default at index 7 if it isn't already in v13.3, I can't remember if I updated my 13.3 copy because I was working/testing the new alarm management modules coming in 13.3.1. You would then create a new display starting from AlmSupp and change the options I described above to get what you are looking for.

    Make sure that you set the Field Security for OPSUP, SUPRSN, SUPTMO and OOS to the appropriate levels which I suggest changing from the DeltaV defaults of Restricted Control for all except SUPTMO.

    • OPSUP to Alarms
    • SUPRSN to Alarms
    • OOS to Can Calibrate (allows mantinence to take alarms OOS while working on devices)

    Regards

  • Kent

    In reply to Matt Stoner:

    Thanks!
  • Rachelle McWright

    In reply to Kent:

    , we held a Live event in October that featured 5 Alarm experts, one of which is guru, . TONS of great information on topics related to alarm management can be viewed in the EE365 community here: http://emrsn.co/alarmexperts

    Best Regards,

    Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast

  • Matt Stoner

    In reply to Kent:

    Also forgot to mention that you should probably have the logic be a one shot and not continually writing to the alarm OOS and SUPRSN. This would allow someone to manually do things without thinking the system is broke.
  • Kent

    In reply to Rachelle McWright:

    Thank you very much. It is great having access to so much expertise.
  • Kent

    In reply to Matt Stoner:

    Definitely.
  • Kent

    In reply to Matt Stoner:

    Thanks again

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.