Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lessons learned process”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 451 records · Page 25

Constellation Stretch Goals: Review of Industry Inputs

Many good ideas received based on industry experience: a) Shuttle operations; b) Commercial aircraft production; c) NASA's historical way of doing business; d) Military and commercial programs. Aerospace performed preliminary analysis: a) Potential savings; b) Cost of implementation; c) Performance or other impact/penalties; d) Roadblocks; e) Unintended consequences; f) Bottom line. Significant work ahead for a "Stretch Goal"to become a good, documented requirement: 1) As a group, the relative "value" of goals are uneven; 2) Focused analysis on each goal is required: a) Need to ensure that a new requirement produces the desired consequence; b) It is not certain that some goals will not create problems elsewhere. 3) Individual implementation path needs to be studied: a) Best place to insert requirement (what level, which document); b) Appropriate wording for the requirement. Many goals reflect "best practices" based on lessons learned and may have value beyond near-term CxP requirements process.

Lang, John↗

Space Shuttle Program Legacy Report

Share lessons learned on Space Shuttle Safety and Mission Assurance (S&MA) culture, processes, and products that can guide future enterprises to improve mission success and minimize the risk of catastrophic failures. Present the chronology of the Johnson Space Center (JSC) S&MA organization over the 40-year history of the Space Shuttle Program (SSP) and identify key factors and environments which contributed to positive and negative performance.

Johnson, Scott↗

(abstract) FASTER -- A Tool for DSN Forecasting and Scheduling

FASTER, the Forecasting And Scheduling Tool for Earth-based Resources is a suite of software tools developed at JPL to aid in the process of allocating DSN 70 and 34 meter antennas and equipment to support deep space satellites and ground based astronomy. FASTER has been designed for use by a diverse user community, including mid-level managers, data entry and analysis teams, and project scheduling personnel. The system helps to automate many of the previously labor intensive tasks and ensure proper analysis and consistency throughout all phases of the allocation process. FASTER implements an interactive environment for both forecasting and scheduling. This paper will discuss technical aspects of the FASTER system, including forecasting and scheduling algorithms, issues related to large scale use of a scheduling and forecasting system, implications to the process in which a forecasting and scheduling system is embedded, and lessons learned and implications to similar systems.

forecasting↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S. Faragalla↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S Faragalla↗

Real-Time Payload Operations on the International Space Station

This paper will focus on the challenges that Payload Operations have faced as Payload Utilization has evolved over the last three years of real-time experience. Specifically the paper will focus on the planning challenges and the constant battle over program allocation between core systems and payloads, the process of developing and implementing crew training in a centralized location that is being support by a payload development community spread out all over the US, the unique challenges associated with deployed pressurized payload payloads that are not located within an ISPR, and the importance of documenting specific requirements that the payload development community must implement to get through the crew reviews associated with training and procedures. The authors will focus on specific lessons learned and improvements that have been made in both the streamlining of the processes and the associated documentation.

Cissom, Rick D.↗

Lessons Learned from Demolition of Hanford's Plutonium Finishing Plant - 20507

U.S. Department of Energy (DOE) contractor CH2M Hill Plateau Remediation Company (CHPRC), a Jacobs owned company, is making significant progress demolishing the Plutonium Finishing Plant (PFP), which has long been known as one of the most hazardous buildings in the DOE Environmental Management Complex (DOE Complex). The facility is located on the Hanford Site and produced plutonium metal during the Cold War. Production was stopped in 1989, the facility was formally shut down in 1996, and material processing was completed in 2004. After approximately 25 years of demolition preparations, open-air demolition of the main portions of the Hazard Category II nuclear facility began in November 2016. To prepare the PFP for demolition, CHPRC employees performed some of the most hazardous work across the DOE Complex. In addition to extensive demolition preparations, including a wide-reaching communication strategy across the Hanford Site, CHPRC implemented robust controls and monitoring during demolition, and when necessary, adjusted demolition practices and sequence to maintain employee safety and project efficiency. Demolition of the main PFP building began in November 2016. The technical complexity, high hazards and radiological concerns have all led to a difficult demolition environment. Following a spread of contamination at the project site beyond the radiological boundaries in December 2017, work was halted and a recovery plan was generated to allow the demolition work to continue. After the implementation of additional controls and concurrence from regulatory agencies and DOE, the demolition was ready to resume work and reinitiated in August 2018. There are a number of lessons learned from the demolition activities and recovery plan process. This paper allows CHPRC and DoE's Richland Operations Office (RL) to share lessons learned and progress to date with other challenging and hazardous projects across the DOE Complex. Understanding the risk acceptance level is critical to execution of any open-air demolition project and is unique to each facility. Four key lessons learned from this project include: 1) plan execution issues, 2) stakeholder communication issues, 3) watching for summit fever and 4) minimizing exposed contaminated surfaces during demolition. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

A Cognitive Systems Engineering Approach to Developing HMI Requirements for New Technologies

This document examines the challenges inherent in designing and regulating to support human-automation interaction for new technologies that will deployed into complex systems. A key question for new technologies, is how work will be accomplished by the human and machine agents. This question has traditionally been framed as how functions should be allocated between humans and machines. Such framing misses the coordination and synchronization that is needed for the different human and machine roles in the system to accomplish their goals. Coordination and synchronization demands are driven by the underlying human-automation architecture of the new technology, which are typically not specified explicitly by the designers. The human machine interface (HMI) which is intended to facilitate human-machine interaction and cooperation, however, typically is defined explicitly and therefore serves as a proxy for human-automation cooperation requirements with respect to technical standards for technologies. Unfortunately, mismatches between the HMI and the coordination and synchronization demands of the underlying human-automation architecture, can lead to system breakdowns. A methodology is needed that both designers and regulators can utilize to evaluate the expected performance of a new technology given potential human-automation architectures. Three experiments were conducted to inform the minimum HMI requirements a detect and avoid system for unmanned aircraft systems (UAS). The results of the experiments provided empirical input to specific minimum operational performance standards that UAS manufacturers will have to meet in order to operate UAS in the National Airspace System (NAS). These studies represent a success story for how to objectively and systematically evaluate prototype technologies as part of the process for developing regulatory requirements. They also provide an opportunity to reflect on the lessons learned from a recent research effort in order to improve the methodology for defining technology requirements for regulators in the future. The biggest shortcoming of the presented research program was the absence of the explicit definition, generation and analysis of potential human-automation architectures. Failure to execute this step in the research process resulted in less efficient evaluation of the candidate prototypes technologies in addition to the complete absence of different approaches to human-automation cooperation. For example, all of the prototype technologies that were evaluated in the research program assumed a human-automation architecture that relied on serial processing from the automation to the human. While this type of human-automation architecture is typical across many different technologies and in many different domains, it ignores different architectures where humans and automation work in parallel. Defining potential human-automation architectures a priori also allows regulators to develop scenarios that will stress the performance boundaries of the technology during the evaluation phase. The importance of adding this step of generating and evaluating candidate human-automation architectures prior to formal empirical evaluation is discussed.

human systems integration↗

Human Systems Integration in Practice: Constellation Lessons Learned

NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.

Zumbado, Jennifer Rochlis↗

EnDEVR: An Environment for Data Engineering in VR

Organizations within the public and private sectors are looking to improve their data science operations for research, development, and operational purposes. As this interest in data science grows, so too does interest in tools and programs that facilitating such operations. This paper presents EnDEVR, the Environment for Data Engineering in Virtual Reality, a user-extensible system that allows for the execution of custom data science functions. We describe the user-centered design process for the EnDEVR system, based on the needs of subject matter experts within the aerospace and aviation industries. Fundamental to this design is a method for users to integrate their existing analysis code (that may leverage third-party vendors) as usable objects in the virtual environment; this allows organizations to operate without the price tag and lifetime obligations associated with commercial data science toolkits, a concept known as “vendor lock-in”. We then present our system design with iterative implementations, and conclude with lessons learned. The presented work may provide insight into future user-centered design processes for VR applications, particularly for digital transformation stakeholders to circumvent vendor lock-in.

Human-centered computing↗

Magellan spacecraft and memory state tracking: Lessons learned, future thoughts

Numerous studies have been dedicated to improving the two main elements of Spacecraft Mission Operations: Command and Telemetry. As a result, not much attention has been given to other tasks that can become tedious, repetitive, and error prone. One such task is Spacecraft and Memory State Tracking, the process by which the status of critical spacecraft components, parameters, and the contents of on-board memory are managed on the ground to maintain knowledge of spacecraft and memory states for future testing, anomaly investigation, and on-board memory reconstruction. The task of Spacecraft and Memory State Tracking has traditionally been a manual task allocated to Mission Operations Procedures. During nominal Mission Operations this job is tedious and error prone. Because the task is not complex and can be accomplished manually, the worth of a sophisticated software tool is often questioned. However, in the event of an anomaly which alters spacecraft components autonomously or a memory anomaly such as a corrupt memory or flight software error, an accurate ground image that can be reconstructed quickly is a priceless commodity. This study explores the process of Spacecraft and Memory State Tracking used by the Magellan Spacecraft Team highlighting its strengths as well as identifying lessons learned during the primary and extended missions, two memory anomalies, and other hardships encountered due to incomplete knowledge of spacecraft states. Ideas for future state tracking tools that require minimal user interaction and are integrated into the Ground Data System will also be discussed.

Bucher, Allen W.↗

The Port Hope Areas Initiative's Port Granby Project: The Decontamination of Site Equipment from a Low Level Waste Facility - 20330

The Port Hope Area Initiative (PHAI) is the Government of Canada's response to the community recommended solutions for the remediation and safe, long-term management of historic low-level radioactive waste (LLRW) that was the result of uranium and radium processing operations in the Municipality of Port Hope, Ontario from the 1930's to the 1980's. The Eldorado refinery, on the shores of Lake Ontario, began refining radium-226 from pitchblende ore, later transitioning to the refining of uranium ore. Process residues were deposited at the Welcome Waste Management Facility in Port Hope until the mid-1950's switching to the Port Granby Waste Management Facility (PGWMF), which continued to accept waste until the late 1980's. The Port Granby Project involves the construction of a new, secure long-term waste management facility (LTWMF) and supporting infrastructure, and the excavation and relocation of approximately 1,200,000 m{sup 3} of historic low-level radioactive waste and marginally contaminated soil from the PGWMF to the newly constructed LTWMF. Since the project's inception in 2016, the bulk of the material has since been moved to the final long term storage cell. This has taken over 500,000 person-hours and a large amount of one site heavy equipment to accomplish including excavators, bulldozers, rock trucks, baker tanks and vacuum trucks. While many of the pieces of heavy equipment and water management equipment has further work to do on site, several of the sites larger items have already undergone the decontamination process prior to release from the site. This process has posed a serious challenge as the waste has a caustic nature to it and over the last few years it has had time to work its way into the metallic structures and framework of the equipment. Coupled with the tight work spaces and in some cases confined work areas there have been many issues that needed to be addressed to successfully reach a state where items can be free released to the unrestricted limits of the sites license. This ongoing process has led to a more refined decontamination program at the Port Granby Facility and has had a rather high success rate considering the length of time the equipment has been exposed to the waste materials on site. This paper discusses the varied challenges of decontamination faced at a low-level radioactive waste facility with a focus on the following aspects: - Challenges faced regarding different equipment types and the solutions implemented by Wood to address these challenges; - An examination of various decontamination methods employed throughout the project; and - Lessons learned over three years of remediation work and how they impact the decontamination process. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Lessons Learned Using Iridium to Communicate with a CubeSat in Low Earth Orbit

This paper presents the design and approval process for operating an Iridium transceiver on orbit and provide on-orbit performance data obtained from a CubeSat platform in Low Earth Orbit (LEO) (500 km orbit). On-orbit data demonstrates that use of a commercial, low-cost Iridium transceiver can serve as a valuable communication approach for low volume telemetry with less than a 30-minute lag for approximately 90% of the time. In this work, we also demonstrate that a radial differential velocity of 7 km/sec corresponding to about a 37.5kHz doppler shift and a distance of less than 2,000 km can be used for mission planning.

42 ENGINEERING↗

Mars Reconnaissance Orbiter In-flight Anomalies and Lessons Learned: An Update

The Mars Reconnaissance Orbiter mission has as its primary objectives: advance our understanding of the current Mars climate, the processes that have formed and modified the surface of the planet and the extent to which water has played a role in surface processes; identify sites of possible aqueous activity indicating environments that may have been or are conducive to biological activity; and thus identify and characterize sites for future landed missions; and provide forward and return relay services for current and future Mars landed assets. MRO's crucial role in the long term strategy for Mars exploration requires a high level of reliability during its 5.4 year mission. This requires an architecture which incorporates extensive redundancy and cross-strapping. Because of the distances and hence light-times involved, the spacecraft itself must be able to utilize this redundancy in responding to time-critical failures. For cases where fault protection is unable to recognize a potentially threatening condition, either due to known limitations or software flaws, intervention by ground operations is required. These aspects of MRO's design were discussed in a previous paper [Ref. 1]. This paper provides an update to the original paper, describing MRO's significant in-flight anomalies over the past year, with lessons learned for redundancy and fault protection architectures and for ground operations.

Mars Reconnaissance Orbiter↗

An On-line Technology Information System (OTIS) for Advanced Life Support

OTIS is an on-line communication platform designed for smooth flow of technology information between advanced life support (ALS) technology developers, researchers, system analysts, and managers. With pathways for efficient transfer of information, several improvements in the ALS Program will result. With OTIS, it will be possible to provide programmatic information for technology developers and researchers, technical information for analysts, and managerial decision support. OTIS is a platform that enables the effective research, development, and delivery of complex systems for life support. An electronic data collection form has been developed for the solid waste element, drafted by the Solid Waste Working Group. Forms for other elements (air revitalization, water recovery, food processing, biomass production and thermal control) will also be developed, based on lessons learned from the development of the solid waste form. All forms will be developed by consultation with other working groups, comprised of experts in the area of interest. Forms will be converted to an on-line data collection interface that technology developers will use to transfer information into OTIS. Funded technology developers will log in to OTIS annually to complete the element- specific forms for their technology. The type and amount of information requested expands as the technology readiness level (TRL) increases. The completed forms will feed into a regularly updated and maintained database that will store technology information and allow for database searching. To ensure confidentiality of proprietary information, security permissions will be customized for each user. Principal investigators of a project will be able to designate certain data as proprietary and only technical monitors of a task, ALS Management, and the principal investigator will have the ability to view this information. The typical OTIS user will be able to read all non-proprietary information about all projects.Interaction with the database will occur over encrypted connections, and data will be stored on the server in an encrypted form. Implementation of OTIS will initiate a community-accessible repository of technology development information. With OTIS, ALS element leads and managers will be able to carry out informed technology selection for programmatic decisions. OTIS will also allow analysts to make accurate evaluations of technology options. Additionally, the range and specificity of information solicited will help educate technology developers of program needs. With augmentation, OTIS reporting is capable of replacing the current fiscal year-end reporting process. Overall, the system will enable more informed R&TD decisions and more rapid attainment of ALS Program goals.

Levri, Julie A.↗

One NASA: Sharing Knowledge Through an Agency-wide Process Asset Library (PAL)

This poster session will cover the key purpose and components behind implementing the NASA PAL website. This session will present the current results, describing the process used to create the website, the current usage measure, and will demonstrate how NASA is truly becoming ONE. The target audience for the poster session includes those currently implementing the CMMI model and looking for PAL adoption techniques. To continue to be the leader in space, science and technology, NASA is using this agency-wide PAL to share knowledge, work products and lessons learned through this website. Many organizations have failed to recognize how the efforts of process improvement fit into overall organizational effort. However, NASA as an agency has adopted the benefits of process improvement by the creation of this website to foster communication between its ten centers. The poster session will cover the following, topics outlined below: 1) Website purpose; 2) Characteristics of the website; 3) User accounts status; 4) Website content size; and 5) Usage percentages.

Truss, Baraka J.↗

Semantic Search with Sentence-BERT for Design Information Retrieval

Managing and referencing design knowledge is a critical activity in the design process. However, reliably retrieving useful knowledge can be a frustrating experience for users of knowledge management systems due to inherent limitations of standard keyword-based searches. In this research, we consider the task of retrieving relevant lessons learned from the NASA Lessons Learned Information System (LLIS). To this end, we apply a state-of-the-art natural language processing (NLP) technique for information retrieval (IR): semantic search with sentence-BERT, which is a modification of a Bidirectional Encoder Representations from Transformers (BERT) model that uses siamese and triplet network architectures to obtain semantically meaningful sentence embeddings. While the pre-trained sBERT model performs well out-of-the-box, we further fine-tune the model on data from the LLIS so that it learns on design engineering-relevant vocabulary. We quantify the improvement in query results using both standard sBERT and fine-tuned sBERT over a keyword search. Our use case throughout the paper is to use queries related to specific requirements from a NASA project. Fine tuning the sBERT model on LLIS data yields a mean average precision (MAP) of 0.807 on queries based on information needs from a real NASA project. Results indicate that applying state-of-the-art natural language processing techniques, especially when finetuned using engineering data, to design information retrieval tasks shows significant promise in modernizing design knowledge management systems.

Hannah S. Walsh↗

Retrieval of Transuranic Drums with Deflagration to Detonation Potential from a Vault at the Oak Ridge National Laboratory - 20207

During the final phase of a long-term project, a total of 80 TRU waste drums at ORNL have been retrieved from a below-grade storage vault in which they have remained untouched for about 25 years. The drums, which house material generated from past ORNL operations, are now stored and ready for eventual transfer to the Transuranic Waste Processing Center, located on Highway 95 in Oak Ridge. The Transuranic Waste Processing Center will process and ship the drums to WIPP in Carlsbad, New Mexico, for disposal. Workers lifted the drums one-by-one from the underground storage vault with a 110-ton crane over a one-week period in October 2017. Although the physical work was performed in one week, years of detailed planning preceded the fieldwork. A key obstacle needed to be overcome before the project could safely proceed. This obstacle involved the need to ensure controls were developed for the Deflagration to Detonation Transition (DDT) potential. DDT refers to a phenomenon in ignitable mixtures of a flammable gas and air (or oxygen) when a sudden transition takes place from a deflagration type of combustion to a detonation type of explosion. Basically, these drums, under certain circumstances, have a potential to detonate and overpressurize. Extensive analysis of the drums verified that detonation, while unlikely, was possible. Of the total 103 drums that were retrieved or moved in preparation for retrieval, 18 had DDT potential. Extensive security requirements were also necessary, due to the nature of the material, and this added another layer of complexity to the fieldwork. Prior to retrieving the drums from the underground storage vault, space needed to be made for them within the various above-grade facilities. Inventory and security requirements dictated what could be stored where, and the first step of the field work involved a number of drum movements in preparation for storage of the newly retrieved drums. This effort involved moving 21 drums already in the storage area to facilitate the addition of the newly retrieved ones. The retrieval project required a total of 107 critical lifts using the 110-ton crane, under 3 critical lift plans. The TRU waste storage facility is a Category 2 Nuclear Facility and is managed under an extensive Documented Safety Analysis. The TRU retrieval project was conducted in accordance with DOE Order 425.1D and included three Implementation Verification Reviews, two Management Assessments, one Readiness Assessment, and seven mock-ups in preparation for the field work. Despite being stored for 25 years, the drums were in good shape due to the integrity of the facilities where the drums were stored. Of the 80 drums that were retrieved, 12 were placed in special containers called 'overpacks' based on their content. The drums were removed safely and without incident, thanks to a lot of preparation and the efforts of a highly skilled team. Lessons learned through the DDT control development and the drum retrieval and overpacking process could be beneficial to others having to manage similar drums of TRU waste. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗