Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Systems Engineering”

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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Systems Engineering for the PRANDTL-D 3c Aircraft

The purpose of the Preliminary Research in AerodyNamicDesign to Lower Drag (PRANDTL-D) project is to show that birds fly using a "bell" shaped spanload rather than using an elliptical shaped spanload and to demonstrate the extensive benefits of this alternative spanload. This validation is done by flying a research glider with a twenty five foot wingspan that collects a range of parameters in flight. To ensure the data collection computers and suite of sensors work together and mesh well with the aircraft, systems engineering principles are applied. Needs for new one-off parts require a systems engineering approach as all the criteria of the plane, such as aerodynamics, structures, and avionics, must be taken into account when making decisions. The result of this approach were effective solutions that had a minimal negative impact on other systems that were not related to the original problem.

Larson, James G.↗
NASA NTRS1973

Systems engineering at the Jet Propulsion Laboratory.

Work at the JPL in systems engineering is surveyed with the emphasis on practical experience with large hardware and software systems. Systems concepts in lunar and planetary projects, in the Morgantown project, and in the Urban Health Systems Task are discussed. Goal definition, problem statement, objective and criteria development, and synthesis, analysis, selection and implementation of systems are considered as successive steps in the optimization of the overall system.-

Pickering, W. H.↗
NASA NTRS1990

Intelligent systems engineering methodology

An added challenge for the designers of large scale systems such as Space Station Freedom is the appropriate incorporation of intelligent system technology (artificial intelligence, expert systems, knowledge-based systems, etc.) into their requirements and design. This presentation will describe a view of systems engineering which successfully addresses several aspects of this complex problem: design of large scale systems, design with requirements that are so complex they only completely unfold during the development of a baseline system and even then continue to evolve throughout the system's life cycle, design that involves the incorporation of new technologies, and design and development that takes place with many players in a distributed manner yet can be easily integrated to meet a single view of the requirements. The first generation of this methodology was developed and evolved jointly by ISX and the Lockheed Aeronautical Systems Company over the past five years on the Defense Advanced Research Projects Agency/Air Force Pilot's Associate Program, one of the largest, most complex, and most successful intelligent systems constructed to date. As the methodology has evolved it has also been applied successfully to a number of other projects. Some of the lessons learned from this experience may be applicable to Freedom.

Fouse, Scott↗
NASA NTRS1980

Coal gasification systems engineering and analysis. Volume 1: Executive summary

Feasibility analyses and systems engineering studies for a 20,000 tons per day medium Btu (MBG) coal gasification plant to be built by TVA in Northern Alabama were conducted. Major objectives were as follows: (1) provide design and cost data to support the selection of a gasifier technology and other major plant design parameters, (2) provide design and cost data to support alternate product evaluation, (3) prepare a technology development plan to address areas of high technical risk, and (4) develop schedules, PERT charts, and a work breakdown structure to aid in preliminary project planning. Volume one contains a summary of gasification system characterizations. Five gasification technologies were selected for evaluation: Koppers-Totzek, Texaco, Lurgi Dry Ash, Slagging Lurgi, and Babcock and Wilcox. A summary of the trade studies and cost sensitivity analysis is included.

Source record↗
NASA NTRSDate not supplied

Artemis I Orion ESM Propulsion System Engine Performance

NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine(OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging f rom STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.

liquid propulsion systems↗
NASA NTRSDate not supplied

Artemis I Orion ESM Propulsion System Engine Performance

NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine (OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty-four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging from STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.

liquid propulsion systems↗
NASA NTRS1993

Systems engineering and the user: Incorporation of user requirements into the SE process

This paper is organized into four parts. In the Gestation Phase, I describe the process of starting a new mission and establishing its rough boundaries. Next I show how the scientific experiments are selected. Then we enter the Preliminary Design Phase, where we incorporate the scientist's instruments into the systems engineering process. Finally, I show how the Preliminary Design Review (PDR) assures NASA management and the scientists that the scientific requirements have been incorporated into the systems engineering process to everyone's satisfaction.

Naugle, John E.↗
NASA NTRS1991

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

Wray, Richard B.↗
DOE OSTI2020

Systems Theory Principles and Complex Systems Engineering Concepts for Protection and Resilience in Critical Infrastructure: Lessons from the Nuclear Sector

Part of the Presidential Policy Directive 21 (PPD-21) (PPD 2013) mandate includes evaluating safety, security, and safeguards (or nonproliferation) mechanisms traditionally implemented within the nuclear reactors, materials, and waste sector of critical infrastructure—including a complex, dynamic set of risks and threats within an all-hazards approach. In response, research out of Sandia National Laboratories (Sandia) explores the ability of systems theory principles (hierarchy and emergence) and complex systems engineering concepts (multidomain interdependence) to better understand and address these risks and threats. Herein, this Sandia research explores the safety, safeguards, and security risks of three different nuclear sector-related activities—spent nuclear fuel transportation, small modular reactors, and portable nuclear power reactors—to investigate the complex and dynamic risk related to the PPD-21-mandated all-hazards approach. This research showed that a systems-theoretic approach can better identify inter-dependencies, conflicts, gaps, and leverage points across traditional safety, security, and safeguards hazard mitigation strategies in the nuclear reactors, materials, and waste sector. Resulting from this, mitigation strategies from applying systems theoretic principles and complex systems engineering concepts can be (1) designed to better capture interdependencies, (2) implemented to better align with real-world operational uncertainties, and (3) evaluated as a systems-level whole to better identify, characterize, and manage PPD-21's all hazards strategies.

42 ENGINEERING↗
NASA NTRS2020

Pattern Identification - A Foundation for Research in the Emphasis of Design Patterns in Systems Engineering and Knowledge Capture

Pattern Language describes the morphology and functionality of a system in the absence of design particulars. Harnessing this capability will provide the Systems Engineering discipline a means of managing the development of increasingly complex systems with increasingly distributed design teams while capturing and retaining knowledge for future generations. Pattern Language is a syntax for describing, and structurally relating, design patterns. Design patterns contextually describe the application of domain knowledge in the engineered solution to the force balance problem. The parallels between pattern recognition and application, as a fundamental stage of human learning, and pattern observation within a complex system, suggests pattern language may be a valuable tool in the capture and dissemination of knowledge. Pattern application has enjoyed considerable study over the last several decades, however much of this work has focused on the replication of design particulars. This work returns to the roots of Pattern Language and explores the utility of patterns as an architectural description and guide, and knowledge capture method, for complex system development beginning with the identification of a time proven design pattern.

Russell, Samuel P.↗
NASA NTRS2005

ESMD Risk Management Workshop: Systems Engineering and Integration Risks

This report has been developed by the National Aeronautics and Space Administration (NASA) Exploration Systems Mission Directorate (ESMD) Risk Management team in close coordination with the Systems Engineering Team. This document provides a point-in-time, cumulative, summary of key lessons learned derived from the SE RFP Development process. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

Systems Engineering↗
NASA NTRS1997

General Aviation Propulsion (GAP) Program, Turbine Engine System Element

The goal of the General Aviation Propulsion (GAP) Program Turbine Engine System Elements is to conduct a shared resource project to develop an affordable gas turbine engine for use on 4 to 6 place, light aircraft that will lead to revitalization of the general aviation industry in the United States, creating many new, high-quality jobs.

Source record↗
DOE OSTI2019

Circular Economy - A challenge and an opportunity for Process Systems Engineering

Rising populations put huge stresses on natural resources. Extraction and depletion of raw materials and waste created throughout the supply chain of products have enormous environmental and socioeconomic impacts. One way to reduce these impacts is through the move towards the circular economy (CE). CE aims to solve resource, waste, and emission challenges confronting society by creating a production-to-consumption total supply chain that is restorative, regenerative, and environmentally benign. This article highlights research challenges and identifies process systems engineering (PSE) research opportunities to assist in the understanding, analysis and optimization of CE supply chains. A motivating example on the supply chain of coffee is introduced to illustrate the challenges of the transition towards a CE and to propose PSE research opportunities.

42 ENGINEERING↗
NASA NTRS2002

CloudSat system engineering: techniques that point to a future success

Over the past three years the CloutSat Project, a NASA Earth System Science Pathfinder mission to provide from space the first global survey of cloud profiles and cloud physical properties, has implemented a successful project system engineering approach. Techniques learned through heuristic reasoning of past project events and professional experience were applied along with select methods recently touted to increase effectiveness without compromising effiency.

CloudSat system engineering project management↗
NASA NTRS1993

Optimization in the systems engineering process

The essential elements of the design process consist of the mission definition phase that provides the system requirements, the conceptual design, the preliminary design and finally the detailed design. Mission definition is performed largely by operations analysts in conjunction with the customer. The result of their study is handed off to the systems engineers for documentation as the systems requirements. The document that provides these requirements is the basis for the further design work of the design engineers at the Lockheed-Georgia Company. The design phase actually begins with conceptual design, which is generally conducted by a small group of engineers using multidisciplinary design programs. Because of the complexity of the design problem, the analyses are relatively simple and generally dependent on parametric analyses of the configuration. The result of this phase is a baseline configuration from which preliminary design may be initiated.

Lemmerman, Loren A.↗
NASA NTRS1997

The MUSES Satellite Team and Multidisciplinary System Engineering

In a unique partnership between three minority-serving institutions and NASA's Jet Propulsion Laboratory, a new course sequence, including a multidisciplinary capstone design experience, is to be developed and implemented at each of the schools with the ambitious goal of designing, constructing and launching a low-orbit Earth-resources satellite. The three universities involved are North Carolina A&T State University (NCA&T), University of Texas, El Paso (UTEP), and California State University, Los Angeles (CSULA). The schools form a consortium collectively known as MUSES - Minority Universities System Engineering and Satellite. Four aspects of this project make it unique: (1) Including all engineering disciplines in the capstone design course, (2) designing, building and launching an Earth-resources satellite, (3) sustaining the partnership between the three schools to achieve this goal, and (4) implementing systems engineering pedagogy at each of the three schools. This paper will describe the partnership and its goals, the first design of the satellite, the courses developed at NCA&T, and the implementation plan for the course sequence.

Chen, John C.↗