Reducing the cost of mission operations has necessitated a high level of automation both on spacecraft and ground systems. While automation on spacecraft is implemented during the design phase, ground system automation tends to be implemented during the prime mission operations phase. Experience has shown that this tendency for late automation development can be hindered by several factors: additional hardware and software resources may need to be procured; software must be developed and tested on a non-interference basis with primary operations with limited manpower; and established procedures may not be suited for automation requiring substantial rework. In this paper we will review the experience of successfully automating mission operations for seven on-orbit missions: the Compton Gamma Ray Observatory (CGRO), the Rossi X-Ray Timing Explorer (RXTE), the Advanced Composition Explorer (ACE), the Far Ultraviolet Spectroscopic Explorer (FUSE), Interplanetary Physics Laboratory (WIND), Polar Plasma Laboratory (POLAR), and the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE). We will provide lessons learned in areas such as: spacecraft recorder management, procedure development, lights out commanding from the ground system vs. stored command loads, spacecraft contingency response time, and ground station interfaces. Implementing automation strategies during the mission concept and spacecraft integration and test phase as the most efficient method will be discussed.
Managing the Implementation of Mission Operations Automation
AIAA SpaceOps Conference ; 2006 ; Rome, Italy
2006-01-01
Conference paper
No indication
English
Automation of ESOC Mission Operations
British Library Conference Proceedings | 2007
|Automation of ESOC Mission Operations
AIAA | 2007
|Automation of HST Mission Operations
British Library Conference Proceedings | 2012
|Automation of HST Mission Operations
AIAA | 2012
|Automation of ESOC Mission Operations
AIAA | 2006
|