Intelligent Model Hierarchy for Infrastructure Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional infrastructure modeling software generates separate databases for each modeling perspective and granularity, leading to data redundancies, inconsistencies, storage inefficiencies, and processing inefficiencies, hindering effective software reasoning and analysis without human intervention.
Innovation Solution
An intelligent model hierarchy is implemented, with a repository model serving as the root, organized into subjects and information partitions reflecting different modeling perspectives, and child models hierarchically structured to manage infrastructure elements, maintained in a cloud-based repository accessible to clients for efficient data management and analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate databases are generated for each modeling perspective and granularity, then comprehensive modeling coverage is achieved, but data redundancies and storage inefficiencies occur
Solution Approach 1:
The patent merges multiple separate databases into a unified model hierarchy where a single repository model serves as the root, and child models branch out to represent different modeling perspectives and granularities. This consolidation eliminates data redundancies while maintaining comprehensive modeling coverage across all perspectives.
Solution Approach 2:
The repository model acts as a universal root that serves multiple functions simultaneously - it stores data for all modeling perspectives (physical, functional, etc.) and all granularities (facility-level, equipment-level, component-level). This multi-functional approach replaces the need for separate specialized databases.
2Adaptability or versatility
If separate databases are maintained for each modeling perspective, then detailed perspective-specific modeling is enabled, but data inconsistencies increase
Solution Approach 1:
The patent implements a nested hierarchical structure where child models representing specific modeling perspectives are nested within the repository model. This nesting ensures that all perspective-specific models share a common root data source, automatically maintaining data consistency across different perspectives without requiring separate databases.
3Adaptability or versatility
If multiple separate models of the same entity are created, then comprehensive modeling perspectives are achieved, but processing inefficiencies occur
Solution Approach 1:
The patent segments the unified model hierarchy into distinct child models representing different modeling perspectives (physical, functional, etc.) and granularities. This segmentation allows software to efficiently access and process only the relevant subset of models needed for a specific task, rather than processing all separate databases, thereby improving processing efficiency while maintaining perspective diversity.
4Adaptability or versatility
If separate databases are used for different granularities, then detailed granularity-specific modeling is achieved, but software reasoning capability is hindered
Solution Approach 1:
The patent organizes models in a hierarchical dimension where the repository model at the root represents the highest level of granularity, and child models represent progressively finer granularities. This hierarchical dimensionality allows software to automatically reason about relationships between different granularities by traversing the hierarchy, enabling automation without requiring separate databases for each granularity level.
Data Source
AI summary
In one embodiment, techniques are provided for modeling infrastructure from a plurality of modeling perspectives using an intelligent model hierarchy. A repository model for the infrastructure is generated that serves as a root of the intelligent model hierarchy. The repository model includes a root subject and one or more child subjects. One or more information partitions are generated for each subject, each information partition being associated with a respective modeling perspective. One or more child models are associated with each information partition. The one or more child models each containing one or more infrastructure elements that express the modeling perspective of the information partition with which the child model is associated. The repository model and the one or more child models are maintained together in a repository, and infrastructure elements of a selected model may be displayed on demand in a user interface of a client.