PI Munich: How to develop “single BOM” strategy

PI Munich: How to develop “single BOM” strategy


I’m attending PI Congress event in Munich these days. There are lot of interesting information and presentation. If you follow my Twitter or #PIMunich hash tag, you can find some comments and slides that I shared earlier today.

This afternoon, I had an honor to share my thoughts and ideas related to development “single BOM” management strategies and data integration in manufacturing organization.

To create, maintain and share Bill of Material in your organization is one of the most complicated process in every manufacturing organization. Understanding your company processes is a first step into better organization of Bill of Material. At the same time, BOM is not a spreadsheet you can pass into organization. BOM is a fundamental data structure in product design, development, manufacturing, support and maintenance.

My presentations and slides below are outlining some of the experience and observations I collected for the last year of my consulting business. It covers best practices and challenges of management of Bill of Materials in any manufacturing organization.

BOM creation and transfer remains a big challenge for a smooth PLM deployment. Many are wary of bringing BOM management into PLM as it can raise a lot of challenges in management, time and cost. However, with the demand for better integration and collaboration, companies soon may not have a choice as they attempt to close the loops between engineering and manufacturing.

Here are three level of my Single BOM maturity model:

1- Share: access and edit the same Bill of Materials

2- Reference: connect multiple elements of product information (BOMs)

3- Query: retrieve on-demand BOM information from diverse systems and data sources.

What is my conclusion? Single BOM is not a product. It is a vision and maturity model that enables to create a consistent way to create, update and share Bill of Materials in manufacturing organization. It is an integrated approach. The success is dependent on multiple factors – business processes, technology, PLM products and specifics of existing implementations. Just my thoughts…

Best, Oleg


Share This Post

  • Sami Kentta

    I had the honor to follow Oleg’s presentation and later also to share some thoughts with him. As a vision, the “single BOM” concept is in my mind an important target for a company. Usually discussion today evolves around ebom-mbom-as built but most companies have much more “BOMs”. In my organization, we have started to talk about “product structure views”, which provides a certain view, e.g. ‘As Required’, ‘As Defined’, ‘As Developed’, ‘As Offered’, ‘As Sold’, ‘As to be Built’, ‘As Built’, ‘As Installed’, ‘As Used’ to the product or asset. Each of these views are today existing in various it tools, but very importantly they’re referencing each others. In the future, I expect these to integrate to each others much more tighly, eventually becoming a “single bom” – keeping of course in the mind the limitations technologies are setting.

  • beyondplm

    Hi Sami, thanks for your comment! Product structure views are one of the possible approach to implement “single BOM” model. The challenge of “view model” is mostly related to the implementation of BOM which is distributed between multiple systems (there are some tech limitations there). It can work well into single PLM system.

  • Pingback: Beyond PLM (Product Lifecycle Management) Blog Single BOM (Bill of Materials) journey - Beyond PLM (Product Lifecycle Management) Blog()

  • Pingback: Beyond PLM (Product Lifecycle Management) Blog ACE2019 - BOM management and PLM nirvana - Beyond PLM (Product Lifecycle Management) Blog()