In many industrial organizations, FMEAs follow a well-established process, with expected links between Design FMEA and Process FMEA: DFMEA is developed during the design phase, while PFMEA is created during manufacturing preparation. Both are reviewed, validated, and managed within their respective environments.
A few months later, production relies on a Control Plan. However, ensuring that all critical controls identified during FMEA analyses have been properly transferred, implemented, and maintained over time remains a challenge. When product changes occur, evaluating their impact on existing analyses and ensuring overall consistency across the lifecycle can require significant effort.
This situation is common across many industries. It is not a matter of team discipline or methodology — it is a matter of digital continuity. Risk-related data does not always flow seamlessly across processes, and the connections between product lifecycle phases are not continuously maintained.
This is the principle behind Digital Thread:
not simply digitizing documents but creating and maintaining meaningful connections between critical data throughout product design, industrialization, validation, production, and field feedback.
A context that makes the issue more urgent. Industrial products are becoming increasingly complex, product changes are accelerating, and regulatory requirements are becoming more demanding across many industries. In this context, the ability to quickly identify the impact of a change — and ensure that all related data remains consistent — has become a major operational challenge. The question is no longer only “How can we perform an effective FMEA?” but rather “How can we ensure that risk data remains consistent, traceable, and actionable throughout the entire product lifecycle”? This is precisely the challenge addressed by Digital Thread.
When product lifecycle phases do not communicate with one another.
In many organizations, each phase of the product lifecycle operates with its own data and tools. Design teams develop their DFMEA in one environment. Manufacturing engineering teams create the PFMEA in another. Production relies on its Control Plan to monitor critical process characteristics.
Even when these different deliverables are theoretically connected, maintaining their consistency over time remains challenging, especially when multiple tools or reference systems are involved throughout the product lifecycle.
This approach is not a problem by itself. The challenge arises when changes accumulate and the links between these different deliverables must be continuously maintained.
When the connections between PFMEA and the Control Plan are not reliably and sustainably maintained, the risk of inconsistencies increases as product and process changes occur. During an audit or a change assessment, ensuring overall alignment across all deliverables can become a significant effort.
The Digital Thread: Ensuring Information Continuity
The Digital Thread concept has emerged as a response to this challenge across manufacturing industries. The goal is not to centralize everything within a single tool, but rather to ensure information continuity throughout the product lifecycle: enabling data to remain interconnected, consistent, and accessible wherever it creates value.
When applied to FMEA, this approach translates into continuous data flows between analyses: the functional analysis feeds the DFMEA; the DFMEA supports both the PFMEA and the DVP; and the PFMEA feeds the Control Plan.
This continuity makes it possible to quickly assess the consequences of a change, identify impacted data, and support decision-making throughout the entire product lifecycle.
When field feedback becomes available, Reverse FMEA provides a way to compare the initial analysis with real-world performance and reintegrate these insights into the risk management loop, based on structured and traceable data.
Why is FMEA one of the most connected information assets in the product lifecycle?
Among all product lifecycle data, the information contained in FMEAs — functions, failure modes, causes, effects, actions, and controls — maintains numerous connections with other lifecycle information assets.
This data is initially built from product requirements and functional analysis. It directly influences the Control Plan and verification and validation activities downstream.
It is reassessed whenever significant changes occur, making it a key reference point for any impact analysis. Finally, it is enriched by field feedback through Reverse FMEA, enabling risk analyses to be continuously reviewed based on real-world data throughout the product lifecycle.
This central position makes FMEA data far more than a simple quality deliverable. FMEA data becomes a central information hub — which is why keeping it isolated in a standalone file, disconnected from other lifecycle phases, disrupts the Digital Thread precisely where it can create the most value.
A Digital Thread centered around FMEA aims to keep these connections alive: ensuring that design changes are consistently propagated through to production, and that traceability between identified risks and implemented controls remains continuously demonstrable.
A challenge shared across all industrial sectors
The challenge of digital continuity is universal. Standards may differ and regulatory constraints may vary, but the need to maintain data consistency across lifecycle phases remains the same.
In the automotive industry, the AIAG-VDA 2019 FMEA Handbook formalized the links between DFMEA, PFMEA, and Control Plans. It establishes the need for consistency and traceability between analyses. However, without an appropriate digital environment, maintaining this continuity throughout product and process changes remains a significant operational challenge.
In the medical device industry, The EU Medical Device Regulation (MDR) and ISO 14971 require identified risks, implemented risk control measures, and post-market surveillance data to remain consistent throughout the device lifecycle. Ensuring continuity between risk analyses and field information is a major regulatory requirement.
In aerospace, safety analyses performed according to ARP4761 must remain consistent with system requirements, design decisions, and verification activities. Any significant change requires a rigorously documented impact analysis to preserve the safety assurance case.
Three industries, three sets of standards, one common reality: risk-related data must remain consistent, traceable, and actionable throughout the entire product lifecycle.
Conclusion
The Digital Thread is not only intended for large enterprises or ambitious digital transformation programs. Above all, it is a matter of data governance: is the information generated throughout each lifecycle phase interconnected? Does your risk data evolve with your product, or does it remain separate from it?
The Digital Thread is often presented as a way to connect product data. However, in regulated industries, ensuring continuity of risk data is equally essential. Without this continuity, decisions made during design, validation, or production gradually lose their consistency.
At Knowllence, ensuring risk data continuity is at the core of our approach. We believe that risk data must remain connected to other product lifecycle information in order to preserve the consistency of decisions made throughout product development, manufacturing, and operation.
This approach is supported by the TEEXMA Platform, which extends this continuity to other lifecycle data through its connections with Quality, PLM, MES, and LIMS environments.
The following articles will explore in detail how this digital continuity is built, phase by phase.
This data continuity is also becoming a key enabler for addressing new traceability challenges, particularly those driven by the Digital Product Passport (DPP). To learn more about this topic, discover our dedicated article on the DPP.