Our company keys everything off an internal job number having child assemblies so I include that info in the program name along with an operation# if needed. I've also used customer contract and vendor/receiver#. Basically whatever it takes to make it unique to that specific part measurement. A batch of parts get temporary serial numbers assigned if needed. Each inspection is saved to the company server in case it ever needs to be reviewed. Once an inspection is finished it is not overwritten - a copy is used instead and renamed for the next part. I also import models using Cad by Reference to lower space requirements on the server. Each company is different, as Nano mentioned. Find a way that makes sense for you and develop a routine you can live with. You might also want to see if your customers have any requirements to keep in mind.
Our company keys everything off an internal job number having child assemblies so I include that info in the program name along with an operation# if needed. I've also used customer contract and vendor/receiver#. Basically whatever it takes to make it unique to that specific part measurement. A batch of parts get temporary serial numbers assigned if needed. Each inspection is saved to the company server in case it ever needs to be reviewed. Once an inspection is finished it is not overwritten - a copy is used instead and renamed for the next part. I also import models using Cad by Reference to lower space requirements on the server. Each company is different, as Nano mentioned. Find a way that makes sense for you and develop a routine you can live with. You might also want to see if your customers have any requirements to keep in mind.
