Name
Each Node has a readable name, such as Supply Air Temperature, and sits in the place it measures.
Every reading belongs to a Node with a name, unit, timestamp and quality flag, placed in an Organization, Site, Facility, Level and Area hierarchy.

A BACnet present value, a Modbus register and a LoRa payload mean nothing to anyone outside their protocol. The model gives them a shared shape as Nodes, so a temperature is a temperature wherever it came from and can be compared, trended and alerted on the same way.
Each Node has a readable name, such as Supply Air Temperature, and sits in the place it measures.
Engineering units are stored with every Node, and scaling is applied once in the device setup or template.
Each value carries the time it was read, so history from different protocols lines up.
A quality flag marks good, stale and failed readings, so a stuck value is never mistaken for a steady one.
Nodes sit in Organization, Site, Facility, Level and Area levels that match how your team talks about the estate.
Align Node names with conventions such as Project Haystack or Brick Schema if your team uses them.
Each Organization can rename the hierarchy levels in its own console, so the screens use the words your team already uses.
Derive a value from up to six other Nodes with a safe formula, and show a gap rather than a guess when an input is missing.
Ready formulas turn a level reading into the volume of a horizontal or vertical cylinder tank, in m³ or litres.
A company address such as iotserva.com/yourcompany opens a sign-in page with your logo and name.


Screens from the live IoTServa software with a demo company and demo data.
Yes. Node names are yours, and each Organization can rename the hierarchy levels it sees.
It keeps its place in history with a failed quality flag, so a gap is visible and explained rather than silent.
See VYROX Hardware or Read the Protocol Guides
Tell us which protocols are on site. We will scope a pilot that reads your real devices.