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 > Elsmar Cove Quality Assurance and Business Standards Wiki

Related






Corrective Action

From Elsmar Cove Quality Assurance and Business Standards Wiki

Corrective Action: Also known as a CA, Corrective Actions are actions taken to eliminate the root cause of an existing nonconformance and to prevent its reoccurrence.

Preventive Action: Actions taken to eliminate a 'potential root cause' to a potential problem that has not occurred.

ISO 9001:2000 clauses 8.5.2 and 8.5.3 require that you identify areas for both within your organization. The CA portion deals with items such as customer complaints received, nonconformances uncovered as part of internal quality audits, or received incoming materials not meeting specifications for example. These problems exist in the here and now and require corrective action to prevent their reoccurrence. What do you do to correct the issues and how do you document what you did? Did it work (close the loop)? Do you review this as part of Management Review?

Preventive Action is a more difficult idea to grasp for most (maybe because we tend to put out fires rather than prevent them) and can be accomplished in various ways. I like to think of it this way. If a process or system is in a state of statistical control, does a problem exist? Sometimes but not always. There is natural variation in any process or system, but their output may not meet our desired expectations. A process not meeting our expectations may need refining, but not necessarily correcting. We often think something 'must' be wrong when we don't get the results we hoped for. There is a significant difference in a process not meeting expectations and a process not producing to specification. This misunderstanding of system output usually leads to a landslide of issuing Corrective Action for every problem encountered. Does your organization make defective products occasionally? Mine does. Should I create a Corrective Action Report for each defective product especially if some level of defects is to be expected (the system will never produce zero defects)? No. Doing so would bog down the CA process and creates another set of problems (missing CA reports, CA reports not filled correctly, duplicate CAR for the same problem). Not all problems are Corrective Action opportunities. Some are Preventive Action opportunities. This example is more typical of a Continuous Improvement process with Preventive Action ties. Give thought to which situation you have and take actions commensurate with risks encountered. I hope this helped.


For a 'definitive' discussion, see: Corrective Action vs. Preventive (Predictive) Action - A Definitive Discussion

The Elsmar Cove Wiki SideBar!
Sponsor Links





$ Contributor Forum Access

The time now is 01:43 AM. 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*