The digital thread might be the latest buzz phrase in content management. But what does it mean? How is it used? And what can it do for you?
If we think of the different components of a product as cloth, that cloth needs to be stitched together to form an entire garment. The associations between these components, or the thread, is what binds the discrete pieces into a whole. The same cloth might be used to make a shirt or dress, but it is the way the components are assembled that renders the full product.
Let’s say you’re a technician working on a system that was recently updated with a new panel. That system experiences a fault with the panel and you get out the documentation to troubleshoot it. The illustrations and the troubleshooting steps do not account for the new panel at all. Suddenly, you are unable to do your job or get the system back online.
While the system has been updated recently, to include this new panel, the documentation is updated on a separate process, which requires someone manually associating the service content for the new panel with the existing product. If the product was leveraging the digital thread, the panel and its associated content would have been incorporated at the same time.
Put simply, the digital thread establishes associativity between all artifacts along a product’s lifecycle. In most cases, this involves running that thread from the initial engineering bill of material (EBOM) to the service bill of materials (SBOM) to the service and training content delivered with the product.
The digital thread ensures that all groups working on a project are on the same page.
No more design changes that were never communicated downstream. Participants no longer need to rely on manual processes or human memory. All artifacts are associated within the software, and workflows are enforced by the system. When an engineering change occurs, it triggers a workflow that notifies the responsible groups downstream.
The digital thread is digital accountability. You can always find out where a change is in the lifecycle, who has completed their tasks, and who has not. This also supports auditing and reporting.
If we take our undocumented new panel as an example, had the project been using the digital thread through supported software, the engineering design would have been revised with the new panel. That change in design and associated parts would have impacted the EBOM. The EBOM change would have caused the associated SBOM to fall out of sync. When the SBOM was updated to account for the change, the content associated with the affected parts would have been flagged. In parallel to engineering changing the actual product, the content owners could have updated the documentation and got it out into the field with the new panel.
The digital thread is a simple connected information concept with compounded benefits. If you want to see how information associativity can simplify your process and improve your product, get in touch with us here.
In the mean time, have a look at this recent Digital Thread Webinar.
Your technical content is about to make the leap. You are about to make the change everyone has told you about. You are moving to structured authoring. You have an idea of what the change means, but what will it look like? How will your content actually change when you move to structured authoring?
Read moreWhat does it actually look like to work with the digital thread? As a product engineer. As a logistics engineer. As an illustrator. As a technical writer. As a service technician. Take a journey down the digital thread and see what it looks like from the perspective of some of the roles contributing to the larger product lifecycle.
Read more