Emerson Exchange 365

What is the simplest way to obtain a list of all supressed alarms that are active?

What is the simplest way to obtain a list of all supressed alarms that would be active?

By active I mean it would annunciate if supression was removed, e.g. for a HI_ALM, the PV > HI_LIM.

I can get a list of supressed alarms by saving an xml export of the alarm banner. It is the last criteria that is causing me issues.

• Supression
• reporting
• alarm management
• DeltaV

richardwilliambrooks

• 25 May 2016 4:51 PM
• Cancel

5 Replies

• Matt Stoner

  

  • 25 May 2016 5:46 PM

  You can get a list of suppressed alarms (and the ones that are Out of Service as well in v13) by opening the graphic "AlmSupp" on any operator station. You can also get to this on the toolbar by clicking the button to the right of the Area Filter button. This button won't be visible if no alarm is suppressed so you should be able to tell very quickly just by looking for the button.
  
  This display will only show the alarms that are in any of the areas assigned to that workstation. If you want all the alarms suppressed on the system, you will need to do this on a station that has all the areas assigned to that station.
  
  If the alarm is unsuppressed, it won't "annunciate" again if the PV is past the limit. It will come back as active and acknowledged, no horn or requiring the alarm to be acknowledged is required.

  • Cancel
• richardwilliambrooks

  

  • 25 May 2016 5:56 PM

  In reply to Matt Stoner:

  Thank you for your reply.
  Is there anyway (easy) way of filtering (or identifying) supressed alarms in the list where PV is past the limit - i.e. have been supressed because otherwise they would be active?
  The client wants this information in an Excel Sheet, and we have DeltaV 12.3.1 (forgot to mention this).

  • Cancel
• Andre Dicaire

  

  • 26 May 2016 4:17 PM

  If you have a list of suppressed alarms, you could use an Excel spreadsheet with the DeltaV Addin to read the current state of suppressed alarms for these that are in a state of alarm.
  
  In column A place the name of a suppressed alarm: FIC-100/HI_ALM. Configure an OPC read of the FIC-100/HI_ALM.CV path. If this is OK the PV is not in alarm. If it returns a Priority number, the alarm is triggered.
  
  you can use the DVREAD command with a Concatonate expression to combine the alarm path in column A with the .CV field. Save this and use in the future, simply by populating the A column with the Alarm paths.

  Andre Dicaire

  • Cancel
• Jason.Brumfield

  

  • 13 May 2021 12:33 AM

  In reply to Andre Dicaire:

  Andre, I had an interesting question come up today. Operations asked if I could auto un-suppress all the alarms 30 minutes after shift change everyday. I put in a GSC ticket response was no, DeltaV doesn't have that functionality. I am in 13.3.1, do you have any guidance on where to start with this initiative. I have all of the alarm suppression timeouts set to 12hr already, but depending on when it was suppressed during the prior shift, impacts what time in the next shift it is de-suppressed. I am considering trying to capture the records from the event chronicle as they are suppressed, but not sure what method or action to unsuppress that list. I could add logic in every module but that is excessive load on my controllers for anything that is not classed. I thought about a supervisory module but based my module count, that would be a PIA and another thing to maintain, plus I would have to add every module and alarm to a sequence of action blocks and that doesn't seem appealing to me either. I support a honeywell site, and the functionality is out of the box, just looking for guidance on any other options I am not considering. Thanks!

  • Cancel
• Benji_Kidmose

  

  • 13 May 2021 2:57 AM

  In reply to Jason.Brumfield:

  Create a module that calculates time till shift end. Then this is an exercise in VBA on your detail display that should link to a single “master” script to do your task that you create in user defined. Create a custom combo box on every detail display that when selected grabs the current time remain till end of shift out of your module Then with a custom “set” button for suppressing the alarm set the time out on the alarm to the shift time remain clock by passing the time and the alarm parameters up to your master script  

  you can write to the time out parameters online, there is some formatting to figure out in script but nothing very difficult. If you use a master script it’s really just a quick update to all detail displays to copy your combo box and set buttons around for each alarm. You pass the alarm tag and the time up to your master script, and good to go. 
  
  Makes it so no alarm can ever be suppressed longer than the time remaining for the shift.
  
  Most of things you actually want out of the system for CRO always require a ton of scripting unfortunately, but it’s the way it is. Use a single script in the user defined so that you actually only have one piece of code to maintain.
  
  Going to be some  new challenges in Live replacing all the custom “tools” you create in VBA with the type script so keep that in mind, as nothing is impossible but it will take some new thinking when you convert. Cause once the CRO has had a function it will be next to impossible to convince them the “new” graphics can’t do that

  You can also have the OOS actuated through here but have this linked to use based on privlages of user. So that only certain people can set an alarm oos. Also if you want the CRO’s to only use this function for shelving alarms you have to make sure the right click “suppress” is removed from every alarm summary including in faceplates. 
  
  

  leave yourself a hidden summary though so DCS techs can work from a summary for suppression still if needed. 

  • Cancel