Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engineered systems”

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

Phase 1 of the First Small Power System Experiment (engineering Experiment No. 1). Volume 4: Commercial System Definition

The development and design of a modular solar thermal power system for application in the 1 to 10 MWe range is described. The system is used in remote utility applications, small communities, rural areas, and for industrial uses. The operational reliability, the minimum risk of failure, and the maintenance and repair characteristics are determined and the commercial system design is defined.

Holl, R. J.↗

Effect of propeller slipstream on the drag and performance of the engine cooling system for a general aviation twin-engine aircraft

The pressure recovery of incoming cooling air and the drag associated with engine cooling of a typical general aviation twin-engine aircraft was investigated experimentally. The semispan model was mounted vertically in the 40- by 80-Foot Wind Tunnel at Ames Research Center. The propeller was driven by an electric motor to provide thrust with low vibration levels for the cold-flow configuration. It was found that the propeller slipstream reduces the frontal air spillage around the blunt nacelle shape. Consequently, this slipstream effect promotes flow reattachment at the rear section of the engine nacelle and improves inlet pressure recovery. These effects are most pronounced at high angles of attack, that is, climb condition. For the cruise condition those improvements were more moderate.

Katz, J.↗

Requirement Discovery Using Embedded Knowledge Graph with ChatGPT

- NASA’s Air Traffic Management-Exploration (ATM-X) Urban Air Mobility (UAM) Airspace Subproject is conducting research that evolves UAM airspace towards a highly automated and operationally flexible system of the future. - (see https://www.nasa.gov/uam-overview/ for more information) - The complexity of UAM airspace, and its evolution through a series of transformative epochs, requires a planning tool to effectively organize, integrate, and communicate the research that will guide the evolution of UAM operations in the National Airspace System (NAS). - The planning tool, called the UAM airspace research roadmap (or just roadmap), is being developed as a new system engineering methodology leveraging model based system engineering (MBSE) and artificial intelligence capabilities. This presentation gives an overview of the Knowledge Graph and ChatGPT applications within this system engineering methodology and will describe how it is being used to meet the ATM-X UAM Airspace Subproject’s overarching research goals.

systems engineering↗

Digital Assistance for System Requirement Discovery and Analysis using Machine Learning Natural Language Processing Algorithm

NASA’s Air Traffic Management-Exploration (ATM-X) Urban Air Mobility (UAM) Airspace Subproject is conducting research that evolves UAM airspace towards a highly automated and operationally flexible system of the future (see https://www.nasa.gov/uam-overview/ for more information). The complexity of UAM airspace, and its evolution through a series of transformative epochs, requires a planning tool to effectively organize, integrate, and communicate the research that will guide the evolution of UAM operations in the National Airspace System (NAS). The planning tool, called the UAM airspace research roadmap (or just roadmap), is being developed as a new system engineering methodology leveraging model based system engineering (MBSE) and machine learning natural language processing (ML NLP, or just NLP) capabilities. This presentation gives an overview of the NLP application within this system engineering methodology and will describe how it is being used to meet the ATM-X UAM Airspace Subproject’s overarching research goals.

ATM↗

SOFIA Program SE and I Lessons Learned

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Ray, Ronald J.↗

Infinite possibilities: Computational structures technology

Computational Fluid Dynamics (or CFD) methods are very familiar to the research community. Even the general public has had some exposure to CFD images, primarily through the news media. However, very little attention has been paid to CST--Computational Structures Technology. Yet, no important design can be completed without it. During the first half of this century, researchers only dreamed of designing and building structures on a computer. Today their dreams have become practical realities as computational methods are used in all phases of design, fabrication and testing of engineering systems. Increasingly complex structures can now be built in even shorter periods of time. Over the past four decades, computer technology has been developing, and early finite element methods have grown from small in-house programs to numerous commercial software programs. When coupled with advanced computing systems, they help engineers make dramatic leaps in designing and testing concepts. The goals of CST include: predicting how a structure will behave under actual operating conditions; designing and complementing other experiments conducted on a structure; investigating microstructural damage or chaotic, unpredictable behavior; helping material developers in improving material systems; and being a useful tool in design systems optimization and sensitivity techniques. Applying CST to a structure problem requires five steps: (1) observe the specific problem; (2) develop a computational model for numerical simulation; (3) develop and assemble software and hardware for running the codes; (4) post-process and interpret the results; and (5) use the model to analyze and design the actual structure. Researchers in both industry and academia continue to make significant contributions to advance this technology with improvements in software, collaborative computing environments and supercomputing systems. As these environments and systems evolve, computational structures technology will evolve. By using CST in the design and operation of future structures systems, engineers will have a better understanding of how a system responds and lasts, more cost-effective methods of designing and testing models, and improved productivity. For informational and educational purposes, a videotape is being produced using both static and dynamic images from research institutions, software and hardware companies, private individuals, and historical photographs and drawings. The extensive number of CST resources indicates its widespread use. Applications run the gamut from simpler university-simulated problems to those requiring solutions on supercomputers. In some cases, an image or an animation will be mapped onto the actual structure to show the relevance of the computer model to the structure. Transferring the digital files to videotape presents a number of problems related to maintaining the quality of the original image, while still producing a broadcast quality videotape. Since researchers normally do not create a computer image using traditional composition theories or video production requirements, often the image loses some of its original digital quality and impact when transferred to videotape. Although many CST images are currently available, those that are edited into the final project must meet two important criteria: they must complement the narration, and they must be broadcast quality when recorded on videotape.

Beam, Sherilee F.↗

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗

Exploration Life Support Technology Development for Lunar Missions

Exploration Life Support (ELS) is one of NASA's Exploration Technology Development Projects. ELS plans, coordinates and implements the development of new life support technologies for human exploration missions as outlined in NASA's Vision for Space Exploration. ELS technology development currently supports three major projects of the Constellation Program - the Orion Crew Exploration Vehicle (CEV), the Altair Lunar Lander and Lunar Surface Systems. ELS content includes Air Revitalization Systems (ARS), Water Recovery Systems (WRS), Waste Management Systems (WMS), Habitation Engineering, Systems Integration, Modeling and Analysis (SIMA), and Validation and Testing. The primary goal of the ELS project is to provide different technology options to Constellation which fill gaps or provide substantial improvements over the state-of-the-art in life support systems. Since the Constellation missions are so challenging, mass, power, and volume must be reduced from Space Shuttle and Space Station technologies. Systems engineering analysis also optimizes the overall architecture by considering all interfaces with the life support system and potential for reduction or reuse of resources. For long duration missions, technologies which aid in closure of air and water loops with increased reliability are essential as well as techniques to minimize or deal with waste. The ELS project utilizes in-house efforts at five NASA centers, aerospace industry contracts, Small Business Innovative Research contracts and other means to develop advanced life support technologies. Testing, analysis and reduced gravity flight experiments are also conducted at the NASA field centers. This paper gives a current status of technologies under development by ELS and relates them to the Constellation customers who will eventually use them.

Ewert, Michael K.↗

The Behavior, Constraint, and Scenario (BeCoS) Tool: A Web-Based Software Application for Modeling Behaviors and Scenarios

The Behavior, Constraint, and Scenario (BeCoS) tool has been developed to allow engineers to specify system and component behaviors. The tool is a web application that is developed in JavaScript and uses the React framework for the user interface and Redux for maintaining application state. The foundation of the tool is its underlying ontology, which expands upon a previously-defined behavior ontology with a scenario ontology. The behavior ontology includes elements like behaving elements, state variables, parameters, and constraints, while the scenario ontology includes core constructs like activities, temporal constraints, and timepoints. BeCoS allows users to easily create behaving elements and to specify their state variables, parameters, state machines, and constraints. BeCoS also allows users to develop temporal constraint networks that specify constraints on component states over time. BeCoS is a prototype tool that has been deployed and tested by systems engineers on the Europa Clipper project, which generated several use cases and helped steer its current developmental effort. By enabling systems engineers to specify behavior in a semantically-rigorous manner, BeCoS is an enabling technology for analyses that previously could not be performed, and when exporting its model to other tools, allows for consistent behavior models to be used.

Ingham, Michel D.↗

The Behavior, Constraint, and Scenario (BeCoS) Tool: A Web-Based Software Application for Modeling Behaviors and Scenarios

The Behavior, Constraint, and Scenario (BeCoS) tool has been developed to allow engineers to specify system and component behaviors. The tool is a web application that is developed in JavaScript and uses the React framework for the user interface and Redux for maintaining application state. The foundation of the tool is its underlying ontology, which expands upon a previously-defined behavior ontology with a scenario ontology. The behavior ontology includes elements like behaving elements, state variables, parameters, and constraints, while the scenario ontology includes core constructs like activities, temporal constraints, and timepoints. BeCoS allows users to easily create behaving elements and to specify their state variables, parameters, state machines, and constraints. BeCoS also allows users to develop temporal constraint networks that specify constraints on component states over time. BeCoS is a prototype tool that has been deployed and tested by systems engineers on the Europa Clipper project, which generated several use cases and helped steer its current developmental effort. By enabling systems engineers to specify behavior in a semantically-rigorous manner, BeCoS is an enabling technology for analyses that previously could not be performed, and when exporting its model to other tools, allows for consistent behavior models to be used.

Inghams, Michel D.↗

Exploration Life Support Critical Questions for Future Human Space Missions

Exploration Life Support (ELS) is a project under NASA s Exploration Technology Development Program. The ELS Project plans, coordinates and implements the development of advanced life support technologies for human exploration missions in space. Recent work has focused on closed loop atmosphere and water systems for a lunar outpost, including habitats and pressurized rovers. But, what are the critical questions facing life support system developers for these and other future human missions? This paper explores those questions and discusses how progress in the development of ELS technologies can help answer them. The ELS Project includes Atmosphere Revitalization Systems (ARS), Water Recovery Systems (WRS), Waste Management Systems (WMS), Habitation Engineering, Systems Integration, Modeling and Analysis (SIMA), and Validation and Testing, which includes the sub-elements Flight Experiments and Integrated Testing. Systems engineering analysis by ELS seeks to optimize the overall mission architecture by considering all the internal and external interfaces of the life support system and the potential for reduction or reuse of commodities. In particular, various sources and sinks of water and oxygen are considered along with the implications on loop closure and the resulting launch mass requirements.

Ewert, Michael K.↗

NASA Risk Management Handbook

The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.

Dezfuli, Homayoon↗

Exploration Medical System Technical Development

The Exploration Medical Capability (ExMC) Element systems engineering goals include defining the technical system needed to implement exploration medical capabilities for Mars. This past year, scenarios captured in the medical system concept of operations laid the foundation for systems engineering technical development work. The systems engineering team analyzed scenario content to identify interactions between the medical system, crewmembers, the exploration vehicle, and the ground system. This enabled the definition of functions the medical system must provide and interfaces to crewmembers and other systems. These analyses additionally lead to the development of a conceptual medical system architecture. The work supports the ExMC community-wide understanding of the functional exploration needs to be met by the medical system, the subsequent development of medical system requirements, and the system verification and validation approach utilizing terrestrial analogs and precursor exploration missions.

McGuire, K.↗

ALS engine controller system

This report summarizes analysis and design done on the controller system for the Advanced Launch System (ALS) main engine.

Payne, Roger↗

Engine protection system for recoverable rocket booster

A rocket engine protection system for a recoverable rocket booster which is arranged to land in a salt water body in substantially a nose down attitude. The system includes an inflatable bag which is stowed on a portion of a flat annular rim of the aft skirt of the booster. The bag is hinged at opposing sides and is provided with springs that urge the bag open. The bag is latched in a stowed position during launch and prior to landing for recovery is unlatched to permit the bag to be urged open and into sealing engagement with the rim. A source of pressurized gas further inflates the bag and urges it into sealing engagement with the rim of the skirt where it is locked into position. The gas provides a positive pressure upon the interior of the bag to preclude entry of salt water into the skirt and into contact with the engine. A flotation arrangement may assist in precluding the skirt of the booster from becoming submerged.

Shelby, Jr., Jerry A.↗