Deployment model for Control Centre operating heterogenous missions
Programme
GSTP
Programme Reference
GT17-419GD
Prime Contractor
SPACEBEL SA.
Start Date
End Date
Status
Closed
Country
Belgium
Objectives
;;
The objective of the activity is the development and deployment model for efficient handling of control centre installations. It will address heterogenous missions including validation of migration of existing missions using the specified model.
;
;
Description
;;
The number of missions to be launched is expected to increase in the coming years. The current development (engineering) and deployment (operations) concept for SCOS-2000 based Mission Control Systems are considered suboptimal for such a high number of missions. The rise of the Software-as-a-Service (SaaS) principle and Cloud-based architecture offers new opportunities to streamline this model into a scalable architecture where only the aspects which are truly mission specific are handled at the mission level, while sharing resources and systems to achieve economy of scale. The new development and deployment model needs to:
-
- Support a clear separation between common and (mission) specific artefacts for mission control applications;
- Enable a drastic reduction in the time and effort currently required to integrate and validate ground systems in preparation to mission operations;
- Provide load balancing and resource scalability for missions under routine allowing for sharing of common services while providing guaranteed resources to supporting critical operations (like LEOPs),
- Provide suitable level of availability and robustness in case of failures, while consolidating to avoid unnecessary duplication of systems to maintain.
- Provide a system maintenance and evolution concept allowing automation of software release activities.
- Cope with mission customizations of deployments and configurations in an efficient way.
- Ease the migration of existing flying missions using S2K based MCS to the new shared infrastructure.
;
This activity encompasses the following tasks:
-
- Analyse the mission requirements for the future Copernicus and EO missions and identify an optimal control centre infrastructure deployment taking into account the issues listed above;
- Select a tool chain that best fits with the envisaged deployment and instantiate the deployment model to this specific infrastructure in a technical architecture document;
- Create a demonstration system capable of demonstrating scalability to add missions ?seamlessly?;
- Demonstrate the suitability of the demo-system by adding a flying Copernicus mission including migration of operational artefacts based on EGOS-CC (i.e. data definitions and operational data archive);
- Demonstrate the capabilities of the deployed system to support critical LEOP operations. This can be done either by shadowing a real LEOP (for monitoring only) or via a simulated LEOP using Operational Simulators for a selected Copernicus mission;
- Demonstration of availability and robustness of system in case of system failures.
;
;
Application Domain
GEN-Generic Technologies
Technology Domain
9-Mission Operation and Ground Data Systems
Competence Domain
8-Ground Systems and Mission Operations
Initial TRL
TRL 4
Target TRL
TRL 8
Achieved TRL
TRL 7
Public Document
Final Presentation