Scope you can explain in public and defend in an audit
You do not answer to shareholders. You answer to the people who live on the lines you maintain, and to the local government that approves what you spend on them. That makes a defensible record less of a compliance exercise and more of a civic one.
Municipals
A municipal utility runs on a public budget, in public, with a staff sized for steady state rather than for a migration. Every one of those three facts shapes what a good project looks like.
The budget is public and annual
Funding moves through the annual appropriation, revenue bonds or a state revolving fund — and in many utilities a board of public works signs off before elected officials ever see it. Scope that cannot be explained in a public meeting does not get approved, however good it is.
The record is a public record
State public-records laws and open-meeting rules mean your data can be requested by anyone. What you hold has to be legible to a resident, not just to a GIS analyst.
There is no bench
A two-person GIS team cannot absorb a migration on top of daily work. If the project depends on your staff being free, it will slip.
What an inaccurate model actually costs you
For a municipal utility, an inaccurate model shows up first as a dig that hits something nobody mapped, and second as the public meeting where you explain it. Locate tickets, capital planning and emergency response all read the same dataset, and none of them tolerate a guess. We measure model fit before commitments are made, and the assessment gives you counts you can stand behind in public without qualifying them.
The migration is capital. The savings are operating.
The migration is a defined capital item, scoped and priced up front so it survives a budget cycle. The readiness assessment stands alone: even if the migration waits a year for funding, you keep a measured view of your data.
After go-live the cost is operating, and it lands on a staff that is already full. A model that stays correct is the difference between GIS being a service your crews trust and a system they work around with a paper map.
Most migration vendors finish at go-live, which is the moment the model starts drifting. Ours is built to be maintained afterwards — continuous validation against the same checks the assessment ran, so the accuracy you paid for in capital is still there in year three.
The record has to survive being read by someone else
- State one-call and damage-prevention obligations, which depend on knowing where the asset actually is
- State public-records and open-meeting laws, under which the dataset itself may be disclosable
- Grant and state revolving fund reporting, where the asset inventory has to match what was funded
We do not file on your behalf and we do not sell compliance. What we do is make the underlying data defensible enough that the people who do file are not guessing.
Other ownership models
Scope you can explain in public and defend in an audit
Thirty minutes with an engineer who has read a network like yours. No data, no commitment.
Book a call →