See Topic,
Just curious if there is a possibility of forcing users to follow a naming convention when checking files into PDM Workgroup. We are just starting to implement PDM Workgroup and I want to start out in the best possible manner with naming convention and rev control. Ideally, I would like the ability to set rules for how users name files when checking them in, forcing them to follow a specific naming convention. Anyone know whether this is possible using PDM Workgroup?
Nathan,
Welcome to the forum.
You can setup permissions, lifecycles along with rev controls, but there
is not file naming guidelines in PDMW. EPDM yes, but not workgroup.
Thanks all for the quick replys! Sounds like I'm outa luck on the naming control. I am at the moment trying to develop and test a naming convention that will work best with our company. We manufacture in-house and all products are custom runs made at the time the order is placed. We do not inventory individual components. Each component manufactured is directly consumed in fabrication and assembly.
I was considering a naming convention such as XXXX-YY-ZZ, all numeric characters. The first set of four digits being the project#, the second two digits being sub-assemblies, and the last two digits being individual parts. I may get crazy and consider a alpha character following the project# to aide in breaking up larger projects, but this case is few and far between. This is easy for us as each component is unique to the project#. Standard hardware such as nuts and bolts get assigned their manufacturer's part#.
The main driving factors are ease of naming for the Designers and ease of reading the prints for assembly and fabrication in Production. This will also work fine in our ERP. I haven't settled on anything and am exploring options at the moment.
Yes, at least with PDMW. You are just going to have to setup strict permissions
and have strong guidelines within your department for what youare going to try and do.
Unfortunately, WPDM is mostly built on the "honor" system. Whereas, if someone is checking something in, they should have it named correctly. Although, since you are just starting out the with vault, it would not take too long to look through the files and if something looks out of place, you can go back to who checked it in and be able to offer a little more training on proper vault use.
Chris
Not really, the only thing it will not let you do is add a duplicate filename.
The best you could do is use the "Triggers" functionality and write a custom program that would monitor files checked in the dirst time or when they were renamed. It could send email to person adding the file and admin person that a file was added that did not meet your naming conventions.
What file naming convention are you trying to implement and where is that filename used?
I find a large blunt object sometimes works to enforce naming convention.....(sadly, as the others have said, the answer is no)
Seriously though, the best way to control it is to come up with a process prior to making the vault active, then train that process, then monitor and enforce it. If someone doesn't want to play by the rules, then you may need to adjust their think (this is where the blunt object comes in).
I recommend you stick to part numbers for filenames, and think of how you could use configuration names as well. Stay away from Word based names, as it will be easy to make duplicates without realizing, depending on the number of users and their skill sets.
PDMW is a great tool, and user correctly works like a champ. It is also open enough to let havoc rain on your install, by just running with it.
You've started on the right foot, so don't let it get stepped on!
I was hoping not to resort to the blunt object method but that may help me weed out the non-believers more easily. It's just always good to keep the honest people honest.
In an earlier job, I was the "checker" for a drafting department. Part of my responsibility was to verify that standards were being met on the drawings. The method of verifying that the proper terminology was being used to define a part involved me returning the drawing back to the creator if it ws not correct. I was not allowed to make the change myself because there may be nobody else verifying my accuracy, also, if I did not send it back, the same mistake would likely be made by that individual at a later date. The job of "checker" is becoming scarce as more spell-checking software and SWork's drawing checking app's are available. Unfortunately, the reason that some mistakes are no longer made is NOT because people have learned correct techniques.
We actually have a checking policy here, and that is one of the checkpoints to verify. We also use Bluebeam Revu to compare PDF files. It's an awesome tool for cheap money, and has more than paid for itself! If you have complex drawings, and have changes that go un-noticed because the Solid was updated incorrectly, it can cause major headaches. More reason to have a policy, and enforce it. Checking solids is not something the systems are in place to do yet, but eventually should be.
I would create a small group of users to be the policy team, not an individual making the decision.
Nathan,
Welcome to the forum.
You can setup permissions, lifecycles along with rev controls, but there
is not file naming guidelines in PDMW. EPDM yes, but not workgroup.