CAD Integration via Virtual Persistent Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current CAD software lacks reliable, automatic integration with CAD files from other formats, leading to loss of design history and compatibility issues when translating between different CAD systems, requiring expensive API-based solutions and manual rework upon software updates.
Innovation Solution
The use of a Design Change Vector (DCV) software program that applies virtual persistent identifiers to stabilize entity identifiers across different CAD formats, allowing for automatic integration and update of dependent engineering applications by analyzing geometry and topology changes between CAD models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional format-specific APIs are used for CAD integration, then integration between specific sending and receiving formats is achieved, but the solution becomes expensive and requires advance installation of integration software
Solution Approach 1:
The patent introduces a translator that acts as an intermediary between different CAD formats. This translator uses a common intermediate format (such as STEP or IGES) to bridge the sending and receiving formats, eliminating the need for multiple format-specific API integrations. The translator converts the imported CAD model to the intermediate format, which can then be processed by the receiving application, thereby simplifying the integration architecture while maintaining reliability across different format combinations.
Solution Approach 2:
The patent implements a universal integration approach where a single translator component can handle multiple CAD format combinations through the use of a common intermediate format. Instead of requiring separate integration solutions for each format pair (e.g., SolidWorks to AutoCAD, CATIA to Inventor), the system uses one translator that can convert from any sending format to any receiving format via the intermediate format, making the integration solution universally applicable and reducing overall system complexity.
2Adaptability or versatility
If translators re-assign entity identifiers during model translation, then compatibility between different CAD formats is achieved, but design history is lost and integration with dependent applications fails
Solution Approach 1:
The patent changes the identifier parameter from format-specific unique identifiers to persistent identifiers that remain consistent across format translations. Instead of re-assigning new identifiers during translation (which breaks design history), the system modifies the translation process to preserve and map original identifiers through the intermediate format. This allows dependent applications to continue referencing the same entities across different CAD formats without losing design history or requiring re-integration.
Solution Approach 2:
The patent implements a feedback mechanism where the translator analyzes the structure and entity relationships of the imported CAD model, then uses this information to preserve identifier consistency during translation. By examining the feature tree and entity hierarchies in the intermediate format, the translator can feedback to the translation process which identifiers should be maintained, ensuring that design history and entity relationships are preserved across format conversions rather than being lost.
3Reliability
If API-based integration is implemented for each format combination, then specific format integration works, but the solution becomes expensive and requires manual updates when CAD software is updated
Solution Approach 1:
The patent introduces a translator as an intermediary layer that isolates the integration logic from format-specific updates. When CAD software is updated, only the translator component needs to be updated to handle the new format version, rather than requiring updates to all dependent applications and integration configurations. This intermediary approach maintains integration reliability while significantly improving maintenance efficiency, as the translator absorbs the burden of format changes.
Solution Approach 2:
The patent creates a universal translator component that can handle multiple CAD format combinations through a common intermediate format. This universal approach means that when a new CAD format or version is introduced, the system only needs to add support in the translator rather than creating new integration solutions for each format pair. This reduces the number of integration points that need maintenance and improves overall productivity by eliminating redundant update work across multiple format-specific integrations.
4Adaptability or versatility
If feature tree analysis is performed during translation, then CAD model conversion between formats is achieved, but the process is time-consuming and complex
Solution Approach 1:
The patent extracts only the essential information needed for translation from the full feature tree of the imported CAD model. Instead of performing comprehensive analysis of all feature tree elements (which is time-consuming), the translator identifies and extracts only the critical geometric and topological data required to recreate the model in the target format. This selective extraction maintains model translation capability while significantly reducing translation time by avoiding unnecessary analysis of non-essential feature tree elements.
Data Source
AI summary
Disclosed is a method of integrating changes to a computer aided manufacturing software application file for a manufactured component comprising the steps of: obtaining a first computer aided design file for the manufactured component; displaying a first solid model of the manufactured component; obtaining a second computer aided design file for a revised version; displaying a second solid model of the revised version of the manufactured component; and matching at least one face on the second solid model to at least one face on the first solid model.