AnsweredAssumed Answered

Question regarding computed BOMs versus named BOMs

Question asked by Tedd McHenry on Aug 10, 2018
Latest reply on Sep 30, 2018 by Tedd McHenry

We're configuring a new PDM installation and working out the details of migrating data from our old PDM system (DBWorks). One issue we're uncertain how to proceed on is cut to length items or other items in an assembly that have non-count quantities, and I'm interested in how others have done this.


In DBWorks, we have been dealing with these items by adding them to the DBWorks BOM which, as far as I can tell, is roughly equivalent to what SW PDM calls a named BOM. That is, the DBWorks BOM reads in all the items from the assembly plus any other items that are manually added. So, for example, if we have x meters of tubing in the assembly then, rather than have an empty tubing part file in the assembly, we simply add that item to the DBWorks BOM, along with the quantity. In our 2D drawings we use the DBWorks BOM to make the drawing BOM table.


As part of our migration strategy, we had planned to export the DBWorks BOM to a spreadsheet or CSV format and import that into a named BOM in SW PDM. But it's now our understanding that a named BOM can't be used on a 2D drawing (unless we write a custom API routine). The 2D drawing BOM is read from the assembly file. Is that a correct assumption? If so, how have others handled cut to length parts so that they can be on the drawing BOM?