MBSE is already common practice in much of the space industry, supporting the design, assembly, integration, and testing of space systems. Typically, the reliance on MBSE stops once the system leaves the supplier. Once phase C/D is over and the system is delivered to the client/operator, all the information and knowledge encoded in the models are usually written down in text-based design documents, user manuals, and operational procedures. The client/operator must then start from the information/knowledge in this format, to configure their systems (planning, data distribution, mission control, other), and to build all the supporting information and procedures needed by the Mission Operations Centre (MOC) to operate the space system. There is a clear digital divide at the end of phase C/D, and manifest room for optimization of the information/knowledge exchange interface between the design and operations teams. The objective of the activity here proposed is to understand how to best bridge this divide, and implement a proof of concept, demonstrating how existing models and MBSE standards and tools can best be tailored and/or extended to generate models for operations. Particular focus will be given to models for planning (e.g. DDL, PDDL, other), models for execution (e.g. operational procedures), and models for FDIR. Demonstration of effective digital continuity between design and operations has the potential to reduce the cost of operations. This will be achieved by speeding up training of operations personnel, making configuration of operational systems faster, and by guaranteeing consistency, at all times, between the models used for design and for operations.
