<img alt="" src="https://secure.office-information-24.com/785791.png" style="display:none;">

What's New @ Casne

Predictive Alarm Management: Benchmarking

Benchmarking Alarms
"All Good to Great companies began the process of finding a path to greatness by confronting the brutal facts about the reality of their business. When you start with an honest and diligent effort to determine the truth of your situation, the right decisions often become self-evident.”
— Jim Collins

In our last blog, we discussed the first step in Casne’s 7 Step Solution: The Alarm Philosophy. Consider the Alarm Philosophy document as the destination point on a roadmap. The benchmarking activity is the time to plan the journey. First, we need to know the starting point. While some discussions during the Alarm Philosophy point out the areas of need, benchmarking dials in on the specific pains of the current way of operations. Benchmarking takes a closer look at the current system, identifies the alarm performance metrics needed to achieve the objectives set forth in the Alarm Philosophy Document. When we discuss benchmarking, we will want to know the brutal reality of your business operations.

Capacity and Flux

alarm managment blog 3 capacity and flux

First, we will consider the current operator handling capacity and the alarm flux. Operator Handling Capacity is the total number of events your operations team can handle per unit of time, usually hour. It’s important to know how many alarm events your team can successfully handle. If you are having more alarms than your team can handle, then we will make a note to address this in our plan. An Alarm Flux is the average number of alarms issued per unit of time. While operator handling capacity looks at how many alarms your team can handle, alarm flux benchmarks the average number of alarms coming in during a set amount of time. Ultimately, we want the two benchmarks to be similar.

Floods and Missed Actions

alarm management blog 3 data flood

Next, we will look at the number of alarm floods and resulting actions missed during the floods. An alarm flood is a specific event that causes the system to be flooded with an unusual amount of alarms. An alarm flood is often due to a cascade effect from a single point of failure. When these occur, operators become detectives trying to find out what is the ultimate event that began the flood. When alarm flooding happens, operators begin responding to alarms with little to no severity information. As a result, not all alarms will be responded to in a timely manner. Those alarms that were not responded to are called actions missed.

Problem Alarms

alarm managment blog 3 overwhelmed operatorWe will also take a look at the problem alarms in your system. From alarms that are always alerting to alarms that are excessively alarming, these have an effect on your critical operations. We will also look at the current priority of the different alarms and consider how they align to the goals stated in the alarm philosophy document. Whether it is chattering, suppressed, or stale alarms, we need to know what they are and document their occurrences.

Develop KPIs

alarm management blog 3 kpiOnce we know your benchmarks, we can see where the issues are and develop KPIs that are unique to your facility’s needs. We have over 40 years of success in professional engineering and technology integration services for major utilities, process industries, and critical facilities. Our team of capable engineers and technologists develops and supports engineered solutions using the best of breed products and technologies. Contact us here to get started on solving your alarm management needs.

Topics: Alarm Management



Do you have a project involving engineering, system integration, technology infrastructure, or critical system support?

discuss your project with an Industry Principal