PLM Siamese Twins
Oleg Shilovitsky
CEO @ OpenBOM | Innovator, Leader, Industry Pioneer | Transforming CAD, PLM, Engineering & Manufacturing | Advisor @ BeyondPLM
The original article was published on my Beyond PLM blog
Digital Twin is a new cool name coming on the horizon of PLM and together with DIgital Thread, it has a chance to rebrand what PLM does. For the last few years, the interest in the development of Digital Twin and Digital Thread has grown and you can see how these two are actually getting more potential to be sold to corporate executives and PLM ITs. Digital sells and two strange words Twin and Thread make it really cool. Read my earlier blogs about it.
Digital Twin: Is it cool enough to replace PLM?
Digital Twin and Digital Thread - are those two names to replace PLM?
There is no commonly agreed definition of what these two (Digital Twin and Digital Thread) include. The definitions are vague. Generally, you can think about Digital Twin as a set of many models of a product (eg. 3D CAD, Simulation, etc.) combined together into a coherent data set. Digital Thread is a database connecting all changes of the product over the entire lifecycle period. Sounds complex… Here is a new thing revealing. Are you ready? Buckle up.
Buckle up… According to CIMdata, Digital Twin and Digital Thread are actually cannot be separated. You can learn more about it during the coming soon CIMdata PLM event - CIMdata PLM Roadmap 2020. Here is the passage from the agenda of the event. And here is the passage from the opening keynote by Peter Bilello.
The concepts of the digital twin and digital thread have been around for decades. Industry insiders generally agree that keeping them joined maximizes their value and justifies the effort of keeping them current. Yet the gaps between them seem not to be closing. The specifics of digital twins and digital threads differ widely, but many of their underlying considerations are similar; both are fed by many of the same information flows, especially if PLM enables them. Fundamentally, a digital twin without a digital thread is an orphan, disconnected from the decisions and processes that impact it. Whether the product is a drill bit or an aircraft, its virtual representation will undoubtedly struggle to be complete and up to date without a digital thread. When information flows between them are synchronized and unimpeded, every business unit gains. Ultimately, the benefit of joining the digital twin to its digital thread is a competitive advantage. This presentation will make a case for how and why the digital twin and its digital thread are inseparable.
Now, that's actually a very complex thing. I don't want to have an orphan twin, but why I cannot actually have it as a model that defines the product behavior. It is like simulation - I can simulate the behavior of the product using different simulation tools or I can even fly a virtual aircraft. This model can be used. The changes of the model, including all states of the model across the lifecycle, are saved in the digital thread. The model can be incomplete and the thread can be incomplete either. They can benefit from each other, but they can live separately.
It appears that my assumption is wrong and CIMdata is going to explain it to me just in a few weeks. If you like me, want to learn first hand about this and many other topics, here is the registration link (https://www.cimdata.com/en/education/plm-conferences/plmrm-pdt-fall-2020). The vent is virtual, so you can watch it from an office located in the cloud. If for some reason, you won't attend, I promise to share the answer to this question after the event via my blog.
I wonder what you think about the inseparable characters of Digital Twin and Thread? Are you in the process of setting it up in your organization? Or you're prepared to learn more before and to allow the industry to figure it out first.
What is my conclusion?
According to CIMdata, Digital Twin and Digital Thread are inseparable things and can hugely benefit each other. I look forward to learning from the event. If you cannot attend, please share your questions with me, I will help you to facilitate the conversation and share the opinion. ,
Just my thoughts…
Best, Oleg
Disclaimer: I’m co-founder and CEO of OpenBOM developing a digital network platform that manages product data and connects manufacturers and their supply chain networks.
The original Data PLuMber (fixing PDM leaks and blockages across the lifecycle to improve information/data flow)
4 年I think there is some confusion here Oleg Shilovitsky. I think what is being said is that you can have different instances of Digital Twin (product test simulation, tool order completeness or bill of process NB/ a Twin doesn't have to be a 3D twin) but you need the Digital Thread to maintain alignment across all of those Twin instances (if required, for example you might no longer perform digital tests if you are testing physical products, but if you do you want to digital BOM to align to your physical product) but also through time so you can trace what and why changes to the product were made.