Configuring SIMATIC PC Station and WinCC Application Types for OS Single Stations in PCS 7

In SIMATIC PCS 7, an OS Single Station is an autonomous operator station that connects directly to the automation system (AS) and executes its own runtime project. When configuring an OS Single Station (such as an IPC 547G with CP 1623) in SIMATIC Manager, insert a 'SIMATIC PC Station'. In the Hardware Configuration (HW Config) of this PC station, insert a 'WinCC Application' (do NOT insert WinCC Application Client) alongside the communications processor (CP 1623 or IE General). The 'WinCC Application' designation assigns full server and single-station functionality, enabling direct S7 Named Connections to the CPU. 'WinCC Application Client' is reserved exclusively for dependent OS Clients in a client-server architecture.

Executive Summary

When designing decentralized or compact control room architectures in SIMATIC PCS 7, engineers frequently deploy multiple independent OS Single Stations alongside an Engineering Station (ES). A common point of confusion arises when defining the PC station object type and WinCC application model within SIMATIC Manager and HW Config. Selecting 'WinCC Application Client' instead of 'WinCC Application' prevents the station from establishing direct S7 Named Connections to the controller and disables local tag processing. This guide clarifies the distinctions between OS Single Stations and OS Clients, details hardware configuration steps, and outlines software licensing requirements.

Architecture and Fundamental Mechanics

SIMATIC PCS 7 categorizes human-machine interface (HMI) architectures into three primary topologies:
1. OS Single Station: Operates as an independent unit hosting local archives, process graphics, and direct S7 communication channels to one or more AS controllers. In HW Config, this role requires the 'WinCC Application' component.
2. OS Server (Redundant or Standalone): Centralizes data acquisition, alarm logging, and historical archiving, serving visualization packages to distributed clients. Configured using 'WinCC Application' or 'WinCC Application (stby)'.
3. OS Client: A thin client station that does not communicate directly with the AS. It accesses process tags and alarms through loaded Server Data packages (.pdk) generated by OS Servers. In HW Config, this role requires 'WinCC Application Client'.

When a station is configured with CP 1623 communications processors, the PC Station uses the HARDNET-IE S7 communication layer. The 'WinCC Application' binds to the CP 1623 in the Station Configuration Editor (SCE), allowing NetPro to generate direct S7 Named Connections to the CPU 410-5H. If 'WinCC Application Client' is erroneously chosen, NetPro prohibits S7 Named Connections because clients lack native S7 communication drivers.

Step-by-Step Implementation Procedure

Create SIMATIC PC Station in SIMATIC Manager:
a. In SIMATIC Manager Component View, right-click the Multiproject or OS subproject.
b. Select 'Insert New Object -> SIMATIC PC Station'.
c. Rename the station to match the exact Windows computer name of the physical OS Single Station (e.g., OS_SINGLE_01).
Configure Hardware in HW Config:
a. Double-click the 'Configuration' object inside the newly created PC station to open HW Config.
b. From the Hardware Catalog, expand SIMATIC PC Station -> HMI -> WinCC Application.
c. Drag and drop 'WinCC Application' into an empty rack slot (typically Index 1 or Index 2).
d. From the catalog, expand SIMATIC PC Station -> CP Industrial Ethernet -> CP 1623.
e. Drag and drop 'CP 1623' into another empty slot and assign its IP address, subnet mask, and connect it to the merged Plant Bus subnet.
f. Save and compile HW Config.
Configure S7 Named Connection in NetPro:
a. Open NetPro from SIMATIC Manager.
b. Highlight the 'WinCC Application' object inside OS_SINGLE_01.
c. In the connection table below, right-click an empty row and select 'Insert New Connection'.
d. Select the target CPU 410-5H controller and set Connection Type to 'S7 connection'.
e. In connection properties, verify that the Local ID is designated as an 'S7 connection' and check the 'Named Connection' option.
f. Save and compile the network configuration.
Commission Station Configuration Editor and Download:
a. On the physical IPC 547G, launch the Station Configuration Editor.
b. Add the 'WinCC Application' at the exact rack index configured in HW Config.
c. From SIMATIC Manager, select the PC Station and download the hardware configuration via 'PLC -> Download'.
d. Compile the OS project and execute the target OS download.

Verification

In NetPro, verify that the S7 Named Connection between the WinCC Application and the CPU 410-5H reports 'Active' with 0 compilation errors.
In Station Configuration Editor on the IPC 547G, confirm that the WinCC Application and CP 1623 display steady 'Ready' status with yellow operational icons.
Launch WinCC Runtime on the OS Single Station: verify that process screens update and values show valid quality codes.
Open WinCC Channel Diagnosis: confirm the Named Connection channel displays 'OK' with active read/write telegram counts.

Limitations and Operational Precautions

Each OS Single Station requires an autonomous 'SIMATIC PCS 7 OS Software Single Station' runtime license, plus AS RT PO and OS RT PO capacity licenses corresponding to its active process objects. OS Single Stations cannot serve process data to other OS Clients; if client visualization is needed, an OS Server architecture must be selected. License requirements and MLFB numbers should be validated with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Can two OS Single Stations communicate with the same CPU 410-5H simultaneously?

Yes. The CPU 410-5H supports multiple independent S7 Named Connections, allowing two or more OS Single Stations to read and write process data concurrently.

What is the difference between WinCC Application and WinCC Application Client?

'WinCC Application' represents a full server or single station with direct AS communication and archiving. 'WinCC Application Client' represents a client that displays data sourced exclusively from an OS server.

Can an OS Single Station be converted into a redundant server pair later?

Yes, by adding a redundant partner PC station, reconfiguring the WinCC Application to 'WinCC Application (stby)', and updating licenses to OS Server Redundancy.

Why does NetPro give an error when trying to create an S7 connection from an OS Client?

OS Clients (WinCC Application Client) do not support direct S7 connections to automation systems; they obtain process values exclusively via OS Server data packages.