20 March 2023
Sometimes there is a need to restart alarm redirection sequence if a particular alarm does not get acknowledged or cleared in specified time. Consider an example where a redirection action is configured to send an e-mail once a point goes into alarm. If the alarm does not get cleared within 30 minutes, another e-mail needs to be sent out. The e-mails should be sent out repeatedly every 30 minutes until the alarm is cleared.
This can be achieved by using the RestartRedirections() method. Below is a quick run through on how this method could be used.
1. Consider an analog point named Pressure with an alarm redirection action configured to send an e-mail whenever the point is in alarm.
2. Locate this E-Mail Action in Database Explorer and assign this action to a particular redirection group for which alarm redirection needs to be restarted. If no redirection groups have been configured yet, type in an arbitrary name to create a redirection group.
3.Create new Method Action and specify Method Object. In this case, Method Object is going to be the object for which alarm redirection needs to be restarted. Select Restart Redirections as Method. Enter the redirection group's name in single quotes ('Redirection Group Name') as the value for the Redirection Group argument.
4. Add the newly created method action to the list of redirection actions in point's properties. Make sure to specify a delay to restart alarm redirection.
Only redirection actions configured under the same redirection group (PressureGroup in this case) will be restarted. Do not assign other redirection actions to the same redirection group if they do not need to be triggered repeatedly. Make sure the method action is also assigning the same redirection group (PressureGroup in this case) to be triggered again.