Alarm Notification
The Alarm Notification module allows you to send messages to groups of users when alarms become active, acknowledged, or cleared. This functionality requires the Alarm Notification module to be installed, along with alarm pipelines and at least one configured notification profile. Additional modules like the SMS notification and Voice notification modules extend this functionality to include additional communication methods.
Notification Contact Info​
To send alarm notifications, users need contact information, such as email addresses or phone numbers. This information is managed through the Platform > Security > User Sources section in the Gateway. Users typically have contact information added when their accounts are created, but it can also be updated as needed.
On-Call Rosters​
An On-Call Roster is a collection of users who should receive notifications when an alarm occurs. Rosters evaluate user schedules to ensure only those with active schedules receive notifications, preventing unnecessary alerts. Configure rosters in the Services > Alarming > Rosters section of the Gateway.
Notification Profiles​
Notification Profiles define how alarm notifications are sent, such as via email, SMS, or voice calls. Profiles connect Ignition to external systems for message delivery, supporting one-way and two-way communication. Configure profiles in the Services > Alarming > Notification section of the Gateway.
Alarm Pipelines​
Alarm Pipelines define the logic for handling alarm notifications, including routing, escalation, and filtering. Pipelines are created and managed in the Ignition Designer. The Services > Alarming > Pipelines section of the Gateway provides an overview of active pipelines, including details like the pipeline name, path, active status, and current items. Clicking the ellipses next to a pipeline entry reveals additional details, including the source, display path, block, time in block, status, and a log of recent activity.
Assigning Pipelines to Tags​
After creating pipelines, you must assign them to individual alarms. This is done in the Ignition Designer. To assign a pipeline to a tag:
- Open the Tag Browser and double-click the tag you want to edit.
- In the Tag Editor, select the Alarming section.
- Choose an alarm, then select the desired notification pipeline.
- Save your changes.
Once a pipeline is assigned, the alarm will use it whenever it becomes active, acknowledged, or cleared, depending on the pipeline configuration.
Testing Alarm Notifications​
Ignition 8.3 includes a Test button for verifying alarm notifications directly from the Gateway. To test your alarm notification configuration:
- Go to the Services > Alarming > Notification section of the Gateway.
- Click the Test button next to the Create Profile button.
- In the sidebar that appears, configure the following:
- Pipeline: Select the pipeline you want to test.
- Display Path: (Optional) Enter a display path to help identify the test event.
- Priority: Choose a priority level for the test (Diagnostic, Low, Medium, High, Critical).
- Click Submit to initiate the test.
- Use the progress table to monitor the test, which includes columns for:
- Source: The originating source of the test.
- Display Path: The path entered during the test setup.
- Block: The current block in the pipeline.
- Time in Block: The time the test has spent in the current block.
- Status: The current status of the test.
- Config: Provides a cancel option for active tests.
Testing through the Gateway ensures that your pipelines, notification profiles, and rosters are correctly configured before going live.