Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 937 records · Page 52

Preliminary Examination Process of Apollo Core 73002 - Insights and Lessons Learned From ANGSA for Future Sample Return Missions

Apollo Sample 73002 is part of a 2-foot long “drive tube” (73001/73002) of regolith that was collected from a landslide deposit near Lara Crater at the Apollo 17 site, Station 3. The double drive tube is believed to have penetrated a lunar landslide deposit that was transported from the slope of the South Massif into the TLV [1]. As part of the ANGSA (Apollo Next Generation Sample Analyses) initiative, preparing preliminary examination (PE) catalog of 73002 is a crucial first step for the early identification of material types such as rock fragments, and potential stratigraphy within the core. PE of Apollo core 73002 is distinct from science activities with the main goal to produces a sample catalog with a level of detail about sample characterization that is sufficient for the ANGSA PIs (and later on the lunar sample community) to select and request the samples to conduct their individual, scientific studies. Ultimately, the PE catalog of 73002 will help to establish a better understanding of the stratigraphy of the land slide deposit; the processes of the landslide including the trigger(s) and possibly number of landslide events, as well as the role of volatiles [1] and will aid in the careful preservation of the material for future studies [2].

Apollo↗

Application of Agile for Systems Engineering, Project Management and Modeling and Lessons Learned

The Systems Engineering team within the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has been transforming its development processes to be more efficient, robust,and responsive to change and to its stakeholders. To these ends, the Systems Engineering team trialed the integration of agile development techniques into existing and new processes. Agile development methods are well understood within the software development community. Outside ofsoftware development, however, how non-software project management (PM) and systems engineering (SE) teams implement agile development techniques is less well understood. In its transformation efforts, the ExMC SE team focused on three main areas: Improving the project communications among subsystem teams and stakeholders by adopting a scrum-like process, Changing the status and reporting mechanisms to improve schedule coordination between the subsystem team, SE leadership, and ExMC Element leadership, and Unifying the model-based SE workflow to improve understanding of Concepts of Operations across projects.This presentation highlights several of these transformations and what the SE team learned while undergoing the transformation.

S Lumpkins↗