How it connects
AEMP 2.0, standardised as ISO 15143-3, is the manufacturers' common telematics interface. Renttix implements it once as a generic provider: OAuth2 client credentials obtain a token, and a paged fleet snapshot returns the readings. The manufacturers differ only in their endpoint URLs, which your OEM provisions for your account. That means adding a second or third manufacturer is a configuration exercise, not an integration project. You enter the credentials and endpoint your OEM gave you, and their machines report alongside everything else.
Why it matters
Almost no hire fleet is single-manufacturer. A yard typically runs machines from several OEMs, each with its own telematics portal, its own login and its own way of presenting hours. The data exists several times over, and precisely because it is fragmented, nobody uses it. The standard exists to solve exactly this. Rather than integrating each manufacturer's proprietary platform — a project per OEM, repeated whenever you buy a different brand — one standard interface serves all of them. For a rental business, that is the difference between telematics being a fleet-wide capability and being something that works for whichever brand someone once set up.
Key workflows
Mixed fleets in one place
Machines from different manufacturers report through the same standard interface, so a yard running several brands sees one set of asset records instead of several OEM portals.
Add an OEM by configuration
Because the standard is implemented once, connecting an additional manufacturer means entering the credentials and endpoint they provision — not commissioning another integration.
Hours that drive servicing and billing
Readings land on the asset record and feed service intervals, utilisation reporting and usage-based charges, the same as any other telematics source.
The AEMP provider sits alongside the Samsara and Trackunit integrations in Renttix. Aftermarket trackers and OEM telematics can run together across one fleet, with every reading landing on the same asset record and carrying the provider it came from.
AEMP telematics FAQ
Any OEM that publishes the ISO 15143-3 (AEMP 2.0) interface — in practice that includes JCB LiveLink, Cat, John Deere, Bobcat and Komatsu. They differ only in endpoint URL, which your OEM provisions for your account.
No. That is the point of the standard. Renttix implements it once, so adding a manufacturer is a matter of entering the credentials and endpoint they give you.
Yes. AEMP, Samsara and Trackunit can all be in use across one fleet. Every reading lands on the same asset record and records which provider supplied it.
Ready to modernize your rental operations?
Payments + deposits enabled • Quick setup • No credit card trial