Industrial IoT devices used by utilities are no longer simple communication accessories.
Routers, modems, gateways and data loggers installed in substations, meter cabinets, pumping stations or remote industrial sites become operational assets.
If they cannot be updated, diagnosed, secured and managed remotely, the utility inherits avoidable field visits, weak configuration control and long-term security risk.
For procurement teams and IT/OT managers, this creates a practical problem.
Tender documents often specify cellular technology, interfaces and environmental ratings in detail, but remote management requirements remain vague.
Phrases such as “remote management support required” are not enough.
A good tender should define what remote management must do, who can use it, how it is secured, how it integrates with existing systems and how acceptance will be tested before rollout.
Remote management is the ability to configure, update, monitor, diagnose and secure deployed IoT devices without sending a technician to the installation site.
For utility projects, this usually applies to cellular routers, industrial modems, smart metering gateways, data concentrators and data loggers.
In practice, remote management covers:
It is not just a software feature. It is part of the operating model of the whole device fleet.
Utilities often evaluate industrial IoT devices on hardware features first:
These are important, but they do not answer the full operational question.
After deployment, the utility must manage hundreds, thousands or tens of thousands of devices over many years.
During that lifecycle, teams may need to:
Without clear remote management requirements, the project may work during pilot testing but become expensive during operation.
Before writing technical clauses, define who will operate the device fleet.
Key questions to answer:
This operating model changes the tender language.
A municipality with a small water metering deployment may need simple diagnostics and configuration backup.
A DSO managing remote grid assets may require stricter access control, audit logs, encrypted communication, controlled firmware rollout and long-term support commitments.
A strong tender should define the minimum functions required for the full device lifecycle.
The following areas are usually the most important.
Firmware updates affect security, stability, interoperability and long-term device usability.
A tender should not only ask whether firmware updates are possible. It should define how they are controlled.
Specify at least the following:
Example tender wording:
The device management system shall support remote firmware updates for deployed devices. The bidder shall describe the update process, including authentication, transfer security, update validation, failure handling, rollback or recovery options and reporting of update status.
Remote configuration is often more valuable than firmware updating in daily operation.
Many utility issues are caused by APN changes, protocol settings, server address changes, VPN parameters, polling intervals or meter interface settings.
Configuration areas to include:
Practical requirement:
The system should allow authorized users to change configurations remotely and track what was changed, when and by whom.
For large fleets, group-based configuration is important. If every device must be changed manually, the operational workload becomes too high.
Configuration backup is often forgotten until a device fails.
For utilities, backup and restore can reduce site visit time and simplify device replacement.
If a router or gateway must be replaced in the field, the technician should not need to rebuild the configuration manually from old emails, spreadsheets or screenshots.
Tender requirements:
Acceptance test idea:
During factory acceptance testing, ask the bidder to configure a device, back up the configuration, reset or replace the device, then restore the configuration and prove that communication is re-established.
Remote diagnostics determine how quickly a utility can understand a fault without sending a technician to site.
A tender should define the minimum diagnostic data required.
Useful diagnostic data:
Diagnostics should be available in a structured way, not only through manual command line access.
Logs are essential for troubleshooting intermittent problems.
For example, a device may lose connection only at certain times, after a network change, during poor signal conditions or when a backend server is unavailable.
Without logs, the operator sees only that the device is offline.
Tender requirements for logs:
The tender should also define whether logs must be exportable for analysis or compliance reporting.
Remote management creates operational value, but it also creates security responsibility.
A tender should avoid shared administrator accounts.
Role-based access control, or RBAC, is important when multiple teams are involved.
Roles to consider:
Each role should have only the permissions it needs.
Tender requirement:
The remote management system shall support user authentication and role-based access control. The bidder shall describe available user roles, permission granularity, password policy options and support for integration with enterprise identity systems where available.
Audit trails are different from technical logs.
Logs help troubleshoot device behavior. Audit trails help prove who did what.
For utility environments, this matters because configuration changes can affect billing data, SCADA communication, metering availability or security posture.
Audit trail requirements:
Audit trails are especially important when external system integrators or service providers have access to the fleet.
Security requirements should be specific.
Asking for a “secure device” is not enough.
Tender documents should define the expected security architecture without forcing a single implementation unless the utility has a strict internal standard.
Areas to specify:
For critical infrastructure, the tender should also ask the bidder to describe how the solution supports network segmentation and controlled access between IT and OT environments.
A utility cannot manage what it cannot see.
Fleet inventory should be part of remote management, especially when devices are deployed across many regions or subcontractors.
Useful inventory fields:
Inventory data should be exportable. Many utilities need to connect this information with asset management, ticketing or maintenance systems.
Remote management should not become another isolated system.
For larger deployments, the tender should ask whether the management platform can exchange data with other systems.
Integration points to consider:
Not every utility needs deep integration at the start.
Still, asking the question during procurement protects the project from future lock-in.
Remote management is not only software functionality.
Utilities also need to know what happens when something does not work.
SLA questions for bidders:
For tenders, it is useful to separate warranty support, operational support and project engineering support.
They are not the same thing.
Lifecycle topics to include:
This is particularly important for cellular deployments.
Network technologies, SIM platforms, APN configurations and operator policies can change during the lifetime of a utility project.
Acceptance testing should prove remote management capabilities before mass deployment.
A common mistake is to test only basic connectivity.
The device connects, sends data and passes the pilot.
Later, the utility discovers that firmware updates, audit logs or configuration restore were never properly tested.
Recommended acceptance tests:
Use this checklist when preparing a tender for industrial IoT routers, modems, gateways or data loggers.
WM Systems develops industrial IoT devices for utility and industrial communication, including routers, modems, gateways, data concentrators and data loggers.
Its portfolio also includes remote device management capabilities for managing deployed devices such as routers and modems.
For buyers, the important point is not to treat remote management as an optional extra.
Whether the project uses WM Systems equipment or another vendor’s devices, the tender should define how the fleet will be configured, updated, diagnosed, secured and supported over its full operating life.
In WM Systems projects, these discussions are especially relevant where utilities need cellular communication, smart metering connectivity, industrial router deployment, data concentrator operation or secure remote access for distributed field assets.
Remote management means the ability to configure, update, monitor, diagnose and secure deployed devices without visiting the site. For utilities, this can reduce field visits and improve operational control.
Because remote management affects lifecycle cost, security, maintenance and support. If it is not specified before procurement, the utility may discover important limitations only after deployment.
No. Firmware update support is important, but utilities also need configuration control, backup and restore, diagnostics, logs, access control, audit trails and lifecycle support.
The biggest mistake is using vague language such as “remote management required”. The tender should define exact functions, security controls, user roles, logging requirements and acceptance tests.
It depends on the utility’s IT/OT policy, security requirements and operating model. The tender should state whether cloud, on-premise or hybrid management is acceptable.
They should include acceptance tests for firmware update, remote configuration, backup and restore, diagnostics, log retrieval, RBAC, audit trails and group operation.
Remote management requirements should be written into the tender before devices are selected.
For utility and DSO projects, the long-term cost of an industrial IoT deployment is rarely determined only by the device purchase price.
It is shaped by firmware maintenance, configuration control, diagnostics, access management, auditability, security, support and the number of site visits required during operation.
A strong tender does not simply ask for “remote management”.
It defines the functions, controls, integrations and acceptance tests needed to operate the device fleet safely and efficiently.
That makes procurement clearer, evaluation more objective and field operation more predictable.
Planning an industrial IoT or utility communication tender?
Define remote management requirements before device selection. WM Systems can support projects where secure connectivity, remote device operation and long-term fleet management are part of the procurement challenge.
Contact Us to find the best solution for your tender requirements.
| Requirement area | Weak tender wording | Strong tender wording |
| Firmware | Remote firmware update required | The system shall support authenticated remote firmware updates, staged rollout by device group, update status reporting and recovery procedure after failed update. |
| Configuration | Remote configuration required | Authorized users shall be able to change APN, VPN, reporting interval and protocol settings remotely, with change history and user attribution. |
| Backup | Backup support required | The system shall support export, scheduled backup, pre-update backup and restore to a replacement device where technically possible. |
| Diagnostics | Device status visible | The system shall show online status, cellular signal, SIM/operator status, VPN state, uptime, last reboot reason and last successful data transmission. |
| Access control | User login required | The system shall support role-based access control with separate read-only, configuration, firmware, security admin and vendor support roles. |
| Audit | Logs required | The system shall maintain exportable audit records for logins, configuration changes, firmware updates, role changes and remote reboot actions. |
A practical guide for utilities, DSOs and system integrators on how to define firmware updates, configuration backup, diagnostics, access control and auditability before buying industrial IoT devices.
How utilities can achieve smart water metering fast—without replacing millions of working meters
Why Cheap Smart Meter Modems Are a Budget Trap
Secure LAN-Based meter communication via Industrial DIN-Rail Router
And What It Means for Industrial IoT?
Why On-Device Applications Are Becoming Essential in Industrial IoT
Amanah Teknologia & WM Systems Deploy Industrial IoT Routers for Masaha Construction
How ELMŰ-ÉMÁSZ and WM Systems solved technical challenge of modernizing legacy medium-voltage switchgear to enable real-time monitoring and automation in an environment with limited space and strict installation constraints
How WM Systems and ELMŰ-ÉMÁSZ Modernized Medium-Voltage Network Monitoring in Hungary
The essential communication hub that connects electricity meters to utility systems
