Equipment transfer

Equipment transfer is one of Demiton's published registers for Australian civil construction. Plant and equipment moves between sites. 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

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

• ISO 55001Asset management - Asset management system - RequirementsInternational · 2024 (AS ISO 55001:2024 identical AU adoption) · clause 8.1 · paywalled, from a secondary description
• ISO/TS 55010Asset management - Guidance on the alignment of financial and non-financial functionsInternational · 2024 (2019 edition withdrawn 2025-04-09) · clause Annex I · paywalled, from a secondary description

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Hilti ON!Track

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
• HammerTechPartial
• Procore
• SitematePartial

Fields

11 fields: 5 required, 6 optional.

Required

Every record carries these fields.

assetText

The machine or tool that moved.

Example: 9301

external_idText

The transfer line's dedup key.

Example: ET-2026-0210

occurred_atDate and timeISO 8601, with time zone

When the transfer happened.

Example: 2026-07-20T05:30:00Z

to_locationNumber

The location the asset arrived at.

Example: 8102

from_locationNumber

The location the asset left.

Example: 8101

Optional

Present when the source system records them.

projectText

The project the transfer is attributed to.

Example: BWG-2025-002

to_workerNumber

The worker who received custody.

Example: 5503

from_workerNumber

The worker who held the asset before.

Example: 5501

financial_periodText

The accounting period the movement is attributed to.

Example: 2026-07

to_storage_assetNumber

The storage unit / container the asset arrived in.

from_storage_assetNumber

The storage unit / container the asset left.

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.

equipment_transfer.example.json

{
  "asset": "9301",
  "external_id": "ET-2026-0210",
  "financial_period": "2026-07",
  "from_location": 8101,
  "from_worker": 5501,
  "occurred_at": "2026-07-20T05:30:00Z",
  "project": "BWG-2025-002",
  "source_system": "ASSIGNAR",
  "to_location": 8102,
  "to_worker": 5503
}

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/equipment_transfer/v1.json

Show the full JSON Schema

Loading the schema…