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
-
Operator portal
Fleet monitoring, a map, a card for every device, counters, alerts, logs and remote commands for the company that runs the equipment.
-
Manufacturer portal
A registry of every device made, firmware and over-the-air updates, quality and warranty cases, and product analytics.
-
Connectivity administration
A registry of eSIM profiles with their lifecycle, traffic monitoring and contract terms.
-
Device communication
A protocol agreed with the hardware team, a secure connection for every device and a service that delivers commands reliably.
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.
-
Dashboard
Fleet size, devices online and offline, active alerts, consumption and a list of devices with problems.
-
Map
Devices at their installation addresses, coloured by status and filtered by status, customer, region or alert type. Markers are grouped on the server, so the map stays quick as the fleet grows.
-
Device card
Current parameters, charts of their history, the customer and address, and everything that has happened to the device.
-
Counters and consumption
Counters kept separately for each kind of output and added up by day, week and month for a device, a customer or the fleet.
-
Consumables forecast
The remaining life of a consumable part is calculated from actual use, with a list of upcoming replacements and alerts at set thresholds.
-
Alerts
Rules turn telemetry and events into alerts, for example when a device goes offline, a temperature leaves its range or a new error code appears.
-
Remote commands
Request data now, change a setting, start a service cycle or run self-diagnostics. Commands that can do harm ask for a second confirmation.
-
Logs and audit
Error, service and command logs with filters, and an audit trail of sign-ins, permission changes and commands.
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.
-
Device registry and passport
Every device made, with its model, hardware revision, batch and components, factory test results, firmware, warranty and service history.
-
Firmware registry
Versions with their change notes and status, and a table of which firmware fits which hardware and protocol version.
-
Over-the-air updates
An update goes to a small test group first, then to the rest on a schedule. A campaign that fails can be stopped and rolled back.
-
Quality and warranty
Warranty calculated from the serial number and shipment, return cases with attachments and decisions, and analysis of repeated defects by batch, firmware or region.
-
Product analytics
How the product is used by model and market, and how calculated service intervals compare with the real ones.
-
Certificates
Issue, rotation and revocation of device certificates, and blocking of a device that has been compromised.
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.
- Device
- IoT gateway
- Ingestion
- Time-series storage
- Rules and alerts
- 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.
-
Designed for the target, sized for today
The architecture, data model and protocol are designed for the fleet the business is aiming at. The infrastructure is sized for the fleet that exists, and growing it is configuration work.
-
One database technology
Business data, time series and map queries all run on PostgreSQL with its extensions. A team maintains one technology.
-
Isolation in the database
When several operators share the platform, the database itself keeps their data apart. A forgotten condition in a query cannot show one operator another's fleet.
-
Stateless application servers
Shared state lives in the database and the cache, so servers can be added and removed freely.
-
Every outside service behind an adapter
The mobile network provider, the map service and the message gateway are each reached through an interface of our own. Changing a provider means writing a new adapter.
-
People and devices on separate paths
Browser traffic and device traffic enter the platform through different doors and are protected by different means.
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.
| 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.
Planning to connect your equipment?
Tell us what the devices report today and who needs to see it.