SEARCH · Search NASA

Results for “STEP system engineering”

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 91 records · Page 5

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Overview of Propulsion Systems for a Mars Aircraft

The capabilities and performance of an aircraft depends greatly on the ability of the propulsion system to provide thrust. Since the beginning of powered flight, performance has increased in step with advancements in aircraft propulsion systems. These advances in technology from combustion engines to jets and rockets have enabled aircraft to exploit our atmospheric environment and fly at altitudes near the Earth's surface to near orbit at speeds ranging from hovering to several times the speed of sound. One of the main advantages of our atmosphere for these propulsion systems is the availability of oxygen. Getting oxygen basically "free" from the atmosphere dramatically increases the performance and capabilities of an aircraft. This is one of the reasons our present-day aircraft can perform such a wide range of tasks. But this advantage is limited to Earth; if we want to fly an aircraft on another planetary body, such as Mars, we will either have to carry our own source of oxygen or use a propulsion system that does not require it. The Mars atmosphere, composed mainly of carbon dioxide, is very thin. Because of this low atmospheric density, an aircraft flying on Mars will most likely be operating, in aerodynamical terms, within a very low Reynolds number regime. Also, the speed of sound within the Martian environment is approximately 20 percent less than it is on Earth. The reduction in the speed of sound plays an important role in the aerodynamic performance of both the aircraft itself and the components of the propulsion system, such as the propeller. This low Reynolds number-high Mach number flight regime is a unique flight environment that is very rarely encountered here on Earth.

Colozza, Anthony J.↗

NASA NTRS2012

Curiosity: the Mars Science Laboratory Project

The Curiosity rover landed successfully in Gale Crater, Mars on August 5, 2012. This event was a dramatic high point in the decade long effort to design, build, test and fly the most sophisticated scientific vehicle ever sent to Mars. The real achievements of the mission have only just begun, however, as Curiosity is now searching for signs that Mars once possessed habitable environments. The Mars Science Laboratory Project has been one of the most ambitious and challenging planetary projects that NASA has undertaken. It started in the successful aftermath of the 2003 Mars Exploration Rover project and was designed to take significant steps forward in both engineering and scientific capabilities. This included a new landing system capable of emplacing a large mobile vehicle over a wide range of potential landing sites, advanced sample acquisition and handling capabilities that can retrieve samples from both rocks and soil, and a high reliability avionics suite that is designed to permit long duration surface operations. It also includes a set of ten sophisticated scientific instruments that will investigate both the geological context of the landing site plus analyze samples to understand the chemical & organic composition of rocks & soil found there. The Gale Crater site has been specifically selected as a promising location where ancient habitable environments may have existed and for which evidence may be preserved. Curiosity will spend a minimum of one Mars year (about two Earth years) looking for this evidence. This paper will report on the progress of the mission over the first few months of surface operations, plus look retrospectively at lessons learned during both the development and cruise operations phase of the mission..

project formulation↗

NASA NTRS2026

Prototype Demonstration of Solar-Carbothermal System to Extract Oxygen From Regolith

The Carbothermal Reduction Demonstration (CaRD) project was an effort to develop a prototype system to demonstrate the extraction of oxygen from simulated lunar regolith using concentrated solar energy and a carbothermal reaction. The prototype consisted of a deployable solar concentrator capable of tracking the sun, carbothermal reactor, fluid system, gas analysis, and a solar concentrator control system consisting of avionics and software. These subsystems were developed by multiple NASA centers and a private industry partner, Sierra Space. The various teams worked together to define requirements and interfaces to successfully assemble the complex system and demonstrate an integrated solar carbothermal process. The solar concentrator developed at Glenn Research Center (GRC) was designed to be stowed for a launch environment then deployed on the lunar surface. It utilized a crossed dragone configuration of composite mirrors to direct horizontal sunlight onto a target 90° from the incoming sunlight. The key performance parameters for the solar concentrator were efficiency and power density. The carbothermal reactor was developed by Sierra Space through a separate project called the Carbothermal Oxygen Production Reactor (COPR) where it successfully demonstrated a fully automated process in a thermal vacuum environment [1]. The fluid system needed for the carbothermal reaction was also developed by Sierra Space and successfully demonstrated in the same thermal vacuum test. The gas analysis system was developed at Kennedy Space Center (KSC) and was required to determine the amount of oxygen extracted during each test. The gas analysis system was based on the Mass Spectrometer Observing Lunar Operations (MSOLO) instrument. Avionics and software for the CaRD prototype were also developed at KSC and based on experience with MSOLO avionics and software. The control system was designed to stow, deploy, track the sun, and perform beam alignment of the concentrated light. The prototype subsystems were integrated and tested at Johnson Space Center’s (JSC) Energy Systems Test Area. A heliostat was used to direct sunlight toward the prototype in a way that is representative of the sunlight conditions at the south pole of the Moon. When concentrated sunlight was focused on simulated lunar regolith within the reactor, the gas analysis team confirmed the presence of carbon monoxide gas, which confirmed that a solar carbothermal reaction took place. The key performance parameter for the integrated prototype was grams of oxygen extracted per kilowatt hour of energy arriving at the concentrator primary mirror. The prototype design successfully demonstrated end-to-end capability and further steps to achieve a flight capable system have been defined. With lunar data, engineers would be able to design a scaled-up system capable of extracting oxygen from regolith at useful quantities for crew life support and rocket propellant. On the long term, this method of In-Situ Resource Utilization could be used to drastically reduce the cost and risk of a sustained human presence on the Moon by reducing the amount of oxygen that would have to be delivered.

Koorosh R Araghi↗

NASA NTRS2026

Prototype Demonstration of Solar Carbothermal System to Extract Oxygen from Regolith

The Carbothermal Reduction Demonstration (CaRD) project was an effort to develop a prototype system to demonstrate the extraction of oxygen from simulated lunar regolith using concentrated solar energy and a carbothermal reaction. The prototype consisted of a deployable solar concentrator capable of tracking the sun, carbothermal reactor, fluid system, gas analysis, and a solar concentrator control system consisting of avionics and software. These subsystems were developed by multiple NASA centers and a private industry partner, Sierra Space. The various teams worked together to define requirements and interfaces to successfully assemble the complex system and demonstrate an integrated solar carbothermal process. The solar concentrator developed at Glenn Research Center (GRC) was designed to be stowed for a launch environment then deployed on the lunar surface. It utilized a crossed dragone configuration of composite mirrors to direct horizontal sunlight onto a target 90° from the incoming sunlight. The key performance parameters for the solar concentrator were efficiency and power density. The carbothermal reactor was developed by Sierra Space through a separate project called the Carbothermal Oxygen Production Reactor (COPR) where it successfully demonstrated a fully automated process in a thermal vacuum environment. The fluid system needed for the carbothermal reaction was also developed by Sierra Space and successfully demonstrated in the same thermal vacuum test. The gas analysis system was developed at Kennedy Space Center (KSC) and was required to determine the amount of oxygen extracted during each test. The gas analysis system was based on the Mass Spectrometer Observing Lunar Operations (MSOLO) instrument. Avionics and software for the CaRD prototype were also developed at KSC and based on experience with MSOLO avionics and software. The control system was designed to stow, deploy, track the sun, and perform beam alignment of the concentrated light. The prototype subsystems were integrated and tested at Johnson Space Center’s (JSC) Energy Systems Test Area. A heliostat was used to direct sunlight toward the prototype in a way that is representative of the sunlight conditions at the south pole of the Moon. When concentrated sunlight was focused on simulated lunar regolith within the reactor, the gas analysis team confirmed the presence of carbon monoxide gas, which confirmed that a solar carbothermal reaction took place. The key performance parameter for the integrated prototype was grams of oxygen extracted per kilowatt hour of energy arriving at the concentrator primary mirror. The prototype design successfully demonstrated end-to-end capability and further steps to achieve a flight capable system have been defined. With lunar data, engineers would be able to design a scaled-up system capable of extracting oxygen from regolith at useful quantities for crew life support and rocket propellant. On the long term, this method of In-Situ Resource Utilization could be used to drastically reduce the cost and risk of a sustained human presence on the Moon by reducing the amount of oxygen that would have to be delivered.

Aaron Paz↗

NASA NTRS2026

Prototype Demonstration of an Integrated Solar Concentrator System and Carbothermal Reactor Using Solar Energy to Extract Oxygen from Regolith

The Carbothermal Reduction Demonstration (CaRD) project was an effort to develop a prototype system to demonstrate the extraction of oxygen from simulated lunar regolith using concentrated solar energy and a carbothermal reaction. The prototype consisted of a deployable solar concentrator capable of tracking the sun, carbothermal reactor, fluid system, gas analysis, and a solar concentrator control system consisting of avionics and software. These subsystems were developed by multiple NASA centers and a private industry partner, Sierra Space. The various teams worked together to define requirements and interfaces to successfully assemble the complex system and demonstrate an integrated solar carbothermal process. The solar concentrator developed at Glenn Research Center (GRC) was designed to be stowed for a launch environment then deployed on the lunar surface. It utilized a crossed dragone configuration of composite mirrors to direct horizontal sunlight onto a target 90° from the incoming sunlight. The key performance parameters for the solar concentrator were efficiency and power density. The carbothermal reactor was developed by Sierra Space through a separate project called the Carbothermal Oxygen Production Reactor (COPR) where it successfully demonstrated a fully automated process in a thermal vacuum environment. The fluid system needed for the carbothermal reaction was also developed by Sierra Space and successfully demonstrated in the same thermal vacuum test. The gas analysis system was developed at Kennedy Space Center (KSC) and was required to determine the amount of oxygen extracted during each test. The gas analysis system was based on the Mass Spectrometer Observing Lunar Operations (MSOLO) instrument. Avionics and software for the CaRD prototype were also developed at KSC and based on experience with MSOLO avionics and software. The control system was designed to stow, deploy, track the sun, and perform beam alignment of the concentrated light. The prototype subsystems were integrated and tested at Johnson Space Center’s (JSC) Energy Systems Test Area. A heliostat was used to direct sunlight toward the prototype in a way that is representative of the sunlight conditions at the south pole of the Moon. When concentrated sunlight was focused on simulated lunar regolith within the reactor, the gas analysis team confirmed the presence of carbon monoxide gas, which confirmed that a solar carbothermal reaction took place. The key performance parameter for the integrated prototype was grams of oxygen extracted per kilowatt hour of energy arriving at the concentrator primary mirror. The prototype design successfully demonstrated end-to-end capability and further steps to achieve a flight capable system have been defined. With lunar data, engineers would be able to design a scaled-up system capable of extracting oxygen from regolith at useful quantities for crew life support and rocket propellant. On the long term, this method of In-Situ Resource Utilization could be used to drastically reduce the cost and risk of a sustained human presence on the Moon by reducing the amount of oxygen that would have to be delivered.

Oxygen from Regolith↗

NASA NTRS2004

HSCT Sector Combustor Evaluations for Demonstration Engine

In LET Task 10, critical development issues of the HSCT lean-burn low emissions combustor were addressed with a range of engineering tools. Laser diagnostics and CFD analysis were applied to develop a clearer understanding of the fuel-air premixing process and premixed combustion. Subcomponent tests evaluated the emissions and operability performance of the fuel-air premixers. Sector combustor tests evaluated the performance of the integrated combustor system. A 3-cup sector was designed and procured for laser diagnostics studies at NASA Glenn. The results of these efforts supported the earlier selection of the Cyclone Swirler as the pilot stage premixer and the IMFH (Integrated Mixer Flame Holder) tube as the main stage premixer of the LPP combustor. In the combustor system preliminary design subtask, initial efforts to transform the sector combustor design into a practical subscale engine combustor met with significant challenges. Concerns about the durability of a stepped combustor dome and the need for a removable fuel injection system resulted in the invention and refinement of the MRA (Multistage Radial Axial) combustor system in 1994. The MRA combustor was selected for the HSR Phase II LPP subscale combustor testing in the CPC Program.

Greenfield, Stuart↗

NASA NTRS1991

A generic trade study methodology for the system analysis of regenerative life support systems

The performance of engineering tradeoffs is a key technique in a rigorous system engineering process used to develop advanced regenerative life support technology by NASA Ames Research Center. The trade study methodology consists of several steps that include deriving relevant life support system functional requirements from a given space exploration mission scenario and synthesizing a set of design options to be analyzed during the study. Examples relevant to life support technology are used to describe the trade study methodology.

Bilardo, Vincent J., Jr.↗

NASA NTRS1986

Multiperspective analysis and testing of expert systems

The paper describes a technique which the author developed for testing expert systems. The technique, which he calls multiperspective testing, can be applied during both the knowledge engineering phase and the acceptance testing phase of developing an exppert system. The first step in multiperspective testing is to define a group of performance measures ('perspectives') that focus on the behavior of the knowledge base. For each such measure, the results of testing are summarized in four scores, which the author calls 'expansion,' 'detection,' 'discrimination,' and 'comprehension.' These scores have the advantage of providing more specific information about how the knowledge base should be updated or corrected.

Bollinger, Terry B.↗

NASA NTRS1991

Intelligent systems/software engineering methodology - A process to manage cost and risk

A systems development methodology is discussed that has been successfully applied to the construction of a number of intelligent systems. This methodology is a refinement of both evolutionary and spiral development methodologies. It is appropriate for development of intelligent systems. The application of advanced engineering methodology to the development of software products and intelligent systems is an important step toward supporting the transition of AI technology into aerospace applications. A description of the methodology and the process model from which it derives is given. Associated documents and tools are described which are used to manage the development process and record and report the emerging design.

Friedlander, Carl↗

NASA NTRS2007

Model-Based Systems

Engineers, who design systems using text specification documents, focus their work upon the completed system to meet Performance, time and budget goals. Consistency and integrity is difficult to maintain within text documents for a single complex system and more difficult to maintain as several systems are combined into higher-level systems, are maintained over decades, and evolve technically and in performance through updates. This system design approach frequently results in major changes during the system integration and test phase, and in time and budget overruns. Engineers who build system specification documents within a model-based systems environment go a step further and aggregate all of the data. They interrelate all of the data to insure consistency and integrity. After the model is constructed, the various system specification documents are prepared, all from the same database. The consistency and integrity of the model is assured, therefore the consistency and integrity of the various specification documents is insured. This article attempts to define model-based systems relative to such an environment. The intent is to expose the complexity of the enabling problem by outlining what is needed, why it is needed and how needs are being addressed by international standards writing teams.

Frisch, Harold P.↗

NASA NTRS2011

Extravehicular Activity Systems Education and Public Outreach in Support of NASA's STEM Initiatives

The exploration activities associated with NASA?s goals to return to the Moon, travel to Mars, or explore Near Earth Objects (NEOs) will involve the need for human-supported space and surface extravehicular activities (EVAs). The technology development and human element associated with these exploration missions provide fantastic content to promote science, technology, engineering, and math (STEM). As NASA Administrator Charles F. Bolden remarked on December 9, 2009, "We....need to provide the educational and experiential stepping-stones to inspire the next generation of scientists, engineers, and leaders in STEM fields." The EVA Systems Project actively supports this initiative by providing subject matter experts and hands-on, interactive presentations to educate students, educators, and the general public about the design challenges encountered as NASA develops EVA hardware for these missions. This paper summarizes these education and public efforts.

Paul, Heather L.↗

NASA NTRS2017

Propulsion Powertrain Real-Time Simulation Using Hardware-in-the-Loop (HIL) for Aircraft Electric Propulsion System

It is essential to design a propulsion powertrain real-time simulator using the hardware-in-the-loop (HIL) system that emulates an electrified aircraft propulsion (EAP) systems power grid. This simulator would enable us to facilitate in-depth understanding of the system principles, to validate system model analysis and performance prediction, and to demonstrate the proof-of-concept of the EAP electrical system. This paper describes how subscale electrical machines with their controllers can mimic the power components in an EAP powertrain. In particular, three powertrain emulations are presented to mimic 1) a gas turbo-=shaft engine driving a generator, consisting of two permanent magnet (PM) motors with brushless motor drives, coupled by a shaft, 2) a motor driving a propulsive fan, and 3) a turbo-shaft engine driven fan (turbofan engine) operation. As a first step towards the demonstration, experimental dynamic characterization of the two motor drive systems, coupled by a mechanical shaft, were performed. The previously developed analytical motor models1 were then replaced with the experimental motor models to perform the real-time demonstration in the predefined flight path profiles. This technique can convert the plain motor system into a unique EAP power grid emulator that enables rapid analysis and real-time simulation performance using hardware-in-the-loop (HIL).

turbo-electric propulsion↗

NASA NTRS2016

The Value of Successful MBSE Adoption

The value of successful adoption of Model Based System Engineering (MBSE) practices is hard to quantify. Most engineers and project managers look at the success in terms of cost. But there are other ways to quantify the value of MBSE and the steps necessary to achieve adoption. The Glenn Research Center (GRC) has been doing Model-Based Engineering (design, structural, etc.) for years, but the system engineering side has not. Since 2010, GRC has been moving from documents centric to MBSE/SysML. Project adoption of MBSE has been slow, but is steadily increasing in both MBSE usage and complexity of generated products. Sharing of knowledge of lessons learned in the implementation of MBSE/SysML is key for others who want to be successful. Along with GRC's implementation, NASA is working hard to increase the successful implementation of MBSE across all the other centers by developing guidelines, templates and libraries for projects to utilize. This presentation will provide insight into recent GRC and NASA adoption efforts, lessons learned and best practices.

MBSE↗

NASA NTRS2023

Bacillus Subtilis Engineered for Aerospace Medicine: A Platform for Off-Planet Production of Pharmaceutical Peptides

Biologics, such as pharmaceutical peptides, have notoriously short shelf lives, insufficient for long-duration space flight missions to the Moon or Mars. To enable the sustainable presence of humans on the Moon or Mars, we must develop methods for on-site production of pharmaceutical peptides in space, a concept we call the Astropharmacy. Here, we present a proof-of-concept for the first step needed: a low-mass system for pharmaceutical production designed to be stable in space. To demonstrate feasibility, we engineered strains of the space-hardy spore-forming bacterium, Bacillus subtilis, to secrete two pharmaceutical peptides important for astronaut health: teriparatide (an anabolic agent for combating osteoporosis) and filgrastim (an effective countermeasure for radiation-induced neutropenia). We found that the secretion peptides from the walM and yoqH genes of B. subtilis worked well for secreting teriparatide and filgrastim, respectively. In consideration of the Translational Research Institute for Space Health (TRISH) challenge to produce a dose equivalent in 24 h, dried spores of our engineered strains were used to produce 1 dose equivalent of teriparatide from a 2 mL culture and 1 dose equivalent of filgrastim from 52 mL of culture in 24 h. Further optimization of strain growth conditions, expression conditions, and promoter sequences should allow for higher production rates to be achieved. These strains provide the template for future optimization efforts and address the first step in the Astropharmacy, capable of on-site production, purification, and processing of biopharmaceutical compounds in platforms amenable for use in space.

Alec Vallota-Eastman↗

NASA NTRSDate not supplied

Developing Mars-Based Clinical Scenarios for an Earth Independent Medical Operations (EIMO) – Based Decision Support Service

As crewed missions move beyond Low-Earth Orbit, pre-mission planning cannot fully buy down the medical risks of exploration-class missions. Martian missions, where increased hazards exist, (such as long-duration spaceflight, surface-level EVA operations, and communications delays) will require a paradigm shift in the structure of a medical system. An Earth-Independent Medical Operations-based Medical System (EIMO-MS) will need to optimize four critical domains to help provide medical care: utilization of Pre-Mission Planning, augmentation of Acute and Prolonged Medical Decision Making, automated tracking of Resource Management, and assistance in Task Load Balance. The ideal EIMO-MS will be able to accomplish this goal by having an interactive, adaptable interface that will be able to provide real-time medical services. It must respond based on the level of crewmember training, medical situation, and available medical and non-medical resources. To showcase the capabilities and requirements of such a sophisticated automated MS, a series of clinical scenarios of escalating complexity were developed with clinical and systems engineering input. These scenarios describe in clinical detail what a theoretical future medical system, enhanced with multiple information streams (such as a medical database, an AI-based Decision Support System, real-time monitoring, enhanced in-situ laboratory imaging, etc.) can achieve in conjunction with a trained and experienced crew. Scenarios are comprised of: a context section including objectives and applicable spaceflight environment, a highlighted assumptions section, a clinical narrative section, and a systems engineering activity diagram demonstrating the integrated Medical System (MS). The “swim lanes” of the activity diagram act as the logistical core of each scenario and show how the MS will interact with the crew, ground support, and other in-flight systems. The Design Reference Mission that is used for the scenarios is based on existing reference mission profiles [1] with a projected 30-sol stay on the Martian surface. Scenarios span the spectrum from planned evaluations, minor medical care, urgent care, surgical guidance, critical and expectant management, and behavioral health care. Mission complexity will exponentially increase during deep space and Mars exploration-class missions, and medical support for these missions will likewise need to increase in autonomy and adaptability. The integrated system that will support these missions will need to provide assistance in a variety of anticipated and unforeseen scenarios. These medical scenarios, guided by clinician input, are initial steps in crafting the requirements for an EIMO-based medical system. By working in a systems engineering framework, requirements and capabilities can be extracted and mapped while maintaining a clinical core.

Prashant Parmar↗

NASA NTRS2013

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗

NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Lessons Learned↗