Platform planning
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
- v3 (3.0.1)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- CPRsCommonwealth Procurement Rules
- EU 2019/1780 (eForms)Commission Implementing Regulation (EU) 2019/1780 standard forms for procurement notices, as amended by (EU) 2023/2884
- OC4IDSOpen Contracting for Infrastructure Data Standard
- OCDSOpen Contracting Data Standard
- NZ GPRNew Zealand Government Procurement Rules
- UK Procurement Act 2023Procurement Act 2023 (c. 54) and Procurement Regulations 2024 (SI 2024/692)
Connectors
Connected today
Demiton keeps this register current from these systems now.
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
30 fields: 10 required, 20 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 time
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.
- valueNumber
Estimated or budgeted value of the planned work; the single declared measure.
- subtypeText
Distinguishes AER's 5-year regulatory capex envelopes from project-level notices.
- currencycurrency
The currency of every amount on this record (
value,value_min,value_max), an ISO 4217 alpha-3 code as the source states it. A record with no currency has no usable amount.- value_maxNumber
Upper bound of a published value range.
- value_minNumber
Lower bound of a published value range.
- descriptionText
Longer published description of the planned work.
- region_codejurisdiction
Geographic scope of the work.
- jurisdictionjurisdiction
Jurisdiction the notice is published for.
- network_nameText
AER regulatory-period envelope attributes.
- category_nameText
Sector / category / classification of the work.
- 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_startDate
ANZIP's construction window.
- determination_dateDate
Date of AER's final determination.
- procurement_methodText
Published procurement method, where the source gives one.
- expected_start_dateDate
Expected commencement of the work.
- expected_tender_dateDate
When the authority expects to go to market.
- expected_tender_quarterText
The quarter QLD FPP expects to go to market.
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Projectwhat the record is about, from
Always set - Agencycontext for the record, from
Always set - Region codecontext for the record, from
When known
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.
https://docs.demiton.io/registers/platform_planning/v3.jsonShow 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.