Hydro-John engineering prototype, the design, development and fabrication of a waste management and water recovery system
Engineering prototype waste management and water recovery system for spacecrew
WATER RECOVERY↗
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.
A PPE Use Case on Configuration Management Approach for MBSE
Systems engineers worldwide have been working to implement Model-based Systems Engineering (MBSE) environments, tools, and methodologies. MBSE is a formalized application of modeling to support systems engineering, including requirements, design, analysis, verification, and validation activities over the project’s lifecycle[1]; MBSE captures the system data into a digital environment. Significant benefits of MBSE includes a reduction in the time in performing systems engineering activities and an improvement higher fidelity data production. As more Systems Engineers are using MBSE, the models it produces are becoming the source of truth for Systems Engineering artifacts. As we move towards using these models as the source of truth, a more rigorous Configuration Management (CM) infrastructure is needed. Many of the MBSE tools provide CM options but utilizing them efficiently and effectively can be challenging. More rigorous methods and tools are needed to assist with keeping track of changes in the model, making sure inadvertent changes to baseline data did not occur, visibility of changes in the different model versions, and the impacts of changes to the models. System engineers and configuration management personnel from the Power and Propulsion Element (PPE) project at NASA Glenn Research Center have been working to develop a modeling construct that allows models to be the source of truth and maintain a configuration managed baseline. This paper presents a process that leverages the existing CM tools and describes how PPE used this process to manage changes more rigorously. It will describe the process behind building the model architecture that utilizes the MBSE tool capabilities and the configuration management process. It will contain some of the advantages and disadvantages of the architecture that the PPE project had settled upon utilizing, as well as some enhanced capabilities that the PPE MBSE team has developed.
MBSE↗
Digital Prototyping Methods to Enable Product Development Analysis Cycle Compression in Aerospace Systems
Historically, the product development life cycle (spanning from origination of a systems concept to initial delivery or fielding) for large-scale aerospace systems is 10-25 years. Examples of recent programs exhibiting this timeline are the Space Shuttle (13 years), , International Space Station (18 years), NASA Hubble telescope (16 years), USAF F-35 Strike Fighter (22 years), Missile Defense Agency THAAD (21 years), USAF V-22 Osprey (26 years), USAF B-2 Spirt (19 years), US Army RAH-66 Comanche (22 years, cancelled prior to fielding), James Webb Space Telescope (25 years), Space Launch System (10 years). This list illustrates the challenges of developing and fielding a modern integrated multi-disciplinary aerospace system. These development timelines are often preceded by significant research and development programs and followed by multiple increments, blocks, or spirals to reach planned operational capability. In the modern era of aerospace system acquisition, there is significant pressure to reduce system development timelines to meet system objectives and enable competitiveness in the current industry and landscape. Across the aerospace industry, a range of rapid acquisition and prototyping programs are seeking to achieve system development within timelines considerably less than 10 years. Notably, in September of 2019, NASA issued a solicitation for the development and demonstration of a Human Landing System (HLS) to deliver humans to the lunar surface by 2024 (5 years) and for the development and demonstration of a more sustainable HLS by 2026 (7 years). Lengthy product development cycle timelines are a product of multiple factors ranging from programmatic, sociological, technical, and systems engineering issues. New approaches in systems engineering provide new ways to enable these compressed development timelines. These approaches employ expanded application of advanced systems engineering methods and cross-cutting digital tools to accelerate system development, utilizing digital prototyping to connect maturing sub-system or component technologies into system or system-of-systems hardware prototypes. Approaches such as the use of system integrating physics relationships to reduce the number of design analysis cycle iterations and state analysis modeling to reduce necessary software testing (and improving coverage of system execution scenarios) represent steps forward in reducing the engineering time needed to field new systems. In addition to cost, schedule and performance benefits, expanded digital exploration and demonstration reduce risk in live system test and demonstration. This incremental demonstration approach, where digital prototyping and demonstration leads and informs full system test and demonstration, could be more important for space applications because of the increased difficulty of test and demonstration of space systems and architectures. The Advanced Concepts Office (ACO) at Marshall Space Flight Center merges traditional multi-disciplinary concept definition methods with modern, cross-cutting systems engineering concepts to enable iterative design and analysis of space architectures and systems through coordinated, strategic management of human capital, technical processes, and technology. This paper provides an overview of that approach, including recent examples and a strategic path forward to enabling continued reduction of aerospace system product development life cycles.
Michael D Watson↗
A computer aided engineering tool for ECLS systems
The Computer-Aided Systems Engineering and Analysis tool used by NASA for environmental control and life support system design studies is capable of simulating atmospheric revitalization systems, water recovery and management systems, and single-phase active thermal control systems. The designer/analysis interface used is graphics-based, and allows the designer to build a model by constructing a schematic of the system under consideration. Data management functions are performed, and the program is translated into a format that is compatible with the solution routines.
Bangham, Michal E.↗
Design of Liquid Propellant Rocket Engines Second Edition
This book intends to build a bridge for the student and the young engineer: to link the rocket propulsion fundamentals and elements (which are well covered in the literature) with the actual rocket engine design and development work as it is carried out in industry (which is very little, if at all covered in literature). The book attempts to further the understanding of the realistic application of liquid rocket propulsion theories, and to help avoid or at least reduce time and money consuming errors and disappointments. In so doing, it also attempts to digest and consolidate numerous closely related subjects, hitherto often treated as separate, bringing them up to date at the same time. The book was written "on the job" for use by those active in all phases of engine systems design, development, and application, in industry as well as government agencies. Since it addresses itself to human beings set out to create new machines, rather than describing machines about to dominate man, the language chosen may not always be "functional" in the strict sense of the word. The book presents sufficient detail to familiarize and educate thoroughly those responsible for various aspects of liquid propellant rocketry, including engine systems design, engine development, and flight vehicle application. It should enable the rocket engineer to conduct, independently, complete or partial engine systems preliminary detail designs and to understand and judge the activities in, and the problems, limitations, and "facts of life~ of the various subsystems making up a complete engine system. It also attempts to educate those ultimately interested in specialized subsystems and component design (thrust chamber, turbopump, control valves, etc.) about their own as well as neighboring subsystems and about the complete engine system. This should enable the student to prepare realistic analytical calculations and design layouts with a long headstart toward the final specialized designs for subsystem production release. Special emphasis has been placed on engine flight application to stimulate engine systems and subsystem designers to think in these terms from the outset. The book is intended as a textbook, with specific consideration of the teacher without industry experience. We hope it will stimulate those desiring to specialize in the area of a rocket engine subsystem by supplying adequate information to enable them to benefit fully from the specialized literature. Thus, it provides a realistic expert introduction for those joining the liquid propellant rocket engine field.
Dieter K Huzel↗
Integrated modeling tool for performance engineering of complex computer systems
This report summarizes Advanced System Technologies' accomplishments on the Phase 2 SBIR contract NAS7-995. The technical objectives of the report are: (1) to develop an evaluation version of a graphical, integrated modeling language according to the specification resulting from the Phase 2 research; and (2) to determine the degree to which the language meets its objectives by evaluating ease of use, utility of two sets of performance predictions, and the power of the language constructs. The technical approach followed to meet these objectives was to design, develop, and test an evaluation prototype of a graphical, performance prediction tool. The utility of the prototype was then evaluated by applying it to a variety of test cases found in the literature and in AST case histories. Numerous models were constructed and successfully tested. The major conclusion of this Phase 2 SBIR research and development effort is that complex, real-time computer systems can be specified in a non-procedural manner using combinations of icons, windows, menus, and dialogs. Such a specification technique provides an interface that system designers and architects find natural and easy to use. In addition, PEDESTAL's multiview approach provides system engineers with the capability to perform the trade-offs necessary to produce a design that meets timing performance requirements. Sample system designs analyzed during the development effort showed that models could be constructed in a fraction of the time required by non-visual system design capture tools.
Wright, Gary↗
Second Generation RLV Space Vehicle Concept
NASA has a long history of conducting development programs and projects in a consistent fashion. Systems Engineering within those programs and projects has also followed a given method outlined by such documents as the NASA Systems Engineering Handbook. The relatively new NASA Space Launch Initiative (SLI) is taking a new approach to developing a space vehicle, with innovative management methods as well as new Systems Engineering processes. With the program less than a year into its life cycle, the efficacy of these new processes has yet to be proven or disproven. At $776M for phase 1, SLI represents a major portion of the NASA focus; however, the new processes being incorporated are not reflected in the training provided by NASA to its engineers. The NASA Academy of Program and Project Leadership (APPL) offers core classes in program and project management and systems engineering to NASA employees with the purpose of creating a "knowledge community where ideas, skills, and experiences are exchanged to increase each other's capacity for strong leadership". The SLI program is, in one sense, a combination of a conceptual design program and a technology program. The program as a whole doesn't map into the generic systems engineering project cycle as currently, and for some time, taught. For example, the NASA APPL Systems Engineering training course teaches that the "first step in developing an architecture is to define the external boundaries of the system", which will require definition of the interfaces with other systems and the next step will be to "define all the components that make up the next lower level of the system hierarchy" where fundamental requirements are allocated to each component. Whereas, the SLI technology risk reduction approach develops architecture subsystem technologies prior to developing architectures. The higher level architecture requirements are not allowed to fully develop and undergo decomposition and allocation down to the subsystems before the subsystems must develop allocated requirements based on the highest level of requirements. In the vernacular of the project cycles prior to the mid 1990's, the architecture definition portion of the program appears to be at a generic Phase A stage, while the subsystems are operating at Phase B. Even the management structure of the SLI program is innovative in its approach to Systems Engineering and is not reflected in the APPL training modules. The SLI program has established a Systems Engineering office as an office separate from the architecture development or the subsystem technology development, while that office does have representatives within these other offices. The distributed resources of the Systems Engineering Office are co-located with the respective Project Offices. This template is intended to provide systems engineering as an integrated function at the Program Level. the program management of SLI and the MAT agree that "program/project managers and the systems engineering team must work closely together towards the single objective of delivering quality products that meet the customer needs". This paper will explore the differences between the methods being taught by NASA, which represent decades of ideas, and those currently in practice in SLI. Time will tell if the innovation employed by SLI will prove to be the model of the future. For now, it is suggested that the training of the present exercise the flexibility of recognizing the new processes employed by a major new NASA program.
Bailey, Michelle↗
Performance of ion engines and systems for satellite control.
Ion engine satellite control system noting design and laboratory tests
OPTIMAL CONTROL↗
Condition monitoring requirements for the development of a space nuclear propulsion module
To facilitate the development of a space nuclear propulsion module for manned flights to Mars, requirements must be established early in the technology cycle. The long lead times for the acquisition of the engine system and nuclear test facilities demands that the engine system, size, performance, safety goals and condition monitoring philosophy be defined at the earliest possible time. These systems are highly complex and require a large multi-disciplinary systems engineering team to develop and track the requirements and to ensure that the as-built system reflects the intent of the mission. An effective methodology has been devised coupled with sophisticated computer tools to effectivly develop and interpret the functional requirements. These requirements can then be decomposed down to the specification level for implementation. This paper discusses the application of the methodology and the analyses to develop condition monitoring requirements under a contract with the National Aeronautics and Space Administration (NASA) Lewis Research Center (LeRC) Nuclear Propulsion Office (NPO).
Wagner, Robert C.↗
F-15 digital electronic engine control system description
A digital electronic engine control (DEEC) was developed for use on the F100-PW-100 turbofan engine. This control system has full authority control, capable of moving all the controlled variables over their full ranges. The digital computational electronics and fault detection and accomodation logic maintains safe engine operation. A hydromechanical backup control (BUC) is an integral part of the fuel metering unit and provides gas generator control at a reduced performance level in the event of an electronics failure. The DEEC's features, hardware, and major logic diagrams are described.
Myers, L. P.↗
Closed Environment Air Revitalization System Based on Metal Organic Framework Adsorbents
This project utilized a systems engineering methodology to develop a vacuum swing adsorption system with full Labview automated control. The project was successful and provided students with an introduction to systems engineering and air revitalization. Specifically, two stainless steel adsorption beds were custom designed and manufactured and a sequence of computer controlled valves were used to deliver CO 2 laden, humid air, to the adsorbent where the CO 2 was removed from the air stream. Runs were completed using 13X zeolite and bed timing and switching was controlled by the computer based on the data output of a CO 2 detector. Adsorption runs using the MOF have not been completed upon the writing of this report; however, the MOF material is currently being synthesized and the runs will be completed upon receipt of the material. A follow up meeting with NASA has been tentatively planned to discuss the output of these experiments. Consistent with systems engineering practice, an end of project assessment of the class was conducted with the students and several items were realized. Specifically, the short period of performance of this grant makes it necessary to maintain a narrowly focused scope on the project such that multiple experiments after systems development (T&E) need to be limited to ensure timely completion of the proposed tasks. Also, procurement of parts may need to be moved forward in time to allow for delivery delays, and it may be necessary to request SDR, PDR, and CDR dates from NASA that are ahead of the NASA anticipated schedule. These types of lessons provided valuable to both the PI and the students and ultimately illustrate the necessity of proper systems engineering schedule risk assessment. The class met the objectives of the project and provided an introduction to systems engineering to undergraduate students. As a metric of that success, the lead engineer of the undergraduate design team acquired a job with an aerospace defense contractor, which he attributed to his knowledge of systems engineering concepts that were acquired via the X-Hab class.
T. Grant Glover↗
Integrating MBSE into Ongoing Projects: Requirements Validation and Test Planning for the ISS SAFER
The International Space Station (ISS) Simplified Aid for Extra Vehicular Activity (EVA) Rescue (SAFER) is the spacewalking astronaut's final safety measure against separating from the ISS and being unable to return safely. Since the late 1990s, the SAFER has been a standard element of the spacewalking astronaut's equipment. The ISS SAFER project was chartered to develop a new block of SAFER units using a highly similar design to the legacy SAFER (known as the USA SAFER). An on-orbit test module was also included in the project to enable periodic maintenance/propulsion system checkout on the ISS SAFER. On the ISS SAFER project, model-based systems engineering (MBSE) was not the initial systems engineering (SE) approach, given the volume of heritage systems engineering and integration (SE&I) products. The initial emphasis was ensuring traceability to ISS program standards as well as to legacy USA SAFER requirements. The requirements management capabilities of the Cradle systems engineering tool were to be utilized to that end. During development, however, MBSE approaches were applied selectively to address specific challenges in requirements validation and test and verification (T&V) planning, which provided measurable efficiencies to the project. From an MBSE perspective, ISS SAFER development presented a challenge and an opportunity. Addressing the challenge first, the project was tasked to use the original USA SAFER operational and design requirements baseline, with a number of additional ISS program requirements to address evolving certification expectations for systems operating on the ISS. Additionally, a need to redesign the ISS SAFER avionics architecture resulted in a set of changes to the design requirements baseline. Finally, the project added an entirely new functionality for on-orbit maintenance. After initial requirements integration, the system requirements count was approaching 1000, which represented a growth of 4x over the original USA SAFER system. This presented the challenge - How to confirm that this new set of requirements set would result in the creation of the desired capability.
Anderson, Herbert A.↗
Explicit Finite Element Modeling of Multilayer Composite Fabric for Gas Turbine Engine Containment Systems, Phase II: Material Model Development and Simulation of Experiments - Part 3
A team consisting of Arizona State University, Honeywell Engines, Systems & Services, the National Aeronautics and Space Administration Glenn Research Center, and SRI International collaborated to develop computational models and verification testing for designing and evaluating turbine engine fan blade fabric containment structures. This research was conducted under the Federal Aviation Administration Airworthiness Assurance Center of Excellence and was sponsored by the Aircraft Catastrophic Failure Prevention Program. The research was directed toward improving the modeling of a turbine engine fabric containment structure for an engine blade-out containment demonstration test required for certification of aircraft engines. The research conducted in Phase II began a new level of capability to design and develop fan blade containment systems for turbine engines. Significant progress was made in three areas: (1) further development of the ballistic fabric model to increase confidence and robustness in the material models for the Kevlar(TradeName) and Zylon(TradeName) material models developed in Phase I, (2) the capability was improved for finite element modeling of multiple layers of fabric using multiple layers of shell elements, and (3) large-scale simulations were performed. This report concentrates on the material model development and simulations of the impact tests.
Zylon↗
HIDEC F-15 adaptive engine control system flight test results
NASA-Ames' Highly Integrated Digital Electronic Control (HIDEC) flight test program aims to develop fully integrated airframe, propulsion, and flight control systems. The HIDEC F-15 adaptive engine control system flight test program has demonstrated that significant performance improvements are obtainable through the retention of stall-free engine operation throughout the aircraft flight and maneuver envelopes. The greatest thrust increase was projected for the medium-to-high altitude flight regime at subsonic speed which is of such importance to air combat. Adaptive engine control systems such as the HIDEC F-15's can be used to upgrade the performance of existing aircraft without resort to expensive reengining programs.
Smolka, James W.↗
Explicit Finite Element Modeling of Multilayer Composite Fabric for Gas Turbine Engine Containment Systems: Ballistic Impact Testing - Part 2
Under the Federal Aviation Administration's Airworthiness Assurance Center of Excellence and the Aircraft Catastrophic Failure Prevention Program, National Aeronautics and Space Administration Glenn Research Center collaborated with Arizona State University, Honeywell Engines, Systems and Services, and SRI International to develop improved computational models for designing fabric-based engine containment systems. In the study described in this report, ballistic impact tests were conducted on layered dry fabric rings to provide impact response data for calibrating and verifying the improved numerical models. This report provides data on projectile velocity, impact and residual energy, and fabric deformation for a number of different test conditions.
ZYLON↗
Engineering stategies and implications of using higher plants for throttling gas and water exchange in a controlled ecological life support system
Engineering stategies for advanced life support systems to be used on Lunar and Mars bases involve a wide spectrum of approaches. These range from purely physical-chemical life support strategies to purely biological approaches. Within the context of biological based systems, a bioengineered system can be devised that would utilize the metabolic mechanisms of plants to control the rates of CO2 uptake and O2 evolution (photosynthesis) and water production (transpiration). Such a mechanism of external engineering control has become known as throttling. Research conducted at the John F. Kennedy Space Center's Controlled Ecological Life Support System Breadboard Project has demonstrated the potential of throttling these fluxes by changing environmental parameters affecting the plant processes. Among the more effective environmental throttles are: light and CO2 concentration for controllingthe rate of photsynthesis and humidity and CO2 concentration for controlling transpiration. Such a bioengineered strategy implies control mechanisms that in the past have not been widely attributed to life support systems involving biological components and suggests a broad range of applications in advanced life support system design.
Chamberland, Dennis↗
A Survey of Applications and Research in Integrated Design Systems Technology
The initial part of the study was begun with a combination of literature searches, World Wide Web searches, and contacts with individuals and companies who were known to members of our team to have an interest in topics that seemed to be related to our study. There is a long list of such topics, such as concurrent engineering, design for manufacture, life-cycle engineering, systems engineering, systems integration, systems design, design systems, integrated product and process approaches, enterprise integration, integrated product realization, and similar terms. These all capture, at least in part, the flavor of what we describe here as integrated design systems. An inhibiting factor in this inquiry was the absence of agreed terminology for the study of integrated design systems. It is common for the term to be applied to what are essentially augmented Computer-Aided Design (CAD) systems, which are integrated only to the extent that agreements have been reached to attach proprietary extensions to proprietary CAD programs. It is also common for some to use the term integrated design systems to mean a system that applies only, or mainly, to the design phase of a product life cycle. It is likewise common for many of the terms listed earlier to be used as synonyms for integrated design systems. We tried to avoid this ambiguity by adopting the definition of integrated design systems that is implied in the introductory notes that we provided to our contacts, cited earlier. We thus arrived at this definition: Integrated Design Systems refers to the integration of the different tools and processes that comprise the engineering, of complex systems. It takes a broad view of the engineering of systems, to include consideration of the entire product realization process and the product life cycle. An important aspect of integrated design systems is the extent to which they integrate existing, "islands of automation" into a comprehensive design and product realization environment. As the study progressed, we relied increasingly upon a networking approach to lead us to new information. The departure point for such searches often was a government-sponsored project or a company initiative. The advantage of this approach was that short conversations with knowledgeable persons would usually cut through confusion over differences of terminology, thereby somewhat reducing the search space of the study. Even so, it was not until late in our eight-month inquiry that we began to see signs of convergence of the search, in the sense that a number of the latest inquiries began to turn up references to earlier contacts. As suggested above, this convergence often occurred with respect to particular government or company projects.
Source record↗
Phase 1 of the First Small Power System Experiment (engineering Experiment No. 1). Volume 3: Experimental System Descriptions
The design and development of a modular solar thermal power system for application in the 1 to 10 MWe range is described. The system consists of five subsystems: the collector, power conversion, energy transport, energy storage, and the plant control subsystem. The collector subsystem consists of concentrator, receiver, and tower assemblies. The energy transport subsystem uses a mixture of salts with a low melting temperature to transport thermal energy. A steam generator drives a steam Rankine cycle turbine which drives an electrical generator to produce electricity. Thermal and stress analysis tests are performed on each subsystem in order to determine the operational reliability, the minimum risk of failure, and the maintenance and repair characteristics.
Holl, R. J.↗