What is a Digital Twin and why is it important
We talk about Digital Twins, but what is it, and why is it beneficial? In this issue, I will explore this very question. Trying to explain this topic and how it all fits together. Additionally, just some news Twitter is getting rid of the Revue platform. This was kind of shocking to me, but it’s true. So I have moved over to the Substack platform. It’s quite an easy transition as there aren’t many subscribers yet. If you were subscribed, I’ll move you over.
What is a Digital Twin
A digital twin can mean different things to different people. For some, this concept is a 3D representation of the physical device. Understanding its size in a conceptual 3D environment. This 3D object is then used to create an understanding of how it behaves in this virtual world. This serves the purpose of troubleshooting some devices but is mainly for building a virtual world. For others, the digital twin is more; it includes conceptual databases; understanding products by the model and serial number that has been physically installed on site. This database can be very specific, identifying information gathered from the devices. Let’s take the example of my sketch of the pump above the database for such a digital twin could look like this:
Part Number
Model Number
Manufacturer
Installation date
Weight
3D drawing of the device
Pump Curve
Life expectancy
End of Life information
Measurements from devices
Power
Current
Voltage
Vibration
Temperature
Etc.
Our imagination only limits this database. The concept of the digital twin and the details around the installation are endless.
From here, the digital twin expands even further into the maintenance and service of the device and then into the IoT environment. Connecting this 3D model and database to predictive maintenance and artificial intelligence. Connect the information and behaviour to Scientists and Engineers to create a form of remote support.
Is this overboard? Yes. Is it the future? Definitely, as we maintain and try to understand what we will be doing, we don’t realize the problems we could solve with the information we have today unless we get out from under the weeds.
We are creating a mess.
As this digital transformation continues, we are creating a mess of things. We are putting information and data in multiple places, and the data isn’t complete in any one environment. We are struggling to create a single source of truth. We use a SCADA database with limited information from the field. Then we create maintenance databases to understand when the device was last updated.
Furthermore, we create asset management databases and disaster recovery databases. This all takes significant time to maintain and update. By the time they are completed with an asset database, they are already outdated. The biggest challenge with digital transformation is the struggle to gather information quickly and accurately from the point of installation.
Even worse, the data is dirty. Asset management databases try to gather similar information to disaster recovery databases; because they have been collected at different times, the databases don’t match.
Where do you start?
So, where do you start? Start by creating a database model to store the information in a single location. Building this model is similar to creating a design standard. Create a road map of where you would like your digital twin to be in 3 years.
Don’t overdo this; the requirements and changes will come naturally but instead, look to have everything connected in a single location—one source of truth. I look at this as the digital heart of the information. If the AI is the brain, the data is the heart. Without accurate information, the brain can’t make wise decisions. Start building your digital heart out today, which will lead to the digital twin that will be connected to everything else.
Why bother?
This all looks pretty labour-intensive and complicated. Why bother starting now? Well, the answer is simple. Information can be used to manipulate and control an environment. If your method of verifying that information is complicated, you will be at the mercy of the costs associated with this. We see these costs regarding creating standards and the ROI (return on investment) for having a standard. Don’t get stuck in the same mindset and go through the same cost implication at a later date. Get ahead of the game, start planning and preparing now, and create your digital heart, the single source of truth. Think about the data model you want to make and get excited about the future. Keep your mind engaged on the analytical and informative things, and keep growing.
Thanks for reading hope you enjoyed this week’s issue.
Slawek