19.05.2013 Views

View Document Here - Hanford Site

View Document Here - Hanford Site

View Document Here - Hanford Site

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix E - Detailed Description of Alternative 1: DOE/lu.2001-1 l<br />

I Full Removal and Disposal Rev. e Lpsaft n<br />

^ Redlinc/SUikeout<br />

1 E.1.4 Modify External Area<br />

2<br />

3 The following modifications would be performed to support full removal and disposal of the<br />

4 221-U Facility. Before demolition and removal of 221-U can begin, the legacy structures that<br />

5 surround the exterior of 221-U must first be removed. Demolition of 221-U would involve a<br />

6 large excavation to remove the foundation slab and the cell drain. Waste sites would be removed<br />

7 that are within the limits of this excavation.<br />

8<br />

9 The Alternative 1 approach conservatively assumes that all concrete demolition debris would be<br />

10 disposed at ERDF. During final design this assumption could be revisited to determine if<br />

11 decontaminating and recycling steps could be economically included to support DOE waste<br />

12 minimization goals.<br />

13<br />

14 E.I.A.I. Disposition of External Legacy Structures and Systems. These structures include<br />

15 276-U. 271-U, 211-U, 211-UA, and the access stairs into 221-U.<br />

16<br />

17 E.1.4.1.1 Demolition of the 276-U Solvent Recovery Facility. The 276-U Solvent Recovery<br />

18 Facility, attached to the southwest end of the 221-U Facility, is composed of walkways, tanks,<br />

19 and associated piping set in an open-concrete basin. Decommissioning would involve removing<br />

20 the tanks, walkways, and all aboveground piping. The concrete basin and underground piping<br />

i^'21 would be removed. Concrete surfaces would be decontaminated using selected off-the-shelf<br />

22 technologies.<br />

23<br />

24 Tanks, steel framing, and concrete walls and floors could be removed concurrently with the<br />

25 canyon cleanout activities. The concrete could be left in place until the canyon is demolished,<br />

26 because considerable excavation is required for complete removal and it may be more cost<br />

27 effective to do all concrete removal and excavation at the same time. if left in place, the concrete<br />

28 walls should be fenced for worker safety. Demolition debris would be taken to ERDF for final<br />

29 disposal.<br />

30<br />

31 E.1.4.1.2 Demolition of the 271-U Office Building. The northwest side of the building must<br />

32 be leveled to allow access for a very large mobile crane for canyon demolition. This activity<br />

33 would begin with demolition of the 271-U Office Building. The building is a concrete framed<br />

34 structure built against the northwest face of the 221-U Canyon.<br />

35<br />

36 The 271-U Office Building consists of a basement, three floors, and a reinforced concrete slab<br />

37 roof. There Is a concrete masonry perimeter wall supported on a basement wall, with interior<br />

38 masonry walls within the building. The roof is a reinforced concrete slab similar to the floors.<br />

39 The third floor is a chemical makeup area with floor slabs up to 0.3 m thick that support<br />

40 chemical tanks. Additional building features included in the demolition are a stack on the roof<br />

41 (296-U-10), an elevator, a second floor vault, and mechanical equipment in the basement.<br />

42 Demolition would use typical building demolition techniques. Building 271-U demolition debris<br />

(O'N43 would be stockpiled and used for backfill of the 221-U excavation. After demolition of 271-U,<br />

44 the building footprint would be leveled and compacted as necessary for crane access across this<br />

45 area.<br />

Final Feasi6iiiry Study jor die Canyon Disposition Initiative (221 •U Facifity)<br />

me200 3 E-10

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

Saved successfully!

Ooh no, something went wrong!