Emerson Exchange 365

Filtering Alarm Banner by Priority

Hi,

I am working on setting up a bypass summary for my system. I plan on doing this with the alarm summary as outlined in some PCSD documentation I have found. I have created a new bypass Alarm priority. The issue is that this alarm shows up in my alarm summary, on my faceplates, and in my alarm banner. I am not as concerned about the alarms showing in the faceplate, but I don't want them in the alarm summary or the alarm banner. Currently our alarm summary is configured to filter the same as the alarm banner. Is there a way to filter the alarm banner on priority? So far it seems it is just filtered to priority 4-15 by default and can only be adjusted to filter by Aria. Does anyone know a way to filter the alarm banner by priority?

Thanks

Joshua Story

• 14 Nov 2022 4:51 PM
• Cancel

3 Replies

• Andre Dicaire

  

  • 14 Nov 2022 6:31 PM

  Joshua, Are you using Live or Operate. You can set the Alarm banner priority filters in both, but it is done differently.
  
  In Operate, the User Settings File allows you to set the global parameters for alarm threshold. This is set in every Settings file you are using. It allows you to set the values differently on each station.
  
  In Live, you can set the alarm Threshold Standards which are used in the Layout files to set the Alarm Banner priority. You can customize various workstations by using a different layout.
  
  With the Alarm summary following the Alarm banner, this will give you the filtering you are looking for to exclude your bypass alarm.

  Andre Dicaire

  • Cancel
• Joshua Story

  

  • 14 Nov 2022 6:48 PM

  In reply to Andre Dicaire:

  Andre, Thanks. I finally stumbled on the Operate solution is some other forums. That is what I am working with currently, and I have it setup and working on my development system. I am anticipating a move to Live before too much longer. Could you elaborate on that solution so that I can capture it in my notes to implement when we migrate to live? Specifically, what is the name and location of the file to be edited? Any other info you think I might need.
  
  Thanks
  Josh

  • Cancel
• Andre Dicaire

  

  • 14 Nov 2022 6:54 PM

  In reply to Andre Dicaire:

  One more thing. In Operate, the Global Variables, or parameters are runtime modified in each station. That means the Dynamos can also filter out alarms based on the alarm threshold variables. In Live, the OOB GEMS use the Alarm threshold standards, which are system wide and cannot be modified per station at run time.
  
  If you adjust the threshold standards, and you want the same behavior in the GEMs, no problem. The GEMS will use the standard threshold.
  
  But if you have dynamic thresholds, say based on logged on user or for different workstations, the Alarrm Banner and Summary will filter based on the customized settings, but all GEMs will still show alarms based on the Standards values.
  
  As you mention, this is not a problem for you, as you are only interested in the behavior of the banner and summary. My take away is to adopt the Threshold Standards to drive all your GEM alarm behavior. Then, in your layout's, you can adopt this or customize the banner/summary to be different. Alternatively, you can update your GEMs to use a Layout Variable for Threshold filtering and initialize this as needed in the layout.
  
  Note that you can change the threshold values of the alarm banner and summary at any time by running the following in a script:
  
  // Set Alarm Priority Thresholds
  let thresholds = GL.Library.S_ProcAlmThresh + "," + GL.Library.S_DevAlmThresh + "," + GL.Library.S_HWAlmThresh + "," + GL.Library.S_SISProcAlmThresh + "," + GL.Library.S_SISDevAlmThresh + "," + GL.Library.S_SISHWAlmThresh;
  await ENV.RunAsync(GL.Library.S_SAT_path, thresholds);
  
  The above script uses a string variable that is populated with the 6 Threshold standards in a comma delimited format. This string is then used as a command lint variable with the executable defined in the S_SAT_path standard. The file is %DeltaVPath%\SAT.exe
  
  I'm thinking SAT stands for "Set Alarm Thresholds". You can set up logic to use a different threshold value and push that into the Threshold string to modify the filters. If you want to change the GEM behavior on displays to follow the alarm banner and summary when you deviate from the standards, you'll need to create Layout variable for your GEMs to use. If the variable does not exist in a layout, the GEMs could default to the Standard. I'd lean toward leaving the GEMs linked to the standard and having only the Alarm Banner and Summary follow any custom filtering.
  
  Bottomline, Live behaves differently than Operate if you want different thresholds on different consoles. The Banner and Summary will be the same, but displays will show alarms a bit differently.

  Andre Dicaire

  • Cancel