SEARCH · Search NASA

Results for “Lessons Learned”

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.

SourceResearch connectionFrom yearThrough year

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

At least 1,405 records · Page 78

All sources NASA NTRS DOE OSTI

NASA NTRS2006

Safety and Mission Assurance Knowledge Management Retention: Managing Knowledge for Successful Mission Operations

Knowledge Management is a proactive pursuit for the future success of any large organization faced with the imminent possibility that their senior managers/engineers with gained experiences and lessons learned plan to retire in the near term. Safety and Mission Assurance (S&MA) is proactively pursuing unique mechanism to ensure knowledge learned is retained and lessons learned captured and documented. Knowledge Capture Event/Activities/Management helps to provide a gateway between future retirees and our next generation of managers/engineers. S&MA hosted two Knowledge Capture Events during 2005 featuring three of its retiring fellows (Axel Larsen, Dave Whittle and Gary Johnson). The first Knowledge Capture Event February 24, 2005 focused on two Safety and Mission Assurance Safety Panels (Space Shuttle System Safety Review Panel (SSRP); Payload Safety Review Panel (PSRP) and the latter event December 15, 2005 featured lessons learned during Apollo, Skylab, and Space Shuttle which could be applicable in the newly created Crew Exploration Vehicle (CEV)/Constellation development program. Gemini, Apollo, Skylab and the Space Shuttle promised and delivered exciting human advances in space and benefits of space in people s everyday lives on earth. Johnson Space Center's Safety & Mission Assurance team work over the last 20 years has been mostly focused on operations we are now beginning the Exploration development program. S&MA will promote an atmosphere of knowledge sharing in its formal and informal cultures and work processes, and reward the open dissemination and sharing of information; we are asking "Why embrace relearning the "lessons learned" in the past?" On the Exploration program the focus will be on Design, Development, Test, & Evaluation (DDT&E); therefore, it is critical to understand the lessons from these past programs during the DDT&E phase.

Johnson, Teresa A.↗

NASA NTRSDate not supplied

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: 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 pretrained sBERT model shows excellent out-of-the-box performance, 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 the LLIS’s built-in keyword search. Additionally, we demonstrate a use case for the query system by searching for lessons learned relevant to specific requirements from a NASA project as part of a broader knowledge management and retrieval system. Results indicate that applying state-of-the-art natural language processing techniques, especially when fine-tuned using engineering data, to design information retrieval tasks shows significant promise in modernizing design knowledge management systems.

Hannah S. Walsh↗

DOE OSTI2020

Savannah River Site H-Canyon Advancing Technologies for Remote Inspections - 20345

In 2017, the DOE Environmental Management Office of Technology Development (DOE-EM TD) sponsored the H-Canyon Advanced Technology Demonstration (ATD) to demonstrate to DOE facilities the value of using new commercial-off-the-shelf (COTS) and near-ready technologies to solve difficult problems and enhance worker safety. The DOE Savannah River Site (SRS) H-Canyon Air Exhaust Tunnel (HCAEX) inspection task was identified as representative of the hazardous, human denied environments which could benefit from advanced technologies. The HCAEX underground concrete tunnel is visually inspected biannually using a camera mounted on a remotely operated vehicle (ROV) designed and built by SRNL. While tunnel images have provided valuable visual information, it is desirable to have a higher order of understanding of the environment to support a more thorough structural integrity (SI) analysis and for long term planning purposes. As part of the ATD, the Concrete Integrated Product Team (CIPT) was formed to identify and evaluate available sensors and methods mature enough to remotely obtain tunnel concrete characterization data of high value and with a high probability of success. The team included SMEs and H-Canyon stakeholders in the field of concrete, nondestructive examination (NDE), structural integrity, sensors and remote systems from SRNL, SRNS, LANL, DOE-SR and the Army Corps of Engineering. The CIPT completed an in-depth identification of customer concrete inspection needs and potential technology solutions. Sensors and methods were evaluated on performance, data usefulness, cost and the feasibility of a successful deployment given the unique tunnel access challenges and environment. Two technologies were identified as promising by the CIPT for near term demonstration and evaluation: Lidar (Light Detection and Ranging) 3-dimensional (3D) mapping and remote robotic deployment of NDE instrumentation. Laser spectroscopy to characterize tunnel surface chemical changes was also of interest, but presently cost prohibitive. This paper will include a discussion of the two efforts underway to evaluate and implement the CIPT recommendations. First, the status of the November 2019 deployment of Lidar at a single location into the tunnel is presented. This initial deployment provided the team a learning curve and lessons learned on the challenges of tunnel deployment to include remote operation and data collection, stabilization of the sensor in high air flow (∼30 mph), ability to achieve a tolerance accuracy of 0.25-inches, and the probability to identify change in tunnel dimensions over time. Secondly, a discussion on the development of the Robotic Arm Concrete Inspection Test Bed capable of deploying NDE instruments to examine custom concrete forms will be presented. Concrete forms simulating the rough concrete surfaces, strength, composition and potential structural defects that can be found at our DOE EM facilities have been designed and built for the test bed. Two state-of-the art concrete NDE instruments have been identified as having potential to work on rough concrete walls, they are being tested and characterized as to their ability to provide desired structural integrity data to include wall thickness and defect identification on the developed test beams. Lastly, lessons learned, and the path forward will be presented. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS2014

Lessons We Learned Designing and Building the Chandra Telescope

2014 marks the crystal (15th) anniversary of the launch of the Chandra X‐ray Observatory. This paper offers some of the major lessons learned by some of the key members of the Chandra Telescope team. We offer some of the lessons gleaned from our experiences developing, designing, building and testing the telescope and its subsystems, with 15 years of hindsight. Among the topics to be discussed are the early developmental tests, known as VETA‐I and VETA‐II, requirements derivation, the impact of late requirements and reflection on the conservatism in the design process.

Arenberg, Jonathan↗

DOE OSTI2020

Sludge Removal: Success and Partnership with T Plant - 20510

U.S. DOE contractor CH2M Hill Plateau Remediation Company (CHPRC) has safely and efficiently managed the removal of highly radioactive sludge from the 105-K West Reactor fuel storage basin (105- KW Basin) near the Columbia River. In mid-September 2019, sludge retrieval was completed after 21 storage containers were safely loaded with highly radioactive sludge and transported approximately 13 miles from the 105-KW Basin to T Plant, located in the 200 West Area on the Central Plateau of the Hanford Site. Sludge removal represents the last major source term reduction necessary before the K West Reactor and fuel storage basin can transition to closure activities in preparation for final deactivation and demolition. The technical complexity of the sludge retrieval process, coupled with the challenging physical and radiological characteristics of the waste, necessitated a methodical and deliberate approach using unique design and operational solutions to safely conduct the work. This challenge was further complicated by the need to plan and conduct the work in two separate facilities, each subject to the controls and requirements of its own nuclear facility safety basis. The project overcame these challenges through creating an integrated team that actively engaged, communicated and coordinated each phase of the project to ensure successful completion. This paper will cover how these key elements of the Sludge Removal Project led to its success: - Integrating project planning and management; - Lessons learned from design and construction; - Preparing for a successful campaign (lessons learned from testing and start-up); - Lessons learned from operating in two separate facilities, transporting sludge containers on the Hanford Site and ensuring compliance with a range of regulatory and safety basis requirements. The establishment of an integrated group spanning two facilities and multiple organizations created a team capable of overcoming the challenges necessary to successfully plan and execute the sludge retrieval mission. Sharing lessons learned from this successful project can enhance the ability of teams across the DOE complex to successfully plan and execute complex projects. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS2015

Lessons from 30 Years of Flight Software

This presentation takes a brief historical look at flight software over the past 30 years, extracts lessons learned and shows how many of the lessons learned are embodied in the Flight Software product line called the core Flight System (cFS). It also captures the lessons learned from developing and applying the cFS.

Flight Software↗

NASA NTRS2011

Surviving the Lead Reliability Engineer Role in High Unit Value Projects

A project with a very high unit value within a company is defined as a project where a) the project constitutes one of a kind (or two-of-a-kind) national asset type of project, b) very large cost, and c) a mission failure would be a very public event that will hurt the company's image. The Lead Reliability engineer in a high visibility project is by default involved in all phases of the project, from conceptual design to manufacture and testing. This paper explores a series of lessons learned, over a period of ten years of practical industrial experience by a Lead Reliability Engineer. We expand on the concepts outlined by these lessons learned via examples. The lessons learned are applicable to all industries.

lessons learned↗

DOE OSTI2019

Utah FORGE: Phase 2C Topical Report

This is the topical report that wraps up the work and results achieved during Utah FORGE Phase 2C. The zip file includes several folders containing (1) an overview; (2) the results; (3) the lessons learned; and (4) the conclusions. It also contains a folder containing appendices including (1) the updated permitting inventory; (2) the updated site characterization data inventory; (3) the updated conceptual geological model; and (4) the stakeholders engagement and outreach status.

15 GEOTHERMAL ENERGY↗

NASA NTRS2004

Ontology Development and Evolution in the Accident Investigation Domain

InvestiigationOrganizer (IO) is a collaborative semantic web system designed to support the conduct of mishap investigations. IO provides a common repository for a wide range of mishap related information, allowing investigators to integrate evidence, causal models, and investigation results. IO has been used to support investigations ranging from a small property damage case to the loss of the Space Shuttle Columbia. Through IO'S use in these investigations, we have learned significant lessons? about the application of ontologies and semantic systems to solving real-world problems. This paper will describe the development of the ontology within IO, from the initial development, its growth in response to user requests during use in investigations, and the recent work that was done to control the results of that growth. This paper will also describe the lessons learned from this experience and how they may apply to the implementaton of future ontologies and semantic systems.

Carvalho, Robert↗

NASA NTRS2014

Cost Analysis in a Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature service-oriented, multi-mission control centers to streamline or refine their cost analysis process.

Felton, Larry↗

NASA NTRS2014

Cost Analysis In A Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature serviceoriented, multi-mission control centers to streamline or refine their cost analysis process.

Newhouse, M.↗

NASA NTRSDate not supplied

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↗

NASA NTRS2022

Making or Breaking a Rover: System Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

NASA NTRS2022

Making or Breaking a Rover- Systems Engineering Parameters On-Board the Mars 2020 Perseverance Rover

Roth, Brian↗

NASA NTRS2024

Flight Mechanics Modeling and Simulation of the Earth Entry System

Introduction: The Mars Sample Return (MSR) Campaign being planned by NASA and ESA has the ambitious goal to return Mars samples back to Earth. This international collaboration had developed a concept of operations that included a ESA-designed Earth Return Orbiter (ERO) and NASA-designed Capture, Containment, and Return System (CCRS). The Earth Entry System (EES), consisting of a protective aeroshell that houses the samples as well as sample containment vessels, would conduct entry, descent, and landing (EDL) on a direct Earth trajectory. The EES would enter on a spin-stabilized ballistic trajectory with the goal to passively achieve aerodynamic stability throughout all regions of flight. The EDL sequence would end with the EES impacting the soft playa soil of the Utah Test and Training Range (UTTR). As of the submission of this abstract, the MSR campaign is undergoing a re-architecture leading to a pause in EES development. However, the novel approaches developed in flight mechanics modeling and simulation can significantly benefit the greater IPPW community in the development of Earth return vehicles. This paper will present the latest state of EES flight mechanics modeling and simulation. The paper will highlight the simulation architecture developed and key lessons learned from understanding of EDL trajectory sensitivities. Modeling and Simulation: Figure 1 provides a high-level concept of operations for the approach, entry, descent, and landing (AEDL) phase of the CCRS-portion of MSR. The objective of EES flight mechanics is to model and simulate the EES trajectory from ERO separation to ground impact at UTTR. A variety of flight mechanics simulation models were utilized to model both exo-atmopsheric and atmospheric portions of flight. 42, a 6-DOF simulation developed at Goddard Space Flight Center, is utilized for propagating the attitude of EES during exo-atmospheric flight. 42 allows for a variety of spin eject mechanism scenarios to be simulated for analysis. 10 minutes prior to entry, the 42 states are handed off to the EDL sims. The prime EDL sim utilized by EES is the Program to Optimize Simulated Trajectories II (POST2), a 6-DOF sim developed at Langley Research Center, and the independent verification and validation EDL sim utilized is DSENDS, a 6-DOF sim developed at Jet Propulsion Laboratory. Figure 2 provides a visualization of the flight mechanics simulation model flow through various points in the AEDL phase. Due to the existence of a variety of sim models, the EES flight mechanics team developed processes for data hand-off. These processes included the development of a centralized coordinate frame document, utilization of a single, centralized simulation input document for all sims to reference, and hand-off files containing both the technical data to be ingested by other flight mechanics sims as well as annotations of modeling assumptions utilized to generate the data. Figure~\ref{fig:post2simarchitecture} provides an overview of the POST2 sim architecture wherein POST2 ingests numerous subsystem models and input files. The dispersed state file generated by MONTE provides the position/velocity state of the trajectory while the 42 Handoff file provides the attitude. The aerodynamics database, delivered by the EES aeroscience team, is utilized to simulate the aerodynamic forces and moments experienced during EDL. A custom atmosphere model, developed by EES atmosphere team, is utilized to simulate the anticipated atmosphere environment around the region of Earth through which the EES trajectory flys. These inputs and subsystem models can be varied depending on the AEDL flight mechanics scenario being simulated. Monte Carlo simulations are utilized to generate statistical AEDL performance metrics in the form of scorecards and violin plots. Furthermore, outputs from the POST2 simulation are utilized for follow-on analyses including aerothermal and landing performance. \section{Flight Mechanics Lessons Learned} Though the EES flight mechanics team uncovered a variety of lessons learned through the analysis conducted to support CCRS through preliminary design review, this paper will highlight the most important lessons. A key AEDL performance goal is to ensure the landing footprint of EES remains on the UTTR south range. A common modeling strategy used in EDL analysis is One-Variable-At-a-Time (OVAT). OVAT analysis provides insight into the key drivers that affect AEDL performance metrics. Figure 3 shows the landing ellipses for single dispersion sources as compared to the baseline aggregate of all dispersions. The figure shows that atmosphere winds alone dominate the size of the footprint ellipse (note: EES does not use a parachute unlike previous Earth-return missions and is in wind-driven free fall for ~5min). The significance of the wind led the EES flight mechanics team to pursue the development of a Custom Atmosphere Model [4], in lieu of EarthGRAM [1], built on actual radiosonde wind measurements around the UTTR-region. This decision was driven by the realism in the generated footprint ellipses and lessons-learned from Stardust [5]. These findings will be invaluable for future Earth-return missions in providing an early understanding of the key drivers affecting footprint size and modeling considerations for which to account. Another lesson learned is tied to the AEDL performance goal of achieving passive stability throughout all regions of flight. It is well understood that blunt-body aeroshells are less stable as they transition from supersonic to subsonic. Eliminating a backshell does help improvestability; however, other phenomena such as roll-induced instability during terminal descent can still arise. The EES flight mechanics team developed stability metrics as tools to better understand the causes of and better predict the onset of dynamic instability. These tools were built upon analytical models developed by Jaffe [3] and Murphy [2]. The tools were shown to both be very accurate in correlation with actual unstable cases and useful in developing stability margin policies based on the vehicle design and simulation considerations (e.g. sphere-cone angle change, mass change, wind turbulence). These tools allowed for the current EES design to demonstrate the ability to achieve passive stability and can be an invaluable tool for consideration in the design of parachute-less Earth-return vehicles.

Rohan Deshmukh↗

NASA NTRS2010

Introduction of the Space Shuttle Columbia Accident, Investigation Details, Findings and Crew Survival Investigation Report

As the Space Shuttle Program comes to an end, it is important that the lessons learned from the Columbia accident be captured and understood by those who will be developing future aerospace programs and supporting current programs. Aeromedical lessons learned from the Accident were presented at AsMA in 2005. This Panel will update that information, closeout the lessons learned, provide additional information on the accident and provide suggestions for the future. To set the stage, an overview of the accident is required. The Space Shuttle Columbia was returning to Earth with a crew of seven astronauts on 1Feb, 2003. It disintegrated along a track extending from California to Louisiana and observers along part of the track filmed the breakup of Columbia. Debris was recovered from Littlefield, Texas to Fort Polk, Louisiana, along a 567 statute mile track; the largest ever recorded debris field. The Columbia Accident Investigation Board (CAIB) concluded its investigation in August 2003, and released their findings in a report published in February 2004. NASA recognized the importance of capturing the lessons learned from the loss of Columbia and her crew and the Space Shuttle Program managers commissioned the Spacecraft Crew Survival Integrated Investigation Team (SCSIIT) to accomplish this. Their task was to perform a comprehensive analysis of the accident, focusing on factors and events affecting crew survival, and to develop recommendations for improving crew survival, including the design features, equipment, training and procedures intended to protect the crew. NASA released the Columbia Crew Survival Investigation Report in December 2008. Key personnel have been assembled to give you an overview of the Space Shuttle Columbia accident, the medical response, the medico-legal issues, the SCSIIT findings and recommendations and future NASA flight surgeon spacecraft accident response training. Educational Objectives: Set the stage for the Panel to address the investigation, medico-legal issues, the Spacecraft Crew Survival Integrated Investigation Team report and training for accident response.

Chandler, Michael↗

DOE OSTI2021

Heavy Oil Polymer EOR in the Challenging Alaskan Arctic - It Works!

Under co-sponsorship of the US Department of Energy and Hilcorp Alaska LLC the first ever polymer field pilot commenced on 8/28/2018 in the Schrader Bluff heavy oil reservoir at the Milne Point Field on Alaska North Slope (ANS). The primary objective of the pilot is to prove the efficacy of polymer Enhanced Oil Recovery (EOR) to unlock the vast heavy oil resources on ANS. More than two and half years after startup, the polymer injection, supporting laboratory experiments and simulation studies steadily continue. The pilot started injecting hydrolyzed polyacrylamide (HPAM), at a concentration of 1,750 ppm to achieve a target viscosity of 45 cP, into the two horizontal injectors in the flood pattern. Production is monitored in the two horizontal producers. Based on laboratory measurements of polymer viscosity at reservoir conditions, the team decided to reduce polymer concentration to 1,200 ppm since July 2020 in an effort to control injection pressure and optimize polymer utilization. Quality control (QC) on the field ensures uniform polymer solution properties. Representative rock and fluid systems and test conditions are utilized in the corefloods on polymer retention, effect of injection water salinity, polymer loading, and their combinations on oil recovery. A history matched reservoir simulation model for forecasting oil recovery was developed on the basis of all the available field data. Field concerns related to the post-polymer breakthrough impact on flow assurance is addressed via specialized laboratory tests. Notwithstanding early operational disruptions and hydration issues, continuous polymer injection in both injectors has been achieved. To date, 950,000 lbs of polymer or 2 million barrels of polymer solution, equating to 13% of total pore volume (PV), has been placed in the flood pattern, serving as an effective indicator of adequate polymer injectivity. So far, the success of polymer EOR is evident from drastically reduced water cut in the producers, an estimated incremental 1,000 bopd over waterflood, and a favorable polymer utilization of 1.7 lbs/barrel of incremental oil. Polymer breakthrough was observed 26 months after the start of polymer injection. Main observations from corefloods are unusually high polymer retention values in some cases and a positive response to low salinity water. Although the heterogeneity in the flood pattern and exceptionally low water cut pose some challenges, persistent novel and justifiable simulation approaches have resulted in a robust history matched model. Experimental results on produced fluids treatment provide operational guidance for improved oil-water separation and mitigation of heater tube fouling. The ongoing success of the pilot is a key indicator of bringing the team ever closer to meeting the project’s primary objective. The encouraging results of the pilot is one of the drivers that has provided the impetus to apply polymer EOR throughout the Milne Point Field, which would increase oil recovery and extend the economic life of the Trans Alaska Pipeline System. The scientific knowledge, including the many lessons learned from this pilot also has referential value for other potential heavy oil EOR projects throughout the world. The collected data, operational lessons learned, and the overall success of the pilot are summarized in the paper.

None, None↗

NASA NTRS2011

The Habitat Demonstration Unit Project: A Modular Instrumentation System for a Deep Space Habitat

NASA is focused on developing human exploration capabilities in low Earth orbit (LEO), expanding to near Earth asteroids (NEA), and finally to Mars. Habitation is a crucial aspect of human exploration, and a current focus of NASA activities. The Habitation Demonstration Unit (HDU) is a project focused on developing an autonomous habitation system that enables human exploration of space by providing engineers and scientists with a test bed to develop, integrate, test, and evaluate habitation systems. A critical feature of the HDU is the instrumentation system, which monitors key subsystems within the habitat. The following paper will discuss the HDU instrumentation system performance and lessons learned during the 2010 Desert Research and Technology Studies (D-RaTS). In addition, this paper will discuss the evolution of the instrumentation system to support the 2011 Deep Space Habitat configuration, the challenges, and the lessons learned of implementing this configuration. In 2010, the HDU was implemented as a pressurized excursion module (PEM) and was tested at NASA s D-RaTS in Arizona [1]. For this initial configuration, the instrumentation system design used features that were successful in previous habitat instrumentation projects, while also considering challenges, and implementing lessons learned [2]. The main feature of the PEM instrumentation system was the use of a standards-based wireless sensor node (WSN), implementing an IEEE 802.15.4 protocol. Many of the instruments were connected to several WSNs, which wirelessly transmitted data to the command and data handling system via a mesh network. The PEM instrumentation system monitored the HDU during field tests at D-RaTS, and the WSN data was later analyzed to understand the performance of this system. In addition, several lessons learned were gained from the field test experience, which fed into the instrumentation design of the next generation of the HDU.

Rojdev, Kristina↗