Remote Industrial Monitoring: The Complete Guide 2026

· 13 min read
13 min read
Eziwan Team
Eziwan Team
IoT Infrastructure

Remote industrial monitoring has become a strategic issue for French manufacturers. Between the phase-out of the 2G GPRS network (Bouygues and SFR will discontinue service by the end of 2026), the NIS2 Directive, which mandates enhanced cybersecurity measures, and pressure to reduce maintenance costs, companies must modernize their approach to remote monitoring.

This guide covers the entire subject: definitions, technical architectures, protocol selection, cybersecurity, and practical implementation for deployments ranging from 1 to 1,000 sites.

What is remote industrial monitoring?​

Remote industrial monitoring (or industrial telemetry) refers to the range of technologies that enable:

  • View the status of industrial equipment (machines, PLCs, sensors) from a remote location
  • Receive alerts in real time in the event of an anomaly, threshold exceedance, or failure
  • Remotely operate equipment (adjust setpoints, restart, reconfigure)
  • Analyze historical data to optimize performance and plan maintenance

It applies to all sectors: manufacturing, water and wastewater, energy, agriculture, and building services.

Monitoring vs. SCADA vs. IIoT: What Are the Differences?​

These terms are often confused. Here are the differences:

TermScopeInfrastructure
SCADA (Supervisory Control and Data Acquisition)Single site or network of sites with centralized architectureOn-premises server + local HMIs
Remote Monitoring / Remote SupervisionMulti-site, access from anywhereWAN (4G, fiber) + cloud or central server
IIoT (Industrial Internet of Things)Networked sensors & equipmentCloud, edge computing, APIs

In 2026, the lines between them are blurring: modern IIoT platforms (including Eziwan) offer cloud-based SCADA capabilities while integrating legacy industrial protocols (Modbus, OPC-UA).

Remote Monitoring Architectures​

Benefits:

  • Rapid deployment, with no on-site server infrastructure required
  • Access from any browser, tablet, or smartphone
  • Scalability from 1 to thousands of sites without requiring an architectural overhaul
  • Centralized updates with no on-site intervention required

Typical use cases: water utilities, power distribution networks, solar farms, and geographically dispersed fleets of industrial equipment.

Architecture 2: On-premises SCADA with VPN remote access​

Advantages:

  • Data remains within the company's IT infrastructure
  • Compatible with existing SCADA systems (Wonderware, WinCC, Vijeo Citect)
  • Full control over hosting and security

Typical use cases: large industrial companies with existing SCADA systems, industries with data sovereignty requirements.

Architecture 3: Edge Computing + Hybrid Cloud​

For sites that generate large amounts of data (production lines, presses, CNC machines), edge computing allows critical data to be processed locally and only aggregated data to be sent to the cloud.

Industrial Protocols for Remote Monitoring​

Modbus RTU/TCP — the universal standard​

Modbus is the most widely used protocol in the industry. It comes in two variants:

  • Modbus RTU: over an RS-485 serial connection. Up to 32 devices over 1,200 m of cable. Data rate: 9,600 to 115,200 bps.
  • Modbus TCP: Modbus encapsulation over Ethernet/IP. Port 502. Data rate limited only by the network.

What Modbus allows you to monitor: all modern industrial PLCs (Siemens S7, Schneider Modicon, ABB, Allen Bradley), as well as the vast majority of energy meters, variable-speed drives, and industrial sensors.

Limitation: Master/slave architecture only. No event notifications—the master must poll the slaves regularly.

MQTT — The IIoT Protocol​

MQTT (Message Queuing Telemetry Transport) is a lightweight publish/subscribe protocol designed for low-bandwidth connections.

Key Features for Remote Monitoring:

  • Persistent Connection: The MQTT client (gateway) connects to the broker once and maintains the session
  • Configurable QoS: Guaranteed delivery of critical messages (QoS 1 or 2)
  • Hierarchical topics: usine/ligne1/pompe3/courant — logical data structure
  • Last Will & Testament: automatic notification if a device disconnects

Cloud integration: MQTT is natively supported by AWS IoT Core, Azure IoT Hub, Google Cloud IoT, and HiveMQ.

OPC-UA — for demanding SCADA environments​

OPC-UA (Unified Architecture) is the interoperability standard for Industry 4.0.

Key Features:

  • Object-oriented information model (not just digital registers)
  • Built-in security: authentication, encryption, message signing
  • Compatible with major SCADA systems (WinCC, FactoryTalk, Ignition)
  • Standard for MES and ERP applications

When to choose OPC-UA: Integrations with existing SCADA, MES, and SAP ERP systems. Environments where data semantics (not just raw values) are important.

Cybersecurity in Remote Monitoring​

Remote industrial monitoring is a major attack vector if it is not properly secured. In 2024–2025, several incidents involved unsecured remote access to OT equipment.

The 5 Golden Rules of OT Cybersecurity​

1. No open incoming ports on the industrial network

The zero-inbound-port architecture is the fundamental principle: industrial devices themselves initiate the connection to the monitoring cloud. No RDP, VNC, or Modbus ports are directly exposed to the Internet.

2. VPN and Encryption Required

All communications between industrial sites and the monitoring platform must be encrypted. OpenVPN with AES-256-GCM encryption is the 2026 recommendation for new deployments.

3. Strong Authentication for Remote Access

Every technician accessing the system remotely must authenticate using a personal cryptographic key (not a shared password). Multi-factor authentication (MFA) is mandatory for entities subject to NIS2.

4. Principle of Least Privilege

A maintenance technician for a specific PLC has access only to that PLC—not to the entire OT network. Fine-grained access segmentation limits the spread of a breach.

5. Complete audit log

All remote connections, configuration changes, and actions are logged with a timestamp, user ID, and source IP address. These logs are required by the NIS2 directive for critical and important entities.

NIS2 and Remote Monitoring​

The NIS2 Directive (transposed into French law in October 2024) requires critical entities and important entities to implement specific measures for remote access:

  • Identity-based access control (no shared accounts)
  • Encryption of communications
  • Access logging and monitoring
  • Incident management with notification within 24 hours (critical entities)

Sectors involved: water and sanitation, energy, transportation, health care, waste management, and critical industrial production.

Practical Deployment: From 1 to 1,000 Sites​

For a single site (POC or pilot)​

Required equipment:

  • 1 IoT gateway with 4G connectivity and RS-485 interfaces
  • M2M SIM subscription (or use your carrier's SIM)
  • Access to the cloud-based monitoring platform

Deployment time: 2 to 4 hours for a technician (hardware installation + cloud configuration + Modbus data validation).

Estimated cost: €300–600 for equipment + €30–80/month for platform subscription + M2M SIM card.

For 10 to 50 sites​

At this scale, Zero-Touch Provisioning (ZTP) becomes essential for reducing deployment costs.

Eziwan ZTP Process:

  1. You set up a standard configuration in the cloud (protocols, alerts, VPN)
  2. Each gateway is shipped preconfigured from the factory (or configured remotely)
  3. On-site: connect power, SIM, and RS-485—the gateway configures itself
  4. Less than 30 minutes of technician time per site

Cost savings vs. manual configuration: For 50 sites, ZTP typically saves 2 to 3 person-days of network configuration time.

For 100+ sites (fleet management)​

For large fleets, centralized management features become critical:

  • Fleet Dashboard: Overview of connectivity and status for each site
  • Aggregated Alerts: Filtering of false alarms, automatic escalation
  • OTA firmware updates: Deploy updates across the entire fleet without on-site visits
  • SIM management: Data usage by site, one-click SIM replacement
  • Automated Reports: network availability, incidents, service calls—for CSR or contractual reporting

Real-World Use Cases​

Water utility — network of 80 pumping stations​

Previous situation: weekly supervisory rounds, 2–3 on-call shifts per week for emergency response.

Solution deployed: 80 4G LTE gateways with Modbus RTU, real-time alerts on pump levels and faults, and remote access for technicians via OpenVPN/IPSec.

Results:

  • Inspection rounds reduced by 70% (from weekly to monthly for routine checks)
  • Fault detection in less than 30 seconds (vs. 4–48 hours previously)
  • ROI achieved in 4 months

Food Processing Industry — 3 Production Sites​

Previous situation: Each site had its own local SCADA system, with no consolidated visibility at the group level.

Solution deployed: 3 IoT gateways that consolidate Modbus data from each site into a single cloud-based dashboard. Remote access for the group's maintenance team.

Results:

  • A single dashboard for all three sites (vs. three separate SCADA interfaces)
  • Incident response time reduced by 65%
  • Secure and traceable access for maintenance contractors

Solar Farm — 15 Power Plants​

Previous situation: Proprietary data loggers that were incompatible across different inverter manufacturers.

Deployed solution: IoT gateways with a universal Modbus parser supporting the SunSpec, SMA, ABB, and Fronius protocols. Performance monitoring dashboard (kWh, performance ratio, availability).

Results:

  • Consolidation of monitoring into a single dashboard
  • Detection of performance drops of +3% → planned preventive action
  • Automatic reports for investors and the network operator

Remote Monitoring Deployment Checklist​

Before launching your remote monitoring project, check the following:

Connectivity​

  • 4G LTE coverage verified at each site (carrier tests)
  • Dual SIM option evaluated for critical sites
  • Estimated data usage per site (Modbus polling frequency × register size)

Field Equipment​

  • Protocol inventory: Modbus RTU (RS-485), Modbus TCP, or proprietary?
  • List of variables to monitor per device (Modbus registers)
  • Power supply available in the cabinet (24V DC or 230V AC)

Cybersecurity​

  • Zero-inbound-port architecture selected
  • OpenVPN/IPSec or IPSec VPN planned
  • Technician access policy defined (permissions, time slots)
  • Is NIS2 applicable to your organization? (critical/important entities)

Cloud Platform​

  • Data hosted in France or the EU (GDPR)
  • API available for integration with existing SCADA/MES systems
  • Platform availability SLA (minimum 99.5%)

Conclusion​

Remote industrial monitoring is no longer an option in 2026: the phase-out of 2G GPRS, the NIS2 Directive, and economic pressure to reduce maintenance costs make it a necessity for all industrial companies with remote sites.

The good news: With 4G LTE solutions featuring Zero-Touch Provisioning, you can now connect an industrial site in less than an hour, for less than 50€/month, all-inclusive.

The key to success is choosing a secure cloud-native architecture from the start—not adding security as an afterthought on top of an architecture that wasn't designed for it.

FAQ — Remote Industrial Monitoring​

What is the difference between SCADA and cloud-based IoT monitoring?

A traditional SCADA system is a centralized (often on-premises) system with thick clients (dedicated PC software), local data archiving, and a star architecture. Cloud-based IoT monitoring is a distributed architecture: each site sends its data to the cloud via a gateway, without a central on-site server. The cloud offers multi-site access, mobile access, and a REST API for integration—whereas traditional SCADA requires a site-to-site VPN and a license per client. The two can coexist via OPC-UA or Modbus connectors to the existing SCADA system.

How many variables can be monitored simultaneously across 100 sites?

There is no fixed limit on the cloud side—modern IIoT platforms are designed to handle millions of measurement points. The practical limit lies with the gateway and network: a standard gateway collects up to 500 Modbus variables per site with a 5-second polling interval, or 6,000 values per minute per site. Across 100 sites, that’s 600,000 values per minute—manageable if the cloud is scaled accordingly (time series, site-based partitioning).

Can remote monitoring work if the PLC is in STOP mode (program stop)?

Yes, for monitoring the PLC's status (CPU in STOP mode, time of last alarm, I/O status). No for Modbus collection of process variables—the PLC’s Modbus TCP server stops responding in STOP mode on certain models (the S7-1200 stops the MB_SERVER when in STOP mode). Check the specific behavior of the PLC in STOP mode before relying on Modbus data collection to detect CPU stops.

What is the minimum latency between a state change on the PLC and its appearance on the dashboard?

With a 1-second Modbus polling interval and a properly sized cloud infrastructure, the total latency is typically 2 to 5 seconds (1 second of polling wait time + 1 to 2 seconds of 4G transit time + 1 to 2 seconds of cloud processing time). For critical alarms (threshold exceedances), Eziwan can send SMS/email notifications in less than 10 seconds after detecting the exceedance. For a real-time response (< 100 ms), local logic is required on the PLC or gateway—not the cloud.

Can non-Ethernet devices (RS-485 meters, 4-20 mA sensors) be monitored?

Yes, via the gateway's RS-485 port for Modbus RTU, and via the analog inputs for 4–20 mA or 0–10 V signals. Sensors without a digital protocol (simple dry contacts, level switches) connect to the digital inputs of the gateway or an expansion module. The goal is to monitor the entire site from a single gateway, regardless of the heterogeneity of the equipment.

Additional Resources​

Additional Resources​