Exclude Points from Embedded Alarm List/Areas of Interest on Calculated points

[MichaelAur]

Hi All,

We currently display all alarms in a big embedded alarms list. This is beginning to become a little unwieldy. We were hoping to filter out some of the less urgent alarms into a secondary alarms list. I had thought that 'Areas of Interest' would be a perfect solution here.  I had hoped to make areas of interest like below and then set our 'Normal' alarms list show only 'Important' points of interest and then another alarms list that shows the less important Items.

  World

• Important (Set to default)
• Less Important

However, we also use Calculated points to trigger a number of our alarms, and it doesn't seem you can assign areas of interest to these? So when I modify our normal list to only show Important areas of interest it skips all these calculated point as they are in the top level 'World' group.

As such I was wondering if anyone could think of a good way to be able to have these two separate alarm lists?

Thanks.
Ps we are currently using Geo Scada Expert 2021, March 2024 Update (84.8852)

[tfranklin · Accepted solution]

So the first part of your question -- calculated points do indeed have areas of interest.  You configure them on the analog point / digital point tabs under the limits category. 

One thing to note with AOI is that any alarmable type will have its own independent AOI, so this may add to some configuration for you to manage. You can use AOI for this, but the issue is that if you determine an AOI on a point is "not important" and classify it as such, the whole item is now not important.  That might not be the desired behavior -- maybe only the low alarm is not important, but if it goes to high high -- I need people to know.

What you described though of normal vs important alarms is exactly what severities are for.  By default GS comes with low, medium, high, and critical.  There's nothing to stop you from creation additional classifications though then using filters on your alarm lists for filtering out low severity items.

A popular configuration here in the US (and likely elsewhere) is that users will often have severities < 100 be for notifications or things the SCADA team is responsible for, but anything >= 100 will be for operators/controllers.  This allows us to configure severities on a limit by limit basis and only show what's required to the users.  This allows you to set severity levels on different state values and the filters are respected as such in the alarm lists. 

[MichaelAur]

Hey Tfranklin. Thats a little embarrassing on my side. When I was looking through Bulk edit options I didnt see the areas of interest. But I now see that it is under 'StateAreaOfInterestID'! vs most of the other data points being 'AreaOfInterestID'

As for the adjusting the levels of alarms. This is probably a case of putting the horse before the cart. But our users want to preserve the severities level but just have them in a separate tab. Thankfully in this case the users do indeed want any alarms from this one object/point to be shunted into its own screen. So I just thought areas of interest (which we havenet been using) might be the easiest option. But by keeping the top level 'World' group if we ever want I can just change the main alarms list to display 'world' area of interest. 

[AdamWoodlandToo]

You'll find the extra AreaOfInterestID fields when the object has multiple alarm subconditions and it makes sense for them to have different AOIs