Home IoT platforms

IoT platforms for fleets of connected equipment

We design platforms that keep a fleet of LTE-connected devices visible and under control. The operator sees telemetry, maps and alerts and sends remote commands. The manufacturer manages firmware, over-the-air updates and warranty data. Both work in one portal.

What the platform covers

From a site visit to a live connection

Equipment that talks only over Bluetooth has to be visited. A technician must stand next to the device to read its state, so every diagnostic question costs a trip.

A permanent LTE connection changes that. The operator sees the whole fleet all the time and can act on a device remotely. The manufacturer receives firmware, quality and warranty data that it would otherwise never see.

What the operator sees

The operator portal answers the daily questions of dispatchers, technicians and managers. Which devices are offline, which need service soon, and what happened to this one last week.

What the manufacturer sees

A manufacturer supplies several operators and answers for the product throughout its life. Its portal sits above the operators and shows the data it is entitled to see.

How a device talks to the platform

Devices connect over MQTT with TLS, and each device has its own X.509 certificate. A device without a valid certificate cannot connect.

Telemetry is sent as one combined message every few minutes. This keeps mobile data use predictable over the years a device is in service.

A command has a life of its own. It is queued, sent, acknowledged and finished, or it fails or expires. The platform retries, keeps time limits and makes sure a command is not carried out twice.

Messages carry a version number from the first release, so firmware and the platform can change independently.

  1. Device
  2. IoT gateway
  3. Ingestion
  4. Time-series storage
  5. Rules and alerts
  6. Portal

Design decisions we make early

A few decisions determine what the platform costs to run and how far it can grow. We make them at the start and write down the alternatives we rejected.

Keeping data for ten years

Equipment stays in service for many years, and warranty questions come late. Storing every reading at full detail for a decade is expensive, so data moves through tiers as it ages.

How telemetry is stored as it ages
Age of data What is kept Why
Recent months Every reading at full detail Diagnostics and support
The next few years Hourly values Trends and reports
After that Daily values and an archive History and warranty questions
Always Counter readings Small in volume, high in value

Security

Each device proves its identity with its own certificate, and the connection is encrypted in both directions.

People sign in to roles with defined permissions. Sign-ins, permission changes, commands and firmware operations go into an audit log that cannot be edited.

Data is hosted in the European Union, and personal data is kept apart from technical data.

A device simulator

Hardware is rarely ready when the software team needs it. We build a simulator that speaks the agreed protocol and plays a fleet of any size, with devices that go offline, report errors and wear out their consumables.

With it the platform can be developed before the first real device connects, tested for situations that are hard to produce on a workbench, and loaded with a fleet far larger than the real one.

Technology

The platform is built on the same tools as our other back ends, with open standards for the device side.

Technology

Planning to connect your equipment?

Tell us what the devices report today and who needs to see it.