Upgrading SIMATIC PCS 7 from V7.1 to V9.0 - Hardware Reuse and Modernization Rules

Upgrading a SIMATIC PCS 7 installation from V7.1 to V9.0 requires replacing obsolete PC hardware while allowing selective reuse of controller and communication modules. Legacy SIMATIC IPC547D workstations running Windows XP must be replaced because modern PCS 7 V9.0 mandates 64-bit Windows 10 Enterprise 2016 LTSB or Windows Server 2016, for which legacy IPC chipsets lack certified drivers. Existing S7-400 CPUs (e.g., CPU 416-3) and CP 443-1 communication processors can be retained if their firmware meets the minimum thresholds published in the PCS 7 Released Modules catalog. All software licenses require purchasing official PCS 7 V7.1-to-V9.0 Upgrade Packages in Automation License Manager.

Hardware Lifecycle Assessment: What to Retain vs Renovate

Upgrading an automation facility across three major generations (from PCS 7 V7.1 released in 2008 to PCS 7 V9.0 released in 2017) involves navigating substantial architectural transitions: 32-bit to 64-bit operating systems, classic drivers to the Advanced Process Library (APL), and legacy fieldbuses to PROFINET.

Engineers must distinguish between plant-floor components that can remain operational and supervisory computer hardware that must be replaced to support modern cybersecurity baselines.

Industrial PC Modernization and Operating System Migration

The table below details component disposition when upgrading from PCS 7 V7.1 to V9.0:

Hardware / Software AssetV7.1 BaselineV9.0 CompatibilityUpgrade RecommendationEngineering & Operator PCsSIMATIC IPC547D (Windows XP SP3)Obsolete / IncompatibleReplace with SIMATIC IPC547G / IPC647D running Windows 10 Enterprise LTSB or Server 2016.Central ControllerCPU 416-3 (6ES7416-3ES06)Compatible (Firmware >= V5.3)Retain: Update firmware; note that CPU 410-specific features (TCiR, PO expansion) are unavailable.Communication ProcessorCP 443-1 (6GK7443-1EX20/30)Compatible (Firmware >= V2.0)Retain: Fully supported on modern Industrial Ethernet plant bus networks.Communication CardCP 1613 (PCI)Incompatible with modern IPCsReplace with CP 1623 (PCIe x1) (6GK1162-3AA00).Software LicensesPCS 7 V7.1 Engineering & RTInvalid for V9.0Upgrade: Procure official PCS 7 Upgrade Packages via ALM.

Controller and Communication Processor Firmware Dependencies

While classic S7-400 CPUs can be retained, their onboard firmware must be verified against the official SIMATIC PCS 7 Released Modules (V9.0) catalog:

CPU 416-3: Must run at least Firmware V5.3. Older revisions (V4.x or early V5.0) must be flashed using an S7 Memory Card before loading V9.0 system blocks.
CP 443-1: Standard Industrial Ethernet processors (6GK7443-1EX20-0XE0 or 1EX30-0XE0) are fully compatible with V9.0 NetPro and Named Connections.
Architectural Limitation: Retaining a CPU 416-3 precludes utilizing Type Change in RUN (TCiR) and online Process Object expansion, which require the unified CPU 410-5H.

Procurement Schedule for PCS 7 V7.1 to V9.0 Upgrade

The following Equipment Schedule specifies the relevant order numbers for migration:

Workstation Hardware Replacement:
- SIMATIC IPC547G Rack PC (Win10 Enterprise LTSB):  6AG4104-4...-....
- SIMATIC NET CP 1623 PCIe Communications Card:     6GK1162-3AA00

Software Upgrade Packages (V7.1 to V9.0):
- PCS 7 Engineering Upgrade Package V7.1 to V9.0: 6ES7658-5AX58-0YE5
- PCS 7 OS Server Upgrade Package V7.1 to V9.0:      6ES7658-2CX58-0YE0
- PCS 7 OS Single Station Upgrade Package:          6ES7658-2AX58-0YE0
- SIMATIC NET HARDNET-IE S7-REDCONNECT Upgrade:     6GK1716-0HB00-0AE0

[!IMPORTANT]
Commercial Accuracy Disclaimer: Upgrading from PCS 7 V7.1 to V9.0 requires purchasing official upgrade license entitlements. Existing V7.1 license keys stored in Automation License Manager cannot authorize V9.0 runtimes. Sizing must be re-verified for AS and OS Process Objects. Final equipment quantities and MLFBs must be validated against the applicable Siemens ST PCS 7 Catalog and authorized distributor quotations.

Verification

To verify successful modernization to PCS 7 V9.0:

On the new IPC547G, open Automation License Manager: confirm all upgraded V9.0 licenses display status OK.
Open SIMATIC Manager and load the migrated multiproject: perform a full project consistency check (Check Consistency).
In HW Config, verify the CPU 416-3 and CP 443-1 hardware configurations compile cleanly without catalog obsolescence warnings.
Compile CFC with Generate module drivers selected: confirm that APL driver blocks compile successfully.
Download changes to the CPU: verify that the controller enters RUN mode and establishes communication with the new V9.0 WinCC OS.

Limitations and Operational Precautions

Operational boundaries when executing multi-version upgrades:

Intermediate Migration Required: A PCS 7 V7.1 project cannot be converted to V9.0 in a single step. Follow official Siemens guidelines: migrate first to PCS 7 V8.0 / V8.1, then perform the final upgrade to PCS 7 V9.0.
Classic Driver Migration: If retaining the classic Standard Library rather than converting to APL, install the PCS 7 Migration Library to ensure driver compatibility on modern 64-bit operating systems.
Backup Prior to Flashing: Always archive the original V7.1 multiproject (*.zip) and capture physical controller memory card images before initiating firmware updates.

Engineer FAQ

Can we install Windows 7 on the existing IPC547D computers?

While Siemens provided limited 32-bit Windows 7 drivers for IPC547D in earlier years, running PCS 7 V9.0 requires a 64-bit operating system and substantial RAM (minimum 16 GB). Replacing aging IPC547D units with modern IPC547G hardware is the standard engineering practice.

Does the CPU 416-3 need to be replaced by a CPU 410-5H?

No. The CPU 416-3 is fully supported in PCS 7 V9.0, provided its firmware is at least V5.3. However, upgrading to CPU 410-5H is required if you wish to use Type Change in RUN (TCiR) or PROFINET redundancy.

Can I migrate a V7.1 project directly to V9.0?

No. Siemens migration guidelines mandate a staged migration: migrate the project from V7.1 SP4 to V8.0 or V8.2 first, then perform the final migration to V9.0.