Chronological Installation and Software Upgrade Order from PCS 7 V7.1 SP4 to V8.2

To execute a software upgrade from SIMATIC PCS 7 V7.1 SP4 to PCS 7 V8.2 SP1, you must follow a disciplined, chronological installation and data transformation sequence. Upgrading cannot be accomplished by installing V8.2 directly over an existing V7.1 operating system due to fundamental 32-bit (Windows XP) versus 64-bit (Windows 7 SP1) architectural boundaries. The verified engineering sequence requires capturing a clean, reorganized baseline archive in V7.1 SP4, deploying a dedicated 64-bit staging environment with PCS 7 V8.2 SP1, running the WinCC Project Migrator to convert SQL Server 2005 databases to SQL Server 2014, upgrading internal CFC/SFC data structures, and recompiling both AS and OS projects.

Environmental Prerequisites: Establishing the V8.2 Staging Platform

Attempting to perform an in-place software upgrade on existing V7.1 engineering computers is prohibited:
- Operating System Boundary: PCS 7 V7.1 SP4 runs on 32-bit Windows XP Professional. PCS 7 V8.2 SP1 requires 64-bit Windows 7 Enterprise/Ultimate SP1 or Windows Server 2008 R2 SP1.
- The Staging Machine: Deploy a dedicated physical PC or virtual machine (VMware Workstation/ESXi) configured with:
- 64-bit Windows 7 SP1.
- Minimum 16 GB RAM and 200 GB solid-state disk space.
- Clean installation of SIMATIC PCS 7 V8.2 SP1.
- Automation License Manager (ALM) with PCS 7 V8.2 engineering licenses.

Step-by-Step Chronological Upgrade Sequence

Follow this strict chronological order across the source and staging environments:

[Step 1: V7.1 SP4 System] ──► Reorganize Databases ──► Archive Multiproject
                                                             │
[Step 2: Transfer Archive] ──────────────────────────────────┘
                                                             │
[Step 3: V8.2 Staging VM] ──► Restore Archive ──► Upgrade STEP 7 Schema
                                                             │
[Step 4: WinCC Migrator]  ──► Convert SQL 2005 to SQL 2014
                                                             │
[Step 5: CFC & SFC Modern] ─► Update Block Types ──► Compile AS Entire Scope
                                                             │
[Step 6: OS Project Edit] ──► Refresh System PDLs ──► Compile OS Entire Scope

WinCC Database Conversion and OS Project Editor Execution

Converting the operator station database is the most critical phase of the upgrade:

Step 1: Execute WinCC Project Migrator

In SIMATIC Manager on the V8.2 staging machine, navigate to the WinCC OS Server project.
Right-click the OS project and select Open Object:
- SIMATIC Manager automatically launches the WinCC Project Migrator.
- The Migrator inspects database tables, converts Sybase/SQL Server 2005 structures, creates modern Microsoft SQL Server 2014 tables, and modernizes user archives.
Review Migration.log upon completion to verify zero fatal conversion errors.

Step 2: Run the OS Project Editor in WinCC Explorer

Once migration finishes, WinCC Explorer opens.
In the WinCC project navigation tree, double-click OS Project Editor.
Select the Basic Data tab:
- Ensure the option Replace all standard picture files with new ones is enabled.
- This replaces legacy V7.1 system graphics (@Faceplate.pdl, @pg_*.pdl, @screen.pdl) with modernized V8.2 APL-compatible templates.
Click OK to execute the generator.

CFC Block Type Updating and AS Compilation Verification

After the OS layer is upgraded, modernize the automation controller software:

Step 1: Upgrade CFC/SFC Internal Data Structures

In SIMATIC Manager, open any CFC chart.
A prompt confirms: The chart contains objects from an older version. Do you want to convert the chart?
Click Yes. The CFC editor converts the internal binary schema to CFC V8.2 format.
Repeat for Sequential Function Charts (SFC).

Step 2: Update Block Types in the Master Data Library

Open the project's Master Data Library (MDL).
Copy the latest library blocks (APL V8.2 or updated Standard Library blocks) into the MDL block folder.
In SIMATIC Manager, select Options -> 'Charts' -> Update Block Types....
Select all participating AS projects: the wizard compares block interfaces, updates instance data blocks, and synchronizes all CFC charts.

Step 3: Execute Full Compilations

Select the Chart folder: run Chart -> Compile -> Charts as Program:
- Select Entire Scope.
- Ensure Generate module drivers is checked.
In SIMATIC Manager, select the OS project and execute Compile OS:
- Select Entire Scope for tags and messages.
- Confirm compilation finishes with 0 Errors.

Verification

To verify that the project is completely and successfully upgraded to V8.2 SP1:
- Open SIMATIC Manager: confirm that all AS controller projects, charts, and OS stations display without padlock icons or version mismatch warnings.
- Open Options -> Reference Data -> Block Types: verify that all technological blocks are fully synchronized with the V8.2 Master Data Library.
- In WinCC Explorer, activate Runtime: confirm that the alarm banner, picture tree navigator, and faceplates load cleanly with dynamic process communication.
- Save the upgraded project using File -> Save As... With Reorganization (Slow) and create a certified V8.2 project archive.

Limitations and Operational Precautions

Do Not Attempt Online Change Download to AS: The transition from V7.1 SP4 to V8.2 SP1 modifies core system driver blocks, runtime group headers, and memory descriptors. Downloading the upgraded program to the physical CPU requires a full download (Entire Scope) in CPU STOP mode.
Preserve V7.1 Backups: Maintain permanent read-only archives of the original V7.1 SP4 project. Never overwrite original backups with intermediate migration files.
Active Batch Precautions: In installations running SIMATIC BATCH, complete and archive all active production batches in V7.1 before taking the final engineering backup.

Engineer FAQ

Can I upgrade directly from V7.1 SP4 to V8.2 without installing intermediate hotfixes?

Yes. V7.1 SP4 is the fully consolidated, certified baseline for direct migration into PCS 7 V8.2 SP1. No secondary hotfixes are required before starting the V8.2 migrator.

What should I do if the WinCC Project Migrator halts on an encrypted script?

If third-party or custom C-scripts were password-protected in V7.1, the migrator may halt. Temporarily remove script encryption in the V7.1 environment before archiving, or recompile the script manually in V8.2 Graphics Designer.

Does the V8.2 upgrade require purchasing new hardware immediately?

Not necessarily. While final operational deployments eventually require modern IPCs, the entire software conversion sequence can be executed and validated offline inside virtual machines without purchasing field hardware.

Why is running the OS Project Editor mandatory after migration?

The WinCC Migrator only converts database tables; it does not replace graphical picture files. Running the OS Project Editor extracts the authentic, version-matched standard faceplates and navigation scripts required for runtime stability.

Technical References

Siemens Industry Online Support: SIMATIC PCS 7 Software Update with Migration from V7.1 to V8.2 (Official Manual).
SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Software Update Sequences).
SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules and Operating Systems.
Siemens Support Guide: Best Practices for WinCC Database Migration to SQL Server 2014.