Technical Guide

Manage a fleet of 50 to 500 industrial routers without a dedicated team

How can you manage hundreds of industrial routers spread across your sites without a dedicated network team?

OTA firmware updates, multi-site configuration pushes, SIM and signal monitoring, remote troubleshooting, proactive alerts, RBAC for technicians and admins… The Eziwan platform centralizes the management of your entire industrial 4G fleet from a single web console, without the need for any additional tools.

The Problem

Once you have more than a dozen routers, manual management becomes unmanageable. Each router has its own firmware version, its own configuration, and its own incident history. When a site goes down, no one knows right away whether it’s the router, the SIM card, the carrier, or the equipment behind it. And when a security vulnerability requires an urgent update, deploying it across 200 routers takes weeks.

  • Inventory impossible to maintain manually: firmware version unknown at 30% of sites
  • Updating firmware at 100 sites requires 100 individual SSH connections
  • No proactive alerts: we only discover that a router has failed when the site hasn’t sent any data for 3 days
  • Inconsistent configuration across sites: each technician has their own version of the configuration
  • Troubleshooting in the dark: impossible to know if the SIM is active, the signal is strong, or the VPN connection is active
  • Unpatched security vulnerabilities due to the lack of a structured update process
  • No visibility into data usage per SIM: unexpected billing charges and data plan overages
  • VPN certificates and technician access cannot be tracked without a centralized tool

Our Approach

Eziwan centralizes the management of your entire fleet from a modern web console. ZTP (Zero Touch Provisioning) for new sites, configuration pushes by group or by site, schedulable firmware updates outside of production hours, and real-time monitoring with proactive alerts. A single tool to manage 10 to 500 industrial routers.

  • Zero-Touch Provisioning: A new router configures itself automatically when powered on
  • Configuration push by groups: Apply a change to 200 sites with a single click
  • Scheduled firmware updates outside of production hours with automatic rollback
  • Real-time monitoring: 4G signal, latency, data usage, VPN status
  • Configurable proactive alerts: low signal threshold, disconnection, unexpected reboot
  • Automatic monthly availability report with CSV/PDF export

Key Features

Zero-Touch Provisioning

Automatic configuration upon first startup using the serial number. A field technician can deploy a site without network training.

Configuration Push

Deploy a configuration to a site, a group, or the entire fleet with a single click. You can validate the configuration beforehand on a test site.

Scheduled Firmware Update

Schedule updates outside of production hours. Automatically roll back if the new version does not respond within 5 minutes.

Real-Time Network Diagnostics

4G signal (RSSI/RSRQ), ping latency, VPN status, recent reboots, data usage. All in 30 seconds without touching the router.

Proactive Fleet Alerts

Notification as soon as a router disconnects, restarts abnormally, reaches a data quota, or experiences signal degradation.

RBAC and Access Management

Configurable roles: field technician (read-only access to their sites), regional manager (management of their team), administrator (entire fleet). Logging of all actions.

SIM Monitoring and SIM Pooling

Data usage dashboard by SIM, router, and group. Threshold alerts before limits are exceeded. Optimization via SIM pooling to reduce costs by 20 to 40%.

REST APIs and ITSM Integrations

Comprehensive REST API for integrating Eziwan with your CMDB, ServiceNow, Jira, or existing monitoring system. Webhooks for automatically creating incident tickets.

VPN Certificate Management

Automatic renewal of OpenVPN certificates before they expire. Immediate revocation if a technician leaves the company. Scheduled rotation without service interruption.

Manual Management vs. Centralized Platform

The transition from manual management to a fleet management platform changes the economics of operations. The table below compares the two approaches for the most common operations, for a fleet of 100 industrial 4G routers.

OperationManual management (SSH on a site-by-site basis)Eziwan centralized platform
Deployment of a new site2 to 4 hours (on-site network technician)15 minutes (ZTP, non-specialized technician)
Firmware update for the entire fleet2 to 4 weeks, risk of oversight1 night, scheduled, automatic rollback
Global configuration change100 individual connections1 push per group, validation on a pilot site
Detection of an offline siteSeveral hours to several daysAlert in less than 2 minutes
Diagnosis of a connectivity failureOn-site visit almost always required30 seconds: signal, SIM, VPN, and uptime visible
Monitoring of SIM data usageCarrier bill at the end of the monthReal-time, threshold alerts, SIM pooling
Firmware/configuration inventoryOutdated spreadsheetDynamic, exportable, accurate inventory
Access traceability (NIS2)NonexistentComplete audit log for each action

Example of an Eziwan architecture for a multi-site fleet

The typical architecture of a managed fleet is based on a simple chain that is entirely outbound from a network perspective:

Industrial 4G routers at each site → multi-carrier M2M SIM card → encrypted outbound VPN tunnel → Eziwan cloud platform → fleet management console, alerts, and APIs.

Each router includes an agent that continuously reports its health status: 4G signal (RSSI, RSRP, RSRQ), active SIM status, data usage, uptime, firmware version, and VPN tunnel status. The platform aggregates this telemetry by group and triggers alerts based on your thresholds. No incoming ports are open at the sites: the router always initiates the connection, which meets OT cybersecurity and NIS2 compliance requirements.

Case Study: 180 Pumping Stations Managed by 2 People

A water utility operating 180 pumping stations and reservoirs spread across three departments replaced its aging GPRS modems with industrial 4G routers managed via the Eziwan platform. Results observed after one year of operation:

  • Initial deployment: 180 sites deployed in 6 weeks by the regular operations teams, thanks to Zero Touch Provisioning—no external network service providers.
  • Day-to-day operations: Two people (non-network specialists) manage the entire fleet, compared to an initial estimate of 1.5 FTE dedicated to manual management.
  • Availability: Measured availability rate of 99.7% across the fleet, with dual-SIM failover absorbing local carrier outages.
  • Responsiveness: Detection of an offline site in less than 2 minutes, compared to 24 to 72 hours previously (when the issue was discovered upon the absence of remote meter reading data).
  • Data Costs: Connectivity costs reduced by 30% thanks to SIM pooling and overage alerts.

Checklist Before Implementing a Fleet Management System

  1. Inventory the existing fleet: models, firmware versions, SIM operators, critical sites.
  2. Define groups: by region, business line, or criticality level—this is the key to a risk-free configuration rollout.
  3. Standardize configuration profiles: one profile per site type, versioned, and tested at a pilot site.
  4. Choose connectivity: multi-carrier M2M SIMs for remote sites, dual SIMs for critical sites.
  5. Define roles (RBAC): who sees what, who modifies what, with systematic logging.
  6. Schedule maintenance windows: Firmware updates outside of production hours, with automatic rollback enabled.
  7. Integrate alerts with your tools: Email, SMS, and webhooks to ITSM systems (ServiceNow, Jira) to automatically create tickets.

Further Reading

Frequently Asked Questions

You might also like