How to Trigger an Alert Based on a Downtime Reason Code
In OFS-Flow, you can set up alerts and flows to fire when a specific downtime reason is selected on the operator console. This is ideal for notifying maintenance or supervisors of critical issues.
Step 1: Create the Alert Configuration
-
Navigate to Fusion Manager > Alerts & Flow > Alerts
-
Select an existing Alert Group or create a new one by clicking the + button
-
Click the + button under the Alerts section and name your alert (e.g., "Critical Pump Failure Alert")

-
In the General tab, enter the Alert Message that will be sent. You can use variables to make it dynamic, such as:
has stopped due to
⚠️ The Important Caveat (Operator Timing)
There is a specific limitation when triggering alerts based on reasons:
-
The 30-Second Window: When a line stops, the system initially records the state as "Unplanned". Operators have 30 seconds to set the specific reason code for the alert to fire correctly based on that "Start" trigger.
-
The Workaround: If your operators typically take longer than 30 seconds to allocate downtime, you should offset the trigger by 5 minutes. This allows the operator enough time to select the reason before the system checks to trigger the alert.
Step 2: Configure the Machine State Trigger
-
Go to the Triggers tab within your alert
-
Click the + button and select Machine State
-
Choose the specific machine state you want to trigger from (e.g., Downtime)
-
Toggle Offset to ON
-
Enter '5' for the number of minutes or the desired time
-
Select the Lines this alert should apply to
-
Click Reason or Category and toggle ON
-
Select the Reason Set and select the Reason Code

Step 3: Link to a Service
-
In the Triggers tab of your alert, select the Service (Email or SMS) that should receive the notification.
-
If you haven't created a service yet, you can do so in Alerts & Flow > Services by entering the recipient's email address. Video link.
