REG NASA-LLIS-1518--2004 Lessons Learned - Early Involvement of Mission Ops is a Key Success Factor.pdf

《REG NASA-LLIS-1518--2004 Lessons Learned - Early Involvement of Mission Ops is a Key Success Factor.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1518--2004 Lessons Learned - Early Involvement of Mission Ops is a Key Success Factor.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1518Lesson Info:a71 Lesson Number: 1518a71 Lesson Date: 2004-11-01a71 Submitting Organization: JPLa71 Submitted by: Neil ToySubject: Early Involvement of Mission Ops is a Key Success Factor Abstract: Because the MER Flight Control Team (FCT) was fully formed only one month pri

2、or to MER launch, critical software engineering and operations management problems resulted. Staff FCT participation in project development at the beginning of Phase C and assure continued FCT involvement in project activities. Or at a minimum, select a few operations team members for early training

3、.Description of Driving Event: The Mars Exploration Rover (MER) Flight Control Team (FCT) was fully formed only one month prior to the June 2003 launch of the first rover and did not participate in the development of the Mission Operations System (MOS) and the Ground Data System (GDS). Had the team

4、been involved at the beginning of Phase C (Design and Build phase), critical software engineering and operations management problems, that were accepted as known risks, might have been avoided:a71 Late Formation of the Ops Team. The FCT was not trained and certified in time for launch operations, an

5、d it had insufficient time to become familiar with the spacecraft and project procedures. The FCT was staffed too late to provide input or effect change to critical processes and project developed tools. For example, when MER held its first Operations Readiness Test (ORT), the FCT was funded at a on

6、e-half person level, and that person was too busy writing team procedures to participate in the ORT. Also, additional personnel who joined the ops team just prior to the launch date lacked user accounts on the workstations used for spacecraft command and control.a71 Command File Format. During devel

7、opment of the MER command files, the test engineers changed the naming convention to a longer 20 to 50-character format. Because the length of Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-the file names exceeds the width of the FCT displays, the c

8、ontrollers have to call out each character of the file name over the voice net prior to transmission to the spacecraft. This increases the risk that the FCT may send erroneous commands to the spacecraft. The FCT was not involved in the decision to change the naming convention, and a return to the pr

9、eferred shorter format would require MER to rebuild and revalidate the command files.Additional Key Words: Deep Space Telemetry, Tracking and Command System (TTC)Lesson(s) Learned: 1. Inadequate involvement of Operations Engineering in project development may increase the risk to mission success.2.

10、Late formation of the Flight Control Team can place a spacecraft in the hands of Mission Control Engineers who are poorly qualified and inadequately prepared for mission operations.Recommendation(s): 1. Staff FCT participation in project development at the beginning of Phase C (Design and Build phas

11、e).2. Assure continued FCT involvement in the following project activities - GDS testing, system integration and test (ATLO), MOS process development, ORT, and FCT tool development.3. If early participation by the full mission operations team in project development is not feasible, project and line

12、management should select a few operations team members for early training to support priority activities such as MOS and GDS development and testing.Evidence of Recurrence Control Effectiveness: Preventive Action Notice No. Z87147 was opened by JPL on August 2, 2005 to initiate and document appropri

13、ate Laboratory-wide corrective action on the above recommendations.Documents Related to Lesson: JPL Flight Project Practices, Rev. 5, JPL Doc ID 58032, February 27, 2003, Paragraphs 6.3.8, 6.3.9, 6.3.11, and 6.3.15.Mission Directorate(s): a71 Exploration SystemsProvided by IHSNot for ResaleNo reprod

14、uction or networking permitted without license from IHS-,-,-a71 Sciencea71 Aeronautics ResearchAdditional Key Phrase(s): a71 Flight Operationsa71 Ground Equipmenta71 Ground Operationsa71 Hardwarea71 Program and Project Managementa71 Safety & Mission Assurancea71 Softwarea71 Spacecrafta71 Test & VerificationAdditional Info: Approval Info: a71 Approval Date: 2005-04-14a71 Approval Name: Carol Dumaina71 Approval Organization: JPLa71 Approval Phone Number: 818-354-8242Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-