IMDTouchKnowledge BaseShop main store

Comparison

WinCC vs WinCC Flexible for small PC SCADA applications

HMI and touchscreens Published 6 min read

Short answer

WinCC Flexible can build a small SCADA application that runs on a PC, but only the Advanced edition does it — Standard stops at operator panels. Treat two decisions separately: the Advanced engineering license buys the PC runtime capability, and each PC that runs the finished application still needs its own runtime license. Beyond single-station scope, the WinCC family is the SCADA tool.

On this page
  1. What the two names actually are
  2. Edition by edition: what the editor can target
  3. Why the PC runtime sits in Advanced
  4. One runtime license per PC that runs the application
  5. Licensing three operator PCs plus one engineering station
  6. When Flexible Advanced stops being the answer
  7. The TIA path forward
  8. The decision, case by case
  9. Questions asked

WinCC Flexible can build a small SCADA application that runs on a PC, but only the Advanced edition does it — Standard stops at operator panels — and every PC that runs the finished application needs its own runtime license. The two names are not two versions of one editor: WinCC Flexible is panel engineering software whose Advanced tier extends to small PC runtime, while WinCC is the SCADA product family, native to the PC and built to scale. Split your decision accordingly: choose the edition for what the editor must target, then license each machine that runs the result. One PC per machine is Flexible Advanced territory; server and client architectures belong to the WinCC family.

What the two names actually are #

WinCC Flexible is engineering software for operator panels from the classic, pre-TIA generation, paired with the classic STEP 7 world. It comes in four editions — Micro, Compact, Standard and Advanced — and the edition you buy sets which device classes the editor can configure. WinCC, by contrast, is the SCADA product family itself: in its classic V7.x form the runtime is PC-native, and the family scales into server and client architectures. The same WinCC name continues inside TIA Portal as a set of editions that step up to Professional, the tier that adds PC runtime there.

The two are separate product lines, not two editions of one editor, and they do not trade projects between them. This overlapping-name pattern repeats across the whole automation portfolio — PLCs, drives, HMI software — so it helps to keep a map of Simatic PLC product families and their documentation at hand when the names start to blur.

Edition by edition: what the editor can target #

The editions are ordered tiers, and each higher tier configures more device classes. Laid out against the question you are actually asking — can the finished application run on a PC — the split looks like this:

Tool and edition Editor targets Runtime platform Small PC SCADA?
WinCC Flexible Micro, Compact operator panel tiers below Standard the panel No
WinCC Flexible Standard operator panels the panel No
WinCC Flexible Advanced operator panels plus a PC target a PC Yes — small applications
WinCC classic (V7.x) PC SCADA projects a PC, scaling to client/server Yes — the SCADA family itself
WinCC editions in TIA Portal panels, stepping up to Professional panels; a PC at Professional Yes, via Professional

Everything below Advanced in the Flexible line stops at panel runtime. The PC target exists only in Advanced, and that is the documented boundary behind the short answer.

Why the PC runtime sits in Advanced #

The edition split is not a checkbox inside a project; it is what the editor is licensed and built to target. Standard configures operator panels. Advanced adds the PC target that a small SCADA application needs, so the decision has to be made before the project starts: you cannot build the PC application in Standard and switch to it later. Plan on the Advanced engineering license from day one.

The second half of the decision is what the Advanced license does not buy: any right to run the finished application. Engineering entitlement and runtime entitlement are separate lines, and the runtime is licensed per machine.

One runtime license per PC that runs the application #

The rule is short: every PC that must run the application carries its own runtime license. One license does not follow the project, and it does not follow the disk image — it follows the machine. A runtime placed onto a second PC without its own entitlement is a licensing fault, and what a WinCC flexible runtime shows on a copied target PC is exactly that fault surfacing at the machine.

Count machines, not users: three operators working one shift on one PC still mean one runtime machine. Order the runtime licenses per machine count through the vendor or its distributors, and keep the count next to the panel list so it survives the next project revision.

Licensing three operator PCs plus one engineering station #

Take the deployment this question usually comes from: one line, three operator PCs mounted at the machine, each running the WinCC Flexible Advanced application in runtime, plus one engineering station used to build and download projects. The PC counts are this example's own inputs, not published limits; the licensing rule is the documented one.

Inputs

  • 3 operator PCs that run the application in runtime (example deployment)
  • 1 engineering station that runs the Advanced editor only (example deployment)
  • Rule: one runtime license per PC that must run the application (vendor licensing)

Rule in words. Count every PC that executes the application and assign it exactly one runtime license. A PC that only edits projects assigns zero.

Arithmetic.

  • Operator PCs: 3 × 1 runtime license = 3 runtime licenses
  • Engineering station: 1 × 0 = 0
  • Total: 3 + 0 = 3 runtime licenses, plus the Advanced engineering license for the station

Result and decision. The deployment needs three runtime licenses and one Advanced engineering license. The test behind the count is binary: does this machine execute the application? The engineering station passes that test only if it stays on the floor running the application between edits — then it counts too, and the total moves to four. The same test adds one license for every PC added later, so a fourth operator PC next year takes the deployment to four runtime licenses.

Each of those operator PCs is a touchscreen computer mounted at the machine, and the runtime belongs on industrial panel PCs rather than an office desktop left open to dust and shift work.

When Flexible Advanced stops being the answer #

"Small" is the scope word in the capability statement itself, and the architecture behind it is a single runtime PC per application. That draws the boundary somewhere you can test without any tag counts. If the system needs one server machine feeding several operator clients, redundant runtime pairs, or a plant-wide tag database, the WinCC family is the tool — client/server SCADA is what that product line exists for. If the system is one PC visualizing one machine, Flexible Advanced covers it, and the license math stays at one engineering seat plus one runtime license per machine.

The same runtime-selection question comes up on other platforms — how to choose a PC-based HMI runtime for a Modbus TCP PLC works through it on a different stack — and this edition question is one input inside the larger task of choosing HMI software for a new control system.

The TIA path forward #

WinCC Flexible belongs to the classic STEP 7 generation, and panel engineering has moved into the WinCC editions inside TIA Portal, which step up to Professional for PC runtime. A Flexible project does not drift there on its own; it moves as a migration project of its own, so install the target TIA Portal software first and plan the migration as a deliberate step rather than an in-place upgrade.

So the standing decision is this: maintain the classic line with Flexible Advanced and a runtime license per PC, or move the system to TIA and re-host the application there. A new system started today means the TIA editions; an existing classic plant means Flexible Advanced remains the correct answer for its small PC SCADA applications.

The decision, case by case #

  • Small PC SCADA application in a classic STEP 7 environment → WinCC Flexible Advanced, with one runtime license for every PC that runs it.
  • Panel-only system → Standard is enough if its supported panels cover yours; Advanced buys a PC target you will not use.
  • Server and client machines, redundancy, plant-wide tags → the WinCC family, not Flexible.
  • New build today → the TIA Portal editions, with PC runtime at the Professional tier.

Questions asked

Does the PC running the WinCC Flexible engineering software also need a runtime license?

If that PC only edits projects and downloads them to the line, no — the runtime license attaches to machines that execute the application. The moment the engineering PC stays on the floor running the application between edits, it has become a runtime machine and needs its own runtime license, counted the same as any operator station.

Can a WinCC Flexible project be opened in WinCC?

No. The two families keep separate project formats: a WinCC Flexible project does not open in classic WinCC, and a classic WinCC project does not open in WinCC Flexible. Moving a Flexible project forward means migrating it into the TIA Portal WinCC environment, not converting it into a WinCC V7 project — plan the migration as its own step with the target software installed first.

What happened to WinCC Flexible — is it still the tool for a new system?

For panels it has been superseded by the WinCC editions inside TIA Portal — Basic, Comfort, Advanced and Professional — and for scalable PC SCADA the current TIA platform is WinCC Unified. WinCC Flexible still matters for maintaining classic STEP 7 V5.x projects and the older operator panel families it supported. For a new system started today, build in TIA Portal.

Which STEP 7 generation pairs with WinCC Flexible?

The classic generation. WinCC Flexible integrates with STEP 7 V5.x — V5.5 is the version engineers commonly pair with WinCC Flexible Advanced in the classic world. The TIA Portal replaced that pairing: its WinCC editions live inside TIA alongside the newer STEP 7, and projects started there do not use WinCC Flexible at all.

Does one runtime license cover a standby PC kept as a cold spare?

If the spare PC must be able to run the application — swapped in when an operator PC fails — it needs its own runtime license. The entitlement is per PC that runs the application, not per project or per site, so a cold spare is licensed like any operator station even if it never displays a screen.

Keep reading

  • How-to

    Editing WinCC Flexible Recipes From a PC Without the Engineering Tool

    Recipe values and new data records can be edited from any PC when the WinCC flexible runtime exports a CSV to MMC or USB and imports it back; the .dat, .rdf and .vdf files inside the panel have no supported external editor. Adding or removing recipe parameters always needs the engineering project.

    HMI and touchscreens

  • Selection guide

    How to Choose HMI Software for a New Control System

    Count operator stations, controllers and connections first, keep sequencing and permissives in the PLC, and pick the smallest architecture that meets the full requirement. One station with no logging duties takes a dedicated panel; multiple stations needing simultaneous control or sustained history take a PC-based runtime.

    HMI and touchscreens

  • How-to

    How to migrate a WinCC flexible project to TIA Portal

    One TIA Portal installation replaces both STEP 7 Classic and WinCC flexible, but the two project types move differently: the STEP 7 V5.x project is imported, and the WinCC flexible 2008 project is migrated through an intermediate release because the newest TIA Portal versions no longer offer that migration. Verify the exact S7-300 CPU and panel against the device lists and license STEP 7 and WinCC Comfort separately.

    HMI and touchscreens