Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
If your effectivity is immediate for failures or immediate recalls, then it will automatically set the resulting objects to obsolete or superceded.
Hopefully you get to this stage. There is a whole lot more with WTPart management business process to meet to most large aerospace company standards like Boeing,EADS, Lockhead Martin, Airbus, Northrop Grumman Corp, Bombardier, BAE, Mitsubishi,etc which follow most change management processes like CMII for each functional group. This is to ensure that thereis accountability and process is clear, concise and valid. Most contractors or vendors of these companies have to comply to their change process because for large mass production, the process must be efficient to cut cost down for the entire supply chain. A fit, form and function change or not has to be common knowledgeand iron clad.
Hopefully Windchill can mature to meet the needs of this standard change process in the aerospace industry for the past 30+ years.
Hi Patrick, It seems you've dealt with the change management process in detail. I have question regarding revision tumbling of parent assemblies if only revision changed happened in child assembly. Doing revision tumbling on all higher level 'where used' Released parent assemblies if form,fit and function was not jeopordized 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
You would not revise multiple next higher assemblies. Rather, you would change part numbers of next higher assemblies up to a point of interchangability based on your configuration managment rules, revise the point of interchangeability, and not change anything above taht revision at the point of interchangeability. You can then use a variety of effectivity techniques to cut in the use of the new numbers under that new revision. You would not continue to revise above the point of revision.
Morning Albert,
Appreciate the reply.It makes sense to revise to the point where interchangeability occurred. Is this acceptable business practice? Because parent models iskept inReleased state it can not be opened in Creo session to regenerate the model to bring in the new revision of child. parent model properties like weight and child component vieweables will display incorrectly in parnt models. What is good industry strandard to follow working with Creo and Windchill applying CMII principles?