My WebLink
|
Help
|
About
|
Sign Out
ITEM 24 ATTACHMENT 2
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2025
>
071525 REGULAR
>
ITEM 24 ATTACHMENT 2
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/8/2025 9:52:54 AM
Creation date
7/8/2025 9:51:44 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
7/15/2025
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
133
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
City of Pleasanton <br />2025 Water Rate Study <br /> <br />Water Resources Economics <br />97 <br />7. WATER CONNECTION FEES <br />7.1 CONNECTION FEE OVERVIEW <br />New customer connections to the City’s water system are subject to a water connection fee, which is <br />necessary to ensure that existing users are not unfairly burdened by costs incurred to provide capacity for <br />new users. The overall purpose of a connection fee is to equitably recover capital costs incurred by the <br />agency to provide system capacity to new users. Water connection fees in California are typically <br />developed based on one of three common methodologies outlined by the AWWA in its M1 Manual. <br /> <br />The three methodologies include: <br />1. Buy-In Method: The Buy-In Method establishes connection based on the value of the system’s <br />existing capital assets and is typically most appropriate when a system’s current capacity is <br />sufficient to serve both short-term and long-term projected demands. The rationale underlying <br />the Buy-In Method is that new customers should pay to “buy-in” to existing system capacity <br />funded by past and current users. <br />2. Incremental Cost Method: The Incremental Cost Method establishes connection fees based on <br />the cost of planned capital expenditures required to expand system capacity and is typically most <br />appropriate when a system’s current capacity is already fully utilized by existing users. The <br />rationale underlying the Incremental Cost Method is that new users should fund planned capital <br />projects that are necessary to accommodate growth. <br />3. Hybrid Method: The Hybrid Method 23 establishes capacity charges based on a combination of <br />the Buy-In Method and the Incremental Cost Method. The Hybrid Method is typically most <br />appropriate when some existing capacity is available to new users, but capacity expansion is still <br />necessary to accommodate long-term demands. <br /> <br />WRE recommends the Hybrid Method for the City’s water connection fees. The existing system has some <br />remaining capacity to serve new customers, and the City will be investing in additional capacity over the <br />next several years. <br /> <br />7.2 BUY-IN COMPONENT <br />The Buy-In component, shown in Table 7-1, calculates the value of the existing water system and its <br />remaining capacity. The existing system value is determined based on the value of fixed assets (Line 1), <br />cash balances (Line 2), and subtracting outstanding debt principal (Line 3). <br /> <br />The fixed asset value is based on data received from City staff regarding water system assets, original <br />cost, accumulated depreciation, acquisition date, and net book value. WRE converted all asset values <br />from original cost into replacement cost less depreciation (RCLD) using the Construction Cost Index <br />(CCI) to adjust for annual cost inflation. WRE recommends using the RCLD asset valuation methodology <br />because it accounts for both inflation and depreciation and is often considered the most equitable <br />approach. The detailed asset list is included in the Appendix (Table 8-6). <br /> <br /> <br />23 The Hybrid Method is referred to by the AWWA as the “Combined Cost Approach.”
The URL can be used to link to this page
Your browser does not support the video tag.