Edge, IoT & Compute · Module
IoT Hub
Sensors and machines that create work orders, not unwatched alarms
IoT Hub is planned to connect sensors, meters, gateways and machines to One3 and turn telemetry into governed business actions. It is not a device-maker cloud; hyperscaler and ThingsBoard deployments can be sources through connectors.
What it does
IoT Hub keeps a registry of devices and sensors with secure identities, ingests telemetry over MQTT and HTTP, stores and rolls it up, evaluates no-code rules, raises alerts, and calls Actions in Assets & Maintenance, Frontline, EHS, Energy and Inventory. A chiller warming up, a vibration band drifting or a cold-chain excursion becomes a work order, a store task or an EHS observation with the evidence attached.
Devices with least authority
Every device gets its own X.509 certificate or token; shared credentials are rejected at provisioning. Bulk provisioning uses CSV with claim codes, and certificates rotate and revoke on a defined lifecycle. Devices are thing identities, never seats. MQTT topics are restricted per device.
Rules you can test first
Rules cover thresholds, rate of change, absence of data, duration, combinations across sensors and schedules, with site overrides. Every rule can be simulated against history before it is enabled. Alerts deduplicate per device, rule and condition, with suppression windows, acknowledgement, escalation ladders and clearing conditions. Silent devices are never reported as normal. A rule that creates spend or external messages must name an owner and an approver.
Edge and fleet
On site edge nodes, rules keep running during WAN loss with store-and-forward, no-code edge data flows filter and downsample before upstream, and read-only auto-discovery proposes devices for human adoption. Firmware rolls out by rings and halts on failure rate. Industry solution templates bundle device models, decoders, rules and checklists for cold chain, energy metering, facility HVAC and dairy chilling.
What it will not do yet
Before the W6 physical-risk tier, no Action from IoT Hub changes physical equipment state. Commands are limited to configuration and diagnostics. PLC and OT protocol breadth comes through certified partner gateways.
Features
What IoT Hub includes
Device models
Versioned device types with telemetry schema, units, ranges, command set, decoder and documentation.
Device registry
Devices and sensors with serial, site, asset link, location, tags and lifecycle state.
Secure provisioning
Per-device certificates or tokens, bulk CSV with claim codes, rotation and revocation; no shared credentials.
MQTT and HTTP ingestion
Per-device topic ACLs, QoS handling, payload limits and per-tenant rate limits.
Payload decoders
No-code JSON mapping and sandboxed decoder scripts for binary payloads, with tests and versions.
Partner gateways
Modbus, BACnet and OPC UA devices through certified partner gateways; LoRaWAN through network server partners.
Telemetry storage and explorer
Monthly partitions with 1-minute, 1-hour and 1-day rollups, cold archive, charts, device comparison and device map.
No-code rules with simulation
Thresholds, rate of change, silence, duration and combinations, simulated on history before enabling.
Alerts and Actions from rules
Deduplicated alerts with escalation; outcomes create work orders, frontline tasks, EHS observations or quarantine proposals.
Device health
Last seen, expected interval, battery, signal, firmware and silent-device detection.
Firmware OTA by rings
Staged rollouts that halt on failure rate, with rollback where the device supports it.
Anomaly detection and maintenance signals
Seasonal baselines and condition indicators feeding work-order proposals for the maintenance planner.
Edge rules and data flows
Rules on site edge nodes during WAN loss and no-code filtering, downsampling and enrichment before upstream.
Platform connectors and templates
Ingest from AWS IoT Core, Azure IoT and ThingsBoard; industry solution templates for cold chain, energy, HVAC and dairy.
Workflow
Telemetry to business action
- 1
Device sends telemetry with its own identity
- 2
Decoder normalises payload and units
- 3
Rules evaluate the condition for its duration
- 4
A deduplicated alert is raised
- 5
The Action Bus applies tier, DoA and approvals
- 6
Owner app creates the work order, task or EHS observation
- 7
Alert closes when the condition clears; ROI entries written
Workflow
Firmware rollout by rings
- 1
IoT engineer creates a rollout with a signed image and rings
- 2
Ring 1 devices are offered the firmware
- 3
Failure rate is checked against the threshold
- 4
Above threshold: halt and roll back where supported
- 5
Within threshold: next ring after the wait time
AI
AI skills and Digital Employees
Rule drafting from plain language
Drafts the condition, window, suppression and target Action and shows the simulated firing count on history. Enabling stays human.
Payload decoder drafting
Proposes a decoder from sample payloads and a datasheet with a test harness; never auto-activated.
Anomaly detection
Per-asset baselines, change points, drift and stuck sensors as proposals.
Alert narrative and triage
Why the alert fired, what changed, similar past alerts and a suggested first check.
Silent-device explanation
Distinguishes network outage, power loss, battery, gateway failure and decommission.
Copilot over telemetry
Natural-language questions answered with a chart and the query shown.
Digital Employees that use this module
- AI Maintenance Planner
- AI IoT Reliability Analyst (proposed)
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
We already have an IoT dashboard. Why add this?
Keep it as a source. IoT Hub is designed to add the action layer: rules that create work orders, tasks and EHS observations in the apps where the work is done.
Can it read data from AWS IoT, Azure or ThingsBoard?
Yes, as planned connectors through Integration Hub. External platform sources are read-only; API access is to be verified.
Will it switch machines on or off?
No, not before the physical-risk tier planned for W6. Until then commands are limited to non-safety configuration and diagnostics.
Does it support OPC UA, Modbus or LoRaWAN?
Through certified partner gateways and LoRaWAN network servers. An OPC UA connector on edge nodes is planned at GA in W5.
See IoT Hub in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.