Plant snapshot

Plant snapshot is one of Demiton's published registers for Australian civil construction. The plant register at a project location at a point in time. 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

plant_snapshotUse 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

DeclaredDefined, and fills when a source produces its first record.

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 7.6; 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.

No system fills this register yet.

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
• HammerTech
• Mitti

Fields

16 fields: 5 required, 11 optional.

Required

Every record carries these fields.

assetsList

The register rows behind the count. Must be a structured attribute, not a measure.

projectText

The project the register snapshot is taken at; the fact's subject anchor.

Example: BWG-2025-003

asset_countWhole numberUnit: dimensionless (count)

Number of plant assets at the project at snapshot time.

Example: 2

external_idText

The fact's supersede key; today plant:{job_no}, i.e. one current snapshot per project.

Example: plant-snapshot-8103-20260831

occurred_atDate and timeISO 8601, with time zone

The instant the snapshot was taken (the writer uses date.today(), :623).

Example: 2026-08-31T23:59:00Z

Optional

Present when the source system records them.

assets[].nameText

Display name of the plant item.

Example: CAT 140 Grader

assets[].modelText

Model of the plant item.

Example: 140M3

assets[].statusText

The asset's status in the source register (available / in use / etc.).

Example: On site

legal_entity_idText

Legal-entity context coordinate.

assets[].scan_codeText

Barcode / QR scan code, the value field crews scan.

Example: BWG-AST-9302

assets[].asset_typeText

The plant class/category (excavator, EWP, crane, …).

Example: Grader

assets[].location_idText

The source location the asset sat at when the snapshot was taken (the Hilti locationId the fetch was filtered by).

Example: 8103

assets[].manufacturerText

Manufacturer / make.

Example: Caterpillar

assets[].serial_numberText

The manufacturer's serial number.

Example: CAT140M3-88291

assets[].source_asset_idText

The source system's own asset identifier (Hilti id, falling back to externalId) so a snapshot row can join the equipment_list register.

Example: 9302

assets[].responsible_employee_idText

The custody holder in the source register.

Example: 5502

Filed against

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

• Legal entitycontext for the record, from When known
• Projectwhat the record is about, from Always set

Example record

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

plant_snapshot.example.json

{
  "asset_count": 2,
  "assets": [
    {
      "asset_type": "Grader",
      "location_id": "8103",
      "manufacturer": "Caterpillar",
      "model": "140M3",
      "name": "CAT 140 Grader",
      "responsible_employee_id": "5502",
      "scan_code": "BWG-AST-9302",
      "serial_number": "CAT140M3-88291",
      "source_asset_id": "9302",
      "status": "On site"
    },
    {
      "asset_type": "Road Roller",
      "location_id": "8103",
      "manufacturer": "Bomag",
      "model": "BW213",
      "name": "Bomag Roller",
      "responsible_employee_id": "5504",
      "scan_code": "BWG-AST-9303",
      "serial_number": "BW213-40217",
      "source_asset_id": "9303",
      "status": "On site"
    }
  ],
  "external_id": "plant-snapshot-8103-20260831",
  "occurred_at": "2026-08-31T23:59:00Z",
  "project": "BWG-2025-003",
  "source_system": "ASSIGNAR"
}

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

Show the full JSON Schema

Loading the schema…