Water Research Foundation Project #4618: Status and Application of Cathodic Protection in the Water Utility Industry
Bibliographic record
Abstract
Some water utilities have been exploring a variety of techniques to fight external corrosion and to preserve the value of their buried assets however a standardized and defensible approach does not exist. This project will investigate technical and economic considerations to retrofit buried metallic pipelines with CP. The water utility industry is inherently different as compared to oil and gas pipeline industry. The water utility industry is not regulated or required to apply cathodic protection to its pipelines. Application of cathodic protection in the water utility industry is elective and only for the purpose of leak rate reduction and asset preservation. Hot spot and retrofit applications of cathodic protection are typical in the water industry to control leak and break rates. Hot spot cathodic protection is and operations and maintenance driven procedure of installing a galvanic anodes directly connected to metallic pipes at the location of a pipe failure during the pipe repair activities. These anodes are installed without any means of monitoring and stay in the ground until total depletion, usually without replacement. Retrofit CP refers to the practice of systematically protecting existing pipes with galvanic cathodic protection after construction. The on-going water research foundation project (WRF # 4618) included a literature survey, corrosion industry and water industry workshops at major conferences, collection and analysis of utility case studies from U.S. and Canadian utilities, and development of a CP hot spot and retrofit guidance manual to assist water utilities in achieving economic savings and extending asset life. The goal was to produce a utility focused design criteria manual, standard specifications, drawings, and financial template/methodology that will provide a consistent financial benefit measurement of the value of the anode hot spot and retrofit programs. In this paper, a summary of the research and analysis is presented along with supporting case studies.
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.010 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.008 | 0.002 |
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".