Remote PLC Commissioning: Reach Any Site Without a Plane Ticket

Your automation integrator just booked a $4,500 flight to commission a PLC at a manufacturing site in Vietnam. The project budget allocated $2,000 for travel. Someone's eating a loss — either the integrator absorbs the cost, or the customer pays a premium, or the commissioning gets delayed.

There's a better way. Remote PLC commissioning via WireGuard connectivity lets engineers reach any site from their laptop, running TIA Portal, GX Works, or SoMachine against the PLC at its local IP — as if they were plugged into the switch on-site. No screen-share lag, no travel costs, and global reach in minutes.

This guide explains how remote PLC commissioning works, the FAT/SAT workflows it enables, and why network-level access beats screen-sharing for engineering work.

The Cost of On-Site Commissioning

PLC commissioning travel is expensive, and the costs compound:

Direct Costs

• Flights: $2,000–$8,000 for international economy, $5,000–$20,000 for business class (often required for long-haul technical work)
• Accommodation: $150–$400/night for hotels, 5–14 nights per trip
• Per diem: $50–$100/day for meals and incidentals
• Local transport: Rental cars, taxis, fuel — $500–$2,000 per trip

Opportunity Costs

• Engineer time: Senior PLC engineers earn $100–$200/hour. A 10-day trip is $8,000–$16,000 in billed opportunity cost
• Project delays: Visa processing, flight availability, and quarantine (in some regions) can delay projects by weeks
• Risk concentration: If the on-site engineer falls ill, encounters visa issues, or the trip is cancelled, the project stalls

Carbon Costs

• CO2 emissions: A round-trip flight from New York to Vietnam emits ~2.5 tons of CO2. For frequent commissioning trips, this adds up quickly
• ESG impact: Companies with net-zero commitments are increasingly scrutinizing business travel, especially for tasks that can be done remotely

How Remote PLC Commissioning Works

Voltrus Remote provides network-level access to PLC subnets. The engineer's laptop receives routes to the PLC network, and TIA Portal/GX Works/SoMachine connects to the PLC at its local IP — no RDP layer, no screen-share lag, just native connectivity.

Architecture

Engineer's Laptop (Germany)
├─ TIA Portal V16
├─ GX Works 3
└─ Voltrus Remote Client
   │
   │ WireGuard tunnel (outbound to control plane)
   ▼
Headscale Control Plane (self-hosted)
   │
   │ WireGuard tunnel (outbound from gateway)
   ▼
OT Gateway (Vietnam site)
├─ eth0: 192.168.1.10 (PLC network)
└─ wlan0: internet breakout
   │
   ▼
Siemens S7-1500 PLC
└─ 192.168.1.20 (local IP)
   └─ TIA Portal reaches this directly

Key properties:

1. Outbound-only: Both the engineer's laptop and the OT gateway initiate outbound connections to the Headscale control plane. No firewall ports need to be opened.
2. Native tooling: TIA Portal sees the PLC at 192.168.1.20, same as on-site. No special configuration, no "remote mode" workaround.
3. Full protocol support: S7-1200/1500, Rockwell Ethernet/IP, Modbus TCP, Mitsubishi MELSEC, Omron NJ/NX, Schneider Modicon — all work because the engineer's laptop has Layer 3 reachability.

FAT/SAT Workflows Remotely

Remote commissioning supports both Factory Acceptance Testing (FAT) and Site Acceptance Testing (SAT) workflows:

Factory Acceptance Testing (FAT) — Remote Option

Traditionally, FAT requires the customer to travel to the integrator's facility. With Voltrus Remote, the integrator deploys the PLC on a test network, advertises the subnet, and the customer connects remotely:

Site Acceptance Testing (SAT) — Remote Option

SAT traditionally requires integrator travel to the customer's site. With Voltrus Remote, the integrator connects remotely to the site's PLC network:

Why Network-Level Access Beats Screen Sharing

The old approach to remote commissioning was screen sharing: TeamViewer into the HMI, or share the screen with on-site personnel via Zoom/Teams. This works for viewing but fails for doing:

Aspect	Screen Sharing (TeamViewer/Zoom)	Network-Level Access (Voltrus Remote)
TIA Portal Performance	Laggy, feels like remote desktop (cursor delay, UI sluggishness)	Native, feels like local (no RDP layer)
PLC Upload Speed	Limited by RDP compression and screen-share bandwidth	Limited only by WireGuard throughput (near-native)
Multi-PLC Projects	Painful: switch RDP sessions, reconnect to each PLC	Seamless: all PLCs reachable at local IPs
Diagnostic Tools	Limited: can run tools on remote PC but latency is high	Full: run Wireshark, PacDrive, Modbus poll locally
On-Site Dependency	High: requires someone at the PC to accept connections, reboot, etc.	Low: gateway is autonomous, engineer can reboot PLC remotely
Security	Risk: third-party SaaS, inbound exposure, no ACL enforcement	Secure: outbound-only, scoped ACLs, self-hosted control plane

Real-World Performance: What Engineers Report

Engineering teams using Voltrus Remote for commissioning report:

TIA Portal Project Upload

• On-site: 50 MB project in 4 seconds
• Voltrus Remote (Germany → Vietnam, 180ms RTT): 6 seconds
• Screen share (same route): 45–120 seconds (highly variable)

GX Works Online Monitoring

• On-site: Real-time monitoring (no perceptible lag)
• Voltrus Remote (Japan → Indonesia, 90ms RTT): Real-time (imperceptible lag)
• Screen share: 2–5 second lag, hard to catch transient events

Modbus TCP Debugging

• On-site: Wireshark captures full packet stream, analysis in real-time
• Voltrus Remote: Wireshark runs locally, captures WireGuard-encapsulated traffic, decrypts for analysis
• Screen share: Can't run Wireshark remotely effectively, limited to on-site personnel running captures

Deployment for Remote Commissioning

Step 1: Deploy OT Gateway at Site

# On a Linux device at the commissioning site
curl -fsSL https://get.voltrus.id/gateway | sudo bash

# Register with your control plane
voltrus-remote register --control-plane=https://headscale.your-domain.com

# Advertise PLC subnets
voltrus-remote advertise 192.168.1.0/24

Step 2: Create Commissioning ACL

# In Headscale ACL configuration
acls:
  - action: accept
    users: ["commissioning-engineer@example.com"]
    routes: ["192.168.1.0/24"]
    # Optional: time-box for commissioning window
    start: "2026-07-13T00:00:00Z"
    end: "2026-07-20T23:59:59Z"

Step 3: Engineer Connects

# On engineer's laptop
voltrus-remote login --control-plane=https://headscale.your-domain.com

# Ping PLC to verify connectivity
ping 192.168.1.20

# Open TIA Portal, add PLC at 192.168.1.20
# Works identically to on-site access

Step 4: Run Commissioning Workflows

1. Load project to PLC via TIA Portal (full upload speed)
2. Run online monitoring and debugging (real-time)
3. Test HMI/SCADA connectivity
4. Verify safety interlocks (with local operator coordination)
5. Document test results, sign off remotely

Multi-Site Commissioning: One Trip, Many Sites

Voltrus Remote enables parallel commissioning across multiple sites. Instead of traveling to 5 sites sequentially (5 trips, 5 weeks), one engineer can commission all 5 sites in 1 week:

Monday: Site A (Germany) — 2 hours
Tuesday: Site B (Vietnam) — 3 hours
Wednesday: Site C (Brazil) — 4 hours
Thursday: Site D (India) — 3 hours
Friday: Site E (Indonesia) — 2 hours

Total: 5 sites, 1 week, $0 travel

This is impossible with on-site commissioning. With Voltrus Remote, it's routine.

When On-Site Presence Is Still Required

Remote commissioning doesn't eliminate all on-site work. These tasks still require physical presence:

• Hardware installation: Mounting PLCs, wiring I/O, installing actuators
• Physical safety verification: Testing emergency stops, light curtains, safety relays
• Calibration: Sensor calibration, analog loop tuning
• Regulatory inspections:某些 jurisdictions require physical witnessing for certifications

But for PLC programming, logic debugging, HMI configuration, and software verification — which constitute 70–80% of commissioning effort — remote access is sufficient.

The Bottom Line

Remote PLC commissioning isn't a niche workaround — it's a fundamentally better way to do FAT/SAT for 70–80% of commissioning work. By providing network-level access to PLC subnets, Voltrus Remote lets engineers run TIA Portal, GX Works, and SoMachine at native speed from anywhere in the world.

The economics are compelling:

• Cost savings: $5,000–$20,000 per international trip saved
• Time savings: No travel days, no visa delays, commissioning starts immediately
• Quality improvement: Native tool performance beats screen-share lag
• Parallel execution: One engineer can commission multiple sites in parallel

For automation integrators, this means higher margins and faster delivery. For customers, it means lower project costs and faster time-to-production. For engineers, it means less time in airports and more time doing productive work.

The shift from "fly to site, plug in laptop" to "remote VPN to site, run TIA Portal" is one of the most significant operational improvements in industrial automation. With Voltrus Remote, it's available today for Siemens, Rockwell, Mitsubishi, Omron, and Schneider PLCs.

Keep reading

Comparison Siemens S7-1200 vs S7-1500: Which PLC for Your Project August 11, 2026 Comparison TeamViewer Alternative for PLC Remote Access: Why OT Teams Are Switching July 13, 2026 Guide Secure Remote Access to PLC Networks: A Practical Guide for Integrators July 13, 2026