Is there a preferred method to prevent electric meter readings that are wildly out of line from the prior/following averages from being recorded in PI?

We use Schneider StruxureWare for metering, and occasionally we'll get a reading that is orders of magnitude out of line with the prior and following averages. For example 15 minute kWh readings for the prior hour might be 686.65, 683.56, 671.37, 576.15, and then 125424.57, followed by 1360.94, 1722.31. I've seen some readings spike to 1 million kWh higher than the prior and following readings.

What I'd like to happen is that either the prior reading or an average of the prior and following 'normal' readings would be recorded to ignore the spike. The end result is that I need a monthly cumulative/odometer total for the energy use for the meters at our installation that removes the obviously invalid/spike readings.

In a related question: is there a desired method of handling meter rollover and for handling if a meter is reset/replaced and begins in the middle of a month with a zero value?

Thanks!

Myron