VIDEO How-To Fix Cyclic References in Engineering BOM Created From CAD Assemblies

Oleg Shilovitsky
Oleg Shilovitsky
28 January, 2025 | 3 min for reading
VIDEO How-To Fix Cyclic References in Engineering BOM Created From CAD Assemblies

When working with engineering BOMs (Bills of Materials) derived from CAD assemblies, one common and frustrating issue is the occurrence of cyclic references or loops. These can lead to confusion, errors, and inefficiencies in your design and manufacturing processes. In this article, we break down how cyclic references happen and provide a structured approach to identifying and resolving them using OpenBOM.

Understanding Cyclic References

Cyclic references occur when relationships within a BOM point back to themselves or create an endless loop of dependencies. This problem often arises due to the following reasons:

  1. Messy CAD Data: Engineering data exported from CAD systems can be inconsistent, especially when part numbers are not assigned correctly.
  2. File Name Dependencies: Engineers often rely on file names as identifiers. However, file names can overlap (e.g., using the same name for an assembly and a part), leading to circular relationships.
  3. Configuration Complexity: Part numbers reused across different configurations or versions of components can also result in loops because of the same Part Numbers assigned to multiple configurations .

Why Fixing Cyclic References is Critical

Cyclic references create mistakes in product structures, making it difficult to:

  • Generate accurate BOMs for production and procurement 
  • To allow OpenBOM flattened BOM functionality to work
  • Ensure traceability and data integrity.

Resolving these issues early in the design process is essential for ensuring smooth transitions from engineering to manufacturing.

Step-by-Step Guide to Fix Cyclic References in OpenBOM

The following process outlines how to identify and resolve cyclic references in engineering BOMs created from CAD assemblies:

1. Identify Cyclic References

  • Use OpenBOM to import the BOM generated from your CAD system.
  • Navigate to the BOM and expand sub-level or switch to ‘flattened BOM”
  • Check for duplicate part numbers or references that appear multiple times in conflicting roles (e.g., a part listed as both a component and an assembly).
EBOM CAD circular reference find root cause

Open the problematic BOM: 

EBOM CAD circular reference navigate to BOM

2. Review Part Number Assignments

  • Ensure that each part and assembly has a unique, clearly defined part number.
  • Avoid using file names or generic identifiers as part numbers.
  • Create a naming convention that distinguishes between parts, assemblies, and configurations.
EBOM CAD circular reference in BOM display

3. Correct Relationships

  • Remove duplicate or conflicting references within the BOM.
  • Edit or replace part numbers to resolve overlaps.
  • For assemblies with cyclic references, redefine parent-child relationships to create a clear hierarchy.

4. Validate the Updated BOM

  • Re-import the updated BOM into OpenBOM and confirm that cyclic references are eliminated.
  • Use OpenBOM’s validation tools to verify the integrity of the relationships.
  • Generate test reports to ensure that all connections align with the intended product structure.
EBOM CAD circular reference resolved

Best Practices to Prevent Cyclic References

  1. Standardize Part Numbering: Establish a robust part numbering system to avoid conflicts and duplicates. Note, relying on file names for part numbers is a bad idea. 
  2. Organize CAD Data: Maintain clean, well-structured data in your CAD system to minimize errors during BOM generation.
  3. Use OpenBOM for Real-Time Collaboration: OpenBOM’s cloud-based platform enables teams to collaborate on BOMs in real time, reducing the likelihood of introducing errors.

Watch the Video Tutorial

For a hands-on walkthrough of this process, watch our detailed video tutorial.

This video demonstrates:

  • How cyclic references form in engineering BOMs.
  • Step-by-step instructions to resolve loops using OpenBOM.
  • Tips to streamline your BOM creation process for better results.

Conclusion

Cyclic references in engineering BOMs can disrupt workflows and impact product development timelines. By understanding their causes and following the structured approach outlined above, you can eliminate these issues and ensure smooth collaboration between engineering and manufacturing teams. OpenBOM’s powerful tools and cloud-native platform make this process efficient and effective.

Ready to take control of your BOMs? Visit OpenBOM to learn more and start improving your engineering data today.

Best, Oleg

Related Posts

Also on OpenBOM

4 6
28 August, 2025

In 2025, the push for better design-to-manufacturing integration is stronger than ever. But for many companies, this still gets reduced...

27 August, 2025

For decades, PDM meant file vaults, check-in/check-out, and revision control. But today’s products span mechanical, electronic, and software domains, with...

26 August, 2025

This article is part of OpenBOM BOM Excel MCP building in public. For the next few weeks, we are going...

22 August, 2025

In yesterday’s article – Understanding OpenBOM’s Multi-Tenant Data Model and System Configuration, I shared some insights about OpenBOM’s multi-tenant data...

21 August, 2025

In today’s manufacturing and engineering world, the term multi-tenant triggers both questions and confusion. Product Lifecycle Management (PLM) has historically...

20 August, 2025

Since the very beginning of OpenBOM, our mission has been to help engineers, manufacturers, and teams organize product information and...

19 August, 2025

There is a need for a rich and structured context.  Artificial intelligence has quickly become the buzzword in every boardroom,...

15 August, 2025

A recent post by Martijn Dullaart on LinkedIn about Product Changes caught my attention. Here is the link to the...

14 August, 2025

Let’s be honest, most conversations about innovation and manufacturing gravitate toward sleek CAD models, breakthrough technology, or ambitious product roadmaps....

To the top