How to Resolve 'License Installed on Target System Is Insufficient' During OS Changes-Only Download in PCS 7

In SIMATIC PCS 7 V8.1 SP1, the error 'Cannot load changes, license installed on target system is insufficient' during an OS 'Changes Only' download occurs when the target Operator Station lacks an active WinCC Runtime Process Object (RT PO) license or when Automation License Manager (ALM) detects that cumulative tag/PO consumption exceeds the installed license capacity. While an 'Entire Download' simply transfers static project files without enforcing online licensing validations, a 'Changes Only' delta download connects dynamically to the running WinCC database service and interrogates active license availability. To resolve this, verify installed WinCC RT PO licenses in ALM on the target OS, check actual tag count in WinCC Explorer, and transfer required upgrade licenses.

DCS Licensing Architecture: Entire Download vs Changes-Only Download

SIMATIC PCS 7 enforces distinct validation mechanisms depending on whether an engineer performs an 'Entire Download' or a 'Changes Only' download to an Operator Station:

Entire OS Download (PLC > Download > Entire Download):
Deactivates WinCC Runtime on the target server, purges the destination directory, and copies all project binaries and SQL databases over the network share.
Because WinCC is not active during the file transfer, the Engineering Station checks only offline engineering project consistency; it does not interrogate the online licensing daemon on the target machine.
Changes-Only Download (PLC > Download > Changes):
Designed to update an active, running OS Server without interrupting live plant operations.
Before applying delta changes to the active SQL Server database, the engineering system communicates via DCOM/OPC with the target station's Automation License Manager (ALM) and WinCC license service.
If the number of configured process objects exceeds the installed WinCC Runtime PO license, or if the runtime license has entered the 14-day trial grace period, the delta loader aborts immediately: Cannot load changes, license installed on target system is insufficient.

How WinCC Process Objects (PO) Are Counted and Validated

In PCS 7 OS engineering, licensing is structured around Process Objects (PO) rather than raw I/O tag counts:

What Constitutes an OS Process Object?:
Any CFC block capable of operator communication and monitoring (S7_m_c := 'true'), such as MotL (motor), VlvL (valve), PIDConL (PID controller), or MonAnL (analog monitor), consumes exactly 1 OS RT PO.
Internal tags, raw SFC charts, and basic mathematical blocks do not consume OS RT POs.
Cumulative PO Tiers:
OS Runtime licenses are purchased in discrete capacity tiers (e.g., 250 PO, 1,000 PO, 2,000 PO, 5,000 PO, 8,500 PO, or Count-relevant PowerPacks).
In redundant OS Server architectures, both OS Server Master and OS Server Standby must possess identical, independently licensed WinCC RT PO capacity installed in ALM.

Root Causes of 'License Installed on Target System Is Insufficient'

Forensic analysis of PCS 7 V8.1 SP1 projects identifies three primary triggers for this compilation failure:
1. Delta Expansion Exceeding PO Ceiling: The engineering changes added new process equipment (motors, valves, transmitters) in CFC that pushed total OS PO consumption beyond the installed license limit (e.g., 1,008 POs configured with only a 1,000 PO license installed).
2. Missing or Corrupted License Key in ALM: The license key on the target OS server was moved, corrupted by disk errors, or converted to a trial license (Trial 14 days) following a Windows patch or ALM version mismatch.
3. Engineering Station AS/OS Engineering License Shortage: In certain PCS 7 service packs, the delta download mechanism checks the Engineering Station's AS/OS Engineering license in parallel with the target server's runtime license. If the ES engineering license is missing or expired, a false-positive target license error is triggered.

Verifying and Managing Licenses in Automation License Manager (ALM)

To diagnose and restore OS licensing compliance:

Check License Inventory on Target OS Server:
* On the target OS server, launch Automation License Manager (ALM).
* Select local drive C: and inspect the list of installed license keys.
* Verify the presence of: SIMATIC WinCC Server and SIMATIC WinCC RT (xx PO) (e.g., WinCC RT 1000 PO).
* Confirm the License type is Single or Floating (NOT Trial) and that the license status is OK.
Audit Actual Process Object Consumption:
* Open the OS project in WinCC Explorer on the ES.
* Select the root project node and right-click Properties.
* Open the Process Objects tab: inspect Configured Process Objects versus Licensed Process Objects.
Transfer Additional PO PowerPack Licenses:
* If configured POs exceed licensed POs, purchase and install an official Siemens WinCC RT PO PowerPack license.
* In ALM on the ES, connect to the target OS station via License Key > Connect Computer... and transfer the required PowerPack license directly onto the target server drive.

Comparison of OS Download Modes and Licensing Requirements

The table below contrasts the characteristics and licensing enforcement of Entire versus Changes-Only OS downloads.

Operational FeatureEntire OS DownloadChanges-Only OS DownloadWinCC Server Runtime StateMust be deactivated / stoppedRemains fully active in RUN modePlant ImpactLoss of server visualization during transferZero downtime; continuous operator controlLicensing ValidationValidates only ES engineering keysQueries online target ALM licensing servicePO Overrun HandlingDownloads successfully; triggers demo popupsAborts download immediately with errorRedundant Partner SynchronizationRedundant partner remains active; manual syncAutomated delta sync across redundant pairTypical Execution Time10 to 30 minutes30 to 90 seconds

Verification

To confirm that the license issue is resolved and delta download functions:
1. In Automation License Manager on the target OS server, verify that the total installed WinCC RT PO capacity equals or exceeds the total configured PO count.
2. In SIMATIC Manager on the ES, right-click the OS project: select Compile. Perform a delta compilation.
3. Once compiled, select PLC > Download.
4. Choose Changes download and click OK.
5. Confirm that the download dialog successfully executes through all delta steps without displaying the insufficient license error.
6. On the OS Server, verify that the WinCC message window reports: Delta download successfully completed.

Limitations and Operational Precautions

Operating a production OS server with insufficient PO licenses or in trial mode can cause WinCC Runtime to enter demo mode, displaying recurring hourly pop-up warnings that disrupt operator actions.
In redundant OS configurations, never install the runtime license on only one server; both physical or virtual servers must have independent, matching license counts.
Do not attempt to bypass licensing restrictions by manipulating system clocks or deleting license database files, as ALM will permanently flag the license storage as corrupted.
Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why did Entire Download work, but Changes Download failed?

Entire Download transfers static database files while WinCC is offline, bypassing live ALM runtime validation. Changes Download requires live interaction with the active WinCC runtime licensing manager, which strictly enforces PO limits before allowing database injection.

How can I see how many POs my project currently uses?

In SIMATIC Manager, select the multi-project root, right-click, and choose PCS 7 License Information. This utility displays total configured AS Runtime POs and OS Runtime POs alongside available licenses.

Can I upgrade OS PO licenses while the plant is running?

Yes. WinCC RT PO licenses can be transferred to the target OS server using Automation License Manager across the network while WinCC Runtime is actively running, immediately enabling Changes Only downloads.