Devices and connectivity
Define the device identity, messages and communication path. Account for intermittent connectivity, timestamps and the difference between an event occurring and a platform receiving it.
IoT engineering from device integration and telemetry to fleet applications, analytics and AI. We connect the physical system to the software people use to operate it.
Connect with the teamDefine the device identity, messages and communication path. Account for intermittent connectivity, timestamps and the difference between an event occurring and a platform receiving it.
Ingest and validate measurements, route events and retain the history needed for later analysis. Give applications a consistent view across devices and tenants.
Build the operational interface: device state, trends, maps, alerts and workflows. Apply roles and permissions to the actions as well as the data.
Connect telemetry history to analysis and model inference. Keep observed measurements distinct from derived indicators and model predictions.
Specify buffering, retry behaviour and how late or duplicated messages are handled before relying on a dashboard.
Model organisations, users and devices together. Define access boundaries for operators, administrators and integrations.
Separate collection from interpretation. Agree the meaning of an alert and how a person investigates it.
Our demonstrator connects a simulated device to an Android application and a cloud fleet view, including charts, a map and a 3D twin. It lets us explore the full telemetry path. It is not evidence of field-validated failure prediction.
For product questions, technical collaboration or feedback on our published work, get in touch with Horizon Tech.
Connect with Horizon Tech