Fleet management systems: maintenance, fuel, and telematics data

Reference article · 5 min read

Almost every agency runs vehicles and equipment: patrol cars, refuse packers, plows, crew trucks, mowers, and trailers. The technology that tracks them arrives in layers. A maintenance system comes first, fuel is measured at the island, telematics arrives after a safety concern or a grant, motor pool bookings live in a shared calendar, and the replacement list is rebuilt by hand each budget cycle.

Each layer holds part of the record for the same vehicle. The stack works only when they agree on one asset identity and feed data to one place. What follows walks through the components and the decisions to settle before a solicitation.

The maintenance system at the center

The fleet management information system, or FMIS, holds the asset record and work history.

• Asset master. VIN or serial number, class, department, fund, acquisition cost and date, warranty, and disposal status. Pick one asset identifier and require every other system to carry it.
• Meter readings. Odometer and engine hours drive preventive maintenance, arriving from fuel transactions, telematics, and technicians at the counter. Decide which source is authoritative and how bad readings are rejected rather than averaged in.
• Work orders. Labor time, parts issued, outside vendor invoices, cause and correction codes, and downtime. Coding discipline here decides whether any later cost analysis means anything.
• Schedules and inspections. Preventive maintenance by time, mileage, or hours, plus regulated inspections for commercial, passenger, and emergency vehicles. Those requirements vary by class and state and change, so confirm them with the responsible state agency.
• Parts and warranty. Bin locations, reorder levels, cycle counts, and issue to work order, tied to purchasing. Warranty recovery and recall tracking repay an organized asset record.

Fuel: islands, cards, and reconciliation

Fleets usually have two fuel paths and need both in one ledger. On-site islands use a controller that authenticates vehicle and driver by key, card, or automatic identification device, prompts for odometer, and records gallons by tank and product. Fuel cards cover purchases away from the yard.

• Tank monitoring. Automatic tank gauges, inventory reconciliation, and release detection. Federal and state storage tank rules impose monitoring and recordkeeping duties; confirm current obligations with the state agency that administers the program.
• Exception reporting. Gallons exceeding tank capacity, two fills minutes apart, odometer regressions, wrong product, off-shift transactions. These are the practical control over fuel loss.
• Allocation and tax. Fuel posts back to using departments. Public fleets may qualify for certain fuel tax exemptions or refunds, and vehicles crossing state lines may carry reporting duties. Confirm with finance and counsel.

Telematics and vehicle location

A telematics device reads position and speed from GPS and vehicle data from the diagnostic bus, typically SAE J1939 on heavy vehicles and OBD-II on light duty. Outputs include ignition state, engine hours, odometer, fault codes, fuel consumed, idle time, and harsh events. Plow position, spreader rate, and cameras can be added.

The uses that hold up are operational: a map of which streets have been plowed, verification of service complaints, automatic meter readings into the FMIS, idle reduction, and early triage of fault codes. Settle employee notice and any labor relations obligations first. Location and video data accumulate continuously, may be subject to public records law, and belong on a retention schedule.

Motor pool, reservations, and utilization

A motor pool module handles reservations, driver eligibility, keyless or kiosk access, trip logs, and billing to the reserving department. Its lasting value is utilization data: assigned vehicles that sit and pool vehicles booked solid are both arguments for reassignment.

Replacement planning and total cost of ownership

Replacement decisions need cumulative cost per asset: purchase price, maintenance labor and parts, outside repairs, fuel or electricity, downtime, utilization, and resale proceeds. Most agencies combine those into a score weighing age, meter reading, repair cost relative to value, condition, and mission, then review the ranked list with departments.

The score is only as good as work order coding and the capture of outside invoices against the right asset. Funding matters as much as ranking: a replacement or internal service fund with annual charges produces a steadier schedule than an annual capital request, and rates should be recalculated from the same cost data.

Charging and battery data

• Charge sessions. Energy delivered, duration, port, and cost, from the charger and its management software. Open Charge Point Protocol is a common interface between chargers and those platforms; ask which version a product supports.
• Battery data. State of charge, state of health, and energy per mile. Some light-duty vehicles report through the manufacturer's data service rather than a plug-in device, limiting what a telematics vendor sees.
• Site load and cost models. Depot charging interacts with utility rates, including demand charges, so scheduling is a cost decision. Chargeback rates, budgets, and replacement scoring all have to handle energy alongside gallons.

What to ask vendors and put in the contract

• Ask which fuel controllers, card providers, telematics devices, charging networks, and financial systems the product has been interfaced with, and whether each was standard or custom.
• Require export of all agency data, including attachments and photos, on request and at termination, in a documented format at no added charge.
• Separate telematics hardware and service terms from the maintenance software so either can be replaced.
• Settle device questions: purchase or lease, ownership, cellular service, pricing per asset or per device, and who reinstalls units when vehicles rotate.
• State data ownership, limits on vendor use of driver-identifiable location and video, and retention settings matching the agency's records schedule.
• Plan the conversion: asset history, parts counts, open work orders, and a fuel island cutover window.

HQT works with state and local agencies on system selection, integration between operational and financial systems, and reporting built on that data.

Frequently asked questions