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
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...

5 October, 2026

An open cloud architecture connecting design and engineering information I’m starting a series of articles this week to speak about...

3 October, 2026

Welcome to the OpenBOM October 2026 update! This month we’re putting AI to work on one of the oldest chores...

1 October, 2026

For most of my career in engineering software, I have watched teams turn a bill of materials into purchase orders...

1 October, 2026

Team ownership is an administrative detail right up until the day it becomes a blocker. People change roles. An engineering...

28 September, 2026

Last Friday, I published Everyone Wants to Build the Engineering Harness. But What Will It Run On?. My argument was...

To the top