Infrastructure data problems rarely announce themselves. They accumulate quietly for years — a paper as-built filed away instead of digitized, a GIS layer updated by one crew but not shared with another, an attribute field left blank because nobody agreed on what it should contain. None of these feel like a crisis when they happen. The crisis arrives later, at the worst possible time.
It arrives when an outage happens at 2am and the control room is working from a map that hasn't been updated since 2018. It arrives when a regulator requests documentation of a pipeline segment and the answer requires three weeks of manual archive searching. It arrives when an engineering team designs a capital project on baseline data that turns out to be incomplete, and the contractor finds the discrepancy mid-construction.
In my 25 years working with Canadian utilities, I watched this pattern play out repeatedly. What changed was how explicitly Canadian utilities — under pressure from provincial regulators and increasingly demanding safety legislation — were forced to confront the problem and build systems to prevent it. Mexico's utility sector is at an earlier point in that arc. But the pressure is building faster than most organizations recognize.
What the records problem actually looks like
Most utilities don't have one records problem. They have several, layered on top of each other, each one masking the others.
The digitization gap. A significant portion of infrastructure records at most Mexican utilities still exists only on paper — as-builts, field redlines, inspection logs, construction drawings. This paper lives in physical archives, often in varying condition, often incompletely indexed. When it needs to be found, it requires a human who knows where to look. When that person retires, the institutional knowledge goes with them.
The maintenance gap. Even where digital records exist, they tend to drift from reality over time. Construction crews complete work and submit paper redlines. The redlines sit in a queue. The GIS gets updated weeks or months later, if at all. Over years, the accumulated lag between what's in the ground and what's on the map becomes a serious operational problem.
The governance gap. The most fundamental problem, and the hardest to fix: nobody owns the data. Every department has opinions about it, but no single role has accountability for its accuracy, completeness, or currency. Without clear ownership, every other fix is temporary.
The map that nobody trusts is not a technology problem. It's an organizational problem wearing a technology disguise.
Why Mexico's utilities are particularly exposed
Several forces are converging that make the records problem more urgent than it's been in the past.
Grid reform and private participation. As Mexico's energy sector continues its evolution, utilities face increasing scrutiny from regulatory bodies, private investors, and international partners. All of these audiences want data they can trust. Reliable infrastructure records are no longer just an operational nicety — they're a prerequisite for regulatory compliance and investor confidence.
Renewable interconnection. Integrating distributed generation — solar, wind, small hydro — into existing grid infrastructure requires detailed knowledge of network topology, capacity, and condition. Utilities with poor spatial records are discovering that they can't answer basic interconnection questions without commissioning expensive field surveys.
Urbanization pressure. Mexico's cities are growing. The infrastructure underneath them is aging. Expansion and rehabilitation projects require accurate baseline data to design efficiently. When the baseline is unreliable, projects cost more and take longer — or fail entirely.
Damage prevention and locate programs. As one-call and locate programs formalize in more Mexican jurisdictions, utilities face increasing liability for locate accuracy. A locate issued from incorrect GIS data is a compliance problem and, more importantly, a safety problem.
What it actually costs
The cost of poor records is diffuse, which is partly why it's tolerated so long. It doesn't show up on one line item. It shows up in:
- Extended outage restoration times, when field crews can't confirm asset locations from the map
- Locate errors and the damage claims that follow
- Regulatory penalties and audit failures
- Capital project cost overruns caused by inaccurate baseline data
- Duplicate survey and inspection work, because the existing records can't be trusted
- Engineering rework, when design assumptions don't match field reality
None of these costs is trivial. Most utilities experiencing them attribute them to other causes — project complexity, contractor performance, regulatory overreach. The records problem stays invisible until someone does the arithmetic.
The Canadian precedent
Canadian utilities spent much of the 2000s and 2010s working through exactly this problem. The drivers were different in their specifics — provincial pipeline safety legislation, damage prevention liability under the Canadian Common Ground Alliance framework, Ontario's One Call Act — but structurally identical. External pressure forced utilities to confront records problems they'd been deferring for years.
What emerged from that period was a set of methodologies, governance frameworks, and operational practices that have since become standard in the Canadian industry: UPDM-aligned data models, disciplined as-built workflows, locate management programs with audit trails, mobile GIS for field capture. None of this was invented from scratch. It was developed under pressure, refined through implementation, and documented so it could be repeated.
That body of practice is directly applicable to the challenges Mexican utilities face today. The regulatory context is different. The workforce is different. The technology landscape has, if anything, improved. But the underlying problem — infrastructure records that nobody fully trusts — is the same problem Canadian utilities solved. The playbooks work. The question is whether they get applied with sufficient discipline, and whether the knowledge transfers to the internal teams who will own the systems long after any consulting engagement ends.
Where to start
The most common mistake is to start with technology. A utility buys an ArcGIS Enterprise license, stands up a Utility Network, and then discovers that the data going into it is too unreliable to support operations. The technology is fine. The problem is that nobody fixed the underlying records problem before expecting the software to solve it.
The right starting point is assessment. Before any technology decision, a utility needs an honest answer to four questions:
- What percentage of our infrastructure records exist in a reliable digital form?
- How large is the gap between our GIS and what's actually in the ground?
- Who is accountable for data quality, and what does that accountability actually mean in practice?
- What are the workflows that create and maintain records — and where do they break down?
A structured GIS data audit answers these questions with enough specificity to build a remediation plan and a realistic budget. It's the difference between a modernization program that succeeds and one that produces an expensive map that nobody trusts.
The records crisis in Mexican utilities is real, it's measurable, and it's solvable. But it requires treating the governance and workflow problems as primary, not as afterthoughts to the technology procurement.