How Alarm Notifications Work

Author: Qube Staff

Alarms Overview

Qube’s continuous monitoring system detects and tracks methane emissions with advanced sensors and machine learning algorithms capable of quantifying leaks and pinpointing their source. Alarms are notifications sent by email or through API integration with the Qube platform to key operator personnel when a potential leak has been detected.

The Qube platform allows users to set their own parameters for triggering alarm notifications, such as when specific emission volumes or emission rates over time are reached. User-defined alarm parameters can be set on a site-by-site basis, which enables operators to respond to emission events with targeted resources. 

Qube’s alarm notifications also provide operators with contextual information to inform decision-making such as the largest emitting source during the alarm period, plume composition with max values of all other sensors on the device, and CH4 emission volumes over previous periods. 

Alarm conditions are evaluated every 15 minutes by the Qube platform so operators can make remedial decisions based on the most current conditions. Platform users may receive alarm notifications without having to log into the dashboard, which can expedite a response. 

How Alarms Work: An Example 

To set up alarms in the Qube platform, the first thing an operator will do is set the parameters of the alarm. Parameters refer to the emissions volume or emissions rate that must be exceeded to trigger the alarm, and the duration over which the emissions volume or rate must be detected to trigger the alarm. The image below illustrates the alarm-setting mechanism in the Qube platform.

Note that emissions rate over an averaging period is equivalent to a volume measurement over an averaging period; you can set up the parameter either way to your operational preference, but they are evaluated the same way by the system.

In this example, the operator set up the alarm to be issued when the CH4 emission rate exceeds 100 kilograms per hour over an averaging period of one hour. These factors are what we refer to as alarm conditions - conditions that must be met for the alarm notification to be issued. Conditions can also be thought of as thresholds. 

In this example using the parameters above, so long as the detected emissions remain below 100 kilograms per hour, no alarm will be issued.

However, in this next image, the Qube platform detects CH4 emission rates in excess of 100 kilograms per hour over an averaging period of one hour. An alarm is now issued based on the parameters set by the operator. 

The alarm will remain active so long as the volume remains over 100kg. As noted above, alarm conditions are evaluated every 15 minutes by the Qube platform so the operator can make remedial decisions based on the most current conditions.  

Key Takeaways:

• Alarms are notifications that are sent from the Qube platform to key operator personnel when a potential leak has been detected. 

• The Qube platform allows users to set their own parameters for triggering alarm notifications, such as when specific emission volumes or emission rates over time are reached. 

• Alarms are configurable either as a general rule across all of an operator’s facilities, or on a site-by-site basis. 

• Alarm thresholds should be actionable, resource-conscious, and serve specific emissions reduction goals. 

In our next article we’ll discuss best practices for setting up alarm notifications on the Qube platform.