Laserfiche WebLink
PDDR • -3- • 31 March 1995 <br /> DDRW; Tracy <br /> and the Depot Area on a relatively smaller scale (Figure 4-3). However, it is unclear how <br /> discretization was established at the boundaries and how the scale of the discretization was refined in <br /> the area of interest during model development to reflect available field data. Apparently, the area of <br /> interest was discretized into rectangular cells in horizontal planes which were applied in each of the <br /> model layers in the same manner. It is unclear whether or not this approach was appropriate and <br /> adequate. The PDDR must substantiate and illustrate discretization of the area of interest with respect <br /> to field data and describe boundary condition effects. In addition, the PDDR must include a map <br /> illustrating the boundary and initial conditions in the area of interest with respect to ground water flow <br /> in each horizon. This map should be provided on a relatively small scale and used to illustrate the <br /> initial grid system and it's refinement. <br /> 4. Sensitivity Analysis. The PDDR provides a general discussion of a sensitivity analysis that was <br /> apparently conducted after the model was calibrated. As discussed in our 22 September 1993 <br /> comment letter- specific comment 3, sensitivity analyses should have been performed during <br /> calibration of the model to quantify the uncertainties associated with the model parameters. The <br /> PDDR should provide an appendix of the details from the calibration history in a table, including any <br /> sensitivity analyses, used to compare these uncertainties to the model and available field data. <br /> EVALUATION OF THE REMEDIAL ALTERNATIVES <br /> 1. Specific Objectives. Section 5.1 of the PDDR presents the design objectives used to evaluate four <br /> modeling scenarios. Four modeling scenarios were simulated with the intent of developing potential <br /> remedial design alternatives to meet these design objectives. However, these objectives are not <br /> consistent with the requirements to demonstrate whether or not it is technically and economically <br /> feasible to clean up the contaminated aquifer on and off base to background concentrations, <br /> specifically to non-detect (ND) levels for TCE and PCE. The design objectives, as presented, appear <br /> to focus on providing hydraulic containment versus capture and cleanup of the plume. <br /> 2. Model Scenarios. The model scenarios appear to assume certain physical constraints associated <br /> with potential locations for remedial wells. However, the model scenarios should be used to <br /> optimize the locations and pumping capacities of these wells. This optimization should then be used <br /> as a tool to assist in selecting the remedial well field. <br /> 3. Costs Associated with Hydraulic Capture versus Time Required for Clean Up. The technical <br /> and economic feasibility associated with hydraulic capture of the plume to background levels, versus <br /> levels greater than background, or MCLS (capital costs) must be evaluated. A separate analysis <br /> should be performed to evaluate the feasibility and time required to clean up ground water within the <br /> capture zone(s) (operation costs) to background levels versus levels greater than background, or <br /> MCLS. <br /> 4. Model Limitations. The limitations of the ground water models, as discussed in Sections 4.6 and <br /> 10.0 of the PDDR, to accurately predict cleanup times, do not automatically become effective when <br /> MCLS are achieved. These limitations should be ". . . considered in decision-making based on the <br /> model predictions." as indicated in Section 4.6.0.5 of the PDDR. The uncertainties associated with <br /> the model predictions may be equally applicable to all model predictions. Therefore, it seems <br /> inappropriate to extend the clean up time for cleanup alternative 4B (alternative focused on containing <br /> and treating the combined TCE/PCE plume to detection limits) by some calculated amount for the <br />