Quick-Start with CAD & Legacy Data Imports (Day 23 of 30) 

I continue my 30 days blogging journey. Yesterday, I outlined how customers can start using OpenBOM and today we do a first step in this journey – start using CAD add-ins and spreadsheet imports. This is a technical overview of how to turn CAD assemblies or spreadsheets into structured, connected BOM data inside OpenBOM.

The most efficient way to begin working with OpenBOM is to bring in data you already use—either from your CAD system or from existing spreadsheets. These two sources represent the majority of early engineering and manufacturing data, and OpenBOM is designed to convert both into structured, consistent, multi-level BOMs with minimal manual effort.

This article explains the underlying mechanics of how imports work, what OpenBOM extracts, how it structures the data, and why this step is the functional foundation for everything that follows in Days 24–30.

Starting With an Existing Dataset

Most companies already maintain product data in one of two forms:

1. CAD assemblies that implicitly contain structured component and metadata relationships.
2. Excel or CSV spreadsheets that explicitly list parts, quantities, and properties.

OpenBOM reads both kinds of data and transforms them into:

• structured item objects
• multi-level product structures
• catalogs representing reusable item definitions
• property sets and metadata
• relationships between objects

This conversion is instantaneous and requires no reformatting of the source data.

CAD → BOM: Functional Overview

OpenBOM integrates with major mechanical and electronic CAD tools (SolidWorks, Autodesk Fusion 360, Autodesk Inventor, Onshape, Altium, and others). Each integration follows the same functional pattern:

1. Plugin reads the CAD assembly tree. The add-in accesses the CAD model’s structure via the CAD API, extracting the hierarchy of assemblies, subassemblies, and components.
   
2. Extraction of metadata. The integration retrieves part numbers, names, materials, custom properties, configuration information, and suppressed/unsuppressed states (depending on CAD capabilities).
   
3. Transmission to OpenBOM. The plugin sends the structured data to OpenBOM using documented APIs.
   
4. Transformation into multi-level BOM. OpenBOM converts the incoming structure into a multi-level, navigable BOM. Each row becomes an item reference, each item becomes part of a catalog, and relationships form automatically.
   
5. Creation or update of item records. If matching items already exist in a catalog, OpenBOM reuses them instead of creating duplicates.

The result is a BOM that reflects the CAD structure exactly—without manual creation, copy/paste, or data transcription.

To learn more about starting using OpenBOM check the YouTube OpenBOM How to Series playlist. The following video is an example of how to start using OpenBOM with SoliWorks. 

Excel → BOM: Functional Overview

Legacy spreadsheets often contain mixed-quality data—multiple tabs, inconsistent column names, formatting variations, or ad hoc property definitions. OpenBOM is designed to tolerate this variability.

The import sequence is:

1. File ingestion. The user uploads an Excel, CSV, or Google Sheet export.
   
2. Column detection and mapping. OpenBOM automatically identifies common fields (part number, name, description, quantity, cost, vendor, etc.). If needed, the user maps remaining fields manually.
   
3. Generation of item objects. Each spreadsheet row becomes an item, with its properties stored in a catalog.
   
4. Construction of BOM. Items are compiled into a BOM that reflects the spreadsheet’s structure—flat or (via option) hierarchical.
   
5. Standardization of properties. Imported columns become editable properties with types (text, numeric, list, etc.) and can be normalized later.
   

This import pathway allows teams to convert existing spreadsheet-based processes directly into structured, reusable product data.

What Happens After Data Is Imported

Whether the data originates from CAD or Excel, the result is the same data structure inside OpenBOM:

• BOM: A list of item references with quantities and levels.
• Items: Individual object records stored in one or more catalogs.
• Catalogs: Reusable definitions of items shared across multiple BOMs.
• Properties: Metadata attached to items or BOM rows.
• Relationships: Links between assemblies, subassemblies, and items.

This structure supports:

• hierarchical navigation
• “where used” indexing
• real-time simultaneous editing
• data sharing across users and companies
• downstream integration to procurement (RFQ/PO)
• data cleanup and normalization (covered in Day 24)

The import process produces a functional digital representation of a product with no manual modeling effort.

Combining CAD and Spreadsheet Data

Many companies maintain some information in CAD (engineered items) and other information in spreadsheets (purchased or non-modeled components). OpenBOM allows these data sources to merge cleanly.

• CAD import creates mechanical item objects.
• Excel import creates purchased/electronic item objects.
• Both populate the same catalog or multiple catalogs.
• BOMs reference items regardless of source.

This removes the need for parallel manual reconciliation in spreadsheets and ensures that downstream processes (procurement, costing, supplier management) use a unified data source.

Practical Recommendations for First-Time Users

To begin using OpenBOM effectively:

• Start with a small test dataset—one simple assembly or one spreadsheet.
• Validate that the imported structure matches expectations.
• Examine item reuse and “where-used” visibility.
• Verify that quantities and levels were interpreted correctly.
• Observe how imported properties map into catalogs.

For more information about how to start using OpenBOM, check this YouTube playlist – OpenBOM How To Series. 

This initial step provides a stable foundation for the work in upcoming articles:

• Day 24: Catalogs and part numbering
• Day 25: Linking objects into a digital thread
• Day 26: Connecting BOMs to RFQs, PO creation, and procurement

The purpose of Day 23 is functional onboarding, not full process definition.

Conclusion

The fastest, lowest-friction way to start with OpenBOM is to load existing data—either directly from CAD or from legacy Excel files. These imports establish the product structure, item definitions, and metadata required for all further steps in the OpenBOM workflow.

Once data is inside OpenBOM, users can gradually normalize, clean, link, and extend it across engineering, procurement, and supplier collaboration processes. This is the beginning of that structured data transformation.

If you feel ready, REGISTER FOR FREE and start your OpenBOM journey- in 1-2 hours, you will discover how you can transform your work. 

Best, Oleg