PLM to SCM Hierarchical Data Export via Mediator Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for integrating Source Code Management (SCM) systems and Product Lifecycle Management (PLM) systems lack efficient data linking, limited functionality, and do not allow for controlled data flow or automatic updates between the two systems, hindering effective data management and synchronization.
Innovation Solution
A computer system and method that extracts data from a PLM system, customizes it to match SCM system requirements, maps identities, and provides breadcrumb links for version control, enabling bidirectional synchronization and data transfer between SCM and PLM systems, including the creation of modules and hierarchical relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional PLM and SCM systems are used separately without linking, then system simplicity is maintained, but data synchronization and integration efficiency deteriorate
Solution Approach 1:
The patent implements an intermediary integration layer that connects PLM and SCM systems through standardized data exchange protocols. This mediator handles data transformation, mapping, and synchronization without requiring deep integration into either system's core architecture, thus improving data synchronization efficiency while controlling integration complexity.
Solution Approach 2:
The integration architecture is segmented into independent functional modules including data extraction components, transformation layers, and synchronization engines. Each module handles specific aspects of data exchange independently, allowing the system to scale and maintain simplicity while achieving comprehensive data synchronization across hierarchical structures.
2Adaptability or versatility
If limited functionality linking is implemented between PLM and SCM, then implementation ease is maintained, but data flow control and automatic update capabilities deteriorate
Solution Approach 1:
The system implements dynamic data flow control where synchronization rules, update frequencies, and transformation logic can be configured and adjusted without reimplementation. The integration framework supports adaptive mapping relationships that automatically adjust to changing data structures and requirements, providing versatility while maintaining ease of implementation through configuration rather than code changes.
3Productivity
If manual data transfer between PLM and SCM is used, then system simplicity is maintained, but time consumption and operational efficiency deteriorate
Solution Approach 1:
The patent implements continuous automated synchronization that operates in the background between PLM and SCM systems. Data extraction, transformation, and loading processes run continuously or on scheduled intervals without requiring manual intervention, eliminating data transfer delays and maintaining constant synchronization across hierarchical product structures and source code repositories.
Solution Approach 2:
The integration system performs self-service data synchronization by automatically detecting changes in either PLM or SCM systems and triggering appropriate update workflows. The system autonomously handles data extraction, validation, transformation according to mapping rules, and insertion into the target system without human intervention, significantly improving operational efficiency while reducing time consumption.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Traditionally, PLM systems and SCM systems have not been linked. In an embodiment, a computer method includes, responsive to a user request to transfer a module from a product lifecycle management (PLM) system to a source code management (SCM) system, extracting, from a processor at the PLM system, the data representing modules, versions of the modules, and hierarchical relationships of the modules from a data source of the PLM system. The method further includes creating an SCM system module having the extracted data representing the modules, versions of the modules, and the hierarchical relationships of the modules. Therefore, the PLM system can export a module to the SCM system in a process controlled at the PLM system.