Technical Products Update

Technical Products Update

Funding Impact

• NDRRA Funding - replace the existing on a like for like basis,

• Standard - but expected to meet current engineering standards.

• Risks – Legal, Safety, Political etc.

Lower Order Road Design Guidelines

Another Standards Initiative from IPWEAQ

Lower Order Design Guidelines

• Road geometric values ; sealed & unsealed

• Road volume categories ^:

• 1-10 Formed Track

• 10-50 Local Access

• 50-150 Minor Road

• Road drainage – resilience vs immunity, floodways

• Pavement design – DCP’s, HCV’s

• Site assessment – observations & techniques

Example Project

Replacement of existing timber bridge with box culverts.

• Lightly trafficked rural road – AADT 25

• Generally gravel construction

• Width varies from one to two lane formation

• No reported crashes at the site

• Good visibility on approaches > 300m in both directions

• The creek is predominantly dry and only flows in rain events

• No change to existing risk rating

• Local access road with few unfamiliar users Solution – no guardrail – use signage

i.e., floodway warning signs and hazard markers.

Standard Drawings

COMPLETE STREETS &

QLD STREETS

Guidelines for Urban Street Design

QUDM

ADAC Overview

South West Queensland Branch Conference

Toowoomba

November 2015

The Need for a Standard for Exchange of

As Constructed Data

Problems ADAC Solves

Typical Paper-Based Process

Problems ADAC Solves

1. Multiple AM data standards / formats

− Designs / as cons created in multiple formats

− Difficult to exchange data between systems or organisations 2. Re-work caused by incomplete / inconsistent asset data capture

− Not all data captured

− Data collected in different formats

− Spatial data & asset component data are not consistent Two major problems facing Asset Managers today:

Result: a lack of confidence in your asset data that impacts

your ability to do long-term asset, service & financial planning

Problems ADAC Solves

The Smarter (ADAC) Process

* Asset Design & As Constructed (Data Standard)

What is ADAC*?

• A set of tools to make the transfer of survey accurate asset data easier

– Between asset constructors, contractors & owners

• Developed by a consortium of asset owners

– Informed by industry (incl. surveyors) – Supported by IPWEA Queensland

• Endorsed by NAMS.AU

– See case study 32 in the International Infrastructure

Management Manual (2011) p. 2|56

ADAC Components

• ADAC Data standard

– Project information

– Spatial & non-spatial data schemas

• Transport, Drainage, Water, Sewer, Open Space, Cadastre, Surface, Enhancements, Supplementary

• 68 asset types

• ADAC Data transfer mechanism

– XML based

• Supporting Documentation

– Data capture guidelines

Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.

It is defined in the XML 1.0 Specification produced by the World Wide Web Consortium ( W3C), and several other related specifications, all gratis open standards.

The design goals of XML emphasize simplicity, generality, and usability over the

Internet. It is a textual data format with strong support via Unicode for the languages of the world. Although the design of XML focuses on documents, it is widely used for the representation of arbitrary data structures, for example in web services.

What is XML ?

</adac:Pipe>

<adac:Pipe>

<adac:ObjectId>ala_DPipob_RCP_acad_07100004</adac:ObjectId>

<adac:ComponentInfo>

<adac:InfrastructureCode>DrainagePipe</adac:InfrastructureCode>

<adac:Owner>Council</adac:Owner>

<adac:Status>Design</adac:Status>

<adac:Notes>Design Values</adac:Notes>

<adac:SupportingFiles></adac:SupportingFiles>

</adac:ComponentInfo>

<adac:PipeStructure>

<adac:CircPipe>

<adac:Diameter_mm> 300</adac:Diameter_mm>

<adac:Material>CSP</adac:Material> 1<adac:Class>6</adac:Class>

<adac:JointType>FJ</adac:JointType>

</adac:CircPipe>

</adac:PipeStructure>

<adac:Cells>1</adac:Cells>

<adac:ConcreteCoverType>Standard</adac:ConcreteCoverType>

<adac:Grade> -7.983653</adac:Grade>

<adac:Length_m> 4.24618</adac:Length_m>

<adac:Geometry>

<adac:Polyline>

<adac:Path>

<adac:PolySegment>

<adac:Vertex>

<adac:X> 497328.88694</adac:X>

<adac:Y> 6973067.53185</adac:Y>

</adac:Vertex>

<adac:Vertex>

<adac:X> 497328.28302</adac:X>

<adac:Y> 6973063.32883</adac:Y>

</adac:Vertex>

</adac:PolySegment>

</adac:Path>

</adac:Polyline>

</adac:Geometry>

Metadata (data about the data)

• What type of information this is

• Used by programs to determine what to do with the information that follows

Asset attribute data

• Non-spatial data about the asset

Geometry elements

• Spatial data about the asset

ADAC Data Capture Guideline

Source: Moreton Bay Regional Council

ADAC Vision

Asset Design Information

Asset Construction

Information

Asset Handover Information

Asset Register

GIS

Drawing Repository

Document Management

System Asset Owner’s

Submission Portal

Submission errors Rapid validation against requirements

(e.g. ADAC)

Constructor Asset Owner

ADAC Benefits

• Asset Owners (e.g. Councils & Utilities)

– Better asset data quality & asset management

• Minimises re-work & manual data entry

– Not tied to specific software products

• Asset Constructors & Contractors

– Simplifies doing business with utilities & Councils – Reduces approval time for projects

– Better quality data out

• “Round tripping” of asset data

Who’s Behind ADAC?

• A mix of small, medium & large Councils & utilities

• Not profit motivated

− Focused on advancing asset management practice

− Sharing with & learning from each other

• Operating under the governance of IPWEAQ

− ADAC governance model

− Role of the IPWEAQ

ADAC Consortium

Thank you

_____________

Engineering Communities – it’s what we do!