Configuring WinCC Picture Hierarchy Inheritance and User Tag Deployment in SIMATIC PCS 7 Multi-Client Architectures

In SIMATIC PCS 7 multi-client architectures (1 ES, 2 OS Servers, 4 OS Clients), resolving issues where newly generated objects fail to display on process pictures, manually created tags on the ES do not propagate to clients, and specific operator stations cannot execute controls requires configuring three foundational settings: first, enable 'Picture receive tag from Hierarchy Folder' in the Plant Hierarchy properties so picture windows inherit the '@PCS7' tag prefix; second, create custom tags directly on the OS Server project and execute 'Generate Server Data' to propagate them to OS Clients via server packages; third, assign the client Windows user to the 'SIMATIC HMI' user group and grant Level 5/6 permissions in WinCC User Administrator.

Plant Hierarchy Tag Prefix Inheritance and Picture Windows

In SIMATIC PCS 7, process pictures are engineered to be modular and reusable through the Plant Hierarchy (PH):
1. The Role of Hierarchy Folders:
- Each folder in Plant View represents a physical plant area, unit, or equipment module (e.g. Plant1/UnitA/Reactor1).
- When a process picture (.pdl) is assigned to a hierarchy folder, it inherits the structural tag path of that folder.
2. The 'Picture receive tag from Hierarchy Folder' Property:
- If an engineer creates a graphic picture without linking it to the hierarchy folder properties, the picture window lacks the internal @PCS7 tag prefix.
- When the OS compiler runs, block icons are generated, but faceplates and dynamic symbols cannot resolve their tag connections because the parent picture does not pass the folder path to the child faceplate windows.
- Enabling Picture receive tag from Hierarchy Folder in picture properties binds the folder's hierarchical string to the picture's TagPrefix property automatically.

Propagating Custom Tags to OS Clients via Server Packages

A common operational misunderstanding in multi-client systems concerns where internal tags must be created:
- The Local ES Tag Fallacy:
* If an engineer manually inserts an internal tag (e.g. @Custom_Global_Mode) into Tag Management on the Engineering Station's local WinCC project, that tag exists strictly in the local ES database.
* Downloading to an OS Client does not transfer internal tags created on the ES because OS Clients read process data through Server Packages (<Project_Name>.pck) published by the OS Servers.
- Correct Tag Propagation Workflow:
1. Open the OS Server project in WinCC Explorer on the ES.
2. Create the required internal tag or communication variable in the OS Server's Tag Management.
3. Right-click Server Data in the OS Server navigation tree and select Generate.
4. In the OS Client project, right-click Server Data > Load, and select the updated server package.
5. Download the OS Client project to the target operator stations.

Resolving Client-Specific Control Lockouts and Permissions

When three out of four OS Clients can issue setpoint changes and start motors, but one specific client station cannot control equipment (buttons grayed out or permission denied):
1. Windows User Group Membership:
- On the problematic client PC, open Windows Computer Management (compmgmt.msc).
- Check Local Users and Groups > Groups.
- Verify that the active logged-in Windows user is an explicit member of the local SIMATIC HMI group. Without this membership, WinCC suppresses write commands to the server via DCOM.
2. WinCC User Administrator Area Authorizations:
- Open User Administrator on the OS Server.
- Select the user account.
- Verify that the user has authorization for Area 1, Area 2, etc. (Level 5 Process controlling).
- In PCS 7, authorizations can be assigned on a per-plant-area basis. If Client 4 is assigned a fixed default user whose authorization table omits that specific plant unit, controls are disabled.

Multi-Client Configuration and Synchronization Parameter Table

The following table details configuration rules across PCS 7 multi-client components:

Architectural ComponentConfiguration LocationMandatory SettingOperational PurposePicture Hierarchy BindingPlant Hierarchy > Picture Properties'Picture receive tag from Hierarchy Folder' = ActiveAutomatically assigns @PCS7 tag prefix to picture windowsCustom Server TagsOS Server > Tag ManagementCreated on Server ProjectEnsures variable resides in central runtime databaseServer PackageOS Server > Server Data'Generate Server Data' executedExports tag catalog and alarm schema for OS ClientsClient Package LinkOS Client > Server Data'Load Server Data' executedBinds client graphic controls to server package tagsClient Control RightsWindows User GroupsUser added to SIMATIC HMIAuthorizes DCOM write access from client to server

Verification

To confirm that pictures inherit tags and clients possess full control rights:
1. Open the process picture on an OS Client: confirm that all newly added block icons and instruments populate with live process values.
2. Open a motor faceplate from that picture: verify that the faceplate header displays the full hierarchical tag name (e.g. Area1/UnitA/Pump101).
3. On the previously locked client (Client 4), log in with standard operator credentials.
4. Click a motor start button: confirm that the command execution prompt appears, click Start, and verify that the PLC output energizes immediately.
5. In the WinCC Alarm Logging list, confirm that the operator action is logged with the client's workstation name and username.

Limitations and Operational Precautions

When managing multi-client PCS 7 systems:
1. Never Create Production Tags on Client Projects: OS Clients should contain zero process tags in their local Tag Management. All process tags must reside exclusively on the OS Server projects to maintain database synchronization.
2. Synchronize OS Project Editor Across All Stations: Whenever the OS Project Editor is updated on the OS Server, it must be re-run on all OS Clients to ensure screen resolutions, alarm line formatting, and horn configurations match.
3. Simatic Shell Adapter Priority: Ensure that Simatic Shell on all clients and servers is bound to the Terminal Bus network adapter; binding to the wrong adapter breaks server package loading.

Engineer FAQ

Why did copying the project from Client 2 to Client 4 resolve the issue?

Copying the project replaced a corrupted local client database (.mcp / .ldf), local computer name misconfiguration, or broken server data package link with a verified working client template.

Can an OS Client communicate if its computer name is not registered on the OS Server?

Yes, provided the OS Client project references the server package correctly and the client user account exists with matching credentials on the OS Server's Windows operating system.

What does 'Generate Server Data' actually create?

It compiles an export file (<Project_Name>.pck) containing the server's symbolic tag names, archive names, message classes, and network connection endpoints for distribution to client stations.

Why do block icons show gray text when 'Picture receive tag' is disabled?

Because without hierarchy inheritance, the block icon cannot determine which controller instance DB it belongs to, resulting in unresolved '@Tag' pointers.