How PCS 7 Counts AS and OS Process Objects

In PCS 7, a faceplate alone does not make a block instance an OS process object. The V9.1 licensing manual counts all SFCs and block instances that can be operated and monitored, generate messages, and are not part of the driver library; the block's S7_m_c attribute marks operator control and monitoring capability. AS RT PO and OS RT PO are separate license categories, so check each with the PCS 7 license information tools for the relevant project and OS.

What qualifies as a PCS 7 process object

The PCS 7 V9.1 manual defines process objects (POs) as all SFCs and block instances meeting the stated criteria: the instance can be operated and monitored, it generates messages, and it is not part of the driver library. A block that supports operator control and monitoring has S7_m_c = true in its CFC block properties. The criteria are cumulative for block instances; S7_m_c alone does not establish that the instance is license-relevant.

The objects are transferred to the OS and require licensing. A graphical faceplate is not itself the counting test: the relevant object properties and PCS 7's license calculation determine the count.

AS RT PO and OS RT PO

AS RT PO concerns the process-object capacity for the automation system. The PCS 7 license-information view reports configured AS license objects for the selected multiproject or project. OS RT PO concerns the number of process objects that the operator station is licensed to operate and monitor. The OS license calculation is a separate view and uses an OS compile as a prerequisite.

Treat these as separate licensing checks. Do not infer either count solely from the number of faceplates, CFC block instances, or I/O points. Consult the license documentation applicable to the installed PCS 7 release and the installed license level.

How to inspect the AS RT PO count

Use the procedure documented in the PCS 7 V9.1 “Licenses and configuration limits” manual:

Open the multiproject or project in SIMATIC Manager and select it in Component View.
Choose Options > PCS 7 license information.
Select Process objects (AS RT PO) in the table.
Read the configured license-object count for the selected project and compare it with the available AS RT PO license capacity shown in the dialog.

For diagnosis, inspect relevant CFC block properties when an instance's eligibility is unclear. The manual distinguishes the license-information result from CFC Chart Reference Data statistics: the statistics can report all OCM-capable blocks whether or not they generate messages, while the license view reflects the licensing criterion.

How to inspect the OS RT PO count

The V9.1 manual's OS calculation procedure requires compiling the OS before determining the configured OS process-object count:

In SIMATIC Manager, compile the OS for the project.
Select the multiproject or project in Component View.
Choose Tools > PCS 7 License Information.
Select OS process objects and read the configured license objects.
Check that OS RT PO capacity is installed on the OS server or OS single-station system as applicable. The manual says an OS client does not require an OS RT PO license.

Use the count from the compiled configuration when checking the operator-station license requirement; a successful OS compile by itself does not demonstrate that sufficient license capacity is installed.

Verification

Compare the project's AS RT PO count in the license-information dialog with its available AS capacity. After compiling the OS, inspect the OS process-object count separately and check the OS server or single-station license capacity. If CFC Chart Reference Data shows a larger OCM-capable total, remember that its statistics include OCM-capable blocks that do not generate messages; that total is not interchangeable with the AS RT PO licensing count.

Limitations and Operational Precautions

The procedures and criteria cited here are from the PCS 7 V9.1 licensing manual. Menu labels or counting behavior should be checked against the manual for the installed PCS 7 release. The source question does not provide a project, configured blocks, or license inventory, so no numeric requirement can be calculated here. License counts are not a substitute for checking the installed license keys and the specific OS architecture.

Engineer FAQ

Does every block with a faceplate count as an OS PO? No. A faceplate by itself is not the criterion. The documented block-instance rules include operator control and monitoring, message generation, and exclusion from the driver library.

Does S7_m_c = true alone make a block count? No. It indicates that the block can be operated and monitored; the documented licensing criteria also require message generation and that the instance is not part of the driver library.

Why can Chart Reference Data show a different number? The CFC statistics can include all OCM-capable block instances regardless of whether they generate messages. The license-information dialog is the relevant view for AS RT PO licensing.

Do AS RT PO and OS RT PO represent the same license? No. They are separate license categories, reported through the AS and OS license-information calculations.

When can I calculate the OS PO count? The cited V9.1 manual specifies that the OS must be compiled before its configured process-object count is determined.

Technical References

Siemens, SIMATIC PCS 7 — Licenses and Configuration Limits (V9.1), §§ 4.1, 4.3–4.4, “Determining the process objects for the automation systems” and “Calculating the process objects for the operator station”: https://cache.industry.siemens.com/dl/files/371/109794371/att_1057404/v1/ps7lic_en-US_en-US.pdf
Siemens support attachment for the same V9.1 manual: https://support.industry.siemens.com/cs/attachments/109794371/ps7lic_en-US_en-US.pdf

How PCS 7 Counts AS and OS Process Objects