Komatsu KOMTRAX + DirtFleet.

KOMTRAX is Komatsu's own surface for machine performance, location, and utilization. DirtFleet handles what comes after: hour-based PM scheduling, work-order queues for the shop, repair logs, tool tracking, project P&L. The OEM data feed is the engine-hours source; the maintenance workflows live in DirtFleet.

Most heavy-iron operations that run Komatsu also run other OEMs (Caterpillar, Hitachi, John Deere on the periphery). The AEMP-generic path means one DirtFleet org can absorb telemetry from all of them simultaneously — see the field- mapping notes below.

1. Pattern 1 — KOMTRAX vehicle list via AEMP (live)

   Komatsu publishes an AEMP-compliant telematics endpoint per fleet. DirtFleet's AEMP adapter polls it on a 30-min cadence and mirrors Equipment rows as DirtFleet assets. SerialNumber → Asset.serial; that's the cross-reference key.

   When to pick this

   Standard Komatsu fleet (excavators, dozers, wheel loaders, mining trucks) where KOMTRAX is the OEM telemetry source. Connect once via /settings/integrations/aemp, paste the endpoint URL + credentials, polling starts.

   Show the setup

   # What happens on the DirtFleet side (no code on yours):
   #
   # 1. In DirtFleet:  /settings/integrations/aemp
   # 2. Add a new AEMP source — Komatsu KOMTRAX
   #      Endpoint URL: https://komtrax.komatsuamerica.com/api/aemp/...
   #      Credentials:  HTTP Basic (provided by Komatsu)
   # 3. Initial sync runs immediately — typically 1-3 min for a 30-machine
   #    fleet. Subsequent polls every 30 min.
   # 4. Each AEMP <Equipment> row becomes a DirtFleet Asset with
   #    assetClass=off-road, meterType=HOURS by default.
   #
   # What you get back per machine:
   #   SerialNumber, Make=Komatsu, Model, CumulativeHours (engine hours),
   #   Location (lat/lng), Odometer (for wheel-loaders / mining trucks).

2. Pattern 2 — Scheduled engine-hours capture (live)

   Same AEMP poll that pulls vehicle metadata also reads CumulativeHours per machine. The DirtFleet side computes the delta from the last seen reading and writes a HoursLog. Hour-based PM thresholds fire automatically on the next reading.

   When to pick this

   Once Pattern 1 is connected, you're already on Pattern 2 — the same poll handles both. No separate setup. Mechanics see new hours in the dashboard the same way they would if a driver logged manually.

   Show the setup

   # AEMP XML example (received every 30 min):
   #
   #   <Fleet>
   #     <Equipment>
   #       <SerialNumber>KMTX0123456</SerialNumber>
   #       <Make>Komatsu</Make>
   #       <Model>PC360LC-11</Model>
   #       <CumulativeHours>4,283.7</CumulativeHours>
   #       <Location>
   #         <Latitude>39.7392</Latitude>
   #         <Longitude>-104.9903</Longitude>
   #         <LocationTime>2026-05-14T12:00:00Z</LocationTime>
   #       </Location>
   #     </Equipment>
   #   </Fleet>
   #
   # DirtFleet side:
   #   - SerialNumber matched → assetId
   #   - 4283.7 > last reading? → POST HoursLog
   #   - Note: "auto-synced from Komatsu KOMTRAX"
   #   - clientMutationId: "komatsu-KMTX0123456-4284" (deduped per integer hour)
   #
   # Hour-based PM thresholds (e.g. "service every 250 hours") trigger as
   # normal once the new reading lands.

3. Pattern 3 — Dedicated KOMTRAX API (roadmap)

   Komatsu also publishes a richer non-AEMP API that surfaces utilization patterns, fuel consumption, fault codes, and operator events. The dedicated adapter would tap into those for DTC routing + fuel cost analytics in DirtFleet.

   When to pick this

   For Komatsu-heavy mining or large earthmoving operations that want fault-code routing or fuel-burn cost analytics integrated with the maintenance workflow. Roadmap; not shipped today.

   Show the setup

   # Status: Roadmap — not shipped today.
   #
   # The KOMTRAX dedicated API is a richer per-machine feed than AEMP:
   #   - Fault codes (J1939 / proprietary Komatsu codes)
   #   - Idle / working / traveling time breakdowns
   #   - Fuel consumption rate per hour
   #   - Operator events (loaded vs empty cycles for mining trucks)
   #
   # DirtFleet would route DTCs into AI-explained YELLOW flags (same
   # shape as Samsara DTC routing and the JD Service Advisor roadmap)
   # and fold fuel-cost analytics into the project P&L rollup.
   #
   # Activation: roadmap, gated on a Komatsu-heavy customer who
   # commits to using it. Email hello@dirtfleet.app to be that
   # customer.

• Bidirectional sync. KOMTRAX → DirtFleet is one-way today. Komatsu's side stays authoritative for the telematics record.
• Sub-minute location. 30-minute polling is plenty for maintenance triggers; real-time GPS stays in the KOMTRAX dashboard.
• Production / yield analytics. Loaded / empty / cycle-time data for mining trucks lives in KOMTRAX (and Komatsu's Smart Construction layer). DirtFleet doesn't double-store that — the AEMP feed gives us engine hours, which is what hour-based PM actually needs.

Mixed Komatsu + Caterpillar + John Deere fleets connect via one AEMP source per OEM in DirtFleet. The XML shape is identical; the DirtFleet adapter doesn't care which OEM is upstream. See also /integrations/john-deere-operations-center for the JD-side counterpart and /integrations/directory for the full named-vendor matrix.