ABB800xA Alarm/Event List Configuration Solution
Hi, Can you please some advice on alarm and event configuration on our DCS system?
We have system which uses 4 layers (J25 building, Individual Subsystem, Individual object, Data types) as detailed in attached document.
We seems to be using alarm and event list under each layer and I can see configuration for alarm list is same under each layer but event configuration is different in top layer (J25, Building) and 3 bottom layers (Individual Subsystem, Individual object, Data types) as shown in attached document.
Though event configuration used is not enabled to record any event under configuration of bottom layers (Individual Subsystem, Individual object, Data types) but it’s still captures all event for objects it’s associated with but those events doesn’t get copied across to top layer (J25, Building) process event list because its only recording tracking event as shown in attached document.
- Is there any better way to implement alarm/event list then what we have currently configured on the system as it’s seems bit confusing?
- Do you really need alarm and event list under each layer?
- Is it ok to have alarm and event list just on top level and subsystem level to capture all alarms/events generated by each objects below it? What's the best way to achieve this?
- How to make sure that all events appearing in individual object level gets copied to top level (J25, Building) process events list?
Thank you for your help.
System 800xA Base system's storage of events is limited.
If there are a constant flood of alarm transitions (e.g. an oscillating alarm) an event that was recorded in the morning may be gone by lunch (with the alarm still listed as NEW in alarm lists).
The factory default is 10.000 events (per category) but can be increased to 50.000 (per category) - I suggest increasing to 50k as a first step. This is documented in the user's guides. Increase the number of events by factor 5x and in the same increase file size by same (5x) factor. Event list performance will drop with increased storage (see below recommendation on number of categories in filter)
Each alarm transition to NEW and to RTN is logged by Event Storage. Additional events (ACK, DELETE, etc) can be requested from Alarm Manager Special Configuration tab, but will reduce time span of event storage (adding logging of ACK increases storage requirements by +50%).
An Information Manager (IM) Message Log can store up to 12.000.000 events - but the integration of IM messages back into the event lists is not seamless nor trivial.
For performance reasons, include as FEW event categories as possible into your event lists. The Common Event List filter is the slowest of them all since all category files will have to be scavenged in the hunt for events. In most cases, including the PLC's category of events is enough - e.g. Process Condition Event and Process Simple Event for AC 800M.