Multi-site Operators — Monitor your plants, stations, and high-voltage substations from headquarters

You manage dozens—sometimes hundreds—of industrial sites spread across a region. Each site has its own PLC, sensors, and critical thresholds. The volume of information to be processed exceeds what a team can handle manually.

Centralized multi-site monitoring is not just a convenience tool. It is a driver of operational productivity, reduced travel, regulatory compliance, and data-driven decision-making.

The Problem of an Operator Without a Centralized View​

Operating Blindly​

Without centralized oversight, each site is a black box. Information comes in a fragmented and reactive manner:

  • Delayed detection: The team learns of a pump failure when production stops or when a user calls—rarely before then. The time between the start of an incident and its detection is typically 2 to 8 hours.
  • Poorly targeted on-call assignments: The on-call technician heads out without knowing what they’ll find. Between 30 and 50% of on-call trips are “false alarms”—problems that resolved themselves, false alarms, or issues that do not warrant a nighttime response.
  • Lack of data: It is impossible to analyze trends, identify deteriorating equipment, or justify replacement investments to management or a project owner.
  • Time-consuming reporting: Producing monthly or annual reports (pumped volumes, availability rates, incidents) requires several days of manual data consolidation.

Hidden Costs​

On-site visits: Across a network of 80 stations, with one unnecessary on-call visit per site per year at €500 per technician-day, that amounts to €40,000 per year in avoidable costs.

Poorly Prepared Service Calls: A technician who arrives on site without knowing what to expect often has to leave to find the right part. Each round trip costs €200 to €400.

Regulatory non-compliance: For water and wastewater operators, an undetected overflow of a retention tank can lead to an overflow into the distribution network, resulting in environmental consequences and contractual penalties.

The Solution: A Unified Dashboard for All Your Sites​

Principles of the Eziwan Platform​

Eziwan consolidates data from all your sites in real time into a cloud-based dashboard accessible from any browser or mobile app. The architecture is designed for fleets ranging from 10 to 500+ sites, with consistent performance across the board.

Data reported by each gateway:

  • Process variables: levels, flow rates, pressures, temperatures, currents, machine statuses
  • Connectivity data: 4G signal, gateway availability
  • Events: starts, stops, alarms, acknowledgments
  • System information: firmware version, VPN status, last synchronization

Key Dashboard Features​

Map view of the sites​

The main view displays all of your sites on an interactive map, with a color-coded status for each site:

Green: Site connected, no active alarms
Orange: Active Alert (threshold exceeded, abnormal condition)
Red: critical alarm or loss of connectivity
Gray: gateway offline (power outage, network issue)

At a glance, the operations operator can see which sites require attention. Clicking on a site opens the detailed view.

Detailed view by site​

From the site view, the operator can access:

Real-time variables:

  • All monitored variables with their current values
  • Status indicator (normal / pre-alarm / alarm)
  • Timestamp of the last measurement received
  • Alarm acknowledgment button

Historical Charts:

  • Trend lines for each variable over 1 hour, 6 hours, 24 hours, 7 days, 30 days, or a custom time range
  • Overlay of multiple variables on the same chart (e.g., tank level + pump status)
  • Zoom and scroll through the history

Event Log:

  • Timeline of all site events: alarms, restarts, status changes, user logins
  • Can be exported to CSV for incident reports

VPN Access:

  • Button to connect via VPN to the site's local network (with MFA)
  • Connect to TIA Portal, EcoStruxure, or an engineering tool through this tunnel

Comparative Multi-Site Dashboard​

For operators managing similar sites (a network of pumping stations, a network of substations), the comparison table allows them to view the KPIs for all sites on a single page:

Site | Tank Level | Pump 1 | Pump 2 | Flow Rate | Last Incident
──────────────|──────────────|─────────|─────────|─────────|─────────────────
SP-01 Mornas  | 78%  ✓ | Running | Stopped | 45 m³/h | 3 days ago
SP-02 Bollène | 45%  ✓ | Stopped | Stopped | 0 | Today at 8:23 a.m. ⚠
SP-03 Orange  | 92%  ⚠ | Running | Running | 89 m³/h | 12 days ago
...

This format makes it possible to immediately identify anomalies (SP-02: pumps have been shut down with no flow since this morning; SP-03: very high level).

Configuring Alerts​

Philosophy: Gradual Adjustment to Prevent Alarm Fatigue​

A poorly configured alerting system generates too many alerts, which are then ignored by the teams. The recommended configuration follows a three-level hierarchy:

Level 1 — Information (team email, business hours):

Pre-alarm: Tarpaulin level > 80%
Pump 2 (backup) starts up even though Pump 1 is available
Motor current > 105% of the reference value

Level 2 — Alert (text message + email, at any time):

Tarp Level Alarm > 90%
Thermal failure of a pump
Pumps have not been activated for more than 4 hours (level > 40%)
Abnormal temperature on the variable-speed drive

Level 3 — Emergency (On-Call SMS + Webhook + Escalation):

Very high tarpaulin level alarm > 95% → risk of overflow
Two simultaneous faults (station out of service)
Power Outage
Loss of gateway connectivity for more than 15 minutes
Courant moteur < 30% nominal (fonctionnement à sec)

Alert Channels​

ChannelUse CaseResponse Time
SMSUrgent alerts, on-call duty< 30 seconds
EmailPre-alerts, reports< 1 minute
WebhookITSM integration, automatic ticket creation< 30 seconds
Push notification (app)All alerts for mobile teams< 30 seconds
Phone callUnacknowledged critical emergencyUpon escalation

Alerts can be configured with time ranges: a non-critical error triggers an email during business hours and a text message to the on-call staff outside of business hours.

Integration with Existing Systems​

Existing SCADA System​

For operators who already have a SCADA system (Wonderware, Ignition, WinCC, PCVUE) at certain sites, Eziwan can coexist with and complement it:

Complementary Mode: Eziwan monitors sites without a local SCADA system (or with heterogeneous SCADA systems), while the existing SCADA system monitors sites that are equipped with it. The Eziwan dashboard provides a unified view of the entire fleet.

Integration Mode: The Eziwan REST API allows data to be fed into a centralized SCADA system or a business intelligence platform. The SCADA system receives data from Eziwan via the API and consolidates it with its local data.

# SCADA Integration via the Eziwan REST API
import requests

# Retrieve the latest values for a site
response = requests.get(
    "https://api.eziwan.com/v1/sites/SP-42/variables",
    headers={"Authorization": "Bearer <api_key>"},
    params={"limit": 1}  # Last value of each variable
)
variables = response.json()["data"]

# Retrieve active alarms across the entire fleet
alarms = requests.get(
    "https://api.eziwan.com/v1/organization/alarms/active",
    headers={"Authorization": "Bearer <api_key>"}
).json()

Ticket Management Systems (ITSM)​

Eziwan webhooks allow you to integrate alerts into your ticket management systems:

  • ServiceNow: Automatic creation of an incident upon a critical alarm
  • JIRA Service Management: Preventive maintenance ticket for current deviation
  • GLPI / iTop: Opening a service request
  • Any system that supports JSON webhooks

Reports and Exports​

Automatic Reports:

  • Daily report: summary of alarms, pumped volumes, and operating times by site
  • Monthly report: availability summary, meter readings, consumption, and incidents by site
  • Annual report: data for RPQS (water/sewer) or operator report

Manual Exports:

  • CSV export for a custom time range, by variable or group of variables
  • PDF export for incident reports
  • JSON export via API for integration with BI tools (Power BI, Grafana, Tableau)

Regulatory Compliance​

Drinking Water and Sanitation (DSP)​

Operators under a Public Service Delegation are subject to reporting requirements:

RPQS (Report on Price and Service Quality):

  • Performance indicators: compliance rate, network efficiency, outage rate, LCI (Linear Consumption Index)
  • Eziwan provides the raw data (pumped volumes, downtime) to calculate these indicators

SDAGE and prefectural decrees:

  • Certain structures are subject to enhanced monitoring, with data automatically transmitted to government agencies
  • Automatic export of Eziwan data can be used to feed these transmissions

Data Retention:

  • Minimum 5-year retention requirement for drinking water
  • Retention period configurable up to 10 years depending on the Eziwan subscription

Other Regulations​

NIS2 (Operators of Essential Services): For operators classified as OSE (water, energy), NIS2 mandates security measures for supervisory systems. The Eziwan architecture (outbound VPN, MFA, audit logs) meets these requirements.

ISO 50001 (Energy Management): For operators who are certified or in the process of obtaining certification, the energy consumption data collected via Eziwan can be used to feed into the Energy Management System.

Getting Started: From Scratch to a Supervised Park​

Step 1 — Assessment and Priorities​

Before deployment, conduct a site inventory:

InformationWhy It's Important
Type of device at each siteDetermines the data collection protocol
4G coverage (3 carriers)Choice of primary SIM card
Critical variables to monitorPrioritize configuration
Maintenance constraintsAvailable installation windows

Step 2 — Pilot Program at 5 Sites​

Start with 5 sites representative of the diversity of the system (different types of PLCs, different geographic areas). Verify:

  • Modbus data collection on each type of PLC
  • The quality of the 4G signal
  • Alerts and their relevance
  • The usability of the dashboard for operations teams

Step 3 — Mass Deployment​

Once the pilot has been validated, roll out the system in waves of 10 to 20 sites per week. The ZTP allows local maintenance technicians to perform installations in parallel.

Step 4 — Training and Adoption​

Training for driving teams (2 hours): navigating the dashboard, managing alerts, exporting data. Training for operations managers (1 hour): reports, account management, configuring alerts.

Operations FAQ​

Q: How do I access monitoring from the field (smartphone)? The Eziwan mobile app (iOS and Android) provides access to the same dashboard as the web version. Push notifications are available, and the map view lets technicians see nearby sites while they’re out on the road.

Q: Can there be multiple access levels within the organization? Yes. The administrator can create profiles with distinct permissions: operator (read-only, alarm acknowledgment), technician (+ VPN access, threshold modification), manager (+ administration), and executive (read-only, reports).

Q: What is the availability of the Eziwan cloud service? Eziwan's SLA guarantees 99.5% monthly availability. The infrastructure is hosted in European data centers (France and Germany) with geographic redundancy.

Q: What happens if the Internet goes down at headquarters? The gateways at the sites continue to collect data locally. Real-time monitoring from headquarters is unavailable during the outage, but the data is not lost. SMS alerts continue to function (they are sent directly via the gateway’s 4G network, without going through the Internet at headquarters).

👉 Get Started

Do you operate multiple sites and would like a demonstration tailored to your specific use case?

Contact the operations team →

Overview of the solution tailored to your types of sites (water, energy, industry) with features relevant to your organization.

Frequently Asked Questions​

Up to how many sites can the solution still be managed?​

The platform is designed for fleets ranging from 10 to 500 locations: groups, map views, consolidated alerts, and automated reports ensure operations can continue with a consistent staff level.

Can we keep our existing SCADA system?​

Yes: Eziwan collects data in parallel (Modbus read-only) or feeds data to the SCADA system via the site-to-site VPN tunnel. The cloud-based monitoring system complements the SCADA system without replacing it.

How are on-call duties managed?​

Alerts are routed based on on-call schedules and geographic areas: each team receives only events from its own sites, via email, text message, or webhook to your incident management tool.

What is the cost per site?​

A monthly subscription per site covers hardware, M2M SIM cards, the platform, and support. The pricing details and the ROI calculator allow you to build a business case based on your existing fleet.