The term digital thread is used to describe the ability to trace how digital information was created, with which other information objects it is interrelated, and what status it has across the different domains.
It is crucial that users do not have to spend a great deal of time compiling this information manually, but that it is made available pretty much at the touch of a button. To do this, you need to be able to look into more than one IT system without necessarily having to consolidate the information in a single system.
The most widely used PLM or ALM systems are unable to do this as they only manage and monitor their own information. PROSTEP, however, links all the systems in product development and manufacturing with its well-known products, brands and solutions and consolidates this information in the PROSTEP Digital Thread Platform. The platform is used to synchronize or link the data between the different IT systems and exchange it with partners.
Complex products with short lifecycles
End-to-end digitalization is not necessarily a new requirement, but the difficulties that companies are facing have increased in recent years. Their products are becoming increasingly complex, while product lifecycles are becoming ever shorter. If companies want to address issues such as model-based systems engineering (MBSE) and the increasing proportion of software in products, they need to introduce new IT systems. This, however, only improves the work ability of individual domains and groups of engineers but not their ability to collaborate across domain boundaries, which means that the real benefit of end-to-end digitalization is lost.
A major challenge when creating a digital thread is organizing human collaboration. The domains still focus far too often on their own specific objectives and pay too little attention to how the other domains work and what information they therefore require. Which is why they find it difficult to see the connecting factors in their day-to-day work. This is exactly what is currently radically changing – not least due to the impact of new development methods such as MBSE.
The increasing possibilities offered by digital product descriptions and the growing proportion of software in the products mean that functions can now be described based on models – regardless of whether they are subsequently mapped in the hardware or software. Without MBSE, there would be an unnecessarily large number of iterations during development due to the fact that although the data in the software systems is digital, it is not linked. The model-based description of the product or system also provides a basic framework of the relationships for the digital thread, which is then filled with content and instantiated in the domains. The domains define the lifecycles of the components, regardless of whether they involve mechanical engineering, electrical/electronic engineering or software. They must, however, be linked together. This is the only way to determine, for example, which software version can be used on which control unit.