C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Engineering Workflow for Migrating SIMATIC PCS 7 from V6.x to V7.1 on Intermediate Systems

Engineering Workflow for Migrating SIMATIC PCS 7 from V6.x to V7.1 on Intermediate Systems

When modernizing legacy plants from SIMATIC PCS 7 V6.x to V7.1 (as an intermediate milestone toward V8.x or V9.x) while retaining existing S7-400 AS hardware, migration must be executed on an intermediate Engineering Station running Windows XP Professional SP3 or Windows Server 2003. Retrieve the V6.x backup in PCS 7 V7.1 SIMATIC Manager to convert the project database. Open each WinCC project to allow the WinCC Project Migrator to convert the database from Microsoft SQL Server 2000 to SQL Server 2005. Then update the Master Data Library, execute Options > Block Types to update driver blocks, run the OS Project Editor, and compile all charts and OS stations.

Table of Contents

Executive Summary

Industrial lifecycle strategies frequently dictate upgrading multi-decade legacy automation infrastructure in phased, risk-mitigated stages. When migrating from SIMATIC PCS 7 V6.0 or V6.1 to modern releases (such as PCS 7 V8.1 or V9.1), engineers quickly discover that direct migration is unsupported by Siemens toolchains. PCS 7 V7.1 SP4 represents the mandatory architectural bridge between legacy Sybase/SQL Server 2000 systems and modern 64-bit SQL Server platforms. By performing the first stage of migration on an intermediate PCS 7 V7.1 engineering environment, automation teams successfully convert project schemas, update block libraries, and validate OS graphics before progressing to newer Windows operating systems. This guide details the required engineering workflow.

The Role of PCS 7 V7.1 as an Intermediate Migration Milestone

PCS 7 V7.1 SP4 occupies a unique position in Siemens automation history:

  • Dual Library Support: Natively supports both the legacy PCS 7 Standard Library (classic MOTOR, VALVE) and the modern Advanced Process Library (APL).
  • Database Bridge: Contains the migration scripts capable of ingesting Microsoft SQL Server 2000 database archives and upgrading them to Microsoft SQL Server 2005 format.
  • Project Converter: Transforms STEP 7 V5.3 / V5.4 internal database pointer structures into the unified STEP 7 V5.5 schema.

Database Shift: SQL Server 2000 to SQL Server 2005

WinCC OS projects store plant tags, graphic dynamics, and historical archives in relational SQL databases:

  • In PCS 7 V6.x, WinCC V6.0/V6.2 utilizes Microsoft SQL Server 2000 (32-bit).
  • In PCS 7 V7.1, WinCC V7.0 utilizes Microsoft SQL Server 2005 SP3/SP4.
  • Modern SQL Server releases (SQL Server 2008 R2 / 2014 / 2016 in PCS 7 V8/V9) cannot attach or convert SQL Server 2000 files; the project must be opened and saved inside WinCC V7.0 (PCS 7 V7.1) to elevate the schema version.

Operating System and Compatibility Prerequisites

The intermediate migration system must be carefully provisioned:

  • Operating System: Windows XP Professional SP3 (32-bit) or Windows Server 2003 Standard SP2.
  • Installed Software: SIMATIC PCS 7 V7.1 SP4 complete engineering package.
  • Virtualization: A dedicated virtual machine (VMware Workstation or ESXi) running Windows XP SP3 provides an ideal isolated sandbox for executing intermediate migrations without altering physical hardware.

PCS 7 Version Upgrade Milestone Matrix

The following table details the technical parameters across the migration progression:

Engineering PhasePCS 7 VersionOperating SystemWinCC VersionSQL Server VersionTarget ActionSource StatePCS 7 V6.0 / V6.1Windows 2000 / XP SP2WinCC V6.0 / V6.2SQL Server 2000Create full multiproject .zip backup.Intermediate MilestonePCS 7 V7.1 SP4Windows XP SP3WinCC V7.0 SP3SQL Server 2005Upgrade database schema, OS Project Editor.Target State 1PCS 7 V8.1 SP1Windows 7 64-bitWinCC V7.3 SESQL Server 2008 R2Migrate to modern 64-bit platform.Target State 2PCS 7 V9.1 SP2Windows 10 / Server 2019WinCC V7.5 SP2SQL Server 2017Final contemporary production release.

Step-by-Step Procedure to Migrate from V6.x to V7.1

Method: Executing Migration on Intermediate Environment

  1. On the legacy V6.x Engineering Station, perform Chart > Read Back in CFC to capture all runtime setpoints into the project.
  2. Create an uncompressed archive of the multiproject using File > Archive... in SIMATIC Manager.
  3. Transfer the .zip archive to the intermediate migration PC running Windows XP SP3 and PCS 7 V7.1 SP4.
  4. Open SIMATIC Manager and select File > Retrieve... to unpack the project.
  5. When opening the project, confirm the prompt to convert the STEP 7 project database to V7.1.
  6. Open the Component View, expand each OS station, right-click the OS project, and select Open Object.
  7. The WinCC Project Migrator launches automatically; allow it to convert SQL Server 2000 tables to SQL Server 2005.
  8. In WinCC Explorer, open the OS Project Editor and click OK to update standard system pictures (@Screen.pdl, @Overview.pdl).
  9. In SIMATIC Manager, update the Master Data Library (MDL) block types.
  10. In CFC, select Options > Block Types, select system driver blocks, and click New Version.
  11. Execute a complete compilation of CFC charts and OS projects (Compile Entire Program).
  12. Archive the verified project as the pristine PCS 7 V7.1 SP4 milestone.

Verification

To verify successful migration to PCS 7 V7.1:

  1. Compilation Log Review: Review the CFC and OS compilation logs. Confirm that compilation completes with 0 errors.
  2. WinCC Runtime Activation: Start WinCC Runtime on the intermediate station. Confirm that process graphic screens open without script errors.
  3. Milestone Archiving: Generate a timestamped backup of the converted V7.1 project, ready for ingestion by PCS 7 V8.1.

Limitations and Operational Precautions

  • Do Not Skip Intermediate Stages: Attempting to jump directly from V6.x to V8.x causes irreversible corruption of WinCC SQL databases.
  • AS Hardware Firmware Checks: Verify that existing S7-400 CPUs have firmware compatible with PCS 7 V7.1 (e.g. V3.1 or higher).
  • License Procurement: Ensure proper upgrade licenses are procured; always validate upgrade paths and order numbers (MLFBs) with an authorized Siemens distributor quotation.

Engineer FAQ

Can I migrate from PCS 7 V6.0 directly to V7.1 without installing Service Pack 4?

While baseline V7.0 or V7.1 can migrate V6.0, PCS 7 V7.1 SP4 is strongly recommended because it contains the most stable migration tools.

Do I need to rewire CFC charts when migrating from V6.x to V7.1?

No. Graphic chart topology, interconnections, and block parameters are fully preserved during STEP 7 project conversion.

Are custom C-scripts in WinCC graphics preserved during migration?

Yes, user-authored C-actions and VBS scripts are retained; however, obsolete API calls should be reviewed against WinCC V7.0 syntax.

Technical References

Related Articles

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