Notes & signals from the network.
Field notes from the engineers moving utilities onto the Utility Network — plus the industry shifts, standards, and trends shaping where utility GIS is heading.
What a Utility Network Migration Actually Costs (And What's Actually Yours to Control)
The honest breakdown of what an ArcGIS Utility Network migration really costs a utility your size — what's genuine spend, what you already own, and why most quotes price a solved problem as if it were a mystery.
Which Utility Network data model should you start with?
One of the most common questions we hear from electric utilities is: "Which data model should we start with?" The short answer is that it matters far less than you think. The Utility Network is a platform, the Foundation and partner packages are just configurations on top of it — and whichever you pick, you'll reshape it anyway. Here's how to choose the starting line without mistaking it for the finish.
What Esri UC 2026 signals about AI in utility GIS
Esri's User Conference lands July 13–17 in San Diego, and the plenary is framed explicitly around ArcGIS enhanced with AI to automate workflows. For utility GIS teams, that one phrase is a signal worth reading before you're standing in the hall. Here's what the framing tells you about where the platform is heading — and the question it quietly hands back to you.
Utility Network migrations are taking too long
Esri's materials suggest a 3–6 month Utility Network migration. In reality most utilities take 12–18 months, and the established partners are spending years per project. It may sound like a hot take, but it's really a simple math problem — and the math says something has to change. Here's the throughput gap, the complexity trap that created it, and the lens that gets you live in months instead of years.
Trust, but validate: putting AI agents near regulated utility records
Esri just shipped a Trusted AI tab and transparency cards to the ArcGIS Trust Center — and still tells you to validate every AI result before you decide. That tension isn't a bug. It's the whole job. Here's how agent work near regulated records stays human-checked and audit-ready by design.
Migration ends. The bad edits don't.
Everyone sells the cutover. The industry quietly admits the truth: projects stumble after go-live, when editors start touching a live network and bad edits silently corrupt connectivity. That's not a migration problem — it's a forever problem. And it's the strongest AI argument for a durable business: always-on agents that validate the network continuously, catching bad edits before they break it.
Dirty data is the real deadline
Every AI migration demo maps a clean schema in ninety seconds. Real migrations don't die on schema — they die on data quality, the months of analyst cleanup the demo never shows. "Agentic data quality" is having a moment for exactly that reason. Here's the reframe: AI isn't a mapping toy, it's the thing that compresses that cleanup from months into days.