Would you like to learn about the different migration paths that are officially supported today, when you need to import SOLIDWORKS data currently stored externally, to be connected with PLM Collaboration Services and revealed in the 3DEXPERIENCE platform?
Let's look at each path, solution and its scope as of today...
The most important consideration is the way the legacy data is stored. Is the data purely file-based, or is it managed by another PDM/PLM (possibly an in-house ad hoc approach)?
If your answer to this simple question is: "Yes I'm file-based BUT...," then you will probably end up in the second category.
In many cases, where people first claim they have a file-based storage, we eventually find out that there is additional data aggregated in some adjacent repository. For example, it can be as simple as maintaining a file-naming convention to encode a variation, a history or a revision scheme (e.g. part42-B-v8-r15970). This amounts to having a PDM mechanism in place, which has to be accounted for.
Let's start with the first category: File-based import.
Prior to using the Dassault Systemes PLM Collaboration Services for SOLIDWORKS, customers often have accumulated many unmanaged SOLIDWORKS files. These customers usually wish to bring these existing SOLIDWORKS files into the 3DEXPERIENCE platform. Of course, they can do it manually by loading these files in a SOLIDWORKS Desktop interactive session and saving them directly to the 3DEXPERIENCE platform through the 3DEXPERIENCE PLM Collaboration Services task panel — but this one-by one approach could prove time consuming for many scenarios.
Since R2018xFD04, the DS batch command-line utility has the ability to save one single file, assembly or drawing, or an entire directory of such files into the 3DEXPERIENCE platform.
Saving SOLIDWORKS files into the 3DEXPERIENCE platform using this process, involves three components:
- A new command-line executable provided on the client via the SOLIDWORKS Connector installation (SaveInto3DEXPERIENCE.exe). Note that the default location is:
C:\\Program Files\\Dassault Systemes\\B420xcadconnectors\\win_b64\\USWC\\
- The IEF Client Workspace Service
- The server
Saving SOLIDWORKS assembly structures this way is similar to saving the said structures from a SOLIDWORKS interactive session.
Second category: Legacy PDM-based import
Since 2017, ENOVIA provides tool kits to partners to help deploy the 3DEXPERIENCE platform.
This EDAT portfolio is made up of three migration kits:
- SmarTeam Migration Toolkit
- SOLIDWORKS ePDM Migration Toolkit
- DEC migration toolkit
Migration tool features :
- Comprehensive data migration to the 3DEXPERIENCE platform unified product structure (UPS) to ensure data integrity and quality
- Modular design for better performance and traceability
- Full mode and update mode migrations
- Imports to UPS supporting:
- Attribute mapping
- Customized revisioning/versioning
- Workflow/life-cycle mapping
- Custom user name mapping
- Fully automated migration process using automation tool set
- Failed job restart
- Comprehensive report about legacy data, including information on missing files, invalid file names, orphaned parts, etc. provided at data analyzer stage
- Message logging in XML format for review and reporting of the migration process
The release of the EDAT suite featuring full support for SOLIDWORKS data import is tentatively planned for end of September.
For more information or questions please comment on this post or submit an iQuestion.
