Calendar Redirection

[Killultagh]

I am looking to redirect alarms from a facility which is manned during the hours of Monday - Friday (8am to 4pm).

Using the calendar redirection functionality I am able to achieve the redirect during working hours however, come 4pm the alarm severity does not revert to its monitored state i.e. High.  I'm sure it is something as simple as using the correct 'Abort' setting.

The end-goal will be to revert the alarm to its monitored state if after 2 hours it remains in alarm even during the working day which may involve logic or VB I guess however, I am attempting to walk before crawling!

Has anyone experience in using the calendar functionality?  Our system is already using 1 hour redirection against comms failures and this works as expected.

[sbeadle]

You write "the alarm severity does not revert to its monitored state i.e. High" - so are you modifying the alarm severity using the Change Priority Action? If so then the priority will not change back by the calendar - you will need another redirection or script to restore it.

Perhaps you don't need to change the priority to redirect?

[Glenn]

Yes, we are currently using the Change Priority Action, for example to change the Alarm Severity from Medium to "Redirected Medium", which our Alarm Management Centre staff can't see, with the idea that if the cause of the alarm has not been resolved within 2 hours then the redirect will revert and the AMC staff will be notified with a Medium Alarm. Also that if the set time in which the site is manned elapses while an alarm is redirected, then it will also revert back to alarm.

Originally I tried an instant redirection to Redirected Medium, and a 2H delayed redirection back to Medium. However that just led to it once again being picked up by the first redirection, getting it caught in a loop.

Do you think there is a better way this could be done, if at all? I'm sure it could be done through script but we wanted to see if it could be accomplished with just using the calendar tools.

[Killultagh]

Steve

Yes that is correct, we are using the Alarm Redirection Change Priority Action to change to a severity filtered out of the Alarm Monitoring Centre's alarm banner which does work and is tried and trusted with RTU comms failures.  If the alarm clears the redirection is stopped.

In this instance with manned works we wish for the alarm severity to be changed to one which is filtered out of the Alarm Monitoring Centre's alarm banner during working hours Monday - Friday (8am-4pm).  Again this works similar to the comms failure alarms however upon the clock reaching 4pm the priority does not revert back to its configured alarm severity which can be annunciated on the alarm banner.

[Killultagh]

Here are some screen shots to provide some further detail into the problem.  The redirection successfully applies as expected when an alarm is generated at source from Critical to Redirected Critical and be hidden from the Alarm Management Centre alarm banner with applied filters.  If the IO continues to be in alarm come the end of the day (in this case 16:00) it should redirect its alarm severity back to its configured severity (in this case Critical) to be actioned by the Alarm Management Centre.  The issue is that the redirection does not release when it is 16:00.  Any help would be appreciated.

[sbeadle · Accepted solution]

Thanks. What do these two redirections do?

I think the issue is a misunderstanding of what the redirection calendars do. A calendar states what will happen when an alarm state transition occurs. It does not make something happen when the calendar lists roll over to a new time/list.

I think you need a Logic program to force-redirect/restore alarms at your chosen time of 4pm.

(Assuming the answer to my query about what the redirections do is what I think they do!)

[Killultagh]

Steve

Thanks for the response.  Yes it looks as if logic will be required to modify the severity at the time boundary if the signal remains in alarm.