Types of Maintenance (Scheduled vs Trigger-Based)
Overview
ARMOR supports multiple maintenance trigger types, allowing you to track service based on time, usage, or a combination of both. Understanding which trigger type to use ensures your equipment gets the right maintenance at the right time.
The Three Maintenance Trigger Types
ARMOR monitors three different metrics to determine when maintenance is due:
| Trigger Type | What It Tracks | Best For | Example |
|---|---|---|---|
| Time-Based | Calendar days | Inspections, certifications, time-sensitive components | Annual safety inspection |
| Runtime-Based | Operating hours | Engine maintenance, wear items, filters | Oil change every 250 hours |
| Distance-Based | Miles or kilometers | Vehicle maintenance, tires, belts | Tire rotation every 5,000 miles |
Time-Based Maintenance (Calendar)
How It Works
Time-based maintenance triggers alerts after a specific number of calendar days, regardless of how much the asset was used.
Example Timeline:
Day 0: Maintenance completed (or rule created), counter resets
Day 1-364: ARMOR counts days passing
Day 365: Alert triggered: "Annual inspection is due"
User marks complete: Counter resets to Day 0, cycle repeats
When to Use Time-Based
- Regulatory inspections: Annual safety checks, certifications, licenses
- Time-sensitive components: Batteries (regardless of use), belts (age deterioration), hoses
- Compliance requirements: Insurance-mandated inspections, OSHA requirements
- Seasonal maintenance: Winterization, summer prep
- Rarely-used assets: Equipment that sits idle but still needs periodic maintenance
Configuration Example
Maintenance Name: Annual Safety Inspection
Data Field: None (time-based only)
Threshold: 0 (not applicable)
Max Days: 365
Unit: Days
Result: Alert triggers 365 days after last completion
Important: Max Days Setting
The Max Days field defines the calendar interval. If set to 0, only usage-based triggers are used. If set to a value (e.g., 365), ARMOR triggers maintenance when that many days pass, even if usage thresholds haven't been reached.
Runtime-Based Maintenance (Operating Hours)
How It Works
Runtime-based maintenance monitors the asset's operating hours (also called "engine hours" or "runtime") from telemetry. When accumulated hours reach the threshold, maintenance is triggered.
Example Timeline:
Hour 0: Maintenance completed, runtime counter resets
Hours 1-249: Asset operates, ARMOR tracks runtime from telemetry
Hour 250: Alert triggered: "Oil change is due (250 hours)"
User marks complete: Counter resets to 0, cycle repeats
When to Use Runtime-Based
- Engine maintenance: Oil changes, spark plugs, air filters
- Wear items: Brushes (scrubbers), belts (based on running time)
- Lubrication: Grease points, hydraulic fluid
- Heavy-use monitoring: Equipment that runs continuously vs. sporadically
- Manufacturer specifications: Most OEM maintenance schedules use runtime
Configuration Example
Maintenance Name: Oil Change
Data Field: runtime (or runTimeTotal)
Threshold: 250
Max Days: 0 (or 365 if you also want calendar backup)
Unit: Hours
Result: Alert triggers after 250 hours of operation
Telemetry Requirement
Runtime-based maintenance requires assets to have telemetry devices that report operating hours. If an asset doesn't have telemetry or the telemetry device isn't reading runtime (e.g., CAN bus not connected), runtime-based maintenance won't work for that asset.
Distance-Based Maintenance (Miles or Kilometers)
How It Works
Distance-based maintenance monitors miles or kilometers traveled from GPS telemetry. When accumulated distance reaches the threshold, maintenance is triggered.
Example Timeline:
Mile 0: Maintenance completed, odometer counter resets
Miles 1-4,999: Asset travels, ARMOR tracks distance from GPS
Mile 5,000: Alert triggered: "Tire rotation is due (5,000 miles)"
User marks complete: Counter resets to 0, cycle repeats
When to Use Distance-Based
- Vehicle-specific maintenance: Tire rotations, brake inspections, transmission service
- Mobile equipment: Forklifts, sweepers, delivery vehicles
- Fleet tracking: Any asset that moves significant distances
- Mileage-based warranties: OEM requirements tied to miles traveled
Configuration Example
Maintenance Name: Tire Rotation
Data Field: distance (or distanceTotal)
Threshold: 5000
Max Days: 0 (or 180 if you also want calendar backup)
Unit: Miles
Result: Alert triggers after 5,000 miles traveled
Important Considerations
- GPS Required: Distance tracking relies on GPS telemetry. Stationary equipment (generators, compressors) won't accumulate distance.
- Unit Matching: Ensure your threshold unit (miles/km) matches what your telemetry reports.
- Indoor/Poor GPS: If asset operates primarily indoors, GPS may not accurately track distance.
Hybrid Maintenance (Combined Triggers)
Using Multiple Triggers Together
The most robust maintenance rules use both usage-based and time-based triggers. This ensures maintenance happens whether equipment is heavily used or rarely operated.
Example: Oil Change with Hybrid Triggers
Maintenance Name: Oil Change
Data Field: runtime
Threshold: 250 hours
Max Days: 365 days
Logic: Alert triggers when either 250 hours OR 365 days is reached (whichever comes first)
Scenario 1: Asset runs 5 hours per day → reaches 250 hours in ~50 days → alert triggers at 50 days (usage-based)
Scenario 2: Asset runs 10 minutes per week → only 8.6 hours in a year → alert triggers at 365 days (time-based)
Why Hybrid Triggers Are Important
| Scenario | Usage-Only Problem | Hybrid Solution |
|---|---|---|
| Rarely-used backup equipment | Never hits usage threshold, oil never changed | Max Days ensures annual oil change |
| Seasonal equipment | Sits idle 6 months, oil breaks down | Calendar trigger catches it during off-season |
| High-use equipment | Calendar-only would be too infrequent | Usage threshold triggers more frequently |
Choosing the Right Trigger Type
Decision Matrix
| If your maintenance is... | Use this trigger type | Configuration |
|---|---|---|
| Required annually regardless of use (inspection) | Time-Based Only | Threshold = 0, Max Days = 365 |
| Based on engine hours (oil, filters) | Runtime + Time Backup | Threshold = hours, Max Days = 365 |
| Based on miles driven (tires, brakes) | Distance + Time Backup | Threshold = miles, Max Days = 180 |
| Critical safety item (high-risk) | Both Usage + Aggressive Time | Threshold = usage, Max Days = short |
| Cosmetic/non-critical (cleaning) | Time-Based Only (lenient) | Max Days = 90-180 |
Understanding Trigger Priority
Which Trigger Fires First?
When you configure both usage-based and time-based triggers, ARMOR triggers maintenance when either condition is met (whichever comes first).
Example Configuration:
- Data Field: runtime
- Threshold: 250 hours
- Max Days: 365
Logic:
- IF runtime reaches 250 hours → TRIGGER (even if only 50 days passed)
- IF 365 days pass → TRIGGER (even if only 50 hours accumulated)
Common Mistake: Conflicting Triggers
❌ Problem: Setting Max Days too short for usage threshold
Example: Oil change at 250 hours OR 30 days
Result: Time trigger always fires before usage threshold is reached (asset would need to run 8+ hours per day to hit usage before time)
✅ Fix: Set Max Days to allow sufficient time to reach usage threshold under normal operation (e.g., 365 days for 250 hours)
Telemetry Requirements by Trigger Type
| Trigger Type | Telemetry Required? | Data Source |
|---|---|---|
| Time-Based | ❌ No | ARMOR server tracks calendar days |
| Runtime-Based | ✅ Yes | Asset telemetry (CAN bus or hour meter) |
| Distance-Based | ✅ Yes | GPS telemetry (odometer/distance traveled) |
If assets don't have telemetry, use Time-Based Only triggers or install telemetry devices.
Real-World Examples
Example 1: Floor Scrubber Oil Change
Requirement: Change oil every 300 hours or annually
Configuration:
- Data Field: runtime
- Threshold: 300 hours
- Max Days: 365
- Unit: Hours
Result: Most scrubbers hit 300 hours in 3-6 months; alert triggers based on usage. Rarely-used scrubbers trigger after 1 year.
Example 2: Delivery Vehicle Tire Rotation
Requirement: Rotate tires every 5,000 miles or every 6 months
Configuration:
- Data Field: distance
- Threshold: 5000 miles
- Max Days: 180
- Unit: Miles
Result: High-mileage vehicles trigger every 2-3 months. Low-mileage vehicles trigger at 6 months.
Example 3: Generator Annual Inspection
Requirement: Annual safety inspection regardless of use
Configuration:
- Data Field: None
- Threshold: 0
- Max Days: 365
- Unit: Days
Result: Triggers exactly 365 days after last inspection, even if generator never ran.
Quick Reference: Trigger Type Selection
Use Time-Based When:
- Maintenance is compliance-driven (annual inspections)
- Component degrades over time regardless of use (batteries, hoses)
- Equipment has no telemetry
Use Runtime-Based When:
- Maintenance depends on engine hours (oil, filters, spark plugs)
- Manufacturer specifies hour-based intervals
- Equipment usage varies widely (some run constantly, some rarely)
Use Distance-Based When:
- Maintenance is tied to miles/km (tires, brakes, transmission)
- Asset is mobile and travels significant distances
- Warranty requirements are mileage-based
Use Hybrid (Usage + Time) When:
- You want comprehensive coverage (most cases!)
- Equipment usage is unpredictable
- Following best practices for preventative maintenance
Related Topics
- Introduction to Maintenance Management - Overview of the maintenance system
- Understanding Maintenance Rules - Detailed guide to rule configuration
- Creating a Maintenance Plan - Step-by-step instructions
- Auto-Scheduling Maintenance From Runtime/Hours - Advanced runtime configuration
Getting Help
If you need assistance choosing trigger types or configuring maintenance rules, 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
Feedback sent
We appreciate your effort and will try to fix the article