Contents
Strategic Partner Links
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Resources
Knowledge Base Articles
Inductive University
Forum
IA Support
SDK Documentation
SDK Examples
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Knowledge Base Articles
Inductive University
Forum
IA Support
SDK Documentation
SDK Examples
It is possible to setup escalation procedures in alarm notification pipelines in Ignition. The following example will create a pipeline that notifies operators three times. If a user does not acknowledge the alarm after the third time, the alarm escalates to the Production Supervisor’s on-call roster.
The following example requires that two separate on-call rosters have been configured ("Production Supervisors" and "Operators"), as well as an email notification profile.
If the alarm is still active and not acknowledged, the counter will increment by 1. In order to increment the counter, drag in another Set Property Block and connect the OUT of the Notification block to the IN of the Set Property block. You can right click on the Set Property block to reverse the orientation.
A Note on Syntax
The Set Property Block's Property Value uses Ignition's Expression language. More information on the Expression language can be found on the Expression Overview and Syntax page.
In the Pipeline Block Editor, set the Property Name to ‘numCalls.' In the Property Value Expression type in, ‘{numCalls} + 1.’ In this expression, use the curly braces to refer to that variable so the counter gets incremented by 1.
As you can see, when the Escalate Pipeline sets the ‘numCalls’ variable to a value of 0, it’s going to notify the Operators on-call roster through email that the alarm is active. It will wait 5 minutes, and if the alarm is still active, it will increment the counter by 1. This will repeat until the ‘numCalls’ is > 3. After the 3rd time, if the alarm is still active and in the pipeline, then the Production Supervisors will be notified. Keep in mind, that if the alarm at any point meets the dropout conditions, it will not go to the next block of the pipeline.
You can also use the Jump Block as your escalation instead of a second Notification Block. This will allow you to jump into another complete pipeline when nobody answers.