Search NASA⌕ Search

SEARCH · Search NASA

Results for “system engineering program”

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 703 records · Page 39

Simulating a small turboshaft engine in real-time multiprocessor simulator (RTMPS) environment

A Real-Time Multiprocessor Simulator (RTMPS) has been developed at NASA Lewis Research Center. The RTMPS uses parallel microprocessors to achieve computing speeds needed for real-time engine simulation. This report describes the use of the RTMPS system to simulate a small turboshaft engine. The process of programming the engine equations and distributing them over one, two, and four processors is discussed. Steady-state and transient results from the RTMPS simulation are compared with results from a main-frame-based simulation. Processor execution times and the associated execution time savings for the two and four processor cases are presented using actual data obtained from the RTMPS system. Included is a discussion of why the minimum achievable calculation time for the turboshaft engine model was attained using four processors. Finally, future enhancements to the RTMPS system are discussed including the development of a generalized partitioning algorithm to automatically distribute the system equations among the processors in optimum fashion.

Milner, E. J.↗

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↗

Integrated Analysis Capability Program

Integrated Analysis Capability (IAC) software system intended to provide highly effective, interactive analysis tool for integrated design of large structures. Supports needs of engineering analysis groups concerned with interdisciplinary problems. Developed to serve as software interface between computer programs from fields of structures, thermodynamics, controls, and dynamics of systems on one hand and executive software system and data base on other hand to yield highly efficient multi-disciplinary system. Special attention given to such users' requirements as handling data and online assistance with operational features and ability to add new modules of user's choice at future date. Written in FORTRAN 77.

Vos, R. G.↗

Orion Service Module Reaction Control System Plume Impingement Analysis Using PLIMP/RAMP2

The Orion Crew Exploration Vehicle Service Module Reaction Control System engine plume impingement was computed using the plume impingement program (PLIMP). PLIMP uses the plume solution from RAMP2, which is the refined version of the reacting and multiphase program (RAMP) code. The heating rate and pressure (force and moment) on surfaces or components of the Service Module were computed. The RAMP2 solution of the flow field inside the engine and the plume was compared with those computed using GASP, a computational fluid dynamics code, showing reasonable agreement. The computed heating rate and pressure using PLIMP were compared with the Reaction Control System plume model (RPM) solution and the plume impingement dynamics (PIDYN) solution. RPM uses the GASP-based plume solution, whereas PIDYN uses the SCARF plume solution. Three sets of the heating rate and pressure solutions agree well. Further thermal analysis on the avionic ring of the Service Module showed that thermal protection is necessary because of significant heating from the plume.

Wang, Xiao-Yen J.↗

Orion Service Module Reaction Control System Plume Impingement Analysis Using PLIMP/RAMP2

The Orion Crew Exploration Vehicle Service Module Reaction Control System engine plume impingement was computed using the plume impingement program (PLIMP). PLIMP uses the plume solution from RAMP2, which is the refined version of the reacting and multiphase program (RAMP) code. The heating rate and pressure (force and moment) on surfaces or components of the Service Module were computed. The RAMP2 solution of the flow field inside the engine and the plume was compared with those computed using GASP, a computational fluid dynamics code, showing reasonable agreement. The computed heating rate and pressure using PLIMP were compared with the Reaction Control System plume model (RPM) solution and the plume impingement dynamics (PIDYN) solution. RPM uses the GASP-based plume solution, whereas PIDYN uses the SCARF plume solution. Three sets of the heating rate and pressure solutions agree well. Further thermal analysis on the avionic ring of the Service Module was performed using MSC Patran/Pthermal. The obtained temperature results showed that thermal protection is necessary because of significant heating from the plume.

Wang, Xiao-Yen↗

Blade loss transient dynamics analysis, volume 1. Task 1: Survey and perspective

An analytical technique was developed to predict the behavior of a rotor system subjected to sudden unbalance. The technique is implemented in the Turbine Engine Transient Rotor Analysis (TETRA) computer program using the component element method. The analysis was particularly aimed toward blade-loss phenomena in gas turbine engines. A dual-rotor, casing, and pylon structure can be modeled by the computer program. Blade tip rubs, Coriolis forces, and mechanical clearances are included. The analytical system was verified by modeling and simulating actual test conditions for a rig test as well as a full-engine, blade-release demonstration.

Gallardo, V. C.↗

NASA's Discovery Program: Moving Toward the Edge (of the Solar System)

NASA's Planetary Science , Division sponsors a competitive program of small spacecraft missions with the goal of performing focused science investigations that complement NASA's larger planetary science explorations at relatively low cost. The goal of the Discovery program is to launch many smaller missions with fast development times to increase our understanding of the solar system by exploring the planets, dwarf planets, their moons, and small bodies such as comets and asteroids. Discovery missions are solicited from the broad planetary science community approximately every 2 years. Active missions within the Discovery program include several with direct scientific or engineering connections to potential future missions to the edge of the solar system and beyond. In addition to those in the Discovery program are the missions of the New Frontiers program. The first New Frontiers mission. is the New Horizons mission to Pluto, which will explore this 38-AU distant dwarf planet and potentially some Kuiper Belt objects beyond. The Discovery program's Dawn mission, when launched in mid-2007, will use ion drive as its primary propulsion system. Ion propulsion is one of only two technologies that appear feasible for early interstellar precursor missions with practical flight times. The Kepler mission will explore the structure and diversity of extrasolar planetary systems, with an emphasis on the detection of Earth-size planets around other stars. Kepler will survey nearby solar systems searching for planets that may fall within the habitable zone,' a region surrounding a star within which liquid water may exist on a planet's surface - an essential ingredient for life as we know it. With its open and competitive approach to mission selections, the Discovery program affords scientists the opportunity to propose missions to virtually any solar system destination. With its emphasis on science and proven openness to the use of new technologies such as ion propulsion, missions flown as part of the program will test out technologies needed for future very deep-space exploration and potentially take us to these difficult and distant destinations.

Johnson, Les↗

Conceptual design of an optic based engine control system

Use of optics in the aircraft engine control systems would provide immunity to electromagnetic effects (such as lightning, radar, and nuclear pulses) for flight and propulsion control systems located throughout the aircraft and in need of communication and would result in weight reduction. This paper discusses a conceptual design of an optic engine control system that is being developed by the Fiber Optic Control System Integration (FOCSI) program. The features inherent in each of the optic-based components of the optic system, which includes the on-engine full authority digital electonic control, optic sensors, optic-based actuators, and an optic data bus for communication with the aircraft flight control system are described in detail. The diagrams of the FOCSI control system and its components are included.

Davies, W. J.↗

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.

Gill, Paul S.↗

MUST - An integrated system of support tools for research flight software engineering

The objectives of NASA's MUST (Multipurpose User-oriented Software Technology) program at Langley Research Center are to cut the cost of producing software which effectively utilizes digital systems for flight research. These objectives will be accomplished by providing an integrated system of support software tools for use throughout the research flight software development process. A description of the overall MUST program and its progress toward the release of a first MUST system will be presented. This release includes: a special interactive user interface, a library of subroutines, assemblers, a compiler, automatic documentation tools, and a test and simulation system.

Straeter, T. A.↗

Airframe-propulsion system aerodynamic interference predictions at high transonic Mach numbers including off-design engine airflow effects

The transonic speed regime for airplanes at conditions where inlet spillage takes place is discussed. A wind tunnel test program to evaluate aerodynamic performance penalties associated with propulsion system installation and operation at subsonic through low supersonic speeds was conducted. The accuracy of analytic methods for predicting transonic engine airframe interference effects was assessed. Study variables included Mach number, angle of attack, relative nacelle location, and nacelle mass flow ratio. Results include test theory comparisons of forces as well as induced pressure fields. Prediction capability of induced shock wave strength and locations is assessed. It was found that large interference forces due to engine location and flow spillage occur at transonic speeds, that theory explains these effects; and that theory can predict quantitatively these effects.

Kulfan, R. M.↗

Mars 2020 Model Based Systems Engineering Pilot

The pilot study is led by the Integration Engineering group in NASA's Launch Services Program (LSP). The Integration Engineering (IE) group is responsible for managing the interfaces between the spacecraft and launch vehicle. This pilot investigates the utility of Model-Based Systems Engineering (MBSE) with respect to managing and verifying interface requirements. The main objectives of the pilot are to model several key aspects of the Mars 2020 integrated operations and interface requirements based on the design and verification artifacts from Mars Science Laboratory (MSL) and to demonstrate how MBSE could be used by LSP to gain further insight on the interface between the spacecraft and launch vehicle as well as to enhance how LSP manages the launch service. The method used to accomplish this pilot started through familiarization of SysML, MagicDraw, and the Mars 2020 and MSL systems through books, tutorials, and NASA documentation. MSL was chosen as the focus of the model since its processes and verifications translate easily to the Mars 2020 mission. The study was further focused by modeling specialized systems and processes within MSL in order to demonstrate the utility of MBSE for the rest of the mission. The systems chosen were the In-Flight Disconnect (IFD) system and the Mass Properties process. The IFD was chosen as a system of focus since it is an interface between the spacecraft and launch vehicle which can demonstrate the usefulness of MBSE from a system perspective. The Mass Properties process was chosen as a process of focus since the verifications for mass properties occur throughout the lifecycle and can demonstrate the usefulness of MBSE from a multi-discipline perspective. Several iterations of both perspectives have been modeled and evaluated. While the pilot study will continue for another 2 weeks, pros and cons of using MBSE for LSP IE have been identified. A pro of using MBSE includes an integrated view of the disciplines, requirements, and verifications leading up to launch. The model allows IE to understand the relationships between disciplines throughout test activities and verifications. Additionally, the relationships between disciplines and integration tasks are generally consistent. The model allows for the generic relationships and tasks to be captured and used throughout multiple mission models should LSP further pursue MBSE. A con of MBSE is the amount of time it takes upfront to understand MBSE and create a useful model. The upfront time it takes to create a useful model is heavily discussed in MBSE literature and is a consistent con throughout the known applications of MBSE. The need to understand SysML and the software chosen also poses the possibility of a "bottleneck" or one person being the sole MBSE user for the working group. The utility of MBSE will continue to be evaluated through the remainder of the study. In conclusion, the original objectives of the pilot study were to use artifacts from MSL to model key aspects of Mars 2020 and demonstrate how MBSE could be used by LSP to gain insight into the spacecraft and launch vehicle interfaces. Progress has been made in modeling and identifying the utility of MBSE to LSP IE and will continue to be made until the pilot study's conclusion in mid-August. The results of this study will produce initial models, modeling instructions and examples, and a summary of MBSE's utility for future use by LSP.

Dukes, Alexandra Marie↗

Flight Test of a Propulsion-Based Emergency Control System on the MD-11 Airplane with Emphasis on the Lateral Axis

A large, civilian, multi-engine transport MD-11 airplane control system was recently modified to perform as an emergency backup controller using engine thrust only. The emergency backup system, referred to as the propulsion-controlled aircraft (PCA) system, would be used if a major primary flight control system fails. To allow for longitudinal and lateral-directional control, the PCA system requires at least two engines and is implemented through software modifications. A flight-test program was conducted to evaluate the PCA system high-altitude flying characteristics and to demonstrate its capacity to perform safe landings. The cruise flight conditions, several low approaches and one landing without any aerodynamic flight control surface movement, were demonstrated. This paper presents results that show satisfactory performance of the PCA system in the longitudinal axis. Test results indicate that the lateral-directional axis of the system performed well at high attitude but was sluggish and prone to thermal upsets during landing approaches. Flight-test experiences and test techniques are also discussed with emphasis on the lateral-directional axis because of the difficulties encountered in flight test.

Burken, John J.↗

Space transfer vehicle concepts and requirements, volume 2, book 1

The objective of the systems engineering task was to develop and implement an approach that would generate the required study products as defined by program directives. This product list included a set of system and subsystem requirements, a complete set of optimized trade studies and analyses resulting in a recommended system configuration, and the definition of an integrated system/technology and advanced development growth path. A primary ingredient in the approach was the TQM philosophy stressing job quality from the inception. Included throughout the Systems Engineering, Programmatics, Concepts, Flight Design, and Technology sections are data supporting the original objectives as well as supplemental information resulting from program activities. The primary result of the analyses and studies was the recommendation of a single propulsion stage Lunar Transportation System (LTS) configuration that supports several different operations scenarios with minor element changes. This concept has the potential to support two additional scenarios with complex element changes. The space based LTS concept consists of three primary configurations--Piloted, Reusable Cargo, and Expendable Cargo.

Source record↗

Propulsion System

Adaptation of Titan II liquid propellant rocket engine for Gemini program

LIQUID PROPELLANT ROCKET ENGINE↗