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 21st November 2001, 02:32 PM
Ace's Avatar
Ace Ace is offline
Registered Visitor

Registration Date: Oct 2001
Location: CA USA
 
Posts: 15
Thanks Given to Others: 1
Thanked 2 Times in 1 Post
Karma Power: 33
Karma: 20
Ace has less than 100 Karma points so far.
Cool Corrective Action and Preventive Action clauses - ISO 9001 - Corrective Action

I need some advice petaining to the ISO 9001:1994 Corrective Preventive Action clause.

First - some background information.

We recently endured our registration surveillance audit and had a non-conformance identified with our customer concern process.

Although our database files identified root cause, CA, & PA, the auditor stated we had a non-conformance because our notes were not detailed enough. For example - we had a pc board returned by a customer and after our analysis found it had a hard failure.

The database was documented to show root cause as: Hard Failure
Corrective Action: Replace PC board
Preventive Action: Go thru inventory, retest, and purge per established documentation.

My questions are:

1. Is there an ISO requirement that mandates how detailed our documentation should be?

2. Would I be justified in challenging this non-conformance issued by the auditor?

Thanks in advance for any advice provided.

Redolpho (ACE)
Reply With Quote

Sponsored Links
  #2  
Old 21st November 2001, 02:40 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
Default

I would be looking for the documentation to show what caused the hard failure. The information you gave would be all corrective to me - and really all 1st step of corrective which basically establishes the scope of the problem. Corrective action should address why it was a hard failure. Preventive gets alot of discussion in other threads, but I always look at if there was something else to be learned from the failure that hasn't happened yet - possibly on another product line. Or maybe you determine there were 4 potential root causes. If you implement changes to address all 4, then 3 are "preventive" because they haven't happend yet.

In answer to your direct question:
1 - No
2 - No
Reply With Quote
Sponsored Links

  #3  
Old 21st November 2001, 03:38 PM
Al Dyer
Unregistered Guest

 
Posts: n/a
Default

I believe that the nonconformance as issued as "not detailed" enough could be challanged.

What I would not agree with is the content of the answers for correcive and preventive action.

Maybe if you posted the root cause to the cove we might be better able to help.
Reply With Quote
  #4  
Old 21st November 2001, 07:32 PM
David Mullins's Avatar
David Mullins David Mullins is offline
Aussie Bloke

Registration Date: Nov 1999
Location: Adelaide, South Australia, Australia
Age: 47
 
Posts: 495
Thanks Given to Others: 0
Thanked 13 Times in 8 Posts
Karma Power: 51
Karma: 84
David Mullins has less than 100 Karma points so far.
Default look out!

1. You haven't stated the dispositioning of the failed board.

2. checking your inventory goes a VERY small way in terms of preventive action. PREVENT - prevent it happening again, reduce the likelihood of it happening again, decide that this is an acceptable failure rate as it is technologically and financially not feasible to improve.

3. At the moment you're looking for a lazy (non-quality) exit - are you a manaufacturing manager?

PS - Who cares if it's ISO if it makes good sense!
__________________
Aussie Bloke
Reply With Quote
  #5  
Old 22nd November 2001, 06:19 PM
Ace's Avatar
Ace Ace is offline
Registered Visitor

Registration Date: Oct 2001
Location: CA USA
 
Posts: 15
Thanks Given to Others: 1
Thanked 2 Times in 1 Post
Karma Power: 33
Karma: 20
Ace has less than 100 Karma points so far.
Exclamation

Dave,

Apparently you missed the bottom line to my inquiry. I wasn't writing in to get lectured on ISO's terms and definitions.

Simply stated, we complied with our documentation in stating root cause, CA & PA on our database records. I was inquiring if there was any ISO requirement dictating how specific we had to be with the amount of details we record on our records.

My job title has no bearing on the question at hand and I certainly didn't appreciate your personal remarks. If you can't keep it professional, why bother responding.

Go have yourself a great day!!!!!

Rodolfo
Reply With Quote
  #6  
Old 22nd November 2001, 07:26 PM
David Mullins's Avatar
David Mullins David Mullins is offline
Aussie Bloke

Registration Date: Nov 1999
Location: Adelaide, South Australia, Australia
Age: 47
 
Posts: 495
Thanks Given to Others: 0
Thanked 13 Times in 8 Posts
Karma Power: 51
Karma: 84
David Mullins has less than 100 Karma points so far.
Default Landin' On Both Feet - In Mouth

Quote:
Originally posted by Ace
Apparently you missed the bottom line to my inquiry. I wasn't writing in to get lectured on ISO's terms and definitions.
You said:
"My questions are:
1. Is there an ISO requirement that mandates how detailed our documentation should be?
2. Would I be justified in challenging this non-conformance issued by the auditor? "

1. You have to have enough detail to demonstrate compliance, which apparently you didn't.
2. I'm guessing you lost the argument with the auditor, you can run the argument through the registrar and higher, but this is really a last resort scenario. I'd suggest you just fix it.


You said:
"Simply stated, we complied with our documentation in stating root cause, CA & PA on our database records. "
and,
"the auditor stated we had a non-conformance because our notes were not detailed enough"

I think these are contradictory statements. If you complied, you wouldn't have got pinged.


I think my previous advice was very sound.
Sorry about the wise crack - Experience indicates these things to be generally true.

__________________
Aussie Bloke

Last edited by David Mullins; 22nd November 2001 at 08:37 PM.
Reply With Quote
  #7  
Old 26th November 2001, 01:47 AM
Ace's Avatar
Ace Ace is offline
Registered Visitor

Registration Date: Oct 2001
Location: CA USA
 
Posts: 15
Thanks Given to Others: 1
Thanked 2 Times in 1 Post
Karma Power: 33
Karma: 20
Ace has less than 100 Karma points so far.
Default Re: ISO Clause 4.14

Thanks for the advice David, and I apologize for my defensive posture.

Rodolfo
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
High Level CAPA (Corrective Action Preventive Action) SOP Example Needed brecksnowshoer Nonconformance and Corrective Action 6 31st October 2009 10:45 PM
Complaints & CAPA's (Corrective Action Preventive Action) for Clinical Trials PPcricket ISO 13485 - Medical Devices - Quality Management Systems 4 10th August 2009 09:35 AM
Tracking Corrective Action - Preventive Action - Simple Product/Documentation Change craig-c Nonconformance and Corrective Action 1 27th November 2006 05:35 PM
CAR/PAR (Corrective Action / Preventive Action) process flow - Seeking example Bpoole Nonconformance and Corrective Action 7 31st October 2006 05:23 AM
CAPA (corrective action preventive action) Effectiveness - Medical Device Industry jampot Nonconformance and Corrective Action 3 26th February 2006 04:22 PM



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