Restoring Missing Operator Input Messages on PCS 7 OS Clients via Standard Server Configuration

In SIMATIC PCS 7 multi-client architectures, operator input messages (such as setpoint modifications, interlock bypasses, and manual motor starts) disappear from OS client alarm lists when the client lacks a valid 'Standard Server for Alarms' assignment. While process alarms generated by controllers continue to display via loaded server data packages, local operator actions cannot be logged without an assigned default server. To restore operator messages, open WinCC Explorer on each OS client, navigate to 'Server Data > Standard Server...', and assign the primary redundant OS server package to both 'Alarms' and 'SSM'.

Executive Summary

In SIMATIC PCS 7 operator stations, alarms and messages are categorized into process alarms (generated by AS driver and technological blocks like MonAnL and MotL) and operator input messages (generated locally when an operator alters a setpoint, toggles a manual mode, or activates an interlock bypass). A recurring issue in PCS 7 V8.0 through V9.1 environments is the sudden disappearance of operator input messages from the OS client message lists, even while process alarms, warnings, and acknowledgments function normally.

Because OS clients operate without local runtime databases, they rely entirely on WinCC OS Servers to store and timestamp events. However, the transmission of client-initiated operator actions differs from passive alarm display: the client requires an explicit, designated target server known as the 'Standard Server'. When server data packages are updated, or if an Engineering Station is renamed, the Standard Server configuration on OS clients can become unlinked or blank. This guide details the underlying WinCC client-server messaging architecture and provides the step-by-step procedure to re-establish Standard Server bindings.

Architecture and Fundamental Mechanics

The PCS 7 OS client-server communication topology distinguishes between subscribing to alarm archives and publishing new operator events:

Process Alarm Subscription: OS clients load WinCC Server Data packages (*.pck) generated by each OS Server pair. These packages inform the client which OS servers host specific process tags and alarm archives. When an AS block asserts an alarm via ALARM_8P, the OS server logs it to its local SQL database, and the client displays it via standard OPC/WinCC channel subscriptions.
Operator Event Publishing: When an operator interacts with an APL faceplate (e.g., clicking 'Start' on a motor or modifying a setpoint slider), the WinCC APL C-script or VBS script invokes the WinCC function SetTag... and simultaneously generates an operator input message (Message Class: 'Operation Message' / 'Bedienmeldung', Class 10/11) to record the user ID, workstation name, old value, and new value for audit trails.
The Standard Server Requirement: Because an OS client may load packages from multiple independent OS servers (e.g., Boiler Server, Turbine Server, Water Treatment Server), the client does not know which server's SQL database should archive client-local events. WinCC resolves this via the 'Standard Server' configuration:
- Standard Server for Alarms: Designates the primary OS server database where client-generated operator messages are recorded.
- Standard Server for SSM (Split Screen Manager): Designates the server responsible for coordinating picture layouts, trend groups, and multi-monitor client screen configurations.

If the 'Standard Server for Alarms' is unassigned (shows <No standard server> or is blank), the client's internal messaging engine discards operator input messages at runtime because there is no target database endpoint. Consequently, process alarms from the plant remain visible, but audit trails for manual actions vanish.

Step-by-Step Implementation Procedure

Follow these steps to configure the Standard Server and restore operator messages across all PCS 7 OS Clients:

Regenerate and Download Server Data Packages:
- On the Engineering Station (ES) in SIMATIC Manager, select the primary OS Server project (e.g., OS_SRV).
- Right-click OS_SRV and select 'Options > OS > Generate Server Data'.
- Ensure the server data package generates without errors.
- If OS Servers and OS Clients are part of the same multiproject, server data packages are updated across client projects automatically during project compilation.
Open WinCC Explorer on the OS Client Project:
- In SIMATIC Manager Component View, expand your OS Client station and double-click the WinCC project (OS_CLT.mcp) to open WinCC Explorer.
- (Alternatively, perform this configuration locally on the physical OS Client station if working outside centralized ES downloads).
Configure Standard Server Assignments:
- In the WinCC Explorer project tree, locate and right-click 'Server Data'.
- Select 'Standard Server...' from the context menu.
- In the 'Configure standard server' dialog window, locate the component list:
- Component 'Alarms': Click the dropdown menu in the 'Server symbolic name' column and select your primary OS server package (e.g., OS_SRV_Package_Name).
- Component 'SSM' (Split Screen Manager): Select the same primary OS server package.
- Component 'User Archives' (if used): Select the appropriate server package.
- Click 'OK' to save the assignments and close the dialog.
Replicate Settings to All OS Clients:
- Repeat Step 3 for every OS Client project defined within the multiproject.
- In SIMATIC Manager, right-click the OS Client folder and execute 'PLC > Download' to transfer the updated configuration to each physical OS Client station.
Restart WinCC Runtime on OS Clients:
- On each physical OS Client, deactivate WinCC Runtime if active.
- Restart WinCC Runtime to allow the messaging subsystem to initialize the new standard server communication sockets.
- In SIMATIC Manager, verify that OS Client projects compile cleanly during subsequent AS-OS compilations.

Verification

On a running OS Client, open any APL faceplate (such as a control valve or motor block MotL).
Execute an operator intervention: switch the drive from 'Auto' to 'Manual' mode, or alter an analog setpoint.
Open the WinCC Alarm Logging runtime screen on the OS Client and navigate to the 'Operation Messages' (or 'Operator Input Messages') view tab.
Verify that a new entry appears immediately showing the precise timestamp, the logged-in Windows username, the block tag name, and the text detailing the old and new setpoint values.
Verify that operator messages persist correctly after an OS redundancy switchover between the master and standby OS servers.

Limitations and Operational Precautions

In multi-server architectures where clients view multiple separate process areas, all operator messages from a given client are routed to the single configured Standard Server for Alarms. If that specific server goes offline and redundant partner synchronization is impaired, operator messages will buffer locally in client memory until communication is re-established. Standard server assignments must be re-checked whenever an Engineering Station or OS Server is renamed. Verify all software licensing with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why did process alarms remain visible when operator messages were lost?

Process alarms originate in the AS and are collected directly by OS servers, which broadcast them to clients via server data packages. Operator messages originate on the client and require an assigned Standard Server to accept and archive the record.

Must I configure the Standard Server on the OS Server as well?

No. The Standard Server configuration is required only on OS Clients. OS Servers write alarms and operator events directly to their own local SQL database instances.

What happens if I select different servers for Alarms and SSM?

In most standard architectures, Alarms and SSM should point to the same primary OS Server package. Splitting them across different servers is supported only in specialized multi-server architectures with dedicated central message servers.

Why does the Standard Server setting reset to blank after some updates?

If server data packages are deleted and regenerated with a new symbolic computer name, the prior Standard Server binding becomes invalid and reverts to <No standard server> until manually reassigned.