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 1,207 records · Page 67
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

DRACO Flowpath Performance and Environments

The Advanced Space Transportation (AST) project office has challenged NASA to design, manufacture, ground-test and flight-test an axisymmetric, hydrocarbon-fueled, flight-weight, ejector-ramjet engine system testbed no later than 2005. To accomplish this, a multi-center NASA team has been assembled. The goal of this team, led by NASA-Marshall Space Flight Center (MSFC), is to develop propulsion technologies that demonstrate rocket and airbreathing combined-cycle operation (DRACO). Current technical activities include flowpath conceptual design, engine systems conceptual design, and feasibility studies investigating the integration and operation of the DRACO engine with a Lockheed D-21B drone. This paper focuses on the activities of the Flowpath Systems Product Development Team (PDT), led by NASA-Glenn Research Center (GRC) and supported by NASA-MSFC and TechLand Research, Inc. The objective of the Flowpath PDT at the start of the DRACO program was to establish a conceptual design of the flowpath aerodynamic lines, determine the preliminary performance, define the internal environments, and support the DRACO testbed concept feasibility studies. To accomplish these tasks, the PDT convened to establish a baseline flowpath concept. With the conceptual lines defined, cycle analysis tasks were planned and the flowpath performance and internal environments were defined. Additionally, sensitivity studies investigating the effects of inlet reference area, combustion performance, and combustor/nozzle materials selection were performed to support the Flowpath PDT design process. Results of these tasks are the emphasis of this paper and are intended to verify the feasibility of the DRACO flowpath and engine system as well as identify the primary technical challenges inherent in the flight-weight design of an advanced propulsion technology demonstration engine. Preliminary cycle performance decks were developed to support the testbed concept feasibility studies but are not discussed further in this paper.

Komar, D. R.↗
NASA NTRS1992

Knowledge modeling for software design

This paper develops a modeling framework for systems engineering that encompasses systems modeling, task modeling, and knowledge modeling, and allows knowledge engineering and software engineering to be seen as part of a unified developmental process. This framework is used to evaluate what novel contributions the 'knowledge engineering' paradigm has made and how these impact software engineering.

Shaw, Mildred L. G.↗
NASA NTRS2014

Engineering Antifragile Systems: A Change In Design Philosophy

While technology has made astounding advances in the last century, problems are confronting the engineering community that must be solved. Cost and schedule of producing large systems are increasing at an unsustainable rate and these systems often do not perform as intended. New systems are required that may not be achieved by current methods. To solve these problems, NASA is working to infuse concepts from Complexity Science into the engineering process. Some of these problems may be solved by a change in design philosophy. Instead of designing systems to meet known requirements that will always lead to fragile systems at some degree, systems should be designed wherever possible to be antifragile: designing cognitive cyberphysical systems that can learn from their experience, adapt to unforeseen events they face in their environment, and grow stronger in the face of adversity. Several examples are presented of on ongoing research efforts to employ this philosophy.

Jones, Kennie H.↗
NASA NTRS1991

Nuclear thermal rocket workshop reference system Rover/NERVA

The Rover/NERVA engine system is to be used as a reference, against which each of the other concepts presented in the workshop will be compared. The following topics are reviewed: the operational characteristics of the nuclear thermal rocket (NTR); the accomplishments of the Rover/NERVA programs; and performance characteristics of the NERVA-type systems for both Mars and lunar mission applications. Also, the issues of ground testing, NTR safety, NASA's nuclear propulsion project plans, and NTR development cost estimates are briefly discussed.

Borowski, Stanley K.↗
NASA NTRS1995

On the Development of a Computing Infrastructure that Facilitates IPPD from a Decision-Based Design Perspective

Integrated Product and Process Development (IPPD) embodies the simultaneous application of both system and quality engineering methods throughout an iterative design process. The use of IPPD results in the time-conscious, cost-saving development of engineering systems. Georgia Tech has proposed the development of an Integrated Design Engineering Simulator that will merge Integrated Product and Process Development with interdisciplinary analysis techniques and state-of-the-art computational technologies. To implement IPPD, a Decision-Based Design perspective is encapsulated in an approach that focuses on the role of the human designer in product development. The approach has two parts and is outlined in this paper. First, an architecture, called DREAMS, is being developed that facilitates design from a decision-based perspective. Second, a supporting computing infrastructure, called IMAGE, is being designed. The current status of development is given and future directions are outlined.

Hale, Mark A.↗
NASA NTRS1999

Stirling Space Engine Program: Final Report - Volume 1

The objective of this program was to develop the technology necessary for operating Stirling power converters in a space environment and to demonstrate this technology in full-scale engine tests. Hardware development focused on the Component Test Power Converter (CTPC), a single cylinder, 12.5-kWe engine. Design parameters for the CTPC were 150 bar operating pressure, 70 Hz frequency, and hot-and cold-end temperatures of 1050 K and 525 K, respectively. The CTPC was also designed for integration with an annular sodium heat pipe at the hot end, which incorporated a unique "Starfish" heater head that eliminated highly stressed brazed or weld joints exposed to liquid metal and used a shaped-tubed electrochemical milling process to achieve precise positional tolerances. Selection of materials that could withstand high operating temperatures with long life were another focus. Significant progress was made in the heater head (Udimet 700 and Inconel 718 and a sodium-filled heat pipe); the alternator (polyimide-coated wire with polyimide adhesive between turns and a polyimide-impregnated fiberglass overwrap and samarium cobalt magnets); and the hydrostatic gas bearings (carbon graphite and aluminum oxide for wear couple surfaces). Tests on the CTPC were performed in three phases: cold end testing (525 K), engine testing with slot radiant heaters, and integrated heat pipe engine system testing. Each test phase was successful, with the integrated engine system demonstrating a power level of 12.5 kWe and an overall efficiency of 22 percent in its maiden test. A 1500-hour endurance test was then successfully completed. These results indicate the significant achievements made by this program that demonstrate the viability of Stirling engine technology for space applications.

Dhar, Manmohan↗
NASA NTRS2003

Transient Simulation of the Integrated Powerhead Demonstrator (IPD) Rocket Engine

The IPD rocket engine is the product of a joint Air Force/NASA program to demonstrate the concept of a full-flow staged combustion power cycle. In this type of rocket engine cycle, both the entire fuel flow and the entire oxidizer flow are combusted in one of two pre-bumers and used to drive two turbopumps, thus utilizing the flow work of the total propellant flow. The basis of the IPD engine program relies on integrating newly developed and pre-existing hardware to demonstrate the component and material technologies to make this concept feasible, while simultaneously saving development time and costs. To provide insight to the project team and contractors during engine development and test phases, the engine system was modeled at MSFC using the Rocket Engine Transient Simulation (ROCETS) software to analyze system performance and determine component integration issues. The ROCETS software is used extensively a MSFC to perform steady-state power-balances and transient simulations of thermodynamic power and general fluid systems. The software is favored for its capability to solve large systems of non-linear equations, its librarie of fluid properties and flow devices, its flexibility to modify existing code to improve the physics-derived approximations of real fluid thermodynamic behavior, and the ability to add unique system constraints. The purpose of this paper is to present the methodology used to model the IPD engine system, detail the pitfalls encountered with the software, and explain the approximations made to more accurately represent engine component and fluid behavior. Engine system performance output from the model will be presented and explained in comparison with real fluid and component behavior.

Guidos, Mike↗
NASA NTRS1972

Performance and control study of a low-pressure-ratio turbojet engine for a drone aircraft

The results of analog and digital computer studies of a low-pressure-ratio turbojet engine system for use in a drone vehicle are presented. The turbojet engine consists of a four-stage axial compressor, single-stage turbine, and a fixed area exhaust nozzle. Three simplified fuel schedules and a generalized parameter fuel control for the engine system are presented and evaluated. The evaluation is based on the performance of each schedule or control during engine acceleration from a windmill start at Mach 0.8 and 6100 meters to 100 percent corrected speed. It was found that, because of the higher acceleration margin permitted by the control, the generalized parameter control exhibited the best dynamic performance.

Seldner, K.↗
NASA NTRS2012

Orion Flight Test 1 Architecture: Observed Benefits of a Model Based Engineering Approach

This paper details how a NASA-led team is using a model-based systems engineering approach to capture, analyze and communicate the end-to-end information system architecture supporting the first unmanned orbital flight of the Orion Multi-Purpose Crew Exploration Vehicle. Along with a brief overview of the approach and its products, the paper focuses on the observed program-level benefits, challenges, and lessons learned; all of which may be applied to improve system engineering tasks for characteristically similarly challenges

Multi-Purpose Crew Exploration Vehicle.↗
NASA NTRSDate not supplied

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗
NASA NTRS2012

Early Formulation Model-centric Engineering on Nasa's Europa Mission Concept Study

By leveraging the existing Model-Based Systems Engineering (MBSE) infrastructure at JPL and adding a modest investment, the Europa Mission Concept Study made striking advances in mission concept capture and analysis. This effort has reaffirmed the importance of architecting and successfully harnessed the synergistic relationship of system modeling to mission architecting. It clearly demonstrated that MBSE can provide greater agility than traditional systems engineering methods. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.

science mission afforability↗
NASA NTRSDate not supplied

Modeling NASA’s Procedural Requirement Processes – Implications for a Digital Future

The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions).

NPR↗
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

Mission Benefits Analysis of Logistics Reduction Technologies

Future space exploration missions will need to use less logistical supplies if humans are to live for longer periods away from our home planet. Anything that can be done to reduce initial mass and volume of supplies or reuse or recycle items that have been launched will be very valuable. Reuse and recycling also reduce the trash burden and associated nuisances, such as smell, but require good systems engineering and operations integration to reap the greatest benefits. A systems analysis was conducted to quantify the mass and volume savings of four different technologies currently under development by NASA fs Advanced Exploration Systems (AES) Logistics Reduction and Repurposing project. Advanced clothing systems lead to savings by direct mass reduction and increased wear duration. Reuse of logistical items, such as packaging, for a second purpose allows fewer items to be launched. A device known as a heat melt compactor drastically reduces the volume of trash, recovers water and produces a stable tile that can be used instead of launching additional radiation protection. The fourth technology, called trash ]to ]supply ]gas, can benefit a mission by supplying fuel such as methane to the propulsion system. This systems engineering work will help improve logistics planning and overall mission architectures by determining the most effective use, and reuse, of all resources.

Ewert, Michael K.↗
NASA NTRS2013

Mission Benefits Analysis of Logistics Reduction Technologies

Future space exploration missions will need to use less logistical supplies if humans are to live for longer periods away from our home planet. Anything that can be done to reduce initial mass and volume of supplies or reuse or recycle items that have been launched will be very valuable. Reuse and recycling also reduce the trash burden and associated nuisances, such as smell, but require good systems engineering and operations integration to reap the greatest benefits. A systems analysis was conducted to quantify the mass and volume savings of four different technologies currently under development by NASA s Advanced Exploration Systems (AES) Logistics Reduction and Repurposing project. Advanced clothing systems lead to savings by direct mass reduction and increased wear duration. Reuse of logistical items, such as packaging, for a second purpose allows fewer items to be launched. A device known as a heat melt compactor drastically reduces the volume of trash, recovers water and produces a stable tile that can be used instead of launching additional radiation protection. The fourth technology, called trash-to-gas, can benefit a mission by supplying fuel such as methane to the propulsion system. This systems engineering work will help improve logistics planning and overall mission architectures by determining the most effective use, and reuse, of all resources.

Ewert, Michael K.↗