Oh, you mean the operator needed more training.RetNavy wrote:while i was still working found most of the root causes of problems was the operator screwed up
![rlol "rlol"](./images/smilies/rlol.gif)
Oh, you mean the operator needed more training.RetNavy wrote:while i was still working found most of the root causes of problems was the operator screwed up
You would think that but I work for a company that believes SOMETHING could have been done to prevent the operator from screwing up. You wouldn't believe the man hours that are spent trying to idiot proof processes because an operator screwed up.RetNavy wrote:while i was still working found most of the root causes of problems was the operator screwed up
Right2Carry wrote:You would think that but I work for a company that believes SOMETHING could have been done to prevent the operator from screwing up. You wouldn't believe the man hours that are spent trying to idiot proof processes because an operator screwed up.RetNavy wrote:while i was still working found most of the root causes of problems was the operator screwed up
Hopefully we all appreciate the irony of having wasteful Kaizen meetingsjmra wrote:![]()
ISO9000 and Kaizen meetings - two of my most reoccurring nightmares.
I like this.mloamiller wrote:I've been in software development for about 25 years and many/most root causes turn out to be a "PICNIC" - "Problem In Chair Not In Computer."
This is so true. Also, many companies are obsessed with being ISO and have no idea why they want it. You can have a very effective management program without having to pay a third party to certify your program as ISO.G26ster wrote:Wow, that reference from ISO9000 brought back some real nightmarish memoriesOne of the reasons "root cause analysis" has such poor results in many companies is they simply don't fully grasp the real simplicity of ISO, and create a big, heavy, cumbersome system that works for no one. I'm so glad I'm retired
It's been a while since I was in the business, but at the time if you were doing any type of business with Europe you had to be ISO certified. You couldn't even sit at the table to discuss a bid without the certification. Things may well have changed in the last decade.txcharvel wrote:This is so true. Also, many companies are obsessed with being ISO and have no idea why they want it. You can have a very effective management program without having to pay a third party to certify your program as ISO.G26ster wrote:Wow, that reference from ISO9000 brought back some real nightmarish memoriesOne of the reasons "root cause analysis" has such poor results in many companies is they simply don't fully grasp the real simplicity of ISO, and create a big, heavy, cumbersome system that works for no one. I'm so glad I'm retired
When I first heard of ISO9000 certification, it was described as "It means you have a very well-documented process. Not that you follow it necessarily, just that it's written down."txcharvel wrote:This is so true. Also, many companies are obsessed with being ISO and have no idea why they want it. You can have a very effective management program without having to pay a third party to certify your program as ISO.
Still true, at least in the Medical Device world I work in. If you're not ISO certified, then don't even bother.jmra wrote:It's been a while since I was in the business, but at the time if you were doing any type of business with Europe you had to be ISO certified. You couldn't even sit at the table to discuss a bid without the certification. Things may well have changed in the last decade.