05.08.2013 Views

ORNL-5388 - the Molten Salt Energy Technologies Web Site

ORNL-5388 - the Molten Salt Energy Technologies Web Site

ORNL-5388 - the Molten Salt Energy Technologies Web 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.

7-21<br />

7.3. PROSPECTS FOR IMPLEMENTATION AND COMMERCIALIZATION<br />

OF DENATURED 233U FUEL CYCLE<br />

J. C. Cleveland and T. J. Burns<br />

Oak Ridge National Laboratory<br />

Chapter 5 has discussed <strong>the</strong> reactors in which denatured 23% might be deployed, as<br />

we1 1 as <strong>the</strong> accompanying fuel recycle facility requirements , and has presented schedules<br />

of d ployment that are based solely on <strong>the</strong> minimum time estimated to be required to solve<br />

technical problems.<br />

evaluations presented in Chapter 6, were developed in discussions between Hanford Engi-<br />

neering Development Laboratory (HEDL) Argonne National Laboratory (ANL) , Oak Ridge<br />

National Laboratory (<strong>ORNL</strong>)<br />

specifically as a bounding case for assessing <strong>the</strong> maximum benefits that could be obtained<br />

by employing denatured 23% fuel. As a result, <strong>the</strong> schedules are not entirely consistent<br />

with those that have been developed subsequently in <strong>the</strong> Nonproliferation A1 ternative<br />

Systems Assessment Program (NASAP). While <strong>the</strong> introduction dates of <strong>the</strong> lead plants do<br />

not differ significantly, <strong>the</strong> NASAP scenarios predict a much slower deployment of<br />

commercial reactors.<br />

These schedules, which have been used in <strong>the</strong> nuclear power system<br />

Combustion Engineering (CE) , and <strong>the</strong> Department of <strong>Energy</strong> (DOE)<br />

The reactor introduction dates and deployment schedules used in this study were<br />

based on <strong>the</strong> following assumptions:<br />

~ 1 yr 0 to develop/commercialize new fuel design<br />

%14 yr to develop/comercialize modified reactor design<br />

~ 1 yr 8 to develop/commercialize new advanced converter design<br />

.~24 yr to develop/commercialize new breeder design<br />

The resulting introduction dates for <strong>the</strong> various reactors are as listed below, where <strong>the</strong><br />

introduction date is defined as <strong>the</strong> date of startup of <strong>the</strong> first unit, reactor deployment<br />

<strong>the</strong>reafter being limited to a maximum introduction rate*' by biennium of 1, 2, 4, . reactors:<br />

1969 - LWRs operating on LEU fuel<br />

1987 - LWRs operating on "denatured 235U'' fuel (i.e., MEU(235)/Th)<br />

1991 - LWRs operating on denatured 233U, Pu/U, and Pu/Th fuels<br />

1991 - SSCRs operating on LEU, denatured 233U, or Pu/Th fuels<br />

1995 - HWRs operating on any of several proposed fuels<br />

1995 - HTGRs operating on any of several proposed fuels<br />

2001 - FBRs operating on PUN, Pu/Th, or denatured 233U fuels<br />

Since <strong>the</strong> above introduction dates are those estimated to be <strong>the</strong> earliest possible<br />

dates that technical problems could be resolved, it is clear that <strong>the</strong>y cannot be achieved<br />

without substantial initiatives and strong financial support from <strong>the</strong> U.S., Government.<br />

*<br />

The introduction rate of any new technology is likely to be less than <strong>the</strong> maximum rate<br />

noted above, since <strong>the</strong> construction market loss rate of an established technology is<br />

limited to 10% per year and total nuclear capacity additions cannot exceed 15 GWelyr.<br />

233U systems are fur<strong>the</strong>r constrained because <strong>the</strong> number or 233U-burning plants that can<br />

be operated is limited by <strong>the</strong> 23%1 production rate.

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

Saved successfully!

Ooh no, something went wrong!