Name
A readable path such as site.tower-a.ahu-02.supply-air-temp, built from your own hierarchy.
Platform
Tag Model
Every reading becomes a tag with a name, unit, timestamp and quality flag, placed in a hierarchy of site, building and equipment.
Why It Matters
A BACnet present value, a Modbus register and a LoRa payload mean nothing to anyone outside their protocol. The tag model gives them a shared shape, so a temperature is a temperature wherever it came from and can be compared, trended and alerted on the same way.
- Same shape for BACnet, Modbus, KNX, MQTT, LoRa and BLE
- Units and scaling applied once, in the profile
- Quality flags on every value
- Hierarchy that matches how you run the site
What It Does
Unit
Engineering units are stored with every tag, and scaling is applied once in the device profile.
Timestamp
Each value carries the time it was read, so history from different protocols lines up.
Quality
A quality flag marks good, stale and failed readings, so a stuck value is never mistaken for a steady one.
Hierarchy
Tags sit in site, building, floor and equipment levels that match how your team talks about the estate.
Your Naming, Your Conventions
Align names with conventions such as Project Haystack or Brick Schema if your team uses them.
Tag Model Questions
Can we use our own tag naming scheme?
Yes. Names follow your hierarchy and can be aligned with your own convention.
What happens to a reading that fails?
It keeps its place in history with a failed quality flag, so a gap is visible and explained rather than silent.
More From the Platform
Start With One Site. Prove It on Real Devices.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.