Hardware Requirements for PCS 7 OS Servers and Role of Thin Clients in Terminal Architectures

Hardware Requirements for PCS 7 OS Servers and Role of Thin Clients in Terminal Architectures

In SIMATIC PCS 7, an Operator Station (OS) Server cannot run on a Thin Client because an OS Server is a high-performance database and communication engine requiring a multi-core industrial PC or server platform (such as a SIMATIC IPC647E/IPC847E) with hardware RAID, ECC RAM, and dedicated communications processors (CP 1623). Thin Clients (such as SIMATIC ITC or standard RDP terminals) are deployed exclusively as operator client interfaces connecting to a centralized Terminal Server hosting WinCC WebNavigator, WinCC WebUX, or a virtualized OS Client pool. The optimal architecture uses dedicated redundant industrial servers on the Plant Bus while thin clients access the system over the Terminal Bus.

Table of Contents

Executive Summary

Modernization and centralization initiatives in process automation frequently explore thin client technology to reduce footprint, eliminate moving parts in harsh plant environments, and streamline hardware maintenance. A frequent point of confusion among system architects is whether a PCS 7 OS Server can be deployed on a compact Thin Client hardware device. Because an OS Server is responsible for real-time polling of automation controllers, managing massive Microsoft SQL Server runtime archives, and coordinating redundant failover, deploying an OS Server on low-power thin hardware is technically impossible. This article delineates the server hardware specifications mandated by Siemens, clarifies the legitimate role of Thin Clients in terminal and web architectures, and presents approved distributed deployment models.

Architecture and Fundamental Mechanics

DCS Server Workloads, Real-Time Database Engine Requirements, and Thin Client Topologies:

  • Workload and Resource Demands of a PCS 7 OS Server:
  • Real-Time SQL Engine: Every OS Server hosts instances of Microsoft SQL Server (WinCC) managing high-frequency Tag Logging (up to thousands of cyclic values per second) and Alarm Logging.
  • Controller Communication Stacks: Servers maintain high-speed Industrial Ethernet S7 connections (often fault-tolerant S7-REDCONNECT) to multiple S7-400 / S7-410 controllers via PCI Express communication processors (CP 1623).
  • Redundancy Coordination: Redundant server pairs execute real-time database synchronization (CCRedCom.exe) over high-bandwidth links.
  • Hardware Requirements: Siemens mandates robust hardware platforms such as the SIMATIC IPC647E (2U rack) or SIMATIC IPC847E (4U rack) equipped with Intel Xeon or Core i7 processors, minimum 16 GB to 32 GB ECC RAM, and hardware RAID 1 or RAID 5 storage.

  • The Architectural Role of Thin Clients (SIMATIC Industrial Thin Clients - ITC):

  • A Thin Client is a zero-maintenance or low-maintenance display terminal with no local hard drive, minimal RAM, and a compact embedded operating system (e.g. Linux-based Siemens ITC OS or Windows 10 IoT).
  • Thin Clients have NO capability to execute SQL Server, run PCS 7 background services, or host communications processors.
  • Legitimate Use Case: Thin Clients operate as Display Terminals for Operators:

    1. Web Architecture: Thin Clients run web browsers pointing to a WinCC WebNavigator or WinCC WebUX server.
    2. Terminal Server Architecture: Thin Clients establish Remote Desktop Protocol (RDP) sessions to a Microsoft Remote Desktop Session Host (RDSH) running WinCC/WebNavigator or virtualized OS Clients managed by a hypervisor (e.g. VMware vSphere / ESXi).
  • Management Console Integration:

  • The SIMATIC Management Console (SMMC) is not an execution platform for servers; it is a centralized administrative tool used to inventory hardware, deploy software updates, and verify installed license keys across the facility.

Step-by-Step Implementation Procedure

  1. Procure the Proper Platform for the OS Server:
    * Review the official hardware requirements in the Siemens PCS 7 Readme document (typically pages 15-18).
    * Select a certified industrial PC: SIMATIC IPC647E / IPC847E or an approved enterprise virtualization server running VMware ESXi.
    * Ensure redundant power supplies, RAID-1 SSD/SAS storage, and CP 1623 network cards are configured for the Plant Bus.

  2. Deploy Thin Clients for Operator Control Rooms and Field Consoles:
    * Select industrial thin terminals (e.g. SIMATIC ITC1900, ITC2200) for control cabinet doors or operator desks.
    * Connect the Thin Clients to the Terminal Bus (isolated from the Plant Bus).

  3. Configure Centralized Terminal / Web Services:
    * Option A: WinCC WebNavigator:

    • Install the SIMATIC WinCC/WebNavigator package on an OS Single Station or dedicated Web Server PC.
    • Configure the Internet Information Services (IIS) web server and publish process graphics via the Web View Publisher.
    • Configure the Thin Client's integrated browser or WebNavigator client app to connect to the server's URL.
    • Option B: Remote Desktop Session Host (RDS):
    • Deploy a Windows Server configured with the Remote Desktop Services role.
    • Configure Thin Clients to initiate RDP connections to the terminal server.
  4. Centralized Inventory via SIMATIC Management Console (Optional):
    * Deploy SMMC on the central Engineering Station to monitor the lifecycle, software version, and patch levels of all physical IPCs across the plant.

Verification

  1. On the physical OS Server, start WinCC Runtime; verify that CPU utilization remains stable under 30% and SQL Server services log zero disk write latency errors.
  2. Power up a SIMATIC ITC Thin Client in the field; verify that it establishes an RDP or web session to the terminal/web server within 15 seconds.
  3. Verify that the Thin Client renders process graphics, acknowledges alarms, and responds to operator clicks without lag.

Limitations and Operational Precautions

Under no circumstances can an OS Server software installation package be installed onto a Thin Client terminal. Operating WinCC WebNavigator or WebUX on thin terminals requires procuring appropriate client access licenses (SIMATIC PCS 7 OS Web Server). Virtualizing OS Servers requires high-performance hypervisor hardware and strict compliance with the Siemens virtualization whitepaper.

Engineer FAQ

Can I install a PCS 7 OS Server on a Thin Client?

No. An OS Server requires a full industrial PC or server with multi-core CPUs, RAID storage, and hardware communications processors.

What are Thin Clients used for in PCS 7?

Thin Clients are used as operator display terminals connecting via RDP or web browser to a Terminal Server or WebNavigator server.

What is the difference between an OS Server and an OS Client?

An OS Server acquires data from PLCs and manages historical databases; an OS Client provides the graphical operator display without hosting data.

What industrial PC models are recommended for OS Servers?

Siemens SIMATIC IPC647E, IPC847E, or IPC547J (or certified virtualization on VMware ESXi).

What is the SIMATIC Management Console used for?

SMMC is an administrative software tool used to inventory installed hardware/software and deploy software updates across the plant network.

Technical References

Related Articles

Related Tags

  • OS Server
  • Thin Client
  • SIMATIC ITC
  • Hardware Requirements
  • SIMATIC IPC
  • WebNavigator
  • Terminal Bus
  • PCS 7 V9.1
20 respuestas