WebTools OAClient is a modern browser-based HMI that replaces the native WinCC OA UI client. Deploy operator stations without thick-client installs — 1,000+ simultaneous web sessions on one WebTools server.
Three complementary products for WinCC OA projects: browser HMI, user-configurable reports, and high-performance Excel exchange.
Web HMI
Browser-based HMI that replaces the native WinCC OA UI client — operator stations without thick-client installs, up to 1,000+ concurrent sessions.
Reporting
User-configurable report module for live and historical SCADA data — templates, calculated fields, Excel export, and scheduled generation.
Data exchange
Direct high-performance XLSX import and export from WinCC OA — no OLE, no Microsoft Excel installation required.
Professional visualization of controlled database and process parameters for administrators, developers, and analysts. WebTools is a client–server application with a built-in engineering environment: create HMIs, bind live data, and publish to operators — typically without writing code.
Full-featured web replacement for the standard WinCC Open Architecture UI client. WSS connectivity to WinCC OA 3.x / 4.x servers.
Designed for control rooms and enterprise roll-outs: from pilot projects to 1,000+ concurrent browsers and up to 1M subscribed data points.
Operator interfaces with simultaneous multilingual support — aligned with global production and CMM scenarios.
Live monitoring, alarms, trends, and operator dialogs for continuous and batch processes.
Many operators on one infrastructure — web thin clients instead of hundreds of UI installations.
Combine WinCC OA tags with SQL and time-series sources in unified screens.
Migrate or extend existing WinCC OA projects with modern HTML5 graphics and responsive layouts.
| Criterion | Native WinCC OA UI | WebTools OAClient |
|---|---|---|
| Delivery | Installed thick client per workstation | Any modern browser (Chrome, Edge, Firefox, Safari, Yandex) |
| Concurrent users | Limited by classic client architecture | 1,000+ web clients per WebTools server (sized) |
| Engineering | WinCC OA GEDI / paradigms | Built-in widget & screen editors, menus, themes |
| Data sources | Primarily WinCC OA | WinCC OA + PostgreSQL, InfluxDB, MES/ERP, third-party SCADA |
| Updates | Client rollout on each PC | Central server update — operators refresh the page |
| Concurrent clients | Subscribed points (approx.) | Reference server |
|---|---|---|
| up to 10 | 5,000 | 4 GB RAM, 4 cores |
| up to 100 | 50,000 | 8 GB RAM, 4 cores |
| up to 500 | 300,000 | 12 GB RAM, 6 cores |
| up to 1,000 | 1,000,000 | 24 GB RAM, 8 cores |
WebTools follows a layered architecture: connectors and message broker on the backend, BFF (backend-for-frontend) for subscriptions, and a React-based presentation tier in the browser. WinCC Open Architecture is the primary SCADA path, but the same runtime can consume databases and external systems in parallel.
Logical architecture (based on product description; labels use WinCC OA, not legacy naming)
WinCC OA connector, PostgreSQL & InfluxDB connectors, message broker — acquisition, normalization, and exchange of live data.
Pre-subscriptions and handlers optimized for the web UI — efficient push of tag updates over WebSocket to many clients.
Rendered screens and widgets in the browser; engineering tools for layout, dynamics, and security zones.
Core functions from the WebTools OAClient specification — visual development, runtime, and administration in one product.
Composite controls with properties, events, aliases, layers; import/export to file or project database; undo/redo and simulation.
Process mimics and dashboards: standard symbols, dynamics, input dialogs, device templates and references.
Application shell — top/side/bottom panels, menus, navigation between screens and roles.
Model tags from WinCC OA or map external sources; subscription management for high point counts.
Users, groups, responsibility zones, permissions; switch user at runtime; LDAP and OpenID Connect.
Light/dark themes and runtime language switching for international operator teams.
Embed web content and custom HTML widgets inside supervised graphics.
Document and debug interaction flows between operators, screens, and data sources.
React, Redux, TypeScript — responsive HMI in the browser.
NestJS, TypeORM, Socket.IO, C++ connectors — real-time and persistence.
99% availability target, <1% error rate, 100+ req/s in reference tests.
Real WebTools OAClient UI from the user guide.
Full user guide, quick-start, and WinCC OA integration chapters are available online. Request a guided demo with your tag database, redundancy, or PostgreSQL hybrid scenario.
Get in touch about WebTools OAClient.
Website: webtools-ui.tech
Documentation: docs.webtools-ui.tech
Sales / demo:
info@webtools-ui.tech