Migrating SIMATIC PCS 7 from Windows XP to Windows 10: Licensing and Upgrade Paths

Migrating a SIMATIC PCS 7 system from Windows XP (PCS 7 V7.1 or earlier) to Windows 10 (PCS 7 V9.0/V9.1) requires a staged migration path because direct single-step database conversion is unsupported. Projects must first be migrated to an intermediate version (such as PCS 7 V8.2) to convert S7 project blocks and WinCC databases, followed by migration to V9.0/V9.1 on Windows 10 (64-bit). Commercially, this requires purchasing PCS 7 Upgrade Packages for Engineering, OS Servers, OS Clients, and Process Objects, upgrading license keys in Automation License Manager (ALM), and verifying that existing CPU hardware and communications processors support the target release.

Executive Summary

Plant modernization projects that transition from obsolete Windows XP-based PCS 7 installations (V7.0, V7.1) to modern 64-bit Windows 10 systems (PCS 7 V9.0 SP3 or V9.1) face significant technical and commercial complexities. Major version upgrades in PCS 7 are paid commercial software packages, not free updates. Furthermore, database architectures, APL block libraries, and operating system requirements have changed completely. This guide provides a comprehensive migration roadmap, detailing multi-step project conversion, licensing upgrade mechanics in ALM, hardware compatibility assessments, and operational precautions.

Architecture and Fundamental Mechanics

Migration Architecture, Database Progression, and Licensing Mechanics:

Multi-Step Project Migration Path:
Direct project opening of a V7.0/V7.1 project in PCS 7 V9.1 is unsupported and will corrupt WinCC Sybase/SQL databases and CFC data structures.
Standard Migration Path: PCS 7 V7.1 SP4 (Win XP) -> PCS 7 V8.2 SP1 (Win 7 64-bit) -> PCS 7 V9.0 SP3 / V9.1 SP2 (Win 10 Enterprise LTSC 64-bit).
Commercial Licensing Upgrade Rules:
PCS 7 upgrades are commercial products requiring specific upgrade packages (e.g., 'Upgrade Package ES V7.x/V8.x to V9.0').
In Automation License Manager (ALM), an 'Upgrade License' combines with the old license key to generate the valid V9.x license key.
Existing Process Object (PO) quantities are preserved, but upgrade PO packages must be purchased for both AS RT PO and OS RT PO.
Redundant OS servers require dedicated OS Server Redundancy upgrade packages.
Hardware Compatibility and Firmware Audits:
S7-400 CPUs: CPUs with older firmware (e.g., CPU 414-4H V3/V4) cannot be configured directly in newer PCS 7 HW Config catalogs without firmware updates or hardware replacement.
CP 1613 cards (PCI) must be replaced with CP 1623 (PCIe).
The CPU 410-5H requires System Expansion Cards (SEC) sized for Process Object capacities.

Step-by-Step Implementation Procedure

Comprehensive Roadmap for XP to Windows 10 PCS 7 Migration:

Audit Existing Software and Hardware Inventory:
- On the legacy ES, open SIMATIC Manager -> Help -> Installed Software -> export the detailed list.
- Document exact MLFBs and firmware versions of all CPUs, CPs, and interface modules.
- Open Automation License Manager (ALM) -> export installed license keys and PO counts.
Procure Migration Licensing and Hardware:
- Consult Siemens distributors to procure exact PCS 7 Upgrade Packages:
- ES Upgrade Package (STEP 7, CFC, SFC, PDM, SCL)
- OS Server Upgrade Package & OS Server Redundancy Upgrade
- OS Client Upgrade Packages
- AS & OS Runtime PO Upgrade Packages
- Procure Windows 10 Enterprise LTSC industrial PCs (SIMATIC IPCs or certified commercial servers).
Stage 1 Migration (V7.1 to V8.2 on Intermediate System):
- Restore the project archive on an intermediate engineering station running Windows 7 SP1 and PCS 7 V8.2.
- Open project in SIMATIC Manager; run 'Save As with Reorganization (Slow)'.
- Run the OS Migrator to convert the WinCC SQL database.
- Check block types and update library blocks if migrating from Standard Library to APL.
Stage 2 Migration (V8.2 to V9.0/V9.1 on Windows 10):
- Archive the converted V8.2 project and transfer to the Windows 10 PCS 7 V9.x ES.
- Open project; update block types from PCS 7 AP Library V9.x.
- Run OS Project Editor on all OS Server and Client projects.
- Perform full AS compilation and full OS compilation.
Upgrade License Keys in ALM:
- Connect the legacy license USB stick or transfer old licenses to the new PC via network.
- Insert the Siemens Upgrade License USB.
- In ALM, select the old license key and the upgrade license -> execute 'License Key -> Upgrade'.
- Verify that the upgraded license keys show valid V9.x versions.

Verification

To verify successful migration:
1. In ALM on all nodes, verify zero missing license errors and confirm adequate AS RT PO and OS RT PO counts.
2. Perform a successful full compilation of all S7 programs and OS projects with zero critical errors.
3. Test controller download in S7-PLCSIM or staging hardware; verify that SFC sequences and APL block faceplates operate correctly.
4. Start WinCC Runtime on the OS Server; verify that communication with AS stations is established via Named Connections and that historical archives log without errors.

Limitations and Operational Precautions

Operational precautions:
- Never attempt an in-place operating system upgrade of Windows XP to Windows 10 on the same machine; always perform a clean installation on new hardware or clean disks.
- Major version migrations require a planned plant shutdown because downloading the newly compiled V9.x program to S7-400 controllers requires a CPU STOP/Cold restart if block interfaces or operating system versions have changed.
- Verify all third-party drivers (MODBUS, PROFIBUS DP slaves, PDM device descriptions) for 64-bit Windows 10 and PCS 7 V9 compatibility before cutover.

Engineer FAQ

Can I upgrade PCS 7 V7.1 directly to V9.1 in a single step?

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

Are PCS 7 version upgrades free if I have an older license?

No. Major version upgrades (e.g., V7 to V9) are paid commercial software packages and require purchasing upgrade licenses.

How do upgrade licenses work in Automation License Manager?

The upgrade license key combines with the existing predecessor license key in ALM to generate a single new license key valid for the target version.

Do I lose my purchased Process Objects during an upgrade?

No. Your existing PO capacity is preserved, but you must purchase corresponding PO upgrade packages to elevate them to the new version.

Will my legacy S7-400 hardware work in PCS 7 V9.1?

Only if the CPU MLFB and firmware are supported in the V9.1 HW catalog. Legacy CPUs with older firmware may require firmware upgrades or replacement.

Technical References

Related Tags

PCS 7 Migration
Windows 10 Upgrade
ALM Licensing
Upgrade Packages
Intermediate Migration

Intermediate Migration

20 respuestas

Migrating SIMATIC PCS 7 from Windows XP to Windows 10: Licensing and Upgrade Paths