Building Data Platform
By generating rich events and constructing building graphs through a cloud-based system, the integration challenge of existing building system control methods is solved, enabling dynamic and scalable building management and control, and improving the system's agility and flexibility.
Patent Information
- Application Number
- CN202080097068.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-10-26
- Filing Date
- 2020-12-28
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-12-28
AI Technical Summary
Existing building system control methods cannot achieve dynamic, scalable, and adjustable overall management, and discrete, predefined control systems cannot effectively integrate the various subsystems of a building.
By using cloud-based systems and leveraging event enrichment and graphics projection technologies, rich events can be generated and building graphics can be constructed, enabling dynamic management and control of building systems.
It enables dynamic, scalable, and adjustable overall management of building systems, improving system agility and flexibility, and supporting energy optimization, predictive maintenance, and remote operation.
Smart Images

Figure CN115210700B_ABST
Abstract
Description
[0001] Cross-reference to related patent applications
[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 955,856 filed on December 31, 2019, U.S. Provisional Patent Application No. 63 / 005,841 filed on April 6, 2020, and U.S. Provisional Patent Application No. 63 / 105,754 filed on October 26, 2020, the entire contents of each of which are incorporated herein by reference. Background Art
[0003] The present disclosure generally relates to management of building systems of a building. More specifically, the present disclosure relates to control of building systems through a cloud-based system. A building may contain various types of building subsystems, such as heating, ventilation, and air conditioning (HVAC) systems, security systems, fire response systems, etc. Discrete predefined control systems may operate each subsystem individually without knowledge of the building. However, discrete predefined control systems may not allow for a dynamic, scalable, and adjustable solution that can manage the building as a whole. Summary of the invention
[0004] Event enrichment through contextual information
[0005] One embodiment of the present disclosure is a building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive an event from an event source, the event indicating a data value associated with a piece of building equipment occurring at a specific time. The instructions cause the one or more processors to: identify context data of a database, the context data providing a context description of the event; generate an enriched event by enriching the event with the context data, the enriched event comprising the data value, the specific time, and the context data; and provide the enriched event to a consuming application configured to operate based on the enriched event.
[0006] In some embodiments, the instructions cause one or more processors to: retrieve one or more schemas from an architecture database, the one or more schemas indicating available architecture formats for an event; determine whether the architecture in which the event is formatted matches the one or more schemas; generate an enriched event in response to determining that the architecture in which the event is formatted matches the one or more schemas; and perform at least one of the following: in response to determining that the architecture in which the event is formatted does not match the one or more schemas, add the event to a dead letter storage area, or in response to determining that the architecture in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode for discovering new architectures, add the architecture in which the event is formatted to the architecture database.
[0007] In some embodiments, the instructions cause the one or more processors to add the enriched event to a topic subscribed by the consuming application.
[0008] In some embodiments, the instructions cause the one or more processors to maintain the enriched events in an event database.
[0009] In some embodiments, the instructions cause one or more processors to identify context data based on one or more enrichment rules associated with a consuming application. In some embodiments, the instructions cause one or more processors to identify second context data of the database based on one or more second enrichment rules associated with a second consuming application; generate a second enriched event by enriching the event with the second context data, the data value, and the specific time; and provide the second enriched event to the second consuming application.
[0010] In some embodiments, the event is received from a piece of building equipment of a building. In some embodiments, the instructions cause the one or more processors to identify the contextual data by searching for a graphical projection containing a contextual description of the piece of building equipment.
[0011] In some embodiments, the graph projection includes nodes and edges. In some embodiments, the nodes represent entities of a building and the edges represent relationships between the entities of the building. In some embodiments, the nodes include a node representing a piece of building equipment. In some embodiments, the instructions cause the one or more processors to identify contextual data by identifying one or more nodes based on one or more of the edges between the node representing the piece of building equipment and one or more of the nodes related to the node representing the piece of building equipment.
[0012] In some embodiments, the contextual data includes one or more capabilities of a piece of construction equipment.
[0013] In some embodiments, the context description includes at least one of: a location where a piece of construction equipment is located, another piece of construction equipment related to the piece of construction equipment, a point of a piece of construction equipment, and a person associated with a piece of construction equipment.
[0014] In some embodiments, the location is at least one of a building in which a piece of construction equipment is located or a space in which a piece of construction equipment is located.
[0015] Another embodiment of the present disclosure is a method, the method comprising receiving, by processing circuitry, an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a specific time. The method further comprises: identifying, by the processing circuitry, context data of a database, the context data providing a context description of the event; generating, by the processing circuitry, an enriched event by enriching the event with the context data, the enriched event comprising the data value, the specific time, and the context data; and providing, by the processing circuitry, the enriched event to a consuming application configured to operate based on the enriched event.
[0016] In some embodiments, the method includes retrieving, by processing circuitry, one or more schemas from a schema database, the one or more schemas indicating available schema formats for the event; determining, by processing circuitry, whether a schema in which the event is formatted matches the one or more schemas; and generating, by processing circuitry, an enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas. In some embodiments, the method includes performing, by processing circuitry, at least one of: adding the event to a dead letter storage area in response to determining that the schema in which the event is formatted does not match the one or more schemas, or adding the schema in which the event is formatted to the schema database in response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas.
[0017] In some embodiments, the method includes adding, by the processing circuitry, the enriched event to a topic subscribed by a consuming application.
[0018] In some embodiments, the method includes maintaining, by the processing circuit, the enriched events in an event database.
[0019] In some embodiments, the method includes identifying, by the processing circuit, the context data based on one or more enrichment rules associated with the consuming application. In some embodiments, the method further includes: identifying, by the processing circuit, second context data of the database based on one or more second enrichment rules associated with the second consuming application; generating, by the processing circuit, a second enriched event by enriching the event with the second context data, the data value, and the specific time; and providing, by the processing circuit, the second enriched event to the second consuming application.
[0020] In some embodiments, the method further includes identifying, by the processing circuit, contextual data by searching for a graphical projection that includes a contextual description of the piece of building equipment.
[0021] In some embodiments, the graph projection includes nodes and edges. In some embodiments, the nodes represent entities of a building and the edges represent relationships between the entities of the building. In some embodiments, the nodes include nodes representing a piece of building equipment. In some embodiments, the method includes identifying, by processing circuitry, contextual data including identifying one or more nodes based on one or more of the edges between the node representing the piece of building equipment and one or more of the nodes related to the node representing the piece of building equipment.
[0022] In some embodiments, the contextual data includes one or more capabilities of a piece of construction equipment.
[0023] In some embodiments, the context description includes at least one of: a location where a piece of construction equipment is located, another piece of construction equipment related to the piece of construction equipment, a point of a piece of construction equipment, and a person associated with a piece of construction equipment.
[0024] Another embodiment of the present disclosure is a building system, the building system including one or more memory devices having instructions thereon and one or more processors, the processors being configured to: execute the instructions, the instructions causing the one or more processors to receive an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a specific time; identify context data of a database, the context data providing a context description of the event; generate an enriched event by enriching the event with the context data, the enriched event including the data value, the specific time, and the context data; and provide the enriched event to a consuming application configured to operate based on the enriched event.
[0025] Building Graphics Change Feed
[0026] One embodiment of the present disclosure is a building system for a building, the building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive modifications to a graph, the graph comprising nodes and edges between the nodes, the nodes representing entities of the building and the edges representing relationships between the entities of the building. The instructions cause the one or more processors to generate change feed events, the change feed events recording the modifications to the graph, and to add the change feed events to a change feed, the change feed comprising change feed events representing modifications to the graph at different times.
[0027] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0028] In some embodiments, the instructions cause one or more processors to construct a graph at a time point including a first time and a second time by performing the following operations: selecting a first set of change feed events that occur up to the first time; generating a graph at the first time based on the first set of change feed events; selecting a second set of change feed events that occur up to the second time; and generating a graph at the second time based on the second set of change feed events.
[0029] In some embodiments, the modification is at least one of: adding a new node to the nodes of the graph; adding a new edge to the edges of the graph; deleting an existing node in the nodes of the graph; deleting an existing edge in the edges of the graph; modifying an existing node in the nodes of the graph; or modifying an existing edge in the edges of the graph.
[0030] In some embodiments, the instructions cause the one or more processors to communicate a change feed event of the change feed to one or more consuming applications.
[0031] In some embodiments, the instructions cause one or more processors to add a change feed event to a change feed topic, wherein one or more consuming applications subscribe to the change feed topic and receive the change feed event in response to adding the change feed event to the change feed topic.
[0032] In some embodiments, one or more consuming applications update a graph stored by the one or more consuming applications based on a change feed event.
[0033] Another embodiment of the present disclosure is a method, the method comprising receiving, by processing circuitry, modifications to a graph, the graph comprising nodes and edges between the nodes, the nodes representing entities of a building and the edges representing relationships between the entities of the building. The method comprises generating, by the processing circuitry, change feed events, the change feed events recording the modifications to the graph, and adding, by the processing circuitry, the change feed events to a change feed, the change feed comprising change feed events representing the modifications to the graph at different times.
[0034] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0035] In some embodiments, the method includes: constructing, by a processing circuit, a graph at a time point including a first time and a second time by the following operations: selecting a first set of change feed events occurring up to the first time; generating a graph at the first time based on the first set of change feed events; selecting a second set of change feed events occurring up to the second time; and generating a graph at the second time based on the second set of change feed events.
[0036] In some embodiments, the modification is at least one of: adding a new node to the nodes of the graph; adding a new edge to the edges of the graph; deleting an existing node in the nodes of the graph; deleting an existing edge in the edges of the graph; modifying an existing node in the nodes of the graph; or modifying an existing edge in the edges of the graph.
[0037] In some embodiments, the method further includes communicating, by the processing circuitry, a change feed event of the change feed to one or more consuming applications.
[0038] In some embodiments, the method further includes adding, by the processing circuit, the change feed event to the change feed topic, wherein one or more consuming applications subscribe to the change feed topic and receive the change feed event in response to adding the change feed event to the change feed topic.
[0039] In some embodiments, one or more consuming applications update a graph stored by the one or more consuming applications based on a change feed event.
[0040] Another embodiment of the present disclosure is one or more memory devices having instructions thereon and one or more processors configured to execute the instructions, the instructions causing the one or more processors to receive modifications to a graph, the graph comprising nodes and edges between the nodes, the nodes representing entities of a building and the edges representing relationships between the entities of the building. The instructions causing the one or more processors to generate change feed events, the change feed events recording the modifications to the graph, and adding the change feed events to a change feed, the change feed comprising change feed events representing modifications to the graph at different times.
[0041] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0042] In some embodiments, the instructions cause one or more processors to construct a graph at a time point including a first time and a second time by performing the following operations: selecting a first set of change feed events that occur up to the first time; generating a graph at the first time based on the first set of change feed events; selecting a second set of change feed events that occur up to the second time; and generating a graph at the second time based on the second set of change feed events.
[0043] In some embodiments, the modification is at least one of: adding a new node to the nodes of the graph; adding a new edge to the edges of the graph; deleting an existing node in the nodes of the graph; deleting an existing edge in the edges of the graph; modifying an existing node in the nodes of the graph; or modifying an existing edge in the edges of the graph.
[0044] In some embodiments, the instructions cause the one or more processors to communicate a change feed event of the change feed to one or more consuming applications.
[0045] In some embodiments, the instructions cause one or more processors to add a change feed event to a change feed topic, wherein one or more consuming applications subscribe to the change feed topic and receive the change feed event in response to adding the change feed event to the change feed topic.
[0046] Building graphics-based capabilities
[0047] One embodiment of the present disclosure is a building system for a building, the building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to identify capabilities of entities in a building graph, the building graph comprising nodes and edges, the nodes representing entities of the building comprising entities and capabilities, the edges representing relationships between entities of the building and capabilities, wherein a first node of the nodes represents an entity, and a second node of the nodes related to the first node by one or more of the edges represents a capability. The instructions cause the one or more processors to receive a command to perform an operation associated with the entity, the operation being associated with the capability of the entity, and provide the command to perform the operation associated with the entity to an operating system.
[0048] In some embodiments, the instructions cause one or more processors to identify a capability of an entity by: identifying a first node among the nodes of a building graph that represents the entity; and identifying at least one of one or more nodes or one or more edges between the first node and a second node that represents the capability of the entity.
[0049] In some embodiments, the entity is a piece of building equipment of a building. In some embodiments, the capability is a control operation that the piece of building equipment is configured to perform.
[0050] In some embodiments, the entity is a user of the building. In some embodiments, a capability is an action associated with a user that the system is configured to perform.
[0051] In some embodiments, the instructions cause the one or more processors to receive a command to perform an operation associated with an entity from a requesting system. In some embodiments, the instructions cause the one or more processors to identify whether the requesting system has a policy to issue a command to perform an operation based on a building graphic, wherein the building graphic indicates a policy to issue a command. In some embodiments, the instructions cause the one or more processors to provide a command to perform an operation associated with an entity to an operating system in response to identifying that the requesting system has a policy to issue a command.
[0052] In some embodiments, the instructions cause one or more processors to identify whether the requesting system has a policy for issuing a command to perform an operation based on the building graph by: identifying a third node in the nodes that represents the requesting system; and identifying one or more specific edges in the edges between the third node and a fourth node in the nodes that represents a policy for issuing a command.
[0053] In some embodiments, the instructions cause one or more processors to determine that the operating system is a piece of building equipment for a building; identify a device hub based on a building graphic, the device hub being configured to facilitate message passing between the building system and the piece of building equipment, wherein the node includes a node representing the device hub; and send a command to the piece of building equipment through the device hub.
[0054] In some embodiments, the entity is a piece of building equipment. In some embodiments, the instructions cause the one or more processors to determine that the operating system is an external system separate from the building system; identify a connection agent configured to facilitate a connection between the building system and the external system, wherein the node includes nodes representing the connection agent and the external system; and send a command to the piece of building equipment through the connection agent.
[0055] Another embodiment of the present disclosure is a method, the method comprising identifying, by processing circuitry, capabilities of entities in a building graph of a building, the building graph comprising nodes and edges, the nodes representing entities of the building comprising the entities and the capabilities, the edges representing relationships between the entities of the building and the capabilities, wherein a first node of the nodes represents the entity and a second node of the nodes that is related to the first node by one or more of the edges represents the capabilities. The method comprises receiving, by the processing circuitry, a command to perform an operation associated with the entity, the operation being associated with the capabilities of the entity; and providing, by the processing circuitry, the command to perform the operation associated with the entity to an operating system.
[0056] In some embodiments, identifying, by the processing circuit, a capability of an entity includes identifying a first node representing the entity among nodes of a building graph; and identifying at least one of one or more nodes or one or more edges between the first node and a second node representing the capability of the entity.
[0057] In some embodiments, the entity is a piece of building equipment of a building. In some embodiments, the capability is a control operation that the piece of building equipment is configured to perform.
[0058] In some embodiments, the entity is a user of the building. In some embodiments, a capability is an action associated with a user that the system is configured to perform.
[0059] In some embodiments, the method includes receiving, by the processing circuit, a command to perform an operation associated with the entity, which includes receiving the command from a requesting system. In some embodiments, the method includes identifying, by the processing circuit, whether the requesting system has a policy to issue a command to perform the operation based on a building graphic, wherein the building graphic indicates the policy to issue the command. In some embodiments, the method includes providing, by the processing circuit, the command to perform the operation associated with the entity to an operating system in response to identifying that the requesting system has a policy to issue the command.
[0060] In some embodiments, the method includes identifying, by a processing circuit, whether a requesting system has a policy for issuing a command to perform an operation based on a building graph by: identifying a third node in the nodes that represents the requesting system; and identifying one or more specific edges in the edges between the third node and a fourth node in the nodes that represents a policy for issuing a command.
[0061] In some embodiments, the method includes determining, by a processing circuit, that the operating system is a piece of building equipment of a building; identifying, by the processing circuit, a device hub based on a building graphic, the device hub being configured to facilitate message passing between the processing circuit and the piece of building equipment, wherein the node includes a node representing the device hub; and sending, by the processing circuit, a command through the device hub to the piece of building equipment.
[0062] In some embodiments, the entity is a piece of building equipment. In some embodiments, the method includes determining, by the processing circuit, that the operating system is an external system separate from the building system; identifying, by the processing circuit, a connection agent configured to facilitate a connection between the building system and the external system, wherein the node includes nodes representing the connection agent and the external system; and sending, by the processing circuit, a command to the piece of building equipment through the connection agent.
[0063] One embodiment of the present disclosure is one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to identify capabilities of entities in a building graph of a building, the building graph comprising nodes and edges, the nodes representing entities of the building comprising entities and capabilities, the edges representing relationships between entities of the building and capabilities, wherein a first node of the nodes represents an entity, and a second node of the nodes related to the first node by one or more of the edges represents a capability. The instructions cause the one or more processors to receive a command to perform an operation associated with the entity, the operation associated with the capability of the entity, and provide the command to perform the operation associated with the entity to an operating system.
[0064] In some embodiments, the instructions cause one or more processors to identify a capability of an entity by: identifying a first node among the nodes of a building graph that represents the entity; and identifying at least one of one or more nodes or one or more edges between the first node and a second node that represents the capability of the entity.
[0065] In some embodiments, the entity is a piece of building equipment of a building. In some embodiments, the capability is a control operation that the piece of building equipment is configured to perform.
[0066] In some embodiments, the entity is a user of the building. In some embodiments, a capability is an action associated with a user that the system is configured to perform.
[0067] Building graphics based communication actions
[0068] One embodiment of the present disclosure is a building system for a building, the building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive a command to perform an action of an entity. The instructions cause the one or more processors to identify a service configured to perform an action based on a building graph, the building graph comprising nodes and edges, wherein the nodes represent entities, services, and one or more other services of the building, wherein the edges represent relationships between entities and communication actions of the service with one or more other services, and causing the service to perform the action by causing the service to perform one or more communication actions with the one or more other services indicated by the building graph.
[0069] In some embodiments, the communication action is an application programming interface (API) call to one or more other services.
[0070] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0071] In some embodiments, a first node in the nodes represents a service, and a second node in the nodes represents a second service in one or more other services. In some embodiments, an edge in the edges relates the first node to the second node and indicates a communication action that the service can make to the second service.
[0072] In some embodiments, the service is a connection agent configured to coordinate a connection between a building system and an external system separate from the building system. In some embodiments, the action is an operation performed by the external system. In some embodiments, one or more communication actions are API calls that the connection agent makes with one or more other services to cause the external system to perform the operation.
[0073] In some embodiments, the service is a device hub configured to handle messages between a building system and a piece of building equipment. In some embodiments, an action is an operation performed by a piece of building equipment. In some embodiments, one or more communication actions are API calls that a device hub makes with one or more other services to cause a piece of building equipment to perform an operation.
[0074] In some embodiments, the instructions cause one or more processors to identify capabilities of an entity in a building graphic indicating that the entity can perform actions and cause a service to perform actions based on one or more communication actions indicated by the building graphic in response to identifying the capabilities of the entity.
[0075] In some embodiments, the instructions cause the one or more processors to receive a command to perform an action from a requesting system. In some embodiments, the instructions cause the one or more processors to identify whether the requesting system has a policy to issue a command to perform an action based on a building graphic, wherein the building graphic indicates the policy to issue the command. In some embodiments, the instructions cause the one or more processors to cause the service to perform the action in response to identifying the policy to issue the command.
[0076] In some embodiments, the instructions cause one or more processors to identify whether a requesting system from which a building system receives a request to execute a command has a strategy for issuing commands by: identifying a first node in the node that represents the requesting system in a building graph; and identifying one or more edges between the first node and a second node in the node that represents the strategy for issuing commands.
[0077] Another embodiment of the present disclosure is a method, the method comprising receiving, by a processing circuit, a command to execute an action of an entity; identifying, by the processing circuit, a service configured to execute the action based on a building graph, the building graph comprising nodes and edges, wherein the nodes represent entities, services, and one or more other services of the building, wherein the edges represent relationships between entities and communication actions of the service with one or more other services; and causing the service to execute the action by causing the service to execute one or more communication actions with one or more other services indicated by the building graph.
[0078] In some embodiments, the communication action is an application programming interface (API) call to one or more other services.
[0079] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0080] In some embodiments, a first node in the nodes represents a service, and a second node in the nodes represents a second service in one or more other services. In some embodiments, an edge in the edges relates the first node to the second node and indicates a communication action that the service can make to the second service.
[0081] In some embodiments, the service is a connection agent configured to coordinate a connection between a building system and an external system separate from the building system. In some embodiments, the action is an operation performed by the external system. In some embodiments, one or more communication actions are API calls that the connection agent makes with one or more other services to cause the external system to perform the operation.
[0082] In some embodiments, the service is a device hub configured to handle messages between a building system and a piece of building equipment. In some embodiments, an action is an operation performed by a piece of building equipment. In some embodiments, one or more communication actions are API calls that a device hub makes with one or more other services to cause a piece of building equipment to perform an operation.
[0083] In some embodiments, the method includes: identifying, by processing circuitry, a capability of an entity in a building graphic, the capability indicating that the entity can perform an action; and causing, by the processing circuitry, in response to identifying the capability of the entity, a service to perform an action based on one or more communication actions indicated by the building graphic.
[0084] In some embodiments, the method includes receiving, by the processing circuit, a command to perform an action from a requesting system. In some embodiments, the method includes identifying, by the processing circuit, whether the requesting system has a policy to issue a command to perform an action based on a building graphic, wherein the building graphic indicates the policy to issue the command. In some embodiments, the method includes causing, by the processing circuit, the service to perform the action in response to identifying the policy to issue the command.
[0085] In some embodiments, the method includes identifying, by a processing circuit, whether a requesting system from which a building system receives a request to execute a command has a strategy for issuing commands, which includes identifying a first node in a node that represents the requesting system in a building graph; and identifying one or more edges between the first node and a second node in the node that represents the strategy for issuing commands.
[0086] Another embodiment of the present disclosure is one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive a command to perform an action of an entity. The instructions cause the one or more processors to identify a service configured to perform an action based on a building graph, the building graph comprising nodes and edges, wherein the nodes represent entities, services, and one or more other services of the building, wherein the edges represent relationships between the entities and communication actions of the service with the one or more other services, and cause the service to perform the action by causing the service to perform one or more communication actions with the one or more other services indicated by the building graph.
[0087] In some embodiments, the communication action is an application programming interface (API) call to one or more other services.
[0088] Building graphics-based strategies
[0089] One embodiment of the present disclosure is a building system for a building, the building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive a request from the system to access a portion of a building graph of the building, the building graph comprising nodes and edges, the nodes representing entities of the building and the edges representing relationships between the entities of the building. The instructions cause the one or more processors to determine whether the system can access the portion of the building graph based on a policy indicated by the nodes and edges of the building graph, and in response to determining that the system can access the portion of the building graph, provide the portion of the building graph to the system.
[0090] In some embodiments, the building graph includes a first node representing a policy. In some embodiments, the building graph includes a second node indicating a read policy for reading events associated with the first node via a first of the edges. In some embodiments, the building graph includes a third node indicating a command policy for sending commands associated with the first node via a second of the edges.
[0091] In some embodiments, the instructions cause one or more processors to determine whether a system can access a portion of a building graph based on a policy by: identifying a first node among the nodes that represents the system; and identifying an edge among the edges between the first node and a second node that represents a policy for accessing the portion of the building graph.
[0092] In some embodiments, the policy for accessing a portion of a building graph is an access policy for accessing events associated with a particular entity. In some embodiments, the node comprises a first node representing the policy and a second node representing the particular entity. In some embodiments, an edge in an edge links the first node to the second node.
[0093] In some embodiments, the strategy for accessing events associated with a particular entity is a specific access strategy for accessing other events of other entities, and the other entities are related to the particular entity. In some embodiments, the node includes other nodes representing other entities. In some embodiments, the edge includes one or more edges that relate other nodes to a second node representing the particular entity.
[0094] In some embodiments, the instructions cause one or more processors to receive a command to execute an action of an entity from a requesting system, and to determine whether the system has a command strategy for issuing a command to execute the action based on a building graphic identification system by: identifying a first node in the node that represents the requesting system; and identifying one or more edges between the first node and a second node in the node that represents the command strategy for issuing the command.
[0095] In some embodiments, the instructions cause the one or more processors to identify capabilities of entities in a building graphic and, in response to identifying the capabilities, provide commands to an operating system to perform actions associated with the entities.
[0096] In some embodiments, the instructions cause one or more processors to identify a capability of an entity by: identifying a node in a building graph that represents the entity; and identifying at least one of one or more specific edges between the one or more nodes or a third node that represents the capability of the entity.
[0097] In some embodiments, the entity is a piece of construction equipment of a building. In some embodiments, the capability is an operation that the piece of construction equipment is configured to perform.
[0098] Another embodiment of the present disclosure is a method that includes receiving, by processing circuitry, a request from a system to access a portion of a building graph of a building, the building graph including nodes and edges, the nodes representing entities of the building and the edges representing relationships between the entities of the building. The method includes determining, by the processing circuitry, whether the system can access the portion of the building graph based on policies indicated by the nodes and edges of the building graph, and providing, by the processing circuitry, the portion of the building graph to the system in response to determining that the system can access the portion of the building graph.
[0099] In some embodiments, the building graph includes a first node representing a policy. In some embodiments, the building graph includes a second node indicating a read policy for reading events associated with the first node via a first of the edges. In some embodiments, the building graph includes a third node indicating a command policy for sending commands associated with the first node via a second of the edges.
[0100] In some embodiments, determining by processing circuitry whether a system can access a portion of a building graph based on a policy includes identifying a first node among nodes representing the system; and identifying an edge among edges between the first node and a second node representing a policy for accessing the portion of the building graph.
[0101] In some embodiments, the policy for accessing a portion of a building graph is an access policy for accessing events associated with a particular entity. In some embodiments, the node comprises a first node representing the policy and a second node representing the particular entity. In some embodiments, an edge in an edge links the first node to the second node.
[0102] In some embodiments, the strategy for accessing events associated with a particular entity is a specific access strategy for accessing other events of other entities, and the other entities are related to the particular entity. In some embodiments, the node includes other nodes representing other entities. In some embodiments, the edge includes one or more edges that relate other nodes to a second node representing the particular entity.
[0103] In some embodiments, the method includes: receiving, by a processing circuit, a command to execute an action of an entity from a requesting system; and determining, by the processing circuit based on a building graphic identification system, whether the system has a command strategy for issuing a command to execute the action by: identifying a first node in the node that represents the requesting system; and identifying one or more edges between the first node and a second node in the node that represents the command strategy for issuing the command.
[0104] In some embodiments, the method includes: identifying, by the processing circuit, a capability of an entity in a building graphic; and providing, by the processing circuit, a command to an operating system to perform an action associated with the entity in response to identifying the capability.
[0105] In some embodiments, the method includes identifying, by processing circuitry, a capability of an entity by: identifying a node in a building graph that represents the entity; and identifying at least one of one or more nodes or one or more edges between the node and a third node that represents the capability of the entity.
[0106] In some embodiments, the entity is a piece of construction equipment of a building. In some embodiments, the capability is an operation that the piece of construction equipment is configured to perform.
[0107] One embodiment of the present disclosure is one or more memory devices having instructions thereon, which instructions, when executed by one or more processors, cause the one or more processors to: receive a request from a system to access a portion of a building graph of a building, the building graph comprising nodes and edges, the nodes representing entities of the building, and the edges representing relationships between the entities of the building; determine whether the system can access the portion of the building graph based on policies indicated by the nodes and edges of the building graph; and provide the portion of the building graph to the system in response to determining that the system can access the portion of the building graph.
[0108] In some embodiments, the building graph includes a first node representing a policy. In some embodiments, the building graph includes a second node indicating a read policy for reading events associated with the first node via a first of the edges. In some embodiments, the building graph includes a third node indicating a command policy for sending commands associated with the first node via a second of the edges.
[0109] Building graphic projection
[0110] One embodiment of the present disclosure is a building system for a building, the building system comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to retrieve projection rules for generating a building graph projection. The instructions cause the one or more processors to retrieve entities representing elements of the building and relationships between entities representing relationships between entities; construct a building graph projection including nodes and edges based on the entities, relationships, and projection rules; and perform one or more operations based on the building graph projection.
[0111] In some embodiments, the instructions cause one or more processors to construct a building graph projection by generating a node in nodes for each entity; generating an edge in edges for each relationship in relationships; and connecting an edge from a first node in the nodes to a second node in the nodes to illustrate a particular relationship in the relationship between a first entity in the entities and a second entity in the entities.
[0112] In some embodiments, the projection rules indicate permissions of the subscriber, wherein the permissions identify a set of entities and a set of relationships. In some embodiments, the instructions cause the one or more processors to construct a building graphic projection based on the set of entities and the set of relationships.
[0113] In some embodiments, the projection rules indicate an ontology indicating allowed relationships between types of entities. In some embodiments, the instructions cause the one or more processors to construct a building graphic projection based on the types of entities and the allowed relationships between the types of entities.
[0114] In some embodiments, the instructions cause the one or more processors to retrieve, for a subscriber, projection rules for generating a graphic projection of the building from graphic projection rules stored in a database, wherein the graphic projection rules are associated with the subscriber.
[0115] In some embodiments, the instructions cause one or more processors to retrieve a second projection rule for a second subscriber among the subscribers; construct a second building graph projection comprising a second plurality of nodes and a second plurality of edges based on at least some entities, at least some relationships, and the second projection rule; and store the building graph projection and the second building graph projection in a graph projection database.
[0116] In some embodiments, the instructions cause one or more processors to: receive a modification to a building graphic projection; generate a change feed event that records the modification to the building graphic projection; and add the change feed event to a change feed that includes change feed events representing modifications to the building graphic projection at different times.
[0117] In some embodiments, the modification is at least one of: adding a new node to the nodes of the building graph projection; adding a new edge to the edges of the building graph projection; deleting an existing node in the nodes of the building graph projection; deleting an existing edge in the edges of the building graph projection; modifying an existing node in the nodes of the building graph projection; or modifying an existing edge in the edges of the building graph projection.
[0118] In some embodiments, the instructions cause one or more processors to: receive an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a specific time; identify context data from a database, the context data providing a context description of the event; generate an enriched event by enriching the event with the context data, the enriched event including the data value, the specific time, and the context data; and provide the enriched event to a consuming application configured to operate based on the enriched event.
[0119] In some embodiments, the instructions cause the one or more processors to identify the contextual data by searching for a building graphic projection that contains a contextual description of the piece of building equipment.
[0120] In some embodiments, the nodes represent entities and the edges represent relationships between the entities. In some embodiments, the nodes include a node representing a piece of construction equipment. In some embodiments, the instructions cause the one or more processors to identify contextual data by identifying one or more nodes based on one or more of the edges between the node representing the piece of construction equipment and one or more of the nodes related to the node representing the piece of construction equipment.
[0121] Another embodiment of the present disclosure is a method, the method comprising retrieving, by a processing circuit, a projection rule for generating a building graph projection. The method comprises retrieving, by a processing circuit, entities representing elements of a building and relationships between entities representing relationships between entities; constructing, by the processing circuit, a building graph projection including nodes and edges based on the entities, the relationships, and the projection rule; and performing, by the processing circuit, one or more operations based on the building graph projection.
[0122] In some embodiments, the method includes generating, by processing circuitry, a node in the nodes for each entity; generating, by processing circuitry, an edge in the edges for each of the relationships; and connecting, by processing circuitry, an edge from a first node in the nodes to a second node in the nodes to illustrate a particular relationship in the relationships between a first entity in the entities and a second entity in the entities.
[0123] In some embodiments, the projection rules indicate permissions of the subscriber, wherein the permissions identify a set of entities and a set of relationships. In some embodiments, the method further includes constructing, by the processing circuit, a building graphic projection based on the set of entities and the set of relationships.
[0124] In some embodiments, the projection rules indicate an ontology indicating allowed relationships between types of entities. In some embodiments, the method further comprises constructing, by the processing circuit, the building graphic projection based on the types of entities and the allowed relationships between the types of entities.
[0125] In some embodiments, the method further includes retrieving, by the processing circuit, projection rules for generating the graphic projection of the building from graphic projection rules stored in a database for the subscriber, wherein the graphic projection rules are associated with the subscriber.
[0126] In some embodiments, the method further includes retrieving, by the processing circuit, a second projection rule for a second subscriber of the subscribers. In some embodiments, the method further includes constructing, by the processing circuit, a second building graph projection including a second plurality of nodes and a second plurality of edges based on at least some of the plurality of entities, at least some of the relationships, and the second projection rule; and storing, by the processing circuit, the building graph projection and the second building graph projection in a graph projection database.
[0127] In some embodiments, the method further includes receiving, by the processing circuit, a modification to the building graphic projection; generating, by the processing circuit, a change feed event, the change feed event recording the modification to the building graphic projection; and adding, by the processing circuit, the change feed event to a change feed, the change feed including change feed events representing modifications to the building graphic projection at different times.
[0128] In some embodiments, the modification is at least one of: adding a new node to the nodes of the building graph projection; adding a new edge to the edges of the building graph projection; deleting an existing node in the nodes of the building graph projection; deleting an existing edge in the edges of the building graph projection; modifying an existing node in the nodes of the building graph projection; or modifying an existing edge in the edges of the building graph projection.
[0129] Another embodiment of the present disclosure is one or more memory devices having instructions thereon, which, when executed by one or more processors, cause the one or more processors to: retrieve projection rules for generating a building graph projection; retrieve relationships between entities representing elements of a building and relationships between entities representing relationships between the entities; construct a building graph projection including nodes and edges based on the entities, relationships, and projection rules; and perform one or more operations based on the building graph projection.
[0130] Event-based query of building graphs
[0131] One embodiment of the present disclosure is a building, the building comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive a query for information of a building graph of the building from a system, the query comprising an indication of an entity and an indication of an event associated with the entity. The instructions cause the one or more processors to: query the building graph with the indication of the entity and the indication of the event associated with the entity to obtain information of the building graph, the building graph comprising nodes and edges, the nodes representing entities and events including the entity and the event, the edges representing relationships between entities and events; and generate a query response based on the information and provide the query response to the system.
[0132] In some embodiments, the indication of the entity is an indication of an entity type of the entity. In some embodiments, the instructions cause the one or more processors to query the building graph with the indication of the entity and the event by: identifying a node of the nodes corresponding to the entity type of the entity, the node representing the entity; and identifying one or more edges between the node representing the entity and a second node of the nodes representing the event. In some embodiments, the instructions cause the one or more processors to generate a query response by causing the query response to include the entity in response to identifying the node and identifying one or more edges between the node and the second node.
[0133] In some embodiments, the system includes a user application. In some embodiments, the instructions cause the one or more processors to receive a query from the user application, wherein the user provides a request for information to the user application and the user application generates the query and provides the query to the building system.
[0134] In some embodiments, the instructions cause the one or more processors to provide the query response to the user application. In some embodiments, the user application generates a display of information indicative of the query response.
[0135] In some embodiments, one or more of the edges between a first node representing a particular event and a second node representing a particular building entity indicates that the particular event is associated with the particular building entity.
[0136] In some embodiments, the particular building entity is a piece of building equipment that generates the particular event.
[0137] In some embodiments, the instructions cause one or more processors to determine whether the system can access information of the building graph based on policies indicated by nodes and edges of the building graph, and provide the information of the building graph to the system in response to determining that the system can access the information of the building graph.
[0138] In some embodiments, the instructions cause one or more processors to determine whether a system can access information of a building graph based on a policy by: identifying a first node among the nodes that represents the system; and identifying an edge among the edges between the first node and a second node that represents a policy for accessing information of the building graph.
[0139] In some embodiments, the instructions cause one or more processors to: receive a request for an entity's capabilities from the system in response to providing a query response to the system; identify the capabilities of the entity in a building graphic; receive a command to perform an operation associated with the entity, the command performing an action associated with the entity's capabilities; and provide the command to perform the operation associated with the entity to an operating system.
[0140] In some embodiments, the instructions cause one or more processors to identify a capability of an entity by: identifying a first node among the nodes of a building graph that represents the entity; and identifying at least one of one or more nodes or one or more edges between the first node and a second node that represents the capability of the entity.
[0141] Another embodiment of the present disclosure is a method, the method comprising receiving, by processing circuitry, a query for information of a building graph of a building from a system, the query comprising an indication of an entity and an indication of an event associated with the entity. The method comprises: querying, by the processing circuitry, the building graph with the indication of the entity and the indication of the event associated with the entity to obtain the information of the building graph, the building graph comprising nodes and edges, the nodes representing entities and events including the entity and the event, the edges representing relationships between entities and events; and generating, by the processing circuitry, a query response based on the information and providing the query response to the system.
[0142] In some embodiments, the indication of the entity is an indication of an entity type of the entity. In some embodiments, querying, by the processing circuit, the building graph with the indication of the entity and the event comprises identifying a node of the node corresponding to the entity type of the entity, the node representing the entity; and identifying one or more edges between the node representing the entity and a second node of the node representing the event. In some embodiments, generating, by the processing circuit, the query response comprises causing the query response to include the entity in response to identifying the node and identifying one or more edges between the node and the second node.
[0143] In some embodiments, the method includes receiving, by the processing circuit, a request for capabilities of an entity from the system in response to providing a query response to the system. In some embodiments, the method includes identifying, by the processing circuit, capabilities of an entity in a building graphic; receiving, by the processing circuit, a command to perform an operation associated with the entity, the command performing an action associated with the capabilities of the entity; and providing, by the processing circuit, the command to perform the operation associated with the entity to an operating system.
[0144] In some embodiments, the method includes receiving a query from a user application, wherein the user provides a request for information to the user application and the user application generates the query and provides the query to the building system.
[0145] In some embodiments, the method includes providing, by the processing circuit, the query response to the user application. In some embodiments, the user application generates a display of information indicative of the query response.
[0146] In some embodiments, one or more of the edges between a first node representing a particular event and a second node representing a particular building entity indicates that the particular event is associated with the particular building entity.
[0147] In some embodiments, the particular building entity is a piece of building equipment that generates the particular event.
[0148] In some embodiments, the method includes determining, by processing circuitry, whether the system can access information of a building graph based on policies indicated by nodes and edges of the building graph, and providing, by the processing circuitry, the information of the building graph to the system in response to determining that the system can access a portion of the building graph.
[0149] In some embodiments, the method includes determining, by a processing circuit, whether a system can access information of a building graph based on a policy by: identifying a first node among nodes that represents the system; and identifying an edge among edges between the first node and a second node that represents a policy for accessing information of the building graph.
[0150] Another embodiment of the present disclosure is one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to receive a query for information of a building graph of a building from a system, the query comprising an indication of an entity and an indication of an event associated with the entity. The instructions cause the one or more processors to: query the building graph with the indication of the entity and the indication of the event associated with the entity to obtain information of the building graph, the building graph comprising nodes and edges, the nodes representing entities and events including the entity and the event, the edges representing relationships between entities and events; and generate a query response based on the information and provide the query response to the system.
[0151] Area-based tenant rights model
[0152] One embodiment of the present disclosure is a building, the building comprising one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to manage subscription rights of one or more buildings with a building rights model, wherein a first subscription in the subscription is linked to a first area via the building rights model, and a second subscription in the subscription is linked to a second area via the building rights model. The instructions cause the one or more processors to: receive a first request to perform a first operation on the first subscription and a second request to perform a second operation on the second subscription; determine whether the first subscription has a first right for the first operation and whether the second subscription has a second right for the second operation based on the building rights model; and perform a first operation on a first computing resource in the first area based on the building rights model in response to a first determination that the first subscription has the first right and perform a second operation on a second computing resource in the second area based on the building rights model in response to a second determination that the second subscription has the second right.
[0153] In some embodiments, the entitlement indicates whether the subscription has authorization to utilize functional resources of the building system.
[0154] In some embodiments, the instructions cause one or more processors to: receive first operation data associated with a first subscription, the first operation data indicating actions of the first subscription that utilize a first computing resource; determine a resource utilization metric for the first subscription based on the first operation data; determine to throttle actions of the first subscription in response to determining that the resource utilization metric exceeds a level; and throttle actions of the first subscription in response to determining that the resource utilization metric exceeds the level to reduce an amount of actions of the first subscription.
[0155] In some embodiments, the instructions cause one or more processors to: receive first operation data associated with a first subscription, the first operation data indicating a first action of the first subscription utilizing a first computing resource; receive second operation data associated with a second subscription, the second operation data indicating a second action of the second subscription utilizing a second computing resource; determine a first resource utilization metric for the first subscription based on the first operation data; and determine a second resource utilization metric for the second subscription based on the second operation data.
[0156] In some embodiments, the instructions cause one or more processors to generate a first bill for an amount proportional to a first resource utilization of a first subscription based on the first resource utilization metric, and to generate a second bill for a second amount proportional to a second resource utilization of a second subscription based on the second resource utilization metric.
[0157] In some embodiments, the first region represents a first geographic boundary, and the first computing resource is located within the first geographic boundary. In some embodiments, the second region represents a second geographic boundary, and the second computing resource is located within the second geographic boundary.
[0158] In some embodiments, the first computing resource comprises a computing resource and a storage resource. In some embodiments, the second computing resource comprises a second computing resource and a second storage resource.
[0159] In some embodiments, the building rights model includes tenants, where tenants represent entities associated with billing boundaries. In some embodiments, tenants are linked to subscriptions through the building rights model.
[0160] In some embodiments, the building rights model includes a second tenant, wherein the second tenant represents a second entity associated with a second billing boundary. In some embodiments, the second tenant is linked to a second plurality of subscriptions of the building rights model via the building rights model.
[0161] Another embodiment of the present disclosure is a method, the method comprising managing subscription rights of one or more buildings by a processing circuit using a building rights model, wherein a first subscription in the subscription is linked to a first region via the building rights model, and a second subscription in the subscription is linked to a second region via the building rights model. The method comprises: receiving, by the processing circuit, a first request to perform a first operation on the first subscription and a second request to perform a second operation on the second subscription; determining, by the processing circuit based on the building rights model, whether the first subscription has a first right for the first operation and whether the second subscription has a second right for the second operation; and implementing, by the processing circuit, a first operation on a first computing resource in the first region based on the building rights model in response to a first determination that the first subscription has the first right and implementing a second operation on a second computing resource in the second region based on the building rights model in response to a second determination that the second subscription has the second right.
[0162] In some embodiments, the entitlement indicates whether the subscription has authorization to utilize functional resources of the building system.
[0163] In some embodiments, the method further includes: receiving, by the processing circuit, first operation data associated with the first subscription, the first operation data indicating an action of the first subscription that utilizes the first computing resource; and determining, by the processing circuit, a resource utilization metric of the first subscription based on the first operation data. In some embodiments, the method further includes: determining, by the processing circuit, in response to determining that the resource utilization metric exceeds a level, to throttle the action of the first subscription; and throttling, by the processing circuit, in response to determining that the resource utilization metric exceeds the level, the action of the first subscription to reduce the amount of the action of the first subscription.
[0164] In some embodiments, the method includes: receiving, by the processing circuit, first operation data associated with a first subscription, the first operation data indicating a first action of the first subscription utilizing a first computing resource; receiving, by the processing circuit, second operation data associated with a second subscription, the second operation data indicating a second action of the second subscription utilizing a second computing resource; determining, by the processing circuit, a first resource utilization metric of the first subscription based on the first operation data; and determining, by the processing circuit, a second resource utilization metric of the second subscription based on the second operation data.
[0165] In some embodiments, the method further includes: generating, by the processing circuit, a first bill for an amount proportional to a first resource utilization of the first subscription based on the first resource utilization metric; and generating, by the processing circuit, a second bill for a second amount proportional to a second resource utilization of the second subscription based on the second resource utilization metric.
[0166] In some embodiments, the first region represents a first geographic boundary, and the first computing resource is located within the first geographic boundary. In some embodiments, the second region represents a second geographic boundary, and the second computing resource is located within the second geographic boundary.
[0167] In some embodiments, the first computing resource comprises a computing resource and a storage resource. In some embodiments, the second computing resource comprises a second computing resource and a second storage resource.
[0168] In some embodiments, the building rights model includes tenants, where tenants represent entities associated with billing boundaries. In some embodiments, tenants are linked to subscriptions through the building rights model.
[0169] In some embodiments, the building rights model includes a second tenant, wherein the second tenant represents a second entity associated with a second billing boundary. In some embodiments, the second tenant is linked to a second plurality of subscriptions of the building rights model via the building rights model.
[0170] Another embodiment of the present disclosure is one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to manage subscription rights for one or more buildings with a building rights model, wherein a first subscription in the subscription is linked to a first region via the building rights model, and a second subscription in the subscription is linked to a second region via the building rights model. The instructions cause the one or more processors to: receive a first request to perform a first operation on the first subscription and a second request to perform a second operation on the second subscription; determine based on the building rights model whether the first subscription has a first right for the first operation and whether the second subscription has a second right for the second operation; and implement a first operation on a first computing resource in the first region based on the building rights model in response to a first determination that the first subscription has the first right and implement a second operation on a second computing resource in the second region based on the building rights model in response to a second determination that the second subscription has the second right.
[0171] In some embodiments, the entitlement indicates whether the subscription has authorization to utilize functional resources of the building system.
[0172] Edge-based event enrichment
[0173] One embodiment of the present disclosure is an edge platform for a building, the edge platform being communicatively coupled to a cloud system, the edge platform comprising one or more memory devices having instructions stored thereon, the one or more memory devices being located within the building's premises and one or more processors being located within the building's premises, the one or more processors executing instructions that cause the one or more processors to receive an event from a piece of building equipment of the building, the event indicating a data value associated with the piece of building equipment occurring at a specific time. The instructions cause the one or more processors to: identify context data of a data structure that provides a context description of the event; generate an enriched event by enriching the event with the context data, the enriched event comprising the data value, the specific time, and the context data; and transmit the enriched event to a cloud system configured to operate based on the enriched event.
[0174] In some embodiments, the instructions cause the one or more processors to train one or more machine learning models stored locally by the edge platform based on the enriched events, and to perform one or more operations with a piece of construction equipment based on the one or more machine learning models.
[0175] In some embodiments, the instructions cause the one or more processors to identify context data based on one or more enrichment rules. In some embodiments, the instructions cause the one or more processors to identify second context data of the data structure based on one or more second enrichment rules; generate a second enriched event by enriching the event with the second context data, the data value, and the specific time; and provide the second enriched event to the cloud system.
[0176] In some embodiments, the data structure is a graph.In some embodiments, the instructions cause the one or more processors to identify the context data by searching the graph for a context description of the event.
[0177] In some embodiments, the graph includes nodes and edges. In some embodiments, the nodes represent entities of a building and the edges represent relationships between the entities of the building. In some embodiments, the nodes include a node representing a piece of building equipment. In some embodiments, the instructions cause the one or more processors to identify contextual data by identifying one or more nodes based on one or more of the edges between the node representing the piece of building equipment and one or more of the nodes related to the node representing the piece of building equipment.
[0178] In some embodiments, the data structure is a digital twin stored by the edge platform. In some embodiments, the digital twin of the edge platform is updated based on changes made to the second digital twin stored by the cloud system to synchronize the second digital twin stored by the cloud system with the digital twin of the edge platform.
[0179] In some embodiments, the instructions cause one or more processors to receive a change feed of a change feed event indicating a change of a second digital twin, and update the digital twin stored by the edge platform with the change feed by making changes to the digital twin stored by the edge platform.
[0180] In some embodiments, the second digital twin is a graph comprising nodes representing entities of the building and a plurality of edges representing relationships between the entities of the building. In some embodiments, the change comprises at least one of: adding a new node to the nodes of the graph; adding a new edge to the edges of the graph; deleting an existing node in the nodes of the graph; deleting an existing edge in the edges of the graph; modifying an existing node in the nodes of the graph; or modifying an existing edge in the edges of the graph.
[0181] In some embodiments, the instructions cause the one or more processors to read change feed events from a change feed topic, wherein the edge platform subscribes to the change feed topic and receives the change feed events in response to the change feed events being added to the change feed topic by the cloud system.
[0182] Another embodiment of the present disclosure is a method, the method comprising receiving, by an edge platform, an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a specific time, the edge platform being located on-site within the building and communicatively coupled to a cloud system; identifying, by the edge platform, contextual data of a data structure that provides a contextual description of the event; generating, by the edge platform, an enriched event by enriching the event with the contextual data, the enriched event including the data value, the specific time, and the contextual data; and transmitting, by the edge platform, the enriched event to a cloud system configured to operate based on the enriched event.
[0183] In some embodiments, the method includes training, by the edge platform, one or more machine learning models stored locally by the edge platform based on the enriched events; and performing, by the edge platform, one or more operations with a piece of building equipment based on the one or more machine learning models.
[0184] In some embodiments, the method includes: identifying, by the edge platform, context data based on one or more enrichment rules; identifying, by the edge platform, second context data of the data structure based on one or more second enrichment rules; generating, by the edge platform, a second enriched event by enriching the event with the second context data, a data value, and a specific time; and providing, by the edge platform, the second enriched event to the cloud system.
[0185] In some embodiments, the data structure is a graph.In some embodiments, the method further comprises identifying, by the edge platform, the contextual data by searching the graph comprising a contextual description of the event.
[0186] In some embodiments, the graph includes nodes and edges. In some embodiments, the nodes represent entities of a building and the edges represent relationships between the entities of the building. In some embodiments, the nodes include a node representing a piece of building equipment. In some embodiments, the method further includes identifying, by the edge platform, contextual data by: identifying one or more nodes based on one or more of the edges between the node representing the piece of building equipment and one or more of the nodes related to the node representing the piece of building equipment.
[0187] In some embodiments, the data structure is a digital twin stored by the edge platform. In some embodiments, the method further includes updating the digital twin of the edge platform based on changes made to the second digital twin stored by the cloud system to synchronize the second digital twin stored by the cloud system with the digital twin of the edge platform.
[0188] In some embodiments, the method includes: receiving, by the edge platform, a change feed of a change feed event indicating a change of a second digital twin; and updating, by the edge platform, a digital twin stored by the edge platform with the change feed by making changes to the digital twin stored by the edge platform.
[0189] In some embodiments, the second digital twin is a graph comprising nodes representing entities of the building and a plurality of edges representing relationships between the entities of the building. In some embodiments, the change comprises at least one of: adding a new node to the nodes of the graph; adding a new edge to the edges of the graph; deleting an existing node in the nodes of the graph; deleting an existing edge in the edges of the graph; modifying an existing node in the nodes of the graph; or modifying an existing edge in the edges of the graph.
[0190] In some embodiments, the method includes reading, by the edge platform, change feed events from a change feed topic, wherein the edge platform subscribes to the change feed topic and receives the change feed events in response to the change feed events being added to the change feed topic by the cloud system.
[0191] Another embodiment of the present disclosure is an edge platform for a building, the edge platform being communicatively coupled to a cloud system, the edge platform comprising one or more memory devices having instructions stored thereon and one or more processors, the one or more processors executing instructions that cause the one or more processors to receive an event from a piece of building equipment of the building, the event indicating a data value associated with the piece of building equipment occurring at a specific time. The instructions cause the one or more processors to: identify context data of a data structure that provides a context description of the event; generate an enriched event by enriching the event with the context data, the enriched event comprising the data value, the specific time, and the context data; and transmit the enriched event to a cloud system configured to operate based on the enriched event.
[0192] In some embodiments, the data structure is a graph.In some embodiments, the instructions cause the one or more processors to identify the context data by searching the graph for a context description of the event.
[0193] Synchronize with digital twins of external systems
[0194] One embodiment of the present disclosure is a building system for a building, the building system including one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to store a digital twin of the building including a graph data structure, the graph data structure including nodes representing entities of the building and edges between the nodes representing relationships between the entities of the building. The instructions cause the one or more processors to: receive modifications to the digital twin of the building, update at least one of the modified nodes or edges; generate change feed events for a change feed, the change feed events recording modifications to the graph data structure, the change feed including change feed events representing modifications to the graph data structure at different times; and synchronize an external digital twin of the building of an external system with the digital twin of the building by communicating with an external system based on the change feed events.
[0195] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0196] In some embodiments, the instructions cause one or more processors to receive a modification to a digital twin of a building by receiving an event from a piece of building equipment of the building and determining a modification to the digital twin of the building based on the event.
[0197] In some embodiments, the instructions cause one or more processors to synchronize an external digital twin of a building in an external system with a digital twin of the building based on a change feed event by transmitting the change feed event to the external system, wherein the external system updates the external digital twin of the building based on the change feed event.
[0198] In some embodiments, the instructions cause one or more processors to receive modifications to the digital twin of the building from a second external system, wherein the modifications to the digital twin of the building are based on second modifications made by the second external system to a second external digital twin of the building stored by the second external system.
[0199] In some embodiments, the modification is at least one of: adding a new node to the nodes of the graph data structure; adding a new edge to the edges of the graph data structure; deleting an existing node in the nodes of the graph data structure; deleting an existing edge in the edges of the graph data structure; modifying an existing node in the nodes of the graph data structure; or modifying an existing edge in the edges of the graph data structure.
[0200] In some embodiments, the instructions cause the one or more processors to add the change feed event to the change feed topic, wherein the external system subscribes to the change feed topic and receives the change feed event in response to adding the change feed event to the change feed topic.
[0201] In some embodiments, the instructions cause one or more processors to synchronize an external digital twin of a building of an external system with a digital twin of the building by communicating with the external system based on a change feed event, wherein a first format of the external digital twin of the building is different from a format of the digital twin of the building.
[0202] In some embodiments, the instructions cause one or more processors to synchronize a second external digital twin of a second external system based on a change feed event, wherein a second format of the second external digital twin is different from the first format of the external digital twin and the format of the digital twin of the building.
[0203] In some embodiments, the instructions cause one or more processors to: generate a first update to an external digital twin of a building based on a change feed event in a first format of an external digital twin of the building for an external system; generate a second update to a second external digital twin of the building based on a change feed event in a second format of a second external digital twin of the building for a second external system; transmit the first update to the external digital twin of the building to the external system, wherein the external system updates the external digital twin of the building based on the first update; and transmit the second update to the second external digital twin of the building to the second external system, wherein the second external system updates the external digital twin of the building based on the second update.
[0204] Another embodiment of the present disclosure is a method, the method comprising storing, by a processing circuit, a digital twin of a building comprising a graph data structure, the graph data structure comprising nodes representing entities of the building and edges between the nodes representing relationships between the entities of the building. The method comprises: receiving, by the processing circuit, a modification to the digital twin of the building, updating at least one of the modified nodes or edges; generating, by the processing circuit, a change feed event of a change feed, the change feed event recording the modification to the graph data structure, the change feed comprising change feed events representing modifications to the graph data structure at different times; and synchronizing, by the processing circuit based on the change feed event, an external digital twin of the building of an external system with the digital twin of the building by communicating with the external system.
[0205] In some embodiments, the entity of the building is at least one of building equipment, a location of the building, a user of the building, and an event of the building.
[0206] In some embodiments, receiving, by the processing circuit, a modification to the digital twin of the building includes receiving an event from a piece of building equipment of the building and determining, based on the event, the modification to the digital twin of the building.
[0207] In some embodiments, synchronizing, by processing circuitry, an external digital twin of a building of an external system with a digital twin of the building based on a change feed event includes transmitting the change feed event to the external system, wherein the external system updates the external digital twin of the building based on the change feed event.
[0208] In some embodiments, the method includes receiving, by the processing circuit, a modification to the digital twin of the building from a second external system, wherein the modification to the digital twin of the building is based on a second modification made by the second external system to a second external digital twin of the building stored by the second external system.
[0209] In some embodiments, the modification is at least one of: adding a new node to the nodes of the graph data structure; adding a new edge to the edges of the graph data structure; deleting an existing node in the nodes of the graph data structure; deleting an existing edge in the edges of the graph data structure; modifying an existing node in the nodes of the graph data structure; or modifying an existing edge in the edges of the graph data structure.
[0210] In some embodiments, the method further includes adding, by the processing circuit, the change feed event to the change feed topic, wherein the external system subscribes to the change feed topic and receives the change feed event in response to adding the change feed event to the change feed topic.
[0211] In some embodiments, synchronizing, by processing circuitry, an external digital twin of a building of an external system with a digital twin of the building based on a change feed event includes communicating with the external system, wherein a first format of the external digital twin of the building is different from a format of the digital twin of the building.
[0212] In some embodiments, the method includes synchronizing, by the processing circuit, a second external digital twin of a second external system based on the change feed event, a second format of the second external digital twin being different from the first format of the external digital twin and the format of the digital twin of the building.
[0213] Another embodiment of the present disclosure is one or more memory devices having instructions thereon, the instructions, when executed by one or more processors, causing the one or more processors to store a digital twin of a building comprising a graph data structure, the graph data structure comprising nodes representing entities of the building and edges between the nodes representing relationships between the entities of the building. The instructions cause the one or more processors to: receive modifications to the digital twin of the building, update at least one of the modified nodes or edges; generate change feed events for a change feed, the change feed events recording modifications to the graph data structure, the change feed comprising change feed events representing modifications to the graph data structure at different times; and synchronize an external digital twin of the building of an external system with the digital twin of the building by communicating with the external system based on the change feed events. BRIEF DESCRIPTION OF THE DRAWINGS
[0214] Various objects, aspects, features and advantages of the present disclosure will become more apparent and better understood by reference to the detailed description taken in conjunction with the accompanying drawings, in which the same reference numerals identify corresponding elements throughout. In the drawings, the same reference numerals generally represent identical, functionally similar and / or structurally similar elements.
[0215] Figure 1 is a block diagram of a building data platform including an edge platform, a cloud platform, and a twin manager according to an exemplary embodiment.
[0216] Figure 2 is a process according to an exemplary embodiment from Figure 1 The edge platform receives the event Figure 1 Block diagram of the cloud platform and twin manager.
[0217] Figure 3 The processing of the event is shown in more detail according to an exemplary embodiment. Figure 1 Block diagram of the cloud platform.
[0218] Figure 4 is a method for generating a projection according to an exemplary embodiment and with Figure 1The components of the cloud platform work together to enrich the event Figure 1 Block diagram of the twin manager.
[0219] Figure 5 According to an exemplary embodiment, Figure 1 Flowchart of a pre-processing workflow that a cloud platform executes to pre-process events.
[0220] Figure 6 According to an exemplary embodiment, Figure 1 Flowchart of a discovery workflow performed by a cloud platform to discover new entities from metadata and device trees.
[0221] Figure 7 According to an exemplary embodiment, the projection is generated by Figure 1 Flowchart of the projection workflow performed by the twin manager.
[0222] Figure 8 is a method according to an exemplary embodiment of enriching an event with contextual information Figure 1 Flowchart of the rich workflow executed by the cloud platform.
[0223] Fig. 9 According to an exemplary embodiment, Figure 1 A flowchart of a command processing workflow performed by a cloud platform, where commands are sent to a device or transmitted to an external system via a connection agent.
[0224] Fig.10 According to an exemplary embodiment, Figure 1 Flowchart of the message delivery workflow executed by the cloud platform, where Figure 1 The edge platform receives messages from the building systems and transmits commands for the building systems to the building subsystems via the edge platform.
[0225] Fig.11 According to an exemplary embodiment Figure 1 A graphical projection of the twin manager, containing application programming interface (API) data, capability data, policy data, and services.
[0226] Fig.12 According to an exemplary embodiment Figure 1 Another graphical projection of the twin manager, containing application programming interface (API) data, capability data, policy data, and services.
[0227] Fig.13 According to an exemplary embodiment Figure 1 A graphical projection of the twin manager that contains data about devices and their capabilities.
[0228] Fig.14is a block diagram of a user interaction manager that processes user queries and requests according to an exemplary embodiment.
[0229] Fig.15 A security dashboard according to an exemplary embodiment and Figure 1 Flowchart of a process for communicating with a building data platform to check information about a device and command the device.
[0230] Fig.16 According to an exemplary embodiment, Figure 1 Flowchart of the process performed by the cloud platform, where events of building equipment are enriched with graphical contextual information.
[0231] Fig.17 According to an exemplary embodiment, Figure 1 Flowchart of the process performed by the Twin Manager, where a change feed of events records modifications to the graph.
[0232] Fig.18 According to an exemplary embodiment, Figure 1 A flowchart of a process performed by a cloud platform in which a graphic recognition capability of a piece of equipment is used to operate the piece of equipment.
[0233] Fig.19 is a flowchart of a process according to an exemplary embodiment, wherein Figure 1 The cloud platform operates through different services related to the graph.
[0234] Fig. 20 According to an exemplary embodiment, Figure 1 A flow chart of a process performed by a cloud platform in which information and control capabilities are provided to users or services based on policies stored within a graph.
[0235] Fig.21 is a flow diagram of a process in which a graphical projection for a system is constructed based on projection rules according to an exemplary embodiment.
[0236] Fig. 22 is a flow diagram of a process in which a graph is queried based on entities and events according to an exemplary embodiment.
[0237] Fig.23 According to an exemplary embodiment Figure 1 Block diagram of a platform manager of a cloud platform that manages tenant and subscription rights with a tenant rights model.
[0238] Fig.24 is a block diagram of a more detailed tenant rights model according to an exemplary embodiment.
[0239] Fig.25is a flow diagram of a process for managing tenant and subscription rights with a tenant rights model according to an exemplary embodiment.
[0240] Fig.26 According to an exemplary embodiment Figure 1 Block diagram of an edge platform that performs event enrichment at the edge before transmitting the events to the cloud.
[0241] Fig. 27 According to an exemplary embodiment, before transmitting the event to the cloud, Figure 1 Flowchart of the process by which the edge platform performs event enrichment at the edge.
[0242] Fig.28 According to an exemplary embodiment Figure 1 Block diagram of a twin manager that synchronizes the twin manager's digital twin with the digital twins of other external systems.
[0243] Fig.29 is a flow chart of a process for synchronizing a twin manager's digital twin with digital twins of other external systems according to an exemplary embodiment. DETAILED DESCRIPTION
[0244] Overview
[0245] Referring generally to the accompanying drawings, a building data platform is shown according to various exemplary embodiments. The building data platform described herein can be configured to facilitate the management and control of a building. The building data platform can provide agility, flexibility, and scalability for building management, thereby making the building a dynamic space.
[0246] The building data platform may allow users to systematically manage operations with a building having memory, intelligence, and unique identification. The building data platform may be configured to perform energy and space optimization, predictive maintenance, and / or remote operations. Although the building data platform is described for a building, such as for a building subsystem of a building (e.g., for an HVAC system, a security system, an access control system, an elevator system, a fire response system, etc.), the building data platform may be applied to other industries, such as motor vehicles, airports, manufacturing systems, transportation systems, aircraft, and / or any other type of system requiring device management. The building data platform may provide seamless integration of devices regardless of brand, make, model, or subsystem.
[0247] The building data platform may include multiple components, such as an edge platform, a cloud platform, and a twin manager. The edge platform may be configured to facilitate connecting the building data platform directly to the building systems. The edge platform may facilitate receiving, collecting, and / or retrieving data from the building subsystems. In some embodiments, the edge platform may facilitate command and control of the building systems for the building data platform.
[0248] The cloud platform may be configured to facilitate message control of the building data platform. The cloud platform may be configured to receive messages from the building subsystems through the edge platform and manage the messages. The cloud platform may route messages around the building data platform. In addition, the cloud platform may facilitate directing operation commands for the building subsystems to the building subsystems through the edge platform. In some embodiments, the cloud platform is configured to enrich messages received from the building subsystems. The cloud platform may be configured to add contextual information to event messages received from the building subsystems via the edge platform. The contextual information may be used by applications that consume event messages and may allow applications to immediately access the contextual information, rather than requiring the application to query another system to receive the contextual information.
[0249] The twin manager can facilitate the management of digital twins of buildings (e.g., building subsystems). A digital twin can be a digital replica of a physical entity that enables in-depth analysis of the data of the physical entity and provides monitoring systems to reduce risks, manage problems, and test future solutions using simulations. Digital twins can play an important role in helping technicians find the root cause of problems and solve them faster, supporting safety and security protocols, and supporting building managers to use energy and other facility resources more efficiently. Digital twins can be used to implement and unify security systems, employee experience, facility management, sustainability, and more.
[0250] The twin manager can be configured to track building subsystems by storing entities (e.g., data representing devices, buildings, spaces, floors, software services, policies, etc.), relationships (e.g., relationships between devices and their locations, API calls between software services, etc.), and events (e.g., data, measurements, commands, states, etc. that have occurred). The twin manager can create a graph projection, e.g., a graph with nodes for entities and events of the building and edges for relationships between entities and / or events. The graph projection can be based on specific policies (e.g., which entities, events, and / or relationships should be included in the graph) and / or ontologies (types of relationships that should be established with different types of entities and / or events). In this regard, specific graph projections can be generated for specific subscribers, users, systems, etc.
[0251] Reference now Figure 1, according to an exemplary embodiment, a building data platform 100 including an edge platform 102, a cloud platform 106, and a twin manager 108 is shown. The edge platform 102, the cloud platform 106, and the twin manager 108 can each be a separate service deployed on the same or different computing systems. In some embodiments, the cloud platform 106 and the twin manager 108 are implemented off-site of the computing system, such as outside of a building. The edge platform 102 can be implemented on-site, such as inside a building.
[0252] The building data platform 100 includes applications 110. The applications 110 may be various applications for managing building subsystems 122. The applications 110 may be remote or on-site applications running on various computing systems. The applications 110 may include an alarm application 168 configured to manage alarms for the building subsystems 122. The applications 110 include an assurance application 170 that implements assurance services for the building subsystems 122. In some embodiments, the applications 110 include an energy application 172 configured to manage energy usage of the building subsystems 122. The applications 110 include a security application 174 configured to manage the security system of the building.
[0253] In some embodiments, the application 110 and / or the cloud platform 106 interact with a user device 176. In some embodiments, components of the application 110 or the entire application extend on the user device 176. The user device 176 may be a laptop computer, a desktop computer, a smartphone, a tablet computer, and / or any other device having an input interface (e.g., a touch screen, a mouse, a keyboard, etc.) and an output interface (e.g., a speaker, a display, etc.).
[0254] The application 110, the twin manager 108, the cloud platform 106, and the edge platform 102 can be implemented on one or more computing systems, such as on processors and / or memory devices. For example, the edge platform 102 includes a processor 118 and a memory 120, the cloud platform 106 includes a processor 124 and a memory 126, the application 110 includes a processor 164 and a memory 166, and the twin manager 108 includes a processor 148 and a memory 150.
[0255] The processor may be a general or special purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGA), a group of processing components, or other suitable processing components. The processor may be configured to execute computer codes and / or instructions stored in the memory or received from other computer readable media (e.g., CDROM, network storage device, remote server, etc.).
[0256] The memory may include one or more devices (e.g., memory cells, memory devices, 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 drive storage, temporary storage, non-volatile memory, flash memory, optical storage, or any other suitable memory for storing software objects and / or computer instructions. The memory may include a database component, an object code component, a script component, or any other type of information structure for supporting various activities and the information structures described in the present disclosure. The memory may be communicatively connected to the processor and may include computer code for executing (e.g., by the processor) one or more processes described herein.
[0257] The edge platform 102 may be configured to provide connectivity to the building subsystem 122. The edge platform 102 may receive messages from and / or deliver messages to the building subsystem 122. The edge platform 102 includes one or more gateways, such as gateways 112 to 116. The gateways 112 to 116 may act as gateways between the cloud platform 106 and the building subsystem 122. The gateways 112 to 116 may be gateways described in U.S. Provisional Patent Application No. 62 / 951,897 filed on December 20, 2019, the entire contents of which are incorporated herein by reference. In some embodiments, the application 110 may be deployed on the edge platform 102. In this regard, lower latency in managing the building subsystem 122 may be achieved.
[0258] The edge platform 102 can be connected to the cloud platform 106 via a network 104. The network 104 can communicatively couple the devices and systems of the building data platform 100. In some embodiments, the network 104 is at least one 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 various communication protocols (e.g., BACnet, IP, LON, etc.). The network 104 can include routers, modems, servers, cell phone towers, satellites, and / or network switches. The network 104 can be a combination of wired and wireless networks.
[0259] The cloud platform 106 can be configured to facilitate messaging and routing between the applications 110, the twin manager 108, the edge platform 102, and / or any other systems. The cloud platform 106 can include a platform manager 128, a messaging manager 140, a command processor 136, and an enrichment manager 138. In some embodiments, the cloud platform 106 can facilitate messaging between the building data platform 100 via the network 104.
[0260] The information delivery manager 140 can be configured to operate as a transport service that controls communications with the building subsystem 122 and / or any other system, such as management commands to devices (C2D), commands to connectors for external systems (C2C), commands from devices to the cloud (D2C), and / or notifications. The information delivery manager 140 can receive different types of data from the application 110, the twin manager 108, and / or the edge platform 102. The information delivery manager 140 can receive value data changes 142, such as data indicating that the value of a point has changed. The information delivery manager 140 can receive time series data 144, such as a time-related sequence of data entries each associated with a specific timestamp. In addition, the information delivery manager 140 can receive command data 146. All messages processed by the cloud platform 106 can be processed as events, for example, data 142 to 146 can each be encapsulated as an event with a data value occurring at a specific time (e.g., a temperature measurement taken at a specific time).
[0261] The cloud platform 106 includes a command processor 136. The command processor 136 may be configured to receive commands to perform actions from the application 110, the building subsystem 122, the user device 176, etc. The command processor 136 may manage the commands, determine whether the command system is authorized to perform a particular command, and transmit the commands to the command system, such as the building subsystem 122 and / or the application 110. The commands may be commands to change operating settings that control environmental conditions of the building, commands to run analytics, etc.
[0262] The cloud platform 106 includes an enrichment manager 138. The enrichment manager 138 can be configured to enrich events received by the information delivery manager 140. The enrichment manager 138 can be configured to add contextual information to the events. The enrichment manager 138 can communicate with the twin manager 108 to retrieve the contextual information. In some embodiments, the contextual information is an indication of information related to the event. For example, if the event is a time series of temperature measurements of a thermostat, contextual information such as the location of the thermostat (e.g., what room), the device controlled by the thermostat (e.g., what VAV), etc. can be added to the event. In this regard, when a consuming application, such as one of the applications 110, receives an event, the consuming application can operate based on the data of the event, the temperature measurements, and the contextual information of the event.
[0263] The enrichment manager 138 can address the following problem: when devices generate a lot of information, the information may contain simple data without context. An example may contain data generated when a user scans a badge at a badge scanner of the building subsystem 122. This physical event may generate an output event containing information such as "DeviceBadgeScannerID", "BadgeID", and / or "Date / Time". However, if the system sends this data to consuming applications, such as Consumer A and Consumer B, each consumer may need to call the Building Data Platform Knowledge Service to query the information through queries such as "What space, building, floor is the badge scanner in?" or "What user is associated with the badge?"
[0264] By performing enrichment on the data feed, the system may be able to perform inferences on the data. The result of the enrichment may be a transformation of the message "DeviceBadgeScannerId, BadgeId, Date / Time" to "Region, Building, Floor, Asset, DeviceId, BadgeId, Username, EmployeeId, Scan Date / Time". This may be a significant optimization as the system may reduce the number of calls by 1 / n, where n is the number of consumers of this data feed.
[0265] By using this enrichment, the system can also have the ability to filter out undesirable events. If there are 100 buildings on a campus, each receiving 100,000 events per hour, but only 1 building is actually in use, only 1 / 10 of the events are being enriched. By looking at what events are being enriched and what events are not, the system can shape the forwarding of those events to reduce the cost of forwarding events that no consuming application wants or reads.
[0266] Examples of events received by enrichment manager 138 may be:
[0267]
[0268] Examples of enrichment events received by enrichment manager 138 may be:
[0269]
[0270]
[0271] By receiving the enriched events, an application in the applications 110 may be able to populate and / or filter what events are associated with what regions. In addition, the user interface generation application may generate a user interface containing contextual information based on the enriched events.
[0272] The cloud platform 106 includes a platform manager 128. The platform manager 128 may be configured to manage users and / or subscriptions of the cloud platform 106. For example, what subscriptions buildings, users, and / or tenants use the cloud platform 106. The platform manager 128 includes a provisioning service 130, which is 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, which is configured to manage subscriptions for buildings, users, and / or tenants, and an entitlement service 134, which may track entitlements for buildings, users, and / or tenants.
[0273] The twin manager 108 may be configured to manage and maintain a digital twin. A digital twin may be a digital representation of a physical environment, such as a building. The twin manager 108 may include a change feed generator 152, an architecture and ontology 154, a projection manager 156, a policy manager 158, an entity, relationship, and event database 160, and a graph projection database 162.
[0274] The graphic projection manager 156 may be configured to construct graphic projections and store the graphic projections in the graphic projection database 162. Examples of graphic projections are described in Figures 11 to 13 Entities, relationships, and events may 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 entity-relationship sets for multiple subscriptions. Subscriptions may be, for example, Fig.24 A subscription for a specific tenant as described in .
[0275] In some embodiments, the graphic projection manager 156 generates a graphic projection of a specific user, application, subscription and / or system. In this regard, in addition to the ontology specific to the user, application and / or system, a graphic projection can be generated based on the strategy for a specific user, application and / or system. In this regard, an entity can request a graphic projection, and the graphic projection manager 156 can be configured to generate a graphic projection of an entity based on the strategy and ontology specific to the entity. The strategy can indicate what entity, relationship and / or event an entity can access. The ontology can indicate the entity that the requesting entity expects to see, such as what type of relationship between the floor in the building, the device in the floor, etc. Another requesting entity can have an ontology to view the device in the building and the application for the device in the graphic.
[0276] The graph projections generated by the graph projection manager 156 and stored in the graph projection database 162 can be knowledge graphs and are integration points. For example, a graph projection can represent floor plans and systems associated with each floor. In addition, the graph projection can contain events, such as telemetry data for the building subsystems 122. The graph projection can show application services as nodes and API calls between services as edges in the graph. The graph projection can illustrate the capabilities of spaces, users, and / or devices. The graph projection can contain indications of the building subsystems 122, such as thermostats, cameras, VAVs, etc. The graph projection database 162 can store graph projections that maintain the current state of the building.
[0277] In some embodiments, the enrichment manager 138 may enrich the event using the graph projection of the graph projection database 162. In some embodiments, the enrichment manager 138 may identify nodes and relationships associated with and related to the device that generated the event. For example, the enrichment manager 138 may identify a thermostat that generated a temperature measurement event within the graph. The enrichment manager 138 may identify a relationship between the thermostat and a space, such as a zone in which the thermostat is located. The enrichment manager 138 may add an indication of the zone to the event.
[0278] In addition, the command processor 136 can be configured to use the graphic projection to command the building subsystem 122. The command processor 136 can identify the policy for the command entity within the graphic projection to determine whether the command entity has the ability to issue commands. For example, before allowing the user to issue a command, the command processor 136 determines based on the graphic projection database 162 that the user has a policy that enables the command to be issued.
[0279] In some embodiments, the policy can be a condition-based policy. For example, the building data platform 100 can apply one or more conditional rules to determine whether a particular system has the ability to perform an action. In some embodiments, the rules analyze behavior-based biometrics. For example, behavior-based biometrics can indicate normal behavior and / or normal behavior rules for the system. In some embodiments, when the building data platform 100 determines that the action requested by the system does not match normal behavior based on one or more conditional rules, the building data platform 100 can deny the system the ability to perform an action and / or request approval from a higher-level system.
[0280] For example, a behavior rule may indicate that a user has the right to log into the system with a specific IP address between 8 a.m. and 5 p.m. However, if the user logs into the system at 7 p.m., the building data platform 110 may contact the administrator to determine whether to provide the user with login permissions.
[0281] The change feed generator 152 can be configured to generate an event feed indicating changes to a digital twin (e.g., a graph). The change feed generator 152 can track changes to entities, relationships, and / or events of a graph. For example, the change feed generator 152 can detect the addition, deletion, and / or modification of nodes or edges of a graph, such as changing entities, relationships, and / or events within the database 160. In response to detecting a change in a graph, the change feed generator 152 can generate an event summarizing the change. Events can indicate what nodes and / or edges have changed and how the nodes and edges have changed. Events can be published to topics by the change feed generator 152.
[0282] The change feed generator 152 can implement a change feed of the knowledge graph. The building data platform 100 can implement subscriptions to knowledge graph changes. When the change feed generator 152 publishes events in the change feed, the subscribing system or application can receive the change feed events. By generating a record of all changes that have occurred, the system can hierarchical data in different ways and then replay the data back in any order the system wishes. This can include running changes one by one and / or by jumping from one major change to the next. For example, in order to generate a graph at a specific time, all change feed events up to the specific time can be used to build the graph.
[0283] In some embodiments, a change feed can track changes to each node in a graph and the relationships associated with it. If a user wants to subscribe to these changes and the user has the appropriate permissions, the user can simply submit a network API call to obtain sequential notifications of each change that occurs in the graph. The user and / or system can replay the changes one by one at any given time slice to reestablish the graph. Although the message is "streamlined" and only contains change notifications and reference "id / seq id", the change feed can maintain a copy of each state of each node and / or relationship, so that the user and / or system can retrieve those past states of each node at any time. In addition, consumers of the change feed can also create dynamic "views", allowing different "snapshots" of the appearance of the graph to be obtained in a timely manner from a specific context. Although the twin manager 108 may contain the history and current state of the graph based on architectural evaluation, consumers can retain a copy of the data, thereby creating dynamic views using change feeds.
[0284] The architecture and ontology 154 can define the message architecture and graph ontology of the twin manager 108. The message architecture can define what format the messages received by the information delivery manager 140 should have, such as what parameters, what format, etc. The ontology can define a graph projection, such as an ontology that a user wants to view. For example, various systems, applications, and / or users can be associated with a graph ontology. Therefore, when the graph projection manager 156 generates a graph projection for a user, system, or subscription, the graph projection manager 156 can generate the graph projection based on the user-specific ontology. For example, an ontology can define what types of entities are related in what order in a graph, for example, for the ontology of the subscription of "Consumer A", the graph projection manager 156 can create the relationship of the graph projection based on the following rules:
[0285] Area ←→ Building ←→ Floor ←→ Space ←→ Asset
[0286] For the subscribed ontology of “Consumer B”, the graph projection manager 156 may create a relationship based on the following rules:
[0287] Building ←→ Floor ←→ Asset
[0288] The policy manager 158 can be configured to respond to requests from other applications and / or policy systems. The policy manager 158 can query the graph projection to determine what permissions different applications, users, and / or devices have. The graph projection can indicate the various permissions that different types of entities have, and the policy manager 158 can search the graph projection to identify the permissions of a particular entity. The policy manager 158 can facilitate fine-grained access control of user permissions. The policy manager 158 can apply permissions across the graph, for example, if "users can view all data associated with floor 1", then they can view all subsystem data for that floor, such as surveillance cameras, HVAC units, fire detection and response devices, etc.
[0289] Reference now Figure 2 , according to an exemplary embodiment, a cloud platform 106 and a twin manager 108 are shown processing events received from an edge platform 102. The cloud platform 106 includes a preprocessor 202, a topic 204, an enrichment manager 138, and enriched events 208. The twin manager 108 is shown to include an entity, relationship, and event database 160, an architecture and ontology 154, and a projection manager 156. The projection manager 156 includes a policy manager 158, a graph projection generator 210, and a graph projection database 162.
[0290] If the information delivery manager 140 has not yet formatted the data into events, the data received from the edge platform 102 or any other system described herein can be converted into events. The information delivery manager 140 can provide the events to the preprocessor 202. The preprocessor 202 can analyze the events to ensure that the events are formatted appropriately. For example, the preprocessor 202 can call the architecture and ontology 154 of the twin manager 108 to identify the architecture of the event. The preprocessor 202 can determine whether the format of the event is correct based on the architecture.
[0291] In addition, preprocessor 202 can identify what topic the event belongs to, for example, whether the event is related to changes in graphic projection database 162 or whether the event is related to telemetry data of the building. Preprocessor 202 can provide the event to the appropriate topic of topics 204.
[0292] The enrichment manager 138 can be configured to enrich events for one or more specific topics of the topics 204. The enrichment manager 138 can receive a schema for enrichment and a graphical projection for enrichment. In some embodiments, the ontology received by the enrichment manager 138 can define enrichment rules for specific types of events, such as what information should be shown for a specific event. For example, for an event for a thermostat, a rule can define that the location and device controlled by the thermostat should be enriched into the event.
[0293] The enrichment manager 138 may receive a graph projection containing all nodes and edges defining context information associated with an event from the graph projection database 162. The received projection may contain information added to the event as part of the enrichment. The enriched event 208 is then provided to the application 110 for processing, where the application 110 operates based on the raw data of the event and the context information enriched into the event.
[0294] The graphic projection generator 210 is shown receiving data from the entity, relationship, and event database 160. In addition, the graphic projection generator 210 may receive an ontology from the architecture and ontology 154. The graphic projection generator 210 may generate a graphic projection based on the ontology and the data received from the database 160. The graphic projection may be stored in the graphic projection database 162. In addition, the policy manager 158 may select different ontologies to provide to the graphic projection generator 210 and / or the enrichment manager 138. In this regard, based on the entity (e.g., application or system) that will consume the graphic projection and / or receive the enriched events, the policy manager 158 may select an entity-specific ontology.
[0295] Reference now Figure 3 , according to an exemplary embodiment, a cloud platform 106 is shown processing events. The preprocessor 202 receives the events through the consumer feed filter and processes the events. The consumer feed filter can filter the events into specific topics for consumption by various consumers, for example, for a specific event topic 324. In this regard, a specific application or system can create a subscription in the topic-to-subscription mapping 302, and can add the corresponding events of the topic to the topic of the event topic 324.
[0296] The preprocessor 202 includes an architecture validator 306. The architecture validator can call the architecture and ontology 154 and receive an architecture or architecture collection to validate an event to determine whether the event is formatted in an allowed architecture and / or contains minimum fields. If the event is formatted appropriately (e.g., matches an approved architecture in the architecture and ontology 154), the event can be provided to the router 308. If the event is formatted inappropriately, the event can be added to the malformed device tree 336. A user and / or an analysis system can examine the malformed device tree 336 to determine a system configuration error. For example, the cloud platform 106 can identify an inappropriate graph configuration with missing nodes or relationships within the graph.
[0297] The router 308 may add events to one or more topics of the topics 204. One of the topics 310 is the change feed topic 310. Graphic change feed events are created by the change feed generator 152 and added to the change feed topic 310. The topics 204 further include a raw event topic 312, a metadata topic 314, and a device tree topic 316. The router may separate events into various topics based on the type of event.
[0298] The metadata topic 314 may contain metadata 320. Metadata may be data describing an entity (e.g., a device) and / or capabilities and / or policies associated with an entity. During a discovery phase in which the cloud platform 106 may be configured to operate, in which devices are discovered by the cloud platform 106, or during a normal operating mode of the cloud platform 106, metadata events may be added to the metadata topic 314 to update entities, relationships, and events of the database 160, e.g., to establish a graph projection.
[0299] In some embodiments, all events are added to the raw events topic. In some embodiments, if the event is about how to represent a graphic, the event is added to the metadata topic 314. In some embodiments, if the event represents a new device or set of devices, the device is added to the device tree topic 316. In some embodiments, the device tree data of the device tree topic 316 can be an event type that describes an object or asset discovered by the cloud platform 106, including relationships containing the object and other objects of similar context.
[0300] The raw events 318 of the raw event topics 312 may be provided to the enrichment manager 206 for enrichment. The enrichment manager 206 may receive the graphic projections from the graphic projection database 162 and enrich the raw events 318 based on the context of the graphic projections. In some embodiments, the enrichment manager 206 may enrich the raw events 318 based on one or more user rules. For example, a rule may be an indication to enrich an asset shown within the field of view of a camera, where an event is a frame or set of frames captured by the camera. The enriched events may be enriched based on a target. For example, the events may be enriched based on the system that will receive the events. In this regard, the events may be enriched at multiple different times for multiple different receiving systems.
[0301] Enrichment can help the system operate quickly. For example, a person can scan a badge at a door. An application can look up the user of the badge using the badge number. Additionally, the application can look up devices and places associated with the scanner. However, by performing multiple searches, the application's processing may be slow. However, through enrichment by the enrichment manager 206, for example, a telemetry event of scanning a door badge can have floor indications, user identification, etc. added, so that the receiving application can act on the event and context information without having to search and / or retrieve context information.
[0302] Rich events can be added to event topics 324. Various systems can subscribe to event topics 324. For example, graph projection processor 326 can update the projection of graph projection database 162 based on the rich events. For example, telemetry data can be added to graph projection database 162, the state of the device can be added to graph projection database 162, etc. The persistence service 328 can persist the rich events in event database 332. In addition, publisher 330 can provide the rich events to applications 110, for example, to specific applications that subscribe to the rich events.
[0303] Reference now Figure 4 , according to an exemplary embodiment, a twin manager 108 is shown that generates projections and operates with components of the cloud platform 106 to enrich events. The twin manager 108 includes an event manager 404. The event manager can receive data from a user device and / or another system. The event manager 404 can receive additions of event types, additions of event streams, new events, and / or new event subscriptions. Based on the received information, the event manager 404 can be configured to update the topic to subscription mapping 408. In addition, if the received information indicates a change in the graphic projection of the graphic projection database 162, the event manager 404 can be configured to generate a change event for the change feed.
[0304] The twin manager 108 includes a query manager 402. The query manager 402 may receive a query or a publication from a user device or another system. The query manager 402 may be configured to query the entity, relationship, and / or event database 160 based on the query. The ontology received from the architecture and ontology 154 may define the query that the query manager 402 performs on the database 160. In some embodiments, the query manager 402 may be configured to update or insert new entities, relationships, and / or events into the database 160. In some embodiments, the query manager 402 constructs a query or determines whether to update or insert information into the database 160 based on an access control list received from the policy manager 158. In this regard, the policy manager 158 and the query manager 402 may verify whether an entity requesting information by querying or sending a publication of new information has an appropriate access policy.
[0305] The policy manager 158 is shown receiving a projection from the graph projection generator 210. In some embodiments, the policy manager 158 may receive the projection from the graph projection database 162. The policy manager 158 may be configured to receive a request to access information and may examine the graph to determine whether the requesting entity has appropriate access rights to the information. The policy manager 158 may provide an access control list determined from the graph projection to the query manager 402. The policy manager 158 may provide the access control list to the architecture and ontology 154 for use in providing the ontology to the enrichment manager 206 and / or for use in user-determined projection rules for the graph projection generator 210.
[0306] Reference now Figure 5 , according to an exemplary embodiment, a pre-processing workflow 500 performed by the cloud platform 106 to pre-process an event is shown. An event can be received by the platform 106. In step 502, the cloud platform 106 can filter the event. The event can be filtered into an architecture discovery (e.g., a new message architecture) to filter into an existing architecture message category. In addition, in step 502, the cloud platform 106 can add a subscription identifier and entity information to the event. For example, in step 504, the subscription identifier can be looked up via the topic-to-subscription mapping 408. The entity information can indicate an entity related to the event, such as an entity that created the event. For example, a thermostat (entity) may have generated a temperature measurement (entity).
[0307] If the message is for architecture discovery (step 506), the cloud platform 106 can publish the architecture used in the message in the architecture and ontology 154, or alternatively proceed to step 512. In step 508, the cloud platform 106 can find a valid message architecture from the architecture and ontology 154. In step 512, the cloud platform 106 can determine whether the architecture of the event is valid or invalid based on the valid message architecture. In step 514, if the architecture is invalid, the event can be added to the invalid architecture dead letter, where the invalid architecture event is stored. If the architecture is valid, the event can be routed to the message topic based on the type of the message in step 516, such as whether the event is metadata, raw event, etc.
[0308] Reference now Figure 6, according to an exemplary embodiment, a discovery workflow 600 for discovering new entities from metadata 314 and device tree 322 performed by cloud platform 106 is shown. In step 602, cloud platform 106 can receive metadata 314 and start a process timer. In step 604, cloud platform 106 can transform and map devices, types, and capabilities. Cloud platform 106 can reference missing types to architectural mappings. In step 610, cloud platform 106 can look up reference mappings for metadata, entity definitions for metadata, tenants associated with metadata, and / or other information for entity relationship sets. In step 608, the new device type can be maintained as metadata 616 and added to metadata device table 614.
[0309] In step 628, the cloud platform 106 may start a process timer in response to receiving the device tree 322. The device tree 322 may be analyzed to determine what action (e.g., predicate, operation, or subject) contained within the device tree 322 will be performed. The action may be an insert, update, or delete command for a graphical projection. In step 618, the cloud platform 106 may transform or map the device tree based on metadata stored in the device metadata 616. In step 634, the cloud platform 106 may evaluate the process and determine whether the message has been processed. In step 620, the processor cost may be calculated, and in step 622, the event may be recorded in the processing record 613. In step 636, new data for insertion, update, and / or deletion may be published.
[0310] In response to receiving the device tree 322, the cloud platform 106 can start a process timer in step 628. The cloud platform 106 can analyze the device tree 322 for predicates, operations, and / or subjects to construct insert commands, update commands, and / or delete commands 632.
[0311] Reference now Figure 7 , according to an exemplary embodiment, a projection workflow 700 performed by the twin manager 108 is shown. In step 702, the twin manager 108 can receive a change feed event from the change feed generator 152. Based on the change feed event, in step 704, the twin manager 108 can generate a graphic projection and store the graphic projection. The twin manager 108 can edit an existing graphic projection of the graphic projection database 162 based on the change feed event. The twin manager 108 can replace the existing graphic projection of the graphic projection database 162 with a new graphic projection created in response to receiving the change feed event.
[0312] The twin manager 108 may receive a query from the query manager 706. The query may be a query for information about a graph projection and / or a query for the graph projection itself. The query may originate from a requesting application, system, or user device. In step 708, the twin manager 108 may retrieve the graph projection based on a policy of the requesting system.
[0313] The twin manager 108 can retrieve a policy from the policy database 161 to determine which graph projection the query system can access. In response to retrieving the appropriate graph projection from the graph projection database 162, the twin manager 108 can construct a query response that contains specific information from the graph projection and / or the graph projection itself. The twin manager 108 can return the query response to the query manager 706.
[0314] Reference now Figure 8 , according to an exemplary embodiment, an enrichment workflow 800 performed by the cloud platform 106 to enrich an event with contextual information is shown. The cloud platform 106 receives an internal event 802, metadata 320, a device tree 322, and a raw event 314. The internal event 802 may be an event that is created by the building data platform 100 and needs to be enriched. Each data element received may be enriched according to the workflow 800.
[0315] In step 806, in response to receiving the event, a process timer can be started. In step 808, the cloud platform 106 can obtain the event type of the event from the event type storage device 812 and the projection type from the projection type storage device 814. In this regard, the projection type specific to the event can be retrieved. The identified specific projection can be retrieved in step 810, and the entities and relationships specifically for enriching the event can be retrieved from the graph projection. Based on the entities and relationships, a custom enrichment for the event can be generated in step 816.
[0316] In some embodiments, some events may not be associated with any event type and / or projection type. In response to identifying an event that cannot be enriched, the cloud platform 106 can add the event to a dead letter 820. The dead letter 820 can be examined by a user and / or system to identify errors in the operation of the cloud platform 106 and / or problems with the system that created the event.
[0317] Reference now Fig. 9 , according to an exemplary embodiment, a command processing workflow 900 performed by the cloud platform 106 is shown, wherein a command is sent to a device or transmitted to an external system via a connection agent. The cloud platform 106 can receive internal commands 902 and / or external commands 904. The internal command 902 can be a command generated by a component of the building data platform 100. The external command 904 can be a command generated by an external device or system, such as a user device 176.
[0318] In step 906, the internal command 902 and / or the external command 904 may be received and a process timer may be started. In step 908, the cloud platform 106 may authorize the command to determine whether the entity requesting the command is authorized to execute the command. For example, the cloud platform 106 may search the graph projection in the graph projection database 162 for policies and capabilities to determine whether the requesting entity has the authority to issue the command that the entity is issuing.
[0319] If the command is not authorized, then at step 910, the event may be logged in a processing log 912. At step 914, the cloud platform 106 may determine whether the command is a command for a device of the building subsystem 122, e.g., a command-to-device (C2D) command or a command for an external system to be processed via a connector, a command-to-connector (C2C) command. In response to the command being a C2D command, at step 916, the cloud platform 106 may queue a message to be sent to the device via a device hub. The cloud platform 106 may query the graph projection and identify the device hub responsible for processing the device command.
[0320] If the command is a C2C command, the cloud platform 106 can select a connection agent 918 in step 922. The connection agent 918 can be a component configured to communicate and integrate with an external system (e.g., external system 920). For example, an office program suite, a virtual meeting platform, an email server, etc. can be integrated with the building data platform 100 via the connection agent 918. The cloud platform 106 can select an appropriate connection agent for the command through the graphic projection of the graphic projection database 162.
[0321] Reference now Fig.10 , according to an exemplary embodiment, a messaging workflow 1000 performed by a cloud platform 106 is shown, wherein messages for a building subsystem 122 are received via an edge platform 102 and commands for the building subsystem 122 are transmitted to the building subsystem 122 via the edge platform 102. The cloud platform 106 may receive data events from the building subsystem 122 via the edge platform 102 through device hubs 1002 and 1004 dedicated to devices of the building subsystem 122.
[0322] Device hubs 1002 and 1004 can publish events into topics 1006 and 1008. A source identifier 1010 subscribed to topics 1006 and 1008 can look up the identifier of the device hub based on the identifier of the device and publish the event to a data feed topic 1011 associated with the device hub in a device hub identifier 1012 mapped to the device identifier. An event handler 1018 can provide the event to the preprocessor 202.
[0323] Commands process C2D commands of workflow 900. Commands may be published in C2D message topic 1014. Command processor 1016, which subscribes to C2D message topic 1014, may read the C2D messages and provide the C2D commands to the appropriate device topic, such as topic 1006 or topic 1008. Device hubs 1002 and / or 1004 may pick up the C2D commands and operate building subsystems 122 via the C2D commands.
[0324] Reference now Fig.11 , according to an exemplary embodiment, a graph projection 1100 of the twin manager 108 is shown, including application programming interface (API) data, capability data, policy data, and services. The graph projection 1100 includes nodes 1102 to 1140 and edges 1150 to 1172. The nodes 1102 to 1140 and the edges 1150 to 1172 are defined according to a key 1101. The nodes 1102 to 1140 represent different types of entities, devices, locations, points, individuals, policies, and software services (e.g., API services). The edges 1150 to 1172 represent relationships between the nodes 1102 to 1140, such as dependency calls, API calls, inferred relationships, and architectural relationships (e.g., BRICK relationships).
[0325] Graphic projection 1100 includes device hub 1102, which may represent a software service that facilitates the transfer of data and commands between cloud platform 106 and devices (e.g., door actuator 1114) of building subsystem 122. Device hub 1102 is associated with connector 1104, external system 1106, and digital asset "door actuator" 1108 via edge 1150, edge 1152, and edge 1154.
[0326] The cloud platform 106 can be configured to identify the device hub 1102, connector 1104, external system 1106 related to the door actuator 1114 by searching the graph projection 1100 and identifying edges 1150 to 1154 and edge 1158. The graph projection 1100 includes a digital representation of a "door actuator" node 1108. The digital asset "door actuator" 1108 includes a "DeviceNameSpace" represented by the node 1108 and related to the digital asset "door actuator" 1108 through an "object property" edge 1156.
[0327] "Door actuator" 1114 has a point and a time series. "Door actuator" 1114 is related to "point A" 1116 through a "has_a" edge 1160. "Door actuator" 1114 is related to "point B" 1118 through a "has_A" edge 1158. In addition, the time series associated with points A and B are represented by nodes "TS" 1120 and "TS" 1122. The time series is related to points A and B through a "has_a" edge 1164 and a "has_a" edge 1162. The time series "TS" 1120 has specific samples, and samples 1110 and 1112 are each related to "TS" 1120 through edges 1168 and 1166, respectively. Each sample contains a time and a value. Each sample can be an event received from the door actuator, and the cloud platform 106 ingests the event into the entity, relationship, and event database 160, such as into the graph projection 1100.
[0328] Graphic projection 1100 includes building 1134 representing a physical building. Building includes floors represented by floor 1132, which is related to building 1134 by a "has_a" edge from building 1134 to floor 1132. Floors have spaces between floor 1132 and space 1130 indicated by edge "has_a" 1170. Spaces have certain capabilities, for example, being rooms that can be booked for meetings, conferences, private study time, etc. In addition, reservations can be canceled. The capabilities of floor 1132 are represented by capability 1128 that is related to space 1130 by edge 1180. Capability 1128 is related to two different commands, which are command "book a room" 1124 and command "cancel reservation" 1126 that are related to capability 1128 by edges 1184 and 1182, respectively.
[0329] If cloud platform 106 receives a command to reserve a space represented by a node (space 1130 ), cloud platform 106 can search for capabilities 1128 associated with space 1128 in graph projection 1100 to determine whether cloud platform 106 can reserve the room.
[0330] In some embodiments, cloud platform 106 may receive a request to reserve a room in a particular building, such as building 1134. Cloud platform 106 may search graphical projection 1100 to identify a space that has capabilities to be reserved, such as identifying space 1130 based on capabilities 1128 associated with space 1130. Cloud platform 106 may respond to the request with an indication of the space and allow the requesting entity to reserve space 1130.
[0331] Graph projection 1100 includes policies 1136 for floor 1132. Policies 1136 are a related set for floor 1132 based on a "to floor" edge 1174 between policies 136 and floor 1132. Policies 1136 are related to different roles for floor 1132, reading events 1138, and sending commands 1140. Policies 1136 are a set for entity 1103 based on a "has" edge 1151 between entity 1103 and policies 1136.
[0332] The twin manager 108 can identify a policy for a specific entity, such as a user, software application, system, device, etc., based on the policy 1136. For example, if the cloud platform 106 receives a command to reserve space 1130. The cloud platform 106 can communicate with the twin manager 108 to verify that the entity requesting to reserve space 1130 has a policy to reserve space. The twin manager 108 can identify the entity requesting to reserve space as entity 1103 by searching the graph projection 1100. In addition, the twin manager 108 can further identify an edge "has" 1151 between entity 1103 and policy 1136 and an edge 1178 between policy 1136 and command 1140.
[0333] Additionally, the twin manager 108 can identify that the entity 1103 has the capability to command the space 1130 based on the edge 1174 between the policies 1136 and the edge 1170 between the floor 1132 and the space 1130. In response to identifying that the entity 1103 has the capability to reserve the space 1130, the twin manager 108 can provide an indication to the cloud platform 106.
[0334] In addition, if an entity requests an event to read space 1130, such as sample 1110 and sample 1112, the twin manager 108 can respectively identify the edge "has" 1151 between entity 1103 and policy 1136, the edge 1178 between policy 1136 and read event 1138, the edge 1174 between policy 1136 and floor 1132, the "has_a" edge 1170 between floor 1132 and space 1130, the edge 1168 between space 1130 and door actuator 1114, the edge 1160 between door actuator 1114 and point A 1116, the "has_a" edge 1164 between point A 1116 and TS 1120, and the edges 1168 and 1166 between TS 1120 and samples 1110 and 1112.
[0335] Reference now Fig.12 , according to an exemplary embodiment, a graph projection 1200 of the twin manager 108 is shown, including application programming interface (API) data, capability data, policy data, and services. The graph projection 1200 includes Fig.11 1100. The graph projection 1200 includes a connection agent 1254 associated with the capability 1128 via an edge 1298a. The connection agent 1254 can be a node representing a software application that is configured to facilitate a connection with another software application. In some embodiments, the cloud platform 106 can identify the system that implements the capability 1128 by identifying the edge 1298a between the capability 1128 and the connection agent 1254.
[0336] Connectivity agent 1254 is associated with an agent that optimizes space 1256 via edge 1298b. The agent represented by node 1256 can reserve and unreserve the space represented by node 1130 based on edge 1298b between connectivity agent 1254 and node 1256 and edge 1298a between capability 1128 and connectivity agent 1254.
[0337] Connection proxy 1254 is related to cluster 1208 via edge 1298c. Cluster 1208 is related to connector B 1201 via edge 1298e and to connector A 1206 via edge 1298d. Connector A 1206 is related to external subscription service 1204. Connection proxy 1210 is related to cluster 1208 via edge 1211, which represents the remaining call of the connection proxy represented by node 1210 to the cluster represented by cluster 1208.
[0338] The connection agent 1210 is associated with the virtual conference platform 1212 through an edge 1254. The node 1212 represents an external system, which represents a virtual conference platform. The connection agent represented by the node 1210 can represent a software component that facilitates the connection between the cloud platform 106 and the virtual conference platform represented by the node 1212. When the cloud platform 106 needs to communicate with the virtual conference platform represented by the node 1212, the cloud platform 106 can identify the edge 1254 between the connection agent 1210 and the virtual conference platform 1212, and select the connection agent represented by the node 1210 to facilitate the communication with the virtual conference platform represented by the node 1212.
[0339] Capability node 1218 can be connected to connection agent 1210 via edge 1260. Capability 1218 can be a capability of the virtual conference platform represented by node 1212 and can be related to node 1212 through edge 1260 to connection agent 1210 and edge 1254 between connection agent 1210 and node 1212. Capability 1218 can define the capabilities of the virtual conference platform represented by node 1212. Capabilities can be an invite bob command represented by node 1216 and an email to bob command represented by node 1214. Capability 1218 can be linked to node 1220 representing user Bob. Cloud platform 106 can facilitate an email command to send an email to user Bob through an email service represented by node 1204. In addition, cloud platform 106 can facilitate sending an invitation to a virtual meeting through the virtual conference platform represented by node 1212.
[0340] Node 1220 for user Bob may be associated with policy 1136 via a “has” edge 1264. Additionally, node 1220 may have a “check policy” edge 1266 with a portal node 1224. Portal node 1224 has an edge 1268 to policy node 1136. Portal node 1224 has an edge 1223 to node 1226 representing a user input manager (UIM). UIM node 1226 has an edge 1223 to device API node 1228. Door actuator node 1114 has an edge 1274 to device API node 1228. Door actuator 1114 has an edge 1235 to connector virtual object 1234. Device API node 1228 may be an API for door actuator 1114.
[0341] The device API node 1228 is associated with the transport connection agent 1230 via edge 1229. The transport connection agent 1230 is associated with the device hub 1232 via edge 1278. The device hub represented by node 1232 can be a software component that communicates data and commands for the door actuator 1114. The cloud platform 106 can identify the location of the data stored within the graphic projection 1200 received from the door actuator by identifying nodes and edges between points 1116 and 1118 and the device hub node 1232. Similarly, the cloud platform 1208 can identify commands for the door actuator that can be facilitated by the device hub represented by node 1232, such as by identifying edges between the device hub node 1232 and the open door node 1252 and the lock door node 1250. The door actuator 114 has an edge "mapped assets" 1180 between the node 1114 and the capability node 1248. Capability node 1248 and nodes 1252 and 1250 are linked by edges 1296 and 1294 .
[0342] Device hub 1232 is linked to cluster 1236 via edge 1284. Cluster 1236 is linked to connector A 1240 and connector B 1238 through edge 1286 and edge 1288. Connector A 1240 and connector B 1238 are linked to external system 1244 via edges 1288 and 1290. External system 1244 is linked to door actuator 1242 via edge 1292.
[0343] Reference now Fig.13 , according to an exemplary embodiment, a graph projection 1300 of the twin manager 108 is shown, including devices and device capability data. The graph projection 1300 includes nodes 1302 to 1356 and edges 1260 to 1398f. The cloud platform 106 can search the graph projection 1300 to identify the capabilities of different pieces of equipment.
[0344] Building 120 node 1304 represents a specific building that contains two floors. Floor 1 node 1302 is linked to building 120 node 1304 via edge 1360, and floor 2 node 1306 is linked to building 120 node 1304 via edge 1362. Floor 2 contains a specific room 2023 represented by edge 1364 between floor 2 node 1306 and room 2023 node 1308. Room 2023 contains multiple pieces of equipment. Lights represented by light node 1316, bedside light node 1314, bedside light node 1312, and hallway light node 1310 are related to room 2023 node 1308 via edges 1366, 1372, 1370, and 1368.
[0345] The light represented by light node 1316 is associated with light connector 1326 via edge 1384. Light connector 1326 is associated with a plurality of commands for the light represented by light node 1316. The commands may be a brightness set point 1324, an on command 1326, and a hue set point 1328. Cloud platform 106 may receive a request identifying commands for the light represented by light 1316, and may identify nodes 1324 to 1328 and provide indications of the commands represented by nodes 1324 to 1328 to the requesting entity. The requesting entity may then send commands for the commands represented by nodes 1324 to 1328.
[0346] Bedside lamp node 1314 is linked to bedside lamp connector 1381 via edge 1313. Connector 1381 is associated with commands for the bedside lamp represented by bedside lamp node 1314 via edges 1392, 1396, and 1394. The command nodes are brightness setpoint node 1332, on command node 1334, and color command 1340. Corridor light 1310 is associated with corridor light connector 1346 via edge 1398d. Corridor light connector 1346 is linked to a plurality of commands for corridor light node 1310 via edges 1398g, 1398f, and 1398e. Commands are represented by on command node 1352, hue setpoint node 1350, and bulb activity node 1348.
[0347] Graph projection 1300 includes namespace node 1322, which is related to server A node 1318 and server B node 1320 via edges 1374 and 1376. Namespace node 1322 is related to bedside lamp connector 1381, bedside lamp connector 1344, and hallway lamp connector 1346 via edges 1382, 1380, and 1378.
[0348] Reference now Fig.14 , according to an exemplary embodiment, a block diagram of a user interaction manager 1402 that processes user queries and requests is shown. The user interaction manager 1402 can be a component of the cloud platform 106. In some embodiments, the user interaction manager 1402 is a system separate from the cloud platform 106. The user interaction manager 1402 includes a processor 1404 and a memory 1406. The processor 1404 and the memory 1406 can be connected to the reference Figure 1 The processors and memories described are similar or identical.
[0349] The user interaction manager 1402 receives an APPLE query from the user device 176. The user interaction manager 1402 may be configured to query the graph based on the APPLE query, and to generate a query response based on the APPLE query and return the query response to the user device 176. Fig.14 The user device 176 is shown in FIG. 1 to send an APPLE query to the user interaction manager 1402 and receive a query response, but any computing system may send queries and receive query responses from the user interaction manager 1402, such as the application 110, the building subsystem 122, etc.
[0350] The APPLE query may include asset parameters 1410, point parameters 1412, person parameters 1414, location parameters 1416, and event parameters 1418 that the query parser 1408 of the user interaction manager 1402 may utilize when querying the graph projection. The graph parser 1408 may query a graph having entities 1420 and / or relationships 1426, which may indicate capabilities 1434, commands 1436, schema types 1438, and / or entity relationship histories 1440.
[0351] The user interaction manager 1402 may analyze event type records 1422, subscriptions to events 1424, filter related events 1428, validate events 1430, identify event history 1442, and perform event enrichment 1444. For example, an event received from a device hub 1452 at a portal 1454 may be validated against a schema. If the validator 1430 determines that the entity does not have a valid schema, the validator 1430 may add the event to a dead letter 1456.
[0352] The policy evaluator 1432 of the user interaction manager 1402 can determine whether the user of the user device 176 (or another system or application) has the appropriate policy to view the information of the graphic and / or issue the command indicated by the user device 176. The policy evaluator 1432 can determine whether to implement the command based on the command policy for the user device 176 that can be indicated by the graphic projection. In addition, the policy evaluator 1432 can determine whether to respond to the query based on whether the user device 176 has the right to view the queried information. The policy evaluator 1432 can be configured to generate a policy projection 1476. Data access 1446 and 1448 can provide access to assets, points, individuals, locations, and events. Data access 1446 and / or 1448 can retrieve data for the building subsystem 122 via a connector 1474 and / or via a database 1468 containing entities 1472 and relationships 1470. The data retention layer 1450 can retain a record of all queries and query responses.
[0353] User interaction manager 1402 can provide a UI for provisioning service 130 to provision tenants. Tenant management system can provide tenant and / or subscription services to generate new customer subscriptions, for example, subscriptions for tenants of a building. Similarly, provisioning service 130 can receive policy and / or device management commands from tenant management system 1478 for creating graphical projections for customer subscriptions.
[0354] Reference now Fig.15, according to an exemplary embodiment, a process 1500 is shown in which a security dashboard 1502 communicates with a building data platform 100 to check information about a device and command the device. The process 1500 can be performed by the building data platform 100. In some embodiments, the twin manager 108, the application 110, and / or the cloud platform 106 can perform the process 1500. Fig.15 , a security dashboard 1502, a user interaction manager 1402, a cache 1504, a device interface manager 1506, a policy manager 158, and a transport manager 1510 are shown to perform the process 1500. The aforementioned components may be components of the application 110, the twin manager 108, and the cloud platform 106.
[0355] In step 1512, security dashboard 1502 may receive a command from a user to view doors with active alarms on a particular floor, i.e., the second floor of the building. In some embodiments, security dashboard 1502 is an application executed by application 110. In some embodiments, the user interacts with security dashboard 1502 via user device 176.
[0356] In step 1514, the security dashboard 1502 queries the user interaction manager 1402 for assets and events, specifically doors (assets) on the second floor (assets) that have active alarms (events). In step 1516, the user interaction manager 1402 may obtain read permissions to the entity and relationship collection from the policy manager 158. The policy manager 158 may determine which entities and / or events the user may access based on the policies indicated by the graphic projection of the graphic projection database 162. The policy manager 158 may determine whether the user has permission to read the entities and / or relationships.
[0357] In response to the user having the right to read the entities and / or relationships, the policy manager 158 may send a granted indication to the user interaction manager 1402 in step 1518. In step 1520, the user interaction manager may obtain read permission for events on the second floor from the policy manager 158. The policy manager 158 may determine whether the user has access to the events on the second floor by searching the graphical projection, and may respond to the user interaction manager 1402 with a granted message in step 1522 in response to determining that the user has access to the events on the second floor.
[0358] In response to receiving permission to read entities, relationships, and events of the second floor, the user interaction manager 1402 may read entity relationships and events from the cache 1504. In some embodiments, the user interaction manager 1402 may read entities, relationships, and events from the graphical projection in step 1524.
[0359] In step 1526, the cache 1504 may return the requested data of step 1534 to the user interaction manager 1402. In step 1528, the user interaction manager 1402 may return the filtered assets with asset capabilities. For example, all doors on the second floor and the ability to command each door to lock or unlock may be returned in step 1528. In step 1530, the security dashboard 1502 may display the doors on the second floor with active alarms and the capabilities of the doors.
[0360] In step 1532, the user may click on a specific door displayed in step 1530, such as door 13, and select a command to lock the door. In step 1534, the security dashboard 1502 may send a door lock command for door 13 to the user interaction manager 1402. In step 1536, the user interaction manager 1402 may obtain a send command permission for door 13 from the policy manager 158. The policy manager 158 may determine whether the user has the authority to command door 13 to lock based on the graphic projection. In response to detecting that the user does have a policy to lock door 13, in step 1538, the policy manager 158 may send a granted message to the device interface manager 1506. In steps 1540 to 1546, the device manager 1506 may send a command to lock door 13 to the transmission manager 1510. The transmission manager 1510 may facilitate the command to lock door 13. Prior to implementing the command, the device interface manager 1506 may communicate with the policy manager 158 to verify permission to command the gate, and in response to determining that the permission exists, the policy manager 158 may send a granted message to the device interface manager 1506 in step 1544 .
[0361] In step 1548, a confirmation message indicating that the command has been sent may be sent to the device interface manager 1506 via the transmission manager 1510. The device interface manager 1506 may send a success message 1550 to the user interaction manager 1402. In step 1552, the user interaction manager 1402 may send the success message to the security dashboard 1502. In step 1554, the security dashboard 1502 may display a message to the user that the command has been successfully sent to the door 13.
[0362] Reference now Fig.16 , according to an exemplary embodiment, a flow chart of a process 1600 that can be performed by the cloud platform 106 is shown, in which events of building equipment are enriched with graphical contextual information. In some embodiments, the cloud platform 106 can be configured to perform the process 1600. In addition, any computing device or system described herein can be configured to perform the process 1600.
[0363] In step 1602, the cloud platform 106 receives events from building equipment or services. In some embodiments, the cloud platform 106 receives non-event data, such as time series data streams, messages, etc., and normalizes the data into event data. An event may contain one or more parameters, such as a data value (e.g., temperature, equipment status, etc.), the time at which the event occurred, etc. In some embodiments, the cloud platform 106 receives events from event sources, such as cloud data, NC4, weather data services, the cloud platform 106 itself (e.g., events, enriched events, etc.), and / or any other system or device.
[0364] In step 1604, the cloud platform 106 can identify one or more entities and / or one or more relationships of the graph that are related to the event. The entity can be an indication of the location of the event (e.g., what room, what floor, what building the event occurred in), the building entity that consumed the event data, other entities affected by the event (e.g., a temperature set point change in one room affects the temperature of an adjacent room), etc. The relationship can indicate how the event is related to the entity. For example, the relationship "isLocatedIn" can be added to indicate that the sensor that generated the event is located in a specific space.
[0365] In some embodiments, the cloud platform 106 identifies one or more entities and one or more relationships from the graph projection. The graph projection can be a graph projection specific to a particular subscriber (e.g., user or organization) of the cloud platform 106. In some embodiments, the cloud platform 106 receives the graph projection from a graph projection database 162.
[0366] In step 1606, the cloud platform 106 generates an enriched event using the event and the one or more entities and one or more relationships of step 1604. The cloud platform 106 can add multiple attributes to the event based on the entities and relationships. In some embodiments, the cloud platform 106 generates an enriched event package containing all data of the enriched event and the one or more entities and one or more relationships identified in step 1604.
[0367] In step 1608, the cloud platform 106 can provide the enriched event of step 1066 to one or more applications that are configured to operate based on the enriched event. In some embodiments, the application 110 can receive the enriched event and operate based on the data of the event and the contextual information (e.g., entities and relationships) of the enriched event. For example, for an application that controls the temperature of a space, in addition to the identification of the space and the VAV box of the space, the enriched event can also contain a temperature measurement of the space. The application can generate a command for the VAV box based on the temperature measurement and transmit the temperature measurement to the identified VAV box of the enriched event.
[0368] Reference now Fig.17, according to an exemplary embodiment, a process 1700 that may be performed by the twin manager 108 is shown, wherein a change feed of events records modifications to a graph. The twin manager 108 may be configured to perform the process 1700. In some embodiments, components of the twin manager 108 are configured to perform the process 1700, such as the change feed generator 152 and / or the graph projection database 162. In some embodiments, any computing device described herein is configured to perform the process 1700.
[0369] In step 1702, the twin manager 108 receives one or more changes to the graph. The change can modify one or more nodes or one or more edges of the graph. For example, the change can be to add a new node or edge, delete an existing node or edge, or modify an existing node or edge of the graph. In some embodiments, the twin manager 108 receives the modification from a user device 176, such as a user providing the modification to the graph to the twin manager 108. In some embodiments, the modification is received as an event indicating a change to the graph, such as the event is metadata 320 or a device tree 322.
[0370] In step 1704, the twin manager 108 generates a change feed event that records the changes that modify one or more nodes and / or one or more edges. An event can be a data packet containing information about the event time and the time when the event occurred. In some embodiments, the event contains an indication of how the graph was changed, for example, what nodes and / or edges of the graph have changed and how those nodes and / or edges have changed. The twin manager 108 can implement the changes of step 1702 on the graph and also generate an event that records the changes to the graph.
[0371] In step 1706, the twin manager 108 may add events to a change feed. The change feed may contain multiple change events for different changes to the graph. The change feed may be a topic to which certain applications and / or systems (e.g., application 110) subscribe. In step 1706, one or more applications that operate based on the graph may receive the change feed. In this regard, the applications and / or systems may receive the change feed events and update their graph storage based on the change feed. This may allow applications and / or systems to update their graphs without receiving the entire graph, but only receiving change indications. In addition, the twin manager 108 and / or any other system may generate a graph at one or more different times based on the events of the change feed to track the configuration of the graph at multiple different times.
[0372] Reference now Fig.18, according to an exemplary embodiment, a flow chart of a process 1800 that may be performed by cloud platform 106 is shown, wherein the graphic recognition capabilities of a piece of equipment are used to operate the piece of equipment. In some embodiments, cloud platform 106 is configured to perform process 1800. In some embodiments, a component of cloud platform 106, such as command processor 136, is configured to perform process 1800. Any computing device described herein may be configured to perform process 1800.
[0373] In step 1802, the cloud platform 106 may identify a capability of a piece of equipment based on a graph of nodes and edges, wherein a first node in the nodes represents a capability and a second node in the nodes represents a piece of equipment, wherein one or more edges relate the first node and the second node. In some embodiments, the cloud platform 106 may receive a request for information about the capabilities of a piece of equipment, such as from a user request via a user device 176, or from a device of a building subsystem 122 (e.g., a thermostat may request to control a VAV box). The cloud platform 106 may identify capabilities, operational commands that a piece of equipment may perform, by identifying a capability node related to a node for a piece of equipment through one or more edges and / or nodes between a node for capabilities and a node for a piece of equipment. The cloud platform 106 may analyze a graph projection received from the twin manager 108 to identify capabilities.
[0374] In some embodiments, an entity may have capabilities originating from different systems. For example, a room may be an entity that has temperature control capabilities based on the room's HVAC system. A room may also have a booking capability to reserve the room based on a room reservation and / or conference scheduling system.
[0375] In step 1804, the cloud platform 106 may receive commands to operate the piece of equipment based on the capabilities identified from the graphic in step 1802. In some embodiments, the cloud platform 106 transmits the capabilities to a requesting entity, such as a user device 176, an application 110, a device of a building subsystem 122, etc. The requesting entity may check the capabilities and issue commands for the capabilities.
[0376] In step 1806, the cloud platform 106 may provide the command to the piece of equipment. In some embodiments, the cloud platform 106 identifies a software component that is configured to manage messaging of the piece of equipment. The cloud platform 106 may identify the software component from a graph. For example, a node of the graph may represent a software component, and one or more edges or nodes may relate the software component node to a node representing a piece of equipment. The cloud platform 106 may identify the software component by identifying an edge and / or node that relates the software component node to a node representing a piece of equipment. The cloud platform 106 may provide the command to the software component to process the command to the piece of equipment.
[0377] Reference now Fig.19 , according to an exemplary embodiment, a process 1900 is shown in which the cloud platform 106 operates different services related to graphics. In some embodiments, the process 1900 is performed by the cloud platform 106. In some embodiments, any computing device described herein is configured to perform the process 1900.
[0378] In step 1902, the cloud platform 106 receives instructions to perform an action of an entity. The action may be controlling a piece of building equipment. Implementing commands with an external system, such as generating a virtual meeting via a virtual meeting platform, may send an email via an email service, etc.
[0379] In step 1904, the cloud platform 106 can identify a service that is configured to perform an action based on a graph comprising nodes and edges. For example, if the command is to send an email, the cloud platform 106 can identify an email service by identifying an email service node of the graph. If the action is to command a piece of building equipment to operate, the cloud platform 106 can identify a node of the graph representing an equipment hub that processes messages for the piece of building equipment.
[0380] The nodes of the graph can represent various devices or software components. The edges can represent communication actions between various devices or software components. For example, an edge can represent an API call between various software components. Fig.12 , there may be an API call to the device hub 1232 to implement the control command for the door actuator 1242. The API call may be between other connected software components, such as the cluster 1236, connector A 1240, connector B 1238, and the external system 1244. To implement the control command for the door actuator 1242, the device hub 1232 may make an API call 1284 to the cluster 1236, which in turn may make API calls 1286 and / or 1288 to connector A 1240 and connector B 1238. Connector A 1240 may make an API call to the external system 1244, namely API call 1288. Similarly, connector B 1238 may make an API call 1290 to the external system 1244. The external system 1244 may make an API call 1292 to the door actuator 1242 to implement the requested command.
[0381] Similarly, if the command is to send an email via email service 1204, connection broker 1254 can coordinate the connection of cloud platform 106 to email service 1204 and can make one or more API calls to implement the email command. Connection broker 1254 can make API call 1298c to cluster 1208, which can make API call 1298d to connector A, which can make API call 1298f to send the email via email service 1204.
[0382] In step 1906, the cloud platform 106 causes the services identified in step 1904 to perform operations based on the communication action represented by the edge. For example, the cloud platform 106 can identify a set of API calls that implement the action. The API calls can be identified based in part on the graph. For example, to implement sending an email, the cloud platform 106 can identify an API call 1298c made by the connection proxy 1254, an API call 1298d made by the cluster 1208, and an API call 1298f made by the connector A 1206. The cloud platform 106 can cause each service (i.e., the connection proxy 1254, the cluster 1208, and the connector A 1206) to make the appropriate API call to implement the action.
[0383] Reference now Fig. 20 , according to an exemplary embodiment, a process 2000 that can be performed by cloud platform 106 is shown, in which information and control capabilities are provided to users or services based on policies stored in a graph. Cloud platform 106 can be configured to perform process 2000. In some embodiments, any computing device or system described herein can be configured to perform process 2000.
[0384] In step 2002, the cloud platform 106 receives a request from a user and / or service to view a portion of a graph of nodes and edges. The nodes may represent entities of a building, and the edges may represent relationships between entities of the building. The request may be received from the user via the user device 176. In some embodiments, the request may be received from the application 110 and / or the building subsystem 122.
[0385] In step 2004, the cloud platform 106 can determine whether the user and / or service has permission to view a portion of the graph based on the policy indicated by one or more nodes and / or relationships of the graph. For example, the graph can indicate a policy for viewing information of the graph. For example, referring to Fig.11 , entity 1103 has policy 1136 to read event 1138 to floor 1132 1151. In this regard, if the user and / or service is an entity with a policy to read events, the user and / or service can view events 110 and / or 1112.
[0386] Policies for users and / or services can be cascaded through the graph, for example, if a user and / or service has a policy to read information of a higher-level node, the user and / or service can also use a lower-level node. For example, cloud platform 106 can identify that entity 1103 has policy 1136 from 1151 to floor 1132 via edge 1174. Because door actuator 1114 is an asset of space 1130 indicated by edge 1168, and space 1130 is a space of floor 1132 indicated by edge 1170, cloud platform 106 can identify an event that entity 1103 can access door actuator 1114.
[0387] In step 2006, the cloud platform 106 may provide an indication of the portion of the graphic to the user and / or service in response to determining that the policy indicates that the user and / or service has the right to view the portion of the graphic. In some embodiments, the cloud platform 106 may cause a display device of the user device 176 to display the indication of the portion of the graphic. In step 2008, the cloud platform 106 may receive a command for a piece of equipment. In some embodiments, the command may be a command to operate a piece of equipment. In some embodiments, the command is a command to perform an operation on behalf of the user, such as sending an email to the user, scheduling a meeting with the user, etc.
[0388] In step 2010, the cloud platform 106 may determine whether the user or service has the right to execute the command based on the policy indicated by one or more nodes and / or edges of the graph. For example, the policy of the graph may indicate that the user and / or service has the right to operate the piece of equipment.
[0389] For example, refer to Fig.12 , user bob 1220 has a send command policy for a specific floor, for example, Bob 1220 has a policy 1264 for send command 1140 via edge 1178. Policy 1136 is set for floor 1132 via edge 1174. Because entity 1103 has a send command policy for floor 1132, any piece of equipment on the floor can be commanded by entity 1103. For example, door actuator 1114 is a piece of equipment in space 1130 indicated by edge 1168. Space 1130 is a space on floor 1132 indicated by edge 1170. Door actuator 1114 has capability 1248 indicated by edge 1180, and the command can be an open door command 1252 or a lock door command 1250 associated with capability 1248 of door actuator 1114 via edges 1296 and 1294.
[0390] The cloud platform 106 can determine that user Bob 1220 has the ability to command door actuator 1114 via the relationship between door actuator 1114 and floor 1132 for which policy 1136 is set. Because user Bob 1220 has the ability to issue commands to floor 1132, all components related to floor 1132 located on floor 1132 are available to the user, for example, door actuator 1114 is a device of space 1130 via edge 1168 and space 1130 is an area of floor 1132 via edge 1170.
[0391] In step 2012, the cloud platform 106 may operate a device to execute the command. In some embodiments, the cloud platform 106 may identify services and / or communication actions to implement such as Fig.19 For example, the cloud platform 106 can utilize the graph to identify a service that processes messaging of a device and can identify a communication action that the service performs to implement the command.
[0392] Reference now Fig.21 , according to an exemplary embodiment, a process 2100 is shown in which a graphic projection is constructed by the twin manager 108. In some embodiments, the twin manager 108 is configured to perform the process 2100. In some embodiments, a component of the twin manager 108, such as the graphic projection manager 156, is configured to perform the process 2100. In some embodiments, any computing device described herein is configured to perform the process 2100.
[0393] In step 2102, the twin manager 108 may receive a request for a graphical projection from the system. For example, a user may request to generate a graphical projection via the user device 176. In some embodiments, the cloud platform 106 receives an indication of a new subscribing consumer, and the cloud platform 106 provides the request to generate a new projection of the subscribing consumer to the twin manager 108. In some embodiments, the twin manager 108 receives a request from the application 110 to generate a graphical projection for a particular application of the application 110.
[0394] In step 2104, the twin manager 108 retrieves projection rules for the system for generating a graph projection. The projection rules can be system-specific ontologies. For example, an ontology can define what types of nodes can be related in what specific ways. For example, an ontology can indicate that one type of node (e.g., a thermostat) should be related to another type of node (e.g., a space). The ontology can indicate each type of node and to what second type of node each type of node can be related. In addition, the projection rules can indicate policies for the system. For example, the projection rules can identify which nodes and / or edges the system has permission to view.
[0395] In step 2106, the twin manager 108 may retrieve entities and / or relationships representing entities of the building and relationships between entities of the building. The twin manager 108 may retrieve all entities and / or relationships from the entity, relationship, and event database 160. In some embodiments, the twin manager 108 retrieves only entities and / or relationships that the projection rules indicate should be included in the projection graph, for example, only entities and / or relationships corresponding to the ontology, or only entities and / or relationships for which the system has an access policy.
[0396] In step 2108, the twin manager 108 may build a graph projection based on the entities and relationships retrieved in step 2106 and the projection rules retrieved in step 2104. In some embodiments, the twin manager 108 may build the graph projection by generating nodes for the entities and generating edges between the nodes to represent the relationships between the entities.
[0397] In some embodiments, the twin manager 108 generates a graph projection based on the ontology. For example, an ontology may indicate that a building node should have an edge to a room node. Another ontology may indicate that a building node should have an edge to a floor node, and a floor node should have an edge to a room node. Therefore, for entity data indicating that building A has floor A and floor A has room A, through the first ontology, a node for building A and an edge from the building A node to the room A node may be generated. For the second ontology, a building A node with an edge to the floor A node may be generated. In addition, the floor A node may have an edge to the room A node.
[0398] In step 2110, the building data platform 100 may perform one or more operations based on the graph projection. In some embodiments, the building data platform 100 may perform event enrichment (e.g., Fig.16 In some embodiments, the building data platform 100 may generate a change feed based on changes in the graphic projection (e.g., as described in Fig.17 In some embodiments, the building data platform 100 can utilize the graphic projection to command and control the entities represented by the graphic projection (e.g., Fig. 20 In some embodiments, the building data platform 100 may utilize a graphical projection to identify services and / or communication commands to an implementation scheme (e.g., Fig.19 ).
[0399] Reference now Fig. 22, according to an exemplary embodiment, a process 2200 is shown in which a graph is queried based on entities and events. The cloud platform 106 can be configured to perform the process 2200. In some embodiments, any computing device described herein can be configured to perform the process 2200.
[0400] In step 2202, the cloud platform 106 receives a query for the graphical information, the query comprising entities and events. The query may be formed by parameters of asset, point, place, location, and event ("APPLE"). The query may indicate one of entity, asset, point place, and location, and the query may further indicate an event. In this regard, the query may search for certain entities with specific events, for example, floors (asset type) with active door alarms (events), doors (asset type) with active door alarms (events), buildings (asset type) with temperature measurements exceeding a specific amount (events), etc.
[0401] In step 2204, the cloud platform 106 queries a graph of information based on the query received in step 2202, wherein the graph contains nodes and edges, the nodes represent entities and events and the edges represent relationships between entities and events. For example, a query can be run against the graph to identify entities associated with a particular event.
[0402] For example, now refer to Fig.11 , if the query is to find a space where the door actuator has a value of 1 at a specific time "a", the cloud platform 106 can be configured to first search the edges and nodes of all spaces within the graph. Next, the cloud platform 106 can select the graph space that is linked to the event node of the door actuator that has a value of 1 at the specific time "a". For example, the cloud platform 106 can determine that space 1130 has an edge 1168 to door actuator 1114, and door actuator 1114 has an edge 1160 to point A 1116, and point A 1116 has an edge to TS 1120, which in turn has an edge 1168 to event node 1110, which has a value of 1 at time "a".
[0403] In step 2206, the cloud platform 106 can generate a query response based on the information queried in step 2204. The query response can include one or more nodes and / or edges of the graph selected by the query. For example, the query response can identify the queried entity. In addition, the query response can identify the queried entity and one or more nodes and / or edges that relate the entity to the queried event. The cloud platform 106 can return the query response to the system that originally made the query, for example, to the user device 176, the application 110, the building subsystem 122, etc.
[0404] Reference now Fig.23, according to an exemplary embodiment, a platform manager 128 of a cloud platform 106 is shown managing tenant and subscription rights with a tenant rights model 2300. The platform manager 128 can be configured to manage rights for various tenants and / or tenant subscriptions for the building data platform 100. The provisioning service 130 can receive data from a user device 176 to create, end, or update a tenant and / or tenant subscription. The provisioning service 130 can cause the subscription service 132 to update the tenant rights model 2300 appropriately.
[0405] In some embodiments, provisioning service 130 is configured to handle license purchases and / or license activations for tenants and / or tenant subscriptions. A user may purchase a license for a particular tenant subscription through provisioning service 130 via user device 176. In response to the purchase of the license, provisioning service 130 may add the rights for the tenant subscription to tenant rights model 2300, thereby activating the purchased license.
[0406] The tenant rights model 2300 may indicate tenants, each indicating a billing boundary. Each tenant may further include one or more subscriptions, specific implementations of the building data platform 100 for the tenant. For example, a retail chain comprising multiple stores may be a tenant, and each store may have a specific subscription. Each subscription may be associated with a specific geographic operating area, such as an indication of computing resources within the geographic operating area used by the subscription. Each subscription may further indicate the rights of the subscription, such as the services, data, or operations of the building data platform 100 that the subscription is authorized to use.
[0407] The rights service 134 may receive a request for rights from a system 2302 (e.g., edge platform 102, twin manager 108, and / or application 110). The request may be a question of whether a particular subscription has authorization for a particular right, for example, the question may be whether a particular subscription has the right to issue a command in response to a request by the system 2302 to issue the command. In some embodiments, while the systems 2302 are running (e.g., processing control commands, enriching events, generating user interfaces, executing control algorithms), they may encounter actions that require rights. In response to encountering an action that requires a right, the system 2302 may communicate with the rights service 134 to determine whether the particular subscription on which the system 2302 is performing the action has the right to the action.
[0408] The platform manager 128 includes a throttling manager 2304 that is configured to perform throttling operations for specific tenants and / or tenant subscriptions. For example, a specific tenant may be entitled to issue a certain number of commands per minute, receive a certain amount of event data per minute from the building system, utilize a certain amount of processing power to run applications, etc. In some embodiments, the throttling manager 2304 may receive operational data from the system 2302 via a meter 2306 of the platform manager 128. In some embodiments, the meter 2306 receives the operational data, analyzes the operational data to determine a metric for a specific tenant subscription (e.g., commands per minute, storage utilized, etc.).
[0409] Throttling manager 2304 may communicate resource throttling commands for a particular consumer subscription to system 2302. For example, if the consumer subscription has rights to a particular number of event enrichment operations and the operational data indicates that a particular number of event enrichment operations have been performed, throttling manager 2304 may send a throttling command for event enrichment (e.g., stop all enrichment for the tenant subscription, cause enrichment to slow down, etc.). In some embodiments, throttling manager 2303 may slow down operational commands for a particular tenant subscription in response to receiving more than a particular number of requests to perform operational commands within a particular time period (e.g., 1,000 requests per minute).
[0410] Meter 2306 can be configured to generate metrics indicating the operation of system 2302 for tenant subscriptions and / or for tenants. Meter 2306 can receive operational data from system 2302 and determine which tenant subscription the operational data is associated with. For example, system 2302 can record which tenant subscription is associated with the operational data and provide an indication of the tenant subscription to meter 2306. The operational data can be a control command, an amount of events received by system 2302 from a building system of a building, etc. The metrics generated by meter 2306 can indicate computing resources used by a particular tenant subscription, storage resources used by a particular tenant subscription, the number of computing requests or commands issued, etc. In some embodiments, meter 2306 is configured to generate bills for particular tenants and / or tenant subscriptions based on the metrics to scale the bills for the tenant subscriptions based on the tenant subscription usage of system 2302.
[0411] In some embodiments, the meter 2306 generates metrics for one or more tenant subscriptions. The metrics can be API requests per second, per day, per month, and the total amount of data delivered. The metrics can indicate the number of messages processed and / or compute cycles used. The metrics can indicate the amount of data storage used and / or the amount of data retained. The metrics can indicate events per second, per day, and / or per month. In addition, the metrics can indicate event subscriptions per second, per day, and / or per month. A tenant can have one or more event subscriptions that indicate how the data platform 100 processes and / or enriches specific events.
[0412] Reference now Fig.24 , according to an exemplary embodiment, a tenant rights model 2200 is shown in more detail. In some embodiments, the tenant rights model 2200 is a graph data structure, one or more tables, or other data storage structure. A tenant can be a billing boundary. A tenant can have multiple subscriptions, such as multiple sites for a single entity, multiple floors of a building rented to various companies, etc. Tenant 2400 is shown as containing three separate subscriptions, namely, Subscription A 2402, Subscription B 2404, and Subscription C 2406. A tenant 2400 can be a specific account associated with a globally unique identifier (GUID) linked to a specific subscription identifier.
[0413] Each of the subscriptions 2402-2406 may be associated with a particular geographic region, such as region 2408 and region 2410. A region may be a particular geographic region, such as a city, county, state, country, continent, grouping of countries (e.g., Asia Pacific (APAC), Europe, Middle East, and Africa (EMEA), etc.), etc. Each of the subscriptions 2402-2406 may be linked to one of the regions 2408 and 2410. Each of the geographic regions 2408 and 2410 may be associated with computing resources (e.g., servers, processors, storage, memory, network infrastructure, etc.) located within each region for implementing the building data platform 100. The computing resources within each region may be a shared number of subscriptions for that region.
[0414] In some embodiments, the building data platform 100 can implement DNS-style data routing to computing resources of a region based on the subscription identifiers of the subscriptions 2402-2406. Regions 2408 and 2410 can address data residency issues, such as data for a particular subscription not leaving a particular geographic region, such as leaving a country.
[0415] Each of the regions 2408 and 2410 may indicate entitlements for subscriptions linked to the regions 2408 and 2410. For example, table 2414 may indicate entitlements for subscription A 2402 and subscription B 2404 linked to region 2408. Table 2412 may indicate entitlements for subscriptions for region 2410, such as subscription C 2406. Tables 2414 and 2412 may indicate all entitlements provided by the building data platform 100 for a particular region and whether each subscription has authorization for a particular entitlement. Entitlements may indicate the services, resources, and / or compute, storage, and / or network usage levels that subscriptions 2402-2406 are entitled to use.
[0416] For example, the building data platform 100 includes platform resources 2413 and 2418 for zones 2408 and 2410, respectively. In zone 2408, the platform resources 2413 include computing resources 2414 and storage resources 2416. In zone 2410, the platform resources 2418 include computing resources 2420 and storage 2422. The building data platform 100 can facilitate resource expansion, thereby providing various amounts of platform resources 2413 to subscription A 2402 and subscription B 2404, respectively, according to the rights for subscription A 2402 and subscription B 2404. Each subscription can be allocated an amount of resources based on whether the subscription is allocated through entitlements, high-level resource usage tiers, or lower-level resource usage tiers.
[0417] An entitlement may be a set of available capabilities within one of the regions 2408 and 2410 to which a subscription 2402-2406 is assigned or not assigned. An entitlement may be the availability of a graph, an event, a command, an event subscription, a gateway operation, and / or a gateway cloud-to-device (C2D) communication. In some embodiments, event subscriptions are created for specific events or event types, such as ER collection, graphs, and / or the ability to enrich rules are available to some subscriptions but not to other subscriptions. The platform manager 128 may provide an API, for example, through the provisioning service 130, the subscription service 132, and / or the entitlement service 134, for managing the entitlements of the tenant entitlement model 2300.
[0418] Reference now Fig.25 , according to an exemplary embodiment, a process 2500 for managing tenant and subscription rights with the tenant rights model 2300 is shown. In some embodiments, the platform manager 128 is configured to perform the process 2500. In some embodiments, any computing device or system described herein can be configured to perform the process 2500.
[0419] In step 2502, the platform manager 128 is configured to receive one or more tenant and / or subscription management requests from the user device 176. For example, the request can be to create a new tenant and / or a new subscription for a tenant, remove an existing tenant and / or an existing subscription, update the rights of a subscription, etc. In some embodiments, the request is associated with a purchase (e.g., to purchase rights to a specific subscription). In some embodiments, the request can indicate management of subscription region relationships, such as management of which region an existing or new subscription is set for. In some embodiments, the rights set for a subscription are limited to rights that can be used for a specific region to which the subscription is linked. In step 2504, the platform manager 128 can update the tenant rights model 2300 based on the request received in step 2502.
[0420] In step 2506, the platform manager 128 receives a request from one of the systems 2302 to perform an operation on a subscription for a zone. For example, one of the systems 2302 may provide a request to the platform manager 128 to determine whether the operation is available for the subscription. For example, the twin manager 108 may process a command request to command a specific piece of equipment of the building subsystem 122 for a specific subscription. The twin manager 108 may send a request to the platform manager 128 to confirm whether the subscription has command rights for a specific zone.
[0421] In response to receiving the request of step 2508, the platform manager 128 can determine whether the subscription has rights to operate the area based on the tenant rights model 2200. For example, the platform manager 128 can search the rights of the specific area to which the subscription is linked to determine whether the subscription has rights to operate. The platform manager 128 can respond to the system with an indication of whether the subscription has rights.
[0422] In step 2510, the building data platform 100 may perform an operation using computing resources linked to a region of a subscription by the tenant entitlement model. For example, the platform manager 128 may respond to a system with an indication that the subscription has entitlements, where the system is a component of the building data platform 100. The system may continue to perform the operation. Additionally, a subscription may be associated with a region of computing resources linked to the building data platform 100. The operation may be performed on computing resources associated with the region.
[0423] In step 2512, the platform manager 128 may perform metering and / or throttling on the subscription based on the operation and / or one or more additional operations. The platform manager 128 may track all operational data associated with the subscription, and the meter 2306 builds operational metrics. The metrics may indicate resource usage of the subscription. Based on the metrics, the platform manager 128 may generate a bill based on the metrics to charge the subscription a certain amount based on the resource usage. Additionally, based on the metrics, the platform manager 128 may implement resource throttling to control the amount of computing and / or storage resources used by the subscription.
[0424] Reference now Fig.26 , according to an exemplary embodiment, a system 2600 is shown that includes an edge platform 100 that performs event enrichment at an edge platform 102 before transmitting the event to a cloud platform 106. The system 2600 includes a building subsystem 122, an edge platform 102, a cloud platform 106, an application 110, and a twin manager 108. The edge platform 102 can receive events from the building subsystem 122 and enrich the events before passing the events to the cloud platform 106. Because the edge platform 102 is located on-premises (e.g., on the edge), the events can be enriched before being passed to other cloud systems and / or used in edge-based analytics running on the edge platform 102. In some embodiments, the processor, memory device, and / or networking device of the edge platform 102 are located on-premises of a building.
[0425] Edge platform 102 may receive events from building subsystem 122. An event may be a data packet describing an event that has occurred, with a timestamp of when the event occurred. An event may be a raw event consisting of content emitted from a production system. However, an event may not contain any intent or knowledge of the system consuming the event. An event may have a specific event type. Enrichment manager 2602 of edge platform 102 may receive events from building subsystem 122. Enrichment manager 2602 may be the same as or similar to enrichment manager 138.
[0426] The enrichment manager 2602 can enrich the events received from the building subsystem 122 based on the event context received and / or retrieved from the lean digital twin 2608 of the edge platform 102. For example, the enrichment manager 2602 can add entity and / or entity relationship information associated with the event to the event to generate an enriched event 2604. Event enrichment can be combined with reference Figures 1 to 3 and Figure 8 The enrichments described are the same or similar. An enriched event 2604 may be an event with additional added properties or attributes that provide context about the event.
[0427] In some embodiments, the enrichment manager 2602 includes multiple event streams. An event stream can be a data enrichment processing stream for a specific event and / or a specific type of event. Each event stream can be linked to a tenant and / or tenant subscription. Each event stream can indicate one or more rules for enriching an event, such as an indication of information added to the event. In this regard, one can apply to multiple event streams and receive different enrichments to generate multiple enriched events. Each enriched event can be provided to a different application or terminal system.
[0428] The edge platform 102 includes an edge application 2610. The edge application 2610 can be similar or identical to the application 110. While the application 110 can run on a cloud system, the edge application 2610 can run locally on the edge platform 102. The edge application 2610 can operate based on the enriched events 2604 and may not need to query the digital twin to obtain context about the event because the enriched events 2604 may already contain the required context. In some embodiments, the edge application 2610 performs analysis (e.g., aggregation, data monitoring, etc.), control algorithms, etc. of the building subsystems 122.
[0429] For example, edge application 2610 may generate control decisions for building subsystems 122 based on enriched events 2604 (e.g., temperature set points for zones, fan speed settings for fans, duct pressure set points, ventilation commands, etc.). In some embodiments, edge application 2610 includes models, such as machine learning models, for predicting features and / or conditions, and / or for operating building subsystems 122. In some embodiments, machine learning is performed at edge platform 102, which results in higher scores than machine learning performed in the cloud because greater amounts of data can be collected more quickly and used for training at the edge.
[0430] In some embodiments, the enrichment manager 2602 operates only when the twin manager 108 is not operating and enriching events. For example, the edge platform 102 may receive an indication that there is an error with the cloud system, such as a network problem, a computing problem, etc. In this regard, the edge platform 102 may take over enriching the events with the enrichment manager 2602 and operating on the events with the edge application 2610. In this regard, enrichment and application operations can be dynamically moved between the edge platform 102 and the cloud. In addition, load balancing can be implemented so that the edge application 2610 enriches some events and these events operate on the edge application, while other events are passed to the cloud platform 106 and / or the twin manager 108 for enrichment and providing the events to the application 110 for operation.
[0431] In some embodiments, by performing enrichment at the edge platform 102, analysis can be performed at the edge platform 102 based on the enrichment events. In this regard, lower latency can be achieved because the analysis and / or control algorithms can be quickly executed at the edge platform 102 and data does not need to be transmitted to the cloud. In some embodiments, the edge application 2610 and / or the machine learning model of the edge application 2610 can be built in the cloud and transmitted to the edge platform 102, and additional learning can be performed at the edge platform 102.
[0432] The edge platform 102 includes a streamlined digital twin 2608. The streamlined digital twin 2608 can be a version of the digital twin 2610 of the twin manager 108. The digital twin 2610 and / or 2608 can be a virtual representation of the building and / or the building subsystems 122 of the building. The digital twin 2610 and / or the digital twin 2608 can be or can include a graph projection database 162, such as one or more graph data structures. The digital twin 2610 and / or the streamlined digital twin 2608 can be a virtual representation of the building and / or the building subsystems 122 of the building. Figures 11 to 13 In some embodiments, the reduced digital twin 2608 is a projection that does not contain all nodes and edges of the full projected graph. The reduced digital twin 2608 may contain only the nodes or edges required to enrich the event and may be built on projection rules that define the required information to be used to enrich the event.
[0433] In some embodiments, the streamlined digital twin 2608 can be fully or partially synchronized with the digital twin 2610. The streamlined digital twin 2608 can contain less information than the digital twin 2610, such as fewer nodes or edges. The streamlined digital twin 2608 can contain nodes and / or edges required for events that enrich the building subsystem 122. In some embodiments, changes or updates to the digital twin 2610 can be synchronized with the streamlined digital twin 2608 via a change feed of change feed events. The change feed can indicate the addition, removal, and / or reconfiguration of nodes or edges to the graph projection database 162. Each change feed event can indicate an update to the digital twin 2610.
[0434] The digital twin updater 2606 can receive events of the change feed from the change feed generator 152, and based on each change feed event, update the reduced digital twin 2608. The updates made to the reduced digital twin 2608 can be the same updates as indicated by the events of the change feed. In some embodiments, the digital twin updater 2606 can update the reduced digital twin 2608 to include only the nodes and edges required for the enrichment event, and therefore include fewer nodes and edges than the digital twin 2610.
[0435] In some embodiments, if the change feed event does not involve information required to enrich the event, the digital twin updater 2606 filters out the change feed event. In this regard, the digital twin updater 2606 can store a list of information required for enrichment, for example, the digital twin updater 2606 can contain all event subscriptions or enrichment rules. The digital twin updater 2606 can determine whether the change feed event updates information related to event enrichment, and only updates the streamlined digital twin 2608 in response to determining that the change feed event updates the information required for enrichment. In some embodiments, when a new event subscription and / or a new enrichment rule is created, the digital twin updater 2606 can communicate with the digital twin 2610 to retrieve the nodes or edges required for the new event subscription and / or enrichment rule.
[0436] Reference now Fig. 27 , according to an exemplary embodiment, a process 2700 is shown in which an edge platform 102 performs event enrichment at the edge before transmitting the event to the cloud. In some embodiments, the edge platform 102 is configured to perform the process 2700. In addition, any computing system or device described herein can be configured to perform the process 2700.
[0437] In step 2702, the twin manager 108 may receive changes to the digital twin 2610 managed by the twin manager 108. The change may be the addition, removal, or reconfiguration of an edge and / or node. In step 2704, the twin manager 108 may update the digital twin 2610 based on the change. In addition, in step 2706, the twin manager 108 may generate a change feed event for a change feed, which represents the change of the digital twin. In some embodiments, the change feed event may summarize the change. In step 2708, the twin manager 108 may transmit the change feed to the edge platform 102 to synchronize the digital twin 2610 with the streamlined digital twin 2608 of the edge platform 102.
[0438] In step 2710, the edge platform 102 may receive a change feed from the twin manager 108. The edge platform 102 may subscribe to the change feed and may receive all change feed events raised by the twin manager 108 to the change feed. In step 2712, the edge platform 102 may update the reduced digital twin 2608 based on the change feed event. In some embodiments, the edge platform 102 may determine, in response to receiving the change feed event, whether the change feed event affects enrichment performed by the edge platform 102. In response to determining that the change feed event affects a node or edge for enriching the reduced digital twin 2608, the edge platform 102 may update the reduced digital twin 2608 based on the change feed event.
[0439] In step 2714, the edge platform 102 may receive one or more events from a building system of the building. For example, the building subsystem 122 may generate events, such as data collection events, operational command decisions, etc. The event may describe information created for the building subsystem 122 and include a timestamp indicating when the information was created.
[0440] In step 2716, the edge platform 102 may retrieve event context from the reduced digital twin 2608 for one or more events. The event context may indicate attributes describing the event. In step 2718, the edge platform 102 may generate enriched events 2604 by enriching one or more events with the event context retrieved in step 2718. Enriching the event may include adding additional attributes (event context) to the event. In step 2720, the edge platform may transmit the one or more enriched events 2604 to the cloud, such as the cloud platform 106.
[0441] Reference now Fig.28 , according to an exemplary embodiment, a system 2800 is shown that includes a twin manager 108 that synchronizes a digital twin 2610 of the twin manager 108 with digital twins of other external systems. The twin manager 108 can act as a master record of the digital twin of a building and / or building subsystems and use change feeds to update the digital twins of other systems, such as external systems 2806 and 2816. In addition, in some embodiments, the twin manager 108 can receive updates to the digital twin of one external system, such as external system 2806, and synchronize changes to other external systems, such as external system 2816. This synchronization can allow data sharing between all digital twins because each digital twin is up to date.
[0442] The twin manager 108 includes a digital twin 2619 and a change cost generator 152. In addition, the twin manager 108 includes a twin updater 2802 and a change synchronizer 2804. The twin updater 2802 can receive updates to the graph projection database 162, such as updates to nodes or edges of the graph, such as insertion, deletion, or reconfiguration of nodes or edges. Updates can be received from the cloud platform 106 as Figure 3 , where updates to the graph are learned from the events. In some embodiments, the updates can originate from other systems, such as external systems 2806 or 2816. For example, external system 2806 can update digital twin 2808 in a first format stored by external system 2806 and transmit the changes to twin updater 2802. In some embodiments, external system 2806 can transmit the updates to twin manager 108 using a change feed.
[0443] Change synchronizer 2804 can synchronize digital twin 2610 with digital twin 2808 of external system 2806 and digital twin 2814 of external system 2816. Change synchronizer 2804 can update digital twin 2808 and digital twin 2814. In some embodiments, change synchronizer 2804 performs different types of updates based on the formats of digital twins 2808 and 2814. For example, change synchronizer 2804 can perform twin updates in a first format for digital twin 2808 and twin updates in a second format for digital twin 2814 to perform the same updates across twins 2808 and 2814.
[0444] In some embodiments, the change synchronizer 2804 uses the change feed of the change feed event to update the digital twin 2808 and the digital twin 2814. In some embodiments, the change synchronizer 2804 receives the change feed of the change feed event from the change feed generator 152. In response to receiving the new change feed event, the change synchronizer 2804 can make the changes indicated by the change feed event in the digital twin 2808 and the digital twin 2814. In some embodiments, the change synchronizer 2804 transmits the change feed to the external system 2806 and / or the external system 2814, so that the external system 2806 and the external system 2816 update the digital twin 2808 and 2814.
[0445] The external system 2806 can receive updates from the change synchronizer 2804 and update the digital twin 2808 according to the updates. Similarly, the twin updater 2812 of the external system 1816 can receive updates from the change synchronizer 2804 and update the digital twin 2814. In some embodiments, the updates received from the change synchronizer 2804 are in a format associated with the digital twin stored by the external system 2806 and / or 2816. In some embodiments, the updates are change feed events and / or change feeds of change feed events.
[0446] In some embodiments, the building data platform 100 can generate a digital twin 2610 and a condensed graph projection of the digital twin in the first format 2808 and the digital twin in the second format 2814. The projection can be constructed based on projection rules and therefore may not contain all nodes and edges as a full graph projection. The same projection rules can be used for the twin manager 108 and the external system 2806 and / or the external system 2816. The building data platform 100 can compare the projections to each other to confirm that the twins of the twin manager 108 and the external systems 2806 and / or 2816 are the same. By comparing projections, rather than full twins, a more easily feasible comparison can be performed.
[0447] Reference now Fig.29, according to an exemplary embodiment, a process 2900 is shown for synchronizing the digital twin 2610 of the twin manager 108 with the digital twins 2808 and 2814 of other external systems 2806 and 2816. In some embodiments, the twin manager 108 is configured to perform the process 2900. In some embodiments, any computing device or system described herein can be configured to perform the process 2900.
[0448] In step 2902, the twin manager 108 receives updates to the digital twin 2610. The updates may be received from internal systems, such as components of the building data platform 100. For example, events processed by the cloud platform 106 may be analyzed to derive updates to the digital twin 2610, such as Figure 3 Similarly, in some embodiments, a user can provide updates to the digital twin 2610 to the twin manager 108 via the user device 176. In some embodiments, an external system such as the external system 2806 and / or the external system 2816 can provide updates. In this regard, the external system 2806 can update the digital twin 2808 and transmit the updates made to the digital twin 2808 to the twin manager 108.
[0449] In step 2904, the twin manager 108 updates the digital twin 2610 based on the updates received in step 2902. In step 2906, the twin manager 108 generates a change feed event for the change feed based on the updates. The change feed event represents the changes made to the digital twin 2610. In some embodiments, the change feed is a topic where multiple change feed events are published for receipt by consuming systems.
[0450] In step 2908, the twin manager 108 generates a first update in a first format for the digital twin 2808 based on the change feed event. In addition, the twin manager 108 generates a second update in a second format for the digital twin 2814 based on the change feed event. In step 2910, the twin manager 108 may synchronize the digital twin 2808 of the external system 2806 with the update in the first format by communicating with the external system 2806. In step 2912, the twin manager 108 may synchronize the digital twin 2814 of the external system 2816 with the update in the second format by communicating with the external system 2816.
[0451] Configuration of the Exemplary Embodiment
[0452] The construction and arrangement of the system and method as shown in the exemplary embodiment are illustrative only. Although only several embodiments have been described in detail in the present disclosure, multiple modifications are possible (e.g., changes in the size, dimensions, structure, shape and proportion of each element, parameter values, mounting arrangements, material use, color, orientation, etc.). For example, the position of the element may be reversed or otherwise changed, and the nature or number of discrete elements or positions may be changed or varied. Therefore, 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 changed or reordered according to alternative embodiments. Other substitutions, modifications, changes and omissions may be made to the design, operating conditions and arrangements of the exemplary embodiments without departing from the scope of the present disclosure.
[0453] The present disclosure encompasses methods, systems, and program products on any machine-readable medium for implementing various operations. The embodiments of the present disclosure may use existing computer processors or special computer processors for appropriate systems incorporated for this or another purpose, or may be implemented by a hard-wired system. Embodiments within the scope of the present disclosure include program products, including machine-readable media for carrying or storing machine-executable instructions or data structures thereon. Such machine-readable media may be any available medium that can be accessed by a general or special-purpose computer or other machine with a processor. For example, this machine-readable medium may include RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of machine-executable instructions or data structures and can be accessed by a general or special-purpose computer or other machine with a processor. When information is transmitted or provided to a machine via a network or another communication connection (hard-wired, wireless, or a combination of hard-wired or wireless), the machine properly regards the connection as a machine-readable medium. Therefore, any such connection is properly referred to as a machine-readable medium. The above combination is also included in the scope of computer-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
[0454] Although the drawings show a specific order of method steps, the order of steps may be different from the order depicted. Also, two or more steps may be performed simultaneously or partially simultaneously. This variation will depend on the selected software and hardware systems and designer selections. All such variations are within the scope of the present disclosure. Similarly, software implementations may be implemented using standard programming techniques with rule-based logic and other logic to implement various connection steps, processing steps, comparison steps, and decision steps.
[0455] In various embodiments, the steps and operations described herein can be performed on a processor or in a combination of two or more processors. For example, in some embodiments, various operations can be performed in a central server or central server set configured to receive data from one or more devices (e.g., edge computing device / controller) and perform operations. In some embodiments, the operation can be performed by a local controller or computing device (e.g., edge device), such as a controller dedicated to and / or located in a specific building or part of a building. In some embodiments, the operation can be performed by a combination of one or more central or off-site computing devices / servers and one or more local controllers / computing devices. All such embodiments are expected to be within the scope of the present disclosure. In addition, unless otherwise specified, when the present disclosure relates to one or more computer-readable storage media and / or one or more controllers, such computer-readable storage media and / or one or more controllers can be implemented as 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.
Claims
1. A building system comprising one or more memory devices having instructions thereon that, when executed by one or more processors, cause the one or more processors to: receiving an event from an event source, the event indicating a data value associated with the event source occurring at a particular time; identifying contextual data of a database, the database comprising a plurality of nodes and a plurality of edges associated with the plurality of nodes, wherein identifying the context data comprises identifying a node of the plurality of nodes that is related to another node representing a source of the event via one or more of the plurality of edges, and wherein the node indicates the context data that provides a contextual description of the event; generating an enriched event by enriching the event with the context data, the enriched event including the data value, the specific time, and the context data; and The enriched event is provided to a consuming application configured to act upon the enriched event.
2. The building system of claim 1, wherein the instructions cause the one or more processors to: retrieving one or more schemas from a schema database, the one or more schemas indicating available schema formats for the event; determining whether a schema in which the event is formatted matches the one or more schemas; generating the enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas; and Do at least one of the following: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
3. The building system of claim 1, wherein the instructions cause the one or more processors to add the enriched event to a topic subscribed to by the consuming application.
4. The building system of claim 1, wherein the instructions cause the one or more processors to maintain the enriched events in an event database.
5. The building system of claim 1 , wherein the instructions cause the one or more processors to identify the contextual data based on one or more enrichment rules associated with the consuming application; wherein the instructions cause the one or more processors to: identifying second contextual data of the database based on one or more second enrichment rules associated with a second consuming application; generating a second enriched event by enriching the event with the second context data, the data value, and the specific time; and The second enriched event is provided to the second consuming application.
6. The building system of claim 1, wherein the event is received from a piece of building equipment of a building; Wherein the instructions cause the one or more processors to identify the contextual data by searching for a graphical projection containing the contextual description of the piece of construction equipment.
7. The building system of claim 6, wherein the graph projection comprises the plurality of nodes and the plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
8. The building system of claim 6, wherein the database is a digital twin of the building, wherein the contextual data includes one or more capabilities of the piece of building equipment.
9. The building system of claim 6, wherein the context description comprises at least one of: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
10. The building system of claim 9, wherein the location is at least one of the building in which the piece of building equipment is located or a space in which the piece of building equipment is located.
11. A method comprising: receiving, by processing circuitry, an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a particular time; identifying, by the processing circuit, context data of a database, the database comprising a plurality of nodes and a plurality of edges associated with the plurality of nodes, wherein identifying the context data comprises identifying a node of the plurality of nodes that is associated with another node representing a source of the event via one or more of the plurality of edges, and wherein the node indicates the context data that provides a contextual description of the event; generating, by the processing circuit, an enriched event by enriching the event with the context data, the enriched event comprising the data value, the specific time, and the context data; and The rich event is provided, by the processing circuitry, to a consuming application configured to operate based on the rich event.
12. The method according to claim 11, further comprising: retrieving, by the processing circuit, one or more schemas from a schema database, the one or more schemas indicating available schema formats for an event; determining, by the processing circuitry, whether a schema in which the event is formatted matches the one or more schemas; generating, by the processing circuitry, the enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas; and At least one of the following is performed by the processing circuit: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
13. The method according to claim 11, further comprising: The processing circuit causes the enriched event to be added to a topic subscribed by the consuming application.
14. The method according to claim 11, further comprising: The enriched events are maintained by the processing circuit in an event database.
15. The method of claim 11, wherein identifying, by the processing circuitry, the context data is based on one or more enrichment rules associated with the consuming application; Wherein the method further comprises: identifying, by the processing circuitry, second contextual data from the database based on one or more second enrichment rules associated with a second consuming application; generating, by the processing circuit, a second enriched event by enriching the event with the second context data, the data value, and the specific time; and The second enriched event is provided, by the processing circuitry, to the second consuming application.
16. The method of claim 11, further comprising identifying, by the processing circuit, the contextual data by searching for a graphical projection containing the contextual description of the piece of construction equipment.
17. The method of claim 16, wherein the graph projection comprises the plurality of nodes and the plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
18. The method of claim 16, wherein the contextual data includes one or more capabilities of the piece of construction equipment.
19. The method of claim 16, wherein the context description comprises at least one of the following: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
20. A building system comprising: one or more memory devices having instructions thereon; as well as one or more processors configured to execute the instructions, the instructions causing the one or more processors to: receiving an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment occurring at a particular time; identifying contextual data for a digital twin of the building, the digital twin comprising a plurality of nodes and a plurality of edges associated with the plurality of nodes, wherein identifying the contextual data comprises identifying a node of the plurality of nodes associated with another node representing a source of the event via one or more of the plurality of edges, and wherein the node indicates the contextual data providing a contextual description of the event; generating an enriched event by enriching the event with the context data, the enriched event including the data value, the specific time, and the context data; and The enriched event is provided to a consuming application configured to act upon the enriched event.
21. A building system comprising one or more memory devices having instructions thereon that, when executed by one or more processors, cause the one or more processors to: receiving an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment; identifying contextual data for the piece of building equipment for the event in a digital twin of the building, the digital twin of the building comprising contextual building data identifying the piece of building equipment and one or more relationships associating one or more entities with the piece of building equipment, wherein the one or more entities providing a contextual description of the piece of building equipment, wherein the digital twin of the building is a building graphic, wherein identifying the contextual data comprises searching the building graphic, the building graphic comprising the contextual description of the piece of building equipment; generating an enriched event by enriching the event with the context data, the enriched event comprising the data value and the context data; and The enriched event is provided to a consuming system configured to act upon the enriched event.
22. The building system of claim 21, wherein the instructions cause the one or more processors to: retrieving one or more schemas from a schema database, the one or more schemas indicating available schema formats for the event; determining whether a schema in which the event is formatted matches the one or more schemas; generating the enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas; and Do at least one of the following: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
23. The building system of claim 21, wherein the instructions cause the one or more processors to add the enriched event to a topic subscribed to by the consuming system.
24. The building system of claim 21, wherein the instructions cause the one or more processors to maintain the enriched events in an event database.
25. The building system of claim 21, wherein the instructions cause the one or more processors to identify the contextual data based on one or more enrichment rules associated with the consuming system; wherein the instructions cause the one or more processors to: identifying second contextual data for the digital twin based on one or more second enrichment rules associated with a second consuming system; generating a second enriched event by enriching the event with the second context data and the data value; and The second enrichment event is provided to the second consuming system.
26. The building system of claim 21, wherein the building graph comprises a plurality of nodes and a plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
27. The building system of claim 21, wherein the contextual data includes one or more capabilities of the piece of building equipment.
28. The building system of claim 21, wherein the context description includes at least one of: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
29. The building system of claim 28, wherein the location is at least one of the building in which the piece of building equipment is located or a space in which the piece of building equipment is located.
30. A method comprising: receiving, by processing circuitry, an event from a piece of building equipment of a building, the event indicating a data value associated with the piece of building equipment; identifying, by the processing circuitry, contextual data for the piece of building equipment for the event in a digital twin of the building, the digital twin of the building comprising contextual building data identifying the piece of building equipment and one or more relationships associating one or more entities with the piece of building equipment, wherein the one or more entities provide a contextual description of the piece of building equipment, wherein the digital twin of the building is a building graph, wherein identifying the contextual data comprises searching the building graph, the building graph comprising the contextual description of the piece of building equipment; generating, by the processing circuitry, an enriched event by enriching the event with the context data, the enriched event comprising the data value and the context data; and The enriched event is provided, by the processing circuitry, to a consuming system configured to operate based upon the enriched event.
31. The method of claim 30, further comprising: retrieving, by the processing circuit, one or more schemas from a schema database, the one or more schemas indicating available schema formats for an event; determining, by the processing circuitry, whether a schema in which the event is formatted matches the one or more schemas; generating, by the processing circuitry, the enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas; and At least one of the following is performed by the processing circuit: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that a current operating mode is a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
32. The method of claim 30, further comprising: The processing circuit causes the enriched event to be added to a topic subscribed by the consuming system.
33. The method of claim 30, further comprising: The enriched events are maintained by the processing circuit in an event database.
34. The method of claim 30, further comprising: identifying, by the processing circuitry, the contextual data based on one or more enrichment rules associated with the consuming system; identifying, by the processing circuitry, second contextual data for the digital twin based on one or more second enrichment rules associated with a second consuming system; generating, by the processing circuitry, a second enriched event by enriching the event with the second context data and the data value; and The second enrichment event is provided, by the processing circuitry, to the second consuming system.
35. The method of claim 30, wherein the building graph comprises a plurality of nodes and a plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
36. The method of claim 30, wherein the contextual data includes one or more capabilities of the piece of construction equipment.
37. The method of claim 30, wherein the context description comprises at least one of: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
38. A building system comprising: one or more memory devices having instructions thereon; as well as one or more processors configured to execute the instructions, the instructions causing the one or more processors to: receiving an event from an event source, the event indicating a data value associated with the event source; retrieving one or more schemas from a schema database, the one or more schemas indicating available schema formats for the event; determining whether a schema in which the event is formatted matches the one or more schemas; identifying contextual data for the event in a digital twin of a building, the digital twin of the building comprising contextual building data identifying a source of the event and one or more relationships associating one or more entities with the source of the event, wherein the one or more entities provide a contextual description of the event; generating an enriched event by enriching the event with the context data in response to determining that the schema in which the event is formatted matches the one or more schemas, the enriched event comprising the data value and the context data; and providing the enriched event to a consuming system configured to act upon the enriched event, and Do at least one of the following: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
39. The building system of claim 38, wherein: receiving the event from a piece of building equipment of the building; wherein the digital twin of the building is a building graphic; Wherein, the instructions cause the one or more processors to identify the contextual data by searching the building graphic including the contextual description of the piece of building equipment.
40. The building system of claim 38, wherein: The instructions cause the one or more processors to add the enriched event to a topic subscribed to by the consuming system.
41. A building system comprising one or more memory devices having instructions thereon that, when executed by one or more processors, cause the one or more processors to: receiving an event from an event source associated with a building, the event indicating a data value associated with the event source associated with the building; identifying, in a digital twin of the building, a contextual description of the event source associated with the building, the digital twin of the building comprising contextual building data and one or more relationships, the contextual building data identifying the event source associated with the building, the one or more relationships associating one or more entities of the building with the event source associated with the building, wherein the one or more entities of the building provide the contextual description of the event source associated with the building; generating an enriched event by enriching the event with the contextual description of the event source associated with the building, the enriched event comprising the data value and the contextual description of the event source associated with the building; and The enriched event is provided to a consuming system configured to act upon the enriched event.
42. The building system of claim 41 , wherein the instructions cause the one or more processors to: retrieving one or more schemas from a schema database, the one or more schemas indicating available schema formats for the event; determining whether a schema in which the event is formatted matches the one or more schemas; generating the enriched event in response to determining that the schema in which the event is formatted matches the one or more schemas; and Do at least one of the following: In response to determining that the schema in which the event is formatted does not match the one or more schemas, adding the event to a dead letter store; or In response to determining that the schema in which the event is formatted does not match the one or more schemas and in response to determining that the building system is operating in a discovery mode to discover new schemas, the schema in which the event is formatted is added to the schema database.
43. The building system of claim 41 wherein the instructions cause the one or more processors to add the enriched event to a topic subscribed to by the consuming system.
44. The building system of claim 41 wherein the instructions cause the one or more processors to maintain the enriched events in an event database.
45. The building system of claim 41 wherein the instructions cause the one or more processors to identify the context description based on one or more enrichment rules associated with the consuming system.
46. The building system of claim 45, wherein the instructions cause the one or more processors to: identifying second contextual data for the digital twin based on one or more second enrichment rules associated with a second consuming system; generating a second enriched event by enriching the event with the second context data and the data value; and and The second enrichment event is provided to the second consuming system.
47. The building system of claim 41, wherein: receiving the event from a piece of building equipment of the building; wherein the digital twin of the building is a building graphic; Wherein, the instructions cause the one or more processors to identify the contextual description by searching the building graphic for a contextual description including the piece of building equipment.
48. The building system of claim 47, wherein: The building graph includes a plurality of nodes and a plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
49. The building system of claim 47, wherein: The context description includes one or more capabilities of the piece of construction equipment.
50. The building system of claim 47, wherein: The context description includes at least one of the following: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
51. The building system of claim 50, wherein: The location is at least one of the building in which the piece of construction equipment is located or a space in which the piece of construction equipment is located.
52. A method comprising: receiving, by processing circuitry, an event from an event source associated with a building, the event indicating a data value associated with the event source associated with the building; identifying, by the processing circuit, a contextual description of the event source associated with the building in a digital twin of the building, the digital twin of the building comprising contextual building data and one or more relationships, the contextual building data identifying the event source associated with the building, the one or more relationships associating one or more entities of the building with the event source associated with the building, wherein the one or more entities of the building provide the contextual description of the event source associated with the building; generating, by the processing circuit, an enriched event by enriching the event with the contextual description of the event source associated with the building, the enriched event comprising the data value and the contextual description of the event source associated with the building; and The enriched event is provided, by the processing circuitry, to a consuming system configured to operate based upon the enriched event.
53. The method of claim 52, further comprising: The processing circuit causes the enriched event to be added to a topic subscribed by the consuming system.
54. The method of claim 52, further comprising: The enriched events are maintained by the processing circuit in an event database.
55. The method of claim 52, wherein: The context description is identified, by the processing circuit, based on one or more enrichment rules associated with the consuming system.
56. The method of claim 52, wherein: receiving the event from a piece of building equipment of the building; wherein the digital twin of the building is a building graphic; The method further includes identifying, by the processing circuit, the contextual description by searching the building graphic for a contextual description that includes the piece of building equipment.
57. The method of claim 56, wherein: The building graph includes a plurality of nodes and a plurality of edges; The plurality of nodes represent entities of the building and the plurality of edges represent relationships between the entities of the building.
58. The method of claim 56, wherein the context description includes one or more capabilities of the piece of construction equipment.
59. The method of claim 56, wherein the context description comprises at least one of the following: the location of the piece of construction equipment; another piece of construction equipment related to the piece of construction equipment; the point of the piece of construction equipment; and A person associated with said piece of construction equipment.
60. A building system comprising: one or more memory devices having instructions thereon; as well as one or more processors configured to execute the instructions, the instructions causing the one or more processors to: receiving an event from an event source associated with a building, the event indicating a data value associated with the event source associated with the building; identifying, in a digital twin of the building, a contextual description of the event source associated with the building, the digital twin of the building comprising contextual building data and one or more relationships, the contextual building data identifying the event source associated with the building, the one or more relationships associating one or more entities of the building with the event source associated with the building, wherein the one or more entities of the building provide the contextual description of the event source associated with the building; generating an enriched event by enriching the event with the contextual description of the event source associated with the building, the enriched event comprising the data value and the contextual description of the event source associated with the building; and The enriched event is provided to a consuming system configured to act upon the enriched event.
