Digital Twin under the hood

From source model to Digital twin

Just a 3D model? That can’t be hard to make? It has taken tens of thousands of hours of R&D to master 3D modelling, now we can do it in just couple of hours. When you start to build #Digitaltwin or #Smartfactory solutions with visibility, safety and quality in mind one must master at least aspects mentioned under to make scalable end results with profit.

 

  1. The source model! Usually a three-dimensional design template or a point cloud, is fed into an automated process, which creates a polygon "mesh" template that is still too heavy in detail for rendering and WebGL (read; web browser) purposes. In other words, the model must be optimized by reducing polygons.  If this is handmade the process is far too slow and expensive. Also mathematically automated algorithm-based solution is not quite simplistic as one might think, the challenge is to get just the right precision in the conversion which again requires strong experience in finding and using the right parameters.

 

  1. Next, the model is taken to the next pipeline we have developed. This pipeline is overflowing with technical terms loved by our coders but simply the output as nicely rotating Digital Twin with built-in three-axis geo-referencing and KKS / SAP / data points at their correct locations.

 

  1. The last major step is to connect the data to your 3D digital copy. Here we use our experience with different interfaces, ready-made APIs, IoT platforms, automation, and so on. On the most demanding cases we have connected dozens of data sources to the browser rotating model. For this reason, there is no point getting fixated on one platform or technology, this will stop your development very efficiently.

 

Me, Sami, Antti and the rest of our team will be happy to talk more about how open source and transparent collaboration can deliver real benefits and avoid the most expensive missteps at the same time.

 

#pioneers for 6 years