Integration with IOT and NZTA System

Integration with IOT and NZTA System

Introduction

This article provides a step‑by‑step guide to connect an IoT provider to 3PM Construction and keep asset data in sync. You’ll also find notes on optional NZTA compliance updates and how meter readings behave for IoT‑linked vs non‑IoT assets.

Data Flow

3PM supports direct integrations with the following IoT providers:
  1. EROAD
  2. NAVMAN
  3. CARTRACK
  4. BLACKHAWK
Direction: One‑way into 3PM.
  1. IoT Providers → 3PM: asset identifiers, location, and meters
  2. NZTA → 3PM: compliance (WOF, REGO expiry)
Fields such as IOT_ID, Current_Odo, Current_Hubo, Current_Hours are updated from the IoT provider to 3PM. (Full details of the fields setup and sync provided in the individual IoT provider article).

When it flows:
  1. Automatic sync: daily at 5:00 AM (NZ time)
  2. Manual (on demand): Asset Settings → Sync From IOTHub
    1. (Runs in the background; typical duration ~5–10 minutes depending on asset volume.)
First‑time import:
  1. All provider assets are brought into 3PM during the initial sync.
  2. Categorisation:
    1. With REGO → Vehicle
    2. Without REGO → Plant
  3. You can change this anytime by editing the asset’s Asset Type.
  4. Evidence of link: The Assets report → Link column shows the connected IoT provider name for each asset.
NZTA compliance:
  1. Trigger from Assets report → NZTA Update on the selected asset.
  2. Retrieves information like WOF and REGO expiry.
  3. Per‑asset charges apply; billed on the monthly invoice.
Data Precedence (IoT Overrides)
  1. For all mapped fields listed, the IoT provider is the source of truth.
  2. On each sync, if the provider value is non-empty, 3PM updates/overwrites the 3PM value (even if you edited it manually in 3PM).
  3. If the provider value is empty or null (or that field isn’t supplied), 3PM keeps the existing 3PM value.
  4. 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”.
  5. Note: Manual edits to mapped fields may be overwritten on the next IoT sync.

Steps to Integrate an IoT Provider with 3PM

Step 1: Contact 3PM
Reach out to 3PM Support or 3PM Implementation to request the IoT provider connection. 3PM will configure provider details plus authentication/authorisation.

Step 2: Open Asset Settings
In 3PM, navigate to Asset Settings → IoTHub Settings to view your provider configuration and credential status.

Step 3: Link & Verify
Once 3PM completes setup, the connection will be linked. You can verify in Asset Settings. Linked assets will display the provider in the Link column on the Assets report.

Step 4: Initial Sync
3PM performs a one‑time initial sync to import assets from the provider into 3PM. During import:
  1. With REGO → categorised as Vehicles
  2. Without REGO → categorised as Plant
  3. You can later edit an asset to update its Asset Type if needed.
















Step 5: Ongoing Syncs
  1. Automatic daily sync runs at 5:00 AM.
  2. Manual sync (On Demand): Go to Asset Settings and click Sync From IOTHub. This typically takes ~5–10 minutes, depending on your asset volume, and runs in the background.

How to Run a Manual IoT Sync

  1. Go to Asset Settings.
  2. Click Sync From IOTHub.
  3. Continue working—sync runs in the background (allow ~5–10 minutes depending on asset count).
  4. Check the Assets report; the Link column and asset meters/locations will reflect the latest provider data after completion.

NZTA Compliance Integration

What it does: On‑demand retrieval of latest WOF and REGO expiry from NZTA for selected assets.

Setup
3PM will enable NZTA for your tenant and issue a unique Tenant ID.

Run an NZTA update

  1. Open the Assets report.
  2. Select the asset.
  3. Click NZTA Update to fetch the latest compliance information.

Billing
NZTA updates are charged per update for each asset and appear on your monthly invoice.

Setting: Asset_Config → Update_Meter_to_Asset controls when meter readings are written back for non‑IoT assets. Options:

  1. On Pre‑Start
  2. On Job Task
  3. On Log Service

IoT‑linked assets: Meter readings are only updated via the IoT provider sync; the Update_Meter_to_Asset setting does not apply to these assets.


    • Related Articles

    • EROAD & 3PM Field-Level Mapping

      Purpose This article shows exactly which EROAD fields populate each 3PM asset field. Fields Asset Registry Information IOT ID ← id (IOTID) Asset Code ← assetCode Asset Information Registration Number ← registrationPlate Make ← make Model ← model VIN ...
    • How to Setup Asset Tracking Categories

      NOTE: This is only available if you are integrated with Xero (this is setup in the Company Settings) The purpose of assigning tracking categories and options to assets is to ensure that any bills allocated to those assets are accurately reflected in ...
    • How to setup Asset Settings

      This article will explain to setup General Settings Navigate to the Web Portal and login On the left-hand main menu, select Assets->Asset Settings The Asset Spreadsheet displays the list of Assets Update Asset Class: How to Create Asset Class Update ...
    • How to Setup Project Tracking Categories

      NOTE: This is only available if you are integrated with Xero (this is setup in the Company Settings) The purpose of assigning tracking categories and options to projects is to ensure that any bills allocated to those projects are accurately reflected ...
    • How to Sync MYOB Clients and Suppliers on 3PM Construction

      Follow the steps below to Sync MYOB Clients and Suppliers on 3PM Construction Navigate to the Web Portal and login On the left-hand main menu, select Admin->Company Settings Follow the instruction to Integrate MYOB with the 3PM Construction Portal- ...