# Presentation: 926766

## Roadmapping Process Improvements by Experience at the Idaho National Engineering Laboratory’ High Level Waste Program and Synergistic Interfaces with Decision-Making

- James Murphy and Arlin Olson
- Bechtel, BWXT Idaho LLC
- March 1, 2001
- WM-’01

- Technology Roadmapping Lessons Learned and
- Interactions of Roadmapping and Decision-Making

## HLW Generation at INTEC

- GV00 0176

## HLW Program Major Functions and Drivers

**Store, Treat, and Make Ready for Final Disposal**
**~1.2 Million gallons of liquid wastes stored in 11 tanks**
**~4,400 Cubic meters of calcine stored in six bin sets**
**Major Drivers**
**Recently completed**
**Commenced negotiations of plan/schedule for calcine treatment by December 1999**
**Declared calciner future by June 2000**
**Submitted tank closure plan for one tank by December 2000**
**Upcoming**
**Cease use of Pillar/Panel Tanks by June 2003**
**Cease use of the remaining tank farm tanks by December 2012**
**Treat HLW to be road ready for disposal by December 2035**

## Baseline Problems

- Technology baseline has changed frequently
- The HLW EIS will set the baseline
- Baseline was most likely  to change

## EIS

- Record of Decision

- Current Direction

- Slow Change

- Desired New Direction

- Previous Practice:
- Begin development
- plan after decision

- Direction change was slow to migrate development activities
-     - wasted time and $$

- Affect of Change in Direction to Technology Development

- Begin
- development
- plan for new
- decision

## Required development of multiple paths
Created for top three performing flowsheets
Direction change was much faster to new direction
Lost less time in long run

- EIS
- Record of Decision

- Current Direction

- New Direction

- Affect of Change in Direction to Technology Development

- Begin
- roadmap of
- best options

- Latest Change:
- Began technology
- roadmap just before
- decision

- Required development of multiple paths
- Created for top three performing flowsheets
- Direction change was much faster to new direction
- Lost less time in long run

## Roadmap Experience - Cost and Schedule

- First two SBW roadmaps (Ion Exchange and Solvent Extraction based flowsheets)
- 3 months, $300 K
- Third SBW roadmap (Direct Vitrification based flowsheet)
- 2 months, $190 K
- Three calcine technology roadmaps (two solvent extraction and direct vitrification)
- 6 weeks total, $150 K

## Slide 8

## How was the roadmap created

- Used DOE Draft Guidance
- Identified lessons learned in each phase
- Roadmap initiation
- Technical needs assessment
- Technical response development
- Roadmap implementation
- Identified decision and roadmap process interfaces

## Roadmapping Lessons Learned

- Roadmap Initiation
- Define the functional flowsheet
- Build a team of experts in the functional areas
- Define the next decision point to be affected

## Define Complete Functional Flow Diagram of System

- Complete Flowsheet
- Example
- (SBW Direct Vitrification)

-   Identify Team Members with Functional Expertise
- 	- Seeking outside expertise when needed

## Define Decision Points Affected

- Technology
- Selection

- Initial
- Design

- Final
- Design

- Operations

- Program
- Progression

- Resolve large uncertainties

-  Resolve smaller uncertainties and improvements

- SBW Roadmap Scope

- Calcine Roadmap Scope

-   Develop roadmaps for top alternatives
-   Perform the roadmap to support initial and
-    final design of selected technology

-   Develop roadmaps for top alternatives
-   Perform viability development and economic evaluations
-     to support final technology selection

## Roadmapping Lessons Learned

- Technical Needs Assessment
- Redefine technical needs as uncertainties to resolve or specific performance gains desired
- Evaluate entire flowsheet
- Categorize consequences (H-failure, M-sizing, L-optimization)
- Assessment Observations
- Uncertainty exists until data are available
- Use a combination of systematic and brainstorming techniques to identify uncertainties

## Roadmapping Lessons Learned

- Technical Response Development
- Prioritize uncertainties with decision points
- Focus technical responses for uncertainties included in roadmap scope
- While developing technical responses for uncertainties,
- maintain relationship between response and uncertainty and
- organize uncertainty and response with the unit operation
- Uncertainties placed in later decision points are developed at a later date

## Roadmapping Lessons Learned

- Roadmap Implementation
- Build the roadmap in a tool that is easy to integrate into the project management schedule (uncertainty-milestones)
- Use tool that supports budget evaluations

## Integrated Decision-Making and Technology Roadmapping

- Benefits to Roadmapping Process
- Decision Points used to prioritize uncertainties
- Scheduling decision points provides completion drivers for development

- Benefits to Decision Support Process
- Further define technical uncertainty
- Define time to comparable maturity level
- Define approximate cost to mature technology

- High Priority Uncertainties for UNEX