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...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5.3.5 Anomaly Identification and Response PlanThe following is an outline of the steps to be followed in response to an anomaly. Note, iteration will likely berequired within this plan as an anomaly investigation proceeds:1. Any real-time operations team member that suspects an anomaly informs the current shift <strong>Flight</strong>Director.2. The <strong>Flight</strong> Director, Mission Director, or Anomaly Review Board member collects information andrecognizes it as a an anomaly.• In the event of a major anomaly, the <strong>Flight</strong> Director uses pre-approved contingency procedures tosafe the vehicle where possible.• In the event of a medium anomaly, the <strong>Flight</strong> Director consults with the Mission Director andAnomaly Review Board on a course of action.• In the event of a time minor anomaly, the <strong>Flight</strong> Director uses pre-approved contingency proceduresor flight rules to recover from the anomaly.• In the event of an observation, the Anomaly Review Board informs the Mission Director and thesystem RE of the observation for evaluation.3. The <strong>Flight</strong> Director notifies continues to assess the real-time operations issues and timeline impact of theanomaly.4. The Anomaly Resolution Coordinator convenes the Anomaly Review Board, briefs the board on theanomaly, commissions an Anomaly Team, and coordinates with the board for resources, schedule, andmilestones for investigation.5. The Mission Director works with the Anomaly Review Board to assess short and long-term implicationsto the mission timeline.6. The Anomaly Coordinator tracks the actions of the Anomaly Team and maintains the status documents(databases) for the program.7. The Anomaly Review Board manages Anomaly Team’s activities and augments the makeup of the teamas needed to successfully understand the anomaly.8. Once the anomaly is understood, the Anomaly Coordinator and the Anomaly Review Board proposes aplan for resolution. Should this anomaly require software changes or procedure changes, the AnomalyResolution Coordinator will work with the Anomaly Team and the <strong>Flight</strong> Software Team to generate theappropriate change paperwork.9. The Anomaly Review Board reviews and endorses recommended mitigations from the Anomaly Teamsand coordinates their insertion into the timeline with the Mission Director. The interface between theBoard and Mission Planning is via the Timeline Change Request (TCR) process. If real-timecommanding is required, a Pass Plan Change Request (PPCR) is coordinated with the <strong>Flight</strong> Director.10. The Anomaly Coordinator briefs the <strong>Flight</strong> Director of the chosen course of action.11. The Anomaly Team monitors and assesses the effects of the mitigations via flight telemetry and reportsresults to the ARB.12. The ARB and Anomaly Team assesses downstream implications of anomaly and possible operationalchanges to mitigate any negative effects.13. The Anomaly Resolution Coordinator completes the post anomaly report.14. The Mission Director closes the anomaly when mitigations are complete.132 March 2007 Chapter 5 — Managing Anomalies and Risk

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

Saved successfully!

Ooh no, something went wrong!