Fleet PM and maintenance
PM schedules and programs, meter readings, the due and overdue dashboard, and deferred work.
Preventive maintenance (PM) is scheduled revenue: every unit that comes due is a ticket waiting for a phone call. Set your service intervals up once, keep the meters current, and the Fleet PM Dashboard shows the whole fleet's due, overdue, and projected work in one place.
PM contracts need Mobile, Parts & Service or Enterprise
Everything on this page — PM schedules, programs, meter readings, the due/overdue dashboard and deferred work — works on every edition. Only PM contracts (Settings → PM Contracts) are edition-gated. See your edition and what's included.
Define your PM schedules. Open Settings → PM Schedules and click New Schedule. In the New PM Schedule window, give it a Name and Category (Oil & Filter, Tires, Brakes, Inspection, and so on), then set the Service Intervals — Miles, Days, and Hours. Any interval that's reached makes the PM due, so a schedule can trigger on mileage, time, engine hours, or whichever comes first. Add the Labor Operations and Parts / Supplies it should carry, and save.
Bundle schedules into programs. Open Settings → PM Programs and click New Program to group schedules into a named tier — a Class 8 linehaul truck might run one program, a light service van another. Give it a Name, check the Schedules in this program, and save. Units then enroll in the program instead of being wired to schedules one at a time.
Keep the meters current. Mileage and engine-hour readings drive every projection — the fresher the meters, the more accurate the due dates. Readings captured on tickets and inspections flow in automatically, and you can add one by hand from a vehicle's Meter History panel: click Add reading, pick Miles or Hours, enter the value and date, and click Record.
Open the Fleet PM Dashboard. Click Fleet PM in the sidebar (under Customers). The cards count Overdue, Due now, and Due soon units, plus the Projected revenue sitting in that visible work.
Work the list. Filter with the bucket chips — All, OVERDUE, DUE NOW, DUE SOON — then work top-down. Each row shows the Unit, Customer, which PM is due, its Status, the Projected date, and Miles left. Click Open to jump to the vehicle and book the work.
Don't lose declined work. Recommended jobs a customer put off don't vanish — the Deferred Work Backlog report (under Reports) keeps them valued and aged, sorted by severity (SAFETY, SOON, MONITOR), so they resurface at the next visit instead of falling through the cracks.
Watch contract renewals. If you sell maintenance agreements, the Contract renewals panel on the dashboard flags how many renew in the next 90 and 30 days and the Revenue at risk in that window, so a lapsing contract gets a call before it's gone.
Telematics, in one setup. Under Settings → Telematics you can connect Samsara, Motive, or Geotab with a read-only API token, then link each device to its unit. Odometer and engine-hour readings then sync in automatically, so PM projections stay current without anyone typing meters — and you can optionally turn reported fault codes straight into deferred work.
What happens behind the scenes
None of this posts to your books on its own — PM is about surfacing work, not billing it. Meridian compares each unit's latest meter reading and service dates against its schedule intervals and sorts every unit into overdue, due now, or due soon, projecting a due date from how fast that unit accumulates miles or hours. The projected-revenue figure is just the value of the labor and parts on the due PMs — a forecast of what's bookable, not money earned. Booking the work happens on the vehicle, the same as any other ticket, and that's when revenue and your books come into play. Declined jobs are held in the deferred backlog with a value and an age so nothing recommended is silently lost, and telematics simply feeds fresher meters into the same math.
Troubleshooting
The dashboard works off meter readings and intervals. If a unit's odometer or hour meter is stale, its projected due date drifts. Add a current reading from the vehicle's Meter History panel, and confirm the unit is enrolled in a program or attached to the right PM schedule.
The empty state — "Nothing due — the fleet is current" — means no unit has crossed an interval yet. That's good news, not an error. As meters advance, units move into the Due soon and Due now buckets automatically.
Meridian flags a reading that looks impossible — a big jump or a number lower than the last one (often a replaced odometer). Open the vehicle's Meter History, then Correct the value, record an Offset for a swapped odometer, or Dismiss it if it's genuinely right. Fixing flagged readings keeps projections honest.
Check the connection under Settings → Telematics — the card shows its status and last sync. Make sure each unit's device is linked; an unlinked device has no vehicle to post readings to. You can trigger Sync now to pull the latest immediately.