Skip to content
Equipment rental · Construction · Platform fit

Preventive maintenance for distributed fleets

Recurring service schedules that watch live machine hours and book the job themselves. Auto-generated maintenance orders, completed in the field by QR, with a permanent service history per asset.

The problem

Equipment runs on hours, but the service that keeps it running tends to run on memory. The 250-hour service happens at 310 because nobody was watching the meter. A rental unit goes back out with an overdue inspection because the work order was a sticky note that fell off a desk. Multiply that across a few yards and the “maintenance program” is really a stack of clipboards and one stressed service manager.

A continuous hour meter from telemetry fixes the measurement. It does not, on its own, change the oil. Knowing a machine sits at 490 hours only matters if it turns into a job someone is assigned, does, and signs off.

What we built

On top of continuous hour accrual, a maintenance layer for an operator running mixed equipment across multiple yards — the thing that turns the number into work:

  • Recurring schedules per asset — every 250 hours, every 6 months, or both, whichever comes due first. A machine that runs hard gets serviced on hours; one that sits all winter still gets its annual.
  • A nightly checker that compares every schedule to live machine hours and elapsed time, and generates an order the moment one comes due — with the schedule’s checklist copied onto it.
  • Orders that carry the work — assignee, priority, due date, and the checklist. Owners are emailed when an order is generated, and again if it passes its due date unfinished.
  • A printable QR label so a technician scans the order on their phone, reads the hours straight off the meter, and marks it complete in the field — no account, no login.
  • Automatic closeout — completing an order resets the schedule’s baseline so the next one fires on the next full interval, and writes a permanent line to the asset’s service history.

The outcome

  • Services land on the interval, not after it — booked at 490, done by 500, without anyone tracking it by hand.
  • The clipboard is gone. The hours come off the machine in front of the tech, not someone’s memory of it back at the desk.
  • Idle and hard-run machines both stay covered — time-based inspections still fire on the units that sit, hour-based services fire on the units that don’t.
  • Every completed service is on the record, per asset — the history that warranty claims, audits, and resale conversations actually need.

This is the other half of the 490-hour service. Maintenance Orders ship on the Enterprise plan.

Have something similar?

Let's talk Back to all solutions