HiveMQ Pulse Nodes

In HiveMQ Pulse, a node is an addressable data point in the namespace that carries state, event, or configuration information. Each node has a single node type that defines its function within HiveMQ Pulse.

Namespace nodes organize data in a tree structure following the ISA95 model:

Enterprise
└── Site
        └──   Area
                └── Line
                        ├── Asset
                        │   ├── Tag
                        │   └── Field
                        └── Tag
                            └── Field

HiveMQ Pulse Node Types

HiveMQ Pulse uses organizational nodes to structure data (Enterprise, Site, Area, Line, Asset, and Folder nodes) and
data nodes to hold operational data (Field, and Tag nodes).

Enterprise Node

The Enterprise node is a top-level namespace node that represents the entire organization in the ISA-95 hierarchy.
An Enterprise node provides the root structure for all operational data in one HiveMQ Pulse project.

Site Node

The Site node type in HiveMQ Pulse corresponds to the second level of the ISA-95 hierarchical structure.
Each Site node represents a geographical location or facility where manufacturing operations take place.
For example, a manufacturing plant in Berlin.

Area Node

The Area node type in HiveMQ corresponds to the third level of the ISA-95 hierarchical structure.
Each Area node is a logical subdivision of a site.
For example, a department, production zone, or process step.

Line Node

The Line node type in HiveMQ Pulse corresponds to the production line level of the ISA-95 hierarchical structure.
Each Line node is a structured container that acts as a bridge between higher-level nodes and equipment-level nodes. Line nodes enable both contextual hierarchy and aggregation of line-level KPIs such as throughput, downtime, or OEE.
For example, a facility that houses equipment for the manufacture of a distinct group pf products.

Asset Node

The Asset node type in HiveMQ Pulse corresponds to the work unit/equipment level of the ISA-95 hierarchical structure.
Each Asset node is represents an individual piece of equipment, machine, or logical resource that includes all its operational data and context.
For example, a robotic welding arm responsible for spot welds on a production line with all its telemetry signals, status, events, and metadata.

Folder Node

the Folder node type in HiveMQ Pulse provides an additional organizational container in the namespace.
A Folder node can be used to group related nodes for clarity, navigation, and governance. For example, to group the Asset nodes in Line, or to group Tag nodes by function.

Tag Node

The Tag node type in HiveMQ Pulse corresponds to the attribute/parameter at the lowest level of the ISA-95 hierarchical structure.
Each Tag node represents a single data point, signal, or measurement such as a sensor value or status flag.
For example, a robot_status tag that shows the current state of the equipment asset to which it is attached (up, down, idle).

Field Node

The Field node type in HiveMQ Pulse corresponds to the attribute data element level in the ISA-95 hierarchy.
Each Field node represents an actual value field. The Field node is the smallest structural element within a Tag node.
For example, the numeric reading, status code, or quality indicator that is stored and transmitted.

Namespace Node Information

The specific information and parameters available vary based on the namespace node type.

Namespace Node General Tab

The General tab of the provides node details and access to editing options. The parameters available vary based on the node type.

Table 1. Available *General* parameters
Entry	Description
Namespace	The path that shows the node position of the node within the namespace.
Node Name	The name of the node.
MQTT Topic Level	The MQTT subtopic name that is expected for this node. The full MQTT topic path will be shown in the MQTT topic above, with the node’s topic level corresponding to the last element. For example, for an Area node named 'Munich' may have a corresponding MQTT level of 'munich'. If the Munich Area node is a child node of an Enterprise node named 'Carrot Inc', with its own MQTT level of 'carrot', the Area node’s full MQTT path will be 'carrot/munich'.
Traffic Origin	The name of the Agent that is expected to provide data for this namespace node. The traffic origin can be inherited from a parent node.
Description	A plain-language description of the node and its purpose. A clear description helps provide context for other users.
Data Type	The data type expected for the payloads described by the Asset. The data type can be simple (such as an Integer) or complex (such as a JSON payload with a complex structure).
Data Serialization Format	Defines how the corresponding data type for the payload is serialised. For example, a `DateTime` data type can be serialised as a Unix timestamp in seconds or milliseconds, or as an ISO8601 timestamp.
History	A record of previous data that is stored for the node type. Historic information can be used in computations, to assist when comparing payloads in governance, or to show prior data points associated with this node in Data Output. Three parameters that determine whether and how many messages are being retained: * Time Frame: For example, 1 week. * Quantity: For example 5 messages. * Data Volume: For example, 1 MB of messages. When new data/a new payload is received, any stored previous data that exceeds any of the limits is removed. For example, more than 1 week, more than 5 messages, or more than 1 MB of messages.

Namespace Node Data Sources Tab

The Data Sources tab provides options to define how data is collected for nodes that hold operational data (Field, and Tag nodes).

Table 2. Available *Data Sources* parameters
Option	Description
MQTT	Data for this node is sourced a connected MQTT broker with the MQTT topic determined by the MQTT topic level of the node and its parents, and the expected payload determined by the node’s type.
Calculation	Data for this node is provided by a calculation (for example, a SUM), typically relying on other tags as variables.
Expression	Data for this node is the result of a user-defined expression (for example, `sum(pressure2, pressure2)`). Variables detected in the expression can then be associated with other payload-bearing namespace nodes such as Tags, Fields, or Assets to supply input for the expression.
Link	This node functions as a tie to the payloads provided by another payload-bearing namespace node. Any new data the linked node receives is also populated to this node.

HiveMQ Pulse Node Data Output

For namespace nodes types that are populated with data (Tag, Asset, and Field), the Data Output tab shows the latest payloads from the node’s history if history is enabled for the node.

HiveMQ Pulse Node Consumers

Namespace nodes whose data is populated by computations, expressions, or links are regarded as consumers of any tags they reference in a computation, expression, or link. When you view a node, any other node that references it are listed in the Node Consumers tab. Information about the type of reference is also provided. For example, an input for a computation.