Voxelized PLM Knowledge Graphs for Cross-Department 3D Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 3D digital mock-ups in PLM systems are not standardized across departments, leading to data siloing and manual intervention for data adaptation, and identifying 3D objects is difficult due to varying technical parameters, hindering seamless integration and retrieval of information across the product lifecycle.
Innovation Solution
A method and system that generates a new technical solution by consolidating PLM data into voxel form, using a knowledge graph to establish logical relationships between elementary parts, and generating topology attributes, allowing for streamlined 3D object management and democratized access without requiring advanced CAD software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If 3D digital mock-ups are generated by CAD software in different departments, then each department can have customized 3D data optimized for their specific needs, but data becomes siloed and requires manual intervention for adaptation, increasing complexity and reducing efficiency
Solution Approach 1:
The patent creates a universal voxel-based data format that can be used across all departments and CAD software platforms. By converting diverse 3D digital mock-up data into a standardized voxel representation, the system enables one data format to serve multiple departments with different needs, eliminating the need for manual data adaptation while preserving the ability to retrieve original technical parameters when needed.
Solution Approach 2:
The voxel data structure acts as an intermediary format between different CAD software and departments. Instead of requiring direct compatibility between various CAD systems, all 3D data is converted to voxels as a common intermediate representation, which can then be processed by any department without manual intervention.
2Ease of operation
If standardized 3D data formats are implemented across all departments, then data integration and retrieval become easier, but departments lose the ability to customize data for their specific processing needs
Solution Approach 1:
The patent segments 3D data into discrete voxel units, each representing a small volumetric element. This segmentation allows the system to provide a simplified standardized interface for general data retrieval while enabling detailed customized processing when needed, as voxels can be selectively assembled and manipulated to meet specific departmental requirements.
Solution Approach 2:
The system dynamically adapts to different needs by allowing flexible assembly and manipulation of voxel data. For routine operations, a simplified standardized interface is used, but when customized processing is required, the voxel structure enables dynamic reconfiguration and detailed manipulation without requiring full customization of the underlying data format.
3Measurement precision
If detailed technical parameters are stored for each 3D object, then identification and functionality are more accurate, but data volume increases and integration across different systems becomes more difficult
Solution Approach 1:
The patent extracts essential geometric information into the voxel structure itself, while separating detailed technical parameters into associated metadata. This extraction allows the core 3D representation to remain compact and efficiently integrable, while detailed parameters are stored separately and only accessed when needed for specific operations.
Solution Approach 2:
The patent transitions from traditional 3D mesh representations to a 4D voxel structure (x, y, z, and value/property dimensions). This dimensional change allows detailed technical parameters to be embedded within the spatial structure itself, enabling efficient storage and retrieval without increasing overall data volume proportionally to the detail level.
Data Source
AI summary
A method and system for generating a new technical solution by acquiring PLM data of an industrial product having at least two 3D objects, extracting attributes and rules for each 3D object from the PLM data, generating a knowledge graph of tree relationships between the 3D objects, generating topology attributes for each 3D object, consolidating, for each 3D object, its attributes and rules, its tree relationships and its topology attributes into at least one relational database, in voxel form, receiving a request from a user relating to a technical solution, the request having at least one 3D volume, evaluating whether the technical solution is present in the PLM, and when it is not present: generating a new technical solution in the 3D volume, implementing at least one new 3D object, generating a new voxel associated with the new 3D object, and re-introducing the new voxel into the relational database.