Glossary
This glossary provides definitions for key terms and concepts used in the DeltaTwin® Service.
| Concept | Description |
|---|---|
| Artifact | An Artifact is a DeltaTwin® special output that can be published or reused by the user. It is documented with a list of metadata indicating its characteristics and generation context. |
| DeltaTwin® component | A project definition in DeltaTwin® environment, referencing or embedding the needed inputs and runnable models to produce the expected results (outputs). DeltaTwin® component can be composed to build more complex systems and generate digital twin. It is similar to a project on Gitlab and is represented by a set of files and directories. |
| Digital Twin | A digital twin is a virtual and dynamic digital representation of a physical system or a set of physical interacting systems. It is created using computer models and regularly updated data collection. The physical systems can be various : natural phenomenon, a manufacturing process or an object. The digital twins enable to analyse, simulate, predict and monitor physical systems. |
| DeltaTwin® Service | It allows registered users to access to existing and freely available components, run them in a cloud infrastructure and publish the results they generate. |
| Drive (module) | The Drive module (DeltaTwin® Drive module) brings together a set of functionnalities that enables to manage all user data :
|
| Input | Any data that an user can provide to parametrize a DeltaTwin® before running it. Inputs might reference resources. |
| Initial resources | Data referenced by the process and that need to be downloaded before or during the process execution. exemple : reference to a specific DEM. |
| Job runner | A process execution, started for instance manually or by a specific trigger, which is stopped when its activity is completed. Its lifecycle is different from the daemon runner, not intended to stay in running mode forever. See also : Job (computing) |
| Model | A model is a ready-to-use software function enabling to transform data following an abstract representation of a system, a concept or natural phenomenon. This software implements the numerical translation of this theorical concept. |
| Output | All the data generated by the DeltaTwin® execution. |
| Resource | Numerical data that represents the information to be manipulated as input of the processing model. Resources are usually stored into the “resources” folder of the DeltaTwin®. |
| Run | An execution of a DeltaTwin®workflow. |
| Run (module) | The Run module (DeltaTwin® Run module) brings together a set of functionnalities that enables to design a DeltaTwin® and execute it. The Run functionnalities are expected to work remotely or locally |
| Source | Source code files used to build the process. When available, these files are stored into the “sources” folder of the DeltaTwin®. |
| Starter Kit | Set of read-only DeltaTwin® components that serve as samples for quick on-boarding: user can consult and execute them without modification. These DeltaTwin® components can be cloned by user and re-used to build more complex DeltaTwin® in the future. |
| Studio (module) | The Studio is the Web Graphical User Interface (GUI) of the DeltaTwin® Service, proposed to the users to view, configure, create or modify DeltaTwin® component (in particular for editing workflows, integrating models and compose DeltaTwin® components). |
| Workflow | An orchestrated flow of processes. See also Workflow (Wikipedia). |