Planning and Executing Software Upgrades to SIMATIC PCS 7 V9.0

Upgrading an existing SIMATIC PCS 7 installation to V9.0 requires a structured progression path because direct database conversion across multiple major generations is unsupported. Systems on PCS 7 V7.1 or earlier must first migrate through an intermediate version (such as PCS 7 V8.2) to convert CFC structures and WinCC SQL databases before upgrading to V9.0 on Windows 10 (64-bit) or Windows Server 2016. The upgrade requires purchasing commercial PCS 7 Upgrade Packages for Engineering, OS Servers, Clients, and Process Objects, upgrading licenses in ALM, and auditing CPU firmware compatibility.

Executive Summary

Plant managers and automation engineers frequently seek a straightforward, single-step upgrade path to elevate older PCS 7 installations to modern PCS 7 V9.0 releases to take advantage of PROFINET, CPU 410-5H controllers, and Windows 10 security. However, jumping across multiple PCS 7 versions without adhering to intermediate migration steps leads to database corruption, uncompilable CFC charts, and stranded hardware. This guide details the version progression roadmap, commercial upgrade licensing rules, hardware lifecycle evaluations, and step-by-step execution procedures.

Architecture and Fundamental Mechanics

PCS 7 Version Progression Roadmap and Upgrade Mechanics:

Multi-Version Upgrade Rules:
Direct migration to PCS 7 V9.0 is officially supported from PCS 7 V8.2 SP1 or PCS 7 V8.1 SP1.
Legacy versions (V7.0, V7.1, V8.0) must execute a two-stage migration: V7.1 -> V8.2 -> V9.0.
Operating System Paradigm Shift:
PCS 7 V9.0 dropped support for 32-bit operating systems. Workstations require Windows 10 Enterprise LTSC (64-bit) or Windows Server 2016 (64-bit).
In-place OS upgrades are strictly unsupported; clean OS installations on new or reformatted hardware are mandatory.
Commercial Licensing Upgrades:
Major version upgrades are paid commercial products, not free maintenance updates.
Upgrade packages (e.g., Upgrade Package ES V8.x to V9.0) require existing valid predecessor license keys in Automation License Manager (ALM) to generate new V9.0 keys.
Redundant OS pairs require dedicated OS Server Redundancy upgrades.
Hardware Lifecycle Checks:
Legacy CPUs (e.g., S7-400 V4 or older) are not supported in the V9.0 hardware catalog and must be audited via MLFB for firmware upgrade eligibility or hardware modernization.

Step-by-Step Implementation Procedure

Step-by-Step Upgrade Roadmap to PCS 7 V9.0:

Audit System Inventory and Compatibility:
- In SIMATIC Manager, check Help -> Installed Software -> export list.
- Audit all CPU, CP, and remote I/O interface MLFBs against the PCS 7 V9.0 Released Modules catalog.
- Export current license keys and Process Object counts from ALM.
Procure Upgrade Packages:
- Order commercial PCS 7 Upgrade Packages:
- ES Upgrade Package (STEP 7, CFC, SFC, SCL, PDM)
- OS Server Upgrade Packages & OS Server Redundancy Upgrade
- OS Client Upgrade Packages
- AS and OS Runtime PO Upgrade Packages
Stage 1 Migration (if migrating from V7.x):
- Restore project on an intermediate V8.2 engineering PC.
- Open project -> Save As with Reorganization (Slow).
- Run OS Migrator to convert WinCC databases.
- Archive converted V8.2 project.
Stage 2 Migration to V9.0 on Windows 10:
- Restore project archive on the Windows 10 PCS 7 V9.0 ES.
- Update Master Data Library blocks from PCS 7 AP Library V9.0.
- Run 'Options -> Charts -> Update Block Types' across all S7 programs.
- Open each OS project -> run the OS Project Editor.
Execute Full Compilations:
- Compile all CFC charts (Scope: Entire program) with 'Generate module drivers'.
- Compile all OS projects (Scope: Entire OS, Tags and messages).
License Upgrade in ALM:
- Insert the Siemens Upgrade License USB sticks.
- In ALM, select old license keys and upgrade keys -> click 'License Key -> Upgrade'.
- Verify resulting V9.0 license keys.

Verification

To verify the V9.0 upgrade:
1. In ALM, verify that all installed license keys indicate version '9.0' with zero missing license warnings.
2. Open SIMATIC Manager; perform a complete 'Check and Compile Everything' in NetPro; verify zero network errors.
3. Compile S7 programs and OS projects; verify clean compilation with zero critical errors.
4. Test execution in S7-PLCSIM or staging hardware; confirm faceplates, interlocks, and alarms operate correctly.

Limitations and Operational Precautions

Operational precautions:
- Upgrades across major versions require a planned plant shutdown because downloading the newly compiled V9.0 program to S7-400 controllers requires a CPU STOP/Cold restart.
- Never attempt an in-place upgrade of Windows on an active PCS 7 workstation.
- Ensure that all third-party communication drivers (Modbus, PROFIBUS DP slaves) have 64-bit compatible device descriptions before initiating cutover.

Engineer FAQ

Can I upgrade directly from PCS 7 V7.1 to V9.0?

No. Direct single-step migration across multiple major generations is unsupported; projects must be migrated through an intermediate version such as PCS 7 V8.2.

Are PCS 7 upgrades free if I already purchased PCS 7?

No. Major version upgrades (e.g., V8 to V9) are commercial products requiring the purchase of upgrade packages.

What operating system is required for PCS 7 V9.0?

Windows 10 Enterprise LTSC (64-bit) for engineering and clients, and Windows Server 2016 (64-bit) for servers.

Do my existing Process Objects carry over to V9.0?

Yes, but you must purchase corresponding PO upgrade packages to elevate them to the V9.0 release.

Can older S7-400 CPUs run in PCS 7 V9.0?

Only if their specific MLFB and firmware are listed in the PCS 7 V9.0 Released Modules catalog; legacy hardware may require firmware updates or replacement.