EDS-OML

Description

Welcome to our solution designed to streamline and standardize the use of Electronic Data Sheets (EDS) in the space industry. Our project focuses on enhancing the efficiency and accuracy of spacecraft design and integration by leveraging the power of EDS.

Key Features

• Standardized Data Sheets: Implement a unified format for EDS, ensuring consistency and clarity across different systems and components.
• Automated Documentation: Facilitate the automatic generation of engineering artifacts from EDS, significantly reducing manual effort and the potential for human error.
• Integration with Existing Systems: Seamlessly integrate with current spacecraft design and development processes, supporting both SOIS (Spacecraft Onboard Interface Services) and SAVOIR (Space Avionics Open Interface Architecture) standards.
• Compiler Applications: Develop tools to interpret EDS and automatically generate corresponding engineering outputs, enhancing the design lifecycle of space missions.

Background

The project was initiated to address the challenges faced in the space industry due to the lack of standardized documentation. By adopting a digital, machine-readable format for EDS, our project aims to significantly reduce errors and inefficiencies in spacecraft design and integration.

Reference

To develop our project, we utilized the Recommendation for Space Data System Standards: Recommended Standard for Spacecraft Onboard Interface Services—XML Specification for Electronic Data Sheets authored by the Consultative Committee for Space Data Systems (CCSDS).

Getting Start

This project uses Ontological Modeling Language (OML) developed by the Jet Propulsion Laboratory (JPL), and provided by the openCAESAR project.

Requirement

Java : 17 Gradle : 7.4.2 or +

Installation

git clone https://github.com/SophieCurinier/EncoreToOML-seed
cd EncoreToOML-seed/oml-eds
./gradlew build

Functionality

Task to convert the OML catalog to OWL catalog

./gradlew omlToOwl

Task to generate documentation for the OWL catalog

./gradlew generateDocs

Task to run a set of SPARQL queries on a Fuseki dataset endpoint

./gradlew owlQuery

• Component-Interface query: Component-Interface query retrieves information about components and their associated interfaces. It extracts the ID and name of each component, along with the IDs and names of interfaces that are required, declared, and provided by these components.

• Component set query: Component Set query extracts the identifiers and names of component sets and their respective components, highlighting the structure and organization of components within the system. Useful for visualizing the modular architecture of components in the datasheet.

• Device-Metadata query: Device-Metadata query identifies each device's ID and name along with the IDs and names of associated metadata. It helps in understanding the metadata attributes specific to each device, crucial for device configuration and management.

• Interfaces query: Interface query retries information about query and their associated command, generic type and set.It extract the ID and name of each component for each of them.

Visualization

We use Eclipse Sirius to do the visualisation part of our model.

Demonstration

This is a video

Documentation

In this document, you will find the purpose on our project, its challenges and all the doucmentation about it.

Contact

• Swendart : Sophie Curinier
• CharlesdeMalefette : Charles de Malefette