Emerson Exchange 365

Filtering Alarm Banner by Unit Modulew

I see that the alarm lists can be set up to be filtered by Unit Module.  Is it possible to filter the alarm banner based on Unit Modules as well?

Kent

• 28 Feb 2024 8:50 PM
• Cancel

8 Replies

• KeithStThomas

  

  • 28 Feb 2024 10:44 PM

  Yes, but it takes some careful planning. In Alarm Priorities, each priority property can be setup so the Alarm Banner shows Unit/Equipment Module Name. If a module is in a Unit, then the Unit name shows in the banner. Click on the Unit to show a popup of all the modules in alarm within that Unit. Note, the Unit must also be assigned and downloaded to a controller. If a module is not inside a Unit, then the Module name shows in the alarm banner.
  
  We have our priorities setup so critical alarms show the module name in the alarm banner, whereas non-critical alarms can be grouped inside a Unit.

  • Cancel
• Kent

  

  • 29 Feb 2024 2:54 PM

  In reply to KeithStThomas:

  This is what I am trying to do with this. In several areas with several unit modules within them. Within each of the areas, the operators are only responsible for what is in a given unit module. What I'd like to be able to do limit the alarms that the operators see on the alarm banner on their workstation is just for their unit module.

  • Cancel
• Andre Dicaire

  

  • 29 Feb 2024 3:13 PM

  In reply to Kent:

  I seem to recall the ability for an Operator to mask out alarms by Unit. That enabled an operator to focus the console for his responsible span of control, beyond what the Plant Area assignments create. But I can't find the display used to do this. Haven't had to deal with this in a long time. Had something to do with the $U alarms.

  Andre Dicaire

  • Cancel
• KeithStThomas

  

  • 29 Feb 2024 3:15 PM

  In reply to Kent:

  Ah, I see. Alarming is handled by Area. So, in this case you will have to create new Areas, one per Operator, add this new area to the Operator user in User Manager, and move the unit(s) to the correct Area. Then assign the Area to that Operator's workstation. The Operator will only be able to operate and get Alarms for Modules in the Area assigned to their workstation. Be aware attempting this while the process is running since moving modules from one area to another may result in loss of operator control. Ensure the new area is assigned to the operator and workstation first. I would even build a test module to confirm the operator has control and the alarms work before moving the units into the new area.

  Any new Area will also have to be added to the Historian and Event Chronicle.

  • Cancel
• Kent

  

  • 29 Feb 2024 3:39 PM

  In reply to KeithStThomas:

  Thanks for all the responses. I know that you can do this alarm filtering in Live with the alarm list but it looks like it hasn't made it to the alarm banner yet.

  • Cancel
• Kent

  

  • 29 Feb 2024 3:51 PM

  In a related question, Live has the capability to filter by UM/EM in the Alarm List. What parameter does AlarmList use for this? I see that the AB_AlarmBox has a place to configure where it gets it's data. The default is THISUSER/FALMS. Might it be possible to use the parameter that AlarmList is currently using on the Alarm Banner?

  • Cancel
• Andre Dicaire

  

  • 29 Feb 2024 11:31 PM

  In reply to Kent:

  A colleague sent me a snippet of VBA code that shows how to filter Units on a station. This is documented in BOL for Graphics and uses the U$ (not $U) Alarm groupings in the console.
  
  The path is U$/UNIT_NAME/UFILT.CV.
  
  In Operate this is "DVSYS.U$/MY_UNIT/UFILT.F_CV" By writing a "0" to this parameter, the Unit's Alarms are filtered. Writing a "1" Enables the units. I looked on my system and there is no default display Out Of the Box, so this has to be done manually.
  
  In Live it would be DLSYS["U$/MY_UNIT/UFILT.CV"]
  
  The Area Filter display could provide a basis for designing a Unit Filter display. This would allow the operator to have an overview of this filtered Units and a means to quickly set this up. Further automation of this filtering mechanism would possible on Logon change or some other trigger. This would allow you to maintain the Area structure if that is important.
  
  Many customers create additional Plant Areas for each unit as suggested by Keith. Totally up to you to go that route.
  
  I've suggested before that Operator span of control should be more granular than Plant Area. That way the S88 structure of the DeltaV Explorer tree can remain true to the plant design. Maybe this is a suitable suggestion to the User Directed Enhancement Projects (UDEP).

  Andre Dicaire

  • Cancel
• Kent

  

  • 1 Mar 2024 2:16 PM

  In reply to Andre Dicaire:

  Thank you very much for your input. I'll look into this.

  • Cancel