Asset Management Consulting for Hawke's Bay Councils and Contractors

Corridor Solutions was appointed to manage AMDS implementation for HDC's transportation assets, working alongside Beca and Thinkproject, with NZTA providing governance across the project. The work ran in three stages: pre-implementation (planning and stakeholder engagement), implementation (mapping and migrating data into AMDS-compliant tables within AWM, plus supported User Acceptance Testing), and post-implementation (lessons learned and a data quality improvement plan). In November 2025 the project delivered 57 automated migrations and 2 manual migrations, and the scope extended beyond core transportation assets to Parks and Reserves assets, including bridges and cycle amenities. It's the clearest example in the region of what an AMDS project involves end to end, and it's why Hawke's Bay councils considering the same work don't need to start from a blank page.

No - and this is the most common misunderstanding. AMDS (Asset Management Data Standard) is NZTA's national standard for how transport asset data should be structured, not a replacement for your existing database. Your council's data almost certainly already sits in AWM (Asset and Work Manager - still widely referred to by its former name, RAMM). An AMDS project re-maps that existing data into AMDS-compliant tables within the same system; it isn't a migration to a different platform. The distinction matters for budgeting and planning: it's a data structuring and quality project, not a system replacement, and the effort goes into mapping, attribute values and User Acceptance Testing rather than a platform switch.

The named project experience is with Hastings District Council, and that's the honest basis of the region's Proof Bank right now. The asset management consulting work - AMDS mapping, network assessments, tender support and lifecycle planning - applies the same way to any Hawke's Bay council or contractor managing transport asset data, including Napier. If your council is earlier in the AMDS conversation than Hastings was, that's a reasonable starting point for a first call.

It depends on the size of the asset base and the state of the existing data, but the HDC project is a useful reference point: pre-implementation planning, a defined implementation phase covering data mapping and migration with a dedicated UAT week, then a post-implementation stage addressing data quality. Historic data quality is consistently the factor that extends timelines - inconsistent attribute values or gaps in older records take longer to resolve than the mapping work itself. A realistic scoping conversation upfront, based on a sample of your current AWM (RAMM) data, gives a far more accurate timeframe than a generic estimate.

Most councils don't have a dedicated AMDS specialist on staff, and hiring one for a single migration project rarely makes sense against the workload. Corridor Solutions provides project management, data mapping, UAT coordination and post-migration data quality work as a defined engagement rather than a new hire - and because the practice doesn't sell software or equipment, the recommendations are about what your data actually needs, not what a platform vendor wants to sell alongside it. The Hastings District Council project is the clearest demonstration of that approach delivered in full, from planning through to a data quality improvement plan.