Spacecraft COst REduction Team (SCORE): TQM/CI on a massive scale
The business of building satellites and space systems has matured. Few missions require, or can afford, excellent performance at any price. The new paradigm is doing more with less, providing quality systems at lower cost--in other words, doing our job 'Faster-Better-Cheaper.' The TRW Spac...
Gespeichert in:
1. Verfasser: | |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | The business of building satellites and space systems has matured. Few missions require, or can afford, excellent performance at any price. The new paradigm is doing more with less, providing quality systems at lower cost--in other words, doing our job 'Faster-Better-Cheaper.' The TRW Spacecraft COst REduction (SCORE) initiative was launched in 1990 by Daniel S. Goldin, then general manager of TRW's Space & Technology Group. The SCORE mission is to apply continuous improvement (CI) techniques to effect major reductions in the cost (our primary goal) and span time (as a corollary) required for the production of spacecraft. SCORE is a multi-year initiative that is having a profound effect on both the procedural and the cultural aspects of how we do business. The objectives of this initiative are being realized. The focus of this paper is not on the results of SCORE per se, but rather on the things we have leaned about how to do continuous improvement on a massive scale, with multilevel (hierarchical) CI teams. The following sections summarize the chronology of the SCORE initiative, from team formation to development of the year-end report for 1991. Lessons learned, the core of this presentation, are discussed--with particular focus on the unique aspects of SCORE. The SCORE initiative is continuing and, as a part of our evolving culture, will never end. It has resulted in profound insights into the way we do work and (the topic at hand) how to do CI for large and complex multidisciplinary development activities. |
---|