Step-by-Step Migration Strategy for Upgrading SIMATIC PCS 7 from V6.0 to V8.1

Upgrading SIMATIC PCS 7 from V6.0 to V8.1 cannot be performed in a single direct step because the underlying Microsoft SQL Server database engines and internal project structures are incompatible (WinCC V6.0 uses SQL Server 2000, whereas PCS 7 V8.1 uses SQL Server 2008 R2 SP2). The mandatory migration path requires an intermediate migration stage: first migrate the project from PCS 7 V6.0 to PCS 7 V7.1 SP4 on an intermediate migration system (converting the database to SQL Server 2005). Then migrate the project from PCS 7 V7.1 SP4 to PCS 7 V8.1 on the new Engineering Station. AS hardware components (S7-400 CPUs) can be retained provided CPU firmware and memory cards meet V8.1 compatibility requirements.

Executive Summary

Modernizing legacy automation systems represents a major milestone in industrial lifecycle management. When plant facilities operating SIMATIC PCS 7 V6.0 (originally commissioned on Windows 2000 or Windows XP) approve a system upgrade to PCS 7 V8.1 (running on Windows 7 64-bit or Windows Server 2008 R2), plant engineers frequently procure all-new industrial PC hardware for the Engineering Station (ES), OS Servers, and OS Clients while intending to retain existing S7-400 controller racks and distributed I/O. However, attempting to open a PCS 7 V6.0 backup archive directly on a fresh PCS 7 V8.1 Engineering Station fails completely or irreversibly corrupts the project database. Understanding the mandatory intermediate migration stages, SQL Server transitions, and block library modernization paths is essential for a seamless upgrade.

Why Direct Migration from PCS 7 V6.0 to V8.1 Is Prohibited

Direct migration across multiple major generations is architecturally impossible due to fundamental software shifts:

SQL Server Database Discontinuity: WinCC V6.0 stores project configuration and archives in Microsoft SQL Server 2000. PCS 7 V8.1 operates on Microsoft SQL Server 2008 R2 SP2 (64-bit). Microsoft provides no direct database conversion path from SQL Server 2000 to SQL Server 2008 R2; migration requires passing through SQL Server 2005 (used in WinCC V7.0 / PCS 7 V7.1).
OS Project Editor and Faceplate Engine: PCS 7 V6.0 relies on classic Faceplate Designer scripts, while PCS 7 V8.1 standardizes on the Advanced Process Library (APL) with APL style guides and multi-monitor client structures.
STEP 7 Database Schema: The internal relational project schema underwent structural reorganizations between V6.0 and V7.1.

Intermediate Migration Milestones and Database Evolution

The approved Siemens migration path consists of two discrete stages:

Stage 1 (V6.0 -> V7.1 SP4): The V6.0 archive is opened on an intermediate migration PC or virtual machine running Windows XP / Windows Server 2003 with PCS 7 V7.1 SP4. The project and WinCC database are converted to SQL Server 2005.
Stage 2 (V7.1 SP4 -> V8.1 SP1): The resulting V7.1 SP4 archive is transferred to the new target Windows 7 64-bit ES running PCS 7 V8.1. The WinCC Project Migrator converts the SQL Server 2005 database to SQL Server 2008 R2.

Operating System and Windows Compatibility Matrix

The following table details the operating system and SQL Server software stack across migration stages:

Migration StagePCS 7 VersionSupported Operating SystemWinCC ReleaseDatabase Engine InstalledSource LegacyPCS 7 V6.0 SP4 / V6.1Windows 2000 Pro / Windows XP SP2WinCC V6.0 SP3 / SP4Microsoft SQL Server 2000Intermediate MilestonePCS 7 V7.1 SP4Windows XP SP3 / Server 2003 SP2WinCC V7.0 SP3Microsoft SQL Server 2005Target ProductionPCS 7 V8.1 SP1Windows 7 Ultimate 64-bit / Server 2008 R2WinCC V7.3 SEMicrosoft SQL Server 2008 R2 SP2

Hardware Retention and Firmware Requirements for S7-400 AS

When retaining existing S7-400 CPUs from a PCS 7 V6.0 installation:

CPU Firmware Compatibility: Early S7-400 CPUs (e.g. 6ES7416-2XK02-0AB0 or 6ES7417-4XL00-0AB0) may not support modern PCS 7 V8.1 firmware features or advanced communication blocks. Verify the exact MLFB against the Siemens Compatibility Tool.
Memory Cards (RAM / Flash): PCS 7 V8.1 charts compile into larger MC7 block containers than V6.0; verify that existing CPU memory cards have sufficient capacity or upgrade memory cards as required.
CP 443-1 Communication Processors: Ensure Ethernet CPs support ISO-on-TCP and named connections compatible with modern SIMATIC NET V8.2 / V12.

Step-by-Step Multi-Stage Migration Procedure

Stage 1: Migrating from PCS 7 V6.0 to V7.1 SP4 (Intermediate PC)

Create a complete, uncompressed archive (.zip) of the V6.0 multiproject from the legacy ES.
Transfer the archive to an intermediate Engineering PC or VM running Windows XP SP3 and PCS 7 V7.1 SP4.
In SIMATIC Manager, select File > Retrieve... and open the project.
When prompted with the project conversion dialog, confirm conversion of the STEP 7 project to V7.1 format.
Open each WinCC OS project within SIMATIC Manager; confirm that the WinCC Project Migrator launches and converts the project database from SQL Server 2000 to SQL Server 2005.
Open OS Project Editor, run picture tree updates, and compile the OS.
Execute File > Archive... to generate a clean PCS 7 V7.1 SP4 archive.

Stage 2: Migrating from PCS 7 V7.1 SP4 to V8.1 (New Target ES)

Transfer the V7.1 SP4 archive to the new Engineering Station running Windows 7 64-bit and PCS 7 V8.1 SP1.
Retrieve the project in SIMATIC Manager.
Allow SIMATIC Manager to upgrade the database schema to V8.1.
Open the OS projects; the WinCC V7.3 Project Migrator converts the database from SQL Server 2005 to SQL Server 2008 R2 SP2.
In CFC, execute Options > Block Types > New Version to update system driver blocks to V8.1.
Run the OS Project Editor with the modern screen resolution layout.
Execute a complete compilation of CFC charts and OS projects (Compile Entire Program / Tags and messages).

Verification

To verify successful multi-stage migration:

Compilation Cleanliness: Compile all CFC charts and OS projects. Confirm that compilation completes with 0 errors.
WinCC Runtime Activation: Activate WinCC Runtime on the new ES/OS. Confirm that graphic screens, alarm logging, and trend archives operate cleanly.
Controller Communication: Connect the new ES to the plant industrial Ethernet terminal bus. Test communication with the retained S7-400 CPUs in online test mode.

Limitations and Operational Precautions

Never Uninstall Software on Active Production ES: Do not attempt to install, remove, and reinstall intermediate PCS 7 versions on a single operating production computer; use dedicated migration virtual machines.
Library Considerations: Migrating from the classic PCS 7 Standard Library to the Advanced Process Library (APL) is an engineering redesign, not an automated one-click conversion. Standard library blocks can continue to run in PCS 7 V8.1 using legacy block icons.
Procurement Disclaimer: Always validate final license upgrade quantities, MLFBs, and hardware compatibility against the applicable Siemens catalog and an authorized Siemens distributor quotation.

Engineer FAQ

Can I use Windows 10 for the intermediate migration step?

No. PCS 7 V7.1 SP4 is strictly incompatible with Windows 10; the intermediate step must run on Windows XP or Server 2003.

Do I have to re-draw all graphic screens during migration?

No. The WinCC Project Migrator retains all existing PDL graphic pictures, C-actions, and VBS scripts without requiring re-drawing.

Can I migrate directly from PCS 7 V6.1 to V8.1 without V7.1?

No. The database leap from SQL Server 2000 to SQL Server 2008 R2 requires the SQL Server 2005 migration step present in V7.1.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=migration
https://industrialautomation.net/search?query=wincc
https://industrialautomation.net/search?query=upgrade

6 respuestas

Step-by-Step Migration Strategy for Upgrading SIMATIC PCS 7 from V6.0 to V8.1