Jonathan Scott discusses PLM/data migration challenges

1. Technical Data Migration
Made Simple
Jonathan Scott
Razorleaf Corporation

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. 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. 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. Moving is Painful

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. Why is Moving Data Migration Painful?

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

10. 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)

11. 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)

12. Where Are We Going?
PLM

13. Where Are We Going?
PLM

14. Data Sources: Homegrown Access DB
Access
PLM

15. Data Sources: Network File Servers
Access Windows
PLM

16. Data Sources: ERP System
Access Windows ERP
PLM

17. How Are We Getting There?
Access Windows ERP
PLM

18. ECOs
Data Streams: ECOs
Access Windows ERP
PLM

19. ECOs
BOM
Data Streams: BOMs & Comps
Access Windows ERP
PLM

20. ECOs
PDF(ECO)
PDF(Drwg)
BOM
Data Streams: PDFs
Access Windows ERP
PLM

21. ECOs
ECO-Comp
PDF(ECO)
PDF(Drwg)
BOM
Data Streams: ECO-Comp
Access Windows ERP
PLM

22. ECOs
ECO-Comp
ECO-Drwg
PDF(ECO)
PDF(Drwg)
BOM
Data Streams: ECO-Drwg
Access Windows ERP
PLM

23. ECOs
ECO-Comp
ECO-Drwg
Comp-Drwg
PDF(ECO)
PDF(Drwg)
BOM
Data Streams: Comp-Drwg
Access Windows ERP
PLM

24. ECOs
ECO-Comp
ECO-Drwg
Comp-Drwg
PDF(ECO)
PDF(Drwg)
BOM
OrCAD
Data Streams: Electrical CAD
Access Windows ERP
PLM

25. ECOs
ECO-Comp
ECO-Drwg
Comp-Drwg
Microstation
PDF(ECO)
PDF(Drwg)
BOM
AutoCAD
OrCAD
Data Streams: Mechanical 2D CAD
Access Windows ERP
PLM

26. 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

27. 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

28. 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

29. 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

30. 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

31. 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%

32. Estimating ECO Data Stream
• Latest revision only
• Metadata without files
• 90% accuracy means only 3 iterations

33. 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

34. Estimating CATIA Data Stream
• Full revision history
• Metadata and files, files links, links to “space”
• 90% accuracy means only 3 iterations

35. 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

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. 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%

38. Migration Accuracy
90% = 110 days (3 iterations)

39. Migration Accuracy
90% = 110 days (3 iterations)
95% = 121 days (4 iterations)
98% = 133 days (5 iterations)
99% = 146 days (6 iterations)

40. 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?

41. 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)

42. Data Migration Key Factors
• Congruity

43. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)

44. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)
• Transformation needed

45. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)
• Transformation needed
• Files or just metadata

46. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)
• Transformation needed
• Files or just metadata
• Inter-relationships (CAD links)

47. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)
• Transformation needed
• Files or just metadata
• Inter-relationships (CAD links)
• Space (logical location)

48. Data Migration Key Factors
• Congruity
• Accuracy required (iterations)
• Transformation needed
• Files or just metadata
• Inter-relationships (CAD links)
• Space (logical location)
• History (versions/revisions)

49. Moving is Painful

50. Contact Us
Jonathan.Scott@Razorleaf.com
www.Razorleaf.com