Object Data Model for KBE System Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software integration platforms and KBE systems for product development are limited by their inability to implement new analysis methods efficiently, lack flexibility in using data models of machine components, and require complex and expensive software development for integrating complex rules, leading to heterogeneous architectures and restricted design configuration freedom.
Innovation Solution
An apparatus using an object data model represented by an equation system that encapsulates engineering knowledge, allowing flexible use of component and construction rules through component objects and functional objects, enabling unitary embedding of knowledge and clear modeling processes, with a resolution unit to analyze and modify design stages automatically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software integration platforms are used to integrate different software tools, then data exchange between tools is automated and the conception process is speeded up, but the platforms import the limitations and drawbacks of the integrated tools and do not permit implementation of newly created analysis methods
Solution Approach 1:
The system segments the design support functionality into independent modules (equation system resolver, object database, analysis methods) that can be selectively integrated. This allows new analysis methods to be added without being constrained by the limitations of existing integrated tools, while still benefiting from automated data exchange.
Solution Approach 2:
The equation system serves as a universal data model that can represent various machine objects and their parameters. This universal representation enables different analysis methods to work with the same data structure, allowing new methods to be implemented without being restricted by tool-specific limitations.
2Adaptability or versatility
If KBE platforms with integrated CAD functionality are used, then engineering knowledge can be embedded in the system, but the embedding of knowledge is not effected in a unitary fashion and heterogeneous architectures are created
Solution Approach 1:
The system merges the equation system, object database, and analysis methods into a unified architecture. All engineering knowledge is embedded through the common equation system data model, creating a homogeneous structure where different knowledge types (design rules, analysis methods, component models) are integrated through a single representation framework.
Solution Approach 2:
The equation system acts as an intermediary data model that mediates between the object database and analysis methods. This intermediary layer provides a unitary fashion for knowledge embedding, allowing diverse engineering knowledge to be represented and processed through a common interface without creating heterogeneous architectures.
3Reliability
If complex rules are integrated into KBE systems, then design constraints can be enforced, but complicated and expensive software development procedures are required
Solution Approach 1:
The system represents design constraints as equations with parameters that can be defined and modified without complex software development. By changing the mathematical representation of constraints from complex procedural code to parameter-based equations, the system enforces design constraints reliably while simplifying the software development process.
Solution Approach 2:
The system replaces complex software development procedures with a mathematical equation-based approach. Instead of implementing constraint enforcement through complicated programming, the system uses equation solvers that automatically handle constraint satisfaction, reducing software development complexity while maintaining reliability.
4Adaptability or versatility
If manual work is used for integrating methods and rules via API, then complex methods can be incorporated, but the process remains complicated and expensive
Solution Approach 1:
The system enables self-service integration where the equation system automatically manages the integration of methods and rules. Rather than requiring manual API programming, the system provides automatic data exchange and method invocation based on the equation model, reducing integration complexity while maintaining versatility.
Data Source
AI summary
The invention concerns an apparatus and a computer software product for the conceptioneering, predesign and configuration of a machine object represented by an object data model. Component objects are stored in an object database, wherein a component object contains at least one parameter object. In addition the database contains functional objects. The modeling approach implemented by the separation according to the invention of component objects and functional objects permits a distinction to be drawn between constraints within a component object and constraints which exist between component objects. The former are embraced by the component objects themselves and the latter by the functional objects. That encapsulation has in particular the advantage that the modeling process can be substantially clearer. In addition encapsulation permits re-use of the component objects in various systems.