1. Home
  2. Fundamentals
  3. Abnormal Condition Message Priority

Abnormal Condition Message Priority

Objects can only display 1 abnormal condition message at a time so there is a priority system in place to determine which message is displayed.

Message Priority:  

The first condition with the highest action with highest severity or the first elevated condition (active conditions are processed first)

Severity Info vs None 

Info set the {object}.AC.InfoAlarm which does nothing except for CMs where it sets the Alert.  For all other objects it is identical to none.

In general the InfoAlarm holds the object in an alarm

EM – Nothing

CM – Sets CM.Sts.Alert along with actions: Alert, Fault, Trip; and severities: Warning and Critical.

Permissive condition should alert if trying to start

Info can alert

Alert options 

  • Set alert if trying to start but doesn’t have permissive?  Not currently
  • Set alert if alarm and active or trying to start
  • Set alert if action and active or trying to start
  • Set alert if Alert is true when active or trying to start
  • How should options affect alerting?


  • Alert – Object is functional but has a noteworthy condition.  Hardware related alerts are always active while process alerts are only active while running.
  • Perm – Object has a condition preventing it from starting.  However, once started this is not a consideration.  This condition is disabled after starting and will not display or alert.  It will alert if the object is trying to start.
  • Fault – Object has a condition preventing normal operation but isn’t tripping so normal operation may resume once the condition has been resolved.
  • Trip – Object has a condition that prevents normal operation and was shutdown requiring operator intervention to restart.
  • Trip_Oper – Same as trip except it will also trip in operator mode.


Updated on December 6, 2018

Related Articles

Password Protected