Project
Groundwater Pump-and-Treat Capture Zone Validation Project
Environmental engineering project for validating pump-and-treat hydraulic capture with groundwater gradients, extraction capacity, mass removal, monitoring evidence, rebound checks, and release criteria.
This project builds a validation package for a groundwater pump-and-treat system used to hydraulically contain a dissolved contaminant plume. The engineering question is not whether pumps are running. The question is whether the extraction system captures the plume, removes or treats the required contaminant load, and produces enough monitoring evidence to justify an operating release decision.
The project is written for engineering education. Real remediation work must follow the approved conceptual site model, remedy design, permits, discharge requirements, health and safety plan, sampling quality assurance plan, and professional review.
Project Objective
Validate that a pump-and-treat system is controlling a groundwater plume downgradient of a source area. The final engineering deliverable should answer:
- What plume boundary, aquifer interval, receptor and compliance plane must be protected?
- Is the extraction rate large enough relative to estimated groundwater through-flow?
- Do head measurements show inward or controlled hydraulic gradients across the capture boundary?
- Is contaminant mass removal consistent with the conceptual site model?
- Does the treatment train have enough hydraulic and contaminant loading capacity?
- Which monitoring wells prove capture, plume stability, treatment performance and rebound control?
- What operating triggers require pump adjustment, well maintenance, treatment changeout or design review?
- What evidence supports release for routine operation, shutdown testing or long-term stewardship?
The deliverable should be a capture-zone validation memo, extraction-well operating basis, groundwater elevation map, contaminant trend review, treatment loading check, monitoring matrix, alarm and interlock list, rebound-test plan and release decision.
Baseline Scenario
A dissolved solvent plume is migrating in a shallow sand aquifer toward a property boundary. Three extraction wells and an aboveground treatment unit have been installed. The design objective is hydraulic capture at the compliance plane, treatment before discharge, and evidence that downgradient concentrations are not increasing.
Use the following simplified validation basis.
| Parameter | Value |
|---|---|
| aquifer thickness represented at compliance plane | b=6.0\ \text{m} |
| plume width at compliance plane | W=55\ \text{m} |
| hydraulic conductivity | K=2.8\times10^{-5}\ \text{m/s} |
| natural hydraulic gradient toward boundary | i_n=0.0065 |
| effective porosity | n_e=0.28 |
| combined extraction rate from three wells | Q_{ext}=92\ \text{m}^3/\text{day} |
| minimum capture ratio target | R_c=1.5 |
| average influent concentration | C_{in}=1.8\ \text{mg/L} |
| treatment discharge limit | C_{out,limit}=0.010\ \text{mg/L} |
| measured treated effluent concentration | C_{out}=0.004\ \text{mg/L} |
| treatment hydraulic capacity | 125\ \text{m}^3/\text{day} |
| action level for compliance-plane concentration increase | 25\% above baseline |
| minimum data period before routine release | 90\ \text{days} |
These values are simplified. A real validation package must use surveyed well elevations, screened intervals, aquifer tests, pumping records, water-level stabilization criteria, chemistry data quality, seasonal water-level variation, plume geometry, discharge permits, treatment media capacity, and receptor-specific decision criteria.
Step 1: Define the Capture Boundary
The capture boundary is the portion of the aquifer that must be controlled to prevent plume migration beyond the compliance plane. It should be drawn on the current conceptual site model with:
- source area and residual source uncertainty;
- interpreted plume core and fringe;
- extraction well screens and pumping rates;
- compliance wells and downgradient sentinel wells;
- groundwater elevation contours before and during pumping;
- utilities, drains, sand seams or fractures that may create preferential pathways;
- discharge point and treatment boundary.
Engineering Comment
The capture boundary must match the risk objective. Capturing the highest concentration well is not enough if a lower concentration plume fringe bypasses the extraction system toward a receptor.
Step 2: Estimate Natural Groundwater Through-Flow
Groundwater flow through the plume control plane can be screened with Darcy flow:
The cross-sectional area is:
Natural through-flow is:
Convert to cubic metres per day:
Engineering Comment
This value is a bulk flow estimate, not a capture proof. Hydraulic conductivity and plume width are uncertain, and most sites are heterogeneous. The calculation is useful because it reveals whether the extraction rate is in the right order of magnitude before detailed water-level evidence is reviewed.
Step 3: Check Extraction Capacity Against Through-Flow
The extraction ratio is:
This exceeds the minimum screening target:
Engineering Comment
The extraction rate is far larger than the natural through-flow estimate, so hydraulic capacity is not the obvious weakness. However, a high extraction ratio can still fail if well placement is wrong, vertical capture is incomplete, preferential pathways bypass the wells, screens are clogged, or pumping pulls contamination from an unintended source.
Step 4: Estimate Seepage Velocity and Travel Time Without Pumping
Darcy velocity is:
Seepage velocity is:
Convert to metres per day:
If the compliance plane is 85\ \text{m} downgradient from the plume core, the no-control travel time is:
Engineering Comment
The travel time is long enough that trend evidence will not appear instantly at downgradient wells. That is why head control, capture modelling and intermediate monitoring wells are needed. Waiting for a receptor well to improve can be a late and weak validation method.
Step 5: Review Hydraulic Head Evidence
After startup and stabilization, measured heads along a centerline transect are:
| Location | Head before pumping | Head during pumping |
|---|---|---|
| upgradient plume well | 101.42\ \text{m} | 101.31\ \text{m} |
| extraction-well midpoint | 101.08\ \text{m} | 100.62\ \text{m} |
| downgradient compliance well | 100.87\ \text{m} | 100.96\ \text{m} |
Before pumping, the upgradient-to-downgradient head drop is:
During pumping, compare the compliance well to the extraction midpoint:
The compliance well is now higher than the extraction midpoint, so the gradient between those points is directed inward toward the extraction system.
Engineering Comment
This is stronger evidence than pumping rate alone. Hydraulic capture requires a head field that drives water toward the extraction wells across the boundary. The measurement still needs survey control, screen-interval consistency and enough wells to avoid missing a lateral bypass.
Step 6: Calculate Contaminant Mass Removal
Influent concentration is:
Convert to kilograms per cubic metre:
Daily mass entering treatment is:
Treated effluent concentration is:
Daily mass discharged after treatment is:
Mass removed or destroyed by treatment is approximately:
Over 90 days:
Engineering Comment
Mass removal is useful evidence, but it is not closure evidence by itself. A system can remove dissolved mass while a source zone continues to feed the plume. Compare mass removal with concentration trends, source-area data, rebound after shutdown and the conceptual site model.
Step 7: Check Treatment Hydraulic and Concentration Capacity
Hydraulic loading to the treatment unit is:
Treatment hydraulic capacity is:
Hydraulic margin:
Relative margin:
Effluent concentration margin:
Engineering Comment
The treatment unit has hydraulic margin and effluent concentration margin for the tested condition. The release should still include action levels for rising influent concentration, media breakthrough, flow increase, fouling, bypass, power loss and discharge-limit changes.
Step 8: Define Monitoring Evidence
| Evidence line | Minimum validation use |
|---|---|
| groundwater elevations | show inward or controlled gradients at the capture boundary |
| extraction flow totals | prove each extraction well contributes to the required pumping rate |
| influent concentration | track source strength and mass removal |
| treated effluent concentration | prove discharge compliance |
| compliance-plane wells | detect plume migration beyond hydraulic control |
| sentinel wells | provide early warning before receptor impact |
| pump runtime and alarms | show continuity of capture |
| treatment maintenance records | show that removal capacity remains valid |
Engineering Comment
The monitoring network should prove the failure modes that matter. If the main concern is a lateral bypass, a centerline well is insufficient. If vertical gradients matter, shallow-only wells are insufficient. If a pump can fail silently, flow totalizers and alarms are part of the environmental control.
Step 9: Set Trigger Actions
Use these simplified triggers for routine operation.
| Trigger | Action |
|---|---|
| total extraction rate below 80\ \text{m}^3/\text{day} for more than one day | inspect pumps, fouling, power and valves; increase monitoring frequency |
| any extraction well below 85\% of target rate | diagnose screen fouling, pump wear, valve position or air binding |
| loss of inward gradient at compliance transect | restrict release claim and perform geotechnical or hydrogeologic review |
| treated effluent above 0.008\ \text{mg/L} | prepare media changeout or process adjustment before limit exceedance |
| compliance-plane concentration above baseline by 25\% | evaluate plume bypass, sampling QA, seasonal effect and pumping adjustment |
| sentinel well detection above action level | escalate to corrective action and receptor protection review |
| unplanned shutdown longer than 12\ \text{h} | document restart, head recovery, missed capture duration and exposure risk |
Engineering Comment
Trigger actions should be written before the data arrives. Otherwise every adverse trend becomes a negotiation. Good remediation operation defines the decision authority, response time and evidence required to return to routine status.
Step 10: Rebound and Shutdown Test Logic
After stable operation, a controlled shutdown test may be proposed. It should not start until the system has enough trend evidence, receptors are protected, and a restart criterion is defined.
For this project, a shutdown test may proceed only if:
- extraction and treatment have operated for at least 90 days with no unresolved alarms;
- compliance-plane and sentinel wells show stable or decreasing concentrations;
- the conceptual site model has no uninvestigated plume bypass;
- treated discharge has remained below the action level;
- restart triggers are approved before shutdown.
The restart triggers should include:
- loss of protective gradient;
- plume-core concentration rebound above a defined threshold;
- compliance-plane increase above the 25\% action level;
- sentinel detection above action level;
- field evidence of an active source that was not included in the model.
Engineering Comment
Shutdown testing is not proof that remediation is finished. It is a controlled stress test of the conceptual site model. If concentrations rebound quickly, the system may be containing a continuing source rather than finishing cleanup.
Final Release Decision
The system can be released for routine operation with conditions:
Release the pump-and-treat system for routine hydraulic containment, provided all three extraction wells remain within their operating bands, inward gradients are maintained across the compliance transect, treated effluent remains below the action level, and compliance-plane trends do not increase beyond the approved trigger.
Do not release the system for closure or permanent shutdown. The current evidence supports containment and treatment performance during operation, not proof that the source is exhausted.
Final Deliverable
The completed package should include:
- updated conceptual site model and capture boundary;
- extraction well layout, screened intervals and operating setpoints;
- groundwater elevation map before and during pumping;
- Darcy through-flow and extraction-ratio screen;
- head-gradient evidence across the compliance plane;
- mass-removal and treatment-loading calculations;
- monitoring network and sampling QA matrix;
- trigger action response table;
- shutdown and rebound test criteria;
- release decision with residual risks and change-control triggers.
Validation Checks
Before accepting the package, verify that:
- wells compared for gradient are screened in the same hydrostratigraphic interval;
- water-level elevations use surveyed datums and recent measurements;
- extraction rates are totalized by well, not only estimated from pump nameplates;
- treatment samples match flow and operating periods;
- concentration trends are interpreted with sampling uncertainty and seasonal water levels;
- compliance and sentinel wells cover likely bypass pathways;
- shutdown criteria include restart triggers;
- the release statement separates routine operation from closure.
Limits of the Project
This project does not replace a numerical groundwater model, long-term remedial design, toxicological risk assessment, discharge permit, or regulatory closure report. It is a first-pass validation package for an operating pump-and-treat capture system.
The most common mistakes are treating extraction flow as capture proof, comparing heads from different aquifer intervals, ignoring lateral or vertical plume bypass, celebrating mass removal without source control, sampling too few wells to detect failure, and starting a shutdown test without a restart rule.