Submission ID 92161

Session Title DA - Digital Twinning for Transportation Assets
Title Is There Value In A Digital Twin?
Abstract

The concept of creating a Digital Twin isn’t new. For years engineers have attempted to represent ideas in different ways including watercolor sketches, plan and cross section, and even miniature models. While these are all used to try to communicate how a design may fit into the real world, they represent limited dimensions of the real world. As there are more technologies available that collect and aggregate data, the engineering industry has shifted towards the concept and implementation of BIM and Digital Twins.

Digital Twin aims to be the virtual representation of a real-life system. If something in the real world can be measured, it can be incorporated into the Digital Twin model. The more data that is being captured, the more robust and accurate this virtual model will be. With a seemingly infinite amount of input data that can be used for a Digital Twin, at what point can we maximize the value of a Digital Twin for ourselves as designers, for clients, and for the public. By understanding the proper cost (dollar amount of data, time and resource spent to create model, etc.) we can effectively advance our communication and lead the way in how we engage on our projects.

This presentation will show how we can use the typical type of data available to us as designers to start creating a Digital Twin. This includes existing contours, aerial imagery, and existing buildings. And how we can use this data to inform us how the design may impact the real world. I will also explore some of lessons learned from past projects that brought more complications than value.

Presentation Description (max. 50 words) What is a Digital Twin and how do we utilize it for the benefit for ourselves as designers, for our clients, and for the public? Exploring both data requirements and lessons learned from previous projects.
Presenter / Author Information Billy Wong, Stantec Consulting Ltd.
x

Loading . . .
please wait . . . loading

Working...