Configurable/dynamic delay of alarm redirection?

[AppSupport]

Hi, we have a user requirement to allow an operator to dynamically enter a delay time for an alarm redirection... eg:

- Operator acknowledges alarm and enters a required time period

- Alarm reannunciates after specified time

Is there any way of passing the chosen time parameter into an alarm redirection as the delay period?

We have some configured redirections, and we use delays on some of these, but these are fixed whereas here the operator wants to choose the time period at the point of acknowledgement.

[BevanWeiss]

Not that I'm aware of.
It is possible to retrigger Alarm Redirections from Logic.  And the Alarm Redirection itself can be Logic... so what you can do is have something like the Alarm Redirection fire every 1 minute.  The Logic just looks to see if it should escalate.  If so, then it escalates it.  If not, then it just restarts the Alarm Redirection (resetting the timer, so in another 1 minute the logic will trigger again).

Notes: Be VERY careful what you set that time to.  Don't be smart and think 1s is a good value.  1 minute is an 'ok' value if you'll only have a few such alarms active.  If you'll have more than 60 alarms calling this logic, then it's possibly a bad plan.  You'd really want to do some performance testing.

The other option is to have the Logic such that it can manipulate the Configuration of the object to re-write the Alarm Redirection time (before re-triggering).  However, this writes to the Configuration Stream, has DB lock considerations, general IO performance considerations, and I generally don't like this idea (because once you've got Logic writing to Configuration fields like this it becomes a slippery slope).

The nicest might be to just have some set options for operators to assign, i.e. delay 5minutes, delay 15minutes, delay 30minutes, delay 1hr, delay 4hrs, delay 8hrs, delay 24hrs etc.. and then you could have Alarm Redirections for a very specific Alarm Severity range (i.e. AlarmDelayed5Min = 110-119, AlarmDelayed15Min = 120-129, AlarmDelayed30Min=130-139, AlarmDelayed1Hr = 140-149, etc...) and then the Logic just sets the Alarm Severity to the appropriate delay value (i.e. 141 for a 1Hr delay on a natural Severity 1 alarm), and then the Alarm Redirections for 140-149 will have a delay of 1hour and will escalate that delayed 141 severity up to 201 after 1 hour, where it will show up in the operator banner.  Having an operator enter a time at Acknowledgement doesn't quite work.. the alarm instance may or may not be active at this time.. and changing alarm severity (outside of Configuration Changes) only applies for a currently active alarm instance.