WinCC Server Location: SCADA Architecture Best Practices

Physical placement of the WinCC Server, WinCC Redundant Server, and WinCC clients is governed by network reach, redundancy cable length, control-room environmental conditions, and the license model. The WinCC server hosts the active project, the process image, historical archives, alarms, and reports, and serves these to all online clients. There is no hard rule that a server must sit beside the PLC; the determining factors are topology, latency, redundancy, and operator workflow.

1. WinCC Server/Client Architecture Overview

The WinCC server is the central data provider. It runs the project, holds the tag database, the alarm/log archive, the picture database, and the report templates, and publishes this data to clients over the network. A WinCC client is a viewer/operator station: it loads the project data from the server and exchanges operator commands, but does not hold archives of its own unless it is configured as a stand-alone with its own archive.

Per Siemens documentation, "The WinCC server provides the process and log data, alarms, screens, and reports to its online WinCC clients," and the server project is stored either in the default WinCCProjects folder or in a custom shared folder that all clients can resolve through UNC paths. See the Clients and servers (RT Professional) reference and the Activating and deactivating projects on the WinCC server procedure.

2. Component Roles and License Implications

The license model matters for placement: a server cannot legally serve clients without a valid server license, and a client can only connect to a server for which it is authorized. The redundant server is a separate license that must be paired with the primary server's project.

3. Network Reach: Distance Is Effectively Unlimited Over TCP/IP

Distance between the WinCC server and its clients is constrained only by the network. Standard TCP/IP routed networks, VLANs, and even WAN links with sufficient latency budget allow clients to be located anywhere they can resolve the server hostname and reach the WinCC ports (default TCP 102 for S7Comm, plus configured WinCC RPC/UDP ports). Practical limits are:

• Latency: Keep round-trip time under ~100 ms for comfortable operator response; archive sync tolerates more, but the user archive and alarm pipeline begin to feel sluggish above ~250 ms.
• Bandwidth: A picture swap with full graphics typically peaks at 1-3 MB per second on first load; steady-state traffic for a 5,000-tag process is usually under 500 kbit/s.
• Routing: All WinCC stations must be in routable subnets or have explicit routes/relays (e.g., S7 routing via the PLC when crossing Security Modules).

Because the network abstracts distance, the WinCC server is often placed in a centralized control room rather than a field cabinet, and clients are spread across multiple control rooms, engineering offices, and remote plants.

4. The One Distance That Does Matter: Server-to-Redundant-Server

The WinCC Redundancy package synchronizes partner servers using a dedicated serial redundancy cable (or a serial-over-UDP fallback). The maximum cable length is the electrical limit of the serial interface used:

This single constraint is the primary reason both servers are co-located in the same control room, on the same equipment rack, often in adjacent 19" chassis. When co-location is not possible, an RS-422 extension with proper shielding and a 100 Ω termination at each end is the field-proven solution.

5. Recommended Placement Patterns

5.1 Pattern A: Centralized Control Room (Most Common)

1. Primary server and redundant server are installed in the same control-room server rack, separated by 1-3 U to allow independent power feeds and to keep the redundancy cable under 3 m.
2. Clients are installed at every operator desk, in the engineering office, and in a remote monitoring room connected by plant LAN.
3. The PLCs are typically in field cabinets distributed across the plant and connect to the server rack via the plant industrial Ethernet backbone.

5.2 Pattern B: Two Control Rooms (Geographically Redundant)

1. Each control room hosts a server. The two servers act as the redundant pair and are linked via RS-422 (1,200 m) or serial-over-Ethernet.
2. Clients at each location connect to their local server for low latency, with automatic failover to the remote server on local failure.
3. The PLCs are reached through the plant backbone from both server locations; ensure both servers have independent network paths to the controllers (no shared single switch in the path).

5.3 Pattern C: Field Cabinet Server (Rare, Justified Only by Process Criticality)

1. When a process must survive a complete control-room loss, the server sits in a hardened field cabinet close to the PLCs.
2. The redundant server is typically still in the control room, with the redundancy cable extended via RS-422.
3. Remote monitoring clients connect over the plant network to whichever server is currently active.

6. Control-Room Environmental Requirements

Server-class hardware for WinCC should be installed in an environment that meets the manufacturer's server specs. Typical targets for industrial server rooms:

A field cabinet generally cannot meet these conditions long-term. If the process dictates a field-cabinet server, use an industrial panel PC (e.g., SIMATIC IPC) rated for the cabinet's temperature range, and budget for more frequent storage and fan replacements.

7. Project Folder and Path Resolution

The server project must live on a path that all clients can resolve. Two supported placements:

• Local default path: C:\Program Files\Siemens\Automation\WinCC\WinCCProjects\<ProjectName> on the server. Clients reach it via the WinCC server name and the configured shared project directory.
• Custom shared folder: A UNC path such as \\SCADASVR01\WinCCProjects\LineA configured in the project properties. WinCCStart is launched from the Windows Start menu ("Start > All Programs > Siemens Automation > WinCC > WinCCStart") and the project is activated from this path.

Regardless of where the server hardware physically sits, the folder must be writable by the WinCC service account and reachable by the redundancy partner so that mirror activations complete cleanly after a failover.

8. Network Architecture Diagram (Inline SVG)

The diagram shows a typical Pattern A layout: PLCs in field cabinets at the plant edge, both servers co-located in the control-room rack with a short redundancy link, local clients on the operator floor, and remote-monitoring clients anywhere on the WAN.

9. Commissioning and Verification Checklist

1. Confirm the server's WinCCProjects folder is shared and that the redundancy partner has read/write access.
2. From the redundancy partner, open \\SCADASVR01\WinCCProjects\<Project> in Explorer and verify the project files list without error.
3. Activate the project on the primary server via WinCCStart; verify the runtime window appears and tags begin updating from the PLCs.
4. On the redundant server, configure the redundancy partner in the project properties; the redundancy icon in the system tray should report "Partner reachable" within a few seconds.
5. From each client, launch the WinCC RT client and confirm the project loads from the server. Force a manual failover to verify the client reconnects to the new primary within its configured timeout (default 60 s).
6. From the remote monitoring client, verify picture load time, alarm visibility, and user-archive reads over the WAN link. Document measured round-trip time.

10. Troubleshooting Placement-Related Issues

11. Decision Path Summary

Use this matrix to converge on a placement quickly:

• Single control room, no geographic redundancy required: Pattern A; both servers in the same rack.
• Two control rooms in the same building, < 1,200 m apart: Pattern B with RS-422 redundancy link.
• Two control rooms on different sites: Pattern B with serial-over-Ethernet, or accept the longer failover time and rely on client auto-reconnect.
• Process must survive control-room loss: Pattern C with field-cabinet server; redundant partner stays in the control room.
• Remote monitoring only, no local control room: Pattern A; remote clients connect over the WAN to the centralized server.

12. Field-Proven Caveats

• The WinCC server's load (tag count, archive write rate, alarm rate) is the determining factor for hardware sizing, not the distance to PLCs. A 50,000-tag archive server belongs in a server room regardless of where the PLCs are.
• Redundant servers must run the same WinCC version, the same project revision, and ideally the same OS patch level. Drift between partners is a documented cause of failover failures.
• Clients do not need to be on the same subnet as the server; they only need to be on a network where S7Comm (TCP 102) and the WinCC RPC ports are reachable.
• Activating a project on the server is a one-time-per-revision operation; the clients pick up the new project on the next load, not at the moment of activation. Schedule client re-launches if a hot client reload is not configured.