19.05.2013 Views

View Document Here - Hanford Site

View Document Here - Hanford Site

View Document Here - Hanford Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

(^N<br />

Appendix E - Detailed Description of Alternative 1: DOF/R1.-2001-1I<br />

I Full Removal and Disposal Rev. o raft t;<br />

Redlinelstrikeout<br />

1 would be designed for equipment disassembly, dccontamination, and packaging of large items in<br />

2 a controlled environment. Disassembly activities would include mechanical and flame cutting,<br />

3 hydraulic shearing, and manual methods. Additional technologies that could be applied are<br />

4 described in Appendix 1. Equipment and materials would be transferred into and out of the<br />

5 enclosure with the main overhead crane.<br />

6<br />

7 The most significant contribution to worker exposure under Alternative I would be the size<br />

8 reduction and packaging of the contaminated legacy equipment that is currently within the<br />

9 221-U Facility. Estimated worker dose for these activities alone is nearly 200 pcrson-rem (BFA<br />

10 2001a). If all of the legacy equipment is volume reduced for shipment, significant worker time<br />

11 and resulting higherexposures would occur. This activity, even with latest technologies<br />

12 available, would be performed in personal protective equipment-required work areas (i.e.,<br />

13 contaminated areas and airborne areas). Significant engineering controls would be required to<br />

14 reduce worker exposure from external and internal exposure sources. Worker turnover could<br />

15 increase due to harsher working conditions. The preliminary ALARA estimate (BHI 2001 a)<br />

16 considered technology currently available.<br />

17<br />

18 E.19.4 Hot Pipe Trench. After the anvon deck can support work<br />

19 activities, equipment currently stered in the process cells could be prepared for removal. The<br />

20 equipment would require the same level of planning and disposition approach as the eanyon<br />

^21 deck equipment. Based on review of available historical photographs, the<br />

22 hot pipe trench contains small-diameter piping. Piping could be removed by cutting a section<br />

23 free, ensuring it is empty, then crushing the cut ends. It would be removed, size reduced as<br />

24 necessary, wrapped, and placed into the modular containers ready for hauling and disposal at<br />

25 ERDF.<br />

26<br />

27 E.13S Remove Surface Contamination. To safely enter the building during its operational<br />

28 phase in this alternative, contamination survey results would be used to identify where<br />

29 decontamination activities are needed. Contamination would either be removed or fixed to the<br />

30 canyon surface to reduce the dose rate and contamination risk to the lowest possible level. It is<br />

31 assumed that water jet, water blasting, or water flushing are practical on the canyon's interior<br />

32 because the waste water could be collected in cell 10 and disposed of in the 200 Area's Liquid<br />

33 Effluent Remediation Facility. Scarifying may be required on some areas.<br />

34<br />

35 After the building has been surveyed and the contamination removal planned, the work would<br />

36 require scaffolding and wastewater collection systems to be installed and maintained, and<br />

37 disposal of wastewater during and after decontamination.<br />

38<br />

39 E.1.3.6 F'ix Contamination on 221-U Interior Surfaces. It is assumed that surface<br />

40 contamination on the canyon walls, Aeercanyon deck s, and ceiling could be addressed with<br />

41 application of a fxative. Fixative would also be applied to all of the interior surfaces of the pipe<br />

42 trench, process cells, craneway, and vent tunnel.<br />

>'\43<br />

Final Feasibility Siady for rite Canyon Disposirion Initiative (221 •U Faeiliry)<br />

J une 2 00-1 E-9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!