Goal Alerts & Notifications

Modified on Mon, 17 Nov at 10:23 PM

Goal Alerts & Notifications

Overview

When a goal threshold is crossed, ARMOR automatically generates alerts and sends notifications to the appropriate users. This system ensures that your team is immediately aware of performance issues, utilization problems, or threshold violations without needing to constantly check dashboards.

This guide explains how goal alerts work, where you see them, and how they're delivered to your team.

How Goal Alerts Work

The Alert Lifecycle

  1. Goal Check Runs - ARMOR evaluates the goal on its scheduled frequency (daily, weekly, or monthly)
  2. Threshold Evaluated - System compares actual telemetry data to the target value
  3. Alert Triggered (Set) - If threshold is crossed, an alert is created with status "Set"
  4. Notifications Sent - All configured recipients receive notifications
  5. Alert Clears - When performance returns to normal, alert status changes to "Cleared"
  6. Clear Notification Sent - Recipients are notified that the issue is resolved

Set vs. Cleared Alerts

Alert State When It Occurs Example
Set (Active) Threshold is crossed (performance below or above target) Goal requires 6 hours runtime, asset only ran 3 hours
Cleared (Resolved) Performance returns to acceptable range Asset ran 7 hours the next day, meeting goal

Alert Frequency

Alerts are generated based on your goal's checking frequency:

  • Daily Goals - Checked overnight (around 2:00 AM local time). Alerts appear the following morning.
  • Weekly Goals - Checked at the end of the last selected weekday (e.g., Friday night for Mon-Fri goals).
  • Monthly Goals - Checked at the end of the month (last day of month).
? Note: ARMOR does not send duplicate alerts. If an asset already has an active "Set" alert for a goal, no additional alert is created until it clears and crosses the threshold again.

Where Alerts Appear

1. Alerts Page

Location: Main navigation → Alerts

What you see:

  • List of all active and cleared alerts
  • Alert severity (Info, Warning, Critical)
  • Alert message (custom text from goal configuration)
  • Which asset triggered the alert
  • Timestamp of when alert was set
  • Link to view goal details

Filtering:

  • Filter by alert type: "Goal Alert"
  • Filter by status: Active (Set) or Cleared
  • Filter by asset, site, or date range

2. Asset Detail Pages

Location: Asset detail page → Alerts tab

What you see:

  • All goal alerts specific to that asset
  • Current status of all goals applied to that asset
  • Goal performance widget showing pass/fail status

Use case: When investigating an asset's performance, see all related goal alerts in one place.

3. Dashboard Widgets

Location: Custom dashboards → Alert widgets

What you see:

  • Summary count of active goal alerts
  • Trend graphs showing alert frequency over time
  • Top offending assets (most alerts triggered)

Use case: High-level operational overview for managers and supervisors.

4. Email Notifications

When sent: Immediately when alert is Set, and again when Cleared

Email contains:

  • Subject: Goal name + asset identifier
  • Alert message (Set or Clear text from goal config)
  • Asset details (name, serial number, location)
  • Goal threshold details
  • Link to view alert in ARMOR platform
? Pro Tip: Set up email filtering rules to sort goal alerts by priority or asset type for better inbox management.

Notification Settings

Who Receives Notifications?

By default, alerts are sent to:

  • The user who created the goal
  • Account Admins (for account-scoped goals)
  • Super Admins (if configured to receive all alerts)

You can customize recipients when creating or editing a goal. See Who Receives Alerts? for detailed configuration.

Notification Delivery Methods

Method When Used Configuration
In-App Notifications Always enabled for all users Automatic - no setup required
Email Notifications Alert Set and Cleared events Configured per goal or user preferences
Webhook (Advanced) Integration with external systems Requires API integration setup

Understanding Alert Messages

Customizing Messages in Goals

When creating or editing a goal, you define two messages:

  • Set Message - Appears when threshold is crossed (issue detected)
  • Clear Message - Appears when performance returns to normal

Example:

Goal: Daily Runtime Goal - At least 6 hours per day

Set Message: "Equipment runtime below 6 hours. Contact site supervisor."

Clear Message: "Equipment runtime back to normal levels."

Best Practices for Alert Messages

  • Be specific - Include the threshold value and what action is needed
  • Actionable - Tell recipients what to do (investigate, contact someone, check equipment)
  • Avoid jargon - Use language your team understands
  • Include context - Mention the impact (e.g., "affects productivity", "safety concern")

Good examples:

  • ✅ "Forklift runtime below 6 hours - check with warehouse manager"
  • ✅ "Excessive idle time detected (>2 hours) - review operator training"
  • ✅ "Charging time exceeds 8 hours - inspect charger and battery health"

Avoid:

  • ❌ "Goal not met" (too vague)
  • ❌ "RT_DAILY < 6" (too technical)
  • ❌ "Alert triggered" (no actionable information)

Alert Priority Levels

ARMOR assigns priority to alerts based on the goal configuration:

Priority When Used Visual Indicator
Info Minor deviations, informational tracking Blue icon
Warning Moderate performance issues requiring attention Yellow/orange icon
Critical Urgent issues, safety concerns, major deviations Red icon

Priority is set during goal creation based on the severity of the metric being tracked.

Managing Alert Volume

If You're Getting Too Many Alerts

Causes:

  • Thresholds are too strict
  • Goals are applied too broadly (entire fleet instead of specific assets)
  • Multiple similar goals creating duplicate alerts

Solutions:

  1. Adjust thresholds - Edit goals to relax target values slightly
  2. Narrow scope - Apply goals to specific asset groups instead of all assets
  3. Consolidate goals - Combine overlapping goals to reduce redundancy
  4. Change frequency - Switch from daily to weekly checks for less urgent metrics
  5. Use notification filters - Configure email rules to prioritize critical alerts

If You're Not Getting Enough Alerts

Causes:

  • Thresholds are too lenient
  • Goal is inactive
  • Notification settings are incorrect
  • Assets aren't sending telemetry data

Solutions:

  1. Verify goal is active - Check Goal Management page for Active status
  2. Review thresholds - Ensure target values are challenging but realistic
  3. Check notification recipients - Confirm your email is listed
  4. Test with known failure - Temporarily set an extreme threshold to verify alerts are working

Alert History and Reporting

Viewing Past Alerts

Access historical alert data from:

  • Alerts page - Filter by date range to see past alerts
  • Asset detail pages - View alert history per asset
  • Reports - Generate custom reports on goal performance and alert trends

Exporting Alert Data

  1. Navigate to Alerts page
  2. Apply desired filters (date range, goal type, assets)
  3. Click "Export"
  4. Choose format (CSV, Excel, PDF)
  5. Download for analysis or reporting

Troubleshooting Notifications

Not Receiving Email Notifications

Check:

  • Spam/junk folder - ARMOR emails may be filtered
  • Email address in user profile - Ensure it's correct and verified
  • Notification preferences - Check if goal alerts are enabled
  • Goal recipient list - Verify you're added as a recipient

Receiving Duplicate Notifications

Possible causes:

  • Multiple goals with overlapping scope
  • User listed multiple times in recipient list

Solution: Review goal configurations and consolidate where possible. Remove duplicate recipient entries.

Next Steps

Getting Help

If you need assistance with goal alerts or notifications, contact the ARMOR Support Team.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article