Asset Management Data Standard For better land transport investment decision-making
Overview What is the Asset Management Data Standard and why do we need it
What is the AMDS TOTAL LAND TRANSPORT ASSETS A national standard for land transport assets the sector can share • 68 road controlling authorities responsible for the management of A common language and data structure creating a consistent way of roads in NZ defining and describing land transport assets • 95,608 kms of road • the standard is comprised of : • 19,962 bridges • NZ$657,148,346 million • the standard itself - design principles and concepts • the technical specifications handbook • technical specifications that describe assets and contextual information or ‘entities’ including: • location • controls - including legislation and contracts • measures • business activities like construction and maintenance • supporting tools to view and comment on the technical specifications • exportable files of the asset schema and content
Why do we need the AMDS TOTAL LAND TRANSPORT ASSETS Better land transport investment decision-making • 68 road controlling authorities responsible for the management of • better evidence to inform land transport asset investment decisions roads in NZ • 95,608 kms of road • opportunities for sector-wide best practice sharing and collaboration • 19,962 bridges • supports effective and efficient allocation of funding • NZ$657,148,346 million • Assist investment partners to make the case for regional investment • savings and benefits of approx. $70m annually • access to and confidence in asset related data
Why now ONTOLOGICAL vs HIERARCHICAL Collaboration and digital engineering mandated Allows for multiple groups of entities to be related to multiple groups of entities without duplication • 2018/19 Govt Policy Statement Functional relationships allow entities to • deliver the right infrastructure at the best cost to achieve value for money be related to many functions e.g. a barrier to crash / protection / delineation / mode separation • Treasury’s National Infrastructure Plan Makes it easy to map across different • develop a national, shared, open data standard for infrastructure relational models e.g. transport asset and water • Synergistic collaboration • Road Efficiency Group • New technology • Ontological model sets the groundwork for digital engineering across the asset life-cycle and in harmony with other sectors.
Who are we talking to This programme will only be Everyone! successful if it is designed, developed and delivered as a • Experts in asset management and asset data management across the transport sector collaborative effort between Waka • Road controlling authorities Kotahi, the Road Efficiency Group, • Road maintenance contractors and the local government and • Transport infrastructure developers and consultants • Utility providers transport sectors. • Asset management software providers • 3Waters standard development team • Government agencies • Government Chief Data Steward • Interest groups (national and international) • REG - LGNZ – NZUAG – Engineering NZ - IPWEA – AustRoads - …
What you need to know SECTOR-WIDE RCAS CAN BENEFITS WILL CHOOSE STANDARD IS ONLY BE IMPLEMENTATION ITERATIVE – ACHIEVED WITH TIMING AND EVEN AFTER GO STRONG (NON-FINANCIAL) LIVE MID-2021 ADOPTION SUPPORT
AMDS | Release Plan To co-design the standard and support successful implementation
Timeline – to beginning of implementation programme* Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Activity 2020 2020 2020 2020 2020 2020 2021 2021 2021 2021 2021 2021 2021 Data Standard releases Consult on support and timing Detailed Implementation Plan Prototyping and Testing Business Case Roll out of the Data Standard * Implementation of the standard across the sector starts in July 2021 for a maximum of 9 years
Indicative Release Roadmap July 2021 July 2020 October 2020 January 2021 April 2021 Release v0.1 Release v0.2 Release v0.3 Release v0.4 Release v1.0 Content Content Content Content Content Completed Data Standard Pavement and Surfacing Location Structures | Bridges, All asset types. document and Technical gantries (DSS Stage 2), Poles and Gantries | device Zones | amenities, Completion of all related Specification Guidance high masts (DSS Stage supporting structures environmental lens entities (e.g. controls, document for adoption by 2), retaining walls, and inclusion of further sector Signs | as an example of a Devices | Signs tunnels, M&E plant, performance measures device (electronic), street lights, pedestrian and stock as required). traffic lights, weather underpasses Barriers monitoring, slope Completion of Stormwater | Culverts, monitoring, pedestrian environmental, heritage, surface water channels, crossing/ refuges, cultural, social subsoil drainage, platforms, road perspectives. retaining wall drainage markings, splitter islands & roundabouts, speed Geo-technical assets | humps slopes, restraints (rock mesh, debris fences, rock anchors), retaining walls, barriers Prioritised feedback on Prioritised feedback on Prioritised feedback on Rv0.1 Rv0.2 Rv0.3 and Rv0.4
Conceptual relational models are already part of our vocabulary
AMDS Entity Model: ‘asset’ is impacted by multiple contextual entities that make up the asset management system informs require Driver Measure informs informs is owned mandates Business Business by Actor Function Activity is responsible mandates for realises realises supports participates in Business Process Role regulates initiates performs in resolves Event Control constructs establishes maintains Actor delivers realises ASSET Zone Business Product regulates Location locates locates Information System is recorded generates owns requires Information manages accesses/creates/modifies
The AMDS Entity Model captures and describes all stages and activities in the asset life-cycle, from design to dispose Active mode infrastructure GPS: Safe measure informs require + Healthy Driver Measure informs People informs is owned mandates Business Business by Actor Asset construction Function Activity Walking and is responsible cycling mandates for improvement realises realises supports Construction participates in Business Process Role Contractor regulates initiates Constructs performs in Construction resolves Event Control Contract maintains establishes Fulton Actor Hogan delivers realises Pavement ASSET Zone + Surface Business Cycle Lane Cycle Product regulates Network Location locates locates Information System is recorded generates owns requires Information As built manages accesses/ creates /modifies
Scenario: Pavement Condition Assessment Driver Business Function GPS Amenity: CO1 State highway road mandates Smooth Travel construction/improvements and Exposure maintenance realises realises Business Activity mandates Business Asset condition Process assessment High Speed Data Initiates Condition Assessment realises participates in regulates Event Control ONRC ASSET Classification measures Role provides data to Role Zone NOC NOC delivers Carriageway Pavement Principal Contractor on SH1 Layer Business Product has role Location locates locates Fulton Condition Hogan Assessment Asset Information Actor supplies Information Condition Assessment delivers creates System report contains e.g. RAMM, NZTA transforms INFOR Actor requires
Scenario: Sealed road resurfacing – State Highway Asset information and Business activity Measure informs NZTA IPM: 26 requires/ ONRC TO 04: loss Business informs of control on wet Function State highway road roads Driver construction/improvements and maintenance GPS Safety driver mandates realises realises Business Activity Business mandates Asset Lifecycle: Asset construction Process NLTP WC 212, NOC MS 6.3, etc Sealed road initiates resurfacing realises participates in Control (NOC regulates Event control) NOC Contract NZTA SM012, M10, ASSET TNZ P11, P17 Role maintains Role NOC Zone NOC delivers Principal Contractor Surface Layer Carriageway provides data to Business on SH1 Product has role Location locates locates [name of New surface layer Actor] Asset Information Actor Renewal quality plan Information contains delivers supplies Public notification(s) transforms System Post verification report e.g. RAMM, creates NZTA Job data INFOR requires Actor
Example: Portal Gantry
Example: Portal Gantry
‘Gantries’ (an asset) have multiple relationships to other assets and non-asset entities Clicking on the ‘bubbles’ jumps to further detail e.g. drills down into gantry attributes
Viewers can explore multiple levels and in the ‘comment’ module, can leave and see feedback and suggestions Feedback will be considered for integration into iterative releases of the standard, both during the v0.x releases and post implementation of the “completed” standard on 1 July 2021
Recommend
More recommend
