The satellite database model formalizes the format of data exchanged between the satellite and the ground segment.
Too many formats coexist for describing the satellite database. Each program or working group chooses its own database modeler, its own packet interpreter… and fills all the gaps between tools – or during exchanges with other industrials – with transformation tools or even manual transformations. So why make yet another database modeler with its own format for the CNES?
The goal of the DISCO database modeler is not to define a new format, but to support the best of each format, to bring them all and bind them. With a cocktail of EMF-based technologies, DISCO currently supports compatibility with 3 different formats, in order to fill the gap between other tools which each use a specific format. Therefore DISCO becomes the central hub of the toolchain.
The performance expectations are satisfied and DISCO is now actively used for cross-formats conversion needs – it has proven more maintainable than the dedicated transformation tool it displaced. It is still not operational as an editor only because the HMI development is just starting in 2020.