My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
R97-17 AUTHORIZING AGREEMENT - ECONOMIC AND ENGINEERING SERVICES, INC.
COD
>
City Clerk
>
RESOLUTIONS
>
1997
>
R97-17 AUTHORIZING AGREEMENT - ECONOMIC AND ENGINEERING SERVICES, INC.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/19/2016 3:06:16 PM
Creation date
4/19/2016 3:06:14 PM
Metadata
Fields
Template:
Resolution/Ordinance
Res Ord Num
R97-17
Res Ord Title
AUTHORIZING AGREEMENT - ECONOMIC AND ENGINEERING SERVICES, INC. - WATER RATE STUDY
Approved Date
1/21/1997
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
• • Attachement A <br /> between classes of service, and whether these differences are significant enough to <br /> warrant the establishment of classes of service. <br /> A more detailed discussion of cost of service and the basic analytical steps required <br /> in this process is provided below. <br /> 1.4.1 Selection of Test Period <br /> The selection of the test period for the cost of service analysis is similar to the <br /> process noted above for revenue requirements. Generally, the revenue <br /> requirement test period and the cost of service test period are the same. <br /> However, in some cases, the revenue requirement study may review an <br /> extended period of time, e.g. 3 to 5 years. In contrast, the cost of service <br /> analysis typically reviews a 1 to 2 year period, or the period over which rates <br /> will ultimately be set. It is recommended that a 1 year test period for the , <br /> cost of service analysis be used. It is generally recommended that water ' <br /> rates be reviewed on an annual basis. In the opinion of EES, much like the , <br /> utility prepares and annual budget and financial audit, the level and <br /> adequacy of rates should also be examined on an annual basis. It should be <br /> noted however that this statement does not necessarily imply that water <br /> rates should be adjusted each year, but simply, that they should be examined <br /> to assure that price (rates) closely matches costs. <br /> 1.4.2 Selection of a Costing Methodology <br /> Much like the revenue requirements, the allocation of costs within the cost of <br /> service study can use either a "cash basis" or a "utility/accrual basis" for cost <br /> allocation purposes. Under the "cash basis" approach, the cash basis revenue <br /> requirements are simply allocated to each class of service. While this <br /> approach is typically used by municipal water utilities, given the City's <br /> unique mix of customers and their usage requirements, the City may want to <br /> consider using the "utility/accrual basis" for cost allocation. This <br /> recommendation is provided for two reasons. First, under the "utility/accrual <br /> basis" approach, the City would earn a "fair" return on their investment to <br /> the major industrial customers. In any particular year, these industrial <br /> customers could argue that under a "cash basis" approach the specific capital <br /> projects to be undertaken in that year are not benefiting them and therefore, <br /> they should be allocated no capital project costs. By using the "utility/accrual <br /> basis" approach, this issue is eliminated, and the utility simply earns a "fair <br /> return" on their investment from year to year. This tends to stabilize the <br /> rates for the industrial customers, and the revenues of the utility. The <br /> second reason this approach is recommended is that certain customers may <br /> have provided significant "up-front" capital contributions for the construction <br /> of facilities. This clearly needs to be considered within the analysis. The <br /> Scope of Services 1-7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.