PLM Storage for Legacy CAD Configurations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern product lifecycle management (PLM) platforms are unable to handle the configuration features of legacy computer-based models, limiting the ability to seamlessly integrate and manage these models within modern software systems.
Innovation Solution
The solution involves defining rules for CAD file configurations to map them to either a PLM physical product or a representation of a physical product, allowing users to assign different sub-types for parts and assemblies based on file-level criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy computer-based models with configuration features are imported into modern PLM platforms, then the ability to manage and simulate complex 3D models is improved, but the PLM platform cannot properly handle the configuration features, leading to loss of design intent and improper storage
Solution Approach 1:
The patent segments the configuration data into distinct components (configuration name, configuration type, elements, characteristics) and processes each separately through defined rules. This segmentation allows the system to handle different configuration aspects independently, preserving the complete configuration information rather than losing it during import.
Solution Approach 2:
The patent introduces an intermediary rule-based processing layer between the legacy CAD model import and the PLM platform storage. This intermediary layer translates and transforms configuration data according to defined rules, acting as a mediator that preserves design intent while adapting the data to the PLM platform's structure.
2Manufacturing precision
If all configurations are stored as unique physical products in the PLM platform, then complete model fidelity is maintained, but database size increases and performance decreases
Solution Approach 1:
The patent changes the parameter of how configurations are stored by introducing configuration types (unique physical product, representation, or alternative) based on analyzed characteristics. This parameter change allows the system to optimize storage decisions dynamically, balancing model fidelity with database performance based on the specific needs of each configuration.
Solution Approach 2:
The patent applies different storage qualities to different configurations based on their local characteristics. Rather than applying a uniform storage approach to all configurations, the system analyzes each configuration's specific features and applies the appropriate storage method (unique product, representation, or alternative), optimizing both fidelity and performance locally for each case.
3Productivity
If configuration data is processed without defined rules, then processing speed is faster, but design intent is not accurately reflected and incorrect storage decisions are made
Solution Approach 1:
The patent performs preliminary action by defining and establishing configuration handling rules before the actual import and processing of legacy models. This preliminary rule definition ensures that when configurations are processed, they are automatically routed to the correct storage method based on pre-established criteria, maintaining both speed and accuracy without requiring real-time decision-making during import.
Data Source
Figure 1
Figure 1
Figure 2
AI summary
Embodiments store legacy computer-based models in product lifecycle management (PLM) platforms. Using a legacy computer-based model which is comprised of one or more configurations of one or more elements representing a real-world object, embodiments define a data handling rule which indicates a type for at least one element of a given configuration. The type defines logic for processing the at least one element as a function of characteristics of the at least one element. The given configuration is processed in accordance with the defined data handling rule and the defined logic. Processing the configuration includes storing the at least one element of the given configuration in memory associated with the PLM platform as a unique product or a representation of a unique product.