Typical error and TIPs for Process Flow

  1. Inspection Operations, especially Receiving Inspection, are not included in Process Flow Diagram.
  2. Input in Column : Product Characteristics (may be defined as Desired Outcomes or Outgoing Dimensions) are not covered Product Characteristics relating to supporting activities such as clamping or locating,… in next operations. Use of Characteristic Matrix will help to define all related characteristics.
  3. Number of Operation Symbol defined in Process Flow does not reflect all sources of variation such as Number of Sub-contractors, all location of stores (outside and inside), number of machines.

Typical error and TIPs for Process Failure Mode and Effect Analysis

  1. Failure Modes from previous operations are included in analysis in considered operation, that leads to repeated reference of Failure Modes between operations. And the Potential Causes of repeated Failure Modes will not be defined as clearly as done by the directly-related operation’s analyzer. (Note : The directly-related operation is the operation responsible for creating Product Characteristics of which Failure Mode considered.)
  2. Defining of Failure Mode in some particular operation, some may put “Fail inspection” or “out of Specification” as failure mode inspection operation which is actually should be the failure mode of previous operation(s) producing that bad product characteristic (Failure Mode).
  3. There is confusion between “Potential Failure Mode” and “Potential Causes”. This incidents are frequently happen in real situation when you team up all APQP/Process Review Members and the very first input you will have during brainstorming is all the sufferings from customer (:- next process Customer, OEM customer, end user of product, all issuer of regulation (Government or States) suddenly you will add in “Potential Effects of Failure Modes” Column. Here, the confusion arises, because there is tendency to put the failure modes into “Potential Causes” Column and some may put the effect or additional description of specified Effects into Potential Failure Mode” Column in stead.
  4. Most of Failure Mode Analysis can be operation-oriented failure mode analysis. But for complex or automated operations which be able to create many PCID at a time, not all PCIDs are considered for their failure modes. Therefore, to comprehensively define all of the failure modes under one particular operation, you should add PCID (or Product Characteristics, Desired Outcomes or Outgoing Dimensions) column and description before considering Potential Failure Modes.
  5. According to PFMEA form, there are some information (in columns) which can be expanded or branched as appropriate during further analysis, namely from left to right, Operation Number/Description, Product Characteristics (PCID), Potential Failure Modes, Potential Causes and Current Control.
  6. Potential Failure and Effect Analysis

  7. Effects of Potential Failure are not considered to cover possible effects with all customer : next process Customer, OEM customer, end user of product, all issuer of regulation (Government or States).
  8. Potential Causes are not the root cause or the Recommended Actions are not Permanent Corrective Action or Preventive Action, it may be just Immediate or Containment Action.
  9. Rating of Severity, Occurrence and Detection Degree are not appropriately justified (within the same APQP team or different team considering the same part number).
  10. There is reduction of new Severity Degree after taking Recommended Action. This is not likely to occur when considering PFMEA, you can have less new severity degree in Design FMEA.
  11. Occurrence degree given to any potential causes are not compliance with PPM (defective Part Per Million) or Cpk results (if available). (see below Table)
  12. If you don’t have official “Current Process Control” or official inspection operation/station to detect that Failure Mode Detection Degree are not necessary to be 10, provided that the operator may monitor the Failure / defect during operating.
  13. No Recommended Action defined for high RPN.
  14. No completion date defined and/or no follow-up of Recommended Actions and recalculation of new RPN.
  15. Recommended Actions are focused only for detection, Not Prevention of failure mode or defect.
  16. Recommended Actions have been limited by pre-defined resources namely, number of measuring equipment, Machine Capability, number of operators, Quality level of component from sub-contractors.

Home

QS9000

APQP

PFMEA

SPC

MSA

QSA

Links

About Author

E-Mail