Hierarchical Component Configuration for Valid Selection and Cost Estimation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient method to manage and visualize the complex relationships between components in a product, leading to inefficiencies in selecting optimal combinations and estimating costs accurately.
Innovation Solution
A management system that utilizes a configurator to select component combinations based on configuration information defined using a modeling language, incorporating data on components, links, and constraints, and includes an estimate calculation module to predict costs even when lower-level components are undetermined.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a configurator is used to determine product specifications based on customer requests, then the ability to select component combinations is improved, but the complexity of managing and visualizing relationships between components increases
Solution Approach 1:
The patent segments the product configuration system into distinct hierarchical levels (product level, module level, component level). Each level has its own configuration data and relationships, allowing complex component relationships to be broken down into manageable segments that can be independently managed and visualized.
Solution Approach 2:
The patent introduces configuration information as an intermediary data structure that mediates between customer requests and component selections. This configuration information serves as a structured interface that simplifies the interaction between users and the complex component relationships, hiding the underlying complexity while enabling effective selection.
2Measurement precision
If configuration information is stored to define component data, links, and constraints, then the precision of component combination selection is improved, but the quantity of data to be managed increases
Solution Approach 1:
The patent creates a universal configuration information structure that serves multiple functions simultaneously: it stores component data, defines relationships between components, specifies constraints, and enables both selection and estimation functions. This multi-functional data structure reduces the need for separate data stores for each function.
Solution Approach 2:
The patent implements a nested data structure where configuration information contains component data, which in turn contains links to other components, which may contain further nested configuration data. This hierarchical nesting allows complex relationships to be represented compactly, with inner structures reused within outer structures, reducing overall data redundancy.
3Measurement precision
If an estimate calculation module is added to predict costs of undetermined components, then the precision of cost estimation is improved, but the device complexity increases
Solution Approach 1:
The estimate calculation module utilizes the existing configuration information structure to perform cost estimation autonomously. It self-services by reading component data, links, and constraints from the already-stored configuration information, and applies estimation logic without requiring additional external data or complex integration with other systems.
Solution Approach 2:
The patent performs preliminary organization of configuration information during the selection phase, structuring data in a way that enables subsequent estimation. By pre-organizing component relationships and constraints in the configuration information, the system prepares the data structure in advance to facilitate efficient cost calculation without requiring complex processing during the estimation phase.
Data Source
AI summary
A management system is configured to manage a configurator configured to select a candidate of a combination of components included in a product. The management system includes a storage part and a controller; the storage part is configured to store configuration information defining data related to the components, data related to a link between the components, and data related to a constraint of the link; and the controller is configured to select the candidate of the combination based on a request accepted from a user, and a rule related to the combination of the components generated from the configuration information.