PDMWorks 5 Questions

[cadmgr2004]

We are creating a new 2004 vault and will appreciate any feedback you may have to these questions:

1. We have a "Released" lifecycle state to which only two admin people have access. We do not isolate released files by storing them in a different folder than WIP. Do you protect released files by using lifecycle states or by storing all released files in a separate, secured folder?

2. Within each project, do you store your drawing and model files in separate folders or together in one folder?

3. On the client options panel there is the setting to "Compare vault file to [ ] File on disk [ ] File in Memory". Our assumption is that the default should be to compare the vault file to the file on disk (local view). Is this correct, or are their arguments supporting why using the file in memory is better?

4. On the client options panel there is the setting to "Open documents [ ] As Built [ ] Latest versions". Our assumption is that the default should be to use the latest versions. Is this correct, or are their arguments supporting why using the as-built versions is better?

5. Is it possible to rename a project, or must its contents be swapped out, the project deleted and recreated, and the contents swapped back in?

Thank you in advance,
Marc

 

[engAlright]

Hi cadmgr2004,

1) We do not use lifecycles for out production vault, as the designers have full access to their parts at every stage of the design process. To my knowledge you can't change the project of a part according to a lifecycle change, thus it would make sense to keep it in the same folder with different access.

2) Together - this is the default arrangement. The only advantage I could see to having drawings in a folder is to change access to that folder.

3) Personally I think "File in memory" is better as you can check a document in before it is saved. "File in memory" will show a document being newer than what's in the vault as soon as you edit that part - this is what user's should be seeing, the status of the active part.

4) "Latest versions" to makes sure everyone is making changes only to the latest versions of parts.

5) Projects cannot be renamed to my knowledge. In PDMWorks 2005 you can copy projects, so you could probably do a roundabout rename that way.