Phoenix surface mission operations processes

Abstract

We present an overview of Phoenix Mars Scout Mission (Phoenix) surface operations process design with an emphasis on the science portion of the process. We describe the drivers and constraints on Phoenix operations and the resulting choices that the development team made to accommodate these constraints. The two most important drivers on Phoenix operations are the choice of orbiter relay only for data and the limited amount of data storage on the lander. These two combine to regulate the amount of data the spacecraft can collect, save, and transmit on any given sol. We discuss the interplay between the daily (tactical) and long-term/multiday (strategic) processes and finish with lessons learned for future mission operations design. Integration of mostly complete engineering requirements toward the front end of the tactical process, as well as the multiday nature of science acquisition, results in particular design decisions that have not been incorporated in previous ground operations planning. Copyright 2008 by the American Geophysical Union.