{{Short description|Architectural approach to distributed lifecycle data integration}} {{Use dmy dates|date=May 2026}}
A '''federated digital thread''', also called an integrated digital thread, is a design method used in modern manufacturing and digital engineering to organize and connect end-to-end data across multiple systems without requiring a single central database. It links data across different tools and organizations while allowing each system to remain independent.
A standard digital thread usually connects data within one organization. A federated digital thread, by contrast, links information across different organizations, such as suppliers, manufacturers, vendors, and others. A federated digital thread can also be used within a single organization to connect groups who do not share a common, single 'source of truth' - such as customer support, engineering, quality assurance, line of business owners and executives.<ref>{{cite web|url=https://www.opshub.com/blogs/data-federation-what-is-it-and-why-enterprise-leaders-are-running-towards-it/|title=Data Federation: What is it, and why enterprise leaders are running towards it|publisher=OpsHub|date=December 18, 2025}}</ref> In a federated model, these groups do not share one central database but use common communication rules to exchange details. The federated framework allows each participant to maintain strict control and security over their own data while still contributing to a shared, complete record of a product.
Making this work often depends on technologies such as linked data and graph-based relationships, which enable seamless communication between systems.<ref>{{Cite journal |url=https://www.nist.gov/publications/towards-lifecycle-information-framework-and-technology-manufacturing |title=Towards a Lifecycle Information Framework and Technology in Manufacturing |first1=Thomas D. |last1=Hedberg |first2=Allison Barnard |last2=Feeney |first3=Moneer M. |last3=Helu |first4=Jaime A. |last4=Camelio |date=14 July 2016 |journal=NIST |via=www.nist.gov}}</ref><ref name="Hedberg-2020">{{Cite journal |title=Using Graphs to Link Data Across the Product Lifecycle for Enabling Smart Manufacturing Digital Threads |first1=Thomas D. |last1=Hedberg |first2=Manas |last2=Bajaj |first3=Jaime A. |last3=Camelio |date=1 February 2020 |journal=Journal of Computing and Information Science in Engineering |volume=20 |issue=1 |article-number=011011 |doi=10.1115/1.4044921 |pmid=32831801 |pmc=7437158 }}</ref> Unlike centralized data architectures, a federated approach enables integration without requiring consolidation into a single repository.
==Background and evolution==
The need for connected lifecycle data grew in the early 2000s, particularly in aerospace and defense sectors that manage complex systems and large volumes of engineering data. A digital thread enables a continuous information flow across design, manufacturing, and operational stages.<ref>{{Cite web |url=https://www.industryweek.com/technology-and-iiot/systems-integration/article/22008200/how-manufacturers-benefit-from-the-digital-thread |title=How Manufacturers Benefit from the Digital Thread |first=Andrew |last=Waycott |date=25 March 2016 |website=IndustryWeek}}</ref>
Earlier approaches focused on consolidating data into centralized systems to create a “single source of truth.” However, as projects expanded to include global partners, this model became difficult to manage due to differences in tools, data formats, and security requirements.
Government initiatives such as the United States Department of Defense DoDI 5000.97, which described their Digital Engineering Strategy, emphasize the use of authoritative data across lifecycle stages, reinforcing the need for connected but controlled data environments.<ref>{{cite web|url=https://ac.cto.mil/wp-content/uploads/2019/06/2018-Digital-Engineering-Strategy_Approved_PrintVersion.pdf|publisher=Department of Defense|date=June 2018|title=Digital Engineering Strategy}}</ref>
Over time, research and industry practices shifted toward federated approaches, where integration is achieved by connecting existing systems rather than replacing them. Studies on federated product lifecycle management architectures highlight that such approaches can reduce integration complexity and improve scalability compared to centralized systems.<ref>{{Cite journal |url=https://www.cambridge.org/core/journals/proceedings-of-the-design-society/article/from-tears-to-tiers-architectural-principles-for-federated-plm-landscapes/AD63EEEFFE01D5E39068CA117DFAAD0B |title=From tears to tiers – architectural principles for federated PLM landscapes |first1=Erik |last1=Herzog |first2=Johan |last2=Tingström |first3=Johanna Wallén |last3=Axehill |first4=Åsa Nordling |last4=Larsson |first5=Christopher |last5=Jouannet |date=1 May 2024 |journal=Proceedings of the Design Society |volume=4 |pages=593–602 |via=Cambridge University Press |doi=10.1017/pds.2024.62|doi-access=free }}</ref>
==Key concepts and maturity levels==
Organizations typically progress through different stages of digital maturity.
The first stage is digitization, which converts physical records into digital formats such as scanned documents.
The second stage, digitalization, introduces specialized software systems across departments, although these systems often operate independently and require manual data exchange.<ref>{{Cite web |url=https://www.researchgate.net/publication/332111919 |title=From Digitization, through Digitalization, to Digital Transformation}}</ref>
The third stage is a digital thread, where systems are connected through integrations that enable data flow across lifecycle stages. However, research shows that these integrations are often limited and may not preserve full context or relationships across lifecycle data.<ref>{{Cite journal |title=A Literature Review of the Digital Thread: Definition, Key Technologies, and Applications |first1=Qiang |last1=Zhang |first2=Jihong |last2=Liu |first3=Xu |last3=Chen |date=23 February 2024 |journal=Systems |volume=12 |issue=3 |pages=70 |doi=10.3390/systems12030070 |doi-access=free }}</ref>
Implementing a digital thread is more complex than simply storing data digitally. It is an advanced capability that organizations build by moving through several stages of digital maturity.<ref name="Hedberg-2020" />
A fully developed federated digital thread represents a more advanced stage, where lifecycle data remains distributed but is linked across systems. Research from the National Institute of Standards and Technology (NIST) highlights that lifecycle data is inherently heterogeneous and distributed, requiring approaches that support integration across multiple systems without centralization.<ref>{{Cite journal |url=https://www.nist.gov/publications/testing-digital-thread-support-model-based-manufacturing-and-inspection |title=Testing the Digital Thread in Support of Model-Based Manufacturing and Inspection |first1=Thomas D. |last1=Hedberg |first2=Joshua |last2=Lubell |first3=Lyle |last3=Fischer |first4=Larry |last4=Maggiano |first5=Allison Barnard |last5=Feeney |date=8 March 2016 |journal=NIST |volume=16 |issue=2 |pages=1–10 |article-number=021001 |doi=10.1115/1.4032697 |pmid=27325911 |pmc=4904719 |via=www.nist.gov}}</ref>
This approach enables organizations to maintain their existing tools while still providing a unified view of product lifecycle information.
==Applications in industry==
Highly regulated industries such as aerospace, defense, and medical device manufacturing rely on integrated lifecycle data to manage complex products over long periods. These sectors require traceability, compliance, and the ability to maintain digital records across decades.
A federated approach supports these requirements by ensuring that lifecycle data remains accessible even when systems change or organizations evolve. It also allows suppliers and subcontractors to retain control over their intellectual property, since data remains within their own systems while only relevant information is shared.
In addition, digital thread implementations have been shown to support improved traceability, quality management, and operational decision-making in manufacturing environments.<ref>{{Cite web |url=https://www.automationworld.com/products/software/article/13315564/the-digital-thread-on-display |title=The Digital Thread on Display |first=David |last=Greenfield |date=14 June 2016 |website=Automation World}}</ref>
==Related concepts==
The federated digital thread is closely related to the concept of a digital twin, but the two serve different purposes. A digital twin is a virtual representation of a specific physical asset that reflects its current state. The digital thread provides data connections that enable information to flow across lifecycle stages and support the digital twin.<ref>{{cite web|url=https://kiwi.oden.utexas.edu/papers/Engineering-design-digital-thread-Singh-Willcox.pdf|title=Engineering Design with Digital Thread|publisher=Massachusetts Institute of Technology|author=Victor Singh}}</ref>
Standards such as Open Services for Lifecycle Collaboration (OSLC) provide mechanisms for linking data across systems, supporting federated integration without requiring data centralization.<ref>{{Cite web |url=https://www.oasis-open.org/standard/oslc-core-version-3-0/ |title=OSLC Core Version 3.0}}</ref>
==References== {{reflist}}
Category:Software frameworks Category:Software design patterns