Alarm redirections can be triggered automatically, manually, or both (see Understand Alarm Redirection). However, Geo SCADA Expert will not trigger alarm redirections on any:
- Alarms that do not meet all of the redirection criteria (the criteria is configured on the Redirection tab of the relevant configuration Forms—see Configure Alarm Redirections for an Item or Group)
- Alarms that are disabled (see Disable Alarms in the Geo SCADA Expert Guide to Alarms)
- Alarms that are suppressed (see Alarm Redirection and Suppressed Alarms)
- Items or Groups for which the CancelRedirections method is used to abort alarm redirections (see CancelRedirections and RestartRedirections Methods)
- Alarms that are configured to redirect to the users in a User Group or User Roster, but at least one of the users in that User Group or User Roster does not meet the Inhibit Action criteria. For example, if the Inhibit Action requires that none of the users in the User Group or User Roster are logged on to Geo SCADA Expert from a ViewX and/or Virtual ViewX client, but Geo SCADA Expert determines that at least one user in that User Group or User Roster is logged on via such a client. (This criteria only applies to E-Mail Actions, Pager Actions, and Method Action (User) redirection actions (for more information, see Define the E-Mail Action Details, Define the Pager Action Details, or see Define the Method Action (User) Details, as applicable).)
(With such a scenario, it is assumed that the user(s) that are logged on are manning a workstation and will take appropriate action when they see that the alarm has been raised. As such, Geo SCADA Expert aborts the redirection.)
- Alarms that are configured to redirect to the 'Duty User' in a User Roster, but no 'Duty User' has been defined for that User Roster. (By default, when you add a new User Roster to the database, no 'Duty User' is selected, so you have to specify the required 'Duty User' for the User Roster (see Specify the Duty User).)
- Alarms that are configured to redirect according to geographical criteria, but none of the intended recipients meet that geographical criteria. For example:
- None of the users are assigned a suitable Region
- None of the users have geographical coordinates (if the redirection criteria requires these for determining whether the users are within the relevant geographical region).
For more information, see Specify Whether to Redirect Alarms to Users According to Geographical Criteria.
- Items or Groups on which specified redirection Action, Action Roster, and alarm redirection Calendar is inactive. (As with most database items, a redirection Action, Action Roster, and alarm redirection Calendar needs to be In Service in order to be active on the system.)
- Lone server systems on which the server is shut down while alarm redirections are in progress. On lone server systems, any pending alarm redirections will be lost and the intended recipients will not be notified. (On multi-server systems, the alarm redirections will still be sent to the recipients, but from the Standby server that goes Main.)