Upgrade PCS 7 V9.0 to V9.1 on One Engineering Laptop: Version and License Checks

Before upgrading PCS 7 V9.0 projects to V9.1 on an Engineering Station, establish the exact V9.0 service pack and the supported target path. Siemens' PCS 7 V9.1 Readme identifies V9.0 SP3 projects as an upgrade source, but that does not establish a route for an unspecified V9.0 level or prove two versions can be installed side by side. Keep a verified V9.0 archive and confirm V9.1 license entitlement separately.

The release level determines the upgrade route

The PCS 7 V9.1 Readme says projects can be upgraded from PCS 7 V8.2 SP1 or PCS 7 V9.0 SP3 to V9.1. The question names only PCS 7 V9.0, without its service pack, so that statement does not establish the project's eligible path. Identify the exact source build first.

Same laptop or separate engineering stations

The available evidence does not settle whether the two specific software packages may be installed side by side on one laptop. The V9.1 Readme states that update installation is not supported as of V9.1 and gives installation/OS requirements; do not interpret this as approval for simultaneous versions. Check the V9.1 PC Configuration manual and supported OS table for the proposed workstation. A separate engineering station can isolate environments when concurrent maintenance is needed, subject to licensing and site architecture.

Protect versions, projects and licenses

Keep the V9.0 and V9.1 projects distinct and archive the original V9.0 project before conversion. Siemens documentation describes license keys in the product media and use of Automation License Manager for license transfer in specified regional editions. The source's license entitlements and transfer rights are unknown; verify them with Siemens or the license supplier instead of assuming a V9.0 key authorizes V9.1.

Recommended migration sequence

Record exact PCS 7 service pack/update, libraries, options, engineering-station OS and hardware.
Verify that the source project version appears in the target-version migration documentation.
Create and verify a restorable archive; work on a copy.
Follow the matching “Software Update Without Utilization of New Functions” or “With Utilization of New Functions” manual.
Resolve library and block updates and validate AS, OS and optional components separately before any production download.

Verification

Confirm that the actual source version is supported, licenses are valid for the installed software, the project opens and compiles according to the prescribed migration path, and representative AS/OS functions work in a test environment. A successful installation or project opening alone does not prove a safe migration.

Limitations and Operational Precautions

The exact V9.0 service pack, license SKUs, operating system, and whether both packages are installed concurrently are not stated. The V9.1 Readme's upgrade path is specific; do not generalize it to V9.0 SP1 or another level. No migration test was reported.

Engineer FAQ

Can any PCS 7 V9.0 project be opened as a supported V9.1 migration? The V9.1 Readme names V9.0 SP3, not an unspecified V9.0 installation. Check the actual source update and matching migration manual.

Do separate licenses guarantee that both versions can run on one laptop? No. License entitlement and supported co-installation are separate questions.

Technical References

PCS 7 Readme V9.1, “Updating PCS 7 projects” and “Updating the PCS 7 Software”; opened and read. It names V8.2 SP1 and V9.0 SP3 project sources and states update installation is not supported as of V9.1.
Software Update with Utilization of New Functions V9.1 SP1, official V9.1 SP1 update manual; opened for upgrade context.
PCS 7 documentation — locate the corresponding no-new-functions update manual and PC Configuration manual for the exact installation.