Asset utilisation
Asset utilisation is one of Demiton's published registers for Australian civil construction. Engine hours and utilisation for plant and equipment. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
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
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- GDA2020 / MGA2020Geocentric Datum of Australia 2020 and Map Grid of Australia 2020 (EPSG:7844 / EPSG:78xx zones)
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- Workplace Surveillance Act 2005 (NSW)Workplace Surveillance Act 2005 (tracking surveillance of employees)
- GDPRGeneral Data Protection Regulation (GDPR)
- ISO 55001Asset management - Asset management system - Requirements
- ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)
- WGS 84 (EPSG:4326)World Geodetic System 1984 datum ensemble (EPSG:6326)
- 49 CFR Part 395 Subpart BFMCSA - Hours of Service of Drivers - Electronic Logging Devices
Connectors
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
18 fields: 4 required, 14 optional.
Required
Every record carries these fields.
- assetText
The machine the reading belongs to.
Example:
Grader 140M #1- odometerDecimal number
Lifetime GPS odometer, CUMULATIVE.
Example:
138452.2- occurred_atDate and time
The timestamp of the reading snapshot.
Example:
2026-08-14T06:30:00Z- engine_hoursDecimal number
Lifetime GPS engine-hours meter, CUMULATIVE (never summed)
Example:
4820.5
Optional
Present when the source system records them.
- fuelNumber
CAN-bus tank-level reading, INSTANTANEOUS (never summed)
Example:
78.5- rangeDecimal number
Cumulative/remaining range counter; meaning and unit not documented.
- deviceNumber
The telematics device that produced the reading.
- projectText
The project the asset was working on.
Example:
BWG-2025-001- locationText
Last known position/place as delivered by the source; datum and unit unverified
- operatorNumber
The operator/driver attributed at reading time.
Example:
5501- energy_usedDecimal number
Cumulative energy counter; meaning and unit not documented in any digest read.
- fuel_periodDecimal number
Fuel consumed over the reading window, ADDITIVE.
- odometer_canDecimal number
CAN-bus lifetime odometer twin, CUMULATIVE.
- source_unitsGroup of fields
The source unit each measure arrived in, beside the canonical unit.
- distance_periodDecimal number
Distance delta over the reading window, ADDITIVE.
Example:
42.3- engine_hours_canDecimal number
CAN-bus lifetime engine-hours twin, CUMULATIVE.
- financial_periodText
The period the reading is attributed to.
Example:
2026-08- engine_hours_periodDecimal number
Engine-hours delta over the reading window, ADDITIVE.
Example:
8.5
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Projectwhat the record is about, from
When known - Assetwhat the record is about, from
Always set - Financial periodcontext for the record, from
When known
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.jsonShow 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 fill from them, on your data, in a 30-minute call.