The Elsmar Cove Forum and Site Map The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page

Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Nonconformance and Corrective Action


The Elsmar Cove Forum SideBar!
Monitor the Forum
Monitor New Forum Posts
New Threads Feeds
RSS FeedRSS Feed
Sponsor Link










$ Contributor Forum Access
Courtesy Quick Links

Links that Elsmar Cove visitors will find useful in your quest for knowledge:


Howard's International Quality Services

Atul's Symphony Technologies

Dave Scott's Scott Quality Solutions

Praxiom Research Group


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest Portal

IEST - Institute of Environmental Sciences and Technology

ASQ - American Society for Quality


All the Important Standards and Related Web Sites in the World
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  #1  
Old 15th March 2000, 04:41 PM
Dan De Yarman
Unregistered Guest

 
Posts: n/a
Question Defect Prevention

What are some easy, yet effective defect prevention methods?

Don't we first have to observe a defect before we can attempt to prevent a similar one? Is it similar to the difference between corrective vs. preventive action; where corrective action is performed to correct a specific problem, and preventive action is performed on similar jobs(procedures, etc.) to prevent the problem from occurring?

Thanks for your help,

Dan
Reply With Quote

Sponsored Links
  #2  
Old 17th March 2000, 03:42 PM
Marc's Avatar
Marc Marc is offline
Your Elsmar Cove Host

Registration Date: Jan 1996
Location: West Chester, Ohio - USA
Age: 59
 
Posts: 15,857
Thanks Given to Others: 1,895
Thanked 1,566 Times in 1,018 Posts
Blog Entries: 4
Karma Power: 605
Karma: 11559
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Send a message via AIM to Marc Send a message via Skype™ to Marc
Yin Yang

Poke Yoke is one 'defect prevention' methodology.
Reply With Quote
Sponsored Links

  #3  
Old 17th March 2000, 05:14 PM
Dan De Yarman
Unregistered Guest

 
Posts: n/a
I've heard the term before, but I'm not sure what it is or how to use it. Could you please describe what it is and how to use it? I guess I'm still not up to speed on all the theoretical aspects of quality control/quality assurance.

Thank you Marc,

Dan
Reply With Quote
  #4  
Old 17th March 2000, 05:28 PM
Marc's Avatar
Marc Marc is offline
Your Elsmar Cove Host

Registration Date: Jan 1996
Location: West Chester, Ohio - USA
Age: 59
 
Posts: 15,857
Thanks Given to Others: 1,895
Thanked 1,566 Times in 1,018 Posts
Blog Entries: 4
Karma Power: 605
Karma: 11559
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Send a message via AIM to Marc Send a message via Skype™ to Marc
Yin Yang

See http://Elsmar.com/pdf_files/ - file name: Poka_yoke_B.pdf
Reply With Quote
  #5  
Old 17th March 2000, 06:21 PM
Laura M's Avatar
Laura M Laura M is offline
Courtesy Access

Registration Date: Aug 1999
Location: Rochester, NY US
 
Posts: 759
Thanks Given to Others: 3
Thanked 17 Times in 15 Posts
Karma Power: 70
Karma: 656
Laura M is appreciated, and has over 500 Karma points.Laura M is appreciated, and has over 500 Karma points.Laura M is appreciated, and has over 500 Karma points.Laura M is appreciated, and has over 500 Karma points.Laura M is appreciated, and has over 500 Karma points.Laura M is appreciated, and has over 500 Karma points.
Send a message via AIM to Laura M Send a message via Skype™ to Laura M
Dan,
Lot's of examples come to mind from my mmanufacturing days. Errorproofing is another term.
- If a part can be designed non-symmetrical to avoid accidentaly misassembly. (upside down or backwards - offsett locating pins)
- If not by design, then is there a feature on the part you can use to design the nest so it can only be assembled one way.
- Color coding 2 different part numbers that are similar for correct assembly, and using light detection to verify the right part. Or better yet, can the designs be reduced to one?
- Having rejects pass through a reject chute (with detection verification) before the stand will cycle again.

Haven't referenced the pdf files as yet, may be redundant...if I think of more, shall I let you know? Of course to be considered "prevention" these activities should take place before a reject is produced, but are just as useful as corrective action.
Reply With Quote
  #6  
Old 27th June 2000, 02:29 PM
Marc's Avatar
Marc Marc is offline
Your Elsmar Cove Host

Registration Date: Jan 1996
Location: West Chester, Ohio - USA
Age: 59
 
Posts: 15,857
Thanks Given to Others: 1,895
Thanked 1,566 Times in 1,018 Posts
Blog Entries: 4
Karma Power: 605
Karma: 11559
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.Marc is appreciated, and has over 1700 Karma points.
Send a message via AIM to Marc Send a message via Skype™ to Marc
Yin Yang

ISO 9001 requires that you have procedures for identifying and eliminating the causes of actual or potential nonconformities in your products, processes, or the quality system.

Product and service nonconformance reports are the source of information leading to the corrective action that you should take to prevent the same or a similar problem from recurring. Situations may include the following:

Failures, malfunctions or nonconformities in incoming materials, processes, tools, equipment or facilities needed to produce your product or deliver your service, including the equipment and systems you use;
  • Inadequate or non-existent procedures and work instructions;
  • Non-compliance with procedures or work instructions;
  • Inadequate process control;
  • Poor scheduling;
  • Lack of training;
  • Inadequate working conditions;
  • Inadequate resources, (human or material);
  • Inherent process variability.

These conditions may be found by reviewing:
  • Inspection and test records;
  • Nonconformance reports;
  • Observations during process monitoring;
  • Audit observations;
  • Field, service, or customer complaints;
  • Regulatory authority or customer observations;
  • Observations and reports by your personnel;
  • Sub-contract problems;
  • Management review results;
  • Inherent process variability.

The same causes and conditions may indicate where preventive action is needed and where patterns or trends that may indicate the potential for nonconformities should be investigated. The degree of corrective or preventive action taken depends upon and is directly related to the risk, size and nature of the problem and its direct effects on product quality.

Corrective and preventive action reports should be part of the management review process.

Corrective action

Corrective action is taken to eliminate the cause of an existing nonconformity or other undesirable situation. There is a distinction between "correction" and "corrective action". Correction refers to repair or rework as is done to eliminate a nonconforming product situation whereas corrective action is taken to prevent recurrence of the situation.

Your procedures should describe how to implement corrective action, how it should be carried out and the effectiveness of the results verified.

It is important to implement procedures to deal with nonconformities discovered in any products that have already been delivered. You must determine whether the nonconformity is an isolated or a repetitive problem, and any actions to be taken, if necessary.

Corrective action to eliminate the cause of a nonconformity is not necessarily required every time or for isolated incidents of a minor nature, but a periodic analysis of nonconformance reports should be done to identify opportunities for process improvement.

Preventive action

It should be noted that corrective action is taken after nonconformities are identified. Preventive action is taken when a potential nonconformity is identified as a result of the analysis of records and other relevant sources of information, such as the following:
  • Statistical process control documents;
  • Customer complaints;
  • Review product, process and quality system information,
  • Risk analysis and risk assessment of products and processes.

Records relating to the product performance should be analyzed regularly, to detect trends and to identify areas of risk that may lead to nonconformities. The analyses should also determine how to prevent any identified potential problems.

Information on preventive action taken must be part of your management review to maintain and improve your quality system.

Preventive action is taken to prevent occurrence whereas corrective action is taken to prevent recurrence of a situation or nonconformity. Preventive action is not necessarily required for all the potential nonconformities you have identified, but it should be considered if there are opportunities to improve your quality management system.

From: www.isoman.com/CorAct.htm

[This message has been edited by Marc Smith (edited 27 June 2000).]
Reply With Quote
  #7  
Old 18th August 2000, 02:40 AM
Derek
Unregistered Guest

 
Posts: n/a
BIG Smile

The easiest defect prevention approach I have used (for mass production type manufacturing is to:
1. Record all defects part numbers, quantities and reason for defect. (You probably already record this info or similar).
2. Each month, group all the defect information by "reasons for defect" and the number of occurances. A pareto chart is the ideal. It should show what defect type occured the most.
3. Talk with all relevant people associated with the process causing the highest defect for the month, to determine the root cause. this includes engineers, operators, supervisors, subcontractors, etc. 4. Develop an implementation plan to prevent the defect problem from recurring. (This must eliminate the root cause).
5. Future months pareto charts should show a reduction in the defect.
6. You know when you are winning when the smallest reason for defects become your highest reason.
I have tried this system on chrome/gold/zinc plating lines with enourmous success.
Reply With Quote
  #8  
Old 18th August 2000, 05:04 PM
Jim Evans
Unregistered Guest

 
Posts: n/a
FEMAs are another potential source of preventive actions.

Jim
Reply With Quote
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Forum > Common Quality Assurance Processes and Tools > Nonconformance and Corrective Action

Bookmarks


Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
Completing 8D in the section "System Prevention Action To Prevent Recurrence" QC Lifer Customer Complaints including ISO 10002 7 27th September 2009 04:45 PM
Root cause analysis on non-defect defect reports? Momazona Problem Solving, Root Cause and Failure Analysis 1 10th April 2008 03:39 PM
Zero Defect Dating JRKH Coffee Break and Water Cooler Discussions 37 9th February 2007 09:22 AM
Design and Development - Defect Prevention Plan sasiengineer Design and Development - Process and Product 10 11th October 2006 02:25 AM
What is an organizational defect prevention plan? sanmint Documentation Control Systems, Procedures, Forms and Templates 3 14th April 2005 02:02 PM



The time now is 03:33 PM. All times are GMT -4.
The time zone can be changed in your UserCP --> Options.



   

All Y'All Come Back Now, Y' Hear?

Made With A Mac! FreeBSD OS Powered by Apache!
Using php4 Forums provided and maintained by Marc Smith Database by MySQL

FAIR USE and CORRECTNESS NOTICE: This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe herein constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit to those who have expressed a prior interest in receiving the included information for research and educational purposes. For more information go to: http://www.law.cornell.edu/uscode/17/ If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. In addition, I do not guarantee the correctness of the content. The risk of using content from the Elsmar Cove web site and forums remains with the user/visitor.

Responsibility Statement: Each person is responsible for anything they post in the Elsmar Cove forum. Neither I, Marc Timothy Smith, nor any of the forum Moderators, are responsible for the content of posts people make. Liability for post content resides with the poster as does interpretation and/or acceptance and/or use of advice by the reader.

Complaints: If you have a complaint with a post in a forum discussion thread, including Content in general, fighting, flaming, copyright infringement, defamation and/or 'slander', please use the 'Report This Post Report This Post Button button which appears at the top of every post in every thread.

Site courtesy of:
Marc Timothy Smith - Cayman Business Systems, 8466 Lesourdsville-West Chester Road, West Chester, Ohio 45069-1929 - USA
(513) 341-6272

To contact me, click the Google Voice link below, enter Your Name and Your Phone Number and Google will ring your phone and connect you for free!

The Elsmar Cove Web Site is *CopyFree*
no new posts