Use the search and browse feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Search Solutions Results By: View All Solutions

Kepware Knowledge Base: Solution


What Are the Custom Alarm Conditions in the Alarms and Events Plug-In?


Last Update: 11/12/2018

The Alarms and Events plug-in supports nine conditions that are separated into three categories: Multi Level, Rate of Change, and Deviation. Each condition has a unique name and set of sub-conditions.

  • MULTI_LEVEL: MULTI_LEVEL conditions support multiple sub-conditions, which include HI_HI, HI, LO, and LO_LO. This condition should be used if the source has multiple states of interest (and if users want to know when the condition transitions between states). For example, this condition should be used when a temperature tag with multiple temperatures of interest is being used. The HI_HI sub-condition has the highest priority; the LO_LO sub-condition has the lowest. The condition is in the HI_HI state when all the sub-conditions are active.
  • HI_HI, HI, LO, LO_LO: These single level conditions contain a sub-condition that matches the condition name. These conditions should be used if there is a single state of interest for the source. For example, this condition should be used if a temperature tag with a single temperature of interest is being used. To follow convention, use HI_HI for high priority states and LO_LO for low priority states.
  • ROC_HI, ROC_LO: Rate of Change (ROC) conditions have a single sub-condition that matches the condition name. They are used to compare the source to a static or dynamic ROC. For example, this condition should be used if using a source tag that represents production output (and when users want to trigger the condition if the output falls below 100 units a minute). To follow convention, use ROC_HI for high priority conditions and ROC_LO for low priority conditions.
  • DEV_HI, DEV_LO: Deviation conditions have a single sub-condition that matches the condition name. They are used to monitor the deviation of the source and trigger the condition if the source exceeds the limits set by the deviation. For example, this condition should be used if using a source that monitors power consumption (and when users want to trigger the condition if the power consumption is outside of 100W 20%). To follow convention, use DEV_HI for high priority conditions and DEV_LO for low priority conditions.

Note: For real-world examples, refer to the Alarms and Events product manual.

Related Products
Alarms and Events