What is the prefered default check-out configuration: As-Stored or Latest?
What are the pros and cons of each?
How do you ensure the 'As stored' versions of these higher level parent assemblies reflect the correct parent revision model if lower level part model changed a revision. Changing a revision on child model does not neccesary force higher level parent models to be revised and checked out too. To get correct As stored revision model it seems that the parent level assemblies will have to be at least revised, regenerated in Creo and checked back in and then be promoted in Windchill to a Released state again?This seems to be a revision tumbling ladder effect onto all parent assemblies where the child model is used. This is time consuming. According to CMII principles it should only be neccesary to revise to point where interchageability is restored? Doing revision tumbling on all higher level 'where used' Released parent assemblies if form,fit and function was not jeopordized in an effort to get the 'As Strored' parent models right is an adminstrative burden. For full explanation refer to my discussion on this forum (http://portal.ptcuser.org/p/fo/st/topic=16&post=127791#p127791). Any reply on possible solution will be much appreciated. Thanks
In Reply to Lourens du Toit:
How do you ensure the 'As stored' versions of these higher level parent assemblies reflect the correct parent revision model if lower level part model changed a revision.
They don't. The "correct" as-stored model of the assembly is with the older revisions of the parts it was stored with. Also, As-Stored is a downward looking used-on config spec, not an upward looking where-used spec. There is no reflection of the correct parent.
Simply put, CMII is referring to parts and products, not models of parts and products. The Creo models cannot adhere to these rules without significant extra effort as you point out. There is also a greater level of difficulty: Creo detail parts and their interchangeability in their respective assemblies are not only Revison dependent, they are iteration dependent.
When a detail part is modified for any reason, there is no guarantee it's references are still in tact to regenerate in any of its next higher assemblies. It is for this reason it's critical to maintain a good "As-Stored" configuration spec for any assembly (or part-drawing relationship for that matter.) It's unrealistic to think the assembly model will match the assembly on the shop floor down to the Revision of all its components. We don't even know what therevision mix is onthe shop floor, nor do we care. For that reason, the last regenerated version of the assembly (which is it's latest released revision) should be adequate for most engineering & planningpurposes of that assembly if no engineering changehas caused it to revise. The detail parts will always be operated on with their latest revisions separately.
When a higher level assembly is revised, then it's time to bring in all the latest detail models and start resolving conflicts and regen failures and create the new latest version of the regenerated assembly. This is when we find out how much our training, modeling standards, model check policies, robustness of our new Creo versions, and all the other governance we've put in place has really been worth it. There are a number of other strategies companies use to mitigate this, but they seldom justify the continuous upfront effort when the Configuration Management of the physicalassembly doesn't demand it.
Solar Turbines Incorporated
In Reply to Dan Glenn:
"When a higher level assembly is revised, then it's time to bring in all the latest detail models and start resolving conflicts and regen failures and create the new latest version of the regenerated assembly."
Question for Dan - Say for example, that assembly 1 does not have a revision changebut has a regen failuredue to a revised part. Now, I need to use assembly 1 in anew assembly that I am creating. Would you use the "As-Stored" (last regenerated version) of assembly 1or go thru a process to resolve the failures caused by the part and create a new "Latest" version of the regenerated assembly 1?