Overview

Designing for the fleet, not the first unit

Most connected-product pain appears after launch: devices that cannot be identified reliably, configuration that has to be applied by hand, updates that cannot be rolled back, and failures that cannot be diagnosed without shipping the unit back.

These are design decisions, made early, usually by omission. We make them explicitly: how a device proves what it is, how it receives configuration, how it reports health, how it is updated and what happens when an update fails.

The result is a product that can be manufactured, commissioned, monitored and maintained at scale — which is usually what determines whether a connected product is profitable.

Device mechanisms

What a manageable device needs

Six mechanisms that decide whether a deployed fleet is supportable.

  1. Identity and provisioning

    A reliable way for each device to prove what it is, established at manufacture rather than improvised at installation.

  2. Configuration management

    Parameters that can be set, validated, changed remotely and recovered safely when something is set incorrectly.

  3. Connectivity management

    Connection handling, retry behaviour, fallback and defined operation during outages of any length.

  4. Remote diagnostics

    Health data, fault codes and logs that let a support engineer understand a failure without visiting the device.

  5. Secure update

    Firmware update with integrity verification, staged rollout, rollback and defined behaviour on interruption.

  6. Lifecycle support

    Versioning across a mixed fleet, backwards compatibility and a plan for devices that will still be running in ten years.

Failure modes

Fleet problems and the design decisions that prevent them

Each of these is a design decision made — or omitted — before the hardware is frozen.

Problem after launchRoot causeDesign decision that prevents it
Devices cannot be told apartIdentity improvised at install timeUnique identity provisioned during manufacture
Update bricks unitsNo verification or rollback pathSigned updates, integrity check, atomic switch and rollback
Failures cannot be explainedNo retained diagnostic dataStructured fault logging sized to the platform, retrievable remotely
Configuration drift across fleetManual configuration with no recordCentral configuration model with validation and reporting
Mixed versions become unmanageableNo compatibility strategyVersioning and backwards-compatible interfaces defined up front

Fleet process

Engineering a device for its whole service life

Each stage below is where an unmanaged fleet usually starts to hurt.

  1. Lifecycle definition

    How devices are manufactured, commissioned, operated, updated, diagnosed and eventually retired.

  2. Identity design

    Device identity and credentials established during manufacture, in a process production can actually run.

  3. Configuration model

    What is configurable, who changes it, how it is validated and how a bad configuration is recovered.

  4. Update architecture

    Update packaging, delivery, verification, rollback and behaviour if power or connectivity is lost mid-update.

  5. Diagnostics design

    What the device records, what it reports, and how support staff retrieve it in the field.

  6. Fleet validation

    Mechanisms exercised across multiple devices and firmware versions, not just on one bench unit.

Scale

Designing for the fleet, not the first unit

Shipping one connected device is an engineering exercise. Shipping ten thousand and still being able to fix them two years later is a different problem.

Identity, configuration, diagnostics and update are decided early, because retrofitting them to deployed hardware is often impossible.

Technical illustration of connected device management showing identity, configuration, diagnostics and update flows
Device lifecycle mechanisms

Applications

Where device management decides the outcome

Where it decides the outcome

  • Large fleets of deployed sensors or controllers
  • Devices installed in locations that are expensive to visit
  • Products with long service lives and evolving firmware
  • Equipment requiring commissioning by non-specialist installers
  • Products where field failures must be diagnosed remotely
  • Existing connected products that have become unmanageable

Mechanisms

  • Device identity
  • Provisioning
  • Remote configuration
  • OTA update
  • Diagnostics
  • Fleet versioning

FAQ

Connected device questions

What teams ask once they start thinking past the first unit.

Ask our team

Next step

Planning a fleet you will still be supporting in five years?

We will map the identity, configuration, update and diagnostic mechanisms it needs before the hardware is fixed.