Skip to content
Demiton

Platform planning (v2)

Platform planning is one of Demiton's published registers for Australian civil construction. Forward programme and works-to-tender notices from government pipelines. 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 Platform in the register catalog.

Register ID
platform_planningUse 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
PublicShared, from public sources such as procurement portals.
Version
v2 (2.0.0)Superseded by v3.

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

  • CPRsCommonwealth Procurement RulesAustralia · 17 November 2025 · public summary
  • EU 2019/1780 (eForms)Commission Implementing Regulation (EU) 2019/1780 standard forms for procurement notices, as amended by (EU) 2023/2884European Union · 2019/1780 as amended by 2023/2884 (applies 1 Jun 2024; Annex 1 Nov 2024) · clause Planning form · verified against full text
  • OC4IDSOpen Contracting for Infrastructure Data StandardInternational · 0.9.5 (site switcher shows 0.9.4; unresolved) · clause project identification/preparation phases; budget · verified against full text
  • OCDSOpen Contracting Data StandardInternational · 1.1 (documentation release 1.1.5) · clause release ocid, id, date, tag, initiationType; planning block (optional) · verified against full text
  • NZ GPRNew Zealand Government Procurement RulesNew Zealand · 5th edition (effective 1 Dec 2025) · public summary
  • UK Procurement Act 2023Procurement Act 2023 (c. 54) and Procurement Regulations 2024 (SI 2024/692)United Kingdom · in force 24 Feb 2025 · clause s. 93; SI 2024/692 reg. 15 · verified against full text

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.

None planned yet.

Fields

29 fields: 10 required, 19 optional.

Required

Every record carries these fields.

ocidText

The source record's own natural key; provenance and the release identity across harvests.

stageText

Source-stage label; always the planning stage for this shelf.

titleText

Human-readable name of the planned work.

agency_idWhole number

Resolved platform entity for the agency.

source_idText

Source-native record id; idempotency key with source_dataset.

project_idWhole number

Resolved civil-project roll-up; the primary lifecycle tracking axis.

shelf_typeText

platform_planning — the stage discriminator.

agency_nameText

Buying agency / proponent name as published.

occurred_atDate and timeISO 8601, with time zone

Valid-time the notice became true; drives freshness and ordering.

source_datasetText

Producer identity (the harvested system, lowercased).

Optional

Present when the source system records them.

urlText

Canonical source link for citation.

subtypeText

Distinguishes AER's 5-year regulatory capex envelopes from project-level notices.

value_audNumberUnit: AUD

Estimated or budgeted value of the planned work; the single declared measure.

descriptionText

Longer published description of the planned work.

region_codejurisdictionUnit: AU/NZ state code or AU

Geographic scope of the work.

jurisdictionjurisdictionUnit: ISO 3166-1 alpha-2 or AU state code

Jurisdiction the notice is published for.

network_nameText

AER regulatory-period envelope attributes.

category_nameText

Sector / category / classification of the work.

value_max_audNumberUnit: AUD

Upper bound of a published value range.

value_min_audNumberUnit: AUD

Lower bound of a published value range.

delivery_modelText

Published delivery/contract model.

financial_yearText

Financial year the work is planned into.

procurement_phaseText

Source's own phase label (e.g. planning vs construction).

construction_startDateYYYY-MM-DD

ANZIP's construction window.

determination_dateDateYYYY-MM-DD

Date of AER's final determination.

procurement_methodText

Published procurement method, where the source gives one.

expected_start_dateDateYYYY-MM-DD

Expected commencement of the work.

expected_tender_dateDateYYYY-MM-DDUnit: ISO 8601 date / quarter label

When the authority expects to go to market.

expected_tender_quarterTextUnit: e.g. Q1 2027-28

The quarter QLD FPP expects to go to market.

Version history

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/platform_planning/v2.json
Show 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.

Book a 30-minute callStart free