PDMWorks setup

[vher]

I am trying to setup our PDMWorks vault, but have quickly become annoyed with its slow manual method of creating projects. Does anyone out there know of a way to take an exiting windows files structure, with or without the files, and copy it over into PDMWorks.

Also, is anyone out there experienced with PDMWorks and know where I can get some tips and tricks with PDMWorks? I'ld greatly appreciate anyone who can steer me in the right direction.

Thanks.

Vang

 

[GFranck]

How can you be annoyed about creating new projects in PDM/Works. All you do is go into the PDM/Works Vault Admin and click on "NEW PROJECT". It don't get any easier than that.

 

[vher]

Well.....let me see..um over 300 projects with multiple levels. I admit its easy to create, but it does get tedious. I gues I've just beeen spoiled.

 

[Standing]

Why you are trying to control your projects by putting the drawings & models in different folders? Bradley

 

[vher]

Where there are drawings and 3D models they would go in the same project, but we do have extensive data that doesn't have 3D data which still needs to be transferred to the new system. The nature of our products have long service lives, which means we find ourselves having to maintain alot of our older programs as well as our newer ones. Plus we can leverage alot of the older designs that weren't so practical in the past because of manufacturing limitations.

Oh well.... back to my fun life of servitude to PDMWorks.

 

[Standing]

Vang,
I have found in the past that once, a system that has over fifty categories, it is hard to find anything. In your case, this would be folders. We have setup a few projects and put new work into their folders. Once a drawing is released, we move it to a released folder. The plan is that when the project is complete we will delete the folder. Have not done this as of yet. PDM/Works has such a great search tool that I never go to a project and start hunting. I start all my searches from the top. Although I do see engineers clicking there way through the tree. I do not understand why and I do not ask. Some things are better left unsaid. I hope this helps.
Bradley

 

[JDone]

We put all of our products that are released to production in one folder named Released. The multiple project folder option will drive you nuts, specifically when dealing with parts that are shared among multiple projects. We have created a naming convention we use in the PDMWorks description field that includes a project name along with an intelligent description. This enhances PDMWorks searching capability and eliminates the need for multiple project folders. You should also be careful what you put in the vault. Only documents that require an official revision scheme should be placed there. Supporting documents that are not changed by an official change notice (ECN,PCN)will clutter your vault. You should also consider the time it takes to set up and maintain supporting documents or legacy data from other systems.

 

[Standing]

JDone,
Working outside PDM/Works has not been an easy road for us. Some of our Engineers do not trust the PDM, so they are working outside the system. We have a seat of PDM/Works for everyone who models in SolidWorks, currently 19 seats of SolidWorks and 27 seats of PDM/Works. Working outside the PDM we find extra copies, and within those copies the model features are not the same. So when someone is working with a sub-assembly outside the PDM, he or she must always check with the responsible Engineer as to the last. While everyone else works within the PDM and he or she checks in any changes someone else might want to see. Everyone is kept current.
Bradley

 

[JDone]

I did not say to work with SolidWorks outside of PDMWorks. I said be careful what you put in the vault. We put all released SolidWorks data in the vault. People will always have the choice whether to use current or out-of-date parts, with or without a vault. We also have the problem of some engineers not liking the vault. It takes a great deal of administrative effort to maintain a vault. In our organization "unreleased" or "experimental" data is the responsibility of the produt engineer. If he chooses to use out-of-date data it's his butt. We maintain the PDMWorks vault so that current data can be accessed. If an engineer goes around that system he is accountable.

 

[Standing]

JDone,
I agree, and yes it is the engineers butt if something goes wrong and they know it.
Thanks for the explanation. Bradley