REG NASA-LLIS-2556-2011 Lessons Learned Design for Operations -Operational Costs Drivers.pdf

《REG NASA-LLIS-2556-2011 Lessons Learned Design for Operations -Operational Costs Drivers.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-2556-2011 Lessons Learned Design for Operations -Operational Costs Drivers.pdf（2页珍藏版）》请在麦多课文档分享上搜索。

1、Public Lessons Learned Entry: 2556 Lesson Info: Lesson Number: 2556 Lesson Date: 2010-03-31 Submitting Organization: KSC Submitted by: Annette Pitt Subject: Design for Operations -Operational Costs Drivers Abstract: Space Shuttle processing operations were significantly more complicated and costly t

2、han planned in the original concept of operations because operational requirements were not defined sufficiently during the programs development phase. The program concentrated on developing performance requirements but not requirements related to operational considerations. Attached is a Space Shut

3、tle lessons learned presentation. Description of Driving Event: In 2005, Bo Bejmuk of the Boeing Company presented a set of lessons learned from the Space Shuttle integration process to a group of NASA managers. One of these lessons learned dealt with the operational cost drivers for the Space Shutt

4、le Program. In his presentation, Bejmuk described the original “nave” concept of operations in contrast to the Programs operational reality, which was significantly more complicated and led to a very labor-intensive vehicle. Lesson(s) Learned: Space Shuttle processing operations were significantly m

5、ore complicated and costly than planned in the original concept of operations because operational requirements were not defined sufficiently during the programs development phase. The program concentrated on developing performance requirements but not requirements related to operational consideratio

6、ns. Moreover, the Shuttle design organizations were not held responsible for operational costs that would be incurred, and there were very few incentives for development contractors to incorporate operational considerations into their designs. Recommendation(s): During the development phase of any n

7、ew program, there must be integration between designers in order to achieve continuity between ground operations and flight operations requirements. This can be done by first defining a realistic concept of operations during the development phase, and then by levying these operational requirements o

8、n the development contractors. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: October 2005 Space Shuttle Lessons Learned briefing by Bo Bejmuk Click here to download document Mission Directorate(s): N/A Provided by IHSNot for ResaleNo reproduction or networking permit

9、ted without license from IHS-,-,-Additional Key Phrase(s): Mission and systems trade studies Systems analysis cost analysis Engineering design and project processes and standards Long-term sustainability and maintenance planning Ground support systems Additional Info: Project: Space Shuttle Program Approval Info: Approval Date: 2011-08-03 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-