REG NASA-LLIS-1503-2003 Lessons Learned - Orbital Space Plane - Communication.pdf

《REG NASA-LLIS-1503-2003 Lessons Learned - Orbital Space Plane - Communication.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1503-2003 Lessons Learned - Orbital Space Plane - Communication.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1503Lesson Info:a71 Lesson Number: 1503a71 Lesson Date: 2003-07-01a71 Submitting Organization: MSFCa71 Submitted by: Lisa CarrSubject: Orbital Space Plane - Communication Abstract: The Orbital Space Plane (OSP) systems design activities were impacted as communications became a

2、n issue, program-to-program cultures clashed, and internal program integration encountered obstacles and walls. Programs cannot expect to modify other programs and organizations operating culture and processes without, first, agreement, and, second, proper implementation. Description of Driving Even

3、t: OSP found it difficult to communicate information across organizations.Lesson(s) Learned: OSP systems design activities were impacted as communications became an issue, program-to-program cultures clashed, and internal program integration encountered obstacles and walls. OSP achieved a level of c

4、ollaboration among various centers that may be unprecedented, yet conflicts still remained.Additionally: a. Communication OSP Program forums did not allow for adequate discussion/questions from the implementing team members so that the basis of the marching orders could be readily understood. Questi

5、oning of direction, decisions, and policies can strengthen the rationale and buy-in. Additionally, successful implementation of Information Technology (IT) requirements for protection of competition sensitive material, resulted in the inability to quickly and effectively disseminate information to t

6、he users.b. Shrinking of the Inner Circle After each occurrence of increased stress (budget cut, schedule Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-accelerated) the “inner circle” of the Program Management team seemed to shrink and data flow to

7、 the mid-level managers and workers was reduced. Recommendation(s): Programs cannot expect to modify other programs and organizations operating culture and processes without, first, agreement, and, second, proper implementation. IT security needs can result in unforeseen, intra-program bottlenecks i

8、n electronic communications. When the volumes of information get large, access becomes more difficult - especially if you allow individual users to set the filing format for storage and retrieval. IT tools must be proven by adequate testing and deployed across all participating centers consistently

9、to ensure adequate and timely communication. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 Exploration Systemsa71 Space Operationsa71 Aeronautics ResearchAdditional Key Phrase(s): a71 Administration/Organizationa71 Program and Project Ma

10、nagementa71 Research & DevelopmentAdditional Info: Approval Info: a71 Approval Date: 2005-04-01a71 Approval Name: Lisa Carra71 Approval Organization: MSFCa71 Approval Phone Number: 256-544-2544Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-