PredictivePortal uses the terms Alarms, Alerts, and Notifications when setting up how users interact with faults or abnormal conditions of a machine. Alarms, Alerts, and Notifications all work together but have different criteria that defines how a user will interact with the system
Alarms = an exceedance from a threshold.
For scalar data, you can set a Warning and Critical Alarm level for temperature and Velocity RMS. For diagnostic data, alarms are based on the average baseline. When an alarm is breached, it will only appear when viewing the data, such as an indication of a threshold has been exceeded in a scalar trend plot or spectra amplitudes that exceed the average baseline.
Alert = an alarm exceedance plus user defined criteria.
For scalar data, the criteria includes persistence of the alarm. The user can set the criteria as either aggressive (1:1, where any alarm will create an alert) or relaxed (x:y, where x number of alarms must occur in y number of hours to create an alert. The default is 3 alarms in 12 hours). For diagnostic data, the alert (formerly event) is defined as the EADS criteria to generate the severity-based fault. Diagnostic data will soon have persistence logic also available that will ensure a fault is stable before getting an analyst’s attention.
Notifications = an alert plus user defined criteria.
Not all users need to be notified when an Alert happens. A user can set the criteria for when they want to receive a notification of the Alert. Commonly, this includes hierarchy level and repair priority, but will also include other criteria.