Demonstrate, and validate on study cases, how digital engineering can improve exchange and exploitation of engineering data in space projects across disciplines, lifecycle phases, organisations and tools

 

Space Projects suffer from cumbersome and poor information sharing among disciplines, lifecycle phases and supply chain partners. This causes inefficiencies, costly mistakes and slippages of schedule. Interoperability among heterogeneous models is needed. The need is to inject the acquired knowledge into a sustainable quot;hubquot;-like eco-system, enabling reliable sharing and analysis capabilities for all engineering information needed by multiple stakeholders. This activity encompasses the following tasks:

1. Analyse the space system processes and capture the stakeholder needs into a concept of operations and user requirements

2. Conceive a long-term implementation strategy for sharing multi-disciplinary engineering data

3. Develop a semantic information model as a foundation for the hub, as well as an implementation approach

4. Define solutions to prototype the eco-system, based on recently completed developments in the areas of ground segment engineering, reliability analysis, requirements management, phase 0 concurrent design studies, spacecraft design. Analyse external developments for potential usefulness.

Develop and demonstrate in particular:

4.a Model Based Reliability Engineering, by developing a digital reference model for a space product that contains the reliability figures of merit for all relevant engineering disciplines

- Link/Develop existing digital model libraries/sources of component failure data

- Model reliability, fault tolerance and operational availability at system level

- Enable reliability-oriented system trade-offs

4.b Model Based Operations Engineering, by bridging the ground and space segment domains and developing a reference model in support of operations

- Link and/or develop data sources/models that support definition of the operations concept, capture operational rules and constraints and link operational teams/roles, processes and procedures to the system architecture

- Enable operations-oriented system trade-offs

5. Contribute towards a strategy report, including recommendations for extensions to previous developments/domain-specific modelling tools, standardization, processes, workflows, eco-system support, documentation, and training, with a focus on long-term, incremental, sustainable evolution

6. Produce a final report evaluating the work performed, as well as providing recommendations the next steps

;

Software shall be delivered under an ESA Software Community Licence, so that any individuals or entities within ESA Member States can access to it and can provide update to the community of users.

;