Architecting and Configuring Multi-Client OS Workstations Across Multiple PCS 7 Servers

To configure a SIMATIC PCS 7 OS Client to access multiple OS Servers simultaneously (Multi-Client mode) across one or more multiprojects, generate the Server Data package ('.pck') on each respective OS Server, import and assign these packages into the OS Client station in SIMATIC Manager, and designate the standard server for alarms and split-screen management. Standard PCS 7 OS Client runtime licenses support connections to up to 18 OS single servers or 12 redundant server pairs simultaneously without requiring additional software options or multi-client add-on licenses.

Executive Summary

In large industrial plants with multiple process areas (e.g., Utilities, Reaction, Distillation, and Packaging), automation systems are frequently partitioned into separate PCS 7 OS Servers or distinct multiprojects. Central control room operators require unified visualization across all plant areas from a single workstation. In PCS 7, this is achieved through Multi-Client architecture. This article explains the server-client data package mechanics, standard server assignments, engineering procedures in SIMATIC Manager, and licensing verification for multi-client deployments.

Architecture and Fundamental Mechanics

Multi-Client Architecture, Server Packages, and Communication Paths:

Multi-Client Topology:
An OS Client in PCS 7 does not have its own process tag database. Instead, it acts as a client to one or more OS Servers.
The client connects to all servers over the common Terminal Bus.
Server Data Packages (.pck):
Each OS Server compiles its local AS tags, alarms, and graphics into a exportable Server Data Package (<ServerName>.pck).
Importing these packages into the OS Client exposes all server tags in the client's Tag Management under the respective server prefix (e.g., ServerA::Motor1.PV_Out).
Standard Server Designation:
Because an OS Client can see multiple servers, it must know where to send global commands that lack an explicit server prefix.
Standard Server for Alarms: Directs operator alarm acknowledgments to the appropriate server.
Standard Server for Split-Screen Manager / User Archives: Manages layout storage and batch archives.
Licensing Rules:
The 'SIMATIC PCS 7 OS Software Client' license covers multi-client access; there is no separate licensing fee for attaching a client to multiple servers.

Step-by-Step Implementation Procedure

Step-by-Step Procedure to Configure a Multi-Client Station:

Generate Server Data on All OS Servers:
- In SIMATIC Manager, right-click each OS Server project -> select 'Server Data -> Generate'.
- Verify that <ServerName>.pck is successfully compiled in the server project directory.
Assign Server Packages on the OS Client:
- In SIMATIC Manager, expand the OS Client PC Station -> open WinCC Explorer.
- Right-click 'Server Data' -> select 'Assign...'.
- In the package assignment dialog, check the packages for all target servers (e.g., OS_Area1 and OS_Area2).
- Click OK.
Configure Standard Server Assignments:
- In WinCC Explorer on the client, right-click 'Server Data' -> select 'Standard server...'.
- Assign the primary server responsible for alarms (Alarms) and screen management (SSM).
Run OS Project Editor on the Client:
- Open OS Project Editor in WinCC Explorer.
- Select the target monitor resolution and multi-monitor arrangement.
- Under the 'Areas' tab, verify that picture hierarchies from both servers are visible.
- Click OK to build the composite navigation hierarchy.
Download OS Client Project:
- Right-click the OS Client in SIMATIC Manager -> Target System -> Download.
- Ensure target path on the client PC is accessible over the network.
Activate Runtime on Client:
- Verify network visibility in Simatic Shell on the client PC.
- Activate WinCC Runtime; confirm screen navigation bars show pictures from all configured servers.

Verification

To verify multi-client operation:
1. In WinCC Runtime on the client, navigate between process displays originating from Server A and Server B; verify seamless display loading without lag.
2. Check the global alarm banner: verify alarms from both Server A and Server B populate the unified alarm list.
3. Issue an alarm acknowledgment on an alarm from Server B; verify the acknowledgment reflects instantly on Server B and other clients.

Limitations and Operational Precautions

Operational precautions:
- All OS Servers and OS Clients must synchronize time via a central NTP master clock; unsynchronized time stamps will disrupt alarm sorting and trend display.
- Ensure that computer names and IP addresses on the Terminal Bus are completely unique across all servers and clients.
- A standard OS Client should not exceed connections to 18 single servers or 12 redundant server pairs to prevent network socket starvation.

Engineer FAQ

Does a PCS 7 OS Client require an extra license to connect to multiple servers?

No. The standard SIMATIC PCS 7 OS Software Client runtime license permits connection to multiple OS servers simultaneously.

How many OS servers can a single OS client connect to in PCS 7?

A PCS 7 OS client can connect to up to 18 single servers or 12 redundant server pairs.

What is a Server Data package?

A compiled file (.pck) containing tag names, message definitions, and archive references generated by an OS server for client use.

What is the purpose of configuring a 'Standard Server' on an OS client?

It defines which OS server handles unqualified requests, such as operator alarm acknowledgments or global script executions.

Can an OS Client access servers from two different PCS 7 multiprojects?

Yes, by generating server data in each multiproject and importing the .pck files onto the client station.

Technical References

Related Tags

Multi-Client
OS Server
Server Data
Standard Server
Terminal Bus

20 respuestas

Architecting and Configuring Multi-Client OS Workstations Across Multiple PCS 7 Servers