Do PCS 7 Version Upgrades Require Booking Back Process Objects?

Changing engineering PCs and upgrading a PCS 7 project does not, by itself, mean process-object counts should be manually booked back from unchanged CPUs. PCS 7 CFC manages PO usage when programs are downloaded and can book back counts when a program is replaced or no longer uses the same allocation. Preserve the license keys and verify the CPU PO status under the upgrade procedure; do not perform a separate manual booking operation unless the licensing workflow requires it.

Distinguish PC software licenses from CPU process objects

The ticket keeps the AS/OS PO licensing identical and replaces engineering/server PCs while retaining the PLCs. Siemens documentation distinguishes PC-station license keys from countable process-object licenses handled by the automation system. A PCS 7 software version upgrade may require applicable upgrade licenses, but that is separate from booking back CPU process objects.

What triggers PO booking

Siemens CFC documentation describes booking PO counts during download and returning counts in certain cases, such as when a different program is loaded or used process objects are reduced. Replacing the engineering PC alone is not identified as a PO-book-back trigger. Follow the exact version-upgrade guide for any required downloads and CPU licensing checks.

Upgrade checks

Back up the project and license keys before migration.
Verify PCS 7 upgrade license requirements for the source-to-target version.
Confirm the target project's PO configuration and each CPU's available/used PO count.
Follow the upgrade manual's compile/download sequence; do not load an altered program to force a license counter change.
After required downloads, verify CPU PO status in the supported license management tools.

Verification

Confirm each unchanged CPU reports the expected process-object capacity and usage after the project is migrated and any required program download is complete. Separately confirm the new engineering/OS stations have valid software licenses.

Limitations and Operational Precautions

The source does not identify the PCS 7 source/target versions, PO expansion options or whether the CPU program is recompiled/downloaded. Some software upgrades require upgrade license keys. Check the corresponding release upgrade manual.

Technical References

Siemens, CFC for SIMATIC S7 V8.2, section 6.2 “Count and booking of the PO licenses” (principle of booking during downloads): https://support.industry.siemens.com/cs/attachments/109736727/s7cfcs7b_en-US.pdf
Siemens PCS 7 software update procedures (select source and target versions): https://support.industry.siemens.com/cs/ww/en/view/109748899
Siemens, PCS 7 PC Configuration V9.0 SP1, license types and PO counter: https://support.industry.siemens.com/cs/attachments/109754983/ps7pck_b_en-US.pdf

PCS 7 process object license booking
PCS 7 project version upgrade licensing

Engineer FAQ

What version details must be confirmed? Check the exact PCS 7, STEP 7, WinCC and device versions against their applicable documentation.

Does a successful communication trial prove GSD compatibility in every project? No. Verify the exact device revision, GSD version, hardware catalog and tested project configuration.

Should process-object capacity be treated as a PC license counter? No. PCS 7 process-object accounting and PC-station licenses are distinct; verify the exact license type and CPU.

What evidence should be retained? Keep software and hardware versions, license status, compile logs and verification results.

Can recommendations for a different version be used directly? No. Treat them as background and verify the matching release instructions.

Should an unresolved SFC setpoint reset be fixed by forcing a retained value? No. Trace the setpoint path and initialization before changing retention or sequence logic.

Does Audit Trail mean the same thing in every PCS 7 release? No. The product and licensing model changes by version; identify the required audit functions first.

Does this article claim a lab test? No. It uses available product documentation and the ticket record.

What is a safe next step when the precise cause is unknown? Capture diagnostics and reproduce the behavior in a project copy or controlled test system.

When should Siemens support be involved? Escalate if version-matched documents and diagnostics do not resolve the incompatibility or licensing question.

Do PCS 7 Version Upgrades Require Booking Back Process Objects?