The Digital Twin is a virtual representation of system that serves as the indistinguishable digital counterpart of it for practical purposes such as system simulation. In the scope of the current toolbox, a digital twin can be used to either simulate an existing trained hybrid model, or to implement from scratch a custom one without hybrid models.

UI Layout

The UI is divided in 3 main areas,

Execution console

Contains 4 buttons to trigger/control the execution of the digital twin simulations and a log/report console.


Sim / Opt

To start digital twin simulation/optimization. When clicked a pop up will appear requesting user which action to perform,

  • Simulation

  • Optimization


Additionally, only for digital twins created from hybrid models, Use DLL can be checked (unchecked by default).

When doing so, digital twin will use the same code as it will be available during the [Export](TO BE SET !!!) instead of the self-managed internal logic. This allows users to reproduce same exact behavior that will be expected when consuming exported code somewhere else.


Stops ongoing simulation.


This button is only enabled when there is an ongoing simulation being carried out.


After Stop button is triggered, in some occasion, it might still take some seconds to stop. That is because it will wait until the ongoing simulation finishes executing the EvaluateStep method it might be evaluating.


Resets last ongoing/stopped simulation so a new one can be carried out. This avoids accidentally starting a new simulation.


This button is only enabled after an ongoing simulation has been stopped or completely simulated.


Generates a report within the Report tab of last successful performed simulations.


This button is only enabled if last ongoing simulation has finished successfully (100%). If stopping simulation before completion, report will not be available for generation and simulation will have to be performed again.


The logger window, outputs messages regarding current ongoing simulation; from simple simulation statuses (e.g., Started, Stopped…) to user custom logs generated from within the custom code (e.g., using the “WriteLine” method).

Setup / Configuration

The setup/configuration of the digital twin differs depending if it was created from an existing trained hybrid model or if it was created from scratch. Sections are differ as follow,

*1 Legacy


A Hybrid model,

  • has Inputs and Outputs

  • can be integrative or not

Because of that, only digital twins created from hybrid models have output variables which are handled directly by the digital twin engine. When needed, digital twins also handle the integration of those outputs properly in an automated manner when integration of outputs is enabled.


Digital Twins without hybrid models, don’t have Outputs per say, but one or multiple Simulated variables that can be treated as the equivalent process outputs.