Digital Twin Schema Extension Without Building System Redeployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing digital twin schema is static and does not allow for dynamic expression of new information, leading to inefficiencies in updating systems and redeploying infrastructure to accommodate changing requirements, resulting in wasted time and resources.
Innovation Solution
A building system that dynamically updates the digital twin schema by adding properties, tags, or states to entity classes without requiring redeployment, allowing for real-time adaptation and integration of new information through processor instructions that modify the schema while the digital twin is operational.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the digital twin schema is made static to ensure system stability, then system reliability is improved, but adaptability to new information requirements deteriorates
Solution Approach 1:
The patent applies the dynamics principle by transforming the static schema into a dynamic one that can adapt to new information requirements. The system now allows schemas to be modified at runtime through version control mechanisms, enabling the digital twin to evolve without compromising system stability. This resolves the contradiction by making the schema flexible while maintaining operational reliability.
Solution Approach 2:
The patent implements preliminary action through version control and validation mechanisms that prepare schema changes before they are applied. By pre-validating new schema versions and maintaining version history, the system ensures that adaptability improvements do not compromise system reliability. This allows safe evolution of the schema structure.
2Adaptability or versatility
If the schema is updated frequently to accommodate new information requirements, then adaptability is improved, but loss of time for redeployment increases
Solution Approach 1:
The patent applies the copying principle by creating version copies of the schema rather than modifying the original directly. Each schema change creates a new version that can be validated and deployed independently, eliminating time-consuming redeployment processes. The system can switch between versions without full system redeployment, significantly reducing time loss.
Solution Approach 2:
The patent implements preliminary validation and testing of schema versions before deployment. By preparing and validating schema changes in advance, the system minimizes actual deployment time when changes are needed, resolving the contradiction between adaptability and time loss.
3Adaptability or versatility
If the schema is updated frequently to express new information, then adaptability is improved, but system complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the schema management into distinct, manageable components: version control, validation rules, and deployment mechanisms. This modular approach reduces complexity by organizing schema updates into discrete, manageable units rather than monolithic changes, making frequent updates more tractable.
Solution Approach 2:
The patent implements a universal version control system that handles multiple schema types and update scenarios through a single framework. This multi-functional approach reduces complexity by providing a unified mechanism for managing diverse schema changes rather than requiring separate management systems for each scenario.
Data Source
AI summary
A building system includes one or more memory devices comprising instructions thereon that, when executed by one or more processors, cause the one or more processors to perform one or more first operations based on a digital twin of a building. The instructions cause the one or more processors to update a schema of the digital twin by adding a property or tag to an entity class of the schema, add, based on the schema, one or more data elements representing the property or tag to the digital twin, the one or more data elements related to an entity of the entity class, and perform one or more second operations based on the one or more data elements representing the property or tag.