Perspective
You Already Own the Fleet Data You Can't Use
You have been paying for telematics for five years, maybe ten. Every machine in your fleet with a factory-installed system or an aftermarket tracker has been reporting hours, location, fault codes and idle time the entire time. That data exists. It belongs to you. And most of it sits in a portal you log into once a quarter, if that.
The question nobody asks out loud: why?
The data is not the problem
A modern telematics feed carries more than a location dot. Engine hours. Idle percentage. Fuel level where the sensor exists. Fault codes. Service intervals. Battery voltage. Operating mode. The feed is rich enough to run a fleet on—if you could actually reach it.
But you cannot. Not because the data is missing, and not because you lack permission. You cannot reach it because the software reading that data was not built for you.
Hardware-led vendors build hardware-led software
The company that sold you a telematics device has a hardware business to run. Its roadmap competes with component costs, dealer programs, regional rollouts, firmware updates and whatever else keeps the hardware moving. Software is a necessary add-on, not the product.
That is not a criticism. It is a business model. A hardware company builds software to support its hardware. A single-brand OEM builds a portal for its own equipment. The incentives line up exactly the way you would expect.
The result is predictable. You log into Cat for Cat. Deere for Deere. JLG for JLG. Genie for Genie. Four portals before your Monday meeting—export each to Excel, paste them together, hope the columns line up—and you still have not touched the Bobcat skid steers or the aftermarket trackers on your attachments.
That is not a technology gap. That is an incentive gap.
The single-brand portal argument
A Cat dealer with a single-brand fleet is well served by VisionLink. The portal matches the fleet. The roadmap matches the business.
A rental company with three aerial brands is not. JLG, Genie and Skyjack compete head-to-head. None of them has an incentive to surface another manufacturer's machines in its own portal. So an OEM portal is worth roughly the share of the fleet carrying that brand. On a mixed fleet, that share is never one hundred percent.
This is structural. It is not going to change because someone asks nicely.
The market has already conceded the point
John Deere agreed to acquire Tenna in December 2025 and completed the deal in February 2026. Deere already had JDLink. It built and maintained its own telematics platform for years. And it still bought a company whose entire value proposition was mixed-fleet visibility.
Deere could have extended JDLink. It chose not to. It acquired rather than built—because the problem is not writing more code, it is serving fleets that will never be single-brand.
That is public record. What Deere does next is its own business. But the acquisition itself says something about where the industry knows the value is.
The data you already have is the asset
Think about what is sitting in your telematics history right now. Five years of hour meters on every tracked machine. Fault code logs. Utilization patterns by season, by branch, by customer. Service intervals tied to actual operating hours, not calendar guesses.
That history cannot be recreated. If you replaced every device in your fleet tomorrow, you would start from zero. The value is in the accumulation—and right now, most of that value is locked in portals you barely use.
This is not about switching hardware. You do not need to rip out what you have. The hardware works. The data flows. What you need is software that reads it all in one place and treats the accumulated data as the asset, not as a byproduct of a hardware sale.
Software first, not software last
Incus5 is a data intelligence platform for equipment rental companies and construction contractors. Founded in 2019, headquartered in Tempe, Arizona. Device-agnostic—Incus5 sells no hardware or telematics devices. It reads data from telematics feeds, ERP systems and operational records that customers already have, and unifies owned and rented assets into one view.
That includes assets with no telematics at all. Attachments. Older machines. Small equipment. A fuel truck delivery record is neither telematics nor ERP—it is operational paperwork—and it still belongs in the fleet picture. Flat rate per asset, regardless of data source.
The point is not that Incus5 is better than any particular OEM portal. The point is that the software leads. It is not an afterthought attached to a hardware sale. The roadmap serves the fleet, not the device business.
What this looks like in practice
Imagine your Monday meeting. Instead of four logins and four exports, you open one screen. Every machine—Cat, Deere, JLG, Genie, Bobcat, the aftermarket trackers, the assets with no telematics—shows up in the same view. Utilization by branch. Idle-on-rent by customer. Service due by engine hours, not by the calendar. Fault codes that surfaced overnight, ranked by severity.
You are not missing any of this data today. You are just missing the software that reads it together.
Incus5 connects to 51+ integrations, of which 36+ are telematics and IoT. The customer holds the relationship with the OEM or telematics provider. Incus5 reads data the customer is already entitled to.
The longer you wait, the more history you lose access to
Every month you stay fragmented, your telematics history gets harder to use. Not because it disappears—because the pattern recognition depends on continuity. Utilization trends, seasonal shifts, service forecasting from actual hours—all of it gets better with depth.
The data is already there. The question is whether you can use it before the next budget cycle, or the one after that, or never.
This is not a pitch for a feature
This is an argument about who should own the software that reads your fleet data. A hardware vendor will always prioritize its hardware business. An OEM will always prioritize its own brand. A software company that sells no hardware has one job: make the data useful.
You already own the fleet data you cannot use. The fix is not more hardware. It is software that was built for your problem, not someone else's.
Key takeaways
- Your telematics devices have been collecting valuable data for years—hour meters, fault codes, utilization history—but fragmented portals keep most of it out of reach.
- Hardware-led vendors build software to serve their hardware business, not your operations. OEM portals cover one brand; mixed fleets need something else.
- The accumulated history in your telematics feeds cannot be recreated. That data grows more valuable the longer you have had hardware installed—if you can access it.
- Device-agnostic software treats the data as the asset, not as a byproduct. One view, every brand, including assets with no telematics at all.
Frequently asked questions
Why can't rental operators use telematics data they've been collecting for years?
The data exists and belongs to the operator, but it is scattered across multiple OEM portals—each built to serve that manufacturer's equipment only. Combining Cat, Deere, JLG and Genie data requires manual exports and spreadsheet work. The barrier is not technology; it is that hardware-led vendors build software around their hardware business, not around mixed-fleet operations.
What does device-agnostic mean in fleet software?
Device-agnostic means the software sells no hardware and reads data from whatever telematics devices the customer already has—OEM-installed systems, aftermarket trackers, or both. The software is not tied to any particular device manufacturer, so it can unify data across brands and even include assets with no telematics at all, like attachments or older machines.
Can fleet data from multiple OEMs really be combined in one system?
Yes. The customer owns their telematics data regardless of which OEM portal displays it. A platform with integrations to multiple OEM feeds can pull that data into one view—hours, fault codes, location, utilization—without requiring the customer to swap hardware or negotiate new agreements with each manufacturer.
Why is historical telematics data valuable?
Years of hour meters, fault codes and utilization patterns reveal trends that a fresh install cannot show. Service forecasting improves with depth. Seasonal utilization becomes visible. Residual value decisions get sharper. That history cannot be recreated if lost—it is the compound interest of fleet intelligence.