Alerts when a meter is forced into e-automate from Remote Tech.

Jump to a specific section by clicking a link

Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts

 

Click to Subscribe

 

Overview

Overview

One of the ongoing challenges with meter readings is having service call meters come into the meter tables and override a contract billing meter reading that has been obtained, which then upsets the customer who expects you to use the meter reading they reported, not the latest.  So, the best practice is to have all service call meters come in as Not Valid for Billing.  That solves the customer-reported vs. service call meters that overlap in the billing cycle. This alert will trigger when the service tech forces a meter reading into e-automate via Remote Tech. You can then review these meters and decide if they should be updated to be valid or left as is.

 

*Nov 2020 - This alert does NOT work for MobileTech clients.  MobileTech does not have a data point available to indicate that the meter is forced, and therefore, this alert will not trigger.

 

Run Schedule:  Daily in the afternoon

Type of Output: Email

*  *  *

Sample

Sample

The previous meter on the email is the most recent non-estimated meter. The meter on Call is the meter that needs to be validated in e-automate.

 

*  *  *

Variables

Variables

Variable W: Branch Numbers - List the branch numbers for the alert to trigger on. Leave blank for all branches.

 

*  *  *

Alert Functionality

Alert Functionality

1. The option to have service call meters come in as not billable is set in Options - Service Calls:

When this option is unchecked, the meter reads that have a source of Service Call will not have the option to use the meter for billing checked:

2. When a meter reading is outside of the acceptable validation buffer, then the technician has to force the meter into the system.   When this happens, the meter goes into the system as invalid so that it is not used for billing.  The alert will allow someone to verify this meter so it can be used for billing. 

3. The technician indicates that the meter is forced by adding "Force" to the remarks on the meter reading:

4. The meter validation buffer is used to set the acceptable meters that can be entered. When the meter is outside of this buffer, the technician must force the meter when it is required.

The buffer is set under options and equipment.  This is the amount of difference between the meter entered and the expected meter.  This prevents extra-large meter readings from being entered by mistake.

 

5. When you get the email, open the meter reading console in e-automate and review the meter.  If the meter is truly a good meter, check the “This is a valid Reading”. If you wish to use the meter for billing purposes, click the "Use this reading for billing purposes." Click OK to save your changes.

 

*  *  *

 

Best Practices & Tips

Best Practices & Tips

We suggest starting by setting your meter validation buffer at 60% and see if it catches true errors without too many unneeded warnings, and increasing it if needed. The lower this threshold is set, the higher the number of warnings you'll see when users are entering meter reads.

*  *  *

Related Alerts

Related Alerts

ID409 - Report of contract invoice meter billings where there were two or three consecutive estimated meters used for billing.

ID550 - Takes new meter readings and compares to volume trend for sanity check.

ID556 - Same meter billed Variable W number of times.

 

*  *  *