AVEVA Input on SA Project template - SOE Filter functions & Roadmap

Hi Rune ,

I checked with a developer, and they said the following:

"It looks like the code deliberately include system events regardless of whether filter is applied or not. This might be part of the requirement at the time. Will need to check past requirement to confirm. 

In terms of “OFF” state, system events are not alarms which do not have concept of ON / OFF, and the State column just shows the default state."

So it looks like this behavior is by design, but they said they would confirm.

I'd recommend putting forward your suggestion for future consideration in the roadmap on the Citect Ideas website: https://citectscada.ideas.aha.io/

Kind regards

Olivier

Hi Olivier,

Thanks a lot for checking and clearing this with the developers, most appreciated. 

From our opinion the system events should be possible to filter when you troubleshoot an incident, so I'll add an entry to the Citect Ideas website. I will also push this through our distributor as we get push back from customer, along with the capability of filtering on timestamp. 

Regards,

Rune

Hi Rune,

I got confirmation that this was by design, but probably due to limitations in where the data was coming from the alarm back end. There was a change in behavior from v8.10 to v8.20 due to a defect fix.

"The issue was that whenever we filter on non-historic fields, such as Equipment, Category, Priority etc., the system events will disappear from the SOE list. This is due to those fields do not exist in the event journal table in the database. When the historic table is joined with the configuration tables, their values will be NULL and be always filtered out. For example if we just want to filter out priority 3 alarms, i.e. Priority<>3, the system events will be gone too.

 The resolution at the time was to always display the system events regardless of filtering is turned on or off to prevent the above issue. The side-effect is that the user won’t be able to filter out the system events if they want to. Perhaps we can provide a way for the user to filter out the system events if needed. One of the ways may be to only include system events if none of the filtered fields are from the event journal table."

It might be worth raising a support ticket with AVEVA Support and see if there is a change that could be made to make this filtering more useable for you.

Kind regards

Olivier

This is another example of the deficiencies in the current implementation of the alarm pages packaged with the SA include projects. In their current state they are causing real issues for customers using the system and integrators trying to deliver to customer expectations. I understand there may have been budget/time constrains which led to to the original release missing some features, but it has been several years now and no updates to what was released with the very first SA projects. It would be great to see something in the roadmap to improving the SA alarm page functionality.

This is another example of the deficiencies in the current implementation of the alarm pages packaged with the SA include projects. In their current state they are causing real issues for customers using the system and integrators trying to deliver to customer expectations. I understand there may have been budget/time constrains which led to to the original release missing some features, but it has been several years now and no updates to what was released with the very first SA projects. It would be great to see something in the roadmap to improving the SA alarm page functionality.