Alerts Documentation
This document describes the various alerts, their logic, purpose, and recommended actions.
Alerts are divided into Operational Alerts and Merchandising Alerts, with additional notes on recipients and notification setup.
Definitions
- IR: Image recognition.
- OOS: Out of stock.
- Ping: Device heartbeat or telemetry ping.
- Time/threshold values are configurable; examples use default windows (e.g., 36h, 72h).
Operational Alerts
Operational alerts cover device behavior, asset connectivity, configuration issues, maintenance checks, and telemetry monitoring.
Note: All Operational Alerts are considered only when:
- The asset is Active and Not Deleted.
- The asset belongs to Retrofit or OEM.
- The asset is assigned to a Location.
- The location is Active and Not Deleted.
Communication / Image update
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action recommendation |
|---|---|---|---|---|---|
| Device data without asset/location | Device data or ping received while the linked asset or location is missing, inactive, or deleted. | Remains open while the device continues to ping and remains unassigned. | Closes when the device is linked to an active asset and location. | Detect devices transmitting without valid linkage. | Link the device to the correct asset and location. |
| No communication (>36h) | The last ping is older than 36 hours for an active asset. | Remains open until new communication is received. | Closes when the device pings again. | Identify disconnected or powered-off devices. | Verify device power and network; perform a remote reset if needed. |
| Hub unplugged | Hub is not charging (IsPowerOn = 0) but is still pinging. | Remains open while the hub is unplugged. | Closes when the hub resumes charging or the device status changes. | Detect gateways running on battery power. | Check power supply and replace the charger if necessary. |
| No door data | Vertical asset is pinging but no door-open events recorded in the configured window (default 36 hours). | Remains open while door events remain absent. | Closes once a door-open event occurs. | Detect inactive or unused coolers. | Confirm store activity and verify the door sensor. |
| No image data | Asset has pinged recently but the most recent image is older than the configured cutoff. | Remains open until a new image is captured. | Closes when a new image is received. | Detect camera or capture issues. | Check camera calibration and alignment. |
| Low battery | Device telemetry indicates voltage below the device-type threshold. | Remains open while voltage stays below threshold. | Closes when battery voltage recovers above threshold. | Detect imminent device battery failure. | Replace or recharge the device battery. |
Notes
- For "No communication (>36h)", review the last reported battery level in the alert to assist troubleshooting.
- Corrective actions for rejected images:
- Blurry/foggy images: check for moisture and apply anti-fog measures.
- Dark/black images: check store lighting.
- No planogram: assign the appropriate planogram.
Configuration errors
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action |
|---|---|---|---|---|---|
| High ping count | Ping count exceeds the configured threshold (default: 2 within the window). | Remains open while the count is above threshold. | Closes when the count is ≤ threshold. | Detect abnormal ping frequency. | Investigate configuration or network loops. |
| High image count | Image count exceeds the configured threshold in the defined window (example: >3 in 72h). | Updates while the count remains above threshold. | Closes once the image count normalizes. | Detect excessive image capture frequency. | Review capture schedule and automation settings. |
| High rejected images | Two or more rejected images in the configured window (example: 72h). | Remains open until rejections drop below threshold. | Closes when rejections fall below threshold. | Detect recurring image-quality or planogram issues. | Investigate root cause (blurry, wrong layout, lighting). |
| High motion count | Motion events for vertical assets exceed the configured threshold. | Remains open while motion remains high. | Closes when motion returns within range. | Detect unusual door/cabinet motion. | Investigate site usage or possible tampering. |
| High GSM duration | Upload duration exceeds the configured threshold. | Remains open while uploads are delayed. | Closes when GSM/upload duration returns to normal. | Detect poor network or SIM issues. | Validate GSM signal and SIM/data plan. |
| Additional / missing shelf | IR processing detects shelf mismatch compared to the planogram. | Updates if the mismatch persists on the next image. | Closes when shelves align with the planogram. | Detect planogram or shelf-setup inconsistencies. | Verify planogram and correct physical shelf setup. |
Maintenance alerts
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action |
|---|---|---|---|---|---|
| Battery depletion | Battery drops by more than the configured delta (example: 200 mV) versus the previous reading. | Updates if depletion continues. | Closes when depletion falls below the configured threshold. | Detect rapid or unusual battery drain. | Investigate power issues or replace the device. |
Telemetry alerts
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action |
|---|---|---|---|---|---|
| Location mismatch | Asset Lat/Long versus latest ping Lat/Long displacement exceeds threshold after accounting for accuracy. | Updates with new ping data while displacement remains above threshold. | Closes when displacement returns within threshold. | Detect moved, misplaced, or potentially stolen assets. | Verify physical location and update system coordinates or investigate. |
| Temperature issue | Cooler temperature is outside configured thresholds for the asset type. | Remains open while temperature stays out of range. | Closes when temperature normalizes. | Detect cooler malfunction. | Check compressor, power supply, and store conditions. |
Merchandising alerts
Merchandising alerts monitor planogram compliance, stock levels, share of shelf, and purity for assets and outlets.
Out-of-stock alerts
These alerts can be defined at product or category level and at store or asset level.
- Criteria: product / planogram.
- Thresholds: based on facings or occupancy% (defaults and overrides available).
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action |
|---|---|---|---|---|---|
| Product out of stock | A planogram product is not detected in the latest image. | Remains open while the product is still OOS. | Closes if the product appears in the next IR. | Detect SKU OOS situations. | Notify the replenishment team. |
| Category OOS / low occupancy | Category facing% is below the configured threshold. | Updates with the next IR if still low. | Closes when category occupancy reaches the threshold. | Detect low category presence. | Escalate for refilling or restocking. |
| Consolidated OOS by outlet | For parent-child assets: product appears OOS across related assets. | Updates if still OOS in latest images. | Closes if product is available again. | Detect consolidated OOS issues across an outlet. | Notify stakeholders. |
| Occupancy % | Product occupancy% is below the expected value. | Updates with each IR. | Closes when stock reaches expected occupancy. | Maintain minimum occupancy levels. | Trigger refill alerts. |
Purity alerts
| Alert Name | Logic to open | Logic to update | Logic to close | Purpose | Action |
|---|---|---|---|---|---|
| Foreign alert | A foreign product is detected in recent images. | Updates with new images and metrics. | Closes when no foreign products are detected in subsequent images. | Maintain shelf purity and brand visibility. | Remove competitor SKUs and refill own products. |
Recipient setup
Recipients and alert delivery can be configured by:
- Alert category: All / Operational / Merchandising.
- Alert type: All / Specific.
- Role: Individual or location-specific roles.
- Market: All / Specific.
- Channel: Email / Slack / role-based channels.
- Classification: All / Specific.
- Notification type: Email / Role-based notifications.
- Communication mode: Summary / Individual