Preparing for implementation

It’s recommended that Road Controlling Authorities (RCAs) plan early for their Asset Management Data Standard (AMDS) implementation.

We recommend you:

• Review the AMDS Version 1.0
  • identify the data that you are collecting and not collecting
  • discuss the data standard with subject matter experts to understand how the standard will impact your organisation.
• Talk to your suppliers:
  • understand what will change for your suppliers
  • let your suppliers know when you plan to adopt AMDS.
• Discuss AMDS with RCAs in your region:
  • consider how you can support each other to adopt AMDS.
• Include AMDS in your business planning:
  • 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
  • if tendering for new suppliers, include when you plan to adopt AMDS in your tender documentation.
  • include AMDS implementation in your asset management plan and NLTP
  • if you are unsure which tranche you are in, email amds@nzta.govt.nz
• Identify system integrations that you have with your asset management system:
  • common asset management system integrations:
  • 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
  • create a process map or diagram to show how asset data is used by other systems, forms, or reports
  • do a stock take of your queries, training material, and procedures that use or support asset data management.

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. 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 early data 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, therefore the migration from RAMM to the AMDS compliant table will remain the same.
  • With the same business rules you will just get a much greater match between the old RAMM data and the new AMDS data.