PCS 7 Process Object Licensing: Version Independence and MLFB Compatibility Across V8.2 and V9.0

In SIMATIC PCS 7, runtime Process Object licenses—specifically AS RT PO (Automation Station Runtime Process Objects) and OS RT PO (Operator Station Runtime Process Objects)—are version-independent starting from PCS 7 V7.0 onward. A 100 AS RT PO license (MLFB 6ES7653-2BA00-0XB5) or 100 OS RT PO license (MLFB 6ES7658-2CS00-0XB0) purchased under PCS 7 V9.0 or V9.1 can be deployed directly onto a PCS 7 V8.2 system via Automation License Manager (ALM) without version conflict. Note that standard AS RT PO licenses apply to classical S7-400 CPUs; CPU 410-5H controllers utilize hardware System Expansion Card (SEC) PO upgrade packages. Always validate MLFB availability with an authorized Siemens distributor quotation.

Executive Summary

Expanding existing industrial automation facilities operating legacy or mature SIMATIC PCS 7 releases (such as PCS 7 V8.2) frequently requires procuring additional Process Object (PO) runtime capacity for newly added control loops, motors, and valves. When consulting Siemens procurement catalogs or the Siemens Industry Mall, procurement engineers often observe that order numbers (MLFBs) are cataloged under the current release (e.g. V9.0 or V9.1), prompting uncertainty as to whether modern license packages will be recognized by older PCS 7 V8.2 engineering stations and runtime servers. In Siemens licensing architecture, runtime PO licenses are fundamentally version-independent. This article explains the counting and licensing rules for AS and OS Process Objects, details MLFB cross-compatibility, and outlines distributor validation practices.

Architecture and Fundamental Mechanics

Process Object Architecture, ALM License Key Structure, and Controller-Specific Capacity Models:

Version-Independent Runtime PO License Model (V7.0 to V9.x):
In SIMATIC PCS 7, engineering licenses (e.g. PCS 7 Engineering V8.2) are version-specific, requiring version upgrades.
In contrast, Runtime Process Objects (AS RT PO and OS RT PO) represent purely quantitative capacity entitlements.
The Automation License Manager (ALM) license key header specifies Version: 7.0+ or Version-independent.
Consequently, an AS RT PO or OS RT PO license generated today for V9.0/V9.1 transfers seamlessly into an ALM database running on PCS 7 V8.2, V8.1, or V8.0.
Critical Distinction: Classical S7-400 vs. CPU 410-5H PO Licensing:
Classical S7-400 Controllers (CPU 414, 416, 417):
- Licensed via ALM Software License Keys: PCS 7 AS Runtime License (PO 100) (MLFB 6ES7653-2BA00-0XB5).
- Loaded onto the Engineering Station via ALM. During CFC compilation, the compiler queries the ES license store to tally cumulative PO utilization across all classical S7-400 controllers.
CPU 410-5H Process Automation Controllers:
- Do NOT utilize ALM AS RT PO software licenses!
- Licensed via a physical hardware card: the System Expansion Card (SEC) plugged directly into the CPU.
- PO capacity is upgraded by purchasing CPU 410 PO Upgrade Packages (MLFB 6ES7653-2CC00-...), which load SEC capacity credits directly onto the hardware card.
OS Runtime Process Object Licensing:
OS RT PO licenses (e.g. MLFB 6ES7658-2CS00-0XB0 for 100 OS POs) are installed directly onto each physical OS Server or OS Single Station. For redundant server pairs, identical OS RT PO counts must be installed on BOTH servers.
Commercial and Ordering Accuracy Guardrails:
Always distinguish AS RT PO software licenses from CPU 410 SEC hardware capacity upgrades.
Never estimate PO consumption solely from physical I/O channel counts. Calculate exact utilization in SIMATIC Manager via Options > Charts > Process Objects.
Validate final package MLFBs and licensing quantities against authorized Siemens distributor quotations.

Step-by-Step Implementation Procedure

Calculate Actual Process Object Utilization in SIMATIC Manager:
* In SIMATIC Manager on the PCS 7 V8.2 ES, open the project.
* Select menu Options > Charts > Process Objects.
* Review the summary table: inspect Configured POs vs Available Licenses for both AS and OS.
* Determine the exact shortfall (e.g. 100 additional AS POs and 100 additional OS POs).
Identify the Target Controller Type:
* Check if the target PLC is a classical S7-400 (requires software MLFB 6ES7653-2BA00-0XB5) or a CPU 410-5H (requires hardware SEC PO upgrade 6ES7653-2CC00-...).
Procure PO License Packages:
* Request an authorized quotation for:
- 100 AS RT PO: MLFB 6ES7653-2BA00-0XB5 (single software license).
- 100 OS RT PO: MLFB 6ES7658-2CS00-0XB0 (additive OS PO license).
- Confirm that electronic delivery (OSD) or USB certificate options match plant IT requirements.
Transfer Licenses to Workstations via Automation License Manager (ALM):
* Insert the license transfer USB drive or connect to the Siemens Online Software Delivery (OSD) portal.
* Open Automation License Manager as Administrator.
* Transfer the AS RT PO license key to the local drive C: of the Engineering Station.
* Transfer the OS RT PO license key to the local drive C: of the OS Server(s).
Verify and Compile:
* In SIMATIC Manager, re-open Options > Charts > Process Objects; confirm that available license counts increase immediately.
* Execute a CFC Changes compilation and download to verify zero license shortage warnings.

Verification

In Automation License Manager, select drive C:; confirm that the newly transferred licenses display status 'Valid' and license type 'Single'.
In SIMATIC Manager, execute a CFC compile; verify that the compiler logs zero AS PO overrun warnings.
On the OS Server, launch WinCC Runtime; confirm that the runtime starts without 'Demo Mode' license shortage dialogs.

Limitations and Operational Precautions

AS RT PO software licenses cannot be transferred into a CPU 410-5H System Expansion Card. Attempting to run an OS Server with insufficient OS RT POs triggers recurring hourly demo mode popups, though supervisory control remains operational.