Hi we're currently reviewing our model change management process and need to know what is good industry standard best practice w.r.t. the following example(Please refer to pdf example). For example let say a Creo part on a indent level 3(BN3 Rev C) needs to change. The part is interchangeable in all "where used" parent models.Hence only revision change to this part is needed. In Windchill PDM Link the part will get revised( to BN3 rev D) and checked out of Windchill to make appropriate changes in Creo session. After changes is made the part gets checked into Windchill again and promoted to a Released state.
My question is how does companies handle the parent CAD models in the Creo/Windchill environment for a child revision example as explained above? For instance if I open a Released parent model in Creo(lets say Model BN4 RevA) the 'As stored model' will be opened in Creo showing the old BN3 Rev C child model. The BN4 model can not be regenerated since it is kept in a Released state. The only way to capture the BN3 Rev D model change is to revise the BN4 parent model to allow model to regenerate. To capture the BN3 Rev D change in all the 'Where Used" parent models all higher level parent models needs to be revised so as to be put into In-Work state to allow Creo regenerate to run. We call this process Revision Tumbling. This creates a massive administrative nightmare due to all the drawings that needs to get signed off again. So how does other companies handle this? According to configuration Management principles when a changed is made on lower level model, that does not effect interchangeability,a company should only have to revise that specific model. No other revision changes of higher level parents should have to happen. Do companies except that higher level parent drawing illustrations of BN3 will be out of date?
My 2nd question relates to how does companies manage Windchill publishing of all the parent models after the BN3 Rev C change. Our company is setup to publish BN3 Rev C on promotion to Released state. This will update the BN3 vieweable but all the parent vieweable models will still be out of date. What is the best method to use to ensure all parent assemblies vieweables are up kept up to date? Can we use positioning assembly option in Windchill better? We need some kins of automated solution to keep our illustrations current as best possible
Thanks for any inputs on this duscussion.
Revising all assemblies creates a huge administrative burden for design office ito drawings that needs to be signed-off again even though it was only a small revision change that happened on a lower level not effecting interchangeability. In worst case scenario in our company we've had to revise 180 parent assemblies due revising one common component on an indent level 7. Is there nobody that has created a solution to solve this issue? We're seriously considering not doing revision tumbling in higher level assemblies. Hence leaving higer level assemblies out of date untill need for it to be revised arrises. What do we need to be careful off if we follow this approach? Does business out there really except this administrative burden of manual 'Where used' parent assembly model Revise =>check-out=>Regenerate=>check-in=>Promote To Release=>sign-off parent assembly drawing? I suppose the only way to keep properties like the weights of parent assemblies up to date is to regenerate all the parent models but this will require to revise all of them. Anybody tried setting up an automated server solution for after work hours that would keep a log queue of all Release state promoted parts for the day? The server starts running a sequential task list that would do a "Set State" to In-Work on parent models =>Check-Out=>Regen=>check-in=>Set State to previous Released state? This might be something to look at but we're scared to test this on our Windchill production server.
we always pull the "latest released" so the latest released top assy will pull the latest released sub components if their revison rolled, it still would require a checkout regen and check in, so when the top assy is on a ECO all rev's are up to date
Hi Han, I think I understand your question. We have not investigated how to link the history of FFF changes to each other. We know this as supersession cause current identification gets superceeded by new one. found a post on here that state Windchill10.2 has functionality that caters for this type of history.http://portal.ptcuser.org/p/fo/st/topic=16&post=119197#p119197