1、Lessons Learned Entry: 1614Lesson Info:a71 Lesson Number: 1614a71 Lesson Date: 2005-08-29a71 Submitting Organization: ARCa71 Authored by: Donald R. MendozaSubject: Systems Engineering: Functional Performance Verification Abstract: Functional performance verification requirements are critical for ens
2、uring mission hardware will perform as intended. Description of Driving Event: STS 90/Neurolab was a Spacelab module mission focusing on the effects of microgravity on the nervous system. The mission was flown abroad the Columbia and launched on the 17 of April 1998 and lasted 17 days. The goals of
3、Neurolab were to study basic research questions and to increase the understanding of the mechanisms responsible for neurological and behavioral changes in space. The mission was a joint venture of several space agencies and U.S. research agencies including the National Institutes of Health, the Nati
4、onal Science Foundation, and the Office of Naval Research, as well as the space agencies of Canada, France, Germany, and Japan, and the European Space Agency. While the Neurolab mission was an overall success it experienced several on-orbit hardware failures and problems that could have been prevent
5、ed had adequate functional performance verification been accomplished. In fact several of the conditions that the systems experienced on-orbit could have been achieved on ground but were not due to inadequate requirements with regard to what environmental conditions were needed. Lesson(s) Learned: N
6、ot having formal functional performance verification requirements to determine and verify the crews ability to use mission hardware as intended or to ensure the hardware would perform as designed will result in a significant increase in on-orbit crew-hardware interface time and unknown impacts to th
7、e science return. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Recommendation(s): All flight systems must have established functional performance requirements and verify them to ensure they are capable of performing their designed function using t
8、he intended crew interaction in the intended on-orbit environment. The mission should not rely on on-orbit crew time to debug equipment. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: NPR 7120.5Mission Directorate(s): N/AAdditional Key Phrase(s): a71 Configuration Mana
9、gementa71 Independent Verification and Validationa71 Risk Management/Assessmenta71 Safety & Mission AssuranceAdditional Info: Approval Info: a71 Approval Date: 2006-04-17a71 Approval Name: dkruhma71 Approval Organization: HQProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
