You are not logged in.
Pages: 1
When initially being introduced to Vericut, are many companies relying on one person to become a Super User giving the complexity and time required to process a job through it? I would think that this person would then train another to take over the Super User Role for several months and then another rotation until proficiency was obtained throughout the department.
Additionally, am I wrong in thinking that the best practice is to have a person other that the one who had programmed the job, set-up Vericut verification. This thought is due to the many ways to circumvent the system with false realities.
Last edited by jfrederick (2020-04-29 16:22:29)
Offline
We have users run their own, all the time. System design planning is required for Tooling, CAM system and Vericut to work together.
We have an 2-3 admins that can edit the default project, machine, control files and subroutine files. General users do not edit machine, control or subroutine files. They work out of the local project file.
We make our attach points a common program 0 point on the machines.
We simulate machine 0 as it is on the floor, we use common offset values in our master vcproject files to match the default program 0 and Attach point. Offsets in Vericut and at the machine are very close. (Vericut can be perfect, but machines aren't)
When models are setup up in the CAM system, they are accurate. The close enough of 20 years ago is gone.
When models import in to Vericut, no repositioning is needed. Using the NX interface.
We have a master tooling system, no edits to tooling.
The old NC programming rule of thumb applies, you have to know where program 0 is and how you got there. Once that is learned, users progress quickly.
Offline
Pages: 1