Which PCS 7 Licenses Are Needed to Edit and Monitor a Project from a PG
Select licenses by the engineering functions, PCS 7 release and station role required on the PG. Editing an AS project, configuring an OS, observing online and downloading are separate requirements. Siemens documents engineering and download licensing separately for V9.0, but an exact purchase or update recommendation cannot be made without the installation version and existing entitlement. Prepare that inventory first, then obtain a release-specific license and upgrade confirmation.
Table of Contents
- Engineering and Runtime License Roles
- Prepare a Version-Specific License Request
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Engineering and Runtime License Roles
For PCS 7 V9.0, the configuration-station table lists AS Engineering and OS Engineering. AS RT PO is a separate, count-relevant download license. The manual distinguishes version-dependent functionality from scalable capacity. These categories do not establish the exact orderable package for an unidentified installation. Siemens licensing manual, sections 3.1 and 4.1.
Prepare a Version-Specific License Request
Use this engineering preparation workflow before purchasing or updating licenses:
- Record the installed PCS 7 version, Service Pack and Update on the PG and existing engineering station. Record affected component versions separately.
- Identify the work: AS chart changes, OS picture changes, online observation, compilation or download. List these as separate requirements.
- Record whether the PG is a separate engineering station or combines engineering with runtime.
- Inventory existing license names, versions and capacities without distributing license keys or credentials.
- Identify optional engineering products used by the project and the plant-bus connection hardware.
- Submit this inventory with the requested target version to the manufacturer or authorized supplier for a version-specific package and upgrade-entitlement confirmation.
The expected result is a requirements list that can be checked against the applicable edition's station table. This is procurement preparation, not a manufacturer installation or migration procedure.
Verification
Check the quoted package against the recorded tasks, installed release, existing entitlements and capacity requirements. Resolve omissions before purchase. After approved installation, demonstrate the intended online observation on the intended station under the site's access controls; opening a local project does not demonstrate an online connection or authorize a download.
Limitations and Operational Precautions
The original configuration does not identify a PCS 7 release, existing license inventory or requested update. Consequently, an exact purchase list, upgrade entitlement and online-monitoring license requirement remain unresolved. V9.0 examples must not be applied to another release without confirmation.
Preserve a restorable project backup before modifications. Keep license evaluation separate from software migration and production download approval. No commissioning or license transfer has been performed here.
Engineer FAQ
Is a PG itself a license category? The required functions and software configuration need to be identified; the computer description alone does not resolve the purchase.
Does an installed runtime license settle engineering requirements? Check engineering and runtime requirements separately.
Which manual edition should be used? Use the edition applicable to the installed or approved target release.