Emerson Exchange 365

• Not Answered

Disabling the Suppression Function on a Faceplate

Hi,

I want to achieve a set up whereby an operator has to verify when an alarm is suppressed. So far we have set up a policy in electronic signatures using the opsup parameter. This function works when suppressing alarms from the detail faceplate by checking the appropriate box however, an operator can still suppress an alarm that's active in the faceplate or in the alarm lists.

I have found in DeltaV Operate Configure with any faceplate open or the Alarm List (from DVCtrlAlmSum1), right clicking in the Ack/Message field/or alarm List, using pop up menu and selecting 'properties...DeltaV.DVAlarmSummary Object' a new window opens 'DeltaV Alarm Summary Configuration', selecting the last tab 'Actions' shows the actions availble from right-click context menu.

Finally, my question is de-selecting Suppress/unsuppressed an alarm the way to go or is there a downfall to implemeting this or another tried and tested method for this.

Thanks,    

David Billington

• 30 Sep 2014 2:05 PM
• Cancel

3 Replies

• BC Spear

  

  • 30 Sep 2014 8:05 PM

  I assume by verify you mean they need to push a second "OK" button to confirm they wish to suppress the alarm. I don't think I have ever done that for an alarm. I would think if they clicked the faceplate, then the detail faceplate, and then the alarm suppress button they would always click the last "OK" button at that point. Anyway, you have the correct idea that you would need to place a wrapper on all the locations the alarm can be suppressed for this to work everywhere.

  As for other options, I typically implement this using security keys and the suppression timer. If the alarm is used as a Safety IPL then I give it a security setting such that it can only be suppressed by a Supervisor login. Then based on priority and site alarm policy I set the suppression timeout. Any HI priority or Safety based alarm I set the timeout to one shift, this way it will re-alarm and need to be suppressed each shift by each operator/supervisor.  It sounds a little annoying but it should be annoying so they get it fixed.

  I also set the rest of the suppression timeouts to something longer (2 wks to 30 days) so we remember that it is suppressed and not just forget about it forever. I would suggest anything suppressed longer than a month or two likely should not be an alarm. You can set the timeout based on priority or determine it for each alarm in alarm rationalization.

   

  BC

  • Cancel
• Andre Dicaire

  

  • 30 Sep 2014 11:39 PM

  I gave this a quick look and it does what you're thinking. However, you do have to remove the option on all Alarm Summary controls to force suppression to happen in the Detail display. But the alarm summary drop down list gives you direct access to the Detail display, so it adds an extra click to set the suppress check box, and then additional confirm.
  
  I like the simpler," no code, set the options" solution you came up with.I think that makes the most sense. Using the electronic signature saves you having to create a custom dialog.
  
  However, a custom dialog could evaluate alarm priority and only show confirmation for say high and medium alarms, but suppress low priority alarms without the confirmation. Of course this would need additional modification of the alarm suppress check box function, but only if you want more granularity on what needs confirmation. The Alarm Summary Action setting seems easy and global, once all the controls are set.

  Andre Dicaire

  • Cancel
• David Billington

  

  • 1 Oct 2014 10:36 AM

  Thanks for the replies, that is an approach i'll consider too, using the time out function for suppressed alarms.
  Situation I have here is that operators can suppress alarms using the generic operator account so in this instance we don't have traceability when looking back in event viewer as to who suppressed the alarm, we only see the workstation name from where it was suppressed. I want the operator verify or sign for when they've suppressed an alarm, this way we can track whose suppressed an alarm and then at least have a chance of follow up work to establish why the alarm was suppressed and look to resolve any issues experienced by the operator. At present we are running with a log book for recording purposes.
  This feature works when suppressing from the detail faceplate but not suppressing elsewhere from say the alarm list or on the faceplate.

  • Cancel