PLM, SOLIDWORKS

Migrating from Vault (Autodesk PLM) to SOLIDWORKS

By Tim Paris on December 28, 2018

TriMech has developed a 12-phased approach to migrating data from one system to another. Typically, with PLM to PDM, we start off with a detailed analysis of the database. Then, we move on to the definition of what you are looking to do with your data. The complexity comes with all the features of a PLM system that a PDM system inherently does not have. Items, for instance, are records in the systems that may have a file, many files or no file associated with it. These have to be converted to a file-based system.  There are several other types of PLM features that will need to be addressed.

Face it, how often are you in a position to be touching every piece of data you have? When this comes up there are many things that can be done, from advanced renaming and restructuring to simple removal of duplication.

>> Learn what to do when PDM just isn't enough

Once we’ve determined what you are looking to do and how we can do it after interrogating your database we use this process below to get the job done right!

Phase 1: Project Initialization

Kick off the project by contacting the main point of contact. Then, acquire a fresh copy of the database to get things started.

Phase 2: Data Analysis

Put together an in-depth analysis of the database to formulate a plan of attack.

Phase 3: Disposition Generation

Then, we'll generate a disposition document to review. This will be our guide for the rest of the process.

Phase 4: Internal Proof of Concept (POC)

Next, you will create a custom toolset to perform tests of the data based on the disposition document.

Phase 5: Disposition Review

We provide you training to perform the required Disposition mappings and markups. This allows you to be involved early on in the process to help eliminate alignment issues between parties.

Phase 6: Disposition & Scope of Work

The disposition document is completed and validated for accuracy. The SOW is updated to reflect any custom rulesets or project specific details.

Phase 7: Remote Access Validation

We work with you to obtain suitable remote access to work with the data on your servers.

Phase 8: Internal Validation & Coding

Acquire a fresh version of the database and clone any existing systems for the next phases. This allows us to work and test without disruption of your current system. Toolsets are adjusted and validated.

Phase 9: First Pass Validation

This is the first migration of the data, with the database, in a test vault in PDM. We utilize the disposition document and all custom toolsets we developed in previous phases to complete this. You are then given training on how to validate this test vault and provided ample time in the project timeline to validate this test vault in the environment. This validation is a data integrity focused process.

Phase 10: Second Pass Validation

In this second validation, we take lessons learned in the first pass to make all final adjustments to the toolsets. We then provide any additional training for validation and allow for more time, so you can validate your vault. This validation is a continuation of data integrity with PDM system validation added.

Phase 11: Live Migration Schedule

After all signatures are complete from the last two phases, we will plan out the schedule for the live migration taking into consideration downtime and how to minimize it or eliminate it altogether.

Phase 12: Live Migration

This is the third migration with your data and database that has been tweaked and adjusted to your specifications. This final step will leave you with a new system that was thoroughly vetted by you.

Your migration is now complete. Enjoy!

View Implementation Services