Mixed-fleet reality: ISO 15143-3 (AEMP) — what it solves (and what it doesn’t)

Purpose: Mixed fleets are normal now: multiple OEMs, a few generations of machines, plus some aftermarket trackers. ISO 15143-3 (often called “AEMP 2.0”) is one of the main standards used to exchange machine status data from telematics providers to customer applications. This article explains what that actually helps with—and the common expectations it will not meet.

On FMA, this topic sits under Implementation Reality and Data Portability, because standards can reduce integration effort, but they don’t eliminate it. Treat ISO 15143-3 as a useful baseline when comparing vendors—especially for construction mixed-OEM use cases.

What is ISO 15143-3 in plain language?

ISO 15143-3 is a standard for exchanging a defined set of machine status information over the internet from a telematics system (or OEM backend) to a customer application. In mixed fleets, the goal is straightforward: reduce the “N different data formats” problem so a buyer can combine baseline status data across multiple OEMs and sources.

In practice, it’s most relevant when you need consistent cross-fleet visibility for metrics like basic operating status, locations, and operating hours—without rebuilding a custom connector for each OEM.

Why mixed fleets create integration pain (real life)

Mixed fleets create predictable friction because each data source tends to have its own:

  • Data definitions: what “hours” means, how idling is counted, what “engine on” implies
  • Identifiers: equipment IDs and asset naming conventions that don’t match across systems
  • Sampling: location update rates, event triggers, retention windows
  • Access patterns: API availability, export formats, onboarding steps, permissions

Standards like ISO 15143-3 can help by narrowing variability for a baseline data set—but the “implementation reality” still matters.

What ISO 15143-3 typically solves

Think of ISO 15143-3 as a way to standardize a common vocabulary for machine status data exchange.

Problem in mixed fleetsWhat the standard helps withWhat changes for the buyer
Different OEM data formatsDefines a common structure for a baseline set of machine status parametersLess custom mapping work to get a cross-OEM “status dashboard” running
Hard to unify basic visibilityProvides a consistent framework to request/receive certain data fieldsFaster time-to-first mixed-fleet view (location/hours/status baseline)
Repeated integrations for every OEMReduces connector diversity when supported across sourcesLower integration cost for the baseline layer (not always for advanced workflows)

What it does not solve (common misunderstandings)

ISO 15143-3 is useful, but it’s not a magic “everything becomes comparable” switch. These are the common gaps buyers hit:

1) It doesn’t guarantee deep diagnostics or every OEM-specific signal

Many of the most valuable signals (advanced diagnostics, proprietary health indicators, specialized work-mode analytics) remain OEM- or vendor-specific. Even when a standard exists, vendors can differ in what they expose and under what terms.

2) It doesn’t standardize your workflow

The standard is about data exchange. Your workflows—maintenance planning, inspections, job costing, dispatch—still depend on your tools and how well the platform supports them.

3) It doesn’t remove onboarding and credential friction

Even with a standard, you typically still deal with onboarding steps (permissions, account linkage, “who owns the telematics subscription,” etc.). “Supported” can still mean “supported with conditions.”

4) It doesn’t make utilization definitions identical

Utilization is a definition problem as much as a data problem. A mixed-fleet dashboard can still be misleading if different sources interpret “idle,” “operating,” or “engine on” differently.

Real-life use cases (where the standard helps)

These are common mixed-fleet scenarios where ISO 15143-3 support can reduce implementation effort.

Use case 1: Multi-OEM contractor needs a single baseline dashboard

Situation: A contractor runs multiple OEMs across jobsites and wants a unified view of location + basic operating status + hours to support site-level allocation decisions.

Where ISO 15143-3 helps: It can reduce data normalization work for the baseline layer—enough to power a consistent “fleet status” view across OEM sources.

Use case 2: Rental company needs cross-OEM status for off-rent control

Situation: A rental fleet wants to detect assets that are off-rent but moving, or assets that are missing location updates for long periods.

Where ISO 15143-3 helps: Standardized status/location fields can support consistent exception reporting across OEMs—assuming the vendors actually expose the needed fields and update frequency is acceptable.

Use case 3: Enterprise wants a data lake feed (BI layer)

Situation: A group wants to ingest telematics data into a BI layer to measure utilization, downtime, and fleet availability across business units.

Where ISO 15143-3 helps: It can provide a consistent baseline schema for ingestion—helpful when you’re building one pipeline to serve multiple dashboards.

How to evaluate “ISO 15143-3 support” on vendor profiles

On FMA, treat “supports ISO 15143-3” as a claim that needs evidence. Here’s how to validate it consistently:

  • Ask for documentation evidence: link to docs or an integration guide, not just a brochure.
  • Confirm scope: which data domains/fields are actually provided (location, hours, status, events, etc.).
  • Confirm access reality: is it customer-accessible or partner-only? Is it a paid tier?
  • Confirm retention + refresh: how far back can you retrieve, and how often does it update?
  • Confirm identifier consistency: stable asset identifiers across sources and over time.

This evaluation approach fits the FMA principle: consistent definitions + evidence links + explicit uncertainty when the documentation isn’t clear.

Mini RFP questions that expose mixed-fleet reality

These questions force concrete answers (links, scope, limitations):

  • Do you support ISO 15143-3 for mixed-fleet status exchange? Provide documentation links.
  • Which data domains/fields are included in your ISO 15143-3 coverage?
  • What onboarding steps and permissions are required to activate mixed-fleet data feeds?
  • What are the refresh frequency and historical retention windows?
  • Which signals are excluded (e.g., deeper diagnostics) and what alternatives exist (API/export, OEM tools)?

References

Confidence level: 0.79