Everything your team looks at, in one place.
Sites, lines and machines as an asset tree. Devices with their status and messages. Measures, dashboards, an inbox and scheduled reports — all scoped to the assets each person looks after.
The shape of your operation
A branch holds a tree of assets — sites, lines, machines, rooms. Every device, measure, dashboard, policy and action hangs under one. Each asset shows its health: the worst alert open under it, with how many are unacknowledged.
- · Assign people to assets; optionally they see only those and what's below
- · Each asset page lists its devices, newest readings and the policies watching it
- · “Who can see it” for every asset
Know what's connected, and what it sent
Each device has its own MQTT credential and topics, or an HTTP ingest key. Online and offline come from the broker itself, and the device page keeps its last 100 messages — the first place support looks.
- · A wrong password, a client-ID mismatch or an unknown device is refused and logged
- · Readings from a device that doesn't own the measure are dropped and counted
Send anything, any time
A measure is a JSON object, not a fixed column. When firmware adds a field, it's simply there. Each measure belongs to one device and moves with it; history is kept as time series with retention per branch.
17 widget types, live while you watch
Pick a widget, bind its measures, set thresholds and colours, and place it on a 12-column grid. Readings arrive over a websocket while the page is open. Draw on your own floor plan with the blueprint widget.
- Number
- KPI
- Boolean
- Gauge
- Tank
- Text
- Line
- Bar
- Pie
- Scatter
- Heatmap
- Table
- Map
- Blueprint
- Action button
- Action input
- Action toggle
writes to a device: the three action widgets send a command when pressed.
Notifications and messages, together
Alerts, reports and invitations arrive in each person's inbox. People who share an asset can message each other — subject, body and replies — without leaving the platform.
The same numbers, on paper
Build a template with real data on the canvas, publish it as a version, and schedule it. Sections repeat per device or child asset. PDF or CSV, delivered by email and inbox at a time in the branch's zone, kept for 90 days.