PLM Was Built for MCAD. OpenBOM Is Building What Comes Beyond PLM

Oleg Shilovitsky
Oleg Shilovitsky
11 May, 2026 | 0 min for reading
PLM Was Built for MCAD. OpenBOM Is Building What Comes Beyond PLM

This is a deliberate architectural choice, not a roadmap promise. The data model was built to be source-neutral from the beginning. CAD files are inputs. Structured, connected product knowledge is the output. The distinction between those two things is what separates a file management tool from a product memory platform.

CAD is the source. Product data and product memory is the destination.

Related Posts

Also on OpenBOM

4 6
14 August, 2026

Excel is a natural lifeblood of every organization. We have “love and hate” relationships with Excel at OpenBOM. While we...

13 August, 2026

Seamless integration with design tools was always the main goal of OpenBOM. As such we’re expanding our integration with PCB...

13 August, 2026

Some of the most valuable product improvements are not new capabilities. They are the removal of repetition. Adding items to...

12 August, 2026

The demand for API usage has been growing dramatically in the last year. There are two observations here – an...

12 August, 2026

BOM Review started with a simple premise: catch data problems before they travel downstream to purchasing, manufacturing, and release. The...

11 August, 2026

Welcome to the OpenBOM August 2026 update! The August 2026 update brings important improvements across BOM validation, Public API access,...

6 August, 2026

I had a conversation with Rob Ferrone earlier this week and we decided to publish it. Rob spent 25 years...

5 August, 2026

Every company that validates a bill of materials produces two things. The first is the corrected BOM. Missing quantities filled...

4 August, 2026

The most dangerous request in a PLM implementation is not “can we import our Excel files?” Of course you can....

To the top