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
6 March, 2026

I’m excited to share what our team was working on recently and the updates we released in OpenBOM earlier this...

6 March, 2026

Modern products are no longer just mechanical. A smart appliance, an industrial machine, or an electric vehicle all combine mechanical...

5 March, 2026

In OpenBOM, Items are the starting point for building product structures. One Item can be used in several types of...

4 March, 2026

Managing procurement directly from engineering data is one of the powerful capabilities of OpenBOM. By connecting BOMs, inventory, and purchasing,...

3 March, 2026

A quick heads up on a user experience improvement for orders and PO / RFQ visibility in the dashboard.  If...

26 February, 2026

A change is not an ECO button, it is a connected process. Change management in engineering rarely starts with a...

25 February, 2026

For a long time, managing products meant managing mechanical structures. Assemblies, subassemblies, parts, revisions — the Bill of Materials was...

24 February, 2026

For the third consecutive year, OpenBOM has been recognized in the G2 Top 50 CAD & PLM Software list. When...

24 February, 2026

OpenBOM, a provider of cloud-native Product Data Management (PDM) and Product Lifecycle Management (PLM) software, today announced that it has...

To the top