Diagnosing WinCC License Expiration Warnings and OS RT Process Object Overruns in PCS 7
The WinCC Runtime warning 'The use time of your license has expired, please obtain a valid license' on PCS 7 OS Servers and Clients indicates that the system is operating in Demo Mode because configured runtime tags or Process Objects exceed installed license entitlements. In SIMATIC PCS 7 OS architectures, licensing is governed by count-based OS Runtime Process Object (OS RT PO) licenses. When the number of OS process objects generated by AS-OS compilation exceeds the installed license capacity, WinCC grants a 2-hour grace period before issuing recurring warning dialogs and watermarking operator graphics. To resolve this, run WinCC License Analysis (CCLicenseAnalysis.exe) to determine the exact PO deficit, order additive OS RT PO expansion licenses, and transfer the license keys to the server via Automation License Manager.
Table of Contents
- Executive Summary
- Architecture and Fundamental Mechanics
- Step-by-Step Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
During commissioning or following the expansion of a SIMATIC PCS 7 plant, control room operators and system engineers may encounter recurring modal popup dialogs stating that the software license has expired and prompting them to check license and upgrade options for a designated OS server. While Automation License Manager (ALM) may show that existing basic server licenses are intact without trial expiration dates, WinCC enters a restricted Demo Mode. In PCS 7, this symptom is almost universally caused by OS Runtime Process Object (OS RT PO) license overruns. This technical guide explains how PCS 7 calculates OS PO consumption during AS-OS compilation, details the diagnostic workflow using the WinCC License Analysis utility, and outlines the procurement and installation of additive PO licenses.
Architecture and Fundamental Mechanics
OS Runtime Process Object Licensing Architecture
Unlike standalone WinCC SCADA systems licensed strictly by raw tag count (e.g., 2048 tags, 64k tags), SIMATIC PCS 7 OS Runtime is licensed by Process Objects (PO).
+-------------------------------------------------------------------------+
| SIMATIC PCS 7 Multiproject |
| |
| CFC AS Engineering: |
| - Motors (MotL): 450 blocks |
| - Valves (VlvL): 600 blocks |
| - Controllers (PIDConL): 150 blocks |
| - Digital OPs (OpDi01): 950 blocks |
| - Total AS Blocks with OCM: 2,150 Process Objects |
+-------------------------------------------------------------------------+
|
v AS-OS Compilation
+-------------------------------------------------------------------------+
| WinCC OS Server Runtime |
| |
| Actual OS PO Consumption: 2,150 OS RT PO |
| Installed ALM License: 2,000 OS RT PO (Single Station / Basic) |
| ------------------------------------------------------------------- |
| DEFICIT: +150 OS RT PO [OVERRUN DETECTED] |
| |
| WinCC Behavior: |
| - 2-Hour Grace Period expires |
| - Warning Dialog: 'The use time of your license has expired...' |
| - Graphic Designer runs in Demo Mode |
| - Runtime screens display demo watermark banner |
+-------------------------------------------------------------------------+
Process Object Counting Rules in PCS 7 OS
- What Consumes an OS PO?: Any CFC function block instance that has the attribute
S7_m_c := 'true'(Operator Control and Monitoring / OCM enabled) and generates WinCC tags and messages during OS compilation consumes exactly 1 OS RT PO. - Blocks that DO NOT Consume OS POs: Raw logic blocks without OCM (e.g.,
AND,OR,XOR), user-created internal calculation blocks without WinCC visibility, and raw module drivers (Pcs7AnInif interlinked to a parentPIDConLwithout independent faceplates) do not consume additional OS POs. - Redundant Server Requirement: In redundant OS Server configurations (
SERVER1andSERVER2), both servers must have identical OS RT PO license quantities installed in ALM. Licensing is evaluated locally on each server machine.
Step-by-Step Implementation Procedure
Step 1: Diagnose License Deficit via WinCC License Analysis
- On the affected OS Server (or Single Station), open Windows Start and launch Siemens Automation > WinCC > Tools > WinCC License Analysis (or run
CCLicenseAnalysis.exefromC:\Program Files (x86)\Siemens\WinCC\bin). - Inspect the License Information grid:
- Review the column Configured / Used versus Licensed.
- Look for items highlighted in Red.
- Check the entrySIMATIC PCS 7 OS Software Runtime PO(orWinCC Process Objects).
- Note the exact deficit (e.g., Used:2150, Licensed:2000-> Deficit:150 PO).
Step 2: Verify Process Object Count in SIMATIC Manager
- On the Engineering Station, open SIMATIC Manager.
- In the Plant Hierarchy or Component View, select the OS Server project.
- Right-click the OS project and select Process Objects > Book Process Objects... or view the OS Compile summary report in the compilation log.
- Confirm the exact number of booked OS Process Objects across all operator stations.
Step 3: Procure Additive OS RT PO Licenses
- To eliminate the deficit, select additive expansion packages:
-SIMATIC PCS 7 OS Software Runtime PO 100
-SIMATIC PCS 7 OS Software Runtime PO 1,000
-SIMATIC PCS 7 OS Software Runtime PO 5,000 - Note: For purchasing and license validation, always consult an authorized Siemens distributor or the Siemens Industry Mall to verify the exact order numbers (MLFBs) compatible with your installed PCS 7 version (e.g., V9.0 vs V9.1).
- If operating a redundant OS pair, order identical expansion packs for both Server 1 and Server 2.
Step 4: Transfer Licenses via Automation License Manager
- Open Automation License Manager (ALM) on the Engineering Station or directly on the OS Server.
- Insert the Siemens license USB stick or connect via online license transfer.
- Drag and drop the additive OS RT PO license keys onto the local system drive (typically
C:). - In ALM, right-click the transferred license and select Check License Key to verify integrity and status (Valid / OK).
Step 5: Refresh WinCC License Status
- In WinCC Explorer on the OS Server, open Tools > License Analysis again.
- Confirm that the status has changed from red to green (OK) and that the licensed capacity exceeds configured consumption.
- The runtime warning popups will cease immediately without requiring an OS Server reboot.
Verification
- License Analysis Tool Check: In
CCLicenseAnalysis.exe, verify that all displayed licenses show green status with zero overruns. - Runtime Popup Clearance: Observe WinCC Runtime for more than 2 hours. Confirm that the license expiration dialog no longer appears.
- ALM Overview: In Automation License Manager, select the local
C:drive and execute View > Log. Confirm that no license denial or grace period countdown events are logged.
Limitations and Operational Precautions
- No Mixed Versions: OS RT PO licenses must match the base PCS 7 major release family (e.g., PCS 7 V9.0 licenses cannot fulfill V9.1 requirements unless an upgrade license is applied).
- AS PO vs. OS PO Separation: Purchasing OS RT PO licenses does not expand AS RT Process Objects on the controller (which are locked to the CPU System Expansion Card). AS RT POs and OS RT POs are completely separate license mechanisms.
Engineer FAQ
Why does the popup say 'expired' when ALM shows no expiration date?
WinCC uses the phrase 'license expired' generically to describe both expired trial licenses and license overruns where consumption exceeds licensed count.
What happens after the 2-hour grace period?
WinCC displays persistent modal warning boxes every 10 minutes, watermarks the screen, and restricts Graphic Designer and other editors to read-only demo mode.
Do OS Clients need OS RT PO licenses?
No. Standard PCS 7 OS Clients require only the OS Client runtime license; Process Objects are counted and licensed exclusively on the OS Servers or Single Stations.
Are OS RT PO licenses additive?
Yes. Count-based PO licenses are cumulative. You can add multiple 100 PO or 1000 PO license keys on top of an existing base license.
Do redundant servers share a pooled license?
No. Redundant OS Servers do not share licenses. Both Server 1 and Server 2 must possess identical individual OS RT PO licenses installed on their local drives.
How do I avoid consuming unnecessary OS POs?
Disable the 'OCM' (Operator Control and Monitoring) attribute on internal logic and calculation blocks in CFC that do not need to be displayed in WinCC.
Can I transfer licenses while WinCC Runtime is active?
Yes. Automation License Manager allows transferring valid license keys to the local disk while WinCC Runtime is running, and WinCC detects them dynamically.
Does Web Navigator consume OS RT POs?
No. Web Navigator uses dedicated concurrent client access licenses; it relies on the OS Server's existing PO license base.
What tool identifies which specific blocks consume POs?
In SIMATIC Manager, use the 'Process Objects > Book Process Objects' dialog or inspect the OS compilation log file.
Where can I find the official licensing rules?
Refer to the SIMATIC PCS 7 Licenses and Configuration Limits manual published on Siemens Industry Online Support.
Technical References
- SIMATIC PCS 7 Licenses and Configuration Limits Manual V9.0 / V9.1
- WinCC V7.5 / PCS 7 OS System Description - Licensing Concepts
- Siemens Industry Online Support (SIOS) Entry ID 109780813: SIMATIC PCS 7 Process Objects Licensing
- Automation License Manager (ALM) V6.0 Operating Manual
Related Articles
- Diagnosing Missing AS RT Process Object Licenses and Unbooked PO Discrepancies in PCS 7
- Recovering Lost Process Object Licenses When the Original PCS 7 Project is Missing or Deleted
- Adding OS Clients to Legacy SIMATIC PCS 7 V8.0 Plants - License Compatibility and Ordering Constraints
Related Tags
- WinCC Licensing
- OS RT PO
- Process Objects
- License Analysis
- Demo Mode
- Automation License Manager
- PCS 7 V9.0