Overview
Siemens PCS 7 installations commissioned on V7.1 (released 2009) have now reached a decision point. Active Siemens support is bounded to the current release plus the immediately previous release. Once V9.1 ships, V8.2 leaves the free-of-charge support window and V9.0 becomes the only fully-supported predecessor. This means an operator running V7.1 in 2024 must plan either an aggressive double-step (V7.1 → V8.x → V9.x) or a direct upgrade to V9.x, each with distinct license, hardware, and PROFIBUS-to-PROFINET migration consequences.
This reference consolidates the engineering decisions required for a brownfield PCS 7 V7.1 → V9.0 migration: IPC selection (IPC547E, IPC547G, IPC647D), AS 400/AS 410 controller compatibility, PROFINET enablement, license upgrade economics, and the V8.2 feature floor required before V9.0 can be installed.
Why V9.0 Is the Correct Target, Not V8.2
PCS 7 V8.2 introduced the bulk of the modern engineering toolset: Tag Browser, Logic Matrix, SFC Calculation, enhanced SIMATIC PDM integration, and the CFC/SFC multi-user engineering extensions that underpin redundant engineering workflows. Skipping V8.2 and going V7.1 → V9.0 is technically possible, but the upgrade path that Siemens licenses and tests is sequential: V7.1 → V8.0/V8.1 → V8.2 → V9.0.
V9.0 layers on top of V8.2:
- Native PROFINET support in the AS (S7-410E required for PROFINET IO with IRT).
- New SIMATIC PCS 7 NEO architecture (V9.1 expands this; V9.0 lays the foundation).
- Updated WebUX with HTML5 graphics, deprecating legacy WinCC Web Navigator ActiveX clients.
- Windows 10 IoT Enterprise LTSC 2019 as the only supported OS, removing the WinCC 7.0 / Win Server 2008 R2 stack that V7.1 installations frequently still carry.
- Newer CPU generations validated against the SIMATIC IPC547G and IPC647D.
Siemens Support Lifecycle and the V8.2 Cliff
Siemens Industry Online Support grants free basic support (entry-level firmware patches, KB article access, hotline time) only to the current release (N) and the predecessor (N-1). Premium / standard support contracts are sold separately and continue to honor N-2 for a transitional period, but security patches and functional corrections cease to ship for older branches.
| Installed PCS 7 Version | Status after V9.1 release | Free Support | Action |
|---|---|---|---|
| V9.1 (current) | N | Full | Maintain |
| V9.0 (N-1) | Supported predecessor | Full (until V10.0) | Recommended landing target |
| V8.2 | Outside free support window | Pay-per-incident only | Avoid as long-term landing |
| V7.1 / V7.1 SP3 | Out of support | None | Immediate migration required |
The economic conclusion is to stop on V9.0 if the budget cannot absorb a license-jump to V9.1 immediately, but to plan V8.2 strictly as a transitional node on the upgrade path, not the final state.
Hardware: IPC547E vs IPC547G vs IPC647D
The original V7.1 OS stations typically run on the SIMATIC IPC547C (Core 2 era) or IPC547D (first-generation Core i). These are long out of support. The candidates in 2018-2020 specification work were:
| IPC Model | Order Number (configurable) | Status | OS Station Role | PCS 7 Compatibility |
|---|---|---|---|---|
| IPC547E (Core i5/i7 4th gen) | 6AG4112-2... | Discontinued 2018-03-06 | Single-station OS / Server | V8.2 / V9.0 supported, no V9.1 certification on latest SP |
| IPC547G (Core i5/i7 8th/9th gen) | 6AG4112-3... | Current | OS Server, Engineering, Single-station | V9.0 SP2 and above certified |
| IPC647D (Core i5/i7 6th gen, 19" rack) | 6AG4114-3... | Current (at time of V8.2/V9.0 evaluation) | OS Server (1U/2U), redundant pair | V8.2 SP1 / V9.0 certified |
| IPC847D / IPC847E | 6AG4125-... | Current | OS Server (high-availability pairs), Batch server | V9.0 certified |
The 2018-03-06 discontinuation of the IPC547E made it non-procurable as a new unit. A brownfield migration that proceeds in 2018-2019 must therefore buy IPC547G or IPC647D; remaining IPC547E stock on the second-hand market is unsupported and cannot host V9.1 when it lands.
License Upgrade Economics: Sequential vs Direct Jump
Siemens license pricing treats version jumps non-linearly. The standard PowerPlus upgrade licenses and the PCS 7 PowerPack contracts are structured to make the V7.1 → V8.2 step cheaper than a single V7.1 → V9.0 step, and a V8.2 → V9.0 step cheaper again. The cheapest path from V7.1 to V9.0 is therefore the two-step route.
| Path | License Steps | Approximate Cost Factor | Engineering Effort |
|---|---|---|---|
| Direct V7.1 → V9.0 | One PowerPack, V9.0 key on existing V7.1 | 1.6× (single but expensive step) | One pass of CFC/SFC mass migration; risk of skipped compatibility |
| V7.1 → V8.2 → V9.0 | V7.1→V8.2 PowerPack, then V8.2→V9.0 PowerPack | 1.0× baseline (cheaper combined) | Two passes; each pass smaller and better validated |
| V7.1 → V8.0 → V8.1 → V8.2 → V9.0 | Strict sequential | 1.05× | Four passes; only justified when V7.1 SP level is very old |
The economic recommendation is unambiguous: go V7.1 → V8.2 → V9.0. The engineering effort is split into two manageable migrations, and the in-flight V8.2 system is a known stable configuration on which you can run production between the two upgrades.
Prerequisites for the Migration
- PCS 7 V7.1 SP3 minimum on every OS, AS, and engineering station. Earlier SP levels are not on the Siemens-tested migration path to V8.2.
- Hardware catalog check: confirm every IPC is in the supported hardware list for the target version. Reference the PCS 7 V9.0 - Released Modules and the corresponding V8.2 list.
- OS image: Windows 10 IoT Enterprise LTSC 2019 for V9.0, Windows 7 SP1 / Server 2008 R2 for V8.2 transitional state.
- Domain / user accounts: PCS 9.0 enforces a stricter password policy; verify SIMATIC Logon settings before upgrade.
- Backup: full CFC/SFC export, WinCC project export, complete image of each OS station.
- License set: ensure V8.2 PowerPack keys are on the license server, then V9.0 keys once V8.2 is installed and activated.
Step-by-Step: V7.1 → V8.2 → V9.0 Migration
Phase 1 - Engineering pre-work (offline)
- In the V7.1 engineering station, run
SIMATIC Manager → Options → PCS 7 → Migration Checkagainst the master data library. Document every block with a migration warning (custom blocks, third-party libraries). - Export the complete WinCC project as a backup
*.bckand a compressed*.zipproject package. - Update the AS firmware: AS 410 to
V8.2firmware, AS 400 to the last V8.2-compatible firmware. Do this before the OS upgrade to avoid runtime inconsistency.
Phase 2 - OS station migration to V8.2
- Re-image the OS station to Windows 10 IoT Enterprise LTSC 2019 (or Server 2016 Standard for the OS server role).
- Install PCS 7 V8.2 from the standard image. Do not attempt in-place upgrade of the V7.1 OS - the runtime database structure changed in V8.x.
- Restore the WinCC project from the
*.zipbackup. The import wizard will flag any incompatible graphics, scripts, and tag connections. - Compile OS, then run the
OS Project Editor → Compile OSwith the "with migration" option. - Run the redundant server synchronization check (for OS server pairs).
- Switch over the operator stations one at a time; verify SFC Visualization, alarm routing, and
@ReduLightindication.
Phase 3 - V8.2 to V9.0 second step
- Apply the V9.0 PowerPack license to the license server.
- Re-image OS stations to Windows 10 IoT Enterprise LTSC 2019 (V9.0 does not support older OS).
- Install PCS 7 V9.0 and import the V8.2 project. The migration wizard will offer: keep PROFIBUS, migrate PROFINET devices, and update the WebUX client configuration.
- Compile and download the new AS firmware if the AS type changed (e.g. AS 410 → AS 410E for PROFINET IRT).
- Run the PCS 7
Commissioning → Diagnosticcheck; verify all SFCs cycle and the time-of-day synchronization between OS servers and AS.
Controller and Fieldbus Compatibility Matrix
| AS Type | Order Number | PROFIBUS DP | PROFINET IO RT | PROFINET IO IRT | V9.0 Certified Firmware |
|---|---|---|---|---|---|
| AS 410 (6ES7410-5HX08) | 6ES7410-5HX08-0AB0 | Yes | No (only via IE/PB link) | No | V8.2.x |
| AS 410E (PROFINET capable) | 6ES7410-5HM08-0AB0 | Yes (PN/DP variant) | Yes | Yes | V9.0.x |
| AS 410S (safety) | 6ES7410-5HX08 with F-CPU | Yes | Limited | No | V8.2.x |
| AS 400 (legacy) | 6ES7400-x... | Yes | No | No | V8.2 SPx only |
| AS 150 / AS 410E 5H redundant | 6ES7410-5HR08 | Yes | Yes | Yes | V9.0.x |
If PROFINET field migration is on the project scope, the AS 410E is the minimum controller; for IRT-class motion or high-speed isochronous I/O, only the 5H redundant pair with PROFINET CBA modules is recommended.
PROFINET Enable Checklist
Migrating the field from PROFIBUS DP to PROFINET IO is independent of the OS upgrade but is the single most common reason an operator finally commits to V9.0.
- Topology: replace PROFIBUS OLM/OLP rings with SCALANCE XC/XB/XR managed switches. PN/PN couplers replace the DP/DP coupler.
- Device description: import GSDML files (GSDML-Vx.x-...xml) into SIMATIC PDM; the older PROFIBUS GSD files cannot be used on PN devices.
- IP plan: PROFINET devices need an IP, a device name, and a MAC. PCS 7 V9.0 supports DCP-based assignment; pre-stage IP addresses in the address book.
- Replacement strategy: phased cutover is safer than a single big-bang. Each new PN island is hot-swapped into the existing DP segment through a PN/PN coupler; verify I/O update time stays below the configured OB1 cycle.
- Diagnostics: enable SNMP traps on SCALANCE switches; integrate into the PCS 7 diagnostic screens via the standard SIMATIC NET OPC server.
Verification Procedure
After every OS station swap, run the following checks before handing the station back to operations:
-
SIMATIC Manager → CPU → Diagnostics → Module Information: confirm no SF / BF on AS or IM modules. - Trigger an alarm on every AS; verify it surfaces on the OS with the correct priority, color, and audible routing.
- SFC Visualization: open a representative SFC chart; verify step transitions, mode changes, and operator prompts.
- Trend archive: open a historical trend from the operator station; confirm samples are written to the configured segmented archive.
- Redundancy test: stop the standby OS server; confirm the active server takes over within the configured switchover time (default < 30 s, typically 4-8 s for PCS 7 V9.0).
- Time sync: confirm OS server time and AS time match within 1 s (NTP or SIMATIC time protocol).
- Backup: run the configured archive backup; restore on a test path to verify integrity.
Common Pitfalls
| Symptom | Likely Cause | Remedy |
|---|---|---|
| OS crashes on startup after migration | Custom C-script incompatibility with V9.0 runtime | Check WinCC Explorer → Computer → Properties → Startup; isolate and rewrite scripts that use removed COM interfaces |
| SFC chart shows "Wrong version" alarm | AS firmware newer than OS knows about | Install matching V9.0 AS firmware package from Siemens Industry Online Support |
| PROFINET device stays in "Station failure" | Device name not assigned | Use PRONETA or STEP 7 → PLC → Ethernet → Assign PROFINET Device Name
|
| Operator station freezes on graphics change | WinCC project not compiled after library update | Re-run OS Project Editor with "Complete compilation" |
| Alarm log missing entries | Time sync drift between OS server and AS | Reconfigure SIMATIC time master; verify NTP source reachable |
| License error after PowerPack | Old V7.1 license key still on license server | Remove V7.1 keys, return V8.2/V9.0 keys to license server pool |
Recommended Migration Sequence Summary
- Re-image the engineering station first; validate the project compiles in V8.2 against a sandbox AS.
- Migrate OS servers (in pairs) to V8.2 on IPC547G or IPC647D; run production for at least one full batch cycle on V8.2.
- Migrate AS firmware last on V8.2; only after OS is stable.
- Apply V9.0 PowerPack, re-image OS stations to Windows 10 IoT Enterprise LTSC 2019, install V9.0.
- Bring up the AS 410E with PROFINET IO; cut over field islands per the PROFINET enable plan.
- Decommission V7.1 hardware and V8.2 transitional licenses only after V9.0 passes a 30-day stability gate.
FAQ
Is it cheaper to upgrade PCS 7 from V7.1 directly to V9.0, or to step through V8.2 first?
Stepping through V8.2 first is cheaper overall. The V7.1 → V8.2 and V8.2 → V9.0 PowerPack license pairs together cost less than a single V7.1 → V9.0 PowerPack, and each step is smaller, lowering engineering risk.
Will an IPC547E (discontinued 2018-03-06) still run PCS 7 V9.0?
Yes, the IPC547E is on the V9.0 released-modules list. It is, however, end-of-life hardware with no spare-parts guarantee and is not certified for V9.1. Plan a replacement to IPC547G or IPC647D within the V9.0 service window.
Do existing AS 400 / AS 410 controllers and PROFIBUS DP need to be replaced when migrating to V9.0?
No. The AS-side firmware and fieldbus are independent of the OS IPC swap. AS 410 with V8.2 firmware continues to run under V9.0 OS; PROFIBUS DP segments remain valid. PROFINET IO with IRT does, however, require the AS 410E (6ES7410-5HM08) and matching firmware.
What happens to PCS 7 V8.2 support when V9.1 is released?
Siemens free basic support covers only the current and predecessor versions. Once V9.1 is the current version, V9.0 becomes the predecessor and V8.2 drops out of the free support window. V8.2 is still valid as a transitional installation but should not be the long-term landing target.
Is Windows 10 IoT Enterprise LTSC mandatory for PCS 7 V9.0?
Yes. PCS 7 V9.0 supports Windows 10 IoT Enterprise LTSC 2019 and Windows Server 2016/2019 as the only operating systems. Windows 7 SP1 and Windows Server 2008 R2 are dropped at this version, so a V7.1 OS station on legacy Windows must be re-imaged as part of the V9.0 migration.