cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

BOM table in Annotation should count by subassy

BOM table in Annotation should count by subassy

I have a drawing of an assy and this assy contains subassys. The subassys contain parts, shared in one or more other subassys. When I create a BOM table in Annotation, it will now count all instances of the shared part, ignoring the assy-structure. I would like to have the option to count them per level (per subassy).

6 Comments
Visitor

then i think you should use the option 'one level' when scanning the model in stead of 'all levels'.

this way the scan wil only look down 1 level, scanning the sub-assembly and not the parts. or is this not really what you mean?

I also think the BOM functionality should be expanded, so multi-level BOM's are possible. kinda like the BOM editor in Model Manager.

Newbie

No, I really want "all levels". The shares in the subassys are intentionally organized that way and reflect some kind of assembly procedure. I need one comprehensive table of the top-level assy containing the BOM-information.

Moonstone

After generating the BOM, then create a report.  this will let you expand all of your subassemblies. You can expand the sub assemblies and included or exclude the sub assembly.

It takes a little time to develop your best practices that best suits your needs.  Once you do, you can generate your bill of materials very quickly.

Newbie

I think your suggestion refers to the BOM-module, but I mean the BOM functions inside Annotation (without BOM license).

Moonstone

You are correct.  I have not used the BOM functions inside Annotation in a long time. 

Community Manager
Status changed to: Archived