Linking Maintenance to Goals

Modified on Tue, 18 Nov at 11:08 AM

Linking Maintenance to Goals

Overview

ARMOR's Maintenance and Goals features work beautifully together to provide comprehensive fleet tracking. Maintenance ensures equipment receives preventive service, while Goals track performance and efficiency. This guide explains how to use both systems for maximum insight into your fleet's health and productivity.

Understanding the Difference

Maintenance: Preventive Service Tracking

Purpose: Ensure regular service intervals are met based on runtime, distance, or time

Triggers:

  • Runtime accumulation (engine hours)
  • Distance traveled (miles/km)
  • Calendar time (days since last service)

Outcome: Alerts when service is due, counter resets after completion

Example: "Oil change every 250 hours or annually"

Goals: Performance and Efficiency Tracking

Purpose: Monitor equipment performance, efficiency, and utilization against targets

Triggers:

  • Performance below threshold (low efficiency)
  • Utilization targets not met (idle time too high)
  • Telemetry values outside acceptable range

Outcome: Alerts when performance degrades or targets missed

Example: "Runtime efficiency should be ≥80% daily" or "Maximum idle time ≤2 hours/day"

How They Work Together

Maintenance → Tracks when to service equipment (schedule-based)

Goals → Tracks how well equipment is performing (performance-based)

Together → Complete picture of equipment health and productivity

Complementary Use Cases

Use Case 1: Detecting Maintenance Needs Early

Scenario: Equipment performance degrades before scheduled maintenance due

Maintenance Rule: Oil change every 250 hours

Goal: Runtime efficiency ≥ 75%

Normal Operation:

  • At 100 hours: Efficiency = 82% (Goal OK, no alert)
  • At 180 hours: Efficiency drops to 70% (Goal ALERT triggers)
  • Action: Investigate cause - dirty air filter found and replaced early
  • At 250 hours: Normal oil change performed

Result: Goal alerted to performance issue before scheduled maintenance. Early intervention prevented further degradation.

Use Case 2: Validating Maintenance Effectiveness

Scenario: Use Goals to verify maintenance actually improved performance

Maintenance Rule: Oil change every 250 hours

Goal: Average runtime per day ≥ 6 hours

Timeline:

  • Week before maintenance: Runtime = 5.2 hours/day (below goal)
  • Oil change performed at 250 hours
  • Week after maintenance: Runtime = 6.8 hours/day (above goal)

Result: Goal data confirms maintenance restored performance. If runtime hadn't improved, would indicate another issue exists.

Use Case 3: Optimizing Maintenance Intervals

Scenario: Use Goals performance data to adjust maintenance frequency

Initial Setup:

  • Maintenance: Oil change every 250 hours
  • Goal: Runtime efficiency ≥ 75%

Observations over 6 months:

  • Efficiency consistently drops below 75% around 200 hours
  • After oil change, efficiency jumps back to 85%
  • Pattern repeats every cycle

Action: Reduce maintenance interval to 200 hours

Result: Efficiency stays above 75% throughout cycle, equipment runs better, fewer alerts

Recommended Goal + Maintenance Combinations

Combination 1: Runtime Tracking

Maintenance Goal Benefit
Oil change every 250 hours Daily runtime ≥ 6 hours Maintenance ensures regular service; Goal alerts if utilization drops (equipment not being used enough)

Combination 2: Efficiency Monitoring

Maintenance Goal Benefit
Filter replacement every 100 hours Runtime efficiency ≥ 80% Maintenance prevents clogged filters; Goal alerts if efficiency drops early (indicating filter clogging faster than expected)

Combination 3: Distance and Fuel Efficiency

Maintenance Goal Benefit
Tire rotation every 5,000 miles Weekly distance ≥ 500 miles Maintenance keeps tires healthy; Goal alerts if vehicle underutilized (not meeting route expectations)

Setting Up Integrated Tracking

Step 1: Establish Maintenance Rules

  1. Create maintenance rules for all equipment (see Creating a Maintenance Plan)
  2. Focus on critical maintenance: oil changes, filter replacements, inspections
  3. Set appropriate intervals based on manufacturer recommendations

Step 2: Create Complementary Goals

  1. For each major equipment type, create goals monitoring:
    • Utilization (runtime per day/week)
    • Efficiency (runtime efficiency percentage)
    • Idle time (if excessive idling is concern)
  2. Set realistic thresholds based on baseline performance
  3. Configure daily or weekly checks as appropriate

Step 3: Monitor Both Systems

  • Check Maintenance alerts for service due
  • Check Goals alerts for performance issues
  • When Goal alerts on performance drop, investigate:
    • Is maintenance due soon? May need early service
    • Is operator error involved? Training opportunity
    • Is equipment malfunctioning? Repair needed

Step 4: Analyze Trends

  • Review Goal performance charts before/after maintenance
  • Look for patterns: Does performance degrade predictably before maintenance?
  • Use data to optimize maintenance intervals
  • Adjust Goal thresholds if maintenance schedule changes

Reporting: Combined View

Dashboard to Monitor

Ideally, create a dashboard showing both:

  • Maintenance Status: Upcoming maintenance, overdue items
  • Goal Status: Assets meeting/missing performance targets
  • Correlation: Assets with both maintenance due AND poor performance (high priority)

Example Dashboard Layout

Section 1: Critical Assets

  • Assets with maintenance overdue AND goal alerts (needs immediate attention)

Section 2: Upcoming Maintenance

  • Next 30 days of scheduled maintenance
  • Highlight any with current goal alerts

Section 3: Performance Issues

  • Assets with goal alerts but maintenance not due
  • May indicate need for unscheduled repair or investigation

Section 4: Healthy Fleet

  • Assets meeting goals and on maintenance schedule
  • No action needed

Best Practices

  • Start simple: Implement maintenance first, add goals gradually
  • Focus on critical assets: Don't try to track everything at once
  • Use consistent metrics: If maintenance tracks runtime, create runtime-based goals too
  • Review correlations monthly: Look for relationships between maintenance and performance
  • Document findings: Note when goals reveal maintenance needs early
  • Adjust both as needed: Optimize maintenance intervals AND goal thresholds based on data
  • Train team: Ensure everyone understands difference between maintenance and goals alerts

Troubleshooting

Goals Alert Right After Maintenance

Problem: Performed maintenance but goal still shows poor performance

Possible Causes:

  • Maintenance didn't address root cause of performance issue
  • Additional repair needed beyond routine maintenance
  • Operator error or training issue
  • Goal threshold set too aggressively

Solutions:

  • Investigate further - what's causing poor performance?
  • Review maintenance notes - was anything unusual found?
  • Check telemetry data for clues
  • Consider adjusting goal threshold if unrealistic

Maintenance Due But Goals Show Good Performance

Situation: Maintenance interval reached but equipment performing fine

Options:

  • Perform maintenance as scheduled: Don't skip preventive maintenance even if performance OK (degradation may be imminent)
  • Extend interval slightly: If consistently performing well at maintenance threshold, consider increasing interval by 10-20%
  • Monitor closely: If deferring maintenance, watch goals closely for first sign of degradation
⚠️ Caution: Don't use good goal performance as excuse to skip maintenance. Preventive maintenance prevents failures that goals won't detect until it's too late.

What's Next?

Getting Help

For guidance on integrating Maintenance and Goals tracking for your fleet, contact the ARMOR Support Team with your equipment types and tracking objectives.

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