The Discovery Phase Explained: What US Municipal Public Works Directors Get Before a Line of a Custom Asset Management Platform Is Written

Audit Fifty Assets

An asset management discovery phase should start with an exercise a department can run without hiring anybody. Take fifty assets at random across your classes and establish, for each attribute, where the information came from.

Surveyed and verified. Taken from an as-built. Inferred from the assets either side. Or assumed by somebody at some point and never questioned.

Most departments find the distribution uncomfortable. The pipe material everybody treats as known turns out to be an inference. The installation year is a decade with a question mark. The depth is a standard the city used in that era rather than a measurement.

That exercise takes a few days and produces the most important finding in the whole project, which is how much of the capital plan would be resting on things nobody actually knows.

It also sizes the field verification work, which is the largest budget item and the one departments most often discover late.

And it is useful regardless of what gets built. Discovery is the decision layer of the full custom software development guide to asset management platform development, and the field verification it sizes is what custom mobile app development later has to support.

The Second Exercise: Age Your Condition Data

For each asset class, establish when the condition information was last observed rather than estimated.

Pavement may have been surveyed two years ago or seven. Sewer may have a small inspected fraction and a large estimated remainder. Sidewalks may never have been assessed at all. Bridges will be current because the regime requires it.

Then calculate what proportion of the network has condition data less than one assessment cycle old.

Departments doing this frequently find the figure lower than they assumed, and find that the capital plan is being driven by the asset classes that happen to have recent data rather than by the assets in worst condition.

A third quick exercise completes the picture. Take one street segment and assemble every repair cost over the last ten years.

Most departments cannot, and discovering that is the clearest demonstration of why work order cost capture matters.

All three use existing records, all three inform decisions regardless of procurement, and all three belong in any asset management discovery phase worth paying for.

What the Sprint Should Establish

Inventory Confidence

The audit above, extended across classes, with the proportion of attributes that are surveyed, derived, inferred or assumed. This sizes field verification, which is the largest budget item in the program.

Condition Currency

The age of condition data per asset class and the proportion of network within one assessment cycle. This determines what the capital plan can honestly rest on and what assessment program is needed.

The GIS Ownership Decision

Who holds asset geometry, who corrects it, how long a field correction takes to land, and which of the three ownership patterns the jurisdiction will adopt.

Established with the GIS group rather than decided for them, because this is the decision that most affects cost and goodwill.

The Prioritization Position

What model is currently used, whether anybody adopted it deliberately, whether it is published, and whether the governing body needs to act. Policy work a sprint surfaces rather than performs.

The Compliance Draw

Which reporting, permit and disaster obligations draw on this data, established with finance, the permitting authority’s requirements and the attorney. This frequently reveals that several teams are assembling the same information separately.

The obligations a sprint must establish are set out in GASB 34 Infrastructure Reporting, MS4 Stormwater Permit Documentation, FEMA Public Assistance Damage Records and Prevailing Wage Rules on Capital Work.

What the Director Receives

An inventory confidence report by asset class with the field verification scope and cost estimated, which is the largest line in the program.

A condition currency assessment with the assessment program required to reach and maintain a usable baseline.

A GIS ownership recommendation agreed with the GIS group rather than imposed on them.

A prioritization position with current practice documented and whatever governing body action is needed identified.

A compliance draw map showing which obligations use this data and who currently assembles each, which frequently identifies duplicated effort.

A deferral cost illustration on one asset class using the department’s own data, which is the business case and the artefact for a council.

A product evaluation against the established platforms, with geographic integration treated as the primary criterion.

A defined first release with exclusions written down.

And a costed comparison of at least three paths, adopt a product, adopt a product and build the planning layer, and build fully, with field data collection and recurring assessment shown as program lines in all three. The budget a sprint produces is detailed in Custom Public Works Asset Management Platform Budget Guide.

Reading the Recommendation

Adopt a product when it models your asset classes and its geographic integration fits your arrangement, which for most departments is the answer and where the maintained GIS relationship is the real benefit.

Adopt a product and build the planning layer when operations are well served but the capital planning and scenario capability the department needs is not expressible, which is a real and narrower outcome.

Build when asset classes are unusual, when a utility’s operational requirements are specific, or when the jurisdiction is building a shared municipal platform.

Collect data without new software when the audit shows the current system is adequate and the real deficit is that nobody knows what exists. That is a common finding and the cheapest path, since field verification helps whatever platform follows.

One consideration applies whichever path is chosen. The inventory confidence findings and any overdue inspection cycles are operational facts now, and the deficiency backlog if one exists deserves immediate attention for reasons beyond software.

A consultant who recommends collecting data before buying anything has given sound advice.

What a Consultant Should Know About This Department

Four questions establish whether a consultant has worked with public works.

Ask what the asset inventory actually is. A good answer uses the word confidence and distinguishes surveyed from inferred. Anyone treating a GIS layer as a record rather than a reconstruction has not worked with buried infrastructure.

Ask who decides the prioritization model. The answer is the governing body, published and applied consistently, with valuation and demographic proxies excluded. Anyone proposing an optimization default has made a policy decision they had no standing to make.

Ask what happens when a resident reports a hazard and nothing is done for a year. A consultant who understands this sector raises notice and liability immediately and says the record must be complete. Anyone proposing features to tidy old deficiencies should end the conversation.

And ask about the crew application. The right answer is that if crews find it awkward the cost data will not exist, which makes the field interface the project’s most important screen.

Red Flags in the Conversation

A sprint offered free and contingent on winning the build. A fixed price before the inventory is audited. Field data collection absent from the program budget. No conversation with the GIS group. Recurring condition assessment absent from running costs. No product comparison. Crew adoption treated as a training matter rather than a design one.

And the ones that should end the conversation: features to bulk-close, archive or suppress old deficiency records. Prioritization including assessed value, tax contribution or any demographic variable. Automated condition ratings presented as assessments. Any suggestion that software can clear an asset for service. And deterioration projections presented as forecasts rather than models.

The strongest positive signal is a partner who asks to ride with a crew for a day.

Conclusion

An asset management discovery phase starts with your own records: audit fifty assets and age your condition data before deciding anything, since both frequently show the deficit is data rather than software.

Settle the GIS ownership question with the GIS group early. And build the deferral cost illustration on your own asset class, because it is the business case and the only thing in this project a council will remember.

Apply the same questions to every partner, including the software companies in the United States who would like to build it.

If you are weighing a custom platform, auditing fifty assets to establish where each attribute came from is the week to spend before any vendor conversation.