Merging alarms from two different areas into one alarm list
I am basically trying to merge alarms and events from two different areas into one list. I tried to create a site object in the functional structure, and inserted the two area objects from the control structure in there. I added an alarm and event list aspect to the site object, selecting objects and descendents, but it didn't work. I also tried creating a graphic display PG2 aspect with references to the two areas, then pointing in the alarm and event list configuration to this graphic display using "objects referenced by aspect" and selecting "including descendents", but this also didn't work.
Could you help me find the right way on this one?
Voted best answer
This very same question has been answered before, search!
Objects and Descendants only work if the list is above the objects it shall include. Think ”pyramid”. You cannot have the ”top stone” (alarm list) in one structure and the objects in another.
Referenced by = graphic aspect works. This is extensively used in Tabbed Navigation. A product bulletin is on the way out declaring a problem with calling the alarm list first (show up empty) and edit the graphic (adding objects) later expecting the list to grow by each object you add to the graphic. Restart the Alarm Manager (all providers, at once) or use the lesser interruptive, but slightly more complex workaround described in the bulletin.
You can also add new & custom alarm attributes to any object or hierarchy of objects using Event Attribute Extensions. Search AKS for help - I have posted many such answers. Eg declare ”Process Section” as an extension on the AC 800M’s Process Condition Event category, then set controller 1 with section 10 and controller 2 with section 11. Each new alarm from those controllers will carry the new attribute which you can apply an attribute filter for. Search for a bulletin on ABB Library. There was a problem with that method 10 years ago, I saw to that the bulletin was appended with a good user example.
Generally speaking, Objects and Descendants based filtering is favored before attribute filters due to lesser overhead in filtering objects.
If the applications are in same Control netowrk then create the Alarm List Aspect in Control Nework so that alarms in Applications will appear in the Alarm List.You will get all alarms of the application in Alarm list.
or another method is that you can use alarm class and merge the alarms in the alarm list.
You dont need fancy work arounds at all....
Alarm lists can see EVERY alarm in the system. You set up the filter to remove the alarms you DON'T want.
There is an extensive set of filters available, but if you set up the Process Area of an alarm correctly, then you can easily filter several different groups and ranges into the same alarm list.