WinCC V7.0 SP2 Licensing: RT vs RC PowerTags and PC Counts

David Krause11 min read
SiemensTechnical ReferenceWinCC
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

WinCC V7.0 SP2 Licensing: RT vs RC PowerTags, PC Counts, and Bundled Software

1. Overview of the WinCC V7.0 SP2 Licensing Model

SIMATIC WinCC V7.0 SP2 (released 2010, entry ID 32248844) is licensed per workstation and per PowerTag count. There is no project-wide tag pool that is shared between operator stations; each PC that runs the WinCC Explorer, the WinCC Runtime, or both must carry its own license. Two license roles exist, and selecting the wrong one either blocks configuration on the engineering station or removes runtime capability on the operator station.

Three orthogonal dimensions must be sized before ordering:

  1. Role per PC — Runtime only (RT) versus Runtime plus Configuration (RC).
  2. PowerTag count per PC — 128 / 256 / 512 / 1024 / 2048 / 4096 / 8192 / 16384 / 65536 / 131072.
  3. Communication channel count per PC — limited by the bundled SIMATIC NET edition.

The compatibility and supplementary information document for V7.0 SP2 is published as WinCC V7.0 SP2 Compatibility Notes (PDF, 08/2010). Use this PDF to verify supported operating systems, supported SQL Server versions, and the SIMATIC NET editions that co-install without a separate license transaction.

2. PowerTag Count Tiers

A PowerTag is the unit Siemens uses to charge for tag capacity. Internal tags, archive tags, and process tags all consume PowerTags. Tags driven by scripts, scheduled tasks, or structure tags each count as one PowerTag per referenced element. The license tier must be equal to or greater than the configured count; otherwise WinCC Runtime starts in demo mode (watermark) and the project switches to "limited operation" after the grace period.

PowerTag Tier Order Code Prefix (RT) Order Code Prefix (RC) Typical Use
128 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Small machine, single station
256 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Compact line, 1–2 stations
512 6AV6381-2BD07-0AX0 6AV6381-2BN07-0AX0 Mid-size SCADA, 350–500 tags
1024 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Plant-level visualization
2048 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Multi-area SCADA
4096 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Redundant server pair + clients
8192 / 16384 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Site-wide SCADA
65536 / 131072 6AV6381-2B..07-0AX0 6AV6381-2B..07-0AX0 Enterprise archive servers

For a system that has 350 configured PowerTags, the 128 and 256 tiers are insufficient. The next tier, 512, is the smallest license that covers the project and is the standard recommendation for that footprint. The 512-tier part numbers confirmed in field deployment are:

  • Runtime 512 PowerTags (RT 512) — 6AV6381-2BD07-0AX0
  • Runtime and Configuration 512 PowerTags (RC 512) — 6AV6381-2BN07-0AX0

3. RT versus RC: Which License for Which PC

Siemens splits the license into two complementary products. The right choice depends on what the PC will do at runtime, not during project engineering only.

License Type Runtime Capability Configuration Capability Typical Hardware
RT (Runtime, 6AV6381-2BD07-0AX0 for 512) Yes — WinCC Runtime runs. No — project is read-only; changes require the engineering station. Operator panel PC, control room client.
RC (Runtime and Configuration, 6AV6381-2BN07-0AX0 for 512) Yes — WinCC Runtime runs. Yes — full WinCC Explorer and Graphics Designer available. Engineering station, developer workstation, test bench.
Rule of thumb: Order one RC license for the engineering PC and one RT license for every operator or client PC. If a PC will both develop and display, RT is not enough — use RC. If a PC only displays, RC is functional but adds cost without need.

4. Multi-PC and Multi-Workstation Rules

Each PC that runs WinCC components must be licensed individually. WinCC does not pool PowerTags across machines. The V7.0 SP2 license model supports client/server and redundant server topologies, but the licensing pattern is fixed: one license file per PC, sized for the highest tag count that PC ever loads.

4.1 Single-server, multi-client

  • Server: 1 × RC 512 (or higher), acts as the data manager and project source.
  • Each client: 1 × RT 512 (or higher), receives the published project.
  • Total licenses for 1 server + 4 clients at 350 tags = 1 × RC 512 + 4 × RT 512.

4.2 Redundant server pair

  • Server A and Server B: each carries its own RC license at the same tier (failover requires identical tag counts on both).
  • Clients connect to the active server; they do not need redundant licenses, just RT.

4.3 Project editing on a client

Even a client that only edits the offline copy (for example, a remote engineering laptop) needs an RC license, because WinCC configuration is bound to the local installation. An RT-licensed client cannot open the project for editing.

Scenario Server License Client License (per PC) Total for 4 PCs (1 server + 3 clients)
3 RT clients viewing a server project 1 × RC 512 1 × RT 512 1 RC + 3 RT
1 RC client and 2 RT clients 1 × RC 512 1 × RC 512, 2 × RT 512 2 RC + 2 RT
Single engineering PC only n/a 1 × RC 512 1 RC
Single operator PC only n/a 1 × RT 512 1 RT

5. SIMATIC NET Bundling and PLC Connection Limits

Every RT and RC WinCC V7.0 SP2 license includes a copy of SIMATIC NET at a defined edition. The bundled license covers the communication channels required by that single WinCC PC, but it does not extend to a second WinCC PC or to other applications on the same network.

  • SIMATIC NET Basic — OPC server / client functionality for non-S7 protocols.
  • SIMATIC NET Softnet Lean — S7 communication for up to 8 PLC connections per network adapter (CP).

The "up to 8 PLCs via a common network adapter" figure is the Softnet Lean ceiling. If the WinCC PC must talk to more than 8 S7 controllers on a single Ethernet adapter, upgrade to Softnet S7 Lean plus or to a S7-1613 / CP1623 hardware bundle, or split PLCs across multiple network adapters.

The bundled SIMATIC NET license is per WinCC station, not per project. Adding a fifth operator PC means a fifth bundled SIMATIC NET license activates, and a fifth independent limit of 8 S7 connections applies to that PC. This is the most common source of "why does my new client fail to connect?" tickets in the field.

6. STEP 7 and Engineering Software Requirements

STEP 7 (the SIMATIC Manager for S7-300 / S7-400 programming) and WinCC V7.0 SP2 are separate products with separate licensing. WinCC does not include a STEP 7 license, and a STEP 7 license does not grant WinCC runtime rights.

Software Used For License Needed Separately?
SIMATIC STEP 7 V5.4 / V5.5 Programming S7-300 / S7-400 PLCs Yes, per engineering seat.
SIMATIC STEP 7 Professional (TIA Portal) Programming S7-1200 / S7-1500 / S7-300 / S7-400 Yes, per engineering seat. WinCC V7.x does not include the TIA Portal WinCC Comfort / Advanced / Professional packages.
S7-PLCSIM PLC simulation for offline WinCC testing Yes, per seat. Optional but standard in test labs.
WinCC V7.0 SP2 (RT or RC) SCADA runtime and configuration Yes — the license this article covers.

If the WinCC PC will edit S7 tag symbols, it needs STEP 7 installed locally. STEP 7 is not bundled with WinCC V7.0 SP2, so the STEP 7 license must be acquired and activated independently on each engineering seat.

7. License File, License Key, and Activation

Siemens delivers WinCC V7.0 SP2 licenses as printed certificates with an 18-character License Key. The key is bound to the Automation License Manager (ALM) on the target PC.

  1. Install WinCC V7.0 SP2 from the product DVD or the Siemens Online Software Delivery (OSD) portal.
  2. Install the Automation License Manager (bundled on the same DVD).
  3. Transfer the License Key from the certificate to the local ALM vault. Without this, WinCC Runtime starts in demo mode for 14 days and then reverts to a read-only display with a watermark.
  4. Verify in ALM that the license appears under the correct PC name and is not flagged as defective.
  5. For a redundant or client PC, repeat the transfer; each PC gets its own license slot.

The Compatibility Notes PDF is the authoritative reference for which license key works with which installed WinCC V7.0 SP2 build. SIMATIC NET Edition 2010 and Edition 2008 keys remain valid for the V7.0 SP2 runtime without re-issuance.

8. License Migration to Newer WinCC Versions

Older WinCC licenses are generally not forward-upgradable. If a plant plans to move to WinCC V7.2, WinCC V7.3, WinCC V7.4, or to TIA Portal WinCC Professional, the legacy V7.0 SP2 keys remain valid only for the V7.x line and only as defined by the V7.0 SP2 Compatibility Notes. The PowerTag tier can typically be carried over by purchasing a Software Upgrade License; confirm with Siemens Industry Online Support for the exact order codes in the destination version.

9. Sizing a 350-Tag System: Worked Example

The original question: 350 PowerTags on a single PC. Use the following checklist before placing the order.

  1. Confirm the role of the PC. If it will only display, order 1 × RT 512 (6AV6381-2BD07-0AX0). If it will also configure, order 1 × RC 512 (6AV6381-2BN07-0AX0).
  2. Add 10–20 percent headroom for future tags. 350 / 512 = 68 percent, which is comfortable.
  3. If a future upgrade to 700 tags is expected, skip the 512 tier and order 1024 (6AV6381-2B..07-0AX0) to avoid a second purchase.
  4. Order SIMATIC NET Softnet Lean only if a separate application needs it — it is already included with the WinCC license.
  5. Order STEP 7 V5.5 (or STEP 7 Professional in TIA Portal) only if the PC will edit PLC programs. Pure SCADA operation does not need it.
  6. Verify Windows version. WinCC V7.0 SP2 supports Windows XP Professional 32-bit, Windows Server 2003 32-bit, Windows 7 32/64-bit, and Windows Server 2008 R2 64-bit. The Compatibility Notes PDF lists the exact build numbers.
  7. Verify SQL Server. V7.0 SP2 uses Microsoft SQL Server 2005 or 2008 for the archive database. SQL Server license is bundled with WinCC; no separate purchase required.
  8. For each additional PC, repeat steps 1–7 with the appropriate RT or RC tier.

10. Common Field Pitfalls

Symptom Likely Cause Remediation
Watermark in runtime, "Demo mode" banner. License key not yet transferred to ALM. Open ALM, transfer the key from the certificate to the local vault.
Runtime starts then stops after 14 days. Grace period expired; license not registered. Transfer the key; if the certificate is lost, request reissue from Siemens.
Cannot edit project on a client PC. Client has an RT license instead of RC. Replace RT with RC for the engineering seat.
Operator PC connects to only 8 of 12 PLCs. Softnet Lean 8-connection limit reached. Upgrade to Softnet S7 Lean plus or distribute PLCs across two NICs.
Project loads on server but client shows "invalid project structure". Server has higher tag tier than client. Match client tier to server tier, or lower server project to client maximum.
License flagged "defective" in ALM after PC hardware change. License bound to old SID (security ID). Return defective license, reactivate on new hardware using new SID.
STEP 7 symbols greyed out in WinCC tag management. STEP 7 not installed locally. Install STEP 7 and the matching version of SIMATIC NET on the WinCC PC.

11. Ordering Process

Siemens does not publish a fixed retail price list for WinCC V7.0 SP2; the actual invoice depends on the country, the channel partner, and current promotions. The correct path is:

  1. Contact a Siemens sales representative or authorized distributor (e.g., Siemens Industry Online Support regional contact).
  2. Provide the part numbers from this article: 6AV6381-2BD07-0AX0 for RT 512, 6AV6381-2BN07-0AX0 for RC 512.
  3. Specify whether the bundled SIMATIC NET and SQL Server usage is acceptable on each PC.
  4. Specify the number of operator PCs and engineering PCs to size the total license count.
  5. Request a quotation with delivery of the License Key certificates by mail and the WinCC V7.0 SP2 install media (or OSD download rights).

For sites that already own WinCC V6.x licenses, ask the sales contact about a PowerTag upgrade trade-in, which usually reuses the existing tier with a delta payment.

12. Verification Checklist After Installation

  1. Automation License Manager shows the correct RT or RC entry, tier matches the project, status is "Valid".
  2. WinCC Explorer opens without a demo banner.
  3. Project download to the local runtime completes without "license insufficient" error.
  4. Each configured PLC connection is online in WinCC Tag Management.
  5. Process screens display live values for all 350 configured tags.
  6. For client PCs, the published project from the server loads and reflects updates within the configured refresh interval.
  7. For redundant server pairs, fail over manually and confirm both servers carry the same license tier.

Does a 350-tag WinCC V7.0 SP2 system need a 512-tag license?

Yes. The 128 and 256 tiers are below the configured count and would start runtime in demo mode. The smallest license that covers 350 PowerTags is the 512 tier. Order 6AV6381-2BD07-0AX0 for RT or 6AV6381-2BN07-0AX0 for RC.

Do I need a separate STEP 7 license for the WinCC PC?

Yes, if the PC will edit PLC programs or import STEP 7 symbols into the WinCC tag database. WinCC V7.0 SP2 does not bundle STEP 7. Pure SCADA display on a WinCC-only PC does not require STEP 7.

For four operator PCs, do I buy four WinCC licenses?

Yes, one per PC. Each operator PC needs an RT license at the same PowerTag tier. The engineering PC, if separate, needs an RC license. A 1-server + 3-client topology with 350 tags requires 1 × RC 512 and 3 × RT 512.

How many PLCs can a WinCC PC connect to?

Up to 8 S7 controllers per network adapter using the bundled SIMATIC NET Softnet Lean license. Additional controllers require a Softnet S7 Lean plus upgrade, a CP1613 / CP1623 hardware bundle, or splitting PLCs across multiple NICs.

What is the difference between RT and RD licenses in WinCC?

RT (Runtime) licenses run the project but block configuration. RC (Runtime and Configuration) licenses run the project and allow full engineering in WinCC Explorer. The RD abbreviation sometimes seen in older materials is a typo for RC; verify the part number on the certificate before activation.

Back to blog