I am trying to understand why there is a vast difference with alarms when you apply history tracking and with history tracking enabled, it condenses the alarms down to just 4 per instance?
If it is the same alarm that is coming and going (due to rain fade in this case) there were some 67 alarms. Once history tracking was applied as a filter, the alarm count had reduced to just 16.
This has caused some confusion and misdiagnosis of faults as there were clearly more alarms to indicate there was an issue onsite.
Does anyone else experience the same kind of filtering in Cube?
I'm asking this because we still have users on System Display (Plan is to migrate them over very soon and upgrade) who have been interpreting alarms a particular way in System Display and moving over to Cube is displaying or highlighting alarms very differently which is probably why the current operators a hesitant to move over.
Hi Nathan,
The idea of the history tracking is that alarms on the same element/parameter/index combination are grouped.
These groups can be expanded to show all the alarms on that element/parameter/index. In that case the groups are counted, and it is indeed possible that the alarm count goes from 76 down to 16 if there are on average about 5 alarms in each group.
In this case it is up to the operators to expand the groups and look at all the alarms included in the group.
If this behavior is not desired it can be disabled from the alarm console menu, or it can be enforced from the user group settings.
Great Answer and clarification Michiel!