Skip to content

Latest commit

 

History

History
57 lines (40 loc) · 2.13 KB

about_digital_twins.rst

File metadata and controls

57 lines (40 loc) · 2.13 KB

Digital Twins

A digital twin is a virtual representation of a real life being - a physical asset like a wind turbine or car - or even a human.

There are three reasons why you might want to create a digital twin:
  • Monitoring
  • Prediction
  • Optimisation

On its own, a digital twin can be quite useful. For example, a twin might embody an AI-based analysis to predict power output of a turbine.

A digital twin consists of some kind of analysis or processing task, which could be run many times per second, or daily, down to occasionally or sometimes only once (the same as a "normal" analysis).

A digital twin consists of some kind of analysis or processing task, which could be run many times per second, or daily, down to occasionally or sometimes only once (the same as a "normal" analysis).

Coupling digital twins is generally even more useful. You might wish to couple your turbine twin with a representation of the local power grid, and a representation of a factory building to determine power demand... enabling you to optimise your factory plant for lowest energy cost whilst intelligently selling surplus power to the grid.

A hierarchy of digital twins. Each blue circle represents a twin, coupled to its neighbours. Yellow nodes are where schema are used to connect twins.

A hierarchy of digital twins. Each blue circle represents a twin, coupled to its neighbours. Yellow nodes are where schema are used to connect twins.

Gemini Principles

The Gemini Principles have been derived by the Centre for Digital Built Britain (CDBB). We strongly recommend you give them a read if embarking on a digital twins project.

The aim of twined is to enable the following principles. In particular:

  1. Openness (open-source project to create schema for twins that can be run anywhere, anywhen)
  2. Federation (encouraging a standardised way of connecting twins together)
  3. Security (making sure schemas and data can be read safely)
  4. Public Good (see our nano-rant about climate change in reason_for_being)