Traffic management plan
Traffic management plan is one of Demiton's published registers for Australian civil construction. Traffic management plans (AS 1742.3). 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 Projects in the register catalog.
- Register ID
traffic_management_planUse this name to ask for the register. The API calls it a shelf ID.- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v2 (2.0.2)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AS 1742.3:2019Manual of uniform traffic control devices - Traffic control for works on roads
- TfNSW TS 05492Traffic Control at Work Sites Technical Manual
- Traffic Signs Manual Chapter 8Traffic Signs Manual Chapter 8 - road works and temporary situations
- MUTCD Part 6Manual on Uniform Traffic Control Devices - Temporary Traffic Control
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.
None planned yet.
Fields
22 fields: 3 required, 19 optional.
Required
Every record carries these fields.
- projectText
The project the plan is for.
- plan_kindText
Whether this is a traffic management plan or a traffic guidance scheme.
- plan_referenceText
The plan's reference number.
Optional
Present when the source system records them.
- ends_onDate
When the works under the plan end.
- revisionText
The revision this row describes.
- tgs_typeText
Generic, site-suitable or site-specific, for a TGS.
- starts_onDate
When the works under the plan begin.
- approved_byText
Who approved the plan.
- approved_onDate
The date of the approver's sign-off.
- external_idText
The source's own record id.
- prepared_byText
Who designed the plan.
- speed_limitWhole number
The posted speed limit at the works.
- jurisdictionjurisdiction
The jurisdiction whose rules govern the plan.
- works_locationText
Where the works are, including the roads affected.
- client_acceptedTrue or false
Whether the client has accepted the plan.
- governing_rulesText
The rule set and edition the plan was designed to, e.g. TS 05492:1.0.
- works_descriptionText
What the works are.
- road_classificationText
The road's classification and environment, urban or rural.
- inspection_frequencyText
How often traffic management is inspected each shift.
- preparer_qualificationText
The designer's qualification, e.g. Prepare a Work Zone Traffic Management Plan.
- road_occupancy_licenceText
The road occupancy licence the works rely on.
- speed_zone_authorisationText
The speed zone authorisation the works rely on.
Version history
- v2 (current)
- v1
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/traffic_management_plan/v2.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.