Device Profiles
Describe a device model once: points, scaling, units. Reuse it for every identical device on every site.
Platform
From Raw Registers to Usable Data
Drivers read the devices. The tag model makes them comparable. Services and APIs put the data to work.
The Path of One Reading
Devices
Chillers, meters, switches, sensors and tags, on the protocol they already speak.
Drivers
One driver per protocol, running at the edge or on a server.
Tag Model
Every reading gets a name, unit, timestamp and quality in your site hierarchy.
Services
History, alerts, rules and users, all working from tags.
Outputs
Dashboards, an open REST API, and MQTT to anything else.
What You Get Once the Data Is One Shape
Site Hierarchy
Organise tags by site, building, floor and equipment, so a query reads like the real world.
History
Store tag history, query it by time range, and export it when another team needs it.
Alerts and Rules
Raise alerts on thresholds, rate of change and silence, and trigger actions from rules.
Dashboards
Build views for operators and managers from the same tags, with roles that decide who sees what.
Open API
Read tags and history over REST, and publish live values to any MQTT broker.
Five Parts, One Platform
Each part has its own page with the detail.
Edge Gateway
Protocol drivers that run beside the equipment.
Read More
Tag Model
One shape for every reading, whatever protocol sent it.
Read More
Dashboards and Alerts
The right view for each role, and an alert only when it matters.
Read More
Open API
Your data, available to the tools you already use.
Read More
Device Profiles
Describe a device model once, reuse it everywhere.
Read MoreWhat a Pilot Needs From You
A short list, so the first week is spent reading devices, not hunting for documents.
- The list of devices, makes and models on site
- Which protocol each device speaks, and where it connects
- Device manuals or register maps for Modbus equipment
- The exported ETS project for KNX installations
- Network access for a gateway or server at the site
Platform Questions
Does IoTServa replace my BMS or SCADA?
No. It reads from them and from the devices beneath them, and adds a common tag model, history and APIs. Existing control logic stays where it is.
Can I integrate IoTServa with my own software?
Yes. Tags and history are available over a REST API, and live values can be published to an MQTT broker.
What happens if the internet connection drops?
With drivers running on an edge gateway, collection continues at the site and data is forwarded when the connection returns.
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.