Building a data governance council for a utility

Why utilities specifically need this

Utilities sit on data with three competing owners by design:

• Metering cares about the meter point: consumption, intervals, tamper flags.
• Commercial (billing, customer operations) cares about the customer account tied to that meter point.
• Grid operations cares about the physical asset: the transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète →, feeder, or substation the meter sits behind.

These three views describe the same real-world object but live in different systems: a Meter Data Management System (MDMS), a Customer Information System (CIS), and a Geographic Information System (GIS) or Asset Management System (often built on tools like IBM Maximo or SAP PM). When a field crew replaces a transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète →, someone has to update all three, in the right order, or downstream systems (billing, outage maps, load forecasting) silently drift apart.

No single team has authority to force the other two to fix their side. That is the governance gap.

What a data governancedata governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.Voir la définition complète → council actually is

A data governance council (sometimes called a data stewardshipdata stewardshipA business-side owner responsible for the quality, consistency and appropriate use of data in their domain.Voir la définition complète → board) is a standing cross-functional body with formal authority to:

1. Define who is the system of record for each data domain (the one authoritative source when copies disagree).

2. Approve or reject changes to shared data models (for example, adding a new "asset status" field that both GIS and CIS must respect).

3. Adjudicate disputes when two teams both claim ownership or both claim veto power.

4. Set data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète → thresholds and sign off on remediation plans.

This is distinct from IT governance (which manages systems and infrastructure) and from a compliance function (which manages regulatory obligations). The council owns the *business meaning and authority* over data, not the pipes it flows through.

Charter: the four things it must specify

A charter that skips any of these four elements will fail within a year.

1. Scope. Name the data domains explicitly: asset master data, meter point data, customer data, outage data. Vague scope ("all utility data") produces a council that never meets because nobody knows if their issue qualifies.

2. Decision rights. Use a simple RACI-style split (Responsible, Accountable, Consulted, Informed) per domain. Example:

| Domain | System of record | Accountable owner | Consulted |

|---|---|---|---|

| Physical asset attributes | GIS/Asset Management | Grid Operations | Metering, Engineering |

| Meter point status | MDMS | Metering | Commercial |

| Customer-to-meter linkage | CIS | Commercial | Metering, Billing |

3. Escalation path. Define what happens when the two accountable owners disagree, for instance grid operations says a transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète → is decommissioned but metering still shows active reads. The path typically runs: data stewarddata stewardA business-side owner responsible for the quality, consistency and appropriate use of data in their domain.Voir la définition complète → level (weekly working group) to council level (monthly) to executive sponsor (CIO, CDO, or COO) if unresolved after a set number of days, commonly 10 to 15 business days in mature programs.

4. Cadence and quorum. Monthly council meetings, weekly steward triage, defined quorum (for example, at least one accountable owner from each domain plus a compliance or privacy representative).

Roles: who sits at the table

• Chief Data Officer (CDO) or equivalent, chairs the council. A 2023 Gartner survey (a widely cited industry benchmark, figures approximate) found over 80 percent of large enterprises had appointed a CDO, though utilities lag other sectors in giving that role real authority.
• Data stewards, one per domain (metering, commercial, grid ops, asset engineering). These are working-level people who fix records day to day, not executives.
• Data owners, department heads accountable for the accuracy of their domain.
• Privacy/compliance representative, ensures decisions respect regulatory constraints (see next section).
• IT/architecture representative, non-voting in most models, advises on technical feasibility.
• Executive sponsor, breaks ties and owns escalations that the council cannot resolve.

Regulatory guardrails the council must respect

Governance decisions in the US and EU do not happen in a vacuum; they sit inside binding rules.

• NERC CIP (Critical Infrastructure Protection) standards, mandatory for US bulk power system owners, require documented access controls and change management for data tied to grid-critical assets. A council decision to "merge" two asset records must preserve the audit trail CIP-010 requires.
• State-level data privacy law, for example the California Consumer Privacy Act (CCPA), governs customer usage data (like interval meter reads that reveal occupancy patterns).
• EU General Data Protection Regulation (GDPR), for European utilities, treats granular smart meter data as personal data when linkable to a household, requiring documented legal basis and data minimization.
• EU Network Code / ENTSO-E data exchange rules govern how transmission system operators share asset and grid data across borders.

The council's escalation path should always route privacy-flagged disputes (does this dataset contain personal data, can it be shared across teams) to the compliance representative before a business decision is finalized. For a plain-language primer on the GDPR provisions most relevant to utilities, see the European Data Protection Board's guidance.

A worked example: resolving the transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète → dispute

Back to the 2 a.m. outage. Here is how the council process resolves it in practice:

1. Field technician flags the mismatch via a data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.Voir la définition complète → ticket.

2. Data stewards from metering and grid ops triage weekly: grid ops confirms via GIS that the transformertransformerA Transformer is a neural network architecture that uses self-attention to process sequences in parallel, powering most modern language and generative AI models.Voir la définition complète → was physically replaced in 2019; metering confirms its record still points to the old serial number.

3. Root cause: the decommissioning workflow never triggered an automated update to MDMS. This is a process gap, not a data entry error.

4. Council decision (per the RACI table): GIS is system of record for asset status, so MDMS must be corrected to match. But the council also mandates a system integration fix: decommissioning events in GIS must publish an automated event to MDMS going forward.

5. Executive sponsor approves budget for the integration fix within the next sprint cycle.

A simple check any analyst can run before escalating a dispute like this is a record reconciliation query:

This kind of reconciliation check, run on a schedule (daily or weekly), is the practical audit that feeds the council's agenda rather than replaces it.

Practical checks and audits the council should mandate

• Cross-system reconciliation audits, quarterly, comparing asset counts and statuses across GIS, MDMS, and CIS.
• Access log review, tied to NERC CIP requirements, confirming only authorized roles modified critical asset records.
• Data lineage documentation, tracing where a field like "meter status" originates and every system it flows through, so a dispute can be traced to its source in minutes, not days.
• Privacy impact assessments (PIAs), required under GDPR for high-risk processing, triggered automatically whenever the council approves a new use of granular meter data.

Key Takeaways

• A governance council's core job is assigning decision rights, not building dashboards: name a system of record for each shared data domain (asset, meter, customer).
• The charter must specify scope, decision rights (RACI), an escalation path with timeframes, and meeting cadence, or it will not survive contact with a real dispute.
• Route any dispute touching customer usage data through a privacy/compliance representative first; GDPR and CCPA both treat granular meter data as sensitive.
• NERC CIP standards require an auditable trail for changes to grid-critical asset records; council decisions must preserve that trail, not bypass it.
• Automate reconciliation checks (cross-system queries, access log reviews) so the council spends its time adjudicating genuine ownership conflicts, not chasing data entry typos.