Search NASA⌕ Search

SEARCH · Search NASA

Results for “concurrent engineering design”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Lunar Surface Relay - Mobile: Concept to Provide Relay Links to Surface Assets

At the request of NASA’s Space Communication and Navigation (SCaN) program, the Glenn Research Center’s (GRC) Compass concurrent engineering team developed a conceptual design of a Lunar Surface Relay- Mobile (LSR-M) system to provide a variety of surface and relay communication links in support of future Artemis sorties. The team determined that a mobile asset, with its ability to relocate to support a variety of surface sites and leverage more hospitable winter locations on the lunar south pole, would be of particular use in the architecture. Following the design of a solar array and battery powered baseline case, a quick look design further investigated adding a multi-mission radioisotope thermoelectric generator (MMRTG) to the system to reduce battery requirements to survive the lunar night and remove the need to relocate to favorable night locations during the lunar winter.

Lunar Surface Relay↗
NASA NTRS1999

Rotor Re-Design for the SSME Fuel Flowmeter

The present report describes the process of redesigning a new rotor for the SSME Fuel Flowmeter. The new design addresses the specific requirement of a lower rotor speed which would allow the SSME operation at 1 15% rated power level without reaching a blade excitation by the wakes behind the hexagonal flow straightener upstream at frequencies close to the blade natural frequency. A series of calculations combining fleet flowmeters test data, airfoil fluid dynamics and CFD simulations of flow patterns behind the flowmeter's hexagonal straightener has led to a blade twist design alpha = alpha (radius) targeting a kf constant of 0.8256. The kf constant relates the fuel volume flow to the flowmeter rotor speed, for this particular value 17685 GPM at 3650 RPM. Based on this angle distribution, two actual blade designs were developed. A first design using the same blade airfoil as the original design targeted the new kf value only. A second design using a variable blade chord length and airfoil relative thickness targeted simultaneously the new kf value and an optimum blade design destined to provide smooth and stable operation and a significant increase in the blade natural frequency associated with the first bending mode, such that a comfortable margin could be obtained at 115% RPL. The second design is a result of a concurrent engineering process, during which several iterations were made in order to achieve a targeted blade natural frequency associated with the first bending mode of 1300 Hz. Water flow tests preliminary results indicate a kf value of 0.8179 for the f-irst design, which is within 1% of the target value. The second design rotor shows a natural frequency associated with the first bending mode of 1308 Hz, and a water-flow calibration constant of kf 0.8169.

Marcu, Bogdan↗
NASA NTRS1990

SE and I system testability: The key to space system FDIR and verification testing

The key to implementing self-diagnosing design is a systems engineering task focused on design for testability concurrent with design for functionality. The design for testability process described here is the product of several years of DOD study and experience. Its application to the space station has begun on Work Package II under NASA and McDonnell direction. Other work package teams are being briefed by Harris Corporation with the hope of convincing them to embrace the process. For the purpose of this discussion the term testability is used to describe the systems engineering process by which designers can assure themselves and their reviewers that their designs are TESTABLE, that is they will support the downstream process of determining their functionality. Due to the complexity and density of present-day state-of-the-art designs, such as pipeline processors and high-speed integrated circuit technology, testability feature design is a critical requirement of the functional design process. A systematic approach to Space systems test and checkout as well as fault detection fault isolation reconfiguration (FDFIR) will minimize operational costs and maximize operational efficiency. An effective design for the testability program must be implemented by all contractors to insure meeting this objective. The process is well understood and technology is here to support it.

Barry, Thomas↗
NASA NTRS1992

Control-structure-thermal interactions in analysis of lunar telescopes

The lunar telescope project was an excellent model for the CSTI study because a telescope is a very sensitive instrument, and thermal expansion or mechanical vibration of the mirror assemblies will rapidly degrade the resolution of the device. Consequently, the interactions are strongly coupled. The lunar surface experiences very large temperature variations that range from approximately -180 C to over 100 C. Although the optical assemblies of the telescopes will be well insulated, the temperature of the mirrors will inevitably fluctuate in a similar cycle, but of much smaller magnitude. In order to obtain images of high quality and clarity, allowable thermal deformations of any point on a mirror must be less than 1 micron. Initial estimates indicate that this corresponds to a temperature variation of much less than 1 deg through the thickness of the mirror. Therefore, a lunar telescope design will most probably include active thermal control, a means of controlling the shape of the mirrors, or a combination of both systems. Historically, the design of a complex vehicle was primarily a sequential process in which the basic structure was defined without concurrent detailed analyses or other subsystems. The basic configuration was then passed to the different teams responsible for each subsystem, and their task was to produce a workable solution without requiring major alterations to any principal components or subsystems. Consequently, the final design of the vehicle was not always the most efficient, owing to the fact that each subsystem design was partially constrained by the previous work. This procedure was necessary at the time because the analysis process was extremely time-consuming and had to be started over with each significant alteration of the vehicle. With recent advances in the power and capacity of small computers, and the parallel development of powerful software in structural, thermal, and control system analysis, it is now possible to produce very detailed analyses of intermediate designs in a much shorter period of time. The subsystems can thus be designed concurrently, and alterations in the overall design can be quickly adopted into each analysis; the design becomes an iterative process in which it is much easier to experiment with new ideas, configurations, and components. Concurrent engineering has the potential to produce efficient, highly capable designs because the effect of one subystem on another can be assessed in much more detail at a very early point in the program. The research program consisted of several tasks: scale a prototype telescope assembly to a 1 m aperture, develop a model of the telescope assembly by using finite element (FEM) codes that are available on site, determine structural deflections of the mirror surfaces due to the temperature variations, develop a prototype control system to maintain the proper shape of the optical elements, and most important of all, demonstrate the concurrent engineering approach with this example. In addition, the software used for the finite element models and thermal analysis was relatively new within the Program Development Office and had yet to be applied to systems this large or complex; understanding the software and modifying it for use with this project was also required. The I-DEAS software by Structural Dynamics Research Corporation (SDRC) was used to build the finite element models, and TMG developed by Maya Heat Transfer Technologies, Ltd. (which runs as an I-DEAS module) was used for the thermal model calculations. All control system development was accomplished with MATRIX(sub X) by Integrated Systems, Inc.

Thompson, Roger C.↗
NASA NTRS1994

STEP: A Futurevision, Today

STEP (STandard for the Exchange of Product Model Data) is an innovative software tool that allows the exchange of data between different programming systems to occur and helps speed up the designing in various process industries. This exchange occurs easily between those companies that have STEP, and many industries and government agencies are requiring that their vendors utilize STEP in their computer aided design projects, such as in the areas of mechanical, aeronautical, and electrical engineering. STEP allows the process of concurrent engineering to occur and increases the quality of the design product. One example of the STEP program is the Boeing 777, the first paperless airplane.

Source record↗
DOE OSTI2026

Engineering Thermally Resilient and Kinetically Active Reversible Protonic Ceramic Cells via Interfacial Design

Achieving concurrent fast electrode kinetics and long-term thermo-mechanical durability remains a critical challenge for reversible protonic ceramic electrochemical cells (R-PCECs). Herein, we report an interfacial engineering strategy that integrates a perovs.kite-type PrBaRu0.1Co1.9O5+δ (PBRC) nanoparticle layer onto a PrBa0.5Sr0.5Co1.5Fe0.5O5+δ (PBSCF) substrate (PBRC-PBSCF), together with a modified pellet-assisted sintering approach to fabricate dense BaZr0.4Ce0.4Y0.1Yb0.1O3-δ (BZCYYb4411) electrolytes. The in situ reconstructed heterointerface enhances oxygen reduction/evolution reaction (ORR/OER) kinetics, promotes H2O adsorption/dissociation, and improves steam tolerance, as verified by electrochemical measurements and interfacial microstructural analyses. Density functional theory reveals that Ru-induced electronic modulation at the PBRC-PBSCF interface lowers the energy of oxygen vacancy formation and optimizes the position of the O 2p band center, thereby accelerating oxygen redox kinetics and stabilizing the interface. The resulting R-PCECs deliver an excellent peak power density of 1.112 W cm−2 and an electrolysis current density of −1.257 A cm−2 at 1.3 V in 3% H2O wet air at 600°C, with a reasonable faradaic efficiency. Furthermore, the cells demonstrate excellent stability, sustaining 100 h of thermal cycling (400–600°C, 200°C h−1) in both fuel cell and electrolysis modes, with 600 h of stability in electrolysis mode (600°C, −0.5 to −2 A cm−2).

30 DIRECT ENERGY CONVERSION↗
NASA NTRS1999

True Concurrent Thermal Engineering Integrating CAD Model Building with Finite Element and Finite Difference Methods

Thermal engineering has long been left out of the concurrent engineering environment dominated by CAD (computer aided design) and FEM (finite element method) software. Current tools attempt to force the thermal design process into an environment primarily created to support structural analysis, which results in inappropriate thermal models. As a result, many thermal engineers either build models "by hand" or use geometric user interfaces that are separate from and have little useful connection, if any, to CAD and FEM systems. This paper describes the development of a new thermal design environment called the Thermal Desktop. This system, while fully integrated into a neutral, low cost CAD system, and which utilizes both FEM and FD methods, does not compromise the needs of the thermal engineer. Rather, the features needed for concurrent thermal analysis are specifically addressed by combining traditional parametric surface based radiation and FD based conduction modeling with CAD and FEM methods. The use of flexible and familiar temperature solvers such as SINDA/FLUINT (Systems Improved Numerical Differencing Analyzer/Fluid Integrator) is retained.

Panczak, Tim↗
NASA NTRS2004

Reducing Design Cycle Time and Cost Through Process Resequencing

In today's competitive environment, companies are under enormous pressure to reduce the time and cost of their design cycle. One method for reducing both time and cost is to develop an understanding of the flow of the design processes and the effects of the iterative subcycles that are found in complex design projects. Once these aspects are understood, the design manager can make decisions that take advantage of decomposition, concurrent engineering, and parallel processing techniques to reduce the total time and the total cost of the design cycle. One software tool that can aid in this decision-making process is the Design Manager's Aid for Intelligent Decomposition (DeMAID). The DeMAID software minimizes the feedback couplings that create iterative subcycles, groups processes into iterative subcycles, and decomposes the subcycles into a hierarchical structure. The real benefits of producing the best design in the least time and at a minimum cost are obtained from sequencing the processes in the subcycles.

Rogers, James L.↗
NASA NTRS1996

Working on the Boundaries: Philosophies and Practices of the Design Process

While systems engineering process is a program formal management technique and contractually binding, the design process is the informal practice of achieving the design project requirements throughout all design phases of the systems engineering process. The design process and organization are systems and component dependent. Informal reviews include technical information meetings and concurrent engineering sessions, and formal technical discipline reviews are conducted through the systems engineering process. This paper discusses and references major philosophical principles in the design process, identifies its role in interacting systems and disciplines analyses and integrations, and illustrates the process application in experienced aerostructural designs.

Ryan, R.↗
NASA NTRS1993

Systems design analysis applied to launch vehicle configuration

As emphasis shifts from optimum-performance aerospace systems to least lift-cycle costs, systems designs must seek, adapt, and innovate cost improvement techniques in design through operations. The systems design process of concept, definition, and design was assessed for the types and flow of total quality management techniques that may be applicable in a launch vehicle systems design analysis. Techniques discussed are task ordering, quality leverage, concurrent engineering, Pareto's principle, robustness, quality function deployment, criteria, and others. These cost oriented techniques are as applicable to aerospace systems design analysis as to any large commercial system.

Ryan, R.↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we describe JPL’s concurrent engineering A-Team and Team X support to the Psyche competed concept study team in the areas of 1) Initial Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery-class mission started as a grassroots idea from Principal Investigator L.T. ElkinsTanton. Is there a compelling Discovery mission to visit the interior of a body for the first time, by sending a mission to an iron metal asteroid? In less than five years the Psyche concept was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and subject matter experts throughout their mission concept formulation lifecycle

Ziemer, John↗
NASA NTRS2018

How Do You Go From a Concept Idea to a NASA Selected Mission? Formulating the Psyche Discovery Mission with JPL's Concurrent Engineering Teams

JPL’s Office of Formulation provides continuity of support and access to domain subject matter experts, as Principal Investigators mature their mission concepts from “cocktail napkin” ideas to Preliminary Design Reviews [1]. Using NASA’s Psyche mission as a case study, we will describe JPL’s concurrent engineering ATeam and Team X support to the Psyche competed concept study team in the areas of 1) Science Feasibility, 2) Trade Space Exploration, 3) Spacecraft Point Design and Cost Estimate, 4) Science, Technical, Management, and Cost Review, and 5) Strategy and Communication Development. NASA’s Psyche Discovery class mission started as a grassroots idea in our A-Team facility, and in less than five years was selected as a mission under NASA’s Discovery Program. While Psyche had a dedicated concept development team [2], they utilized JPL’s concurrent engineering teams, methods, analysis tools, and experts throughout their mission concept lifecycle.

Ziemer, John↗
NASA NTRS1995

DREAMS and IMAGE: A Model and Computer Implementation for Concurrent, Life-Cycle Design of Complex Systems

Computing architectures are being assembled that extend concurrent engineering practices by providing more efficient execution and collaboration on distributed, heterogeneous computing networks. Built on the successes of initial architectures, requirements for a next-generation design computing infrastructure can be developed. These requirements concentrate on those needed by a designer in decision-making processes from product conception to recycling and can be categorized in two areas: design process and design information management. A designer both designs and executes design processes throughout design time to achieve better product and process capabilities while expanding fewer resources. In order to accomplish this, information, or more appropriately design knowledge, needs to be adequately managed during product and process decomposition as well as recomposition. A foundation has been laid that captures these requirements in a design architecture called DREAMS (Developing Robust Engineering Analysis Models and Specifications). In addition, a computing infrastructure, called IMAGE (Intelligent Multidisciplinary Aircraft Generation Environment), is being developed that satisfies design requirements defined in DREAMS and incorporates enabling computational technologies.

Hale, Mark A.↗
NASA NTRS1993

Interdisciplinary technology

The 'computational test-cell' will enable the incorporation of new methodologies, such as concurrent engineering and probabilistic methods, into the propulsion design process. This will provide the capability to conduct credible, interdisciplinary analyses of new propulsion concepts and designs. Probabilistic methods can be used as the basis for reliability-based design. Recently methods have been devised that provide the capability of simulating the performance of propulsion systems at several levels of resolution. These methods make it possible to quantify uncertainty and to establish confidence bounds for the calculated values. The introduction of reliability-based design methodology along with probabilistic analyses will provide a tool to reduce the design space for new systems and to reduce our dependence on hardware testing for proof-of-concept and system integration demonstrations. The resulting simulations will reduce the need for testing and identify potential operational problems early in the design process. This capability will make it possible to compute the expected performance, stability, reliability, and life of propulsion components, subsystems, and systems at design and off-design conditions, to bring life cycle cost trade-offs early into the design process and to determine optimum designs to satisfy specified mission requirements.

Nichols, Lester D.↗
NASA NTRS1994

Implementing Software Safety in the NASA Environment

Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.

Wetherholt, Martha S.↗
NASA NTRS2001

Non-Deterministic, Non-Traditional Methods (NDNTM)

The review effort identified research opportunities related to the use of nondeterministic, nontraditional methods to support aerospace design. The scope of the study was restricted to structural design rather than other areas such as control system design. Thus, the observations and conclusions are limited by that scope. The review identified a number of key results. The results include the potential for NASA/AF collaboration in the area of a design environment for advanced space access vehicles. The following key points set the context and delineate the key results. The Principal Investigator's (PI's) context for this study derived from participation as a Panel Member in the Air Force Scientific Advisory Board (AF/SAB) Summer Study Panel on 'Whither Hypersonics?' A key message from the Summer Study effort was a perceived need for a national program for a space access vehicle whose operating characteristics of cost, availability, deployability, and reliability most closely match the NASA 3rd Generation Reusable Launch Vehicle (RLV). The Panel urged the AF to make a significant joint commitment to such a program just as soon as the AF defined specific requirements for space access consistent with the AF Aerospace Vision 2020. The review brought home a concurrent need for a national vehicle design environment. Engineering design system technology is at a time point from which a revolution as significant as that brought about by the finite element method is possible, this one focusing on information integration on a scale that far surpasses current design environments. The study therefore fully supported the concept, if not some of the details of the Intelligent Synthesis Environment (ISE). It became abundantly clear during this study that the government (AF, NASA) and industry are not moving in the same direction in this regard, in fact each is moving in its own direction. NASA/ISE is not yet in an effective leadership position in this regard. However, NASA does have complementary software interoperability efforts that should be a part of any major ISE program. Software standards that assure interoperability of data systems and modeling representations are enabling for the proposed research advocated herein and should be a major element in the ISE initiative. The international standard for data interchange is known by the acronym 'STEP.' The NASA participation and lead for that effort is at the Goddard Space Flight Center. NASA/GRC is leading an effort to define CAD geometry standards through the Object Management Group (OMG). To enable the design environment so necessary to the above national vision for a unique space vehicle will require an integrating software environment with interoperability standards that allow the development and widespread deployment of tools and toolsets, rather than traditional "shrink-wrapped" software used by engineers today.

Cruse, Thomas A.↗
NASA NTRS2005

Collaborative Mission Design at NASA Langley Research Center

NASA Langley Research Center (LaRC) has developed and tested two facilities dedicated to increasing efficiency in key mission design processes, including payload design, mission planning, and implementation plan development, among others. The Integrated Design Center (IDC) is a state-of-the-art concurrent design facility which allows scientists and spaceflight engineers to produce project designs and mission plans in a real-time collaborative environment, using industry-standard physics-based development tools and the latest communication technology. The Mission Simulation Lab (MiSL), a virtual reality (VR) facility focused on payload and project design, permits engineers to quickly translate their design and modeling output into enhanced three-dimensional models and then examine them in a realistic full-scale virtual environment. The authors were responsible for envisioning both facilities and turning those visions into fully operational mission design resources at LaRC with multiple advanced capabilities and applications. In addition, the authors have created a synergistic interface between these two facilities. This combined functionality is the Interactive Design and Simulation Center (IDSC), a meta-facility which offers project teams a powerful array of highly advanced tools, permitting them to rapidly produce project designs while maintaining the integrity of the input from every discipline expert on the project. The concept-to-flight mission support provided by IDSC has shown improved inter- and intra-team communication and a reduction in the resources required for proposal development, requirements definition, and design effort.

Gough, Kerry M.↗