Search NASASearch

NASA NTRS · 20060043274

Next-generation concurrent engineering: developing models to complement point designs

Abstract

Concurrent Engineering Design (CED) teams have made routine the rapid development of point designs for space missions. The Jet Propulsion Laboratory's Team X is now evolving into a 'next-generation CED; in addition to a point design, the Team develops a model of the local trade space. The process is a balance between the power of a model developing tools and the creativity of humal experts, enabling the development of a variety of trade models for any space mission. This paper reviews the modeling method and its practical implementation in the ED environment. Example results illustrate the benefit of this approach.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Morse, Elizabeth, Leavens, Tracy, Cohanim, Babak, Harmon, Corey, Mahr, Eric, Lewis, Brian. 2006-03-01. Next-generation concurrent engineering: developing models to complement point designs. https://ntrs.nasa.gov/citations/20060043274

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

2020 I.F._Wickizer_New CE Tool for MDC_Final Report

Our team surveyed available products and found no readily-available/U.S. commercial or Agency products which supported our envisioned workflow for the Mission Design Center and the concurrent engineering (CE) process we use. Therefore, we sought to create our own CE tool. Changes in agency policy during the performance period allowed us to shift direction and instead adapt our previous legacy tool (Atlas) to include the collaboration features we sorely needed. Atlas relied upon databases for its back-end data management. Poseidon, the work proposed under this effort, was also intended to leverage from that previous back end (in part). However, in May 2021, EUSO announced that “SBU/CUI Information Can Now Be Shared/Stored Within O365 Without Encryption.” Consequently, we made the decision to use O365 in place of our back end. This change provides for version history, collaborative simultaneous editing, and other collaboration tools agency-wide that were previously unavailable with the old database architecture. The new Atlas O365 has more flexibility and capability for users. It’s now easier for users to switch between using the tool for concurrent engineering and individual subsystem engineering. A version was delivered for concurrent engineering of small satellite missions; so far, it has been used successfully on the Aeolus MDC study. Atlas O365 will facilitate the design and assessment of Small Satellite Missions at low Concept Maturity Level at Ames. Feasibility assessments on mission concepts still at a low CML permit strategic planning and decision-making efforts at the center level about which concepts should be pursued and proposed.

concurrent engineering

Spreadsheets in Team X: Preserving Order in an Inherently Chaotic Environment

JPL is NASA's prime center for deep space missions. In response to the need to reduce the cost and time to complete early concept studies and proposals JPL created the first concurrent engineering team in the aerospace industry: Team X. Started in 1995, Team X has carried out over 800 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. Since its inception, the software backbone of this highly successful design team - engaged in examining some of NASA's cutting edge concepts - has been the unassuming spreadsheet. Over the years the Team X spreadsheet-based tools have evolved from simple standalone engineering models into a networked spreadsheet intensive system with real time parameter updating. Recent new capabilities include stochastic cost estimation and a graphical drag and drop block diagram that automatically populates the related spreadsheet parameters of cost, mass and power. This paper describes how the spreadsheet functions within Team X: its history, architecture, current capabilities, enabling strengths and persistent weaknesses. In addition, the verification methods and institutional oversight that have evolved as the Team X products became increasingly critical to Laboratory success are also discussed.

concurrent engineering