# Running a data audit before a regulatory filing
Three weeks before a demand-response performance filing, an analyst at a mid-size utility discovered that 12% of the interval meter data feeding into the baseline calculation had been silently backfilled by a vendor's estimation algorithm, and nobody had documented it. The filing deadline did not move. The audit trail did.
This is the scenario every energy company faces before submitting demand-response (DR) performance data, capacity verification reports, or emissions disclosures to a regulator. DR programs pay customers or aggregators to reduce electricity use during peak periods, and the payment depends entirely on measuring a "baseline" (what usage would have been) against actual usage. If the underlying data cannot be traced, defended, and reproduced, the filing is exposed.
In the US, the Federal Energy Regulatory Commission (FERC) and regional grid operators like PJM, ERCOT, and CAISO require utilities and demand-response providers to submit performance data that supports capacity and energy market settlements. FERC Order 2222 (2020) opened wholesale markets to distributed energy resources, which multiplied the number of data sources feeding these filings, aggregators, meter vendors, third-party measurement and verification (M&V) firms.
In Europe, the EU's REMIT (Regulation on Wholesale Energy Market Integrity and Transparency) requires transaction and fundamental data reporting to ACER (the EU Agency for the Cooperation of Energy Regulators), and national regulators like Germany's Bundesnetzagentur or the UK's Ofgem run separate DR and flexibility market oversight. 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 → failures here are not abstract: misreported data can trigger financial penalties and, in repeat cases, suspension from market participation.
A pre-filing data audit is not a spot check. It is a structured walk from raw source to submitted number. Six steps matter most.
Data lineageData lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète → means the documented path a data point takes from its origin (a smart meter reading) through every transformation to its final form in the filing. For DR filings, lineage typically runs: meter → utility meter data management system (MDMS) → aggregator platform → baseline calculation engine → regulatory report.
Ask: can you point to the exact system and timestamp where each number was created, and every place it was touched afterward? If the answer requires guessing, the lineage is broken.
A simple but powerful check: count the number of meters, intervals, or customer accounts at the source and compare to what appears in the final filing.
source_meter_count = 4,850
filing_meter_count = 4,806
missing = source_meter_count - filing_meter_count = 44Forty-four missing meters is not automatically a problem, but it must be explained (decommissioned meters, opted-out customers, 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 → exclusions). An unexplained gap is a lineage failure waiting to be flagged by a regulator's own reconciliation.
Estimation, interpolation, and outlier removal are normal in meter data pipelines, smart meters occasionally miss intervals due to communication failures. The problem is not the transformation itself, it is the absence of a record.
Every transformation should log: what rule was applied, when, by what system or person, and why. A common failure mode: a vendor's estimation algorithm silently fills missing intervals using a default method, and the utility's internal team never sees a flag distinguishing "measured" from "estimated" data. Regulators increasingly ask for this distinction explicitly. PJM's Demand Response Operations manual, for example, requires baseline methodology disclosure precisely because estimation choices materially change settlement amounts.
DR baselines are typically calculated using methods like the "10-in-10" (average of the highest 10 usage days out of the prior 10 similar days) or regression-based weather-normalized baselines. Confirm the same methodology version was applied consistently across the entire filing period.
A frequent error: a mid-year software update changes a rounding rule or a weather-adjustment coefficient, and half the filing period reflects the old method while the other half reflects the new one. This is a governance issue, not just a technical one, someone approved the change without triggering a data recheck.
Cross-check filing data against an independent source: interval data from the wholesale market operator's settlement system, weather station data from a public source like NOAA's Climate Data Online, or third-party M&V reports. Discrepancies above a defined threshold (commonly 2 to 5%, though this varies by program) should trigger investigation before submission, not after a regulator's audit finds it.
The audit needs its own record: who ran which checks, when, what was found, what was remediated, and who signed off. This is the artifact that demonstrates good faith compliance if a regulator later questions the filing. Under frameworks like REMIT, the ability to reconstruct not just the data but the review process is itself part of demonstrating compliant conduct.
Vérification des acquis
1. Why does silent backfilling of interval meter data by a vendor's estimation algorithm pose a serious risk to a demand-response performance filing?
2. What is the primary reason FERC Order 2222 increased the data governance burden for demand-response filings?
3. A DR baseline determines payment by comparing actual usage to 'what usage would have been.' Why does this make pre-filing data audits especially critical compared to a simple actual-usage report?
4. Select ALL correct answers about the regulatory context for energy data filings described in the lesson.
Sélectionnez toutes les réponses correctes.
5. Select ALL correct answers about why a pre-filing data audit should be described as a 'structured walk from raw source to submitted number' rather than a spot check.
Sélectionnez toutes les réponses correctes.
A clean audit depends on clear ownership, not just a checklist.
One underrated tool: a maintained data dictionary, a document defining every field in the filing (source system, unit of measure, calculation method, owner, last review date). When a regulator or auditor asks "how was this number derived," the answer should be a lookup, not a scramble. FERC and European regulators alike have increasingly cited the absence of clear field-level documentation as a contributing factor in enforcement actions, because it signals the filer itself may not fully understand its own submission.
🎬 [VIDEO: "Data LineageData LineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète → Explained" - youtube.com - a concise walkthrough of what data lineagedata lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète → means in practice and why it matters for audit and compliance work]
Penalties vary widely by jurisdiction and severity, and figures should be treated as illustrative rather than universal. FERC has authority to impose civil penalties for market manipulation and reporting violations under the Federal Power Act, with maximum statutory penalties in the range of roughly $1.4 million per violation per day (this figure is periodically adjusted for inflation, so treat it as an estimate and check FERC's current guidance). ACER and national European regulators can refer REMIT breaches for penalties determined at the member-state level, which vary considerably by country. The exact dollar or euro figure matters less than the underlying lesson: penalties scale with the number of days and the number of affected data points, so a lineage gap discovered late is far more expensive than one caught in a pre-filing audit.