Bom versioning, looking for real world experiences

[HugoHermans]

Hey all,

Is someone willing to share real-world experiences about BOM-versioning in ERP and on the shopfloor? Or motivations not to do it?

We are in a process of replacing our home grown ERP system, and one of the objectives is the introduction of versioning on articles, so implicit also on BOMs. It's obvious that the version management as such will be done in Windchill, but we haven't seen any company yet that showed us versioning on BOM's in ERP, and we have identified some business cases where BOM versioning could cause more troubles then it solves.

Another reason to be suspicious, is that our choosen ERP system doesn't support versioning out-of-the-box, it can be configured to be compatible, but it's not build for it.

So we are a little reluctant to introduce versioning articles and boms outside the boundaries of R&D.

Thanks in advance, Hugo.

[GregoryPERASSO]

Hi Hugo

complicated topic ... related to BOM and configuration Management... and difference between "PLM BOM "instant T " and "ERP BOM execution/transaction with a temporal offset"

I think in most PLM>ERP cases, should be managed by a Version to Effectivities "conversion".:

-identify Parts that you want to track

-clearly define interchangeability rules

-Handling correctly effectivities (config item and/or dates) throught Change Management (for all xBOMs views - Design, Manuf and Support if needed ...)

-manage all related documentation (notably manufacturing and QA) in a "part centric" approach to be able to identify correct versions to use , regarding a particular part version/effectivity

-trigger PLM to ERP BOM interface by change management ....

regards