barb butrym
Quite Involved in Discussions
The thing about preventive Action is that nearly everyone does it, but 99% don't document it well.
I have difficulty seeing how you can put that into an existing process. AND I use process flow diagrams ALL the time. Seems to me, if you can predict it, then its corrective action (poka-yoke) not preventive. I see that fitting nicely into a flow diagram, but preventive is yet another animal. Preventive is many things, your process engineering group does it all the time I bet. As do task teams and all good managers. AND the best to capture is the operator level stuff.
Some registars just tell you PA is a long term fix to correct the root cause, and CA the short term to fix the problem at hand. That if you do CA correctly, then PA is the result. I disagree, but depending on the registrar I am representing, I have to adjust that a bit.
As a consultant I approach it for the prevention of potential issues...a common sense approach that leads you onto the path toward Continuous Improvement.....which now will fit nicely into the '2000' revision, even though I have been doing it for years. CA still addresses root cause of issues at hand.
I have difficulty seeing how you can put that into an existing process. AND I use process flow diagrams ALL the time. Seems to me, if you can predict it, then its corrective action (poka-yoke) not preventive. I see that fitting nicely into a flow diagram, but preventive is yet another animal. Preventive is many things, your process engineering group does it all the time I bet. As do task teams and all good managers. AND the best to capture is the operator level stuff.
Some registars just tell you PA is a long term fix to correct the root cause, and CA the short term to fix the problem at hand. That if you do CA correctly, then PA is the result. I disagree, but depending on the registrar I am representing, I have to adjust that a bit.
As a consultant I approach it for the prevention of potential issues...a common sense approach that leads you onto the path toward Continuous Improvement.....which now will fit nicely into the '2000' revision, even though I have been doing it for years. CA still addresses root cause of issues at hand.