Challenges and Opportunities in Hydraulic Modeling during Business Transformation
Bibliographic record
Abstract
Pennsylvania-American Water, a subsidiary of American Water, provides water and wastewater service to approximately 2.2 million people throughout the Commonwealth of Pennsylvania. Hydraulic models were built for all of Pennsylvania-American Water's major systems and widely used in asset management and system planning in the past decades. As American Water is now in the process of business transformation to promote operating excellence and efficiency, challenges and opportunities have been noticed in hydraulic modeling. Geographic information dystem (GIS) was selected to map all company assets, enterprise asset management (EAM) system is to record nongeographic characteristics of the assets, and customer information system (CIS) is to manage all customer-related data. A large amount of information stored in GIS, EAM, and CIS, along with data recorded in supervisory control and data acquisition (SCADA) systems, serves as the foundation of the next generation of hydraulic models. This paper introduces how to build a model from GIS, assign demands using CIS billing data, and determine hydraulic gradients using EAM data. Two methods of performing hydrant flow tests are also discussed. At the end, this paper briefly lists typical model applications widely used in Pennsylvania-American Water planning activities and some potential uses in the near future.
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.005 | 0.010 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.005 | 0.008 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 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".