BOM: Best Practices of Data Sharing – Right Data, Right Person, Right Time.

Oleg Shilovitsky
Oleg Shilovitsky
21 December, 2019 | 2 min for reading
BOM: Best Practices of Data Sharing – Right Data, Right Person, Right Time.

Everyone needs the information that is in the Bill of Materials. But everyone needs it to be delivered differently. Engineers might have an access to all assemblies and sub-assemblies, descriptions, technical information about parts. Procurement has information about suppliers, contractors, and cost. How to balance all this information together. 

Typically. Organizations are struggling with the data. It comes from siloed enterprise systems or the absence of these systems. Data is not located in a single place. People are taking the data they need and offload it to Excels they can control. This is not a good way to share data. 

The fundamental data management principles of BOM management and product development are Item and Usage. Sometimes we call it Reference-Instance. The main point is that Item (Reference) represents all common information about parts. Eg. the screw cost and description are the same in all assemblies and sub-assemblies. But Quantity is not. In such a situation, Quantity is an instance (usage) information. 

To think about who gets what, let’s take a look at the overall process. 

As you can see the needs for information are different. Therefore, a good idea is to define roles and what information can be available. User-defined views is a good way to think about what information is available. 

Check this video from the webinar for more details. 

And watch video recording from the webinar. 

And this is a slide deck. 

Conclusion.

When you think about product development and manufacturing, you need to image different roles and information that belongs to these roles. That would be your roadmap on how to plan data access. Bill of Materials can be overwhelming with the complexity. Therefore to bring the right data at the right time is a way to go. 

Best, Oleg @ openbom dot com.

Let’s get to know each other better. If you live in the Greater Boston area, I invite you for a coffee together (coffee is on me). If not nearby, let’s have a virtual coffee session — I will figure out how to send you a real coffee.

Want to learn more about PLM? Check out my Beyond PLM blog and PLM Book website

Related Posts

Also on OpenBOM

4 6
16 October, 2026

How OpenBOM Engineering Frontend connects SOLIDWORKS design data with electrical, electronics, software, and manufacturing information. A SOLIDWORKS assembly can be...

15 October, 2026

A BOM management system organizes product Items, assembly relationships, quantities, revisions, and supporting information so engineering, manufacturing, and purchasing can...

14 October, 2026

Product development depends on people working together across engineering, purchasing, manufacturing, and suppliers. Each participant brings different information and often...

13 October, 2026

Every day brings another example of AI at work: reading documents, writing code, analyzing data, generating content, or helping someone...

13 October, 2026

For years, the PDM vs PLM conversation followed a familiar pattern. Product Data Management controlled CAD files and engineering revisions....

9 October, 2026

A design change is not finished when the CAD model is saved. Engineering still needs to know which component changed,...

8 October, 2026

A buyer asks which bracket to order. Engineering sends a drawing. The BOM lists a part number, the supplier quotation...

7 October, 2026

The engineering frontend workflow across disciplines This is the third article in the series of articles about OpenBOM engineering frontend....

7 October, 2026

Files and Items in the product knowledge graph This is the second article in the series of articles about OpenBOM...

To the top