Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
I am curious if anyone has any good workarounds for parts that are "new" in your workspace, but already exist in windchill commonspace.
An example of this would be-
Day 1: Vendor sends you a .STP of a large assembly file. You import it as an assembly, save it, and check it into commonspace.
Day 2: Vendor sends you an updated version of the large .STP file. You import it, save it, and
(FYI: my example is a little more simple than the exact situation we have going on, and I cannot simply add the "day 1" model to workspace and get those parts updated in that manner.)
Thanks!
Here is my "trick" (I'm using Windchill 9.1 and Wildfire 5/Creo Elements)
Right, I can usually make that work too. My complication comes in like this:
Lets say the vendor has sent us 10 similar assemblies over the past few years. Each one is very large, and they all have some common parts.
Assembly A uses parts also in assembly B, C, E, and H. But B,C,E, and H may or may not share components wiuth eachother.
Trouble is, maybe I dont know what E and H were called when they were checked it (it could have happened years ago). And,I don't even know about B and C's existance.
And I am not talking about a total of 20 or 30 components when I say large; I mean upper triple digits, so I can't just start performing a where used report on everything either.
What has happened in the past is putting a date stamp on the assemblies and just rolling with the huge amount of repeated data and wasted space. But I am trying to find a better way around it, and maybe there just isn't.