The Meter Journal Display frame allows you to view a list of meter transactions for a particular Unit or Component. You can also filter by the Location Where the Meter Changed, the Meter Source, and between ranges of dates.
It can be useful to check this frame frequently to help catch errors in meter entries so can make the necessary corrections. You can correct meters on the Unit/Component Meter Entry screen.
To run a search, enter in the selection criteria you want to filter by and click the Retrieve button. The list of records will display in the i-frame below.
Each record will display the Unit/Comp Number, Location, Source (for example, W – Work Order, U – Unit/Meter Entry, V – Unit Asset Inventory, E – Commuter Usage), Primary Meter information, Secondary Meter Information, Application User, and Meter Updated information in a read-only format.
There are three flags at the end of each record, Meter Override, Ignore for Billing and Unit Rec Updated. The Ignore for Billing is the only flag that can be updated. If you want to ignore a certain transaction for billing purposes, check this box and click Save.
NOTE: large data-sets can cause display/performance issues, it is recommended to use additional filters to narrow your results to address any display issues.
The following steps outline how the M5 system determines whether an entered meter value is valid. Meter validity depends on multiple factors and conditions as well as the value/setting of certain system flags.
M5 compares the value in the Length field on MCC Main against the number of digits entered for that meter.
The system then calculates the maximum meter value based on meter size selected from step one.
For example: if the value entered in the Length field is 6, then 999999 is the maximum value.
So, If the meter being validated is 7 digits long, then the system will return an error message.
After the length check, the system moves on to see if the new meter is less than the current meter while the date value has advanced.
This is a possible rollover.
In other words, if the date is later, but the meter is less, is this a legitimate rollover? The next section - Check Meter Routine covers this in more detail.
Select the rollover percentage based on system flag values.
M5 uses the user-define rollover percentage from System Flags 1053 and 1074. See System Flag settings below.
Once the system has checked for a rollover, it looks to determine if the meter has exceeded the total amount of usage allowed based on the current meter reading, MCC min and max usages values, and total amount of time elapsed:
Rollover = Round((1# + (RollOver_PC * 0.01)) * (HighAllowMeter - OldMeter),
RollOver_PC is the value selected in step 4
HighAllowMeter is the value calculated in step 3
OldMeter is the value that was passed to this routine from the calling program
Check if current usage > the rollover value. If it is, then the system produces an error:
“This amount of usage {0} exceeds the allowable usage on a meter rollover for unit number {1}. The maximum usage allowed based on MCC maximum usage and time elapsed since the last meter reading is {2}. If the reading is valid, it must be entered in the Unit \ Use Cost History screen.”
Where {0} = the CurUsage value calculated in step 3 and {1} = the unit number and {2} = the rollover calculation from above.
The system uses the following criteria to process non-rollover meter entries:
NewLTDUsage = OldLTDUsage + (CurMeter - OldMeter)
CurUsage = (CurMeter - OldMeter)
OldLTDUsage is passed to this routine from the calling program
CurMeter is passed to this routine from the calling program
OldMeter is passed to this routine from the calling program
CurMeter can be either the new meters value itself or a calculation of CurUsage + OldMeter depending if we are processing meters as a reading value or a usage value.
Call the CheckMeter routine (See the CheckMeter section for more detail).
Determine if MCC information is available. This step is a good reason why users should always set meter limits on the MCC.
Note: If the MCC information was not available in the CheckMeter routine then report the following error:
"Warning! The Unit max usage, meter date, or last meter reading is missing. Meter check bypassed."
Determine if the new meter value is outside the system calculated average.
Note: If the HighAllowMeter (calculated in the CheckMeter routine) is > the new meter value then report the following error:
"Warning! The given meter reading of {0} is larger than the system calculated mileage of {1}."
Where {0} = new meter and {1} = HighAllowMeter.
The following is how the M5 System performs the CheckMeter Routine:
Select the maximum usage value from the MCC.
Select the current meter date and value for the unit/component.
If no existing date is found, use now.
If no existing value is found, use zero.
Select the value of system flag 1012 (number of fiscal periods).
Determine the number of days between the current meter date and the new meter date.
Calculate and return the HighAllowMeter value based on the data from steps one through four.
Note: HighAllowMeter = ((MaxUsage * Fiscal_PD * (DaysPast + 1)) / 365.26) + CurrentMeter
MaxUsage is the MCC max usage selected in step 1.
Fiscal_PD is the value selected in Step 3.
DaysPast is the value calculated in Step 4.
CurrentMeter is the value selected in Step 2.
The following flags are mentioned above and have impacts on how M5 checks for and validates meter entries:
1012 - Define the number of Fiscal Periods - The system provides for a fiscal year of either 12 or 13 periods. The Number of fiscal periods flag controls whether your fiscal calendar has 12 or 13 periods. It is recommended that the number of periods coincide with your financial systems.
1053 - Meter Rollover Limit % - This module flag is used to determine if a potential primary meter rollover is valid. If the usage being added by a meter rollover exceeds the maximum expected usage, as determined by the MCC of the unit, by more than the percentage denoted by this flag, this meter update will be rejected. For example, if the usage from this meter rollover = 1150 miles and the maximum expected usage, based on the MCC is 1000 miles and this flag is set to 10, the entry is rejected since 1150 miles is greater than 1100 miles (1000 + (.1 * 1000)
1054 - Secondary Meter Rollover Limit % - This system flag is used to determine if a potential secondary meter rollover is valid. If the usage being added by a meter rollover exceeds the maximum expected usage, as determined by the MCC of the unit, by more than the percentage denoted by this flag, this meter update will be rejected. For example, if the usage from this meter rollover = 1150 miles and the maximum expected usage, based on the MCC is 1000 miles and this flag is set to 10, the entry is rejected since 1150 miles is greater than 1100 miles (1000 + (.1 * 1000).
Last Update: 11/25/2020
NOTE: To view a list of System Flags and Role Privileges that may impact this screen, hover over the screen title in M5 to display the bubble help/tooltip. At the bottom of the bubble help/tool tip, there is a Settings hyperlink. Click that hyperlink to display the list of flags and privileges.
Additional training and technical documents on this subject may be available in the Resource Files area.