Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

COE 2016: Technical Data Migration Made Simple

1,844 views

Published on

Jonathan Scott discusses PLM/data migration challenges

Published in: Software
  • Be the first to comment

COE 2016: Technical Data Migration Made Simple

  1. 1. Technical Data Migration Made Simple Jonathan Scott Razorleaf Corporation
  2. 2. • Monday » 4115: (DEM) Technical Data Migration Made Simple 11:35:00 AM - 12:25:00 PM | Jonathan Scott » 4114: (COL) LIVE DEMO: How to Get to Full Digitalization 4:35:00 PM - 5:25:00 PM | Brian Lau, Jonathan Scott • Tuesday » 4116: (IDM) LIVE DEMO: ENOVIA 2013x Tips 2:00:00 PM - 2:50:00 PM | Michael Craffey, Brian Lau • Wednesday » 4113: (COL) 10 Cool Tools for 2016 12:05:00 PM - 12:35:00 PM | Jonathan Scott
  3. 3. Explaining the Title • What I’m NOT going to do: » Make the activity of migrating technical data easier » Give advice on technical migration mechanics
  4. 4. Explaining the Title • What I’m NOT going to do: » Make the activity of migrating technical data easier » Give advice on technical migration mechanics • What I AM going to do: » Make technical data migrations easier to understand » Give you a framework for explaining it to others
  5. 5. Moving is Painful
  6. 6. Why is Moving Painful? • The process is time-consuming • Valuables can be broken & lost • You need to clean-up first (or you risk moving junk) • No room for error
  7. 7. Why is Moving Data Migration Painful?
  8. 8. Why is Moving Data Migration Painful? • The process is time-consuming • Valuables can be broken & lost • You need to clean-up first (or you risk moving junk) • No room for error
  9. 9. Moving Cost Variables • How many houses (to/from) • How many rooms per house • How many levels per house • Heavy/large furniture • Room-specific delivery • Acceptable breakage (insurance)
  10. 10. Data Migration Variables • Homogeneousness / congruity • Required accuracy (iterations) • Needed transformations • Metadata or files or both • Inter-relationships (CAD links) • Location in Space (logical location) • History (versions/revisions)
  11. 11. Where Are We Going? PLM
  12. 12. Where Are We Going? PLM
  13. 13. Data Sources: Homegrown Access DB Access PLM
  14. 14. Data Sources: Network File Servers Access Windows PLM
  15. 15. Data Sources: ERP System Access Windows ERP PLM
  16. 16. How Are We Getting There? Access Windows ERP PLM
  17. 17. ECOs Data Streams: ECOs Access Windows ERP PLM
  18. 18. ECOs BOM Data Streams: BOMs & Comps Access Windows ERP PLM
  19. 19. ECOs PDF(ECO) PDF(Drwg) BOM Data Streams: PDFs Access Windows ERP PLM
  20. 20. ECOs ECO-Comp PDF(ECO) PDF(Drwg) BOM Data Streams: ECO-Comp Access Windows ERP PLM
  21. 21. ECOs ECO-Comp ECO-Drwg PDF(ECO) PDF(Drwg) BOM Data Streams: ECO-Drwg Access Windows ERP PLM
  22. 22. ECOs ECO-Comp ECO-Drwg Comp-Drwg PDF(ECO) PDF(Drwg) BOM Data Streams: Comp-Drwg Access Windows ERP PLM
  23. 23. ECOs ECO-Comp ECO-Drwg Comp-Drwg PDF(ECO) PDF(Drwg) BOM OrCAD Data Streams: Electrical CAD Access Windows ERP PLM
  24. 24. ECOs ECO-Comp ECO-Drwg Comp-Drwg Microstation PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD Data Streams: Mechanical 2D CAD Access Windows ERP PLM
  25. 25. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD Data Streams: Mechanical 3D CAD Access Windows ERP PLM CATIA
  26. 26. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD Data Streams: Office Docs Access Windows ERP PLM CATIA
  27. 27. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Data Streams: PDF Relationships Access Windows ERP PLM CATIA
  28. 28. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Unnecessary Data Streams Access Windows ERP PLM CATIA
  29. 29. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Data Streams & Revision History Access Windows ERP PLM CATIA
  30. 30. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Data Streams & Accuracy Access Windows ERP PLM CATIA 90%
  31. 31. Estimating ECO Data Stream • Latest revision only • Metadata without files • 90% accuracy means only 3 iterations
  32. 32. Estimating ECO Data Stream • Latest revision only • Metadata without files • 90% accuracy means only 3 iterations • 2 days to develop the process • 3 days to automate the process • 2 days for refinement 1 • 1 day for refinement 2
  33. 33. Estimating CATIA Data Stream • Full revision history • Metadata and files, files links, links to “space” • 90% accuracy means only 3 iterations
  34. 34. Estimating CATIA Data Stream • Full revision history • Metadata and files, files links, links to “space” • 90% accuracy means only 3 iterations • 8 days to develop/automate the process • 4 days for refinement 1 • 2 days for refinement 2
  35. 35. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Data Stream Estimates Access Windows ERP PLM CATIA 90%
  36. 36. ECOs ECO-Comp ECO-Drwg Comp-Drwg SolidWorks Microstation OfficeDoc PDF(ECO) PDF(Drwg) BOM AutoCAD OrCAD PDF-Native Data Stream Estimates Access Windows ERP PLM CATIA 90%
  37. 37. Migration Accuracy 90% = 110 days (3 iterations)
  38. 38. Migration Accuracy 90% = 110 days (3 iterations) 95% = 121 days (4 iterations) 98% = 133 days (5 iterations) 99% = 146 days (6 iterations)
  39. 39. Always Ask Questions • Which file types are included/excluded? • Which locations/sources are included/excluded? • Latest versions or full revision history? • Correlation of native files to static files? • Will security be maintained? • How accurate will the results be?
  40. 40. Data Migration Key Factors • Homogeneousness / congruity • Required accuracy (iterations) • Needed transformations • Metadata or files or both • Inter-relationships (CAD links) • Location in Space (logical location) • History (versions/revisions)
  41. 41. Data Migration Key Factors • Congruity
  42. 42. Data Migration Key Factors • Congruity • Accuracy required (iterations)
  43. 43. Data Migration Key Factors • Congruity • Accuracy required (iterations) • Transformation needed
  44. 44. Data Migration Key Factors • Congruity • Accuracy required (iterations) • Transformation needed • Files or just metadata
  45. 45. Data Migration Key Factors • Congruity • Accuracy required (iterations) • Transformation needed • Files or just metadata • Inter-relationships (CAD links)
  46. 46. Data Migration Key Factors • Congruity • Accuracy required (iterations) • Transformation needed • Files or just metadata • Inter-relationships (CAD links) • Space (logical location)
  47. 47. Data Migration Key Factors • Congruity • Accuracy required (iterations) • Transformation needed • Files or just metadata • Inter-relationships (CAD links) • Space (logical location) • History (versions/revisions)
  48. 48. Moving is Painful
  49. 49. Contact Us Jonathan.Scott@Razorleaf.com www.Razorleaf.com

×