What is a digital twin?

Published on 1月 31, 2020

Paolo Rinelli

Global Head of Product Management

The phrase “digital twin” has become ubiquitous in the field of transportation, but it has been applied so undiscriminatingly to so many different concepts that it is hard to know what people mean by it. I’ve seen “digital twin” used to refer to anything from an offline model to a 3D render, but neither of these can truly be considered a digital twin in any meaningful sense.

 

The concept of a digital twin is not new: virtual replicas first appeared in manufacturing to support performance optimization. The idea was to have a virtual representation of a manufactured product or production system and, crucially, to continuously feed the digital copy with new data in order to monitor, diagnose, and predict issues. These digital twins allowed manufacturers to reduce the time and costs associated with assembling, validating and maintaining factory production systems.

 

From this description we can identify the following core requirements for a digital twin:

 

  1. It must be fed sensor data continuously and in real time 
  2. It must update its state based on the data received from those sensors 
  3. It must be capable of predicting its future state

 

This implies that a simple 3D rendering of an object, or indeed of a city, cannot be considered a digital twin, because it is not updated with real-time data and therefore completely lacks understanding of how the current state will evolve based on those inputs. This at most can be classified as a 3D map, which may be useful for navigation, but not for management and decision support. In fact, although the phrase “digital twin” conjures up a very visual image, photorealism and 3D representation are not even requirements for a digital twin.

 

Additionally, the three core requirements mentioned above must be all present in every digital twin. For example, a mobility model built for a specific scenario, such as the afternoon rush hour of a typical weekday in say, Atlanta, fulfills only the third condition, but is not connected to real data or capable of automatically updating itself, so it is just a model, rather than a digital twin. Equally, a map or a 3D rendering of a city that shows the current traffic state is not capable (without an underlying model) of predicting its future state, so it’s just a situational awareness platform, not a digital twin.

 

However, if we look at the Aimsun portfolio of solutions, we can find a real digital twin, and in fact we’ve been creating digital twins since well before this concept even became common parlance in the field of transportation simulation: Aimsun Live. Aimsun Live is a decision support tool for transportation management that fulfills all the core requirements listed above:

 

  1. It receives continuous input data from permanent sensors installed in the field
  2. It uses these data to update the current traffic conditions and detect automatically non-recurrent situations
  3. It runs models to predict how the current traffic conditions will evolve in the next hour how they will evolve if there is an intervention, such as the deployment of a response plan

 

A digital twin is a valuable tool in the field of transportation management, but only if it is a true digital twin like Aimsun Live, not if it’s just perfunctorily labelled as such. To see some of the use cases for our digital twins, look here: www.aimsun.com/real-time-transportation-management/.

Aimsun
  • 有问题吗? 请联系我们。

    我们在这里提供帮助!

  • 有问题吗? 请联系我们。

    我们在这里提供帮助!

分享

引用Aimsun Next

Aimsun Next 20

Aimsun (2021). Aimsun Next 20 User’s Manual, Aimsun Next Version 20.0.3, Barcelona, Spain. Accessed on: May. 1, 2021. [In software].
Available: qthelp://aimsun.com.aimsun.20.0/doc/UsersManual/Intro.html


Aimsun Next 8.4

Aimsun (2021). Aimsun Next 8.4 User’s Manual, Aimsun Next Version 8.4.4, Barcelona, Spain. Accessed on: May. 1, 2021. [In software]. Available: qthelp://aimsun.com.aimsun.8.4/doc/UsersManual/Intro.html

Aimsun Next 20

@manual {​​​​​​​​AimsunManual,

title = {​​​​​​​​Aimsun Next 20 User’s Manual}​​​​​​​​,

author = {​​​​​​​​Aimsun}​​​​​​​​,

edition = {​​​​​​​​​​​​​​​Aimsun Next 20.0.3}​​​​​​​​​​​​​​​,

address = {​​​​​​​​​​​​​​​Barcelona, Spain}​​​​​​​​​​​​​​​,

year = {​​​​​​​​​​​​​​​2021. [In software]}​​​​​​​​​​​​​​​,

month = {​​​​​​​​​​​​​​​Accessed on: Month, Day, Year}​​​​​​​​​​​​​​​,

url = {​​​​​​​​​​​​​​​qthelp://aimsun.com.aimsun.20.0/doc/UsersManual/Intro.html}​​​​​​​​​​​​​​​,

}​​​​​​​​​​​​​​​


Aimsun Next 8.4

@manual {​​​​​​​​AimsunManual,

title = {​​​​​​​​Aimsun Next 8.4 User’s Manual}​​​​​​​​,

author = {​​​​​​​​Aimsun}​​​​​​​​,

edition = {​​​​​​​​​​​​​​​Aimsun Next 8.4.4}​​​​​​​​​​​​​​​,

address = {​​​​​​​​​​​​​​​Barcelona, Spain}​​​​​​​​​​​​​​​,

year = {​​​​​​​​​​​​​​​2021. [In software]}​​​​​​​​​​​​​​​,

month = {​​​​​​​​​​​​​​​Accessed on: Month, Day, Year}​​​​​​​​​​​​​​​,

url = {​​​​​​​​​​​​​​​qthelp://aimsun.com.aimsun.8.4/doc/UsersManual/Intro.html}​​​​​​​​​​​​​​​,

}​​​​​​​​​​​​​​​

Aimsun Next 20

TY – COMP

T1 – Aimsun Next 20 User’s Manual

A1 – Aimsun

ET – Aimsun Next Version 20.0.3

Y1 – 2021

Y2 – Accessed on: Month, Day, Year

CY – Barcelona, Spain

PB – Aimsun

UR – [In software]. Available: qthelp://aimsun.com.aimsun.20.0/doc/UsersManual/Intro.html


Aimsun Next 8.4

TY – COMP

T1 – Aimsun Next 8.4 User’s Manual

A1 – Aimsun

ET – Aimsun Next Version 8.4.4

Y1 – 2021

Y2 – Accessed on: Month, Day, Year

CY – Barcelona, Spain

PB – Aimsun

UR – [In software]. Available: qthelp://aimsun.com.aimsun.8.4/doc/UsersManual/Intro.html