Field
Meters, controllers, drivers, sensors and tags on the site, each speaking its own protocol.
- BACnet and Modbus devices on LAN and RS-485
- DALI lines behind a gateway or controller
- KNX rooms, LoRaWAN sensors, BLE tags
Architecture
How IoTServa Works
Field protocols in, one tag model in the middle, dashboards, alerts and an API out. Here is the whole path and the ways it can be deployed.
The Path of Every Reading
Edge
Protocol drivers run where the wires are. Serial and local networks never need to reach the internet.
- One poller per serial line, one request at a time
- Designed to hold readings on disk during an uplink outage
- Outbound TLS connection only
Normalize
Every reading becomes a tag with a name, unit, timestamp and quality flag, placed in your hierarchy.
- Scaling and word order applied once, in the profile
- Good, stale and bad quality on every value
- Site, building, floor and equipment levels
Use
History, dashboards and alerts are built once and work for every protocol. Data leaves through the API.
- Thresholds, rate of change and silence alerts
- Role-based dashboards per site
- REST, MQTT publish, webhooks and CSV export
Four Readings, One Shape
| Source | Native Address | Normalized Tag | Value | Unit |
|---|---|---|---|---|
| BACnet AHU Supply Temperature | Device 2001, AI 3, present value 18.4 | site.tower-a.ahu-02.supply-air-temp | 18.4 | degC |
| Modbus Meter Active Power | Unit 12, holding register 40013, scale 0.1 | site.plant.mcc-1.meter-12.active-power | 92.6 | kW |
| DALI Luminaire Dim Level | Line 2, short address 14, via gateway | site.office.level-3.zone-b.luminaire-14.dim-level | 80 | % |
| LoRaWAN Cold Room Temperature | devEUI ...4F2A, port 2, bytes 00 18, scale 0.1 | site.store.cold-room-1.shelf-top.temperature | 2.4 | degC |
Illustrative examples. Tag names follow your own hierarchy, and the native addresses come from your device manuals and ETS project.
Four Ways to Deploy
Edge Gateway Plus Cloud
Drivers on a gateway at the site, storage and dashboards in the cloud. The usual choice for buildings and plants with serial or local-only networks.
- Outbound connection only
- Collection continues during uplink outages
- Many sites in one account
On-Premise Server
The platform on a server in your own network, for sites that must keep data inside the fence. Available on request and scoped per project.
- No data leaves the site
- Your own backup and access control
- Suits regulated or isolated facilities
Cloud Only
For sources that are already on IP: an MQTT broker, a LoRaWAN network server or a BACnet/IP network reachable over a secure link.
- No hardware to install
- Fastest start for a pilot
- Not for serial-only devices
Hybrid Estate
A mix per site: gateways where there are wires, cloud reads where there are brokers, all in one tag hierarchy.
- One model across sites
- Add sites without redesign
- Per-site roles and permissions
Architecture Questions
Where does the data live?
In the cloud account, on an on-premise server, or both, depending on the deployment model you choose. The tag model and the tools are the same in each case.
What happens when the internet drops at a site?
With an edge gateway, readings are held on disk at the site and sent in order when the connection returns, with their original timestamps. Without a gateway, cloud-only sources pause until the link is back.
Can we start small and grow?
Yes. A pilot usually starts with one gateway or one IP source at one site. More devices, protocols and sites are configuration inside the same hierarchy.
Which Model Fits Your Sites? Ask Us.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.