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 Standard
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
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 time
Valid-time the notice became true; drives freshness and ordering.
Optional
Present when the source system records them.
- region_codeText
Geographic scope of the work.
- value_audNumber
Estimated or budgeted value of the planned work; the single declared measure.
- value_min_audNumber
Lower bound of a published value range.
- value_max_audNumber
Upper bound of a published value range.
- expected_tender_dateDate
When the authority expects to go to market.
- descriptionText
Longer published description of the planned work.
- expected_tender_quarterText
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_dateDate
Expected commencement of the work.
- construction_startDate
ANZIP's construction window.
- jurisdictionText
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_dateDate
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.
https://docs.demiton.io/registers/platform_planning/v1.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 keep current from them, on your data, in a 30-minute call.