Increase PCS 7 V9.0 Single-Station Process Object Capacity

For a PCS 7 V9.0 ES/OS single-station system, distinguish engineering entitlement from runtime process-object capacity. The AS/OS Engineering license enables engineering editors; increasing runtime limits requires the appropriate AS RT PO and OS RT PO license keys for the automation system and operator station. The 250-PO base capacity depends on the exact product bundle, so verify the order number and use PCS 7 License Information to count the configured objects before purchasing additional keys.

Engineering and Runtime Licenses Serve Different Purposes

An engineering license provides access to project engineering functions such as CFC, SFC, and OS editors. Runtime process-object license keys authorize a defined number of objects in the AS and OS. Buying or upgrading engineering access does not automatically raise AS or OS runtime object limits.

Which Capacity to Increase

Determine where the capacity is exceeded:

NeedLicense category to checkWhat it coversAdditional AS runtime objectsAS RT POProcess objects processed by an AS, subject to controller limitsAdditional OS runtime objectsOS RT POObjects operated and monitored by the OSEngineering editor accessAS/OS Engineering licenseEngineering software and editors; not a substitute for runtime PO keys

Use Siemens' V9.0 manual and product catalog for the exact license levels available for the station.

Calculate the Required Keys

Record the exact single-station product and order number, including its included AS/OS capacity.
In SIMATIC Manager, compile the OS as required by the license manual, then open Tools > PCS 7 License Information.
Review the configured AS and OS process-object counts separately.
Compare each count with the valid keys visible in Automation License Manager and the bundle's included capacity.
Add the appropriate AS RT PO or OS RT PO license level for the deficit, respecting the model-specific AS limit and product ordering rules.
Transfer and allocate keys according to the PCS 7 licensing manual, then recheck the license information.

Do Not Count the Bundle Name as the Full License Inventory

The source names a V9.0 ES Single Station package with 250 POs, but does not give its order number or all delivered license keys. Bundles can include specific base levels and optional license keys. Use the product catalog, purchase/delivery record, and current Automation License Manager inventory to confirm the starting capacity.

Verification

Check the license information for configured AS and OS objects and confirm sufficient matching keys are available on the runtime station. Validate the station's engineering and runtime functions separately; a visible OS project does not establish runtime license sufficiency.

Limitations and Operational Precautions

The exact bundle SKU and license inventory are missing. AS and OS PO counts are separate, and AS capacity depends on CPU type. Do not move license keys or expand a production system without confirming the correct key type and station allocation.

Engineer FAQ

Engineering licenses enable the editors; AS RT PO and OS RT PO keys increase their respective runtime object capacities. Count each side separately using PCS 7 License Information.

Technical References

Siemens, PCS 7 Licenses and Configuration Limits (V9.0): https://support.industry.siemens.com/cs/attachments/109746549/ps7lic_en-US_en-US.pdf
Siemens, PCS 7 Licenses and Configuration Limits (V9.0 SP3), OS PO calculation and license-information procedure: https://support.industry.siemens.com/cs/attachments/109780813/ps7lic_en-US_en-US.pdf
Siemens PCS 7 Catalog ST: https://support.industry.siemens.com/cs/ww/en/view/109745632