Building Digital Twin Schema Extension Without Redeployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing digital twin schema is static, which hinders the expression of new information needed by building systems, leading to inefficiencies such as wasted time in redeveloping and redeploying systems to accommodate changing requirements.

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 extension of the schema to include new information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the digital twin schema is kept static, then system stability is maintained, but adaptability to new information requirements deteriorates

Engineering Contradiction:
Improveschema adaptabilityVSAvoidtime for redeveloping and redeploying
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a dynamic schema evolution mechanism that allows the digital twin schema to be updated at runtime without requiring system redeployment. The schema can be extended with new properties, tags, and states through automated versioning and migration processes, transforming the previously static schema into a flexible, evolving structure that adapts to changing building system requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs automated schema versioning and migration strategies that prepare for future changes in advance. By establishing a framework that pre-defines how schemas will evolve and how data will be migrated between versions, the system eliminates the need for time-consuming manual redevelopment when new information requirements emerge.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If the schema is updated to include new properties and states, then information expression capability is improved, but system complexity increases

Engineering Contradiction:
Improveinformation expression capabilityVSAvoidschema complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the schema into modular entity classes with hierarchical relationships. Each entity class (e.g., building, floor, room, equipment) can independently extend its properties without affecting the entire schema. This modular segmentation allows new information to be added in isolated, manageable units rather than requiring comprehensive schema restructuring.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements universal base entity classes that can serve multiple purposes. These base classes define common properties and behaviors that can be inherited and extended by specific entity types, reducing the need to create separate complex structures for each entity. The unified entity class framework provides a versatile foundation that simplifies schema extension.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If schema updates require redeployment, then system reliability is maintained, but productivity deteriorates

Engineering Contradiction:
Improvesystem deployment efficiencyVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements automated feedback mechanisms through schema versioning and validation systems. Before applying schema updates, the system validates the changes against existing data and constraints, providing feedback on potential conflicts. This automated validation ensures that schema evolution maintains system reliability while enabling continuous deployment without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary schema migration layer that acts as a buffer between the existing system and new schema versions. This migration layer handles data transformation and compatibility issues, allowing schema updates to be applied without requiring full system redeployment. The intermediary layer ensures reliable transitions while maintaining productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20230400825A1Building data platform with schema extensibility for states of a digital twin
Publication Date: 2023.12.14 TYCO FIRE & SECURITY GMBH
  • US20230400825A1 patent drawing
  • US20230400825A1 patent drawing
  • US20230400825A1 patent drawing

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.