Mission interactive scenarion studio for autonomous spacecraft

We propose building a Studio enabling the use of diverse existing mission activity and scenario patterns, the creation of new ones, and the modeling of their effects using existing modeling tools. The core of the Studio is a component-based Type Library, which captures years of mission adaptation patterns in various forms. The Studio works as a content server to capture the developed adaptation knowledge for reuse and provides bridging into different mission uplink implementations, including the Mission Data System [l] (MDS) state/goal machinery. Various activities can be coordinated, controlled, and reused through the Studio's component interface to establish and model a mission scenario. A special component Factory mechanism will be in place to facilitate the adaptation of projects into the Studio. The architecture of the Studio reflects and enforces a division of knowledge and actions into three parts: Model, Controller, Viewer. The Model contains information about (a proposed version of) the spacecraft and mission. The Controller contains logic for constructing scenarios of mission activities. The information in the Model and Controller is principally in the form of reusable patterns. A Viewer can be a simple or complex software system. For example, Apgen [2,3] is one possible viewer, MDS is another. A 3-tiered infrastructure is used for the Studio, reflecting the Model, Controller, Viewer architecture [4,5]. The Studio is useful in pre-phase A of a project by enabling spacecraft design options to be played against desired mission scenarios. In later design phases of a project, the construction and modeling of more detailed scenarios is supported by the Studio.