data migration 2.0
TRANSCRIPT
![Page 1: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/1.jpg)
data migration.
![Page 2: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/2.jpg)
We believe customers should be assisted in making informed decisions about Product
Lifecycle Management
o Learn more about us and how we can help you implement a Product Lifecycle Management (PLM) Platform tailored to support your business model and focused on your business initiatives.
At zerowait-state.com“PLM is in our DNA”
Zero Wait-State.
![Page 3: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/3.jpg)
•Established in 1999
•SolidWorks Partner: EPDM
•Oracle Gold Partner: Agile PLM
•PLM Implementation, Integration and Data Migration
•Core competencies: All Agile PLM Modules
our company.
![Page 4: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/4.jpg)
our customers.
![Page 5: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/5.jpg)
core competencies.
![Page 6: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/6.jpg)
implementation products.
![Page 7: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/7.jpg)
integration products.
![Page 8: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/8.jpg)
We have extensive research in PLM and data migration.– Major migrations at
John Deere, Dell, Raytheon and Maxtor
– Successful migrations from Intralink and PDMLink to Enterprise PDM
the experience.
![Page 9: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/9.jpg)
Data migration is hard...very very hard.
Data condition is a variable hard to predict which must be done without disrupting current production environment
the facts.
![Page 10: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/10.jpg)
• It’s a critical process.
• Product data is the lifeblood of a company
• Bad data can render a PLM or PDM system useless
the process.
![Page 11: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/11.jpg)
the big bang bad idea.
• Moving it all is problematic
• Moving increments is more manageable
• Eliminates time constraints
• Reduces Risks
![Page 12: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/12.jpg)
• Extracting and transferring history to a new PLM is challenging
• Most companies rarely access earlier versions of data
• Using a “latest only” dramatically reduces costs and complexity
history is best forgotten.
![Page 13: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/13.jpg)
• Just because you can migrate all your data, doesn’t mean you should.
• Take a hard look at legacy data and be selective
• Do not pollute your new system with corrupt or inaccurate data
• Don’t “under provision” hardware
• Identify needs and have analysis of data cleansing solutions ready
• Clean up data as much as possible
garbage in, garbage out.
![Page 14: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/14.jpg)
• Two test passes and a production pass are minimum recommendations for most migrations
• Have a specific test plan to evaluate data in the test system
• Resist the urge to truncate testing
test. validate. repeat.
![Page 15: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/15.jpg)
mission accomplished.
• Moving Intralink 3.4 to enterprise PDM• Joint project with GoEngineer• Extracted meta data and binary files from
Pro/Engineer from Intralink • Used drag and drop to load the CAD files and an
import tool for GoEngineer for the meta data• Customer was successful and shut down two
servers
![Page 16: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/16.jpg)
mission accomplished.
• Moving from PDMlink 9.0• Joint project with GoEngineer• Using drag and drop to load the CAD files
and sent meta data to Agile PLM• Customer successfully transitioned from
PDMLink to Agile PLM and EPDM
![Page 17: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/17.jpg)
conclusion.
1. Data migration is tricky
2. Data migration is important
3. Preparation and planning can alleviate issues
4. Incremental migration without history is best
5. Beware of undermining the difficulty of migration
![Page 18: Data migration 2.0](https://reader033.vdocuments.mx/reader033/viewer/2022052505/555f3824d8b42a65118b50bc/html5/thumbnails/18.jpg)
zero wait-state.
follow us!!
www.facebook.com/zerowaitstate
http://linkd.in/VqVdda twitter.com/zerowaitstate