PLM Integration of 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 multiple variations of parts and assemblies is improved, but the system complexity and inability to handle configuration features worsen
Solution Approach 1:
The patent segments the configuration data into individual configurations, each treated as a separate entity with its own product model. This allows the PLM system to handle legacy CAD configurations by breaking down the complex configuration structure into manageable, discrete configuration units that can be processed independently.
Solution Approach 2:
The patent introduces an intermediary conversion process that translates legacy CAD configuration data into a format compatible with modern PLM systems. This intermediary step includes creating product models, defining bill of materials, and establishing configuration relationships, thereby bridging the compatibility gap between legacy and modern systems.
2Loss of information
If all CAD configurations are converted to unique physical products in PLM, then complete representation of design intent is improved, but database size and performance worsen
Solution Approach 1:
The patent creates product models as digital representations or copies of the actual physical products defined in legacy CAD configurations. Instead of storing all configuration data as unique physical products, the system uses product models to represent configurations, reducing database redundancy while preserving design intent information.
Solution Approach 2:
The patent implements a universal product model structure that can represent multiple configurations through a single product definition. This allows the same product model to serve multiple configuration variants, reducing the overall quantity of data stored while maintaining the ability to represent all design variations.
3Productivity
If configuration data is imported without conversion rules, then import speed is improved, but data accuracy and design intent preservation worsen
Solution Approach 1:
The patent performs preliminary actions by establishing conversion rules and product models before the actual configuration data import. This includes defining the structure of product models, setting up bill of materials templates, and configuring conversion parameters in advance, which enables faster and more accurate import processing.
Solution Approach 2:
The patent transforms configuration data by changing its parameters from the legacy CAD format to the PLM system format. This includes converting configuration properties to product model attributes, transforming bill of materials structures, and adapting dimension and tolerance data, thereby ensuring data accuracy while maintaining import efficiency.
Data Source
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.