Applying the PCS 7 V9.1 SP1 Software Update Manual to V9.1 SP2 Migrations

The official Siemens SIMATIC PCS 7 V9.1 SP1 software update manual can be applied directly to PCS 7 V9.1 SP2 migrations without alteration. Both service packs share identical underlying database formats, identical Windows operating system platforms (Windows 10 Enterprise LTSC 2019/2021 and Server 2019/2022), and identical migration stepping stones from legacy releases such as V7.1 SP4. Upgrading to V9.1 SP2 is the manufacturer-recommended target because it incorporates all cumulative security updates, bug fixes, and compatibility enhancements released since SP1.

Technical Equivalence of V9.1 SP1 and SP2 Migration Procedures

Engineers updating legacy plants often find that published Siemens documentation specifically references PCS 7 V9.1 SP1 as the target release when PCS 7 V9.1 SP2 is already commercially available.

The migration instructions remain 100% applicable for the following reasons:
* Identical Architectural Framework: PCS 7 V9.1 SP2 is a maintenance and service update built on the V9.1 core engine. It introduces no breaking schema changes to CFC, SFC, or WinCC SQL database structures compared to SP1.
* Identical Migration Prerequisite: Both SP1 and SP2 require legacy projects to reach V7.1 SP4 (or V8.0 SP2 / V8.2) before executing direct project conversion.
* Operating System Support: Both service packs support identical target operating systems:
* Windows 10 Enterprise LTSC 2019 and 2021 (64-bit).
* Windows Server 2019 and 2022 (64-bit).
* Library Support: Both releases provide simultaneous support for the legacy PCS 7 Standard Library (for unmigrated blocks) and the modern Advanced Process Library (APL V9.1).

Applying the SP1 guide while installing SP2 software provides the exact same procedural steps while delivering improved runtime stability and security compliance.

Step-by-Step Migration Verification Workflow

Follow this workflow when executing a migration from V7.1 SP4 to V9.1 SP2 using the SP1 documentation.

Prerequisites

Verified project archive from PCS 7 V7.1 SP4.
Target PC prepared with fresh Windows 10 LTSC installation and PCS 7 V9.1 SP2 media.
Official manual: SIMATIC Process Control System PCS 7 Software update with/without utilization of new functions.

Step 1: Execute Project Migration According to Manual

Follow the manual's checklist for retrieving the project archive onto the V9.1 SP2 Engineering Station.
Allow SIMATIC Manager to execute automated internal project structure conversion.
Open WinCC Explorer to trigger the WinCC Project Migrator. Verify that all server and client databases convert cleanly to SQL Server 2017.

Step 2: Update Master Data Library and Block Catalogs

Open the project Master Data Library in SIMATIC Manager.
Select Options -> Block Types.
If continuing with legacy standard blocks, ensure the PCS 7 Standard Library V7.1/V8.2/V9.1 compatibility package is installed.
Execute block version checks and update instance blocks across all CFC charts.

Step 3: Run OS Project Editor

In WinCC Explorer, open the OS Project Editor.
Select the screen resolution matching your control room displays.
Click OK to regenerate standard picture layouts (@Overview1.pdl, @Screen.pdl, @Buttons.pdl) to the V9.1 SP2 standard.

Step 4: Full Compilation and Testing

Compile all automation stations: Chart -> Compile -> Entire Program.
Compile WinCC OS: Right-click OS -> Compile -> Entire OS.
Validate that both compilers finish with 0 critical errors.

Verification

In SIMATIC Manager, check Help -> About to confirm that PCS 7 displays version V9.1 SP2.
Open CFC and verify that chart interconnections, block icons, and runtime group sequences are preserved without corruption.
Launch WinCC Runtime on the OS Server or simulation client; verify that process graphics, faceplates, and alarm journals render dynamically.
Check the WinCC Project Migrator log file (Migration.log in the project directory) to ensure all SQL table updates completed with status Success.

Limitations and Operational Precautions

Avoid Base V9.1 (No Service Pack): Never deliberately install base V9.1 without service packs simply to avoid downloading updates; base V9.1 contains early release defects resolved in SP1 and SP2.
Firmware Dependencies: If updating S7-400 or S7-410 controllers to newer firmware levels released with SP2, verify hardware compatibility and execute firmware updates before downloading project changes.
Update Collections (UC): After installing V9.1 SP2, always check the Siemens Industry Online Support portal for the latest Update Collection (e.g., V9.1 SP2 UC1 or UC2) to apply post-release security patches.

Engineer FAQ

Can I migrate directly from V7.1 base to V9.1 SP2?
No. You must upgrade to V7.1 SP4 first. Migrating directly from unpatched V7.1 base causes SQL database migrator failure.
Does V9.1 SP2 require different licenses than V9.1 SP1?
No. PCS 7 V9.1 software licenses are version-wide; a PCS 7 V9.0/V9.1 license authorizes V9.1 base, V9.1 SP1, and V9.1 SP2.
Are my custom SCL blocks compatible with V9.1 SP2?
Yes, provided they are recompiled using the S7-SCL compiler included in V9.1 SP2 to generate updated internal block headers.
Will legacy WinCC graphic scripts (C-scripts and VBS) work in V9.1 SP2?
Standard WinCC C and VBS scripts migrate cleanly, but any script utilizing hardcoded 32-bit Windows API calls or obsolete OLE controls must be adapted for 64-bit compatibility.
What is the difference between update 'with' and 'without' utilization of new functions?
Updating 'without utilization of new functions' minimizes engineering effort by preserving legacy blocks and faceplates. Updating 'with utilization' replaces old blocks with APL blocks to utilize modern features.

Technical References

Siemens Industry Online Support Entry ID 109801081: SIMATIC PCS 7 Software Update Manual (V7.1 SP4 to V9.1 SPx).
Siemens Delivery Release: SIMATIC PCS 7 V9.1 SP2.
Siemens Compatibility Tool: Operating Systems and Software Dependencies for PCS 7 V9.1 SP2.