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 487 records · Page 27
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Developing the Next Generation of Science Data System Engineers

At Goddard, engineers and scientists with a range of experience in science data systems are needed to employ new technologies and develop advances in capabilities for supporting new Earth and Space science research. Engineers with extensive experience in science data, software engineering and computer-information architectures are needed to lead and perform these activities. The increasing types and complexity of instrument data and emerging computer technologies coupled with the current shortage of computer engineers with backgrounds in science has led the need to develop a career path for science data systems engineers and architects.The current career path, in which undergraduate students studying various disciplines such as Computer Engineering or Physical Scientist, generally begins with serving on a development team in any of the disciplines where they can work in depth on existing Goddard data systems or serve with a specific NASA science team. There they begin to understand the data, infuse technologies, and begin to know the architectures of science data systems. From here the typical career involves peermentoring, on-the-job training or graduate level studies in analytics, computational science and applied science and mathematics. At the most senior level, engineers become subject matter experts and system architect experts, leading discipline-specific data centers and large software development projects. They are recognized as a subject matter expert in a science domain, they have project management expertise, lead standards efforts and lead international projects. A long career development remains necessary not only because of the breadth of knowledge required across physical sciences and engineering disciplines, but also because of the diversity of instrument data being developed today both by NASA and international partner agencies and because multidiscipline science and practitioner communities expect to have access to all types of observational data.This paper describes an approach to defining career-path guidance for college-bound high school and undergraduate engineering students, junior and senior engineers from various disciplines.

Next Generation of Science↗
NASA NTRSDate not supplied

Impact of Emerging Computing Architectures and Opportunities for Process Systems Engineering Applications

Moore’s “law” was the observation that the number of transistors in an integrated circuit doubled approximately every two years. This trend has distinctly failed to hold in recent years. The death of Moore’s law has left researchers and practitioners in the computational sciences searching for technologies to provide the speedups formerly supported by Moore’s law. Previously overlooked chip architectures and other computing technologies are now receiving more development resources. Critically, these technologies are gaining more mature software support, opening their adoption by researchers in algorithms and applications. In this article, we review some of these computing technologies, their relationship with various algorithms and applications, and their potential benefits (or pitfalls). We close with recommendations for future work by the process systems engineering community specifically.

Emerging hardware↗
NASA NTRS2019

Method for Tracking and Communicating Aggregate Risk Through the Use of Model-Based Systems Engineering (MBSE) Tools

Large, complex projects can identify a significant number and variety of risks, throughout the project life cycle. These risks are analyzed, mitigated, closed or accepted as independent uncertainties. Once closed or accepted, it is easy for projects to lose awareness of their impact. In reality, each of these risks contributes some amount to the overall risk posture of the project. The ability to track and effectively communicate this aggregate risk has represented a challenge to project management. There have been previous attempts to create a schema to communicate the aggregate effect of risks, without notable success. Most of these attempts have centered on some additive metric derived from the scoring of likelihood and consequence values. This, in and of itself, is a logical approach, but all too often the scores were then aggregated to a level where all context was lost. One weakness has been a lack of attempt to create linkages or logical groups of the risks upon which useful aggregation could then occur. The overall move to model-based (systems) engineering (MBSE) has opened up a vast frontier of opportunities to better integrate all project data. MBSE provides an underlying layer that links data items to each other. Objectives link to requirements, which then link to functions, functions to physical architecture items, and so on, as far down as projects want to model. While it started with a focus on modeling requirements based on things like use cases, efforts are now underway to integrate safety and mission assurance (S&MA) information and analyses, such as risks. This effort, called Model Based Mission Assurance (MBMA), is yielding models that are more useful and are a more accurate representations of the systems. MBSE models, with this ability to link related items, provide a new means of tracking and communicating aggregate risks. In the proposed method, risks are added into the models as distinct items, having attributes that communicate a scoring derived from the likelihood and consequence values as charted on the standard NASA 5x5 risk matrix. Like earlier efforts, each box in the 5x5 has an associated scoring, which may include both a current score and potential post-mitigation/control score. The risk items are then linked to elements of the model, such as system objectives/goals, requirements, functions, or physical architecture items, with "Risk to" relationships. These risks will then be communicated by use of reports generated from the model, detailing all risks and/or hazards linked to model elements. These reports can include aggregate impacts, including a current scoring and potential future state scoring based on the planned mitigations and/or controls. These reports will show all risks, open, accepted, and closed, linked to project objectives or requirements. When run as part of an upcoming risk acceptance discussion, these reports will serve to remind the team of all previous risks that relate to the effected portion of the system. When included as part of periodic program or project reviews, risk reviews, and safety reviews, this method can improve the overall understanding of the system's true risk posture. This proposed method takes full advantage of the advances that modern modeling techniques provide, with a minimal investment of additional time. Utilizing the model environment also enables a near constant access to current state of aggregate risks.

model based mission assurance↗
NASA NTRS2016

A Model Based Systems Engineering Approach Towards Developing a Rapid Analysis and Trades Environment

In this work, an integrated and end-to-end modeling environment was developed to assess the system-level impacts of evolving requirements and design parameters. Researchers at the Georgia Institute of Technology's Aerospace Systems Design Laboratory (ASDL) collaborated with JPL engineers to develop, implement, and test a modeling environment to assess design changes to a notional Europa Mission called the Jupiter Europa Buzzer (JEB). This environment was developed using a Model-Based Systems Engineering (MBSE) approach and consists of three major components: the Systems Model, the Mission Simulator, and the Web Based Interactive Dashboard. In summary, utilizing this environment in a representative notional end-to-end scenario, performance margins were calculated in hours while maintaining consistent analytical, hardware, and operational assumptions.

Model Based System Engineering↗
NASA NTRS2022

Should’ve Could’ve: Progress in the Systems Engineering of the Mars2020 On-Board Planner

Mars rover operations has traditionally controlled behavior using meticulously compiled, so-called “Master” sequences that enforce deterministic timing and ordering of activities. While the approach is effective at managing risk and complexity, it can also be inefficient. Extended operations of the Mars2020 rover envisions a fundamentally different scheduling and execution approach. Atomic activities are constrained by mission operators in time, resource usage, and a structure of dependencies. The rover flight software will create and re-create schedules, responding to available energy, data volume, actual activity durations and execution status, observed temperatures, and other on-board state. Schedules are expected to change substantially in the course of execution. The solution space is prohibitively large and probabilistic in nature. A range of emergent behavior is accessible depending on the interaction between actual on-board state and a given formulation of constraints. For years, the specification and implementation of this capability have been considered and refined, as testing and analysis have mapped the contours of the system. Many concepts that could have been adopted were rejected, and in some cases, emergent properties have been exposed and beaten back with approaches to steer the behavior. This paper discusses some of the design history and underlying reasoning in the systems engineering of the first autonomous activity planner on Mars.

Kuhn, Stephen R↗
NASA NTRS1993

Fluid design studies of integrated modular engine system

A study was performed to develop a fluid system design and show the feasibility of constructing an integrated modular engine (IME) configuration, using an expander cycle engine. The primary design goal of the IME configuration was to improve the propulsion system reliability. The IME fluid system was designed as a single fault tolerant system, while minimizing the required fluid components. This study addresses the design of the high pressure manifolds, turbopumps and thrust chambers for the IME configuration. A physical layout drawing was made, which located each of the fluid system components, manifolds and thrust chambers. Finally, a comparison was made between the fluid system designs of an IME system and a non-network (clustered) engine system.

Frankenfield, Bruce↗
NASA NTRS2012

2012 Alabama Lunabotics Systems Engineering Paper

Excavation will hold a key role for future lunar missions. NASA has stated that "advances in lunar regolith mining have the potential to significantly contribute to our nation's space vision and NASA space exploration operations." [1]. The Lunabotics Mining Competition is an event hosted by NASA that is meant to encourage "the development of innovative lunar excavation concepts from universities which may result in clever ideas and solutions which could be applied to an actual lunar excavation device or payload." [2]. Teams entering the competition must "design and build a remote controlled or autonomous excavator, called a lunabot, that can collect and deposit a minimum of 10 kilograms of lunar simulant within 10 minutes." [2]. While excavation will play an important part in lunar missions, there will still be many other tasks that would benefit from robotic assistance. An excavator might not be as well suited for these tasks as other types of robots might be. For example a lightweight rover would do well with reconnaissance, and a mobile gripper arm would be fit for manipulation, while an excavator would be comparatively clumsy and slow in both cases. Even within the realm of excavation it would be beneficial to have different types of excavators for different tasks, as there are on Earth. The Alabama Lunabotics Team at the University of Alabama has made it their goal to not only design and build a robot that could compete in the Lunabotics Mining Competition, but would also be a multipurpose tool for future NASA missions. The 2010-2011 resulting robot was named the Modular Omnidirectional Lunar Excavator (MOLE). Using the Systems Engineering process and building off of two years of Lunabotics experience, the 20ll-2012 Alabama Lunabotics team (Team NASACAR) has improved the MOLE 1.0 design and optimized it for the 2012 Lunabotics Competition rules [I]. A CAD model of MOLE 2.0 can be seen below in Fig. 1.

Baker, Justin↗
NASA NTRS2005

Intelligent Engine Systems Work Element 1.3: Sub System Health Management

The objectives of this program were to develop health monitoring systems and physics-based fault detection models for engine sub-systems including the start, lubrication, and fuel. These models will ultimately be used to provide more effective sub-system fault identification and isolation to reduce engine maintenance costs and engine down-time. Additionally, the bearing sub-system health is addressed in this program through identification of sensing requirements, a review of available technologies and a demonstration of a demonstration of a conceptual monitoring system for a differential roller bearing. This report is divided into four sections; one for each of the subtasks. The start system subtask is documented in section 2.0, the oil system is covered in section 3.0, bearing in section 4.0, and the fuel system is presented in section 5.0.

Ashby, Malcolm↗
NASA NTRSDate not supplied

Space Launch System Engine Out Capabilities

NASA's Space Launch System (SLS) is being developed with the primary purpose of returning people to the Moon and eventually landing people on Mars. With these lofty goals, ensuring mission completion is paramount even in the event of an in-flight mishap. One possible mishap is the loss of an engine in flight. While SLS was not required to show full engine out capability, the program took an ``assess to'' approach to see when the launch vehicle could complete the mission after an engine failure versus when the launch vehicle targets required a down-mode to an alternate mission target to ensure at least some flight objectives were complete, or at a minimum ensure safe return of Orion and the Crew. While this paper will focus on Artemis I, an uncrewed mission, some comparisons will be made to how the engine out capability will change for the subsequent Crewed flights of SLS and Orion.

Engine Out↗
NASA NTRS1975

Engine systems technology

Current full-scale engine development programs are discussed, and efforts to improve the available technology base are presented. The Lewis full-scale engine test facilities are described. Several typical engine programs and plans for research in aeromechanical instability or flutter are summarized. An overview of Lewis studies of flow distortion and its effects on engine stability is presented. The origins and nature of the distortion problem are summarized, and some of the results and methods for both steady and time-varying distortions are discussed.

Willoh, R.↗
NASA NTRS2007

Calculation of Dynamic Loads Due to Random Vibration Environments in Rocket Engine Systems

An important part of rocket engine design is the calculation of random dynamic loads resulting from internal engine "self-induced" sources. These loads are random in nature and can greatly influence the weight of many engine components. Several methodologies for calculating random loads are discussed and then compared to test results using a dynamic testbed consisting of a 60K thrust engine. The engine was tested in a free-free condition with known random force inputs from shakers attached to three locations near the main noise sources on the engine. Accelerations and strains were measured at several critical locations on the engines and then compared to the analytical results using two different random response methodologies.

Christensen, Eric R.↗
NASA NTRS1999

Non-Toxic Orbital Maneuvering System Engine Development

Recent results using the Aestus engine operated with LOx/ethanol propellant are presented. An experimental program at Rocketdyne Propulsion and Power is underway to adapt this engine for the Boeing Reusable Space Systems Division non-toxic Orbital Maneuvering System/Reaction control System (OMS/RCS) system. Daimler-Chrysler Aerospace designed the Aestus as an nitrogen tetroxide/monomethyl hydrazine (NTO/MMH) upper-stage engine for the Ariane 5. The non-toxic OMS/RCS system's preliminary design requires a LOx/ethanol (O2/C2H5OH) engine that operates with a mixture ratio of 1.8, a specific impulse of 323 seconds, and fits within the original OMS design envelope. This paper describes current efforts to meet these requirements including, investigating engine performance using LOx/ethanol, developing the en-ine system sizing package, and meeting the vehicle operation parameters. Data from hot-fire testing are also presented and discussed.

Green, Christopher↗
NASA NTRS2015

Systems Engineering, Quality and Testing

AS9100 has little to say about how to apply a Quality Management System (QMS) to aerospace test programs. There is little in the quality engineering Body of Knowledge that applies to testing, unless it is nondestructive examination or some type of lab or bench testing. If one examines how the systems engineering processes are implemented throughout a test program; and how these processes can be mapped to AS9100, a number of areas for involvement of the quality professional are revealed.

Shepherd, Christena C.↗
NASA NTRS1976

Space shuttle engineering and operations support. Orbiter to spacelab electrical power interface. Avionics system engineering

The results are presented of an investigation of the factors which affect the determination of Spacelab (S/L) minimum interface main dc voltage and available power from the orbiter. The dedicated fuel cell mode of powering the S/L is examined along with the minimum S/L interface voltage and available power using the predicted fuel cell power plant performance curves. The values obtained are slightly lower than current estimates and represent a more marginal operating condition than previously estimated.

Emmons, T. E.↗