Failure of Process / Failure of Mission

Slides:



Advertisements
Similar presentations
©2006 The Aerospace Corporation Activities Associated With Working With Xilinx to Develop A Space Flow for Virtex Family of FPGA’s Larry Harzstark The.
Advertisements

Electronic Measure and Test Unit 53 Task 4 (P4).  A plan that clearly details the tests that will be performed  What to test  How to test (step by.
Mars Climate Orbiter Team Magna Corp: Tim Toba Mohamed Sahil Nyema Johnson Abner Yemaneab University of Minnesota.
Asset Optimization Solutions. Asset Optimization Solutions Will Help to identify and Improve the true Potential of existing Plant and Machinery.
Ask Pete Acquired Software Knowledge Project - Estimation- Tool - Effort Presented to the NASA OSMA SAS ‘01 NASA IV&V Facility September 5-7, 2001 Tim.
21st Annual Arizona Space Grant Consortium Symposium
LSU 10/09/2007System Design1 Project Management Unit #2.
SPACECRAFT ACCIDENTS: EXAMINING THE PAST, IMPROVING THE FUTURE Hubble Recovery with STS Bryan Palaszewski working with the Digital Learning Network NASA.
April 4, 2014 Flight Dynamics 1 MMS-THEMIS Phasing An apples-to-apples comparison between the Winter Nominal and THEMIS Launch Block Conrad Schiff MMS.
System Software Integration Testing Mars Polar Lander Steven Ford SYSM /05/12.
Incident Reporting Procedure
Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.
Understand how space organizations use concepts of operations and system integration plan to ensure the success of their program Space Concept of Operations.
Energy Balancing Credit Proposals Transmission Work Stream 6th November 2008 Mark Cockayne.
Slide 1  Improving the Current State of Software within NASA May 8, 2000 Presentation by CIO, CE, and Code Q SMC and NASA Administrator Version 5 Briefing.
20a - 1 NASA’s Goddard Space Flight Center Attitude Control System (ACS) Eric Holmes, Code 591 Joe Garrick, Code 595 Jim Simpson, Code 596 NASA/GSFC August.
1. Objectives  Describe the responsibilities and procedures for reporting and investigating ◦ incidents / near-miss incidents ◦ spills, releases, ◦ injuries,
JPL AUTONOMOUS RENDEZVOUS OVERVIEW Rob Bailey Jet Propulsion Laboratory Inter-Agency AR&C Working Group Meeting May , 2002 Naval Research Laboratory.
The Solar System Chapter 6 COPY DOWN THE LEARNING GOALS ON PG SKIP 5 LINES BETWEEN EACH!
University of Toronto Department of Computer Science CSC444 Lec02 1 Lecture 2: Examples of Poor Engineering “Software Forensics” Case Studies Mars Pathfinder.
LSU 01/17/2006Spring LaACES Schedule For the semester and the next few weeks.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
FIRST/Planck 12 December 2000PT The FIRST Mission Implementation Status and Schedule T. Passvogel The Promise of FIRST.
1 PPMF101 – Lecture 1 Measurement. 2 Basic quantity & Derived quantity  Base quantity  A quantity which is not a combination of other physical quantities.
NASA’s Mars Climate Orbiter Mishap. References Official investigation report IEEE Spectrum investigation report Official report on project management.
Using the Factor Label Method. “That costs five.”
California Institute of Technology Formalized Pilot Study of Safety- Critical Software Anomalies Dr. Robyn Lutz and Carmen Mikulski Software Assurance.
Observations and Analysis of the Planets AS 103 Lab Part I.
What happened to the Mars Climate Explorer in September 1999? By Leslie Palomino.
SE&I Pre-Proposal Meeting GSFC - JPL Systems Engineering Management Colleen McGraw.
ST5 PDR June 19-20, 2001 NMP 2-1 EW M ILLENNIUM P ROGRA NNMM Program Overview Dr. Christopher Stevens Jet Propulsion Laboratory, California Institute of.
SE-3910 Real-time Systems Week 9, Classes 1 and 2 – Announcement* (regexp style) – Significance Testing – Failure statistics – Structured Analysis & Design.
DAILY fizziks CHALLENGE 2.The United States officially uses the English System, not the Metric System, primarily for measurement. Besides the U.S., the.
CDU – School of Information Technology HIT241 Integration Management - Slide 1 HIT241 - Project Integration Management Introduction Project Integration.
1 Mars Exploration Rovers Spirit SOL-18 Anomaly: NASA IV&V Involvement April 2004.
Operated by Los Alamos National Security, LLC for the U.S. Department of Energy's NNSA UNCLASSIFIED Classified Information Security Event EFCOG Fall Workshop.
Data Flow Diagrams Slide 1. Key Definitions Data flow diagramming shows business processes and the data that flows between them Slide 2.
Two IT Projects that were successful & Two failure projects.
Mars Climate Orbiter. FOR IMMEDIATE RELEASE September 23, 1999 NASA'S MARS CLIMATE ORBITER BELIEVED TO BE LOST NASA's Mars Climate Orbiter is believed.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
Corrective Action Plan Overview Chief Executive Office Risk Management Branch Inspector General Office.
2014 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Tethered Aerostat Program Concept Design Review Team Name Conceptual Design Review University/College Team Members Date.
Standards Certification Education & Training Publishing Conferences & Exhibits Communication necessary to achieve LowE valve sealing compliance Presented.
IISME Fellowship Lockheed Martin Space Systems Summer 2010 SBIRS Space Based Infrared System GEO-1 satellite All pictures are from google.
Conversions using Unit Rates Joanne Smithies Our Lady & St. Gerards RCP.
Tethered Aerostat Program Concept Design Review College of Menominee Nation Conceptual Design Review College of Menominee Nation Marilyn Madosh, Larry.
Presented to: By: Date: Federal Aviation Administration Obstacles in the Visual Segment 20:1 Background, Policies and Action Gerard G Lebar Eastern Flight.
Product Validation Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Session 3: Risk Analysis Tools and Techniques
BPM/NPC Individual-Managing Your Risk Training
Failure of Process / Failure of Mission
Presented to the NASA OSMA SAS ‘01
Improving Accuracy & Consistency in Location Validation
Dimensions and Units Textbook Chapter 14 Today’s highlights:
Data Integrity Leadership Institute
Lesson 3: SI units and prefixes
TEMPO’s Commercially Hosted Payload Concept
AJS 562 Competitive Success/snaptutorial.com
AJS 562 Education for Service/snaptutorial.com
AJS 562 Teaching Effectively-- snaptutorial.com
Incident Reporting And Investigation Program
Systems Engineering Management
BPM/NPC Individual-Managing Your Risk Training
Unit Conversions.
Scale of things : Big and Small
Up and At ‘Em The Importance of Clear Communications
Software Engineering for Safety: a Roadmap
EagleSat 2 – Mission and Development Overview
Project Management Unit #2
Presentation transcript:

Failure of Process / Failure of Mission Mars Climate Orbiter Gerry Tucker [2021275825] (got150030@utdallas.edu) EMSE 6361 – Fall 2015 Term Paper – Interim http://utdallas.edu/~got150030/emse6361/

Case Study Overview

Case Study Overview* Mars Climate Orbiter (MCO) launched Dec. 11, 1998 with an anticipated arrival at Mars of Sept. 1999 On Sept. 23, 1999 all contact was lost as MCO was 4 minutes into the Mars Orbital Insertion (MOI) burn On Sept. 29, 1999 the root cause of the failure was discovered *Background information derived from MCO Mishap Investigation Board Phase 1 Report

Prime contractor for vehicle development Case Study Primaries Lead NASA center for Mars Surveyor Program Project office created by JPL with the responsibility to define the mission, develop the spacecraft / payload elements, and integrate/test/launch the flight system.* Prime contractor for vehicle development *Background information derived from MCO Mishap Investigation Board Phase 1 Report

Vehicle Positioning / Trajectory Process Mission critical process for ensuring vehicle is aligned properly for orbit insertion Angular Momentum Desaturation (AMD) process utilizes thruster firings to keep spacecraft within operational range AMD Event Occurs Vehicle Trajectory Modeling Small Forces Processing Data AMD File

Project Timeline Dec. 11, 1998 Dec. 1998 – April 1999 April 1999 – Sept. 1999 Sept. 23, 1999 Sept. 29, 1999 Vehicle Launch Vehicle Modeling using informal AMD timing (via email) Vehicle Modeling using AMD file Loss of Vehicle Initial Root Cause Discovered Began to notice discrepancies in data Errors in format of file prevented use

Direct Root Cause

Root Cause* AMD Event Occurs Vehicle Trajectory Modeling Small Forces Processing Data AMD File Units = Newtons Units = lbf-s *Background information derived from MCO Mishap Investigation Board Phase 1 Report

Root Cause* - Consequence Result was a small error build up Vehicle entered the atmosphere at a periapsis of 57km Lowest projected by model using the fault data was 110km Lowest survivable periapsis: 80km Figure 4 form MCO Mishap Investigation Board Phase 1 Report * *Background information derived from MCO Mishap Investigation Board Phase 1 Report

Root Cause Analysis

Root Cause Analysis Why did unit conversion issue cause mission failure? Conversion issue not found during validation testing. Why? Failure in program validation process. Failure in developer quality process. Operations processed without formal AMD data. Why? Failure in project schedule and risk management. Operations noticed small inconsistencies throughout mission, but did not formally raise issue. Why? Failure in project planning for transition to operations (lack of training).

Problem 1 (P1) Failure in program validation process. System integration testing failed to validate that the interface of the AMD file was satisfied correctly.

Problem 2 (P2) Failure in developer quality process. Developer had a clear specification that indicated the units required for the AMD file. Quality process should have enforced some sort of review that would catch something as critical as the requirements of the interface.

Problem 3 (P3) Failure in project schedule and risk management. Project management attempted to mitigate the late schedule of the developer providing an in spec AMD file with a manual interaction. Given the criticality of this particular system function, it is not clear that the risk was properly quantified. Mitigation plan not thorough enough to require validation of AMD interface upon receipt of late system function. Contributing factor to P1.

Problem 4 (P4) Failure in project planning for transition to operations (lack of training). Operations team responsible for utilizing AMD interface was not part of original program development Thorough background training on the specifications of the system was not provided This lack of background knowledge contributed to the issue of operations noticing minor inconsistencies in the data without realizing the larger consequence to the system

References

References Mars Climate Orbiter Mishap Investigation Report – Phase 1 Report: Nov. 10, 1999; Stephenson, Mulville, Bauer, etc. [ftp://ftp.hq.nasa.gov/pub/pao/reports/1999/MCO_report.pdf] Slide 4,5,8 – JPL Logo - http://www.jpl.nasa.gov/ Slide 4,5,8,12,14,15 – Lockheed Martin Logo - http://www.lockheedmartin.com/ Slide 4,11,14,15 – Mars Surveyor Logo http://mars.jpl.nasa.gov/msp98/gif/m98patch.gif Slide 5, 8 – MCO Picture http://www.jpl.nasa.gov/jplhistory/the90/images/climate-orbiter- browse.jpg