What we doIoT & connected systems

Connected equipment. Useful operational data.

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 team
Device-to-insight architectureDevices send telemetry to an IoT hub and a big data platform. Data branches into analytics and AI, which feed the app and dashboard. Role-based access control spans the platform.AT THE EDGECONNECTED PLATFORMIngestionData layerIntelligenceExperienceDeviceSensors & equipmentTelemetryIoT HubIngest & routeBig DataStore & organiseAnalyticsPatterns & trendsAIModels & inferenceAppActions & workflowsDashboardInsights & visibilityRBACRole-based access controlAcross the platformDevice-to-insight architectureDevices send telemetry to an IoT hub and a big data platform. Data branches into analytics and AI, which feed the app and dashboard. Role-based access control spans the platform.AT THE EDGEDeviceSensors & equipmentTelemetryIoT HubIngest & routeBig DataStore & organiseAnalyticsPatterns & trendsAIModels & inferenceAppActions & workflowsDashboardInsights & visibilityRBACRole-based access control
Device-to-insight architectureConceptual system design

What we engineer

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.

Telemetry platforms

Ingest and validate measurements, route events and retain the history needed for later analysis. Give applications a consistent view across devices and tenants.

Applications and fleet visibility

Build the operational interface: device state, trends, maps, alerts and workflows. Apply roles and permissions to the actions as well as the data.

Analytics and model integration

Connect telemetry history to analysis and model inference. Keep observed measurements distinct from derived indicators and model predictions.

The decisions that shape the system

What happens when a device disconnects?

Specify buffering, retry behaviour and how late or duplicated messages are handled before relying on a dashboard.

Who can see and control each device?

Model organisations, users and devices together. Define access boundaries for operators, administrators and integrations.

Which signals deserve action?

Separate collection from interpretation. Agree the meaning of an alert and how a person investigates it.

System building blocks

  • Device and telemetry contracts
  • Ingestion and storage design
  • Fleet applications and access model
  • Deployment and operational documentation

A device-to-fleet demonstrator

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.

Build on the work. Join the conversation.

For product questions, technical collaboration or feedback on our published work, get in touch with Horizon Tech.

Connect with Horizon Tech