12.07.2015 Views

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

16.1.1.3 <strong>Flight</strong> science downlink databaseIssue Summary: Use flight science downlink database for system functional testing.Description of the <strong>GP</strong>-B experience:During system and vehicle functional testing prior to launch, a custom engineering data analysis package wasused to evaluate system performance. This package was incompatible with the flight data system and was onlyavailable at Lockheed-Martin, the system integrator. A separate database was to be used to manage data fromthe vehicle once on orbit.A lack of load-testing of this science database, especially using the science data reduction applications, longaccess times. Lack of system administrator resources slowed the development and deployment of hardware andsoftware solutions to the data bottlenecks.Lessons:1. Dedicate personnel resources to develop flight database infrastructure early in the program.2. Performance test database with high user loads to identify and rectify bottlenecks prior to launch.3. Establish one master database for both vehicle test and operations.16.1.1.4 Early integrated vehicle testingIssue Summary: Perform early integrated tests of the space vehicle.Description of the <strong>GP</strong>-B experience:A system level test was performed late in the program. This test determined that the ECU was generating noiseadversely impacting the SRE. Removing the ECU from the space vehicle for rework resulted in a program delay.Lessons:1. Perform perceptive system level tests as early as possible in during the integration of the vehicle.2. Allow significant spans of time to perform integrated vehicle tests; plan time in the schedule to performsystem rework if necessary. Hold tight to this contingency time – do not trade it off for schedule reliefelsewhere in the program.16.1.1.5 Configuration verification prior to vehicle power-onIssue Summary: Verify vehicle configuration prior to power-on to avoid blowing fuses.Description of the <strong>GP</strong>-B experience:Power distribution fuses were blown during in-process testing of the space vehicle. The most likely cause was anin-work power harness with non-terminated wires touching the spacecraft structure when power was applied.Lesson:• Verify configuration of vehicle, especially un-terminated cables, to ensure that power can safely beapplied without the risk of a short circuit.16.1.1.6 Customer-contractor information exchangeIssue Summary: Establish customer-to-contractor information exchange protocols early.444 March 2007 Chapter 16 — Lessons Learned and Best Practices

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!