When Software Meets the BOM

Oleg Shilovitsky
Oleg Shilovitsky
25 February, 2026 | 2 min for reading
When Software Meets the BOM

For a long time, managing products meant managing mechanical structures.

Assemblies, subassemblies, parts, revisions — the Bill of Materials was designed around physical things. Electronics eventually found their place in that structure as well. Boards, components, firmware — they could be anchored to hardware.

But software changed the equation.

Software doesn’t behave like a physical part. It versions independently. It evolves continuously. It may update long after the product ships. It connects to hardware, but it is not constrained by hardware hierarchies. And that creates tension.

Many organizations still manage software outside the product structure, or reduce it to a simple line item in a BOM. Neither approach truly reflects how modern products are built — especially in robotics, smart devices, industrial equipment, and embedded systems where code defines behavior.

At OpenBOM, we’ve been working on a practical way to bring mechanical, electronics, and software elements together in one connected product structure. Not by forcing software into a rigid hierarchy, but by supporting relationships that reflect real engineering workflows.

If this challenge sounds familiar, I invite you to join our upcoming live session:

When Software Meets the BOM: Managing Mechanical, Electronics & Code Together (Live Demo)

We’ll walk through a practical demonstration of how these three domains can coexist inside a digital BOM and how changes across hardware and software can stay aligned.

Modern products are multidisciplinary by nature. The systems we use to manage them should reflect that reality.

Join us and let’s discuss how to make it work.

👉 March 4, 2026 at 11am EST (Eastern US time)  

Register here: https://my.demio.com/ref/qAJtEu8A7ok8qAow 

Why join?

Software in BOMs is no longer a theoretical problem.


If your product includes firmware, embedded code, or software-driven functionality, the way you structure your BOM will either support alignment — or create friction between teams.

This session is an opportunity to step back and look at how modern product structures can reflect the reality of multidisciplinary engineering. You’ll see practical examples, not slides. And you’ll have a chance to ask questions and discuss how others are approaching the same challenge.

Modern products are multidisciplinary by nature. The systems we use to manage them should reflect that reality.

Best, Oleg

Related Posts

Also on OpenBOM

4 6
16 April, 2026

Part numbering sounds simple until a design project starts to grow. At the beginning, many teams use whatever feels convenient....

15 April, 2026

A bill of materials is one of the most important records in any manufacturing business. It defines what goes into...

13 April, 2026

AI-Powered CAD File Management Beyond PDM Engineering teams create an enormous amount of knowledge in the course of building a...

12 April, 2026

A bill of materials is where product definition begins. Creating a bill of materials is a collaborative effort that typically...

10 April, 2026

Every time an engineer opens a product data management system, they face a small but real cognitive task before any...

10 April, 2026

OpenBOM will be presenting at Threaded in Miami, the startup gathering space hosted by Aras ACE 2026 at the Hilton...

9 April, 2026

In manufacturing, quality standards are not optional. They shape product quality, customer satisfaction, regulatory compliance, and the overall success of...

9 April, 2026

I’m coming to Share PLM Summit 2026, taking place on May 19–20 in Jerez de la Frontera, Spain. It the...

8 April, 2026

If you design, build, source, manufacture, or service products, the bill of materials is one of the most important documents...

To the top