DataHub.
BACnet/IP → MQTT → REST API

The IoT DataHub that connects your field to your decisions

Collect controller points on site, historise them in the cloud, and serve them to QRPanels through a single REST API. Running on BACnet/IP today, with Modbus TCP, OPC UA, and Wattsense in integration.

Request a demoSee the architecture

DATAHUB / Console

Fleet overview

+ Bridge

Bridges

12

Online

9

Points

248

BridgeStatusPoints
HQ — Tower AOnline86
Warehouse NorthOnline54
Clinic OranOffline37
Campus LabOnline71

DataHub Bridge

Site box connected

MQTT · BACnetLive

What runs today, and what is coming

BACnet/IPMQTT QoS 1REST API v1MultitenantModbus TCPOPC UAWattsense

1

Protocol in production (BACnet/IP)

3

Connectors in integration

3 s

Live refresh interval

10 min

Consolidated history step

Platform features

A complete platform, built for industrial sites

From the controller point to the QRPanels dashboard, every block is decoupled and observable.

AvailableThe six blocks below are running in production

BACnet/IP collection

The on-site bridge reads controller points and publishes them to the DataHub over MQTT. Modbus TCP, OPC UA, and Wattsense follow the same chain.

Bridge configuration

Import a controller scan, pick the points, and set the BACnet/IP target and MQTT parameters from the console — no manual work on the mini-PC.

Normalised point mapping

Every BACnet reference maps to a structured topic — site, building, equipment, point — with its object type and engineering unit.

REST API for QRPanels

Live values and offline-trend history (10-minute downsample, bounded by the trend config) exposed over HTTP, with one API key per bridge.

Multitenant by design

Organisation, building, bridge, controller, equipment, and point form one hierarchy, partitioned by database policies and by the organisation API key.

Fleet supervision

Heartbeat and connectivity status per bridge, latest received values, and a local BACnet simulator to validate a configuration before rollout.

Architecture

A controlled data flow, from the source to the dashboard

Field zone

  • BACnet/IP controllers
  • AI / BI / MI objects
  • Modbus & OPC UA coming

SIEMTEC Bridge

  • Mini-PC on site
  • BACnet/IP polling
  • MQTT QoS 1 publishing

SIEMTEC Cloud

  • Multitenant DataHub
  • Point historisation
  • REST API read by QRPanels
01

Acquisition

The bridge reads controller points on the field network, timestamps them at the source, and attaches each value to its organisation, building, and equipment.

02

Publishing

Values are published over MQTT with QoS 1, carrying the bridge identifier and a structured topic, on an outbound authenticated connection.

03

Historisation

The cloud stores the latest values and the dense change history. Offline trends are downsampled to 10 minutes at read time, without a second history table.

04

Read by QRPanels

QRPanels queries the REST API with its bridge key: available boxes, live values, and offline-trend history bounded by period, rolling cap, and end date.

Field connectors

Integrating the industrial standards

BACnet/IP is deployed and tested on real installations. The other connectors reuse the same bridge, MQTT, and DataHub pipeline, and land in stages.

Available

BACnet/IP

  • AI / BI / MI objects
  • Read per controller instance
  • Engineering units mapped
  • Local test simulator
  • Read-only
In progress

Modbus TCP

  • Functions 01/02/03/04
  • Grouped reads
  • Endianness & scale factor
  • Rate per point class
  • Controlled writes later
In progress

OPC UA

  • Basic256Sha256 targeted
  • SignAndEncrypt
  • Managed trust lists
  • Subscriptions / MonitoredItems
  • No AcceptAll in production
In progress

Wattsense

  • Outbound connected boxes
  • Reuses the MQTT pipeline
  • Dedicated adapter
  • Unified supervision
Security

Architecture choices that limit exposure

The field is never reachable from the internet, and every access to data goes through an identity tied to one organisation.

Encrypted transport

Console and API served over HTTPS, MQTT publishing authenticated per bridge identifier.

No inbound port on site

The bridge opens every connection towards the cloud. Nothing to expose on the customer network.

API keys per organisation

Keys stored hashed, compared in constant time, with revocation and last-use tracking.

Data partitioning

User accounts belong to an organisation, and database policies filter every request.

Read-only on the field side

No writes to controllers today, so there is no risk of an unwanted action on the BMS.

Compliance — target

Intended trajectory: GDPR, IEC 62443, and ISO/IEC 27001 practices. Not certified at this stage.

Ready to connect your installations?

Let's go through your context: the controllers already in place, the points to collect, expected volumes, and your integration schedule.

Contact the teamSign in to the console

The Modbus TCP, OPC UA, and Wattsense connectors are in integration and flagged In progress above. No security certification is claimed at this stage.