If you run dozens or hundreds of tablets bolted into trucks and tractors, updating firmware by visiting each vehicle with a cable and a laptop does not scale. Over-the-air (OTA) updates replace that with a remote push over cellular or Wi-Fi. This post covers what "an update" actually means, how to stage one, and what to ask a vendor.
Three kinds of update, three levels of risk
"OTA update" gets used for three different things:
- Application updates: a new version of the dispatch or fleet app. Lowest risk, most frequent.
- Configuration changes: settings, kiosk lock-down, allowed apps. Changed from the console, no new build needed.
- Firmware and OS updates: the layer under everything else. Highest risk, so this is the one that needs staging and a rollback plan.
Over-the-air device management is the umbrella. It covers all three, plus the visibility to see what each device received.
Stage it
Do not push to the whole fleet at once.
- Push to a small group of vehicles first.
- Confirm they come back healthy: app starts, GNSS and CAN data still flowing, cameras still show.
- Widen to the next group.
- Keep a list of which units took the update, which failed and which are still pending.
This matters most when one tablet runs several systems together (driver monitoring, 360° camera view, ISOBUS implement control). An update to one component has to be checked against the others before wide rollout.
The real metric is downtime
A vehicle waiting for a scheduled update is a vehicle not working. With manual updates, you pay that cost every time a fix or feature has to roll out. OTA turns it into a background task.
Questions to ask a vendor
- How are updates staged, and can I target a subset?
- How are failures reported per device?
- What happens if a vehicle loses signal mid-download? Does it resume, retry or roll back?
- How fast can a critical patch reach every unit?
- Who builds the firmware: the hardware maker or a third party? That decides who can issue a fix.
Answers to these tell you whether OTA is a real capability or a checkbox.
FAQ
Does the vehicle have to be parked on Wi-Fi?
Usually no. Most systems work over cellular, though updates are typically scheduled for low-usage windows.
What if connectivity drops mid-update?
A well-designed system resumes or retries, rather than leaving the unit half-updated. Behaviour depends on configuration, so confirm retry and rollback for your project.
Is staging worth it for a small fleet?
It costs little extra time and scales down easily, so yes.
Written by the CF-Device team. We build rugged vehicle-mount tablets (the VCM series) and the TANK V2 screenless vehicle computer. The full version of this article, with links to our MDM and fleet guides, is at CF-Device. CF-Device is the brand of Shenzhen CF INTECH Intelligent Technology Co., Ltd.
Top comments (0)