Avoiding Alarm Fatigue Using Condition Based Alarm Limits in TruVu360

Introduction 

Creating an effective lubrication program consists of many parts from selecting the appropriate equipment to test to selecting the right parameters to test on the oil.

While these are both important steps not be overlooked, the most daunting part tends to be setting alarm limits on equipment. The challenges include setting limits too conservatively, increasing the chances too many components alarm. This can leave an overwhelming number of work orders and likely stretch the budget to maintain the strict levels. On the other hand, setting alarms too loosely leaves a greater risk of missing a critical alarm and can pose a safety risk.

To overcome these challenges associated with alarm limits, TruVu 360 now offers a Condition Based Alarm feature based on statistical evaluation of alarm limits using ASTM D7720 Standard Guide for Statistically Evaluating Measurand Alarm Limits when Using Oil Analysis to Monitor Equipment and Oil for Fitness and Contamination.

The statistical evaluation using D7720 can be applied to all existing component types within TruVu 360. A historical sample set of at least 80 samples within a component type is required to complete the calculation.

Using the guidelines outlined in the ASTM D7720, TruVu 360 produces an output that helps the user:

• Evaluate current alarm limits in each limit set to determine if current alarm limits are effective.
• Recommends adjustments of alarm limits per limit set based on historical data (>80 samples needed).
• Evaluate the effectiveness of current alarms vs recommended alarm limits.
• Carefully and systematically develop an alarm strategy that is achievable and sustainable.

Admin-level user permissions are required to generate the calculations and change alarm limits within a component type. On the next page is a typical output the user will see.

Statistical Evaluation of Alarm Limits to ASTM D7720

1. Sample Count: The number of samples in the limit set.
   
2. Abnormal Limit – Current: The current abnormal limit used in the limit set for the corresponding parameter.
   
3. Abnormal Limit – Recommended: The recommended abnormal limit that may replace the current abnormal limit. The abnormal limit is calculated according to ASTM D7720.
   
4. Percent Abnormal – Current: The percent of samples that triggered abnormal alarms for the corresponding parameter.
   
5. Percent Abnormal – Recommended: The recommended percent of samples that should trigger abnormal alarms. The value is based on statistics outlined in ASTM D7720 and is dependent on the sample count. Note: A large difference between the current and recommended percent of alarms may indicate that the alarm limits should be updated.
   
6. Severe Limit – Current: The current severe limit used by the limit set for the corresponding parameter.
   
7. Severe Limit – Recommended: The recommended severe limit that may replace the current Severe limit. The severe limit is calculated according to ASTM D7720.
   
8. Percent Severe – Current: The percent of samples that triggered severe alarms for the corresponding parameter.
   
9. Percent Severe – Recommended: The recommended percent of samples that should trigger severe alarms. The value is based on statistics outlined in ASTM D7720 and is dependent on the sample count. Note: A large difference  between the current and recommended percent of alarms may indicate that the alarm limits should be updated.
10. 0%: The 0th percentile of the corresponding parameter in the sample data. This is equivalent to the minimum value.
11. 25%: The 25th percentile or 1st quartile of the corresponding parameter in the sample data. 25% of the data are less than this value.
12. 50%: The 50th percentile or median of the corresponding parameter in the sample data. 50% of the data are less than this value.
13. 75%: The 75th percentile or 3rd quartile of the corresponding parameter in the sample data. 75% of the data are less than this value.
    1. The percentile result for each property can help in determining if the recommended limit is reasonable. If the values for the percentiles steadily increase with increasing percentile, then the recommended limit should represent the statistics of the parameter.
    2. If all of the percentiles are 0 or near the LOD then the recommended limits should be carefully reviewed because they may be set too low, which could allow noise to trigger alarms.

Conclusion 

Alarm fatigue can get in the way of lubrication programs making small improvements over time. However, utilizing the concept of condition-based alarms can help users avoid this. By carefully and systematically using data to drive alarm limits, the user can set more effective and practical alarms which can sustain maintenance efforts year after year. For assistance in utilizing this feature, please contact Spectro Scientific Support.