PDM Works usage... 1

[KBeitel]

At a previous workplace, PDM Works (workgroup) was utilized. It worked well and have since upgraded to PDW Works Enterprise.

In my experience in working with a PDM was multiple concepts were modeled and when the design was approved, the assemblies & components would be renamed to the part numbers that were assigned and the metadata for each file would be completed. After all this was done and the files were ready for detailing, then and only then would the files be checked into the PDM vault into its respective project.

I am curious as to how some use PDM from the concept right through to production drawings. I find that I would end up having to delete multiple versions of assemblies & parts that I did not end up using and it would just end up becoming a PDM vault maintenance nightmare.

Anyway, that you in advance for any feedback.

Take care & have fun!

Kevin
"Hell, there are no rules here -- we're trying to accomplish something." - Thomas A. Edison

 

[ctopher]

Most of the time I assign part numbers up front. There are some cases they will never have numbers and are saved onto my hard drive.
All files are checked into the vault per each change. I don't check any in without a p/n assigned.
Having a manager that does not have an understanding of PDM and dictates when and how files are checked in, causes problems.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[KBeitel]

Chris,

I totally agree with you...

I kind of like to blame a bit of this to the canned demos that are done on the PDM products to show how easy it is. They just check-in this and that with no regard or explain what is happening so that when in an actual production environment, the manager expects certain things to be done because it is a feature in the software that they like and want to implement, but it has no benefit to the end result but create more work... (ie increased Vault maintentance)


Take care & have fun!

Kevin
"Hell, there are no rules here -- we're trying to accomplish something." - Thomas A. Edison

 

[GRF]

I get part numbers first and then check in each change that goes to an outside vendor for mock up or proposed design. Those are given number revisions when we decided to cut tools those get letter revisions. I have set that up in the revision scheme settings for the vault.

 

[Gurjjeet]

I assign part no. straight-way & over-write my revisions untill finalized. It is tricky in some big assemblies as you might over-write a possible revision & loose old data. But I try to keep the data on my hard-drive untill I am finished with a new revision.

And yes, when we started using it, we used status & revision & other stuff. But now I find that too much & only use revision control & data mangment. We do not care much about the place where to save a file in project(as long as it is right project it is okay) as we use search function to open drawings, I really like that you can only have one file with one name that helps me a lot.

PDM is a bit tricky but a lot better than nothing.

 

[ng89]

This is where we utilize the Enterprise vaults. We have set up a Development vault and a Production vault. Everything starts in a project folder in the Development vault. Only once a design is finalized/approved do we take out p/n's and copy or save the parts into the Production Vault.

We assign slightly different privileges and workflows to the different vaults which ensures our shop and our suppliers can't accidentally get old development files, etc.

This concept should work to easily preserve old versions of files even if p/n's are taken out at the beginning of the conceptual phase as you'll end up with two separate versions of your files (one in each vault).

- Nick

 

[GRF]

You could do the same with PDMWorks just that is is a pain to rename all the files in an assembly, we use the part number and descritption as the file name. It makes it easier to find specific files since we use SAP to control BOM's and release control of parts (only PDF's and dummy solids). The PDMVault just works as a nice storage area for our solidworks files that is more secure and easier to use than a network drive.


I would think if you had a seperate revision type for prototype and production parts you could limit what vendors could get what files as well or does Enterprise lack that ability? I would imagine you would only want your vendors to be able to get the latest released version of any file.

 

[SteveMartin]

We don't use PDMWorks at my place of employ (DBWorks currently, and Adept at a prior company), but I think all the concepts translate well.

We pull part numbers before saving anything, and save only to the part number. Models are checked in/out as much as necessary/useful, constantly overwriting what's there, until the model is approved, at which point it is a new revision to make any further changes. Typically a model is moved to 'approved' state when the drawing is completed and signed, but occasionally models are approved and immediately revised in order to have a revision of a concept frozen at a particular point in development. It's not unheard of (though fairly rare) for our first release of a new part to be 2-3 revisions in.