PC-DMIS Protect - should have more "user" level access compared to current only 2 - programmer and operator
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 2nd level certification authorizer should be the one who should certify the program. This was very widely asked by many company manager’s.
Customer support service by UserEcho