Using Inflow and Infiltration Analysis to Prioritize Pipe Repairs
Aging sewer systems rarely fail in uniform ways. One neighborhood may experience excessive wet-weather flow because of cracked mains, while another may be affected by roof drains, illegal connections, or deteriorated manholes. Treating every suspected defect as an equal repair priority can consume limited capital without producing a meaningful reduction in peak flow or sanitary sewer overflows.
Inflow and infiltration analysis provides a practical way to connect field conditions with system performance. By comparing rainfall, flow monitoring, inspections, maintenance records, and hydraulic behavior, utilities can identify where unwanted water enters the collection system and estimate which repairs will deliver the greatest operational benefit.
For water and wastewater professionals in the Los Angeles Basin, this approach supports decisions that must account for dense development, variable rainfall, aging infrastructure, environmental protection, and public service continuity. It also creates a common technical language for engineers, operators, consultants, and agency leaders evaluating rehabilitation programs.
Distinguishing Inflow From Infiltration
Inflow is rainwater or surface water that enters a sanitary sewer quickly through direct connections or openings. Common pathways include roof leaders, yard drains, area drains, uncapped cleanouts, manhole covers, and cross-connections with storm drainage. A rapid flow response during or immediately after rainfall often points to inflow.
Infiltration enters more gradually through defects below the groundwater table. Cracked pipes, open joints, failed laterals, porous manholes, and damaged service connections can admit groundwater over hours or days. Infiltration may continue after a storm has ended, producing elevated base flow and reducing available conveyance capacity.
The distinction matters because the repair strategy differs. Removing an improper drain connection may eliminate a sharp wet-weather spike, while groundwater infiltration may require lining, point repairs, manhole rehabilitation, or replacement of a structurally deficient segment. A clear diagnosis prevents utilities from applying an expensive solution to the wrong source.
Building A Reliable Evidence Base
A useful investigation starts with a monitoring plan designed around decisions, rather than data collection alone. Temporary flow meters can be placed at strategic subbasin boundaries, while rain gauges provide localized precipitation records. Comparing dry-weather and wet-weather hydrographs helps estimate the volume, timing, and persistence of excess water.
Useful supporting information includes sewer maps, pipe age and material, CCTV inspection ratings, cleaning history, pump station records, overflow reports, groundwater levels, complaint locations, and previous rehabilitation projects. When available, electrical consumption and treatment plant influent records can help verify whether localized findings align with broader system behavior.
Utilities can also use predictive tools to improve planning. The LABS of CWEA resource on influent flow forecasting describes how machine learning can help identify recurring flow and load patterns. Such models should supplement field evidence, with transparent assumptions and quality checks, rather than replace inspection and engineering judgment.
Connecting Flow Patterns To Pipe Locations
After collecting data, analysts should divide the collection system into manageable drainage areas. Comparing monitored basins during the same storm can reveal where wet-weather response is unusually high. A basin with a fast peak and little persistence may contain direct inflow sources; one with a slow, prolonged elevation may have extensive groundwater infiltration.
Rainfall intensity, storm duration, antecedent moisture, and seasonal groundwater conditions influence the result. A single storm can produce misleading conclusions, especially if a gauge does not represent conditions across the entire service area. Repeated events provide a stronger basis for separating consistent system behavior from isolated anomalies.
The following diagnostic framework can help connect observed patterns with practical next steps:
| Observed signal | Likely source | Useful validation | Typical response |
|---|---|---|---|
| Sharp flow increase during rainfall | Direct inflow, roof or area drain connection | Dye testing, smoke testing, property inspections | Remove connection or seal entry point |
| Delayed, sustained post-storm flow | Groundwater infiltration | Night monitoring, groundwater comparison, CCTV | Line or replace defective pipe |
| High flow from one subbasin | Localized defects or illegal connections | Subarea metering and manhole inspection | Narrow investigation to contributing reaches |
| Repeated surcharge near a known bottleneck | Capacity loss or excessive wet-weather load | Hydraulic model and level monitoring | Repair source, increase capacity, or manage flows |
| Flow anomaly without rainfall | Base infiltration, industrial discharge, meter error | Meter verification and dry-weather sampling | Correct measurement or investigate source |
CCTV inspection becomes more valuable after flow monitoring narrows the search area. Smoke testing can identify direct connections near the surface, while dye testing may confirm suspected pathways when property access and regulatory controls are properly managed. Manhole inspections are essential because infiltration can enter through frames, chimneys, walls, and bench channels even when nearby pipes appear serviceable.
Ranking Repairs By Risk And Return
A repair priority should combine hydraulic benefit with asset risk. A pipe that contributes substantial wet-weather flow but has low structural risk may receive a different treatment from a smaller contributor located beneath a major roadway, near a waterway, or upstream of a chronic overflow. The best candidates improve both system performance and service reliability.
A practical scoring system can include excess flow volume, peak reduction potential, likelihood of recurrence, structural condition, consequence of failure, environmental exposure, public disruption, construction complexity, and estimated cost. Confidence in the diagnosis should also affect the score. A suspected defect supported by several independent data sources deserves more weight than an unverified assumption.
Cost-effectiveness can be expressed through measures such as gallons of wet-weather flow removed per dollar, peak flow reduction per project, or avoided overflow risk. These metrics should not be used mechanically. A repair with modest flow reduction may still be essential if it prevents collapse, protects a critical crossing, or resolves a recurring contamination concern.
Moving From Analysis To A Repair Program
Once candidates are ranked, utilities can group projects by geography, construction method, traffic impacts, or maintenance access. Bundling nearby point repairs may reduce mobilization costs, while coordinating sewer rehabilitation with road paving can limit repeated disruptions. Emergency work and regulatory commitments should remain visible in the program even when their benefit is difficult to express through a single score.
Pilot projects can test whether predicted benefits occur. Flow monitoring before and after rehabilitation helps verify reductions in infiltration or inflow and improves future cost estimates. If a repaired basin remains wet-weather sensitive, the result may indicate another entry pathway, an inaccurate original diagnosis, or a broader capacity issue.
This work benefits from collaboration across disciplines. Operators understand recurring field behavior, engineers interpret hydraulic and structural evidence, inspectors identify constructability concerns, and finance or asset-management staff evaluate lifecycle costs. LABS of CWEA’s committee network offers a professional setting for connecting with peers who work through similar collection-system challenges.
Recommendations For Practical Implementation
A durable prioritization process should be repeatable, documented, and easy to explain to decision-makers. The following practices help convert scattered observations into a defensible capital program:
- Establish dry-weather and wet-weather flow baselines for each major drainage area.
- Match rainfall records to monitoring locations and analyze several representative storms.
- Combine flow data with CCTV, manhole inspections, smoke testing, dye testing, and maintenance history.
- Score projects using flow reduction, structural risk, consequence of failure, confidence, cost, and environmental benefit.
- Verify completed repairs with follow-up monitoring and update the ranking database as conditions change.
The process should also preserve data quality. Meter calibration, time synchronization, missing-data review, and rainfall validation can materially change the interpretation of a hydrograph. Documenting these controls makes findings easier to defend during budget reviews, regulatory discussions, and project closeout.
Effective inflow and infiltration management is a continuing cycle rather than a one-time study. As new storms occur, assets deteriorate, and rehabilitation projects are completed, the evidence base should be refreshed. Agencies that maintain this cycle can direct funding toward repairs that reduce avoidable flow, protect capacity, and improve long-term collection-system resilience.
LABS of CWEA members can apply these methods through technical discussions, facility tours, workshops, and professional development activities that connect analysis with field practice. Explore the organization’s resources and participate in its water environment community to help turn better system data into targeted, measurable pipe repairs.