My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
ARCHIVED REPORTS_2011 REVISED FEASABILITY STUDY
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
I
>
INDUSTRIAL
>
230
>
2900 - Site Mitigation Program
>
PR0009051
>
ARCHIVED REPORTS_2011 REVISED FEASABILITY STUDY
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/5/2020 2:26:35 PM
Creation date
2/5/2020 10:37:50 AM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2900 - Site Mitigation Program
File Section
ARCHIVED REPORTS
FileName_PostFix
2011 REVISED FEASABILITY STUDY
RECORD_ID
PR0009051
PE
2960
FACILITY_ID
FA0000649
FACILITY_NAME
FORMER NESTLE USA INC FACILITY
STREET_NUMBER
230
STREET_NAME
INDUSTRIAL
STREET_TYPE
DR
City
RIPON
Zip
95366
APN
25938001
CURRENT_STATUS
01
SITE_LOCATION
230 INDUSTRIAL DR
P_LOCATION
05
P_DISTRICT
005
QC Status
Approved
Scanner
SJGOV\sballwahn
Tags
EHD - Public
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
276
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Nestle USA, Inc.—Ripon, CA January 28, 2011 <br /> 2011 Revised Feasibility Study <br /> 9.2.3.3 Relative Cost <br /> The relative cost of PRB composed of ZVI downgradient of the area of higher <br /> TCE concentrations beneath the Site (approximately 700 linear feet) to an <br /> average depth of 60 feet bgs would be classified as medium (< $5,000,000). A <br /> PRB installation to encompass COC-affected groundwater in the Intermediate <br /> Aquifer is not considered implementable and costs for such an installation have <br /> not been provided. <br /> 9.2.3.4 Conclusion <br /> The installation of a PRB composed of ZVI has been retained for further <br /> evaluation for the Upper Aquifer beneath the Site. A PRB installation will not be <br /> considered further for Intermediate and Lower Aquifers or for off-site areas. <br /> 9.3 In-situ Treatment <br /> 9.3.1 In-situ Physical Treatment <br /> In-situ physical treatment relies on mechanical processes, such as stripping or <br /> volatilization, to remove COC mass from a source area. In the case of TCE and <br /> daughter products, this would require a vapor collection system such as SVE. <br /> Example technologies include air sparging. Air sparging entails the injection or <br /> "bubbling" of ambient air into the aquifer to form a zone air channels that strip <br /> volatile organics from groundwater. In air sparging applications, treatment is <br /> limited by diffusion of volatile contaminants into the air channels""' Dissolved <br /> COCs will partition into the vapor phase, eventually escaping from the aquifer for <br /> collection. <br /> 9.3.1.1 Effectiveness <br /> In situ physical treatment technologies can effectively remove CDCs; however, <br /> for a physical method to succeed, vapors must escape from the remediated <br /> saturated soils to an overlying soil formation that is permeable to airflow to allow <br /> for collection. Due to the nature of the Site lithology, injected air could cause <br /> vapors to migrate laterally beneath clay layers that are present 40 to 50 feet bgs. <br /> Similar constraints are present in other areas of VOC groundwater impacts, <br /> including Upper and Intermediate Aquifer zones near the WWTP. <br /> 9.3.1.2 Implementability <br /> As stated in the previous section, in situ physical treatment is not implementable <br /> because clay lenses generally cover or partially cover the Study Area. <br /> 9.3.1.3 Relative Cost <br /> Since effectiveness and implementability are not acceptable, cost is irrelevant. <br /> 9.3.1.4 Conclusion <br /> Based on the analysis above, in-situ physical treatment is removed from further <br /> consideration as a feasible remedial technology. <br /> 31 <br />
The URL can be used to link to this page
Your browser does not support the video tag.