Device registry
Register devices by tenant, type, serial number, status, credential reference, and latest heartbeat.
Opt-in module
First implementation surface
IoT is separate because telemetry, device credentials, broker traffic, and remote commands have different scaling and security needs than normal campaign or support pages.
Telemetry ingestion
Accept MQTT and HTTPS telemetry, normalize payloads, and emit platform events for automation.
Alerts and commands
Generate offline and threshold alerts, then queue remote commands with audit records.
How it relates to app.ozibus.com.au
The IoT surface owns device-specific operations, while the Ozibus app remains the place for account access, permissions, billing, notifications, and cross-module automation.
Shared SSO
Users should enter from the Ozibus app and carry tenant, role, and feature entitlement context.
Shared alerts
IoT alert events can notify teams through existing Ozibus email, SMS, push, and broadcast services.
Shared billing
Telemetry volume, device count, command usage, and alerting can feed the existing wallet and subscription layer.