C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Sizing SIMATIC PCS 7 OS Client Runtime Licenses Across Multi-Server Architectures

Sizing SIMATIC PCS 7 OS Client Runtime Licenses Across Multi-Server Architectures

In SIMATIC PCS 7, the OS Software Client runtime license (e.g. 6ES7658-2CX28-0YB5 for V8.2) is licensed strictly per client workstation, not per server connection. If an OS Client accesses process data and alarms from two or more OS Servers (such as Server A and Server B connected to separate AS controllers in a multiproject), exactly ONE OS Client runtime license is required on that client station. OS Servers require their own OS Server runtime and Process Object licenses, but do not consume additional client licenses for multi-server client access.

Table of Contents

Executive Summary

Multi-server distributed architectures are standard in large-scale SIMATIC PCS 7 process plants, where different process areas are governed by independent automation controllers and dedicated OS Server pairs. A common procurement and licensing question is how OS Client runtime licenses (e.g. 6ES7658-2CX28-0YB5) scale when an operator station must display process pictures and receive alarms from multiple distinct OS Servers simultaneously. This article establishes the definitive manufacturer licensing rules: client licenses are station-based, independent of the number of connected servers or Process Objects, and clarifies the licensing boundaries between clients, servers, and web options.

Architecture and Fundamental Mechanics

Architectural Mechanics and Licensing Rules for PCS 7 OS Clients:

  • Station-Based Licensing Principle:
  • The 'SIMATIC PCS 7 OS Software Client' license authorizes a physical PC station or virtual machine to execute the WinCC PCS 7 client runtime software.
  • The license key is installed locally on the client PC (or served floating across the network via Automation License Manager).

  • The One-Client, One-License Rule: Exactly 1 OS Client license is required per operator console, regardless of whether that console accesses 1 OS Server, 2 OS Servers, or up to the maximum tested Siemens architectural limit (e.g. up to 18 server pairs in PCS 7 V9.0/V9.1).

  • Multi-Server Package Mechanics:

  • In a multi-server multiproject, each OS Server compiles its own local project and exports a 'Server Package' (.pck file) containing its tag names, alarm configurations, and archive definitions.
  • The OS Client loads server data packages from multiple servers (e.g. Server A for Unit 1, Server B for Unit 2, Process Historian for long-term trends).

  • The OS Client runtime integrates these disparate server databases seamlessly into a unified plant picture tree. No additional client license keys are consumed on the servers or the client for this cross-server access.

  • Server-Side Licensing Demarcation:

  • Each OS Server requires an 'OS Software Server' runtime license (or 'OS Server Redundancy' license for redundant pairs) and sufficient 'OS RT PO' (Process Object) licenses to cover all tags and alarms generated by that server's assigned controllers.

  • OS Servers do not require client access licenses (CALs) for connecting standard PCS 7 OS Clients.

  • Boundary with Web Clients:

  • Standard OS Clients must not be confused with Web Clients. Accessing PCS 7 via Internet Explorer / web browsers requires 'WinCC WebNavigator' or 'WinCC WebUX' concurrent-user licenses, which are licensed separately.

Step-by-Step Implementation Procedure

Step-by-Step Configuration and License Allocation Procedure:

  1. Calculate Required OS Client Licenses:
    - Count the total number of physical operator PC stations and virtual client machines in the control room and plant floor.
    - Total OS Client Licenses Required = Total Client Workstations (independent of the number of OS Servers in the plant).
  2. Install License on Client Workstations:
    - Launch Automation License Manager (ALM) on each OS Client PC.
    - Transfer one 'SIMATIC PCS 7 OS Software Client' license key (matching the PCS 7 version) to the local hard drive, or configure ALM to point to a central floating license server.
  3. Generate and Assign Server Data in SIMATIC Manager:
    - On OS Server A: Right-click Server Data -> Generate.
    - On OS Server B: Right-click Server Data -> Generate.
    - Open the OS Client project in SIMATIC Manager.
    - Right-click Server Data -> Load...; select and import the generated packages for both Server A and Server B.
  4. Configure Standard Server Assignments on the Client:
    - In the OS Client project, right-click Server Data -> Standard Server....
    - Assign default servers for Alarms and SSM (Split Screen Manager) if required.
  5. Compile and Download OS Client Project:
    - Download the client configuration to the target client workstation.
    - Activate WinCC Runtime on the client.

Verification

Verification Procedure:
1. Multi-Server Runtime Verification: Open WinCC Runtime on the OS Client. Navigate to pictures sourced from Server A and pictures sourced from Server B. Confirm process values update dynamically and alarm banners display alarms from both controllers without communication errors.
2. ALM License Status Check: On the OS Client, open ALM. Select the installed 'OS Software Client' license key. Verify that the 'Status' column shows 'In use' and the 'Number of License Keys' consumed is exactly 1.
3. Absence of License Banners: Confirm that WinCC Runtime runs continuously without displaying demo mode warning popups or periodic licensing timeout dialogs.

Limitations and Operational Precautions

Operational Precautions and Procurement Verification:
- Version Specificity: OS Client license keys are strictly tied to specific major PCS 7 versions (e.g. V8.2 vs V9.0 vs V9.1). The catalog number 6ES7658-2CX28-0YB5 corresponds to PCS 7 V8.2. Upgrading a plant to PCS 7 V9.1 requires purchasing corresponding OS Client Upgrade licenses.
- Multi-Server Architectural Limits: While an OS Client requires only one license across multiple servers, the physical hardware and network must respect Siemens' tested system limits (e.g. max 18 server pairs per client, max 64 clients per server pair).
- Procurement Verification: Always confirm final license quantities, media packages, and MLFBs against the official Siemens ST PCS 7 catalog and an authorized Siemens distributor quotation.

Engineer FAQ

If an OS Client connects to 3 OS Servers, how many client licenses are needed?

Exactly one OS Client license is needed on that workstation. Licensing is based on the number of client PCs, not the number of server connections.

Do OS Servers need client access licenses (CALs) for PCS 7 OS Clients?

No. PCS 7 OS Servers do not consume client connection licenses; they only require their own OS Server runtime and OS Process Object (PO) licenses.

Can an OS Client license be served over the network as a floating license?

Yes. OS Client licenses can reside on a central Automation License Manager server and be dynamically assigned to clients over the network.

Does the OS Client license cover WinCC WebNavigator or WebUX clients?

No. Web-based access requires separate concurrent-user license packages for WebNavigator or WebUX.

What catalog number represents the PCS 7 V8.2 OS Client license?

The catalog number for the PCS 7 V8.2 OS Software Client runtime license is 6ES7658-2CX28-0YB5.

Technical References

Related Articles

Related Tags

  • OS Client Licensing
  • Multi-Server Architecture
  • WinCC Runtime
  • 6ES7658-2CX28-0YB5
  • Server Packages
20 respuestas