Installing SIMATIC PCS 7 Web Server and WinCC: Architecture and Package Deployment Guide

In SIMATIC PCS 7, a dedicated Web Server is an OS Client workstation with the 'WinCC WebNavigator Server' package installed alongside Microsoft Internet Information Services (IIS). You do not install standalone WinCC on the web client; Web Clients require only standard web browsers and the lightweight WebNavigator Client plugin. For combined single stations, WinCC Runtime and WebNavigator Server can coexist on the same PC.

PCS 7 Web Access Architecture: Web Server vs. Web Client

In modern process plant operations, supervisory personnel, plant managers, and remote maintenance specialists require secure, browser-based visualization of plant operations without occupying dedicated control room consoles.

In SIMATIC PCS 7, remote web visualization is provided by SIMATIC WinCC WebNavigator (or modern WinCC WebUX).

When preparing to install the web option in a multi-station PCS 7 environment, commissioning engineers frequently face confusion regarding software package distribution:
* 'Do I install WinCC Runtime on the Web Server?'
* 'Do I install WinCC Runtime on the remote Web Client laptop?'
* 'What software packages must be selected from the PCS 7 installation media?'

Understanding the three-tier web architecture resolves this confusion:
1. The Web Server: Acts as the central web application gateway. It hosts Microsoft Internet Information Services (IIS), translates WinCC process graphics into web-optimized vector formats, and handles client authentication.
2. The Web Client: The remote laptop, office PC, or mobile tablet. It requires zero WinCC Runtime software; it connects via standard web browser (Internet Explorer or modern browser) and downloads a lightweight plugin or renders pure HTML5 (WebUX).

Software Package Requirements Across Node Types

The software packages deployed depend on whether the architecture uses a dedicated or combined server topology:

Dedicated Web Server Architecture (Standard Best Practice for PCS 7):
* The Web Server is physically and logically configured as a PCS 7 OS Client.
* Software installed on the Web Server:
- PCS 7 OS Client software (installs underlying WinCC client libraries).
- WinCC WebNavigator Server (from the PCS 7 DVD optional packages).
- Microsoft Internet Information Services (IIS) with ASP.NET extensions.
- Role: It loads server packages from redundant OS Servers and serves web clients, shielding control room OS Servers from direct corporate LAN traffic.
Combined OS Single Station / Web Server Architecture (Small Systems):
* Both WinCC Runtime Server and WinCC WebNavigator Server reside on the same physical PC.
* Acceptable for small utilities or pilot plants with fewer than 3 concurrent web clients.
The Web Client Station:
* Do NOT install WinCC or PCS 7 DVD software on client laptops!
* The client connects via browser to http://<WebServerName>/.
* The Web Server automatically prompts the user to download and install the lightweight WebNavigatorClient.exe plugin (or renders natively via WebUX).

Step-by-Step Installation and IIS Configuration Workflow

1. Enable Microsoft Internet Information Services (IIS)

Prior to installing the Siemens Web package, enable mandatory Windows IIS features:
1. Open Control Panel > Programs and Features > Turn Windows features on or off.
2. Expand Internet Information Services:
* Enable Web Management Tools > IIS Management Console.
* Enable World Wide Web Services > Application Development Features > ASP.NET, .NET Extensibility, ISAPI Extensions, ISAPI Filters.
* Enable Common HTTP Features > Default Document, Directory Browsing, HTTP Errors, Static Content.
* Enable Security > Request Filtering, Windows Authentication.
3. Click OK and allow Windows to complete feature installation.

2. Install Web Server Packages from the PCS 7 DVD

Insert the SIMATIC PCS 7 DVD 2 (Optional Packages).
Launch Setup.
In the package selection tree:
* Select SIMATIC WinCC / WebNavigator Server.
* (Optional) Select SIMATIC WinCC / DataMonitor or WinCC WebUX.
Complete installation and restart the PC.

3. Configure the Web Configurator in WinCC Explorer

On the Web Server PC, open the WinCC OS project in WinCC Explorer.
In the navigation tree, right-click Web Navigator and select Web Configurator.
Follow the wizard steps:
* Create a new standard web site (default port 80 or SSL port 443).
* Specify the default home page (Default.asp).
* Configure user authentication (Windows integrated authentication or WinCC user credentials).
Run the Web Publisher utility to publish process pictures (.pdl) into web-optimized graphics.

4. Connect from the Web Client

On the client office PC, open Internet Explorer.
Navigate to http://<WebServer-IP-Address>/.
Follow the browser prompt to install WebNavigatorClient.exe.
Log in with authorized credentials; verify process graphics render identically to control room screens.

PCS 7 Web Access Software Package Matrix

Workstation RoleRequired Base SoftwareRequired Web PackageLicense RequirementDedicated Web ServerPCS 7 OS ClientWinCC WebNavigator Server + IISWinCC/WebNavigator Server (x clients)Combined Single StationPCS 7 OS Single StationWinCC WebNavigator Server + IISWinCC/WebNavigator Server (x clients)Remote Web ClientNone (Standard Windows)WebNavigator Client Plugin (or Browser)Zero client licenses (Server-pooled)Mobile Tablet (WebUX)None (iOS / Android / Chrome)WinCC WebUX ServerWinCC/WebUX Server (x clients)

Verification

On the Web Server, open IIS Manager; confirm the WinCC_WebNavigator website is in status Started.
From a remote client PC on the plant office network, open a web browser and navigate to the Web Server URL.
Authenticate with an authorized operator username and password.
Confirm the plant overview mimic loads within 3 seconds.
Invert a digital status bit in the AS; confirm the web client screen updates dynamically in real time without screen refresh.

Limitations and Operational Precautions

Demilitarized Zone (DMZ) Architecture: Never connect a Web Server directly to the public Internet without placing it inside a secured DMZ bounded by dual industrial firewalls.
ActiveX Controls on Clients: Classic WebNavigator requires ActiveX execution, restricting clients to Internet Explorer or IE-mode in Microsoft Edge. For cross-browser / non-Windows clients, deploy WinCC WebUX.
Licensing Sizing: WebNavigator licenses are pooled concurrent client licenses (e.g. 1, 3, 10, or 50 simultaneous client sessions). Exceeding concurrent user quotas denies access to additional users.

Engineer FAQ

Do I need to buy a license for every computer that views the WebNavigator?

No. WinCC WebNavigator utilizes a server-side concurrent licensing model. If you purchase a 5-client license, any computer can connect, but a maximum of 5 concurrent sessions can be active simultaneously.

What is the difference between WebNavigator and WebUX?

WebNavigator relies on Windows ActiveX technology and provides complete pixel-perfect SCADA functionality matching native WinCC. WebUX utilizes pure HTML5, allowing platform-independent access from smartphones, tablets, and non-Windows browsers.