cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Best Practice for sharing modified production assemblies?

Newbie

Best Practice for sharing modified production assemblies?

The description doesn't really fully explain the request. An example:A user uses an existing production part or assembly as the basis for a layout or concept in a workspace. The object is at Released status in Windchill.He wants to share this with other users, but doesn’t want to iterate a standard object that may not actually get changed. How do you share this data with other Windchill users? Currently the user is saving to a network drive which defeats the purpose of having Windchill.


We could just check them in to Windchill at Prototype, for instance, and all would have access. If you do this, do you just
leave a dead-end design in the system for history? And if so, how do you ensure that the next person to attempt a new design based on that assembly goes back to the earlier Released iteration to work from and doesn’t accidentally pick up the incomplete prototype by using the default “Latest” at checkout?


If you do something similar, do you use Purge often to limit the buildup of unnecessary iterations?

3 REPLIES 3

RE: Best Practice for sharing modified production assemblies?

Hi Pete


Have you considered using ProjectLink for this. If you share to a project then check out and modify your conceptual changes from there, you have effectively created a revision branch. You may later choose to merge those changes back into you main product.... or not. You can also perform multiple concurrent change studies, if you share the same models to multiple projects.


Darren

Best Practice for sharing modified production assemblies?

I think that's what ProjectLink is for.
Highlighted

RE: Best Practice for sharing modified production assemblies?

If the released part is just "the basis" for the new concept then that implies that there will be changes.


If the changes are likely to be interchangeable then you could go down the Project-Link route as suggested.


If the changes are not going to be interchangeable (more than likely) then what is wrong with the simple "save-as" to create a new part that is not released yet and you can change it as must as you like?