Plan a PCS 7 V9.0 SP1 to V9.1 SP1 Project Migration
Treat a PCS 7 V9.0 SP1 to V9.1 SP1 upgrade as a version-specific migration, not as a generic compile-and-download checklist. The described multiproject has one AS, one OS and one library. Preserve a restorable project copy, confirm the supported component and operating-system path from matching Siemens migration documentation, and validate each subsystem before production download.
Table of Contents
- Define the migration scope
- Prepare a recoverable project
- Follow the matching migration procedure
- Rebuild and validate
- Stage commissioning
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Define the migration scope
Record PCS 7, APL and Basis Library versions, AS hardware/firmware, WinCC/OS, Engineering Station OS and options such as BATCH or Route Control. Opening, conversion, compilation, runtime compatibility and downloading are different gates.
Prepare a recoverable project
Archive and verify the multiproject, then work on a separate migration copy. Confirm the target Engineering Station and PCS 7 components are supported for V9.1 SP1.
Follow the matching migration procedure
Use the V9.0 SP1/V9.1 SP1 migration instructions and Readmes. The posted checklist mentions library updates, hardware review, AS/OS compilation, OS Project Editor and optional BATCH/Route Control, but supplies no verified order or prerequisites.
Rebuild and validate
Review hardware and network connections, compile AS and OS, and validate installed options and OS server/client assignments. Do not equate project opening or compile success with runtime correctness.
Stage commissioning
Test the migrated project, define outage and rollback plans, and use site change control before production download.
Verification
Record the exact manuals/tool versions; confirm project opening, unresolved compile differences, OS client/server connections and representative values, alarms and commands in a test environment.
Limitations and Operational Precautions
No accessible manual established the exact V9.0 SP1-to-V9.1 SP1 route. A special V9.0 SP3 UC04 Readme note cannot be generalized to SP1. No test result was supplied.
Engineer FAQ
Is the forum checklist complete? No. It lacks a verified release-specific sequence, prerequisites, validation gates and rollback procedure.
Technical References
- PCS 7 Engineering System V9.1 SP1 — official target-version manual; retrieval failed due document size.
- PCS 7 V9.0 SP3 UC06 Readme — migration note applies to UC04, not SP1.
- PCS 7/Open OS V9.1 SP1 Readme — relevant only if this option is installed.