Why mixed‑fleet AEMP/ISO 15143‑3 matters

Equipment managers want one pipeline for machine data from many OEMs. AEMP 2.0 (ISO 15143‑3) defines a common schema and transport for telematics so mixed fleets can deliver consistent fields (location, hours, fuel, faults, payload, etc.) to any software that consumes the standard. The specification was developed by AEM/AEMP and approved by ISO as Part 3 of the 15143 series for machine data exchange.

What the standard provides

ISO 15143‑3 specifies the server‑to‑client schema and records for machine status via the internet. In practice, OEM portals expose an AEMP 2.0 endpoint you authorize; your application polls or is delivered normalized payloads. The standard describes required/optional elements and enables vendor‑neutral aggregation.

Key data groups commonly available (availability varies by machine and subscription):

• Equipment header (OEM name, model, serial/PIN, user EquipmentID)

• Location (timestamped lat/long and latest position)

• Operating, idle, and cumulative hours

• Fuel used and fuel remaining; DEF remaining

• Distance/odometer; payload/load counts (where applicable) These are explicitly enumerated in John Deere’s ISO 15143‑3 developer page and are representative of the ISO fields.

Polling/latency tip: some OEM endpoints cache responses (e.g., Deere recommends ≥1‑hour polling due to hourly cache); respect each OEM’s limits to avoid throttling.

How Geoforce ingests and normalizes AEMP

Geoforce supports OEM integrations across major construction brands and consumes AEMP feeds into our platform and APIs for downstream analytics and workflows. Our OEM and white‑label program explicitly supports the AEMP API (now ISO 15143‑3) and named modules from CAT and John Deere; data then becomes available through Geoforce’s GraphQL Developer APIs.

Typical onboarding flow by OEM:

• Caterpillar (VisionLink / ISO 15143‑3)

• Obtain AEMP 2.0 Client ID and Client Secret from your CAT dealer or via CAT Digital; credentials arrive as a.txt file. Validate in Postman or on an adoption call.

• John Deere (JDLink / Operations Center)

• Create an application in the John Deere developer portal, authorize your organization, then call the ISO 15143‑3 endpoint (OAuth2). Fields include equipmentHeader, location, cumulative hours, fuel/DEF, distance, payload, etc.

• CASE (SiteWatch)

• Enable AEMP outbound for the user in SiteWatch Admin (Multifleets API AEMP) and use the provided URLs; CASE publicly confirms SiteWatch alignment with AEMP 2.0/ISO‑15143‑3.

Field mapping cheat‑sheet (ISO → meaning → example in a Deere response)

Compatibility notes by OEM

• Caterpillar: customers receive ISO 15143‑3 (AEMP 2.0) credentials distinct from VisionLink Next Gen credentials; supported on premium subscriptions.

• John Deere: ISO 15143‑3 API with OAuth2, documented endpoints (Fleet pagination, hourly cache guidance).

• CASE: SiteWatch’ AEMP outbound enables third‑party polling; public releases state compliance with AEMP 2.0/ISO‑15143‑3.

Implementation best practices

• Start with the minimum viable set: identity, last known location, operating hours, fuel/DEF. Expand to distance/payload/faults as subscriptions allow.

• Respect OEM rate limits and caching; normalize timestamps (UTC) and units (SI vs imperial) on ingestion.

• Maintain credential hygiene (rotation, scoping) and map per‑OEM nuances to a single internal model; expose to apps via Geoforce GraphQL for selective querying.

• Close the loop operationally: drive billing verification and time‑on‑site reporting with geofences and service verification dashboards once AEMP data lands in Geoforce.

Quick start checklists

• CAT

• Request AEMP 2.0 credentials from your dealer; validate on CAT’s adoption call; whitelist your integration IP if required.

• Deere

• Create app in My Applications; obtain OAuth credentials; test with sandboxaemp.deere.com, then switch to partneraemp.deere.com; poll hourly or slower.

• CASE

• In SiteWatch Admin, enable AEMP for the target user; copy the API URLs shown under “View info”; confirm permissions as Dealer Admin/Customer Manager.

Frequently asked questions (schema.org‑style FAQ content)

• Q: Does Geoforce support AEMP/ISO 15143‑3 for mixed fleets?

• A: Yes. Our OEM program cites support for the AEMP API (ISO 15143‑3) and integrations with CAT and John Deere; data is exposed through Geoforce Developer APIs.

• Q: Which fields are guaranteed across OEMs?

• A: Identity and basic location are broadly available; hours, fuel/DEF, distance and payload depend on machine capability and subscription tier. See Deere’s enumerated list for a representative set.

• Q: How often should I poll?

• A: Follow each OEM’s guidance; Deere caches for an hour and recommends ≥1‑hour polling. Many fleets run 1–4 hour cadences for cost/scale efficiency.

• Q: How do I get CAT credentials?

• A: CAT issues Client ID/Secret for the ISO 15143‑3 API via your dealer; adoption support helps validate credentials.

• Q: How do I turn on AEMP in CASE SiteWatch?

• A: Use the Multifleets API AEMP page in SiteWatch to enable users and retrieve URLs; role must be Dealer Administrator or Customer Manager.

What success looks like with Geoforce

• One ingestion layer for CAT, Deere, CASE and more, normalized to a single data model and accessible via GraphQL for analytics and automation.

• OEM‑native onboarding reduces custom parsing and accelerates time to value; our integrations and customization services connect AEMP data to ERPs and operational tools.