Bill of material issues in solidworks

[rmetzger]

We're currently experiencing the joy of having our bill of material table automatically renumbering itself and / or deleting entries. Frequently upon opening a drawing with a BOM we've been finding that auto-populated lines are missing information, are rearranged, or are missing entirely without any changes to the models or assembly having occurred. So far we've found no resolution to the issue and for stability sake have been forced on occasion to recreate the BOM manually as a general table. This leads me to two questions:

Can one completely dis-associate a auto-populated BOM from the assembly it is referencing and turn it into a general table.

Is there any fix to make the BOM feature more stable so that we can use it with any sort of confidence.

 

[CorBlimeyLimey]

To make it more stable you need to know what is causing the instability.

You have given us nothing to work with. As a starter:
What are you system specs? (Hardware and software)
Which version and SP of SW and how was it installed? (upgrade, separate clean install or multi-install)

 

[drawoh]

rmetzger,

What version of SolidWorks are you using?

Which BOM are you using, the SolidWorks, or the Excel?

Do your row numbers follow assembly ordering, or are you reserving row numbers for missing components?

Are you sure your assembly model is not being modified? Check the properties of your drawing view and see how the configuration is being selected. The model's "in-use" or last saved configuration setting could make your life weird and interesting.

JHG

 

[rmetzger]

Solidworks 2008, SP4.0 XP-SP2

Solidwoks BOM (not excel)

the row numbers start out as following assembly ordering then auto-rearrange on their own. Some delete, some change names or delete quantities, some change names, some re-order. I believe the software is following the chaos theory in regards to how it seems to managing the auto-populate data. The models in most cases are stored locally while in development with only one one user having access. Often closing the drawing and immediately re-opening them will cause the problem to occur so no changes to the models or assembly had occurred between sessions.

Computers - all in the department (laptops, desktops...)too many to list and its not related to a single machine

Cause of instability - solidworks 2008 I'm presuming

 

[SWCADMAN]

rmetsger,

In the Drawing view properties check the box "Keep linked to BOM" and choose the associated BOM. In table properties of BOM make certain "Follow assembly order" under Item numbers is checked. This sequence usually fixes this type of problem I rin into.

JED

 

[SWCADMAN]

rmetz,ger,

In addtion make sure all your views are linked to BOM so ballon numbers will match BOM.

JED

 

[CorBlimeyLimey]

Others may have had this or similar issues, but I have not read about them in the various forums.

Are you able to update to SP5?

Have you had this problem since installing SW08?

Does it only happen on certain assemblies ... or assemblies with a particular sub-assy or component in them?

Were the installs made from the same source (DVD, download, admin image)

 

[NomLaser]

There is nothing wrong with SW, the install or your hardware. It's a setting in your BOM table. Take a look at them and there are some options; such as keep the item numbers from changing, following assembly order and I believe there is another option that will effectively lock your BOM. SW Bom's are a PITA if you use an ERP/MRP system that relies on item numbering in the BOM.

 

[uGlay]

Keep a good eye on the CONFIGURATION which the BOM is referenced off of. Go into the model and arrange your parts neatly, put them in folders and line em all up nice and neat. This should help you get an organized and consistent BOM.

If you hack an assembly together, make the BOM and then start making changes without tracking them on your BOM-referenced assembly then youre going to definitely go missing some parts or have some disappear or new ones added or who knows what.

I've also found with BOM's that practice makes perfect. If it is just too clusterf'd just delete the BOM and start a new one.

SW2008 Office Pro SP4.0
Intel Core 2 Duo CPU
2.2GHz, 2.00GB RAM
QuadroFX 3700
SpacePilot