My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
6.1. ERMUSR 09-15-2010
ElkRiver
>
City Government
>
Boards and Commissions
>
Utilities Commission
>
Packets
>
2003-2013
>
2010
>
09-15-2010
>
6.1. ERMUSR 09-15-2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/10/2010 1:01:58 PM
Creation date
9/10/2010 1:00:57 PM
Metadata
Fields
Template:
City Government
type
ERMUSR
date
9/15/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
20
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
completely, or never getting through at all. We received a number of emails and a number of <br />phone calls throughout the remainder of the day from customers voicing dissatisfaction in trying <br />to contact us during the outage. As a staff, we discussed some things we might be able to do <br />differently in the future, such as having apre-recorded message ready to place on the phones in <br />the event of such an outage again, and exploring the option of "unrolling the phones" without the <br />assistance of Bob Pearson (he, of course, is onboard with trying to figure this out as well.) <br />One other thing that came out of this outage experience is GRE offered to look into ERMU <br />utilizing the system their member utilities use for receiving customer calls to report the outage <br />and respond back to the customers that they are aware of an outage. GRE's system is automated <br />and once they recognize there is an outage they convert the system over to the automated service. <br />GRE is working on a proposal for us to determine what the cost would be. There are some <br />additional technical items to work through because the database that drives the automated system <br />is interactive. It helps identify who is calling and where they are calling from, as well as let the <br />customer know they are aware of an outage. There will also be an increase in our monthly fee <br />for this dispatch service. As I have more details on this, I will bring them forward. <br />Some really good news is that I have received our medical insurance renewal rate for 201 I and it <br />is a zero increase. Our 201 I rates will be the exact same rates we currently have. If you recall, <br />our dental rates are locked in until January 1, 2012 and so the 201 1 insurances wIll all be the <br />same as 2010. <br />Per commission request, I looked into a check reader/processor for the front counter. Our bank <br />could offer a 1.5% transaction fee, plus $.25 per transaction, with a minimum charge of $40 per <br />month, and an additional monthly fee of $15. The check reader does not have to be purchased <br />separately, it is provided for using their service. In using this equipment, the funds would be <br />verified (although not 100% guaranteed) as the check is processed at the front counter. The <br />volume of checks we process at the front counter is an average of 10 per day, with a max of 20. <br />Using an average amount of $175, an estimated cost would be X590 per month for this service. <br />Staff estimates they collectively spend an average of l 5 to 30 minutes processing an NSF. If it <br />were assumed that al] NSFs come from the counter traffic, and currently we have an average of <br />approximately 24 NSFs in a given month (varying from I S to 33 per month) that cost is <br />approximately $276 per month. While it is not known definitely, it is suspected that the majority <br />of NSFs are not from the counter traffic, but the mail in payments. <br />
The URL can be used to link to this page
Your browser does not support the video tag.