Priorities for Different Alarm/Event state
I am facing some issues with some tags, as they disappear from the event list after a certain period of time.
The tag is configured to be in a priority 1, but when certain events like Conflict, Fault, Abnormal condition thet come with different priority. In my case I noticed that when the event happend it came as Abnormal Condition with Priority level 7 and after almost an hour it disappaered from the list.
We are using Reuse Library and the type is OB. Is there any way we could change priorities for the events so that it can stay in the event list.
Thanks on advance
This has probably nothing to do with priority.
Rather, the Event Storage (event log) capacity has been reached and the oldest event is overwritten by the most recent (FIFO).
Look in users guides or Google AKS for procedure to increase capacity. User's guides permit increasing category storage from 10.000 up to 50.000 events. Each category may have a different setting.
With large amount of IO (tens of thousands+) and a noisy process (many alarm and events per minute) 50.000 is not a whole lot.
Personally, I've seen several systems where 50.000 events are generated just in a few hours. The most extreme case I've seen, the Information Manager Message Log with capacity of holding 12.000.000 (12M) events wrapped in less than a week! At peaks, more than 100.000 events per hour were generated by the process!!
Notice: each event category wrap individually in Event Storage. Hence, just because Process Condition Events wrap in a few hours, another event category, e.g. Alarm Expressions may wrap after several weeks or months. Event lists including more than one event category can be tricky to understand unless this lesser known fact is held by the person viewing the list.
An IM Message Log is easier to calculate since all categories are put in the same storage bin (events of different categories wrap at the same moment in time).
To measure rate of events: create a new temporary event list filter object and set it up with a SINGLE event category (e.g. Process Condition Event, the process alarm category of AC 800M), then sort on reverse time (oldest first). Then check how old the oldest event is.
Hi Stefan, According to the searches I have carried out in the event list I was able to find the tags and events that had occured prior to the particular tag/event I was looking for. I am attaching the screen shot for the two searches. So I think the ones I am looking is not been overwritten by the FIFO method.
While comparing the search results except Priority 1,2&3 all the other low priority events has been disappeared from the list. This was the reason I started thinking the alarms are been pushed out by the priority.