3DEXPERIENCE has two ways to upload existing SOLIDWORKS files into a cloud tenant. Both solutions do latest version of file only, so you won’t have version history for the initially migrated data. Instead, you’ll have every file set as the system’s initial revision, typically A. Now those two methods I mentioned a second ago are as follows:

  1. Bulk load tool
  2. EDAT FTK (File based Transfer)

Both processes have some similarities in what they do and how they do it. That said, there are some distinct difference between them. So, this post will concentrate on the EDAT FTK method and when to use it over the Bulk Load method. Make sure you check out our blog later this week for a post all about using the Bulk Load method.

EDAT FTK – High-Level Overview

Use EDAT FTK to upload SOLIDWORKS files to the 3DEXPERIENCE Platform.

The EDAT FTK solution is really an extension of the Bulk load tool as under the covers it uses the Bulk Load application to load the data. Where EDAT FTK really shines is how it improves the speed and tracking for uploading files. In fact, there are three additional functions that make EDAT FTK such an appealing option:

  1. Uses SQL DB to track information
  2. Ability to analyze data and find issues before trying to load
  3. Ability to import data from multiple machines (decreasing time to load)

Upload to 3DEXPERIENCE with EDAT FTK – Process

We can break uploading SOLIDWORKS files to the 3DEXPERIENCE Platform with EDAT FTK into four phases.

  1. Stage Data
    • With EDAT FTK, we process one folder at a time.
    • Before we stage the data, we do need to make sure to address any duplicate file names.
  2. Analyze
    • Generate reports to help us identify some potential problems such as:
      • illegal characters in filename, configuration name, etc
      • Missing references
      • Data integrity (needs rebuild)
      • Length of file name (maximum length without extension is 208 characters)
    • We’ll then exclude any data identified in the reports from the import.
      • Exception – there is option to ignore the rebuild items from exclusion.
  3. Job Sequencer
    • Use ActiveMQ for generating tasks
    • Sequencer loads Parts first, then Assemblies, and lastly Drawings
    • Depending on structure of data there may be multiple sets of data to sequence
      • As an example, you could see these four sets in your data.
        • Parts
        • Sub Assemblies
        • Top level Assemblies
        • Drawings
  4. Importer
    • Client machine that has SOLIDWORKS Connector installed and connected to 3DEXPERIENCE tenant.
    • Communicates with ActiveMQ and SQL DB for managing status of import
      • We can use multiple machines to process data at the same time because we’re using ActiveMQ and SQL DB.
    • Uses Bulk load application to process jobs.

Why use EDAT FTK to Upload SOLIDWORKS Files?

Unknown data integrity for SOLIDWORKS Files

The analyze phase allows you to find the issues before the import starts by making sure the filenames conform to new system and validating there are no missing files. This is crucial because we could break references with invalid file or configuration names.

Large amount of Data to Upload to 3DEXPERIENCE

We want to start working on the Platform as soon as possible. Downtime means lost productivity, and we don’t want that. So get you up and going faster by load balancing import across multiple machines.

Better tracking

Using a SQL DB and ActiveMQ for managing the import allows for greater visibility on the overall process and tracking of errors/issues during the import process. This means better tracking and better debugging to understand the overall process.

  • Share this
Find Your Design Solution in the CATI Store.
Browse Products