BOM management – are you using Excel?
Posted by mikilumnitz on July 6, 2008
If you needed to take a guess… just a guess.. what is the most common ‘enterprise’ application that is used for managing BOMs in SMB companies?
I am wondering whether this was the first thing you have thought about (I know, you can guess it from this post title
)…
The most common ‘enterprise’ application that is used for managing BOMs in SMB companies is Excel
Is it the right way? why not, some of you will say… Excel is a great tool (agreed by the way…) it is easy to use, it is flexible, but is it controlled?
Let’s look at some critical data management aspects concerning BOM management:
- Look at the following picture, How to Identify the “Right” BOM? Can you help me…
- I need to change the screw, where is it used…
- What about increasing data reuse? or standardization of components? or security?
- And then… as always… what happened when I have a change…
So yes, using PLM to manage your BOMs will be less flexible as using excel and the reason for that will be that a PLM system will take care of your data consistency and your configuration control.
Because of the fact that BOM management is a major challenge in a lot of SMB companies and is very time consuming (time which most of those companies does not have…), we gave special attention to those challenges within our SNE solution (ENOVIA SmarTeam Engineering Express). I think the 3 most important benefits will be:
- Product/BOM Maturity management (with the configurable, embedded business logic to model your company business maturity process and conditions)
- BOM structures synchronization. to enable concurrent and controlled BOM editing (with the configurable, embedded business logic to model your company roles of moving from Design to E-BOM, from E-BOM to M-BOM, Reuse BOMs…)
- Easy to use BOM editing and compare
and in the end… do not forget… COLLABORATION !!!
yml said
Where ever I have been I have seen the BOM transfert to EXCEL at some point :
* Prototype
* Transfert between PLM and ERP
* to manage the evolation
* …
What is interesting is why people are doing it :
* Bad UI to represent/edit the BOMs
* lack of API to integrate several systemes or uncommon API or stupid licensing deadlock (CAA, …)
* re usability it is much easier/quicker to copy paste some Parts between 2 Excel files.
shaun snapp said
This is true and absolutely amazing. Actually there are two problems. One is Excel, the other is ERP. ERP vendors attempted to co-opt PLM with their own repackaging of existing functionality as “PLM” capable. PLM, or rather what I like to call BOM management software should be way more prevalent that it is. Particularly, this software should be hosted, because of all the systems that have to integrate with it, and of course integration capability is crucial. I don’t want to recommend any one vendor, but there are some cool solutions out there that people should check out. As a further note, I am concerned about the acquisition of Agile (industry leading PLM) by Oracle. I think Oracle tends to blot out the functionality of software they acquire. We should remember what they did to Peoplesoft.