Skip to content
Demiton

Platform planning

Forward programme and works-to-tender notices from government pipelines.

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
v1Current version.

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

  • OCDSOpen Contracting Data StandardInternational

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.

source_datasetText

Producer identity (the harvested system, lowercased).

source_idText

Source-native record id; idempotency key with source_dataset.

titleText

Human-readable name of the planned work.

agency_nameText

Buying agency / proponent name as published.

agency_idWhole number

Resolved platform entity for the agency.

project_idWhole number

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

shelf_typeText

platform_planning — the stage discriminator.

stageText

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

occurred_atDate and timeISO 8601, with time zone

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

Optional

Present when the source system records them.

region_codeTextUnit: AU/NZ state code or AU

Geographic scope of the work.

value_audNumberUnit: AUD

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

value_min_audNumberUnit: AUD

Lower bound of a published value range.

value_max_audNumberUnit: AUD

Upper bound of a published value range.

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

When the authority expects to go to market.

descriptionText

Longer published description of the planned work.

expected_tender_quarterTextUnit: e.g. Q1 2027-28

The quarter QLD FPP expects to go to market.

category_nameText

Sector / category / classification of the work.

procurement_methodText

Published procurement method, where the source gives one.

procurement_phaseText

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

delivery_modelText

Published delivery/contract model.

financial_yearText

Financial year the work is planned into.

expected_start_dateDateYYYY-MM-DD

Expected commencement of the work.

construction_startDateYYYY-MM-DD

ANZIP's construction window.

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

Jurisdiction the notice is published for.

urlText

Canonical source link for citation.

subtypeText

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

network_nameText

AER regulatory-period envelope attributes.

determination_dateDateYYYY-MM-DD

Date of AER's final determination.

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/v1.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 keep current from them, on your data, in a 30-minute call.

Book a 30-minute callStart free