CONTACT CENTRE WAIT TIMES: Our Contact Centre is currently experiencing significant wait times. View frequently asked questions

SCAM ALERTS: Report a phishing scam or learn about the latest phishing emails

ROAD USER CHARGES (RUC) DISCOUNT: Find out more about the temporary RUC reduction scheme

ONLINE SERVICES: We are currently experiencing issues with all our online services at the moment. We are working to resolve the services as soon as possible. We apologise for any inconvenience caused.

COVID-19 SERVICES UPDATE: Information on Waka Kotahi services, extensions and more

ONLINE SERVICES: We currently have an issue with receiving some payments and are working to resolve this issue as quickly as possible. We apologise for any inconvenience.

EASTER WEEKEND – PLAN AHEAD: Heading away for the long weekend? Check our holiday journeys tool(external link)

SCAM ALERTS: Refund email and Vehicle licence (rego) renewal phishing emails

Implementation of AMDS will be RCA led. This approach recognises that RCAs are different and have individual operating environments. It provides RCAs with flexibility about how they manage their AMDS implementation.   

Waka Kotahi will provide an Implementation Playbook which includes guidance, tools, and templates to support AMDS implementation. Waka Kotahi will also hold a quality assurance role within each implementation.

As part of AMDS implementation RCAs do not need to collect additional data. Once AMDS has been implemented RCAs can use the data standard to decide where more complete or additional asset data will improve their asset management practice.  

We have contacted all RCAs about AMDS implementation. If you have any questions, please get in touch by emailing amds@nzta.govt.nz

Implementation timeline

AMDS implementation is phased over five years starting, 1 July 2022 and completing by 30 June 2027. It is expected that all RCAs will have adopted AMDS by 30 June 2027.

View larger file [JPG, 181 KB]

Stages, activities and estimated timeframes

We recommend that pre-implementation activities are started early, at least 6-12 months before you plan to start implementation.

Pre-implementation
(6–12 months)
Implementation
(6 months)
Post implementation
(ongoing)
  • Planning
  • Change impact assessment
  • Current state analysis – asset data and system integrations
  • Communications and engagement planning
  • Data mapping and migration
  • Software update
  • Integration updates
  • User acceptance testing
  • Training
  • Updates to documentation
  • Communications and engagement
  • Post implementation support
  • AMDS quality assessment
  • Lessons learnt
  • AMDS community of interest

For larger, complex RCAs we recommend you allow additional time and undertake a current state analysis of your asset data and system integrations early as this is a key input to your planning. 

To help you undertake this analysis we have created a template.

Current state analysis template [XLSX, 356 KB]

What can RCAs do to prepare now for implementation?

Your assets and the data standard

  • Review the output files on the AMDS website
  • Identify the data that you are collecting/not collecting.
  • Discuss the data standard with your subject matter experts to understand how the standard will impact your organisation.

Your business planning

  • Include AMDS implementation in your business planning. If you are unsure which tranche you are in, email amds@nzta.govt.nz
  • Identify who will be involved in your AMDS implementation.
  • Consider other projects and business changes which are planned to occur at the same time as your AMDS implementation.
  • Talk to your suppliers about when you plan to adopt AMDS.
  • If tendering for new suppliers, include when you plan to adopt AMDS in your tender documentation.

For suppliers

  • If responding to a tender, it is recommended that you confirm when the RCA plans to adopt AMDS.

Your systems and processes

  • Start the current state analysis of your systems. This will help you capture information about how your asset data is collected, stored and identify the systems and processes that use asset data.
    Current state analysis template [XLSX, 356 KB]
  • When identifying system and processes that use asset data, include manual extracts, eg including spreadsheets, CSV files and reports.
  • Common asset management system integrations:
    Diagram showing common asset management system integrations - finance, planning and scheduling, data warehouse, reporting, spreadsheets, CSV files and shapefiles, SQL scripts, dispatch and content management
  • Create a process map or diagram to show how asset data is used by other systems, forms, or reports. See the process map example below.
  • Do a stock take of your queries, training material, and procedures that use or support asset data management.

Process map example

Detailed data analysis (optional)

Some RCAs may want to undertake early analysis of their data. This is optional and not a requirement of AMDS implementation.

If you decide to undertake this analysis, we recommend that you wait until AMDS v1.0 is released in July 2022. It should also be noted that some activities will need to be reworked when starting AMDS implementation and the AMDS programme is unable to provide support for this analysis.

Analyse your RAMM look ups:

  • Clean up existing data.
  • Identify how the data relates to the AMDS look ups for that particular asset type.
  • For existing data lists, identify the look up values that you may want to merge or match to AMDS look up values. If it’s a table name, there will be no problem with the merge (as there will no change to a table name (until your tranche date) but the look up value could be different because there might have a trigger or a field on an API that is looking for a particular value, that doesn’t exist anymore.
  • Convert that look up value to the new AMDS value.

Begin to capture data records for assets not currently captured on the network (signs, fences, railings).

Document where you have started to capture/record/store new data attributes, tables, UDTs - this can be used in the pre-implementation/migration phase to quickly identify new and updated records.

Start to collect data in the existing RAMM tables and impose some of the (known) business rules, eg start collecting mandatory values or use RAMM look-up lists to match the value list. 

  • This practice will not change the structure and therefore the migration from RAMM to the AMDS compliant table will remain the same. With the rules remaining the same, you will just get a much greater match between the old RAMM data and the new AMDS data.
  • The benefits would be that you are only collecting one ‘copy’ of the data, the migration won’t be affected, there will be no data loss and less effort not having to try and merge two systems together.

Tools to support RCA implementation of AMDS

Waka Kotahi is developing a playbook to support and guide RCAs for implementation of the AMDS. 

AMDS playbook

Implementation approach

Communications and engagement

Data mapping and quality assurance

  • Pre-implementation activities
  • Implementation activities
  • Key messages
  • Benefits for different audiences
  • SQL scripts
  • Data analysis and triage process
  • Summary of the QA report

Tools

Training

Post implementation

  • Templates
  • Checklists
  • Supplier list
  • Training framework
  • Training materials
  • AMDS change and release processes
    AMDS community of interest

Implementation insights

To help RCAs get ready for AMDS implementation, Waka Kotahi is testing and validating the ability to implement the standard with the RCAs, maintenance contractors and professional services through our prototype activities.

Marlborough Roads

We have been working with Marlborough Roads to validate implementation activities, specifically data migration and training approaches.

Key insights

  • Training: For roles that collect data, a face-to-face training session works best, where there are opportunities for multiple practice exercises. The reference guides provided for use while in the field, were relevant and useful.
  • Data migration: We successfully completed the data analysis and data migration process for a couple of asset types. As such, we are confident that the validated approach will provide RCAs and contractors a viable and effective process for mapping existing asset data to the data standard.

Wellington City Council

We have been working with Wellington City Council to investigate and document integrations. This work will provide key information for RCAs and NOCs as part of implementation of the AMDS.

The focus at WCC has been to investigate and document the integration of RAMM which has provided an operational overview of the Transport Asset processes and the interaction with RAMM; the systems and applications that integrate/relate to RAMM and the reports and SQL that are run using RAMM data.

Key insights

  • Integrations: For a council of this size and this complexity, many integrations can be handled as part of BAU with some integrations potentially requiring vendor resource. We will repeat this process at other councils as part of the prototype to provide further insight.
  • Reporting: With Wellington City Council using different reports predominately managed internally, these reports can be updated as part of BAU operations. The reports will require changes to enable AMDS reporting managed by internal BAU operations.

This is expected to be similar for other RCAs of this size, and with less well-resourced RCAs likely to require more support.