Driving behaviour event

Driving behaviour event is one of Demiton's published registers for Australian civil construction. Harsh braking, acceleration and cornering events from telematics. 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

driving_behaviour_eventUse 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.

Download JSON SchemaSee an example record

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)Australia · GDA2020 = ITRF2014 at epoch 2020.0 · public summary
• Privacy Act 1988Privacy Act 1988 - Australian Privacy PrinciplesAustralia · APP Guidelines ch 3 v1.2 (2026-05-13) · clause APP 3 · verified against full text
• Workplace Surveillance Act 2005 (NSW)Workplace Surveillance Act 2005 (tracking surveillance of employees)Australia · in force (compilation 2025-06-14) · clause s 10 · public summary
• GDPRGeneral Data Protection Regulation (GDPR)European Union · 2016 · public summary
• ISO 55001Asset management - Asset management system - RequirementsInternational · 2024 (AS ISO 55001:2024 identical AU adoption) · paywalled, from a secondary description
• ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)International · 2020 (SA TS ISO 15143.3:2021 AU and PD ISO/TS 15143-3:2020 UK identical adoptions) · paywalled, from a secondary description
• RFC 7946The GeoJSON Format (IETF Proposed Standard)International · August 2016 · verified against full text
• ICO monitoring workers guidanceICO Employment practices and data protection: monitoring workersUnited Kingdom · current guidance (under review after the Data (Use and Access) Act) · verified against full text
• UK GDPRUK GDPR and Data Protection Act 2018United Kingdom · as amended · public summary
• 49 CFR Part 395 Subpart BFMCSA - Hours of Service of Drivers - Electronic Logging DevicesUnited States · current (ELD mandate from 2017-12-18) · clause s 395.26 · verified against full text

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Navman

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
• GeotabPartial

Fields

13 fields: 6 required, 7 optional.

Required

Every record carries these fields.

assetText

The vehicle the event was recorded against.

Example: 9301

categoryText

Which kind of event it is: harsh braking or harsh acceleration.

Example: harsh_braking

external_idText

The source's own event identifier (id)

Example: nav-evt-88104

occurred_atDate and timeISO 8601, with time zone

When the harsh braking/acceleration event occurred.

Example: 2026-07-22T07:41:12+10:00

acceleration_gDecimal numberUnit: g

Peak acceleration of an EA event, magnitude, INSTANTANEOUS.

Example: 0.05

deceleration_gDecimal numberUnit: g

Peak deceleration of an HB event, magnitude, INSTANTANEOUS (never summed)

Example: 0.48

Optional

Present when the source system records them.

gpsGroup of fieldsUnit: — (datum, CRS and precision unverified)

The position carried on the event, and by the declared producer edge the geographic area it is attributed to.

deviceNumber

The telematics device that recorded the event.

Example: 771001

driverNumber

The operator attributed to the event.

Example: 5502

duration_sDecimal numberUnit: s

How long the event lasted (attributes.duration)

Example: 1.8

raw_attributesGroup of fields

The untouched source event payload, including the per-second acceleration/GPS trace the resource description promises.

acceleration_threshold_gDecimal numberUnit: g

The EA threshold the event exceeded (maxAccelerationThrsh)

Example: 0.35

deceleration_threshold_gDecimal numberUnit: g

The HB threshold the event exceeded (minDecelerationThrsh)

Example: 0.4

Filed against

Records are indexed along these dimensions, so they can be asked for by any of them.

• 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.

driving_behaviour_event.example.json

{
  "acceleration_g": 0.05,
  "acceleration_threshold_g": 0.35,
  "asset": "9301",
  "category": "harsh_braking",
  "deceleration_g": 0.48,
  "deceleration_threshold_g": 0.4,
  "device": 771001,
  "driver": 5502,
  "duration_s": 1.8,
  "external_id": "nav-evt-88104",
  "gps": {
    "lat": -25.5326,
    "lon": 152.7011
  },
  "occurred_at": "2026-07-22T07:41:12+10:00",
  "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.

Schema URL

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

Show the full JSON Schema

Loading the schema…