Search NASA⌕ Search

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.

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

At least 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
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

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 NTRS2007

Guide for Oxygen Compatibility Assessments on Oxygen Components and Systems

Understanding and preventing fire hazards is necessary when designing, maintaining, and operating oxygen systems. Ignition risks can be minimized by controlling heat sources and using materials that will not ignite or will not support burning in the end-use environment. Because certain materials are more susceptible to ignition in oxygen-enriched environments, a compatibility assessment should be performed before the component is introduced into an oxygen system. This document provides an overview of oxygen fire hazards and procedures that are consistent with the latest versions of American Society for Testing and Materials (ASTM) Standards G63 (1999) and G94 (2005) to address fire hazards associated with oxygen systems. This document supersedes the previous edition, NASA Technical Memorandum 104823, Guide for Oxygen Hazards Analyses on Components and Systems (1996). The step-by-step oxygen compatibility assessment method described herein (see Section 4) enables oxygen-system designers, system engineers, and facility managers to determine areas of concern with respect to oxygen compatibility and, ultimately, prevent damage to a system or injury to personnel.

Rosales, Keisa R.↗
NASA NTRS2026

Turbofan Engine Power Extraction Demonstration Final Report

As GE Aerospace advances toward a revolutionary step change in propulsion efficiency, the integration and demonstration of new engine architectures and technology systems are essential. The NASA Turbofan Engine Power Extraction Demonstration (PEx), conducted through the Hybrid Thermally Efficient Core (HyTEC) project, aims to develop and demonstrate megawatt-class hybrid electric capability on a modern commercial turbofan engine. The hybrid electric system is critical to meeting the needs of the U.S. aviation industry for next-generational propulsion systems with greater efficiency, durability, and range. This supports energy independence and helps ensure the security and resilience of one of America's largest export industries. The PEx project specifically targets three key objectives: mechanically integrating hybrid electric capability into a commercial turbofan engine, integrating electric machine control with turbofan control for advanced power management, and de-risking performance modeling of future hybrid electric architectures. To mature these technologies to Technology Readiness Level (TRL) 6, a series of electric power system component tests and a baseline engine performance test campaign were conducted. These efforts culminated in an integrated hybrid electric turbofan test campaign demonstrating power extraction, power insertion, and power transfer between spools. Tests of the electric power system were completed at GE Aerospace’s Electrical Power Integrated Systems Center in Dayton, Ohio and engine tests were completed at Peebles Test Operation in Peebles, Ohio. Hybrid electric trade studies extended the demonstrated capability to altitude using the validated cycle model from the PEx test campaigns, allowing for comments on expanded mission benefits not demonstrated in the ground campaign. The knowledge gained from PEx also supports GE Aerospace’s Compact Core Demonstrator as part of HyTEC Phase 2 and ultimately informs the implementation of hybrid electric systems in the next generation of GE Aerospace commercial engine products. This report provides a summary of the program background, test campaigns, trade studies, and insights into the technical maturation required to support future commercial products.

Hybrid Electric↗
DOE OSTI2023

On fast simulation of dynamical system with neural vector enhanced numerical solver

The large-scale simulation of dynamical systems is critical in numerous scientific and engineering disciplines. However, traditional numerical solvers are limited by the choice of step sizes when estimating integration, resulting in a trade-off between accuracy and computational efficiency. To address this challenge, we introduce a deep learning-based corrector called Neural Vector (NeurVec), which can compensate for integration errors and enable larger time step sizes in simulations. Our extensive experiments on a variety of complex dynamical system benchmarks demonstrate that NeurVec exhibits remarkable generalization capability on a continuous phase space, even when trained using limited and discrete data. NeurVec significantly accelerates traditional solvers, achieving speeds tens to hundreds of times faster while maintaining high levels of accuracy and stability. Moreover, NeurVec’s simple-yet-effective design, combined with its ease of implementation, has the potential to establish a new paradigm for fast-solving differential equations based on deep learning.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Integration of a Wigner effect-based energy storage system with an advanced nuclear reactor

In this work, an innovative energy storage concept based on the purposeful creation of defects in crystalline material by neutron irradiation is presented. Lattice defects are generated when heavy particles collide with the atoms in a crystal structure, i.e., if the incoming particles have enough energy, recoil atoms are displaced from their initial lattice sites. Most of the displaced atoms will eventually combine with nearby vacancies, but some of them will come to rest in non-ideal locations. The energy held by displaced atoms is called Wigner energy. Lattice defects can migrate and form clusters, and the Wigner energy can be released from these groupings if sufficient activation energy is provided. In the nuclear industry, this effect is well-known since it represented an issue for graphite-moderated reactors. This work presents the conceptual design of an engineering system that exploits this physical process to store the energy of neutrons in advanced reactor concepts. In the first part of the paper, the theoretical performance of an energy storage system based on the Wigner effect is described. Given the lattice properties and the compatibility with the harsh reactor environment, graphite was selected as the candidate material for the irradiation targets. Both experimental data and molecular dynamics simulations confirmed that this system can achieve performance comparable with state-of-the-art batteries in terms of stored energy density. In the second part of the paper, the engineering challenges of this innovative technology and the proposed solutions are described. After defining the optimal irradiation conditions, the different steps of the operation of the proposed energy system (from energy storing to energy harvesting) were defined. Finally, the integration of this concept with advanced reactor designs, i.e., a Sodium-cooled Fast Reactor and a Molten Salt-cooled Reactor, was investigated and the corresponding performance was evaluated.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
NASA NTRS1997

A Geometry Based Infra-structure for Computational Analysis and Design

The computational steps traditionally taken for most engineering analysis (CFD, structural analysis, and etc.) are: Surface Generation - usually by employing a CAD system; Grid Generation - preparing the volume for the simulation; Flow Solver - producing the results at the specified operational point; and Post-processing Visualization - interactively attempting to understand the results For structural analysis, integrated systems can be obtained from a number of commercial vendors. For CFD, these steps have worked well in the past for simple steady-state simulations at the expense of much user interaction. The data was transmitted between phases via files. Specifically the problems with this procedure are: (1) File based. Information flows from one step to the next via data files with formats specified for that procedure. (2) 'Good' Geometry. A bottleneck in getting results from a solver is the construction of proper geometry to be fed to the grid generator. With 'good' geometry a grid can be constructed in tens of minutes (even with a complex configuration) using unstructured techniques. (3) One-Way communication. All information travels on from one phase to the next. Until this process can be automated, more complex problems such as multi-disciplinary analysis or using the above procedure for design becomes prohibitive.

Haimes, Robert↗
NASA NTRS1998

An Object Model for a Rocket Engine Numerical Simulator

Rocket Engine Numerical Simulator (RENS) is a packet of software which numerically simulates the behavior of a rocket engine. Different parameters of the components of an engine is the input to these programs. Depending on these given parameters the programs output the behaviors of those components. These behavioral values are then used to guide the design of or to diagnose a model of a rocket engine "built" by a composition of these programs simulating different components of the engine system. In order to use this software package effectively one needs to have a flexible model of a rocket engine. These programs simulating different components then should be plugged into this modular representation. Our project is to develop an object based model of such an engine system. We are following an iterative and incremental approach in developing the model, as is the standard practice in the area of object oriented design and analysis of softwares. This process involves three stages: object modeling to represent the components and sub-components of a rocket engine, dynamic modeling to capture the temporal and behavioral aspects of the system, and functional modeling to represent the transformational aspects. This article reports on the first phase of our activity under a grant (RENS) from the NASA Lewis Research center. We have utilized Rambaugh's object modeling technique and the tool UML for this purpose. The classes of a rocket engine propulsion system are developed and some of them are presented in this report. The next step, developing a dynamic model for RENS, is also touched upon here. In this paper we will also discuss the advantages of using object-based modeling for developing this type of an integrated simulator over other tools like an expert systems shell or a procedural language, e.g., FORTRAN. Attempts have been made in the past to use such techniques.

Mitra, D.↗
NASA NTRS2012

Modeling Off-Nominal Behavior in SysML

Fault Management is an essential part of the system engineering process that is limited in its effectiveness by the ad hoc nature of the applied approaches and methods. Providing a rigorous way to develop and describe off-nominal behavior is a necessary step in the improvement of fault management, and as a result, will enable safe, reliable and available systems even as system complexity increases... The basic concepts described in this paper provide a foundation to build a larger set of necessary concepts and relationships for precise modeling of off-nominal behavior, and a basis for incorporating these ideas into the overall systems engineering process.. The simple FMEA example provided applies the modeling patterns we have developed and illustrates how the information in the model can be used to reason about the system and derive typical fault management artifacts.. A key insight from the FMEA work was the utility of defining failure modes as the "inverse of intent", and deriving this from the behavior models.. Additional work is planned to extend these ideas and capabilities to other types of relevant information and additional products.

Soil Moisture Active-Passive (SMAP) Mission↗
NASA NTRS1976

DYNGEN

Steady-state and transient performance of turbofan and turbojet engines are analyzed. Program uses large time steps, gives analyst freedom in selecting equations needed to describe system, and eliminates discrepancies in answers often generated by transient and steady-state simulations.

Sellers, J. F.↗
NASA NTRS1995

First lidar measurements of water vapor and aerosols from a high-altitude aircraft

Water vapor plays an important role in many atmospheric processes related to radiation, climate change, atmospheric dynamics, meteorology, the global hydrologic cycle, and atmospheric chemistry, and yet our knowledge of the global distribution of water vapor is very limited. The differential absorption lidar (DIAL) technique has the potential of providing needed high resolution water vapor measurements from aircraft and from space, and the Lidar Atmospheric Sensing Experiment (LASE) is a key step in the development of this capability. The LASE instrument is the first fully engineered, autonomous DIAL system, and it is designed to operate from a high-altitude aircraft (ER-2) and to make water vapor and aerosol profile measurements across the troposphere. The LASE system was flown from the NASA Wallops Flight Facility in a series of engineering flights during September 1994. This paper discusses the characteristics of the LASE system and presents the first LASE measurements of water vapor and aerosol profiles.

Browell, Edward V.↗