Does Every New Project Start FMEA from Scratch? —— Five Steps to Establish and Reuse Baseline FMEA (Family FMEA)

By: QTank Published: 10/5/2026 Views: 14

Current rating: ★★★☆☆ Rate this Equivalent to 8 ratings

When a new project is launched, the client demands the PFMEA to be submitted within two weeks. Quality engineers typically adopt one of two approaches: either open the previous version, change the part number, and submit it; or start from scratch, only to realize halfway through that a process step has been missed. Both methods lead to the same pitfall—using the same process and the same team, the failure causes and ratings vary each time. The AIAG-VDA FMEA manual provides a clear solution in the first step, "Planning and Preparation": identify the baseline FMEA first, integrate existing lessons learned, and then proceed with the analysis.

1. What Exactly is a Baseline FMEA?

A baseline FMEA is a "settled version" of the analysis: for a specific type of process (welding, injection molding, heat treatment, painting, etc.), it consolidates common process steps, typical failure modes and causes, current control measures, and ratings into a reusable template. When a new project starts, the analysis begins from this template, focusing only on the differences rather than starting from scratch each time.

Two concepts need clarification: the baseline FMEA is a template that is shared across projects; the family FMEA is a usage method that consolidates and analyzes a group of products/processes with highly similar structures, functions, and process routes. The former is the "inventory," while the latter is the "usage rule." The key difference from "copying the previous version" is that the baseline is maintained, reviewed, and has a consistent rating standard; whereas, casual copying inherits the old errors and outdated information from the previous version.

2. Why "Starting from Scratch" and "Copying" Are Both Wrong

Starting from Scratch: Each time, the analysis starts from the structural analysis, leading to a long delivery cycle and inconsistent rating standards. The same "operator missing an installation" might be rated 5 today and 8 tomorrow. When the client compares two projects, they immediately question the consistency of your rating system.
Copying: Directly modifying the part number from the previous project's FMEA, it carries over all the old issues—obsolete process parameters, ineffective detection measures, and more—into the new project.
Not Backfilling: Real failures, 8D conclusions, and customer complaints are clearly documented in repair and scrap records, but no one backfills them into the template. As a result, the FMEA remains a "theoretical" document rather than a "practical" one.

Conversely, a well-maintained baseline FMEA offers direct benefits: when a new project starts, it already has a complete structure and cause analysis, allowing engineers to focus on the differences rather than copying procedures. The rating standards for the same failure are consistent across the family, making it difficult for clients to find contradictions when comparing projects. During audits, the baseline version, backfill records, and list of changes can be presented to demonstrate that the analysis is a continuous accumulation, not a last-minute fabrication.

3. Five Steps to Establish and Reuse

Step 1: Define the Family and Set Boundaries. Group processes by similarity: a set of processes with similar structural forms, materials, key procedures, and equipment types should be circled into a family. If the family is too large, the analysis may become distorted; if it is too small, it loses its reuse value. Generally, the boundary is set as "the same workshop, the same type of equipment, the same process flow."

Step 2: Extract and Clean the Template. From the existing FMEAs, 8Ds, customer complaints, and repair and scrap records within the family, compile the failure modes, failure causes, and current controls for common process steps. Remove project-specific content (specific dimensions, specific customer symbols) and retain the generic items. Standardize the rating criteria to a single set of judgment standards and specify the version of the severity, occurrence, and detection judgment tables used.

Step 3: Label Each Row as "Reusable" or "Must Re-evaluate." Tag each row in the template:

Failure modes of common procedures that are not product-specific can be directly inherited.
Failure modes related to product characteristics or special characteristics—reuse the structure and causes, but re-evaluate the severity and occurrence for the new project.
Failure modes involving customer special requirements (CSRs)—recheck according to customer requirements each time and do not inherit.

Step 4: Conduct Differential Analysis from the Baseline. Align the new project's process flow diagram with the baseline: perform a complete seven-step analysis for any new or changed procedures; for other procedures, reference the baseline row numbers and maintain traceability. List all change points (new equipment, new materials, new process parameters) separately as the focus of this analysis.

Step 5: Backfill New Findings into the Template. After the project is completed, feed back the actual failures, 8D conclusions, and the effectiveness of measures into the template. Update the ratings and detection measures, and record the version, date, and approver. The baseline is a living document—without a backfill mechanism, it will eventually become an outdated and unreliable record.

4. An Example

A fastener factory uses welding as a common process across the family. In the baseline FMEA, "low welding current leading to incomplete penetration" is already fully analyzed, including the failure cause, current control (parameter lock + first article inspection every shift), severity and occurrence ratings, and the corresponding control plan row number.

A new project involves a bracket, which uses the same welding process but changes the material from low-carbon steel to high-strength steel. The approach for reusing the baseline is: directly reference the structure analysis and failure causes from the baseline; re-evaluate the severity and occurrence of "incomplete penetration" based on the new weldability of the material; add a new item "brittleness in the heat-affected zone of high-strength steel" to the list of change points and conduct a complete analysis; and recheck the customer's special characteristic symbols and non-destructive testing requirements. The entire FMEA was completed in two days, with consistent ratings compared to the previous version, and the client did not raise any issues about "inconsistent ratings for the same failure" when comparing the two projects.

5. Three Questions to Ensure Implementation

Which parts of this analysis are shared by the family, and which are unique to this project?
Do the ratings referenced from the baseline match the criteria and version?
Are there any new insights from this project worth backfilling into the template?

By asking these three questions, the FMEA transforms from a "repeated task for each project" into a "growing asset."

The value of a baseline FMEA lies not in saving effort, but in consolidating the experience from each project into a reusable template—conducting differential analysis from the baseline and backfilling new insights ensures consistent ratings and faster delivery.

Knowledge code: 8.3.1

Version: v20261005

Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.