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 use as part of the implementation. Waka Kotahi will also hold a quality assurance role within each implementation.
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.
We will directly contact all RCAs to discuss the implementation of AMDS. If you have any questions, please get in touch by emailing email@example.com
What can RCAs do to prepare now for implementation?
Your assets and the data standard
- Review the output files on the AMDS website
- Assess what you are collecting/not collecting.
- Engage with your specialist asset resource to review assets, eg Drainage asset expert and how the standard will impact your organisation.
*This is a review exercise, and currently there is no requirement to change the way you collect data.
Your business planning
- Assess what programmes business change strategies are taking place around the implementation of AMDS at your organisation, ie Digital Strategy, Asset Management improvement roadmap.
- Consider internal funding processes and roles and responsibilities required for implementation.
- Engage with key stakeholders concerning your annual planning process.
- 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.
- If responding to a tender, it is recommended that you confirm when the RCA plans to adopt AMDS
- Start thinking about your systems that use RAMM data, including miscellaneous spreadsheets and similar documents.
- Create an asset data management process map including systems, forms (eg to collect data) and reports that utilise asset data. This will be helpful when pre-implementation begins. (See process map example below).
- Create a stock take of all queries, training material used in asset data management.
Primary and secondary integration process map
This is an optional piece of work that some RCAs may wish to undertake prior to their implementation. Any of these activities undertaken prior to implementation would be supported by the RCA, not the AMDS programme. We recommend you don’t undertake this work until the standard is released in July 2022. Should you wish to start earlier, please understand there may be changes that may impact the tasks below requiring rework.
Complete the integrations template to gain an understanding of your data and minimise impacts in other systems:
- Identify systems/applications/processes that interact with RAMM data.
- What tools are extracting or exporting data through an API?
- What tools are extracting .csv dumps of their data?
- What is this data being used for?
* Email firstname.lastname@example.org for a copy of the integrations template.
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 benefit(s) 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.
Communications & engagement
Data mapping & quality assurance
- Roles and responsibilities
- Implementation activities
- Draft project schedule
- Lessons learnt
- Key messages
- Benefits for different audiences
- SQL scripts
- Data analysis & triage process
- Summary of the QA report
- Supplier list
- Training framework
- Training materials
- Process for future AMDS updates
- AMDS community of practice
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.
We have been working with Marlborough Roads to validate implementation activities, specifically data migration and training approaches.
- 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.
- 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.