Automation Integrators — Add remote connectivity to all your projects

Remote connectivity has become a standard requirement for your customers. Machine monitoring from headquarters, remote maintenance access, and SMS alerts for malfunctions—these are no longer optional; they are basic expectations.

But integrating this connectivity into your automation projects raises questions you may not necessarily have the answers to: What network equipment should you choose? How should you manage the SIM cards? How can you secure access without opening ports on the customer’s network? How should you bill for and maintain this component over the long term?

Eziwan was designed to answer these questions without requiring you to become an expert in network security.

The Problem with Integrators That Lack a Built-in Network Solution​

What's Holding Projects Back Today​

Without a standardized solution, every remote connectivity project is a unique undertaking. And every project faces the same challenges:

Negotiations with the client’s IT department: Before VPN access can be granted, approval must be obtained from the client’s IT team. This involves a presentation meeting, a security audit, drafting an access policy, and approval by the CISO. In medium-sized companies, this process takes 2 to 6 weeks. In large industrial groups, it can take several months.

SIM Management: Which carrier? Which plan? What data allowance? Who handles renewals? If you purchase two SIM cards from two different carriers (for redundancy), you’ll have to manage two contracts, two bills, and two points of contact in case of a problem—multiplied by the number of projects.

VPN Configuration: A well-designed industrial VPN requires a PKI (public key infrastructure), encryption keys for each site, routing rules, and firewall configurations. These are the responsibilities of a network/security specialist, not an automation engineer.

Long-term support: When a customer calls because the remote connection is no longer working, who handles the issue? If you’re responsible, you need in-house networking expertise. If you refer the customer to a network service provider, you lose the customer relationship and the profit margin.

Liability in the Event of an Incident: If a security incident occurs through the remote access you have set up, you may be held liable. Insecure access (an open port, TeamViewer without an access policy) puts your client and your reputation at risk.

The Impact on Your Business​

These obstacles lead to detrimental behaviors: projects that are rejected or underestimated because the connectivity aspect is too uncertain, makeshift solutions (TeamViewer, RDP access) that work until the first incident occurs, or a reliance on network subcontractors over whom you have no oversight.

The Solution: A Ready-to-Use Gateway with Built-In Connectivity​

How Eziwan Transforms Your Value Proposition​

Eziwan lets you offer remote connectivity as an additional line item on your quote, without having to manage any infrastructure. The Eziwan gateway is a component that you specify, purchase, and install—just like a variable-frequency drive or an HMI.

What Eziwan provides with each gateway:

  • Dual SIM 4G LTE Connectivity: Multi-carrier SIM (Orange, SFR, Bouygues) included with the subscription — no need to negotiate with a carrier, no SIM management
  • Secure Remote Access: Outbound OpenVPN tunnel only — no ports to open on the customer’s network, no firewall changes
  • Zero-Touch Provisioning: The gateway configures itself automatically in less than 5 minutes after connection — no network intervention required
  • Cloud dashboard: multi-site monitoring, SMS/email alerts, history — available immediately
  • CE/FCC/RoHS certification: complete documentation for your compliance records

How This Will Change Your Project Workflow​

Before Eziwan:

  1. Design → 2. Implementation → 3. Deployment → 4. IT negotiations with the client (2 to 6 weeks) → 5. VPN configuration → 6. Remote connection

With Eziwan:

  1. Design → 2. Implementation → 3. Commissioning + remote connection (same day)

The time to deployment is reduced from several weeks to just a few minutes. Signing the acceptance form can include confirming remote access—the customer sees the data on their phone before you leave the site.

Typical Architecture in an Integration Project​

Standard Wiring Diagram​

The Eziwan gateway connects in parallel to the existing Ethernet or RS-485 bus. It does not interfere with communication between the PLC and the HMI. It is transparent to the PLC program—no code changes are required on most PLCs.

Configuring Variables During Development​

During setup (or afterward, from the desktop):

  1. Create the site in the cloud dashboard (10 seconds)
  2. Scan the QR code on the gateway → automatic pairing (30 seconds)
  3. Add the Modbus variables: PLC IP address, register addresses, conversion factors (15 to 30 minutes depending on the number of variables)
  4. Configure alerts: SMS/email thresholds for critical variables (5 minutes)
  5. Test: Check real-time values on the dashboard from your smartphone

Total setup time: 30 to 60 minutes per standard project.

Compatibility with Commercially Available PLCs​

Controllers Supported by Modbus TCP​

ManufacturerModelFirmware VersionNotes
SiemensS7-1200 (CPU 1211C+)≥ V4.0MB_SERVER in TIA Portal
SiemensS7-1500 (all CPUs)≥ V2.0MB_SERVER or OPC-UA
SiemensLOGO! 8.3≥ 1.80Enable in LOGO! Soft Comfort
SchneiderM221, M241AllEcoStruxure Machine Expert
SchneiderM340 (BMX P34)≥ 2.30EcoStruxure Control Expert
SchneiderM251, M262AllSoMachine / EcoStruxure
WagoPFC100, PFC200Alle!Cockpit, native Modbus TCP
Allen-BradleyMicroLogix 1100AllVia Modbus TCP (module)
Allen-BradleyCompactLogixAllVia 1769-ASCII module
BeckhoffCX SeriesAllTwinCAT Modbus TCP
B&RX20 SeriesAllAutomation Studio

Field Instruments Using Modbus RTU (RS-485)​

The Eziwan gateway has an RS-485 port that allows data to be collected directly from field instruments without going through the PLC:

  • Energy meters (Carlo Gavazzi, Socomec, Schneider PM series)
  • Variable frequency drives (Danfoss VLT, Schneider ATV, Siemens SINAMICS)
  • Gas analyzers, temperature sensors, flow meters
  • Any instrument with an RS-485 Modbus RTU interface

Business Model and Billing​

How to Include Eziwan in Your Quote​

Eziwan connectivity is available in two models:

All-inclusive model: You purchase the gateway, sign up for the Eziwan subscription, and include both in your selling price along with your markup. The customer pays a monthly or annual monitoring fee as part of your maintenance contract. It’s simple, but you’re responsible for managing the subscription.

Pass-through model: You recommend Eziwan to your client, who signs up for the subscription directly. You install the gateway and configure the system as part of your service. This model offers greater cost transparency but generates less recurring revenue for you.

Calculating ROI for Your Client​

Demonstrating the ROI of remote connectivity speeds up the purchasing decision. Key metrics to quantify:

Cost SavingsEstimated Calculation
Avoided service calls2 service calls/year × €600 = €1,200/year
Reduced downtimeRemote diagnostics → -1 hour of lost production per incident
Preventive maintenanceDetection of performance drift before failure → prevents 1 major failure every 2 years
Automatic reports2 hours/month saved on reporting × 12 = 24 hours/year

For a machine costing €50,000, an ROI of €1,500 to €3,000 per year on connectivity translates to a payback period of 1 to 2 years.

Integrator Partner Program​

What the program includes​

The Eziwan Partner Program is designed for automation integrators who provide connectivity solutions to their customers:

Preferential Pricing:

  • Discounts on gateways based on annual order volume
  • Partner subscriptions at preferential rates (passed on to customers or used for resale margin)
  • No minimum purchase requirement—single-unit orders accepted

Partner Tools:

  • Partner Portal: Centralized management of all your customers, subaccounts, and billing
  • Configuration Templates: Preconfigured variable templates by PLC type and industry (water, energy, machine tools, food processing)
  • Co-branded documentation: technical data sheets and sales pitches featuring your logo

Training and Support:

  • Onboarding Session (2 hours online): first project from start to finish
  • Comprehensive technical documentation: guides for each PLC, troubleshooting guides
  • Priority support channel: Slack or dedicated email for ongoing projects (response within < 4 business hours)

Marketing and Business Development:

  • Listing on the Eziwan Partners page with a link to your website
  • Joint case studies to showcase your achievements
  • Joint presentations at webinars or trade shows, if desired

Technical FAQ for Integrators​

Q: Does the gateway change the behavior of the PLC network? No. The gateway connects to the network as an observer. It reads Modbus registers without sending any commands to the PLC (unless you explicitly configure it to write to registers). The PLC cycle is not affected.

Q: What happens if the 4G connection is lost? The gateway buffers the data locally during the outage (for up to 48 hours, depending on available memory) and resends it with its original timestamps as soon as service is restored. No data is lost in the event of a short- to medium-term outage.

Q: How do I manage a PLC with a single IP address across multiple VLANs? The gateway must be on the same VLAN as the PLC for Modbus communication. For remote VPN access (access from TIA Portal/Unity Pro), the VPN tunnel connects to the gateway’s VLAN—the remote access PC “sees” the PLC at its local address.

Q: Is remote access available even if I'm the only one with the credentials? Yes. VPN access credentials are separate from configuration credentials. A technician can have VPN access to a site without having administrative rights to the Eziwan account.

Q: Can Eziwan collect data via OPC-UA in addition to Modbus? Yes, OPC-UA is supported in server mode on compatible PLCs (S7-1500 firmware ≥ V2.0, CODESYS 3.x, B&R). Contact technical support for configuration assistance.

Q: What is the typical data collection latency? Under normal conditions (good 4G signal, cloud server operating normally), the data collection latency (between the value on the PLC and its display on the dashboard) is 1 to 3 seconds for a 5-second polling interval. For alerts, the added latency is 1 to 5 seconds.

👉 Get Started

Do you have an ongoing project and want to include Eziwan connectivity?

Request a partner quote →

Our team will respond within 24 business hours with a pricing proposal and an invitation to the onboarding session.

Frequently Asked Questions​

Do you need network expertise to integrate Eziwan into a project?​

No: The gateway is configured via the cloud (ZTP), the VPN is generated automatically, and Modbus/OPC-UA data collection is configured in the console. The integrator can focus on automation, not on the network.

How should connectivity be billed to the end customer?​

Two common models: reselling the subscription at a markup (the integrator remains the sole point of contact), or transferring the contract to the end customer after activation. The multi-client portal isolates each customer base.

Can the gateways be prepared in the workshop before installation?​

Yes, and this is recommended: pre-registration by serial number, configuration profile assigned in advance, bench testing of the data collection system—on-site installation is limited to assembly and connection.

What kind of support is available during the pre-sale phase?​

The Eziwan team provides a reference architecture, PLC compatibility sheets, and a development gateway to help you design the solution for your bid proposal.