Version and Link Management in FMEA and Control Plan Documents

Why does the link between the process flow diagram, PFMEA and control plan break, and how do you keep it? A comparison of Excel, FMEA software and PLM, set revisions and checks.
Technical summary
Technology
IATF 16949:2016 8.3.5.2 and 8.5.1.1, AIAG-VDA FMEA Handbook, PLM, Excel, Python
Topic
Version and consistency management of linked quality planning documents
Level
Intermediate
Prerequisites
  • Familiarity with the structure of the PFMEA and control plan
  • Access to the environment where documents are kept (file server, SharePoint, PLM)
In this article7 sections

One of the auditor’s favorite trail methods is walking backwards from a process step on the shop floor. Is the check in the operation instruction in the control plan? Which failure mode in the PFMEA does the characteristic in the control plan prevent? Which step in the process flow diagram does the step in the PFMEA correspond to? In file-based tools, this chain breaks silently, and the break is often first seen at the audit table. Below we explain why the link breaks, the tool options and a method that works in the field for managing revisions of the linked document set.

IATF 16949 clause 8.3.5.2 lists the process flow diagram, PFMEA and control plan together among the manufacturing process design outputs. Clause 8.5.1.1 requires the control plan to be linked to the PFMEA outputs and ties its content to Annex A of the standard. The AIAG-VDA FMEA Handbook also bases the structure analysis on the process flow. In other words, the three documents are parts of a single logical set. They can’t live separately. The links between them are:

  • Step number: Each step in the flow diagram is analyzed in the PFMEA under the same number and appears in the control plan under the same number.
  • Characteristic: Product and process characteristics defined in the PFMEA are matched in the control plan with a measurement method, sample and reaction plan.
  • Special characteristic: Special characteristics determined by the customer or the organization are marked with the same symbol in all three documents and in operation instructions (IATF 8.3.3.3).
  • Controls: Prevention and detection controls in the PFMEA are consistent with the methods in the control plan. If a detection control assumed in the PFMEA isn’t in the control plan, the risk assessment doesn’t reflect reality.

This link is kept not just at initial approval but throughout the product’s life. Clause 8.5.1.1 requires the control plan to be reviewed and, if necessary, updated when nonconforming product is shipped to the customer, when there’s a change to the product, process, measurement, logistics, supply source or production volume, when there’s a change in risk analysis (FMEA), and after corrective action following a customer complaint, as well as at a set frequency based on risk analysis. Each of the event-based triggers can affect the whole set; the frequency of periodic review should be written in the set record.

Typical problems with file-based management

In Excel-based management, the problem isn’t technical but structural. Each file is consistent within itself; but there’s no mechanism enforcing consistency between files. Situations you may come across:

  • Keeping the revision in the file name: Names such as PFMEA_Line3_rev7_final_FINAL.xlsx make it unclear which version is in force.
  • Duplicating with copy and paste: The existing PFMEA is copied for a similar part, the steps change, but rows for old steps or characteristics belonging to the old part remain.
  • One-way updates: After a problem on the shop floor, a new control is added to the control plan; the detection rating and action priority in the PFMEA aren’t updated.
  • Step numbers drifting: When a new step is added to the flow, numbers are reassigned; the PFMEA and control plan stay on the old numbers.
  • Copies in email: The version sent to the customer for PPAP and the version on the server diverge; nobody knows which one the customer approved.
  • No approval record: The only evidence that the multidisciplinary team reviewed the change is the name of the last person who saved the file.

Even if you stay with Excel, you can check the consistency of the set with a simple script. The example below compares step numbers and special characteristic markings across the three files; adapt the column names to your own templates:

import pandas as pd

flow   = pd.read_excel("Flow_Line3.xlsx",   sheet_name="Flow")
pfmea  = pd.read_excel("PFMEA_Line3.xlsx",  sheet_name="PFMEA")
cplan  = pd.read_excel("CP_Line3.xlsx",     sheet_name="ControlPlan")

def steps(df):
    # Drop empty cells; normalize format differences such as 10 vs 10.0
    s = df["Step_No"].dropna().astype(str).str.strip()
    return set(s.str.replace(r"\.0$", "", regex=True))

f, p, c = steps(flow), steps(pfmea), steps(cplan)

print("In flow, not in PFMEA:              ", sorted(f - p))
print("In PFMEA, not in control plan:      ", sorted(p - c))
print("In control plan, not in flow:       ", sorted(c - f))

sc_p = set(pfmea.loc[pfmea["Special_Char"].notna(), "Characteristic"])
sc_c = set(cplan.loc[cplan["Special_Char"].notna(), "Characteristic"])
print("Special in PFMEA, unmarked in control plan:", sorted(sc_p - sc_c))

This check is also useful for seeing the extent of inconsistency in existing sets before investing in software. A long list on the first run is normal. Not every finding is an error; some transport steps may have been deliberately left out of the control plan. In that case, the justification is written down. The first line to look at in the console is “Special in PFMEA, unmarked in control plan”; that’s where the most serious audit finding comes from.

Excel vs FMEA software vs PLM

Criterion Excel/file-based FMEA software PLM module
Links between documents Manual; prone to breaking Derived from a shared data model Linked to the product structure and process plan
Revision and approval Depends on repository features Built-in workflow Integrated with the corporate change process
Shared knowledge and lessons learned By copying Foundation FMEA and catalog Corporate library
AIAG-VDA 7 steps and AP Depends on template discipline Usually supported out of the box Varies by product
Setup and operating burden Low Intermediate High
Suitable for A small number of product families Many processes and lines Organizations already using PLM

The decision tree is simple. If there are few product families, changes are infrequent and the team is small, a disciplined Excel template and a repository that keeps version history may be enough. If several lines share the same process steps and systematic transfer of lessons learned is wanted, FMEA software that supports the foundation FMEA (family FMEA) logic reduces inconsistency at the source. If the organization already manages product data in a PLM, bringing quality planning documents into the same environment provides a single change flow from engineering change to control plan; but this is a serious configuration and training project. Whichever path is chosen, set aside time for migrating old PFMEAs and run the migrated sets through a consistency check like the one above. The tool changes; disconnected data moves across as it is.

The action priority (AP) approach introduced by the AIAG-VDA FMEA Handbook means old RPN-based templates can’t be used directly. During the transition, having PFMEAs assessed with the old and new methods side by side in the same set is also a kind of inconsistency; which PFMEA was assessed with which method must be recorded.

Revision management in a linked document set

The real change of method is this: give the revision to the set, not to individual files. A workable model:

  1. Set ID: For each part or part family, create a set record listing the flow diagram, PFMEA, control plan and related operation instructions.
  2. Set revision: When any document in the set changes, the set revision goes up; the record states which documents, at which revision, are part of the set.
  3. Impact assessment: In the change request, “Does this change affect the other three documents?” is a required field; if it doesn’t, the justification is written down.
  4. Marking the customer-approved version: The set revision submitted to the customer with PPAP is marked separately; whether later changes need customer approval is assessed against this reference.
  5. Shop floor distribution: Copies of operation instructions and the control plan are distributed only from the set revision in force; the collection of old copies is recorded.

General document control principles are explained in the guide document control and revision management; the difference here is keeping revisions in sync across linked documents. If the source of the change is a machine, recipe or MES change, the set revision should reference the change record in the change management in production systems process. Long-term retention of sets submitted to the customer is the subject of the guide archiving PPAP and quality records. To keep approval, version and publication records digitally, you can set up the document flow through SharePoint document and revision management.

Access and approval records

The PFMEA and control plan are the product of a multidisciplinary team; that’s why write permission should be broad and approval authority narrow. A document anyone can approve is a document nobody approves. In practice, these rules work for IT and quality compliance:

  • Team members can work on the draft; the revision in force is read-only.
  • Approval is given with recorded approval from at least process engineering and a quality representative; if a special characteristic is affected, additional approval is sought according to customer requirements.
  • The approval record shows who approved which revision, and when; an approval workflow within the repository or software is preferred to a wet-signed PDF.
  • Write permissions of people who leave the team or change roles are checked in the periodic access review; how to document this is explained in the guide access review evidence.

Revision checklist

  • Was an impact assessment done in the change request for the flow diagram, PFMEA, control plan and operation instructions?
  • Do step numbers match one-to-one across the three documents?
  • Have new or changed characteristics been defined in the control plan with a measurement method, sample and reaction plan?
  • Are special characteristic markings consistent in all documents and in shop floor instructions?
  • Are the detection controls in the PFMEA consistent with the methods in the control plan?
  • If the change affects the customer-approved set revision, has customer notification been assessed?
  • Has the set revision been increased, and are approvals recorded?
  • Have old copies on the shop floor been collected, and does only the current revision appear on screens?
  • Have lessons learned been passed on to other sets using the same steps, or to the foundation FMEA?

If you need to address the IT infrastructure, access model and evidence structure of quality planning documents together, our IATF 16949 IT requirements and audit preparation work covers this topic. The primary source for the AIAG-VDA FMEA Handbook and control plan reference documents is AIAG.

Frequently asked questions

Should the control plan be updated with every PFMEA change?

Not every PFMEA change alters the control plan, but with every change its effect on the control plan is assessed. IATF 16949 clause 8.5.1.1 lists a change in risk analysis (FMEA) among the situations that require the control plan to be reviewed. Even if no update is made, the result of the assessment should be recorded with its justification.

Is managing FMEA with Excel contrary to IATF 16949?

No. The standard doesn’t mandate a specific tool. What’s required is that the link between the flow diagram, PFMEA and control plan is kept, revisions are controlled and approvals are recorded. If Excel achieves this, it’s enough; but as the number of products and lines grows, keeping consistency by hand gets harder.

What’s the difference between a set revision and a document revision?

A document revision shows a change to a single file. A set revision defines which revisions of the linked flow diagram, PFMEA, control plan and instructions are in force together. That way, which PFMEA revision matches which control plan is read from a single record.

When moving to the AIAG-VDA approach, do old PFMEAs need to be rewritten?

This usually depends on customer requirements and the organization’s transition plan. Common practice is to use the AIAG-VDA method in new projects and to transition existing products during a significant change or review. Which PFMEA was assessed with which method should be recorded; check the customer’s transition expectations in the CSR.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles