I have a bunch of tags in a folder all set to Critical alarm priority. Operators are getting flooded with alarms from this area on the Alarm Summary and the individual tags are not critical alarms. They really only need to be alerted if something in this area fails and be able to trace out where it came from. My idea is:
- Set the Alarm Status table in the Alarm Summary to Min Priority = Low
- Set all the alarms in this area to Diagnostic priority. This should put them in the Alarm History so that they can be found but filter them from the Alarm Summary to reduce the overload. I looked at the editAlarmConfig function to do a bulk edit but since the tagpaths argument would be very long I think I just have to manually set each alarm tag
- Create a new Expression tag of type Boolean to read all of the tags in the area and set the value to true if any of them are in alarm. I would then configure the alarm priority greater than Diagnostic to show up in the Alarm Summary. That way they know when something in that area has failed.
- Ideally I would like it to re-alarm (clear the Acknowledged state) if one of the tags in this area goes into alarm, but my understanding is that Ignition has no way to do this. Often there are many tags in the area in alarm (which is another problem) but I would like them to know that while they already have some tags in alarm that a new one has failed. I don’t see a way to do that.
Are there any recommendations on how best to do this? Is my approach a good one?