What actually happens, stage by stage
Every engagement runs the same five stages in the same order. Each one produces something concrete — a report, an agreement, a validated dataset — that you read and approve before the next stage starts.
Scoping call
Thirty minutes with an engineer rather than a salesperson. We establish which domain you run, what system holds it today, roughly how large the network is, and what has to be true for the migration to count as finished. No data changes hands at this stage, and nothing obliges you to continue.
A written scope summary in your workspace, and a straight answer on whether an assessment is worth doing.
Readiness assessment
You send a copy of your geodatabase — a copy, never a connection to a production system. We read the model and the data behind it, then measure fit against the Utility Network: which classes carry across cleanly, which need rework, and where the data itself will fight the migration. Every figure traces back to a count you can reproduce.
A readiness report with model fit by asset family, data quality findings, and the counts behind each of them.
Agreement
Scope, terms and price live in the workspace as a document you can comment on line by line. A question resolves against the clause that raised it, so the answer stays attached to the text instead of scrolling away in an inbox. When both sides are satisfied, signing happens in place.
A signed agreement, the comment thread that shaped it, and a record of who agreed to what and when.
Migration
Engineers direct an agent workforce that runs against a copy of your data. Every run is followed by validation passes, and anything that fails lands in a triage queue rather than a summary paragraph. You watch the runs, read the failures and see the fixes while the work is happening.
A migrated dataset, validation results for every run, and a triaged list of everything that needed a decision.
Maintenance
A network is not finished at go-live — it changes as crews build. Continuous validation keeps running after handover, so model drift and new data quality problems surface while they are still small. The workspace keeps the history, which means the reasoning behind the original build is still readable when someone asks about it.
Ongoing validation results, and the full record of how your model was built.
Start at stage one
A thirty-minute scoping call with an engineer. No data, no commitment.
Book a call →