SEARCH · Search NASA
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.
This paper discusses the risk communication goals, strategy, planning process and product development for the New Horizons mission, including lessons from the Cassini mission that were applied in that effort, and presents lessons learned from the New Horizons effort that could be applicable to future missions.
Curation is traditionally defined as the process of collecting and organizing information around a common subject matter or a topic of interest and typically occurs in museums, art galleries, and libraries. The task of organizing data around specific topics or themes is a vibrant and growing effort in the biological sciences but to date this effort has not been actively pursued in the Earth sciences. This presentation will introduce the concept of geocuration, which we define it as the act of searching, selecting, and synthesizing Earth science data/metadata and information from across disciplines and repositories into a single, cohesive, and useful compendium. We also present the Climate Data Initiative (CDI) project as an prototypical example. The CDI project is a systematic effort to manually curate and share openly available climate data from various federal agencies. CDI is a broad multi-agency effort of the U.S. government and seeks to leverage the extensive existing federal climate-relevant data to stimulate innovation and private-sector entrepreneurship to support national climate change preparedness. The geocuration process used in the CDI project, key lessons learned, and suggestions to improve similar geocuration efforts in the future will be part of this presentation.
Friction Stir Welding (FSW) is a relatively new industrial process that was invented at The Weld Institute (TWI, United Kingdom) and patented in 1992 under research funded by in part by the National Aeronautics and Space Administration (NASA). Often quoted advantages of the process include good strength and ductility along with minimization of residual stress and distortion. Less well advertised are the beneficial effects of this solid state welding process in the field of occupational and environmental safety. It produces superior weld products in difficult to weld materials without producing any toxic fumes or solid waste that must be controlled as hazardous waste. In fact, it reduces noise pollution in the workspace as well. In the early days of FSW, most welding was performed on modified machine tools, in particular on milling machines with modified milling cutters. In spite of the obvious milling heritage of the process, the techniques and lessons learned from almost 250 years of successful metalworking with milling machines have not been applied in the field of modern Friction Stir Welding. The goal of the current research was to study currently successful FSW tools and parameterize the process in such a way that the design of new tools for new materials could be accelerated. Along the way, several successful new tooling designs were developed for current issues at the Marshall Space Flight Center with accompanying patent disclosures
In 2008, Dr. Thirsk was assigned to the crew of Expedition 20/21. This Expedition represented a milestone for the Canadian Space Program since it was the first time that a Canadian would take part in a long-duration mission. Robert Thirsk had the privilege of expanding the boundaries of space exploration by living and working on board the International Space Station for six months. The launch took place on May 27, 2009 aboard a Soyuz rocket from the Cosmodrome in Baikonur, Kazakhstan. This abstract was written before Dr. Thirsk returned to Kazakhstan. Objective: To gather all medically relevant data needed to support the first Canadian long-duration mission in space, and process it to derive lessons learned for presentation and for public disclosure. Methods: Sources of data used for analysis for Expedition 20 on International Space Station included flight selection data, maintenance annual physicals, Flight Medicine Clinic visits, parabolic flight experiments, preflight exams and baseline data collections, daily in-flight exercise countermeasure and science payloads, weekly periodic fitness, nutrition, radiation and payload assessments, postflight medical exams, rehabilitation, and science activities.
The safety review process for NASA spacecraft flown on Expendable Launch Vehicles (ELVs) has been guided by NASA-STD 8719.8, Expendable Launch Vehicle Payload Safety Review Process Standard. The standard focused primarily on the safety approval required to begin pre-launch processing at the launch site. Subsequent changes in the contractual, technical, and operational aspects of payload processing, combined with lessons-learned supported a need for the reassessment of the standard. This has resulted in the formation of a NASA ELV Payload Safety Program. This program has been working to address the programmatic issues that will enhance and supplement the existing process, while continuing to ensure the safety of ELV payload activities.
A new systems engineering technology has been developed and applied to Shuttle processing. The new engineering approach emphasizes the identification, quantitative assessment, and management of system performance and risk related to the dynamic nature of requirements, technology, and operational concepts. The Space Shuttle Tile Automation System is described as an example of the first application of the new engineering technology. Lessons learned from the Shuttle processing experience are examined, and concepts are presented which are applicable to the design and development of the Space Station Freedom.
Explore the source record for details and available documents.
NASA is currently developing the next generation crewed spacecraft and launch vehicle for exploration beyond earth orbit including returning to the Moon and making the transit to Mars. Managing the design integration of major hardware elements of a space transportation system is critical for overcoming both the technical and programmatic challenges in taking a complex system from concept to space operations. An established method of accomplishing this is formal interface management. In this paper we set forth an argument that the interface management process implemented by NASA between the Orion Multi-Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) achieves the Level 3 tier of the EIA 731.1 System Engineering Capability Model (SECM) for Generic Practices. We describe the relevant NASA systems and associated organizations, and define the EIA SECM Level 3 Generic Practices. We then provide evidence for our compliance with those practices. This evidence includes discussions of: NASA Systems Engineering Interface (SE) Management standard process and best practices; the tailoring of that process for implementation on the Orion to SLS interface; changes made over time to improve the tailored process, and; the opportunities to take the resulting lessons learned and propose improvements to our institutional processes and best practices. We compare this evidence against the practices to form the rationale for the declared SECM maturity level.
The current task of Resource Allocation Process includes the planning and apportionment of JPL's Ground Data System composed of the Deep Space Network and Mission Control and Computing Center facilities. The addition of the data driven, rule based planning system, RALPH, has expanded the planning horizon from 8 weeks to 10 years and has resulted in large labor savings. Use of the system has also resulted in important improvements in science return through enhanced resource utilization. In addition, RALPH has been instrumental in supporting rapid turn around for an increased volume of special what if studies. The status of RALPH is briefly reviewed and important lessons learned from the creation of an highly functional design team are focused on through an evolutionary design and implementation period in which an AI shell was selected, prototyped, and ultimately abandoned, and through the fundamental changes to the very process that spawned the tool kit. Principal topics include proper integration of software tools within the planning environment, transition from prototype to delivered to delivered software, changes in the planning methodology as a result of evolving software capabilities and creation of the ability to develop and process generic requirements to allow planning flexibility.
This paper presents lessons learned by the Software Engineering Process Group (SEPG) from results of supporting two projects at NASA Ames using an Object Oriented Rapid Prototyping (OORP) approach supported by a full featured visual development environment. Supplemental lessons learned from a large project in progress and a requirements definition are also incorporated. The paper demonstrates how productivity gains can be made by leveraging the developer with a rich development environment, correct and early requirements definition using rapid prototyping, and earlier and better effort estimation and software sizing through object-oriented methods and metrics. Although the individual elements of OO methods, RP approach and OO metrics had been used on other separate projects, the reported projects were the first integrated usage supported by a rich development environment. Overall the approach used was twice as productive (measured by hours per OO Unit) as a C++ development.
The purpose for this workshop can be summed up by the question: Are there relevant analogs to planetary (meaning the Moon and Mars) to be found in polar exploration on Earth? The answer in my opinion is yes or else there would be no reason for this workshop. However, I think some background information would be useful to provide a context for my opinion on this matter. As all of you are probably aware, NASA has been set on a path that, in its current form, will eventually lead to putting human crews on the surface of the Moon and Mars for extended (months to years) in duration. For the past 50 V 60 years, starting not long after the end of World War II, exploration of the Antarctic has accumulated a significant body of experience that is highly analogous to our anticipated activities on the Moon and Mars. This relevant experience base includes: h Long duration (1 year and 2 year) continuous deployments by single crews, h Established a substantial outpost with a single deployment event to support these crews, h Carried out long distance (100 to 1000 kilometer) traverses, with and without intermediate support h Equipment and processes evolved based on lessons learned h International cooperative missions This is not a new or original thought; many people within NASA, including the most recent two NASA Administrators, have commented on the recognizable parallels between exploration in the Antarctic and on the Moon or Mars. But given that level of recognition, relatively little has been done, that I am aware of, to encourage these two exploration communities to collaborate in a significant way. [Slide 4] I will return to NASA s plans and the parallels with Antarctic traverses in a moment, but I want to spend a moment to explain the objective of this workshop and the anticipated products. We have two full days set aside for this workshop. This first day will be taken up with a series of presentations prepared by individuals with experience that extends back as far as the late 1940s and includes contemporary experience. The people presenting bring a variety of points of view, including not only U.S. but international, although most, if not all, have collaborated on international teams. The second day will consist of a series of small focused group interactions centered on those elements likely to be needed for traverse missions, such as mobility, habitation, and extravehicular activity (EVA, aka space suits). Our invited participants will be talking with people that specialize in these elements so that we can foster more direct interaction and exchange of experiences between these two exploration communities. After the workshop we will be preparing a report documenting these presentations and the essence of the focused interactions.
The need for large capacity, high speed mass memory storage devices has become increasingly evident at NASA during the past decade. High performance mass storage systems are crucial to present and future NASA systems. Spaceborne data storage system requirements have grown in response to the increasing amounts of data generated and processed by orbiting scientific experiments. Predictions indicate increases in the volume of data by orders of magnitude during the next decade. Current predictions are for storage capacities on the order of terabits (Tb), with data rates exceeding one gigabit per second (Gbps). As part of the design effort for a state of the art mass storage system, NASA Langley has designed a 144 CMOS ASIC to support high speed data transfers. This paper discusses the system architecture, ASIC design and some of the lessons learned in the development process.
One of the most challenging tasks in a space science mission is designing the Mission Operations System (MOS). Whereas the focus of the project is getting the spacecraft built and tested for launch, the mission operations engineers must build a system to carry out the science objectives. The completed MOS design is then formally assessed in the many reviews. Once a mission has completed the reviews, the Mission Operation System (MOS) design has been validated to the Functional Requirements and is ready for operations. The design was built based on heritage processes, new technology, and lessons learned from past experience. Furthermore, our operational concepts must be properly mapped to the mission design and science objectives. However, during the course of implementing the science objective in the operations phase after launch, the MOS experiences an evolutional change to adapt for actual performance characteristics. This drives the re-engineering of the MOS, because the MOS includes the flight and ground segments. Using the Spitzer mission as an example we demonstrate how the MOS design evolved for both the prime and extended mission to enhance the overall efficiency for science return. In our re-engineering process, we ensured that no requirements were violated or mission objectives compromised. In most cases, optimized performance across the MOS, including gains in science return as well as savings in the budget profile was achieved. Finally, we suggest a need to better categorize the Operations Phase (Phase E) in the NASA Life-Cycle Phases of Formulation and Implementation
NASA has a unique history in processing the Space Shuttle fleet for launches. Some of this experience has been captured in the NASA Lessons Learned Information System (LLIS). This tool provides a convenient way for design engineers to review lessons from the past to prevent problems from reoccurring and incorporate positive lessons in new designs. At the Kennedy Space Center, the LLIS is being used to design ground support equipment for the next generation of launch and crewed vehicles. This paper describes the LLIS process and offers some examples.
The International Space Station (ISS) deploys dozens of small satellites into Low Earth Orbit (LEO) each year. This presentation and associated paper cover the ISS Jettison Policy requirements and review/approval process, as well as best practices for satellite Payload Developers who have satellites manifested for deployment from ISS. Specifically, topics will include ISS Jettison Policy requirements to limit generation of orbital debris, limit risk of collision with ISS, and limit risk of collision with ISS visiting vehicles. The paper will include details on the ISS Program jettison candidate analysis and approval process, timelines for data submittal to ISS Program, resources for small satellite developers, and design & analysis recommendations for small satellite developers to maximize their likelihood of successful deployment from ISS. New Station deploy capabilities and ways the ISS Program addresses and facilitates innovations in small satellite technology, including propulsion systems, deorbit devices, constellation development, and novel tech demos, will also be explored. The 2024 session topic that best fits this abstract is Orbital Debris, SSA & STM. The ISS Jettison Policy intends to quantify and control the risks of deploying and operating small satellites, not only to ensure the safety of the humans flying in space, but also to preserve the orbital environment for world space activities and enable the significant benefits brought by such utilization. The ISS Program is committed to working with smallsat providers to address their challenges and enable safe, accessible, innovative missions. The Policy has grown with the industry, with each deploy yielding hard-earned lessons learned that improve our process – not only for the next deploy campaign, but with applicability and adaptability for future applications in LEO and beyond.
The entire procedure of incorporating the requirements and goals of a space flight project into integrated, time ordered sequences of spacecraft commands, is called the uplink process. The Uplink Process Control Task (UPCT) was created to examine the uplink process and determine ways to improve it. The Problem Statement Language/Problem Statement Analyzer (PSL/PSA) designed to assist the designer/analyst/engineer in the preparation of specifications of an information system is used as a supporting tool to aid in the analysis. Attention is given to a definition of the uplink process, the definition of PSL/PSA, the construction of a PSA database, the value of analysis to the study of the uplink process, and the PSL/PSA lessons learned.
The International Space Station offers a unique challenge for integrated testing since the entire station is not launched as an integrated vehicle. The ISS design evolved for over 10 years from the station Freedom program that was based on a "ship and shoot" approach. Ship and shoot assumed the program would accept the hardware for launch and integrate the vehicle on orbit without any ground element-to-element integrated testing. Element-to-Element powered-on integrated testing is needed to identify operational problems on the ground rather than once the hardware is on orbit. The industry is accustomed to testing an integrated vehicle and then verifying it is ready for its operational missions. These tests require ground element emulators to represent on-orbit elements. The ISS Multi-Element Integrated Tests (MEIT) are element-to-element integrated tests bringing together hardware representing several flights. The major purpose of these tests is: 1) Element-to-Element interface compatibility, 2) Systems end-to-end operability and functionality and 3) utilize on-orbit procedures with the crew and mission control center. Execution of these tests is critical since the hardware is available for only a limited period of time. Test configurations are defined which test specific interfaces or functionality. These tests develop operational confidence in the Element-to-Element interfaces and identify major problems on the ground to avoid on-orbit anomalies that could threaten mission success, element survivability or assembly activities. This paper addresses the MEIT process, configurations and lessons-learned from these tests.
The Propulsive Small Expendable Deployer System (ProSEDS) space experiment will demonstrate the use of an electrodynamic tether propulsion system to generate thrust in space by decreasing the orbital altitude of a Delta 11 Expendable Launch Vehicle second stage. ProSEDS will use the flight-proven Small Expendable Deployer System to deploy a newly designed and developed tether which will provide tether generated drag thrust of approx. 0.4 N. The development and production of very long tethers with specific properties for performance and survivability will be required to enable future tether missions. The ProSEDS tether design and the development process may provide some lessons learned for these future missions. The ProSEDS system requirements drove the design of the tether to have three different sections of tether each serving a specialized purpose. The tether is a total of 15 kilometers long: 10 kilometers of a non-conductive Dyneema lead tether; 5 km of CCOR conductive coated wire; and 220 meters of insulated wire with a protective Kevlar overbraid. Production and joining of long tether lengths involved many development efforts. Extensive testing of tether materials including ground deployment of the full-length ProSEDS tether was conducted to validate the tether design and performance before flight.