Runtime/Distance/Efficiency Goal Suggestions

Modified on Mon, 17 Nov at 10:22 PM

Runtime/Distance/Efficiency Goal Suggestions

Overview

ARMOR tracks dozens of telemetry metrics, but three categories consistently drive the most value: runtime, distance, and efficiency. Understanding which metrics to monitor—and what thresholds to set—is key to building an effective goal strategy.

This guide provides detailed recommendations for setting meaningful runtime, distance, and efficiency goals, complete with suggested thresholds, constraint types, and real-world examples.

Runtime Goals

What Runtime Measures

Runtime tracks how long an asset's motor or engine is running. It's the single most important metric for understanding utilization and productivity.

Available runtime metrics in ARMOR:

  • runTimeToday - Hours of operation today (midnight to midnight)
  • runTimeWeek - Cumulative hours this week
  • runTimeMonth - Cumulative hours this month
  • runTimeTotal - Lifetime hours (odometer equivalent)

Recommended Runtime Goals

1. Daily Runtime Goal (Most Common)

Metric: runTimeToday

Constraint: At Least (>=)

Frequency: Daily

Operation Type Suggested Threshold Reasoning
Single shift (8 hours) 5-6 hours Accounts for breaks, lunch, transitions
Double shift (16 hours) 12-14 hours Allows for shift changeover, downtime
24/7 operations 20-22 hours Maintenance windows, operator breaks
Part-time use 2-4 hours Backup assets, occasional use
Rental assets (customer-driven) 4-6 hours Ensures active rental, productive use

Example goal configuration:

Goal Name: "Daily Runtime - Single Shift Forklifts"

Data Field: runTimeToday

Constraint: At Least

Target Value: 6

Frequency: Daily

Alert Message: "Forklift runtime below 6 hours - check with site supervisor for underutilization"

2. Weekly Runtime Goal

Metric: runTimeWeek

Constraint: At Least (>=)

Frequency: Weekly (select work days)

Operation Type Suggested Threshold Weekly Schedule
Standard 5-day work week 30-40 hours Monday - Friday
6-day operations 45-55 hours Monday - Saturday
Full calendar week 50-60 hours Monday - Sunday

Why weekly goals matter: Daily spikes or dips are normal. Weekly goals smooth out variations and provide strategic visibility.

3. Monthly Runtime Goal (Executive KPI)

Metric: runTimeMonth

Constraint: At Least (>=)

Frequency: Monthly

Suggested Threshold: 150-180 hours per month

Use case: Long-term performance tracking, ROI measurement, fleet productivity benchmarking.

Distance Goals

What Distance Measures

Distance tracks how far an asset has traveled. Critical for route-based operations, delivery fleets, and mobile equipment.

Available distance metrics:

  • distanceToday - Miles or kilometers traveled today
  • distanceWeek - Cumulative distance this week
  • distanceMonth - Cumulative distance this month
  • distanceTotal - Lifetime odometer reading

Recommended Distance Goals

1. Daily Distance Goal

Metric: distanceToday

Constraint: At Least (>=)

Frequency: Daily

Asset Type Suggested Threshold Use Case
Warehouse forklifts 3-5 miles Short-range, confined spaces
Pallet jacks 1-3 miles Very localized movement
Delivery vehicles (local) 50-100 miles Urban/suburban routes
Delivery vehicles (regional) 150-250 miles Multi-city coverage
Long-haul transport 400-600 miles Interstate routes
Construction equipment 0.5-2 miles On-site only, minimal travel

Example goal configuration:

Goal Name: "Local Delivery Route Coverage"

Data Field: distanceToday

Constraint: At Least

Target Value: 75

Frequency: Daily

Alert Message: "Vehicle traveled less than 75 miles - verify route completion"

2. Weekly Distance Goal

Metric: distanceWeek

Constraint: At Least (>=)

Frequency: Weekly

Suggested Threshold: 300-500 miles for delivery fleets, 15-25 miles for warehouse equipment

3. Distance + Runtime Ratio (Advanced)

Why it matters: Tracks if vehicles are moving efficiently or sitting idle while running.

Calculation: distanceToday / runTimeToday

Typical ratios:

  • Delivery vehicles: 8-15 miles per hour (accounts for stops, traffic)
  • Forklifts: 0.5-1 mile per hour (short trips within facility)
  • Construction equipment: 0.1-0.5 mile per hour (mostly stationary work)

Note: This requires creating a custom calculated field or using external reporting tools. Not directly available as a single metric in ARMOR goals.

Efficiency Goals

What Efficiency Measures

Efficiency metrics track waste, optimization, and operational performance. These goals directly impact cost savings and sustainability.

Recommended Efficiency Goals

1. Idle Time Goal (Waste Reduction)

Metric: idleTimeToday

Constraint: At Most (<=)

Frequency: Daily

Asset Type Suggested Threshold Impact
Forklifts, pallet jacks At most 2 hours Reduces battery/fuel waste
Delivery vehicles At most 1.5 hours Minimizes fuel consumption
Construction equipment At most 3 hours Expected waiting time on job sites
High-efficiency fleets At most 0.5-1 hour Aggressive waste reduction targets

Example goal configuration:

Goal Name: "Idle Time Waste Alert"

Data Field: idleTimeToday

Constraint: At Most

Target Value: 2

Frequency: Daily

Alert Message: "Excessive idle time detected (>2 hours) - review operator efficiency"

2. Charging Time Goal (Battery-Powered Assets)

Metric: chargeTimeToday

Constraint: At Most (<=)

Frequency: Daily

Charging Type Suggested Threshold Reasoning
Standard charging (lead-acid) At most 8 hours Full charge cycle
Fast charging (lithium-ion) At most 4 hours Rapid charge capability
Opportunity charging At most 2 hours Quick top-ups during breaks

Why it matters: Excessive charging time indicates battery degradation, charger inefficiency, or improper usage patterns.

3. Battery Health Goal

Metric: batteryLevelMin (minimum battery level reached today)

Constraint: At Least (>=)

Frequency: Daily

Suggested Threshold: 15-20%

Why it matters: Batteries that consistently drop below 15% degrade faster and risk operational downtime.

4. Energy Consumption Goal (Advanced)

Metric: energyConsumedToday (kWh or fuel gallons)

Constraint: At Most (<=)

Frequency: Daily or Weekly

Use case: Sustainability reporting, cost control, benchmarking energy efficiency across fleet.

Typical thresholds:

  • Electric forklifts: 15-25 kWh per day
  • Delivery vans (EV): 50-80 kWh per day
  • Gas-powered forklifts: 2-4 gallons per day

Combining Metrics for Comprehensive Monitoring

The "Fleet Performance Package"

Most customers benefit from implementing all three metric categories simultaneously:

  1. Runtime Goal - Tracks utilization (are assets being used?)
  2. Distance Goal - Tracks mobility (are route-based assets covering territory?)
  3. Efficiency Goal - Tracks waste (are assets operating optimally?)

Example: Delivery Fleet Package

  • Daily Runtime: At least 6 hours
  • Daily Distance: At least 75 miles
  • Idle Time: At most 1.5 hours

Together, these goals provide complete visibility into fleet performance.

Adjusting Goals Over Time

Month 1: Baseline

Set conservative thresholds. The goal is to understand actual performance, not trigger constant alerts.

Month 2-3: Refinement

Analyze alert frequency. If too many alerts, relax thresholds. If too few, tighten them. Target 70-85% compliance rate.

Month 4+: Optimization

Introduce stretch goals. Gradually increase runtime expectations or decrease idle time targets to drive continuous improvement.

Common Pitfalls to Avoid

  • ❌ Setting "perfect" thresholds (100% utilization) - Unrealistic and demoralizing
  • ❌ Applying same thresholds to all assets - Customize for asset type and usage pattern
  • ❌ Ignoring seasonality - Winter operations may differ from summer
  • ❌ Not accounting for planned downtime - Exclude assets undergoing maintenance
  • ❌ Monitoring too many metrics at once - Start with 3-5 key goals, expand gradually

Related Topics

Getting Help

Need help choosing the right metrics and thresholds for your operation? Contact the ARMOR Support Team for personalized recommendations.

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