Systems and methods for entity visualization and management with an entity node editor
A method for visualizing and managing entities and connections between entities based on a graphical user interface (GUI) node editor includes constructing an entity datablock, wherein the entity datablock is a data structure describing an entity and comprises entity descriptive information, an entity category, an entity name, entity relationships, and an entity identifier. The method includes establishing the entity relationships as bi-directional relationships, wherein the bi-directional relationships link two disparate entities. The method further includes representing the entity datablock as a node and the bi-directional relationships as lines connecting two nodes, wherein the node comprises at least one of the entity descriptive information, the entity category, or the entity name.
1. A method for visualizing and managing entities and connections between entities using a graphical user interface (GUI) node editor, the method comprising:
constructing an entity datablock, wherein the entity datablock is a data structure representing an entity and comprises entity descriptive information, an entity category, an entity name, entity relationships, and an entity identifier, and wherein at least two of the entities are physical entities;
establishing at least one of the entity relationships as a bi-directional relationship, wherein the bi-directional relationship directly links the two physical entities;
representing the entity datablock as a node and the entity relationships as lines connecting two nodes, wherein the node comprises at least one of the entity descriptive information, the entity category, or the entity name.
2. The method of claim 1 , wherein constructing the entity datablock further comprises:
receiving, by a system to implement a new entity datablock, from a user device, a request to create the new entity datablock;
generating, by the system to implement the new entity datablock, an entity identifier for the new entity datablock;
instantiating, by an entity database, a new data structure element with the entity identifier, wherein the entity database comprises a plurality of data structure elements;
storing, by the entity database, in the new data structure element, entity information, wherein the entity information comprises entity descriptive information, an entity category, an entity name, and entity relationships.
3. The method of claim 1 , wherein establishing the entity relationships further comprises linking the two physical entities with a pair of unique identifiers, wherein the pair of unique identifiers are associated with the two physical entities and are stored in the entity datablock of each of the two physical entities.
4. The method of claim 1 , wherein representing the entity datablock as a node further comprises displaying an interactive GUI element configured to facilitate editing the entity datablock associated with the node.
5. The method of claim 1 , wherein representing the entity relationships as lines further comprises displaying an interactive GUI element configured to facilitate editing the entity relationships of the two physical entities.
6. The method of claim 1 , wherein the GUI node editor further comprises one or more graphical interactive elements that form a digital representation of one or more physical entities.
7. The method of claim 6 , wherein the one or more physical entities further comprise an object that is able to be controlled by the GUI node editor.
8. One or more non-transitory computer-readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to implement a graphical user interface (GUI) node editor for visualizing and managing entities and connections between entities, the GUI node editor configured to:
construct an entity datablock, wherein the entity datablock is a data structure representing an entity and comprises entity descriptive information, an entity category, an entity name, entity relationships, and an entity identifier, and wherein at least two of the entities are physical entities;
establish at least one of the entity relationships as a bi-directional relationship wherein the bi-directional relationship directly links the two physical entities;
represent the entity datablock as a node and the entity relationships as lines connecting two nodes, wherein the node comprises at least one of the entity descriptive information, the entity category, or the entity name.
9. The one or more non-transitory computer-readable media of claim 8 , wherein constructing the entity datablock includes:
receiving from one or more user devices, a request to create a new entity datablock;
generating an entity identifier for the new entity datablock;
instantiating a new data structure element with the entity identifier, wherein the entity database comprises a plurality of data structure elements;
storing in the new data structure element, entity information, wherein the entity information comprises entity descriptive information, an entity category, an entity name, and entity relationships.
10. The one or more non-transitory computer-readable storage media of claim 8 , wherein the GUI node editor is further configured to establish the entity relationships by linking the two physical entities with a pair of unique identifiers, wherein the pair of unique identifiers are associated with the two physical entities and are stored in the entity datablock of each of the two physical entities.
11. The one or more non-transitory computer-readable storage media of claim 8 , wherein the GUI node editor is further configured to represent the entity datablock as a node by displaying an interactive GUI element configured to facilitate editing the entity datablock associated with the node.
12. The one or more non-transitory computer-readable storage media of claim 8 , wherein the GUI node editor is further configured to represent the entity relationships as lines by displaying an interactive GUI element configured to facilitate editing the entity relationships of the two physical entities.
13. The one or more non-transitory computer-readable storage media of claim 8 , wherein the GUI node editor is configured to form a digital representation of one or more physical entities, and wherein the GUI node editor is further configured to control the one or more physical entities.
14. A building automation system comprising:
a processing circuit including a processor and memory having instructions stored thereon that, when executed by the processor, cause the processing circuit to implement a GUI node editor, the GUI node editor comprising:
one or more entity datablocks, wherein the one or more entity datablocks are a data structure representing one or more physical entities and comprise entity descriptive information, an entity category, an entity name, entity relationships, and an entity identifier;
one or more bi-directional entity relationships, wherein the one or more bi-directional entity relationships link two disparate entities;
a plurality of nodes and a plurality of lines connecting two nodes, wherein the plurality of nodes comprise at least one of the entity descriptive information, the entity category, or the entity name.
15. The processing circuit of claim 14 , wherein the one or more bi-directional entity relationships link the two disparate entities with a pair of unique identifiers, wherein the pair of unique identifiers are associated with the two disparate entities and are stored in an entity datablock of each of the two disparate entities.
16. The processing circuit of claim 14 , wherein the GUI node editor represents the one or more entity datablocks as one or more nodes by displaying an interactive GUI element configured to facilitate editing the one or more entity datablocks associated with the one or more nodes.
17. The processing circuit of claim 14 , wherein the GUI node editor represents the one or more bi-directional relationships as one or more lines by displaying an interactive GUI element configured to facilitate editing the one or more entity relationships of the two disparate entities.
18. The method of claim 1 , wherein the physical entity is at least one of a person, equipment, or object.
19. The non-transitory computer-readable storage media of claim 8 , wherein the physical entity is at least one of a person, equipment, or object.
20. The processing circuit of claim 14 , wherein the one or more physical entities are at least one of a person, equipment, or object.