This is a information-packed presentation on data migration made by BWIR, global solutions and services partner to SolidWorks Enterprise PDM. This was showcased at SolidWorks World 2011 and the presentation talks about data migration from other PDM/PLM systems to SolidWorks EPDM.
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
PLM Data Migration
1. Data Migration from other PDM Systems to
SolidWorks Enterprise PDM
Barry-Wehmiller International Resources (BWIR)
Global Solutions & Services Partner
2. Agenda
Successful data migration means
Data migration Processes from source to target system
Understand & Analyze the Source System
Map the configurations in the Target System
Develop the data extractor & loaders to meet the Target System
Perform the Test Migration process
Perform the Validation
Barry-Wehmiller & Corporate Vision
3. Successful data migration means….
Maximum archive data and information (+)
Maximum data consistence (+)
Minimum references Issue (-)
Minimum time to adapt (-)
4. Source System and Target System
Source PDM / PLM System Target System
SolidWorks
Enterprise PDM
Logo courtesy and Copyrights of PTC Product and DBWorks
5. Migration strategies available…
Point to Point migration process
File System Archive Server
PDMWorks Workgroup
-Select the Data that need to be migrated
- Hit the button “Go”
DB Server
6. Migration strategies available…
Hop migration process
1a 2a
File System
Archive Server
Data Extraction Data Cleansing Data Load
1b 2b
DB Server
DB Server
* Complexity Matrix (SQL)
Copy Paste Migration
Copy Paste Migration With Folder structure 1a + 1b * 2a + 2b 1+2
change (1a + 2a)
Non CAD data 20% 30% 40% 25% 65%
CAD Data 25% 45% 65% 55% 100%
* Varies on case to case basis Variance of ± 5%
7. Hardware considerations
• Archive Server: 2 GB of RAM, Intel Xeon 2 GHz. Windows Server 2003 SP 2
• Database Server: 4 GB of RAM, Intel Xeon 2 GHz, Windows Server 2003 SP 2,
Microsoft SQL Server 2005 SP 2.
• Workstation: 4GB of RAM, Intel Core2 Duo 2GHz, Windows XP Professional SP 2
• Free Disk Space Requirements: The general rule of thumb is to have free disk
space of at least twice the size of the vault on the computer running the import.
Source System Target System
10. Understand & Analyze the Source System
Understanding the basic migration requirements
• What are the various file types that need to be migrated?
• Number/ Percentage of CAD files in the source system?
• Number / Percentage of Non CAD files in the source system?
• Does the CAD and Non CAD files have any relationship maintained in the source system?
• Does the family tables/ configurations maintained in the in source system?
• Is metadata maintained for the data in the source system?
Check point 1: Check for data consistency and integrity
Strategize the migration path
• Is data cleanup required in the source system before the migration required?
• Requirement of complete or only the latest data need to be migrated?
• How to migrate work in progress items to the target system?
• How to migrate only the latest data to the target system?
• How to migrate the legacy data to the target system?
• How to migrate the metadata to the target system?
Check point 2: Plan the data migration strategy
13. Components mapping from source to target system
• legacy data
• latest data
• work in progress data
• custom properties
• change objects (change request & change orders)
• product/project/folder structures
• workflow/ process
• approval process
• revision schema
• naming/numbering schema
• users and groups
• Privileges and Roles
• Notification/ communication process
14. Components of Source System & Target System
• Latest data
• Archive data
• File types
• Templates
• Work in progress data
• Custom properties
• Change objects (CR, CO, ECN)
• Product/project/folder structures
• Workflow/ process
• Approval process
• Revision schema
• Naming/numbering schema
• Users and groups
• Privileges and Roles
• Notification/ communication process
15. Components to be configured prior to the migration
Templates
Parts, Assemblies, & Drawings Components can be easily mapped
Folder structure from source system to the target
Other Documents
system.
Classification of data
• Few components can be configured
Project Structure
Folder Structures based on the rules that are followed in
Workflow source system.
Lifecycle States • Few components cannot be
Workflow Process configured but they can be developed
Workflow stages with the help of “EPDM Dispatch” or as
Approval process an “EPDM custom addin” with the help
Revision schema of API.
Major Revisions
Minor Revisions
Should be configured in such a way
Document Naming Convention
Numbering Schema that it can be easily adapted in
Users and groups Enterprise PDM.
Privileges and Roles
Notification & communication process
17. All about Data extractor & Loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
“Downloaded meta-data into SQL Server
migration tables”
18. All about Data extractor & Loaders
Metadata Document Load to Check In Data
Extraction Extraction EPDM in EPDM
19. All about Data extractor & Loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
Data extractor program
Local
folder
20. Data Cleanup in before data loading into EPDM
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
Following cleanup tasks can be performed on downloaded files before
adding files to SolidWorks Enterprise PDM.
a) Checks for an missing dependencies (references).
b) Checks for any circular reference.
c) Check for file duplicates in the vault.
d) Unlocks Windchill or INTRALINK related parameters and renames
parameter names to one as required by customer.
Optional
a) File rename.
b) Files relocation from one location to another.
21. All about Data extractor & Loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
22. All about Data extractor & Loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
23. All about Data extractor & loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
24. All about Data extractor & loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
25. All about Data extractor & loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
26. All about Data extractor & loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
27. All about Data extractor & loaders
Metadata Data Move Data Check In Data
Extraction Extraction To EPDM in EPDM
30. Perform the test migration process
Data Migration
File types
Work in progress data
Latest data
Archive data “Rehearse the migration process
Metadata
Custom Properties for files at least 2 times before performing
Custom Properties for change objects
Change objects the production migration process”
Change Request
Engineering Change Notice
31. Metrics during the test migration process
Following metrics need to be captured during the migration cycle prior to
Production migration process .
a) Capture the actual migration time for each and every test cycle.
b) Capture the time for add files operation to the vault.
c) Capture the time to update the custom properties in the vault.
d) Capture the time to update the parent child relationship.
e) Capture the time to check in the files into the vault.
f) Capture the time to assign the workflow states in the vault.
32. Delta migration process for huge data set…
Following strategies need to be considered during the migration process in
order to achieve minimum PDM system down time.
a) Migration based on product lines
b) Migration based on file types
c) Migration based on particular project
d) Migration based on last modified
e) Migration based on last created
f) Migration based on data that is related to particular group
g) Migration based on data related to particular site
34. Validation Parameters
Following validation parameters can be performed after migration process is
completed to SolidWorks Enterprise PDM.
a) Checks the references for drawings and assemblies by opening at least
10 to 15 assemblies and drawings.
b) Checks for any circular reference errors.
c) Check the parameters if they can be edited or not.
d) Check the revision specific metadata.
e) Check the revision specific parent child relationship.
f) Check the family table/ configuration specific metadata.
g) Check the family table/ configuration specific parent child relationship.
36. BWIR Vision
BWIR is a global leader providing business and
technology solutions to the manufacturing domain
through the power of inspired people
37. What our vision means
• Our focus is manufacturing - discrete manufacturing in
particular where we have a strategic advantage
• Services will include an integrated suite of technology
solutions to meet business objectives
• Within manufacturing, focus is on the Small & Medium
businesses - $ 50 million to $ 2 billion in revenue
38. Contact Us
Barry-Wehmiller International Resources
(BWIR)
8020 Forsyth Blvd. 23-1/B3 Velachery Tambaram Road
St. Louis, MO 63105 Pallikaranai, Chennai - 600 100 INDIA
Ph: +1 (314) 862-8000 Ph: + 91 44 4390 9100
Email: info@bwir.com ● Website: www.bwir.com