Component Connection Database for 3D CAD Assembly Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3D CAD data lacks information about the connection parts between components in a structural body, making it difficult to manage the connection relationships between components in a virtual space.

Innovation Solution

A component management database that stores component IDs, shape data, and connection category IDs, allowing for the association of connection types and model shapes, enabling the determination of connection relationships between components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Shape

If 3D CAD data is used to represent components in virtual space, then visual shape recognition and spatial positioning are improved, but connection part information between components is lost

Engineering Contradiction:
Improvevisual shape recognitionVSAvoidconnection part information
Core Design Contradiction:
ShapeVSLoss of information

Solution Approach 1:

The invention segments the data structure by separating component geometric information (3D CAD data) from connection part information. Each component is assigned a component ID, and connection parts are independently defined with their own IDs and attributes. This segmentation allows 3D CAD data to maintain visual shape recognition while connection information is stored separately in the management database, preventing information loss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention introduces a component management database as an intermediary between 3D CAD data and connection information. The database stores component IDs, part IDs, and connection part information that links components together. This intermediary structure enables the system to maintain both the visual representation from 3D CAD data and the connection relationships that would otherwise be lost.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If only 3D CAD data is stored for components, then data storage simplicity is improved, but determination of connection relationships between components becomes difficult

Engineering Contradiction:
Improvedata storage simplicityVSAvoidconnection relationship determination
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The invention applies preliminary action by pre-defining connection parts for each component before assembly. Connection part information is stored in advance in the component management database, including part IDs and associations with other components. This preliminary structuring of data makes it straightforward to determine connection relationships later, without requiring complex analysis of 3D CAD data alone.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If connection information is not included in 3D CAD data, then data compatibility with existing CAD systems is improved, but component management accuracy deteriorates

Engineering Contradiction:
ImproveCAD system compatibilityVSAvoidcomponent management accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The invention creates a parallel data structure that copies essential component identification information (component IDs, part IDs) from the 3D CAD data into the component management database. This copying approach maintains compatibility with existing CAD systems while establishing a separate, accurate record of connection relationships that improves component management reliability without requiring modifications to CAD software.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3761256B1Component management database, component management system, and component management method
Publication Date: 2023.08.16 MAEDA CORP
  • EP3761256B1 patent drawingFigure 1
  • EP3761256B1 patent drawingFigure 2
  • EP3761256B1 patent drawingFigure 3

AI summary

A component management database for managing a plurality of components constituting a structural body, is configured to: store, for each of the plurality of components, a component ID of the component, a pre-processing shape data of the component, a post-processing shape data of the component, a processed shape data being a difference between the pre-processing shape data and the post-processing shape data, a component ID of a second component to be connected to the component, and a connection category ID representing a connection type of a connection part between the component and the second component, in association with one another; and store a model shape of the connection part by the connection type.