We've recently found that certain demand meters aren't billing correctly after an exchange (replacement).
Common theme is that the new meter has a different register group than the old meter, and the system is creating new logical registers, rather than timeslicing the original logical register , which is what happens when the register group stays the same.
Problem is then in billing, which treats the 2 logical registers separately and is combining the demand reads together, rather than selecting the highest value.
Is this a bug, or is there a configuration change that could be made to force billing to correctly select the highest value, rather than adding the reads together.
Thanks
Astrid
