Alerting System
The document outlines an Alerting System used by Coolr Group, which is designed to monitor and manage various aspects of device and asset performance. The alerts are categorized into different types, each focusing on specific issues or performance metrics. Here’s a brief description of the categories mentioned:
-
Info Missing from the Client:
- This category includes alerts that identify missing or incomplete information related to devices and assets. For example, it flags devices that are sending data but are not linked to any asset, or assets with rejected images due to missing planograms. These alerts help improve asset management and reduce inefficiencies.
-
Performance Alerts (Data Performance):
- These alerts focus on monitoring the performance of devices in terms of data generation and transmission. They track metrics like excessive pings, high image counts, and high rates of rejected images. The goal is to identify abnormal behavior early and provide actionable insights to maintain optimal performance.
-
Performance Alerts (Hardware Performance):
- This category deals with the physical condition and functionality of hardware devices, such as cameras and coolers. Alerts in this category monitor issues like low battery levels, non-functional cameras, and cooler malfunctions. The aim is to ensure operational continuity and reduce downtime by addressing hardware issues proactively.
-
Displacement and Battery Alerts:
- These alerts monitor the physical movement of devices and their power status. They track unauthorized device movement, battery depletion, and insufficient battery levels in specific devices like Vista. The purpose is to ensure devices remain in their intended locations and have sufficient power to function properly.
Each category is designed to address specific operational challenges, ensuring that the system runs smoothly and efficiently.
Architecture
Info Missing from the Client
| Alert Name | Description | Logic | Variables | Benefits |
|---|---|---|---|---|
| Device Data Without Asset | Identifies devices sending data without being linked to an asset. | Triggered if the device has the latest pings and images within a configurable threshold, excluding StoreBuddy images. | Configurable threshold in days. | Improved asset management and monitoring. |
| Rejected Image - No Planogram | Flags assets with images rejected due to missing planograms. | Opens when an asset's image status is rejected due to "No Planogram." Closes when status or reason changes. | None specified. | Pinpoints specific assets for resolution, reducing inefficiencies. |
Performance Alerts
Data Performance
| Alert Name | Description | Logic | Variables | Benefits |
|---|---|---|---|---|
| High Ping Count | Monitors devices with excessive pings within a specified timeframe. | Triggered when pings exceed the configured threshold. Closes when pings fall below the threshold. | Monitoring period (minutes), maximum allowable ping count. | Identifies abnormal device behavior early. |
| High Image Count | Identifies devices capturing excessive images within a specified timeframe. | Triggered when image count exceeds the threshold. Closes when image count falls below the threshold. | Timeframe (days), image count threshold. | Provides real-time notifications and actionable insights. |
| Only Rejected Images | Identifies assets where the last three images have all been rejected (excluding "No Planogram"). | Triggered when the last 3 images are rejected and the reasons are not "No Planogram." Closes when the last image status is provisioned. | None specified. | Quickly identifies assets with recurring issues. |
| High Number of Rejected Images | Flags assets with a high rate of rejected images over a defined period. | Triggered when the percentage of rejected images exceeds the threshold. Closes when the percentage falls below the threshold. | Percentage threshold (default 30%). | Monitors image rejection trends over time. |
Hardware Performance
| Alert Name | Description | Logic | Variables | Benefits |
|---|---|---|---|---|
| Camera Low Battery | Identifies cameras that are operational but with low battery levels. | Triggered when battery level is below the threshold and the device pings within the configured hours. | Hours to consider issue (default 24 hours), low image battery level (default 2.30V). | Reduces downtime by preemptive battery replacements. |
| Camera Not Working | Identifies cameras not sending approved images within a specified timeframe. | Triggered when no approved image is received in the last 48 hours. Closes when an approved image is received. | None specified. | Ensures operational continuity by detecting non-functional cameras. |
Displacement and Battery Alerts
| Alert Name | Description | Logic | Variables | Benefits |
|---|---|---|---|---|
| Displacement Alert | Generated when a device moves from its intended location beyond a defined threshold. | Triggered when displacement exceeds the threshold. | Hours to consider issue (default 24 hours), displacement threshold (default 1000 meters). | Monitors and prevents unauthorized device movement. |
| Cooler Not Working Properly | Generated when the "Cooler Not Working Properly" checkbox is ticked during a survey. | Triggered when the specific checkbox is selected in the survey. | None specified. | Directly highlights problems reported by surveyors. |
| Battery Depletion | Generated when voltage loss exceeds 0.2V over a gap of 15 days. | Triggered if Vloss > 0.2V within the defined time gap. | Voltage loss threshold (default 0.2V), time gap (default 15 days). | Ensures devices are operational with sufficient power. |
| Vista Insufficient Battery | Triggered when a Vista device's battery voltage falls below a certain threshold. | Triggered when battery voltage is below the threshold. | Battery voltage threshold (default 2.8V). | Ensures uninterrupted device functionality. |