Hi Dojo,
We are running 9.6 and we have several use cases where our users would like to raise only one alarm for specific parameters (for all our drivers). In order to do this we wanted to use one of the "General Parameters" : [Element alarm state] (65008).
In this way with the alarm template they could adapt on their need and the parameters impacting the element state and could be "correlated" thanks to their threshold. On the paper this is working.
However each time an alarm is being raised, the parameter [Element alarm state] is raising an alarm (which is normal) but when the initial alarm got cleared, as this parameter is also generating an alarm, it's also counting itself as an alarm and the state stay blocked in this situation, I thought to put a condition but I don't want to end with an infinite loop.
Any suggestion ?
Thanks !
Hi Julien,
Not sure if you tried with our Correlation module before, but I see that you could have a simple correlation rule that groups all the alarms per element.
Here is an example with 3 elements with 5 alarms each:
If we create a simple correlation rule that simply groups the alarms per elements and generates a new Correlated alarm, it will give you an alarm per element, as long as there at least one alarm on them.
You can still see in detail what are the base alarms if you expand the correlated alarm (by clicking in the '>' icon on the left-hand side).
Hope that this helps you.