One suggestion that I would make (along with all the other good ideas that have been mentioned) is a logbook of program files, listed by part number and program name, with a sketch (or marked-up print) showing the point locations of the measurement points, and the meaning of the output files. This is particularly true if you are using a less-than-current programming language (we are still using WTutor), or have a a lot of turnover in the department.
Nothing worse than having an operator bring in a part for FirstOff, and finding that not one person in the department knows how to set the part up on the fixture for measurement, or which of 5 programs is the correct one to run, or what the output format means.
We have a programmer who is very VERY good, gone far beyond what I taught him when first hired, but if he's not there to explain what he has done, we're all in the dark.