Every interval a smart meter records should accurately reflect consumption. Most of the time it does. But meters lose communication, malfunction and clocks drift. If incorrect data flows straight to billing, the utility will hear about it. AMI (Advanced Metering Infrastructure) systems are not infallible. That’s why VEE exists.
VEE stands for validation, estimation and editing, the three-step process that turns raw meter data into data a utility can bill against, report on, and defend if a customer or regulator has questions. But VEE is not a standalone piece of software: it’s a core function of a meter data management (MDM) system, which sits between an AMI headend and the billing system.
What VEE Actually Does
VEE has three jobs.
Validation: each read is checked against a set of rules: Is the value within the expected range for that meter and time of day? Did the read arrive on schedule? Does it match the meter’s own diagnostic flags? A read that fails validation is not deleted or billed as-is. It is flagged for the next step.
Estimation: this fills the gap left by a faulty or missing read. Rather than leaving a blank interval or, worse, letting a zero-usage read slip through to billing, VEE generates a defensible substitute value based on that specific meter’s historical usage pattern, adjusted for day of week, time of day, and other factors. Estimation can tell the difference between a vacant summer cabin and a house that simply lost communication.
Editing: this is where a human enters the process. The MDM system routes estimated and borderline values to staff; they can review estimations, override if necessary and document why. Every override is time-stamped and attributable, which matters when a customer disputes their bill.
Why VEE Matters More Than May Be Apparent
The volume of data involved in this process is massive. According to recent EIA data on U.S. smart meter installations, U.S. electric utilities had roughly 119 million AMI meters installed as of 2022, and that number has grown every year. Each of those meters can generate 24, 48, or even 96 readings a day depending on interval length. A mid-sized utility with 15,000 AMI meters on 15-minute intervals is processing more than a million readings a day. No billing team can eyeball that volume manually, which is exactly why validation and estimation must be automated, and why the editing process must be efficient enough for staff to keep up.
Electric cooperatives, which tend to serve lower-density territories with long distribution lines, have embraced AMI even faster than the rest of the industry. NRECA’s latest analysis of cooperative AMI deployment found that 87% of cooperative meters are now on AMI, compared to 83% for the rest of the industry, with cooperatives adding an average of roughly 1.1 million AMI meters a year since 2013. For any utility the challenge is the same: more meters on shorter intervals means more data, and more data means VEE becomes crucial to ensuring all that data results in an accurate customer bill.
For municipal utilities, VEE is important when budget season arrives and staff must justify rate decisions to a city council or utility board, or when they respond to a public records request: the data behind those numbers needs to hold up. Estimated values that are documented and defendable make that possible.
What Good VEE Looks Like in Practice
Consider a meter that misses its scheduled read for a six-hour stretch because of a network outage, not a problem with the meter itself. Validation flags the gap immediately. Estimation fills it using that meter’s own load profile to produce a value close enough to actual usage to bill on with confidence. The interval is marked as estimated in the record, so if the actual usage turns out to differ meaningfully once communication resumes, the discrepancy is visible rather than silently absorbed into the bill. A billing analyst reviewing the exception queue sees the flag, confirms the estimate looks reasonable and approves it in seconds.
Common VEE Gaps to Watch For
Watch for validation thresholds that are set once and never revisited. Thresholds that are too loose let bad data through while thresholds that are too tight flood staff with false exceptions.
Estimation that ignores account-level history is another: generic estimation formulas that do not account for a specific meter’s own usage pattern.
Manual overrides with no audit trail. If an analyst can change a value with no record of who made the change, it undermines accountability, which in turn undermines credibility.
Inside Meter Data Management
CentralView[1] MDM provides a robust and flexible VEE capability and is compatible with every major AMI provider. CentralView MDM supports electric, water, and gas metering. For a broader look at what MDM covers and how it fits into a utility’s overall technology stack, see What Is Meter Data Management? A Complete Guide for Electric Cooperatives.
See CentralView MDM’s VEE Capability
[1]CentralView is a Central Service Association (CSA) trademark.