Pumping stations, electrical substations, elevated reservoirs, quarries, wind farms, lift stations, mining sites, or agricultural facilities: a remote industrial site can no longer rely solely on on-site visits. With an Eziwan gateway, remote monitoring combines 4G LTE connectivity, a secure VPN, dual SIM, Modbus data collection, satellite backup, local alerts, and measurement history to make the site visible, controllable, and maintainable from a centralized dashboard.
Why Remote Industrial Sites Are Difficult to Monitor
A remote site is not just a site that is far away. It is often an environment where several challenges converge: no fiber-optic connectivity, inconsistent cellular coverage, limited power supply, outdated equipment, difficult physical access, severe weather, the risk of vandalism, and a lack of on-site staff.
Without real-time monitoring, every anomaly becomes an investigation. The technician travels to the site, arrives several hours after the incident, checks the PLC or the local HMI, and then tries to piece together what happened with very little data. Sometimes the outage has already been resolved, sometimes it has worsened, and the root causes remain unclear.
The most common difficulties are:
- lack of visibility between two field rounds;
- trips made solely for routine condition checks;
- delayed diagnostics due to a lack of usable historical data;
- gradual drifts that go undetected until a failure occurs;
- Local alarms that are not visible from the operations center;
- On-call alerts triggered without technical context;
- Data loss during a network outage;
- Reliance on a single mobile operator;
- inability to open incoming ports for security reasons;
- dead zones requiring backup satellite or radio connectivity;
- physical risks detected too late: intrusion, open door, abnormal temperature, power failure.
Monitoring of remote sites must therefore be approached as a comprehensive architecture: local data collection, resilient communication, OT security, alerts, autonomy, and multi-site operations.
Target Architecture for a Supervised Isolated Site
The recommended architecture places an Eziwan industrial gateway as close as possible to the field equipment. It collects local data via Modbus RTU, Modbus TCP, digital inputs, sensors, or industrial PLCs, then transmits it to a centralized platform via 4G LTE, 5G (when available), Ethernet, satellite, or a backup connection.
This architecture prevents PLCs from being exposed to the Internet. The gateway initiates an encrypted outbound tunnel to the concentrator, which works even behind an ISP’s NAT and simplifies site security.
The Objectives of Remote Industrial Monitoring
Remote monitoring is not just about displaying readings on a screen. It should improve operations, reduce unnecessary travel, and provide teams with the information they need to take action at the right time.
The priority objectives are:
- monitor the site’s status in real time;
- detect faults before production shutdowns or service interruptions;
- log critical measurements;
- alert the appropriate personnel based on the time of day and severity;
- provide secure access to the PLC or HMI;
- Maintain local alert capabilities in the event of an Internet outage;
- Compare multiple sites from a single interface;
- Document incidents to improve maintenance;
- Secure OT data flows without public ports;
- Keep a record of accesses and actions.
tip Guiding Principle A remote site must remain operational even when network connectivity is degraded. The gateway must therefore be able to collect data, buffer it, trigger local alerts, and resume synchronization as soon as connectivity is restored.
Collecting Field Data: Modbus, RS-485, TCP, and Local Inputs
The first step is to collect the right data—not all data. At a remote site, bandwidth, available power, and operational visibility are just as important as the breadth of measurements.
The most common sources are:
- PLC;
- local HMI;
- variable-speed drive;
- electric meter;
- pressure sensor;
- temperature sensor;
- flow meter;
- tank level sensor;
- door-open sensor;
- fault relay;
- inverter;
- solar controller;
- weather sensor;
- camera or perimeter detector when warranted by the situation.
| Source | Common Protocol | Useful Data | Usage |
|---|---|---|---|
| PLC | Modbus TCP | statuses, faults, setpoints | process monitoring |
| RS-485 Sensors | Modbus RTU | pressure, level, flow | field monitoring |
| Energy Meter | Modbus RTU or TCP | voltage, current, kWh | energy and autonomy |
| Local HMI | Ethernet | system status, alarms | diagnostics |
| Digital inputs | dry contact | door open, relay fault | safety and local alerts |
| Inverter or solar | Modbus | battery, charge, generation | energy autonomy |
A mapping of data points must specify the name, unit, frequency, alert threshold, criticality, and business owner. This approach prevents dashboards from being filled with unusable values.
4G LTE Connectivity and Dual SIM
4G LTE is often still the best solution for connecting a remote industrial site: extensive coverage, manageable costs, sufficient bandwidth for monitoring, and a short deployment time. But a single carrier isn’t always enough.
Dual SIM allows you to use two different carriers and automatically switch when the active connection becomes unavailable or the signal quality is too poor. The switch can be triggered by several signals:
- Loss of the VPN tunnel;
- Loss of IP connectivity;
- Excessively high latency;
- Persistent packet loss;
- Insufficient radio signal;
- DNS resolution failure;
- Unable to connect to the monitoring platform.
Caution: Network Failover A failover that occurs too quickly can cause instability. You should include delay periods, perform several consecutive tests, and implement a controlled fallback to the primary link.
Satellite Backup for Areas Without Coverage
Some locations do not have reliable cellular coverage, or may only have it at certain times depending on network load and radio conditions. In these cases, a satellite modem can serve as the primary connection or as a backup.
The satellite is particularly useful for:
- 4G dead zones;
- mountainous areas;
- mining sites;
- remote port areas;
- remote renewable energy facilities;
- temporary construction sites;
- continuity of alerts for critical infrastructure.
Satellite backup should be used judiciously. Depending on the technology chosen, latency, data costs, weather availability, and power consumption may vary. It is therefore best to reserve satellite use for essential data flows: alerts, critical statuses, authorized commands, compressed history synchronization, and occasional diagnostic access.
Secure VPN without a public port
A remote site is often more vulnerable than an urban site: there is little physical surveillance, equipment is exposed, maintenance visits are infrequent, and connectivity is sometimes set up in a hurry. It is therefore essential never to expose a PLC, HMI, or router interface directly to the Internet.
Eziwan uses an outbound tunnel architecture: the gateway establishes an encrypted VPN connection to a central hub. Authorized technicians then access the equipment through this tunnel, in accordance with filtered rules.
Best practices include:
- No open incoming ports to the OT network;
- Encrypted OpenVPN or IPsec tunnel;
- Individual certificates;
- Strong authentication for sensitive access;
- Filtering by IP, port, and protocol;
- Connection logging;
- Rapid revocation of access;
- Separation of monitoring, maintenance, and administration.
To learn more about this topic, you can consult the guide on OT network security and industrial connectivity solutions.
Smart Alerts: Avoid Noise, Detect What Matters
A useful alert must be precise, contextualized, and actionable. A simple message stating “défaut site” is not enough. The on-call team needs to know which site is affected, which equipment is involved, which metric has exceeded the threshold, how long this has been going on, and what action is recommended.
Alerts may pertain to:
- high or low threshold;
- slow drift;
- loss of communication with the PLC;
- loss of VPN tunnel;
- SIM failover;
- low battery;
- power supply failure;
- intrusion or open door;
- high enclosure temperature;
- critical tank level;
- abnormal pressure;
- loss of flow;
- stuck meter;
- UPS failure;
- cloud synchronization failure.
A good alert system must also handle escalation. If the first recipient does not acknowledge receipt, the alert can be forwarded to a second level.
Local Alerts Without Internet
Cloud monitoring is useful, but an industrial site sometimes needs to take action locally even if the connection is down. That’s where autonomous local alerts come in.
The gateway can control a relay, a digital output, or a dry contact to trigger:
- alarm;
- indicator light;
- shutdown of a non-critical power supply;
- valve closure;
- local safety shutdown;
- command to a PLC;
- message to a local HMI.
These actions must remain simple and well-documented. Process safety logic must continue to be handled by the PLCs and systems designed for that purpose. The supervisory gateway must not replace an instrumented safety function.
Logging and Resuming After a Disconnection
Remote sites often experience temporary network outages. However, data collection should not stop as a result. A robust architecture includes a local buffer: measurements are stored in the gateway and then synchronized once the connection is restored.
The history feature helps answer questions that real-time data alone cannot address:
- When did the drift begin?
- How long was the equipment in a fault state?
- Is the failure related to a voltage drop?
- Is the battery discharging faster than expected?
- Is the tank level changing at the expected rate?
- Does a fault always occur after a restart?
- Does the SIM failover actually improve availability?
| Historical data | Typical frequency | Operational value |
|---|---|---|
| Pressure | 1 to 5 minutes | leak or clog detection |
| Level | 5 to 15 minutes | anticipatory filling or draining |
| Energy | 5 to 15 minutes | monitoring battery life and anomalies |
| Cabinet temperature | 5 minutes | Overheating prevention |
| VPN status | Event | Availability analysis |
| PLC alarms | Event | Incident diagnosis |
| SIM failover | Event | Operator quality monitoring |
The exact frequencies must be tailored to the process, data volume, connectivity, and battery life.
Multi-site Dashboard
An operator doesn’t just oversee a single site. They often oversee an entire network: pumping stations, remote management cabinets, secondary electrical substations, reservoirs, renewable energy sites, or customer equipment.
A multi-site dashboard should allow you to quickly see:
- sites operating normally;
- sites in alarm mode;
- sites with no communication;
- active operator;
- signal quality;
- power autonomy;
- latest events;
- critical measurements;
- acknowledged or unacknowledged alarms;
- history by site;
- comparison between similar sites.
The goal is to prioritize responses. A site that has lost communication for two minutes does not have the same level of urgency as a site with a low battery, a pump failure, and a critical liquid level.
Solar Energy and Self-Sufficiency
Some remote sites do not have a reliable, continuous power supply. In such cases, the monitoring system must include energy management: solar panels, batteries, controllers, inverters, gateway power consumption, and communication cycles.
The key points to watch for are:
- battery voltage;
- charging current;
- solar regulator status;
- power consumption;
- enclosure temperature;
- estimated time until critical threshold;
- cut-off and restart cycles;
- satellite link data usage, if used;
- standby strategy.
Battery Life Information At a battery- or solar-powered site, the frequency of data collection and transmission must be chosen carefully. Sending non-critical data less frequently can extend battery life without compromising operational safety.
Remote Maintenance and Equipment Access
Monitoring provides visibility. Secure remote access enables action. The two must be separated in terms of permissions.
An operator can access the dashboard and alarms, while an automation engineer can, with authorization, have temporary access to a PLC or an HMI. This separation prevents a read-only account from gaining full access to the OT network.
Example of an access policy:
Position: On-Call Automation Engineer
Authorized sites: northern stations
Authorized equipment: PLC for Pump 1, local HMI
Supported protocols: Modbus TCP, local HTTPS
Authentication: Certificate and MFA
Session duration: 2 hours
Plage horaire : astreinte active
Logging: complete
Termination: effective immediately upon expiration of the contract
This approach is particularly important when subcontractors are working at remote sites.
Common Use Cases
Remote monitoring of remote sites is applicable to many environments.
| Sector | Monitored Equipment | Critical Data |
|---|---|---|
| Water and Wastewater | pumps, tanks, valves | level, flow, pressure, pump failure |
| Energy | substations, inverters, batteries | voltage, temperature, circuit breaker status |
| Mining and Quarries | conveyors, pumps, power units | operational status, faults, vibration, power |
| Agriculture | irrigation, silos, refrigeration | humidity, level, temperature |
| Wind and Solar | inverters, substations, weather | production, faults, communication |
| Off-Grid Logistics | refrigeration units, access, power | temperature, door, power supply |
| Telecom and Infrastructure | shelters, batteries, air conditioning | power, temperature, intrusion |
| Mobile Industry | temporary machinery, job sites | status, usage, geolocation if authorized |
Every sector has its own priorities, but the foundation remains the same: reliable data, resilient communication, useful alerts, and controlled security.
Example of a point layout for a pumping station
| Item | Source | Threshold or Rule | Alert |
|---|---|---|---|
| Tank level | analog sensor | high and low thresholds | on-call SMS |
| Discharge pressure | Modbus RTU | gradual drift | maintenance email |
| Pump 1 status | PLC | active fault | priority SMS |
| Motor current | meter | abnormal value | CMMS ticket |
| Cabinet door | digital input | opened outside scheduled hours | security alert |
| Battery voltage | Solar controller | Delayed low threshold | Energy alert |
| VPN tunnel | Gateway | Connection loss | Network monitoring |
| Cabinet temperature | Internal sensor | High threshold | Preventive maintenance |
This type of plan makes monitoring concrete: each piece of data has a purpose, a threshold, a recipient, and an associated action.
CMMS, SCADA, and API Integration
Eziwan can function as an operational dashboard, but it can also feed data into existing tools.
Common integrations include:
- Central SCADA system;
- CMMS;
- IoT platform;
- on-call system;
- SIEM;
- data lake;
- maintenance ERP;
- webhook to internal tool;
- CSV or JSON export for analysis.
| Destination | Data Sent | Purpose |
|---|---|---|
| SCADA | real-time status and measurements | centralized monitoring |
| CMMS | Faults and qualified alarms | Ticket creation |
| SIEM | VPN connections and events | Cybersecurity |
| Data platform | Time series | Advanced analytics |
| Webhook | Critical alerts | Business automation |
The choice depends on the organization’s level of digital maturity. For some customers, the Eziwan dashboard is sufficient. For others, the value comes from integration with their existing SCADA or CMMS systems.
OT Security and Field Hardening
A remote site may be physically accessible, but it is rarely monitored around the clock. Cybersecurity must therefore be supplemented by on-site security measures.
Best Practices:
- Install the gateway in a locked cabinet;
- Disable unnecessary services;
- Use individual certificates;
- Enable MFA for maintenance access;
- Block incoming traffic on public ports;
- Filter traffic to PLCs;
- Separate the OT network from the monitoring network;
- Log connections;
- Back up the configuration;
- Document SIM cards, antennas, and routes;
- Establish a revocation procedure;
- Test recovery after hardware replacement.
For critical sites, the approach can be aligned with the principles of IEC 62443 and the ANSSI recommendations on industrial systems.
Typical Deployment with Eziwan
A remote monitoring project can be rolled out in phases.
1. Site Inventory
Identify any controllers, sensors, meters, digital inputs, power supplies, cabinets, antennas, and physical constraints.
2. Connectivity Audit
Test the available mobile carriers, the locations of the cell towers, signal quality, and whether a satellite backup is needed.
3. Mapping Points
Select the critical metrics, useful reports, alarms, thresholds, and collection frequencies.
4. Installing the gateway
The Eziwan gateway is connected to field devices, the mobile network, any backup link, and local inputs or outputs.
5. Securing the Tunnel
The outbound VPN connection is established to the platform or hub. Access rules for OT devices are limited to what is strictly necessary.
6. Configuring Alerts
Thresholds, timeouts, recipients, on-call schedules, escalation procedures, and local actions have been configured.
7. Break Tests
Simulate a 4G outage, a SIM switch, an Internet outage, a local alarm, and a synchronization resumption.
8. Commissioning
The site is added to the multisite dashboard, along with its history, user permissions, support procedures, and documentation.
Common Pitfalls
Several common mistakes recur in remote site monitoring projects.
- choosing a SIM card without field testing it;
- placing the antenna inside a metal cabinet;
- collecting too many unnecessary data points;
- forgetting the local buffer in the event of an outage;
- sending too many unqualified alerts;
- using a VPN with overly broad access to the OT network;
- Neglecting power autonomy;
- Failing to test the satellite backup;
- Forgetting the conditions for returning to normal operation after a switchover;
- Failing to document thresholds;
- Ignoring subcontractors’ access;
- Confusing monitoring with process safety functions.
A reliable architecture is proven above all in degraded conditions: network loss, power outage, critical alarm, operator takeover, reboot, and hardware replacement.
How Eziwan Fits Into Your Industrial Monitoring System
Eziwan provides the connectivity and monitoring layer between field equipment and operations teams. The Eziwan gateway collects data on-site, industrial connectivity solutions secure remote connections, and the cloud platform centralizes dashboards, alerts, historical data, and multi-site access.
This approach makes it possible to modernize monitoring without immediately replacing existing PLCs. It is suitable for new sites, legacy installations, and multi-site networks that need to gain greater visibility without deploying a complex network infrastructure.
Conclusion
Remote monitoring of remote industrial sites requires more than just a 4G router. It requires an industrial gateway capable of collecting field data, securing OT access, switching between carriers, using a satellite backup if necessary, triggering local alerts, and maintaining a usable history.
With Eziwan, teams can monitor their stations, posts, tanks, energy equipment, or temporary sites from a centralized dashboard, while reducing unnecessary travel and improving diagnostics. Remote sites become visible, measurable, and manageable, even when connectivity is limited.
Further Reading
- Internet Connectivity for Remote Industrial Sites — connectivity solutions for sites without fiber or ADSL coverage
- Solutions for Remote Sites — turnkey monitoring and connectivity for remote environments
- Generator Monitoring — monitor the status and power consumption of your generators in real time
- Industrial 4G Backup — Ensure continuous monitoring with a 4G LTE backup link
- Industrial Connectivity — Compare technologies to connect your remote sites sustainably