WinCC vs WinCC Flexible Architecture, Limits, and Selection Guide

Platform Overview and Positioning

Siemens ships two distinct visualization product lines that are frequently confused at the project scoping stage: SIMATIC WinCC (the PC-based SCADA) and SIMATIC WinCC Flexible (the HMI configuration suite for Comfort/Operator panels, Multi Panels, and PC Runtime). Although the names differ by a single word, the engineering intent, runtime architecture, license model, and scalability differ by orders of magnitude. WinCC is engineered as a distributed SCADA that can supervise an entire plant; WinCC Flexible is engineered to configure a single panel image and, as an auxiliary option, drive a single PC Runtime instance.

The most common evaluation question is: "Can WinCC Flexible RT on a PC replace WinCC Professional for a line supervision application?" The short answer is no, except for the smallest, single-station, <4,000-tag projects. The detailed answer is below, including script execution, historical buffering, multi-monitor, redundancy, and licensing cost drivers.

System Architecture: SCADA vs HMI Runtime

WinCC (V7.x and TIA Portal WinCC Professional) is a true SCADA server. A project can be split into a Server, one or more Clients, and optional Web Clients. The Server owns the process image, the tag database, the alarm archive, the tag logging archive, and the user administration. Clients render pictures and read process values through the internal WinCC channel API. This model enables a single engineering team to update one server picture and push the change to every client without redeploying the HMI. Operator stations can be added without re-engineering the data source.

WinCC Flexible Runtime, by contrast, is a single-station product. Even when the project is launched on a PC, the runtime is bound to a single image tree with a single set of tags and a single alarm buffer. You cannot install multiple WinCC Flexible RT instances on the same PC to act as redundant servers; the licence terms and the architecture do not support it. The runtime is intended to give an engineering team a PC-based view identical to what the operator sees on an MP377 or TP177, not to host a plant SCADA.

For a multi-line supervision system, the architectural difference is the single most important constraint. If you intend to run more than one operator console, more than one server, or to scale tags beyond 4,096, the PC-based WinCC Flexible RT will block the design before commissioning.

Tag Capacity and Licensing Model

WinCC supports 262,144 power tags by default in V7.x; this is the value Siemens documents in the WinCC Information System and that the licensing tool (Automation License Manager) reports when the 16K, 64K, 128K, 256K, or 512K power tag licence is activated. Internal tags, archive tags, and online trends are licensed separately. The point at which most evaluations conclude is 4,096: this is the hard upper limit of WinCC Flexible for any combination of internal, external, and process tags.

Scripting: Parallelism, Languages, and Limits

The original question asked whether WinCC or WinCC Flexible Runtime allows more than one script to execute in parallel. The behaviour is fundamentally different and is the most common reason projects get stuck on WinCC Flexible.

WinCC Flexible script model

In WinCC Flexible, scripts are VBScript blocks bound to events (tag change, value change, scheduled, click). The runtime scheduler executes scripts sequentially in a single VBScript engine. A long-running script (a 15-second database query, a slow loop, a synchronous file write) blocks every other event-driven script until it returns. This is the behaviour observed on the MP377: "we needed to wait that one script was finish to make another one start." WinCC Flexible also enforces a 200-line per-script limit, which forces long procedures to be split into many small subroutines — and each subroutine call remains in the same single-threaded scheduler.

WinCC script model

WinCC supports C scripts (ANSI-C, compiled native) and VBScript actions. C actions run in a dedicated native thread and are not subject to the 200-line limit. Multiple C actions scheduled at the same cycle are dispatched to a thread pool. VBScript actions in WinCC share an engine similar to WinCC Flexible but with no 200-line cap and with broader COM access. For long-running or computationally heavy work, C actions are the recommended approach. You can also use background tasks, scheduler-triggered actions on different triggers, and independent cyclic actions at different cycle times — all of which run in parallel.

Workaround for WinCC Flexible sequential script bottleneck

If you are committed to WinCC Flexible RT and the sequential scheduler is the bottleneck, the only legal mitigation is to break long procedures into short steps and trigger the next step from a tag-change or a 250-ms cyclic trigger. This effectively turns a long script into a state machine. It works, but it is fragile and prevents any synchronous wait for external resources (database, OPC, file I/O).

Data Storage: SQL Server vs CSV / RDB

WinCC integrates Microsoft SQL Server (Express on small systems, Standard/Enterprise on larger ones). The alarm log, tag logging, and user administration all use SQL tables. This means:

• Queries against history are arbitrary SQL, including joins to MES / ERP tables.
• Archiving is transactional; an interrupted write does not corrupt the previous record.
• Backup is a native SQL Server backup (full, differential, log) — easy to script and to restore.
• External tools (Power BI, Grafana, custom .NET) can connect to the WinCC database directly with read-only credentials.

WinCC Flexible stores tag logging in proprietary RDB files and export data in CSV. There is no SQL interface. Querying a trend requires either opening the project in the engineering tool, exporting the RDB segment by segment, or writing a custom VBScript that reads and emits CSV. The 100-trend licence cap is the practical ceiling. For audit trails, regulatory reporting, or any long-term retention requirement, CSV/RDB is a substantial downgrade from SQL Server.

Graphics, Animation, and Screen Resolution

WinCC Professional and WinCC V7.x support dynamic SVG-like graphics: rotation, scaling, transparency, dynamic polygon points, path animation, and z-order with full transparency. The picture tree uses vector graphics; screen resolution is not constrained. WinCC Flexible graphics are bitmap-heavy, with limited animation channels (visibility, position, color, flashing). Rotation, scale, and path are not available.

Resolution is the most visible constraint of WinCC Flexible RT on a PC. The runtime is configured for a fixed target panel (for example, MP377 15" 1024x768) and will not re-flow to fit a 1920x1080 monitor. Multi-monitor is not supported. WinCC Professional supports up to 4 monitors per client out of the box.

Alarming, Logging, and Historical Trends

WinCC's alarm subsystem is class-based, supports operator actions, comment fields, acknowledgement chains, and a SQL-backed long-term archive. Alarm classes are configurable with custom colours, sounds, and routing to printers, e-mail, SMS, or OPC UA. A 512-trend online limit is the standard; trends can be configured to backfill from the SQL archive with no manual intervention.

WinCC Flexible's alarm subsystem is sufficient for a single panel: discrete and analog alarms, acknowledgement, and a 100-trend log. There is no native long-term archive, no SQL, and no built-in operator-action logging beyond the runtime's own log. For FDA 21 CFR Part 11 / GMP / GAMP environments, WinCC Flexible RT is not an acceptable audit trail source.

Connectivity, Networking, and Web Access

WinCC supports OPC DA 2.0, OPC HDA, OPC AE, and (in recent versions) OPC UA Server and Client. S7-PUT/GET, S7-Optimized, named connections, and Modbus TCP are all available. Web access is sold as WinCC WebNavigator (intranet) and WinCC WebUX (HTML5, any browser). Both are full operator clients.

WinCC Flexible supports S7 MPI/Profibus/Profinet and Modbus RTU/TCP, plus OPC DA client on PC Runtime. Web access is sold as /Sm@rtAccess and /Sm@rtService. The Sm@rtAccess web client is functional but limited: it does not support all picture elements, and the scripting model in the browser is restricted. For multi-user web access, WinCC's WebNavigator and WebUX are markedly more capable.

Redundancy, Multi-Monitor, and Multi-Station

Redundancy is the most decisive feature for plants that cannot tolerate a single point of failure. WinCC V7.x supports server-pair redundancy with automatic failover, shared archive storage, and a 30-second typical switch-over time. The licence "WinCC/Redundancy" is an optional add-on.

WinCC Flexible has no redundancy model. The PC Runtime is a single Windows process; if it crashes, the operator is blind until the PC is restarted and the project is reloaded. For unattended or semi-attended lines, this is unacceptable for most end customers.

Selection Decision Matrix

Use the matrix below to choose the right platform for a greenfield application. Score each row: 0 = not satisfied, 1 = partially satisfied, 2 = fully satisfied. If your total exceeds 8, choose WinCC. If your total is 4 or less, WinCC Flexible RT may be acceptable. Anything between is a forced upgrade.

Migration Path: WinCC Flexible to TIA Portal

Siemens has positioned TIA Portal as the replacement for WinCC Flexible. The successor product family is SIMATIC WinCC (TIA Portal) in three editions: Comfort (for Comfort Panels, the direct replacement of WinCC Flexible target MP377 / TP177), Advanced (for PC-based RT with 2,048 tags), and Professional (full SCADA with 262K+ tags, multi-station, redundancy). If your current project is bound to WinCC Flexible RT on a PC, the migration target is TIA WinCC Advanced (small projects) or TIA WinCC Professional (everything that needs SCADA-grade features).

The conversion tool "WinCC Flexible to TIA Portal" handles the bulk of the picture tree, the tag list, the alarm classes, and the recipe structure, but several constructs do not round-trip cleanly:

• VBScripts over 200 lines must be split manually before the converter accepts them.
• Custom OLE / COM calls in WinCC Flexible scripts are not converted; they must be rewritten against the new COM security model.
• RDB archives are exported to CSV, then re-imported to the SQL archive in TIA WinCC.

Plan a parallel-running phase of at least two weeks during the migration. Do not attempt a hot cut-over from a regulated production line.

Verification Checklist Before You Commit

1. Tag budget. Count the external process tags, internal tags, and pointer tags. Add 25% growth. If the result exceeds 4,096, choose WinCC.
2. Script inventory. List every event-driven script. For each one, estimate the worst-case duration. If any script is > 1 second and is triggered by a fast-cyclic tag, WinCC Flexible RT will starve other scripts.
3. Operator station count. One physical console = either platform. Two or more = WinCC.
4. Archive retention. If the customer requires > 30 days of trend and alarm history with on-line query, you need SQL. WinCC only.
5. Regulatory framing. FDA 21 CFR Part 11, GMP, GAMP 5, IEC 62443 — all push you to WinCC. WinCC Flexible RT is not an acceptable audit source.
6. Failure tolerance. If the line stops when the HMI PC crashes, you need WinCC redundancy or a second PC. WinCC Flexible RT has neither.
7. Resolution target. If the operator desk has a 16:9 1080p / 1440p monitor, WinCC Flexible RT will letterbox. WinCC scales to any resolution.

Frequently Asked Questions