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 3rd January 2003, 10:34 AM
Stormy Stormy is offline
Getting Involved (6 to 9 Posts)

Registration Date: Sep 2002
Location: Gimli, Manitoba, Canada
Age: 37
 
Posts: 6
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 30
Karma: 10
Stormy has less than 100 Karma points so far.
Question Priorizing Non-conformances - What is the best way?

Good Day,

I am wondering if anyone has suggestions on how to priorize non-conformances? I have looked in the other forums at this site, but I haven't found anything about priorizing ncr's.
My goal is to minimize the amount of corrective actions that are dealt with. At this time we use a single form for NCR/corrective actions and we address almost every ncr with a corrective action. This method allowed us to pinpoint where our repeatable processes were, and to pinpoint any missing instructions that would deal with regular non-conformances. But we are now at the point that we feel we should streamline the system, and concentrate on the larger issues.

I hope I haven't confused everyone with this description.

So if anyone has any suggestions, they would be appreciated.

Thanks.
Reply With Quote

Sponsored Links
  #2  
Old 3rd January 2003, 10:43 AM
Mike S. Mike S. is offline
An Early 'Cover'

Registration Date: Mar 2002
Location: East Coast US
 
Posts: 1,773
Thanks Given to Others: 24
Thanked 51 Times in 39 Posts
Karma Power: 103
Karma: 1849
Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.Mike S. is appreciated, and has over 1700 Karma points.
Default

Stormy,

Your problem is a common one -- one that most companies have had to deal with already, or soon will have to deal with. In fact, this issue has been discussed several times here in the last year. Use the search function to look for threads with the words "corrective action" or "CAR", etc. and I know you will find tens of posts with many opinions. If memory serves (not a given!), I think the consensus was that not every NC requires a formal CA; that sometimes "human error" is an acceptable cause; and that prioritization is usually based on risk of recurrance and potential impact.

If you can't find what you're looking for in a search, write back and ask some specific questions and you'll get answers.
__________________
Mike S. ("Gun Nut")
And they ask me why I drink....
Reply With Quote
Sponsored Links

  #3  
Old 8th January 2003, 11:31 AM
Tim Douty
Unregistered Guest

 
Posts: n/a
Default Prioritizing Nonconformances

Stormy,
I am sure you take on the major nonconformances before the minors. My rule of thumb is this - each nonconformance is prioritized by the importance to the end product, I work backwards from there. I base alot of priority on our Lead Auditors preferences as well. I tackle the Lead Auditor's "hot buttons" first! I may be different than most, but I write a corrective action for each nonconformance. I feel it may be more cumbersome up-front, but later, it helps track the entire process - sort of "cradle to grave". I hope this aids to your inquiry.
Tim
Reply With Quote
  #4  
Old 28th January 2003, 03:02 PM
Stormy Stormy is offline
Getting Involved (6 to 9 Posts)

Registration Date: Sep 2002
Location: Gimli, Manitoba, Canada
Age: 37
 
Posts: 6
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 30
Karma: 10
Stormy has less than 100 Karma points so far.
Default

Good Day,

Ted, thank you for responding.

This is my problem: we haven’t yet defined what constitutes a major vs. a minor. You said prioritize by the importance to the end product, but what is your definition of what is important to the end product? What are the criteria that you use, and how did you choose what was the most important factors?

In a different thread in this category a guy by the name of Ken Madder wrote “They were treating every cause as a Special Cause when in fact, most were Common Cause”. I would love to know how he defines Special vs. Common.

I am beginning to prioritize some of our NCR’s, by defining non-conformances that are repeatable up to a certain quantity, and recording those on a data excel sheet. The data is then evaluated monthly. This is where I have trouble. I can use total footage & the amount of the occurrences to decide which repeatable is causing the most non-conformances, and begin a non-conformance report on the highest footage and/or highest occurrence. But in doing this am I missing the non-conformances that are important to the customer? And it isn’t clear how I can carry this type of prioritizing into the non-conformance process?

So I am still searching for clarity, I guess.

But thanks again for replying.
Reply With Quote
  #5  
Old 28th January 2003, 03:04 PM
Stormy Stormy is offline
Getting Involved (6 to 9 Posts)

Registration Date: Sep 2002
Location: Gimli, Manitoba, Canada
Age: 37
 
Posts: 6
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 30
Karma: 10
Stormy has less than 100 Karma points so far.
Default

Sorry Ted, I wrote Tim, but I meant Ted.
Reply With Quote
  #6  
Old 28th January 2003, 03:05 PM
Stormy Stormy is offline
Getting Involved (6 to 9 Posts)

Registration Date: Sep 2002
Location: Gimli, Manitoba, Canada
Age: 37
 
Posts: 6
Thanks Given to Others: 0
Thanked 0 Times in 0 Posts
Karma Power: 30
Karma: 10
Stormy has less than 100 Karma points so far.
Default

or vice versa (I think I will stop now)!!
Reply With Quote
  #7  
Old 28th January 2003, 05:25 PM
M Greenaway's Avatar
M Greenaway M Greenaway is offline
Courtesy Access

Registration Date: Dec 2001
Location: England
 
Posts: 1,643
Thanks Given to Others: 10
Thanked 63 Times in 44 Posts
Karma Power: 80
Karma: 794
M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.M Greenaway is appreciated, and has over 700 Karma points.
Default

Stormy

The process is quite simple (well simple to outline).

Log every complaint in some form of database, and assign a code either to the reported complaint, or to the root cause if you wish to spend time at this point investigating every root cause (I would suggest you do personally).

Take the data from a suitable period of time that gives you a sufficient chunk of information, maybe 3 months. Count the fault or cause codes, arrange the counts in descending order, then simply prioritise your action on the most common occuring reported fault or cause.

This approach is OK, but slightly flawed if different complaints or products have different costs associated with them. Arguably a better approach would be to establish the cost of the complaints, and then target actions to the most costly.
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
Do ALL non conformances have to be documented? LexieB Nonconformance and Corrective Action 1 2nd September 2009 06:08 PM
Non-Conformances in a Service based industry with no product debbie135 Service Industry Specific Topics 9 18th June 2008 04:25 AM
Internal Audit Concerns including Escalation of Non-Conformances chaosweary ISO 19011 and ALL Auditing Discussions 6 16th August 2007 11:33 AM
One weakness of non-conformances is the poor writing marilu44 ISO 14001 and Environmental Related Standards 10 2nd January 2007 05:40 AM
19011 - Reporting Non-conformances: Grading of findings begum ISO 9001 - Quality Management Systems Standard 1 30th September 2005 02:59 AM



The time now is 12:46 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