WP:3 – Software platform (TNO)

The focus of wp:3 is to implement and manage the multi-model infrastructure and design and build software tools for linking different models. Therefore, the main theme of this work package is doing. For this work package, it is important to mention that a functional prototype already exists, developed within the Mondaine project. doen. Voor dit werkpakket is het belangrijk om te vermelden dat functioneel prototype reeds bestaat, ontwikkeld binnen de Mondaine project.


There are two main outcomes of this work package:

wp:3:r:8 Design of the Multi-model Infrastructure

The multi-model infrastructure is a software service that enables model interaction. It is model agnostic, scalable, and does not bottleneck the performance of the multi-models that use it. This software infrastructure is both publicly available with the lowest possible barrier to participation and can be deployed in a closed environment under own management by stakeholders.

wp:3:r:9 Model Coupling

Model Linking is a piece of software that enables specific modeling tools and models to send and receive messages over the multi-model infrastructure. This software is independent of the content of the messages and serves as a "plug" between the model and the platform. Model coupling is by definition model and modeling tool-specific and must be built individually for each model.


Success Indicators

The success of platform infrastructure can be measured by the speed and number of messages that can be exchanged, the complexity of management, and the ease of use by parties outside the consortium. The number of realized model connections is the most important metric of the Model Coupling.


Information Modeling – TNO, TU Delft

During this activity, the requirements and needs during the participatory modeling session in wp:2 are retrieved, to gain insights into the information to be exchanged between the models. Use is made of the energy modeling language ESDL, to assess whether this should be expanded based on the new requirements and needs.

Software architecture design – TNO, Kalavasta, Quintel, Quo Mare, TU Delft

During this activity, the requirements and needs during the participatory modeling session in wp:2 are retrieved and an architecture that is as generic, robust, scalable, and extensible as possible is designed. Hardware platform choices are also made, as are the processes for setting up, operating, and management of the multi-model infrastructure.

Realization of multi-model orchestration – TNO, TU Delft

During this activity, the orchestration mechanism is designed and built, which is necessary for coordinating the model interaction.

Implementation of the multi-model infrastructure software – TNO, TU Delft

During this activity, the design is realized in an agile way, in iterative steps where each time a working system is delivered, after which the users can test and give feedback. agile7 manier gerealiseerd, in iteratieve stappen waar telkens een werkend systeem opgeleverd wordt, waarna de gebruikers kunnen testen en feedback kunnen geven.

Designing and realizing generic model links – TNO, TU Delft

During this activity, generic model links are designed and developed.

Realize specific model links – TNO, DNVGL, Kalavasta, Quo Mare, Quintel, TU Delft, (the model owners are in the lead for their model)

During this activity, the specific model links are realized, using the generic model link from the previous activity.