Architectural Topologies in SIMATIC PCS 7: Standalone, Client-Server, and Decentralized Field Systems

SIMATIC PCS 7 provides multiple structural architectures beyond the traditional centralized Client/Server model, ranging from compact standalone systems to highly decentralized field topologies. For small plants or localized process skids, PCS 7 offers the OS Single Station architecture, combining engineering, server database management, and operator visualization onto a single PC host. For modern decentralized architectures, PCS 7 deploys distributed I/O intelligence directly into the field environment using SIMATIC Compact Field Units (CFU) and ET 200SP HA, eliminating centralized marshalling cabinets. Large plants utilize distributed multi-server architectures where autonomous OS server pairs manage discrete plant areas while sharing visualization data across unified client networks.

Overview of PCS 7 Architectural Topologies

While SIMATIC PCS 7 is renowned for large-scale industrial architectures featuring redundant server pairs and multi-client control rooms, Siemens engineered the platform to scale flexibly across diverse application footprints. Depending on physical plant layout, I/O count, and operational requirements, system architects can select from three fundamental architectural topologies:

OS Single Station (Standalone): A unified hardware platform hosting engineering, server communications, and operator monitoring on a single computer.
Distributed Multi-Server Architecture: Multiple independent OS Server pairs partitioned by plant process areas (e.g., Utilities, Reactor Train, Tank Farm) communicating with shared, cross-area OS Clients.
Decentralized Field System Architecture: Decentralizing control and I/O infrastructure using intelligent field-mounted nodes (such as the Compact Field Unit 6ES7655-5PX31-1XX0 and ET 200SP HA) over PROFINET, reducing field wiring and marshalling requirements.

Standalone Architecture: OS Single Station

For package units, localized test benches, or small production plants (typically under 1,000 process tags and 1 to 2 controllers), a multi-PC client/server architecture introduces unnecessary hardware and network overhead. The OS Single Station combines all supervisory roles into one PC:

Topology TypeHardware FootprintTarget ScopeMaximum ClientsRedundancy CapabilityOS Single StationSingle Industrial PC (IPC)Up to 1,000 POs / Small plantsUp to 4 reference Web/OS ClientsOptional Software RedundancyRedundant OS Server Pair2 Dedicated Server IPCsMedium to large plantsUp to 64 Thick/Thin OS ClientsAutomatic Hot-Standby SynchronizationDistributed Multi-ServerMultiple Server Pairs + ClientsPlant-wide / EnterpriseUnlimited via Multi-Client PackagesRedundant pairs per process areaDecentralized CFU Field NodeField-Mounted DIN-Rail UnitSkid / Field EnclosureManaged via Central AS/OSRedundant PROFINET (MRP/S2)

In a Single Station configuration, WinCC connects directly to the S7-400 or CPU 410 controller over Industrial Ethernet, logging alarms and historical process values directly to the local Microsoft SQL Server instance without routing through a Terminal Bus.

Centralized and Multi-Server Client-Server Architectures

In medium to enterprise-scale facilities, PCS 7 utilizes the Client/Server architecture.

In a Single Server / Redundant Server Pair architecture, a single redundant server pair manages the entire plant. However, when plants expand beyond 30,000 tags or require geographical segregation between production units, PCS 7 implements a Distributed Multi-Server Architecture:
* Each functional area (e.g., Unit 1, Unit 2) possesses its own dedicated redundant OS Server pair.
* Each server pair compiles and publishes an OS Server Package.
* Operator consoles in the central control room operate as Multi-Clients. A Multi-Client loads packages from all server pairs, displaying process screens, alarms, and trends from across the entire plant on a unified multi-screen console seamlessly.

Decentralized Field Automation via CFU and ET 200SP HA

Modern PCS 7 system engineering emphasizes decentralization at the I/O and instrumentation tier:

SIMATIC Compact Field Unit (CFU) (6ES7655-5PX31-1XX0): Installed directly in field enclosures adjacent to process equipment. The CFU provides 8 freely configurable digital channels and 8 PROFIBUS PA / HART fieldbus channels. It connects back to the controller via redundant PROFINET, automatically addressing and integrating intelligent field instruments, completely eliminating field junction boxes and multi-core home-run cables.
SIMATIC ET 200SP HA: High-density distributed I/O mounted on plant skid enclosures, providing hot-swapping and flexible terminal wiring.

Verification

To verify system topology configuration in the engineering environment:
1. In SIMATIC Manager, open the Multiproject and inspect the component tree.
2. In NetPro, verify the network routing between the AS controllers, OS Servers, and OS Clients.
3. On Multi-Client projects, right-click the Server Data folder and select Configure...; verify that all required area server packages are loaded and marked as active.
4. Open WinCC Runtime on an OS Client; verify seamless navigation across graphics belonging to different server packages without disconnection warnings.

Limitations and Operational Precautions

An OS Single Station should never be deployed for mission-critical processes requiring uninterrupted high availability, as single-station hardware maintenance forces loss of operator visualization. If clients are attached to an OS Single Station, Siemens strictly limits client connections to a maximum of 4 workstations to prevent database thread starvation. Review the SIMATIC PCS 7 Compendium Part A guidelines before finalizing system architectures.

Engineer FAQ

Can an OS Single Station also serve as an Engineering Station?

Yes. In small systems, a single PC can be configured as a combined ES/OS Single Station, allowing both automation programming and runtime monitoring on one physical machine.

What is an OS Server Package in a distributed multi-server architecture?

An OS Server Package is an exported database file (.pck) containing tag names, alarm configurations, and archive definitions. OS Clients import this package to communicate with that specific server pair.