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.
Team X is a concurrent engineering team for rapid design and analysis of space mission concepts. It was developed in 1995 by JPL to reduce study time and cost. More than 1100 studies have been completed It is institutionally endorsed and it has been emulated by many institutions. In Concurrent Engineering (i.e., Parallel) diverse specialists work in real time, in the same place, with shared data, to yield an integrated design
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.
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.
The Advanced Projects Design Team, also known as Team X, is a concurrent engineering team that quickly and cheaply designs space mission architectures including the flight system and subsystems, the trajectory, and ground system. Through the use of ICEMaker, an Excel spreadsheet database, the parameters from each subsystem can be shared and used among the other subsystems. This allows for entire missions to be planned with only a few short design team sessions. Based on the results, the feasibility of the mission concept can be determined. Over the Years since the team was created, the amount of information being shared among subsystems on the database has increased, however many of the parameters are now obsolete. Removal of these unused parameters Will clean UP the database and help to streamline the mission design process. By comparing parameter files from previous Team X mission studies, the parameter usage can be determined. As was initially suspected there are more unused parameters on the database than parameters that are actually used.
The Jet Propulsion Laboratory's Advanced Design Team was formed in April 1995 to improve the quality and reduce the cost of JPL proposals and advanced mission studies. Currently a consolidation attempt is underway to develop a Model Library for use by JPL's Advanced Projects Design Team by collecting existing instrument models for inclusion in the library. This will allow users to readily find models of interest. In addition to this, there is also an attempt underway to develop a new approach to instrument model design used by the Advanced Design Team (Team X). This new approach consists of splitting up the different model parts such as orbital parameters, instrument parameters and instrument outputs into separate searchable parts. The user can then decide between design trades and use the different pieces to construct a model that will fit their needs. As well, this will lead to the opportunity for the large variety of usable instrument models.
A Mars sample return mission will answer critical questions concerning the possibility of life on Mars.
In the past decade, many changes have been made to Team X's process of designing each spacecraft, with the purpose of making the overall procedure more efficient over time. One such improvement is the use of information databases from previous missions, designs, and research. By referring to these databases, members of the design team can locate relevant instrument data and significantly reduce the total time they spend on each design. The files in these databases were stored in several different formats with various levels of accuracy. During the past 2 months, efforts have been made in an attempt to combine and organize these files. The main focus was in the Instruments department, where spacecraft subsystems are designed based on mission measurement requirements. A common database was developed for all instrument parameters using Microsoft Excel to minimize the time and confusion experienced when searching through files stored in several different formats and locations. By making this collection of information more organized, the files within them have become more easily searchable. Additionally, the new Excel database offers the option of importing its contents into a more efficient database management system in the future. This potential for expansion enables the database to grow and acquire more search features as needed.
This document is intended to stimulate discussion of the topic described. All technical and cost analyses are preliminary. This document is not a commitment to work, but is a precursor to a formal proposal if it generates sufficient mutual interest. The data contained in this document may not be modified in any way. Cost estimates described or summarized in this document were generated as part of a preliminary, first-order cost class identification as part of an early trade space study, are based on JPL-internal parametric cost modeling, assume a JPL in-house build, and do not constitute a commitment on the part of JPL or Caltech. JPL and Team X add cost reserves for development and operations. Unadjusted estimate totals and cost reserve allocations would be revised as needed in future more-detailed studies as appropriate for the specific cost-risks for a given mission concept.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
No abstract provided