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

5.3.3.1 Anomaly Investigation and ResolutionOnce the vehicle is in a safe configuration the Anomaly Team lead, in consultation with the Anomaly ReviewBoard and the Anomaly Resolution Coordinator, develops, tests, and implements a plan to isolate and correctthe anomaly.After an Anomaly Team has performed its analysis, they meet with the Anomaly Review Board and recommendany resolution options to correct the problem or any further investigative steps they feel need to be made tocome to a resolution method.The Anomaly Resolution Coordinator and the Anomaly Review Board then decides upon a resolution methodand grants approval to implement the mitigation.• If the resolution consists of an already-existing contingency procedure that the Anomaly Board approvesfor use as is, the procedure will be executed in the appropriate manner, usually by an SPC load• If the contingency procedure does not exist, the Anomaly Team will develop the appropriate procedure,soliciting whatever additional help they need via the Anomaly Review Board. The procedure willundergo off-vehicle testing prior approval.5.3.3.2 Management ReportingIn the event of a major space vehicle anomaly the Flight Director immediately notifies the Stanford UniversityProgram Manager in parallel with the Mission Director. The Mission Director and Program evaluates theanomaly and reports their findings to the MSFC Program Manager or his designee. Other classes of anomaliesare reported to Program Management through the Mission Director as soon as practical aft the board’s initialassessment.5.3.3.3 Anomaly ClosureOnce the root cause of the anomaly has been identified, and rectifying or mitigating activities are complete, theAnomaly Team and Anomaly Review Board will submit the anomaly for closure to the Mission Director. Afterreview, the Mission Director will close the anomaly in the ARB database.5.3.4 Anomaly RoomAn anomaly room has been setup outside the MOC as a common meeting area for review and analysis ofanomalies. The room has been designed to collect vehicle data from a variety of sources, act as a library of thekey vehicle technical schematics and operations documentation, and permit multi-mode communication withboth on-site and remote members of the GP-B team.Mission Operations Data:• Non-commanding ops console set (POD) to shadow PODs in MOC for real-time data display.• RTWorks display showing vehicle health and safety data.• Access to post-processed vehicle database with a variety of tools.• Copies of Lockheed-Martin SDRLs, engineering memos.• Copies of Flight Ops Handbook.• Safe mode logic, activation, and recovery plans.130 March 2007 Chapter 5 — Managing Anomalies and Risk