PCS7 V7.0 to V8.1 Migration on IPC827D: Preserving HMI Faceplates and STAHL Third-Party Integration

This reference documents the engineering work required to lift a PCS7 V7.0 / Windows XP OS station onto a Simatic IPC827D running Windows 7 with PCS7 V8.1, while preserving existing WinCC faceplates and a STAHL third-party HMI that depends on a dedicated Non-Simatic OS station. It captures the migration path, the OS-specific adjustments, the SQL Server transition, the faceplate rendering rules, and the verification gates an automation engineer must clear before authorizing production cut-over.

1. Scope and Engineering Problem

The legacy system consists of:

• Operator Station (OS) running Windows XP with PCS7 V7.0 (the WinCC Runtime / Configuration inside the PCS7 suite, not TIA Portal WinCC).
• Simatic IPC627B used as an OPC bridge between the DCS and the third-party HMI.
• STAHL-brand HMI front-end connected to a dedicated Non-Simatic OS station with WinCC installed, communicating via OPC to the IPC627B.
• Existing WinCC faceplates compiled against the V7.0 graphics library (APL not used).

The replacement hardware is a Simatic IPC827D with Windows 7 64-bit. The question is whether the existing faceplates and the STAHL OPC connection survive the upgrade without rebuilding graphics.

2. Migration Path and Software Stack Matrix

The complete staged upgrade sequence is defined below. Each step is a separate engineering action with its own backup and rollback gate.

Mapping each stage to the manufacturer documentation ensures the binaries, scripts, and automation license manager (ALM) keys line up. The V8.0 stage is mandatory even when the target is V8.1 because PCS7 V8.1 setup expects a V8.0 base install for upgrade mode.

3. Hardware Replacement: IPC627B to IPC827D

The Simatic IPC627B is a 15-inch panel-mount PC (Convergent Platform) designed for cabinet integration. The Simatic IPC827D is a rack-mount Box PC of the same industrial class. Both support 24 VDC and ship with identical Siemens diagnostic and SIMATIC IPC DiagMonitor concepts.

The OPC server role transfers unchanged. The OPC DA 2.0 / 3.0 interface is part of the WinCC V7.x installation and does not depend on the hardware platform. Re-install the SIMATIC NET OPC components after the PCS8.1 install completes and re-import the station configuration with Station Configurator.

4. HMI Faceplate Compatibility Across PCS7 Versions

WinCC faceplates (Dynamik-Dialoge in PDL / graphic files inside the WinCC project) are stored in the project database, not in a system-wide library. When a project is opened in a newer PCS7 version, the WinCC Explorer triggers a project converter that rewrites PDL metadata and faceplate internal references to match the destination library version.

4.1 Faceplate Behavior by Version

• V7.0 → V7.1 SP4: Faceplates migrate transparently because both versions share the same PDL compilation model and the same variable interface contract. No manual rebuild required.
• V7.1 SP4 → V8.0: WinCC graphics engine changes the script-host integration. Faceplate-internal VBS scripts continue to run, but any custom OCX controls compiled against the V7.1 COM type library must be re-registered on the V8.0 station.
• V8.0 → V8.1: Faceplate graphic blocks (the F-type blocks in the PCS7 Advanced Process Library / standard library) re-link to the V8.1 library automatically on first compile. If the source project was built without APL, the conversion keeps the legacy faceplate header references intact.

4.2 The APL Question

APL (Advanced Process Library) blocks did not exist in PCS7 V7.0. They were introduced in V7.1 SP1 as an optional replacement for the legacy standard library. If the source V7.0 project uses the standard library only, the faceplates will compile in V8.1 without manual changes. If the engineer chooses to switch to APL during the migration, every faceplate instance and every icon must be re-linked because the block names (e.g., MOT_SPEED vs CTRL_PID) and the faceplate script attribute addresses differ.

Recommendation: if the goal is minimum downtime, keep the standard library throughout the chain. APL can be adopted in a later project, isolated from the production cut-over.

4.3 Non-Simatic OS Station Specifics

The STAHL HMI uses a dedicated Non-Simatic OS station — that is, a WinCC V7.x runtime install without the full PCS7 OS add-on. This installation type preserves faceplate compatibility because the runtime graphics engine and the script host are identical between a PCS7 OS and a Non-Simatic OS install at the same WinCC minor version. The Non-Simatic OS does not carry the PCS7 OS user administration or the WinCC Redundancy add-on; only the basic WinCC Runtime, WinCC Explorer, and the OPC interface.

Procedure to lift the Non-Simatic OS station:

1. Back up the project database (WinCC project path) including all PDL, scripts, and the WinCCExplorer.cfg.
2. Capture the WinCC project version via the project's Version.txt or the project menu in WinCC Explorer.
3. Install WinCC V7.4 SP1 on Windows 7 SP1 (matches PCS7 V8.1).
4. Restore the project database under a temporary name to test compile before touching production.
5. Open the restored project. The converter prompts: Do you want to convert? Accept. The compiler rebuilds PDLs and faceplates in the new internal format.
6. Recompile the OS. Re-activate. Run a 30-minute visual sweep to confirm every faceplate opens, every script fires, and every variable resolves.

5. OPC and STAHL HMI Re-connection

The STAHL HMI does not read faceplate internals; it reads OPC tags from the IPC827D bridge. During the migration, the OPC topic and tag mapping must round-trip exactly.

5.1 DCOM and OPC Security Hardening

Windows 7 enforces tighter DCOM defaults than Windows XP. The OPC DA server will not be reachable until the following registry changes are applied to the IPC827D:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\MachineAccessRestriction = 0 for the engineering test phase, then locked to the OPC user account after commissioning.
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\MachineLaunchRestriction = 0 during commissioning.
• Firewall inbound rule for the OpcEnum service and OPC.SimaticNET.DA on TCP port 135 plus the dynamically assigned range.
• COM security: Launch and Activation Permissions allow the STAHL OPC DA client account (typically STAHL_USER or a domain service account).

6. SQL Server Transition: 2005 → 2008 R2

PCS7 V7.0 uses MS SQL Server 2005. PCS7 V8.1 uses SQL Server 2008 R2 SP3. WinCC Runtime archives, user archives, and tag logging live in SQL databases. The PCS7 setup routine handles the migration of WinCC project archives when the project is opened in the new version, but the system databases must be restored manually.

6.1 Migration Procedure

1. On the source IPC627B, run SQL Server Management Studio 2005 and back up every WinCC database (default names: CC_OS_1_<date>, CC_UA_..., plus system DBs master, msdb, model).
2. Copy the .bak files to the IPC827D.
3. Install SQL Server 2008 R2 SP3 with the same instance name and collation as the source. Default collation for WinCC is SQL_Latin1_General_CP1_CI_AS.
4. Restore the WinCC databases with RESTORE DATABASE ... WITH RECOVERY.
5. Re-link the WinCC project to the restored archive database via WinCC Explorer → Tag Logging → Archive Configuration → Select Database.

Verify the archive data with the WinCC Trend Control on a test picture. If curves do not load, the archive path or the Config.xml for the archive is still pointing to the old instance — repoint and reload.

7. OS-Specific Adjustments for Windows 7

Windows 7 introduces User Account Control (UAC), a new firewall stack, and 64-bit path handling. The PCS7 V8.1 installation routine accounts for UAC during setup, but the WinCC Runtime services need explicit service account configuration post-install.

Disable UAC for the runtime user only (not globally) by setting the registry value HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA = 1 and adding the runtime user to the local Administrators group with UAC exception via Group Policy. Without this, WinCC Runtime will not write to C:\Program Files (x86)\Siemens\Automation\WinCC\WinCCProjects under a non-elevated login.

8. Faceplate Conversion Failure Modes and Field Diagnostics

When a faceplate fails to open or displays a greyed-out icon after migration, the root cause is almost always one of the patterns below. Use this matrix as a fast field triage.

8.1 DiagMonitor Integration

Both the IPC627B and the IPC827D ship with SIMATIC IPC DiagMonitor for hardware health monitoring. After the migration, verify the DiagMonitor service status and confirm that the watchdog is configured to restart the WinCC Runtime service within 60 seconds on a soft fault. This is critical because the STAHL HMI loses OPC tags if the WinCC Runtime stops without restart.

9. Step-by-Step Cut-Over Procedure

1. Pre-cut-over (T-30 days): Engineer the migration on a lab IPC827D identical to production. Restore the latest project backup from the IPC627B. Walk the project through V7.1 SP4 → V8.0 → V8.1. Document every faceplate that does not auto-convert.
2. Pre-cut-over (T-7 days): Hand the converted project to the customer process team for user acceptance testing. Record sign-off.
3. Pre-cut-over (T-1 day): Stop the production OS station. Back up the entire project, OPC configuration, and SQL archives to two independent storage locations (one on-site, one off-site).
4. Cut-over (T-0): Power down IPC627B. Install Windows 7 SP1 on IPC827D from the manufacturer recovery media. Apply the latest BIOS, chipset, and NIC drivers.
5. Cut-over: Install PCS7 V8.1, then WinCC Runtime, then SIMATIC NET V8.1, then SQL Server 2008 R2 SP3. Restore SQL archives.
6. Cut-over: Restore the converted WinCC project. Re-import the OPC station configuration. Re-register the STAHL OPC DA client DCOM identity.
7. Cut-over: Recompile the OS. Start the runtime in test mode. Validate faceplates, trends, alarms, and the STAHL OPC tag subscription.
8. Cut-over: Promote the runtime to production. Start the process. Run a four-hour supervised watch.
9. Post-cut-over (T+7 days): Decommission the IPC627B. Archive its drives. Update the plant asset register.

10. Verification Checklist

Use this list before clearing the OS station for production:

• [ ] All faceplates open from the overview screen without "Invalid pointer" or "No connection" banners.
• [ ] At least one operator action per faceplate type executes (acknowledge alarm, change setpoint, start motor, open valve).
• [ ] WinCC Tag Logging shows historical curves across the cut-over boundary.
• [ ] WinCC Alarm Control shows live and historical alarms.
• [ ] STAHL HMI shows live OPC tags from the IPC827D. Tag latency is below 1 s.
• [ ] OPC DA server status reports "Running" in the OPC Scout V8.1.
• [ ] DiagMonitor reports CPU, RAM, disk, and temperature all in the green band.
• [ ] Service accounts for CCAgent, CCEServer, and WinCC Runtime are set to LocalSystem with desktop interaction allowed.
• [ ] DCOM identity and access permissions set with a dedicated service account — no Everyone.
• [ ] WinCC project license dongle (ALM) recognized on the IPC827D.
• [ ] Backup script for the WinCC project runs clean and produces a .zip with project DB, PDLs, and scripts.

11. Documentation and Standards Reference

The engineer carrying out this migration must hold current copies of the Siemens manuals listed below. Verify against the version you are actually installing — Siemens revises the manuals when a service pack ships.

• Siemens Support: Basics on HMI Faceplates (PDF) — covers the faceplate attribute model, VBS script binding, and the converter behavior when migrating between WinCC major versions.
• Siemens DocV001: WinCC Unified Migration Guide, Section 3.4.5 — Faceplates — describes the manual modernization path, layout restoration (move 10 px left/up, reduce height/width to recover original layout), and object-level faceplate redesign.

For DCS-specific migration manuals, always pull from the Siemens Industry Online Support portal under entry ID 68014632 and the related "PCS7 Software Update" manuals — never rely on memory or third-party summaries.

12. Frequently Asked Questions