REG NASA-LLIS-3640-2011 Lessons Learned Ground Lightning Monitoring System (GLMS).pdf

1、Public Lessons Learned Entry: 3640 Lesson Info: Lesson Number: 3640 Lesson Date: 2010-08-27 Submitting Organization: KSC Submitted by: Annette Pitt Subject: Ground Lightning Monitoring System (GLMS) Abstract: The Ground Lightning Monitoring System (GLMS) was sold to the Shuttle Program as a go/no-go

2、 indicator for the overall health of the Space Shuttle vehicle following a lightning event. The system, recently developed by the Navy for submarine applications, was selected because of its ability to detect and measure magnetic fields. Because GLMS was a new system involving unique technology, its

3、 implementation as a lightning monitoring system at KSC essentially became a research and development project. This called the validity and accuracy of the data into question and prevented the use of GLMS as a fully critical system. Description of Driving Event: Existing lightning instrumentation sy

4、stems, the Lightning Induced Voltage Instrumentation System (LIVIS) and the Catenary Wire Lightning Instrumentation System (CWLIS), were originally assessed as noncritical (nonconfigured) systems but were later reassessed as critical. Several deficiencies were noted during the reassessment: lack of

5、redundancy and design to satisfy a critical system requirement, inability to detect system failures, no remote health-monitoring capabilities, and lack of certification and configuration control for the software application. Because LIVIS and CWLIS provided only limited insight into vehicle systems,

6、 other labor-intensive and time-consuming processes for collecting and evaluating data were necessary to ascertain vehicle health. GLMS was developed to improve insight into the health of vehicle systems and to do so faster and with fewer resources, but it required further validation to meet KSC req

7、uirements. Lesson(s) Learned: GLMS lacked adequate design requirements. In some cases, requirements were written to the operation specifications of hardware that had already been purchased. Hardware was deployed before the system operation was fully understood. System functions were still being test

8、ed and undergoing design changes during attempts to certify the system for critical use. GMLS failed to satisfy the requirements of a critical system and did not provide data that could be completely understood or accepted without question. Recommendation(s): Entertain a COTS solution if at all poss

9、ible. If a custom solution is chosen for implementation, ensure that the research and development are complete and independent of the certification process. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Aeronautics Rese

10、arch Space Operations Additional Key Phrase(s): Test & Verification Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Mission definition and planning Crew operations and supprot concepts Review systems and boards Systems analysis - cost analysis Entry

11、Systems Ground processing and manifesting Early requirements and standards definition Launch support systems Ground support systems Ground Operations Aircraft Ground Equipment Additional Info: Project: Space Shuttle Program Approval Info: Approval Date: 2011-03-01 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-