Every device with a browser is a potential operator station. Here is how web HMIs work, where they beat traditional panels, and how to put live Modbus data on a tablet, an Android panel, or a wall display — with no PC at each station.
A web-based HMI inverts the traditional model. Instead of installing HMI runtime software on every operator station (or buying a proprietary panel per machine), one SCADA server does the heavy lifting: it polls your PLCs and devices over Modbus TCP/RTU, OPC UA or MQTT, evaluates alarms, records history — and serves the operator screens as a normal web application.
Operator stations become trivially cheap and interchangeable: any device that runs a modern browser renders the same screens. Live values arrive over a WebSocket connection, so a tank level changes on screen tens of milliseconds after the server polls it — no page refreshes, no plugins, no Java applets (this is 2026, not 2006).
Crucially, the browser never speaks Modbus. Device communication, alarm logic and history live on the server; the display layer is stateless. Drop a tablet in acid, hand the operator a new one, log in, and everything is exactly where it was.
| Aspect | Web-based HMI | Vendor HMI panel | PC HMI runtime |
|---|---|---|---|
| Hardware per station | Anything with a browser (from ~$100) | Proprietary panel ($500–$5,000+) | Windows PC + license |
| Screen updates deploy… | Once, on the server | Download to each panel | Install on each PC |
| Multi-station cost | Usually flat / per-server | Per panel | Per seat |
| Remote access | Native — same URL anywhere | Usually add-on (e.g. vendor web client) | VPN + remote desktop |
| Local machine control | Via server | Excellent (direct to PLC) | Good |
| Survives device failure | Replace the device, nothing to restore | Restore panel project | Reinstall + restore |
The honest trade-off: a vendor panel hard-wired to one machine is still excellent at being exactly that. Where web HMIs win decisively is everything plant-wide — multiple stations, mixed devices, remote visibility, and the economics of adding "one more screen".
Panel-format Android devices (10–15", IP65 front) cost a fraction of vendor HMI panels. Set the browser to kiosk mode pointing at your HMI URL — done.
A consumer tablet in a plant-rated enclosure makes a capable operator station for light industrial environments — and doubles as a walk-around maintenance display.
Any smart TV or TV-stick with a browser can show a read-only overview screen: line status, alarm counts, KPIs. Great for supervisors and meeting rooms.
Many current vendor panels ship an HTML5 browser. They can keep their local control project and display your plant-wide web screens.
Alarm acknowledgement and spot checks from a phone are realistic on a responsive web HMI. Full operation still deserves a bigger screen.
Same URL, full designer access. Build and edit screens from anywhere on the network — changes appear on every station instantly.
Supervisory control (setpoints, start/stop commands, alarm acknowledgement) is standard on web HMIs with role-based access. Safety functions and hard interlocks belong in the PLC/safety system no matter what HMI technology you use.
The screen should immediately show a disconnected state and stop accepting writes. Prefer wired Ethernet for fixed stations; use Wi-Fi for walk-around displays.
No — a web HMI runs fine on an isolated plant LAN. Internet only matters if you also want remote access, in which case put it behind a VPN or use a cloud-hosted SCADA with proper authentication.
Yes: run a Modbus simulator as a fake device, connect the SCADA to it, and build screens against live changing values. See building an HMI without panel software.
SCADA Cloud serves your HMI screens to any browser — tablets, panels, wall displays — with live WebSocket updates from Modbus TCP/RTU, OPC UA and MQTT devices. Free for 30 days, no credit card.