How to choose a fleet system

Own the hardware and data

Some vendors lease the tracker as part of the subscription; others sell it outright. Leased hardware looks cheaper on day one, but it usually ties the device to the contract: cancel, and you return or pay out every unit. Owned hardware stays on the machine and can be moved, reused or sold with it.

Ask about the warranty in years, not adjectives, and what a replacement involves: who ships it, who fits it, and how long a machine goes unreported in between.

The data matters more than the box. Before you sign, get these in writing:

• You own the machine data: positions, hours, fault codes, inspections and service history.
• You can export all of it at any time, as CSV or through an API, at no charge.
• The export still works for a set period after you cancel.
• The contract names who else can see it: manufacturers, dealers, lenders, insurers or data buyers.

Service history has a cash value. A clean record of every 500-hour service helps at resale and backs a warranty claim when an engine fails inside its coverage. If that record lives in a vendor’s system and cannot leave with you, part of your machine’s value lives there too.

Cover every brand you run

Most heavy fleets are mixed: excavators from one maker, loaders from another, older dozers with no telematics at all, and a yard of trailers, light towers and generators with no engine computer. A system that reads one brand well leaves you a second portal for everything else.

A machine can report three ways. A tracker wired to the machine reads its J1939 engine data and GPS position directly. A manufacturer’s own telematics feed can be pulled in through ISO/TS 15143-3. That ISO standard, which grew out of the AEMP telematics standard, specifies a web-service schema for sending machine status data such as location and operating hours from a telematics provider’s server to other applications. And an older third-party tracker can sometimes be connected through its own data feed. Ask which of the three each vendor supports, and what each one costs.

Then check what actually arrives. Manufacturer feeds differ in which fields they send and how often they refresh, and fault codes are not formatted the same way across makers. Ask for a trial with your own machines, by serial number. Are hours, fuel and active faults showing for each one, and do the fields line up? The question is not whether a vendor “supports” a brand, but whether the excavator in your yard shows its hours next to the loader parked beside it.

Small assets belong on the same map. Battery trackers on trailers and towers, and Bluetooth tags on breakers, buckets and laser levels, should show up beside the iron, not in a separate app.

Plan for the dead zones

Coverage maps describe highways and towns. Jobs happen on lease roads, mesa tops, canyon bottoms and pipeline right-of-way where a phone shows no bars. Ask every vendor what their device does when it loses signal, and for how long.

A useful answer has numbers in it. How many days of data does the device store offline? Does it send everything when it reconnects, or only the latest position? How does the system show a machine that has stopped reporting, as opposed to one that is simply parked? Store-and-forward is enough for most hour and service tracking, because hours do not need to arrive in real time to open a work order on time.

For jobs that need live position or alerts with no coverage at all, ask about satellite. Find out what a satellite message contains (position only, or hours and active fault codes too), how often it sends, what the device and the data plan cost, and whether satellite can be switched on and off per machine as it moves between jobs.

Then test it. Take a trial device to your worst site, leave it a week and see what arrived. Do the same with the mobile app: an inspection or work order completed with no signal should save on the phone and sync later, not fail at the submit button.

Read the contract terms first

Feature lists change every quarter. A contract stays the same for its whole term, so read it before the demo, not after the decision. Check these points, in writing:

• Term and renewal. How many months, whether it renews itself, for how long, and how much notice ends it.
• Notice. How to give it, to whom, and whether an email counts.
• Minimums. A per-machine minimum, a fleet minimum, or a fee to remove machines mid-term. Fleets sell, park and rent machines every season, so you need a way to take one off the bill.
• Price changes. How much notice before the per-machine price goes up, and whether you can leave when it does.
• Hardware at the end. Yours to keep, returned, or paid out.
• Users. Per-user fees discourage giving mechanics and operators a login, and they are the people who most need one.
• Data at the end. Export rights after cancellation, and when the vendor deletes your records.

A month-to-month term makes the vendor keep earning the account every month. If a vendor asks for 36 months, ask what you get in return, in writing, and exactly what it costs to leave in month 14.

What the rollout asks of you

A system is only as good as its first month. Ask each vendor to walk through the rollout week by week, and to say what they need from your team in each week. For 25 to 300 machines, a workable plan usually fits in four to eight weeks:

• The asset list. Every machine, attachment and trailer, with serial numbers, current hour meters and the last service. This is the step most fleets underestimate.
• Installs. Who does them, how many machines a crew fits in a day, whether they work in your yard or on the job, and what proof you get per machine, such as photos and a test report.
• Rules. Service plans, geofences and alert routing. Agree who gets which alert before anything goes live, or every alert goes to everyone and all of them get ignored.
• The first live week. Someone from the vendor checking in daily, and a review at day 30 of what is working and what needs to change.

Ask who your named contact is, for how long, and whether they have worked in a shop or a yard. Ask about training in the languages your crews speak; across much of the Southwest that means English and Spanish for inspections, training and the app.

Do the price math yourself

Turn every quote into one number: total cost per machine per month over three years, hardware included. Here is the arithmetic with round numbers for a 100-machine fleet:

• Subscription: $30 per machine per month × 100 machines × 36 months = $108,000.
• Hardware and installation: a $200 tracker and $100 to fit it, on 100 machines = $30,000.
• Satellite: 20 machines on remote jobs at $10 a month for 36 months = $7,200.
• Total: $145,200, divided by 100 machines and 36 months = about $40 per machine per month.

Put every quote through the same lines and add whatever else it carries: per-user fees, onboarding fees, travel, and the cost of removing a machine mid-term. Machines that already report through a manufacturer feed may need no tracker at all, which changes the hardware line.

Then price the other side. Add up what the problems from your first list cost this year: idle fuel, rental days past the job, a breakdown that stopped a crew. If they cost less than the system, buy a smaller plan or wait a year. The ROI calculator runs that arithmetic with your own figures, and the PM interval planner shows what your service calendar looks like before you change anything.