Alarm Filtering by State

[brian@applied.co.uk]

Hi,

I am working on porting from an obsolete Scada system to OA. The old system has options to filter the alarms (alerts) that are displayed by state in one of the following ways:

a. Display only Active Unacknowledged alarms
b. Display only Clear Unacknowledged alarms
c. Display only Active Acknowledged alarms

I know I can set the .Alerts.FilterState.State element of the appropriate _AESProperties datapoint to filter by state, but have found it possible to do only two of the above combinations:

State=3 displays only active unacknowledged alerts
State=4 displays only active acknowledged alerts

State=1 will display all unacknowledged alerts (both active and cleared).

Is there a State value that displays only alerts that are cleared and unacknowledged?

[adaneau]

Hi,

I guess _act_state should make it:


1 = CAME unacknowledged (Active Unacknowledged alarms)

2 = CAME acknowledged (Active Acknowledged alarms)

3 = WENT unacknowledged (Clear Unacknowledged alarms)

4 = CAME/WENT/unacknowledged (Clear Unacknowledged alarms in case of double ack required)

0 = No alert


BR
Alex

[brian@applied.co.uk]

Alex, thanks for the response, but how do I filter by _act_state? Will I need to use a HOOK function (HOOK_aes_modifyQuery I would guess) to get at the raw SQL to apply the filter that I want?

[leoknipp]

Brian Kelly wrote:

Is there a State value that displays only alerts that are cleared and unacknowledged?

What does "cleared" mean in detail?
Are you talking about alerts which are "gone" and "unacknowledged"?

Best Regards
Leopold Knipp
Senior Support Specialist

[brian@applied.co.uk]

Leopold: yes.

I am talking about the active alerts display, which shows alerts that are in one of three states:

1. Active (CAME) and unacknowledged
2. Active (CAME) and acknowledged
3. Cleared (WENT) and unacknowledged

We will not be using the double acknowledgement feature, so the CAME & WENT both unacknowledged mentioned by Alex is not appropriate to us.

Alex's suggestion looks like just what we want, and my reply to him questioned on how this can be implemented: do we need to implement a HOOK function to modify the query to add a filter on _act_state? Or is there some way to do this with the _AESProperties datapoint?

Brian

[adaneau]

Hi Brian,

Is it for runtime alarms or for historical?

Because in runtime it is possible to show ack / not ack with standard filter, however you cannot show only CAME or WENT ( I guess for security reason as in current mode you dont want to miss a new alarm).

But in closed intervall you can choose direction and status, thus having your filters set.

BR
Alex

[brian@applied.co.uk]

Alex,

Initial requirement is for runtime alarms.

Brian

[adaneau]

You can have a look into

https://portal.etm.at/index.php?option= ... =8071#8071

This show you how to extend filter using HOOK_aes_modifyQuery. That should make the trick.

[brian@applied.co.uk]

Alex, Thanks for the link. I'm now confident that I can implement the required filtering.