No native UI rollout
Operators open HTTPS in Chrome, Edge, Firefox, Safari, or Yandex Browser — no GEDI/UI package on every workstation.
WinCC OA web client for modern control rooms
WebTools OAClient is a browser HMI for WinCC Open Architecture. Deliver operator stations without thick-client installs, keep WinCC OA as the SCADA core, and scale to 1,000+ concurrent web users on one WebTools server.
Why teams choose a WinCC OA web client
Built for concurrency
Reference sizing covers pilots to plant-wide roll-outs: up to 1,000 browsers and ~1M subscribed points.
More than SCADA tags
Combine WinCC OA with PostgreSQL, InfluxDB, MES/ERP, and third-party SCADA in one HMI.
Native UI vs WebTools OAClient
| Need | Native WinCC OA UI | WebTools web client |
|---|---|---|
| Operator access | Installed client per PC | Any modern browser |
| Fleet updates | Client rollout | Central server — refresh the page |
| Concurrent users | Classic client limits | 1,000+ sessions (sized) |
| Engineering | WinCC OA paradigms | Widget & screen editors in the product |
FAQ — WinCC OA web client
What is a WinCC OA web client?
A browser-based HMI connected to WinCC Open Architecture so operators and engineers work without installing the native UI client on each PC.
Can WebTools replace the native WinCC OA UI client?
Yes. OAClient covers visualization, alarms, trends, and dialogs while WinCC OA stays the SCADA server of record.
How many concurrent browser users can one server handle?
A sized WebTools server supports 1,000+ simultaneous sessions and about one million subscribed data points.
Which data sources work besides WinCC OA?
PostgreSQL, InfluxDB, MES/ERP, third-party SCADA connectors, plus LDAP/OIDC for corporate login.
Next steps
Explore the full product overview or jump into the English user guide (install, quick start, editors, connections).