The second step to sending out alarm notifications is creating an On-Call Roster. An On-Call Roster is a collection of users that are notified when an alarm occurs. When an alarm is triggered, it is sent to a designated On-Call Roster where it evaluates the users schedules, and only notifies those users that have an active schedule. Users that are off-schedule will not be notified. The On-Call Rosters are setup in the Configure Section of the Gateway Webpage.
Alarm Notification Profile
The Notification Profile is the third step, and determines what type of notification (Email, SMS, or Voice) is sent out. The notification profile typically connects to an outside system that can do the actual notification. Each alarm notification type can be configured for both one-way and two-way notifications. A notification profile will be set up in the Configure section of the Gateway Webpage.
Alarm Notification Pipeline
The next step is setting up an Alarm Notification Pipeline. The Alarm Notification Pipeline creates a list of actions that the alarm will do. A pipeline can send out notification using pre configured Notification Profiles and On-Call Rosters, and can have logic to determine who to notify and when. Alarm Notification Pipelines have a section in the Ignition Designer where they are created.
The last step of the alarm notification process is to add an Alarm Notification Pipeline to a Tag. Every alarm on a Tag can have a pipeline set up that the alarm will use when the alarm becomes active, which is most common, but can also use a pipeline to notify users when ana alarm becomes acknowledged or gets cleared. This last step of the process is configured on individual alarms on Tags.