The Evolution of Team-X: 25 Years of Concurrent Engineering Design Experience
No abstract provided
SEARCH · Search NASA
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.
No abstract provided
Explore the source record for details and available documents.
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.
The pursuit of high Mach number flight presents several challenges to the airframe and engine design engineers. Most obvious is the resulting high temperatures encountered as the aircraft approaches Mach 3 and above. The encountered high temperatures and shaft speeds of engines require rethinking in the areas of material selections, component design and component operating life. In the area of sump compartment sealing, one of the most difficult sealing applications is the sealing of an engine s rear sump. Normally this sump will need some method of sealing between two rotating shafts. This sealing operation is done with an intershaft seal. The aft sump region also presents an additional design requirement for the intershaft seal. This region has to absorb the engine s thermal growth, which means that in the seal area, axial movement, on the order of 0.30 in., between the rotating shafts must be tolerated. A new concept or new technology of sealing an intershaft sump configuration is being developed. This concept, called a rotating intershaft brush seal has key attributes that will allow this seal to perform better, in the demanding environment of sealing an aft sump with two rotating shafts, when compared to today s sealing technology of labyrinth and carbon sea
This system engineering toolbox is designed to provide tools and methodologies to the design-oriented systems engineer. A tool is defined as a set of procedures to accomplish a specific function. A methodology is defined as a collection of tools, rules, and postulates to accomplish a purpose. For each concept addressed in the toolbox, the following information is provided: (1) description, (2) application, (3) procedures, (4) examples, if practical, (5) advantages, (6) limitations, and (7) bibliography and/or references. The scope of the document includes concept development tools, system safety and reliability tools, design-related analytical tools, graphical data interpretation tools, a brief description of common statistical tools and methodologies, so-called total quality management tools, and trend analysis tools. Both relationship to project phase and primary functional usage of the tools are also delineated. The toolbox also includes a case study for illustrative purposes. Fifty-five tools are delineated in the text.
Virtual Engineering (VE) is a Python software framework designed to accelerate the research and development of engineering processes that are fundamentally defined by multiple unit operations executed in series. VE supports a wide variety of different multi-physics models and integrates them to simulate a complete end-to-end process. To automate the execution of this model sequence, VE provides (i) a robust method to communicate between models, (ii) a high-level, user-friendly interface to set model parameters and enable optimization, and (iii) an overall model-agnostic approach that allows new computational units to be swapped in and out of workflows. Although the VE framework was developed to support the biochemical conversion of biomass to fuel, we have designed each component to easily accommodate new domains and unit models.
The Environment for Application Software Integration and Execution (EASIE) provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational database management system. Volume 1, Executive Overview, gives an overview of the functions provided by EASIE and describes their use. Three operational design systems based upon the EASIE software are briefly described.
The aim is to coordinate the topics of design, engineering dynamics, and fluid dynamics in order to aid researchers in the area of fluid film lubrication. The lubrication principles that are covered can serve as a basis for the engineering design of machine elements. The fundamentals of fluid film lubrication are presented clearly so that students that use the book will have confidence in their ability to apply these principles to a wide range of lubrication situations. Some guidance on applying these fundamentals to the solution of engineering problems is also provided.
The Environment for Application Software Integration and Execution, EASIE, provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating the results of many stand-alone engineering analysis programs. EASIE provides access to these programs via a quick, uniform, user-friendly interface. In addition, EASIE provides utilities which aid in the execution of the following tasks: selection of application programs, modification and review of program data, automatic definition and coordination of data files during program execution and a logging of steps executed throughout a design study. Volume 3, the Program Execution Guide, describes the executive capabilities provided by EASIE and defines the command language and menus available under Version 1.0. EASIE provides users with two basic modes of operation. One is the Application-Derived Executive (ADE) which provides users with sufficient guidance to quickly review data, select menu action items, and execute application programs. The second is the Complete Control Executive (CCE), which provides a full executive interface allowing users in-depth control of the design process.
The Environment for Application Software Integration and Execution, EASIE, provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational data base management system. In volume 2, the use of a SYSTEM LIBRARY PROCESSOR is used to construct a DATA DICTIONARY describing all relations defined in the data base, and a TEMPLATE LIBRARY. A TEMPLATE is a description of all subsets of relations (including conditional selection criteria and sorting specifications) to be accessed as input or output for a given application. Together, these form the SYSTEM LIBRARY which is used to automatically produce the data base schema, FORTRAN subroutines to retrieve/store data from/to the data base, and instructions to a generic REVIEWER program providing review/modification of data for a given template. Automation of these functions eliminates much of the tedious, error prone work required by the usual approach to data base integration.
How much redundancy should be built into a subsystem such as a space power subsystem. How does a reliability or design engineer choose between a power subsystem with 0.990 reliability and a more costly subsystem with 0.995 reliability. How does the engineer designing a power subsystem for a satellite decide between one power subsystem and a more reliable but heavier power subsystem. High reliability is not necessarily an end in itself. High reliability may be desirable in order to reduce the statistically expected loss due to a subsystem failure. However, this may not be the wisest use of funds since the expected loss due to subsystem failure is not the only cost involved. The subsystem itself may be very costly. The cost of the subsystem or the expected loss due to subsystem failure may not be considered separately. Therefore, the total of the two costs is minimized, i.e., the total of the cost of the subsystem plus the expected loss due to subsystem failure. A specific type of redundant system is considered, called a k-out-of-n: G subsystem. Such a subsystem has n modules, of which k are required to be good for the subsystem to be good. Five models are discussed which can be applied in the design of a power subsystem to select the unique redundancy method which will minimize the total of the cost of the power subsystem plus the expected loss due to the power subsystem failure. A BASIC computer program is available.
Advanced forms of electronic and computerized control systems are being developed to optimize traffic flow in and between cities. Modern technology permits communication of real-time information via signs and auditory messages and allows motorists to plan ahead for safer and more efficient travel. This paper describes an on-going research program for defining drivers' information needs and behavior in response to various message types and modes of presentation. Human engineer design criteria for real-time displays will be investigated in the laboratory and in research vehicles with field testing in actual city corridors. The results will be incorporated into a design handbook for use by sign design engineers.
With the increasing use of advanced ceramic materials in high-temperature structural applications such as advanced heat engine components, the need arises to accurately predict thermomechanical behavior that is inherently time-dependent and that is hereditary in the sense that the current behavior depends not only on current conditions but also on the material's thermomechanical history. Most current analytical life prediction methods for both subcritical crack growth and creep models use elastic stress fields to predict the time-dependent reliability response of components subjected to elevated service temperatures. Inelastic response at high temperatures has been well documented in the materials science literature for these material systems, but this issue has been ignored by the engineering design community. From a design engineer's perspective, it is imperative to emphasize that accurate predictions of time-dependent reliability demand accurate stress field information. Ceramic materials exhibit different time-dependent behavior in tension and compression. Thus, inelastic deformation models for ceramics must be constructed in a fashion that admits both sensitivity to hydrostatic stress and differing behavior in tension and compression. A number of constitutive theories for materials that exhibit sensitivity to the hydrostatic component of stress have been proposed that characterize deformation using time-independent classical plasticity as a foundation. However, none of these theories allow different behavior in tension and compression. In addition, these theories are somewhat lacking in that they are unable to capture the creep, relaxation, and rate-sensitive phenomena exhibited by ceramic materials at high temperatures. The objective of this effort at the NASA Lewis Research Center has been to formulate a macroscopic continuum theory that captures these time-dependent phenomena. Specifically, the effort has focused on inelastic deformation behavior associated with these service conditions by developing a multiaxial viscoplastic constitutive model that accounts for time-dependent hereditary material deformation (such as creep and stress relaxation) in monolithic structural ceramics. Using continuum principles of engineering mechanics, we derived the complete viscoplastic theory from a scalar dissipative potential function.
The National Aeronautics and Space Administration (NASA) is developing new capabilities for human and scientific exploration beyond Earth orbit. Natural environments information is an important asset for NASA's development of the next generation space transportation system as part of the Exploration Systems Development (ESD) Programs, which includes the Space Launch System (SLS) and Multi-Purpose Crew Vehicle (MPCV) Programs. Natural terrestrial environment conditions - such as wind, lightning and sea states - can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing to landing and recovery operations, including all potential abort scenarios. Space vehicles are particularly sensitive to these environments during the launch/ascent and the entry/landing phases of mission operations. The Marshall Space Flight Center (MSFC) Natural Environments Branch provides engineering design support for NASA space vehicle projects and programs by providing design engineers and mission planners with natural environments definitions as well as performing custom analyses to help characterize the impacts the natural environment may have on vehicle performance. One such analysis involves assessing the impact of natural environments to operational availability. Climatological time series of operational surface weather observations are used to calculate probabilities of meeting/exceeding various sets of hypothetical vehicle-specific parametric constraint thresholds. Outputs are tabulated by month and hour of day to show both seasonal and diurnal variation. This paper will discuss how climate analyses are performed by the MSFC Natural Environments Branch to support the ESD Launch Availability (LA) Technical Performance Measure (TPM), the SLS Launch Availability due to Natural Environments TPM, and several MPCV (Orion) launch and landing availability analyses - including the 2014 Orion Exploration Flight Test 1 (EFT-1) mission.
NASA is developing new capabilities for human and scientific exploration beyond Earth orbit. Natural environments information is an important asset for NASA's development of the next generation space transportation system as part of the Exploration Systems Development Program, which includes the Space Launch System (SLS) and MultiPurpose Crew Vehicle (MPCV) Programs. Natural terrestrial environment conditions - such as wind, lightning and sea states - can affect vehicle safety and performance during multiple mission phases ranging from prelaunch ground processing to landing and recovery operations, including all potential abort scenarios. Space vehicles are particularly sensitive to these environments during the launch/ascent and the entry/landing phases of mission operations. The Marshall Space Flight Center (MSFC) Natural Environments Branch provides engineering design support for NASA space vehicle projects and programs by providing design engineers and mission planners with natural environments definitions as well as performing custom analyses to help characterize the impacts the natural environment may have on vehicle performance. One such analysis involves assessing the impact of natural environments to operational availability. Climatological time series of operational surface weather observations are used to calculate probabilities of meeting or exceeding various sets of hypothetical vehicle-specific parametric constraint thresholds.
For transporting Large Space Structures (LSS) from Low Earth Orbit (LEO) to Geosynchronous Equatorial Orbit (GEO), a variety of low thrust engine cycles have been evaluated for oxygen/hydrogen and oxygen/hydrocarbon propellants. The engine cycles included conventional propellant turbine drives (gas generator, expander, and staged-combustion cycles), turboalternator/electric motor pump drive, and fuel-cell/electric motor pump drive, as well as pressure-fed engines. The thrust chamber cooling limits and the engine cycle limits were established for a range of thrust levels. The candidate engine cycles were analyzed, screened, rated, and two engine cycle/configurations were selected for preliminary engine design. Preliminary engine designs for these two engines were formulated and engine design layouts prepared and parametric engine data generated.
Low pressure ratio fan engines are receiving increasing attention as a means to provide low speed lift for civilian VTOL transports. Two general types of fan lift engines that are being studied are integral fans and remote power fans. Preliminary engine design studies of both types of lift fan systems have been made. The paper summarizes a portion of the results of the engine design studies, including the crucial engine requirements, and some of the characteristics of the emerging engine designs of each type.
The perceptions of engineers and scientists at NASA Langley Research Center toward engineering design teams were evaluated. A sample of 49 engineers and scientists rated 60 team behaviors in terms of their relative importance for team success. They also completed a profile of their own perceptions of their strengths and weaknesses as team members. Behaviors related to team success are discussed in terms of those involving the organizational culture and commitment to the team and those dealing with internal team dynamics. The latter behaviors focused on team issues occurring during the early stages of a team's existence. They included the level and extent of debate and discussion regarding methods for completing the team task and the efficient use of team time to explore and discuss methodologies critical to the problem. The discussion includes a comparison of engineering teams with the prototypical business team portrayed in the literature.