Skip to Content

Exchanges of Demand Meters and New Logical Registers

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.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Dec 30, 2010 at 07:50 PM

    We found a workaround, EG60 lets you map the new KW register to the same logical register as the old KW register. Billing then treats the account normally.

    Add comment
    10|10000 characters needed characters exceeded