EROAD & 3PM Field-Level Mapping

EROAD & 3PM Field-Level Mapping

Purpose

This article shows exactly which EROAD fields populate each 3PM asset field.

Fields

Asset Registry Information
  1. IOT ID ← id (IOTID)
  2. Asset Code ← assetCode
Asset Information
  1. Registration Number ← registrationPlate
  2. Make ← make
  3. Model ← model
  4. VIN ← vin
  5. Year of Manufacture ← year
Telemetry
  1. Current Odo ← odometer
  2. Current Hubo ← huboSerialNumber
  3. Current Hours ← engineHours
Location & Time
  1. Last Online ← gpsFix.timestamp
  2. Location (coords/readable) ← readableLocation
Compliance Information
  1. Subject to RUC ← rucVehicleStatus

Data Precedence (IoT Overrides)

  1. For all mapped fields listed above, the IoT provider is the source of truth.
  1. On each sync, if the provider value is non-empty, 3PM updates/overwrites the 3PM value (even if you edited it manually in 3PM).
  1. If the provider value is empty or null (or that field isn’t supplied), 3PM keeps the existing 3PM value.

Example:
If Make in 3PM is “NISSAN” and EROAD reports “ISUZU”, the next sync will change Make to “ISUZU”. If EROAD sends blank, 3PM keeps “NISSAN”.

Note: Manual edits to mapped fields may be overwritten on the next IoT sync.