PI Munich Conference: Single BOM
-
Upload
oleg-shilovitsky -
Category
Technology
-
view
1.582 -
download
0
Transcript of PI Munich Conference: Single BOM
Oleg Shilovitsky, blogger @BeyondPLM, CEO @openbom
Single Bill of Materials
Adopting a Single Bill of Materials (BOM) Strategy for Engineering and Manufacturing Integration
Copyright © Beyond PLM 2016
You think BOM is a simple “stückliste” ?
image source: http://help.solidworks.com/2012/German/SolidWorks/acadhelp/Bill_of_Materials.htmCopyright © Beyond PLM 2016
BOM is a very complex structure
Copyright © Beyond PLM 2016
Organizational view of BOM
Engineering
Manufacturing Sales
Maintenance
BOM
Data is complicated. Each department demands different data.
Customer
Copyright © Beyond PLM 2016
Is there a single “master” BOM?
Copyright © Beyond PLM 2016
'The question is,' said Alice, 'whether you can make words mean so many different things.'
'The question is,' said Humpty Dumpty, 'which is to be master — that's all.'
--Lewis Carroll--
Who is controlling BOM?
http://beyondplm.com/2010/03/05/the-ugly-truth-about-plm-erp-monkey-volleyball/Copyright © Beyond PLM 2016
Traditional “siloed” BOM approach
Engineering Manufacturing Maintenance Sales / Customer
Sync, lose of data and semantic, mistakes… Copyright © Beyond PLM 2016
Reality of data distribution
Design Engineering and Manufacturing Physical product
Require-ments
Design Engineering Planning
Planning
Planning
Ordering As-built
As-Built-SNMBOM
Support
Kit
Spec
How to synchronize BOM data across the product lifecycle chain?
Copyright © Beyond PLM 2016
Vertically integrated frameworks
Copyright © Beyond PLM 2016
The challenges of multiple BOMs
#1 → BOM Transfer
#2 → Keep Item data in sync
#3 → Keep consistency of silos
http://beyondplm.com/2011/11/02/bom-and-cad-pdm-plm-erp-integration-challenges/
Copyright © Beyond PLM 2016
Variations of single BOM solutions
Copyright © Beyond PLM 2016
Single Structure BOM Views Federated systems
Why are companies not ready for a “single BOM”?
http://beyondplm.com/2012/12/19/why-companies-are-not-ready-for-single-bom/
Multidisciplinary design tools No agreement to shareData controlling behavior
Copyright © Beyond PLM 2016
Single BOM and John Gall’s law
Gall's Law:
“A complex system that works is invariably found to have evolved from a simple system that
worked.”
Copyright © Beyond PLM 2016
Single BOM maturity model
(1) Share: Access the same BOM
(2) Reference: Connects multiple elements of BOM
(3) Query: Retrieve BOM on-demand from diverse systems
Copyright © Beyond PLM 2016
SHARE REFERENCE QUERY
1
2
3
Share the same BOMAccess & edit data
Share between departmentsShare between engineers Share between contractors
How to eliminate the sync?
Copyright © Beyond PLM 2016
How to work with the “same” BoM?
1
Reference BOMMultiple CAD and PDMsCAE environmentsOther engineering silos
Elements of a BOM need to be easily referenceable in a single environment
This is “mostly” PLM problemHow to manage multidisciplinary BOM between MCAD, ECAD and software?
Copyright © Beyond PLM 2016
2
Query BoMMultiple lifecycle stages
Enterprise systems
PLM, ERP, SCM, Services
Multiple systems
How to integrate BoMs related to different stages of product lifecycle?
Copyright © Beyond PLM 2016
3
BOM management demands...
...No mistakes ...No manual typing ...No painful synchronization
Image courtesy of winnond at FreeDigitalPhotos.netCopyright © Beyond PLM 2016
Conclusion
There is no single recipe for a single BOMIt is a combination of technologies
that can do a job
Copyright © Beyond PLM 2016