TriMech has developed a 12-phased approach to migrating data from one system to another. Typically, with PDM 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 mapping one utility version of features to PDM’s version of features.
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.
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. Follow that by acquiring a fresh copy of the database to get things started.
Phase 2: Data Analysis
Perform an in-depth analysis of the database to formulate a plan of attack.
Phase 3: Disposition Generation
Then, generate a disposition document to review with the customer. This will be our guide for the rest of the process.
Phase 4: Internal Proof of Concept (POC)
Next, you'll create a custom toolset to perform tests of the data based on the disposition document that is built on top of a robust, proprietary TriMech API.
Phase 5: Disposition Review
We provide you training to do the required Disposition mappings and markups. This allows you to be involved early in the process to help eliminate alignment issues between both parties.
Phase 6: Disposition & Statement Of Work (SOW)
In this phase, 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
Acquiring a fresh version of the database is critical here to ensure up-to-date information. Then, we clone any existing systems for the next phases. This allows us to work and test without disruption of your current system while 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. By utilizing the disposition document, and all custom toolsets made in previous phases, we were able to complete this. You are then given provided training on how to validate this test vault and provided ample time in the project timeline to validate this test vault in their 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 their 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 2 phases, we 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. We’ve tweaked and adjusted it to your specifications. This final step will leave you with a new system that you have thoroughly vetted.
Your migration is now complete. Enjoy!
Ready to make the switch to SOLIDWORKS? Download our SOLIDWORKS Buyer's Guide to discover the right package for you!