"Issue & continuous improvement" columns in AIAG-VDA PFMEA form

[morteza]

Hello all,

In AIAG-VDA PFMEA form (Form C on page 163) there are 2 columns with no description on how to filling them. May some one show me how to fill these two columns (issue # and History/change authorization) with an example? what are their meanings?




Thanks all.

 

[John C. Abnet]

(issue # and History/change authorization)

Good day @morteza ;
Don't overthink this. This comes from the "optimization" portion of the AIAG/VDA PFMEA methodology.

What they are asking for here is....
ISSUE # :
This may be an internal trouble report, or "incident" number or other internally (or customer) assigned tracking number. This number may identify or reflect the impetus for a change to the PFMEA

CONTINOUS IMPROVMENT:
This is simply the action taken as result of the aforementioned "ISSUE #". For example, if "ISSUE # is an identifier for a specific process control failure, then "CONTINUOUS IMPROVEMENT" may reflect the corrective action details

NOTE: The terminology you have provided (i.e. "CONTINUOS IMPROVEMENT" ) is not consistent with most terminology associated with the optimization aspect of the AIAG/VDA pfmea. For example, "CONTINOUS IMPROVEMENT" would not be the correct terms for the "corrective action' example I provided. I would recommend a more generic term such as "action taken".

NOTE: Take care not to circumvent or duplicate your organization's current change point control methodology. If your organization already has a well defined and functioning change point control process, then I would recommend (in the fields in question that you have provided) simply POINTING to (e.g.. applying the discrete change point control tracking number) the details within your change point control tracking log, database, etc.. so there is no confusion or contradiction or redundancy.

Hope this helps.
Be well.

 

[John C. Abnet]

Good day @morteza ;
I looked a little closer at your OP. I now see that indeed, in the AIAG/VDA manual (page 163) as you describe, the form template does indeed use the exact verbiage you stated and it is not included in the optimization section. Confusing. As you will note on the referenced form, it states "optional" in this section. As you know, continuous improvement activities generally warrant an update to the PFMEA. As with the change point control advice I mentioned previously in this post, I would recommend simply pointing to your current tracking number/method for identifying the continuous improvement (change point control) activity that was the impetus for the PFMEA change. (Indeed, results of continuous improvement generally result in a controlled change, therefore, the tracking reference may be the same).

Note: The CTS software (AIAG) does NOT have the fields you are describing.

Summary: However you choose to (or not---note the example you provided states "optional"), to use those fields on the PFMEA, be sure not to replicate/duplicate/contradict from existing documenting/tracking methods your organization may use or otherwise fragment information.

Hope this helps.

Be well.

 

[morteza]

Good day @morteza ;
I looked a little closer at your OP. I now see that indeed, in the AIAG/VDA manual (page 163) as you describe, the form template does indeed use the exact verbiage you stated and it is not included in the optimization section. Confusing. As you will note on the referenced form, it states "optional" in this section. As you know, continuous improvement activities generally warrant an update to the PFMEA. As with the change point control advice I mentioned previously in this post, I would recommend simply pointing to your current tracking number/method for identifying the continuous improvement (change point control) activity that was the impetus for the PFMEA change. (Indeed, results of continuous improvement generally result in a controlled change, therefore, the tracking reference may be the same).

Note: The CTS software (AIAG) does NOT have the fields you are describing.

Summary: However you choose to (or not---note the example you provided states "optional"), to use those fields on the PFMEA, be sure not to replicate/duplicate/contradict from existing documenting/tracking methods your organization may use or otherwise fragment information.

Hope this helps.

Be well.

Hi John,

thanks for your explanation. I thought that "ISSUE #" is the publication or edition number. and "History/Change authorization" is a summary description of change applied to the new version.

Thanks

 

[Johnnymo62]

Those two columns aren't in the excel file that came with the handbook I bought.