IoT Device Fleet Management for Manufacturers

For device manufacturers, shipping hardware is just the beginning.

Once a connected device is deployed in the field, you lose physical access to it. When a unit goes offline, requires a security patch, or encounters a bug, you can't just ask the customer to plug it into a laptop.

The challenge with fleet management​

As fleets scale, teams inevitably run into the same operational problems:

• No real-time status visibility: you discover a device is offline when the customer calls, not before.
• No bulk operations: pushing a configuration change to 500 devices requires either manual intervention on each one or custom scripting that is fragile and undocumented.
• No targeting: suppose an emergency firmware fix needs to go to one specific device model, hardware revision, or customer account. Without segmentation, every deployment can only be targeting the entire fleet.
• No audit trail: when something goes wrong, you have no record of what commands were sent, by whom and when.
• Fragmented tooling: device status lives in one system, firmware history in another, customer data in a third. Correlating them to diagnose a problem takes hours.
• Support team bottleneck: software engineers become the only people who can interact with the device fleet because tooling is too complex for support staff.

What it takes to get it right​

Effective fleet management operator requires at least:

1. Real-time device status: online/offline state, last-seen timestamp, firmware version and key health metrics for every device.
2. Group-based targeting: logical groupings by model, customer, firmware version, geography, or any custom attribute. Operations can target a group, not individual devices only.
3. Remote command dispatch: send commands or configuration updates to single devices or entire groups, with delivery confirmation and error reporting.
4. Alerting and rules: define conditions that trigger notifications (e.g. device offline for > N minutes, metric exceeds threshold, update failure) and route them to the right people.
5. Audit log: every action on every device is recorded: who did it, when and what the result was.
6. Role-based access: support staff can check device status; only authorized people can push configuration changes; customer admins only see their own devices.

How Connhex solves it​

Connhex Control is the fleet management layer. It provides dashboards and APIs for:

• Real-time device inventory with status, firmware version and model metadata
• Group management: create groups by fimware model, release or any tag
• Remote command dispatch with acknowledgment tracking
• A remote Linux shell over connected devices
• Firmware campaign management with staged rollouts (see OTA Updates)

Connhex Copilot lets fleet operators troubleshoot and pull insights in plain English, bypassing rigid dashboards to get exactly the data they need.

Connhex Monitoring provides the observability layer: time-series metrics from every device, customizable dashboards and anomaly detection powered by Connhex AI.

Connhex Rules Engine translates telemetry into actions: when a device metric crosses a threshold, automatically trigger a notification, create an incident, or invoke a webhook, without writing custom code. It also supports intelligent rules, based on metrics trends and variations with no predefined thresholds.

Connhex Notifications routes alerts to the right people via email, push, or webhook, with delivery confirmation and per-user preferences.

The IAM system controls who can see and do what: support staff get read-only fleet visibility; field engineers get configuration access; customers only see their own devices.

A concrete operator scenario​

An anomaly alert fires: device telemetry shows that 12 units deployed at a specific customer site started reporting elevated motor temperature after the last firmware release.

The operator uses Connhex Control filtering by customer, hardware revision, and firmware version to query the fleet. Then he asks Connhex Copilot to confirm the scope: 34 units total across three sites, all running firmware 3.2.1 on Rev-B hardware. That group gets targeted specifically by pushing a configuration change that reduces motor duty cycle by 10%, and the rollout is monitored in real time. Within two hours, telemetry confirms the affected units have stabilized.

The full event ¹ is recorded in the audit log.

Fleet management for device manufacturers​

Generic device dashboards show you whether devices are online. Fleet management for a device manufacturer is more complex:

• devices are owned by multiple independent customers (their data must never cross);
• different installer companies manage subsets of the fleet (their access must be scoped precisely);
• hardware revisions change what a command actually does;
• firmware versions determine whether a given configuration is valid.

Connhex handles all of this through its multi-tenant data model and IAM hierarchy:

• the manufacturer has a cross-fleet view;
• each customer admin sees only their own devices;
• each installer sees only the devices they manage.

See it in practice​

An industrial electronics manufacturer uses Connhex fleet management to maintain continuous visibility into deployed devices across multiple customer sites, using telemetry to drive product improvements. Read their story: Electronics Manufacturer.

Fleet management is central to connected product operations across verticals: Connhex for HVAC · Connhex for Vending Machines · Connhex for Industrial Washing Machines

Read the technical docs​

• Connhex Edge, Addons: System Monitor
• Core, Aggregation and Decimation
• Core, Backups and Data Retention