How to choose the alarm condition
The platform provides a flexible set of alarm conditions that can be applied to any device or parameter across the system. These conditions help identify operational anomalies, device failures, or behavioral thresholds in real-time or over a period of time.
Users can select from the following alarm condition types when configuring alarms:
Threshold
Threshold with Duration
Counter
Counter with Duration
Flapping with Duration
Each condition type offers different capabilities suited for specific operational needs.
1. Threshold
Description
This condition checks whether a selected parameter meets a predefined threshold.
When the real-time data meets the specified operator condition against the threshold value, an alarm is triggered.
Supported Object Types
All object types (Analog, Binary, Multistate)
Operator Types
Analog:
Greater than ( > )
Greater than or equal to ( ≥ )
Lesser than ( < )
Lesser than or equal to ( ≤ )
Equal to ( = )
Binary / Multistate:
Equal to the state
Not equal to the state
Examples
Analog:
Room temperature > 25°C
Light intensity > 80%
Tab battery ≤ 20%
Gateway network strength < 50%
Binary:
AC is in "trip" state
Sensor is "occupied" during night hours
Multistate:
AC is in "heating" mode
2. Threshold with Duration
Description
Extension of the Threshold condition with an added time duration.
Alarm triggers only if the threshold condition is continuously met for the selected duration.
Time Options
Minutes
Hours
Examples
Analog:
Room temperature > 25°C for 30 minutes
Light intensity > 80% for 1 hour
Tab battery ≤ 20% for 15 minutes
Gateway network strength < 50% for 10 minutes
Binary:
Pump is ON for more than 2 hours
Sensor is "occupied" during night time for 30 minutes
Multistate:
AC is in "heating" mode for 20 minutes
3. Counter
Description
Counts the number of times a selected condition is met.
Triggers an alarm when the count reaches the defined threshold.
Applicable To
All object types (Analog, Binary, Multistate)
Supported Operators
Count = N
Count > N
Required Fields
Parameter
Expected State
Count to match
Examples
AC powered ON 2000 times
Pump powered ON 100 times
Pump trip status occurred 5 times
Light node rebooted 5 times
4. Counter with Duration
Description
Same as the Counter condition but restricted to a specific duration.
Useful for identifying patterns or anomalies over time.
Time Options
Minutes
Hours
Days
Months
Examples
AC powered ON 2000 times in a month
Pump powered ON >10 times in an hour
Pump trip status occurred 5 times within 30 minutes
Light node rebooted >5 times within 10 minutes
5. Flapping with Duration
Description
Detects frequent back-and-forth switching (e.g., On-Off) between two states in a short duration.
Typically used to detect device instability or faults.
Applicable To
All object types (Analog, Binary, Multistate)
Required Inputs
Parameter
State 1 - Eg: On, Off or 30 C
State 2 - Eg: On, Off or 30 C
Count
Duration (Minutes or Hours)
Note: This condition doesn’t require an operator. It inherently tracks state oscillation between two extremes.
Examples
AC toggles between On and Off 3 times in 5 minutes
Room temperature fluctuates between <15°C and >30°C once in 30 minutes
6. Multi-Condition Alarms (Using AND / OR Logic)
Multi-condition alarms allow you to create compound rules by combining two or more conditions using logical operators:
AND: All conditions must be satisfied for the alarm to trigger.
OR: At least one condition must be satisfied for the alarm to trigger.
This is useful when monitoring systems that may exhibit abnormal behavior under a combination of events or when multiple parameters contribute to a fault state.
Supported Logic
You can mix different condition types (e.g., Threshold + Counter, Threshold with Duration + Flapping).
You can have multiple conditions of the same type for different parameters (Threshold)
Examples
Example 1: AND Condition
Trigger an alarm only if all of the following are true:
Room temperature > 28°C for 20 minutes
AC is in "ON" mode
Interpretation: This could be used to detect if the AC is ineffective and not cooling sufficiently.
Use AND for specific, tightly controlled fault conditions.Example 2: OR Condition
Trigger an alarm if any one of the following is true:
Room Temperature < 18 C
AC Alarm parameter is Active
AC is off
Interpretation: This helps detect any form of anomaly in a Server room AC
Use OR for broad-based monitoring where any anomaly is worth alerting.Quick Summary
Related Articles
Alarm History Page Overview
1. When any device meets the criteria of the alarm rule, an alarm is triggered. 2. When the alarm is triggered selected users will get notified. 3. Once the users check the device and mark the alarm as Done, the alarm details gets stored in the alarm ...Creating an alarm rule
Go to the Alarms module, select the “New Alarm” button in the top right corner. Alarm creation page opens up. 3. There are 5 sections to create an alarm Alarm Details - Mandatory Alarm Names to be added in such a way that the alarm can be recognized ...Alarm Rules Page Overview
Alarm rules define conditions that trigger alerts in monitoring systems. These rules use metrics, thresholds, or events to detect anomalies or critical situations. They ensure timely notifications to the right stakeholders, enabling quick response to ...Handling Alarms once they get triggered
This document outlines how alarm triggers are defined, how users are notified, and the different states an alarm can go through during its lifecycle on the platform. What is a Alarm Trigger ? An alarm trigger is an event generated when a pre-defined ...How To Set Preventive Maintenance (PM) Trigger Scheduling?
To set preventive maintenance (PM) trigger scheduling, follow these steps: Go to the maintenance page On the left panel, find "preventive maintenance." On the preventive maintenance page, you will see a list of existing PM tasks. To add a new one, ...