Importing Foreign CAD Data into Your Product Structure

Introduction

In today’s global and collaborative engineering landscape, teams frequently need to incorporate foreign data—such as supplier-provided components, legacy designs, or multi-CAD assemblies—into their product lifecycle management (PLM) systems. However, importing this data without disrupting existing product structures, losing critical metadata, or creating duplicates can be a challenge. We will now take a look at the methods available to import foreign CAD data into a product structure using 3DEXPERIENCE.

Import Methods

The 3DEXPERIENCE platform supports multiple methods for importing foreign CAD data, each tailored to different needs, workflows, file formats, and user roles. These methods range from direct manual imports via cloud-based tools to automated, programmatic approaches, ensuring flexibility for design, engineering, and manufacturing teams. 

IP Import

The IP Import application on the 3DEXPERIENCE platform is a dedicated tool for importing CAD data without requiring designer intervention. It is ideal for business processes managed outside the design department, such as supplier collaborations or incremental updates. For a quick primer on this application in the earlier blog post, A Quick Look at a New App – IP Import.

Key Features

  • Supported Formats: Handles a wide range of CAD formats and Industry Foundation Class (IFC) files, which are standard in the AEC (Architecture, Engineering, Construction industry.
  • Bulk Imports: Supports single-file or bulk directory imports, including sub-directories and assembly child links.  
  • Incremental updates: If the same structure is re-imported, only changes (new or modified components) are processed, avoiding duplication. This is managed via "Scope"—data imported under the same scope is checked against prior imports, while different scopes treat data as new.

Use Cases

  • Supplier-driven design updates.
  • AEC workflows requiring IFC file integration.
  • Business processes where designers should not manually handle imports.

 

Direct Import using the Authoring Tools 

Users working within a specific CAD solution can utilize the import tools to load the CAD data into session. The PowerBy integration for each CAD authoring tool enables users to then save to the 3DEXPERIENCE platform maintaining digital continuity between design and downstream applications. This method would put the burden on the user to maintain uniqueness of imported data and avoid duplicity of multiple imports of the same data. For a quick primer on Power’By tools, take a look at the post, MySession – Access from the CAD Desktop.

Key Features

  • Digital Continuity: Ensures versioning, history, and vaulting of CAD data are preserved when saved to the platform.
  • Restricted Editing: Non-design users cannot modify the CAD master, protecting design integrity and links as all data passes through the design authoring tools.

Use Cases

  • Design teams using CAD who need to push data to the platform seamlessly.
  • Explicit loading  of data for unique design scenarios with Suppliers or Co-development or 3rd part design firms.

Programmatic Import with VBA Automation

For STL files (common in additive manufacturing and 3D scanning), the platform supports VBA automation within the Digitized Shape Preparation app. This role is available in the Mechanical & Shape Engineer role. This method is ideal for large-scale or repetitive imports. This method also supports other neutral formats such as IGES and STEP. The Knowledge Base contains a good article on this topic called Importing .STL Files in the 3DEXPERIENCE Platform using VBA Automation.

Key Features

  • Automation Scripts: Users can write VBA scripts to control the import process, including file path selection and format specification.
  • Efficiency: Reduces manual effort for repetitive tasks, such as importing multiple STL files for prototyping.

Use Cases

  • Additive manufacturing workflows.
  • Batch processing of 3D scan data.
  • Integration with custom scripts or pipelines.

 

Event-Driven Import via MyX-CAD and Myx-PDM

For advanced users or custom applications, the MyX-CAD and MyX-PDM tools enable event-based imports using web services. These tools are available within the X-PDM Integration for PDMS role. This method is highly customizable and suitable for integrating legacy systems or proprietary data formats.

Key Features

  • Event Exchange Services: Triggers imports when specific events occur such as saving a file.
  • Custom Data Types: Supports proprietary formats like .CAAasm (assembly data) and allows users to define their own import logic.
  • Add-in Integration: Requires loading MyX-PDM add-ins into the MyX-CAD application to enable the "Send to 3DEXPERIENCE Platform" command [3].

Use Cases

  • Custom PLM integrations
  • Legacy system migrations
  • Proprietary CAD data formats

 

Batch Import using EDAT

EDAT (Enterprise Data Migration Toolkit) is a modular migration tool designed specifically to handle the batch import of CAD data and other file-based formats into the 3DEXPERIENCE platform. It automates the migration of assemblies, parts, drawings, and associated metadata while preserving structural relationships, reducing manual effort, and minimizing errors during large-scale data transfers. 

 

Key Features

  • Validation Steps: Includes status checks and post-import validation
  • Scalability: Ideal for enterprise-level migrations with thousands of files

Use Cases

  • Enterprise PLM migrations
  • Bulk historical data imports

Comparison of Methods

Method

Best For

Key Advantages

Limitations

IP Import 

Supplier updates, IFC files

Incremental updates, bulk imports, scope management

Limited to supported formats

Direct Import using the Authoring Tools

Design continuity

Versioning, digital thread

Restricts edits for non-design users

Programmatic Import with VBA Automation

STL files, batch processing

Programmable, efficient for repetition

Requires scripting knowledge

Event-Driven Import via MyX-CAD and Myx-PDM

Custom integrations

Highly flexible, event-driven

Complex setup

Batch Import using EDAT

Enterprise migrations

Scalable, automated

Requires PLM tooling

 

To select the best method for your import needs, consider your workflow requirements (e.g., need for editing, automation, or material assignment), file formats, and scale (single files vs. bulk migrations). For example, if you’re working with supplier-driven incremental updates, the IP Import App is likely your bexst solution, while VBA automation suits the repetitive STL imports for additive manufacturing. For legacy CAD data, PowerBy ensures continuity, but batch tools like EDAT FTK may be better for large-scale migrations.