Vehicle list (v1)
Vehicle list is one of Demiton's published registers for Australian civil construction. Vehicles registered in your telematics system. 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
vehicle_listUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.1)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- WHS Act and RegulationsModel Work Health and Safety Regulations (Safe Work Australia; given effect by each state/territory)
- ISO 55001Asset management - Vocabulary, overview and principles
- ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)
- ISO/TS 55010Asset management - Guidance on the alignment of financial and non-financial functions
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.
- EROAD
- Geotab
- HammerTechPartial
- MapTrackPartial
- SitematePartial
Fields
13 fields: 6 required, 7 optional.
Required
Every record carries these fields.
- vinText
Vehicle Identification Number — the chassis identifier the platform converges the asset on.
Example:
6F5CE28G1PL500123- assetText
The fleet vehicle the row is about.
Example:
Grader 140M #1- labelText
Human-readable vehicle name.
Example:
Grader 140M #1- occurred_atDate and time
The observation/harvest timestamp of the register fact.
Example:
2026-06-01T00:00:00Z- source_systemText
—.
Example:
NAVMAN- source_record_idText
The source's own primary identifier for the record.
Example:
NV-VEH-4021
Optional
Present when the source system records them.
- makeText
OEM / manufacturer.
Example:
Caterpillar- modelText
OEM model designation.
Example:
140M- fleet_groupText
Telematics fleet/group membership.
Example:
Grading Fleet- machine_typeText
plant)Example:
plant- registrationText
Registration plate.
Example:
BWG140M- year_of_manufactureWhole number
Year the vehicle was built.
Example:
2021- registration_jurisdictionText
The state/territory that issued the plate.
Example:
QLD
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", "fleet_group": "Grading Fleet", "label": "Grader 140M #1", "machine_type": "plant", "make": "Caterpillar", "model": "140M", "occurred_at": "2026-06-01T00:00:00Z", "registration": "BWG140M", "registration_jurisdiction": "QLD", "source_record_id": "NV-VEH-4021", "source_system": "NAVMAN", "vin": "6F5CE28G1PL500123", "year_of_manufacture": 2021}Version history
- v2 (current)
- v1
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/vehicle_list/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.