Factory telematics is now standard on most new construction equipment, and manufacturers increasingly expose that data through APIs built on the AEMP standard, ISO 15143-3. But two OEMs' published documentation, from Bobcat and Hitachi Construction Machinery, shows that the data a fleet gets from the factory depends on what it pays for, which machines it owns and how fresh it needs the information to be. That is why, for some fleets, a third-party telematics device remains the better call.
Bobcat: access shaped by subscription
Bobcat's developer portal documents a telematics API that lets third-party software pull machine data for a fleet, using OAuth 2.0 client credentials and the standard's XML format. Identical requests are cached for an hour.
The documentation is explicit that some endpoints require an active Machine IQ subscription, and it splits the data into two tiers:
- Basics / Standard: location, cumulative operating hours, fuel remaining, DEF remaining and engine status.
- Health & Security / Premium only: diagnostic codes, fuel used and cumulative idle hours.
The data most useful for maintenance and utilization analysis, fault codes and idle time, sits behind the higher tier. A platform connecting a customer's Bobcat machines will see different data depending on what that customer pays for.
In Europe, Bobcat also publishes a notice under the EU Data Act (Regulation (EU) 2023/2854), which gives users of connected products the right to access the data those products generate. It explains that owners, renters and lessors can get machine data through the on-board interface or through online services such as Machine IQ, and that data is refreshed about every 20 minutes while a machine runs and once a day when it is off.
Hitachi: faster data as an option
Hitachi Construction Machinery's Telematics API, which also follows ISO 15143-3, addresses the other big limit of OEM feeds: freshness. Hitachi says owners can get operational data every 60 minutes or every 10 minutes instead of the conventional once-a-day communication. It adds that some service options include a paid service, and that customers should contact their Hitachi dealer to learn which models, data elements and regions are covered.
That matters because update speed varies widely across brands. EquipmentShare's T3, for example, documents OEM feeds it supports refreshing anywhere from every 15 minutes to once a day, with its Hitachi connection updating hourly.
The common thread
Bobcat and Hitachi illustrate the two questions every OEM feed raises: which data you are allowed to see, and how current it is. Both answers depend on subscription tier, machine model and region, and they differ from one manufacturer to the next. The AEMP standard settled the format. Access and speed are still decided brand by brand, and in Europe increasingly by regulators.
When third-party telematics is the better call
For many fleets, OEM data through a mixed-fleet platform is the cheapest place to start: no extra hardware, no installation and no downtime. But there are clear cases where fitting an independent, third-party telematics device gives better and more consistent data:
- Freshness matters. Dispatch, theft response, geofence alerts and same-day redeployment need location and engine status within minutes, not hours. Aftermarket trackers can report on their own schedule rather than the OEM's.
- Consistency across brands. One device type across every machine gives the same data points, at the same interval, in the same format, instead of a patchwork of OEM tiers.
- Data behind a paywall. If fault codes or idle hours require a premium OEM subscription on each machine, a third-party device that reads engine data directly may cost less across a large fleet.
- Older, unsupported or unpowered assets. Machines without factory telematics, brands without an API, and trailers, generators and attachments can only be tracked with added hardware.
- Features the OEM does not offer. Operator ID and access control, cameras and sensor inputs typically come from the telematics provider, not the machine.
The trade-offs are real: hardware and installation costs, another subscription, and the risk of paying twice for data the OEM already provides. Some manufacturer-specific diagnostics may also only be available through the OEM. Many fleets end up with a hybrid: OEM feeds where they are fast and complete enough, and third-party devices where the operation needs better data than the factory feed provides.
Sources
Get the week’s connected-operations news in one email.
Free. One email a week. Unsubscribe any time.
