SIMATIC PCS 7 Software Procurement and Licensing: Single Station (ES/OS) Bundles vs Distributed Architectures

For a standalone SIMATIC PCS 7 V8.0 facility with approximately 250 field I/Os where a single computer serves as both Engineering Station and Operator Station (ES/OS Single Station), you do not need to purchase separate engineering and runtime packages. Siemens offers integrated bundles—specifically the SIMATIC PCS 7 Engineering Station Single Station (ES/OS) package—which combines the Engineering Toolset, basic AS Process Objects (AS RT PO), and an OS Single Station runtime license in a unified package. However, if the architecture separates the ES from a dedicated OS Server, engineering toolsets and OS Server runtime packages must be procured separately, with AS and OS Process Objects sized to actual plant requirements.

PCS 7 Software Packaging Paradigms: Single Station vs Distributed Architecture

Procuring software for SIMATIC PCS 7 V8.0 requires selecting between two fundamental architectural deployment models:

Single Station Architecture (ES/OS Combined): A single industrial PC hosts both the engineering environment (STEP 7, CFC, SFC, WinCC CS) and the live process visualization runtime (WinCC RT). This architecture is cost-effective and standard for small plants, pilot skids, and facilities with 100 to 500 I/Os.
Distributed Client-Server Architecture: Dedicated servers execute runtime data acquisition and archiving, while separate Engineering Stations handle configuration and distinct OS Clients provide operator control.

Siemens structures its commercial order numbers (MLFBs) to reflect these distinct operational models. Conflating single-station packages with distributed server packages leads to procurement overruns or severe licensing shortfalls.

The ES/OS Single Station Software Bundle Structure

For combined single-computer installations, Siemens provides the SIMATIC PCS 7 ES/OS Single Station package (e.g. orderable via Siemens Catalog CA 01):

What the Bundle Includes:
PCS 7 Engineering Toolset: STEP 7, CFC, SFC, WinCC RC (Release & Configure), SIMATIC Logon, and Import/Export Assistant.
AS Process Objects: Typically bundled with a baseline of 250 AS RT POs (or 100 POs with expandable powerpacks).
OS Single Station Runtime: Grants authorization to execute WinCC Runtime locally for a single operator console with matching 250 OS RT POs.
Commercial Advantage: Buying the unified ES/OS Single Station bundle is significantly more economical than procuring engineering software and runtime licenses individually.

Separate Licensing Requirements for Dedicated OS Server Configurations

If the project requirement changes such that one PC acts purely as an Engineering Station and a second PC operates as a dedicated OS Server, the software and runtime licenses must be procured separately:

On the Engineering Station PC:
SIMATIC PCS 7 Engineering Toolset (Engineering seat license).
SIMATIC PCS 7 AS RT PO (Pooled controller process object license package in ALM, sized to total CPU logic).
On the OS Server PC:
SIMATIC PCS 7 OS Software Server (Server runtime operating license).
SIMATIC PCS 7 OS RT PO (Server tag/process object capacity license, e.g. 250 POs or 1000 POs).
SIMATIC NET HARDNET-IE S7 (or S7-REDCONNECT if communicating with fault-tolerant S7-400H CPUs).
OS Server Redundancy package (if deploying a redundant server pair).

Process Object (PO) Sizing Principles for 250 Field I/O Systems

When sizing licenses for a facility with approximately 250 physical field I/Os, strict commercial and technical guardrails apply:

[!IMPORTANT]
Never infer licensing quantities solely from CPU count, I/O count, or redundancy topology. Never treat estimated I/O-to-PO ratios as > actual license counts.

In continuous automation:

A Process Object (PO) represents a technological block (such as MotL, VlvL, PIDConL, or MonAnL) that possesses operator control and monitoring capability (S7_m_c := 'true').
Simple raw I/O channels (e.g. Pcs7DiIn, Pcs7AnIn) do not consume Process Objects unless configured with alarm generation.
Depending on the density of complex analog loops versus simple digital indicators, a 250 I/O plant typically consumes between 80 and 150 Process Objects. Therefore, a baseline package of 250 Process Objects provides ideal capacity with ample expansion headroom.

Comprehensive PCS 7 V8.0 Procurement Schedule: Single Station vs Server

The following schedule outlines required software components for both architectural choices:

Architectural OptionTarget ComputerMandatory Siemens Package DescriptionIncluded EntitlementsOption A: ES/OS Single StationSingle Standalone PCSIMATIC PCS 7 ES/OS Single Station V8.0ES Toolset + 250 AS RT PO + 250 OS RT PO (Single Stn)Option B: Dedicated ESEngineering StationSIMATIC PCS 7 Engineering Toolset V8.0STEP 7, CFC, SFC, WinCC RC, ALMOption B: Dedicated ESEngineering StationSIMATIC PCS 7 AS RT PO (250 POs)Controller runtime capacity for downloadOption B: Dedicated OS ServerOS Server PCSIMATIC PCS 7 OS Software Server V8.0Server runtime license + 250 OS RT POsOption B: Dedicated OS ServerOS Server PCSIMATIC NET HARDNET-IE S7Industrial Ethernet communication license

[!NOTE]
Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions > and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens > Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Verifying License Consumption in Installed Software

After deploying the software packages, verify license utilization via native Siemens engineering tools:

Open Automation License Manager (ALM) on the station. Confirm that all transferred license keys show status 'Valid'.
In SIMATIC Manager, open the project, right-click the multiproject root, and select Options -> Process Objects -> Available Licenses.
Inspect the total licensed capacity, currently booked POs, and remaining balance for both AS and OS Process Objects.
Confirm that the PO consumption does not exceed the procured 250 PO threshold.

Verification

Verify system operational readiness:

On the ES/OS Single Station, open SIMATIC Manager and compile all CFC charts; confirm 0 licensing compilation errors.
Download the program to the S7-400 controller; verify that AS POs are successfully booked in ALM.
In WinCC Explorer, activate WinCC Runtime locally; verify that process graphics, faceplates, and alarms operate continuously without license deficit popups.
Check the Windows Event Viewer and ALM log to confirm clean license validation.

Limitations and Operational Precautions

Adhere to the following procurement precautions:

Single Station MultiClient Prohibition: An ES/OS Single Station license authorizes runtime strictly on the local machine; it does not support servicing external OS Clients across the network.
Distinguish AS and OS POs: AS RT POs reside on the Engineering Station and govern controller logic; OS RT POs reside on the OS Server and govern WinCC tags and faceplates. They are distinct licenses and must both be accounted for.
Avoid Unlicensed PO Debt: While PCS 7 allows emergency downloads to proceed when POs are exhausted, operating with a licensing debt violates manufacturer terms of service.

Engineer FAQ

Can an ES/OS Single Station serve external operator clients across a network?

No. The Single Station license is restricted to local runtime operation. Connecting external OS Clients requires an OS Server runtime license and Terminal Bus infrastructure.

What is the difference between an AS RT PO and an OS RT PO?

AS RT PO licenses govern technological blocks running inside the controller, whereas OS RT PO licenses govern tags and faceplates displayed by the WinCC runtime engine.