Engineering topics

Faris, Grant B.

Publications and source records attributed to Faris, Grant B..

6 records

NASA NTRS2018

Preparing to Assure Mission Success

Space flight missions are inherently risky. The mission operations assurance discipline grew out of strategies to control error and evolved into what today is an independent technical authority dedicated to achieving mission success. After the Mars Climate Orbiter loss, NASA made a set of recommendations for missions. Two of those recommendations led to the creation of today’s Mission Operations Assurance Manager role: (1) require an independent Mission Assurance representative during the operational phase of every flight project, and (2) require all flight projects to report and track post-launch anomalies. Since then, the MOAM role has been continually refined by lessons learned from its practice on more than 20 concurrent missions. The MOAM role requires significant operations experience as well as an additional set of skills. In the interests of developing a cadre of potential MOAMs, the MOAM training program was developed. It is a 14-unit set of presentations/discussions covering the 11 categories of MOAM tasks. It is offered to new MOAMs and interested systems engineers with an eye to preparing both types of personnel for present and future assignments, as well as building relationships among personnel of different organizations. MOAM training sessions include presentations on the various tools and processes employed by MOAMs, interspersed with mindset lessons illustrated via “war story” discussions of previous missions.

Bryant, Larry↗

NASA NTRS2012

Improving Operations: Metrics to Results

No abstract available

command file errors↗

NASA NTRS2012

Improving operations: Metrics to Results

As a result of the mission failure of the Mars Climate Orbiter (MCO) spacecraft in 1999, the Jet Propulsion Laboratory (JPL) initiated the development of a Mission Operations Assurance (MOA) program to be implemented across all flight projects managed by JPL. One of the initiatives undertaken in 2001 was the collection of data on command file errors occurring in the operational phase of the mission. This paper defines command file errors and how and where they occur in the operations process. It also describes the problem reporting system (PRS) in use for mission operations at JPL. We examine the recent modifications to the PRS that enable the collection of metrics, specifically on command file errors. This paper discusses what the data show us since metrics have been collected for the operational missions conducted by JPL. We examine the evolution of an operational working group initiative to evaluate proximate, contributing, and root causes for the errors. As part of this discussion we see what the metrics have indicated over a decade. At the macro level, we can say that the aggregate command file error rate has been cut to roughly one third of the initial 2001 level by the end of 2011. Additionally, we explore efficient and innovative means to continually integrate the findings and recommendations from the working group back into the flight operations environment.

command file errors↗

NASA NTRS2011

Risk Balance: A Key Tool for Mission Operations Assurance

The Mission Operations Assurance (MOA) discipline actively participates as a project member to achieve their common objective of full mission success while also providing an independent risk assessment to the Project Manager and Office of Safety and Mission Success staff. The cornerstone element of MOA is the independent assessment of the risks the project faces in executing its mission. Especially as the project approaches critical mission events, it becomes imperative to clearly identify and assess the risks the project faces. Quite often there are competing options for the project to select from in deciding how to execute the event. An example includes choices between proven but aging hardware components and unused but unproven components. Timing of the event with respect to visual or telecommunications visibility can be a consideration in the case of Earth reentry or hazardous maneuver events. It is in such situations that MOA is called upon for a risk balance assessment or risk trade study to support their recommendation to the Project Manager for a specific option to select. In the following paragraphs we consider two such assessments, one for the Stardust capsule Earth return and the other for the choice of telecommunications system configuration for the EPOXI flyby of the comet Hartley 2. We discuss the development of the trade space for each project's scenario and characterize the risks of each possible option. The risk characterization we consider includes a determination of the severity or consequence of each risk if realized and the likelihood of its occurrence. We then examine the assessment process to arrive at a MOA recommendation. Finally we review each flight project's decision process and the outcome of their decisions.

operations↗

NASA NTRS2010

We're Here to Help You

Air Force lore tells us that the two biggest lies you will ever hear on the tarmac are when the Inspector General steps off the plane and says to the Wing Commander, "We're here to help you," and the Wing Commander replies, "We're glad to see you." Not too surprisingly, a similar relationship is often perceived between a project manager and the mission assurance representative (especially for operations). This perception intensifies as budgets shrink and missions shorten, after all, where is the value added? That is the question we will examine for three small, short projects: Phoenix, WISE, and Grail (which is yet to launch). All have limited resources to devote to "niceties" and a very short mission to reap the benefits for their operations. We will examine how mission operations assurance evolved for each project, what worked well, what could have been improved, and how these lessons can be applied to ensure mission operations assurance is a value added function for Grail and future small missions.

Topex↗

NASA NTRS2010

Stardust Blazes MOA Trail

Mission Operations Assurance (MOA) started at the Jet Propulsion Laboratory (JPL) with the Magellan and Galileo missions of the late 80's. It continued to develop and received a significant impetus with the failures of two successive missions to Mars in the late 90's. MOA continued to evolve with each successive project at JPL achieving its current maturity with the Stardust sample return to Earth.

operations assurance mission↗