800XA Create a List of Historical Alarms for List of Tags
The idea is that these alarms cause trips to a main sequence but are spread throughout the plant's controllers and processes so in my functional structure they are spread out and in my control structure they are spread out, so I would like a simple way to reference them into a list of some kind showing when they happened.
We have a functioning environment and alarms and tags exist, what I want to do is take a list of 40-50 alarms and keep a record on the HMI of when these alarms occur. I don't need functionality to acknowledge alarms with this list, but if it has it that is not an issue.
Fairly new to the process as the system was setup before I came in so if you have any ideas please provide as much detail as possible.
Voted best answer
In 800xA alarms disappear when they return to normal and are acknowledged. The term "Historic Alarms" is somewhat misleading as alarms vanish after returning to idle state.
However, for each alarm an equivalent event is generated and persistently stored in the Event Storage service on disk. The storage size is 10.000 events FIFO per category but can be upped to about 50.000 (an IM may store up to a total of 12 million events).
The easiest way of filtering alarms or events for an arbitrary selection of objects is probably by inserting them below a container object that you create in some structure, why not the Functional Structure and call lets say "Trip Objects".
Create an Alarm and Event List aspect on the "Trip Objects" object, select the "Common Event List" filter, then "Copy Template" (to create a local and independent copy of the Common Event List filter on the "Trip Objects" object that you can safely adjust/edit without affecting other event list filters). Apply. Then select "Objects and Descendants" filtering mode, finally edit the new filter's settings and reduce it from including virtually all event categories (as the original Common Event List does) down to as few as possible to speed up the event list performance.
Trip Objects <- (create the event list aspect here)
TripObject1 <- insert objects known to cause trips below "Trip Objects"
Inserting an existing object into yet another location in the system does not require any license, etc. nor will it cause any burden.
As of 5.1 FP4, filtering can be made based on objects contained within a graphic display. So you could also build a graphic display in which you insert "Trip Objects" display element (they need to have some element for this to work - but you can create dummy ones if case there are none to select). After saving the in plant operations term "more or less useless picture" you can have an event list to filter events from objects only appearing in this "dummy picture".
Check if this helps
A group alarm represents the alarm conditions added to a specific Alarm Group through configuration. Defining Alarm Groups in the system reduces the number of alarms displayed in the operator Alarm List. Alarm Groups are configured by creating aGroup Alarm Definition aspect on an object, specifying a group alarm condition, and adding alarm conditions to the Alarm Group. Alarm grouping can be enabled or disabled through the Group Alarm Manager aspect in Library Structure > Alarm & Event > Alarm Grouping Configuration. The Alarm Manager Service in the Service Structure controls the runtime functionality of Alarm Groups. For more information on Alarm Group configuration, refer to System 800xA, Configuration (3BDS011222*) and System 800xA, Administration and Security (3BSE037410*).
Note: This is a feature pack functionality
You can follow the following steps:
1.Create Generic Object in Location Structure
2.Add Alarm and Event List Aspect and Alarm Event Configuration Aspect
3.In Alarm Event Configuration select Objects and Descendents
4.Insert your Trip Objects below the Generic Objects.
By this The Alarm Events shows only the tags inserted Generic Object ..
If you are having IM Server ,We may need to do some configuration,which is explained in 3BUF001092-510_B_en_System_800xA_Information_Management_5.1_Configuration Page no 162.