Asset Performance, Warranties & Reliability Reports

• On each asset and vehicle — the Performance cards at the top of the Details tab, and a Warranty section further down under Purchase Info.
• Equipt > Reports — three tabs: PM Compliance, Uptime and Warranties. Clicking a row opens that asset (or, for a missed PM with a work order, that work order).

Everything is computed live from your work orders, status changes and PM schedules — there's nothing to refresh or rebuild. Assets and vehicles are treated the same throughout.

Open an asset or vehicle, click Edit, and fill in the Warranty section. You can enter it two ways:

• End date — type the date coverage ends. A start date is optional.
• Coverage period — enter a length in years or months (e.g. 3 years). Leave the start blank to count from the purchase date. The form shows the end date it works out, e.g. "Covered through Sep 30, 2026".

A period covers through the day before the anniversary: 12 months from Mar 15, 2026 covers through Mar 14, 2027. Either way, the end date is what every report reads. Use Warranty Notes for the details that don't fit a date — "powertrain 5 yr / 2,000 hrs", "dealer extended plan", a claim phone number.

The window toggle above the cards (30 days / 90 days / 12 months) changes Uptime, PM compliance and Avg repair time. The two cost cards always show 12 months and lifetime.

Hover any card for a one-line reminder of how it's calculated.

Uptime comes from the asset's status. Every time the status changes — from the asset's header, the Edit form, or a work order — Equipt records when it changed. Uptime is the time spent Active divided by the time spent in service:

Example. Over the last 90 days a dump truck was Active for 80 days and In Shop for 10: uptime is 80 ÷ 90 = 88.9%. If it had also sat Inactive for 30 days over the winter, those 30 days wouldn't change the answer.

Avg repair time is the average length of the In Shop / Out of Service stretches that both started and ended inside the window — a truck that's still in the shop counts toward downtime, but not toward the average until it comes back.

• A work order's cost is its parts (quantity × unit cost), plus labor (hours × rate), plus vendor charges — the same lines as its Costs tab.
• It's dated by when the work order was completed. A work order that's still open is dated by when it was created, so money already spent shows up right away.
• Skipped work orders don't count.
• PM is any work order typed Preventive or generated from a PM schedule or a meter automation. Everything else is Repair.
• Only work orders attached to the asset count — a sub-asset's costs aren't rolled up into its parent, and purchases that never touched a work order aren't included.

PM compliance is scored against each schedule's calendar, not just against the work orders that happen to exist. Since PM work orders are generated by hand, a week nobody generated would otherwise vanish. Each PM on each asset lands in one of these buckets:

PM compliance = Done ÷ (Done + Missed). On-time rate = On time ÷ (On time + Late).

• Multi-asset schedules count per asset. A weekly schedule on 3 mowers that nobody generated is 3 missed PMs that week, one on each mower's card.
• Meter-triggered PMs count too. An oil-change automation (Meter Threshold) comes due 7 days after the meter trips. Its work order — whether the automation created it or someone converted the request — is on time if it's done within those 7 days.
• Paused schedules owe nothing. Cycles that fall inside a pause window aren't due, so they can't be missed. See Pausing a schedule.

A weekly schedule on 3 mowers is due Wednesday, Sep 23. The mechanic forgets to generate it.

1. Thursday onward — the Sep 23 cycle shows as 3 Not generated (missed) PMs, and each mower's PM compliance drops.
2. Sunday, Sep 27 — someone generates it. The batch is due Sep 23 (the date it was actually due), and the schedule's Next Due moves to Sep 30 — the next Wednesday, not a week from Sunday. The 3 misses become 3 open, overdue PMs.
3. Monday — the work is done. They count as Late: PM compliance is back to where it was, and only the on-time rate takes the hit.
4. Wednesday, Sep 30 — generate the regular batch as usual. (The previous batch has to be done or skipped first; a schedule can only have one open batch at a time.)

Had the schedule sat for three weeks instead, generating would create one batch for the oldest week; the two weeks it skipped past count as missed.

All three live at Equipt > Reports.

• PM Compliance — compliance and on-time rate for the last 30 days to 12 months, missed PMs broken into not generated / skipped / overdue, a by-month chart, a table per PM schedule and meter rule (worst first), and a list of every missed PM.
• Uptime — fleet uptime, total downtime, average repair time and what's down right now, then a table per asset, worst uptime first. Filter to vehicles or equipment, and switch between assets with downtime and every asset in service.
• Warranties — counts of active, expiring and expired warranties, and the list filtered to the next 30 days, next 90 days, everything under warranty, expired, or no warranty on file. Disposed assets are left out.

• Downtime can't be edited after the fact. If a machine was down but nobody changed its status, the history won't know. Change the status going forward.
• Backdating a pause clears misses. A pause starting in the past removes that period's missed PMs from compliance. Pauses record who created them.
• A brand-new asset reads 100% (or 0%) quickly. With only minutes or days of history, one status change swings the percentage a lot. Longer windows settle it down.
• Hour-based warranties (e.g. 2,000 engine hours) aren't tracked against a meter — put them in Warranty Notes and use the end date for the calendar limit.