Engineering Workflow and Hardware Licensing Strategy for Migrating PCS 7 V8.0 to V9.0

Migrating a SIMATIC PCS 7 V8.0 system to PCS 7 V9.0 SP3 requires a clean installation on modern operating systems (Windows 10 Enterprise LTSC or Windows Server 2016/2019), upgrading engineering and runtime software licenses via Siemens Upgrade Packages, updating the Advanced Process Library (APL) block types, and compiling the migrated database. S7-400 controllers (e.g., CPU 414-5H, 417-5H, 410-5H) are supported in V9.0 but require minimum firmware verification. Final license quantities, upgrade packages, and hardware compatibility must be validated with an authorized Siemens distributor quotation.

Executive Summary

Upgrading an automation facility from SIMATIC PCS 7 V8.0 to V9.0 SP3 represents a major technological leap. Because PCS 7 V8.0 operated on Windows 7 and Windows Server 2008 R2 (which are obsolete and unsupported by Microsoft), the migration mandates new PC station hardware or clean virtual machine deployments. Furthermore, licensing structures, library versions, and controller firmware must be aligned. This guide provides an end-to-end engineering methodology for upgrading projects, details the licensing transition across ES, OS, and AS tiers, and establishes commercial accuracy guardrails.

Architectural and System Mechanics

Architectural Evolution and Migration Mechanics:

Operating System Paradigm: In-place Windows upgrades over PCS 7 installations are strictly unsupported. Migration requires deploying clean operating system instances (Windows 10 Enterprise LTSC 2016/2019 for Clients/ES, Windows Server 2016/2019 for Servers).
Licensing Upgrade Architecture:
Engineering Upgrade: 'SIMATIC PCS 7 Engineering Upgrade Package V8.x to V9.0'.
OS Runtime Upgrade: Dedicated OS Server and Single Station upgrade packages.
Process Objects: Existing AS RT PO and OS RT PO quantities remain valid, but require version upgrade keys in Automation License Manager (ALM).
Separate Software Packages: Maintenance Station, SIMATIC BATCH, and Route Control require independent upgrade licenses.
Hardware Controller Compatibility:
S7-400H (V4.5 / V6.0): Compatible with PCS 7 V9.0, provided firmware meets minimum requirements.
CPU 410-5H: Fully supported across all V8.x and V9.x versions; firmware updates to V8.2.x are recommended.
Library Upgrades: Transitioning from older APL versions to APL V9.0 requires updating block types and regenerating instance DBs.

Step-by-Step Engineering and Implementation Procedure

Step 1: Prepare and Archive the V8.0 Project

On the V8.0 Engineering Station, open SIMATIC Manager.
Execute 'File' -> 'Archive...' selecting the Multiproject.
Choose 'With reorganization (slow)' to clean database fragmentation and purge deleted records.
Export the current license inventory from Automation License Manager (ALM).

Step 2: Procure Migration Upgrade Licenses

Procure the necessary upgrade packages through an authorized Siemens distributor:
- SIMATIC PCS 7 Engineering Upgrade Package V8.x to V9.0.
- SIMATIC PCS 7 OS Software Server / Redundancy Upgrade Packages.
- SIMATIC NET Upgrade licenses for industrial communication.

[!NOTE]
Validate exact MLFBs, software tiers, and runtime PO capacities with your authorized Siemens distributor quotation prior to purchase.

Step 3: Install PCS 7 V9.0 SP3 on New Engineering Station Hardware

Deploy certified industrial PCs (e.g., SIMATIC IPC547G) running Windows 10 Enterprise LTSC.
Install PCS 7 V9.0 SP3 from the official setup media.
Install upgraded license keys via Automation License Manager.

Step 4: Open and Migrate the Multiproject in V9.0

Retrieve the archived project in SIMATIC Manager V9.0.
Open the project; SIMATIC Manager prompts to convert the database to the current format. Confirm conversion.
Open the Master Data Library; copy the latest APL V9.0 blocks into the library.
In CFC, execute 'Options' -> 'Block Types...' -> 'Update...' to update instances across all charts.
Open HW Config; update module descriptions and verify controller firmware compatibility.

Step 5: Migrate and Compile the Operator Stations

Open WinCC Explorer on each OS project; the Project Migrator converts WinCC V7.2/V7.3 databases to WinCC V7.4 SP1.
Run the OS Project Editor to update standard system displays (@Screen.pdl, @Overview1.pdl).
Execute a full AS compilation and full OS compilation.

Verification

To verify migrated project integrity:
1. Execute CFC and SFC consistency checks; verify zero syntax errors or missing block definitions.
2. Check ALM on all stations; confirm zero license deficit warnings.
3. Download the migrated project to a test controller or S7-PLCSIM; verify process logic execution and alarm generation.
4. Start WinCC Runtime; verify that block icons render properly, faceplates open promptly, and trends display historical data.

Limitations and Operational Precautions

Operational precautions:
- Major version migrations across four service packs cannot be performed as delta downloads in RUN; a scheduled plant maintenance outage is required to download upgraded block types.
- Never discard the original V8.0 backup archive until the V9.0 system has successfully completed full site acceptance testing (SAT).
- Third-party communication drivers and PDM device descriptions (EDDs) must be verified for 64-bit OS compatibility.

Engineer FAQ

Q: Can I upgrade PCS 7 V8.0 to V9.0 in-place on the same Windows installation?

A: No. PCS 7 V8.0 is limited to Windows 7 / Server 2008, while V9.0 requires Windows 10 / Server 2016 or 2019. A clean OS install is mandatory.

Q: Do I lose my existing Process Object licenses during upgrade?

A: No. Siemens provides upgrade packages that elevate existing V8.x PO capacities to V9.0.

Q: Can existing S7-400H hardware run PCS 7 V9.0?

A: Yes, standard S7-400H controllers are supported, though older hardware may require firmware updates to ensure compatibility.

Q: What happens if I don't run the OS Project Editor after migration?

A: WinCC system pictures will retain old V8 scripts and styles, causing faceplate loading errors and graphic rendering defects.

Q: Is SIMATIC BATCH migration included in the standard upgrade?

A: No. SIMATIC BATCH requires dedicated BATCH upgrade licenses and database migration utilities.

Technical References

Related Tags

PCS 7 Migration, Upgrade Strategy, APL Update, License Upgrade, S7-400 Migration

20 respuestas

Engineering Workflow and Hardware Licensing Strategy for Migrating PCS 7 V8.0 to V9.0