|Mike Hyde's Special Projects|
Once I figured out how to ping meters, and read the results via SQL, I started creating routines.
One routine is "Re-Read Failed Meters."
This is a web page that sends out a read command to all meters in the AMRCOMMFAIL table.
It lists them in order, by Sub/feeder/phase, so it helps give a good indication of there is a problem related to a specific path.
From that page, clicking on the serial number initiates a TCT ping on that meter.
Clicking on the location ID brings up the account in UPN-WEB.
I used to run this several times in the morning.
When everything is working as it should, all the meters generally return a read after a few attempts.
I decided that this process could be automated, so a scheduled task runs this page once, starting at 3:00 AM, then reruns every 30 minutes for 8 hours.
By having this start automatically before I arrive at work, I know most of the rereads should be taken care of.
I usually kick this off a few more times when I arrive in the morning.
Next, I submit a path map search on the remaning failed meters.
I used to do this thru TNS, but now submit the search by clicking on a link at the bottom of the page.
I monitor the search process by watching the "APM Search Process" page.
Once the searches are done, I look to see how many were successful, which are founds on the "Recent APM Search" report
If any meters have researched, I kick off the "reread failed meters" again.
I also look at the failed pings, failed reads and current open Service orders on DAS Map.
This provides a graphical view. The remaining failed reads are looked at on a case by case basis. The following is considered for each.
After all the options are considered, a miscellaneous Service Order, for "TWACs not reading" is created, and sent to either the serviceman for the area, or to a Customer Service Field Rep (CSFR), depending ion availability, via UPN-WEB.
Essentially, if a meter has not read by 10:00, under normal circumstances, a CSFR will be visiting.
The usual finds are: