CAD Converter Using Synchronization Record for Incremental Format Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing CAD description conversion technologies face inefficiencies in incremental conversion between different storage formats due to lack of effective incremental converters that can detect and process only changed data items, exacerbated by issues like unstable IDs and limited provenance information, hindering the use of conventional synchronization frameworks.

Innovation Solution

A CAD description converter that employs a synchronization information record to track changes and maintain mappings between source and output repositories, using cryptographic hashes and timestamps to identify new, changed, or deleted items, enabling incremental conversion between file-based and relational database-based storage formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional synchronization frameworks are used for incremental conversion, then conversion efficiency can be improved, but the framework cannot function due to unstable IDs and limited provenance information in the source repository

Engineering Contradiction:
Improveconversion efficiencyVSAvoidsynchronization accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces a conversion information record as an intermediary data structure that stores mapping relationships between source repository items and output repository items. This intermediary enables incremental conversion by providing a reliable reference point that compensates for the unstable IDs and limited provenance information in the source repository, allowing the system to track which items have been converted and how they map between repositories.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If full conversion is performed to ensure data consistency, then conversion accuracy is maintained, but conversion time and computational resources increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidconversion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by maintaining a conversion information record that documents the mapping relationships and conversion status before actual conversion operations. This preliminary tracking allows the system to identify which items need conversion and which have already been converted, enabling incremental updates rather than full conversions while maintaining data consistency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial action by converting only the subset of items that have changed or need updating, rather than performing full conversion of all items. The conversion information record enables the system to identify and process only the necessary portion of data, reducing conversion time and computational resources while maintaining data consistency through selective updates.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If incremental conversion is implemented to process only changed items, then conversion speed improves, but the system cannot reliably identify changed items due to unstable IDs

Engineering Contradiction:
Improveconversion speedVSAvoidchange detection accuracy
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The conversion information record serves as an intermediary that stores stable mapping relationships between source repository items and output repository items. Even when source repository IDs are unstable, the conversion information record maintains the correspondence information, enabling the system to reliably detect changes by comparing current state against the stored mapping information from previous conversions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms by using the conversion information record to track and report on conversion status and mapping relationships. This feedback loop allows the system to identify which items have been converted, which have changed, and what the current mapping state is, enabling reliable change detection despite unstable source repository IDs.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3433771B1Method and computer-readable medium for incremental data conversion using a synchronization information record
Publication Date: 2022.07.27 BENTLEY SYSTEMS INC
  • EP3433771B1 patent drawingFigure 1
  • EP3433771B1 patent drawingFigure 2
  • EP3433771B1 patent drawingFigure 3

AI summary

In one embodiment, techniques are provided for converting data items of a source repository that maintains a CAD description according to a first storage format to data items of an output repository that maintains the CAD description according to a second storage format. A converter gathers data items of the source repository and compares current condition information for them with condition information as of a last successful conversion maintained by a synchronization information record separate from the source repository. The converter determines one or more new or changed data items in the source repository since the last successful conversion, converts new or changed data items to the second storage format of the output repository, and stores them in the output repository, while skipping any unchanged data items. The converter further updates the synchronization information record to include the current condition information for data items in the source repository.