This is VOC from APAC PC-DMIS User's seminar which I want to strongly support.

Actually, The user’s are looking for 3 different roles or assignment’s or may be more in some case's . Always,  It cannot be ONLY 2 roles in the companies like Protect support as now - 

There are many companies who have multiple level of access for "programming the part" and "approval". They have clear distinguished flow chart or process that guide's the entire work flow before a MR is approved or passed to approved or "certify" status.

The typical work flow in a company is as below:-

- When I work for a company for 12 years, we do have similar approval systems.

1 – Programmer role – “Administrator” who will program the part and won’t certify - He should not press certify button or should not have access to do Certify or press Certify button. The Certify button must be greyed out for him.

2- Certification “”authorizer””  or Metrology Manager – This is “High level administrator” who wont normally program, but who will have the power to "Certify" the program after revisions and of course make revision approval' s -  

He should have both "Program creation" and "Certify authorization" permissions. He is the Big Boss of certification in one word. He will be in a position to press Certify Button after Programmer finished programming the part. This is the very normal in many companies where the programmer is sitting somewhere and just pass the program after initial draft or just modify it after 1st or 2nd revision. During FAIR qualification or PPAP approval there are so many changes that can happen in a program which must be approved ONLY by certify authorizer or Big boss of Metrology. This scenario is not designed in current Protect model.

3 – Operator – Executor of the MR - Just he has the permission to open the program and run it. Operator mode as now.

After the programmer or low level admin is done with creating MR – the next level administrator or high level manager should be notified about the creation task and should be in a position to Certify. The first level programmer who himself is a admin, but should not have authorization to certify expect MR creation. The 2^nd level certification authorizer should be the one who should certify the program. This was very widely asked by many company manager’s.

Ability to insert balloon symbols into dimensional report. ie triangles, diamonds etc

I'd like to be able to right click a cell in the report header and edit its contents. 

We would like the ability to break a scan into multiple elements that may have different tolerances or requirements for each.

The option to extract individual point data from auto features, so that I can report xyz values for a single point.

As a user of PC-DMIS, I like to see the used qualification parameters (Prehit, Retract, TouchSpeed, MoveSpeed and NumberOfHits) in the results file. This will help to analyze if a setting was not aligned with the used parameters in a measurement routine which can cause significant deviations in the measurement results.

While hardcoding things in PC DMIS, we often run into "line length error" issues and have to break things up into multiple-multiple-multiple feature-sets. Can you please consider eliminating the line error issue if at all possible..or..giving us a lot more room for lines? 

If I can CONSTRUCT a plane with 5000points and see all of them listed in my edit window why can't we do the same with featuresets/while hardcoding? 

Thanks for your time. 

The Idea is to program an Auto Circle and RT is used to position the RT and take the hit on a circle,move RT take next hit, move RT tae next hit. This is a request of MTU.

This is an important function and will help all blisk manufactors which use PC-DMIS Scanning with and without rotary table. Then it is possible to calculate the biggest Diameter on a blisk.