Case: Proe linked to MDM and PDM software (Windchill). All provided by PTC
The PDM software is the reference. It manages the BOM. In this case the BOM hasn't to be anymore on the drawing to avoid to duplicate the BOM and to risk to share two BOMs with differents contents.
If a designer has a legacy drawing with a BOM table and several BOM balloons, he needs to remove the BOM table but keeping the BOM balloons before to link, to publish the drawing to the PDM software.
Actually, if he deletes the BOM table, all the BOM balloons are deleted. He has to place again one by one. He spends a lot of time. Wasted time...
With an option in the function BOM, he could "disconnect", make independent the BOM Balloons and the BOM table. Then he will be able to delete the table and keep all the balloons. Won time
The work around we found is placing the table on a drawing layer and hiding that layer. You also still need to point the indexing to the Windchill Find Number (as a usage attribute) within the table. That's the only real way to keep it dynamic.
It would almost be better if the balloons used the usage attribute data directly rather than mapping to the BOM table which maps to the usage attribute data. Currently you can't use the native BOM balooning tools without having a repeat region BOM table.
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.