IMDTouchKnowledge BaseShop main store

Explainer

WinCC RT vs RC Licenses and Moving a Runtime Key

HMI and touchscreens Published 6 min read

Short answer

RT authorizes running the configured WinCC project; RC (Runtime plus Configuration) is what lets a PC also edit it in WinCC Explorer, and the number in a class such as RT 128 is the external-tag capacity. A license key reaches another PC only through the documented transfer, which removes it from the source machine.

On this page
  1. RT runs the project, RC edits it
  2. What the 128 in RT 128 counts
  3. Client/server adds WinCC/Server
  4. Preparing the destination PC
  5. Transferring the key
  6. Choosing the license per station
  7. Questions asked

RT and RC are rights, not performance tiers. An RT license authorizes running the configured WinCC project in runtime mode; RC (Runtime plus Configuration) is what lets a PC also edit that project in WinCC Explorer. The number in a class such as RT 128 is the external-tag capacity, so RT 128 covers a project holding up to 128 external tags. A license key reaches another PC only through the documented transfer, which removes the key from the source machine.

RT runs the project, RC edits it #

Runtime is execution: the screens, tags, connections and archives exactly as configured. Configuration is engineering: opening the project in WinCC Explorer and changing any of it. The license letters follow that split — RT grants runtime rights only, RC grants runtime plus configuration rights on one key. The letter sets the rights and the number sets the capacity, and they combine independently: an RC 128 key configures and runs a project of up to 128 external tags, which is the arrangement Siemens describes for PowerTags licensing.

What RT never covers is opening WinCC Explorer to change the project. Everything an operator does at a running screen — writing a setpoint, acknowledging an alarm, issuing a command — is runtime functionality, bounded by the user administration configured into the project and by the controller logic that receives the write, not by the RT/RC split. Once an RC station edits the project, why an HMI edit needs a new runtime download is the step that puts the change in front of the operator.

Activity Covered by Not covered by
Run the configured project RT or RC —
Edit screens, tags, connections in WinCC Explorer RC only RT
Write setpoints, acknowledge alarms on runtime screens RT, within configured user rights RC not required
Serve WinCC clients WinCC/Server, on the server RT or RC alone

What the 128 in RT 128 counts #

An external tag is a variable with a communications connection to an external data source such as a controller; current documentation names these PowerTags. The 128 is that count and nothing else — not screens, not operators, not a limit on how often values change. Internal project variables without a communications connection are a separate population and do not consume the external-tag capacity.

Worked example, illustrative numbers. A batching station runs under an RT 128 key with 104 external tags configured across two controllers.

  • Spare capacity today: 128 - 104 = 24 tags.
  • Planned expansion adds 34 tags: 104 + 34 = 138, over the license by 138 - 128 = 10.
  • A cleanup finds 10 tags no longer referenced: 104 - 10 = 94, then 94 + 34 = 128, exactly at the limit with zero spare.

Decision: take the cleanup only if the tag list is final — one further device revision breaches the license again, so order the next tag tier with this expansion. If this station will also edit the project, the replacement key is RC at the higher count, not RT. Licensing and communication stay separate checks after that: the new tags can still show invalid values from a wrong bit address, which fixing invalid bit address errors when adding HMI tags works through.

Client/server adds WinCC/Server #

In a WinCC client/server configuration, the computer acting as the WinCC server needs the WinCC/Server license in addition to its runtime and tag licensing. That license is not another name for RC and does not substitute for it — the server still needs the rights and capacity for the project it hosts. Client requirements are specified per client by Siemens and depend on how each client connects, so budget one license line per client when you specify the system; the server key never covers them. A single-PC installation with no clients needs no WinCC/Server license at all: RT or RC plus the tag count is the entire requirement.

Preparing the destination PC #

The license authorizes use; it installs nothing. Match the destination's installed WinCC product and release to the license's applicability, install that software from Siemens or an authorized distributor, and carry the project over by the supported project-handling procedure — running a WinCC 7.0 project on another PC without a new build is that path for a V7 project. Re-point machine-specific settings such as controller connection endpoints and file paths. If the RC key will land on this PC, engineers must be able to open WinCC Explorer there, which makes configuring Windows user rights for WinCC Explorer access part of the same change.

Back up the project and record the source PC's license inventory before touching anything: product, rights class, tag count. Removing the license changes the source machine's licensing state, so run this as a controlled change in a window where the process tolerates that operator station going dark.

Transferring the key #

Siemens' license help states the rule in one line: "When you transfer a license, the associated license key is removed from the license key storage location." Transfer is a move, not a duplication. Copying project files carries no licensing rights, and copying license-storage files is not a supported transfer — the result is not a valid entitlement on either machine.

  1. Record the source license inventory: product, RT or RC class, tag count.
  2. In the vendor's license-management utility, select the key and execute the documented transfer to the destination.
  3. Confirm the utility reports success and that the key now appears in the destination's license storage with the same product, class and count.
  4. Start the runtime on the destination and confirm it comes up licensed; the source no longer holds the key.

If the utility reports the key damaged, inaccessible or missing, stop and use the documented recovery path or official Siemens support instead of attempting any manual repair of the key data.

Choosing the license per station #

Put RT at the correct tag count on every runtime-only operator PC, and RC on each station where an engineer sits; RC already includes runtime rights, so those stations need no second key. One key serves one machine: a second engineering station takes its own RC, or you transfer the single key when only one engineer edits at a time. Servers carry WinCC/Server on top of their runtime licensing. The RT/RC letters with tag counts span the WinCC PC runtimes — WinCC Explorer projects (WinCC V7) and PC Runtime Advanced, where external tags carry the PowerTags name — and how WinCC V7.4, WinCC Flexible 2008 and TIA Portal differ sorts out which engineering tool belongs to which. Decision in one line: size RT to the external-tag count plus growth, put RC where editing happens, and move keys only by the documented transfer.

Questions asked

Does RC include runtime rights, or does an engineering PC need RT as well?

RC means Runtime plus Configuration in a single key, so an engineering station holding RC both runs the project and edits it; no separate RT key is needed there. Stations that only run still take RT. Size each key's tag count to the project it hosts.

Can I copy the license files to the second PC instead of transferring?

No. The supported transfer removes the key from the source and registers it at the destination; copying license-storage files is not a documented transfer and leaves you without a valid entitlement on either machine. Use the vendor's license-management utility and keep the transfer result for your records.

What if the transfer fails and the key is reported damaged or missing?

Stop and use the documented recovery path or official Siemens support. Deleting or recreating key data by hand is unsupported and can destroy the entitlement. Record the license inventory before you start, because until recovery completes the source PC is in whatever state the utility last reported.

Does one RC license cover several engineering PCs?

No. The RC key sits on one computer; a second engineering station needs its own RC license, or you transfer the single key between them. A transfer suits one roaming engineer, not two people editing different projects at the same time.

Will the source PC still run WinCC after the transfer?

No. The transfer removes the key from the source's license key storage, so that installation is no longer licensed. Schedule the cutover for a window where the process tolerates that station going dark, then either retire the source PC or license it separately for its next role.

Keep reading

  • How-to

    Running a WinCC 7.0 project on another PC without a new build

    No. WinCC has no compile-to-EXE option: the destination PC needs WinCC Runtime of version 7.0 or higher, installed and licensed, and you transfer the project files to it. A newer WinCC opens and converts the project; an older release will not open it.

    HMI and touchscreens

  • How-to

    Running a WinCC Flexible 2008 Project in PC Runtime

    Yes — WinCC flexible 2008 Advanced targets a PC station. Compile the project to a .fwx file and run it with the separately installed, tag-licensed WinCC flexible Runtime through its loader; the compile never produces an .exe.

    HMI and touchscreens

  • How-to

    Launching Windows programs from a Vijeo Designer runtime

    No. A Vijeo Designer runtime screen cannot start a Windows program: the object action lists contain no run-program entry, and the only application-level control is the exit-runtime key. Configure third-party tools from the Windows desktop after exiting, or reach them through a remote session while the runtime keeps running.

    HMI and touchscreens