17 fmea checklist
DESCRIPTION
FMEA CheckListTRANSCRIPT
Process FMEA Checklist
Doc.No : F/CFT/17
25.09.10
Page 1 of 2
S.No. Question Yes No Commentment / Action required Due Date
1 √ Yes. PFMEA 4th Edition used for PFMEA Preparation C.Stephen Completed
2 √ CFT Leader Completed
3 √ C.Stephen Completed
4 √ C.Stephen Completed
5 √ C.Stephen Completed
6 Were similar part FMEA is considered? √ C.Stephen Completed
7 √ No Warranty Complaint recd for this Part. N.Santhosh Completed
8 √ C.Stephen Completed
9 √ Yes. Revised after completion of recommended action C.Stephen Completed
10 √ C.Stephen Completed
11 √ C.Stephen Completed
Part Name : Guard Assy - Fr Wheel Guard LH / RH
Part No :86811 / 12 - 4N000 Model : HA Customer : M/s. HMIL Date : 07.06.2011
Person Responsible
Was the PFMEA prepared using the potential failure mode and effects analysis reference manuals?
Was a multi disciplinary approach used for developing PFMEA
Yes. CFT Team ( Quality, Production, Tooling and Operation Team ) involved I making PFMEA
Does the PFMEA shows a revision status and is it under document control?
Yes. Document control and revision available for this document
Have all operations affecting fit,funtion,durability,govermental regulations and safety been indendified and listed sequently?
Fit and function identified ( checker fitment and Piece 1 and Piece 2 Mating checkment identified )
Are special charecteristics considered for impact of potential failure mode?
Special Character not mentioned in the drawing. But Internal Critical characteristic idntified for part weight and considered the impact in case of failure
Yes. Old Model Wheel Guard FMEA and old problem histories considered
Have historical campaign and warranty data been reviewed?
Have appropriate preventive actions been planed or taken for high severity / occurrence / detection categories?
Yes. Appropriate actions initiated to high severity and occurrce
Is RPN revised after completion of recommended actions?
were high severity numbers revised when design change was completed?
Design is not in our control. Customer design. When design is changed by customer, Severity revised
Do effects consider the customer in term of the subseqent operations,assembly and product?
Yes. Customer end assy and fitment related failure mode considered
12 √ No Warranty Complaint recd for this Part. N.Santhosh Completed
13 √ Yes. Inhouse rej details taken for consideration N.Santhosh Completed
Was waranty information used as an aid in developing the PFMEA?
Were customer plant problems used as an aid in developing the PFMEA?
Process FMEA Checklist
Doc.No : F/CFT/17
Rev no:01 dtd 25.09.10
Page 2 of 2
S.No. Question Yes No Commentment / Action required Due Date
14 √ John Thangaraj Completed
15 √ N.Santhosh Completed
16 √ Yes. Controls reflected in apropriate documents N.Santhosh Completed
17 √ N.Santhosh Completed
18 √ N.Santhosh Completed
19 √ N.Santhosh Completed
20 √ N.Santhosh Ongoing
21 Is the masterlist is updated? √ Yes. Masterlist updated N.Santhosh Completed
Prepared By: Approved by :
Person Responsible
Have the causes been described in terms of something that can be fixed or controlled?
Yes. Causes have been identified and actions have been taken for the same through inhouse rej analysis and trouble shooting methods
Were detection is the major factor,have provisions been made to control the cause prior to the next operation?
100% Inspection carried at each operation to control the cause prior to next operation
Are current controls reflected on appropriate documents?
Is responisibilty and target defined for recommended actions?
Yes. Responsibility and Target date defined for recommended actions
Is there evidence of effective tracking of recommended actions till completion?
Yes. For customer complaints, effectiveness of the corrective actions monitored for 6 months time
After completion,is PFMEA revised to reflect recommended actions as current controls?
Yes. Recommended actions identified as controls after effectiveness monitoring
Is the CFT able to relate occurrence rankings to TGW data?
Yes. CFT Team records the old problem history and Things gone wrong data stored