1、Public Lessons Learned Entry: 2796 Lesson Info: Lesson Number: 2796 Lesson Date: 2010-05-7 Submitting Organization: KSC Submitted by: Annette Pitt Subject: System or Set Configuration Verifications Prior to Operations Abstract: Configuration procedures for Launch Processing System (LPS) systems were
2、 not specifically designed to verify that all systems and end items are ready to support Operations. Over time many off-line checkouts and confidence tests have been developed for LPS systems that test interfaces, verify hardware and software readiness, and establish baseline states. Many of these t
3、ests are specifically designed for particular support activities. These procedures provide greater assurance that the LPS configuration will satisfactorily support scheduled testing. Description of Driving Event: In several instances it was determined that disruptions and downtime could have been av
4、oided by performing off-line systems testing prior to scheduled support activities. These events have led to formal procedures that are now scheduled and executed regularly - some daily and others for specific operations throughout a flow. Lesson(s) Learned: For systems that support activities that
5、are critical to safety and schedule, support impact is not tolerable. Procedures and methods that can ensure the proper configuration of these support systems before testing begins are therefore extremely valuable. While these procedures do require planning and time allotted for their execution, the
6、se expenditures are trivial when compared to the impact of delays in integrated testing. Usually these types of procedures have been developed in response to an unforeseen event, but proactive system examination and analysis can also identify the need for specific verifications that can prevent thes
7、e situations before they occur. Examples of current LPS confidence tests include: 1. LPS Line Validations End-to-end circuit continuity tests and level checks performed each time the Firing Room to test site configuration is changed. 2. LPS Vehicle Safing Check-out Performed prior to initial vehicle
8、 testing at the pad, this tests the vehicle safing interfaces and software against a math model. 3. Verification of software configuration has been incorporated as a setup step in many operational procedures. 4. Checklists performed every shift re-verify the configuration of LPS hardware and softwar
9、e. Recommendation(s): When designing systems that will support critical testing, the development of verification procedures that ensure operability in every mode should be included in the design plan. As a system is developed and tested, any configuration problems encountered should be documented, a
10、nd procedures should be developed that preclude recurrence. It may also be possible to “design out” undesirable configurations. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: Click here to download Line Validations Work Order Click here to download Safing Checks Work
11、Order Click here to download Shift Change Checklist Mission Directorate(s): Exploration Systems Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- Space Operations Additional Key Phrase(s): 1.Software 1.Ground Operations 1.Configuration control and dat
12、a management 1.Engineering design and project processes and standards 1.Launch Systems 1.Ground support systems 1.Configuration Management 1.Computers 1.Launch support systems 1.Information Technology/Systems 1.Hardware Additional Info: Project: Space Shuttle Program Approval Info: Approval Date: 2010-07-07 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
