Top 5 CAD BOM and EBOM Challenges in UPS Migration

Migrating to the 3DEXPERIENCE platform using Unified Product Structure (UPS), also known as “Powered by,” is not merely a system migration—it is a fundamental shift in how engineering data is structured, governed, and consumed across the enterprise. For organisations moving from legacy PLM or CAD-centric environments, UPS promises tighter alignment between design and engineering, improved multi-CAD collaboration, and a true single source of product truth.

However, realising these benefits requires more than data movement. One of the most underestimated complexities in a UPS migration is the alignment of CAD BOM and EBOM. Differences accumulated over years—across structures, naming conventions, revisions, and change processes—often surface during migration and can derail timelines if not addressed proactively. Understanding these challenges early is critical to ensuring a smooth, scalable transition to 3DEXPERIENCE.

Unified Product Structure (UPS) is Dassault Systèmes’ approach to harmonising CAD BOM (Bill of Materials) and EBOM (Engineering BOM) within the 3DEXPERIENCE platform. It enables:

• Seamless multicad design (SOLIDWORKS, CATIA V5, etc.)
• Integrated simulation and manufacturing workflows
• Elimination of data silos across ECAD, MCAD, and software
• Real-time collaboration and front-loaded manufacturing planning

By unifying CAD and EBOM data, UPS simplifies lifecycle management and accelerates product development.

Legacy systems often maintain separate structures and naming conventions for CAD BOM and EBOM. This leads to mismatches such as:

• EBOM containing parts not modelled in CAD (e.g., fasteners, packaging)
• CAD BOM including helper geometries irrelevant to EBOM

Solution: SteepGraph recommends a structured approach:

• Extract both BOMs and identify connections
• Compare and merge structures
• Tag EBOM-only parts as non-CAD items
• Map attributes from both sources
• Use Enterprise Item Number (EIN) to retain EBOM naming

This ensures a unified structure visible across CAD and PLM apps.

It’s common for CAD and EBOM revisions to be out of sync. For example:

• CAD revision B linked to EBOM revision A
• EBOM revision B ahead of CAD revision A

Solution: Depending on business needs:

• Align revisions during migration
• Create new CAD revisions if EBOM is ahead
• Maintain flexibility to preserve title blocks or downstream document references

SteepGraph’s migration tools allow runtime creation of revisions and mapping of attributes to ensure consistency.

Organisations may use separate change actions for CAD and EBOM, or a shared one. Migrating this data requires careful planning.

Solution:

• Prefer completing open changes before migration
• If not possible, ensure changes are in draft or in-work state
• Disconnect legacy items from change actions
• Reconnect new UPS product structures to existing or newly created change actions

This preserves traceability while aligning with organisational workflows.

CAD and EBOM structures often have associated documents—specifications, drawings, derived outputs. Migrating these without losing context is critical.

Solution:

• Extract all related documents
• Connect them to the unified UPS product structure
• Ensure visibility across design and downstream teams

This enables full utilisation of 3DEXPERIENCE’s collaborative capabilities.

Migrating to UPS is more than a technical upgrade—it’s a strategic shift toward digital continuity.