Configuring a Dedicated WebNavigator Server Across Multiple SIMATIC PCS 7 Multiprojects

To provide plant-wide visualization to office web clients across three separate SIMATIC PCS 7 multiprojects using a single web server, engineers must configure a Dedicated Web Server operating as a Multi-Client OS. This architecture loads Server Packages (.pck) generated by each WinCC OS Server across all three multiprojects into a centralized Multi-Client project. The WinCC WebNavigator Server software is installed and configured directly on this Multi-Client station, allowing it to aggregate the process pictures, tag databases, and alarm logging archives from all plant sections and serve them via HTTP/HTTPS to remote web clients without deploying third-party SCADA or OPC bridges.

Architectural Overview: Dedicated Web Server vs Standard Web Server

In large industrial manufacturing facilities, automation plants are frequently segmented into independent engineering multiprojects (e.g., Multiproject 1: Raw Materials, Multiproject 2: Synthesis, Multiproject 3: Utilities). Each multiproject possesses its own S7-400 controllers and dedicated redundant WinCC OS Servers.

When enterprise management or remote technical staff require web-based monitoring of all three sections through a single URL, two engineering configurations exist:
1. Collocated Web Server: Running WebNavigator Server directly on an existing OS Server. This method is restricted to viewing only the local OS server's data.
2. Dedicated Web Server (Multi-Client): A standalone PC station configured with the WinCC Appl. Multi-Client object. This station does not connect directly to the AS plant bus; instead, it imports compiled Server Packages from OS Server 1, OS Server 2, and OS Server 3 across the terminal bus.

By installing the WinCC WebNavigator Server on this Multi-Client station, a unified web portal is created. The Multi-Client resolves picture navigation and tag prefixes across all three multiprojects seamlessly, presenting a unified operator experience to thin-client web browsers.

Cross-Multiproject Server Package Integration

A Server Package (<ProjectName>_<ServerName>.pck) is an exported data structure containing tag names, message archives, and process picture references compiled on a WinCC OS Server.

In a multi-multiproject environment:
- Multiproject 1 exports OS_SRV1.pck.
- Multiproject 2 exports OS_SRV2.pck.
- Multiproject 3 exports OS_SRV3.pck.

Because these OS servers reside in separate multiprojects, automatic server package generation and distribution cannot occur across the multiproject boundary via SIMATIC Manager. Instead:
1. Packages are generated manually or via OS compilation on each individual OS Server.
2. The resulting .pck files are transferred (via network share or SIMATIC Shell) to the Dedicated Web Server machine.
3. The Multi-Client WinCC project explicitly loads each .pck file via the Server Data editor in WinCC Explorer.

Step-by-Step Configuration: Deploying a Multi-Client Web Server

Execute the following procedure to configure the Dedicated Web Server across three multiprojects:

Step 1: Create the Multi-Client Project in SIMATIC Manager

In the central Engineering Station or a designated coordination project, insert a new PC Station named WEB_SRV_MC.
Open HW Config for WEB_SRV_MC:
- Slot 1: Insert WinCC Appl. Multi-Client.
- Slot 2: Insert IE General (assigned to the Terminal Bus subnet).
Save and Compile HW Config.

Step 2: Generate and Export Server Packages on Each Multiproject

Open Multiproject 1. In SIMATIC Manager, right-click the OS Server project and select Compile. Ensure Server Package generation is checked.
Alternatively, open WinCC Explorer on OS Server 1, open the Server Data editor, right-click and select Create....
Repeat this process on OS Server 2 (Multiproject 2) and OS Server 3 (Multiproject 3).
Locate the generated .pck files in each project's directory under \wincproj\<OS_Name>\Packages\.

Step 3: Load Server Packages on the Multi-Client Station

Open the WinCC project on the WEB_SRV_MC station in WinCC Explorer.
In the navigation tree, right-click Server Data and select Load....
Browse and select OS_SRV1.pck. Click Open.
Repeat to load OS_SRV2.pck and OS_SRV3.pck.
In the Server Data editor, verify that all three packages appear with active status.
Right-click each loaded package, select Configure..., and specify default server assignment for alarms and archives if required.

Step 4: Configure WebNavigator Server

In WinCC Explorer on WEB_SRV_MC, right-click Web Navigator and select Web Configurator.
Create a new IIS Web Site (e.g., Port 80 or secure Port 443 HTTPS).
Specify the default start screen (a newly created plant overview navigation screen that contains buttons linking to pictures from all three imported server packages).
Run the Web View Publisher:
- Right-click Web Navigator > Web View Publisher.
- Select and publish the graphics screens (.pdl) from all imported packages.
In User Administrator, create web user accounts and assign appropriate picture access rights.

Architectural Comparison Matrix: Web Visualization Approaches

The table below compares methods for visualizing multiple PCS 7 multiprojects:

ArchitectureThin-Client URLConfiguration ComplexityData FreshnessLicensing ImpactDedicated Web Server (Multi-Client)Single URLModerate (Package export across MP)Real-time (Native WinCC channel)1x Multi-Client RT + WebNav Server license3x Separate Web Servers3 Distinct URLsLow (standard per-project setup)Real-time3x WebNavigator Server licensesThird-Party SCADA via OPCSingle URLHigh (Double engineering tags/screens)Polled / Delayed (OPC DA/UA)Third-party SCADA + 3x OpenPCS 7 licensesProcess Historian + Info ServerSingle URLLow-Moderate (Reporting focus)Archive data only (Not real-time HMI)Information Server Client Access licenses

Verification

To confirm that the Dedicated Web Server operates correctly across all three multiprojects:
1. Server Data Verification: In WinCC Explorer on the Dedicated Web Server, verify that all three server packages indicate status Loaded and valid timestamps.
2. Web Client Connection: Open a web browser on an office PC; navigate to https://<Web_Server_IP>/ and authenticate with user credentials.
3. Cross-Project Navigation: Click navigation buttons leading to pictures from Multiproject 1, 2, and 3; verify that process values update cyclically and faceplates open without connection dropouts.
4. Alarm Line Verification: Verify that the top alarm line displays active alarms originating from all three server packages simultaneously.

Limitations and Operational Precautions

Observe the following engineering constraints:
- Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation. WebNavigator Client Access Licenses (CAL) must cover peak concurrent office users.
- Server packages do not automatically update across separate multiprojects; whenever tags or alarms are modified in an OS Server project, the package must be re-exported and reloaded on the Dedicated Web Server.
- Ensure the Dedicated Web Server resides in a secure Demilitarized Zone (DMZ) with firewall restrictions preventing direct external access to the DCS terminal bus.

Engineer FAQ

Do I need to re-export server packages every time a CFC change is made?

No. Server packages only need to be re-exported and reloaded if new WinCC tags, new alarms, or new graphic screens are created or deleted. Internal CFC logic modifications that do not alter the WinCC tag interface do not require server package regeneration.

Can remote web clients issue setpoint commands through the Dedicated Web Server?

Yes, provided the web user account has write authorization in the WinCC User Administrator. If the client is strictly intended for viewing, assign read-only authorization levels.

Does WebNavigator require Internet Explorer?

Historically, WebNavigator utilized an ActiveX control running in Internet Explorer. In modern PCS 7 releases (v8.2 and v9.x), WebNavigator supports modern browsers using the WinCC WebViewer standalone application or the HTML5-based WinCC WebUX option.