ISO 15143-3 and AEMP 2.0, explained for fleet managers

Many heavy machines built in recent years left the factory with a telematics modem already inside. Each manufacturer sends that data to its own portal, with its own login, its own screens and its own idea of what an hour is. A fleet with three brands ends up with three portals and no single answer.

ISO 15143-3, still widely called AEMP 2.0, is the standard way to get that data out of each portal and into one place. Here is what it covers, how to get a feed turned on, and where it falls short.

What the standard actually says

ISO/TS 15143-3 specifies a web-service schema for sending machine status data, such as location and operating hours, from a telematics provider’s server to third-party applications, for earth-moving and mobile road construction machinery. It grew out of the telematics standard written by the Association of Equipment Management Professionals (AEMP), which is why the old name stuck.

Two things follow from that definition. First, it is server to server. The machine still talks to its manufacturer’s cloud over its own modem; the standard governs the next hop, from that cloud to your fleet system. Second, it defines the format and the request, not the business terms. Whether the feed is switched on, what it costs and how often it refreshes are up to each manufacturer.

What a feed carries

The standard defines a set of fields. Not every machine reports every field, and older models often report only a few. The ones fleet managers use most:

Field	What you use it for
Location and time of fix	The map, geofences, which job the machine is on
Cumulative operating hours	Service intervals, utilization, billing hours to jobs
Cumulative idle hours	Idle share and working utilization
Fuel used	Fuel per hour, fuel per job, emissions reporting
Fuel and DEF remaining	Routing the fuel truck before a machine runs dry
Distance	Machines that travel, such as articulated trucks and graders
Engine status	After-hours running and movement checks
Fault or caution codes	Triage and work orders
Load counts and payload	Haul trucks and loaders with onboard weighing

Some machines also report hours of power take-off use or active DPF regeneration. Ask for a sample response per model rather than assuming a field is there.

How the data moves

Your fleet system pulls the data; the manufacturer does not push it. On a schedule, your system calls the manufacturer’s web service with credentials tied to your account. A snapshot request returns the latest value of each field for every machine on the account. History requests return values for one machine over a time window.

The manufacturer’s server updates its own copy on its own schedule. What you receive can be an hour old or older, depending on the brand and the subscription. That is fine for service intervals, utilization and job costing. It is not fine for a theft alert at 2 a.m. on a remote job.

Timestamps often arrive in UTC, units vary (liters or gallons, hours to one decimal or whole hours), and large fleets come back in pages. A good integration handles all of that before anyone sees a number.

Getting a feed turned on

Work through this list once per manufacturer in your fleet. It usually takes a few emails and one patient phone call.

1. List every machine with its serial number (PIN), model and year, so you can check the feed against it.
2. Find who owns the portal account. Dealers often set up the account at delivery. Confirm it is in your company’s name, not the dealer’s or a former employee’s.
3. Confirm the subscription level. Some manufacturers include feed access with basic telematics; others require a paid tier. Ask directly.
4. Request API credentials for a service account, not a person’s login. When that person leaves, the feed should not leave with them.
5. Compare the machine list in the feed against your own. Missing serials usually mean a lapsed subscription or a machine registered to another account.
6. Pull a test snapshot and check hours on three machines against the hour meter in the cab.
7. Record renewal dates. A lapsed subscription does not raise an error; the feed simply goes quiet.
8. Plan for disposals. When you sell a machine, remove it from the account so the buyer’s hours do not land in your reports.

The gaps to plan around

Practitioners joke that it is a standard that is not quite standard. The schema is shared; the behavior behind it is not. Plan for these:

• Refresh lag. Data arrives when the manufacturer’s server updates, not when the machine reports.
• Different hour definitions. One brand reports engine-running hours, another reports key-on time. Know which one each feed sends before you compare machines.
• Fault codes in house formats. Some feeds send J1939 SPN and FMI pairs; others send the manufacturer’s own codes with its own descriptions. Our guide to reading J1939 fault codes covers the standard format.
• Fields that vary by model and year. A newer excavator may send fuel and DEF; the older one beside it sends location and hours only.
• Silent lapses. No data looks the same whether the machine is parked, broken or unsubscribed.
• Machines with no factory telematics. Older iron, compact equipment, light towers and trailers have nothing to pull.
• Rentals. You rarely get access to a rental company’s feed for its machines.

Example: three brands, one hour count

Say a contractor runs three 20-ton excavators from three manufacturers on the same job, same 10-hour shifts, for one week. The numbers are round and for illustration:

• Excavator 1 reports through its feed as engine-running hours: 48.0 for the week.
• Excavator 2 reports through its feed as key-on hours: 53.5, because the key stays on during walkarounds and lunch.
• Excavator 3 has no feed, so a gateway reads engine hours from the controller: 47.5.

Compared raw, excavator 2 looks like the busiest machine on the job. It is not. Scheduled raw, it also reaches its 500-hour service after roughly 450 real engine hours, because 53.5 ÷ 48 is about 1.11. Neither error is dramatic in one week. Over a year and 40 machines, they decide which excavator you sell and when the shop orders filters.

The fix is dull and effective: record the hour definition for each feed, check it against the cab meter that the service manual’s intervals are written against, and convert before anyone compares machines.

When to add hardware anyway

A feed is the cheapest way to connect a machine. Use these rules to decide when it is enough.

• Feed sends location, hours and fault codes: use the feed, no hardware needed.
• Feed lacks fault codes or refreshes too slowly for theft alerts on a remote job: add a gateway that reads the engine directly.
• No factory telematics: fit a gateway. Gytix’s A1 reads J1939 engine data and GPS and stores 30 days of data when out of coverage.
• Unpowered assets: a battery tracker on trailers, light towers and generators.
• No cellular coverage at all: a satellite-capable gateway, such as the A1S, which sends position, hours and active fault codes every 15 minutes.

Expect a mixed fleet to end up with both. Picture an 80-machine fleet where 35 newer machines connect by feed and 45 older or smaller units get gateways. Both groups land in the same list, with the same fields.

Who controls the data

The feed reads data about your machines through your account, under the manufacturer’s terms of service. Read those terms once, especially the parts about who else can see the data and what happens when a subscription ends. Then make sure your fleet system keeps its own history, so a lapsed subscription or a portal change does not erase two years of hours you need for a warranty claim or a resale.

Questions to ask any fleet system

Before you hand over credentials, ask:

• Which manufacturers’ feeds have you connected, and who builds a new one if mine is missing?
• Do you convert hours, units and fault codes into one format across brands?
• How do you show me that a feed has gone quiet?
• Do I keep my manufacturer subscription and my own credentials?
• Can I export the combined data at any time, including after I cancel?

The answers tell you whether the system treats feeds as a checkbox or as the core of a mixed fleet.

Where Gytix fits

Mixed-fleet telematics pulls ISO 15143-3 feeds from each manufacturer in your fleet and puts them beside Gytix gateways and older trackers, with the same fields and a clear source for every reading. Machines that already report through a manufacturer feed connect with no Gytix hardware, and it is included from the Field plan up.

During onboarding we build any connector you are missing and check each feed against your machine list. It sits inside machinery tracking, and if the acronyms pile up, the heavy equipment telematics glossary defines AEMP 2.0, J1939, SPN, FMI and the rest in plain terms.