Extend Summary mode as more than just a tree view that requires expanding. Make several of the most common features easily accessible (i.e. hits on a circle with +/- buttons, check box for find hole routine in circles, show the features used in an alignment, etc.)

lntroduce self learning packages where a new beginner can learn at home on a simulated software. Step by step training with a library of models from manual alignment to advance features.

Just like MASTERCAM which has excellent training package

a quicker more accessible option for reporting

We would like to be able to pattern around a specified feature as oppose to having to move the datum to that location, as pattern only operates around the datum.

Without having cylinder length in the Measurement Strategy Editor of Widget, it usually leaves us no choice but going into properties on each feature when we create a pattern and changing each one. We often have through holes that are longer than our probes, so the depth/ending offset on auto-features almost always needs adjusted. If length was included in copy/paste parameters, it would at least save a lot of tedious repetition for us.

I am updating from 2015 up to 2024. I have several machines with different probing systems, saved alignments, etc. Each machine has its own folder with all of its programs. I just discovered the 'Open' tab when I open PC-DMIS.

Every time I need to go into the programs for a different machine, I have to remember to change the 'Set Search Path' options. It does not work well after I have a program open, so I have to close it, set the path and then open it again. How about a way to set each folder with its own predefined 'Set Search Path'?

A lot of times, features are reference on drawings and just need to verify if they exist or not. Basically "is the hole there or is it not". This could be done pretty easily with Scan data and a CAD model to verify if features were manufactured properly without having to use actual probing. This specifically would work very well for an Arm, AS1 and PC-DMIS. It would be pretty simple to add to the feature settings instead of extraction, to just verify a hole/slot or whatever feature is there. 

Can we get some way to record what version/schema of PC-DMIS is required to open a particular PC-DMIS file?  With the rolling cutoff and some users having a mix of schema for their routines, I fear difficulties with using the migration utilities in the future. 

Missing evaluation form requirements with rectangular type by Iso Std