This Documentation relates to 3.5.
If you are using a different version, please view the Documentation for All Versions and select the relevant version.
It is not uncommon to have situations where the units of measure change over the billing history of a given meter. An example would be a water meter where the initial billing data was provided in gallons (GAL) and then at some point in time, the utility vendor decided to change the billing units to kilo-gallons (KGAL). This billing change is accommodated in EnergyCAP by making a change to the bill entry template being used to hand-key the data. This change has no impact on reporting or viewing data at the building level or what is commonly referred to as the rollup level; however, the same cannot be said for viewing the usage trends and power views at the meter level. Rollup data is always converted to a common unit of measure to ensure clean data presentation and comparison. Meter level data is always presented in "native" units of measure, meaning the units of measure in which they were entered into EnergyCAP.
The EnergyCAP unit system has a feature built-in to identify and offer the option to convert the historical "native" units to be the same unit of measure for the entire billing history.
The following discussion presents a scenario in which a water meter has units of measure on historical bills that are not the same as the assigned bill template. First we will review the data presentation issues that can result when a meter has mixed units of measure. Then we will walk through the steps to address the mixed units and generate more consistent power views. The previous image highlighted a water meter in which the message field indicated there were "12 bills found where Usage units (Gal) are not equal to units on current template (FD_KGAL_A_N_01)". When viewing the meter bill ledger it is easy to see that there was a drastic change in how the billing data was entered between Dec 2015 and Mar 2016.
The meter Trends Power View clearly shows that the units of measure were not consistent throughout the billing history. This results in making the Trends Power View ineffective for evaluating monthly trends in use per day and unit cost analysis.
If we go back to the Mixed Units of Measure table and select the "Convert Bill History" option, all of the historical bills are updated such that the "counted" usage values are converted to match the units of measure of the current bill template. The original usage value and unit of measure is recorded as an "info-only" line item on the historical bill so that the original entry is not lost and any modifications are clearly visible for record review.
Once the historical bills have been converted to coincide with the current bill entry template, the meter bill ledger and the Trends Power Views reflect the expected data presentation and allow for use and unit cost analysis.