Collaborative CAx Updates via Dual Format Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing CAx systems are not well-suited for collaborative design and editing, leading to data loss or corruption due to incompatible file formats and the need for lengthy conversion processes, which hinder efficient multi-user collaboration in large engineering projects.
Innovation Solution
A method that stores engineering object data in both a client-specific format and a collaborative server format, allowing for real-time updates and synchronization across different CAx applications, using a synchronization module to manage feature identifiers and maintain data consistency across various proprietary representations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is stored in a single client-specific format, then the CAx application can work efficiently with its native format, but other CAx applications cannot access or edit the data without conversion, leading to data loss and corruption
Solution Approach 1:
The patent segments data storage into two distinct formats: a client-specific native format for efficient local editing and a collaborative server format for shared access. The synchronization module divides the data management task by maintaining separate representations and coordinating updates between them, allowing each CAx application to work with its preferred format while ensuring cross-application compatibility through the server format.
Solution Approach 2:
The synchronization module acts as an intermediary between the client-specific format and the collaborative server format. It mediates data exchanges by detecting changes in one format and translating/synchronizing them to the other format, ensuring data consistency across different CAx applications without requiring direct compatibility between them.
2Adaptability or versatility
If data conversion processes are implemented between different CAx formats, then compatibility between applications is improved, but the conversion process is lengthy and results in significant data loss
Solution Approach 1:
The system performs preliminary action by maintaining a collaborative server format copy of the data in advance. When multiple CAx applications need to access the data, the conversion has already been done to create the server format, eliminating the need for repeated real-time conversions. This preliminary preparation reduces conversion time and minimizes data loss by avoiding multiple conversion cycles.
3Productivity
If multiple users edit the same data file simultaneously without coordination, then collaborative efficiency is improved, but editing conflicts result in data loss or corruption
Solution Approach 1:
The synchronization module implements feedback mechanisms by continuously monitoring changes in both the client-specific format and the collaborative server format. When edits are detected, the system provides feedback about the state of the data and coordinates updates to ensure that simultaneous edits by multiple users do not cause conflicts or data loss, maintaining data integrity while enabling collaborative efficiency.
Data Source
AI summary
A method, executed by at least one processor, may include storing, within a set of memory locations within a storage medium, data for a feature of an engineering object in a first client format and a collaborative server format that is different than the first client format, the first client format corresponding to a first CAx application operable by a first user, the collaborative server format corresponding to a collaborative server. The method may also include updating the data for the feature in both the first client format and the collaborative server format in response to receiving an update to the feature from, or detecting an update to the feature by, the first CAx application or the collaborative server. A corresponding system and computer readable medium are also disclosed herein.