System Configuration Derivation Using Historical Similarity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing system design methods struggle to replicate the reliability of proven systems by repeatedly applying embodiment rules to abstract system configurations.
Innovation Solution
A system configuration derivation device and method that calculates evaluation values for similarity between past and new embodiment rule applications, selecting specific abstract configurations for repeated rule application based on these values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If embodiment rules are repeatedly applied to abstract system configurations to design new systems, then the system design can be automated and productivity is improved, but the reliability of the designed system may deteriorate because it cannot guarantee closeness to proven systems
Solution Approach 1:
The patent implements feedback by calculating similarity between the new system configuration being designed and historical proven system configurations. The similarity calculation unit continuously evaluates how close the current design is to proven systems and uses this information to guide the embodiment rule application process, ensuring the design remains aligned with reliable, proven architectures while maintaining automation.
Solution Approach 2:
The patent applies preliminary action by pre-storing multiple proven system configurations and their embodiment rules in a database before the design process begins. This allows the system to quickly reference and compare against established, reliable configurations during the automated design process, rather than discovering reliability issues after design completion.
2Productivity
If the system selects abstract configurations for repeated embodiment rule application without considering similarity to design history, then the design process is simple and fast, but the resulting system configuration may be unreliable and far from proven systems
Solution Approach 1:
The patent implements feedback by calculating similarity between the new system configuration being designed and historical proven system configurations. The similarity calculation unit continuously evaluates how close the current design is to proven systems and uses this information to guide the embodiment rule application process, ensuring the design remains aligned with reliable, proven architectures while maintaining automation.
Solution Approach 2:
The patent changes the selection parameter from random or simple sequential selection to similarity-based selection. The embodiment rule application unit prioritizes applying rules to abstract configurations that maintain high similarity to proven systems, dynamically adjusting the selection criteria based on calculated similarity metrics rather than fixed or arbitrary parameters.
3Reliability
If the system calculates detailed similarity metrics for every embodiment rule application candidate, then the reliability of system configuration selection is improved, but the computational complexity and processing time increase
Solution Approach 1:
The patent applies local quality by calculating similarity metrics selectively rather than uniformly for all possible embodiment rule applications. The system focuses similarity calculations on critical configuration elements and decision points, rather than performing exhaustive calculations for every possible rule application, thereby maintaining accuracy where it matters most while reducing overall computational burden.
Solution Approach 2:
The patent implements partial action by calculating similarity for a subset of embodiment rule application candidates rather than all candidates. The embodiment rule application unit selects representative samples or prioritized candidates for detailed similarity analysis, obtaining sufficient reliability information without the excessive computational cost of complete evaluation.
Data Source
AI summary
A system configuration derivation device calculates a first evaluation value indicating an evaluation of a similarity between a specific embodiment rule application and a candidate of the embodiment rule application, wherein the specific embodiment rule application is included in a design history, the design history indicates a history of in a case where an embodiment configuration is obtained by repeatedly applying an embodiment rule to an abstract configuration; selects, based on a second evaluation value, a specific abstract configuration among the abstract configurations obtained by applying the embodiment rule to the new configuration one or more times, wherein the second evaluation value indicates the evaluation of the similarity with the design history, of the entirety of one or more applications of the embodiment rule until the abstract configuration is obtained from the new configuration; and repeats the embodiment rule application to the selected specific abstract configuration.


