Alarm routing setup

You define who to notify when an alarm event occurs by setting up one or more AlarmClass components and AlarmRecipients. Station-to-station alarm routing requires setup in both stations. Routing to an email or Sms recipient is configured in the point extension of the source.

How many alarm classes and recipient components to connect depend on your needs. For routing to a remote station, you specify the alarm routing in the Alarms extension under the Niagara Station that represents the remote JACE.

• To have a variety of alarming and routing options available for selection from the alarm extension properties, you would set up multiple alarm classes. For example, you may set up an alarm class that routes to the ConsoleRecipient and StationRecipient, while another alarm class routes alarms only to an email recipient.

  
  
  

• To configure alarms in one station (usually a station on a controller) to be received in another station (usually the supervisor station), you would add an AlarmClass component and a StationRecipient in the AlarmService container of the sending (source) station. You then link the AlarmClass component to the StationRecipient.

  It is not necessary to use the same AlarmClass components in the two stations (although that is one approach). In the receiving station, if desired, you can configure all alarms from a remote station to route to a single local AlarmClass. Or, you can also use a “prepend” or “append” scheme to route to different (but associated) AlarmClasses, where all schemes work based on the names of the AlarmClasses.

  Note: In the receiving station’s AlarmService, if you want the remotely-generated alarms to appear in any alarm consoles, be sure to link associated AlarmClass components to the necessary AlarmConsole components.