|
This thread is carried over and continued in the Current Elsmar Cove Forums 
|
|
|
This thread is carried over and continued in the Current Elsmar Cove Forums
|
The New Elsmar Cove Forums
|
 The New Elsmar Cove ForumsThe Elsmar Cove Forums
 Nonconformance and Corrective Action Systems
 Preventive Action
|
 UBBFriend: Email This Page to Someone! |
next newest topic | next oldest topic |
| Author | Topic: Preventive Action |
|
K Marie Lurker (<10 Posts) Posts: 2 |
posted 22 August 2001 04:31 PM
   
We have been ISO certified since 1997 and are in the midst of AS9100 certification. We do everything pretty well, except preventive actions. We do plenty of activities that could be classified as preventive actions but aren't sure how to document them or how to gather all the info in one place. Any suggestions? IP: Logged |
|
Graeme Forum Contributor Posts: 58 |
posted 22 August 2001 10:48 PM
You have asked a question on which there are almost as many opinions as there are auditors... For a start, look at this discussion in the Continuous Improvement section: https://elsmar.com/ubb/Forum32/HTML/000027.html The calibration lab I am working with had the same problems when getting ready for our registration. As for documenting, we handle them just about the same as corrective actions. The only real difference is that instead of correcting a past problem and fixing its cause, we are trying to prevent a potential future problem. The really hard part for us is deciding what is actually a preventive action and what is simply a process improvement. For instance, late last year we started using a computer-based calibration record-keeping and management system. We decided that was a process improvement in that it made our internal processes more efficient. Some months later we decided to get an additional specialty printer for the system, to gain the capability to print calibration labels from the system data instead of hand-writing them. We decided that is a Preventive Action because it eliminates the possibilty that the date on the label is different from the date in our computer records. It had not yet been a problem for us, but we knew it had been a problem for other similar organizations. Graeme [This message has been edited by Graeme (edited 22 August 2001).] IP: Logged |
|
E Wall Forum Contributor Posts: 114 |
posted 23 August 2001 08:08 AM
In our system we describe: The Preventive Action System consists of serveral subsystems. Preventive actions may be initiated as result of process trend analysis, managment-designated roadmaps, staff meetings, internal audit feedback (observations)or preventive maintantenance. There is more info included, but that sums up the system. IP: Logged |
|
Alf Gulford Forum Contributor Posts: 73 |
posted 23 August 2001 12:40 PM
K Marie- Have you tried creating a procedure that defines some of the PAs common to your business? These could include, in addition to Graeme's & Eileen's items: Design Reviews (documented in your project folder), Opening packages ready for shipping to inspect for missing/incorrect parts, and Checking stored product for deterioration. All of these can be easily defined and reported to management at appropriate (monthly? quarterly?) periods as preventive action. Is this the kind of suggestion that's helpful or did I go off course again? Alf IP: Logged |
|
K Marie Lurker (<10 Posts) Posts: 2 |
posted 23 August 2001 12:47 PM
Your responses are definitely helpful. However, the biggest questions still remain: who, in your company, compiles the preventive action information, in what manner, how is it presented to management? IP: Logged |
|
E Wall Forum Contributor Posts: 114 |
posted 23 August 2001 01:16 PM
I missed that before. We use an agenda (and a measureables checklist) that is follwed and 'Preventive Action' is a discussed topic. The improvement teams leader provides information updates, as well as information from Supervisors (or themselves if they ask to attend), Dept Engineers, Managers and other key folks. Basically the onus is on the department staff & Manager. They discusses what is relevant in their department prior to the management meeting, and the dept rep that attends contributes as "preventive action" is discussed. IP: Logged |
|
CarolX Forum Contributor Posts: 124 |
posted 23 August 2001 01:29 PM
K Marie, 2 items we identify as PA are ECO's and the suggestion box. As for reporting to upper managment - QA reports the number of ECO's issued weekly. Suggestions are reviewed weekly by the VP. Hope this helps IP: Logged |
|
Alf Gulford Forum Contributor Posts: 73 |
posted 23 August 2001 03:35 PM
Some PAs aren't reported because they're just business as usual (and some are never reported because they just don't get documented). When we randomly select a full-up unit that's ready to ship, and assemble and test it for function and correct parts/packaging, a formal report of the results is sent to all upper management, including the Management Rep who includes the info in the Management Review. Doing stuff like this can be an expensive hassle, but it's sure helped us. Alf IP: Logged |
All times are Eastern Standard Time (USA) | next newest topic | next oldest topic |
  |
|
Please Visit the new Elsmar Cove Forums! All these threads are there and much more!
Main Site Search 
