This is why the digital twin has long been the focus of many digitalization initiatives. It is all the more surprising to me how little I’ve heard about the digital twin in recent months given all the fuss made by all the major PLM vendors prior to the coronavirus pandemic. The issue has been consigned to the “valley of tears” in Gartner’s Hype Cycle. This may have to do with the fact that companies are now barely able to map the enormous product complexity in a digital twin using traditional development methods and tools.
Smart products contain a large amount of software and electronics that often take on system-relevant functions and must therefore be considered part of the digital twin. This requires a cross-domain perspective, and in many companies, this is hindered by the different processes in the individual domains. Moreover, they lack the golden thread that binds all this information together over the entire product lifecycle and makes the development history traceable. In this context, people also speak of the digital thread as the enabler of traceability. It is an essential prerequisite for the digital twin, or, as Peter Bilello, head of the market research company CIMdata, once said: “without the digital thread, the digital twin is an orphan”.
In the perfect IT world of a single IT vendor, this digital thread could perhaps still be spun without an unacceptable amount of effort. But the world in most companies, and especially among the large carmakers, is not perfect. Instead, it is highly heterogeneous, and this is not set to change in the future. As a result, users have to make a considerable effort to gather all the relevant information at certain milestones and to ensure the traceability of development processes and deliverables.