CMMS for Fleet Management

Forklifts, tow tractors, DG sets, cranes and company trucks rarely get the same maintenance discipline as production machinery — they sit on a different spreadsheet, serviced whenever someone remembers. AssetAI folds these mobile assets into the same CMMS used for plant equipment, so a genset's 500-run-hour service and a lathe's calibration date are tracked with one system, not two.

How Meter-Based Scheduling Actually Works

Every fleet asset carries its own meter unit — kilometres for a truck, run-hours for a DG set, cycles for a crane — and its schedule computes next-due from the last reading plus the interval. There's no separate "fleet module" logic to learn:

• A schedule fires the moment a captured reading crosses its target and auto-rebaselines from there, so due dates stay accurate even if a vehicle runs erratically some weeks and not at all in others.
• Readings come in through the QR scan page, manual entry, WhatsApp, or API — whatever mix fits the yard. Any reading lower than the last one is rejected outright, which stops a mis-typed odometer or hour-meter value from silently resetting a schedule.
• Because it's one schedule type underneath, a plant can mix trucks, forklifts and gensets on the same board without separate configuration per asset class.

This is different from telematics-driven fleet software: AssetAI does not pull odometer or ECU data automatically, and there's no GPS layer showing where a vehicle is right now. What it does track precisely is when something is due for service and whether that service happened — which, for an internal plant fleet, is usually the actual maintenance problem worth solving.

Breakdown Capture From the Yard, Not the Office

Fleet breakdowns happen away from a desk, often outside network coverage, which is why the breakdown flow is built around the vehicle QR code rather than a login:

• A driver or operator scans the vehicle's QR, enters their name and the company scan PIN — no app install, no credentials to manage — and logs severity, failure mode and photos directly from a phone.
• If the phone is offline at submit time, the report and photos are held on-device and sync automatically once back online, which matters for yard corners and highway stretches with poor signal.
• Emergency-severity reports skip the approval step and raise the work order immediately, so a stalled forklift on the shop floor doesn't wait on someone to review it first.
• Closing that work order requires recording a failure cause and remedy, which is what makes the resulting failure Pareto by vehicle trustworthy over months rather than a pile of unstructured tickets.

Seeing Where the Fleet Budget Actually Goes

Because parts, outside services and labour all attach to the vehicle record on the work order, per-vehicle repair cost accumulates automatically rather than needing a separate cost sheet. Set a downtime cost per hour on each asset and the downtime-cost KPI ranks your worst-performing vehicles and equipment in a top-8 Pareto — assets without that figure set simply don't appear, so it's worth populating before relying on the ranking. The same daily 06:15 sweep that watches plant-asset AMC and warranty dates does the same for fleet vehicles, flagging expiries before they become compliance gaps.

For plants benchmarking maintenance discipline against broader OEE and TPM practice, treating fleet as first-class CMMS assets — not a side spreadsheet — is a straightforward way to close a visibility gap. See how it fits your other industries and use cases, or book a demo on your actual fleet data.

Fleet assets bring a different failure profile than static plant equipment — intermittent duty cycles, exposure to weather and yard conditions, and drivers who change shift by shift. AssetAI is built to handle that inside the same system covering use cases like preventive maintenance and spares control, without pretending to be something it isn't.

What AssetAI Fleet Tracking Is Not

It's worth being explicit about scope, because "fleet management" software usually implies telematics and dispatch — this doesn't:

• There's no GPS or telematics layer, no live location tracking, and no automated feed from an odometer, ECU or OBD-II port. Every meter reading gets into the system through a QR scan, manual entry, WhatsApp, or an API push that the customer wires up themselves.
• Fuel isn't tracked. Meter readings hold distance, run-hours or cycles — not litres or fuel spend — so this isn't a fuel-monitoring tool.
• Driver management, licence renewals and route or trip planning sit outside the product entirely.
• There's no permit-to-work workflow. What exists instead is a per-asset safety-measure list — LOTO, PPE, whatever applies — that prints directly on the job sheet so the technician sees it before starting work.

That boundary is deliberate: this is for plants running an internal fleet of forklifts, tow tractors, DG sets, cranes or company trucks who want it managed alongside production assets, not a logistics operator needing dispatch software. If your fleet is really the business — public-road transport, last-mile delivery — you need a purpose-built fleet-ops platform, not a plant CMMS. The full list of features makes this scope clear before you commit to anything.

AMC, Warranty and Failure Records That Hold Up Over Time

A fleet asset's paperwork is usually where things go missing first — an AMC lapses, a warranty claim window closes, nobody notices until the next breakdown. AssetAI watches this on a schedule rather than relying on someone's memory:

• Every AMC, warranty and recorded document date is checked by a daily 06:15 sweep, which flags anything approaching expiry so renewal or claim decisions happen before the cover runs out.
• Closing a breakdown or corrective work order requires entering a failure cause and remedy. Skip this discipline and your failure Pareto is just a list of dates; enforce it and the same data becomes a reliable guide to which vehicle, which failure mode, and which repair actually worked — the same logic that underpins OEE analysis on the shop floor.
• Emergency-severity breakdowns bypass the approval step and raise the work order immediately, so a stalled forklift blocking a dock doesn't wait on a sign-off chain.

None of this replaces a formal maintenance standard, but it gives you the records to support one — worth checking against the structure in ISO's standards library if you're working toward a certified maintenance system, or reviewing our ISO & standards page for how AssetAI maps to it.

Bringing an Existing Fleet Onto AssetAI

For plants coming off spreadsheets, the practical path is usually incremental rather than a big-bang switch:

• Register each vehicle as an asset with its meter unit, then let the first few readings establish a baseline before schedules start firing — this avoids a flood of false-due alerts in week one.
• Set downtime cost per hour on vehicles you actually want ranked; unset assets are simply left out of the Pareto rather than distorting it.
• Print QR tags for the cab or equipment frame so breakdown reporting works from day one without app installs or driver logins.

Manufacturing fleets in India — a sector IBEF tracks in detail — tend to run mixed-age equipment with inconsistent service history, which is exactly the gap meter-based scheduling closes. If you want to see how this fits your specific asset mix, book a demo or check pricing for your fleet size.