PLM Database Rendering for CAD Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Product Lifecycle Management (PLM) databases do not allow users to easily navigate and access necessary information about modeled objects, requiring time-consuming switches between different applications and databases to retrieve information such as lock status, version numbers, and other parameters.
Innovation Solution
A process for rendering an object view in a PLM database that displays modeled objects with associated attributes, allowing users to select and query attributes directly within the database, providing values for rendering, and rendering objects based on these attributes without needing to launch dedicated applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If users switch between different applications and databases to retrieve information about modeled objects, then comprehensive information access is achieved, but time consumption increases significantly
Solution Approach 1:
The patent merges the PLM database with CAD application functionality, allowing users to access and render modeled objects with their attributes directly within the CAD interface. This integration eliminates the need to switch between separate applications and databases, providing comprehensive information access while reducing time consumption through unified access to both geometric and attribute data.
Solution Approach 2:
The system provides multi-functional capability by enabling the PLM database to serve both as a standalone data repository and as an integrated component within the CAD application. The database can be accessed independently or through the CAD interface, allowing users to perform rendering operations and retrieve information without leaving their primary design environment, thus reducing time loss while maintaining complete information access.
2Adaptability or versatility
If multiple dedicated applications are used to access different product data, then specialized functionality is maintained, but system complexity increases
Solution Approach 1:
The patent combines multiple applications into a unified system where the PLM database is integrated with the CAD application interface. Users can access modeled objects, retrieve attributes, and perform rendering operations through a single integrated environment rather than switching between multiple dedicated applications, thereby reducing system complexity while preserving specialized functionality through the database's comprehensive data storage capabilities.
Solution Approach 2:
The PLM database is designed with multi-functional capability, serving as both an independent data management system and an integrated component within the CAD application. This universal design allows the same database infrastructure to support standalone operations and integrated rendering operations, reducing the need for multiple separate applications while maintaining specialized functionality through configurable access methods.
3Measurement precision
If users manually query and retrieve attribute values from the database, then data accuracy is ensured, but user efficiency decreases
Solution Approach 1:
The system performs preliminary actions by automatically querying the PLM database and retrieving attribute values for modeled objects before the user needs to use them. When a user initiates a rendering operation, the system proactively fetches the required attribute data from the database in advance, ensuring data accuracy through direct database retrieval while improving user efficiency by eliminating manual query steps and presenting ready-to-use attribute values.
Data Source
AI summary
The invention proposes a process for rendering an object view using a PLM database. The database comprises modeled objects and relations between said modeled objects. Said modeled objects are associated to a set of values of attributes, whose values are stored in the database or computable based on relations involving said modeled objects. The process comprises displaying to the user a view of a set of modeled objects; receiving a selection by a user of an attribute; querying the database for a modeled object to be rendered; providing a value of the selected attribute, associated to said modeled object; and rendering said modeled object in the view according to the provided value of the attribute. It is also possible for the user to select a value of an attribute and the rendering will be carried out only on the object, whose value(s) matches with the selected value.