AMDS is a data standard and is system agnostic which means the Road Asset Management System you are using today can be used in the future to adopt the standard.
When the standard is adopted, any legacy data that is not supported by the standard will still be available in your Road Asset Management System. From the time the standard is adopted, only standard compliant data will be available for any new work required.
New asset classes are released in quarterly cycles and are available on the AMDS website in output files enabling users to test in an operational environment.
As each batch of asset classes are released, they are tested in prototype environments. This provides the evidence and lessons learnt for RCAs and sector partners come implementation.
Implementation of the standard will begin July 2022 with the first tranche of RCAs and will continue over 5–6 years.
Implementation of AMDS will be RCA led.
The Asset Management Data Standard (AMDS) was established to support the complete asset management lifecycle, whereas many traditional data standards have been developed from a maintenance management perspective.
When comparing to a traditional data standard, a common difference is the AMDS has been designed to support methods or processes on the network rather than at the asset level. This model enables us to reflect the activities that occur around the assets rather than capturing information against the asset itself.
AMDS is intended to support current and future multimodal networks and reflect the planning and design activities around that for asset management.
Supporting the complete Asset Management Lifecycle enables us to monitor trends in impacts, service performance or asset condition targeting the right intervention in the right place and the right time by providing better consistent data. This will help Waka Kotahi improve understanding of when and why maintenance renewal and improvement activities are needed, what different roadworks can achieve and cost, and how they should be designed and scoped to address all service defects and outcomes together for least disruption.