CMM Operator Training

How do you train your operators? Any advise is welcome. Don't be a turd.

We have been intermittently slow at work so I have been building basically a curriculum to train new operators (we are expecting to hire people at the beginning of the year).

My "Curriculum" is basically just notes on how to run the CMM, but with some pictures and a few step by step guides. I have used one of my hand mic guys as a path finder/Guiney pig and it seems like every time I get done with a training section there are so many things that I have left out that he immediately stumbles over.

Idk I am pretty good at explaining things in person but putting them down on paper is a bit harder.

Parents

Cris_C over 3 years ago

I never liked tests. It always made people nervous. I would give my trainees a simple Go/NoGo gage and have them measure it or write a program to measure it. Then I would start giving them simple parts. It made them think, it allowed me to see how they wrote code, and created a more fluid way of learning. Now, everyone I trained had experience checking parts to a print without a CMM. So once I explained features, it turned into more or less knowing what needed to be done and just showing how to do it with the software. I also use non technical terms at first and work in the technical as we progress i.e.: In the beginning, how are you looking at the part, from which direction, when you are measuring that? Later on, what workplane are you in when you are dimensioning those features?

Sounds like a great approach. Especially the part about "...once I explained features, it turned into more or less knowing what needed to be done and just showing how to do it with the software". It is easy for someone getting started to worry too much about the process more than the goals and objectives. I always hated that part of learning many things in school. The teachers would drill and drill on how to do something long before they explained why you would do it in the first place.

Once you have a general idea of what you want to accomplish and the steps you would take to get there, then you can worry about the best way to go about it. Plus in this day and age, you can look up a lot of technical stuff on your own. Maybe even on a online forum!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Cris_C over 3 years ago

I never liked tests. It always made people nervous. I would give my trainees a simple Go/NoGo gage and have them measure it or write a program to measure it. Then I would start giving them simple parts. It made them think, it allowed me to see how they wrote code, and created a more fluid way of learning. Now, everyone I trained had experience checking parts to a print without a CMM. So once I explained features, it turned into more or less knowing what needed to be done and just showing how to do it with the software. I also use non technical terms at first and work in the technical as we progress i.e.: In the beginning, how are you looking at the part, from which direction, when you are measuring that? Later on, what workplane are you in when you are dimensioning those features?

Sounds like a great approach. Especially the part about "...once I explained features, it turned into more or less knowing what needed to be done and just showing how to do it with the software". It is easy for someone getting started to worry too much about the process more than the goals and objectives. I always hated that part of learning many things in school. The teachers would drill and drill on how to do something long before they explained why you would do it in the first place.

Once you have a general idea of what you want to accomplish and the steps you would take to get there, then you can worry about the best way to go about it. Plus in this day and age, you can look up a lot of technical stuff on your own. Maybe even on a online forum!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data