Hi folks,
We recently deployed PDM Workgroup and have been having pretty goodsuccess with the transition.
One thing I'm wondering is how to deal with end-of-lifecycledocuments. We have a simple lifecycle chain that goes Prototype-> Production -> Obsolete. Prototype parts are revisioned 01to 99, Production A to Z, and Obsolete has a single revision calledOBS.
What I want to do is to hide obsolete documents from the standardvault view, since they add clutter. So far I can think of two waysto do this:
1. Remove users' read access to files in the Obsolete lifecyclestage through the Lifecycle tab in VaultAdmin
2. Manually move Obsolete files to a separate project calledObsolete (kind of like the Trash method of deleting)
The problem with approach #1 is that making a doc obsolete isactually a two-stage process for us; first the document's lifecycleis changed to Obsolete, then its revision is bumped to OBS (BTW, isthere a way to make the latter happen automatically?). Problem is,once the lifecycle changes to Obsolete the user no longer hasaccess to the document in order to bump its revision.
I also hesitate to implement method #2, since doing so loses thepart's original project. It's not a big deal but we do see it as adrawback.
So... any best practice recommendations here? In the end I justwant to keep the vault view tidy and free of old (obsolete) stuff,while still maintaining the ability to resurrect old parts ifnecessary.
Thanks
- rdo
SolidworksWorkgroup Pdm
We recently deployed PDM Workgroup and have been having pretty goodsuccess with the transition.
One thing I'm wondering is how to deal with end-of-lifecycledocuments. We have a simple lifecycle chain that goes Prototype-> Production -> Obsolete. Prototype parts are revisioned 01to 99, Production A to Z, and Obsolete has a single revision calledOBS.
What I want to do is to hide obsolete documents from the standardvault view, since they add clutter. So far I can think of two waysto do this:
1. Remove users' read access to files in the Obsolete lifecyclestage through the Lifecycle tab in VaultAdmin
2. Manually move Obsolete files to a separate project calledObsolete (kind of like the Trash method of deleting)
The problem with approach #1 is that making a doc obsolete isactually a two-stage process for us; first the document's lifecycleis changed to Obsolete, then its revision is bumped to OBS (BTW, isthere a way to make the latter happen automatically?). Problem is,once the lifecycle changes to Obsolete the user no longer hasaccess to the document in order to bump its revision.
I also hesitate to implement method #2, since doing so loses thepart's original project. It's not a big deal but we do see it as adrawback.
So... any best practice recommendations here? In the end I justwant to keep the vault view tidy and free of old (obsolete) stuff,while still maintaining the ability to resurrect old parts ifnecessary.
Thanks
- rdo
SolidworksWorkgroup Pdm
