Metrics and Methods for Comparing Water Utility Rate Structures
Bibliographic record
Abstract
Utility managers must design rate structures that meet multiple objectives: full cost recovery, fairness, economic efficiency, and resource conservation. To reach these multiple goals, the design of an optimal rate structure would ideally include detailed information on cost of service, demand elasticity, and preferences of the customer base within each utility. However this information is often unavailable, especially when analyzing utilities at regional or national scales. In this absence, the comparison or benchmarking of rate structures across utilities may reveal insights regarding the features, management, or performance of one utility relative to another. We review the metrics and methods available to water utility managers for comparing rate structures with publicly available information. By presenting the full range of metrics available to utility managers, we aim to facilitate the comparison of water rate structures, and ensure that the analysts can select the metric that best fits their needs. To illustrate how these metrics may help generate insight, we use them to compare the rate structures of five municipalities in Canada. Despite the contextual differences, we find that the rates tend to converge at a single metric, the Canadian standard of 25[Formula: see text]m3/month, suggesting that there is a “looking over the shoulder effect” in which managers are probably cognizant of the metrics used to compare them to others. We suggest that the design or re-design of rate structures can be informed by the metrics that compare rates across utilities, despite the limitations of working with only publicly available information.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.043 | 0.210 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.020 | 0.024 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.007 | 0.008 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.007 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".