Search NASA⌕ Search

SEARCH · Search NASA

Results for “concurrent 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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2021

Lessons Learned in Remote Participant Concurrent Engineering Concept Development Studies

Team-X was born from a need to perform rapid space mission design for principal investigator-led competed proposals in the mid-1990s. Throughout the last 25 years, Team-X at the Jet Propulsion Laboratory has expanded its application of the collaborative, concurrent study approach into every facet necessary to win competed proposals. The COVID-19 pandemic of 2020 created an immediate and new constraint on these studies – the need to conduct them with remote participants, both on the client side requesting the study, but also on the provider side producing the study. This paper provides lessons learned from dozens of design studies run by Team-X at the Jet Propulsion Laboratory during the COVID-19 pandemic. These lessons span all aspects of the information infrastructure: the people, processes, procedures, methods, tools, and “facilities”. These lessons learned will have applicability post-pandemic, as they have shown how best to incorporate participants, both on the provider side, and on the client side, who cannot travel or otherwise be co-located during collaborative, concurrent study sessions.

Nash, Alfred↗
NASA NTRS2021

The Evolution of Team-X: 25 Years of Concurrent Engineering Design Experience

Established in 1995 in response to NASA’s “Faster, Better, Cheaper” era, Team-X was born from a need to perform rapid space mission design for principal investigator-led competed proposals. The success and sustainability of Team-X over the 25 years that have followed is directly attributable to the Team-X business model and its evolution over time. While dozens of organizations and institutions have emulated the Team-X design process, there are nuances to the Team-X business model that are unique to JPL, and explain why it is different than other concurrent design teams. One of the key components of a business model is the customer segments that are served. Team-X was founded to conduct the Pre-Phase A work necessary to formulate a portfolio of multiple planetary mission concepts, but has since expanded to include the capability to conduct studies for Earth science, astrophysics, and heliophysics missions as well as Human Exploration and Operations missions and space technology development. Team-X delivers value to its clients both in terms of speed and cost. Team-X has also added value by creating teams to enable the development of Instrument and SmallSat Concepts. Value has further been enhanced through a revision of its process for reviews and the addition of pre-design architecting capabilities. Other aspects of the Team-X infrastructure, in addition to study process, have enabled it to succeed for over a quarter century. From our most important resource, the people, our tools, especially for cost estimating, as well as our increasing capable IT infrastructure have contributed to our capability to meet the demands of our clients. The Team-X business model and its evolution over time, position it well for success in the decades to come.

Murphy, Jonathan↗
NASA NTRS1991

Concurrent engineering

The following subject areas are covered: issues (liquid rocket propulsion - current development approach, current certification process, and costs of engineering changes); state of the art (DICE information management system, key government participants, project development strategy, quality management, and numerical propulsion system simulation); needs identified; and proposed program.

Chamis, C. C.↗
NASA NTRS1990

Concurrent engineering design and management knowledge capture

The topics are presented in viewgraph form and include the following: real-time management, personnel management, project management, conceptual design and decision making; the SITRF design problem; and the electronic-design notebook.

Source record↗
NASA NTRS1998

An Example of Concurrent Engineering

The Collaborative Engineering Design and Analysis Room (CEDAR) facility allows on-the- spot design review capability for any project during all phases of development. The required disciplines assemble in this facility to work on any problems (analysis, manufacturing, inspection, etc.) associated with a particular design. A small highly focused team of specialists can meet in this room to better expedite the process of developing a solution to an engineering task within the framework of the constraints that are unique to each discipline. This facility provides the engineering tools and translators to develop a concept within the confines of the room or with remote team members that could access the team's data from other locations. The CEDAR area is envisioned as excellent for failure investigation meetings to be conducted where the computer capabilities can be utilized in conjunction with the Smart Board display to develop failure trees, brainstorm failure modes, and evaluate possible solutions.

Rowe, Sidney↗
NASA NTRS2000

Use of Concurrent Engineering in Space Mission Design

In recent years, conceptual-phase (proposal level) design of space missions has been improved considerably. Team structures, tool linkage, specialized facilities known as design centers and scripted processes have been demonstrated to cut proposal-level engineering design time from a few months to a few weeks.

concurent Engineering-Space Mission Design↗