A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost-effective set of multimission MOS products and services.

[1]  Seung H. Chung,et al.  Timeline-Based Mission Operations Architecture: An Overview , 2012 .

[2]  Christopher Delp,et al.  Use of Operational Scenarios in Architecting MOS 2.0 , 2010 .

[3]  Duane Bindschadler,et al.  MOS 2.0: The Next Generation in Mission Operations Systems , 2010 .

[4]  Steve Chien,et al.  Extending the Representational Power of Model- Based Systems using Generalized Timelines , 2001 .

[5]  Christopher L. Delp,et al.  Principles to Products: Toward Realizing MOS 2.0 , 2012 .

[6]  Christopher Alexander,et al.  The Timeless Way of Building , 1979 .

[7]  Murray Silverstein,et al.  A Pattern Language , 1977 .

[8]  William B. Green Multimission ground data system support of NASA'S planetary program , 1995 .

[9]  Barrie Sosinsky Defining Cloud Computing , 2011 .

[10]  Gregor Hohpe,et al.  Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions , 2003 .

[11]  Mary Shaw,et al.  An Introduction to Software Architecture , 1993, Advances in Software Engineering and Knowledge Engineering.

[12]  Maddalena Jackson,et al.  MOS 2.0 - modeling the next revolutionary Mission Operations System , 2011, 2011 Aerospace Conference.

[13]  Michel D. Ingham,et al.  Generating requirements for complex embedded systems using State Analysis , 2006 .

[14]  Rina Dechter,et al.  Temporal Constraint Networks , 1989, Artif. Intell..

[15]  Bradley R. Schmerl,et al.  Evolution styles: Foundations and tool support for software architecture evolution , 2009, 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture.

[16]  Jeffrey M. Barnes NASA's advanced multimission operations system: a case study in software architecture evolution , 2012, QoSA '12.

[17]  Tung Bui,et al.  The Evolvable Advanced MultiMission Operations System (AMMOS): Making Systems Interoperable , 2010 .