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,405 records · Page 78

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↗

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

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

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

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

MOS↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability that can spawn a new approach to mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low TRL concepts into workable solutions for issues in trash management, CO2 processing, foam re-processing, and fecal processing. The results of the crowdsourcing activities are summarized along with a roadmap for future technology development work.

Logistics reduction↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability leading to innovative approaches to space mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low Technology Readiness Level (TRL) concepts into workable solutions for issues in trash management, CO 2 processing, foam reprocessing, and fecal processing. The results of the crowdsourcing activities are summarized along with a discussion for future technology development work.

Logistics reduction↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability leading to innovative approaches to space mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low Technology Readiness Level (TRL) concepts into workable solutions for issues in trash management, CO2 processing, foam reprocessing, and fecal processing. The results of the crowdsourcing activities are summarized along with a discussion for future technology development work.

Logistics reduction↗

Effects of Aircraft Health on Airspace Safety

This manuscript investigates the effects of aircraft health on the surrounding airspace, and proposes a methodology to understand how different aircraft-level faults (system faults, communication faults, etc.) can adversely affect the safety of the airspace, and qualitatively assess the impact of such faults on airspace safety metrics (such as congestion, controller/pilot workload, etc.). The topic of systems health management deals with continuously monitoring the performance of an engineering system, identifying and detecting the presence of faults, predicting the growth/progression of faults, computing the remaining useful life, and aiding online decision-making for the robust, continued operation of such engineering systems. The topic of real-time airspace modeling and safety analysis deals with defining and computing safety metrics for airspace operations in order to support risk-informed decision-making activities for various airspace entities including pilots, air traffic controllers, airlines, etc. This report presents recent research efforts that focus on combining multiple aspects of the aforementioned topics, and investigates the impact of aircraft-level faults on the airspace safety

Aircraft Health↗

Orbit Transfer Vehicle (OTV) advanced expander cycle engine point design study. Task 7: Engine data summary

A performance optimized engine system design for a man-rated advanced LOX/hydrogen expander cycle engine was investigated. The data are presented in tables, figures, and drawings. The following categories of data for the advanced expander cycle engine are presented: engine operating specification and pressure schedule; engine system layout drawing; major component layout drawings, including thrust chamber and nozzle, extendible nozzle actuating mechanism and seal, LOX turbopump, LOX boost pump, hydrogen turbopump, hydrogen boost pump, and propellant control valves; engine performance and service life prediction; engine weight; and engine envelope. The data represent updates based upon current results from the design and analyses tasks performed under contract. Futher iterations in the designs and data can be expected as the advanced expander cycle engine design matures.

Christensen, K. L.↗

I(sup STAR), NASA's Next Step in Air-Breathing Propulsion for Space Access

The United States' National Aeronautics and Space Administration (NASA) has established a strategic plan for future activities in space. A primary goal of this plan is to make drastic improvements in the cost and safety of earth to low-earth-orbit transportation. One approach to achieving this goal is through the development of highly reusable, highly reliable space transportation systems analogous to the commercial airline system. In the year 2000, NASA selected the Rocket Based Combined Cycle (RBCC) engine as the next logical step towards this goal. NASA will develop a complete flight-weight, pump-fed engine system under the Integrated System Test of an Airbreathing Rocket (I(sup STAR)) Project. The objective of this project is develop a reusable engine capable of self-powering a vehicle through the air-augmented rocket, ramjet and scramjet modes required in all RBCC based operational vehicle concepts. The project is currently approved and funded to develop the engine through ground test demonstration. Plans are in place to proceed with flight demonstration pending funding approval. The project is in formulation phase and the Preliminary Requirements Review has been completed. The engine system and vehicle have been selected at the conceptual level. The I(sup STAR) engine concept is based on an air-breathing flowpath downselected from three configurations evaluated in NASA's Advanced Reusable Technology contract. The selected flowpath features rocket thrust chambers integrated into struts separating modular flowpath ducts, a variable geometry inlet, and a thermally choked throat. The engine will be approximately 220 inches long and 79 inches wide and fueled with a hydrocarbon fuel using liquid oxygen as the primary oxidizer candidate. The primary concept for the pump turbine drive is pressure-fed catalyzed hydrogen peroxide. In order to control costs, the flight demonstration vehicle will be launched from a B-52 aircraft. The vehicle concept is based on the Air Breathing Launch Vehicle 4 (ABLV4) lifting body configuration which has design heritage from NASA's NASP Program. The vehicle will be designed to accelerate from Mach 0.8 to Mach 7 and will be equipped with landing gear for horizontal landing. The complete vehicle, including the engine, will be designed for 25 flights and will be approximately 33 feet long with a total vehicle weight of approximately 25000 lbs.

Hutt, John J.↗

NTP comparison process

The systems engineering process for the concept definition phase of the program involves requirements definition, system definition, and consistent concept definition. The requirements definition process involves obtaining a complete understanding of the system requirements based on customer needs, mission scenarios, and nuclear thermal propulsion (NTP) operating characteristics. A system functional analysis is performed to provide a comprehensive traceability and verification of top-level requirements down to detailed system specifications and provides significant insight into the measures of system effectiveness to be utilized in system evaluation. The second key element in the process is the definition of system concepts to meet the requirements. This part of the process involves engine system and reactor contractor teams to develop alternative NTP system concepts that can be evaluated against specific attributes, as well as a reference configuration against which to compare system benefits and merits. Quality function deployment (QFD), as an excellent tool within Total Quality Management (TQM) techniques, can provide the required structure and provide a link to the voice of the customer in establishing critical system qualities and their relationships. The third element of the process is the consistent performance comparison. The comparison process involves validating developed concept data and quantifying system merits through analysis, computer modeling, simulation, and rapid prototyping of the proposed high risk NTP subsystems. The maximum amount possible of quantitative data will be developed and/or validated to be utilized in the QFD evaluation matrix. If upon evaluation of a new concept or its associated subsystems determine to have substantial merit, those features will be incorporated into the reference configuration for subsequent system definition and comparison efforts.

Corban, Robert↗

Highly integrated digital engine control system on an F-15 airplane

The Highly Integrated Digital Electronic Control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine/airframe control systems. This system is being used on the F-15 airplane. An integrated flightpath management mode and an integrated adaptive engine stall margin mode are implemented into the system. The adaptive stall margin mode is a highly integrated mode in which the airplane flight conditions, the resulting inlet distortion, and the engine stall margin are continuously computed; the excess stall margin is used to uptrim the engine for more thrust. The integrated flightpath management mode optimizes the flightpath and throttle setting to reach a desired flight condition. The increase in thrust and the improvement in airplane performance is discussed.

Burcham, F. W., Jr.↗

Hierarchical multi-time-scale predictive thermal management and fuel optimization for heavy-duty compression ignition engines

For heavy-duty diesel engines, NO X emissions reduction is strongly constrained by fuel efficiency. This paper presents a hierarchical model predictive controller (H-MPC) for coordinated control of tailpipe NO X emissions and fuel consumption. The H-MPC uses the separation of slow and fast dynamics that exist in the engine and its aftertreatment system. The controller is synthesized with an architecture in which a high-level MPC uses a longer prediction horizon compared to the low-level predictive controller which tracks the high-level controller command and manages the thermal dynamics of the aftertreatment system. Engine load preview enables the high-level controller to estimate the desired catalyst temperature ahead of time and addresses the selective catalytic reduction (SCR) slow thermal dynamics. Calculated by the high-level controller, the intake manifold pressure, and the start of injection (SOI) crank angle is used as reference trajectories in the low-level controller that regulates fast dynamical behaviors such as engine out NO X emissions. Hardware-in-the-loop (HIL) validation of this integrated H-MPC on a rapid prototype controller shows that when the SCR catalyst temperature is above light-off temperature (warmed-up condition), the engine operation is shifted to operate with the best fuel economy since the warmed-up SCR can efficiently reduce the engine-out NO X emissions. Results indicate that up to 0.8% benefit in cycle averaged BSFC along with a 13% reduction in tailpipe NO X compared to a stock engine calibration can be achieved with the coordinated engine and aftertreatment system through H-MPC.

Engineering↗

A Reference Model for Software and System Inspections. White Paper

Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level.

He, Lulu↗

The Advanced Modeling, Simulation and Analysis Capability Roadmap Vision for Engineering

This paper summarizes a subset of the Advanced Modeling Simulation and Analysis (AMSA) Capability Roadmap that was developed for NASA in 2005. The AMSA Capability Roadmap Team was chartered to "To identify what is needed to enhance NASA's capabilities to produce leading-edge exploration and science missions by improving engineering system development, operations, and science understanding through broad application of advanced modeling, simulation and analysis techniques." The AMSA roadmap stressed the need for integration, not just within the science, engineering and operations domains themselves, but also across these domains. Here we discuss the roadmap element pertaining to integration within the engineering domain, with a particular focus on implications for future observatory missions. The AMSA products supporting the system engineering function are mission information, bounds on information quality, and system validation guidance. The Engineering roadmap element contains 5 sub-elements: (1) Large-Scale Systems Models, (2) Anomalous Behavior Models, (3) advanced Uncertainty Models, (4) Virtual Testing Models, and (5) space-based Robotics Manufacture and Servicing Models.

Zang, Thomas↗