How to add reference document to a BOM?
Posted: Wed Jul 10, 2024 11:49 pm
Sometimes a reference document is needed in an assembly — for example, a P&ID for a plumbing module — what is a good way to do it?
We see two approaches—
1. create a dummy (no geometry) sldprt file for the P&ID and insert it into the assembly. The “part” then shows up on the (parametric) BOM with a Qty of 1 — sometimes the engineer changes it to 0, since no physical copy of the document is needed.
This creates several issues: 1. Inconsistency, since it depends on whether the engineer chooses/remembers to change the qty; 2. If qty is manually changed, it breaks the parametric nature/beauty of SolidWorks; 3. One will need to set up the properties of the empty sldprt file, which then gets released… a bunch of silly actions to be honest;
2. manually add a row of text to the BOM table on the drawing. This naturally breaks the parametric nature, since the row does not correspond to a component in the assembly. Additionally, it (probably) doesn’t show up on the components list if the assembly in PDM, thus could cause data mismatches between PDM and ERP. Another issue is that, if the same document is used in two assemblies, the BOM tables might not agree with each other, since part number and description are manually typed in (hence possible human error).
Is there a better way?
We see two approaches—
1. create a dummy (no geometry) sldprt file for the P&ID and insert it into the assembly. The “part” then shows up on the (parametric) BOM with a Qty of 1 — sometimes the engineer changes it to 0, since no physical copy of the document is needed.
This creates several issues: 1. Inconsistency, since it depends on whether the engineer chooses/remembers to change the qty; 2. If qty is manually changed, it breaks the parametric nature/beauty of SolidWorks; 3. One will need to set up the properties of the empty sldprt file, which then gets released… a bunch of silly actions to be honest;
2. manually add a row of text to the BOM table on the drawing. This naturally breaks the parametric nature, since the row does not correspond to a component in the assembly. Additionally, it (probably) doesn’t show up on the components list if the assembly in PDM, thus could cause data mismatches between PDM and ERP. Another issue is that, if the same document is used in two assemblies, the BOM tables might not agree with each other, since part number and description are manually typed in (hence possible human error).
Is there a better way?