The energy sector has a characteristic that few other sectors share: measurement is already happening continuously. Metering data from smart meters, production figures from proprietary assets, consumption data from installations, emission factors that differ per energy carrier and per source. Where a service provider elsewhere still has to find out whether data exists at all, an energy company often drowns in data that already exists. The question is not so much whether the figure exists, but which of the five systems recording it is the correct one, and whether those five systems use the same definition of a unit of measurement.
That is a different pitfall than in sectors where sustainability data has to be retrieved from external parties. Here the problem lies in abundance and fragmentation: SCADA systems, meter data management platforms, ERP for the financial side, separate spreadsheets for scope 3 estimates from the chain. Each system has its own view of what a data point means, and no one has documented which source belongs to which reporting point.
Within energy companies, two types of data run through each other that do not share the same origin. Production and consumption data usually come from operational systems that were primarily built for business operations, not for reporting. Emissions data, on the other hand, is often calculated after the fact, with conversion factors that differ per source, per year and per reporting framework. Most of the discussions about data quality in this sector are not about the measurement itself, but about the translation from measured value to emissions figure: which factor, which source period, which assumption.
That makes lineage especially important here. A figure in the sustainability report labelled "total CO2 emissions" may be composed of a meter reading, an emission factor from an external database, and a manual correction in a spreadsheet. Without a documented origin per step, it cannot be determined whether a deviation from last year is a change in production, an adjusted factor, or an error in the handover between systems.
In energy companies, the data rarely sits with a single department. Operational metering data falls under asset management or the technical department. Financial and consumption data falls under finance or controlling. Scope 3 estimates from suppliers and customers often sit with procurement or with the sustainability department itself, which does not produce this data itself but must still account for it. Who owns a data point is therefore not a technical question but an organizational one: who can explain the origin, who can process a correction, who signs off on accuracy.
This distribution of ownership also appears in other sectors with many technical assets. The similarities with where sustainability data sits in construction are greater than expected: there too, metering data sits with a technical department and emissions data with a separate function, with little coordination between the two. In the installation sector, a similar pattern plays out, where operational data about installations is disconnected from the reporting cycle that is later assembled from it.
An energy company that purchases a reporting tool for this fragmentation gets a tidier dashboard over the same unclear origin. The dashboard shows a figure, but the question of whether that figure comes from the correct meter, has been reconciled with the correct factor, and has been checked by the correct person, remains unanswered. The tool adds a layer on top of the problem, not a solution to the problem.
What does help is first documenting which data point comes from which source, through which intermediate steps it reaches the reporting point, and who is responsible for each step. That is a register, not a dashboard: a list of data points with their origin, their owner and the rules against which quality is tested. Only once that is in place does a reporting tool have something reliable to build on.
Energy companies with multiple divisions — production, distribution, retail — face an additional complication: the same term means something different in each division. "Consumption" at distribution is a different figure than "consumption" at retail. For this question, it is worthwhile to look at which data points are actually needed when multiple business units report, and at where a data point may already exist at another business unit before it is built up again. Reusing an already existing, validated source is often faster than setting up a new measurement.
Once the data point register is in place — with origin, owner and quality rule per point — visibility also emerges into the work behind it: who collects, who checks, who corrects, and how much of those steps are routine. At that point, the [work scan](https://ftetoai.com) by FTE TO AI becomes relevant: it calculates per task which part of the work can be taken over by AI, based on the tasks that emerge from the data point register rather than on an upfront estimate.
The Data Readiness Scan for the energy sector is in development. Anyone who wants to have the data point register built for their own organization as soon as it becomes available can sign up for the waiting list.
Vraag maar waar een datapunt vandaan komt. Dat is meestal de hele vraag.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.