A Configure BOM for Windchill tool
There is a way to link the line numbers or find numbers between WindChill and Creo as documented:
- https://www.ptc.com/en/support/article?n=CS197902
- https://community.ptc.com/t5/Windchill/Find-and-Line-number-support-pdf/m-p/449900
and other places. This is a good starting point. However, this requires manual entry of the values within the model tree for the component level parameters. The issue with this is that Creo will fail checkin of an assembly if, for example,:
- There are 10 of the same screws and only 9 have the findnumber field entered (you missed one)
- There are 10 screws and you gave some of them one find number and others a different find number (you forgot some of these screws were higher up in the model tree with an already assigned number)
- You gave these 10 screws a find number that was already assigned to something else
Getting the values entered correctly, effectively and quickly is almost impossible in even "smallish" assemblies when:
- Components are embedded in groups
- Components are embedded in patterns
- Similar Components are spread out throughout the model tree
- You don't have access to an easy table within the assembly to view everything, like a BOM table with a quantity.
What do other people do? Is there a company that makes a toolkit that can just autoconfigure the component level parameters and manage them automatically? It shouldn't be too hard to do. Any change to a line number should just get propagated throughout the component level parameters to all of the same components. Otherwise, I would love for PTC to create a tool to do this. Whether at the assembly module, drawing module or both.
Thoughts and comments on this by user's and PTC would be great. If you developed a tool-kit app, please let me know. If you have inventive solutions, I would love to hear it. We are trying to expand our use of Windchill and this was a definite topic of conversation. We don't want duplicate work in entering find numbers in drawings and Windchill. Yet, that is still easier than trying to manage the model tree with the issues discussed above.
