Best Practices and Licensing for Upgrading SIMATIC PCS 7 from v8.0 to v8.2 with Process Object Expansion

Upgrading a live SIMATIC PCS 7 v8.0 plant (1 ES, 1 OS Single Station, 1 AS S7-416) to PCS 7 v8.2 while expanding capacity by 300 Process Objects (PO) requires choosing between an 'Update with utilization of new functions' or an 'Update without utilization of new functions'. To minimize plant downtime, execute the update without utilizing new functions: keep existing AS block libraries unchanged to avoid mandatory CPU stops, migrate the OS project databases on the ES, deploy the upgraded OS runtime, and install the required software upgrade licenses alongside 300 PO expansion packages for ES, OS, and AS runtime.

Upgrade Strategies: With vs Without Utilization of New Functions

When migrating a production facility from SIMATIC PCS 7 v8.0 to v8.2, Siemens defines two official upgrade strategies:

Strategy 1: Update Without Utilization of New Functions (Minimum Downtime):
The existing S7-400 controller block libraries (APL v8.0 or standard library) remain untouched in the CPU.
No block type updates or CPU STOP modes are required for controller logic.
Engineering Station (ES) and Operator Station (OS) software is upgraded to v8.2.
WinCC project files, faceplates, and picture hierarchies are converted to v8.2 format.
The plant continues operating with minimal interruption; only OS runtime restarts during changeover.
Strategy 2: Update With Utilization of New Functions (Full Modernization):
Block types in the CFC charts are updated to APL v8.2.
Requires a complete AS compile and download, necessitating a scheduled plant shutdown and CPU STOP.
Unlocks new technological features (e.g., enhanced interlock bypasses, new driver functions, and expanded diagnostics).

Licensing Architecture and Process Object (PO) Expansion Requirements

Expanding capacity by 300 Process Objects during a version upgrade requires coordinating both version upgrade licenses and runtime capacity licenses:

License TypeScope & Package DescriptionTypical Siemens MLFB / PackagePurpose in Upgraded SystemES Upgrade LicenseUpgrade PCS 7 Engineering from v8.0 to v8.26ES7651-5AA58-0YE5Authorizes STEP 7 v5.5 SP4, CFC v8.2, and engineering tools on the ES.OS Upgrade LicenseUpgrade OS Single Station / Server from v8.0 to v8.26ES7652-0XX58-0YE5Upgrades WinCC runtime from v7.2 to v7.4 and OS runtime software.ES PO ExpansionEngineering Process Object expansion (e.g., +300 PO)6ES7651-5AA58-0YD5Permits compiling additional technological charts and instances in CFC.OS RT PO ExpansionOS Runtime Process Object expansion (+300 PO)6ES7652-0XX58-0YD5Permits WinCC Runtime to process 300 additional AS/OS process tags.AS RT PO ExpansionAS Runtime PO expansion (for S7-416 / S7-410)6ES7653-2BA00-0XB5 (CPU 410 SEC) or AS RT PO CardAuthorizes controller CPU memory and runtime PO execution.

Table 1: License packages required for PCS 7 v8.0 to v8.2 upgrade with +300 PO expansion.

Always validate final license quantities, order numbers (MLFBs), and exact upgrade package compatibility with an authorized Siemens distributor quotation prior to procurement.

Hardware Compatibility and Operating System Prerequisites

Operating system requirements change significantly between versions:
* PCS 7 v8.0: Supported on Windows XP SP3, Windows 7 SP1 32/64-bit, and Windows Server 2008 R2.
* PCS 7 v8.2: Requires 64-bit operating systems: Windows 7 SP1 64-bit (Ultimate/Enterprise) for ES/OS Single Station, or Windows 10 Enterprise 2015 LTSB 64-bit for client roles, and Windows Server 2012 R2 Standard 64-bit for OS Servers.
* Verify that existing IPC hardware (e.g., IPC547D/IPC647D) has sufficient RAM (minimum 8 GB for ES/OS) and 64-bit processor architecture before upgrading.

Step-by-Step Staged Migration Workflow with Minimum Interruption

Follow this staged engineering workflow:

Complete Multiproject Backup:
* In SIMATIC Manager on the ES, perform File > Archive to capture the complete multiproject and OS databases.
* Capture hard drive image backups of the ES and OS stations using an image creation utility.
Upgrade Engineering Station:
* Install Windows 7 SP1 64-bit and PCS 7 v8.2 on the ES (or deploy a new staging ES).
* Install the new licenses via Automation License Manager (ALM): ES upgrade license, ES PO expansion (+300 PO), and AS RT PO licenses.
* Retrieve the multiproject in SIMATIC Manager v8.2.
* Run the Migrate Project wizard to update database headers.
Migrate WinCC OS Project:
* Open the OS project in WinCC Explorer on the ES: the WinCC Project Migrator will run automatically.
* Recompile the OS with option Changes Only.
Deploy to OS Single Station:
* Upgrade the OS Single Station PC to Windows 7 SP1 64-bit / PCS 7 v8.2.
* Transfer the OS Upgrade and OS RT PO (+300 PO) licenses.
* Download the migrated OS project from the ES.
* Activate WinCC Runtime and verify communication to the running S7-416 CPU.
Add New Process Objects:
* Engineer the additional 300 Process Objects in CFC.
* Download CFC changes online (Compile/Download Changes Only) without stopping the CPU.

Verification

To confirm a successful upgrade and PO expansion:

Open Automation License Manager (ALM) on ES and OS: verify that all upgrade licenses and PO expansion licenses show status Valid with zero license errors.
In SIMATIC Manager, select the multiproject, right-click, and select PCS 7 License Information:
* Verify that configured AS POs and OS POs do not exceed the expanded license quota (+300 PO).
Activate WinCC Runtime: confirm that process graphics load cleanly without license violation popups.
Execute a test setpoint change and alarm acknowledge: confirm bidirectional control with the controller.

Limitations and Operational Precautions

Never attempt to upgrade an active controller block library without an authorized plant shutdown; downloading updated block types requires a CPU STOP.
Ensure all third-party software (such as antivirus or backup agents) are updated to versions released for PCS 7 v8.2.
Do not delete the old v8.0 license keys from Automation License Manager until upgrade license keys are successfully upgraded and validated.

Engineer FAQ

Can an S7-416 CPU run with a PCS 7 v8.2 OS without firmware upgrade?

Yes. An existing S7-416-3 or S7-416-5H running supported firmware (e.g., V5.3 or V6.0) communicates seamlessly with PCS 7 v8.2 OS stations over standard Named Connections.

How are AS Process Objects counted during compilation?

The PCS 7 compiler counts every technological block that communicates with the OS (e.g., MotL, VlvL, PIDConL) or generates operator messages as 1 AS Process Object.