As with most words there are multiple meanings of the same word and mainly because of either the usage of the word or what action it describes. In this series we will examine the various aspects of alarm management indicators and determine what the main culprits of control systems or equipment alarms that are causing so much operator activity or failure to act. The first of which is – Frequency.
1. the fact or condition of occurring frequently
the frequency of hurricanes during summer
2. the ratio of the number of actual occurrences to possible occurrences of an event
3. the relative number of times something occurs in a given sample
For alarm management, definition 3 applies the best.
Alarm Activity Analysis Overview
To understand how activity analysis can contribute to alarm management one must understand the Alarm Management Life Cycle. It consists of configuring the Control System according to a planned methodology designed to ensure that equipment malfunctions, process deviations and abnormal conditions are defined and communicated to the operator who may then act in an appropriate or designed response. Our focus on frequency will be highlighted as being in the Monitoring and Assessment stage of the Alarm Management Life Cycle.
The American National Standards Institute (ANSI) in conjunction with the International Society of Automation (ISA) set forth standards relating to how well the Control System manages the production process. The standards have been prepared toward a goal of uniformity in the field of automation which includes instrumentation standards, recommended practices, and best practice technical reports. The standards are also adopted globally as defined by the International Electrotechnical Commission (IEC).
These standards are outlined in ANSI/ISA-18.2-2016 and include the following recommended best practices, which are based upon 30 days of data:
TiPSView ACE Analyses in the LogMate suite are specifically designed to determine how well the plant is performing relative to the ISA 18.2 standard.
What is the Purpose of Frequency Alarm Analysis?
The frequency of alarm activations are used to detect and alert operators about specific conditions that occur for a specific time period, often indicating potential issues in a process. Proper application of frequency alarm analysis requires context-based filtering to avoid indiscriminate triggering under unhelpful circumstances. Diagnostic alarming functions can help identify issues like degradation in equipment, but they must be carefully managed to prevent overwhelming operators with too many alarms at once.
Correcting alarms that occur too often involves several steps, including review of the alarm configuration, prioritization, and continuous monitoring for feedback. First, ensure that alarms are correctly set up to reflect the actual process conditions and not trigger unnecessarily. Implementing advanced alarm logic and regular reviews can help maintain the effectiveness of the alarm system and prevent operator overload.
How Serious are Alarms that Activate Repeatedly in Processes?
Alarms that activate repeatedly in processes are quite serious and important. They serve as critical indicators of abnormal conditions that could affect the safety, efficiency, or quality of a process. Here’s why they matter:
- Safety: Repetitive alarm activations can signal that a process is deviating from normal operating conditions, which might indicate potential safety hazards. For instance, in a chemical plant, repetitive alarm activations could alert operators to an unexpected increase in reaction speed or temperature, which might lead to unsafe conditions.
- Operational Efficiency: Processes often need to run within specific operating ranges to maintain optimal efficiency. A repetitive alarm might indicate equipment malfunctions or process imbalances, which could lead to reduced efficiency, higher costs, or equipment damage.
- Quality Control: Many processes have strict quality requirements. Deviations from expected process results can impact the consistency and quality of the final product. This could trigger legal and governmental compliance issues. Alarms help ensure that the process remains within the desired parameters to meet quality standards.
- Preventive Maintenance: Repetitive alarms can be early warnings of equipment wear or failure. By alerting operators to abnormal frequencies, these alarms can help in scheduling maintenance before a minor issue becomes a major problem, thus preventing costly downtime.
How Do You Handle Repetitive Alarms in Processes?
Identifying repetitive alarms in processes involves several steps and tools to ensure that abnormal conditions are detected early. Here’s a general approach to identifying and managing frequent alarms:
- Understand Normal Operating Ranges: Know the normal operating ranges for your processes and equipment. This involves understanding the typical operating conditions and performance metrics for each part of the system.
- Set Up Monitoring Systems: Use process control systems and monitoring tools (such as SCADA systems, Distributed Control Systems (DCS), building facility controls (HVACs or PLCs), or process historian applications) to continuously track process variables.
- Configure Alarms: Set up alarms based on predefined thresholds. These thresholds are typically configured based on historical data, industry standards, and manufacturer recommendations. Ensure that the alarms are configured to detect deviations that are significant enough to warrant attention.
- Real-Time Monitoring: Continuously monitor process variables in real-time. Advanced monitoring systems can display data trends and highlight anomalies. Alarms often appear as alerts or notifications on these systems when data deviates from the normal range.
- Data Analysis: Use data analysis tools to review historical data and identify patterns. Repetitive occurrences of alarms can indicate underlying issues. Trend analysis helps in understanding whether alarms are due to sporadic anomalies or systemic problems.
- Alarm Prioritization: Not all repetitive alarms are of equal importance. Prioritize alarms based on their impact to safety, operational efficiency, and product quality. High-priority alarms should be addressed immediately, while lower-priority alarms can be reviewed after addressing higher priority alarms.
- Operator Training: Ensure that operators are trained to recognize and respond to repetitive alarms appropriately. They should understand how to interpret alarms and follow proper procedures for troubleshooting and actions.
- Review and Adjust: Regularly review alarm settings and thresholds. Adjust them as needed based on changes in process conditions, equipment performance. or operational goals.
- Root Cause Analysis: When an alarm is triggered, perform a root cause analysis to determine the underlying issue. This helps in addressing the core problem rather than just reacting to the symptoms. This is one of the steps in reducing frequently occurring alarms.
- Documentation and Reporting: Maintain documentation of alarm occurrences, responses, and resolutions. Regularly review alarm reports to identify trends and areas for improvement. Collaboration of your team, good engineering standards, and set procedures will go a long way in decreasing the number of frequently occurring alarms.
Interpreting Frequency Analysis Using TiPSView ACE
A Frequency Analysis displays the number of times a record attribute occurs. It is essentially a count of record instances, grouped by any field in LogMate, filtered by any criteria specified in the analysis configuration, and usually sorted from most to least frequent. For example, a frequency analysis may be performed against a tag and its specific alarm type. This exposes the alarms that generates the most system and operator stress and is an excellent way to pinpoint the top candidates for review and corrective action.
ISA 18.2 Standards recommend that “The percentage contribution of the top 10 most frequent alarm load be held to ~<1% to 5% maximum, with action plans to address deficiencies” and is based on at least 30 days of data.
The TiPSView ACE Frequency Analysis is an excellent tool that may be used to see how well the SCADA/Control System is able to meet the ISA best practice requirement.
Each analysis results screen consists of the same elements, a chart, and a tabbed table with detailed information. The chart and the ‘Results’ tab below the chart reflects each other. They display the same data and are sorted by the same field. The chart is easy to interpret at a glance.
The alarm count for the period specified is displayed, sorted from the highest count to the least. Recall that ISA 18.2 standards recommend that “The percentage contribution of the top 10 most frequent alarms to the overall alarm load to be held to ~<1% to 5% maximum, with action plans to address deficiencies” and is based upon at least 30 days of data.
The ’Accum’ column shows that the top 10 alarms contribute well over the 5% specified as a maximum to the overall alarm load for the period. According to the ISA standards this is far higher than we would like to see. Further investigation is required to see if the root cause for the excessive alarm rates can be determined.
This particular analysis was run for an entire month (hence the high alarm counts) and the configuration include statistics for the Alarm Limits. The statistics are displayed in the ‘Count, Percent, and ‘Accum’ columns and can provide additional valuable information to the user. Note the first record, Tag AI071-9, which accounts for 35.61% of the total alarms for the period. The alarm count is 18708.
Now what does that really mean? This means that the process value of this tag has activated the HI_ALM setpoint more than 18,708 times in a 30 day period which represents 35.61% of the alarms recorded during this time period. Why? Is the alarm point set too low for normal conditions? Has the calibration of the instrument shifted? Have actual operating conditions changed due to a change in temperature or catalyst? Has a change in operating procedures had more of an affect than anticipated? Is this alarm triggered by another alarm? This is where operating knowledge, best engineering judgement, and alarm rationalization aid with understanding root cause.
Solving Repetitive Alarms in Your Process
- Verify the Alarm: Confirm that the alarm is accurate and not a false positive. Check the monitoring system and validate that the frequency deviation is genuine and not due a temporary glitch or calibration issue.
- Assess the Impact: Determine the severity of the alarm. Evaluate how the consequence severity affects process safety, efficiency, and quality. This helps prioritize the response and understand the potential consequences.
- Check Historical Data: Review historical data and trends for the affected parameter. Look for patterns or recurring issues that might provide clues about the cause of the alarm.
- Inspect Equipment: Conduct a physical inspection of the equipment or instrumentation associated with the alarm. Check for signs of wear, damage, or malfunction that might be causing the abnormal frequency.
- Review Process Parameters: Ensure that all process parameters are within their expected ranges. Check if changes in other variables could be affecting the frequency.
- Analyze SCADA/Control System Settings: Verify the settings of SCADA/control systems and calibration of instrument sensors. Incorrect settings in your SCADA/control system database or calibration errors/drift in instrumentation can lead to false alarms or improper frequency measurements. An incorrect range setting or calibration of an oxygen analyzer could result in an increase of unnecessary alarms and possibly safety considerations.
- Consult Documentation: Refer to equipment manuals, process flow diagrams, and standard operating procedures for guidance. This documentation can provide insights into normal operating conditions and troubleshooting steps.
- Perform Troubleshooting: Use troubleshooting procedures to systematically test and isolate potential causes. This may involve mechanical issues, electrical faults, or software problems.
- Correct the Issue: Based on your findings, implement corrective actions. This might involve repairing or replacing faulty equipment, adjusting process parameters, recalibrating sensors, or making changes to the SCADA/control system settings.
- Test and Validate: After making corrections, test the process to ensure that the issue is resolved. Monitor closely to ensure that the alarm does not reoccur.
- Update Procedures: If the issue was due to a process or equipment change, update standard operating procedures, instrument sheets, and maintenance schedules to prevent similar problems in the future.
- Document and Report: Document the alarm event, the steps taken to resolve it, and any changes made. Reporting these details helps in maintain a history of issues and responses, which can be useful for future troubleshooting and continuous improvement.
- Implement Preventive Measures: Based on the root cause analysis, implement preventive measures to avoid similar issues in the future. This could involve changes in maintenance practices, additional training for operations, or upgrades to equipment and systems.
- Review Alarm Settings: Periodically review and adjust alarm thresholds and settings based on updated process conditions and performance data to ensure they remain appropriate.
By following these steps and using TiPSView ACE Frequency Analysis, you can effectively address and resolve repetitive alarms, ensuring that the process remains stable and efficient while preventing future occurrences. Contact for a demo here.



