In the highly demanding and competitive fashion apparel world where the profit margins are shrinking and buyers are placing increased demands for high quality, reliable products on a cheaper price. The increasing cost pressure making it more difficult for manufacturers to maintain the quality and reliability.
Traditionally, quality and reliability has been achieved through extensive quality inspections and the final product inspection on AQL. These are techniques done in the late stages of development. The challenge is to design in quality and reliability early in the development cycle.
FMEA is a qualitative and systematic tool, to help anticipate what might go wrong with a product or process, and then to create plans to mitigate the risk of failure. Analyzing potential reliability problems early in the development cycle where it is easier to take actions to overcome these issues, thereby enhancing reliability through design.
The early and consistent use of FMEAs in the design process allows designing out failures and producing reliable, safe, and customer pleasing products. FMEAs also capture historical information for use in future product improvement.
Benefits of FMEA
Many garment factories now a days started practicing lean and six sigma concepts to get better quality on low cost and with better efficiency.
FMEA, which has become widespread among Six Sigma practitioners, is a system for analyzing the design of a product or service system to identify potential failures, then taking steps to counteract or at least minimize the risks from those failures. Below are the some key benefits of FMEA
- Captures the collective knowledge of a team
- Improve product/process reliability, quality, and safety.
- A logical, structured process for identifying process areas of concern
- Increase customer satisfaction
- Early identification and elimination of potential product/process failure modes
- Prioritize product/process deficiencies
- Emphasizes problem prevention
- Documents and tracks risk reduction activities
- Provide a focus for improved testing and development
- Reduces process development time, late changes and associated cost.
- Helps to identify critical-to-quality characteristics
- Provides historical records; establishes
- Helps increase customer satisfaction and safety
10 Steps to Conducting a FMEA Study
- Review the product or process: A process flowchart can help identify each component of the product or the process
- Brainstorm possible failures: Go over existing data or documentation for any indications
- List possible effects of the failures: It is possible to have more than one effect per failure
- Assign severity ratings: This is based on the degree of the failure consequences
- Assign occurrence ratings: This is based on how often the cause of the cause will happen
- Assign detection ratings: This is based on the changes that the failure will be detected before the customer finds it
- Calculate the Risk Priority Number (RPN): This is Severity (times) Occurrence (times) Detection
- Design an action plan: Outline which team member will do what on the project
- Take action: Your team should implement the improvements to failures
- Calculate a final RPN: Re-evaluate the possible failures once improvements have been made and determined the improvement’s impact on the new product and customer.
FMEA Procedure, How to conduct FMEA
- Select a process to analyze, design, process, workmanship or any other area? What are the limitations? How detailed should we be? You can use flowcharts to identify the scope and to make sure every team member understands it in detail.
- Select team facilitator and team members. A cross-functional team of people with diverse knowledge about the process, product or service
andcustomer needs. Functions often included are:design, production, quality, testing, R & D, maintenance, store and merchandising.
- Brainstorm the purpose of the product, design or process, requirement of
customer. Alsoidentify the different functions of the area you selected for FMEA
- For each function or process, identify all the ways failure could happen. These are potential failure modes.
- For each failure mode, identify all the consequences on the system, process, related processes, product, and customer requirement or process limitation. These are potential effects of failure.
- Determine how serious each effect is. This is the severity rating, or S. Severity is usually rated on a scale from 1 to 10, 1 being not severe at all and 10 being extremely severe. Ensure the team understands and agrees to the scale before you start.
- For each failure mode, determine all the potential root causes. List all possible causes for each failure mode on the FMEA form.
- For each cause, determine the occurrence rating, or O. This rating estimates the probability of
failureoccurring for that reason during the lifetime of your scope. Occurrenceis usually rated on a scale from 1 to 10, where 1 is extremely unlikely and 10 is inevitable. On the FMEA table, list the occurrence rating for each cause.
- For each control, determine the detection rating, or D. This rating estimates how well the controls can detect either the cause or its failure mode after they have happened but before the customer is affected. Detection is usually rated on a scale from 1 to 10, where 1 means the control is absolutely certain to detect the problem and 10 means the control is
certainnot to detect the problem (or no control exists). On the FMEA table, list the detection rating for each cause.
- Calculate the risk priority number, or RPN (S × O × D).
Alsocalculate Criticality by multiplying severity by occurrence (S × O). These numbers provide guidance for ranking potential failures in the order they should be addressed.
- Ø Identify recommended actions. These actions may be design or process changes to lower severity or occurrence. They may be additional controls to improve detection. Document the changes to the product. Ideally, the results of completed actions will reduce the risk. Assign a team member who is responsible for the actions and target completion dates.