Big find in Sacramento. Shopping center client, SMUD Rate GS-TOU3. Demand has been consistently high ? 340-380 kW ? for a 45,000 sq ft strip mall that should be running maybe 180-200 kW based on connected load analysis. Pulled the meter data and found the meter multiplier is set to 2.0 when it should be 1.0. The CT ratio is already accounted for in the meter programming ? the additional 2x multiplier is doubling every reading. This error has been in place for at least 3 years.
Meter multiplier error inflating demand readings by 2x
Barbara ? SMUD meter multiplier errors are more common than people think. I found one in Fresno on a PG&E account last year where the multiplier was set to 4.0 instead of 2.0 because the CTs were replaced during a panel upgrade and the meter was reprogrammed incorrectly. The demand readings were double what they should have been for 18 months. PG&E refunded $47,000.
Phyllis ? exactly the same scenario. CTs were replaced during an electrical upgrade 3 years ago and the meter reprogramming carried over an incorrect multiplier. I calculated the overcharge at approximately $62,000 over 36 months for both demand and consumption. Filed the claim with SMUD last week.
This is why I always request the meter configuration data as part of every audit. The meter face reading, the CT ratio, the programmed multiplier, and the billing multiplier should all reconcile. If any of those numbers dont multiply out to match the billed demand and consumption, youve found an error.
Barbara ? how are you getting the meter configuration data from SMUD? In Spokane, Avista wont provide their meter programming data without a formal written request under our states utility records access statute. They treat it as proprietary equipment configuration.
Ruth ? SMUD has been cooperative. I submitted the LOA and specifically requested the meter test report and configuration data. The meter test report includes the programmed multiplier. Took about 3 weeks to get it. Some utilities provide it readily, others require formal requests. Always include meter configuration data in your standard LOA request language.
From the engineering side ? the way to independently verify the multiplier is to compare the meter nameplate CT ratio with the billing determinant. If the meter is on 400:5 CTs (ratio = 80) and the billing multiplier should be 80, but the bill shows a multiplier of 160, thats your 2x error. You can see the CT ratio stamped on the physical CTs during a site visit without needing utility cooperation.
Update: SMUD acknowledged the error. Theyre refunding 36 months which is their maximum lookback period. Total refund is $58,400 ? slightly less than my $62,000 estimate because they applied a different rate for one of the 36 months due to a tariff change. Client is thrilled. My contingency fee on this one finding alone covers my annual income target.
Barbara ? $58,400 from a single meter multiplier error. This is why demand charge auditing is so lucrative. The error is binary ? the multiplier is either right or wrong ? and when its wrong the financial impact compounds every single month. Nice work.
Outstanding find and excellent documentation of the process. Meter multiplier errors affecting demand charges are among the highest-value single findings in utility bill auditing. Barbaras approach is textbook: 1) Notice demand seems high relative to connected load 2) Request meter configuration data 3) Identify the multiplier discrepancy 4) Calculate the overcharge period and amount 5) File the claim. Vernon and Hectors tips about physical CT verification and common error triggers are valuable additions. Every auditor should include meter configuration verification in their standard audit protocol.
Former TVA operations manager here. Meter multiplier errors happen most frequently after three events: 1) CT replacement during electrical upgrades, 2) Meter change-outs during AMI deployment, 3) Account transfers when a new customer takes over a metered service. The new meter or CTs get installed correctly but the billing system gets programmed wrong. Always verify the billing multiplier matches the physical installation.