Countermeasure For CMM Operator Error

[Pudge]

Had an issue with one of the CMM Operators deleting a feature on a program and allowing production to run all weekend with a NG feature. It is now my job to provide a countermeasure to guarantee there will be no reoccurence. Management is asking for a true pokeyoke that will not allow this mistake to be made. Any info is greatly appreciated.

 

[somashekar]

Had an issue with one of the CMM Operators deleting a feature on a program and allowing production to run all weekend with a NG feature. It is now my job to provide a countermeasure to guarantee there will be no reoccurence. Management is asking for a true pokeyoke that will not allow this mistake to be made. Any info is greatly appreciated.

Authorization and competency... and password protection for edit program.
Did he have these ? Was he qualified for this ?
You simply have to use technology with right authorization.

 

[Pudge]

Authorization and competency... and password protection for edit program.
Did he have these ? Was he qualified for this ?
You simply have to use technology with right authorization.

Yes....he is completely competent in this program...he makes changes constantly....just so happen to miss this one

 

[somashekar]

His acts as you describe added with the all weekend production run without ongoing verification, does not justify the completely competent status you give him.
How did you determine this competency in view of you saying that he makes changes constantly ?
Who is the next up in the reporting ? What is his intervention in program editing and approval ?
Having a high end machine like a CMM, the key to pokeyoke is the way you talk with the CMM.
Have a relook at your competency evaluation process, with all due respects to your CMM operator.
See if you can introduce something like this in your CMM program ...
Program edit >> Save >> after 10 pcs CMM stops and asks for change authentication >> authorized person approves >> machining continues.

 

[Pudge]

His acts as you describe added with the all weekend production run without ongoing verification, does not justify the completely competent status you give him.
How did you determine this competency in view of you saying that he makes changes constantly ?
Who is the next up in the reporting ? What is his intervention in program editing and approval ?
Having a high end machine like a CMM, the key to pokeyoke is the way you talk with the CMM.
Have a relook at your competency evaluation process, with all due respects to your CMM operator.
See if you can introduce something like this in your CMM program ...
Program edit >> Save >> after 10 pcs CMM stops and asks for change authentication >> authorized person approves >> machining continues.

His competency is based on 10 yrs of service and experience. Maybe I wasn't clear on the issue. He was running a program and just so happened to delete a feature on the program. So for the rest of the weekend the feature was not measured in the program. This issue was caught Monday morning when he returned to work. I need help in determining a way to prevent this in the future. Thanks,