Make a function that can measure dimensions in a 3-model like the same way as CAD-software can. Only to know how big some geometry is, or to check something. This can be usefull, because nowadays many drawings are minimum dimensions drawings.

Add a key in the calibration area where you can save and import a list of angles because every time you create a probe you have to start from zero.

Looking for a way to populate results in specific custom order in Excell based first article travelers.

Now PC-DMIS remembers only measurements made on the last part. A lot of time I need a complete data of part that was measured in past. It could be set to remember last xx measured parts. I know that Calypso has this feature.

Add options to construct Datum features in such a way that they reflect the standard.

Example - Datum A is a Plane, and Datum B is a cylinder bore nominally perpendicular to the plane.

As per both ISO and ASME standards, Datum B would be a Max Insc Cylinder Perpendicular to Dat A.

It's easy enough to construct a Max Insc cylinder, but this wouldn't be forced perpendicular to the plane, currently you'd have to measure it as a series of circles, then construct a Max Insc Circle in the correct workplane after levelling to Dat A.

See bottom image for example (image shows shaft not bore but principle is the same).

Like wise construct a datum plane from a measured plane relative to another feature (Top image)

Your program is finished but some points or features were added and their out of numerical order.

A Re-number feature would put them all in ascending order.

This would save lots of time for some parts. Think of it like the shield from the Dune movies. The clearcube should form around the part

I would like the ability to create an attribute dimension, similar to a "Keyed In" dimension that has a non-numerical value of either "PASS" OR "FAIL" and the ability to pass that result to reports or Excel exports.  Currently, all defined dimensions are numerical.

Autocalibration Currently does not remeasure failed tips. My suggestion is to implement a feature within the Autocalibration routine that allows it to remeasure the tips that failed the standard deviation. As well as adding a feature within the autocalibration code that allows you to select the calibration sphere when the qualtool has been moved only. This would be used for all autocalibration within that code as well but only selected at the beginning of the program to ensure correct vector and size are used. My expectation if this gets implemented is when i leave on Friday, i can start the autocalibration routine and come back on Monday with no tips that have been outside of the standard deviations.