ISA-95 Hierarchy

DataHub organizes industrial data in a hierarchy aligned with ISA-95 (Enterprise — Site — Area — Work Center — Equipment).

Entity levels

Level	DataHub entity	Purpose
Site	Plant	Top-level site or factory; scopes users, warehouses, and telemetry
Work Center	Machine	Production line, cell, or equipment group
Equipment	Device	Control connection (PLC, meter, gateway, simulator)
Signal	Tag	Individual data point with protocol-specific address

Each entity has a stable, URL-safe code used in paths, API calls, and NATS subjects.

Tag paths

A tag's global identity is its tagPath, built from hierarchy codes:

plantCode/machineCode/deviceCode/tagCode

Example: gebze/press-line-01/s7-1500-01/motor.current

Tag paths are:

Unique across the platform
Stable — renaming display names does not break paths if codes stay the same
Index-friendly — used in rules, dashboards, and telemetry queries without joins

Warehouses and inventory

Plants also own warehouses with locations for spare parts and WMS items. Inventory entities sit alongside the production hierarchy under the same plant scope.

Hierarchy tab

On plant and machine detail pages, the Hierarchy tab shows the ISA-95 tree with expandable levels. Use it to navigate from site down to individual tags.

Best practices

Use meaningful codes — short, lowercase, hyphen-separated (e.g. press-line-01, not Line 1)
One device per connection — each PLC or gateway is one device with its own adapter config
Group tags logically — use dot notation in tag codes (e.g. motor.current, motor.speed)
Plan before scaling — changing codes after rules and dashboards reference them requires updates