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,027 records · Page 57
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Coupling Between Waveguide-Fed Slot Arrays

Coupling between two waveguide-fed planar slot arrays has been investigated using full-wave analysis. The analysis employs the method-of-moments solution to the pertinent coupled integral equations for the aperture electric field of all slots. In order to compute coupling between two arrays, the input port of the first array is excited with a TE(sub 10) mode wave while the second one is match-terminated. After solving the moment method matrix equations, the aperture fields of all slots are obtained and thereby the TE(sub 10) mode wave received at the input port of the second array is determined. Coupling between two arrays is the ratio of the wave amplitude arriving in the second array port to the incident wave amplitude at the first array port. The coupling mechanism has been studied as a function of spacing between arrays in different directions, e.g. the electric field plane, the magnetic field plane, and the diagonal plane. Computed coupling values are presented for different array geometries. This work is novel since it provides a good understanding of coupling between waveguide-fed slot arrays as a function of spacing and orientation for different aperture distributions and array architectures. This serves as a useful tool for antenna design engineers and system engineers.

Rengarajan, Sembiam↗
NASA NTRS2012

Assessment of NASA's Aircraft Noise Prediction Capability

A goal of NASA s Fundamental Aeronautics Program is the improvement of aircraft noise prediction. This document provides an assessment, conducted from 2006 to 2009, on the current state of the art for aircraft noise prediction by carefully analyzing the results from prediction tools and from the experimental databases to determine errors and uncertainties and compare results to validate the predictions. The error analysis is included for both the predictions and the experimental data and helps identify where improvements are required. This study is restricted to prediction methods and databases developed or sponsored by NASA, although in many cases they represent the current state of the art for industry. The present document begins with an introduction giving a general background for and a discussion on the process of this assessment followed by eight chapters covering topics at both the system and the component levels. The topic areas, each with multiple contributors, are aircraft system noise, engine system noise, airframe noise, fan noise, liner physics, duct acoustics, jet noise, and propulsion airframe aeroacoustics.

Dahl, Milo D.↗
NASA NTRSDate not supplied

NASA Glenn Engine Control Research Facilities

This document describes NASA Glenn facilities available for performing propulsion control work. This includes a real-time hardware in the loop facility for performing complex, multi-rate simulations. The second facility describes a small engine test stand with a modifiable controller for performing advanced control studies and/or testing engine system modifications.

Control Systems↗
NASA NTRS2006

State Analysis Database Tool

The State Analysis Database Tool software establishes a productive environment for collaboration among software and system engineers engaged in the development of complex interacting systems. The tool embodies State Analysis, a model-based system engineering methodology founded on a state-based control architecture (see figure). A state represents a momentary condition of an evolving system, and a model may describe how a state evolves and is affected by other states. The State Analysis methodology is a process for capturing system and software requirements in the form of explicit models and states, and defining goal-based operational plans consistent with the models. Requirements, models, and operational concerns have traditionally been documented in a variety of system engineering artifacts that address different aspects of a mission s lifecycle. In State Analysis, requirements, models, and operations information are State Analysis artifacts that are consistent and stored in a State Analysis Database. The tool includes a back-end database, a multi-platform front-end client, and Web-based administrative functions. The tool is structured to prompt an engineer to follow the State Analysis methodology, to encourage state discovery and model description, and to make software requirements and operations plans consistent with model descriptions.

Rasmussen, Robert↗
NASA NTRS2007

The Nation's Vision for Exploration: An Update

I.Current key activities: a) Constellation Level2-System Engineering. b) Lunar Architecture Team (LAT)2-technology assessment and architectural option for the lander. c) Mars Architecture Team-system engineering support, Science integration, precursor program planning. d) Lunar Lander Project Core Team-GN&C and Flight system engineering. e) Technology program-supporting multiple projects in robotics, power systems, aero entry technology. f) Mission Operation Project-Mission operations system engineering. g) Advanced Environmental Monitoring Instruments. H. Lunar Reconnaissance Orbiter instrument (Diviner). II. Mission Proposals a) Lunar Sample return. b) Lunar Gravity field mapper.

space exploration↗
NASA NTRS2017

The 2015-2016 SEPMAP Program at NASA JSC: Science, Engineering, and Program Management Training

The Systems Engineering Project Management Advancement Program (SEPMAP) at NASA Johnson Space Center (JSC) is an employee development program designed to provide graduate level training in project management and systems engineering. The program includes an applied learning project with engineering and integrated science goals requirements. The teams were presented with a task: Collect a representative sample set from a field site using a hexacopter platform, as if performing a scientific reconnaissance to assess whether the site is of sufficient scientific interest to justify exploration by astronauts. Four teams worked through the eighteen-month course to design customized sampling payloads integrated with the hexacopter, and then operate the aircraft to meet sampling requirements of number (≥ 5) and mass (≥ 5g each). The "Mars Yard" at JSC was utilized for this purpose. This project activity closely parallels NASA plans for the future exploration of Mars, where remote sites will be reconnoitered ahead of crewed exploration.

Graham, L.↗
NASA NTRS2005

Introduction to System Health Engineering and Management in Aerospace

This paper provides a technical overview of Integrated System Health Engineering and Management (ISHEM). We define ISHEM as "the paper provides a techniques, and technologies used to design, analyze, build, verify, and operate a system to prevent faults and/or minimize their effects." This includes design and manufacturing techniques as well operational and managerial methods. ISHEM is not a "purely technical issue" as it also involves and must account for organizational, communicative, and cognitive f&ms of humans as social beings and as individuals. Thus the paper will discuss in more detail why all of these elements, h m the technical to the cognitive and social, are necessary to build dependable human-machine systems. The paper outlines a functional homework and architecture for ISHEM operations, describes the processes needed to implement ISHEM in the system life-cycle, and provides a theoretical framework to understand the relationship between the different aspects of the discipline. It then derives from these and the social and cognitive bases a set of design and operational principles for ISHEM.

Johnson, Stephen B.↗
NASA NTRS1995

Computational Simulation Of A Nuclear Engine

Nuclear Engine System Simulation (NESS) computer program developed to satisfy need for accurate, stand-alone software tool for preliminary design analysis of nuclear thermal propulsion (NTP) engine system. Used for rapid, preliminary detailed design analysis of both reactor and key engine systems. Principal outputs include operating characteristics and weights of reactors, engine-system parameters as performances, weights, dimensions, pressures, temperatures, and mass flows, and operating characteristics of turbopumps under both design and off-design operating conditions. Written in FORTRAN 77.

Walton, J. T.↗
NASA NTRS2011

Lessons Learned from the Space Shuttle Engine Cutoff System (ECO) Anomalies

The Space Shuttle Orbiter's main engine cutoff (ECO) system first failed ground checkout in April, 2005 during a first tanking test prior to Return-to-Flight. Despite significant troubleshooting and investigative efforts that followed, the root cause could not be found and intermittent anomalies continued to plague the Program. By implementing hardware upgrades, enhancing monitoring capability, and relaxing the launch rules, the Shuttle fleet was allowed to continue flying in spite of these unexplained failures. Root cause was finally determined following the launch attempts of STS-122 in December, 2007 when the anomalies repeated, which allowed drag-on instrumentation to pinpoint the fault (the ET feedthrough connector). The suspect hardware was removed and provided additional evidence towards root cause determination. Corrective action was implemented and the system has performed successfully since then. This white paper presents the lessons learned from the entire experience, beginning with the anomalies since Return-to-Flight through discovery and correction of the problem. To put these lessons in better perspective for the reader, an overview of the ECO system is presented first. Next, a chronological account of the failures and associated investigation activities is discussed. Root cause and corrective action are summarized, followed by the lessons learned.

Martinez, Hugo E.↗
NASA NTRS2018

Spaceport Command and Control System: Network Engineering

The Spaceport Command and Control System (SCCS) project's goal is to facilitate the checkout and launch of NASA's next generation SLS vehicle in order to enable human exploration through deep space. SCCS is made up of complex software that will control and monitor the Space Launch System rocket and Orion spacecraft. Once it is fully developed, SCCS will be a large improvement to previous software since it takes advantage of modern computers and information making it faster and more reliable than the software used previously on the Shuttle program. The software will be tailored to the specific needs of the Space Launch System (SLS) and Orion spacecraft. These three projects will be brought together for the launch of Exploration Mission-1.

Mackh, Katherine↗
NASA NTRS2022

SWS TechTalk Systems Modelling for SWS Safety Demonstrator 1 (SD-1): Wildfire Response Operations

Build out a System Safety Model for System-Wide Safety’s first Technical Challenge 5 (TC5) Safety Demonstrator (SD-1), which will be a demonstration of an In-Time Aviation Safety Management System in emerging wildfire response operations. Supporting the Systems Engineer and using Model-Based Systems Engineering (MBSE) practices, languages, and tools. Summer 2022 SD1 milestones: TC5-03-01 Initial Stakeholder Engagement Concept of Operations Development milestone and the upcoming TC5-03-02 Identification of key gaps and prioritization of NASA, SWS milestone.

model-based systems engineering↗
NASA NTRS2019

Medical System Concept of Operations for Mars Exploration Mission-11: Exploration Medical Capability (ExMC) Element - Human Research Program

NASA’s exploration missions to Mars will have durations of 2-3 years and will take humans farther away from Earth than ever before. This will result in a paradigm shift for mission planning, spacecraft design, human systems integration, and in-flight medical care. Constraints on real-time communication, resupply, and medical evacuation are major architectural drivers. These constraints require medical system development to be tightly integrated with mission and vehicle design to provide crew autonomy and enable mission success. This concept of operations provides a common vision of medical care for developing a medical system for Mars exploration missions. It documents an overview of the stakeholder needs and goals of a medical system and provides examples of the types of activities the system will be used for during the mission. Development of the concept of operations considers mission variables such as distance from Earth, duration of mission, time to definitive medical care, communication protocols between crewmembers and ground support, personnel capabilities and skill sets, medical hardware and software, and medical data management. The information provided in this document informs the ExMC Systems Engineering effort to define the functions to be provided by the medical system. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions. This document is applicable to the ExMC Element Systems Engineering process and may be used for collaboration within the Human Research Program.

Urbina, Michelle↗
NASA NTRS1981

A-10/TF34 Turbine Engine Monitoring System (TEMS)

The hardware and software development of the A-10/TF34 turbine engine monitoring system (TEMS) is described. The operation and interfaces of the A-10/TF34 TEMS hardware are discussed with particular emphasis on function, capabilities, and limitations. The TEMS data types are defined and the various data acquisition modes are explained. Potential data products are also discussed.

Christopher, R. G.↗
NASA NTRS1989

SSME component assembly and life management expert system

The space shuttle utilizes several rocket engine systems, all of which must function with a high degree of reliability for successful mission completion. The space shuttle main engine (SSME) is by far the most complex of the rocket engine systems and is designed to be reusable. The reusability of spacecraft systems introduces many problems related to testing, reliability, and logistics. Components must be assembled from parts inventories in a manner which will most effectively utilize the available parts. Assembly must be scheduled to efficiently utilize available assembly benches while still maintaining flight schedules. Assembled components must be assigned to as many contiguous flights as possible, to minimize component changes. Each component must undergo a rigorous testing program prior to flight. In addition, testing and assembly of flight engines and components must be done in conjunction with the assembly and testing of developmental engines and components. The development, testing, manufacture, and flight assignments of the engine fleet involves the satisfaction of many logistical and operational requirements, subject to many constraints. The purpose of the SSME Component Assembly and Life Management Expert System (CALMES) is to assist the engine assembly and scheduling process, and to insure that these activities utilize available resources as efficiently as possible.

Ali, M.↗
NASA NTRS2011

Space Transportation System Liftoff Debris Mitigation Process Overview

Liftoff debris is a top risk to the Space Shuttle Vehicle. To manage the Liftoff debris risk, the Space Shuttle Program created a team with in the Propulsion Systems Engineering & Integration Office. The Shutt le Liftoff Debris Team harnesses the Systems Engineering process to i dentify, assess, mitigate, and communicate the Liftoff debris risk. T he Liftoff Debris Team leverages off the technical knowledge and expe rtise of engineering groups across multiple NASA centers to integrate total system solutions. These solutions connect the hardware and ana lyses to identify and characterize debris sources and zones contribut ing to the Liftoff debris risk. The solutions incorporate analyses sp anning: the definition and modeling of natural and induced environmen ts; material characterizations; statistical trending analyses, imager y based trajectory analyses; debris transport analyses, and risk asse ssments. The verification and validation of these analyses are bound by conservative assumptions and anchored by testing and flight data. The Liftoff debris risk mitigation is managed through vigilant collab orative work between the Liftoff Debris Team and Launch Pad Operation s personnel and through the management of requirements, interfaces, r isk documentation, configurations, and technical data. Furthermore, o n day of launch, decision analysis is used to apply the wealth of ana lyses to case specific identified risks. This presentation describes how the Liftoff Debris Team applies Systems Engineering in their proce sses to mitigate risk and improve the safety of the Space Shuttle Veh icle.

Mitchell, Michael↗
NASA NTRS1982

Flight evaluation of a digital electronic engine control system in an F-15 airplane

Benefits provided by a full-authority digital engine control are related to improvements in engine efficiency, performance, and operations. An additional benefit is the capability of detecting and accommodating failures in real time and providing engine-health diagnostics. The digital electronic engine control (DEEC), is a full-authority digital engine control developed for the F100-PW-100 turbofan engine. The DEEC has been flight tested on an F-15 aircraft. The flight tests had the objective to evaluate the DEEC hardware and software over the F-15 flight envelope. A description is presented of the results of the flight tests, which consisted of nonaugmented and augmented throttle transients, airstarts, and backup control operations. The aircraft, engine, DEEC system, and data acquisition and reduction system are discussed.

Myers, L. P.↗
NASA NTRS1992

SSME Automated Engine Calibration System (AECS)

An algorithm is derived for the real-time calibration of the engine fuel flowmeter and the engine mixture ratio during Space Shuttle Main Engine (SSME) ground testing. Because currently used calibration methods are post-test operations, there exists no fail-safe way of predicting at what mixture ratio a planned test will run. It is proposed that the algorithm developed here be used as part of an Automated Engine Calibration System (AECS) which could ensure that nearly all SSME tests are run at the proper mixture ratio. In this way, AECS has the potential of increasing the efficiency of the SSME ground test program. In addition to the derivation of the algorithm, an overview of this calibration system is presented along with the list of test stand facility instrumentation necessary for AECS implementation.

Greene, William D.↗
NASA NTRS2016

Towards a Reference Architecture for Model-Based Engineering Environments

A key aspect of adopting model-based systems engineering as a practice in an organization is the design and development, and adoption of corresponding processes and tools that support the model-based paradigm. In an effort to enable the unified implementation of such processes and tools, this paper introduces a reference architecture model that serves as a specification for a model-based engineering environment. Current systems engineering practices, products, processes and technologies are used as input for continuously refining the architecture model. In the paper, we introduce and report on the current status of this reference architecture model, and present the methodology applied in developing the reference architecture. We conclude that while there are a very large number of domain- or application-specific processes requiring specialized behavior, these can be reduced through abstraction to a small set of core functions that need to be supported by a realization of a model-based engineering environment. Only very few organization-domain- or application-specific aspects require specialized consideration.

Herzig, Sebastian J. I.↗