System Construction Assistance Using Hierarchical Component Definitions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing system construction methods require redefining dependencies between components whenever a part of the system is changed, leading to low reusability and increased complexity in system definition.
Innovation Solution
A system construction assistance system that includes input means for system definition and setting assignment, allowing for the designation of components with fields and setting definitions, which associates constituent elements with fields and assigns settings based on the system and component definitions, reducing the need for additional setting additions during component changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If component combinations are defined with detailed dependency relationships, then system definition precision is improved, but system complexity increases and reusability decreases
Solution Approach 1:
The patent segments the system definition into two distinct levels: component-level definitions (individual components with their attributes) and combination-level definitions (assemblies of components with their dependencies). This segmentation allows detailed precision at the combination level while reusing standardized component definitions, thereby managing complexity through hierarchical organization.
Solution Approach 2:
The patent implements preliminary action by pre-defining standard component templates with common attributes and behaviors before creating specific system combinations. These pre-defined components can be reused across multiple system definitions, reducing the need to redefine the same dependencies repeatedly and lowering overall system definition complexity.
2Manufacturing precision
If component definitions include detailed field and setting information, then system definition completeness is improved, but ease of system modification deteriorates
Solution Approach 1:
The patent creates universal component definitions that can serve multiple purposes across different system configurations. Each component is defined with standardized fields and settings that can be reused in various combinations, allowing the same component definition to function in multiple contexts without requiring modification, thus improving ease of system modification while maintaining completeness.
Solution Approach 2:
The patent implements copying by allowing system definitions to reference and reuse existing component definitions through templates. When a component is defined once with complete field and setting information, it can be copied and instantiated multiple times in different system combinations, maintaining definition completeness while eliminating the need to recreate the same definitions repeatedly.
3Reliability
If dependency relationships are explicitly defined for each component combination, then system reliability is improved, but time required for system reconfiguration increases
Solution Approach 1:
The patent applies preliminary action by pre-establishing dependency relationship templates at the component level. Common dependency patterns (such as resource requirements, compatibility constraints, and installation sequences) are defined in advance as part of the component definitions. When configuring new systems, these pre-defined dependency relationships are automatically inherited and applied, maintaining system reliability while dramatically reducing reconfiguration time.
Solution Approach 2:
The patent uses copying to replicate proven dependency relationships across multiple system configurations. Once a reliable dependency structure is established for a component in one system, it can be copied to the same component in other systems, ensuring consistent reliability across deployments without requiring time-consuming redefinition of dependency relationships.
Data Source
AI summary
Provided is a system construction assistance system including: a system definition input unit that inputs a system definition including at least a designation of a component using a component definition that is capable of including a field definition and a setting definition about a setting to a constituent element associated with the field, and an assignment definition related to assignment of a constituent element to a field included in the component; and a setting assignment unit that associates a constituent element with a field in a designated component, based on the system definition and the component definition, and assigns a setting to a constituent element constituting a target system, by reflecting a setting content defined with respect to the field in the constituent element associated with the field.