Running someone else's programs

Hello all, I have recently started running a cmm again after not touching one for 5 years. My manager has told me to run through all the pcdmis programs that already exist and says that none can be trusted as the previous operator was not the best and crashed several times.
What are some good habits for running someone else's programs that cant be trusted?I could rewrite them but i feel i should be able to work through what is already there. I will be using breakpoints before Tip changes in the program and running it super slow. Any other tips for someone jumping back on a machine and dealing with a mess like this

Thanks.

Parents

kingsld1 over 1 year ago

The other thing to keep in mind is how a rewrite will affect downstream operations. I've seen new inspectors change methods and reject fully functional parts. Program may not be the best but it is the way things have been done. At the very least run a few parts with the old program and rerun with the new and "improved" version. Show the reports to your customers to get their buy in before implementing the change.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

kingsld1 over 1 year ago

The other thing to keep in mind is how a rewrite will affect downstream operations. I've seen new inspectors change methods and reject fully functional parts. Program may not be the best but it is the way things have been done. At the very least run a few parts with the old program and rerun with the new and "improved" version. Show the reports to your customers to get their buy in before implementing the change.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data