Asset utilisation

Engine hours and utilisation for plant and equipment.

Part of Assets in the register catalog.

Register ID: asset_utilisationUse this name to ask for the register. The API calls it a shelf ID.
Each record is: An eventSomething that happened at a point in time.
Status: AvailableFilled today from connected systems, uploads or public data.
Data: OrganisationPrivate to each organisation's own workspace.
Version: v1Current version.

Download JSON Schema See an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

EROADPartial
Geotab
MapTrackPartial
Procore
Sitemate

Fields

19 fields: 5 required, 14 optional.

Required

Every record carries these fields.

assetText

The machine the reading belongs to.

Example: Grader 140M #1

occurred_atDate and timeISO 8601, with time zone

The timestamp of the reading snapshot.

Example: 2026-08-14T06:30:00Z

source_systemText

Which bound system emitted the row.

Example: NAVMAN

engine_hoursDecimal numberUnit: hours

Lifetime GPS engine-hours meter, CUMULATIVE (never summed)

Example: 4820.5

odometerDecimal numberUnit: km

Lifetime GPS odometer, CUMULATIVE.

Example: 138452.2

Optional

Present when the source system records them.

fuelNumberUnit: pct

CAN-bus tank-level reading, INSTANTANEOUS (never summed)

Example: 78.5

engine_hours_canDecimal numberUnit: hours

CAN-bus lifetime engine-hours twin, CUMULATIVE.

odometer_canDecimal numberUnit: km

CAN-bus lifetime odometer twin, CUMULATIVE.

engine_hours_periodDecimal numberUnit: hours

Engine-hours delta over the reading window, ADDITIVE.

Example: 8.5

distance_periodDecimal numberUnit: km

Distance delta over the reading window, ADDITIVE.

Example: 42.3

fuel_periodDecimal numberUnit: litres

Fuel consumed over the reading window, ADDITIVE.

projectText

The project the asset was working on.

Example: BWG-2025-001

financial_periodText

The period the reading is attributed to.

Example: 2026-08

locationText

Last known position/place as delivered by the source; datum and unit unverified

deviceNumber

The telematics device that produced the reading.

operatorNumber

The operator/driver attributed at reading time.

Example: 5501

source_unitsGroup of fields

The source unit each measure arrived in, beside the canonical unit.

energy_usedDecimal numberUnit: kWh (unverified)

Cumulative energy counter; meaning and unit not documented in any digest read.

rangeDecimal numberUnit: km (unverified)

Cumulative/remaining range counter; meaning and unit not documented.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

{
  "asset": "Grader 140M #1",
  "distance_period": 42.3,
  "engine_hours": 4820.5,
  "engine_hours_period": 8.5,
  "financial_period": "2026-08",
  "fuel": 78.5,
  "occurred_at": "2026-08-14T06:30:00Z",
  "odometer": 138452.2,
  "operator": 5501,
  "project": "BWG-2025-001",
  "source_system": "NAVMAN"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

https://docs.demiton.io/registers/asset_utilisation/v1.json

Show the full JSON Schema

Loading the schema…

Talk to the team

Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.

Book a 30-minute call Start free