Hastings District Council AMDS Migration: A Corridor Solutions Case Study
Hastings District Council appointed Corridor Solutions to manage the implementation of the Asset Management Data Standard (AMDS) across its full transportation asset base - working alongside Beca and Thinkproject, with NZTA providing governance across the project. By November 2025, the project had delivered 57 automated migrations and 2 manual migrations, with scope extending beyond core transportation assets into selected Parks and Reserves assets, including bridges and cycle amenities. Here's what that project actually involved.
The Brief: What Hastings District Council Needed
Like most councils, Hastings District Council held its transportation asset data in AWM (Asset and Work Manager - the database still widely known by its earlier name, RAMM). NZTA's AMDS sets a national standard for how that data should be structured, and HDC needed its existing asset data brought into line with it, across a full transportation asset base rather than a single asset class.
Corridor Solutions was appointed to manage that implementation, working alongside two established firms - Beca and Thinkproject - with NZTA providing project governance throughout. That combination of a specialist AMDS project manager, national engineering and data partners, and NZTA oversight is a realistic picture of what a council-scale AMDS project actually looks like, rather than a single-consultant job.
How the Project Ran: Three Stages
The implementation followed a defined three-stage structure. Pre-implementation covered planning and stakeholder engagement - understanding HDC's existing data, agreeing scope, and setting expectations across the council and delivery partners. Implementation was the core of the work: mapping and migrating data into AMDS-compliant tables within AWM, supported by User Acceptance Testing (UAT) to confirm the mapped data was accurate before sign-off. Post-implementation covered lessons learned and a data quality improvement plan, addressing gaps the migration surfaced rather than leaving them unresolved once the project closed.
How This Compares to the Taupō District Council AMDS Migration
The Hastings project wasn't Corridor Solutions' first AMDS engagement. The team also project managed and undertook the data mapping for Taupō District Council's AMDS migration - re-mapping TDC's transportation asset data, held in AWM (RAMM), into AMDS-compliant tables, and producing a data mapping file specifying exactly where existing assets sit within the AMDS structure. The User Acceptance Testing template built during that project's migration week is now referenced in NZTA's national AMDS Playbook, used by other councils working through comparable migrations.
Seeing the same rigour applied on both projects - defined stages, dedicated UAT, a documented data quality plan afterwards - is the clearest evidence that the HDC result wasn't a one-off. It's a repeatable process, not a single lucky outcome.
What This Means If You're Considering an AMDS Project
A structured, multi-stage project
Expect a structured, multi-stage project - not a single data-entry exercise. Planning and post-migration data quality work matter as much as the mapping itself.
User Acceptance Testing (UAT)
Budget time for User Acceptance Testing as a distinct phase, not a final formality - it's where genuine mapping errors get caught before sign-off.
AWM (RAMM) stays in place
Your existing database (AWM/RAMM) stays in place - the work is structural remapping, not a platform migration.
Multiple delivery partners, NZTA governance
Larger councils may need multiple delivery partners working together, with NZTA providing governance - that's normal at scale, not a sign the project is over-complicated.
Historic data quality issues
Historic data quality issues are common and are exactly what a good post-implementation plan should address, not something to be embarrassed about going in.
Frequently Asked Questions
Did Hastings District Council move its data to a new system?
No. This is the most common misunderstanding about AMDS projects generally. AWM (still widely called RAMM) remained HDC's system of record throughout - the project mapped the data already held within it into AMDS-compliant tables, in line with NZTA's national standard. It's a restructuring of existing data, not a migration to a different database.
How long did the Hastings District Council AMDS project take?
The project ran through three defined stages - pre-implementation planning and stakeholder engagement, implementation covering data mapping and migration with dedicated User Acceptance Testing, and post-implementation addressing lessons learned and a data quality improvement plan. By November 2025 it had delivered 57 automated and 2 manual migrations, with the scope extended to include selected Parks and Reserves assets.
Is this experience specific to Hastings, or does it extend to other councils?
It extends beyond Hastings. Corridor Solutions also project managed and delivered the data mapping for Taupō District Council's AMDS migration, including a UAT template now referenced in NZTA's national AMDS Playbook. The consistent process across both projects - defined stages, dedicated testing, a documented data quality plan - is what makes this a repeatable capability rather than a single result.
Who else was involved in the Hastings project besides Corridor Solutions?
Corridor Solutions worked alongside Beca and Thinkproject, with NZTA providing governance across the project. That mix of specialist AMDS project management, established engineering and data partners, and NZTA oversight is typical of what a full council-scale AMDS implementation requires, rather than something one firm delivers in isolation.
Need more info? We're here to help.
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
