Configuring Daily/Weekly Goal Checks

Overview

When you create a goal in ARMOR, you must specify when the system should check if your assets are meeting their targets. This checking frequency determines how often alerts are generated and how responsive your monitoring system is to performance changes.

This guide explains each frequency option, when to use them, and how to configure check schedules effectively.

Available Frequency Options

1. Daily Goals

Best for:

• Daily runtime monitoring
• Day-to-day utilization tracking
• Immediate feedback on shift performance
• High-priority metrics that need quick attention

Example use cases:

• "Forklifts must run at least 6 hours per day"
• "Idle time should not exceed 2 hours per day"
• "Daily distance must be at least 5 miles"

Configuration: No additional settings required - simply select "Daily" as the frequency.

2. Weekly Goals

Best for:

• Work week performance (Monday-Friday)
• Cumulative runtime goals (e.g., 40 hours per week)
• Weekly productivity targets
• Reducing alert noise for minor daily variations

Example use cases:

• "Equipment must run at least 40 hours per work week (Mon-Fri)"
• "Weekly distance should exceed 100 miles"
• "Cumulative charging time under 20 hours per week"

Configuration: Select "Weekly" and choose which days of the week to include in the calculation.

3. Monthly Goals

Best for:

• Long-term performance tracking
• Monthly KPIs and benchmarks
• Strategic goals with longer measurement periods
• High-level executive reporting

Example use cases:

• "Fleet average runtime must exceed 150 hours per month"
• "Monthly distance goals for delivery routes"
• "Aggregate utilization targets per asset class"

Configuration: Select "Monthly" - no additional day selection required.

Setting Up Daily Goals

Step-by-Step Configuration

1. Create or edit a goal
2. In the "Frequency" section, select "Daily"
3. Choose the data field to monitor (e.g., runTimeToday)
4. Set your target value (e.g., 6 hours)
5. Configure constraint type: "At Least" (>=) or "At Most" (<=)
6. Save the goal

How Daily Checks Work

Timeline example:

Daily Goal Best Practices

• Use for high-priority metrics - Things that need immediate attention
• Start with conservative thresholds - Avoid alert fatigue from overly strict targets
• Monitor for 1-2 weeks - Adjust thresholds based on actual performance patterns
• Pair with weekly goals - Daily for tactical monitoring, weekly for strategic review

Setting Up Weekly Goals

Step-by-Step Configuration

1. Create or edit a goal
2. In the "Frequency" section, select "Weekly"
3. Select which days of the week to include in the calculation
4. Choose the data field (e.g., runTimeWeek)
5. Set your target value (e.g., 40 hours)
6. Configure constraint type
7. Save the goal

Selecting Weekdays

You can include any combination of days:

Selection	Use Case	Check Day
Monday - Friday	Standard 5-day work week	Friday night / Saturday morning
Monday - Sunday	Full calendar week, 24/7 operations	Sunday night / Monday morning
Tuesday - Saturday	Retail schedules (closed Sun-Mon)	Saturday night / Sunday morning
Saturday - Sunday	Weekend operations only	Sunday night / Monday morning

How Weekly Checks Work

Timeline example (Monday-Friday goal):

Weekly Goal Best Practices

• Align with your operational schedule - Match actual work days
• Account for planned downtime - Adjust thresholds if assets are offline certain days
• Use cumulative metrics - Track runTimeWeek, not runTimeToday
• Give buffer room - Don't require 100% utilization (e.g., 38 hours instead of 40 for a 40-hour week)

Choosing the Right Frequency

Decision Matrix

If You Need...	Use This Frequency	Why
Immediate feedback on shift performance	Daily	Alerts appear next morning for quick action
Smooth out daily variations	Weekly	Cumulative view reduces false alerts from one-off events
Track long-term trends	Monthly	Strategic view for executive reporting
Monitor critical safety metrics	Daily	Can't wait a week for safety issues
Reduce alert volume	Weekly	Fewer check cycles = fewer alerts
Allow recovery time before alerting	Weekly	One bad day doesn't trigger alert if week overall is good

Combining Frequencies

For comprehensive monitoring, create multiple goals with different frequencies:

Example: Fleet Runtime Monitoring

• Daily Goal: "At least 6 hours per day" - Catches immediate underutilization
• Weekly Goal: "At least 35 hours per week" - Ensures consistent performance across the week
• Monthly Goal: "At least 160 hours per month" - Long-term utilization KPI

This layered approach gives you tactical, operational, and strategic visibility.

Advanced Configuration

Excluding Specific Days from Weekly Goals

Scenario: Your operation runs Monday-Thursday, with Friday reserved for maintenance.

Solution: Select only Monday, Tuesday, Wednesday, Thursday in the weekDays setting. ARMOR will exclude Friday from the calculation.

Handling Partial Weeks

Scenario: A holiday week has Monday off, so only 4 work days instead of 5.

Options:

1. Temporarily pause the goal - Deactivate for that week, reactivate after
2. Accept the alert - Acknowledge that performance will be lower
3. Use proportional thresholds - Adjust target value for short weeks (e.g., 32 hours instead of 40)

Timezone Considerations

ARMOR uses your account's configured timezone for goal checks. If you have assets in multiple timezones, the check time will be consistent with the account timezone (not per-asset).

Example: Account timezone is Eastern (ET). Daily checks run at 2:00 AM ET for all assets, regardless of their physical location.

Testing Your Check Schedule

Verify Timing

1. Create a test goal with a very lenient threshold
2. Set to Daily or Weekly frequency
3. Activate and wait for first check cycle
4. Confirm alerts appear when expected
5. Check email notifications arrive at the right time

Adjust as Needed

If timing doesn't align with your needs:

• Switch from Daily to Weekly (or vice versa)
• Adjust weekDays selection for weekly goals
• Consider changing your account timezone if consistently misaligned

Troubleshooting

Alerts Appearing at Wrong Time

Check:

• Account timezone settings
• Frequency configuration (daily vs. weekly)
• WeekDays selection for weekly goals

No Alerts Generated

Check:

• Goal is Active (not Inactive or Archived)
• Check cycle has occurred (wait until after scheduled time)
• Thresholds aren't too lenient (all assets meeting goal)
• Assets are sending telemetry data

Weekly Goal Only Checking Some Days

Check:

• WeekDays configuration - ensure all intended days are selected
• Telemetry data availability for excluded days

Related Topics

• Goal Alerts & Notifications - How alerts are delivered
• How to Create a Custom Goal - Building goals from scratch
• Who Receives Alerts? - Configuring notification recipients

Getting Help

If you need assistance configuring goal check schedules, contact the ARMOR Support Team.