DE102022129829A1 - BUILDING DATA PLATFORM WITH SCHEME EXTENSIBILITIES FOR DIGITAL TWIN STATES, PROPERTIES AND TAGS - Google Patents

Abstract

A building system includes one or more storage devices that include instructions thereon that, when executed by one or more processors, cause the one or more processors to perform one or more initial operations based on a digital twin of a building to obtain a state for an entity of the digital twin. The instructions cause the one or more processors to update a schema of the digital twin by adding a state type of the state to an entity class of the schema, based on the schema, adding one or more data items representing the state to the digital twin, wherein the one or more data items are related to an entity of the entity class, and perform one or more second operations based on the one or more data items representing the state.

Description

BACKGROUND

The present application generally relates to a digital twin building system. In particular, the present application relates to the digital twin scheme.

The building system can work against a digital twin, for example the digital twin can inform the building system of information concerning the building that the building system is working against. However, the scheme in which the digital twin is deployed can be static; H. it doesn't change. This can cause problems if the schema does not allow for a specific expression of information that would be useful for building systems to be worked against. Much time can be wasted redesigning schemas and redeploying systems to express information in the digital twin required by other systems.

EXECUTIVE SUMMARY

Dynamic property or dynamic tag

A building system that includes one or more storage devices that include instructions thereon that, when executed by one or more processors, cause the one or more processors to perform one or more initial operations based on a digital twin of a building, wherein the digital twin contains representations of entities of the building and relationships between the entities. 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, based on the schema, one or more data items representing the property or tag to which add a digital twin, the one or more data items being related to an entity of the entity class, the plurality of entities including the entity, and one or more second operations based on the one or more data items representing the property or tag represent to carry out.

In some embodiments, the entities include at least one of a person, point, location, or event, and the schema defines entity classes for entity types of the entities.

In some embodiments, the entities are instances of entity classes defined by the schema.

In some embodiments, the property or tag defines a characteristic of the entity.

In some embodiments, the instructions cause the one or more processors to update the schema of the digital twin while the digital twin is being deployed, without having to re-deploy the digital twin.

In some embodiments, the schema defines entity classes, where the entity classes specify properties, tags, and states for the entity classes.

In some embodiments, the instructions cause the one or more processors to identify entity nodes that specify entities in the entity class and, for each of the entity nodes, to assign the one or more nodes that represent the property or tag based on the schema add to the digital twin, wherein the one or more nodes are related to the entity node.

In some embodiments, the digital twin includes nodes and borders between the nodes, where the plurality of nodes represent the entities of the building and the borders indicate the relationships between the entities. In some embodiments, instructions cause the one or more processors to add, based on the schema, one or more nodes representing the property or tag to the digital twin, the one or more nodes being related to a node, which represents the entity of the entity class by one or more borders.

In some embodiments, the instructions cause the one or more processors to receive an indication to add the property or tag to a first entity, identify the entity class of the first entity based on the schema, identify the digital twin schema by adding the property or update the tag to the entity class of the schema in response to identifying that a class of the first entity is the entity class and the one or more nodes representing the property or tag to the digital twin based on the add schema, wherein the one or more nodes are related to the node representing the entity of the entity class, the entity being a second entity different from the first entity.

In some embodiments, the instructions cause the one or more processors to receive user input from a user device, the user input defining the property or tag to be added to the entity class of the schema, and in response to receiving the user input, the Add the digital twin schema by adding the property or tag to the schema's entity class based on user input.

In some embodiments, the instructions cause the one or more processors to identify an update at a particular node or edges of the digital twin, the update indicating changes affecting the entity to determine that the update indicates a change to one or more characteristics of the entity, and update the schema of the digital twin by adding the property or tag to the entity class of the schema in response to determining that the update reflects the change to the one or more characteristics the entity indicates. Another implementation of the present disclosure is a method that includes performing, by one or more processing circuitry, one or more first operations based on a digital twin of a building, the digital twin including representations of entities of the building and relationships between the entities. The method includes updating, by the one or more processing circuits, a schema of the digital twin by adding a property or tag to an entity class of the schema, adding, by the one or more processing circuits based on the schema, one or more data items, representing the property or tag to the digital twin, the one or more data items being related to an entity of the entity class, the entities including the entity, and performing, by the one or more processing circuits, one or a plurality of second operations based on the one or more data items representing the property or tag.

In some embodiments, the entities include at least one of a person, point, location, or event, and the schema defines entity classes for entity types of the entities.

In some embodiments, the property or tag defines a characteristic of the entity.

In some embodiments, the one or more processing circuits updating the schema of the digital twin while the digital twin is being deployed without having to re-deploy the digital twin.

In some embodiments, the schema defines entity classes, where the entity classes specify properties, tags, and states for the entity classes.

In some embodiments, the digital twin includes a plurality of nodes and a plurality of edges between the plurality of nodes, the plurality of nodes representing the plurality of entities of the building and the plurality of edges indicating relationships between the plurality of entities. In some embodiments, the method further includes adding, by the one or more processing circuits based on the schema, one or more nodes representing the property or tag to the digital twin, the one or more nodes having a node that represents the entity of the entity class by one or more edges.

In some embodiments, the method includes identifying, by the one or more processing circuits, entity nodes that indicate entities in the entity class and adding, by the one or more processing circuits based on the schema, the one or more nodes that represent the property or tag, for each of the entity nodes to the digital twin, wherein the one or more nodes are related to the entity nodes.

In some embodiments, the method includes receiving, by the one or more processing circuits, an indication to add the property or tag to a first entity, identifying, by the one or more processing circuits, the entity class of the first entity based on the schema, updating, by the one or more processing circuits, the digital twin schema by adding the property or tag to the entity class of the schema in response to identifying that a class of the first entity is the entity class, and adding, by the one or more processing circuits based on the schema, the one or more nodes representing the property or tag to the digital twin, the one or more nodes being related to the node representing the entity of the represents an entity class, where the entity is a second entity that is distinct from the first entity.

In some embodiments, the method includes receiving, by the one or more processing circuits, user input from a user device, the user input defining the property or tag to be added to the entity class of the schema, and updating, by the one or the plurality of processing circuits, based on the user input, the digital twin schema by adding the property or tag to the entity class of the schema in response to receiving the user input.

In some embodiments, the method includes identifying, by the one or more processing circuits, an update at one or more particular nodes or one or more particular edges of the digital twin, the update indicating changes affecting the entity, determining by the one or more processing circuits that the update indicates a change to one or more characteristics of the entity, and updating, by the one or more processing circuits, the schema of the digital twin by adding the property or tag to the entity class of the schema , in response to determining that the update indicates the change to the one or more characteristics of the entity.

Another implementation of the present disclosure is a building system that includes one or more storage devices storing instructions thereon and one or more processors configured to execute the instructions causing the one or more processors to execute perform initial operations based on a digital twin of a building, where the digital twin includes representations of entities of the building and the boundaries that indicate relationships between the entities. 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, based on the schema, one or more data items representing the property or tag to which add digital twin, wherein the one or more data items are related to an entity of the entity class, the entities including the entity, and one or more second operations based on the one or more data items representing the property or tag, to perform.

dynamic state

An implementation of the present disclosure is a building system that includes one or more storage devices that include 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 a building to derive a state for a digital twin entity, where the digital twin includes representations of entities of the building and relationships between the entities. The instructions cause the one or more processors to update a schema of the digital twin by adding a state type of the state to an entity class of the schema based on the Schema, adding one or more data items representing the state to the digital twin, the one or more data items being related to an entity of the entity class, and one or more second operations based on the one or more data items that represent the state to carry out.

In some embodiments, the entities include at least one of a person, point, location, or event, and the schema defines entity classes for entity types of the entities.

In some embodiments, the entities are instances of entity classes defined by the schema.

In some embodiments, the instructions cause the one or more processors to update the schema of the digital twin while the digital twin is being deployed, without having to re-deploy the digital twin.

In some embodiments, the schema defines entity classes, where the entity classes specify properties, tags, and states for the entity classes.

In some embodiments, the instructions cause the one or more processors to perform the one or more first operations based on the digital twin of the building and external data collected from an external system, the state of the external data for the Entity of the digital twin is derived.
In some embodiments, instructions cause the one or more processors to receive an indication to add the state to the entity, identify the entity class of the entity based on the schema, the schema of the digital twin by adding the state type to the entity class of the schema update, in response to identifying that a class of the entity is the entity class, and add the one or more nodes representing the state to the digital twin based on the schema, the one or more nodes having a second node representing a second entity of the entity class, the entity being different from the second entity.

In some embodiments, an application begins operating to perform the one or more initial operations based on the digital twin of the building to infer the state for the entity after the digital twin is deployed and before the digital twin schema is updated.

In some embodiments, the instructions are configured to receive output from the application resulting from the one or more first operations, the output indicating the state to search the digital twin schema to determine whether the schema includes the state type indicated by the output of the one or more first operations, and to update the schema of the digital twin by adding the state type of the state to the entity class of the schema, in response to identifying that the Schema does not include the state type.

In some embodiments, the state defines a condition associated with the entity.

In some embodiments, the condition is at least one of an error condition of a piece of equipment of the building or an occupancy level of a room of the building.

In some embodiments, the digital twin includes nodes and borders between the nodes, where the nodes represent the entities of the building and the borders indicate the relationships between the entities. In some embodiments, instructions cause the one or more processors to add one or more nodes representing the state to the digital twin based on the schema, the one or more nodes having one or more relationships with the entity of the entity class to be related.

Another implementation of the present disclosure is a method that includes performing, by one or more processing circuitry, one or more first operations based on a digital twin of a building to obtain a state for an entity of the digital twin deriving, the digital twin including representations of entities of the building and relationships between the entities, and updating a schema of the digital twin by adding a state type of the state to an entity class of the schema by one or more processing circuits. The method includes adding, by one or more processing circuitry based on the schema, one or more data items representing the state to the digital twin, the one or more data items being related to a node representing the entity of the entity class and performing, by one or more processing circuitry, one or more second operations based on the one or more data items representing the state.

In some embodiments, the entities include at least one of a person, point, location, or event, and the schema defines entity classes for entity types of the entities. In some embodiments, the entities are instances of entity classes defined by the schema.

In some embodiments, the method includes updating the schema of the digital twin by one or more processing circuits while the digital twin is being deployed, without having to re-deploy the digital twin.

In some embodiments, the schema defines entity classes, where the entity classes specify properties, tags, and states for the entity classes.
In some embodiments, the method includes performing, by one or more processing circuits, the one or more first operations based on the digital twin of the building and external data collected from an external system, the state of the external data for the entity of the digital twin is derived.

In some embodiments, the digital twin includes nodes and borders between the nodes, where the nodes represent the entities of the building and the borders indicate the relationships between the entities. In some embodiments, the method includes adding, by the one or more processing circuits based on the schema, one or more nodes representing the state to the digital twin, where the one or more nodes are linked by one or more relationships with the entity of the entity class are related.

In some embodiments, the method includes receiving, by one or more processing circuits, an indication to add the state to the entity, identifying, by one or more processing circuits, the entity class of the entity based on the schema, updating by one or more Processing circuitry, the schema of the digital twin by adding the state type to the entity class of the schema, in response to identifying that a class of the entity is the entity class, and adding, by one or more processing circuitry based on the schema, the one or the a plurality of nodes representing the state to the digital twin, the one or more nodes being related to a second node representing a second entity of the entity class, the entity being different than the second entity.

In some embodiments, an application begins operating to perform the one or more initial operations based on the digital twin of the building to infer the state for the entity after the digital twin is deployed and before the digital twin schema is updated.

In some embodiments, the method includes receiving, by one or more processing circuits, output from the application resulting from the one or more first operations, the output indicating the state, browsing, by one or more processing circuits, of the Digital twin schemas to determine whether the schema includes the state type indicated by the output of the one or more first operations and updating, by one or more processing circuits, the digital twin schema by adding the state type of the state to the schema's entity class, responsive to identifying that the schema does not include the state type.

Another implementation of the present disclosure is a building system that includes one or more storage devices having instructions thereon and one or more pro processors configured to execute the instructions that cause the one or more processors to perform one or more first operations based on a digital twin of a building to derive a state for a digital twin entity, the digital twin representations of entities of the building and relationships between the entities. The instructions cause the one or more processors to update a schema of the digital twin by adding a state type of the state to an entity class of the schema, based on the schema, adding one or more data items representing the state to the digital twin, wherein the one or more data items are related to the entity of the entity class, and perform one or more second operations based on the one or more data items representing the state.

character list

• 1 ist ein Blockdiagramm einer Gebäudedatenplattform, die eine Randplattform, eine Cloud-Plattform und einen Zwillingsmanager nach einer beispielhaften Ausführungsform beinhaltet.
• 2 ist eine graphische Projektion des Zwillingsmanagers von 1 einschließlich Anwendungsprogrammierschnittstellen (API)-Daten, Fähigkeitsdaten, Richtliniendaten und Diensten nach einer beispielhaften Ausführungsform.
• 3 ist eine weitere graphische Projektion des Zwillingsmanagers von 1 einschließlich Anwendungsprogrammierschnittstellen (API)-Daten, Fähigkeitsdaten, Richtliniendaten und Diensten nach einer beispielhaften Ausführungsform.
• 4 ist eine graphische Projektion des Zwillingsmanagers von 1 einschließlich Ausrüstungs- und Fähigkeitsdaten für die Ausrüstung nach einer beispielhaften Ausführungsform.
• 5 ist ein Blockdiagramm eines Erweiterbarkeitsmanagers, der eine Schemadefinition eines digitalen Zwillings zur Laufzeit erweitert, nach einer beispielhaften Ausführungsform.
• 6 ist ein Blockdiagramm des Zwillingsmanagers von 1, bei dem ein erweiterbarer Eigenschaftsmanager einen digitalen Zwilling aktualisiert, um neue Eigenschaften in das Schema des digitalen Zwillings einzubeziehen, nach einer beispielhaften Ausführungsform.
• 7 ist ein Flussdiagramm eines Prozesses, bei dem der erweiterbare Eigenschaftsmanager von 6 einen digitalen Zwilling aktualisiert, um neue Eigenschaften in das Schema des digitalen Zwillings einzubeziehen, nach einer beispielhaften Ausführungsform.
• 8 ist ein Blockdiagramm eines erweiterbaren Zustandsmanagers, der den digitalen Zwilling basierend auf von einem Fehleranalyseagenten empfangenen Informationen aktualisiert, wobei die Aktualisierung veranlasst, dass der digitale Zwilling neue Zustände beinhaltet, die Fehler in dem Schema des digitalen Zwillings angeben, nach einer beispielhaften Ausführungsform.
• 9 ist ein Blockdiagramm des erweiterbaren Zustandsmanagers, der den digitalen Zwilling basierend auf von einem Kalenderagenten empfangenen Informationen aktualisiert, wobei die Aktualisierung veranlasst, dass der digitale Zwilling neue Zustände beinhaltet, die die Belegung in dem Schema des digitalen Zwillings angeben, nach einer beispielhaften Ausführungsform.
• 10 ist ein Flussdiagramm eines Prozesses zum Aktualisieren des digitalen Zwillings basierend auf von einem Agenten empfangenen Informationen, wobei die Aktualisierung veranlasst, dass der digitale Zwilling neue Zustände beinhaltet, die eine Belegung in dem Schema des digitalen Zwillings angeben, nach einer beispielhaften Ausführungsform.

Various objects, aspects, features and advantages of the disclosure will become more apparent and better understood by reference to the detailed description in conjunction with the accompanying drawings, in which like reference characters indicate corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

• 1 12 is a block diagram of a building data platform that includes an edge platform, a cloud platform, and a twin manager, according to an example embodiment.
• 2 is a graphical projection of the twin manager of 1 including application programming interface (API) data, capability data, policy data, and services according to an example embodiment.
• 3 is another graphical projection of the twin manager of 1 including application programming interface (API) data, capability data, policy data, and services according to an example embodiment.
• 4 is a graphical projection of the twin manager of 1 including equipment and capability data for the equipment according to an exemplary embodiment.
• 5 12 is a block diagram of an extensibility manager extending a digital twin schema definition at runtime, according to an example embodiment.
• 6 is a block diagram of the twin manager of 1 wherein an extensible property manager updates a digital twin to include new properties in the digital twin's schema, according to an example embodiment.
• 7 is a flowchart of a process by which the extensible property manager of 6 updates a digital twin to include new properties in the digital twin schema, according to an example embodiment.
• 8th 12 is a block diagram of an extensible state manager that updates the digital twin based on information received from a fault analysis agent, the update causing the digital twin to include new states that indicate faults in the digital twin schema, according to an example embodiment.
• 9 12 is a block diagram of the extensible state manager that updates the digital twin based on information received from a calendar agent, the update causing the digital twin to include new states that indicate occupancy in the digital twin schema, according to an example embodiment.
• 10 12 is a flowchart of a process for updating the digital twin based on information received from an agent, the update causing the digital twin to include new states that indicate population in the digital twin schema, according to an example embodiment.

DETAILED DESCRIPTION

With general reference to the FIGURES, systems and methods for dynamic extensibility of properties, tags, and states in a digital twin schema are shown, according to various example embodiments. A digital twin can provide a virtual representation of a building, e.g. B. both in relation to contextual information that describes the building as well as telemetry data collected from building equipment. The digital twin can act as a replica that illustrates the building's entities (e.g., assets, people, points, locations, and events) and relationships between the different entities. The digital twin may be implemented in the form of a graph data structure in some embodiments.

In some embodiments, the entities and relationships between the entities may be defined in the form of a schema. The schema may define the entities, entity properties, entity tags, entity states, etc. in terms of a class structure, with each entity including specific corresponding properties, tags, or states. For example, each thermostat entity could have a temperature setpoint state, a current temperature state, a tag indicating when the equipment was last serviced, a property indicating that the thermostat includes an indicator, properties indicating that the thermostat accepts the types of inputs or outputs of the thermostat, etc. include. The schema could be a strongly-typed schema, such as BRICK, in some embodiments.

BRICK is described in Brick: Towards a Unified Metadata Schema For Buildings by Balaji et al., incorporated herein by reference.

In some embodiments, a building system can extend the digital twin schema to include different properties, tags, and/or states. This extension can be performed at runtime, allowing the digital twin and/or the system running the digital twin to make changes to the schema without redeploying the digital twin and/or the system running the digital twin and/or need to be reconfigured (which would result in downtime). The digital twin schema can be dynamically extended by the building system in some embodiments. For example, the building system may determine (during runtime) that new states, properties, or tags are needed that would increase the performance of the digital twin (e.g., allow the digital twin to relate new key pieces of information to consuming systems) . The building system can make these runtime updates to the digital twin schema.

In some embodiments, the updated schema of the digital twin, e.g. B. the new properties, tags and/or states of the entities, are used by a system, an application and/or an agent that works against data of the digital twin. For example, such a system, application, and/or agent could search and filter the digital twin based on the digital twin's new properties, tags, and/or states. The system, application, and/or agent could implement temperature control, humidity control, air quality control, false alarm analysis, building fault analysis, etc. based on the updated digital twin.

In some embodiments, a BIM viewer capable of rendering BIM-related information in a user interface based on the graph could operate based on the updated digital twin schema. BIM viewers are described by reference to US Provisional Patent Application No. 63/214,217, filed June 23, 2021, at U.S. Patent Application No. 17/136,752 , filed December 29, 2020, the U.S. Patent Application No. 17/136,768 , filed December 29, 2020 and U.S. Patent Application No. 17/136,785 , filed December 29, 2020, the entirety of which is incorporated herein by reference. The BIM viewer may not work in the exact schema of the digital twin. Therefore, updates can be made to the schema to reflect various information required for the proper operation of the BIM Viewer. The BIM viewer could then query a graph of the digital twin in the updated schema based on tags, properties, states and/or other values added to the schema that may not be present in the original schema. The updated schema may allow values or other information to be queried from the digital twin at runtime without requiring updates to applications, systems for rebuilding and/or re-deploying, data migration, etc.

In some embodiments, the building system can update the schema of the digital twin to allow new types of events to be ingested and stored by the digital twin. For example, in some embodiments, the building system may receive new events and determine whether the event types of the new events are not present in the digital twin schema. The building system can add the new event type to the digital twin schema add , in response to detecting that the event type does not exist, allowing events of the new event type to be added to the digital twin. Allowing the digital twin to extend its schema to accommodate new event types for any entity in the digital twin is the driving feature that enables plug-and-play functionality and breaks the barrier to exploiting and extending the functionality of the digital twin lowers.

Examples of digital twins and adding schema information to a schema based on received data information are in U.S. Patent Application No. 17/134,661 , filed December 28, 2020, U.S. Patent Application No. 17/134,664 , submitted on December 28, 2020, U.S. Patent Application No. 17/134,671 , filed December 28, 2020, U.S. Patent Application No. 17/134,659 , filed December 28, 2020, U.S. Patent Application No. 17/134,973 , filed December 28, 2020, U.S. Patent Application No. 17/134,999 , filed December 28, 2020, U.S. Patent Application No. 17/135,023 , filed December 28, 2020, U.S. Patent Application No. 17/134,691 , filed December 28, 2020, U.S. Patent Application No. 17/135,056 , filed December 28, 2020, and U.S. Patent Application No. 17/135,009 , filed December 28, 2020, the entirety of each of which patent applications is incorporated herein by reference.

In some embodiments, adding a dynamic property or state to the schema may not necessarily cause the property or state to be propagated to other entities, e.g. eg it may not cause the creation of new properties or states for each entity of a schema class. For example, when an expected occupancy state is added for a "Conference Room ABC" entity, in some cases a conference room schema class for "Conference Room ABC" can be updated with the expected occupancy state (or a new schema for "Conference Room ABC" could be created, to handle the new state). The building system may not add the expected occupancy state to other existing conference room schema class entities (but may add the occupancy state to future conference room schema class entities when the entities are created).

In some embodiments, the propagation of newly added properties and/or states across entities of a schema type can be controlled by a user. For example, a user could specify a building system setting such that adding a new property or state to a particular entity of a particular schema class causes a new schema class to be created with the new property or state for the particular entity. This would stop propagating a new property to other entities. In some embodiments, a user could specify a preference that adding a new property or state to a particular entity of a particular schema class causes the new property or state to be added to all entities of the particular entity class. This would cause the new property to propagate to other entities. With reference to 1 Shown is a building data platform 100 that includes an edge platform 102, a cloud platform 106, and a twin manager 108, according to an exemplary embodiment. Edge platform 102, cloud platform 106, and twin manager 108 may each be separate services deployed on the same or different computing systems. In some embodiments, cloud platform 106 and twin manager 108 are implemented in external computing systems, e.g. B. outside a building. The edge platform 102 can be implemented internally, e.g. B. inside the building. However, any combination of internal and external building information platform 100 components may be implemented.

The building information platform 100 includes applications 110. The applications 110 can be various applications that operate to manage the building subsystems 122. FIG. Applications 110 may be remote or local (or a hybrid of both) running on different computing systems. Applications 110 may include an alarm application 168 configured to manage alarms for building subsystems 122 . The applications 110 include an insurance application 170 that implements insurance services for the building subsystems 122 . In some embodiments, the applications 110 include an energy application 172 configured to manage energy consumption of the building subsystems 122 . The applications 110 include a security application 174 configured to manage building security systems.

In some embodiments, the applications 110 and/or the cloud platform 106 interact with a user device 176. In some embodiments, a component or an entire application of the applications 110 runs on the user device 176. The user device 176 can be a laptop computer, a desktop Computer, smartphone, tablet, and/or any other device with an input interface (e.g., touch screen, mouse, keyboard, etc.) and an output interface (e.g., speaker, display, etc.).

Applications 110, twin manager 108, cloud platform 106, and edge platform 102 may be implemented on one or more computing systems, e.g. B. on processors and / or memory devices. For example, edge platform 102 includes processor(s) 118 and memory 120, cloud platform 106 includes processor(s) 124 and memory 126, applications 110 includes processor(s) 164 and memory 166, and twin manager 108 includes processor(s) 148 and memory 150.

The processors can be general purpose or special purpose processors, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), an array of processing components, or other suitable processing components. The processors may be configured to execute computer code and/or instructions stored in the memories or received from other computer-readable media (e.g., CD-ROM, network storage, a remote server, etc.).

The memories may include one or more devices (e.g., storage units, temporary storage devices, persistent storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory may include random access memory (RAM), read only memory (ROM), hard disk memory, cache memory, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The stores may include database components, object code components, script components, or any other type of information structure to support the various activities and information structures described in the present disclosure. The memories may be communicably coupled to the processors and may include computer code for executing (e.g., by the processors) one or more processes described herein.

Edge platform 102 may be configured to provide connectivity to building subsystems 122 . The edge platform 102 may receive messages from the building subsystems 122 and/or provide messages to the building subsystems 122 . Edge platform 102 includes one or more gateways, e.g. e.g. the gateways 112-116. The gateways 112-116 can act as a gateway between the cloud platform 106 and the building subsystems 122. The gateways 112-116 can be those in the preliminary U.S. Patent Application No. 62/951,891 , filed December 20, 2019, the entirety of which is incorporated herein by reference. In some embodiments, applications 110 may be deployed on edge platform 102 . In this regard, lower latency in management of the building subsystems 122 can be realized.

The edge platform 102 may be connected to the cloud platform 106 via a network 104 . The network 104 can communicatively couple the devices and systems of the building information platform 100 . In some embodiments, network 104 is at least one of and/or a combination of a Wi-Fi network, a wired Ethernet network, a ZigBee network, a Bluetooth network, and/or any other wireless network. The network 104 can be a local area network or a wide area network (e.g., the Internet, a building WAN, etc.) and can use a variety of communication protocols (e.g., BACnet, IP, LON, etc.). Network 104 may include routers, modems, servers, cell towers, satellites, and/or network switches. Network 104 can be a combination of wired and wireless networks.

Cloud platform 106 may be configured to facilitate communication and routing of messages between applications 110, twin manager 108, edge platform 102, and/or any other system. The cloud platform 106 may include a platform manager 128, a notification manager 140, a command processor 136, and an enrichment manager 138. In some embodiments, the cloud platform 106 can facilitate notification of the building data platform 100 over the network 104 .

Notification manager 140 may be configured to operate as a transport service that controls communication with building subsystems 122 and/or any other system, e.g. B. Managing commands to devices (C2D), commands to connectors (C2C) for external systems, commands from device to cloud (D2C) and/or notifications. Notification manager 140 may receive different types of data from applications 110, twin manager 108, and/or edge platform 102. Notification manager 140 may receive changes to value data 142, e.g. B. Data indicating that a value of a point has changed. Notification manager 140 may receive time series data 144, e.g. B. a time-correlated series of data entries, each associated with a particular timestamp. In addition, notification manager 140 may receive command data 146 . All messages handled by the cloud platform 106 can be handled as an event, e.g. For example, data 142-146 may each be packaged as an event where a data value occurs at a particular time (e.g., a temperature measurement taken at a particular time).

The cloud platform 106 includes a command processor 136. The command processor 136 may be configured to receive commands to perform an action from the applications 110, the building subsystems 122, the user device 176, and so on. The command processor 136 can manage the commands, determine whether the command system is authorized to perform the particular commands, and issue the commands to the commanded system, e.g. B. the building subsystems 122 and / or the applications 110 communicate. The commands could be a command to change an operational setting that controls environmental conditions of a building, a command to perform analysis, and so on.

The cloud platform 106 includes an enrichment manager 138. The enrichment manager 138 may be configured to enrich the events received from the notification manager 140. The enrichment manager 138 can be configured to add context information to the events. The enrichment manager 138 can communicate with the twin manager 108 to retrieve the context information. In some embodiments, the context information is an indication of information related to the event. For example, if the event is a time-series temperature measurement from a thermostat, contextual information such as the location of the thermostat (e.g. which room), the equipment controlled by the thermostat (e.g. which VAV), etc added to the event. In this regard, if a consuming application, e.g. For example, when one of the applications 110 receives the event, the consuming application can operate based on the data of the event, the temperature measurement, and also the context information of the event.

The enrichment manager 138 can solve a problem that when a device produces a significant amount of information, the information may contain simple data without context. An example might include the data generated when a user scans a badge at a building subsystems 122 badge scanner. This physical event may generate an output event that includes such information as "DeviceBadgeScannerID", "BadgeID" and/or "Date/Time". However, if a system sends this data to a consuming application, e.g. B. Consumer A and a consumer B, each customer may need to call the knowledge service of the building data platform to provide information with queries such as "In which room, which building, which floor is this badge scanner located?" or "Which user is connected to this badge ?”

By performing data injection enrichment, a system may be able to make inferences about the data. A result of the enrichment may be the conversion of the message "DeviceID, ID, Date/Time" to "Region, Building, Floor, Asset, DeviceId, ID, UserName, EmployeeId, Date/Time scanned". This can be a significant optimization as a system can reduce the number of calls by 1/n, where n is the number of consumers of that data injection.

By using this enrichment, a system can also have the ability to filter out undesired events. If there are 100 buildings on a campus receiving 100,000 events per building hourly, but only 1 building is actually operational, only 1/10 of the events will be enriched. By considering which events are enhanced and which events are not enhanced, a system can perform traffic shaping of the forwarding of those events to reduce the cost of forwarding events that no consuming application wants or reads.

               {
               „id": „someguid",
               „eventType": „Device_Heartbeat",
               „eventTime": „2018-01-27T00:00:00+00:00"
               „eventValue": 1,
               „deviceID": „someguid"
               }

An example of an event received by the enrichment manager 138 may be:

 {
               "id": "someguid",
               "eventType": "Device_Heartbeat",
               "eventTime": "2018-01-27T00:00:00+00:00""eventValue": 1,
               "deviceID": "someguid"
               }

               {
               „id": „someguid",
               „eventType": „Device_Heartbeat",
               „eventTime": „2018-01-27T00:00:00+00:00"
               „eventValue": 1,
               „deviceID": "someguid",
               „buildingName": "Building-48",
               „buildingID": "SomeGuid",
               „panelID": „SomeGuid",
               „panelName": „Building-48-Panel-13",
               „cityID": 371,
               „cityName": "Milwaukee",
               „stateID": 48,
               „stateName": "Wisconsin (WI)",
               „countryID": 1,
               „countryName": "United States"
               }

An example of an enriched event generated by the enrichment manager 138 may be:

 {
               "id": "someguid",
               "eventType": "Device_Heartbeat",
               "eventTime": "2018-01-27T00:00:00+00:00""eventValue": 1,
               "deviceID": "someguid",
               "buildingName": "Building-48",
               "buildingID": "SomeGuid",
               "panelID": "SomeGuid",
               "panelName": "Building-48-Panel-13",
               "cityID": 371,
               "cityName": "Milwaukee",
               "stateID": 48,
               "stateName": "Wisconsin (WI)",
               "countryID": 1,
               "countryName": "United States"
               }

By receiving enriched events, an application of applications 110 may be able to populate and/or filter which events are associated with which areas. Additionally, user interface generation applications can generate user interfaces that include the context information based on the enriched events.

The cloud platform 106 includes a platform manager 128. The platform manager 128 may be configured to manage the cloud platform 106 users and/or subscriptions. For example, which subscribing building, user, and/or tenant is using the cloud platform 106 . The platform manager 128 includes a provisioning service 130 configured to provision the cloud platform 106, the edge platform 102, and the twin manager 108. The platform manager 128 includes a subscription service 132 for managing a subscription of the building, user, and/or tenant, while the entitlement service 134 may track entitlements of the building, user, and/or tenant.

The twin manager 108 can be configured to manage and maintain a digital twin. The digital twin can be a digital representation of the physical environment, e.g. B. a building. The twin manager 108 may include a change injection generator 152, schema and ontology 154, a projection manager 156, a policy manager 158, an entity, relationship, and event database 160, and a graph projection database 162.

Graph projection manager 156 may be configured to construct graph projections and store the graph projections in graph projection database 162 . Examples of graph projections are in the 11-13 shown. Entities, relationships, and events can be stored in database 160. Graph projection manager 156 may retrieve entities, relationships, and/or events from database 160 and construct a graph projection based on the retrieved entities, relationships, and/or events. In some embodiments, database 160 includes an entity relationship collection for multiple subscriptions.

In some embodiments, graph projection manager 156 creates a graph projection for a particular user, application, subscription, and/or user specific system. In this regard, the graph projection may be generated based on policies for the particular user, application, and/or system in addition to an ontology specific to that user, application, and/or system. In this regard, an entity could request a graph projection and the graph projection manager 156 can be configured to generate the graph projection for the entity based on policies and an ontology specific to the entity. The policies may indicate which entities, relationships, and/or events the entity has access to. The ontology can indicate what types of relationships between entities the requesting entity expects to see, e.g. B. floors within a building, devices within a floor, etc. Another requesting entity may have an ontology to see devices within a building and applications for the devices within the graph.

The graph projections generated by graph projection manager 156 and stored in graph projection database 162 may be a knowledge graph and an integration point. For example, the graph projections can represent floor plans and systems associated with each floor. Furthermore, the graph projections can contain events, e.g. B. Building subsystems 122 telemetry data. The graph projections may show application services as nodes and API calls between the services as edges in the graph. The graph projections can illustrate the capabilities of spaces, users, and/or devices. The graph projections may include information about the building subsystems 122, e.g. B. thermostats, cameras, VAVs, etc. The graph projection database 162 can store graph projections that maintain a current state of a building.

The graph projections of graph projection database 162 may be digital twins of a building. Digital twins can be digital replicas of physical entities, allowing in-depth analysis of the physical entity's data and providing the potential to monitor systems to mitigate risk, manage issues, and use simulation to test future solutions. Digital twins can play an important role in helping technicians find the root cause of problems and resolve issues faster, support safety protocols, and help facility managers use energy and other facility resources more efficiently. Digital twins can be used to enable and unify safety systems, employee experience, asset management, sustainability, etc.

In some embodiments, the enrichment manager 138 may use a graph projection of the graph projection database 162 to enrich events. In some embodiments, the enrichment manager 138 may identify nodes and relationships associated with and relevant to the device that generated the event. For example, the enrichment manager 138 could identify a thermostat that generates a temperature measurement event within the graph. Enrichment manager 138 may identify relationships between the thermostat and rooms, e.g. B. a zone where the thermostat is located. The enrichment manager 138 can add an indication of the zone to the event.

Furthermore, the command processor 136 may be configured to use the graph projections to command the building subsystems 122 . The command processor 136 may identify a policy for a command entity within the graph projection to determine whether the command entity is capable of issuing the command. For example, before allowing a user to issue a command, the command processor 136 determines based on the graph projection database 162 that the user has a policy to be able to issue the command.

In some embodiments, the policies may be conditional policies. For example, building information platform 100 may apply one or more conditional rules to determine whether a particular system is capable of performing an action. In some embodiments, the rules analyze behavior-based biometrics. For example, behavior-based biometrics may indicate normal behavior and/or normal behavioral rules for a system. In some embodiments, if the building information platform 100 determines, based on the one or more conditional rules, that an action requested by a system does not conform to normal behavior, the building information platform 100 may deny the system an opportunity to perform the action and/or a Request approval from a higher-level system.

For example, a behavior rule might specify that a user has access to log on to a system with a specific IP address between 8:00 am and 5:00 pm. If the However, if the user logs into the system at 7:00 p.m., the building information platform 100 can contact an administrator to determine whether to allow the user to log in.

The change feed generator 152 may be configured to generate a feed of events indicative of changes to the digital twin, e.g. B. on the graph. The change injection generator 152 may track changes to the graph's entities, relationships, and/or events. For example, the change injection generator 152 may detect an addition, deletion, and/or modification of a node or an edge of the graph, e.g. e.g., changing entities, relationships, and/or events within database 160. In response to detecting a change in the graph, change injection generator 152 may generate an event summarizing the change. The event may indicate which nodes and/or edges have changed and how the nodes and edges have changed. The events can be published by the change injection generator 152 to a topic.

Change injection generator 152 may implement change injection of a knowledge graph. The building data platform 100 can implement a subscription to changes in the knowledge graph. When the change injection generator 152 publishes events in the change injection, subscribing systems or applications may receive the change injection event. By creating a record of all changes made, a system can provide data in different ways and then play back the data in the order the system desires. This may involve running the changes sequentially one by one and/or jumping from one major change to the next. For example, to generate a graph at a particular point in time, all change injection events up to that particular point in time can be used to construct the graph.

The change injection, in some embodiments, can track the changes in each node in the graph and the relationships associated therewith. If a user wants to subscribe to these changes and the user has the right access, the user can simply make a web API call to get sequential notifications about each change that occurs in the graph. A user and/or system can reflect the changes one by one to restore the graph at any given time period. Even if the messages are "sparse" and contain only the change notification and the reference "id/seq id", the change injection can keep a copy of every state of every node and/or every relationship, so that a user and/or a system can keep these past states can retrieve at any time for each node. Furthermore, a change injection consumer could also create dynamic "views" that allow different time-based "snapshots" of what the graph looks like in a given context. While the twin manager 108 can contain the history and current state of the graph based on the schema evaluation, a consumer can keep a copy of this data and thereby create dynamic views using change injection.

• Region ←→ Gebäude ←→ Stockwerk ←→ Raum ←→ Asset

Schema and ontology 154 may define the twin manager 108 message schema and graph ontology. The message schema may define what format messages received from the notification manager 140 should have, e.g. e.g. which parameters, which formats etc. Ontology can define graph projections e.g. B. the ontology that a user wants to see. For example, different systems, applications, and/or users may be associated with a graph ontology. Accordingly, when the graph projection manager 156 creates a graph projection for a user, system, or subscription, the graph projection manager 156 may create a graph projection according to the ontology specific to the user. For example, the ontology can define what types of entities are related in what order in a graph, e.g., for the ontology for a subscription of "Customer A" the graph projection manager 156 can create relationships for a graph projection based on rule:

• Region ←→ Building ←→ Floor ←→ Room ←→ Asset

• Gebäude ←→ Stockwerk ←→ Asset

For the ontology of a "Customer B" subscription, the graph projection manager can create 156 relationships based on the rule:

• Building ←→ Floor ←→ Asset

Policy manager 158 may be configured to respond to requests for policies from other applications and/or systems. The policy manager 158 can create a graph project tion to determine what permissions different applications, users and/or devices have. The graph projection can indicate different permissions representing different types of entities, and the policy manager 158 can search the graph projection to identify the permissions of a particular entity. Policy manager 158 can facilitate fine-grained access control with user permissions. The policy manager 158 can apply permissions via a graph, e.g. e.g. "the user can see all data related to floor 1", he sees all subsystem data for that floor, e.g. B. Surveillance cameras, HVAC devices, fire detection and response devices, etc.

The twin manager 108 includes a query manager 165 and a twin function manager 167. The query manager 164 may be configured to handle queries submitted by a requesting system, e.g. the user device 176, the applications 110 and/or any other system. The query manager 165 can receive queries that include query parameters and context. The query manager 165 can query the graph projection database 162 with the query parameters to retrieve a result. The query manager 165 can then use an event processor, e.g. a twin function, to work based on the result and the context. In some embodiments, the query manager 165 can select the twin function based on the context and/or perform operations based on the context. In some embodiments, query manager 165 is configured to 5-10 perform the operations described.

The twin role manager 167 may be configured to manage the execution of twin roles. The twin function manager 167 may receive an indication of a context query identifying a particular data item and/or pattern in the graph projection database 162 . In response to the particular data item and/or pattern occurring in the graph projection database 162 (e.g., based on a new data event added to the graph projection database 162 and/or changes to nodes or edges of the graph projection database 162, the twin function manager 167 cause a specific twin function to be performed. The twin function may be performed based on an event, context, and/or rules. The event may be data on which the twin function is performed. The context may be information that provides a contextual description of the provide data such as which device the event is associated with, which checkpoint should be updated based on the event, etc. The twin function manager 167 may be configured to manage the operations of the 11-15 to perform.

With reference to 2 1 is a graph projection 200 of the twin manager 108 that includes application programming interface (API) data, capability data, policy data, and services, according to an exemplary embodiment. Graph projection 200 includes nodes 202-240 and edges 250-272. The nodes 202-240 and the edges 250-272 are defined according to the key 201. Nodes 202-240 represent different types of entities, devices, locations, points, people, policies, and software services (e.g., API services). Boundaries 250-272 represent relationships between nodes 202-240, e.g. B. dependent calls, API calls, derived relationships and schema relationships (e.g. BRICK relationships).

The graph projection 200 includes a device hub 202 that may represent a software service that facilitates the communication of data and commands between the cloud platform 106 and a device of the building subsystems 122, e.g. B. a door operator 214 facilitated. The device hub 202 is in communication with a connector 204, an external system 206, and a digital asset "door operator" 208 through edge 250, edge 252, and edge 254.

Cloud platform 106 may be configured to identify device hub 202, connector 204, external system 206 with respect to door operator 214 by searching graph projection 200 and identifying edges 250-254 and edge 258. Graph projection 200 includes a digital representation of "Door Operator", node 208. Digital asset "Door Operator" 208 includes "DeviceNameRoom" represented by node 207 and connected to digital asset "Door Operator" 208 by edge 256 "Property of object” is related.

The "door operator" 214 has points and time series. The "door operator" 214 is related to "point A" 216 by a "has_a" border 260 . The "door operator" 214 is related to "point B" 218 by "has_a" edge 258 . Furthermore, the time series associated with points A and B are represented by nodes “TS” 220 and “TS” 222 . The time series stand by at points A and B "has_an" edge 264 and "has_an" edge 262 in relation. The time series "TS" 220 has certain samples, patterns 210 and 212, related to "TS" 220, respectively, with margins 268 and 266, respectively. Each sample includes a time and a value. Each sample may be an event received from the door operator that cloud platform 106 records in entity, relationship, and event database 160, e.g. B. in the graph projection 200 includes.

The graph projection 200 includes a building 234 that represents a physical building. The building includes a floor represented by floor 232 that is related to building 234 by "has_a" border from building 234 to floor 232 . The floor has a room indicated by "has_an" 270 between floor 232 and room 230 . The room has special capabilities, e.g. is a room that can be booked for a meeting, conference, private study time, etc. Furthermore, the booking can be cancelled. Capabilities for floor 232 are represented by capabilities 228 with respect to space 230 by border 280 . The capabilities 228 are related to two different commands, the book room command 224 and the cancel booking command 226, which are related to the capabilities 228 by border 284 and border 282.

When the cloud platform 106 receives a command to book the space space 230 represented by the node, the cloud platform 106 can search the graph projection 200 for the capabilities for the space 228 associated with the space 230 to determine whether the cloud platform 106 can book the room.

In some embodiments, the cloud platform 106 could receive a request to book a room in a specific building, e.g. B. the building 234 received. The cloud platform 106 could search the graph projection 200 to identify rooms that have the ability to be booked, e.g. B. identify space 230 based on capabilities 228 related to space 230 . The cloud platform 106 can respond to the request with an indication of the room and allow the requesting entity to book the room 230 .

The graph projection 200 includes a policy 236 for the floor 232. The policy 236 is set relative to the floor 232 based on a "to floor" margin 274 between the policy 236 and the floor 232. FIG.

Policy 236 is related to various roles for floor 232, read events 238 via edge 276, and send command 240 via edge 278. Policy 236 is set for entity 203 based on "has" margin 251 between entity 203 and policy 236 .

The twin manager 108 can set policies for specific entities, e.g. B. identify users, software applications, systems, devices, etc., based on policy 236. For example, when cloud platform 106 receives a command to reserve storage space 230 . The cloud platform 106 may communicate with the twin manager 108 to verify that the entity requesting the booking of the room 230 has a policy to book the room. Twin manager 108 can identify the entity requesting the booking of the room as entity 203 by searching graph projection 200 . Furthermore, the twin manager 108 can further identify the boundary 251 between the entity 203 and the policy 236 and the boundary 1178 between the policy 236 and the command 240.

Furthermore, twin manager 108 may identify that entity 203 has the ability to command room 230 based on boundary 1174 between policy 236 and boundary 270 between floor 232 and room 230 . In response to identifying that entity 203 has the ability to book room 230 , twin manager 108 may provide an indication to cloud platform 106 .

Furthermore, if the entity makes a request to read events for the space 230, e.g. For example, pattern 210 and pattern 212, twin manager 108 can use border 251 between entity 203 and policy 236, border 1178 between policy 236 and read events 238, border 1174 between policy 236 and floor 232, "has_an" edge 270 between the floor 232 and the room 230, the edge 268 between the room 230 and the door operator 214, the edge 260 between the door operator 214 and the point A 216, "has_an" edge 264 between the point Identify A 216 and TS 220 and the margins 268 and 266 between TS 220 and samples 210 and 212, respectively.

With reference to 3 1 is a graph projection 300 of the twin manager 108 that includes application programming interface (API) data, capability data, policy data, and services, according to an example embodiment. The graph projection 300 includes those shown in the graph projection 200 of FIG 2 nodes and edges described. Graph projection 300 includes a connection broker 354 that interfaces with capabilities 228 through edge 398a. Connection broker 354 may be a node representing a software application configured to facilitate connection with another software application. In some embodiments, cloud platform 106 may identify the system implementing capabilities 228 by identifying edge 398a between capabilities 228 and connection broker 354 .

The connection broker 354 is related to an agent that optimizes a space 356 over the edge 398b. The agent represented by node 356 can book and cancel bookings for the space represented by node 230 based on the edge 398b between the connection switch 354 and the node 356 and the edge 398a between the capabilities 228 and the connection switch 354.

Connection broker 354 is related to cluster 308 by edge 398c. Cluster 308 is related to connector B 302 by edge 398e and to connector A 306 by edge 398d. Connector A 306 is related to an external subscription service 304 . A connection broker 310 is related to cluster 308 by an edge 311 that represents a sleep call that the connection broker represented by node 310 can make to the cluster represented by cluster 308 .

The connection broker 310 is related to a virtual session platform 312 by an edge 354 . Node 312 represents an external system that represents a virtual session platform. The connection broker represented by node 310 may represent a software component that facilitates a connection between cloud platform 106 and the virtual session platform represented by node 312 . When the cloud platform 106 needs to communicate with the virtual session platform represented by node 312, the cloud platform 106 can identify the edge 354 between the connection broker 310 and the virtual session platform 312 and select the connection broker represented by node 310 to initiate the communication with the virtual session platform represented by node 312.
A capability node 318 may be connected to connection switch 310 via edge 360 . Capabilities 318 may be capabilities of the virtual session platform represented by node 312 and may be related to node 312 through edge 360 to connection switch 310 and edge 354 between connection switch 310 and node 312 . Capabilities 318 may define capabilities of the virtual session platform represented by node 312. Node 320 is related to capabilities 318 via border 362 . The capabilities may be an "Invite Bob" command, represented by node 316, and an "Email Bob" command, represented by node 314. Capabilities 318 may be associated with a node 320 representing a user, Bob. Cloud platform 106 may facilitate email commands to send emails to user Bob via email service represented by node 304 . Node 304 is related to connecting node 306 across edge 398f. Furthermore, cloud platform 106 may facilitate sending an invitation to a virtual session via the virtual session platform represented by node 312 linked to node 318 by edge 358 .

Node 320 for user Bob may be connected to policy 236 via "has" edge 364 . Further, the node 320 can have a "check policy" border 366 with a portal node 324 . The device API node 328 has a check policy border 370 to the policy node 236 . Portal node 324 has an edge 368 to policy node 236 . The portal node 324 has a border 323 to a node 326 representing a user input manager (UIM). Portal node 324 is related to UIM node 326 by edge 323 . The UIM node 326 has an edge 323 to a device API node 328 . The UIM node 326 is related to the door operation node 214 by an edge 372 . The door operation node 214 has a border 374 to the device API node 328 . The door operator 214 has an edge 335 to the virtual object connector 334 . The device hub 332 overhangs the edge 380 with the virtual object connector Relationship. Device API node 328 may be an API for door operator 214 . Virtual object connector 334 is related to device API node 328 via edge 331 .
The device API node 328 is related to a transport connection switch 330 via an edge 329 . The transport connection switch 330 is related to a device hub 332 by an edge 378 . The device hub represented by node 332 may be a software component that handles the communication of data and commands for door operator 214 . Cloud platform 106 may identify where to store data within graph projection 300 received from door operator by identifying the nodes and edges between points 216 and 218 and device hub node 332 . Similarly, cloud platform 308 may identify door operator commands, which may be facilitated by the device hub represented by node 332, e.g. B. by identifying borders between the device hub node 332 and an open door node 352 and a closed door node 350 . Capability node 348 and nodes 352 and 350 are linked by edges 396 and 394, respectively.

Device hub 332 is linked to cluster 336 by edge 384 . Cluster 336 is linked to connector A 340 and connector B 338 via edges 386 and edge 389 . Connector A 340 and connector B 338 are linked to an external system 344 via edges 388 and 390 . The external system 344 interfaces with a door operator 342 via an edge 392 .

With reference to 4 1 shows a graph projection 400 of twin manager 108 including equipment and capability data for the equipment, according to an exemplary embodiment. Graph projection 400 includes nodes 402-456 and edges 360-498f. The cloud platform 106 can search the graph projection 400 to identify capabilities of different pieces of equipment.

A building node 404 represents a particular building that includes two stories. A floor 1 node 402 is linked to building node 404 by edge 460 , while a floor 2 node 406 is linked to building node 404 by edge 462 . Floor 2 includes a particular room 2023 represented by border 464 between node 406 of floor 2 and node 408 of room 2023 . Various pieces of equipment are included in room 2023. A light represented by light node 416, bedside lamp node 414, bedside lamp node 412, and hallway light node 410 are related to node 408 of room 2023 via edge 466, edge 472, edge 470, and edge 468.

The light represented by light node 416 is related to light connector 426 via edge 484 . Light connector 426 is related to multiple commands for the light represented by light node 416 via edges 484, 486, and 488. The commands may be a brightness command 424, an on command 425, and a tint command 428. Cloud platform 106 may receive a request to identify commands for the light represented by light 416 and may identify nodes 424-428 and provide the requesting entity with an indication of the commands represented by nodes 424-428. The requesting entity can then send commands for the commands represented by nodes 424-428.

The bedside lamp node 414 is linked to a bedside lamp connector 481 by a border 413 . Connector 481 is related to commands for the bedside lamp represented by bedside lamp node 414 via edges 492, 496, and 494. The command nodes are a brightness setpoint node 432, an on command node 434, and a color command 436. The hallway light 410 is related to a hallway light connector 446 by an edge 498d. Hallway light connector 446 is linked to a plurality of commands for hallway light node 410 via edges 498g, 498f, and 498e. The commands are represented by an on command node 452 , a tint setpoint node 450 , and a lightbulb activity node 448 .

The graph projection 400 includes a space name node 422 related to a server A node 418 and a server B node 420 by edges 474 and 476 . Room name node 422 is related to bedside lamp connector 481, bedside lamp connector 444, and hallway light connector 446 via edges 482, 480, and 478. The bedside lamp connector 444 is available with commands, e.g. B. the color command node 440, the hue target value command 438, a lightness target value command 456 and an on command 454 via borders 498c, 498b, 498a and 498 are related.

With general reference to 5 An extensibility manager 502 is shown extending a digital twin schema definition 500 at runtime, according to an exemplary embodiment. Schema definition 500 may be a particular definition of a larger schema. The schema definition 500 provides an example of a particular schema for a particular entity class 510 . The schema definition 500 includes various attributes for the entity class 510, e.g. e.g., an entity property 512, an entity property 514, an entity tag 516, and an entity state 518. The schema definition 500 could be implemented in a digital twin, e.g. B. in the graphs made with reference to the 1-4 or described elsewhere herein.

The entity class 510 could be a thermostat class, a people class, a video camera class, a conference room class, and so on. Entity class 510 may be a general category of an entity that describes all of the entity's attributes through the properties, tags, and states defined in schema definition 500 . When a new entity is created in a digital twin, any properties, tags, and/or states for the new entity may also be created and linked to the new entity through relationships based on the schema definition 500 . The schema definition 500 may be stored in a database in some embodiments.

The entity properties, entity property 512 and/or entity property 514, could be properties of entity class 510, e.g. e.g., inputs of a thermostat, outputs of the thermostat, computational resources of a computing system, capacity of a boiler, maximum air changes of an air handling unit, etc. Entity tag 516 may indicate a tag of entity class 510, e.g. e.g., indicate that a thermostat is part of a test group, indicate a date that maintenance should be performed on a pump system, indicate when a filter was last changed, etc. Entity state 518 could indicate a state of an entity, e.g. a temperature measured by a temperature sensor, a setpoint from a thermostat, an air quality measurement from an air quality sensor, an indication that a variable air volume (VAV) module is in a fault state, etc.

The extensibility manager 502 can be configured to extend the schema definition 500 by adding an extended schema 508 to the schema definition 500 . The extensibility manager 502 can perform the expansion at runtime while a building system running the digital twin is currently operational without requiring any downtime, reconfiguration, recomposition, manual intervention, and so on. The extensibility manager 502 includes an extensible property manager 504 and the extensible state manager 506.

The extensible property manager 504 can be configured to add properties and/or tags to the schema definition 500 . For example, the manager 504 can add tags and/or properties, e.g. e.g., extended entity tag 520 and/or extended entity property 522. The tag or property added to extended schema 508 can be any of the tags or properties discussed herein. The manager 506 can add states to the extended schema 508, e.g. B. the extended entity state 524. The extended entity state can be any state described herein. The manager 502 can update a digital twin based on the extended schema 508 . For example, for each instance of entity class 510, manager 502 may cause each instance of entity class 510 to include new tags, new properties, and/or new states defined by extended entity tag 520, extended entity property 522, and/or extended entity state 524 are. In some embodiments, the tags, properties, and/or states are set to default values.

With reference to 6 1, twin manager 108 is shown with extensible property or tag manager 504 updating a digital twin to include new properties or tags in the digital twin's schema, according to an example embodiment. In 6 the twin manager 108 includes a digital twin 608 that is updated to the digital twin 610 by the manager 504 . The manager 504 extends a schema used to define the entities in the digital twin 608 to add new properties and/or tags to the digital twin 606 .

The digital twin 608 includes nodes 612-628, which may be related to each other via borders. The nodes and edges of the digital twin 608 can form a graph, e.g. B. one of the graphs given with reference to 1-4 or described elsewhere herein. The digital twin 608 includes a building node 620 that represents a building. The building node 620 is related by edges to a floor node 616 and a floor node 622, which indicates that the building has two separate floors. The floor node 616 is related to a space heating node 612 indicating that the floor has space heating. The floor node 616 and the space heater 612 are related to a thermostat node 614 by borders that indicate that the floor has a thermostat that operates the space heater. The thermostat node 614 is related to a temperature setpoint node 618 to indicate the temperature setpoint of the thermostat.

The floor node 622 is related to a space heating node 626 indicating that the floor has space heating. The floor node 622 and the space heater 626 are related to a thermostat node 628 by borders indicating that the floor has a thermostat that operates the space heater. The thermostat node 628 is related to a temperature setpoint node 624 to indicate the temperature setpoint of the thermostat.

The manager 504 includes a user update detector 600, a new node detector 602, a new edge detector 604, and a property or tag updater 606. The user update detector 600 may be configured to receive information from the user device 176. The information can be requests for new properties or tags to be added to various entity classes. The detector 600 can analyze the data received from the user device 176 and identify to which entity classes properties and/or tags should be added. The detector 600 can cause the property or tag updater 606 to add the new properties and/or tags to the entity class in the digital twin schema 608 and further cause corresponding nodes and/or edges to be added to the digital twin 608 to represent the new properties and/or tags.

The new node detector 602 can identify that a new node has been added to the digital twin 608 . New nodes added to the digital twin 608 may indicate that new pieces of equipment have been installed in a building, new conference rooms have been created in the building, new equipment has been discovered over a network, etc. For example, a central fan could be installed in the building For example, central fan node 632 could be added to digital twin 608 to indicate that the central fan works for the building represented by building 620. The new node detector 602 could identify the new central fan node 632 and/or the new edge detector 604 could identify a new edge between the building 620 and the central fan 632 . The manager 504 may identify that the new nodes and/or edges indicate that new properties and/or tags should be added to the digital twin 608, where the new properties and/or tags may update the digital twin's 608 schema.

For example, if a central fan is added to the building, e.g. e.g. central fan 632, and adding a border between node 632 and building 620, manager 504 could identify that building control devices should be able to control the central fan, e.g. B. the controllers on the ability to control the central fan, z. B. because they are connected to the central fan (identified by recognizing relationships between the central fan node 632 and a node representing the controllers). The manager 504 can add a fan control properties node 630 and a fan control properties node 634 to the digital twin 608 . These new fan control properties can extend the schema of digital twin 608 to account for the fact that the thermostats represented by nodes 614 and 628 can now control a central fan, i. H. represented by central fan node 632. Nodes 630 and 634 may be capabilities in some embodiments.

The property or tag updater 606 may be configured to update properties and/or tags based on the detections, identifications, and/or determinations made by the detectors 600-604. Updater 606 may be configured to update a schema that defines digital twin 608 to produce an updated version of digital twin 608, digital twin 610. The updater 606 can cause updates to be made to the digital twin 608 based on the schema. For example, the updater 606 may consult the updated schema to update the properties and/or tags of existing digital twin 608 entities. Furthermore, when new entities of the updated entity class are added to the digital twin 608, they can be added with the new properties and/or tags. The updater 606 can add nodes that contain the new properties and/or Draw tags and borders between the new nodes and the entity node that represents a specific instance of the entity class.

With reference to 7 1 is shown a flow diagram of a process 700 in which the extensible property manager of FIG 6 updated a digital twin to include new properties in the digital twin schema. In some embodiments, manager 504 may be configured to perform process 700. In some embodiments, any computing device described herein may be configured to perform process 700 .

In step 702, the building data platform 100 can be deployed. The building information platform 100 can be deployed to operate based on a digital twin, e.g. B. digital twin 608 and/or any other digital twin and/or other graph data structure described herein. For example, different pieces of software and/or systems (e.g., the applications 110) can run against the digital twin, e.g. B. Making device control decisions for the building subsystems 122 (e.g., controlling temperature, humidity, lighting, etc.), determining alarms, reducing energy consumption of the building subsystems 122, etc.

In step 704, the manager 504 receives an indication to add a property or tag to an entity class of a digital twin schema. In some embodiments, the indication may be received from a user, e.g. via user device 176. In some embodiments, manager 504 may derive insight that the new property or tag should be added by identifying changes to the digital twin, e.g. B. Additions or subtractions of nodes and/or edges in the digital twin 608.
In step 706, the manager 504 operates to add the property or tag to entities of the digital twin, where the entities belong to the entity class. This extends the schema implemented in the digital twin. The extension of the schema, in addition to adding the properties or the nodes to the digital twin, can be performed while the building information platform 100 is being deployed without requiring reconfiguration and/or re-deployment of the building information platform 100 and/or the digital twin.

Updating the schema with new properties or tags for an entity may involve adding nodes and/or borders to the graph for each instance of the entity class. For example, if a new tag for a thermostat is added, the manager 504 can cause a node for the new tag to be added to the digital twin for each thermostat node. The manager 504 can cause one or more edges to relate the new node for the tag and the node for the entity in the digital twin. In step 708, the manager 504 performs one or more operations based on the one or more properties and/or nodes added to the digital twin, where the new properties or nodes extend the digital twin's schema.

With reference to 8th An extensible state manager 506 is shown that updates the digital twin 608 based on information received from a fault analysis agent, the update causing the digital twin 608 to include new states that indicate faults in the digital twin 608 schema, according to an exemplary embodiment. In some embodiments, an agent or any other type of application using the digital twin 608 (or digital twin 608 information) may add states to the digital twin 608 . For example, the failure analysis agent 808 may use machine learning models to detect failures for pieces of equipment in the digital twin 608 (e.g., by analyzing data and/or operations performed by the pieces of equipment).

However, the digital twin schema 608 may not include a mechanism capable of describing whether a particular device is faulty or operational. In this regard, based on the determinations made by the agent 808, the manager 506 may determine to add a state to the schema of the digital twin 608 describing the fault state of the thermostat. The manager 506 can cause a thermostat entity class to include a state that indicates whether or not the thermostat is in an error state. The manager 506 may cause all thermostats instantiated based on thermostat class to include a state indicating whether or not the thermostat is in an error state. Manager 506 may cause the state's default value to be an operational state that indicates that there is no error. However, if agent 808 identifies an error, the state may be set to an error state.

For example, the manager 506 could add a state for each digital twin 608 thermostat entity. The manager 506 could search the digital twin 608 for all entities of a thermostat class and identify the thermostat node 614 and the thermostat node 628 . The manager 506 could cause the fault state node 804 for the thermostat node 614 to be created and related to the thermostat node 614 via a boundary based on the update made to the schema for the thermostat entity class. The manager 506 may add the operational state node 806 and a border between the thermostat node 628 and the operational state 806 to the digital twin 608 based on the update made to the schema for the thermostat entity class. The fault state of node 804 may indicate that the thermostat represented by thermostat node 614 is experiencing a fault. The operational state of node 806 may indicate that the thermostat represented by thermostat node 628 is not experiencing a fault.

Agent 808 may perform the fault determination for the thermostat represented by thermostat node 614 (e.g., by consuming operational data associated with the thermostat, e.g., storing in digital twin 608). Without input to the contrary from agent 808, manager 506 may assume that the thermostat represented by thermostat node 628 is in an operational state, since the operational state may be the default state unless agent 808 indicates otherwise.
With reference to 9 Extensible state manager 506 is shown updating digital twin 608 based on information received from occupancy agent 904, according to an example embodiment, wherein the update causes digital twin 608 to include new states affecting occupancy in the Specify the schema of the digital twin. Calendar application 902 could be a system and/or software component running for a business and/or building. Calendar application 902 may be configured to schedule and track meetings in different rooms of the building represented by building node 620. The calendar application 902 could be an OUTLOOK calendar, a GOOGLE calendar, a MICROSOFT Teams calendar, and so on.

The occupancy agent 904 could be an agent that can be powered up and down to run against the calendar data of the calendar application 902 to derive and/or determine occupancy levels for different areas of the building, e.g. B. rooms, conference rooms, meeting rooms, floors, the building itself, etc. The occupancy levels may, in some embodiments, be predicted occupancy levels that are predicted based on upcoming sessions scheduled for different rooms. Agent 904 may be a twin function, twin functions are described with reference to U.S. Patent Application No. 17/354,436 filed June 22, 2021 and U.S. Patent Application No. 17/354,338 filed June 22, 2021. the entirety of which is incorporated herein by reference.

Manager 506 may receive predicted occupancy levels for the floor represented by floor node 616 and the floor represented by floor node 622 . The manager 506 may review a schema of the digital twin 608 and identify that an occupancy state for floors does not exist and that the floors have been predicted to have an occupancy level. The manager 506 may determine, based on the determinations made by the agent 904, that an occupancy status should be added to the schema for a floor class. Manager 506 may operate to add occupancy status as an attribute for a floor class, identify all floor entities of the floor class (e.g., floor node 616 and floor node 622), add nodes to represent occupancy level (e.g., floor occupancy level node 902 and occupancy level node 904), and relating nodes 902 and 904 to nodes 616 and 622, respectively, by one or more edges.

The occupancy levels added to the floor class digital twin schema can be consumed by other applications. For example, the calendar application 902 could use the occupancy level data in the digital twin 900 to determine which rooms, floors, buildings, etc. are available or booked. Extending state definitions within the digital twin 608 schema allows the digital twin 608 to adapt to new pieces of software running against the digital twin and allows for plug-and-play capabilities and enables It makes it easy to add and query states at runtime without having to update models, rebuild or redeploy any services, or perform any data migrations. For example, if a new application is deployed to run with the building data platform 100 and begins issuing a new state that is not currently included in the schema of the digital twin 608, the manager 608 can identify that the application's release is too should be added to the digital twin 608 and the schema of the digital twin 608 should be added.

With reference to 10 Shown is a process 1000 for updating the digital twin 608 based on information received from an agent, wherein the update causes the digital twin to include new states that indicate occupancy in the digital twin's schema, according to an exemplary embodiment. In some embodiments, manager 506 may be configured to perform process 1000 . In some embodiments, any computing device described herein may be configured to perform process 1000 .

In step 1002, the building information platform 100 is deployed to operate in a particular schema based on a digital twin. The building information platform 100 can be deployed to operate based on a digital twin, e.g. B. the digital twin 608 and/or any other digital twin and/or any other graph data structure described herein. For example, different pieces of software and/or systems (e.g., the applications 110) can run against the digital twin, e.g. B. Making device control decisions for the building subsystems 122 (e.g., controlling temperature, humidity, lighting, etc.), determining alarms, reducing energy consumption of the building subsystems 122, etc.

In step 1004, the building information platform 100 may execute an agent to operate based on digital twin 608 information. In some embodiments, in addition to or instead of the agent, another application may run against the digital twin 608, e.g. B. an error detection application, a calendar application, an occupancy prediction application, a power saving application, etc. In some embodiments, the agent (and / or the additional application) can run against data of the digital twin (and / or other information of the additional application) to new information determine.

In step 1006 , one or more states for an entity of an entity class in the digital twin schema 608 may be inferred by the manager 506 . The manager 506 may examine information determined by the agent and/or the application to determine that a new state should be added to an entity class for the digital twin schema 608 . For example, if the agent returns an error indication, occupancy indication, etc. for a particular entity that is not currently reflected in the digital twin schema, the manager 506 may determine to add a new state type to the schema for the entity class.

In step 1008, the manager 506 may add one or more states to entities of the entity class in the digital twin, thereby extending the schema of the digital twin 608 while deploying the building system to operate based on the digital twin. The manager 506 can add the states as nodes to the digital twin 608 with borders between the state nodes and the nodes representing entities. The manager 506 can search the digital twin 608 for any entity of the entity class and add the new state to any entity of the entity class. At step 1010, one or more operations may be performed based on the one or more new states of the digital twin 608. The one or more operations may consume the new states of the digital twin 608 and make operational decisions based on the new states. For example, the predicted occupancy conditions could be used to determine appropriate temperature and/or humidity control operations of the building subsystems 122 . Likewise, failure states of the building subsystems 122 could be used by a maintenance system to schedule maintenance for the building subsystems 122 .

Configuration of Example Embodiments

The structure and arrangement of the systems and methods shown in the various exemplary embodiments are for illustration only. Although only some embodiments have been described in detail in this disclosure, many modifications are possible (eg, variations in sizes, dimensions, structures, shapes, and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientation, etc.). For example, the position of elements can be reversed or otherwise varied, and the type or number of discrete elements or positions can be changed or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or rearranged according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the construction, operating conditions, and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems, and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a dedicated computer processor for an appropriate system built in for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine having a processor. For example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transmitted or made available to a machine over a network or other communications link (either hardwired, wireless, or a combination of hardwired and wireless), the machine properly considers the connection to be a machine-readable medium. Therefore, any such connection is properly termed a machine-readable medium. Combinations of the foregoing are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data that cause a general purpose computer, special purpose computer, or special purpose processing machine to perform a particular function or group of functions.

Although the figures show a specific order of method steps, the order of steps may differ from that illustrated. Two or more steps can also be carried out simultaneously or partially simultaneously. Such a variation depends on the chosen software and hardware systems and on the choice of the designer. All of these variations are within the scope of the disclosure. Likewise, software implementations could be made using standard programming techniques with rule-based logic and other logic to perform the various connection steps, processing steps, comparison steps, and decision steps.

In various implementations, the steps and operations described herein may be performed on one processor or in a combination of two or more processors. For example, in some implementations, the various operations could be performed at a central server or group of central servers configured to receive data from one or more devices (e.g., edge computing devices/controllers) and perform the operations. In some implementations, the operations may be performed by one or more local controllers or computing devices (e.g., edge devices), such as controllers associated with and/or located within a particular building or portion of a building. In some implementations, the operations may be performed by a combination of one or more central or external computing devices/servers and one or more local controllers/computing devices. All of these implementations are contemplated within the scope of the present disclosure. When the present disclosure relates to one or more computer-readable storage media and/or one or more controllers, unless otherwise noted, such computer-readable storage media and/or one or more controllers may further be one or more central servers, one or more local controllers or computing devices (e.g., edge devices), any combination thereof, or any other combination of storage media and/or controllers, regardless of the location of such devices.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• US 17136752B [0050]
• US 17136768 B [0050]
• US 17136785B [0050]
• US 17134661B [0052]
• US17134664 [0052]
• US 17134671B [0052]
• US 17134659B [0052]
• US 17134973B [0052]
• US 17134999 B [0052]
• US 17135023B [0052]
• US 17134691B [0052]
• US 17135056B [0052]
• US 17135009 B [0052]
• US62951891B [0060]

Non-patent Literature Cited

• Brick: Towards a Unified Metadata Schema For Buildings by Balaji [0047]

Claims (36)

A building system comprising one or more storage devices having 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 to derive a state for an entity of the digital twin, the digital twin comprising representations of a plurality of entities of the building and relationships between the plurality of entities; - update a schema of the digital twin by adding a state type of the state to an entity class of the schema; - based on the schema, add one or more data items representing the state to the digital twin, the one or more data items being related to an entity of the entity class by one or more relationships; and - perform one or more second operations based on the one or more nodes representing the state. building system claim 1 , wherein the plurality of entities include at least one of a person, point, location, or event, the schema defining entity classes for entity types of the plurality of entities. building system claim 1 or 2 , where the plurality of entities are instances of entity classes defined by the schema. Building system according to one of the Claims 1 until 3 , wherein the instructions cause the one or more processors to update the schema of the digital twin while the digital twin is being deployed without having to re-deploy the digital twin. Building system according to one of the Claims 1 until 4 , the schema defining a plurality of entity classes, the plurality of entity classes specifying properties, tags, and states for the plurality of entity classes. Building system according to one of the Claims 1 until 5 , wherein the instructions cause the one or more processors to perform the one or more first operations based on the digital twin of the building and external data collected from an external system, the state of the external data for the entity of the digital twin is derived. Building system according to one of the Claims 1 until 6 , wherein an application begins operating to perform the one or more initial operations based on the digital twin of the building to infer state for the entity after the digital twin is deployed and before the digital twin schema is updated, and preferably wherein the instructions are configured to: - receive an output from the application resulting from the one or more first operations, the output indicating the state; - search the schema of the digital twin to determine whether the schema includes the state type indicated by the output from the one or more first operations; and - update the schema of the digital twin by adding the state type of the state to the entity class of the schema in response to identifying that the schema does not include the state type. Building system according to one of the Claims 1 until 7 wherein the state defines a condition associated with the entity, the state preferably being at least one of a fault state of a piece of equipment of the building or an occupancy level of a room of the building. Building system according to one of the Claims 1 until 8th , wherein the digital twin includes a plurality of nodes and a plurality of edges between the plurality of nodes, the plurality of nodes representing the plurality of entities of the building and the plurality of edges indicating relationships between the plurality of entities; wherein the instructions cause the one or more processors to add, based on the schema, one or more nodes representing the state to the digital twin, the one or more nodes being defined by one or more relationships with the entity of the entity class in relationship. building system claim 9 , the instructions causing the one or more processors to: - receive an indication to add the state to the entity; - identify the entity class of the entity based on the schema; - update the schema of the digital twin by adding the state type to the entity class of the schema in response to identifying that a class of the entity is the entity class; and - based on the schema, adding the one or more nodes representing the state to the digital twin, the one or more nodes being related to a second node representing a second entity of the entity class, wherein the entity is different from the second entity. Building system according to one of the Claims 1 until 10 , further comprising: - the one or more processors configured to execute the instructions. Method comprising: - performing one or more first operations based on a digital twin of a building by one or more processing circuits to derive a state for an entity of the digital twin, the digital twin comprising representations of a plurality of entities of the building and relationships between the plurality of entities ; - updating a schema of the digital twin by adding a state type of the state to an entity class of the schema by one or more processing circuits; - adding, by one or more processing circuits based on the schema, to the digital twin one or more data items representing the state, the one or more data items being related to the entity of the entity class by one or more relationships; and - performing, by one or more processing circuits, one or more second operations based on the one or more data items representing the state. procedure after claim 12 wherein the plurality of entities include at least one of a person, point, location, or event, wherein the schema defines entity classes for entity types of the plurality of entities; wherein the plurality of entities are instances of entity classes defined by the schema. procedure after claim 12 or 13 , further comprising updating the schema of the digital twin by one or more processing circuits while the digital twin is being deployed without having to re-deploy the digital twin. Procedure according to one of Claims 12 until 14 , the schema defining a plurality of entity classes, the plurality of entity classes specifying properties, tags, and states for the plurality of entity classes. Procedure according to one of Claims 12 until 15 , further comprising performing, by one or more processing circuitry, the one or more first operations based on the digital twin of the building and external data collected from an external system, wherein the state of the external data for the entity of the digital twin is derived. Procedure according to one of Claims 12 until 16 , wherein the digital twin comprises a plurality of nodes and a plurality of edges between the plurality of nodes, the plurality of nodes representing the plurality of entities of the building and the plurality of edges indicating the relationships between the plurality of entities; the method further comprising adding, by one or more processing circuits based on the schema, one or more nodes representing the state to the digital twin, the one or more nodes having one or more relationships with the entity of the entity class related. procedure after Claim 17 , further comprising: - receiving, by one or more processing circuits, an indication to add the state to the entity; - identifying, by one or more processing circuits, the entity class of the entity based on the schema; - updating, by one or more processing circuits, the schema of the digital twin by adding the state type to the entity class of the schema in response to identifying that a class of the entity is the entity class; and - adding, by one or more processing circuits based on the schema, the one or more nodes representing the state to the digital twin, the one or more nodes being related to a second node representing a second entity of the entity class, where the entity is different from the second entity. A building system comprising one or more storage devices having 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 digital twin comprising representations of a plurality of entities of the building and relationships between the plurality of entities; - update a digital twin schema by adding a property or tag to an entity class of the schema; - based on the schema, add one or more data items representing the property or tag to the digital twin, the one or more data items being related to an entity of the entity class, the plurality of entities including the entity; and - perform one or more second operations based on the one or more data items representing the property or tag. building system claim 19 , wherein the plurality of entities includes at least one of a person, point, location, or event, the schema defining entity classes for entity types of the plurality of entities. building system claim 19 or 20 , wherein the plurality of entities are instances of entity classes defined by the schema and/or wherein the property or tag defines a characteristic of the entity. Building system according to one of the claims 19 until 21 , wherein the instructions cause the one or more processors to update the schema of the digital twin while the digital twin is being deployed without having to re-deploy the digital twin. Building system according to one of the claims 19 until 22 , wherein the schema defines a plurality of entity classes, wherein the plurality of entity classes specify properties, tags and states for the plurality of entity classes, and/or wherein the instructions cause the one or more processors to: - receive user input from a user device, where the user input defines the property or tag to be added to the schema's entity class; and - in response to receiving the user input, adding the schema of the digital twin by adding the property or tag to the entity class of the schema based on the user input. Building system according to one of the claims 19 until 23 , wherein the digital twin includes a plurality of nodes and a plurality of edges between the plurality of nodes, the plurality of nodes representing the plurality of entities of the building and the plurality of edges indicating relationships between the plurality of entities; wherein the instructions cause the one or more processors to add, based on the schema, one or more nodes representing the property or tag to the digital twin, the one or more nodes being related to a node that represents the entity of the entity class by one or more borders. building system Claim 24 , wherein the instructions cause the one or more processors to: - identify a plurality of entity nodes specifying entities in the entity class; and - based on the schema, adding the one or more nodes representing the property or tag to the digital twin for each of the plurality of entity nodes, the one or more nodes being related to the plurality of entity nodes . building system Claim 24 or 25 , wherein the instructions cause the one or more processors to: - receive an indication to add the property or tag to a first entity; - identify the entity class of the first entity based on the schema; - update the schema of the digital twin by adding the property or tag to the entity class of the schema in response to identifying that a class of the first entity is the entity class; and - add the one or more nodes representing the property or tag to the digital twin based on the schema, the one or more nodes being related to the node representing the entity of the entity class, wherein the entity is a second entity that is different from the first entity. Building system according to one of the claims 24 until 26 , wherein the instructions cause the one or more processors to: - identify an update at one or more particular nodes or one or more particular edges of the digital twin, the update indicating changes affecting the entity; - determine that the update indicates a change to one or more characteristics of the entity; and - update the schema of the digital twin by adding the property or tag to the entity class of the schema in response to determining that the update reflects the change to the one or more characteristics of the entity. Building system according to one of the claims 19 until 27 , further comprising: - the one or more processors configured to execute the instructions. Method comprising: - performing, by one or more processing circuits, one or more first operations based on a digital twin of a building, the digital twin comprising representations of a plurality of entities of the building and relationships between the plurality of entities; - updating, by the one or more processing circuits, a schema of the digital twin by adding a property or tag to an entity class of the schema; - adding, by the one or more processing circuits based on the schema, one or more data items representing the property or tag to the digital twin, the one or more data items being related to an entity of the entity class, wherein the plurality of entities including the entity; and - performing, by the one or more processing circuits, one or more second operations based on the one or more data items representing the property or tag. procedure after claim 29 , wherein the plurality of entities include at least one of a person, point, location, or event, the schema defining entity classes for entity types of the plurality of entities. procedure after claim 29 or 30 , where the property or tag defines a characteristic of the entity. Procedure according to one of claims 29 until 31 wherein the one or more processing circuits update the schema of the digital twin while the digital twin is being deployed without having to re-deploy the digital twin. Procedure according to one of claims 29 until 32 , the schema defining a plurality of entity classes, the plurality of entity classes specifying properties, tags, and states for the plurality of entity classes. Procedure according to one of claims 29 until 33 , wherein the digital twin includes a plurality of nodes and a plurality of edges between the plurality of nodes, the plurality of nodes representing the plurality of entities of the building and the plurality of edges indicating relationships between the plurality of entities; the method further comprising adding, by the one or more processing circuits based on the schema, one or more nodes representing the property or tag to the digital twin, the one or more nodes having a node in relationship that represents the entity of the entity class by one or more borders. procedure after Claim 34 , further comprising: - identifying, by the one or more processing circuits, entity nodes specifying entities in the entity class, and - adding, by the one or more processing circuits based on the schema, the one or more nodes specifying the represent a property or tag for each of the plurality of entity nodes to the digital twin, the one or more nodes being related to the plurality of entity nodes. procedure after Claim 34 or 35 , further comprising: - receiving, by the one or more processing circuits, an indication to add the property or tag to a first entity; - identifying, by the one or more processing circuits, the entity class of the first entity based on the schema; - updating, by the one or more processing circuits, the schema of the digital twin by adding the property or tag to the entity class of the schema in response to identifying that a class of the first entity is the entity class; and - adding, by the one or more processing circuits based on the schema, the one or more nodes representing the property or tag to the digital twin, the one or more nodes being related to the node, representing the entity of the entity class, where the entity is a second entity distinct from the first entity.

Images