Periodic Reporting for period 1 - DOMINO-E (Earth Observation Multi-mission federation layer)
Période du rapport: 2022-11-01 au 2023-10-31
The DOMINO-E project, proposed by a consortium of European organisations, including scientific institutes and SMEs and led by Airbus Defence and Space, aims at solving the key challenge of availability and reactivity of earth observations from space, by enabling multi-mission accessibility on a scalable and automated way.
The implementation of a multi-mission/multi-sensor federation layer allows the end-user to address a variety of acquisition assets using scheduling and optimization algorithms. The orchestration between the users’ patrimonial missions and the third party missions is based on reactivity, persistence, precision and costs criteria, while user experience is improved thanks to cognitive assistants.
The challenge is to overcome the current technological, architectural and economical roadblocks of existing mission ground segments: mono-mission architectures, un-harmonized interfaces between different ground segments, inexistent or crude multi-mission collaborative coverage and dispatch services.
DOMINO-E consists of designing, analysing and modelling the multi-mission federation layer based on users’ requirements and is supported by demonstrations of added value services. A market analysis is performed to assess the commercial perspectives of multi-mission federation approach in terms of client acceptance in sharing assets, industry’s make or buy strategy and SME capability to build catalogues of multi-mission services.
This innovative federation layer supports the change of space industry paradigm from instrumental push to end-client vertical needs pull and allows the EU space industry to embrace the emerging data driven space market. In such, DOMINO-E contributes to European non-dependence for the development of Earth-observation technologies and foster European competitiveness by supporting SMEs in developing multi-mission services agnostic to the end-to-end or ground segment systems integrators.
The implementation of a multi-mission/multi-sensor federation layer allows the end-user to address a variety of acquisition assets using scheduling and optimization algorithms. The orchestration between the users’ patrimonial missions and the third party missions is based on reactivity, persistence, precision and costs criteria, while user experience is improved thanks to cognitive assistants.
The challenge is to overcome the current technological, architectural and economical roadblocks of existing mission ground segments: mono-mission architectures, un-harmonized interfaces between different ground segments, inexistent or crude multi-mission collaborative coverage and dispatch services.
DOMINO-E consists of designing, analysing and modelling the multi-mission federation layer based on users’ requirements and is supported by demonstrations of added value services. A market analysis is performed to assess the commercial perspectives of multi-mission federation approach in terms of client acceptance in sharing assets, industry’s make or buy strategy and SME capability to build catalogues of multi-mission services.
This innovative federation layer supports the change of space industry paradigm from instrumental push to end-client vertical needs pull and allows the EU space industry to embrace the emerging data driven space market. In such, DOMINO-E contributes to European non-dependence for the development of Earth-observation technologies and foster European competitiveness by supporting SMEs in developing multi-mission services agnostic to the end-to-end or ground segment systems integrators.
Status on 30/10/2023
Work Package 2 (Leader Airbus)
• User requirements (UR): The core of the UR was obtained by discussing with current operators on systems, i.e. THEOS2. We had several internal workshops with our vendors (regional and KAM) and took the opportunities of other projects to discuss with partners, institutions and prospects (CNES and TAS during DOMINO-X; ESA during GS Copernicus Reference System, prospects at the conferences listed in the WP8 results).
• Use cases (UC). The uses cases were discussed during workshop with Airbus operators and Engineering teams, consortium partners and aligned with current UC for identified for optical systems.
• system design & architectural guidance and interphases rules. The consortium took the opportunity of the parallel activities performed in DOMINO-X to align DOMINO-E design and interphases.
Work Package 3 (Leader Cap Gemini)
• ADS-FR- Design and interface requirement. Providing feedback on the Implementation and Verification Plan.
• ONERA - Preliminary design and assessment of mathematical models for communication booking. Providing feedback on the Implementation and Verification Plan and Design and interface requirement. State-of-the-art concerning the covering algorithms. Support for the specification of the coverage service. Algorithmic workshops with Airbus.
• CG - Writing of the Implementation and Verification Plan. Providing feedback on the Design and interface requirement. Iterating upon the design from WP3100.
Work Package 4 (Leader ITTI)
• ADS-FR- Writing of the Design and interface requirement for communication booking. Providing feedback on the Implementation and Verification Plan.
• ONERA - Analysis of AWS billing method. Discussion with ADS about the design and the semantics of data structures. Review of the design and implementation and validation plan document. Development of a mono satellite model reflecting the benefits and cost associated to making observations and booking communications. Development of multi-satellite models based on satellite communication needs, respectively in terms of number of contacts and contact duration, provided by the missions. Development and test of first algorithmic ideas. Test of OREKIT usability for SCRMS.
• ITTI - Writing of the Implementation and Verification Plan. Providing feedback on the Design and interface requirement for communication booking. Iterating upon the design from WP4100.
Work Package 5 (Leader TILDE)
• Analyzing VAS Use Cases and formulating corresponding system designs and requirements (ADS-FR, TILDE)
• Reviewing and coordinating the established requirements. A total of 35 requirements have been specified (ADS-FR, TILDE)
• Defining workflows and internal interfaces (ADS-FR, TILDE)
• Specifying the implementation process and methodologies for VAS development. The chosen approach is Agile development, incorporating continuous integration, deployment, and testing (TILDE)
• Specifying the processes and methodologies for testing and validating the VAS. This encompasses unit testing, integration testing, security testing, automatic quality evaluation, and user acceptance testing (TILDE)
• Defining VAS test cases. Test cases have been designed for all specified requirements (TILDE).
• Defining risk management procedures (TILDE)
• Identifying main risks and outlining their corresponding mitigation steps (TILDE)
• Allocating resources, including development teams, testing teams, and necessary infrastructure (TILDE)
• Establishing development and testing infrastructure (TILDE)
Work Package 2 (Leader Airbus)
• User requirements (UR): The core of the UR was obtained by discussing with current operators on systems, i.e. THEOS2. We had several internal workshops with our vendors (regional and KAM) and took the opportunities of other projects to discuss with partners, institutions and prospects (CNES and TAS during DOMINO-X; ESA during GS Copernicus Reference System, prospects at the conferences listed in the WP8 results).
• Use cases (UC). The uses cases were discussed during workshop with Airbus operators and Engineering teams, consortium partners and aligned with current UC for identified for optical systems.
• system design & architectural guidance and interphases rules. The consortium took the opportunity of the parallel activities performed in DOMINO-X to align DOMINO-E design and interphases.
Work Package 3 (Leader Cap Gemini)
• ADS-FR- Design and interface requirement. Providing feedback on the Implementation and Verification Plan.
• ONERA - Preliminary design and assessment of mathematical models for communication booking. Providing feedback on the Implementation and Verification Plan and Design and interface requirement. State-of-the-art concerning the covering algorithms. Support for the specification of the coverage service. Algorithmic workshops with Airbus.
• CG - Writing of the Implementation and Verification Plan. Providing feedback on the Design and interface requirement. Iterating upon the design from WP3100.
Work Package 4 (Leader ITTI)
• ADS-FR- Writing of the Design and interface requirement for communication booking. Providing feedback on the Implementation and Verification Plan.
• ONERA - Analysis of AWS billing method. Discussion with ADS about the design and the semantics of data structures. Review of the design and implementation and validation plan document. Development of a mono satellite model reflecting the benefits and cost associated to making observations and booking communications. Development of multi-satellite models based on satellite communication needs, respectively in terms of number of contacts and contact duration, provided by the missions. Development and test of first algorithmic ideas. Test of OREKIT usability for SCRMS.
• ITTI - Writing of the Implementation and Verification Plan. Providing feedback on the Design and interface requirement for communication booking. Iterating upon the design from WP4100.
Work Package 5 (Leader TILDE)
• Analyzing VAS Use Cases and formulating corresponding system designs and requirements (ADS-FR, TILDE)
• Reviewing and coordinating the established requirements. A total of 35 requirements have been specified (ADS-FR, TILDE)
• Defining workflows and internal interfaces (ADS-FR, TILDE)
• Specifying the implementation process and methodologies for VAS development. The chosen approach is Agile development, incorporating continuous integration, deployment, and testing (TILDE)
• Specifying the processes and methodologies for testing and validating the VAS. This encompasses unit testing, integration testing, security testing, automatic quality evaluation, and user acceptance testing (TILDE)
• Defining VAS test cases. Test cases have been designed for all specified requirements (TILDE).
• Defining risk management procedures (TILDE)
• Identifying main risks and outlining their corresponding mitigation steps (TILDE)
• Allocating resources, including development teams, testing teams, and necessary infrastructure (TILDE)
• Establishing development and testing infrastructure (TILDE)