What Is AMDS?
A Plain-English Guide for Councils Still on AWM (RAMM)
If someone at NZTA or a project meeting has mentioned AMDS and you're not entirely sure whether it means new software, a new database, or just more paperwork - you're not behind. AMDS is the Asset Management Data Standard, NZTA's national standard for how transport asset data should be structured. It isn't a new system you migrate to; it's a standard your existing data gets re-mapped against, inside the database you already use.
AMDS in Plain English
AMDS exists so that every council's transport asset data is structured the same way. Right now, two councils might record the same thing - say, a culvert's material or a road surface's condition rating - using different fields, different codes or different levels of detail. That makes it hard to compare data across councils or roll it up into a national picture, which is exactly what NZTA needs for funding decisions, network planning and reporting at scale.
AMDS fixes that by defining a consistent set of tables and attributes for transport asset data. Adopting it doesn't mean throwing out what your council already holds - it means taking the data you have and organising it so it fits the national shape. Where a council's asset register is thin or inconsistent in places, that's normal; AMDS work usually surfaces those gaps rather than assuming they don't exist.
Where AMDS Projects Usually Get Stuck
The recurring pattern is straightforward: a council holds its transportation asset data in AWM (RAMM), needs it re-mapped to AMDS-compliant tables to meet the national standard, and runs into two things at once - historic data quality issues that only become visible once mapping starts, and a timeframe that doesn't leave much room to fix them properly. Older records often have inconsistent attribute values, gaps where data was never captured, or naming conventions that don't map cleanly to the AMDS structure.
None of that is unusual, and it isn't a reason to delay starting. It is a reason to scope the project with a data quality check upfront, rather than assuming the mapping itself is the whole job. Councils that treat AMDS purely as a data-entry exercise tend to underestimate how much of the timeline goes into resolving what the historic data actually means before it can be mapped correctly.
Frequently Asked Questions
Do we need to buy new software to become AMDS-compliant?
No. AMDS is a data structure standard, not a piece of software you purchase. If your council already uses AWM (still widely called RAMM), your existing data is re-mapped into AMDS-compliant tables within that system - there's no new platform to procure or migrate to. The cost and effort sit in the data mapping, attribute assignment and User Acceptance Testing work, not in software licensing.
How long does an AMDS migration usually take?
It depends heavily on the size of your asset base and the state of your existing data, more than on the mapping work itself. Taupō District Council's project ran through defined pre-implementation, implementation and post-implementation stages, with a dedicated UAT week built into the implementation phase. Historic data quality issues are the most common thing that extends a timeline - budgeting time for a data quality check before committing to a schedule gives a far more realistic estimate than treating it as a fixed-length task.
What's the difference between AMDS and AWM (RAMM)?
AWM (Asset and Work Manager) is the database - the system your council's transport asset data physically sits in, still commonly called RAMM after its earlier name. AMDS (Asset Management Data Standard) is NZTA's national standard for how that data should be structured. An AMDS project doesn't move your data out of AWM into something else; it maps the data already in AWM into AMDS-compliant tables, so it's structured consistently with every other council's data nationally.
Is our council's data too messy to start an AMDS project?
Almost every council's historic asset data has some inconsistency - gaps, outdated naming conventions, or attribute values that don't map cleanly to a new standard. That's the norm, not a reason to hold off. The Taupō District Council project, and the User Acceptance Testing approach that came out of it (now referenced in NZTA's national AMDS Playbook), exists precisely because mapping and quality-checking real, imperfect council data is what an AMDS project is designed to handle.
Need more info? We're here to help.
Ready to Talk AMDS?
Not sure whether your data actually needs mapping to AMDS, or where to start with AWM (RAMM)? That's exactly the kind of question worth asking before you scope the project, not after. Corridor Solutions manages AMDS mapping and migration for councils across Taupō, Rotorua, and the wider North Island - and we're happy to tell you honestly what your project actually needs.
Traffic management and road safety consultants based in Taupō and Rotorua, serving the wider North Island.
CONTACT US
Trusted By
Taupō District Council • NZTA • Downer
