21
Asset Management Data Standard For better land transport investment decision-making
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 AMDSA national standard for land transport assetsthe sector can shareA common language and data structure creating a consistent way of defining and describing land transport assets
• the standard is comprised of:
• 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
TOTAL LAND TRANSPORT ASSETS
• 68 road controlling authorities responsible for the management of roads in NZ
• 95,608 kms of road
• 19,962 bridges
• NZ$657,148,346 million
TOTAL LAND TRANSPORT ASSETS
• 68 road controlling authorities responsible for the management of roads in NZ
• 95,608 kms of road
• 19,962 bridges
• NZ$657,148,346 million
Why do we need the AMDSBetter land transport investment decision-making
• better evidence to inform land transport asset investment decisions
• opportunities for sector-wide best practice sharing and collaboration
• supports effective and efficient allocation of funding
• 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
ONTOLOGICAL vs HIERARCHICALAllows for multiple groups of entities to be related to multiple groups of entities without duplication
Functional relationships allow entities to be related to many functions e.g. a barrier to crash / protection / delineation / mode separation
Makes it easy to map across different relational models e.g. transport asset and water
Why nowCollaboration and digital engineering mandated
• 2018/19 Govt Policy Statement• deliver the right infrastructure at the best cost to achieve value for money
• Treasury’s National Infrastructure Plan• develop a national, shared, open data standard for infrastructure
• 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.
This programme will only be
successful if it is designed,
developed and delivered as a
collaborative effort between Waka
Kotahi, the Road Efficiency Group,
and the local government and
transport sectors.
Who are we talking toEveryone!
• Experts in asset management and asset data management across the transport sector
• Road controlling authorities• Road maintenance contractors• Transport infrastructure developers and consultants• Utility providers• 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 - …
STANDARD IS ITERATIVE –
EVEN AFTER GO LIVE MID-2021
RCAS CAN CHOOSE
IMPLEMENTATION TIMING AND
(NON-FINANCIAL) SUPPORT
SECTOR-WIDE BENEFITS WILL
ONLY BE ACHIEVED WITH
STRONG ADOPTION
What you need to know
AMDS | Release PlanTo co-design the standard and supportsuccessful implementation
Activity Jul 2020
Aug 2020
Sep 2020
Oct 2020
Nov 2020
Dec 2020
Jan 2021
Feb 2021
Mar 2021
Apr 2021
May 2021
Jun 2021
Jul 2021
Data Standard releases Consult on support and timing
Detailed Implementation Plan
Prototyping and Testing
Business Case
Roll out of the Data Standard
Timeline – to beginning of implementation programme*
*Implementation of the standard across the sector starts in July 2021 for a maximum of 9 years
Indicative Release RoadmapJuly 2020 October 2020 January 2021 April 2021 July 2021
Release v0.1 Release v0.2 Release v0.3 Release v0.4 Release v1.0
Content
Pavement and Surfacing
Poles and Gantries | device supporting structures
Signs | as an example of a device
Barriers
Content
Location
Zones | amenities, environmental lens
Devices | Signs (electronic), street lights, traffic lights, weather monitoring, slope monitoring, pedestrian crossing/ refuges, platforms, road markings, splitter islands & roundabouts, speed humps
Content
Structures | Bridges, gantries (DSS Stage 2), high masts (DSS Stage 2), retaining walls, tunnels, M&E plant, pedestrian and stock underpasses
Stormwater | Culverts, surface water channels, subsoil drainage, retaining wall drainage
Geo-technical assets | slopes, restraints (rock mesh, debris fences, rock anchors), retaining walls, barriers
Content
All asset types.
Completion of all related entities (e.g. controls, and inclusion of further performance measures as required).
Completion of environmental, heritage, cultural, social perspectives.
ContentCompleted Data Standard
document and Technical Specification Guidance document for adoption by sector
Prioritised feedback on Rv0.1
Prioritised feedback on Rv0.2
Prioritised feedback on Rv0.3 and Rv0.4
Conceptual relational models are already part of our vocabulary
AMDS Entity Model: ‘asset’ is impacted by multiple contextualentities that make up the asset management system
Business Process
Information
mandates
require
delivers
initiatesresolves
realises
accesses/creates/modifies
constructsmaintains
MeasureDriver
ASSET
Control
Information System
Event
Business Product
Role
Actor
Zone
manages
Business Activity
locateslocates
participates in
informs
Business Function
Location
is responsiblefor
is ownedby Actor
mandates
performs in
owns requires
is recordedgenerates
regulates
establishes
regulates
supportsrealisesrealises
informs
informs
The AMDS Entity Model captures and describes all stages and activities in the asset life-cycle, from design to dispose
Business Process
Information
mandates
require
delivers
initiatesresolves
realises
accesses/creates/modifies
maintains
MeasureDriver
ASSET
Control
Information System
Event
Business Product
Role
Actor
Zone
manages
Business Activity
locateslocates
participates in
informs
Business Function
Location
is responsiblefor
is ownedby Actor
mandates
performs in
owns requires
is recordedgenerates
regulates
establishes
regulates
supportsrealisesrealises
informs
informs
GPS: Safe + Healthy
People
ConstructionContractor
Active mode infrastructure measure
Walking and cycling
improvement
Asset construction
Constructs
Fulton Hogan Pavement
+ Surface
Construction Contract
Cycle LaneCycle Network
As built
Scenario: Pavement Condition Assessment
High Speed Data Condition Assessment
Condition Assessment report
mandates
mandates
e.g. RAMM, INFOR
Condition Assessment
delivers
Initiatesrealises
has role
suppliescreates
ONRC Classification
measures
State highway road construction/improvements and
maintenance
GPS Amenity: CO1 Smooth Travel
Exposure
Pavement Layer
Control
Driver
Asset InformationInformation
System
Event
Business Process
Location
Business Product
Business Function
NZTA
Actor
NOC Principal
Role
Fulton Hogan
Carriageway on SH1
Zone
requires
provides data to
regulates
delivers
containstransforms
Actor
Asset condition assessment
Business Activity
locateslocates
NOC Contractor
Role
realises realises
participates in
ASSET
Scenario: Sealed road resurfacing – State Highway
Sealed road resurfacing
Renewal quality planPublic notification(s)
Post verification reportJob data
mandates
mandates
e.g. RAMM, INFOR
New surface layer
delivers
initiatesrealises
has role
supplies
creates
NOC ContractNZTA SM012, M10,
TNZ P11, P17 maintains
State highway road construction/improvements and
maintenanceGPS Safety driver
Surface Layer
Control (NOC control)
Driver
Asset InformationInformation
System
Event
Business Process
Location
Business Product
Business Function
NZTA
Actor
NOC Principal
Role
[name of Actor]
Carriageway on SH1
Zone
requires
provides data to
regulates
delivers containstransforms
Actor
Asset Lifecycle: Asset constructionNLTP WC 212, NOC MS 6.3, etc
Business Activity
locateslocates
NOC Contractor
Role
realises realises
participates in
NZTA IPM: 26 ONRC TO 04: loss of control on wet
roads
Measure
requires/informs
Asset information and Business activityinforms
ASSET
Example: Portal Gantry
Example: Portal Gantry
‘Gantries’ (an asset) have multiple relationshipsto other assets and non-asset entitiesClicking 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 suggestionsFeedback 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
The Asset Management Data Standard Model
www.nzta.govt.nz/amds
